UE power control for multiple uplink carriers

The methods for UE power control in 5G NR optimize power management across multiple uplink carriers by configuring and managing power control parameters, addressing inefficiencies in BWP and SUL operations to ensure compliance with maximum output power limits, thereby enhancing network performance.

CN111955033BActive Publication Date: 2024-12-10LENOVO (SINGAPORE) PTE LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN201980024742.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2018-04-05
Filing Date
2019-04-05
Publication Date
2024-12-10
Estimated Expiration
2039-04-05

AI Technical Summary

Technical Problem

Conventional power control and power headroom reporting in wireless communication networks, such as 5G NR, are suboptimal and incompatible with bandwidth part (BWP) and supplementary uplink (SUL) operations, leading to inefficiencies in UE power management.

Method used

Methods for UE power control of multiple uplink carriers involve configuring and managing power control parameters, prioritizing uplink carriers, and performing power adjustments to ensure compliance with maximum output power limits, including closed-loop power control and power headroom reporting across multiple BWPs and SULs.

Benefits of technology

Enhances power management efficiency by optimizing power allocation and reporting across multiple uplink carriers, ensuring compliance with maximum output power limits and improving network performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN111955033B_ABST
    Figure CN111955033B_ABST
Patent Text Reader

Abstract

An apparatus, method, and system for UE power control of multiple uplink carriers are disclosed. An apparatus 700 includes a transceiver 725 that receives 805 a configuration of multiple uplink carriers for a serving cell. The apparatus includes a processor 705 that calculates 810 a total transmit power for uplink transmissions on multiple uplink carriers that overlap in time. The processor 705 determines 815 a configured maximum output power and identifies 820 a lower priority uplink carrier of the multiple uplink carriers according to a priority rule in response to the uplink transmissions having the same priority level. In response to the total transmit power exceeding the configured maximum output power in any portion of the overlapping uplink transmissions, the processor 705 reduces 825 the transmit power for the lower priority uplink carrier. The transceiver 725 performs 830 uplink transmissions using the reduced transmit power.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Patent Application No. 62 / 653,482, entitled “Power Control with Bandwidth part and Supplementary Uplink Operation,” filed on April 5, 2018, to Ebrahim Molavian Jazi, Joachim Loehr, Hyejung Jung, Vijay Nangia, and Prateek Basu Mallick, which is incorporated herein by reference. Technical Field

[0003] The subject matter disclosed herein relates generally to wireless communications and, more particularly, to power control for a UE, especially when configured with multiple bandwidth parts and / or supplemental uplink carriers. Background Art

[0004] The following abbreviations are defined herein, and at least some of them are referenced in the following description: 3rd Generation Partnership Project (“3GPP”), positive acknowledgement (“ACK”), bandwidth part (“BWP”), binary phase shift keying (“BPSK”), clear channel assessment (“CCA”), cyclic prefix (“CP”), cyclic redundancy check (“CRC”), channel state information (“CSI”), common search space (“CSS”), discrete Fourier transform spreading (“DFTS”), downlink control information (“DCI”), downlink (“DL”), downlink pilot time slot (“DwPTS”), enhanced clear channel assessment (“eCCA”), enhanced license assisted access (“eLAA”), enhanced mobile broadband (“eMBB”), evolved Node B (“eNB”), European Telecommunications Standards Institute (“ETSI”), ”), frame-based equipment (“FBE”), frequency division duplex (“FDD”), frequency division multiple access (“FDMA”), frequency division orthogonal cover code (“FD-OCC”), guard period (“GP”), hybrid automatic repeat request (“HARQ”), Internet of Things (“IoT”), license assisted access (“LAA”), load-based equipment (“LBE”), listen before talk (“LBT”), long term evolution (“LTE”), multiple access (“MA”), modulation coding scheme (“MCS”), machine type communication (“MTC”), multiple input multiple output (“MIMO”), multi-user shared access (“MUSA”), narrowband (“NB”), negative acknowledgement (“NACK”) or (“NAK”), next generation Node B (“gNB”), non-orthogonal multiple access (“NOMA”), non-supplementary uplink (“NUL”, e.g.,"Normal" uplink carrier), Orthogonal Frequency Division Multiplexing ("OFDM"), Primary Cell ("PCell"), Primary Secondary Cell ("PSCell"), Physical Broadcast Channel ("PBCH"), Physical Downlink Control Channel ("PDCCH"), Physical Downlink Shared Channel ("PDSCH"), Code Division Multiple Access ("PDMA"), Physical Hybrid ARQ Indicator Channel ("PHICH"), Physical Random Access Channel ("PRACH"), Physical Resource Block ("PRB"), Physical Uplink Control Channel ("PUCCH"), Physical Uplink Shared Channel ("PUSCH"), Quality of Service ("QoS"), Quadrature Phase Shift Keying ("QPSK"), Radio Resource Control ("RRC"), Random Access Procedure ("RACH"), Random Access Response ("RAR"), Radio Network Temporary Identifier ("RNTI"), Reference Signal ("RS"), Remaining Minimum System Information ("RMSI"), Resource Extended Multiple Access ("RSMA") ), round trip time (“RTT”), reception (“RX”), sparse code multiple access (SCMA), scheduling request (SR), single carrier frequency division multiple access (SC-FDMA), secondary cell (SCell), shared channel (SCH), signal-to-noise and interference ratio (“SINR”), supplementary uplink (“SUL”), system information block (“SIB”), synchronization signal (“SS”), transport block (“TB”), transport block size (“TBS”), time division duplex (“TDD”), time division multiplexing (“TDM”), time division orthogonal cover code (“TD-OCC”), transmission time interval (“TTI”), transmission (“TX”), uplink control information (“UCI”), user entity / equipment (mobile terminal) (“UE”), uplink (“UL”), universal mobile telecommunications system (“UMTS”), uplink pilot time slot (“UpPTS”), ultra-reliable and low-latency communications (“URLLC”), and world-wide interoperability for microwave access (“WiMAX”). As used herein, "HARQ-ACK" may collectively represent a positive acknowledgement ("ACK") and a negative acknowledgement ("NACK"). ACK means that the TB has been correctly received, while NACK (or NAK) means that the TB has been received in error.

[0005] In certain wireless communication networks, such as 5GNR, it is expected that a UE is configured with one or more downlink bandwidth parts ("DLBWP"). Additionally, in 5GNR, an additional frequency band may be supplemented to the NR serving cell, referred to as a supplementary uplink ("SUL"). However, conventional power control ("PC") and power headroom reporting ("PHR") are suboptimal and / or incompatible with BWP and SUL operations. Summary of the invention

[0006] Methods for UE power control of multiple UL carriers are disclosed. Apparatus and systems also perform the functions of these methods. These methods may also be embodied in one or more computer program products including executable code.

[0007] A first method for UE power control for multiple UL carriers includes: receiving a configuration of multiple uplink carriers for a serving cell; and calculating a total transmit power for uplink transmissions on the multiple uplink carriers, the uplink transmissions overlapping in time. The first method includes: determining a configured maximum output power; and in response to the uplink transmissions having the same priority level, identifying a lower priority uplink carrier among the multiple uplink carriers according to a priority rule. The first method includes: in response to the total transmit power exceeding the configured maximum output power in any portion of the overlapping uplink transmissions, reducing the transmit power for the lower priority uplink carrier; and performing the uplink transmission using the reduced transmit power.

[0008] A second method for UE power control of multiple UL carriers includes: receiving a configuration of multiple uplink carriers for a serving cell; and calculating a PH for each of the multiple uplink carriers on the serving cell. The second method includes: sending a PHR based on the calculated PH for the multiple uplink carriers of the serving cell.

[0009] A third method for UE power control for multiple UL carriers includes: performing a random access procedure, wherein performing the random access procedure includes sending PUSCH Msg3. The third method includes: determining whether the UE is in an RRC_CONNECTED state; and identifying the number of configured CL-PC processes for UL channels or signals. The third method includes: in response to the UE being in an RRC_CONNECTED state and the number of configured CL-PC processes for UL channels or signals exceeding one, using a CL-PC process with an index of zero to calculate the transmit power for PUSCH Msg3. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] A more particular description of the embodiments briefly described above will be presented by reference to specific embodiments illustrated in the accompanying drawings. Understanding that these drawings depict only some embodiments and are therefore not to be considered limiting of 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 UE power control for multiple UL carriers;

[0012] Figure 2is a block diagram illustrating one embodiment of power control for a UE configured with multiple uplink bandwidth portions;

[0013] Figure 3 is a block diagram illustrating one embodiment of a power control process management when switching active uplink bandwidth portions;

[0014] Figure 4 is a block diagram illustrating another embodiment of power control for a UE configured with multiple uplink carriers;

[0015] Figure 5 is a block diagram illustrating one embodiment of power headroom reporting for a UE configured with multiple uplink bandwidth parts;

[0016] Figure 6 is a block diagram illustrating one embodiment of power headroom reporting for a UE configured with multiple uplink carriers;

[0017] Figure 7 is a block diagram illustrating a user equipment apparatus for power control of a BWP when multiple bandwidth parts and / or supplemental uplink carriers are configured;

[0018] Figure 8 is a flow chart illustrating a method of UE power control for multiple UL carriers;

[0019] Fig. 9 is a flow chart illustrating another method of UE power control for multiple UL carriers; and

[0020] Fig.10 is a flow chart illustrating yet another method of UE power control for multiple UL carriers. DETAILED DESCRIPTION

[0021] As will be appreciated by those skilled in the art, aspects of the embodiments may be embodied as systems, devices, methods or program products. Therefore, the embodiments may take the form of a complete hardware embodiment, a complete software embodiment (including firmware, resident software, microcode, etc.), or a combination of software and hardware aspects, which may generally be referred to herein as "circuit", "module" or "system". In addition, the embodiments may take the form of a program product embodied in one or more computer-readable storage devices stored in machine-readable code, computer-readable code and / or program code, hereinafter referred to as code. The storage device may be tangible, non-temporary and / or non-transmitting. The storage device may not embody a signal. In a certain embodiment, the storage device only employs a signal for accessing the code.

[0022] Any combination of one or more computer readable media may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing code. The storage device may 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.

[0023] More specific examples of storage devices (a non-exhaustive list) 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 may 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.

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

[0025] References to "one embodiment", "embodiment" or similar language in this specification are intended to mean that a particular feature, structure or characteristic described in conjunction with the embodiment is included in at least one embodiment. Therefore, unless otherwise expressly stated, the phrases "in one embodiment", "in an embodiment" and similar language appearing throughout the specification may, but not necessarily all refer to the same embodiment, but rather mean "one or more but not all embodiments". Unless otherwise expressly stated, the terms "include", "comprising", "having" and their variations mean "including but not limited to". Unless otherwise expressly stated, the list of items listed does not imply that any or all items are mutually exclusive. Unless otherwise expressly stated, the terms "a", "an" and "the" also refer to "one or more".

[0026] In addition, the features, structures or characteristics of the described embodiments may be combined in any suitable manner. In the following description, many 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. However, those skilled in the relevant art will recognize that the embodiments may be practiced without one or more of the specific details, or using other methods, components, materials, etc. In other cases, well-known structures, materials or operations are not shown or described in detail to avoid obscuring some aspects of the embodiments.

[0027] Various aspects of the embodiments are described below with reference to schematic flow charts and / or schematic block diagrams of the methods, devices, systems, and program products according to the embodiments. It will be understood that each block of the schematic flow charts and / or schematic block diagrams and the combination of blocks in the schematic flow charts and / or schematic block diagrams can be implemented by code. The code can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, so that instructions executed by the processor of the computer or other programmable data processing device create a means for implementing the functions / operations specified in the schematic flow charts and / or schematic block diagram blocks or some blocks.

[0028] The code may also be stored in a storage device that is capable of instructing a computer, other programmable data processing apparatus, or other device to operate in a specific manner so that the instructions stored in the storage device produce an article of manufacture including instructions that implement the functions / operations specified in a block or some blocks of the schematic flowchart and / or schematic block diagram.

[0029] The code may also be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operational steps are performed on the computer, other programmable apparatus, or other device to produce a computer-implemented process, so that the code executed on the computer or other programmable apparatus provides a process for implementing the functions / operations specified in a block or blocks of the flowchart and / or block diagram.

[0030] The schematic flow charts and / or schematic block diagrams in the accompanying drawings illustrate possible implementations of the apparatus, system, method, and program product according to various embodiments, architecture, functions, and operations. In this regard, each block in the schematic flow charts and / or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing a specified logical function.

[0031] It should also be noted that in some alternative implementations, the functions annotated in the blocks may not occur in the order annotated in the drawings. For example, two blocks shown in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order, depending on the functions involved. Other steps and methods are contemplated that are equivalent in function, logic, or effect to one or more blocks or portions thereof of the illustrated drawings.

[0032] Although various arrow types and line types can be used in flow charts and / or block diagrams, it should be understood that they do not limit the scope of the corresponding embodiments. In fact, some arrows or other connectors can only be used to indicate the logical flow of the depicted embodiment. For example, an arrow can indicate a waiting or monitoring period of unspecified duration between the enumeration steps of the depicted embodiment. It will also be noted that each block of the block diagram and / or flow chart and the combination of the blocks in the block diagram and / or flow chart can be realized by a system based on dedicated hardware that performs a specific function or operation, or a combination of dedicated hardware and code.

[0033] The description of an element in each figure may refer to an element of the previous figure. The same numerals refer to the same elements in all figures, including alternative embodiments of the same elements.

[0034] In general, the present disclosure describes systems, methods, and apparatus for PC and PHR-related configuration and operating methods for BWP and SUL operations, including: configuration of power control parameters for BWP operation; resetting closed-loop power control when switching active BWP; priority rules for power allocation across uplink carriers (including supplementary uplink ("SUL") carriers and normal (non-supplementary) uplink ("NUL") carriers) and uplink BWPs; PHR formats and PHR trigger conditions when operating through BWP; and configuration of default settings for virtual PHRs when operating through BWP and / or SUL.

[0035] The various embodiments described herein are generally applicable to UL transmissions. UL transmissions may include PUSCH, PUCCH, SRS, and / or PRACH transmissions. In various embodiments, antenna ports are defined so that the channel on which a symbol of an antenna port is transmitted can be inferred from the channel on which another symbol on the same antenna port is transmitted. One or more antenna ports are used for UL transmissions.

[0036] An "antenna port" according to an embodiment may be a logical port that may correspond to a beam (caused by beamforming) or may correspond to a physical antenna on a device. In some embodiments, a physical antenna may be directly mapped to a single antenna port, where the antenna port corresponds to an actual physical antenna. Alternatively, a set or subset of physical antennas, or a set of antennas or an antenna array or an antenna subarray may be mapped to one or more antenna ports after applying complex weights, cyclic delays, or both to the signal on each physical antenna. A physical antenna set may have antennas from a single module or panel or from multiple modules or panels. The weights may be fixed as in an antenna virtualization scheme, such as cyclic delay diversity ("CDD"). The process for deriving antenna ports from physical antennas may be specific to device implementation and transparent to other devices.

[0037] Two antenna ports are referred to as quasi-co-located ("QCL") if large-scale properties of the channel over which symbols for one antenna port are transmitted can be inferred from the channel over which symbols for the other antenna port are transmitted. The large-scale properties include one or more of delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters. The two antenna ports may be quasi-co-located for a subset of the large-scale properties. The spatial Rx parameters may include one or more of: angle of arrival ("AoA"), primary AoA, average AoA, angular spread, power angular spectrum ("PAS") of AoA, average angle of departure ("AoD"), PAS of AoD, transmit / receive channel correlation, transmit / receive beamforming, spatial channel correlation, etc.

[0038] Carrier aggregation ("CA") allows joint transmit / receive operations in a class set of serving cells or component carriers ("CC"), which are collectively referred to as a cell group ("CG"). In traditional 4G LTE network deployments, each downlink ("DL") or uplink ("UL") CC includes only a single contiguous transmission bandwidth within which a UE can be scheduled for reception / transmission.

[0039] In 5G New Radio ("NR") deployments, transmission and reception may include centimeter wave bands and millimeter wave bands as well as higher frequency bands, for example, from 6 GHz to up to 70 GHz. These frequency bands are expected to be one of the key deployment scenarios. In such high frequency bands, the carrier bandwidth may be up to 400 MHz (or wider) and each carrier may consist of multiple non-contiguous spectrum blocks. Since (i) the UE receive channel bandwidth may be less than the carrier bandwidth, (ii) non-contiguous spectrum may be used for one carrier, and (iii) multiple parameter sets may be configured within one carrier, bandwidth part ("BWP") based operation is developed in 5G NR.

[0040] Each BWP consists of a set of contiguous physical resource blocks ("PRBs") and is associated with a specific parameter set (e.g., subcarrier spacing in OFDM operation) and / or service (e.g., eMBB or URLLC). Some use cases for BWPs will support, for example, reduced UE bandwidth capabilities; reduced UE energy consumption with bandwidth adaptation; frequency division multiplexing ("FDM") for different parameter sets; and non-contiguous spectrum.

[0041] In BWP operation, the UE is configured with one or more DL BWPs for DL ​​reception and one or more UL BWPs for UL transmission. For example, in 5G NR Release 15 ("Rel-15"), a UE may be configured with up to four DL BWPs and up to four UL BWPs in a given serving cell. The configured DL BWP and ULBWP with the same BWP index for a serving cell are considered to have the same center frequency position in TDD operation, but may have different frequency positions (e.g., below 6 GHz) in FDD operation without having to be separated by a frequency division duplex interval.

[0042] The initial DL BPW is defined as the DL BWP of the serving cell (Pcell, PSCell and / or SCell) that corresponds to the control resource set ("CORESET") of the Type0-PDCCH common search space for scheduling reception of the remaining minimum system information ("RMSI"). The initial UL BWP is defined as the UL BWP of the primary serving cell (PCell or PSCell) on which at least the initial random access procedure occurs.

[0043] The active DL / UL BWP is defined as the DL / UL BWP on the serving cell on which data reception / transmission may occur. The active DL / UL BWP may be the same as the initial DL / UL BWP. As of 3GPP NR Rel-15, the UE is not expected to monitor or perform measurements on any configured BWP other than the active DL / UL BWP.

[0044] The active DL / UL BWP may change dynamically. For example, the BWP indicator field in the downlink control information ("DCI") for DL ​​assignment / UL grant may be used to indicate which of the configured DL / UL BWPs is currently active for DL ​​reception / UL transmission. If the active DL BWP has not been used for a long time (e.g., no DCI is received on this DL BWP), the UE falls back to the so-called default DL BWP, which is the initial DL BWP or another DL BWP (e.g., configured by higher layers).

[0045] Additionally, in 5G NR, an additional uplink carrier may be paired / supplemented to an NR serving cell (in TDD and FDD operations) as a supplemental access link for UL transmission purposes only, such that two ULs are paired with a single DL in the NR serving cell. The additional carrier may be in the same frequency band as normal or in a different frequency band. This additional paired uplink carrier to the serving cell is referred to as a supplementary (or auxiliary) uplink ("SUL"). For example, a SUL carrier at 700 MHz may supplement / supplement a "normal" UL carrier (e.g., a non-SUL carrier, also referred to as a "NUL" carrier) at 4 GHz, 30 GHz, or 70 GHz, where the SUL carrier may provide enhanced uplink coverage compared to the NUL carrier. In some cases, the NR SUL carrier may fully or partially overlap with the LTE UL carrier in frequency.

[0046] In terms of interworking of BWP and SUL, note that if a SUL carrier is configured for a serving cell, the SUL can have an independent / separate set of (e.g., up to 4) UL BWPs configured for the UE. Therefore, in NR Rel-15, for a serving cell configured with a SUL carrier, there can be one active UL BWP on the NUL carrier (e.g., non-SUL carrier) and one active UL BWP on the SUL carrier. In addition, an initial UL BWP can be configured on the SUL carrier in addition to the initial UL BWP configured for the NUL carrier of the primary serving cell.

[0047] Transmit Power Control (PC) and Power Headroom Reporting (PHR) are important elements of UE operation. PC and PHR have been fully discussed for non-CA (e.g., single cell) and CA scenarios for previous generations of cellular communication systems (such as in LTE). However, the description of PC and PHR behavior in 5G NR will involve BWP operation and SUL carriers, and create novel situations and scenarios.

[0048] Power control and power headroom formulas involving some aspects of BWP operation have been adopted for 5G operation. For example, if a UE transmits PUSCH on UL BWP b of UL carrier f of serving cell c using parameter set configuration with index j and PUSCH power control adjustment state with index l, the UE determines the PUSCH transmission power in PUSCH transmission occasion i as

[0049]

[0050] Wherein, the PUSCH transmission power in Equation 1 is in units of [dBm], wherein all parameters in the calculation are defined in 3GPP TS 38.213 (version 15.0.0), which is incorporated herein by reference.

[0051] A number of PC parameters are configured per UL BWP, including: a UE-specific component of a target power spectral density ("PSD") value 'P0_UE', a fractional path loss compensation factor α, a path loss ("PL") reference, a closed loop power control ("CL-PC") process, and a transmission bandwidth (e.g., number of PRBs) allocation. However, a configured maximum UE transmit power 'P0_UE' may be configured per UL carrier of a serving cell. CMAX ,f,c' and the nominal component "P0_nominal" of the target PSD value, regardless of the selection of UL BWP.

[0052] In a related example, a UL BWP-dependent PUSCH PHR may be defined in a similar manner as follows: 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] to obtain a Type 1 report. Therefore, if the UE determines that the Type 1 power headroom report for an activated serving cell is based on actual PUSCH transmissions, then for PUSCH transmission occasion i on active UL BWP b of carrier f of serving cell c, the UE calculates the Type 1 power headroom report as

[0053]

[0054] If the UE does not send 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 no PUCCH / PUSCH transmission is performed in transmission occasion i, P CMAX,f,c (i). Instead, the UE reports a "virtual" power headroom based on a reference PUSCH transmission. Therefore, if the UE determines that the Type 1 power headroom report for an activated serving cell is based on a reference PUSCH transmission, then for PUSCH transmission occasion i on active UL BWP b of carrier f of serving cell c, the UE calculates the Type 1 power headroom report in [dB] as

[0055]

[0056] Assume that MPR = 0dB, A-MPR = 0dB, P-MPR = 0dB, ΔT C = 0dB to calculate Among them, MPR, A-MPR, P-MPR and ΔT C are power reduction / backoff items. All these power reduction / backoff items are defined in 3GPP TS 38.101 Rel-15. Note that as of NR Rel-15, only one PHR per serving cell is supported; however, future phases of 3GPP NR (e.g., beyond 5G NR Rel-15) may support multiple PHRs per serving cell.

[0057] Regarding BWP operation for power control, at the time of the invention, it is not defined whether the same or different power control parameters and path loss measurement reference resources need to be configured in each BWP and the closed-loop power control process needs to be reset, or not based on changing the active BWP depending on the deployment and operation scenario. Therefore, the network entity ("NE") (such as, gNB or other RAN node) can select the appropriate configuration and operation mode and indicate it to the UE explicitly or implicitly. In addition, the virtual PHR configuration can correspond to the default settings instead of the gNB configuration settings, in which case the default settings for the UL carrier and UL BWP need to be specified. In addition, in the case of supporting multiple active BWPs, the PC parameters as well as the PHR trigger conditions and PHR format should take into account the number of configured BWPs and the number of active BWPs, which has not been discussed in previous work.

[0058] Figure 1 A wireless communication system 100 for UE power control of multiple UL carriers according to an embodiment of the present disclosure is depicted. In one embodiment, the wireless communication system 100 includes at least one remote unit 105, a radio access network ("RAN") 120, and a mobile core network 140. The RAN 120 and the mobile core network 140 form a mobile communication network. The RAN 120 may include a base unit 110 with which the remote unit 105 communicates using a wireless communication link 115. Even in the case of Figure 1 A specific number of remote units 105, base units 110, wireless communication links 115, RAN 120, and mobile core networks 140 are depicted in the figure, but technicians in this field will recognize that any number of remote units 105, base units 110, wireless communication links 115, RAN 120, and mobile core networks 140 may be included in the wireless communication system 100.

[0059] In one embodiment, the wireless communication system 100 complies with the 5G system specified in the 3GPP specification. However, more generally, the wireless communication system 100 may implement some other open or proprietary communication networks, such as LTE or WiMAX, as well as other networks. The present disclosure is not intended to be limited to any particular wireless communication system architecture or protocol implementation.

[0060] In one embodiment, the remote unit 105 may include a computing device such as a desktop computer, a laptop computer, a personal digital assistant (“PDA”), a tablet computer, a smart phone, a smart TV (e.g., a TV connected to the Internet), a smart appliance (e.g., an appliance connected to the Internet), a set-top box, a game console, a security system (including a security camera), a vehicle-mounted computer, a network device (e.g., a router, a switch, a modem), etc. In some embodiments, the remote unit 105 includes a wearable device such as a smart watch, a fitness band, an optical head-mounted display, etc. In addition, the remote unit 105 may be referred to as a UE, a subscriber unit, a mobile device, a mobile station, a user, a terminal, a mobile terminal, a fixed terminal, a subscriber station, a user terminal, a wireless transmit / receive unit (“WTRU”), a device, or other terms used in the art.

[0061] The remote units 105 may communicate directly with one or more base units 110 in the RAN 120 via uplink ("UL") and downlink ("DL") communication signals. In addition, the UL and DL communication signals may be carried over wireless communication links 115. Here, the RAN 120 is an intermediate network that provides access to the mobile core network 140 for the remote units 105.

[0062] In some embodiments, the remote unit 105 communicates with the application server 135 via a network connection with the mobile core network 140. For example, an application 107 (e.g., a web browser, a media client, a phone / VoIP application) in the remote unit 105 can trigger the remote unit 105 to establish a PDU session (or other data connection) with the mobile core network 140 via the RAN 120. The mobile core network 140 then relays traffic between the remote unit 105 and the application server 135 in the packet data network 130 using the PDU session. Note that the remote unit 105 can establish one or more PDU sessions (or other data connections) with the mobile core network 140. In this way, the remote unit 105 can simultaneously have at least one PDU session for communicating with the packet data network 130 and at least one PDU session for communicating with another data network (not shown).

[0063] The base units 110 may be distributed over a geographic area. In some embodiments, the base units 110 may also be referred to as access terminals, access points, bases, base stations, node Bs, eNBs, gNBs, home node Bs, relay nodes, or by any other terminology used in the art. The base units 110 are typically part of a radio access network ("RAN") such as the RAN 120 that may include one or more controllers communicatively coupled to one or more corresponding base units 110. These and other elements of the radio access network are not shown, but are well known to those of ordinary skill in the art. The base units 110 are connected to the mobile core network 140 via the RAN 120.

[0064] The base unit 110 can serve multiple remote units 105 within a service area (e.g., a cell or cell sector) via a wireless communication link 115. The base unit 110 can communicate directly with one or more of the remote units 105 via communication signals. Typically, the base unit 110 sends DL communication signals in the time domain, frequency domain, and / or spatial domain to serve the remote units 105. In addition, the DL communication signals can be carried on the wireless communication link 115. The wireless communication link 115 can be any suitable carrier in a licensed or unlicensed radio spectrum. The wireless communication link 115 facilitates communication between one or more of the remote units 105 and / or one or more of the base units 110.

[0065] In one embodiment, mobile core network 140 is a 5G core ("5GC") or an evolved packet core ("EPC") that can be coupled to packet data networks 130, such as the Internet and private data networks and other data networks. Remote units 105 can have subscriptions or other accounts with mobile core network 140. Each mobile core network 140 belongs to a single public land mobile network ("PLMN"). The present disclosure is not intended to be limited to any particular wireless communication system architecture or protocol implementation.

[0066] The mobile core network 140 includes several network functions ("NFs"). As depicted, the mobile core network 140 includes a plurality of user plane functions ("UPFs") 145. The mobile core network 140 also includes a plurality of control plane functions, including but not limited to an access and mobility management function ("AMF") 141 serving the RAN 120; a session management function ("SMF") 143, and a policy control function ("PCF") 147. In certain embodiments, the mobile core network 140 may also include an authentication server function ("AUSF"), a unified data management function ("UDM") 149, a network repository function ("NRF") (used by various NFs to discover and communicate with each other through APIs), or other NFs defined for the 5GC.

[0067] Despite Figure 1 Specific numbers and types of network functions are depicted in the mobile core network 140, but those skilled in the art will recognize that any number and types of network functions may be included in the mobile core network 140. In addition, in the case where the mobile core network 140 is an EPC, the depicted network functions may be replaced by appropriate EPC entities such as MME, S-GW, P-GW, HSS, etc. In some embodiments, the mobile core network 140 may include an AAA server.

[0068] In various embodiments, the mobile core network 140 supports different types of mobile data connections and different types of network slices, where each mobile data connection utilizes a specific network slice. Herein, a "network slice" refers to a portion of the mobile core network 140 that is optimized for a certain type of business or communication service. In some embodiments, various network slices may include separate instances of network functions, such as SMF 143 and UPF 145. In some embodiments, different network slices may share some common network functions, such as AMF 141. For ease of illustration, in Figure 1 The different network slices are not shown, but their support is assumed.

[0069] Although Figure 1 Components of a 5G RAN and 5G core network are depicted, but the described embodiments for UE power control for multiple UL carriers apply to other types of communication networks, including IEEE 802.11 variants, UMTS, LTE variants, CDMA 2000, Bluetooth, etc. For example, in an LTE / EPC variant, AMF 141 may be mapped to an MME, SMF 143 may be mapped to a control plane portion of a PGW, UPF 145 may be mapped to a user plane portion of a STW and a PGW, and so on.

[0070] The remote unit 105 may be configured for UL BWP and SUL. In addition, the remote unit 105 may be configured with a maximum UE transmit power on the serving cell c and the UL carrier f. In various embodiments, the remote unit 105 uses the determined transmit power value to perform uplink transmissions on one or more active UL BWPs. The various embodiments described herein are generally applicable to UL transmissions. The UL transmission may include a PUSCH transmission, a PUCCH transmission, an SRS transmission, or a PRACH transmission.

[0071] In one embodiment, in single cell or carrier aggregation operation, simultaneous transmissions (e.g., transmissions with the same or different start time instances and / or transmission lengths) may occur on different (multiple) active UL BWPs of different uplink carriers and / or serving cells, which results in partial or full overlap between different UL transmissions. In such an embodiment, if the aggregate transmit power of the remote unit 105 on all corresponding uplink carriers and / or serving cells in any symbol / portions / parts of the UL transmission exceeds the configured maximum UE transmit power, e.g., P CMAX , the remote unit 105 reduces power and / or abandons transmission on the UL BWP / carrier / cell, for example, by applying a power reduction factor.

[0072] Figure 2 A network architecture 200 for UE power control for multiple UL carriers according to an embodiment of the present disclosure is depicted. The network architecture 200 includes a UE 205 and a RAN node 210. The UE 205 may be an embodiment of the remote unit 105 described above. The RAN node 210 (e.g., a gNB) may be an embodiment of the base unit 110 described above.

[0073] In LTE, the configured maximum UE transmit / output power for serving cell c is denoted as P CMAX ,c, and is essentially defined as the UE power level minus some power reduction terms (e.g., MPR, A-MPR, P-MPR, ΔT C ). To date, a similar definition is adopted for 5G NR, with the extension that a separate P is defined for each UL carrier f (e.g., NUL and SUL) of the serving cell c. CMAX ,f,c.

[0074] As depicted, RAN node 210 may configure multiple UL BWPs to UE 205 (see messaging 215). In some embodiments, the configured maximum UE output power on serving cell c and UL carrier f is also a function of the UL BWP, i.e., P CMAX ,b,f,c. As depicted, the RAN node 210 may configure the UE 205 with a P for each configured UL BWP. CMAX , b, f, c (see messaging 220). Additionally, various specified maximum power reduction terms (eg, MPR, A-MPR, P-MPR, ΔT C ) and / or higher layers for UL carrier f and serving cell c signaled maximum allowed UE output power (P CMAX ,b,f,c in the formula 'PEMAX ,f,c'), so that the parameters MPR_b,f,c or P are specified and / or configured EMAX ,b,f,c,etc.

[0075] Different MPR limits may apply to different UL BWPs of uplink carriers, and the applicable limits may be specified and / or configured for the UE. For example, a first BWP that is not near a band edge may have a first MPR limit, while a second BWP at a band edge may have a second MPR limit. The second MPR limit may be stricter than the first MPR limit.

[0076] Similarly, higher layers may configure the UE with the maximum allowed UE output power (P EMAX ,b,f,c) (see messaging 220). For example, a first BWP that is not near a band edge may have a first value of the maximum allowed UE output power, while a second BWP at a band edge may have a second value of the maximum allowed UE output power. The second value of the maximum allowed UE output power may be less than the first value of the maximum allowed UE output power.

[0077] In one example, if the frequency distance between one UL BWP (or a first UL BWP set) and another UL BWP (or a second UL BWP set) (e.g., the distance between the highest frequency of the first UL BWP set and the lowest frequency of the second UL BWP set) is greater than a certain predetermined / configured threshold, then some or all of the specified maximum power reduction terms (e.g., MPR, A-MPR, P-MPR, ΔT C ) and / or the configured maximum allowed UE output power P EMAX ,b,f,c and therefore, the configured P for the first UL BWP set CMAX ,b,f,c will be different from those of the second UL BWP set.

[0078] In one example, if the UE uses different power amplifiers (PAs) for UL transmission on different UL BWPs of the UL carrier of the serving cell or if it is assumed that the UE uses different power amplifiers (PAs) for UL transmission on different UL BWPs of the UL carrier of the serving cell, different PAs may be set. CMAX ,b,f,c values. Therefore, P can be calculated under the following assumptions CMAX,b,f,c: Increase the transmit power independently on different UL BWPs of UL carrier f of serving cell c. In one example, if the UE uses a common power amplifier (PA) for UL transmissions on different BWPs of the UL carrier of the serving cell or if it is assumed that the UE uses a common power amplifier (PA) for UL transmissions on different BWPs of the UL carrier of the serving cell, P can be calculated under the following assumptions: CMAX ,b,f,c: Increase the transmit power by the same amount in dB at different UL BWPs of UL carrier f of serving cell c. In this case, for each MPR item, a single value common to different UL BWPs can be used; however, for different UL BWPs of UL carrier f of serving cell c, the maximum allowed UE output power P can be varied. EMAX ,b,f,c are configured with different values.

[0079] In addition, the RAN node 210 may activate one or more UL BWPs for the UE 205 (see messaging 225). Thus, the UE 205 may calculate P based on the active UL BWPs. CMAX , b, f, c (see block 230). UE 205 uses a UE transmit power specific to the BWP (e.g., based on P CMAX ,b,f,c) to send PUCCH and / or PUSCH (see message delivery 235).

[0080] In some embodiments, the configured maximum UE transmit power on serving cell c and UL carrier f is not a function of the bandwidth portion, i.e., P CMAX ,f,c. In one example, P CMAX ,f,c The specified maximum power reduction term in the formula (e.g., MPR, A-MPR, P-MPR, ΔT C ) may be independent of the UL BWP, for example, they take the same value for all configured UL BWPs within the carrier of the serving cell, so that P CMAX ,f,c are all the same. This can be useful, for example, when there is only one active UL BWP per UL carrier of the serving cell (e.g., in 5G NR Rel-15).

[0081] In another example, the power reduction term for each individual UL BWP of a given UL carrier of a serving cell may be the same or different, but in order to define / configure the maximum UE transmit power for the overall operation of the UL carriers of the serving cell, a "multi-cluster" maximum power reduction term (e.g., "multi-cluster" MPR, A-MPR, P-MPR, ΔT C), which refers to a power reduction for non-contiguous allocation of scheduled PRBs on different UL BWPs of UL carrier f of serving cell c (and possibly also within it), e.g., in terms of the sum of individual MPR terms, A-MPR terms, P-MPR terms on the UL BWPs, similar to the "multi-cluster" power reduction term in LTE for CA operation with non-contiguous PRB allocation within one serving cell [3GPP TS 36.101]. This may be useful, for example, when supporting transmission on multiple active UL BWPs within the UL carrier of the serving cell (e.g., in 5G NR Phase 2, e.g., beyond Rel-15).

[0082] Figure 3 A process 300 for UE power control for multiple UL carriers according to an embodiment of the present disclosure is depicted. The process 300 may be performed by a UE, such as remote unit 105 and / or UE 205. Here, the UE is configured with multiple BWPs for UL carriers (eg, of a serving cell).

[0083] Process 300 begins when the UE implements a closed loop power control ("CL-PC") procedure for a first BWP of a UL carrier (see block 305). Here, it is assumed that the CL-PC procedure is in accumulation mode. The UE detects a switch from the first UL BWP to a second configured UL BWP (see block 310). In response to the switch, the UE determines whether the first UL BWP and the second UL BWP are closely related using one or more factors discussed below (see decision block 315). If the first UL BWP and the second UL BWP are closely related, the UE continues the power control accumulation state of the CL-PC procedure for the second UL BWP (see block 320).

[0084] However, if the first UL BWP and the second UL BWP are not closely related, the UE may check whether the rate of BWP switching is higher than a threshold amount (see decision block 325). Here, if the rate of BWP switching is higher than the threshold amount, the UE continues the power control accumulation state of the CL-PC process for the second UL BWP (see block 320). Alternatively, if the rate of BWP switching is not higher than the threshold amount, the UE resets the power control accumulation state of the CL-PC process for the second UL BWP (see block 330). Note that in some embodiments, the UE may be configured to ignore the rate of BWP switching. In such an embodiment, if the first UL BWP and the second UL BWP are not closely related, the UE resets the power accumulation state of the CL-PC.

[0085] In various embodiments, one or more CL-PC processes may be shared between different UL BWPs of a UL carrier of a serving cell. For example, there may be a total number of (e.g., two) CL-PC processes shared between all UL BWPs of a serving cell. In another example, there may be 2×N CL-PC processes configured for a UL carrier of a serving cell, where N is the number of active UL BWPs of the UL carrier. In such an embodiment, if a switch of one (or more) active UL BWPs (e.g., a switch from a first active UL BWP to a second active UL BWP) occurs (multiple times), the CL-PC process associated with the currently inactive UL BWP may be used as a power control adjustment state for the (multiple) newly active UL BWPs based on a mapping between the old UL BWP and the new UL BWP. Beneficially, continuing the CL-PC process avoids abrupt UE transmit power changes and potential phase discontinuity issues.

[0086] As discussed above, if the CL-PC process is in accumulation mode and if a BWP switch occurs, the power control accumulation state of the old UL BWP(s) may be continued or reset for the new UL BWP(s) based on how closely the UL BWPs are related. The various factors that the UE may consider when determining whether a UL BWP is closely related are as follows:

[0087] In some embodiments, if the old UL BWP and the new UL BWP are separated to a large extent in frequency, the CL-PC process is reset upon active UL BWP switching. For example, if the frequency distance between the old UL BWP and the new UL BWP is greater than a threshold, the UE resets the CL-PC process. As used herein, "frequency distance" refers to the distance between the highest frequency of a first BWP in a lower frequency portion and the lowest frequency of a second BWP in a higher frequency portion. The threshold may be predetermined or configured at the UE.

[0088] Note that given a large frequency separation between two configured BWPs, similar to inter-band CA or intra-band non-continuous CA operation, the UE may be equipped with separate power amplifiers and radio frequency ("RF") chains. Due to the separate PA and RF chains (and the potentially very different dynamic interference levels on the BWPs), the power offset relative to the desired power level in the new UL BWP may be different from the power offset in the old UL BWP. Therefore, in this scenario, the UE resets the power control adjustment state in the accumulation mode, referred to herein as the "power control accumulation state". Therefore, if the UE's active UL BWP changes from a first BWP in the NUL carrier of the serving cell to a second BWP in the SUL of the serving cell, the UE may reset the power control adjustment state due to the large frequency separation between the UL carrier and the SUL carrier.

[0089] Similarly, if the old UL BWP and the new UL BWP are very close in frequency, the accumulation state of the CL-PC process can be continued at the time of active UL BWP switching. For example, if the frequency distance between the old UL BWP and the new UL BWP is less than a threshold (which can be predetermined or configured), the UE continues to the power control adjustment state. In the case of small frequency separation or bandwidth overlap between the two BWPs, the UE can use the same PA and RF chain for both BWPs, and the interference level will not be very different. Therefore, the UE can continue the power control adjustment state from one BWP to another BWP.

[0090] In some embodiments, the UE considers the open-loop parameter values ​​(e.g., P0 and α) when determining whether the new active BWP and the old active BWP are closely related. For example, if the same open-loop parameter (P0 and α) values ​​are configured for the corresponding old UL BWP and the new UL BWP, the CL-PC process can be continued. Alternatively, if different open-loop parameter (P0 and α) values ​​are configured for the corresponding old UL BWP and the new UL BWP, the CL-PC process can be reset when the UL BWP is switched.

[0091] As discussed above, if UL BWP switching occurs very frequently, the CL-PC process may be continued. Here, "very frequently" may be defined as exceeding a threshold rate, for example, more than X switches in the last Y radio frames. In one embodiment, the threshold rate is predefined. In another embodiment, the threshold rate is configured by the RAN node. If UL BWP switching occurs very frequently, the CL-PC process may be continued to avoid sudden UE transmit power changes and ping-pong effects. If the UL BWP switching rate does not exceed the threshold rate, the UE is allowed to reset the CL-PC process.

[0092] In various embodiments, the UE considers UL carrier attributes when determining whether the new active BWP and the old active BWP are closely related. In some embodiments, if the same parameter set (subcarrier spacing) and / or service (traffic type, e.g., eMBB or URLLC) is configured for the corresponding old UL BWP and the new UL BWP, the CL-PC process continues, otherwise, the CL-PC process is reset when the UL BWP is switched. In some embodiments, if the same modulation and coding scheme (MCS) and / or (multiple) channel quality indicator (CQI) table and / or target reliability (e.g., block error rate, "BLER") requirements are configured for the old UL BWP and the new UL BWP, the CL-PC process continues, otherwise, the CL-PC process is reset when the UL BWP is switched.

[0093] In some embodiments, if the same path loss reference or QCL path loss reference is configured for the old UL BWP and the new UL BWP, the CL-PC process continues. Here, the path loss reference in the first (e.g., old) BWP can be the same or QCL as the path loss reference in the second (e.g., new) BWP. Quasi co-location can be for a subset of large-scale attributes (such as only spatial RX parameters), otherwise the CL-PC process is reset at the UL BWP switch.

[0094] In some embodiments, the UE considers the path loss reference and the open loop parameter values ​​when determining whether the new active BWP and the old active BWP are closely related. For example, if the old UL BWP and the new UL BWP are configured with the same / QCL path loss reference(s) and the same open loop parameters (P0 and α), the CL-PC process can be continued, otherwise, the CL-PC process is reset when the UL BWP is switched.

[0095] In some embodiments, the UE considers the two path loss references in conjunction with other attributes when determining whether the new active BWP and the old active BWP are closely related. In some embodiments, if the old UL BWP and the new UL BWP are configured with the same (multiple) / QCL path loss references and the same (multiple) MCS and / or CQI tables and / or target reliability (e.g., BLER) requirements, the CL-PC process continues, otherwise, the CL-PC process is reset at UL BWP switching. In some embodiments, if the old UL BWP and the new UL BWP are configured with the same (multiple) / QCL path loss references and the same (multiple) MCS and / or CQI tables and / or target reliability (e.g., BLER) requirements and the same open-loop parameters (P0 and α), the CL-PC process continues, otherwise, the CL-PC process is reset at UL BWP switching.

[0096] In some embodiments, (multiple) MCS tables and / or (multiple) CQI tables and / or (multiple) target reliability requirements (e.g., BLER) are configured UE-specifically for a given serving cell rather than for each BWP of the serving cell. For a given path loss reference and a given UL physical channel, if the UE is instructed with an MCS table (or code rate table) and / or target reliability that is different from the previous MCS table (or code rate table) and / or target reliability, the UE resets the power control adjustment state after receiving the indication. The indication may be received via a UL grant DCI based on a granted PUSCH, via RRC signaling of the PUSCH or a corresponding DL allocation DCI, and via RRC signaling of the PUSCH based on the configured grant. In one example, the UL grant DCI and / or the DL allocation DCI may include a field for indicating which MCS table associated with different target reliabilities will be used. Alternatively, (multiple) different DCI formats may be defined to support different target reliabilities.

[0097] In certain embodiments, if different modulation and coding schemes (MCS) and / or channel quality indicator (CQI) tables and / or target reliability (e.g., BLER) requirements are configured for two BWPs (or for two services / logical channels / TTI lengths in the same BWP), then the equations for calculating ΔTF,b,f,c(i) and / or some configured parameters (in the power control equations) for calculating ΔTF,b,f,c(i) may be different for the two BWPs (or for two services / logical channels / TTI lengths in the same BWP). In various embodiments, when the configured K S When the value is non-zero, ΔTF,b,f,c(i) can be calculated using the following equation:

[0098]

[0099] In various embodiments, 3GPP TS 38.213 may be used to determine the BPRE ("bits per resource element") and In some embodiments, K may be provided by the parameter deltaMCS for each UL BWP b and serving cell c for each carrier f. S For example, the K used in ΔTF,b,f,c(i) can be S The values ​​are configured to different non-zero values. In such an embodiment, if the configured parameters for calculating ΔTF,b,f,c(i) are different for the two BWPs, the UE may reset the CL-PC process. In one embodiment, when the configured K SWhen the value is zero, ΔTF,b,f,c(i)=0. In some embodiments, if the PUSCH transmission is on more than one transmission layer, ΔTF,b,f,c(i)=0.

[0100] Therefore, in various embodiments, the UE receives multiple target reliability configurations. Here, each of the multiple target reliability configurations includes at least one of the following: a modulation and coding scheme (MCS) table, a channel quality indicator (CQI) table, and an associated radio network temporary identifier. In addition, the UE can perform a first uplink transmission of the uplink channel based on the first target reliability configuration and the power control adjustment state of the uplink channel.

[0101] In some embodiments, the UE receives an indication of a second uplink transmission for an uplink channel. Here, the second uplink transmission of the uplink channel may be based on a second target reliability configuration and a power control adjustment state of the uplink channel. The UE determines whether the second target reliability configuration is different from the first target reliability configuration, and in response to a determination that the second target reliability configuration is different from the first target reliability configuration, the power control adjustment state of the uplink channel may be reset.

[0102] Afterwards, the UE performs a second uplink transmission of the uplink channel based on the second target reliability configuration and the power control adjustment state of the reset uplink channel. In some embodiments, each of the multiple target reliability configurations further includes an associated downlink control information (DCI) format. In some embodiments, each of the multiple target reliability configurations further includes a power control parameter set. In such an embodiment, the power control parameter set may include at least one of a power spectral density per subcarrier spacing and a path loss compensation parameter.

[0103] In some embodiments, the uplink channel is a physical uplink shared channel (PUSCH).In some embodiments, the UE further receives, via downlink control information, an indication that the second uplink transmission of the uplink channel is based on a second target reliability configuration.

[0104] In beam-based communication operations (such as, 5G NR), due to directional antenna beamforming operations, a single path loss reference and a single CL-PC process (e.g., as used in 4G LTE) are insufficient to capture power characteristics in all directions. Therefore, in 5G NR Rel15, the UE will support up to 2 CL-PC processes per serving cell and up to 4 path loss references per serving cell. This is a trade-off between minimizing UE complexity and accurate UE transmit power determination. Note that since the two UL carriers (e.g., NUL and SUL carriers) of the serving cell are linked to a single DL carrier, the path loss reference cannot be distinguished (e.g., configured differently) for the two UL carriers of the serving cell.

[0105] With BWP-specific power control operation (in which open loop (e.g., α and UE-specific components of at least P0), path loss reference, and CL-PC process are configured per UL BWP), the number of required PL references and CL-PC processes may be different in case of supporting multiple active BWPs. The following solution clarifies whether the number of maintained PL references and / or CL-PC processes will be proportional to the number of active UL BWPs.

[0106] In some embodiments, for a serving cell, the UE is configured with and maintains a total number (e.g., M<=4) of path loss references, regardless of the number of configured BWPs and / or the number of active BWPs per serving cell. This first solution is beneficial for lower UE complexity and is not expected to result in significant performance loss, especially for lower frequency bands (such as, below 6 GHz).

[0107] In some embodiments, the UE is configured with and maintains a number of path loss references (e.g., M<=4) for each configured UL BWP of each UL carrier of each serving cell, such that when up to 4 UL BWPs are configured per serving cell, the UE is configured with and maintains a total number of (e.g., M<=16) path loss references, regardless of the number of active UL BWPs. Note that the UE may be configured with a different number of path loss references for different BWPs. This second solution significantly increases the UE complexity compared to the first solution. Beneficially, the second solution improves UE transmit power determination accuracy for higher frequency bands (e.g., above 6 GHz), where different BWPs within a UL carrier of a serving cell are expected to be farther apart.

[0108] In some embodiments, the UE maintains a total number of (M×N) path loss references per serving cell, where L≤(M×N)≤4N. Here, N≤4 is the number of active UL BWPs within the UL carrier of the serving cell. The number L may be fixed for all frequency bands, or may depend on the frequency band of the UL carrier of the serving cell. The UE may be configured with a different number of path loss references for different active BWPs. For example, in the case of NR Rel 15 (where only one BWP is active within each UL carrier of the serving cell), the UE may maintain up to eight path loss references per serving cell. This third solution may be useful for compromising UE complexity and accurate UE transmit power determination on different UL BWPs in low and high frequency bands.

[0109] In some embodiments, the UE is configured with and maintains a set number (e.g., two) of separate / independent CL-PC processes per UL BWP, so that, for example, when up to 4 UL BWPs are configured for the UL carrier of the serving cell, up to eight separate CL-PC processes per UL BWP of the serving cell, regardless of the number of active UL BWPs. The UE may be configured with different numbers of CL-PC processes for different BWPs.

[0110] In certain embodiments, the UE is configured with and maintains a total number (eg, two) of CL-PC processes per serving cell that are shared among all BWPs of two UL carriers, regardless of the number of configured UL BWPs and / or the number of active ULBWPs.

[0111] In another embodiment, the UE is configured with and maintains a total of 2×N CL-PC processes shared among all UL BWPs of the UL carrier of the serving cell, where N is the number of active BWPs, so that 2×N CL-PC processes are used, as is the power adjustment state of the active BWP. The UE may be configured with different numbers of CL-PC processes for different active BWPs. In one example, if there is only one active BWP (as in the case of NR Rel15), the UE maintains only two CL-PC processes for each UL carrier of the serving cell.

[0112] Figure 4 A network architecture 400 for UE power control for multiple UL carriers according to an embodiment of the present disclosure is depicted. The network architecture 400 includes a UE 405 and a RAN node 410. The UE 405 may be an embodiment of the remote unit 105 described above. The RAN node 410 (e.g., a gNB) may be an embodiment of the base unit 110 described above.

[0113] RAN node 410 may configure NUL carriers and SUL carriers to UE 405 (see messaging 415). During operation with respect to NUL and SUL, UE 405 detects when UL transmissions are scheduled on different UL carriers that overlap in time (see block 420). UE 405 determines that the estimated aggregate transmit power during the overlapping UL transmissions will exceed the P for UE 405. CMAX (See box 425).

[0114] As discussed in more detail below, in response to the aggregate transmission power exceeding the limit, the UE 405 reduces the power of future UL transmissions according to one or more priority rules (see block 430). In some embodiments, the UE 405 reduces the power by applying a power reduction factor to one or more UL carriers during the overlapping period. In some embodiments, the UE 405 reduces the power by abandoning UL transmissions on one or more UL carriers during the overlapping period. The UL transmission power has been reduced to comply with the P CMAX Thereafter, the UE 405 transmits PUCCH and / or PUSCH (see messaging 435).

[0115] Although described with reference to multiple UL carriers on the same serving cell (e.g., NUL / SUL operation), similar techniques can be applied to a UE 405 configured with multiple UL carriers on multiple serving cells (e.g., CA on UL), and overlapping UL transmissions are scheduled on different UL carriers. Similar principles also apply when the UE 405 is configured with multiple active UL BWPs and overlapping UL transmissions are scheduled on different active UL BWPs.

[0116] In some embodiments, in single cell (NUL / SUL) or carrier aggregation operation, overlapping transmissions may overlap in time (e.g., have the same or different start time instances and / or have the same or different lengths / durations) on different uplink carrier(s) of different active UL BWPs and / or serving cells where transmissions occur. This situation results in partial or full overlap between different UL transmissions. If the aggregate transmit power of the UE 405 on all corresponding uplink carriers and / or serving cells in any symbol / part / section of the UL transmission exceeds the configured maximum UE transmit power, e.g., P CMAX , the UE 405 reduces power or abandons transmission on the UL BWP / carrier / cell according to the following priority rules. Note that, for example, when the priority sorting of UL BWP / carrier / cell cannot be resolved by only one priority rule, a combination of priority rules can also be used.

[0117] When simultaneous transmissions do not occur on the UL uplink carrier and the SUL uplink carrier of the same serving cell, the UE 405 may follow rules based on the priority of the signal / channel. For example, in the case of the same priority order and for operation with two UL carriers, the UE 405 prioritizes power allocation for transmissions on the carrier where the UE 405 is configured to send PUCCH. However, if PUCCH is not configured for either of the two UL carriers, the UE 405 prioritizes power allocation for transmissions on the non-supplementary UL carrier.

[0118] When simultaneous transmission occurs on the NUL uplink carrier and the SUL uplink carrier of one or more serving cells, if, when NUL / SUL operation is ignored, the two transmissions on the two UL carriers of the serving cell correspond to signals / channels at different priority levels (e.g., according to the priority rules described in Section 7.5 of 3GPP TS 38.213Rel-15), then the NUL / SUL operation does not affect / change the priority, i.e., only the priority level based on the signal / channel content described above is followed.

[0119] However, if, when ignoring the NUL / SUL operation, two transmissions on two UL carriers of the serving cell correspond to signals / channels of the same priority level (e.g., according to the priority rules described in Section 7.5 of 3GPP TS 38.213 Rel-15) (e.g., when the two transmissions are SRS transmissions of the same time domain periodicity behavior, or, for example, when a PUSCH without uplink control information (UCI) is transmitted on one NUL carrier and another PUSCH without UCI is transmitted on another UL carrier (e.g., SUL)), the UE 405 applies one or more of the following priority rules to resolve the priority order of the NUL carrier and the SUL carrier:

[0120] In some embodiments, UL carriers configured for PUCCH transmission have higher priority than non-PUCCH UL carriers. The NUL / SUL carrier position for PUCCH may be semi-statically configured by higher layers. In some embodiments, the NUL carrier always has higher priority than the SUL carrier regardless of the NUL / SUL position configuration for PUCCH.

[0121] In a scenario where multiple active UL BWPs per UL carrier of a serving cell are supported, when overlapping transmissions occur on more than one active UL BWP of one / two uplink carriers of one or more serving cells, if the UL transmissions on the multiple active UL BWPs correspond to signals / channels at different priority levels (e.g., according to the priority rules described in Section 7.5 of 3GPP TS 38.213 Rel-15) when BWP operation is ignored, the BWP operation does not affect / change the priority level. Therefore, UE 405 follows the priority level based on the signal / channel content described above.

[0122] However, when ignoring BWP operation, if two transmissions on multiple active UL BWPs correspond to signals / channels of the same priority level (e.g., according to the priority rules designed in Section 7.5 of 3GPP TS 38.213 Rel-15) (e.g., when all active UL BWPs have SRS transmissions with the same time-domain periodicity behavior, or, for example, when one PUSCH without UCI is transmitted on one active UL BWP (e.g., toward one spatial direction) and another PUSCH without UCI is transmitted on another UL BWP (e.g., toward another spatial direction)), then the UE 405 applies one or more of the following priority rules to resolve the priority order of the multiple active BWPs:

[0123] In some embodiments, an active UL BWP corresponding to a higher parameter set (e.g., a larger subcarrier spacing) has a higher priority. In some embodiments, an active UL BWP corresponding to a higher priority service / traffic type (e.g., URLLC) has a higher priority than an active UL BWP corresponding to a lower priority service / traffic type (e.g., eMBB).

[0124] In some embodiments, an active UL BWP corresponding to (multiple) higher priority MCS and / or CQI tables and / or target reliability (e.g., BLER) requirements (e.g., that configured for URLLC) has a higher priority than an active UL BWP corresponding to (multiple) lower priority MCS and / or CQI tables and / or target reliability (e.g., BLER) requirements (e.g., that configured for eMBB).

[0125] In certain embodiments, in the case where the active UL BWP belongs to a single serving cell, the active UL BWP with the lowest BWP index has the highest priority. In the case where the (multiple) active BWPs belong to different serving cells, the (multiple) active BWPs on the serving cell with the lowest serving cell index have the highest priority. The case where the active UL BWP belongs to a single carrier of a serving cell has been described above.

[0126] In some embodiments, the attributes (multiple) used for prioritization of multiple active BWPs (such as parameter sets, service / traffic type priority levels, and (multiple) MCS and / or CQI tables and / or target reliability (e.g., BLER) requirement priority levels) are the same. In such embodiments, the UE 405 then applies power scaling between those active UL BWPs in the same manner, except for one or more UL transmissions corresponding to the abandoned one or more active UL BWPs. In other embodiments, the power scaling or reduction between those active UL BWPs depends on the UE implementation.

[0127] In some embodiments, the active UL BWP belongs to a single serving cell, the active UL BWP with the lowest BWP index has a higher priority. In the case where the active BWP(s) belong to different serving cells, the active BWP(s) on the serving cell with the lowest serving cell index has a higher priority.

[0128] Figure 5 A network architecture 500 for UE power control for multiple UL carriers according to an embodiment of the present disclosure is depicted. The network architecture 500 includes a UE 505 and a RAN node 510. The UE 505 may be an embodiment of the remote unit 105 described above. The RAN node 510 (e.g., a gNB) may be an embodiment of the base unit 110 described above.

[0129] As depicted, RAN node 510 may configure multiple UL BWPs to UE 505 (see messaging 515). As discussed above, the configured maximum UE output power on serving cell c and UL carrier f may be a function of the UL BWP, i.e., P CMAX ,b,f,c. As depicted, the RAN node 510 may configure the UE 505 with a P for each configured UL BWP. CMAX,b,f,c (see messaging 520). In addition, the RAN node 510 may activate one or more UL BWPs of the UE 505 (see messaging 525). As used herein, the term "active BWP" refers to a BWP where uplink transmission and / or downlink transmission may occur. Thus, the UE 505 may calculate a power headroom level and / or a power headroom level (PH) of an active BWP. b ) (See block 530). The UE 505 sends one or more PHRs to the RAN node 510 (See messaging 535).

[0130] As described above, when the UE 505 is configured with multiple UL BWPs for a serving cell and one or more of the configured UL BWPs are active, the UE 505 reports power headroom information for each active UL BWP of the serving cell (see messaging 535). The reported power headroom information may include power headroom levels (PHs) used to calculate the power headroom level and / or the power headroom level of the active BWP. b )’s maximum UE transmit power level P CMAX ,b,f,c. A power headroom (PH) type (e.g., Type 1 or Type 3 PH) may also be reported. In some embodiments, the UE 505 may report multiple PHRs for the serving cell.

[0131] In some embodiments, the UE 505 may calculate and report the PHR for an active UL BWP only when the active UL BWP is configured with a different path loss reference (e.g., the DL RS resources used for the path loss estimation of the first active UL BWP are not the QCLs with the DL RS resources used for the path loss estimation of the second active UL BWP (e.g., at least for spatial Rx parameters)).

[0132] In certain embodiments, when the UE 505 is configured to report multiple PHRs for different active UL BWPs of an UL carrier of a serving cell, the UE 505 reports the absolute PHR of a first active UL BWP in the serving cell and the differential PHRs of (multiple) other UL BWPs in the serving cell, where the differential PHR is defined as the relative difference between the second / target PHR and the first / reference PHR.

[0133] The differential PHR can be positive, zero, or negative, where a positive differential PHR means that the power headroom (PH) on the second / target active UL BWP is higher compared to the first / reference active UL BWP; and where a negative differential PHR means that the PH on the second / target active UL BWP is lower compared to the first / reference active UL BWP, and a zero differential PHR means that the PH on the second / target active UL BWP is the same as the first / reference active UL BWP. The differential PHR is used to reduce the bit width used to report multiple PHRs.

[0134] In certain embodiments, when the UE 505 is configured to report multiple PHRs for different active UL BWPs of the UL carrier of the serving cell, all PHRs corresponding to all active BWPs report absolute values, e.g., differential PHRs are not used. In certain embodiments, when the UE 505 is configured to report multiple PHRs for different active UL BWPs of the UL carrier of the serving cell, how to determine whether to report absolute or differential PHRs for all active UL BWPs depends on the gNB determination and / or UE configuration.

[0135] In one example, only when P CMAX ,f,c does not depend on the choice of BWP (e.g., a single P CMAX ,f,c values ​​are used for all BWPs configured on this UL carrier of the serving cell), differential PHR is used, which can be information that has been transmitted to the gNB by the UE 505. In one example, differential PHR is used only when the same or quasi-co-located path loss reference (e.g., the same DL RS resource for path loss estimation) is configured for all UL BWPs configured on this UL carrier of the serving cell. In another example, the UE 505 is semi-statically configured whether to report absolute or differential PHRs for different active UL BWPs of the UL carrier of the serving cell.

[0136] In certain embodiments, when the UE 505 is configured to report multiple PHRs for different active UL BWPs of the UL carrier of the serving cell, the order of the included PH information is from the PH for the lowest active BWP index to the PH for the highest active BWP index. For the BWP corresponding to the lowest active BWP index, an absolute PH is included. For other BWPs, if the path loss reference of the BWP is the same as or QCL to the path loss reference of the BWP with a smaller BWP index (the smaller BWP index is for the other BWP) (for which the path loss reference includes the PH), a differential PH is included, otherwise, a full PH of the other BWP is included.

[0137] In some embodiments, when the UE 505 is configured to report multiple PHRs for different active UL BWPs of the UL carrier of the serving cell, one or more BWP groups may be formed such that each BWP group shares the same or quasi-co-located path loss reference and / or the same PHR. CMAX ,b,f,c values. According to this embodiment, in order to report multiple PHRs for multiple active UL BWPs, the UE 505 reports the absolute PHR of the first BWP in each BWP group and reports the differential PHR(s) of all other active UL BWPs in the BWP group. The first BWP in each BWP group may be the BWP with the lowest BWP index.

[0138] In some embodiments, the UE 505 uses a PHR MAC CE format identified by a MAC PDU subheader with a reserved logical channel ID value. The PHR MAC CE may include a bitmap for each active serving cell indicating which configured UL BWP in the serving cell power headroom information is included in ascending order based on BWP_index.

[0139] In some embodiments, the configured maximum UE transmit power reported within the PH information for the active bandwidth is a BWP-specific maximum UE transmit power (P CMAX ,b,f,c), so that as discussed above, each UL BWP defines P CMAX ,b,f,c Various maximum power reduction terms in the formula (e.g., MPR, A-MPR, P-MPR).

[0140] In some embodiments, for each configured UL BWP of the UL carrier of the serving cell, the configured maximum UE transmit power (P CMAX ) can be the same. Here, P CMAX Defined as the maximum UE transmit power for overall operation on the UL carrier of the serving cell, e.g., the maximum power reduction term (such as MPR, A-MPR, P-MPR) is calculated for non-contiguous allocation of PRBs or resources / channels (e.g., PUSCH, PUCCH) on different active BWPs. In one embodiment, even if multiple power headroom levels (PH c,b ) (e.g., the power headroom level of each active BWP of the UL carrier), the UE 505 may also report only one configured maximum UE transmit power value P per serving cell. CMAX ,f,c.

[0141] In some embodiments, a combined PHR is calculated and / or reported for a serving cell with multiple active UL BWPs. In such embodiments, the combined PHR may be calculated as the difference between the configured UE maximum transmit power of the serving cell and the sum of the estimated powers of UL (e.g., UL-SCH on PUSCH, PUCCH) transmissions on all active UL BWPs of the serving cell. Thus, similar to the carrier aggregation scenario, the UE 505 may report only one PH level and an associated PHR per serving cell. CMAX ,f,c fields (if reported).

[0142] In various embodiments, a transmit power control ("TPC") command linked to a closed-loop index '1' is applied to all active UL BWPs associated with the closed-loop index '1'. In certain embodiments, a group-common TPC command received in a group-common DCI (e.g., DCI format 2_2, 2_3) regarding an active DL BWP includes a BWP index field indicating the UL BWP to which the group-common TPC applies. The group-common TPC command may be associated with a closed-loop index '1'.

[0143] In some embodiments, there is no BWP index field in the group-common DCI, and the UL BWP to which the group-common TPC is applied has the same BWP index as the active DL BWP on which the group-common DCI is received, for example, in the case of TDD. If there is an explicit or implicit link between the DL BWP and the UL BWP (e.g., the UL BWP and DL BWP with the same BWP index are linked), the UL BWP to which the group-common TPC is applied may be determined based on the link to the active DL BWP on which the group-common DCI is received.

[0144] In certain embodiments, in the case of group common TPC operation (e.g., DCI formats 2_2 and 2_3 in NR), the TPC index and CL process index 'l' and / or UL BWP index are semi-statically configured for UE 505 to determine the location of the TPC command in the DCI of UE505 and the associated CL process index 'l' and / or UL BWP index.

[0145] In various embodiments, when the number of active UL BWPs of the serving cell changes, a PHR is triggered at the UE 505. In one example, the RAN node 510 may activate an additional BWP portion in the serving cell, triggering a PHR in response to the BWP activation.

[0146] In some embodiments, when a MAC entity has UL resources for a new transmission, a PHR is triggered in the UE 505 when the phr-ProhibitTimer expires or has expired and the path loss has changed by more than phr-Tx-PowerFactorChange [in dB] for at least one active UL BWP of the serving cell of any MAC entity used as a path loss reference since the last time a PHR was sent in the MAC entity.

[0147] In some embodiments, pathloss change based PHR triggering is allowed only for one or more specific UL BWPs (or corresponding pathloss references). According to this embodiment, a BWP group called allowedPHTriggeringGroup may be configured such that PHR is triggered only for (multiple) UL BWPs belonging to the group (e.g., when dl-PathlossChange [in dB] or phr-Tx-PowerFactorChange is exceeded for one of the members). The allowedPHTriggeringGroup BWP group may be associated with a specific service / parameter set / BWP.

[0148] In certain embodiments, the parameters dl-PathlossChange or phr-Tx-PowerFactorChange for the path loss change based PHR triggering condition may be configured differently for different UL BWPs. For example, the parameters dl-PathlossChange or phr-Tx-PowerFactorChange may be based on the corresponding service / parameter set associated with the UL BWP. In one embodiment, a larger dl-PathlossChange or phr-Tx-PowerFactorChange value may be configured for a BWP to prevent frequent PHR triggering for that BWP. In a related embodiment, the dl-PathlossChange or phr-Tx-PowerFactorChange value of one or more UL BWPs may be set to a very large value (e.g., infinity), thereby essentially disabling path loss based PHR triggering for that / those UL BWPs.

[0149] Figure 6 A network architecture 600 for UE power control for multiple UL carriers according to an embodiment of the present disclosure is depicted. The network architecture 600 includes a UE 605 and a RAN node 610. The UE 605 may be an embodiment of the remote unit 105 described above. The RAN node 610 (e.g., a gNB) may be an embodiment of the base unit 110 described above.

[0150] In the network architecture 600, the UE 605 is configured with a first UL carrier 620 (i.e., UL carrier-1) and a second UL carrier 630 (i.e., UL carrier-2). The UL carriers 620, 630 have multiple time slots. As depicted, the first UL carrier 620 has a first time slot (time slot-0) 621, a second time slot (time slot-1) 622, a third time slot (time slot-2) 623, and a fourth time slot (time slot-3) 624. Similarly, the second UL carrier 630 has a first time slot (time slot-0) 631, a second time slot (time slot-1) 632, a third time slot (time slot-2) 633, and a fourth time slot (time slot-3) 634.

[0151] UE 605 reports, for example, a PHR for time slot -2. In various embodiments, UE 605 reports a virtual PHR 640. Various solutions for selecting which PC parameter set (e.g., associated with the first UL carrier 620 or the second UL carrier 630) to use when calculating the virtual PHR are described below. In the depicted example, the PC parameter set for the first carrier 620 is selected, however, in other embodiments, the PC parameter set for the second carrier 630 may be selected.

[0152] Note that the term "virtual" in relation to the terms "virtual power headroom" and "virtual PHR" refers to its non-standard nature. The "virtual power headroom" is virtual in the sense that the power headroom does not reflect the difference between the maximum transmission power of the component carrier and the actual uplink transmission performed on the non-scheduled uplink component carrier (i.e., the standard characteristic PH), but only assumes a reference uplink transmission that does not actually occur.

[0153] When the UE 605 is configured with two UL carriers for a serving cell (e.g., NUL / SUL operation) and the UE 605 determines a type-1 power headroom report for the serving cell based on a reference PUSCH transmission, the UE 605 calculates the type-1 power headroom report for the serving cell by assuming a reference PUSCH transmission on the UL carrier provided, for example, by the parameter pusch-Config. If the UE 605 is provided with pusch-Config for both UL carriers, the UE 605 calculates the type-1 power headroom report for the serving cell by assuming a reference PUSCH transmission on the UL carrier provided by the parameter pucch-Config. However, if the UE 605 is not provided with pucch-Config for any of the two UL carriers, the UE 605 calculates the type-1 power headroom report for the serving cell by assuming a reference PUSCH transmission on a normal, non-supplementary UL carrier.

[0154] In CA operation, if a serving cell is not scheduled with PUSCH when preparing the PHR, the PUSCH PHR may become virtual for that cell. Since multiple PC parameter sets (e.g., open loop, path loss reference, and closed loop configurations) are possible for UE power control, a reference PC parameter set is necessary for the virtual PUSCH PHR. The reference PC parameters for the virtual PUSCH PHR may be semi-statically selected and configured by the network, or it may be a default / fixed setting in the UE specification. In any case, since the PC parameter set may be configured per UL BWP and UL carrier, it is important for the RAN node 610 to configure / specify which UL carrier and which UL BWP the configuration / default PC parameter set for the virtual PUSCH PHR corresponds to.

[0155] Regarding default settings, consider the following:

[0156] In certain embodiments, if PUSCH and PUCCH transmissions for a serving cell are semi-statically configured to the same UL carrier, then the default PC parameter set for the virtual PUSCH PHR is the PC parameter set corresponding to that UL carrier.

[0157] In some embodiments, if the PHR format in the MAC CE allows only one PHR per serving cell, the default PC parameter set for the virtual PUSCH PHR may be the PC parameter set corresponding to the UL carrier configured for PUCCH transmission. Note that the NUL / SUL carrier position of the PUCCH may be semi-statically configured by higher layers. In some embodiments, the PC parameter set for the virtual PUSCH PHR is always the PC parameter set corresponding to the normal UL (NUL) carrier.

[0158] In certain embodiments, if the PHR format in the MAC CE allows two PHRs per serving cell, i.e., one for each NUL and SUL carrier of the serving cell, then for the virtual PUSCH PHR, the UE 605 uses the following default PC parameter sets: one PC parameter set corresponding to the UL carrier and one PC parameter set corresponding to the SUL carrier. Here, the PUSCH transmission can occur on one or both of the NUL carrier and the SUL carrier. If the PUSCH transmission can only occur on one of the NUL carrier or the SUL carrier, the default PC parameter set for the virtual PUSCH PHR corresponds to the carrier configured with the PUSCH. Similar behavior as described above can also be applied to the virtual PUCCH PHR or the virtual SRS PHR to determine the default PC parameter set.

[0159] In various embodiments, the default PC parameter set for the virtual PUSCH PHR is based on the UL BWP. In a first example, for the virtual PUSCH PHR, the UE 605 uses a PC parameter set corresponding to the initial UL BWP within the UL carrier of the serving cell. For example, the initial UL BWP may be the UL BWP configured for the random access procedure.

[0160] In the second example, for the virtual PUSCH PHR, the UE 605 uses a PC parameter set corresponding to a default UL BWP within the UL carrier of the serving cell. Note that the default BWP is the initial UL BWP or the other half of a statically configured UL BWP. Here, the default UL BWP refers to a UL BWP linked to a default DL BWP, where the UE 605 switches to the default DL BWP when the BWP inactivity timer in a given active DL BWP expires. In some embodiments, there may be an explicit link or an implicit link between the DL BWP and the UL BWP (e.g., a UL BWP and a DL BWP with the same BWP index are linked).

[0161] In a third example, for the virtual PUSCH PHR, the UE 605 uses the PC parameter set corresponding to the latest active UL BWP. This option is beneficial because it is based on the previous actual transmission, but in the case of a missed grant, it is problematic as to which UL BWP is the latest active UL BWP, which may lead to confusion between the RAN node 610 and the UE 605.

[0162] In a fourth example, for the virtual PUSCH PHR, the UE 605 uses a PC parameter set corresponding to a BWP with a predefined bandwidth part index ("BWP_index") within the UL carrier of the serving cell (eg, a BWP with BWP_index=0).

[0163] In a fifth example, for the virtual PUSCH PHR, the UE 605 uses the PC parameter set corresponding to the configured UL BWP associated with the minimum parameter set (eg, minimum subcarrier spacing). If multiple UL BWPs are configured with a minimum parameter set, the UE 605 may select the UL BWP with the smallest BWP_index.

[0164] In a sixth example, for the virtual PUSCH PHR, the UE 605 uses a PC parameter set corresponding to a configured UL BWP that is associated with a default configured MCS / CQI table and / or a configured target-BLER (e.g., that / those for URLLC). If multiple UL BWPs are associated with a default configured MCS / CQI table and / or a configured target-BLER, the UE 605 selects a PC parameter set with a minimum BWP_index.

[0165] In various embodiments, regardless of whether PUSCH Msg3 is sent for initial access or other purposes (such as, radio link reestablishment after RLF, handover, UL synchronization, SR transmission), the DL RS used for path loss estimation follows the SS / PBCH block identified by the UE 605 during the current random access procedure, for example, the SSB used to send Msg1 on the PRACH. Note that the SS / PBCH block identified by the UE 605 during the current random access procedure may be completely different from the SS / PBCH block identified by the UE 605 during the initial random access procedure.

[0166] In addition, as long as the UE 605 has not received a dedicated RRC configuration for path loss estimation for PUSCH / PUCCH, the UE 605 will continue to use the SS / PBCH block identified by the UE 605 during the most recent random access procedure as the DL RS for path loss estimation for PUSCH / PUCCH. In one example, for all PUCCH transmissions without explicit beam indication (e.g., with default / fallback spatial relations), the CL-PC index will be fixed to l=0. Here, for PUCCH without the high-level parameter PUCCH-Spatial-relation-info, the closed-loop index l should also be set to a fixed value, i.e., l=0.

[0167] In one embodiment, for PUSCH Msg3 for a UE in RRC_CONNECTED state, if the UE 605 is configured with more than one PUSCH closed loop procedure, the CL-PC index will be fixed to l = 0. Here, for PUSCH Msg3 and a UE 605 in RRC_CONNECTED state, if the UE 605 is not configured with twoPUSCH-PC-AdjustmentStates or if PUSCH transmission is scheduled by RAR UL grant, the CL-PC index may be fixed to l = 0.

[0168] In one embodiment, for resetting PUSCH / PUCCH closed loop accumulation, if more than one closed loop process is configured for PUSCH / PUCCH, if the closed loop process is reset after receiving a random access response ("RAR") message, the CL accumulation of process l = 0 will be reset. Here, if the UE 605 receives a RAR message in response to a PRACH transmission on an active UL BWPb of carrier f of serving cell c, the CL accumulation of process l = 0 will be reset.

[0169] Furthermore, a combination of the above contents may be used for configurations related to PC and PHR and operating methods for BWP and SUL operations.

[0170] Figure 7 A user equipment device 700 is depicted that can be used for UE power control of multiple UL carriers according to an embodiment of the present disclosure. The user equipment device 700 can be an embodiment of the remote unit 105 described above. In addition, the user equipment device 700 can include a processor 705, a memory 710, an input device 715, an output device 720, and a transceiver 725 for communicating with one or more base units 110.

[0171] As depicted, the transceiver 725 may include a transmitter 730 and a receiver 735. The transceiver 725 may also support one or more network interfaces 740, such as a Uu interface for communicating with a gNB or another suitable interface for communicating with the RAN 120. In various embodiments, the transceiver 725 receives a configuration of a plurality of uplink carriers for a serving cell. In some embodiments, the transceiver 725 receives a configuration of a first number of uplink carriers in the plurality of uplink carriers, the first number of uplink carriers corresponding to a first number of configured and active uplink bandwidth portions of the first number of uplink carriers of the serving cell.

[0172] In some embodiments, input device 715 and output device 720 are combined into a single device, such as a touch screen. In some embodiments, user equipment apparatus 700 may not include any input device 715 and / or output device 720.

[0173] In one embodiment, the processor 705 may include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, the processor 705 may 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 a similar programmable controller. In some embodiments, the processor 705 executes instructions stored in the memory 710 to perform the methods and routines described herein. The processor 705 is communicatively coupled to the memory 710, the input device 715, the output device 720, and the transceiver 725.

[0174] In various embodiments, the processor 705 calculates a total transmit power for UL transmissions on multiple UL carriers, the UL transmissions overlapping in time. The processor 705 may further determine a configured maximum output power, and in response to the UL transmissions having the same priority level, identify a lower priority UL carrier among the multiple UL carriers according to a priority rule. In response to the total transmit power exceeding the configured maximum output power in any portion of the overlapping UL transmissions, in response, the processor 705 calculates a reduced transmit power for the lower priority UL carrier.

[0175] The transceiver 725 performs UL transmission using reduced transmission power. Specifically, the processor 705 may reduce the transmission power by applying a power reduction factor to a lower priority UL carrier and / or abandoning UL transmission of the lower priority UL carrier. Thus, in some embodiments, performing UL transmission using reduced transmission power includes abandoning transmission for the lower priority UL carrier. In some embodiments, the processor 705 reduces the transmission power by applying the same power reduction factor to UL carriers associated with the same priority level.

[0176] In some embodiments, processor 705 identifies the lower priority UL carrier by determining whether PUCCH is configured for any UL carrier of the plurality of UL carriers and prioritizing power allocation for UL carriers configured with PUCCH over UL carriers not configured with PUCCH.

[0177] In some embodiments, the processor 705 identifies the lower priority UL carrier by one or more of the following operations: identifying a parameter set for each UL carrier in a plurality of UL carriers; identifying a service type or a traffic type associated with each UL carrier in a plurality of UL carriers; identifying one or more of the following for each UL carrier in a plurality of UL carriers: a modulation and coding scheme table, a channel quality indicator table, and a target reliability requirement; and identifying an index associated with each UL carrier in a plurality of UL carriers.

[0178] In some embodiments, the plurality of UL carriers include a SUL carrier and a NUL carrier. Here, the processor 705 may identify the lower priority UL carrier by prioritizing power allocation for the NUL carrier over the SUL carrier. As mentioned above, receiving the configuration of the plurality of UL carriers of the serving cell may include receiving the configuration of a first number of uplink carriers in the plurality of uplink carriers, the first number of uplink carriers corresponding to a first number of configured and active uplink bandwidth portions of the first UL carrier of the serving cell.

[0179] In some embodiments, the transceiver 725 receives a configuration of a first number of uplink carriers among a plurality of uplink carriers, the first number of uplink carriers corresponding to a first number of active bandwidth portions of a serving cell, and the processor 705 identifies a lower priority uplink carrier by identifying a lower priority active uplink BWP among the first number of active uplink bandwidth portions according to one or more of the following operations: identifying a parameter set for each active uplink bandwidth portion among the first number of active uplink bandwidth portions; identifying a service type or traffic type associated with each active uplink bandwidth portion among the first number of active uplink bandwidth portions; identifying one or more of the following for each active uplink bandwidth portion among the first number of active uplink bandwidth portions: a modulation and coding scheme table, a channel quality indicator table, and a target reliability requirement; and identifying an index associated with each active uplink bandwidth portion among the first number of active uplink bandwidth portions.

[0180] In various embodiments, the processor 705 calculates the PH of each uplink carrier in the plurality of uplink carriers on the serving cell. The processor 705 may then control the transceiver 725 to send a PHR based on the calculated PH of the plurality of UL carriers for the serving cell.

[0181] In some embodiments, the processor 705 determines a configured maximum output power of a UL carrier from a plurality of UL carriers of a serving cell. In such embodiments, the PH of a UL carrier from a plurality of UL carriers on the serving cell indicates a difference between the configured maximum output power of the UL carrier and the determined transmit power required for UL transmission on the UL carrier.

[0182] In some embodiments, the processor 705 determines a default power control parameter set for the serving cell. In such an embodiment, the PHR may include a single PH. In one embodiment, the PHR also includes a corresponding configured maximum output power. Further, the processor 705 may calculate the PH by calculating a virtual PH in response to the absence of UL transmissions within a reporting period on any UL carrier of a plurality of UL carriers from the serving cell when preparing the PHR. Here, the virtual PH may be based on the default power control parameter set.

[0183] In some embodiments, the default power control parameter set includes one or more of the following: an open-loop parameter set (or set index), a closed-loop process (or process index), and a path loss RS (or RS index). In some embodiments, the default power control parameter set corresponds to a UL carrier on which the PUCCH is semi-statically configured.

[0184] In some embodiments, only a first UL carrier of the plurality of UL carriers is semi-statically configured for PUSCH, wherein the default power control parameter set corresponds to the first UL carrier. In some embodiments, the default power control parameter set corresponds to a UL carrier having a CIF index of zero. In some embodiments, the plurality of UL carriers include a SUL carrier and a NUL carrier, wherein the default power control parameter set corresponds to the NUL carrier.

[0185] In various embodiments, the PHR corresponds to one or more of: PUSCH PHR, PUCCH PHR, and SRSPHR.

[0186] In some embodiments, the transceiver 725 receives a configuration of a first number of uplink carriers among a plurality of uplink carriers, the first number of uplink carriers corresponding to a first number of configured and active uplink bandwidth portions of a serving cell. In such embodiments, the processor 705 may determine a default set of power control parameters for the serving cell. Here, the PHR includes a single PH. In addition, the processor 705 may calculate the PH by calculating a virtual PH in response to the absence of UL transmissions on any active BWP of the first number of active uplink bandwidth portions from the serving cell when preparing the PHR, wherein the virtual PH is based on the default set of power control parameters.

[0187] In some embodiments, the default power control parameter set corresponds to one of: an active UL BWP, an initial UL BWP, and a default UL BWP, wherein the default UL BWP is a UL BWP linked to a default DL BWP. In some embodiments, the default power control parameter set corresponds to one of: a UL BWP with a minimum BWP index, a UL BWP with a minimum parameter set, a UL BWP associated with a service type or a traffic type, and a UL BWP associated with a modulation and coding scheme table, a UL BWP associated with a channel quality indicator table, a UL BWP associated with a target reliability requirement, or a combination thereof.

[0188] In some embodiments, the PHR includes a plurality of PH fields, wherein the PH field includes one or more of a PH, a configured maximum output power, and a UL BWP index. In some embodiments, the configured maximum output power of the UL BWP may be determined based on a power reduction factor, wherein the power reduction factor for a first UL BWP is different from the power reduction factor for a second UL BWP, wherein the first UL BWP and the second UL BWP are different.

[0189] In some embodiments, the configured maximum output power of the UL BWP may be determined based on a power reduction factor, wherein the power reduction factor for a first UL BWP is the same as the power reduction factor for a second UL BWP, wherein the first UL BWP and the second UL BWP are different. In some embodiments, the configured maximum output power of the UL BWP may be determined based on a maximum allowed UE output power (“P EMAX ”) to determine the configured maximum output power of the UL BWP, wherein the first UL BWP has a first P EMAX , and the second UL BWP has a second P EMAX , where the first P EMAX Is with the second P EMAX Different values, and the first UL BWP and the second UL BWP are different.

[0190] In certain embodiments, in response to a first active UL BWP and a second active UL BWP having different configured maximum output powers, the PHR includes a first PH of the first active UL BWP and a second PH of the second active UL BWP, wherein the first active UL BWP is different from the second active UL BWP.

[0191] In certain embodiments, the PHR includes a first PH of the first active UL BWP and a second PH of the second active UL BWP in response to the first active UL BWP and the second active UL BWP being associated with one or more of: different configured maximum output powers, different path loss references, and non-quasi-co-located path loss references, wherein the first active UL BWP is different from the second active UL BWP.

[0192] In some embodiments, the processor 705 calculates a differential PH, the differential PH being a difference between a PH of the second active UL BWP and a PH of the first active UL BWP, wherein the first active UL BWP is different from the second active UL BWP. In such embodiments, the PHR may include a PH of the first active UL BWP and a differential PH of the second active UL BWP in response to the first active UL BWP and the second active UL BWP having one of: the same configured maximum output power, the same path loss reference, and a quasi-co-located path loss reference.

[0193] In certain embodiments, in response to a first active UL BWP and a second active UL BWP having the same configured maximum output power, the same path loss reference, or a quasi-co-located path loss reference, the PHR includes a PH of the first active UL BWP and the second active UL BWP. Here, the first active UL BWP is different from the second active UL BWP. In such embodiments, the PH is calculated for the first UL BWP.

[0194] In some embodiments, the PHR includes PHs of a first active UL BWP and a second active UL BWP. Here, the PH may be calculated as the difference between the configured UE maximum transmit power of the serving cell and the sum of the transmit powers for uplink transmissions on the first active UL BWP and the second UL BWP. In such embodiments, the transmit power for uplink transmissions may include a first transmit power for a first uplink transmission on the first active UL BWP and a second transmit power for a second uplink transmission on the second active UL BWP.

[0195] In some embodiments, the transceiver 725 receives a configuration for a power headroom BWP group. In one embodiment, receiving a configuration for a PH BWP group includes receiving an "allowedPHTriggeringGroup" parameter. Here, the processor 705 detects that the MAC entity has UL resources for a new transmission and determines whether a PHR backoff timer has expired (e.g., phr-ProhibitTimer).

[0196] In such an embodiment, in response to the expiration of the PHR backoff timer and in response to the path loss having changed by more than a threshold amount for at least one active BWP of the PH BWP group belonging to the serving cell (e.g., of any MAC entity used as a path loss reference) since the last transmission of the PHR in the MAC entity, the processor 705 may trigger the PHR. In some embodiments, the threshold amount is indicated by the parameter 'phr-Tx-PowerFactorChange'.

[0197] In some embodiments, the transceiver 725 receives a BWP-specific configuration for a path loss change threshold parameter (eg, 'dl-PathlossChange' parameter).Here, the processor 705 detects that the MAC entity has UL resources for a new transmission and determines whether a PHR backoff timer expires (eg, phr-ProhibitTimer).

[0198] In such an embodiment, in response to the expiration of the PHR backoff timer and in response to the path loss having changed by more than a threshold amount for at least one active UL BWP belonging to a serving cell (e.g., of any MAC entity used as a path loss reference), the processor 705 may trigger a PHR. Here, the threshold amount is configured for at least one active UL BWP. In some embodiments, the threshold amount is indicated by a parameter 'dl-PathlossChange'. In other embodiments, the threshold amount may be indicated by a parameter 'phr-Tx-PowerFactorChange'.

[0199] In some embodiments, the processor 705 communicates on a first active UL BWP in a serving cell configured with multiple UL BWPs, and the processor 705 switches from the first active UL BWP to a second active UL BWP. Here, the first active UL BWP and the second active UL BWP share a CL-PC process. In addition, the processor 705 selectively resets the CL-PC process in response to switching the BWP.

[0200] In some embodiments, selectively resetting the CL-PC process includes resetting the CL-PC process in response to a frequency distance between the first BWP and the second BWP being greater than a threshold, and continuing the CL-PC process in response to the frequency distance being not greater than the threshold.

[0201] In some embodiments, selectively resetting the CL-PC process includes: determining a path loss reference for the first BWP and the second BWP. The processor 705 continues the CL-PC process in response to the path loss reference being the same value for the first BWP and the second BWP or having a quasi-co-located relationship for the first BWP and the second BWP, and resets the CL-PC process in response to the path loss reference not being the same value for the first BWP and the second BWP and not having a quasi-co-located relationship for the first BWP and the second BWP.

[0202] In some embodiments, selectively resetting the CL-PC process includes: determining a quality parameter set for the first BWP and the second BWP, the quality parameter set including: an open-loop power control parameter set, a (e.g., configured) modulation and coding scheme table, a (e.g., configured) channel quality indicator table, a (e.g., configured) target reliability requirement, an associated service type or traffic type, and an associated parameter set. Here, the processor 705 resets the CL-PC process in response to the quality parameter set not being the same value for the first BWP and the second BWP.

[0203] In various embodiments, the processor 705 controls the transceiver 725 to perform a random access procedure. Here, performing the random access procedure includes sending PUSCH Msg3. PUSCH Msg3 may be a third message of the random access procedure. The processor 705 determines whether the user equipment device 700 is in the RRC_CONNECTED state and identifies the number of configured CL-PC processes for UL channels or signals. In response to the user equipment device 700 being in the RRC_CONNECTED state and the number of configured CL-PC processes for UL channels or signals exceeding one, the processor 705 calculates the transmit power for PUSCH Msg3 using the CL-PC process with an index of zero.

[0204] In some embodiments, the processor 705 determines whether the PUCCH transmission lacks an explicit beam indication, and uses the CL-PC process with an index of zero to calculate the transmit power for PUSCH Msg3 in response to the PUCCH transmission lacking an explicit beam indication. In some embodiments, the transceiver 725 receives a RAR when performing a random access procedure, and the processor 705 resets the CL-PC accumulation of the CL-PC process with an index of zero in response to receiving the RAR. In various embodiments, PUSCH Msg3 is sent in response to receiving a RAR (also referred to as Msg2) during the random access procedure.

[0205] In some embodiments, the processor 705 determines a power control parameter based on one or more active uplink bandwidth parts (UL BWPs) of the UL carrier f of the serving cell c. The processor 705 also determines the configured maximum output power of the active UL BWP of the UL carrier f of the serving cell c, and determines at least one transmit power value based on the power control parameter and the configured maximum output power. In various embodiments, the processor 705 controls the transceiver 725 to perform uplink transmission on the one or more active UL BWPs using the determined transmit power value(s).

[0206] In some embodiments, the configured maximum output power P on the UL BWP b of the UL carrier f of the serving cell c is CMAX ,b,f,c depend on the power reduction terms (including MPR, A-MPR, P-MPR, ΔT C ), these power reduction terms depend on the ULBWP. In some embodiments, the configured maximum output power P on the UL BWP b of the UL carrier f of the serving cell c is CMAX ,f,c depends on the power reduction terms (including MPR, A-MPR, P-MPR, ΔT C ), these power reduction terms are calculated over all configured UL BWPs of UL carrier f of the serving cell.

[0207] In some embodiments, the configured maximum output power P on the UL BWP b of the UL carrier f of the serving cell c is CMAX ,b,f,c depends on the maximum allowed UE output power (P EMAX ), that is, P EMAX ,b,f,c.

[0208] In some embodiments, the power control parameters include one or more of an open-loop parameter (such as Po, α) (indicated by index j), a TPC closed-loop process index (l), and a path loss reference signal ("RS") index (q). In such an embodiment, the number of different path loss RSs maintained by the UE may depend on at least one of: the number of configured UL BWPs, the frequency band of the configured UL BWPs, and the number of active UL BWPs. In addition, the number of different TPC closed-loop processes maintained by the UE may depend on at least one of: the number of configured UL BWPs, the parameter set associated with the configured UL BWPs, and the number of active UL BWPs.

[0209] In various embodiments, the TPC closed-loop process is shared between multiple configured UL BWPs. In such embodiments, the processor 705 may further compare the frequency position and the distance / separation between the first UL BWP and the second UL BWP, compare the open-loop power control parameters (P0 and Alpha) associated with the first UL BWP and the second UL BWP, compare the spatial quasi-colocation (QCL) relationship between the path loss reference signals associated with the first UL BWP and the second UL BWP, compare the parameter sets (subcarrier spacing in OFDM operation) and services (traffic types) associated with the first UL BWP and the second UL BWP, compare the configured MCS table and / or CQI table and / or target reliability (indicated by BLER requirements) associated with the first UL BWP and the second UL BWP, and determine whether to reset or continue the cumulative TPC closed-loop process shared by the first UL BWP and the second UL BWP when the active UL BWP switches from the first UL BWP to the second UL BWP based on at least one of these comparisons.

[0210] In some embodiments, the processor 705 calculates the total transmit power over all uplink transmissions on all active UL BPWs of all uplink carriers of all active serving cells (uplink transmissions overlap in time), and if the total transmit power in any part of the overlapping transmissions exceeds the configured maximum output power, determines a power reduction factor or decides to abandon the transmission according to a priority rule. Here, when signals / channels on different active UL BWPs have the same priority level, the priority rules for power scaling and transmission abandonment depend on at least one of the following: the parameter set (subcarrier spacing in OFDM operation) and service (traffic type) associated with the active BWP, the configured MCS table and / or CQI table and / or target reliability (indicated by the BLER requirement) associated with the active UL BWP.

[0211] In addition, the same power scaling may be applied to a set of overlapping uplink transmissions on a set of active UL BWPs that are associated with the same parameter set, service, and configured MCS / CQI table and target reliability, and that include signals / channels of the same priority level, except perhaps for some uplink transmissions dropped in the set. Here, when the signals / channels on the first UL carrier and the second UL carrier have the same priority level, the priority rules for power scaling and transmission dropping are such that the UL carrier on which the PUCCH is semi-statically configured has a higher priority than the other UL carrier.

[0212] In various embodiments, the processor 705 reports a power headroom report (PHR) for UL transmissions on the active UL BWP of the serving cell. Here, the PHR may include the PH of the active UL BWP (the difference between the configured maximum output power and the determined transmit power required for UL transmission) and the configured maximum output power [P CMAX ,b,f,c(i)]. In one such embodiment, a separate PHR may be reported for each active UL BWP. In another such embodiment, a PHR may not be reported for a second active UL BWP associated with the same path loss RS or spatial QCL path loss RS that is also associated with the first UL BWP, but a PHR may be reported for the first active BWP.

[0213] In addition, the processor 705 may report an absolute PH of a first active UL BWP, and report a differential PH of (multiple) second active UL BWPs, the absolute PH being the difference between the configured maximum output power and the determined transmit power required for transmission of the first active UL BWP, and the differential PH being the difference between the PH of the second active UL BWP and the PH of the first UL BWP. Here, reporting differential PHR may be enabled and disabled by a network entity based on higher layer signaling or signaling received in a DCI.

[0214] Further, the processor 705 may form a BWP group as a set of active UL BWPs and report the absolute PH of the first active UL BWP in the BWP group and the differential PH of all other active UL BWPs in the BWP group. In such an embodiment, the BWP group may be the entire set or a strict subset of all active UL BWPs on the serving cell. In a further embodiment, the BWP group may be a set of BWPs sharing the same configured maximum output power [P CMAX ,b,f,c] or the set of all active UL BWPs sharing the same path loss RS or different but spatial QCL path loss RS.

[0215] In various embodiments of the above embodiments, the processor 705 may determine a default power control parameter set for the serving cell, calculate (and report) a PHR (e.g., report a virtual PHR) when there is no UL transmission on the serving cell. In various embodiments, the default power control parameter set may correspond to: an initial UL BWP configured for a random access procedure; a default UL BWP linked to a default DL BWP; the latest active UL BWP; a UL BWP with a BWP-index equal to 0; a UL BWP with a minimum BWP index associated with a minimum parameter set (e.g., a subcarrier spacing in OFDM operation); a UL BWP with a minimum BWP index associated with a default configured MCS / CSI table and / or a target reliability requirement; a UL carrier on which a PUCCH is semi-statically configured; or a UL carrier with a CIF (carrier indicator field) index of zero.

[0216] In some embodiments, the user equipment device 700 is configured with at least one uplink bandwidth portion of a serving cell. In such an embodiment, the processor 705 may report power headroom information by determining power headroom information for each configured and active uplink bandwidth portion at the mobile terminal. Here, the power headroom information may include a power headroom level for the uplink bandwidth portion and a configured maximum transmit power for calculating the power headroom level, including power headroom information for each configured and active uplink bandwidth portion of the serving cell. The processor 705 prepares the power headroom information within a signaling message and controls the transceiver 725 to send the signaling message to the network node.

[0217] In some embodiments, the signaling message is sent using medium access control ("MAC") control signaling. In other embodiments, the power headroom information includes a bitmap indicating which configured uplink bandwidth portion of the serving cell power headroom information is included. In some embodiments, the configured maximum UE transmit power of the uplink bandwidth portion of the serving cell is determined by taking into account a power reduction factor defined for the uplink bandwidth portion.

[0218] In some embodiments, the power headroom information includes a power headroom level and a configured maximum transmit power used to calculate the power headroom level. In such an embodiment, the processor 705 may include the power headroom information for each of the configured and active uplink bandwidth parts of the serving cell in a signaling message and send the control signaling message to the network node. In certain embodiments, the power headroom level of the serving cell is calculated as the difference between the configured UE maximum transmit power of the serving cell and the sum of the estimated powers of uplink transmissions on at least one configured uplink bandwidth part of the serving cell.

[0219] In various embodiments, the processor 705 receives a configuration for a BWP group (e.g., allowedPHTriggeringGroup) and, when the MAC entity has UL resources for a new transmission, triggers a PHR if the phr-ProhibitTimer expires or has expired and if the path loss has changed since the last transmission of a PHR in the MAC entity by more than a threshold amount (e.g., indicated by parameter phr-Tx-PowerFactorChange) for at least one active BWP of the (allowedPHTriggeringGroup) BWP group for a serving cell belonging to any MAC entity used as a path loss reference.

[0220] In various embodiments, the processor 705 receives a configuration for path loss change threshold parameters (e.g., dl-PathlossChange and / or), and when a MAC entity has UL resources for a new transmission, triggers a PHR if the phr-ProhibitTimer expires or has expired and the path loss has changed by more than a threshold amount (e.g., indicated by parameter dl-PathlossChange or parameter phr-Tx-PowerFactorChange) for at least one active BWP of a serving cell belonging to any MAC entity used as a path loss reference since the last transmission of a PHR in the MAC entity. Here, the threshold amount (e.g., dl-PathlossChange and / or phr-Tx-PowerFactorChange) is configured for at least one UL BWP.

[0221] In various embodiments, the processor 705 receives a UE-specific configuration of one or more MCS tables and / or CQI tables and / or target reliability requirements. In such embodiments, the processor 705 performs a first uplink transmission corresponding to the following: a signal / channel, a first MCS table and / or CQI table and / or target reliability requirement, a first transmit power associated with a path loss reference and a closed-loop process index. In addition, the processor 705 may receive an indication of a second MCS table and / or CQI table and / or target reliability requirement different from the first MCS table and / or CQI table and / or target reliability requirement, and reset the closed-loop process associated with the closed-loop process index. In addition, the processor 705 may control the transceiver 725 to perform a second uplink transmission corresponding to the following: the same signal / channel, a second MCS table and / or CQI table and / or target reliability requirement, a second transmit power associated with the same path loss reference and the same closed-loop process index.

[0222] In certain embodiments, indications of (multiple) MCS tables and / or (multiple) CQI tables and / or target reliability requirements may be received via UL grant DCI based on a granted PUSCH, via RRC signaling of a PUCCH or corresponding DL allocation DCI, and via RRC signaling of a PUSCH based on a configured grant.

[0223] In one embodiment, the memory 710 is a computer-readable storage medium. In some embodiments, the memory 710 includes a volatile computer storage medium. For example, the memory 710 may include a RAM, including: a dynamic RAM ("DRAM"), a synchronous dynamic RAM ("SDRAM"), and / or a static RAM ("SRAM"). In some embodiments, the memory 710 includes a non-volatile computer storage medium. For example, the memory 710 may include a hard drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 710 includes both a volatile computer storage medium and a non-volatile computer storage medium.

[0224] In some embodiments, the memory 710 stores data related to UE power control for multiple UL carriers. For example, the memory 710 can store indexes, power control parameters, power headroom, configuration and activation / deactivation status for serving cells and / or BWPs, etc. In some embodiments, the memory 710 also stores program code and related data, such as an operating system or other controller algorithms for operating the remote unit 105.

[0225] In one embodiment, input device 715 may include any known computer input device, including: touch panel, button, keyboard, stylus, microphone, etc. In some embodiments, input device 715 may be integrated with output device 720, for example, as a touch screen or similar touch-sensitive display. In some embodiments, input device 715 includes a touch screen, so that text can be input using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. In some embodiments, input device 715 includes two or more different devices, such as a keyboard and a touch panel.

[0226] In one embodiment, the output device 720 is designed to output visual signals, auditory signals and / or tactile signals. In some embodiments, the output device 720 includes an electronically controllable display or display device capable of outputting visual data to a user. For example, the output device 720 may include, but is not limited to: an LCD display, an LED display, an OLED display, a projector, or a similar display device capable of outputting images, text, etc. to a user. As another non-limiting example, the output device 720 may include a wearable display that is separate from the rest of the user device apparatus 700 but communicatively coupled to the rest, such as a smart watch, smart glasses, a head-up display, etc. Further, the output device 720 may be a component of a smart phone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

[0227] In certain embodiments, output device 720 includes one or more speakers for producing sound. For example, output device 720 can produce audible alarm or notification (for example, beep or ring). In certain embodiments, output device 720 includes one or more tactile devices for producing vibration, motion or other tactile feedback. In certain embodiments, all or part of output device 720 can be integrated with input device 715. For example, input device 715 and output device 720 can form touch screen or similar touch-sensitive display. In other embodiments, output device 720 can be located near input device 715.

[0228] The transceiver 725 includes at least one transmitter 730 and at least one receiver 735. One or more transmitters 730 can be used to provide UL communication signals to the base unit 110. Similarly, as described herein, one or more receivers 735 can be used to receive DL communication signals from the base unit 110. Although only one transmitter 730 and one receiver 735 are shown, the user equipment device 700 can have any suitable number of transmitters 730 and receivers 735. Further, the (multiple) transmitters 730 and (multiple) receivers 735 can be any suitable type of transmitters and receivers. In one embodiment, the transceiver 725 includes a first transmitter / receiver pair for communicating with a mobile communication network on a licensed radio spectrum and a second transmitter / receiver pair for communicating with a mobile communication network on an unlicensed radio spectrum.

[0229] Figure 88 is a schematic flow chart illustrating one embodiment of a method 800 for UE power control for multiple UL carriers according to an embodiment of the present disclosure. In some embodiments, the method 800 is performed by a UE, such as a remote unit 105, UE 205, UE 405, UE 505, UE 605, and / or user equipment device 700. In certain embodiments, the method 800 may be performed by a processor executing program code, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0230] The method 800 starts and receives 805 a configuration of multiple uplink carriers for a serving cell. The method 800 includes calculating 810 a total transmit power for uplink transmissions on the multiple uplink carriers, the uplink transmissions overlapping in time.

[0231] The method 800 includes determining 815 a configured maximum output power. The method 800 includes identifying 820 a lower priority uplink carrier among a plurality of uplink carriers according to a priority rule in response to the uplink transmissions having the same priority level.

[0232] The method 800 includes, in response to the total transmit power exceeding the configured maximum output power in any portion of the overlapping uplink transmissions, reducing 825 the transmit power for the lower priority uplink carrier. The method 800 includes performing 830 the uplink transmission using the reduced transmit power. The method 800 ends.

[0233] Fig. 9 is a schematic flow chart illustrating one embodiment of a method 900 for UE power control for multiple UL carriers according to an embodiment of the present disclosure. In some embodiments, the method 900 is performed by a UE, such as a remote unit 105, UE 205, UE 405, UE 505, UE 605, and / or user equipment device 700. In certain embodiments, the method 900 may be performed by a processor executing program code, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0234] The method 900 starts and receives 905 a configuration of a plurality of uplink carriers for a serving cell. The method 900 includes calculating 910 a power headroom ("PH") for each of the plurality of uplink carriers on the serving cell. The method 900 includes sending 915 a power headroom report ("PHR") based on the calculated PH for the plurality of uplink carriers for the serving cell. The method 900 ends.

[0235] Fig.101 is a schematic flow chart illustrating one embodiment of a method 1000 for UE power control for multiple UL carriers according to an embodiment of the present disclosure. In some embodiments, the method 1000 is performed by a UE, such as a remote unit 105, UE 205, UE 405, UE 505, UE 605, and / or user equipment device 700. In certain embodiments, the method 1000 may be performed by a processor executing program code, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0236] The method 1000 starts and performs 1005 a random access procedure, wherein performing the random access procedure includes sending a physical uplink shared channel ("PUSCH") Msg3. The method 1000 includes determining 1010 whether the UE is in an RRC_CONNECTED state. The method 1000 includes identifying 1015 a number of configured closed loop power control ("CL-PC") processes for an uplink ("UL") channel or signal.

[0237] The method includes: in response to the UE being in RRC_CONNECTED state and the number of configured CL-PC processes for UL channels or signals exceeds one, calculating 1020 a transmit power for PUSCH Msg3 using a CL-PC process with an index of zero. The method 1000 ends.

[0238] A first device for UE power control of multiple UL carriers is disclosed herein. In various embodiments, the first device may be a UE, such as a remote unit 105, a UE 205, a UE 405, a UE 505, a UE 605, and / or a user equipment device 700. The first device includes a transceiver that receives a configuration of multiple uplink carriers for a serving cell. The first device includes a processor that calculates a total transmit power for uplink transmissions on multiple uplink carriers, the uplink transmissions overlapping in time. The processor determines the configured maximum output power, and in response to the uplink transmissions having the same priority level, identifies a lower priority uplink carrier among the multiple uplink carriers according to a priority rule. In response to the total transmit power exceeding the configured maximum output power in any portion of the overlapping uplink transmissions, the processor calculates a reduced transmit power for the lower priority uplink carrier. The transceiver performs uplink transmissions using the reduced transmit power.

[0239] In various embodiments, reducing the transmission power comprises at least one of: applying a power reduction factor to a lower priority uplink carrier; and abandoning uplink transmissions of the lower priority uplink carrier. In some embodiments, reducing the transmission power comprises: applying the same power reduction factor to uplink carriers associated with the same priority level.

[0240] In some embodiments, identifying a lower priority uplink carrier among the plurality of uplink carriers according to the priority rule comprises: the processor determining whether a PUCCH is configured for any uplink carrier among the plurality of uplink carriers, and prioritizing power allocation for uplink carriers configured with the PUCCH over uplink carriers not configured with the PUCCH.

[0241] In some embodiments, the plurality of uplink carriers include a SUL carrier and a NUL carrier. In such embodiments, identifying a lower priority uplink carrier among the plurality of uplink carriers according to the priority rule may include the processor prioritizing power allocation for the NUL carrier over the SUL carrier. In some embodiments, the SUL carrier and the NUL carrier are not configured with a PUCCH.

[0242] In various embodiments, identifying a lower priority uplink carrier among the plurality of uplink carriers according to the priority rule comprises: identifying a parameter set for each of the plurality of uplink carriers; identifying a service type or traffic type associated with each of the plurality of uplink carriers; identifying one or more of the following for each of the plurality of uplink carriers: a modulation and coding scheme table, a channel quality indicator table, and a target reliability requirement; and identifying an index associated with each of the plurality of uplink carriers.

[0243] In some embodiments, the transceiver receives a configuration of a first number of uplink carriers in a plurality of uplink carriers, the first number of uplink carriers corresponding to a first number of configured and active uplink bandwidth portions of the serving cell. In such embodiments, reducing the transmission power comprises applying a same power reduction factor to active uplink bandwidth portions associated with the same priority level.

[0244] In some embodiments, a transceiver receives a configuration of a first number of uplink carriers among a plurality of uplink carriers, the first number of uplink carriers corresponding to a first number of active bandwidth portions of a serving cell, and a processor identifies a lower priority uplink carrier by identifying a lower priority active uplink BWP among the first number of active uplink bandwidth portions according to one or more of the following operations: identifying a parameter set for each of the first number of active uplink bandwidth portions; identifying a service type or traffic type associated with each of the first number of active uplink bandwidth portions; identifying one or more of the following for each of the first number of active uplink bandwidth portions: a modulation and coding scheme table, a channel quality indicator table, and a target reliability requirement; and identifying an index associated with each of the first number of active uplink bandwidth portions.

[0245] A first method for UE power control of multiple UL carriers is disclosed herein. In various embodiments, the first method is performed by a UE, such as a remote unit 105, a UE 205, a UE 405, a UE 505, a UE 605, and / or a user equipment device 700. The first method includes: receiving a configuration of multiple uplink carriers for a serving cell; and calculating a total transmit power for uplink transmissions on the multiple uplink carriers, the uplink transmissions overlapping in time. The first method includes: determining a configured maximum output power; and in response to the uplink transmissions having the same priority level, identifying a lower priority uplink carrier among the multiple uplink carriers according to a priority rule. The first method includes: in response to the total transmit power exceeding the configured maximum output power in any portion of the overlapping uplink transmissions, reducing the transmission power for the lower priority uplink carrier; and performing the uplink transmission using the reduced transmission power.

[0246] In various embodiments of the first method, reducing the transmission power includes at least one of the following operations: applying a power reduction factor to a lower priority uplink carrier; and abandoning uplink transmission of the lower priority uplink carrier. In some embodiments of the first method, reducing the transmission power includes: applying the same power reduction factor to uplink carriers associated with the same priority level.

[0247] In some embodiments of the first method, identifying a lower priority uplink carrier among the multiple uplink carriers according to the priority rule includes: determining whether PUCCH is configured for any uplink carrier among the multiple uplink carriers, and prioritizing power allocation for uplink carriers configured with PUCCH over uplink carriers not configured with PUCCH.

[0248] In some embodiments, the plurality of uplink carriers include a SUL carrier and a NUL carrier. In such embodiments, identifying a lower priority uplink carrier among the plurality of uplink carriers according to the priority rule includes prioritizing power allocation for the NUL carrier over the SUL carrier. In some embodiments, the SUL carrier and the NUL carrier are not configured with a PUCCH.

[0249] In various embodiments, identifying a lower priority uplink carrier among the plurality of uplink carriers according to the priority rule comprises: identifying a parameter set for each of the plurality of uplink carriers; identifying a service type or traffic type associated with each of the plurality of uplink carriers; and / or identifying one or more of the following for each of the plurality of uplink carriers: a table of modulation and coding schemes, a table of channel quality indicators, and a target reliability requirement.

[0250] In some embodiments, receiving a configuration of a plurality of uplink carriers for the serving cell comprises: receiving a configuration of a first number of uplink carriers in the plurality of uplink carriers, the first number of uplink carriers corresponding to a first number of configured and active uplink bandwidth portions of a first uplink carrier of the serving cell. In some embodiments, reducing the transmission power comprises: applying the same power reduction factor to uplink carriers associated with the same priority level.

[0251] In some embodiments, receiving a configuration of a plurality of uplink carriers for a serving cell includes: receiving a configuration of a first number of uplink carriers in the plurality of uplink carriers, the first number of uplink carriers corresponding to a first number of active bandwidth portions of the serving cell. In such embodiments, identifying a lower priority uplink carrier in the plurality of uplink carriers may include: identifying a lower priority active uplink BWP in the first number of active uplink bandwidth portions according to one or more of the following operations: identifying a parameter set for each of the first number of active uplink bandwidth portions; identifying a service type or traffic type associated with each of the first number of active uplink bandwidth portions; identifying one or more of the following for each of the first number of active uplink bandwidth portions: a modulation and coding scheme table, a channel quality indicator table, and a target reliability requirement; and identifying an index associated with each of the first number of active uplink bandwidth portions.

[0252] A second apparatus for UE power control of multiple UL carriers is disclosed herein. In various embodiments, the second apparatus may be a UE, such as a remote unit 105, a UE 205, a UE 405, a UE 505, a UE 605, and / or a user equipment device 700. The second apparatus includes a transceiver that receives a configuration of multiple uplink carriers for a serving cell. The second apparatus includes a processor that calculates a PH for each of the multiple uplink carriers on the serving cell. The second apparatus controls the transceiver to send a PHR based on the calculated PH for the multiple uplink carriers of the serving cell.

[0253] In some embodiments, the processor determines a configured maximum output power of an uplink carrier from a plurality of uplink carriers in a serving cell. In such embodiments, a PH of an uplink carrier from a plurality of uplink carriers on the serving cell indicates a difference between the configured maximum output power of the uplink carrier and a determined transmit power required for UL transmission on the uplink carrier.

[0254] In some embodiments, the processor determines a default power control parameter set for the serving cell. In such an embodiment, the PHR may include a single PH. Further, calculating the PH may include: calculating a virtual PH in response to the absence of UL transmission on any uplink carrier of a plurality of uplink carriers from the serving cell when calculating the PHR. Here, the virtual PH may be based on the default power control parameter set.

[0255] In some embodiments, the default power control parameter set includes one or more of an open loop parameter set, a closed loop process, and a path loss RS. In some embodiments, the default power control parameter set corresponds to a UL carrier on which the PUCCH is semi-statically configured.

[0256] In some embodiments, only a first uplink carrier of the plurality of uplink carriers is semi-statically configured for PUSCH, wherein the default power control parameter set corresponds to the first UL carrier. In some embodiments, the default power control parameter set corresponds to a UL carrier having a CIF index of zero. In some embodiments, the plurality of uplink carriers include a SUL carrier and a NUL carrier, wherein the default power control parameter set corresponds to the NUL carrier.

[0257] In various embodiments, the PHR corresponds to one or more of: PUSCH PHR, PUCCH PHR, and SRSPHR.

[0258] In some embodiments, the transceiver receives a configuration of a first number of uplink carriers from a plurality of uplink carriers, the first number of uplink carriers corresponding to a first number of configured and active uplink bandwidth portions of a serving cell. In such embodiments, the processor may determine a default set of power control parameters for the serving cell. Here, the PHR includes a single PH. In addition, the processor may calculate the PH by calculating a virtual PH in response to the absence of UL transmissions on any active BWPs from the first number of active uplink bandwidth portions of the serving cell when preparing the PHR, wherein the virtual PH is based on the default set of power control parameters.

[0259] In some embodiments, the default power control parameter set corresponds to an active UL BWP. In some embodiments, the default power control parameter set corresponds to one of: an initial UL BWP and a default UL BWP, wherein the default UL BWP is a UL BWP linked to a default DL BWP. In some embodiments, the default power control parameter set corresponds to one of: a UL BWP with a minimum BWP index, a UL BWP with a minimum parameter set, a UL BWP associated with a service type or traffic type, and a UL BWP associated with a modulation and coding scheme table, a UL BWP associated with a channel quality indicator table, a UL BWP associated with a target reliability requirement, or a combination thereof.

[0260] In some embodiments, the PHR includes a plurality of PH fields, wherein the PH field includes one or more of a PH, a configured maximum output power, and a UL BWP index. In some embodiments, the configured maximum output power of the UL BWP may be determined based on a power reduction factor, wherein the power reduction factor for a first UL BWP is different from the power reduction factor for a second UL BWP, wherein the first UL BWP and the second UL BWP are different.

[0261] In some embodiments, the configured maximum output power of the UL BWP may be determined based on a power reduction factor, wherein the power reduction factor for a first UL BWP is the same as the power reduction factor for a second UL BWP, wherein the first UL BWP and the second UL BWP are different. In some embodiments, the configured maximum output power of the UL BWP may be determined based on a maximum allowed UE output power (“P EMAX ”) to determine, wherein the first UL BWP has a first P EMAX , and the second ULBWP has a second P EMAX , where the first P EMAX Is with the second P EMAX Different values, and the first UL BWP and the second UL BWP are different.

[0262] In certain embodiments, the PHR includes a first PH of the first active UL BWP and a second PH of the second active UL BWP in response to the first active UL BWP and the second active UL BWP being associated with one or more of: different configured maximum output powers, different path loss references, and non-quasi-co-located path loss references, wherein the first active UL BWP is different from the second active UL BWP.

[0263] In some embodiments, the processor calculates a differential PH, the differential PH being a difference between a PH of a second active UL BWP and a PH of a first active UL BWP, wherein the first active UL BWP is different from the second active UL BWP. In such embodiments, the PHR may include a PH of the first active UL BWP and a differential PH of the second active UL BWP in response to the first active UL BWP and the second active UL BWP having one or more of: the same configured maximum output power, the same path loss reference, and a quasi-co-located path loss reference.

[0264] In certain embodiments, the PHR includes PHs for the first active UL BWP and the second active UL BWP in response to the first active UL BWP and the second active UL BWP having one or more of: the same configured maximum output power, the same path loss reference, and a quasi-co-located path loss reference. Here, the first active UL BWP is different from the second active UL BWP. In such embodiments, the PH is calculated for the first UL BWP.

[0265] In some embodiments, the PHR includes PHs of a first active UL BWP and a second active UL BWP. Here, the PH may be calculated as the difference between the configured UE maximum transmit power of the serving cell and the sum of the transmit powers used for uplink transmissions on the first active UL BWP and the second UL BWP. In such embodiments, the transmit power used for uplink transmissions includes a first transmit power for a first reference uplink transmission on the first active UL BWP and a second transmit power for a second reference uplink transmission on the second active UL BWP.

[0266] In some embodiments, the transceiver receives a configuration for a power headroom BWP group. In one embodiment, receiving a configuration for a PH BWP group includes receiving an 'allowedPHTriggeringGroup' parameter. Here, the processor detects that the MAC entity has UL resources for a new transmission and determines whether a PHR backoff timer has expired (e.g., phr-ProhibitTimer).

[0267] In such an embodiment, the processor may trigger a PHR in response to expiration of a PHR backoff timer and in response to the path loss having changed by more than a threshold amount for at least one active BWP of a PH BWP group belonging to a serving cell (e.g., of any MAC entity used as a path loss reference) since the last transmission of a PHR in the MAC entity. In some embodiments, the threshold amount is indicated by a parameter 'phr-Tx-PowerFactorChange'.

[0268] In some embodiments, the transceiver receives a configuration for a path loss change threshold parameter (eg, 'dl-PathlossChange' parameter).Here, the processor detects that the MAC entity has UL resources for a new transmission and determines if a PHR backoff timer expires (eg, phr-ProhibitTimer).

[0269] In such an embodiment, in response to the expiration of the PHR backoff timer and in response to the path loss having changed by more than a threshold amount for at least one active UL BWP belonging to a serving cell (e.g., of any MAC entity used as a path loss reference) since the last transmission of the PHR in the MAC entity, the processor triggers the PHR. Here, the threshold amount is configured for the at least one active UL BWP. In certain embodiments, the threshold amount is a BWP-specific configuration. The threshold amount may be indicated by parameters 'dl-PathlossChange' and / or 'phr-Tx-PowerFactorChange'.

[0270] In some embodiments, the processor communicates on a first active UL BWP in a serving cell configured with multiple UL BWPs, and the processor switches from the first active UL BWP to a second active UL BWP. Here, the first active UL BWP and the second active UL BWP share a CL-PC process. In addition, the processor selectively resets the CL-PC process in response to switching the BWP.

[0271] In some embodiments, selectively resetting the CL-PC process includes resetting the CL-PC process in response to a frequency distance between the first BWP and the second BWP being greater than a threshold, and continuing the CL-PC process in response to the frequency distance being not greater than the threshold.

[0272] In some embodiments, selectively resetting the CL-PC process includes: determining a path loss reference for the first BWP and the second BWP. The processor continues the CL-PC process in response to the path loss reference being the same value for the first BWP and the second BWP or having a quasi-co-located relationship for the first BWP and the second BWP, and resets the CL-PC process in response to the path loss reference not being the same value for the first BWP and the second BWP and not having a quasi-co-located relationship for the first BWP and the second BWP.

[0273] In some embodiments, selectively resetting the CL-PC process includes: determining a quality parameter set for the first BWP and the second BWP, the quality parameter set including one or more of the following: an open-loop power control parameter set, a modulation and coding scheme table, a channel quality indicator table, a target reliability requirement, an associated service type or traffic type, and an associated parameter set. Here, the processor resets the CL-PC process in response to the quality parameter set not being the same value for the first BWP and the second BWP. In such an embodiment, the selection of one or more of the following is based on the received DCI: a modulation and coding scheme table, a channel quality indicator table, a target reliability requirement, an associated service type or traffic type.

[0274] A second method for UE power control of multiple UL carriers is disclosed herein. In various embodiments, the second method is performed by a UE, such as a remote unit 105, a UE 205, a UE 405, a UE 505, a UE 605, and / or a user equipment device 700. The second method includes: receiving a configuration of multiple uplink carriers for a serving cell; and calculating a PH for each of the multiple uplink carriers on the serving cell. The second method includes: sending a PHR based on the calculated PH for the multiple uplink carriers of the serving cell.

[0275] In some embodiments, the second method includes determining a configured maximum output power of an uplink carrier from a plurality of uplink carriers of a serving cell. In such embodiments, a PH of an uplink carrier from the plurality of uplink carriers on the serving cell indicates a difference between the configured maximum output power of the uplink carrier and a determined transmit power required for UL transmission on the uplink carrier.

[0276] In some embodiments, the second method includes determining a default power control parameter set for the serving cell. In such an embodiment, the PHR includes a single PH. Here, calculating the PH may include calculating a virtual PH in response to there being no UL transmission on any uplink carrier of a plurality of uplink carriers from the serving cell when calculating the PHR, the virtual PH being based on the default power control parameter set.

[0277] In some embodiments, the default power control parameter set includes one or more of: an open loop parameter set, a closed loop process, and a path loss RS. In some embodiments, the default power control parameter set corresponds to a UL carrier on which the PUCCH is semi-statically configured. In some embodiments, only a first uplink carrier of a plurality of uplink carriers is semi-statically configured for PUSCH, wherein the default power control parameter set corresponds to the first UL carrier.

[0278] In some embodiments, the default power control parameter set corresponds to a UL carrier having a CIF index of 0. In some embodiments, the plurality of uplink carriers include a SUL carrier and a NUL carrier, wherein the default power control parameter set corresponds to the NUL carrier.

[0279] In various embodiments, the PHR corresponds to one or more of: PUSCH PHR, PUCCH PHR, and SRSPHR.

[0280] In some embodiments, receiving a configuration of a plurality of uplink carriers for a serving cell comprises receiving a configuration of a first number of uplink carriers from the plurality of uplink carriers, the first number of uplink carriers corresponding to a first number of configured and active uplink bandwidth portions of the serving cell. In such an embodiment, the second method may comprise determining a default set of power control parameters for the serving cell. Here, the PHR comprises a single PH. In addition, calculating the PH comprises calculating a virtual PF in response to the absence of UL transmissions on any active BWP from the first number of active uplink bandwidth portions of the serving cell when preparing the PHR, wherein the virtual PH is based on the default set of power control parameters.

[0281] In some embodiments, the default power control parameter set corresponds to an active UL BWP. In some embodiments, the default power control parameter set corresponds to one of: an initial UL BWP and a default UL BWP, wherein the default UL BWP is a UL BWP linked to a default DL BWP. In some embodiments, the default power control parameter set corresponds to one of: a UL BWP with a minimum BWP index, a UL BWP with a minimum parameter set, a UL BWP associated with a service type or traffic type, and a UL BWP associated with a modulation and coding scheme table, a UL BWP associated with a channel quality indicator table, a UL BWP associated with a target reliability requirement, or a combination thereof.

[0282] In some embodiments, the PHR includes a plurality of PH fields, wherein the PH field includes one or more of a PH, a configured maximum output power, and a UL BWP index. In some embodiments, the configured maximum output power of the UL BWP may be determined based on a power reduction factor, wherein the power reduction factor for a first UL BWP is different from the power reduction factor for a second UL BWP, wherein the first UL BWP and the second UL BWP are different.

[0283] In some embodiments, the configured maximum output power of the UL BWP may be determined based on a power reduction factor, wherein the power reduction factor for a first UL BWP is the same as the power reduction factor for a second UL BWP, wherein the first UL BWP and the second UL BWP are different. In some embodiments, the configured maximum output power of the UL BWP may be determined based on a maximum allowed UE output power (“P EMAX ”) to determine, wherein the first UL BWP has a first P EMAX , and the second ULBWP has a second P EMAX , where the first P EMAX Is with the second P EMAX Different values, and the first UL BWP and the second UL BWP are different.

[0284] In certain embodiments, the PHR includes a first PH of the first active UL BWP and a second PH of the second active UL BWP in response to the first active UL BWP and the second active UL BWP being associated with one or more of: different configured maximum output powers, different path loss references, and non-quasi-co-located path loss references, wherein the first active UL BWP is different from the second active UL BWP.

[0285] In some embodiments, the second method includes: calculating a differential PH, the differential PH being a difference between a PH of a second active UL BWP and a PH of a first active UL BWP, wherein the first active UL BWP is different from the second active UL BWP. In such an embodiment, the PHR may include a PH of the first active UL BWP and a differential PH of the second active UL BWP in response to the first active UL BWP and the second active UL BWP having one or more of the following: the same configured maximum output power, the same path loss reference, and a quasi-co-located path loss reference.

[0286] In certain embodiments, the PHR includes PHs for the first active UL BWP and the second active UL BWP in response to the first active UL BWP and the second active UL BWP having one or more of: the same configured maximum output power, the same path loss reference, and a quasi-co-located path loss reference. Here, the first active UL BWP is different from the second active UL BWP. In such embodiments, the PH is calculated for the first UL BWP.

[0287] In some embodiments, the PHR includes PHs of a first active UL BWP and a second active UL BWP. Here, the PH may be calculated as the difference between the configured UE maximum transmit power of the serving cell and the sum of the transmit powers used for uplink transmissions on the first active UL BWP and the second UL BWP. In such embodiments, the transmit power used for uplink transmissions includes a first transmit power for a first reference uplink transmission on the first active UL BWP and a second transmit power for a second reference uplink transmission on the second active UL BWP.

[0288] In some embodiments, the second method includes: receiving a configuration for a power headroom BWP group. In one embodiment, receiving a configuration for a PH BWP group includes: receiving an 'allowedPHTriggeringGroup' parameter. Here, the second method also includes: detecting that the MAC entity has UL resources for a new transmission; and determining whether a PHR backoff timer has expired (e.g., phr-ProhibitTimer).

[0289] In such an embodiment, the second method may include triggering a PHR in response to expiration of a PHR backoff timer and in response to the path loss having changed by more than a threshold amount for at least one active BWP of a PH BWP group belonging to a serving cell (e.g., of any MAC entity used as a path loss reference) since the last transmission of a PHR in the MAC entity. In some embodiments, the threshold amount is indicated by a parameter 'phr-Tx-PowerFactorChange'.

[0290] In some embodiments, the transceiver receives a configuration for a path loss change threshold parameter (eg, 'dl-PathlossChange' parameter).Here, the second method further includes: detecting that the MAC entity has UL resources for a new transmission; and determining whether a PHR backoff timer expires (eg, phr-ProhibitTimer).

[0291] In such an embodiment, the second method may include triggering a PHR in response to expiration of a PHR backoff timer and in response to at least one active UL BWP belonging to a serving cell (e.g., of any MAC entity used as a path loss reference) having changed by more than a threshold amount since the last transmission of a PHR in the MAC entity. Here, the threshold amount is configured for the at least one active UL BWP. In some embodiments, the threshold amount is a BWP-specific configuration. The threshold amount may be indicated by parameters 'dl-PathlossChange' and / or 'phr-Tx-PowerFactorChange'.

[0292] In some embodiments, the second method includes: communicating on a first active UL BWP in a serving cell configured with multiple UL BWPs. The second method further includes: switching from the first active UL BWP to a second active UL BWP, wherein the first active UL BWP and the second active UL BWP share a CL-PC process; and selectively resetting the CL-PC process in response to switching the BWP.

[0293] In some embodiments, selectively resetting the CL-PC process includes resetting the CL-PC process in response to a frequency distance between the first BWP and the second BWP being greater than a threshold, and continuing the CL-PC process in response to the frequency distance being not greater than the threshold.

[0294] In certain embodiments, selectively resetting the CL-PC process includes determining a path loss reference for a first BWP and a second BWP, continuing the CL-PC process in response to the path loss reference being the same value for the first BWP and the second BWP or having a quasi-co-located relationship for the first BWP and the second BWP, and resetting the CL-PC process in response to the path loss reference not being the same value for the first BWP and the second BWP and not having a quasi-co-located relationship for the first BWP and the second BWP.

[0295] In some embodiments, selectively resetting the CL-PC process includes: determining a quality parameter set for the first BWP and the second BWP, the quality parameter set including one or more of the following: an open-loop power control parameter set, a modulation and coding scheme table, a channel quality indicator table, a target reliability requirement, an associated service type or traffic type, and an associated parameter set. Here, selectively resetting the CL-PC process also includes: resetting the CL-PC process in response to the quality parameter set not being the same value for the first BWP and the second BWP. In such an embodiment, the selection of one or more of the following is based on the received DCI: a modulation and coding scheme table, a channel quality indicator table, a target reliability requirement, an associated service type or traffic type.

[0296] A third device for UE power control of multiple UL carriers is disclosed herein. In various embodiments, the third device may be a UE, such as a remote unit 105, a UE 205, a UE 405, a UE 505, a UE 605, and / or a user equipment device 700. The third device includes a transceiver that performs a random access procedure. Here, performing the random access procedure includes sending PUSCH Msg3. The third device includes a processor that determines whether the UE is in an RRC_CONNECTED state and identifies the number of configured CL-PC processes for UL channels or signals. In response to the UE being in an RRC_CONNECTED state and the number of configured CL-PC processes for UL channels or signals exceeding one, the processor uses a CL-PC process with an index of zero to calculate the transmit power for PUSCH Msg3.

[0297] In some embodiments, the processor determines whether the PUCCH transmission lacks an explicit beam indication, and in response to the PUCCH transmission lacking an explicit beam indication, uses a CL-PC process with an index of zero to calculate the transmit power for PUSCH Msg3. In some embodiments, the transceiver receives a RAR when performing a random access procedure, and the processor resets the CL-PC accumulation of the CL-PC process with an index of zero in response to receiving the RAR.

[0298] A third method for UE power control of multiple UL carriers is disclosed herein. In various embodiments, the third method may be performed by a UE, such as a remote unit 105, a UE 205, a UE 405, a UE 505, a UE 605, and / or a user equipment device 700. The third method includes: performing a random access procedure, wherein performing the random access procedure includes sending a PUSCH Msg3. The third method includes: determining whether the UE is in an RRC_CONNECTED state; and identifying the number of configured CL-PC processes for an UL channel or signal. The third method includes: in response to the UE being in an RRC_CONNECTED state and in response to the number of configured CL-PC processes for an UL channel or signal exceeding one, using a CL-PC process with an index of zero to calculate a transmit power for PUSCH Msg3.

[0299] In some embodiments, the third method includes: determining whether the PUCCH transmission lacks an explicit beam indication; and in response to the PUCCH transmission lacking an explicit beam indication, using a CL-PC process with an index of zero to calculate the transmit power for PUSCH Msg3. In some embodiments, the third method includes: receiving a RAR when performing a random access procedure; and resetting the CL-PC accumulation of the CL-PC process with an index of zero in response to receiving the RAR.

[0300] A fourth device for UE power control is disclosed herein. In various embodiments, the fourth device may be a UE, such as a remote unit 105, a UE 205, a UE 405, a UE 505, a UE 605, and / or a user equipment device 700. The fourth device includes a transceiver that receives a plurality of target reliability configurations. Here, each of the plurality of target reliability configurations includes at least one of a modulation and coding scheme (MCS) table, a channel quality indicator (CQI) table, and an associated radio network temporary identifier.

[0301] The fourth device includes a processor that performs a first uplink transmission of an uplink channel based on a first target reliability configuration and a power control adjustment state of the uplink channel, and receives an indication of a second uplink transmission for the uplink channel. Here, the second uplink transmission of the uplink channel is based on the second target reliability configuration and the power control adjustment state of the uplink channel. The processor determines whether the second target reliability configuration is different from the first target reliability configuration, and in response to the determination that the second target reliability configuration is different from the first target reliability configuration, resets the power control adjustment state of the uplink channel. The processor controls the transceiver to perform the second uplink transmission of the uplink channel based on the second target reliability configuration and the reset power control adjustment state of the uplink channel.

[0302] In some embodiments, each of the plurality of target reliability configurations further comprises an associated downlink control information (DCI) format. In some embodiments, each of the plurality of target reliability configurations further comprises a power control parameter set. In such embodiments, the power control parameter set may comprise at least one of a power spectral density per subcarrier spacing and a path loss compensation parameter.

[0303] In some embodiments, the uplink channel is a physical uplink shared channel (PUSCH).In some embodiments, the transceiver further receives, via the downlink control information, an indication that the second uplink transmission of the uplink channel is based on a second target reliability configuration.

[0304] A fourth method for UE power control is disclosed herein. In various embodiments, the fourth method may be performed by a UE, such as a remote unit 105, a UE 205, a UE 405, a UE 505, a UE 605, and / or a user equipment device 700. The fourth method includes receiving a plurality of target reliability configurations. Here, each of the plurality of target reliability configurations includes at least one of a modulation and coding scheme (MCS) table, a channel quality indicator (CQI) table, and an associated radio network temporary identifier. The fourth method includes performing a first uplink transmission of an uplink channel based on a first target reliability configuration and a power control adjustment state of the uplink channel; and receiving an indication of a second uplink transmission for the uplink channel, wherein the second uplink transmission of the uplink channel is based on a second target reliability configuration and a power control adjustment state of the uplink channel.

[0305] The fourth method includes: determining whether the second target reliability configuration is different from the first target reliability configuration; and in response to the determination that the second target reliability configuration is different from the first target reliability configuration, resetting the power control adjustment state of the uplink channel. The fourth method includes: performing a second uplink transmission of the uplink channel based on the second target reliability configuration and the reset power control adjustment state of the uplink channel.

[0306] In some embodiments, each of the plurality of target reliability configurations further comprises an associated downlink control information (DCI) format. In some embodiments, each of the plurality of target reliability configurations further comprises a power control parameter set. In such embodiments, the power control parameter set may comprise at least one of a power spectral density per subcarrier spacing and a path loss compensation parameter.

[0307] In some embodiments, the uplink channel is a physical uplink shared channel (PUSCH).In some embodiments, the fourth method further comprises: receiving, via downlink control information, an indication that the second uplink transmission of the uplink channel is based on a second target reliability configuration.

[0308] Embodiments may be practiced in other specific forms. The described embodiments should be considered in all respects as merely illustrative and not restrictive. Therefore, the scope of the present invention is indicated by the appended claims rather than the preceding description. All changes within the meaning and equivalent range of the claims are included within their scope.

[0309] What is sought to be protected is:

Claims

1. A method of a UE, include: performing a random access procedure, wherein performing the random access procedure includes sending a physical uplink shared channel ("PUSCH") Msg3; Determining whether the UE is in an RRC_CONNECTED state; identifying a number of configured closed loop power control ("CL-PC") processes for an uplink ("UL") channel or signal; and In response to the UE being in an RRC_CONNECTED state and the number of configured CL-PC processes for the UL channel or signal being greater than one, calculating the transmit power for the PUSCH Msg3 using a CL-PC process with an index of zero; receiving a random access response ("RAR") when performing the random access procedure; as well as The CL-PC accumulation of the CL-PC process having an index of zero is reset in response to receiving the RAR, and the CL-PC process is reset based on receiving the RAR.

2. The method according to claim 1, further comprising: include: determining whether a physical uplink control channel ("PUCCH") transmission lacks an explicit beam indication; as well as In response to the lack of an explicit beam indication for the PUCCH transmission, a CL-PC process with an index of zero is used to calculate the transmit power for the PUSCH Msg3.

3. A device, include: a transceiver, the transceiver performing a random access procedure, wherein performing the random access procedure comprises sending a physical uplink shared channel ("PUSCH") Msg3; as well as A processor, the processor: determining whether the device is in a RRC_CONNECTED state; identifying a number of configured closed loop power control ("CL-PC") processes for an uplink ("UL") channel or signal; and In response to the apparatus being in an RRC CONNECTED state and the number of configured CL-PC processes for the UL channel or signal exceeds one, using a CL-PC process with an index of zero to calculate the transmit power for the PUSCH Msg3 wherein the transceiver receives a random access response ("RAR") when performing the random access procedure; and Wherein the processor resets the CL-PC accumulation of the CL-PC process having an index of zero in response to receiving the RAR, and the CL-PC process is reset based on receiving the RAR.

4. The device according to claim 3, in, The processor further: determining whether a physical uplink control channel ("PUCCH") transmission lacks an explicit beam indication; and In response to the PUCCH transmission lacking an explicit beam indication, the transmit power for the PUSCH Msg3 is calculated using a CL-PC process with an index of zero.