Power control using at least one power control parameter

Abstract

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] Cross-references to related applications

[0002] 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

[0003] 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

[0004] The following abbreviations are defined herein, at least some of which are referred to within the following description: Third Generation Partnership Project (“3GPP”), Fifth Generation (“5G”), QoS for NR V2X communications (“5QI / PQI”), Authentication, Authorization, and Accounting (“AAA”), Acknowledgment (“ACK”), Aperiodic CSI (“A-CSI”), Application Function (“AF”), Authentication and Key Agreement (“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 (“BD”), Background Data Transfer (“BDT”), Beam Failure Detection (“BFD”), Beam Failure Recovery (“BFR”), Binary Phase Shift Keying (“BPSK”), Base Station (“BS”), Buffer Status Report (“BSR”), Bandwidth (“BW”), Bandwidth Part (“BWP”), Cell RNTI (“C-RNTI”), Carrier Aggregation (“CA”), Channel Access Priority Class (“CAPC”), Contention-Based Random Access (“CBRA”), Component Carrier (“CC”), Clear 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 Grant (“CG”), Closed Loop (“CL”), Coordinated 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 Spread (“DFTS”), Downlink Control Information (“DCI”), Downlink Feedback Information (“DFI”), Downlink (“DL”), Demodulation Reference Signal (“DMRS”), Data Network Name (“DNN”), Data Radio Bearer (“DRB”), Discontinuous Reception (“DRX”), Dedicated Short-Range Communications (“DSRC”), Distributed Unit (“DU”), Downlink Pilot Time Slot (“DwPTS”), Enhanced Clear 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 Multiplex (“FDM”), Frequency Division Multiple Access (“FDMA”), Frequency Division Orthogonal Cover Code (“FD-OCC”), Frequency Range 1 - sub 6 GHz and / or 410 MHz to 7125 MHz (“FR1”), Frequency Range 2 - 24.25 GHz to 52.6 GHz (“FR2”), Generic Area Description (“GAD”), Guaranteed Bit Rate (“GBR”), Group Long (“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”), Generic 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 Acknowledgement (“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”), Identity or Identifier (“ID”), Information Element (“IE”), International Mobile Equipment Identity (“IMEI”), International Mobile Subscriber Identity (“IMSI”), International Mobile Telecommunications (“IMT”), Internet of Things (“IoT”), Key Management Function (“KMF”), Layer 1 (“L1”), Layer 2 (“L2”), Layer 3 (“L3”), License Assisted Access (“LAA”), Local Area Data Network (“LADN”), Local Area Network (“LAN”), Load Based Equipment (“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”), Medium Access Control (“MAC”), Multimedia Broadcast Multicast Service (“MBMS”), Maximum Bit Rate (“MBR”), Master Cell Group (“MCG”), Minimum Communication Range (“MCR”), Modulation 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 Originated (“MO”), Massive MTC (“mMTC”), Message A PUSCH Occasion (“MPO”), Maximum Power Reduction (“MPR”),Multi-panel transmission and reception (“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 acknowledgement (“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 mode-3 in LTE V2X), network slice instance (“NSI”), network slice selection assistance information (“NSSAI”), network slice selection function (“NSSF”), network slice selection policy (“NSSP”), non-supplemental uplink (e.g., “normal” uplink carrier) (“NUL”), operation, administration, 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 (“PCC”), primary cell (“PCell”), policy control function (“PCF”), physical cell identity (“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”), PC5 QoS class identifier (“PQI”), physical random access channel (“PRACH”), physical resource block (“PRB”), proximity service (“ProSe”), positioning reference signal (“PRS”), physical sidelink control channel (“PSCCH”), primary 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”), RA RNTI (“RA-RNTI”), Radio Access Network (“RAN”), Random (“RAND”), Radio Access Technology (“RAT”), Serving RAT (“RAT-1”) (serving Uu), Other RAT (“RAT-2”) (no service with respect to 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 Acknowledged Mode (“RLC-AM”), RLC Unacknowledged Mode / Transparent Mode (“RLC-UM / TM”), Radio Link Failure (“RLF”), Radio Link Monitoring (“RLM”), Radio Network Temporary Identifier (“RNTI”), Reference Signal (“RS”), Remaining Minimum System Information (“RMSI”), Radio Resource Control (“RRC”), Radio Resource Management (“RRM”), Resource Spread 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 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”), Spatial Division Multiplexing (“SDM”), Service 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 Identity / Identity 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 Assistance Information (“S-NSSAI”), Scheduling Request (“SR”), Signaling Radio Bearers (“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 Concealed Identifier (“SUCI”), Scheduling User Equipment (“SUE”), Supplementary Uplink (“SUL”), Subscriber Permanent Identifier (“SUPI”), Tracking Area (“TA”), TA Identifier (“TAI”), TA Update (“TAU”), Timing Alignment Timer (“TAT”), Transport Block (“TB”), Transport Block Size (“TBS”), Transmission Configuration Indicator (“TCI”), Temporary Cell RNTI (“TC-RNTI”), Time Division Duplex (“TDD”), Time Division Multiplex (“TDM”), Time Division Orthogonal Cover Code (“TD-OCC”), Temporary Mobile Subscriber Identity (“TMSI”), Time of Flight (“ToF”), Transmit Power Control (“TPC”), Transmission Reception Point (“TRP”), Transmission Time Interval (“TTI”), Transmit (“TX”), Uplink Control Information (“UCI”), Unified Data Management Function (“UDM”), Unified Data Repository (“UDR”), User 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 can or can not be based on a resource sensing operation), Uplink (“UL”), UL-SCH (“UL-SCH”), Universal Mobile

[0005] In certain wireless communication networks, power control can be used. SUMMARY

[0006] Methods for power control using at least one power control parameter are disclosed. Apparatuses and systems also perform the functions of these methods. One embodiment of a method includes receiving, at a first device, configuration information including a power offset value associated with a first plurality of resources and a first reference signal. In some embodiments, the method includes receiving the first reference signal from a second device. In certain 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 certain 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.

[0007] An apparatus for power control using at least one power control parameter includes a receiver that receives configuration information including a power offset value 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 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 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.

[0008] Another embodiment of a method for power control using at least one power control parameter includes receiving, at a first device, a first reference signal from a second device. In some embodiments, the method includes performing a first measurement on the first reference signal. In certain 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.

[0009] 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 certain 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. BRIEF DESCRIPTION OF DRAWINGS

[0010] A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments and are not therefore to be considered to be limiting of the scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings in which:

[0011] Figure 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for power control using at least one power control parameter;

[0012] Figure 2 is a schematic block diagram illustrating one embodiment of an apparatus that can be used for power control using at least one power control parameter;

[0013] Figure 3 is a schematic block diagram illustrating one embodiment of an apparatus that can be used for power control using at least one power control parameter;

[0014] Figure 4 is a diagram illustrating one embodiment of an IAB system;

[0015] Figure 5 is a diagram illustrating another embodiment of an IAB system;

[0016] Figure 6 is a diagram illustrating yet another embodiment of an IAB system;

[0017] Figure 7 is a flow diagram illustrating one embodiment of a method including transmission and / or reception of a PORS configuration;

[0018] Figure 8 is a timing diagram illustrating timing corresponding to transmission and / or reception of a PORS configuration;

[0019] Figure 9 is a flow diagram illustrating one embodiment of power control;

[0020] Figure 10 is a flow diagram illustrating one embodiment of transmitting a DL-PC grant;

[0021] Figure 11 is a flow diagram illustrating one embodiment of transmitting and receiving a DL-PC grant;

[0022] Figure 12 is a timing diagram illustrating timing corresponding to a DL-PC request and a DL-PC grant;

[0023] Figure 13 is a diagram illustrating one embodiment of a system using sounding;

[0024] Figure 14 is a timing diagram illustrating one embodiment of a communication including probing;

[0025] Figure 15 is a flow diagram illustrating one embodiment of a method for determining a transmit power setting;

[0026] Figure 16 is a flow diagram illustrating one embodiment of a method for power control using at least one power control parameter; and

[0027] Figure 17 is a flow diagram illustrating another embodiment of a method for power control using at least one power control parameter. DETAILED DESCRIPTION

[0028] As will be appreciated by those skilled in the art, aspects of the embodiments can be embodied as a system, device, method or program product. Accordingly, aspects of the embodiments can take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that can all generally be referred to herein as a "circuit," "module" or "system." Furthermore, aspects of the embodiments can take the form of a program product embodied in one or more computer readable storage devices storing machine-readable code, computer readable code, and / or program code, which is executable by a computer. The storage devices can be tangible and / or non-transitory. The storage devices can not embody signals. In a certain embodiment, the storage devices only employ signals for the reading of the code.

[0029] Certain of the functional units described in this specification can be labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module can be implemented as a hardware circuit comprising custom very-large-scale integration ("VLSI") circuits or gate arrays

[0030] Modules can also be implemented in code and / or software for execution by various types of processors. An identified module of code may, for instance, include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure or function. Nevertheless, the executables of an identified module need not be physically located together, but can include disparate instructions stored in different locations which, when joined logically together, include the module and achieve the stated purpose for the module.

[0031] Indeed, a module of code can be a single instruction, or many instructions, and can even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data can be identified within the modules and illustrated in any suitable form and organized within any suitable type of data structure. The operational data can be collected as a single data set, or can be distributed over different locations including over different computer readable storage devices. Where a module or portions of a module are implemented in software, the software portion is stored in one or more computer readable storage devices.

[0032] Any combination of one or more computer readable medium can be utilized. The computer readable medium can be a computer readable storage medium. The computer readable storage medium can be a storage device storing the code. The storage device can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0033] More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory ("RAM"), a read-only memory ("ROM"), an erasable programmable read-only memory ("EPROM" or Flash memory), a portable compact disc read-only memory ("CD-ROM"), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium can be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0034] Code for carrying out operations for embodiments can be any number of lines and can be written in any combination of one or more programming languages including an object oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the "C" programming language, assembly language, or machine code. The code can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network ("LAN") or a wide area network ("WAN"), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0035] References in the specification to “one embodiment,” “an embodiment,” or similar language mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrase “in one embodiment” or similar language in the specification do not necessarily refer to the same embodiment, but can refer to one or more but not all embodiments. The terms “including,” “comprising,” “carrying,” “having,” “containing,” and variations thereof are meant to be broad and encompass the term “consisting of.” Unless otherwise noted, the list of items does not imply that any or all of the items are mutually exclusive. Unless otherwise noted, the terms “a,” “an,” and “the” are meant to be broad and encompass the term “one or more.”

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

[0037] Aspects of the embodiments are described below with reference to schematic flowcharts and / or schematic block diagrams of methods, apparatuses, systems, and program products according to the 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 produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the schematic flowcharts and / or schematic block diagrams block or blocks.

[0038] The code can also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function / act specified in the schematic flowcharts and / or schematic block diagrams block or blocks.

[0039] The code can also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

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

[0041] It also should be noted that in some alternative implementations, the functions noted in the blocks can occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks can sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods can be conceived that are equivalent in function, logic, or effect to those illustrated, with the scope of the present disclosure intended to include such equivalents.

[0042] Although various arrow types and line types can be employed in the flowchart and / or block diagrams, these are merely meant as graphical representations of the various possible implementations of the embodiments. Many of the arrows are used to depict the flow of information between various computational stages. Other arrows are used to depict the flow of control, the sharing of information, further processing, or a combination of these. Each arrow depicted can represent one or more physical transmissions of information, logical transfers of information, or a combination of these. The various implementations of the embodiments can include variations of these descriptions, as well as other descriptions.

[0043] The description of elements in each of the figures can refer to elements of the figure being described. Commonly used reference numerals can be used throughout the description and / or drawings to refer to elements with a common function in the figures. Like numerals can refer to like elements throughout the specification and / or drawings.

[0044] Figure 1 Embodiments of a wireless communication system 100 for power control using at least one power control parameter are described. In one embodiment, the wireless communication system 100 includes remote units 102 and network units 104. While a certain number of remote units 102 and network units 104 are depicted in the Figure 1 While a certain number of remote units 102 and network units 104 are depicted in the FIGS., 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.

[0045] In one embodiment, the remote units 102 can include computing devices, such as desktop, laptop, personal digital assistant ("PDA"), tablet, smart phone, smart television (e.g., television connected to the Internet), set-top box, game console, security system (including security camera), vehicle

[0046] The network units 104 can be distributed over a geographic region. In certain embodiments, a network unit 104 can also be referred to as an access point, an access terminal, a base, a base station, a Node-B, an eNB, a gNB, a Home Node-B, a relay node, a device, a core network, an aerial server, a wireless access node, an AP, NR, a network entity, an AMF, a UDM, a UDR, a UDM / UDR, a PCF, a RAN, a NSSF, an AS, a NEF, a key management server, a KMF, or by any other terminology used in the art. The network units 104 are generally part of a radio access network that can include one or more controllers communicably coupled to one or more corresponding network units 104. The radio access network is usually communicably coupled to one or more core networks, which can be coupled to other networks, like the Internet and public switched telephone networks, among other networks. These and other elements of radio access and core networks are not illustrated but are well known generally by those having ordinary skill in the art.

[0047] In one implementation, the wireless communication system 100 is compliant with the standardized NR protocols in 3GPP, wherein the network units 104 transmit using an OFDM modulation scheme on the DL and the remote units 102 transmit on the UL using a SC-FDMA scheme or an OFDM scheme. More generally, however, the wireless communication system 100 can implement some other open or proprietary communication protocol, for example, WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA2000, ZigBee, Sigfoxx, and other protocols. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.

[0048] The network units 104 can serve a number of remote units 102 within a serving area, for example, a cell or a cell sector, via wireless communication links. The network units 104 transmit DL communication signals to serve the remote units 102 in the time, frequency, and / or spatial domains.

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

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

[0051] Figure 2One embodiment of an apparatus 200 that can be used for power control using at least one power control parameter is depicted. The apparatus 200 includes one embodiment of the remote unit 102. Furthermore, the remote unit 102 can 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 touch screen. In certain embodiments, the remote unit 102 can not include any input device 206 and / or display 208. In various embodiments, the remote unit 102 can include one or more of the processor 202, the memory 204, the transmitter 210, and the receiver 212, and can not include the input device 206 and / or the display 208.

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

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

[0054] In one embodiment, input device 206 can include any known computer input device, including a touchpad, buttons, a keyboard, a stylus, a microphone, or the like. In some embodiments, input device 206 can be integrated with display 208, e.g., as a touchscreen or similar touch-sensitive display. In some embodiments, input device 206 includes a touchscreen such that text can be input 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.

[0055] In one embodiment, display 208 can include any known electronically controllable display or display device. Display 208 can be designed to output visual, audible, 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 can include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or similar display devices capable of outputting images, text, etc. to a user. As another non-limiting example, display 208 can include a wearable display such as smart glasses, smart

[0056] In certain embodiments, display 208 includes one or more speakers for producing sound. For example, display 208 can produce an audible alert or notification (e.g., a beep or chime). In some embodiments, display 208 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all or portions of display 208 can be integrated with input device 206. For example, input device 206 and display 208 can form a touchscreen or similar touch-sensitive display. In other embodiments, display 208 can be positioned near input device 206.

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

[0058] In various embodiments, the receiver 212 can receive the first reference signal from the second device. In various embodiments, the processor 202 can: perform a first measurement on the first reference signal; calculate a first expected received power value associated with the first plurality of resources based on the first measurement; and calculate the first target received power value. In certain embodiments, the transmitter 210 can 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.

[0059] 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 transmitter 210 and the receiver 212 can be any suitable type of transmitters and receivers. In one embodiment, the transmitter 210 and the receiver 212 can be part of a transceiver.

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

[0061] In some embodiments, the receiver 312 can: receive configuration information including a power offset value associated with the first plurality of resources and the first reference signal; receive the first reference signal from the second device. In various embodiments, the processor 302 can: 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 the first target received power value. In some embodiments, the transmitter 310 can 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.

[0062] In various embodiments, the receiver 312 can receive the first reference signal from the second device. In various embodiments, the processor 302 can: perform a first measurement on the first reference signal; calculate a first expected received power value associated with the first plurality of resources based on the first measurement; and calculate the first target received power value. In certain embodiments, the transmitter 310 can 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.

[0063] In some embodiments, IAB can not be limited to a particular multiplexing and duplexing scheme, but can focus on TDM between uplink communications (e.g., with a parent IAB node and / or a donor) and downlink communications (e.g., with a child IAB node or a UE).

[0064] In certain embodiments, if uplink transmissions and downlink transmissions are not always scheduled in separate time intervals, there can be power control issues, particularly in cases where uplink communications and downlink communications share RF and antenna hardware. In various embodiments, an IAB node can be subject to power control in the uplink, which can be similar to uplink power control for a UE, but the IAB node can not perform power control in the downlink. If an IAB node wants to use the same RF chain and antenna panel for simultaneous uplink transmission and downlink transmission, the two communications can suffer from imbalance. If an IAB node simultaneously receives an uplink signal and a downlink signal, similar issues can exist. Described herein are various systems and methods for power control enhancements for IAB systems.

[0065] In some embodiments, such as for uplink power control in NR, two types of uplink power control can be used: 1) closed loop power control, which is implemented by receiving a signal from a transmitter (e.g., a 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, a UE receives a synchronization signal from which it can estimate path loss, and system information from which it can obtain information about a target received power. From the path loss and the target received power, the UE can calculate its transmission power for PRACH transmission.

[0066] In certain embodiments, power control for transmissions on PUSCH can be as follows:

[0067]

[0068] where the variables are defined in Table 1:

[0069] Table 1

[0070] P PUSCH ]]> PUSCH transmission power P CMAX ]]> Maximum transmit power per carrier [P0(j)] Normalised target received power; network configurable PL(q) Uplink path loss estimate α(j) Fractional path loss compensation parameter; network configurable μ Numerology (subcarrier spacing) parameter M RB ]] Number of resource blocks allocated for PUSCH transmission Delta TF ]] Parameter related to modulation and coding scheme (MCS) δ(l) Power adjustment due to closed loop power control

[0071] Further, the following are further defined: 1) P0+ a-PL: basic open loop power control with fractional path loss compensation; 2) Δ TF = 10- log((2 1.25γ- 1) · β), where γ is the number of information bits in the PUSCH normalized by the number of REs used for transmission (excluding DM-RS REs, etc.), and β = 1 for PUSCH containing data, but can be set to other values for Layer 1 PUSCH containing control (UCI). In practice, Δ TF The transmission power is set to 80% of the Shannon capacity. TF The value of is non-zero only for single-layer transmission. It can be disabled. For example, it should be disabled when fractional path loss compensation is used; 3) The beam indices q, j, l correspond to different values of SRI and enable beam-based power control: q allows different values of path loss corresponding to different beams, j allows different values of open-loop power control parameters (P0, a) as seen in Table 2, and l allows two values for the closed-loop procedure.

[0072] Table 2

[0073] j＝0 For random access Msg-3; always a = 1 j＝1 Grant-free PUSCH j＞1 Scheduled PUSCH

[0074] For transmission on PUCCH, a is always equal to 1 (e.g., path loss compensation for PUCCH is never fractional).

[0075] In various embodiments, the MT that is part of an IAB node has similar behavior as a UE, and thus, for uplink communication with its serving cell DU, can be subject to similar power control procedures.

[0076] Figure 4 is a diagram illustrating one embodiment of an IAB system 400. The IAB system 400 includes a network 402 (e.g., a core network) in communication with an IAB donor 404 via a first communication link 406. Further, the IAB system 400 also includes a first UE 408 in communication with the IAB donor 404 via a second communication link 410. Further still, the IAB system 400 includes a first IAB node 412 in communication with the IAB donor 404 via a third communication link 414. The IAB system 400 also includes a second UE 416 in communication with the first IAB node 412 via a fourth communication link 418. Further, the IAB system 400 includes a second IAB node 420 in communication with the first IAB node 412 via a fifth communication link 422. Further still, the IAB system 400 includes a third UE 424 in communication with the second IAB node 420 via a sixth communication link 426.

[0077] As further illustrated in detail, the network 426 is connected to the IAB donor 404 through a backhaul link 428, which can be wired. The IAB donor 404 includes a CU 430 and a DU 432. The IAB donor 404 communicates with all DUs in the system through an Fl interface. Each IAB node (e.g., 412 and 420) is functionally split into at least an MT (e.g., 434, 436) and a DU (e.g., 438, 440). The MT of an IAB node connects to the DU of a parent node, which can be another IAB node or the IAB donor 404.

[0078] The connection between the MT of an IAB node and the DU of a parent node (e.g., 414, 422, 426, 442, 444) is referred to as a wireless backhaul link. In the wireless backhaul link, the MT is similar to a UE in terms of functionality and the DU of the parent node is similar to a base station in a regular cellular wireless link. Thus, the link from the MT to the serving cell of the DU as the parent link is referred to as an uplink, while the link in the reverse direction is referred to as a downlink. In this disclosure, embodiments can simply refer to an uplink or a downlink between IAB nodes, a link between a node and its parent, a link between a node and its child, etc. without direct reference to MTs, DUs, serving cells, etc.

[0079] Each IAB donor or IAB node can serve UEs (e.g., 446) through access links (e.g., 448). An IAB system like the IAB system 400 can be designed to enable multi-hop communication (e.g., a UE can connect to a core network through access links and multiple backhaul links between IAB nodes and an IAB donor). As used herein, unless otherwise noted, an “IAB node” can generally refer to an IAB node or an IAB donor, as long as the connection between a CU and a core network is not involved.

[0080] A node, link, etc. that is closer to an IAB donor and / or a core network can be referred to as an upstream node, link, etc. For example, a parent node of a subject node is an upstream node of the subject node and a link to the parent node is an upstream link with respect to the subject node. Similarly, a node, link, etc. that is further away from an IAB donor and / or a core network is referred to as a downstream node, link, etc. For example, a child node of a subject node is a downstream node of the subject node and a link to the child node is a downstream link with respect to the subject node.

[0081] Table 3 summarizes the terminology used herein.

[0082] Table 3

[0083]

[0084] Described herein are various systems and methods for power control in an IAB system to promote higher performance in terms of resource efficiency, multi-hop latency, complexity, etc.

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

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

[0087] In certain embodiments, there can be various options regarding the structure, multiplexing capability, and / or duplexing capability of an IAB node. For example, each IAB node can have one or more antenna panels, each connected to a baseband unit through an RF chain. One or more antenna panels can be capable of serving an entire space region of interest near the IAB node, or each antenna panel or each group of antenna panels can provide partial coverage, such as in a sector. An IAB node with multiple antenna panels each serving a separate space region or sector can be referred to as a single-panel IAB node, as it behaves similarly to a single-panel IAB node for communication in each of the separate space regions or sectors.

[0088] 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 signals or receiving signals in a 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 signals and receiving signals in a frequency band simultaneously. Unlike FD radios, HD radios can be widely implemented and used in practice, and can be assumed as the default mode of operation in wireless systems.

[0089] Table 4 lists different duplex scenarios that can be used in cases where multiplexing is 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 transmitting or receiving on the downlink (or downstream) and uplink (or upstream) simultaneously; FD refers to simultaneous transmission and reception in a frequency band by the same antenna panel; and MPTR refers to simultaneous transmission and reception by multiple antenna panels, where each antenna panel transmits or receives in a frequency band at a time.

[0090] Table 4

[0091] Scenario IAB-MT IAB-DU Type S1 N1-DL-RX N1-UL-RX SDM S2 N1-DL-RX N1-DL-TX FD S3 N1-UL-TX N1-DL-TX SDM S4 N1-UL-TX N1-UL-RX FD S5 N2-DL-RX N2-UL-RX SDM S6 N2-DL-RX N2-DL-TX MPTR and / or FD S7 N2-UL-TX N2-DL-TX SDM S8 N2-UL-TX N2-UL-RX MPTR and / or FD

[0092] For example, consider scenario S1 in which a single-panel IAB node N1 receives downlink signals and uplink signals. The downlink signals can occur on a backhaul link from an IAB donor or parent IAB node. The uplink signals can be received on an access link from UE1 or on a backhaul link from child IAB node 1 (CN1) or both. The uplink signals can be power controlled so that multiple UEs and / or child nodes are capable of transmitting signals to the node simultaneously. However, the downlink signals can not be power controlled, which can create a significant imbalance between the power received at the parent node. This power imbalance can cause interference to weaker signals so that they cannot be decoded. In various embodiments, downlink power control can be provided.

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

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

[0095] In some embodiments, a parent IAB node of a subject IAB node can adjust transmission power for communications on a set of resources and inform the subject IAB node of the power adjustment through control signaling.

[0096] In certain embodiments, a parent IAB node generally configures a set of resources in a non-periodic, semi-persistent, or periodic manner in time and frequency domain. The configuration can be sent through RRC signaling, but can be conveyed through MAC or physical layer signaling such as DCI. For example, a semi-persistent configuration can be activated and / or deactivated through MAC signaling, or a non-periodic configuration can be indicated through a DCI message.

[0097] In various embodiments, information conveyed by configuration and / or other control signaling (e.g., including one or more configuration messages, which are referred to herein as Power Offset Resource Set (PORS) configurations) can include: 1) an ID for the configuration; 2) a resource set: a) resources in time: slots, symbols, periodicity of occurrence, etc.; b) resources in frequency: PRBs, BWPs, CCs, etc.; 3) a power offset (e.g., in dB relative to a reference power such as ss-PBCH-BlockPower, referenceSignalPower (which is offset from ss-PBCH-BlockPower by powerControlOffsetSS), etc.), in one example, the power offset can be a set of possible power offset values or a range of power offset values (e.g., a minimum power offset, a maximum power offset); 4) beam-based information (e.g., spatial QCL relative to a reference signal); and / or 5) a target receive power from a parent node - a target receive power at the IAB node (e.g., a PSD per RE or RB in dBm can be considered similar to a Po, which can be for a reference channel such as PDSCH and / or PDCCH or a reference signal such as a demodulation RS or CSI-RS, the IAB node can be expected to receive a channel and / or signal at the parent node at a + / - X dB of the target receive power level).

[0098] In one embodiment, an IAB node can request a value for a target receive power for channel and / or signal reception from a parent node on a resource set or generally for any resources allocated. In such an embodiment, the IAB node can determine the target receive power based on a measurement (e.g., RSRP) from the parent node and / or a target receive power setting for reception from a child node or UE that the IAB is serving. The IAB node can transmit the requested target receive power on a PUSCH or PUCCH on the MT uplink (e.g., using higher layer signaling such as a MAC control element). The IAB node can determine uplink power control parameters for the child node or UE based on the target receive power from the parent node.

[0099] After the IAB node receives 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 receive powers (RXP exp).

[0100] Figure 7 is a flow diagram illustrating one embodiment of a method 700 including transmission and / or reception of a PORS configuration.

[0101] The method 700 comprises units 702-708 executed by a parent (e.g., upstream) node and units 710-724 executed by a subject (e.g., downstream) node.

[0102] In the units 702-708 executed by the parent node, the parent node (PN) transmits 702 a PORS configuration comprising at least a time-frequency resource set T and a power offset R_ofs. The PORS configuration can comprise an index and / or a reference to a reference signal such as a SS / PBCH block or a CSI-RS.

[0103] The PN transmits 704 a reference signal while applying a reference power (TXP_ref). The reference signal is implicitly or explicitly associated with the PORS configuration by a higher layer parameter (e.g., a relative power offset with respect to the reference signal power). This reference signal can be a SS / PBCH block or a CSI-RS. The reference signal can be transmitted in a periodic manner (e.g., the transmission can occur before or after unit 702).

[0104] Next, the PN transmits 706 a DCI scheduling a signal and / or a channel (C1) such as a PDSCH on resources in the resource set T.

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

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

[0107] The N receives 712 a reference signal and measures a reference power (RXP_ref) which is typically equal to the transmitted reference power (TXP_ref) attenuated by the communication channel. The reference signal is implicitly or explicitly associated with the PORS configuration by a higher layer parameter (e.g., a relative power offset with respect to the reference signal power). This reference signal can be a SS / PBCH block or a CSI-RS. The reference signal can be transmitted in a periodic manner (e.g., the reception can occur before or after unit 710).

[0108] The N computes 714 a first expected reception power RXP_exp1 associated with the resource set T: = RXP_ref / R_ofs.

[0109] Next, the N receives 716 a DCI scheduling a signal and / or a channel (C1) such as a PDSCH on resources in the resource set T.

[0110] N also obtains 718 a second expected receive power RXP exp2 associated with a signal and / or channel (C2) from another node such as a child node (CN) or a UE. N can obtain RXP exp2 by performing measurements on communications from the CN and / or UE, such as on SRS.

[0111] N then compares 720 the two expected receive powers RXP exp1 and RXP exp2.

[0112] If the ratio between the two values exceeds a threshold Q, N can need to transmit 722 DCI to schedule the signal and / or channel C2 from the CN and / or UE on resources that do not overlap with the resource set T. In particular, N can need to schedule C2 on separate time resources, which yields a TDM approach. The threshold can depend on N’s ability to handle power imbalance.

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

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

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

[0116] In various embodiments, PORS 1 provides a power offset from PN transmissions that yields a receive power RXP1 in the N. Similarly, in such embodiments, PORS 2 provides a power offset from PN transmissions that yields a receive power RXP2 in the N.

[0117] N expects a receive 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 can be tolerated by N. Similarly, N expects a receive 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 can be tolerated by N.

[0118] PN schedules a PDSCH transmission to N that uses resources from PORS 1 and PORS 2. After having obtained the information of the power offset applied to the resources in PORS 1 and PORS 2, N can schedule a PUSCH transmission for CN1 and CN2 in the resources associated with (or multiplexed with) PORS 1 and PORS 2, respectively.

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

[0120] In various embodiments, N can request a transmit power offset request or a receive target power request similar to a DL-PC. However, in such embodiments, the request can not be for a specific transmission and can not need to be taken immediately. Instead, after having obtained a power offset request or a receive target power request from N and possibly its sibling IAB node (SN), PN can configure a new PORS or modify an existing PORS to take into account the need of each IAB node for enhanced duplexing.

[0121] In certain embodiments, N can send control signaling to PN to inform PN which PORS configurations are suitable for N. In a mobile IAB system, this information can change frequently and such updates can be sent periodically.

[0122] In some embodiments, the decision made by the subject node N can be about whether to schedule a downstream communication with a child node or UE simultaneously with an upstream communication with a parent node.

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

[0124] Figure 9 is a flowchart 900 illustrating one embodiment of power control.

[0125] In Figure 9In this, an IAB node N receives 902 a PORS configuration including a set of resources T and an associated power offset R_ofs. This configuration can be transmitted by a parent node (PN). Then, N receives 904 a reference signal such as an SS / PBCH block or a CSI-RS and performs 906 a measurement M on the reference signal. Having obtained a result of the measurement M such as an SSB-RSRP or a CSI-RSRP, N computes 908 a target receive power RXP1 based on M and R_ofs. The result of the computation can be an expected receive power with respect to a communication on the set of resources T.

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

[0127] Finally, N sets 912 uplink control parameters to the CN and / or the UE. The uplink control parameters can include one or more sets of closed-loop power control parameters such as P0, a, and / or open-loop power control parameters. The CN and / or the UE then use those parameters for communicating with N. Specifically, N can set an uplink power control parameter P based on RXP2, and then N can transmit 914 P to another wireless entity.

[0128] In various embodiments, the uplink control parameters used by the CN and / or the UE can be associated with a set of resources in the downstream that overlaps with the set of resources T in the upstream. In some embodiments, a configuration of a similar set of resources can be configured for both an upstream link and a downstream link that include the same or similar set of resources but different power control parameters, such as: 1) the upstream configuration is a PORS configuration that contains power offset information; and / or 2) the downstream configuration contains uplink power control information.

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

[0130] In some embodiments, the relationship between parameters can be maintained by implementation, as the configurations are transmitted and received by different entities, but can be configured in standard specifications in other embodiments.

[0131] In one embodiment, an IAB node (N) can perform power control when there is a significant imbalance between the power of signals received from downstream nodes {CN1, CN2, UE1, UE2} and signals received from an upstream node PN. This can occur when the power of signals received from {CN1, CN2, UE1, UE2} is significantly higher than the power of signals received from PN. The IAB node N can be able to resolve this problem completely or partially by performing uplink power control with {CN1, CN2, UE1, UE2}. However, if the uplink power control alone does not resolve the problem, N can send a power control request to PN to change its transmission power.

[0132] In various embodiments, N cannot tolerate a power imbalance higher than a threshold Q. For example, N can maintain P DL / P UL ≤ Q (and also P UL / P DL ≤ Q) to decode the received signals, where P DL denotes the received power of a downlink signal received from PN, and P UL denotes the received power of an uplink signal received from {CN1, CN2, UE1, UE2}. The received power can be a normalized value such as received power per RB or RE. The threshold Q can apply to signals that are separated by less than a value Af in the frequency domain. Then, if P DL / P UL > Q, the IAB node N can perform power control to increase the uplink power and / or decrease the downlink power.

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

[0134] As can be appreciated, Option 1 can be too constraining considering that the IAB system aims at efficient bandwidth utilization in hyper-dense deployments. Thus, N can send a power control request to PN to reduce the downlink power.

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

[0136] In some embodiments, the PN serves multiple nodes simultaneously and it can also communicate with its own parent node. Thus, the DL-PC request can or can not be admitted. The PN can therefore send a DL-PC response to the N informing it whether the DL-PC request can be admitted and how the DL-PC request can be admitted. The DL-PC response can contain one or more of the following information: 1) an identification number (ID), possibly referring to the DL-PC request ID; 2) whether the DL-PC request is granted; 3) a permitted value of power change, e.g. a ratio R DL — the value can be described in decibels (dB) and can equal or be close to the desired value contained in the DL-PC request— in one embodiment, a value between the minimum requested value and the maximum requested value can be selected; 4) time information for applying the power change, e.g. the DL-PC response can contain a reference to a certain signal and / or channel, to a certain time interval, to the transmission of the next DL-PC signaling, etc.; 5) frequency information, such as a sub-band (e.g. starting PRB and number of PRBs); and / or 6) spatial information, e.g. information of a specific beam. The DL-PC response can refer to a beam by a beam index such as CRI or by a QCL reference to a signal and / or channel such as PDCCH, PDSCH, SSB / PBCH block, etc.

[0137] In certain embodiments, the IAB node N can schedule the uplink signal based on the information (or lack thereof) in the DL-PC response. For example, the N can allow FDM between the downlink signal and the uplink signal that can only be received with sufficient power, e.g. with a power not lower than P UL ≥ Q.P DL In various embodiments, if the threshold Q is applied only to frequency gaps smaller than a value Af, the N can allow a gap of at least Af in case the expected reception power ratio exceeds Q.

[0138] Figure 10 is a flowchart 1000 illustrating one embodiment of transmitting a DL-PC grant from a responding (upstream) IAB node.

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

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

[0141] The PN can then optionally receive 1006 a DL-PC request from the N to reduce the transmission power of C2 with respect to the transmission power of Cl by at least a ratio R.

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

[0143] Next, the PN can transmit 1010 a DL-PC response informing that the power reduction of R_g := TXP / TXP_new is granted.

[0144] In certain embodiments, the PN can transmit a DL-PC response rejecting the power change.

[0145] The PN sets the transmission power TXP to the new value by letting 1012 TXP := TXP_new.

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

[0147] Figure 11 is a flowchart 1100 illustrating one embodiment of transmitting and receiving a DL-PC grant by a requesting (downstream) IAB node.

[0148] The IAB node N receives 1102 a signal and / or channel C1 from a parent node (PN) with a received power RXP. The received power is the transmission power attenuated by the communication channel and other losses.

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

[0150] In addition, the N can receive 1106 an SR and / or BSR from a UE or child node (CN) to obtain an uplink signal with an expected received power RXP exp. In certain embodiments, the N can want to receive the uplink signal from the UE and / or CN simultaneously with receiving C2 (e.g., by employing FDM). However, the expected received power from the UE and / or CN can be constrained by RXP exp.

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

[0152] To perform downlink power control, N can transmit 1110 a DL-PC request to PN to reduce the transmission power of C2 relative to the transmission power of Cl by a requested power reduction ratio R (e.g., R > RXP / (RXP_exp.Q)). The requested power reduction ratio can target at least a received power ratio that is less than the threshold Q.

[0153] N can then receive 1112 a DL-PC response (e.g., DL-PC grant) from PN granting the power reduction ratio R_g.

[0154] Next, N compares 1114 the granted power reduction R_g to the minimum value that satisfies the power ratio constraint (e.g., R_g > RXP / (RXP_exp.Q)).

[0155] If the constraint is not satisfied, N can schedule uplink signals on resources that do not overlap in time domain with C2 and can receive 1116 C2 and the uplink signals and / or channels in TDM.

[0156] If the constraint is satisfied, N can have the option to schedule uplink signals on resources that overlap in time domain with C2 and can receive 1118 C2 and the uplink signals and / or channels in SDM and / or FDM.

[0157] Figure 12 Timing diagram 1200 is a diagram illustrating timing corresponding to a DL-PC request and a DL-PC grant. Timing diagram 1200 illustrates timing 1202 corresponding to a parent IAB node (PN), timing 1204 corresponding to an IAB node (N), and timing 1206 corresponding to a child node (CN).

[0158] First, PN schedules PDSCH 1208 transmission using DCI 1210 transmitted to N. N then sends a DL-PC request 1212 to PN to obtain a change in its downlink power for transmission. PN grants this request by sending a DL-PC grant message 1214 to N. After having received the DL-PC grant message 1214, N can use DCI 1218 to schedule PUSCH transmission 1216 for CN that is frequency domain multiplexed with PDSCH 1208.

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

[0160] However, the PORS approach and the DL-PC request-grant approach can be similar. For example, consider the following for the PORS approach: 1) PN configures PORS in an aperiodic manner and schedules PDSCH to N in PORS; 2) N realizes that it can be able to FDM the PUSCH transmission from CN if PORS takes a different power offset, then it sends a power offset request to PN; 3) then, PN updates the power offset of PORS through control signaling sent to N; and 4) after the update has been obtained, N schedules PUSCH for CN on time resources that overlap with the time resources of PDSCH. A similar procedure can be followed for the DL-PC request-grant approach.

[0161] In various embodiments, a parent IAB node PN can exchange DL-PC control signaling with an IAB node N to adjust the downlink transmission power for transmissions to N. The power adjustment and information exchanged through the control signaling can facilitate duplex enhancement for N.

[0162] In certain embodiments, uplink signaling can be used to inform the parent node of a preferred power adjustment to enable simultaneous reception of downlink and uplink signals. The uplink signaling can be referred to as a power offset request, a target received power request, and / or a DL-PC request.

[0163] In some embodiments, the power offset request or the DL-PC request can be generated based on implementation (e.g., the parent node can estimate the expected received power RXP exp from CN and / or UE based on the measurement of any signal or combination of signals from CN and / or UE).

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

[0165] In certain embodiments, the latest reception power or RSRP can be specified to be associated with a particular beam or QCL parameter, especially in frequency range 2 (FR2). In some embodiments, the uplink signaling can be carried by RRC, MAC, and / or physical layer signaling such as UCI.

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

[0167] In certain embodiments, the DL-PC request can not reference a particular set of channels or resources. In such embodiments, any such request can not be admitted (e.g., can be up to the parent node to decide).

[0168] In some embodiments, downlink signaling can be used to inform the subject node of an upcoming power adjustment (e.g., in response to an earlier uplink signaling). The downlink signaling can be a PORS configuration or a DL-PC grant.

[0169] In various embodiments, the PORS configuration update or DL-PC grant by the PN can be generated based on implementation (e.g., depending on the multiple power offset requests or DL-PC requests received by the PN, transmission power limitations, regulatory constraints, etc.). In certain embodiments, a power control request can not be admitted (e.g., due to conflicting requests in ultra-dense deployments), and the decision as to what request to admit can depend on implementation.

[0170] In some embodiments, the determination of which requests are admitted can be specified in a standard document. For example, if a power control request is received in uplink, QoS regulations, higher layer signaling, etc. can dictate the behavior of the parent node. In another example, low latency traffic and / or wireless backhaul traffic can be given priority and can require a power offset request or DL-PC request associated with the traffic to be admitted based on higher layer specification requirements and / or higher layer signaling.

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

[0172] Table 5

[0173] Minimum frequency gap Maximum power ratio ​ Q1 ​ Q2 … … Delta F N ]] Q N ]]>

[0174] In certain embodiments, the IAB node capabilities for power control can include the following: 1) a number of panels; and / or 2) a maximum number of PORS configurations or a maximum number of DL-PC procedures.

[0175] In various embodiments, the information element containing the capability information can be communicated with the rest of the IAB system and / or network through higher layer signaling, for example, through RRC messages (e.g., automatically at connection time or through request-response signaling). The capability information can be used by implementation, configuration, or specification.

[0176] In some embodiments, downlink power control in some slots or symbols can be subject to power constraints assigned to signals and / or channels scheduled in those slots or symbols. For example, synchronization signals can be transmitted with fixed power that cannot be dynamically changed. In another example, there can be periodic CSI-RS for RLM and RRM. In these examples, large power adjustments to other signals and / or channels can not be admitted by the parent node since the transmission power cannot be dynamically changed.

[0177] In certain embodiments, one or more of the following rules can be specified by standards 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. can be ignored; 3) power offset in PORS configuration on slots and / or symbols containing SS / PBCH blocks, periodic CSI-RS, etc. is subject to a ratio Q with respect to SSB-RSRP, CSI-RSRP, etc.; 4) power offset request for PORS configuration on slots and / or symbols containing SS / PBCH blocks, periodic CSI-RS, etc. can be ignored or assumed invalid by any interested node; 5) DL-PC request for channels on slots and / or symbols containing SS / PBCH blocks, periodic CSI-RS, etc. can be ignored or assumed invalid by any interested node; 6) the rule can apply to the entire PORS or channel if it includes any slots and / or symbols containing SS / PBCH blocks, periodic CSI-RS, etc.; and / or 7) the rule can apply not only in the case of SS / PBCH blocks, periodic CSI-RS, etc. in the current BWP and / or CC, but also on another BWP and / or CC - e.g., in the case of in-band carrier aggregation.

[0178] In various embodiments, there can be a multi-hop scenario N1-N2-N3-N4, where: N1 is a parent node of N2; N2 is a parent node of N3; N3 is a parent node of N4; and N4 can be a child node or UE. In such embodiments, assume that N2 sends PORS configuration to N3, so that N3 will be able to enjoy simultaneous communication with N2 and N4. However, N2 can be a child node of N1 and therefore it has to follow the uplink TPC command provided by N1. In addition, N2 can also be subject to power constraints for transmission, e.g.: 1) the power ratio between simultaneous uplink transmission and downlink transmission to N1 and N3, respectively, can not exceed a threshold value that can be determined by standards or by hardware capability of N2; and / or 2) hardware and / or regulatory constraints apply to the maximum transmission power of N2, which is the sum of transmission power in uplink (to N1) and downlink (to N3) directions. Therefore, the TPC command from N1 can cause a conflict with the PORS configuration from N2.

[0179] In some embodiments, the following can apply: 1) N2 can remove the PORS configuration to avoid power imbalance conflicts - N2 can send a message to N3 informing it that the PORS configuration is no longer valid - in one embodiment, the PORS configuration can have an expiration time after which N3 can 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 updating the power offset value of the PORS or replacing the PORS configuration with a new PORS configuration - the new power offset can then allow power transmission in uplink and downlink without imposing large imbalance at N2; 3) N2 can avoid scheduling downlink transmissions on PORS as long as there is a conflict - thus, if the PORS configuration is not used for a certain period of time, N3 can assume the configuration is expired - the expiration period can be set by standards or through configuration; 4) N2 can be enabled to apply partial power compensation to avoid conflicts, for example, N2 can be enabled to deviate from the transmission power in uplink (e.g., determined by TPC commands from N1) and / or the transmission power in downlink (e.g., determined by PORS configuration) by a certain amount; 5) N2 can send a control message to N1 informing it of the constraints to follow the TPC commands - this control message can be, for example, PHR - where N2 generates the PHR based on the ratio between the transmit power and the power constraints according to PORS configuration, hardware and regulatory limits, etc., the report can be a MAC layer message, and can be triggered and generated according to RRC configuration; and / or 6) N2 can share PORS configuration information completely or partially with N1 and associate power constraints reports such as PHR to the PORS configuration.

[0180] It should be noted that problems can arise due to mobility or any other factor that changes the channel quality (such as path loss) of any wireless link in the system. The embodiments described herein can be applicable to solve any such problems.

[0181] In various embodiments, once the master node (N) obtains the expected received power in downlink and uplink, it can make scheduling decisions through 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 that are expected to have known power offset. Such grouping can depend on 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 can be able to transmit only on certain resources (e.g., certain symbols or time slots) that can correspond to resources in PORS. In this example, since the UEs and / or CNs can not know the PORS configuration directly, N can need to inform the UEs and / or CNs through control signaling (e.g., dedicated grouping signaling).

[0182] In certain embodiments, the UEs and / or CNs in a group can not be restricted to use resources in a resource set or resource pool, but can be restricted to apply a transmission power that yields a desired value (or range of values) of received power at the receiver.

[0183] In various embodiments, the IAB node can have more flexibility in power control in the uplink (e.g., due to fewer implementation constraints and / or fewer regulatory constraints). The uplink power control can be used by adding a partial compensation element to the UL-PC, which can enable the power imbalance to be compensated by the DL-PC “halfway” and by the UL-PC halfway. In some embodiments, the uplink power control can be used based on implementation in conjunction with predetermined signaling. For example, the UL-PC parameters can be included in a communication associated with PORS. Then, if a UE and / or CN is scheduled on resources in PORS, the UE and / or CN can be expected to apply an additional UL-PC term in the power control equation. This signaling can be combined with UE signaling and / or CN signaling.

[0184] One embodiment can be described with respect to scenario S1. In scenario S1, assume the problem is whether an IAB node N can receive downlink signals from its parent IAB node (PN) and uplink signals from {UE1, UE2,..., UEn} and / or child IAB nodes {CN1, CN2,..., CNm}. In addition, there can be interference from upcoming transmissions by other nodes {N1, N2,..., Nk}.

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

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

[0187] In this system 1300, the sounding interval can be configured in advance to N 1302 to recognize whether it can schedule PUSCH from CN 1306 in the presence of already scheduled PDSCH and interference before actual transmission. This is illustrated in Figure 14

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

[0189] It should be noted that the interference measurement can be achieved through cross-link interference (CLI) management mechanisms. Otherwise, the sounding approach can be employed to address power imbalance without CLI coordination.

[0190] As described herein, a DCI message can be assumed to schedule a shared channel and / or a data channel. In some embodiments, DCI formats 1_0 and 1_1 can be designated for scheduling PDSCH, and DCI formats 0_0 and 0_1 can be designated for scheduling PUSCH. Embodiments of the present disclosure can use the same or similar DCI formats for scheduling channels.

[0191] In certain embodiments, a new DCI format can be used for scheduling channels, indicating parameter values for a particular channel, triggering aperiodic configuration, and / or for other purposes. The same and / or similar information can be carried by RRC or MAC signaling.

[0192] As can be appreciated, the configurations and related signaling described herein can be beam-based (e.g., behavior related to resources, signals, or channels can be associated with spatial QCL). For example, if a subject node N intends to schedule PUSCH from CN that is quasi co-located with a reference signal with respect to spatial Rx parameters, N can obtain the expected receive power (RXP exp) by measuring the RSRP of the reference signal that is quasi co-located with the reference signal with respect to spatial Rx parameters.

[0193] Embodiments described herein can be implemented on time-frequency resources with mixed numerologies (e.g., different values of OFDM symbol duration and subcarrier spacing). Appropriate conversion of values can be expected to account for the impact of mixed numerologies. For example, if power control is applied on a resource, all resources that fully or partially overlap with the resource in time domain can follow the rules of FDM signals.

[0194] ​In various embodiments, frequency resources in the PORS can be indicated implicitly or explicitly. An example of implicit indication can be a BWP or an entire CC. Further, in some embodiments, uplink signals from a child IAB node can be distinguished from uplink signals from a UE.

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

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

[0197] In various embodiments, an IAB system can be designed to enable flexible deployments, including deployments in mobile and dynamic environments, support different deployment densities, and / or for other purposes. In some embodiments, there can be means for an IAB node to serve IAB nodes and UEs in highly unbalanced scenarios in terms of channel quality. In any IAB deployment where an IAB node N is serving multiple child nodes and UEs, each child node or UE can require a different range of transmit power values due to different values of path loss, etc. Thus, one setting of transmit power values by the PN can not enable N to multiplex communications in upstream and downstream for a wide variety of CNs and / or UEs, which can thus result in lower resource efficiency and higher latency.

[0198] In certain embodiments, a PN can configure different uplink transmit power control parameters for different sets of resources (e.g., for different symbols and / or slots). The configuration can be semi-static to enable each IAB node served by the PN to schedule downstream communications with its CNs and / or UEs in a timely manner. The configuration of uplink transmit power control parameters for a set of resources can be referred to herein as a power control resource set (PCRS) configuration and can include one or more messages, but can be referred to by any suitable name.

[0199] 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 the configuration; 2) a resource set: a) resources in time: slots, symbols, periodicity of occurrence, etc., and / or b) resources in frequency: PRBs, BWPs, CCs, etc.; 3) power control parameters (e.g., P0, a); and / or 4) beam-based information (e.g., spatial QCL with respect to a reference signal).

[0200] In some embodiments, the information included in the PCRS configuration can instead be included in another configuration, such as a slot configuration, a multi-purpose resource configuration, and / or another configuration.

[0201] In certain embodiments, the PCRS configuration can be used to associate power control parameters to communications in a resource set (e.g., on a time-frequency grid) such that the IAB node N obtains upstream power control information in advance and can schedule downstream communications accordingly. Moreover, assuming that 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.

[0202] Once the IAB node N receives the PCRS configuration, it can proceed to schedule communications with the CN and / or UEs.

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

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

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

[0206] Then, given the PCRS configuration parameters and the TPC commands, the N computes 1506 a transmit power or a range and / or interval of possible transmit powers TXPI for uplink communications with the PN and / or uplink communications (e.g., based on {P} and {C}). When the N computes TXPI, the communication can or can not have already been scheduled on the resource set T.

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

[0208] Next, N can determine 1510 whether it can schedule downlink communication and / or downstream communication D simultaneously with uplink communication and / or upstream communication with PN (e.g., whether N can schedule D while applying TXP2, where: TXPI / Q < TXP2 < TXPI x Q). To this end, N can compare the values of TXPI and TXP2. If the power imbalance between the communications of TDM does not exceed a threshold Q, N can need to ensure that the ratio between TXPI and TXP2 does not exceed this threshold in order to schedule D on time resources that overlap 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 a frequency domain separation value (e.g., in number of RBs) between resources for D and resource set T (e.g., based on the power imbalance between TXPI and TXP2).

[0209] In Figure 15 Q can be assumed to be represented in real metric and it is a value greater than or equal to 1. The value of Q can depend on node capabilities and / or can be determined by a standard, through semi-static configuration, and / or through dynamic indication.

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

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

[0212] In certain embodiments, the decision in step 1510 can be based on whether the ratio between TXPI and TXP2 exceeds the threshold Q, while in other embodiments, the decision in step 1510 can include other considerations. For example, a total transmit power can be constrained. The constraint can be determined by at least one of node capabilities, emission regulations, values set by a standard, and / or configuration and / or indication by the IAB system. In some embodiments, if N recognizes that scheduling uplink communication and / or upstream communication and downlink communication and / or downstream communication simultaneously results in exceeding the power constraint, it can not schedule D on resources that overlap in time with T.

[0213] In various embodiments, there can be a system where the power imbalance constraint Q can be determined from an average (e.g., energy per resource element (EPRE)), while the total power constraint can be determined by the maximum total energy over all resource elements. In such embodiments, the determination made by N in step 1510 can be whether a certain amount of transmission energy for the downlink communication and / or downstream communication D is spread over the set of allocated REs in a way that satisfies both constraints. For example, consider that the upper limit on the transmission energy for D is obtained by subtracting the energy required for the uplink communication and / or upstream communication from the total energy constraint. Then, if there is a lower limit on the EPRE for D based on the power imbalance constraint Q, there is a maximum number of REs that can be allocated to D. N can take this constraint into account with respect to the resource allocation in order to determine whether it can proceed to step 1512 or step 1514.

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

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

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

[0217] In some embodiments, the handover decision moves the UE from one cell to another. In an IAB system, the impact can be greater as a handover of an IAB node MT can cause a topology change. Thus, the IAB node can need to consider other criteria such as load balancing in addition to mobility related measurements to make a decision that a handover is to be performed. In such a system, consistent transmission of reference signals for mobility can be important. Thus, control signaling can be provided to the IAB node to inform its parent node (PN) of its limitations on downlink communications and / or downstream communications such as for mobility related reference signals.

[0218] In certain embodiments, the PH can be the difference between the nominal UE maximum transmit power and the estimated power for the transmission. The estimated power for the transmission can not be the actual power and / or used power for the transmission, but rather the transmit power that would be used without an upper limit on the transmit power. Thus, the PH level can be positive or negative. A negative PH level can indicate the amount that the transmit power of the transmission is limited by the nominal UE maximum transmit power. For a PUSCH transmission, a negative PH level can indicate that the network has scheduled a higher data rate than the UE is able to support given the available transmission power. The network can then adjust the uplink data rate accordingly so that the UE is no longer power limited. The power headroom can be calculated by subtracting the power required to transmit a signal on the PUSCH from the UE’s maximum total transmit power. The UE can report the power headroom periodically through MAC signaling according to a configuration from the serving cell.

[0219] For example, if the UE transmits PUSCH in PUSCH transmission occasion i on UL BWP b of UL carrier f of serving cell c, the UE calculates the actual power headroom in [dB] for Type-1 reporting. Thus, if the UE determines that the Type-1 power headroom reporting for the activated serving cell is based on actual PUSCH transmission, for PUSCH transmission occasion i on UL BWP b of carrier f of serving cell c with open loop parameter set configuration with index j and path loss reference with index q d and PUSCH power control adjustment state with index l, the UE calculates the Type-1 PHR (also known as PUSCH PHR) as:

[0220] where the power headroom of Equation 1 is in [dB] and all parameters are defined in 3GPP TS 38.213. In particular, the configured maximum UE output power P CMAX,f,cIf the UE does not transmit PUSCH in PUSCH transmission occasion i on UL BWP b of UL carrier f of serving cell c, the UE cannot report the actual power headroom. This is due to the fact that if there is no PUCCH transmission and / or PUSCH transmission in transmission occasion i, the P CMAX，f，c (i) The UE instead reports a “virtual” power headroom based on a reference PUSCH transmission. Thus, if the UE determines the Type-1 PHR for an activated serving cell is based on a reference PUSCH transmission, the UE calculates the Type-1 power headroom in [dB] for PUSCH transmission occasion i on active UL BWP b of carrier f of serving cell c as:

[0221] where is calculated with the assumption that MPR = 0 dB, A-MPR = 0 dB, P-MPR = 0 dB, AT C = 0 dB, where MPR (“Maximum Power Reduction”), A-MPR (“Additional Maximum Power Reduction”), P-MPR (“Power Management Maximum Power Reduction”), and AT C are power reduction and / or back-off terms. These power reduction and / or back-off terms are all defined in 3GPP TS 38.101.

[0222] In some embodiments, the UE can determine the Type-3 power headroom report for an activated serving cell based on an actual SRS transmission or a virtual Type-3 PHR based on a reference SRS transmission as described in TS 38.213.

[0223] In certain embodiments, an IAB node MT considers the maximum transmit power not only based on node capabilities or standard specifications but also based on the power required for downlink communications and / or downstream communications. The PHR from the IAB node can be associated with a power control resource set, which essentially 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 signals and / or downstream signals with more stringent power requirements.

[0224] In some embodiments, if a transmit power control TXP2 is allocated to a reference signal or other downlink communication D, the IAB node can consider TXP2 x Q and any total transmit power constraints to produce a power headroom report. If D overlaps in time with a resource set T in the PCRS configuration, the PHR can be associated with T so that the parent node (PN) applies the power headroom information to the communications it will schedule on T.

[0225] In one embodiment, P can be determined or configured for the IAB node MT power control resource set CMAX,f,c In another embodiment, the IAB node MT can determine P separately or in addition based on a transmit power control TXP2 allocated to a reference signal or other downlink communication D CMAX,f,c In certain embodiments, the maximum power reduction needed to multiplex downlink communications and / or downstream communications from the IAB node (e.g., and uplink communications 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., IAB-P-MPR for MPR used to calculate P CMAX,f,c The IAB node MT can indicate P CMAX,f,c and / or IAB-P-MPR in the PHR to the PN. The PHR (e.g., actual or virtual) can be associated with a power control resource set (e.g., PUSCH, PUCCH, and / or SRS transmissions 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.

[0226] In various embodiments, the base station can be the central controller of the cell and the UEs can follow their instructions for scheduling, power control, timing alignment, etc. The UEs can be expected to 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 IAB systems, the IAB nodes can be responsible for controlling their own cells and can be provided with means to cancel communications despite instructions from the serving cell.

[0227] In certain embodiments, upon determining that the transmit power for uplink communications exceeds a threshold, the IAB node can cancel the uplink transmission. The IAB node can 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 can further inform the serving cell (e.g., through a PHR including a negative value) that the uplink communications and / or upstream communications were canceled due to power control reasons.

[0228] In some embodiments, downlink communications can be canceled by the IAB node upon determining that the uplink communications require higher transmit power than previously expected. The IAB node can further inform the downstream nodes (e.g., CN and / or UEs) of the cancellation or can handle the error through HARQ transmissions.

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

[0230] In certain embodiments, if the higher priority signal is an uplink signal and / or upstream signal, then the downlink signal and / or downstream signal is cancelled, and if the higher priority signal is a downlink signal and / or downstream signal, then the uplink signal and / or upstream signal can be cancelled.

[0231] In some embodiments, there can be two types of resource set configurations: 1) PORS for resource sets - mainly for downlink resource sets - make an association between power offset (e.g., from a reference signal such as SS / PBCH block) or reception target power settings; and 2) PCRS for resource sets - mainly for uplink resource sets - make an association between power control parameters.

[0232] In various embodiments, the configuration can be made by a separate RRC IE, can be included in other configurations, or can be made by control signaling.

[0233] In certain embodiments, IAB systems can be expected to utilize flexible resource configurations that enable IAB nodes to share resources in both upstream and downstream directions. Resources can be configured to be flexible (F) on a symbol level, and then resources can be indicated as DL or UL for each instance. In addition, resources can be configured to be hard, soft, or unavailable on a symbol level for an IAB node. If a resource is configured to be hard (H), it is always available, if it is configured to be soft (S), it needs to be indicated as available for each instance, and if it is configured to be unavailable (NA), the IAB node cannot use the resource for scheduling communications. The combination of {DL, UL, F, H, S, NA} and availability indication (by DCI) of soft resources can provide a high level of flexibility for scheduling in IAB systems.

[0234] In some embodiments, since both upstream and downstream resources can be shared, an IAB node can receive a combination of PORS configuration and PCRS configuration, i.e., associate both 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 indication (e.g., by DCI) in order to determine what power control parameters apply to what time resources (e.g., slots, symbols, etc.).

[0235] Further, in various embodiments, an IAB node can not indicate in signaling to a PN or CN and / or UE which time resources in a set of resources are associated with the signaling. Instead, the relevant time resources can be inferred by knowledge of the IAB node’s resource configuration and availability indication. This can be feasible because an IAB node can inform other nodes of its resource configuration. For example, if a slot in a PORS configuration and / or PCRS configuration includes DL symbols and UL symbols, the IAB node can inform its parent node of the slot configuration. A PHR transmitted from the IAB node to its parent node can then involve the entire slot without explicitly indicating which symbols in the slot are configured as UL. However, since the parent node is aware of the configuration, it can infer the information and consider the PHR report only for the UL symbols in the slot.

[0236] In certain embodiments, power control configurations, such as PORS configuration and PCRS configuration, can be provided by a CU of an IAB donor. In such embodiments, IAB nodes in an IAB system served by the IAB donor can be able to communicate the power control configurations to improve coordination, control interference, etc. Thus, the signaling can be provided by a higher layer (e.g., over a Fl interface) and can be periodic, semi-persistent, aperiodic, or based on a request-response protocol.

[0237] In some embodiments, there can be details regarding how various methods can be applied to address power control issues in different scenarios.

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

[0239] Further, the simultaneous transmission and reception in scenario S2 can depend on the capabilities of the node, which can be reported to other nodes in the system either proactively or upon request. The capabilities can include constraints based on the transmission power and reception power in the following cases: 1) resource overlap (e.g., same time-frequency resources are used for transmission and reception); and / or 2) resource non-overlap (e.g., transmission and reception are FDMed).

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

[0241] It can be noted that the information of the downlink transmission power obtained by receiving the PORS configuration on the set of resources T can enable the N to generate and transmit its own PORS configuration on the set of resources T, which can be transmitted to child IAB nodes or UEs served by the N. In various embodiments, some or all of the PORS configuration can be generated at the CU and delivered to the IAB node by higher layers.

[0242] In certain embodiments, the DL-PC request-grant method can be extended to address scenario S2. For this purpose, the N can need to evaluate the range of transmission power suitable for downlink transmission to the CN and / or the UE and send a request to the PN to make adjustments to the downlink transmission power to the N on resources overlapping in either or both of time and frequency with the downlink communication to the CN and / or the UE.

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

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

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

[0246] In certain embodiments, in scenario S3, N can transmit signals to PN and CN and / or UE simultaneously through a single antenna panel. In particular, N transmits signals to PN on PUSCH and to CN and / or UE on PDSCH, where PUSCH and PDSCH are fully or partially FDMed. Methods for other channels can be similar.

[0247] In various embodiments of scenario S3, power control parameters can be informed to N in advance through configuration, which can be referred to as PCRS configuration. PCRS configuration can include the following parameters: 1) ID for configuration; 2) resource set: a) resources in time: (e.g., slot, symbol, periodicity of occurrence, etc.), b) resources in frequency: (e.g., PRB, BWP, CC, etc.); 3) power control parameters (e.g., P0 and a); and / or 4) beam-based information (e.g., spatial QCL with respect to reference signal).

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

[0249] It should be noted that the information of uplink transmission obtained by receiving PCRS configuration on resource set T can enable N to generate and transmit PORS configuration on resource set T, which can be sent to child IAB nodes or UEs served by N. In certain embodiments, some or all of PCRS and PORS configurations can be generated at CU and delivered to IAB nodes by higher layer.

[0250] In various embodiments, the DL-PC request-grant method can be extended to address scenario S3. To this end, N can need to evaluate the range of transmission power suitable for downlink transmission to the CN and / or UE and send a request to PN to make adjustments to the uplink transmission power from N on resources that overlap in either or both of time and frequency with downlink communication to the CN and / or UE.

[0251] In some embodiments, to achieve FDM between PUSCH transmission and PDSCH transmission, PN can transmit a first DCI (e.g., DCI1) that schedules a PUSCH transmission sufficiently in advance. Once N receives and decodes DCI1, it can consider the following to evaluate whether it can schedule a PDSCH transmission on overlapping time resources as follows: the resources scheduled for the PUSCH transmission and / or the power required for transmission of the PUSCH signal.

[0252] In certain embodiments, if N recognizes that there are sufficient resources and power remaining to schedule a simultaneous channel, N can generate and transmit a second DCI (e.g., DCI2) that schedules a PDSCH transmission to be transmitted to the CN and / or UE.

[0253] In various embodiments, the time gap between DCI1 and the scheduled PUSCH transmission can be controlled by the higher layer parameter k2 in RRC IE PUSCH-TimeDomainResourceAllocation. The higher layer parameter 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).

[0254] 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 N needs to decode DCI1 from PN, and k0_min(N) is the minimum value of k0 for PDSCH transmission transmitted from N to the CN and / or UE. The higher layer parameter k0 can be determined by RRC IE PDSCH-TimeDomainResourceAllocation.

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

[0256] In another example, there can be a 3-hop system PN - N - CN - UE. In this example, {PN, N, CN} can schedule {PUSCH, PDSCH, PUSCH} for {N, CN, UE}, respectively.

[0257] Then, the minimum for k0 can take the following recursive form:

[0258] k2_min(PN) : = T_min(N) + k0_min(N)

[0259] k0_min(N) : = T_min(CN) + k2_min(CN)

[0260] Since CN can schedule PDSCH for the UE with k2 = 0, k2_min(CN) : = 0 can be set.

[0261] Thus:

[0262] k0_min(N) : = T_min(CN)

[0263] k2_min(PN) : = T_min(N) + T_min(CN)

[0264] Assuming T_min(N) : = T_min(CN) : = T_min, we obtain:

[0265] k2_min(CN) : = 0

[0266] k0_min(N) : = T_min

[0267] k2_min(PN) : = 2 x T_min

[0268] This recursive rule can be extended to larger hop numbers. For example, in an m-hop IAB system Nm -... - N1 - N0 - UE, assuming all values of minimum DCI decoding time are the same, we have:

[0269] k_min(N0) : = 0

[0270] k_min(N1) : = T_min

[0271] …

[0272] k_min(Nm): = m x T_min

[0273] In the above equations, k_min is either k0_min or k2_min as the case can be.

[0274] It should be noted that since the IAB node can not be aware of the hop count at the RRC layer, the minimum threshold for k0 or k2 can be made configurable by higher layers.

[0275] Assume the IAB node receives the following higher layer parameters in one or more configurations: 1) T: set of resources T (e.g., 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). The 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.

[0276] In certain embodiments, consider the IAB node as the receiver of the DCI scheduling the PUSCH transmission. If the IAB node intends to schedule a PDSCH transmission simultaneously with the 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 the PDSCH transmission with k0 > k0_min? a) if yes, schedule the simultaneous PDSCH transmission if resource and power considerations allow, b) if no, do not schedule the simultaneous PDSCH transmission.

[0277] In various embodiments, consider the IAB node as the receiver of the DCI scheduling the PDSCH transmission. If the IAB node intends to schedule a PUSCH transmission simultaneously 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 the PDSCH transmission with k2 > k2_min? a) if yes, schedule the simultaneous PUSCH transmission if resource and power considerations allow, b) if no, do not schedule the simultaneous PUSCH transmission. As can be appreciated, the elements described with respect to scenario S3 can apply to the other scenarios.

[0278] In some embodiments, N can follow the power control by PN as long as it does not cause collision with power limited downlink signals. N can consider the power constraints introduced by the downlink signals to transmit PHR. PHR can be associated with slots and / or symbols containing power limited downlink signals.

[0279] In certain embodiments, a PN can have a capability consisting of power-limited resources for N. The PN then does not schedule communications with N on those resources that would require N to violate the power constraint, or the PN does not expect N to follow the regular power control procedure for any communications on the power-limited time slots and / or symbols.

[0280] In various embodiments, the duplexing and / or multiplexing capabilities of an IAB node and the tolerance of the node pair power imbalance can be used in decision making. The IAB node’s decision can impact generating and transmitting closed-loop TPC commands, maintaining and updating power control configurations (e.g., PORS, PCRS, etc.), and the like.

[0281] In some embodiments, the configuration rules can set the minimum values of k0 and / or k2, which can be defined by a standard specification or can depend on implementation.

[0282] In certain embodiments, the collective capabilities of the system to efficiently schedule communications can impact the system’s behavior at higher layers for processes such as admission control to guarantee required QoS.

[0283] In various embodiments, in scenario S4, a single-panel IAB node (N) can transmit an uplink signal to a parent node (PN) and can simultaneously receive an uplink signal from a child node (CN) or a 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 capabilities of the nodes.

[0284] In scenario S4, the systems and methods can include one or more of the following: 1) the N reports capabilities to the PN or to the CU of an IAB donor; 2) the N receives a PCRS configuration including a set of resource sets and power control parameters associated with the set of resource sets; 3) the N receives a TPC command; 4) the N calculates a target transmit power based on the PCRS configuration and the TPC command for an upcoming uplink transmission; and / or 5) if possible, based on channel conditions and capabilities of the node, the N sets power control parameters for uplink communications from child nodes and / or UEs on resources that overlap with the set of resource sets in the PCRS configuration in either or both of the time and frequency domains.

[0285] It should be noted that the information of the uplink transmit power obtained by receiving the PCRS configuration on the set of resources T can enable the N to generate and transmit its own PCRS configuration on the set of resources T, which can be sent to child IAB nodes or UEs served by the N. In some embodiments, some or all of the PCRS configurations can be generated at the CU and communicated to the IAB nodes by a higher layer.

[0286] In various embodiments, the DL-PC request-grant method can be extended to address scenario S4. For this purpose, N can need to evaluate the range of transmission power suitable for uplink transmissions from the CN and / or the UE and send a request to the PN to make adjustments to the uplink transmission power from N on resources that overlap in either or both of time and frequency with uplink communications from the CN and / or the UE.

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

[0288] As used herein, although frequent reference is made to IAB, embodiments described herein can be applicable to wireless relay nodes and other types of wireless communication entities.

[0289] Further, as used herein, although entities are referred to as IAB nodes, the same methods can be applied to IAB donors, which are IAB entities that connect a core network to an IAB network with minor or no modifications.

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

[0291] In certain embodiments, configurations can be provided through RRC signaling, MAC signaling, physical layer signaling such as DCI messages, combinations thereof, and / or other means. Configurations can include pre-configuration or semi-static configuration provided by standards, by vendors, and / or by networks and / or operators. Each parameter value received through configuration or indication can override a previous value of a similar parameter.

[0292] Further, configurations and signaling described in embodiments described herein can be introduced to standard specifications through defining new IEs, new MACs, new L1 signaling, or can be included in already existing IEs and / or signaling. For example, parameters of PORS or PCRS can be included in other system configurations such as slot configurations.

[0293] Power and energy values in the embodiments described herein or in standard specifications can be described in real dimensions (e.g., in mW) or in logarithmic dimensions (e.g., dBm). The following are examples of the relationship between values in real dimensions and in logarithmic dimensions:

[0294] For power, energy, etc.:

[0295] P [dB] = P [dBW] = 10 log 10 (P [W])

[0296] P [dBm] = 10 log 10 (P [mW])

[0297] For power offsets, power ratios, etc.:

[0298] R [dB] = 10 log 10 (R)

[0299] It should be noted that a ratio in real dimensions can be equivalent to a difference in logarithmic dimensions. Thus, the words “ratio” and “difference” can be used interchangeably and can be understood from context.

[0300] As used herein, “HARQ-ACK” can collectively represent acknowledgement (“ACK”) and negative acknowledgement (“NACK”). ACK can mean that a TB was received correctly, whereas NACK (or NAK) can mean that a TB was received incorrectly.

[0301] Figure 16 is a flowchart illustrating one embodiment of a method 1600 for power control using at least one power control parameter. In some embodiments, the method 1600 is performed by an apparatus such as the remote unit 102 and / or the network unit 104. In certain embodiments, the method 1600 can be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

[0302] In various embodiments, the method 1600 includes receiving 1602, at a first device, configuration information including a power offset value associated with a first plurality of resources and a first reference signal. In some embodiments, the method 1600 includes receiving 1604 the first reference signal from a second device. In certain embodiments, the method 1600 includes performing 1606 a first measurement on the first reference signal. In various embodiments, the method 1600 includes calculating 1608 a first expected received power value based on the first measurement and the power offset value. In some embodiments, the method 1600 includes calculating 1610 a first target received power value. In certain embodiments, 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.

[0303] In certain embodiments, the first target received power value is calculated based on a second expected received power value associated with the first plurality of resources and a power imbalance threshold. In some embodiments, the power imbalance threshold is predefined, semi-statically configured, dynamically signaled, 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.

[0304] 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 certain embodiments, the method 1600 further includes receiving an accepted power change value from the second device and transmitting scheduling information for an uplink channel associated with the first plurality of resources to a third device based on the accepted power change value, the second expected received power value, and the power imbalance threshold. In some embodiments, calculating the first target received power value includes selecting the first target received power value such that a ratio between the first target received power and the second expected received power is less than the power imbalance threshold.

[0305] 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, the method 1600 further includes receiving an indication of whether the at least one downlink power control parameter is accepted from the second device and transmitting scheduling information for an uplink channel associated with the first plurality of resources to the third device based on whether the indication is affirmative. In certain embodiments, the 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 in a time domain with the first plurality of resources, or a combination thereof.

[0306] Figure 17is a flowchart illustrating another embodiment of a method 1700 for power control using at least one power control parameter. In some embodiments, the method 1700 is performed by an apparatus such as the remote unit 102 and / or the network unit 104. In certain embodiments, the method 1700 can be performed by a processor executing program code, for example a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

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

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

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

[0310] 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, the method 1700 further includes receiving, from the second device, an indication of whether at least one downlink power control parameter is accepted; and transmitting, to the third device, scheduling information for an uplink channel associated with the first plurality of resources based on whether the indication is affirmative. In certain embodiments, the 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 in a time domain with the first plurality of resources; or a combination thereof.

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

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

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

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

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

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

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

[0318] 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.

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

[0320] In certain embodiments, the associating 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 in a time domain with the first plurality of resources; or a combination thereof.

[0321] In one embodiment, an apparatus includes a first device. The apparatus further includes a receiver that receives configuration information including a power offset value 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 receive power value based on the first measurement and the power offset value; and calculates a first target receive power value; and a transmitter that transmits, to the second device, at least one downlink power control parameter based on the first target receive power value and the first expected receive power value.

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

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

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

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

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

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

[0328] 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.

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

[0330] In certain embodiments, the associating with the first plurality of resources comprises being located on a subset of the first plurality of resources; being located on a second plurality of resources that overlap in a time domain with the first plurality of resources; or a combination thereof.

[0331] In one embodiment, a method comprises receiving, at a first device from a second device, a first reference signal; 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, to the second device, at least one downlink power control parameter based on the first target received power value and the first expected received power value.

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

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

[0334] 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.

[0335] 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.

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

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

[0338] 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.

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

[0340] In certain embodiments, the associating 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 in a time domain with the first plurality of resources; or a combination thereof.

[0341] 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 receive power value associated with a first plurality of resources based on the first measurement; calculates a first target receive power value; and a transmitter that transmits, to the second device, at least one downlink power control parameter based on the first target receive power value and the first expected receive power value.

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

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

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

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

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

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

[0348] 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.

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

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

[0351] Embodiments can be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. Also, any embodiment described herein can be combined with any other embodiment described herein. Therefore, the scope of the application is not indicated by the description of the embodiments but instead by the appended claims. All changes coming within the meaning and equivalency range of the claims are intended to be embraced therein.

Claims

1. A method for power control using at least one power control parameter, comprising: receiving, at a first device, configuration information comprising a power offset value associated with a first plurality of resources and a first reference signal; receiving, from a second device, the first reference signal; 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 value; calculating a first target received power value based on a second expected received power value associated with the first plurality of resources and a power imbalance threshold value; and transmitting, to the second device, at least one downlink power control parameter based on the first target received power value and the first expected received power value.

2. The method of claim 1, further comprising: receiving, from the second device, an accepted power change value; and transmitting, to a third device, scheduling information for an uplink channel associated with the first plurality of resources based on the accepted power change value, the second expected received power value, and the power imbalance threshold value. calculating the first target received power value comprises selecting the first target received power value such that a ratio between the first target received power and the second expected received power is less than the power imbalance threshold value.

3. The method of claim 1, wherein, the second device provides a first serving cell for the first device and the second device provides a second serving cell for a third device.

4. The method of claim 1, wherein, 5. The method of claim 1, further comprising: receiving, from the second device, an indication of whether the at least one downlink power control parameter is accepted; and transmitting, to a third device, scheduling information for an uplink channel associated with the first plurality of resources based on whether the indication is affirmative. associated with the first plurality of resources comprises: being located on a subset of the first plurality of resources; 6. The method of claim 1, wherein, being located on a second plurality of resources that overlap with the first plurality of resources in a time domain; or a combination thereof.

7. An apparatus for power control using at least one power control parameter, comprising a first device, the apparatus further comprising: a receiver that: receives configuration information comprising a power offset value associated with a first plurality of resources and a first reference signal; and receives, from a second device, the first reference signal; 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 value; and calculates a first target received power value based on a second expected received power value associated with the first plurality of resources and a power imbalance threshold value; and a transmitter that transmits, to the second device, at least one downlink power control parameter based on the first target received power value and the first expected received power value.

8. The apparatus of claim 7, wherein: the receiver receives, from the second device, an accepted power change value; and the transmitter transmits, to a third device, scheduling information for an uplink channel associated with the first plurality of resources based on the accepted power change value, the second expected received power value, and the power imbalance threshold value. ​ ​ ​ 9. The apparatus of claim 7, wherein, The processor computing the first target received power value includes the processor selecting the first target received power value such that a ratio between the first target received power and the second expected received power is less than the power imbalance threshold.

10. The apparatus of claim 7, wherein: receiving, from the second device, an indication of whether the at least one downlink power control parameter is accepted; and transmitting, to a third device, scheduling information for an uplink channel associated with the first plurality of resources based on whether the indication is affirmative.

11. The apparatus of claim 7, wherein, 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 in a time domain with the first plurality of resources; or a combination thereof.

12. A method for power control using at least one power control parameter, comprising: receiving, at a first device, a first reference signal from a second device; performing a first measurement on the first reference signal; computing a first expected received power value associated with a first plurality of resources based on the first measurement; computing a first target received power value based on a second expected received power value associated with the first plurality of resources and a power imbalance threshold; and transmitting, to the second device, at least one downlink power control parameter based on the first target received power value and the first expected received power value.

13. The method of claim 12, further comprising: receiving, from the second device, a permitted power change value; and transmitting, to a third device, scheduling information for an uplink channel associated with the first plurality of resources based on the permitted power change value, the second expected received power value, and the power imbalance threshold.

14. The method of claim 12, wherein, Computing the first target received power value includes selecting the first target received power value such that a ratio between the first target received power and the second expected received power is less than the power imbalance threshold.

15. The method of claim 12, wherein, The second device provides a first serving cell for the first device and the second device provides a second serving cell for a third device.

16. The method of claim 12, further comprising: receiving, from the second device, an indication of whether the at least one downlink power control parameter is accepted; and transmitting, to a third device, scheduling information for an uplink channel associated with the first plurality of resources based on whether the indication is affirmative.

17. The method of claim 12, wherein, 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 in a time domain with the first plurality of resources; or a combination thereof.

Images