Power control for uplink transmission towards plurality of trps

Abstract

To provide a system and a method for enabling power control of multiple Transmission Reception Points (TRPs).SOLUTION: A wireless device performs at least one of: receiving, in a Downlink Control Information (DCI), a first Transmit Power Control (TPC) command and a second TPC command and an indication of a first transmission to a first TRP associated with a first closed-loop and a second transmission to a second TRP associated with a second closed-loop; determining a first and a second transmit power based on the first and the second TPC commands, respectively; and applying the first and the second transmit power to the first UL transmission and the second UL transmission, respectively. Thus, a system and the method according to the invention enable more accurate per TRP power control using a simple signaling for multiple UL transmissions towards different TRPs scheduled by a single DCI.SELECTED DRAWING: Figure 13

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of Provisional Patent Application No. 63 / 044,851, filed June 26, 2020, the disclosure of which is incorporated herein by reference in its entirety.

[0002] This disclosure relates to power control of multiple transmit receive points (TRPs). [Background technology]

[0003] The next generation mobile radio communication system (5G) or New Radio (NR) will support a diverse set of use cases and a diverse set of deployment scenarios, the latter including deployment at both low frequencies (below 6 GHz) and very high frequencies (up to 10 GHz).

[0004] NR Frame Structure and Resource Grid: NR uses cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) in both the downlink (DL) (i.e., from the network node, gNB, or base station to the user equipment or UE) and the uplink (UL) (i.e., from the UE to the gNB). Discrete Fourier transform (DFT) spread OFDM is also supported in the uplink. In the time domain, the NR downlink and uplink are organized into equal sized subframes of 1 ms each. The subframes are further divided into multiple slots, each of equal duration. The slot length depends on the subcarrier spacing. Δf = (15 × 2 u For a subcarrier spacing of 1 kHz, there is only one slot per subframe, and each slot consists of 14 OFDM symbols.

[0005] Data scheduling in NR is typically done on a slot basis, with an example using a slot of 14 symbols shown in FIG. 1, where the first two symbols contain the Physical Downlink Control Channel (PDCCH) and the rest contain the Physical Shared Data Channel, which is either the PDSCH (Physical Downlink Shared Channel) or the PUSCH (Physical Uplink Shared Channel).

[0006] In NR, different subcarrier spacing values ​​are supported. The supported subcarrier spacing values ​​(also called different numerologies) are Δf = (15 × 2 u ) kHz, where u∈{0,1,2,3,4} and Δf=(15×2 u ) kHz is the basic subcarrier spacing. The slot duration in milliseconds (ms) for subcarrier spacing configuration u is 1 / (2 u ) ms.

[0007] In the frequency domain, the system bandwidth is divided into resource blocks (RBs), each corresponding to 12 consecutive subcarriers. The resource blocks (RBs) are numbered starting with 0 at one end of the system bandwidth. The basic NR physical time-frequency resource grid is shown in Figure 2, where only one resource block (RB) in a slot of 14 symbols is shown. One OFDM subcarrier in one OFDM symbol interval forms one resource element (RE).

[0008] Downlink (DL) PDSCH transmissions can be dynamically scheduled, i.e., in each slot, the gNB transmits downlink control information (DCI) over the PDCCH (Physical Downlink Control Channel) regarding which UE data should be transmitted and on which RBs the data should be transmitted, or a semi-persistent schedule (SPS) can be applied, where periodic PDSCH transmissions are activated or deactivated by the DCI. Different DCI formats are defined in NR for DL ​​PDSCH scheduling, including DCI format 1_0, DCI format 1_1, and DCI format 1_2.

[0009] Similarly, uplink (UL) PUSCH transmissions may also be dynamically or semi-persistently scheduled using uplink grants in the DCI carried in the PDCCH. NR supports two types of semi-persistent uplink transmissions: Type 1 configuration grants (CGs) and Type 2 configuration grants, where Type 1 configuration grants are configured and activated by the Radio Resource Control (RRC) and Type 2 configuration grants are configured by the RRC but activated / deactivated by the DCI. DCI formats for scheduling PUSCH include DCI format 0_0, DCI format 0_1, and DCI format 0_2.

[0010] Transmission with Multiple Beams: In NR Frequency Range 2 (FR2), multiple radio frequency (RF) beams may be used to transmit and receive signals at the gNB and UE. For each DL beam from the gNB, there is typically an associated best receive (Rx) beam from the UE for receiving signals from the DL beam. The DL beam and the associated UE Rx beam form a beam pair. The beam pair can be identified by the so-called beam management process in NR.

[0011] A DL beam is identified by an associated DL Reference Signal (RS) that is transmitted within the beam either periodically, semi-statically, or aperiodically. DL RS for this purpose can be a Synchronization Signal (SS) and a Physical Broadcast Channel (PBCH) Block (SSB), or a Channel State Information RS (CSI-RS). For each DL RS, the UE can perform an Rx beam sweep to determine the best Rx beam associated with the DL beam. The best Rx beam for each DL RS is then stored by the UE. By measuring all DL RSs, the UE can determine and report to the gNB the best DL beam to use for DL ​​transmission.

[0012] Using the reciprocity principle, the same beam pair can also be used in the UL to transmit UL signals to the gNB, which is often referred to as beam correspondence.

[0013] An example is shown in Figure 3, where a gNB consists of a transmission point (TRP) using two DL beams, each associated with a CSI-RS. Each of the DL beams is associated with a best UE Rx beam, i.e., Rx beam #1 is associated with the DL beam with CSI-RS #1 and Rx beam #2 is associated with the DL beam with CSI-RS #2.

[0014] Due to UE movement or environmental changes, the best DL beam for a UE may change over time, so different DL beams may be used at different times. The DL beam used for DL ​​data transmission in PDSCH may be indicated by a transmission configuration indicator (TCI) field in the corresponding DCI that schedules the PDSCH or activates the PDSCH in case of SPS. The TCI field indicates the TCI state, including the DL RS associated with the DL beam. In the DCI, the PUCCH resource for carrying the corresponding HARQ (Hybrid Automatic Repeat Request) acknowledgement, i.e., ACK or NACK (A / N), is indicated. The UL beam for carrying the PUCCH is determined by the PUCCH spatial relationship activated for the PUCCH resource. For PUSCH transmission, the UL beam is indirectly indicated by a sounding reference signal (SRS) resource indicator (SRI) that points to one or more SRS resources associated with the PUSCH transmission. The SRS resource may be periodic, semi-persistent, or aperiodic. Each SRS resource is associated with an SRS spatial relationship, where a DL RS (or another periodic SRS) is specified. The UL beam for the PUSCH is implicitly indicated by the SRS spatial relationship.

[0015] Spatial Relationships

[0016] Spatial relationship is used in NR to refer to the spatial relationship between a UL channel or signal, such as PUCCH, PUSCH, or SRS, and a DL (or UL) reference signal (RS), such as CSI-RS, SSB, or SRS. If a UL channel or signal is spatially related to a DL RS, it means that the UE should transmit the UL channel or signal on the same beam that was used in receiving the DL RS immediately before. More precisely, the UE should transmit the UL channel or signal with the same spatial domain transmit filter used for receiving the DL RS.

[0017] If a UL channel or signal is spatially related to the UL SRS, the UE should apply the same spatial domain transmit filter to the transmission of the UL channel or signal as is used to transmit the SRS.

[0018] For PUCCH, up to 64 spatial relationships can be configured for the UE, one of which is activated by a medium access control (MAC) control element (CE) for each PUCCH resource.

[0019] FIG. 4 shows a PUCCH spatial relationship information element (IE) that a UE may be configured in NR, which includes an SSB index, a CSI-RS resource identity (ID), and an SRS resource ID, as well as one of several power control parameters such as a path loss RS, a closed loop index, etc.

[0020] For each periodic and semi-persistent SRS resource or aperiodic SRS with a configured usage "non-codebook", its associated DL CSI-RS is configured in the RRC. For each aperiodic SRS resource with a configured usage "codebook", its associated DL RS is identified in the SRS spatial relationship activated by the MAC CE. Figure 5 shows an example where one of the SSB index, CSI-RS resource identity (ID), and SRS resource ID is configured.

[0021] For PUSCH, the spatial relationship is defined by the spatial relationship of the corresponding SRS resources indicated by the SRI in the corresponding DCI.

[0022] Uplink Power Control in NR: Uplink power control is used to determine the appropriate transmit power for the PUSCH, PUCCH, or SRS to ensure that they are received by the gNB at an appropriate signal level. The transmit power depends on the amount of channel attenuation on the propagation path, the noise and interference levels experienced at the gNB receiver, and the data rate in the case of PUSCH or PUCCH.

[0023] Uplink power control in NR consists of two parts: open-loop power control and closed-loop power control. Open-loop power control is used to set the uplink transmit power based on path loss estimation and several other factors including target received power, channel / signal bandwidth, modulation and coding scheme (MCS), fractional power control factor, etc.

[0024] Closed loop power control is based on an explicit power control command received from the gNB. The power control command is typically determined based on several UL measurements at the gNB at the actual received signal level. The power control command may include the difference between the actual received signal level and the target received signal level. In NR, either cumulative or non-cumulative closed loop power adjustment is supported. For each UL channel or signal, up to two closed loops can be configured in NR. The closed loop power adjustment in a given period is also called the power control adjustment state.

[0025] In multi-beam transmission in FR2, the path loss estimation also needs to reflect the beamforming gain corresponding to the uplink transmit and receive beam pair used for the UL channel or signal. This is achieved by estimating the path loss based on measurements on the downlink RS transmitted via the corresponding downlink beam pair. The DL RS for this purpose is called DL path loss RS. The DL path loss RS can be a CSI-RS or an SSB. In the example shown in Figure 3, if a UL signal is transmitted in beam #1, CSI-RS #1 may be set as the path loss RS. Similarly, if a UL signal is transmitted in beam #2, CSI-RS #2 may be set as the path loss RS.

[0026] For a UL channel or signal (e.g., PUSCH, PUCCH, or SRS) to be transmitted in a UL beam pair associated with a path loss RS having index k, its transmit power at a transmission opportunity in a slot within a bandwidth portion (BWP) of the carrier frequency of the serving cell and closed-loop index I (I=0,1) is:

number

number

number

[0027] Power control parameter P O , P RB Note that (i), alpha, PL, Δ(i), and δ(i,l) are generally configured separately for each UL channel or signal (e.g., PUSCH, PUCCH, and SRS) and may be different for different UL channels or signals.

[0028] Power control for SRS: For SRS, the path loss RS and other power control parameters (e.g., P O , α, etc.) are configured for each SRS resource set. In NR Release 16, a list of path loss RSs may be configured for an SRS resource set, and one path loss RS is activated / selected by the medium access control (MAC) control element (CE). Note that for each bandwidth portion (BWP) in the serving cell, there can be only one SRS resource set configured with usage set to either "codebook" or "non-codebook" in NR.

[0029] For SRS closed loop power control, the UE can have a dedicated closed loop for SRS or can use a closed loop for PUSCH in the same serving cell. This is configured by the higher layer parameter srs-PowerControlAdjustmentStates in each SRS resource set to select one of three options: a dedicated closed loop for SRS, a first closed loop for PUSCH, and a second closed loop for PUSCH. If the closed loop is shared with PUSCH, the P for PUSCH can be used. closed-loop (i,l) also applies to the SRS transmitted in the SRS resource set.

[0030] In the case of a dedicated closed loop configured for SRS, δ(m,l) corresponds to the TPC command received in DCI format 2_3 for the UE. The mapping between the 2-bit TPC command field of the DCI and the power adjustment value in dB is shown in (Table 1).

[0031] Default Path Loss RS: If the path loss RS is not configured in an SRS resource set and SRS_SpatialRelationInfo is not configured in an SRS resource but the UE is configured with enableDefaultBeamPlForSRS, then in the TCI state of the control resource set (CORESET) with the smallest index if CORESET is configured in the active DL BWP, or in the active PDSCH TCI state with the smallest ID if CORESET is not configured in the active DL BWP, the path loss RS is a periodic RS resource using Quasi-Collocated ('QCL)-Type D.

[0032] PUSCH power control: For PUSCH, O =P O,nominal_PUCCH + P O,UE_PUSCH where P O =P O,nominal_PUCCH is cell specific and configured in RRC, P O,UE_PUSCH is UE specific and dynamically selected. For dynamically scheduled PUSCH, the UE is configured by RRC with a list of P0-PUSCH-Alpha sets and a list of SRI-PUSCH-PowerControl information elements, as shown in Figure 6. One SRI-PUSCH-PowerControl is selected by the SRI field in the DCI (e.g., DCI format 0_1, 0_2). Each of the SRI-PUSCH-PowerControl IEs consists of a PUSCH path loss RS ID, a closed loop index, and a P0-PUSCH-AlphaSet ID, and the P0-PUSCH-AlphaSet is the PUSCH path loss RS ID. O,UE_PUSCH, and α. δ(i,l) is indicated in the 2-bit TPC command field in the same DCI, and the mapping between this field value and dB values ​​is shown in (Table 1).

[0033] In NR Release 16, an additional one or two sets of P0-PUSCH-r16 may be configured for each SRI for ultra-reliable low-latency communication (URLLC) traffic. One set may be configured when the SRI is present in UL DCI format 0_1 ​​or DCI format 0_2 and whether the P0 associated with the SRI or the set of P0s configured for URLLC should be used for PUSCH may be dynamically indicated in the "Open Loop Power Control Parameter Set Indication" field of the UL DCI. Two sets may be configured when there is no SRI in the UL DCI and one of the two P0-PUSCH-r16 sets and the first P0-PUSCH-AlphaSet may be dynamically indicated in the "Open Loop Power Control Parameter Set Indication" field in the UL DCI.

[0034] If a PUSCH transmission is scheduled by a DCI format that does not include an SRI field or if SRI-PUSCHPowerControl is not provided to the UE, the UE shall select P O,UE_PUSCH and determine α.

[0035] In addition to the TPC command field in the DCI that schedules the PUSCH, PUSCH power control for a group of UEs is also supported by DCI format 2_2 with CRC scrambled by the TPC-PUSCH Radio Network Temporary Identifier (RNTI), allowing power adjustments for multiple UEs to be signaled simultaneously.

[0036] (Table 1): Mapping of TPC command fields in DCI formats 0_0, 0_1, 0_2, 2_2 for PUSCH or DCI format 2_3 for SRS to absolute and cumulative values. [Table 1]

[0037] For PUSCH with configured grant, P O ,α,and the closed-loop index are semi-statically configured by RRC. In case of a configured grant (CG) with a path loss RS configured in RRC, that RS is used for path loss estimation, otherwise the path loss RS indicated in the DCI activating the CG PUSCH is used for path loss estimation.

[0038] Default path loss RS: If a PUSCH transmission is scheduled by DCI format 0_0 and the UE is configured with PUCCH-SpatialRelationInfo for the PUCCH resource with the smallest index in the BWP of the serving cell, the UE shall use the same path loss RS resource for PUSCH as for PUCCH transmission in the PUCCH resource with the smallest index.

[0039] If there is no SRI field in DCI format 0_1 ​​or DCI format 0_2 that schedules the PUSCH, or if SRI-PUSCH-PowerControl is not provided to the UE, or for a PUSCH that is scheduled by DCI format 0_0 and for which PUCCH-SpatialRelationInfo is not configured, the path loss RS is the path loss RS contained in the PUSCH-PathlossReferenceRS-Id with the smallest index value.

[0040] If a PUSCH transmission is scheduled by DCI format 0_0 and the UE is not configured with PUCCH-SpatialRelationInfo for the PUCCH resource, and the UE is configured with enableDefaultBeamPlForPUSCH0_0, the UE is in the BWP of the serving cell and the path loss RS is a periodic RS resource with QCL assumption of “QCL-TypeD” in the TCI state or the CORESET with the smallest index in the active DL BWP of the primary cell.

[0041] Power control for PUCCH: O =P O,nominal_PUCCH + P O,UE_PUCCH , and α=1, where P O,nominal_PUCCH is a cell-specific parameter configured by the RRC, and P O,UE_PUCCH are UE-specific parameters, which may be different for different PUCCH resources. O,UE_PUCCH A list of PUCCH resources (each with P0-PUCCH-Id) and up to 8 path loss RSs (each with PUCCH-PathlossReferenceRS-Id). For each PUCCH resource, a PUCCH spatial relation (i.e., PUCCH-SpatialRelationInfo) is activated, where the closed-loop index, the path loss RS (from the corresponding list), and P O,UE_PUCCH (from the corresponding list) is constructed.

[0042] For closed loop power adjustment of PUCCH, up to two control loops can be configured. Accumulation is always active. TPC commands for PUCCH HARQ A / N can be received in any of DCI formats 1_0, 1_1, and 1_2 that schedule the corresponding PDSCH, or in DCI format 2_2 when the DCI is scrambled with the TPC-PUCCH-Radio Network Temporary Identifier (RNTI). The mapping between the TPC field values ​​in the DCI and the power correction values ​​in dB is shown in Table 2.

[0043] Table 2: Mapping of TPC command fields in DCI format 1_0 or DCI format 1_1 or DCI format 1_2 or DCI format 2_2 with accumulated δ(m,l) values ​​for PUCCH: [Table 2]

[0044] Default path loss RS: If no PUCCH spatial relationship is configured but a list of path loss RS is configured for PUCCH, the first path loss RS in the list is used.

[0045] If neither the path loss RS list nor the PUCCH-SpatialRelationInfo list is configured, but the UE is configured with enableDefaultBeamPlForPUCCH, the path loss RS is a periodic RS resource with "QCL-TypeD" in the TCI state of the CORESET with the smallest index in the active DL BWP of the primary cell.

[0046] UL transmission to multiple transmission reception points (TRP): For NR Release 16, 3GPP introduces PDSCH transmission with multiple transmission points, where a transport block can be transmitted over multiple TRPs to improve transmission reliability.

[0047] In NR Release 17, it is proposed to introduce UL enhancements with multiple TRPs by transmitting PUCCH or PUSCH towards different TRPs, either simultaneously or at different times, as shown in Figure 7.

[0048] In one scenario, multiple PUCCH / PUSCH transmissions, each destined for a different TRP, may be scheduled by a single DCI. For example, multiple spatial relationships may be activated for PUCCH resources, and the PUCCH resources may be signaled in the DCI that schedules the PDSCH. The HARQ A / N associated with the PDSCH is then carried by the PUCCH, and the PUCCH is repeated multiple times within a slot or across multiple slots, with each repetition destined for a different TRP. An example is shown in FIG. 8, where the PDSCH is scheduled by the DCI, the corresponding HARQ A / N is transmitted in the PUCCH, and the PUCCH is repeated twice in time, one toward TRP #1 and the other toward TRP #2. Each TRP is associated with a PUCCH spatial relationship.

[0049] An example of PUSCH repetition is shown in Figure 9, where two PUSCH repetitions for the same TB are scheduled by a single DCI, with each PUSCH opportunity going to a different TRP, each TRP being associated with an SRI or UL TCI state signaled in the UL DCI.

[0050] DL TCI condition: Several signals can be transmitted from different antenna ports of the same base station. These signals can have the same large-scale characteristics such as Doppler shift / spread, average delay spread, or average delay. These antenna ports are then said to be quasi-colocated (QCL).

[0051] If the UE knows that two antenna ports are QCL with respect to a certain parameter (e.g., Doppler spread), the UE can estimate that parameter based on one of the antenna ports and apply the estimate to receive signals on the other antenna port.

[0052] For example, the TCI state may indicate the QCL relationship between the CSI-RS for the Tracking RS (TRS) and the PDSCH demodulation reference signal (DM RS). When the UE receives the PDSCH DM RS, the UE may use measurements already made on the TRS to assist in DMRS reception.

[0053] Information about what assumptions can be made regarding the QCL is signaled by the network to the UE. In NR, four types of QCL relationships between a source RS and a destination RS are defined: Type A: {Doppler shift, Doppler spread, average delay, delay spread} Type B: {Doppler shift, Doppler spread} Type C: {average delay, Doppler shift} Type D: {Spatial Rx parameters}

[0054] For dynamic beam and transmission point (TRP) indication, the UE is configured via RRC signaling with up to 128 transmission configuration indicator (TCI) states for PDSCH in FR2 and up to 8 transmission configuration indicator (TCI) states in Frequency Range 1 (FR1) depending on the UE capabilities. Each TCI state includes QCL information, i.e., one or two DL RSs, and each RS is associated with a QCL type. The TCI states can be interpreted as a list of available DL beams / TRPs for PDSCH transmission to the UE.

[0055] For PDSCH transmission, up to eight TCI states or pairs of TCI states are activated, and the UE is dynamically indicated by the TCI codepoints in one or two DCIs of the activated TCI states for PDSCH reception. The UE uses the TCI state according to the value of the "Transmission Configuration Indication" field in the PDCCH with the detected DCI to determine the quasi-identical configuration of the PDSCH antenna ports.

[0056] UL TCI state: Existing methods of using spatial relationships for UL beam indication in NR are cumbersome and inflexible. To facilitate UL beam selection for UEs with multiple panels, a unified TCI framework for UL fast panel selection was evaluated and introduced in NR Release 17. Similar to DL, when the TCI state is used to indicate the DL beam / TRP, the TCI state can be used to select the UL panel and beam to be used for UL transmissions (i.e., PUSCH, PUCCH, and SRS).

[0057] It is assumed that the UL TCI states are configured by higher layers (i.e., RRC) for the UE in several possible ways. In one scenario, the UL TCI states are configured separately from the DL TCI states, and each uplink TCI state may include a DL RS (e.g., NZP CSI-RS or SSB) or a UL RS (e.g., SRS) to indicate the spatial relationship. The UL TCI states may be configured per UL channel / signal or per BWP, such that the same UL TCI states may be used for PUSCH, PUCCH, and SRS. Alternatively, the same list of TCI states may be used for both DL and UL, and thus the UE is configured with a single list of TCI states for both UL and DL beam indications. The single list of TCI states in this case may be configured per UL channel / signal or per BWP information element.

[0058] Power Headroom Reporting: Uplink power availability or power headroom (PHR) at the UE needs to be provided to the gNB. A PHR report is sent from the UE to the gNB when the UE is scheduled to transmit data on the PUSCH. A PHR report can be triggered periodically or when certain conditions are met, such as when the difference between the current PHR and the last report is greater than a configurable threshold.

[0059] There are two different types of power headroom reports defined in NR: Type 1 and Type 3. A Type 1 power headroom report reflects the power headroom assuming transmission of only PUSCH on a carrier. CMAX A negative PHR is a measure of the difference between the transmit power per carrier and the transmit power that would have been used for the PUSCH. A negative PHR indicates that the transmit power per carrier is greater than or equal to P CMAX Indicates that the .lambda. is limited by.

[0060] A Type 1 PHR can be based on the actual PUSCH transmission carrying the PHR report, or based on a reference PUSCH transmission (a.k.a. virtual PHR) if the time from the trigger of the PHR report to the corresponding PUSCH carrying the PHR report is too short for the UE to complete the PHR calculation based on the actual PUSCH. The power control parameters for the reference PUSCH are pre-determined.

[0061] Type 3 power headroom reporting is used for UL carrier switching, where a PHR is reported for carriers that are not yet configured for PUSCH transmissions, but are configured only for SRS transmissions. Similarly, Type 3 PHRs can be based on either actual SRS transmissions or reference SRS transmissions.

[0062] Improved systems and methods for multi-TRP power control are needed. Summary of the Invention

[0063] A system and method are provided for enabling power control of multiple transmit receive points (TRPs). A method is proposed in which multiple PUCCH TPC commands are included in a DL DCI that triggers multiple PUCCH transmissions towards multiple TRPs, each of which is associated with one of the TRPs. The number of TPC commands in a DCI is the same as the number of TCI states indicated in the DCI. The number of TPC command fields in a DCI is determined by the maximum number of spatial relationships (or UL TCI states) that are activated for all PUCCH resources configured in the corresponding BWP on the UL carrier.

[0064] Similarly, multiple PUSCH TPC commands are proposed to be included in an UL DCI for scheduling multiple PUSCH transmissions for multiple TRPs. The number of TPC commands in the DCI is equal to the number of SRIs (or UL TCI states) indicated in the DCI. The number of TPC command fields in the DCI is determined by the maximum number of SRIs (or UL TCI states) associated with a PUSCH transmission configured in the corresponding BWP on the UL carrier.

[0065] The closed loops associated with different TRPs are jointly indexed such that for group-based TPC commands in DCI format 2_2 and / or DCI format 2_3, each block for a UE may include one or more TPC commands and an associated closed-loop indicator. The number of bits of the closed-loop indicator is based on the maximum number of closed loops configured for the corresponding PUSCH, PUCCH, or SRS.

[0066] When the PHR report is based on the actual PUSCH and is carried on repeated PUSCHs towards multiple TRPs, multiple PHRs may be calculated, each based on one PUSCH opportunity to the TRP, and one of the minimum, maximum, or average values ​​of the multiple PHRs may be reported.

[0067] Various embodiments are proposed herein that address one or more of the problems disclosed herein.

[0068] According to some embodiments, a method of uplink transmit power control in a wireless network is provided, the wireless network comprising at least one network node comprising a plurality of transmission / reception points (TRPs) identified by spatial relations or SRIs, and a user equipment, the method comprising: receiving, in a DCI, first and second TPC commands and first and second spatial relations for first and second UL transmissions, respectively; estimating first and second transmit powers based on the first and second spatial relations, respectively; and / or applying first and second transmit powers to the first and second UL transmissions, respectively.

[0069] According to some embodiments, the first and second spatial relationships are associated with first and second DL or UL reference signals. According to some embodiments, the first and second DL or UL reference signals are one of CSI-RS, SSB, or SRS.

[0070] According to some embodiments, the first and second DL or UL reference signals are different. According to some embodiments, the DCI is a DL DCI of one of DCI format 1_1 or DCI format 1_2. According to some embodiments, the first and second UL transmissions are first and second PUCCH transmissions, respectively.

[0071] According to some embodiments, the first and second spatial relationships are associated to a single PUCCH resource. According to some embodiments, the DCI is a UL DCI of one of DCI format 0_1 ​​or DCI format 0_2.

[0072] According to some embodiments, the first and second UL transmissions are first and second PUSCH transmissions, respectively. According to some embodiments, the first and second spatial relationships are associated with first and second SRIs, respectively, indicated in the DCI.

[0073] In some embodiments, the method further comprises calculating first and second PHRs based on the first and second transmit powers, respectively, and reporting one of the first PHR, the second PHR, a maximum of the first and second PHRs, and a minimum of the first and second PHRs in a PHR report for the first and second PUSCH transmissions.

[0074] According to some embodiments, the first and second spatial relationships are associated with first and second UL TCI states, respectively, indicated in the DCI. According to some embodiments, the first and second spatial relationships are associated with first and second sets of power control parameters, respectively.

[0075] According to some embodiments, estimating the first and second transmit powers comprises calculating first and second open loop power adjustment values ​​based on the first and second sets of power control parameters, respectively, and calculating first and second closed loop power adjustment values ​​based on the first and second TPC commands, respectively.

[0076] According to some embodiments, the first spatial relationship and the second spatial relationship are associated with a first TRP and a second TRP, respectively. According to some embodiments, the first TPC command and the second TPC command are jointly encoded.

[0077] Certain embodiments may provide one or more of the following technical advantages: The solution allows for more precise power control per TRP with simple signaling for multiple UL transmissions to different TRPs scheduled by a single DCI. [Brief description of the drawings]

[0078] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate several aspects of the present disclosure and, together with the description, serve to explain the principles of the disclosure.

[0079] [Figure 1] shows data scheduling in New Radio (NR), which is typically slot-based, where the first two symbols contain the Physical Downlink Control Channel (PDCCH) and the rest contain the physical shared data channels, either PDSCH (Physical Downlink Shared Channel) or PUSCH (Physical Uplink Shared Channel).

[0080] [Diagram 2] 1 shows a basic NR physical time-frequency resource grid where only one resource block (RB) in a 14-symbol slot is shown. One orthogonal frequency division multiplexing (OFDM) subcarrier in one OFDM symbol interval forms one resource element (RE).

[0081] [Diagram 3] shows an example in which a gNB has a transmit / receive point (TRP) with two downlink (DL) beams, each associated with a channel state information reference signal (CSI-RS).

[0082] [Figure 4] indicates a PUCCH spatial relationship information element (IE) that may be configured in NR for the UE, which includes a synchronization signal block (SSB) index, a CSI-RS resource identification (ID), and a sounding reference signal (SRS) resource ID, as well as one of several power control parameters such as path loss RS, closed loop index, etc.

[0083] [Diagram 5]1 illustrates an example in which one of an SSB index, a CSI-RS resource identification (ID), and an SRS resource ID is configured, according to some embodiments of the present disclosure.

[0084] [Figure 6] 3 illustrates a dynamically scheduled PUSCH, where the UE is configured by RRC with a list of P0-PUSCH-Alpha sets and a list of SRI-PUSCH-PowerControl information elements, in accordance with certain embodiments of the present disclosure.

[0085] [Figure 7] 1 illustrates transmitting PUCCH or PUSCH to different TRPs, either simultaneously or at different times, in accordance with some embodiments of the present disclosure.

[0086] [Figure 8] 1 illustrates an example in which a PDSCH is scheduled by DCI and the corresponding HARQ A / N is repeated in time twice and transmitted on PUCCH, where one is transmitted towards TRP #1 and the other towards TRP #2, in accordance with some embodiments of the present disclosure.

[0087] [Figure 9] 1 illustrates an example of PUSCH repeat transmission according to some embodiments of the present disclosure, where two PUSCH repeat transmissions for the same TB are scheduled by a single downlink control information (DCI), with each PUSCH opportunity directed to a different TRP.

[0088] [Figure 10] 1 illustrates an example of a cellular communication system 100 in which embodiments of the present disclosure may be implemented.

[0089] [Figure 11]shows a wireless communication system represented as a 5G network architecture having core network functions (NFs), where the interaction between any two NFs is represented by a point-to-point reference point / interface.

[0090] [Figure 12] FIG. 13 shows a 5G network architecture that uses service-based interfaces between NFs in a CP instead of the point-to-point reference points / interfaces used in the 5G network architecture of FIG. 11.

[0091] [Figure 13] 1 illustrates a technique performed by a wireless device to enable multi-TRP power control in accordance with some embodiments of the present disclosure.

[0092] [Figure 14] 1 illustrates a method performed by a base station to enable multi-TRP power control in accordance with some embodiments of the present disclosure.

[0093] [Figure 15] 1 illustrates an example showing the configuration of three or more closed-loop indexes for a PUSCH in accordance with certain embodiments of the present disclosure.

[0094] [Figure 16] 1 illustrates an example showing the configuration of three or more closed-loop indexes for PUCCH, in accordance with certain embodiments of the present disclosure.

[0095] [Figure 17] 1 illustrates an example of signaling two transmit power control (TPC) commands, one for each of two PUCCH transmissions toward two TRPs, in accordance with some embodiments of the present disclosure.

[0096] [Figure 18]1 illustrates a second example of signaling two TPC commands (one for each of two PUCCH transmissions destined for two TRPs) according to some embodiments of the present disclosure.

[0097] [Figure 19] 1 illustrates an example of signaling two TPC commands (one for each of two PUSCH transmissions destined for two TRPs) according to some embodiments of the present disclosure.

[0098] [Figure 20] 1 illustrates an example in which multiple PUSCH transmissions for the same TB are scheduled by a UL DCI with two integrated uplink / downlink TCI states (or alternatively two dedicated uplink TCI states) and two TPC commands, in accordance with some embodiments of the present disclosure.

[0099] [Figure 21] 1 illustrates an example of including multiple TPC commands in a block associated with a UE in extended DCI format 2_2, according to some embodiments of the present disclosure.

[0100] [Figure 22] 1 illustrates an example of different power headroom for two TRPs according to some embodiments of the present disclosure.

[0101] [Figure 23] 1 is a schematic diagram of a radio access node according to some embodiments of the present disclosure.

[0102] [Figure 24] 1 is a schematic block diagram illustrating a virtualized embodiment of a radio access node according to some embodiments of the present disclosure.

[0103] [Diagram 25] 1 is a schematic configuration diagram of a radio access node according to some other embodiments of the present disclosure.

[0104] [Figure 26] 1 is a schematic block diagram of a wireless communication device according to some embodiments of the present disclosure.

[0105] [Figure 27] 12 is a schematic block diagram of a wireless communication device 1200 according to some other embodiments of the present disclosure.

[0106] [Figure 28] 1 illustrates a communications system including a telecommunications network, such as a 3GPP type cellular network, with an access network, such as a Radio Access Network (RAN), and a core network according to some embodiments of the present disclosure.

[0107] [Figure 29] 1 illustrates a communication system including a host computer according to some embodiments of the present disclosure.

[0108] 1 is a flowchart illustrating a method implemented in a communication system according to some embodiments of the present disclosure. [Diagram 30] 1 is a flowchart illustrating a method implemented in a communication system according to some embodiments of the present disclosure. [Diagram 31] 1 is a flowchart illustrating a method implemented in a communication system according to some embodiments of the present disclosure. [Diagram 32] 1 is a flowchart illustrating a method implemented in a communication system according to some embodiments of the present disclosure. [Diagram 33] 1 is a flowchart illustrating a method implemented in a communication system according to some embodiments of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0109] The embodiments described below represent information that enables those skilled in the art to implement the embodiments and show the best mode of implementing the embodiments. Upon reading the following description in light of the accompanying drawings, those skilled in the art will understand the concepts of the present disclosure and recognize applications of these concepts not specifically addressed herein. It is understood that these concepts and applications are within the scope of the present disclosure.

[0110] Wireless Node: As used herein, a "wireless node" is either a wireless access node or a wireless communication device.

[0111] Radio Access Node: As used herein, a "radio access node" or "radio network node" or "radio access network node" is any node in a Radio Access Network (RAN) of a cellular communications network that operates to receive and / or transmit signals wirelessly. Some examples of a radio access node include, but are not limited to, a base station in a 3GPP® Long Term Evolution (LTE) network (e.g., a New Radio (NR) base station (gNB) or an enhanced or evolved Node B (eNB) in a 3rd Generation Partnership Project (3GPP®) Fifth Generation (5G) NR network), a high power or macro base station, a low power base station (e.g., a micro base station, a pico base station, a Home eNB, etc.), a relay node, a network node implementing some of the functionality of a base station (e.g., a network node implementing a gNB Central Unit (gNB-CU) or a network node implementing a gNB Distributed Unit (gNB-DU)), or a network node implementing some of the functionality of some other type of radio access node.

[0112] Core Network Node: As used herein, a "core network node" is a node that implements a core network function or any kind of node in any core network. Examples of core network nodes include a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), a Home Subscriber Server (HSS), etc. Some other examples of core network nodes are an Access and Mobility Management Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), an Authentication Server (ASS), etc. machine This includes nodes that implement the AUSF, Network Slice Selection Function (NSSF), Network Publication Function (NEF), Network Function (NF) Repository Function (NRF), Policy Control Function (PCF), Unified Data Management (UDM), etc.

[0113] Communications Device: As used herein, a "communications device" is any type of device that has access to an access network. Some examples of communications devices include, but are not limited to, a mobile phone, a smartphone, a sensor device, a meter, a vehicle, a home appliance, a medical device, a media player, a camera, or any type of consumer electronics device, such as, but not limited to, a television, a radio, a lighting device, a tablet computer, a laptop, or a personal computer (PC). A communications device may be a portable, handheld, computer-embedded, or vehicle-mounted mobile device that allows for communication of voice and / or data over a wireless or wired connection. device may be also possible.

[0114] Wireless Communication Device: One type of communication device is a wireless communication device, which may be any type of wireless device that accesses (i.e., is served by) a wireless network (e.g., a cellular network). Some examples of wireless communication devices include, but are not limited to, user equipment devices (UEs) in 3GPP networks, machine type communication (MTC) devices, and Internet of Things (IoT) devices. Such wireless communication devices may be, or may be integrated into, mobile phones, smartphones, sensor devices, meters, vehicles, home appliances, medical devices, media players, cameras, or any type of consumer electronics, such as, but not limited to, televisions, radios, lighting devices, tablet computers, laptops, or PCs. Wireless communication devices may be portable, handheld, computer-embedded, or vehicle-mounted, which allow for communicating voice and / or data over a wireless connection. Mobile It may be a device.

[0115] Network Node: As used herein, a "network node" is any node that is part of the RAN or in the core network of a cellular communications network / system.

[0116] In this specification, 3GPP (registered trademark) cellular - It should be noted that, because of the focus of the discussion in communication systems, 3GPP® terminology or terminology similar to 3GPP® terminology is often used, however, the concepts disclosed herein are not limited to 3GPP® systems.

[0117] It should be noted that in the description herein, reference may be made to the term "cell", however, particularly with regard to 5G NR concepts, a beam may be used instead of a cell, and therefore it is important to note that the concepts described herein are equally applicable to both cells and beams.

[0118] FIG. 10 illustrates an embodiment of a cellular communication system 1000 in which embodiments of the present disclosure may be implemented. According to embodiments described herein, the cellular communication system 1000 is a 5G system (5GS) including a Next Generation RAN (NG-RAN) and a 5G Core (5GC). In this example, the RAN includes base stations 1002-1 and 1002-2, which in 5GS include NR base stations (gNBs) and, optionally, Next Generation eNBs (ng-eNBs) (e.g., LTE RAN nodes connected to 5GC) that control corresponding (macrocell) cells 1004-1 and 1004-2. The base stations 1002-1 and 1002-2 are generally referred to herein collectively as base stations 1002 and individually as base stations 1002. Similarly, the (macrocell) cells 1004-1 and 1004-2 are generally referred to herein collectively as (macrocell) cells 1004 and individually as (macrocell) cells 1004. The RAN may also include several low power nodes 1006-1 to 1006-4 that control corresponding small cells 1008-1 to 1008-4. The low power nodes 1006-1 to 1006-4 may be small base stations (such as pico or femto base stations) or remote radio heads (RRHs), or the like. Notably, although not shown, one or more of the small cells 1008-1 to 1008-4 may alternatively be provided by the base station 1002. The low power nodes 1006-1 to 1006-4 are generally referred to herein collectively as low power nodes 1006 and individually as low power nodes 1006. Similarly, the small cells 1008-1 to 1008-4 are generally referred to herein collectively as small cells 1008 and individually as small cells 1008. The cellular communication system 1000 also includes a core network 1010, referred to as 5GC in 5G systems (5GS). The base stations 1002 (and optionally low power nodes 1006) are connected to the core network 1010.

[0119] Base station 1002 and low power node 1006 serve wireless communication devices 1012-1 through 1012-5 in corresponding cells 1004 and 1008. Wireless communication devices 1012-1 through 1012-5 are generally referred to herein collectively as wireless communication devices 1012 and individually as wireless communication devices 1012. In the description that follows, wireless communication devices 1012 are often UEs, although the disclosure is not limited thereto.

[0120] 11 shows a wireless communication system represented as a 5G network architecture composed of core network functions (NFs), where the interaction between any two NFs is represented by a point-to-point reference point / interface. FIG. 11 can be seen as one particular implementation of the system 1000 of FIG.

[0121] From the access side, the 5G network architecture shown in FIG. 11 comprises multiple UEs 1012 connected to either a RAN 1002 or an access network (AN) and an AMF 1100. Typically, the RAN (AN) 1002 comprises a base station, such as an eNB or a gNB. From the core network perspective, the 5GC NFs shown in FIG. 11 include an NSSF 1102, an AUSF 1104, a UDM 1106, an AMF 1100, an SMF 1108, a PCF 1110, and an application function (AF) 1112.

[0122] Reference point representation of 5G network architecture is used to develop detailed call flows in normative standardization. N1 reference point is defined to carry signaling between UE 1012 and AMF 1100. Reference points for connecting between AN 1002 and AMF 1100 and between AN 1002 and UPF 1114 are defined as N2 and N3, respectively. There is reference point N11 between AMF 1100 and SMF 1108, which means that SMF 1108 is at least partially controlled by AMF 1100. N4 is used by SMF 1108 and UPF 1114, so that UPF 1114 can be configured using control signals generated by SMF 1108, and UPF 1114 can report its status to SMF 1108. N9 is a reference point for connections between different UPFs 1114, and N14 is a reference point connecting different AMFs 1100. N15 and N7 are defined because the PCF 1110 applies policies to the AMF 1100 and the SMF 1108, respectively. N12 is required for the AMF 1100 to authenticate the UE 1012. Subscription data of the UE 1012 is required for the AMF 1100 and the SMF 1108, so N8 and N10 are defined.

[0123] The 5GC network aims to separate the UP and CP. The UP carries user traffic and the cyclic prefix (CP) carries signaling in the network. In Figure 11, the UPF 1114 is in the UP and all other NFs, namely, the AMF 1100, the SMF 1108, the PCF 1110, the AF 1112, the NSSF 1102, the AUSF 1104, and the UDM 1106, are in the CP. Separating the UP and CP ensures that each plane resource is scaled independently. Also, the UPF may be located separately from the CP function in a distributed manner. In this architecture, the UPF may be located very close to the UE to reduce the round trip time (RTT) between the UE and the data network for some applications that require low latency.

[0124] The core 5G network architecture is formed from modularized functions. For example, the AMF 1100 and the Session Management Function (SMF) 1108 are independent functions in the CP. The separated AMF 1100 and SMF 1108 allow for independent evolution and scaling. As shown in Figure 11, other CP functions such as the PCF 1110 and the AUSF 1104 can be separated, and the modularized function design allows the 5GC network to flexibly support various services.

[0125] Each NF interacts directly with another NF. An intermediary function can be used to route messages from one NF to another. In the CP, a set of interactions between two NFs is defined as a service and can be reused. The services allow for modularity support. The user plane supports interactions such as forwarding operations between different UPFs.

[0126] FIG. 12 illustrates a 5G network architecture that uses a service-based interface between NFs in a CP instead of the point-to-point reference points / interfaces used in the 5G network architecture of FIG. 11. However, the NFs described above with reference to FIG. 11 correspond to the NFs illustrated in FIG. 12. Services, etc. that an NF provides to other authorized NFs may be exposed to authorized NFs via the service-based interface. In FIG. 12, the service-based interface is indicated by the letter "N", followed by the name of the NF, e.g., Namf for the service-based interface of the AMF 1100, and Nsmf for the service-based interface of the SMF 1108, etc. The NEF 1200 and NRF 1202 of FIG. 12 are not illustrated in FIG. 11 described above. However, it should be clear that all NFs illustrated in FIG. 11 can interact with the NEF 1200 and NRF 1202 of FIG. 12, as necessary, although not explicitly illustrated in FIG. 11.

[0127] Some characteristics of the NFs shown in Figures 11 and 12 can be explained in the following way: The AMF 1100 provides UE-based authentication, authorization, mobility management, etc. The UE 1012 is essentially connected to a single AMF 1100, since the AMF 1100 is independent of the radio access technology, even if multiple access technologies are used. The SMF 1108 is responsible for session management and assigns Internet Protocol (IP) addresses to the UE. It also selects and controls the UPF 1114 for data forwarding. If the UE 1012 has multiple sessions, a different SMF 1108 can be assigned to each session to manage them separately and possibly provide different capabilities for each session. The AF 1112 provides information about the packet flows to the PCF 1110, which is responsible for policy control, to support Quality of Service (QoS). Based on this information, the PCF 1110 determines policies regarding mobility and session management for the proper operation of the AMF 1100 and the SMF 1108. The Authentication Server Function (AUSF) 1104 supports authentication functions for the UE or the like and therefore stores data for authentication of the UE or the like, while the UDM 1106 stores subscription data for the UE 1012. The Data Network (DN) is not part of the 5GC network and provides internet access or operator services, etc.

[0128] An NF can be implemented as a network element on dedicated hardware, as a software instance running on dedicated hardware, or as a virtualized function instantiated on a suitable platform, e.g., a cloud infrastructure.

[0129] As mentioned above, PHR reporting is per carrier and does not explicitly consider beam-based operation. In existing NR, UL power control and PHR reporting consider UL transmission to a single TRP with one or multiple beams. For closed-loop power control, the transmit power control (TPC) commands carried in the DCI are for one closed loop. For multi-TRP transmission, the question arises how to do UL power control. More specifically, the question is how to distinguish closed loops between multiple TRPs and how to indicate multiple TPC commands, one for each TRP, in the DCI. Similarly, for PHR, the question is whether and how to report PHR for multiple TRPs.

[0130] A system and method for power control for uplink transmissions for multiple TRPs is provided. Figure 13 illustrates a method performed by a wireless device to enable power control of multiple TRPs. According to some embodiments, the wireless device performs at least one of receiving a first transmit power control (TPC) command, a second TPC command, and an indication in a downlink control information (DCI) indicating a first transmission of a physical channel to a first TRP associated with a first closed loop and a second transmission of a physical channel to a second TRP associated with a second closed loop (step 1300), determining a first transmit power and a second transmit power based on the first TPC command and the second TPC command, respectively (step 1302), and applying the first transmit power and the second transmit power to a first UL transmission and a second UL transmission, respectively (step 1304). In this way, some embodiments of the present disclosure allow for more accurate per TRP power control with simple signaling for multiple UL transmissions to different TRPs scheduled by a single DCI.

[0131] FIG. 14 illustrates a method performed by a base station to enable power control of multiple TRPs. According to some embodiments, the base station performs at least one of the following: transmitting to the wireless device first and second power control closed loop configurations associated with the first and second TRPs, respectively (step 1400); transmitting to the wireless device, in a DCI, a first transmit power control (TPC) command, a second TPC command, and an indication indicating a first UL transmission of a physical channel to the first TRP and a second UL transmission of a physical channel to the second TRP, respectively (step 1402); and receiving, in the first TRP, a first UL transmission with a first transmit power and a second UL transmission with a second transmit power, respectively (step 1404). In this way, some embodiments of the present disclosure enable more accurate per TRP power control with simple signaling for multiple UL transmissions to different TRPs scheduled by a single DCI.

[0132] For simplicity, two TRPs are considered in the following discussion, but it should be noted that this principle can be easily extended to three or more TRPs.

[0133] Since the channels from the UE to different TRPs are generally different, different closed loops are required for different TRPs for UL power control. Each TRP may also have a different beam for reception, so more than one closed loop may be required for each TRP. Note that the TRP is implicitly indicated to the UE through the spatial relationship or TCI state for UL transmission, and multiple spatial relationships / UL TCI states may be associated with the same TRP.

[0134] Note that TRPs are not part of the standard, but "TCI state", "spatial relationship", or SRI may be used as part of the standard, in which case they are equivalents to indicate a certain TRP.

[0135] To facilitate signaling and maintain consistency between the gNB and the UE for which the TPC command is intended for the closed loop, according to one embodiment, the closed loops related to all TRPs in the UL are indexed together. For example, up to four closed loops may be configured for two TRPs, two per TRP. The existing closed loop index ranges specified for PUSCH, PUCCH, and SRS may then be extended to support multiple TRPs. Note that the number of closed loops in NR is specified as PUCCH-PC-AdjustmentStates for PUCCH, PUSCH-PC-AdjustmentStates for PUSCH, and srs-PowerControlAdjustmentStates for SRS.

[0136] FIG. 15 shows an example illustrating the configuration of more than two closed loop indexes for PUSCH. To extend the number of closed loops of PUSCH beyond two, one option is to introduce a new field "xPUSCH-PC-AdjustmentStates" as part of the PUSCH-PowerControl information element, which can have "twoStates" or "fourStates" as possible values, as shown in FIG. 15. Although FIG. 15 shows "xPUSCH-PC-AdjustmentStates" with two potentially configurable values ​​(i.e., two or four states), according to some other embodiments, other integer values ​​(e.g., 3, 5, 6, 7, 8, etc.) are also configurable values. When "xPUSCH-PC-AdjustmentStates" is present in PUSCH-PowerControl and set to "fourStates", the UE maintains four power control states (i.e., four closed loops) for PUSCH. Furthermore, according to some embodiments, the closed loop index applied to the PUSCH is indicated by the SRI via the closed loop index "SRI-PUSCH-ClosedLoopIndex" given in "SRI-PUSCH-PowerControl" shown in FIG. 15, so that the range of "SRI-PUSCH-ClosedLoopIndex" is extended to more than 2. For example, when the UE is configured to maintain four closed loops for the PUSCH, the range of "SRI-PUSCH-ClosedLoopIndex" is extended to four by including indexes i2 and i3 in addition to i0 and i1. When a first SRS resource is indicated via a first SRI in the DCI scheduling PUSCH, the spatial relationship of that SRS is used to transmit the first PUSCH towards the first TRP. The "SRI-PUSCH-ClosedLoopIndex" given in "SRI-PUSCH-PowerControl" corresponding to the first SRS resource is used for the first PUSCH towards the first TRP.

[0137] According to an alternative embodiment, instead of including "xPUSCH-PC-AdjustmentStates" with two possible values ​​"twoStates" or "fourStates" in the PUSCH-PowerControl information element, a field dedicated to four closed loops can be optionally present in the PUSCH-PowerControl information element. When this optional field is configured, the UE maintains four closed loops for the PUSCH.

[0138] FIG. 16 shows an example illustrating the configuration of more than two closed loop indexes for PUCCH. To extend the number of PUCCH closed loops to more than two, one option is to introduce a new field "xPUCCH-PC-AdjustmentStates" as part of the PUCCH-PowerControl information element, which can have "twoStates" or "fourStates" as possible values, as shown in FIG. 16A. Although FIG. 16B shows "xPUCCH-PC-AdjustmentStates" with two potentially configurable values ​​(i.e., two or four states), other integer values ​​(e.g., 3, 5, 6, 7, 8, etc.) are also potentially configurable values ​​according to some other embodiments. When "xPUCCH-PC-AdjustmentStates" is present in PUCCH-PowerControl and set to "fourStates", the UE maintains four power control states (i.e., four closed loops) for PUCCH. Furthermore, according to some embodiments, the closed loop index applied to the PUCCH is indicated by the spatial relationship activated for the PUCCH via the closed loop index "closedLoopIndex" given in the "PUCCH-SpatialRelationInfo" shown in FIG. 16B, so that the range of "closedLoopIndex" is extended beyond 2. For example, when the UE is configured to maintain four closed loops for the PUCCH, the range of "closedLoopIndex" is extended to 4 by including indexes i2 and i3 in addition to i0 and i1, as shown in FIG. 16B. When the first spatial relationship is activated for the PUCCH, that spatial relationship is used to transmit the first PUCCH towards the first TRP. The "closedLoopIndex" given in the "PUCCH-SpatialRelationInfo" corresponding to the first spatial relationship activated for the PUCCH is used for the first PUCCH towards the first TRP.

[0139] According to an alternative embodiment, instead of including "xPUCCH-PC-AdjustmentStates" with two possible values ​​"twoStates" or "fourStates" in the PUCCH-PowerControl information element, a field dedicated to four closed loops may optionally be present in the PUCCH-PowerControl information element. When this optional field is configured, the UE maintains four closed loops for the PUCCH.

[0140] PUCCH UL power control for multiple TRPs: According to this embodiment, it is assumed that a PUCCH carrying HARQ A / N for a PDSCH scheduled by a single DCI is repeated multiple times toward different TRPs, either in the same PUCCH resource or in different PUCCH resources. For each TRP, one or more closed-loop power controls are maintained in the UE and gNB for PUCCH transmission. For each PUCCH transmission to a TRP, the open-loop power control parameters are specified in the PUCCH spatial relationship that is activated for the corresponding PUCCH resource on which the PUCCH is transmitted. It should be noted that multiple PUCCH spatial relationships may be activated for a PUCCH resource.

[0141] According to this embodiment, multiple TPC commands are included in a DL DCI (e.g., DCI format 1_1 or DCI format 1_2) that schedules a PDSCH. Each TPC command is associated with a closed loop specified in an associated PUCCH spatial relationship for PUCCH transmission. The first and second TPC commands are respectively associated with the first and second PUCCH spatial relationships indicated in the DL DCI.

[0142] According to one embodiment, the number of TPC commands in the DL DCI may be determined by the number of closed loops configured for PUCCH in the PUCCH-PowerControl IE, e.g., if one or two closed loops are configured, one TPC command is included, if three or four closed loops are configured, two TPC commands are included.

[0143] According to another embodiment, the number of TPC commands in the DL DCI may be determined by the maximum number of PUCCH spatial relationships activated per PUCCH resource among all PUCCH resources, e.g., if only one spatial relationship is activated, one TPC command is used, if two spatial relationships are activated for at least one PUCCH resource, two TPC commands are used.

[0144] According to yet another embodiment, the number of TPC commands in a DL DCI may be determined by the maximum number of PUCCH resources that may be indicated in the DCI, e.g., one TPC command is indicated if only one PUCCH resource can be indicated, two TPC commands are indicated if two PUCCH resources can be indicated, etc.

[0145] An example is shown in FIG. 17 where a PDSCH is scheduled by DL DCI and the corresponding HARQ A / N carrying PUCCH is repeated twice, one towards TRP#1 and the other towards TRP#2. FIG. 17 shows an example of signaling two TPC commands, one for each of the two PUCCH transmissions towards the two TRPs. The number of repetitions is indicated by the number of PUCCH spatial relationships activated for the corresponding PUCCH resource indicated by the PRI field in the DCI. In this example, two PUCCH spatial relationships, each associated with one TRP, are activated for the PUCCH resource. Two TPC commands, namely TPC#1 and TPC#2, are included in the DL DCI, TPC#1 being associated with the first spatial relationship and TPC#2 being associated with the second spatial relationship. Alternatively, two PUCCH resources may be indicated in the DCI, with each PUCCH resource being activated with a different spatial relationship.

[0146] According to another embodiment, it is assumed that a PUCCH carrying a Hybrid Automatic Repeat Request (HARQ) A / N for a PDSCH scheduled by a single DCI is repeatedly transmitted multiple times towards different TRPs, and an open loop power control parameter or an indicator of such an open loop power control parameter is specified in the TCI state. It should be noted that multiple TCI states may be activated for a PUCCH resource. In one variant of the embodiment, the TCI state may be a dedicated uplink TCI state. In another variant of the embodiment, the TCI state may be integrated between uplink and downlink (i.e. the same TCI state may be used for uplink or downlink transmission).

[0147] According to a detailed embodiment, multiple TPC commands are included in a DL DCI for scheduling a PDSCH, and the PDSCH can be scheduled using a DL DCI indicating two TCI states (i.e., code points in a TCI field in the DL DCI indicating the two TCI states). In this case, the two TCI states are used as an integrated uplink / downlink TCI state, and open-loop power control parameters and closed-loop indexes for PUCCH transmissions are specified in the integrated TCI state. Each TPC command included in the DL DCI is associated with a closed-loop index specified in one of the integrated TCI states indicated in the DCI. The first and second TPC commands for the first and second PUCCH transmissions are associated with the first and second integrated TCI states indicated in the DL DCI, respectively.

[0148] According to one embodiment, the number of TPC commands in the DL DCI may be determined by the maximum number of integrated uplink / downlink TCI states that are activated in any one of the codepoints in the TCI field (i.e., the transmission configuration indication field) of the DL DCI. That is, if at least one codepoint in the TCI field of the DL DCI activates two integrated uplink / downlink TCI states, there are two TPC commands in the DL DCI. If none of the codepoints in the TCI field of the DL DCI activates two integrated uplink / downlink TCI states, there is a single TPC command in the DL DCI.

[0149] A second example is shown in Figure 18, where the PDSCH is scheduled by DL DCI and the corresponding HARQ A / N carrying the PUCCH is repeated twice, one towards TRP#1 and the other towards TRP#2. Figure 18 shows a second example of signaling two TPC commands, one for each of the two PUCCH transmissions towards the two TRPs. The number of PUCCH repetitions is indicated by the number of integrated uplink / downlink TCI states indicated by the TCI field in the DL DCI. In this example of Figure 18, two integrated uplink / downlink TCI states are indicated in the DL DCI, and each PUCCH repetition is transmitted using one of the integrated uplink / downlink TCI states and is associated with one TRP. Two TPC commands, namely TPC#1 and TPC#2, are included in the DL DCI, TPC#1 being associated with a first integrated uplink / downlink TCI state and TPC#2 being associated with a second integrated uplink / downlink TCI state.

[0150] According to one embodiment, for a PUCCH carrying a HARQ A / N for a corresponding PDSCH, the TCI state for the PUCCH is the same as that indicated in the TCI field in the DCI scheduling the PDSCH, i.e. the TCI state of the PUCCH follows the TCI state of the corresponding PDSCH.

[0151] PUSCH UL power control for multiple TRPs: According to this embodiment, when scheduling PUSCH transmissions to multiple TRPs, each indicated by an SRI in the DCI, multiple TPC commands are included in the UL DCI (e.g., DCI format 0_1 ​​and DCI format 0_2). The first and second TPC commands are associated with the first and second SRIs indicated in the DCI, respectively. For each SRI, the open-loop power control parameters are specified in the corresponding SRI-PUSCH-PowerControl information element configured by the RRC.

[0152] According to an alternative embodiment, when scheduling PUSCH transmissions to multiple TRPs, multiple TPC commands are included in the UL DCI (e.g. DCI format 0_1 ​​and DCI format 0_2), each indicated by an integrated uplink / downlink TCI state or a dedicated uplink TCI state in the UL DCI (i.e. in this case there are either two integrated uplink / downlink TCI states or two dedicated uplink TCI states in the UL DCI). In one variant of the embodiment, the first and second TPC commands are associated with the first and second integrated uplink / downlink TCI states indicated in the DCI. In another variant of the embodiment, the first and second TPC commands are associated with the first and second dedicated uplink TCI states indicated in the DCI.

[0153] According to one embodiment, the number of TPC commands in a UL DCI may be determined by the number of SRIs configured for the DCI.

[0154] According to another embodiment, the number of TPC commands in the UL DCI may be determined by the number of closed loops configured for the PUSCH, e.g., if one or two closed loops are configured, one TPC command is included, if three or four closed loops are configured, two TPC commands are included.

[0155] According to another embodiment, the number of TPC commands in the UL DCI may be determined by the maximum number of integrated uplink / downlink TCI states or dedicated uplink TCI states that are activated in any one of the codepoints in the TCI field (i.e., the transmission configuration indication field) of the UL DCI. That is, if at least one codepoint in the TCI field of the UL DCI has two integrated uplink / downlink TCI states or two uplink TCI states activated, then there are two TPC commands in the UL DCI. If none of the codepoints in the TCI field of the UL DCI has two integrated uplink / downlink TCI states or two dedicated TCI states activated, then there is a single TPC command in the UL DCI.

[0156] Multiple PUSCH transmissions for the same TB scheduled by a UL DCI with two SRIs and two TPC commands are shown in Figure 19. Figure 19 shows an example of signaling two TPC commands, one for each of the two PUSCH transmissions going to the two TRPs. t There are. The number of PUSCH transmission occasions is indicated by the number of SRIs in the UL DCI. In this example, two PUSCH transmissions are shown, each associated with one TRP. Two TPC commands, namely TPC#1 and TPC#2, are included in the UL DCI, TPC#1 is associated with the first SRI and TPC#2 is associated with the second SRI.

[0157] Figure 20 shows a second example in which multiple PUSCH transmissions for the same TB are scheduled by a UL DCI with two integrated uplink / downlink TCI states (or alternatively two dedicated uplink TCI states) and two TPC commands. Figure 20 shows a second example of signaling two TPC commands, one for each of the two PUSCH transmissions toward the two TRPs. The number of PUSCH transmission opportunities is indicated by the number of integrated uplink / downlink TCI states (or alternatively two dedicated uplink TCI states) indicated in the UL DCI. In this example, two PUSCH transmissions are indicated, each associated with one TRP. Two TPC commands, namely TPC#1 and TPC#2, are included in the UL DCI, where TPC#1 is associated with a first integrated uplink / downlink TCI state (or a first dedicated uplink TCI state) and TPC#2 is associated with a second integrated uplink / downlink TCI state (or a second dedicated uplink TCI state).

[0158] TPC command for PUCCH / PUSCH in DCI format 2_2: In the existing DCI format 2_2 for transmitting TPC commands to multiple UEs, a TPC command is assigned to each of a group of UEs. The TPC command is for PUSCH if the CRC of DCI is scrambled by TPC-PUSCH-RNTI, and is for PUCCH if it is scrambled by TPC-PUCCH-RNTI. The PUCCH (or PUSCH) TPC command for a UE may be accompanied by a 1-bit closed loop indicator if the UE is configured with two closed loops for PUCCH (or PUSCH). The DCI does not distinguish between different TRPs.

[0159] By combining closed loop indices across all TRPs, a simple extension of DCI format 2_2 for multiple TRPs is to increase the bit width of the closed loop indicator from 1 bit to multiple bits depending on the number of closed loops configured for PUCCH or PUSCH across all TRPs. For example, if 4 closed loops are configured, 2 bits may be used for the closed loop indicator.

[0160] According to another embodiment, each block of DCI format 2_2 may include multiple TPC commands, each associated with a closed loop. The number of TPC commands in a block may be configured by RRC or determined by the number of configured closed loops. An example is shown in Figure 21, where two closed loops are configured for PUSCH (or PUCCH) across all TRPs. Figure 21 shows an example of including multiple TPC commands in a block associated with a UE in extended DCI format 2_2.

[0161] TPC Commands for SRS in DCI Format 2_3: In the existing DCI format 2_3 for transmitting TPC commands for SRS to one or more UEs, one or more TPC commands can be assigned to the UE. A single closed loop is assumed for SRS, and therefore there is no closed loop indicator. For SRS transmission to multiple TRPs, two or more closed loops are required. To support SRS transmission to multiple TRPs, a closed loop indicator can be introduced into DCI format 2_3 for UEs configured with multiple closed loops for SRS. The number of bits of the closed loop indicator is determined by the number of configured closed loops. For example, if two closed loops are configured, one bit can be used.

[0162] According to another embodiment, each block of DCI format 2_3 may include multiple TPC commands, each associated with a closed loop of the SRS. The number of TPC commands in a block may be determined by the number of closed loops configured or may be configured.

[0163] UL Power Control with UL TCI States: For a given UL channel (i.e., PUCCH, PUSCH, or SRS), if UL TCI states are introduced for UL beam indication instead of using spatial relationships for PUCCH and SRS and SRI for PUSCH, each UL TCI state may be associated with a set of power control parameters. For a given UL TCI state, different sets of power control parameters may be associated with PUCCH, PUSCH, and SRS. Each set of power control parameters may be associated with P O , α, the path loss RS, and the closed loop index, and may be considered as a “power control state” having a power control state ID. O Each of α, path loss RS, or closed loop index is from a configured list of corresponding parameters. For example, P O ,α, a path loss RS, or a list of closed-loop indices may be configured for PUSCH (or PUCCH, SRS).

[0164] In one scenario, the UL TCI state is the same as the DL TCI state, i.e., the same TCI state is shared by both DL and UL. According to some embodiments, some power control parameters common to all UL channels, such as the pathloss RS (and / or possibly the closed loop index), may be included in the UL TCI state. Following the above embodiment, the pathloss RS (and / or the closed loop index) uses one mapping with the "UL state ID" or it follows the ID of the UL TCI state (UL TCI ID) or the ID of the pathloss RS (pathloss RS ID). And, P Oand α are mapped together as a "power control state" with an ID. An alternative is to have a closed-loop index on the "power control state" instead of the "UL state". Then the UL state can be configured per UL PWB and shared with the UL channel / signal, and the "power control state" can be configured per UL channel / signal.

[0165] For PUSCH, in the DCI, the SRI field is currently used to indicate the "UL transmission state" including the UL spatial relationship, the path loss RS, as well as the closed loop index and power control state. One problem is that the number of such states required may increase, especially if two SRI fields are required for two TRP transmissions. According to one embodiment, the UL transmission state includes two UL spatial relationships, two path loss RSs, two closed loop indexes, and the P O and α. This is shown as one SRI field in the DCI. Then, another delta "SRI" field is defined to include one set of P for the one selected for the first TRP. O and α values. These relative values ​​are configured in the “Delta Power Control States”, e.g., alpha_delta is relative to alpha for TRP1, and P0_delta is relative to P0 to TRP1.

[0166] PHR report for multiple TRPs: When a PHR report should be carried on a PUSCH to be repeatedly transmitted towards different TRPs, different transmission powers can be determined for different PUSCH occasions. For PHR calculation based on the actual PUSCH, when a PHR carrying a PUSCH is repeatedly transmitted towards different TRPs, the question arises as to which PUSCH occasion should be used to calculate the PHR. An example in which repeated transmission of a PUSCH is scheduled for two TRPs is shown in Figure 22. Figure 22 shows an example of different power headroom for two TRPs.

[0167] According to one embodiment, multiple PHRs are calculated, each PHR being associated with a PUSCH opportunity for a TRP. Either the maximum or minimum PHR is reported. According to another embodiment, an average value of the multiple PHRs is reported. According to yet another embodiment, a PRH for all TRPs is reported.

[0168] Joint coding of multiple TPCs: According to this embodiment, it is assumed that the power control loops are dependent. This can happen when the main cause of path loss is due to propagation close to the UE. In this case, for example, an increase in power towards a first TRP will likely also cause an increase in power towards a second TRP. An example is a UE moving to the basement of a building. According to this embodiment, this assumption is exploited to compress the signaling overhead by introducing some dependency between the powers, either through joint coding or equivalently.

[0169] For example, for PUCCH, the corresponding table can be seen below. Since one additional TPC bit is added, some of the combinations are removed, thereby reducing the DCI payload by one bit compared to having two independent TPC command fields. For example, the combination that increases the power to TRP#2 by 3 dB while simultaneously decreasing the power to TRP#1 by 1 dB is removed. In case of PUCCH transmission to only a single TRP, the first four entries in the first two columns of the table apply, which corresponds to the existing PUCCH table. A similar idea can be applied to PUSCH. Table 3: Mapping of TPC command fields with joint coding and compression [Table 3]

[0170] UE indication of supporting separate power control per TRP: According to this embodiment, an indication of how the UE can support power control in the uplink related to multi-TRP transmission is signaled via UE capability signaling from the UE to the network. Although the UE does not support separate closed-loop power control per TRP, the UE applies the same closed-loop index and / or open-loop power adjustment while still indicating that it supports UL M-TRP transmission. The UE can support separate open-loop power adjustment as well as separate power headroom reporting.

[0171] One example of indicating support for M-TRP in the UL is the UE indicating support for PUSCH / PUCCH / SRS associated with different CORESETPoolIndex values, where different CORESETPoolIndex values ​​represent different TRPs, and the maximum number of closed loop power controls via different TPC loops for PUCCH / PUSCH per TRP is indicated via capability signaling, as well as the maximum number of power headroom reports per TRP. Another example of supporting M-TRP in the UL relates to supporting multiple UL TCI / SRI for PUSCH / PUCCH simultaneous transmission.

[0172] Depending on the UE capability signaling, three different levels of power control can be configured for the UE for PUSCH, PUCCH, or power headroom reporting, per UE, per TRP, per UCI. Examples of RRC parameters are "perTCIPuschPowerControl", "perTCIPUCCHPowerControl", "perTCIPHRReport". The UE can expect the network to configure the same level of power control for PUSCH / PHR / PUCCH, rather than a combination of different levels.

[0173] FIG. 23 is a schematic block diagram of a radio access node 2300 according to some embodiments of the present disclosure. Optional functionality is represented by dashed boxes. The radio access node 2300 may be, for example, a base station 1002 or 1006 or a network node implementing all or a portion of the functionality of the base station 1002 or gNB described herein. As shown, the radio access node 2300 has a control system 2302, which has one or more processors 2304 (e.g., a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), etc.), a memory 2306, and a network interface 2308. The one or more processors 2304 are also referred to herein as processing circuits. Additionally, the radio access node 2300 may include one or more radio units 2310, each including one or more transmitters 2312 and one or more receivers 2314 coupled to one or more antennas 2316. The radio unit 2310 may be referred to as or be part of a wireless interface circuit. According to some embodiments, the radio unit 2310 is external to the control system 2302 and is connected to the control system 2302, for example, via a wired connection (e.g., optical cable). However, according to some other embodiments, the radio unit(s) 2310 and potentially the antenna(s) 2316 are integrated with the control system 2302. The one or more processors 2304 operate to provide one or more functions of the wireless access node 2300, as described herein. According to an embodiment, the above functions are implemented in software, for example stored in the memory 2306 and executed by the one or more processors 2304.

[0174] 24 is a schematic block diagram illustrating a virtualized embodiment of a radio access node 2300 according to some embodiments of the present disclosure. This description is equally applicable to other types of network nodes. Furthermore, other types of network nodes may have a similar virtualization architecture. Again, optional functionality is represented by dashed boxes.

[0175] As used herein, a "virtualized" radio access node is an implementation of the radio access node 2300 in which at least a portion of the functionality of the radio access node 2300 is implemented as virtual component(s) (e.g., via virtual machine(s) running on physical processing node(s) in network(s)). As shown, in this illustration, the radio access node 2300 may include a control system 2302 and / or one or more radio units 2310, as described above. The control system 2302 may be connected to the radio unit 2310, for example, via an optical cable or the like. The radio access node 2300 includes one or more processing nodes 2400 coupled to or included as part of a network(s) 2402. If present, the control system 2302 or radio units are connected to the processing node 2400 via the network 2402. Each processing node 2400 has one or more processors 2404 (eg, a CPU, ASIC, FPGA, and / or the like), memory 2406, and a network interface 2408.

[0176] In this example, the functions 2410 of the radio access node 2300 described herein are implemented in one or more processing nodes 2400 or distributed across one or more processing nodes 2400 and the control system 2302 and / or radio unit 2310 in any desired manner. According to some particular embodiments, some or all of the functions 2410 of the radio access node 2300 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment hosted by the processing node 2400. As will be appreciated by those skilled in the art, additional signaling or communication between the processing node 2400 and the control system 2302 is used to perform at least some of the desired functions 2410. Notably, according to some embodiments, the control system 2302 may not be included, in which case the radio unit 2310 communicates directly with the processing node 2400 via an appropriate network interface.

[0177] According to some embodiments, a computer program is provided that includes instructions that, when executed by at least one processor, cause the at least one processor to perform functions of the radio access node 2300 or a node (e.g., processing node 2400) implementing one or more of the functions 2410 of the radio access node 2300 in a virtual environment according to any of the embodiments described herein. According to some embodiments, a carrier is provided that carries the aforementioned computer program product. The carrier is one of an electrical signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as a memory).

[0178] 25 is a schematic block diagram of a radio access node 2300 according to some other embodiments of the present disclosure. The radio access node 2300 has one or more modules 2500, each of which is implemented in software. The modules 2500 provide the functionality of the radio access node 2300 described herein. This description is equally applicable to the processing node 2400 of FIG. 24, where the modules 2500 may be implemented in one of the processing nodes 2400 or distributed across multiple processing nodes 2400 and / or distributed across the processing nodes 2400 and the control system 2302.

[0179] FIG. 26 is a schematic block diagram of a wireless communication device 2600 according to some embodiments of the present disclosure. As shown, the wireless communication device 2600 includes one or more processors 2602 (e.g., CPU, ASIC, FPGA, etc.), memory 2604, and one or more transceivers 2606, each including one or more transmitters 2608 and one or more receivers 2610, coupled to one or more antennas 2612. The transceiver 2606 includes a radio front-end circuit connected to the antenna 2612, configured to condition signals communicated between the antenna 2612 and the processor 2602, as will be understood by those skilled in the art. The processor 2602 is also referred to herein as a processing circuit. The transceiver 2606 is also referred to herein as a radio circuit. According to some embodiments, the functionality of the wireless communication device 2600 described above may be fully or partially implemented in software, for example, stored in the memory 2604 and executed by the processor(s) 2602. It should be noted that the wireless communication device 2600 may include additional components not shown in FIG. 26 , such as, for example, one or more user interface components (e.g., input / output interfaces including a display, buttons, a touch screen, a microphone, a speaker, etc., and / or any other components for enabling input of information into the wireless communication device 2600 and / or output of information from the wireless communication device 2600, a power source (e.g., a battery and associated power circuitry), etc.

[0180] According to some embodiments, a computer program is provided that includes instructions that, when executed by at least one processor, cause the at least one processor to perform the functions of the wireless communication device 2600 according to any of the embodiments described herein. According to some embodiments, a carrier is provided that carries the aforementioned computer program product. The carrier is one of an electrical signal, an optical signal, a radio signal, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium such as a memory).

[0181] 27 is a schematic block diagram of a wireless communication device 2600 according to some other embodiments of the present disclosure. The wireless communication device 2600 includes one or more modules 2700, each of which is implemented in software. The module(s) 2700 provide the functionality of the wireless communication device 2600 described herein.

[0182] With reference to FIG. 28, according to one embodiment, a communication system includes a telecommunications network 2800, such as a 3GPP type cellular network, comprising an access network 2802, such as a RAN, and a core network 2804. The access network 2802 comprises a number of base stations 2806A, 2806B, 2806C, such as Node Bs, eNBs, gNBs, or other types of wireless access points (APs), each defining a corresponding coverage area 2808A, 2808B, 2808C. Each base station 2806A, 2806B, 2806C can be connected to the core network 2804 via a wired or wireless connection 2810. A first UE 2812 located in the coverage area 2808c is configured to be wirelessly connected or paged with the corresponding base station 2806c. A second UE 2814 in the coverage area 2808A can be wirelessly connected to the corresponding base station 2806A. Although multiple UEs 2812, 2814 are shown in this example, the disclosed embodiments are equally applicable to situations where a single UE is present within the coverage area and is connected to a corresponding base station 2806.

[0183] The telecommunications network 2800 is itself connected to a host computer 2816, which may be embodied in hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm. The host computer 2816 may be under the ownership or control of a service provider, or may be operated by or on behalf of the service provider. The connections 2818 and 2820 between the telecommunications network 2800 and the host computer 2816 may extend directly from the core network 2804 to the host computer 2816, or may go through any intermediate network 2822. The intermediate network 2822 may be one or a combination of a public, private, or hosted network, if any, the intermediate network 2822 may be a backbone network or the Internet, and in particular the intermediate network 2822 may include two or more sub-networks (not shown).

[0184] The communication system of FIG. 28 generally provides connectivity between the connected UEs 2812, 2814 and the host computer 2816. The connectivity may be described as an over-the-top (OTT) connection 2824. The host computer 2816 and the connected UEs 2812, 2814 are configured to communicate data and / or signaling via the OTT connection 2824 using the access network 2802, the core network 2804, any intermediate networks 2822, and further infrastructure (not shown) that may be considered as intermediaries. The OTT connection 2824 may be transparent in the sense that participating communication devices through which the OTT connection 2824 passes are unaware of the routing of uplink and downlink communications. For example, the base station 2806 does not need to be informed of the past routing of incoming downlink communications with data originating from the host computer 2816 to be forwarded (e.g., handed over) to the connected UE 2812. Similarly, the base station 2806 does not need to be aware of the future routing of outgoing uplink communications from the UE 2812 to the host computer 2816 .

[0185] Now, with reference to FIG. 29, an exemplary embodiment according to the UE, base station, and host computer embodiments discussed in the previous paragraph will be described. In the communication system 2900, the host computer 2902 comprises hardware 2904 including a communication interface 2906 configured to set up and maintain a wired or wireless connection with an interface of another communication device of the communication system 2900. The host computer 2902 further comprises a processing circuit 2908 that may have storage and / or processing capabilities. In particular, the processing circuit 2908 may include one or more programmable processors, ASICs, FPGAs, or combinations thereof (not shown) adapted to execute instructions. The host computer 2902 further comprises software 2910, which is stored in or accessible to the host computer 2902 and executable by the processing circuit 2908. The software 2910 comprises a host application 2912. The host application 2912 may be operable to provide services to a remote user, such as a UE 2914 connecting via an OTT connection 2916 terminated at the UE 2914 and the host computer 2902. In providing services to the remote user, the host application 2912 may provide user data that is transmitted using the OTT connection 2916.

[0186] The communication system 2900 further includes a base station 2918 having hardware 2920 disposed within the communication system to enable communication with the host computer 2902 and the UE 2914. The hardware 2920 may include a communication interface 2922 for setting up and maintaining a wired or wireless connection with an interface of another communication device of the communication system 2900, as well as a wireless interface 2924 for setting up and maintaining at least a wireless connection 2926 with a UE 2914 located in a coverage area (not shown in FIG. 29) served by the base station 2918. The communication interface 2922 may be configured to facilitate a connection 2928 to the host computer 2902. The connection 2928 may be direct, may pass through a core network (not shown in FIG. 29) of the communication system, and / or may pass through one or more intermediate networks external to the communication system. According to the illustrated embodiment, the hardware 2920 of the base station 2918 further includes processing circuitry 2930, which may include one or more programmable processors, ASICs, FPGAs, or combinations thereof (not shown) adapted to execute instructions. Additionally, the base station 2918 includes software 2932 stored internally or accessible via an external connection.

[0187] The communication system 2900 further comprises the UE 2914 already mentioned. The hardware 2934 of the UE 2914 may comprise a wireless interface 2936 configured to set up and maintain a wireless connection 2926 with a base station serving the coverage area in which the UE 2914 is currently located. The hardware 2934 of the UE 2914 further comprises a processing circuit 2938 which may comprise one or more programmable processors, ASICs, FPGAs, or combinations thereof (not shown) adapted to execute instructions. The UE 2914 further comprises software 2940 which may be stored or accessible within the UE 2914 and executable by the processing circuit 2938. The software 2940 comprises a client application 2942. The client application 2942, with the support of the host computer 2902, is operable to provide services to a human or non-human user via the UE 2914. In the host computer 2902, an executing host application 2912 may communicate with an executing client application 2942 via an OTT connection 2916 terminating in the UE 2914 and the host computer 2902. In providing services to a user, the client application 2942 may receive request data from the host application 2912 and provide user data in response to the request data. The OTT connection 2916 may carry both the request data and the user data. The client application 2942 may interact with the user and generate the user data provided by the user.

[0188] It should be noted that the host computer 2902, base station 2918, and UE 2914 shown in Figure 29 may be similar to or identical to the host computer 2816, one of the base stations 2806A, 2806B, 2806C, and one of the UEs 2812, 2814, respectively, of Figure 28. That is, the internal operation of these entities may be as shown in Figure 29 or may be independent therefrom, and the surrounding network topology may be that of Figure 28.

[0189] 29, the OTT connection 2916 is depicted abstractly to show communication between the host computer 2902 and the UE 2914 via the base station 2918 without explicitly referencing any intermediate devices, and the precise routing of messages through these devices. The network infrastructure may determine the routing, which may be configured to be hidden from the UE 2914, or from the service provider operating the host computer 2902, or both. While the OTT connection 2916 is active, the network infrastructure may further determine to dynamically change the routing (e.g., based on load balancing considerations or network reconfiguration).

[0190] The wireless connection 2926 between the UE 2914 and the base station 2918 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT service provided to the UE 2914 using the OTT connection 2916 of which the wireless connection 2926 forms the final leg. More precisely, the teachings of these embodiments may improve, for example, data rates, latency, power consumption, etc., thereby providing advantages such as, for example, reduced user latency, relaxed file size limitations, better responsiveness, extended battery life, etc.

[0191] Measurement procedures may be provided for the purpose of monitoring data rates, latencies, and other factors that one or more embodiments improve. Additionally, there may be optional network functionality for reconfiguring the OTT connection 2916 between the host computer 2902 and the UE 2914 in response to variability in the measurement results. The measurement procedures and / or network functionality for reconfiguring the OTT connection 2916 may be implemented in the software 2910 and hardware 2904 of the host computer 2902, or in the software 2940 and hardware 2934 of the UE 2914, or both. According to some embodiments, sensors (not shown) may be deployed in or associated with the communication devices through which the OTT connection 2916 passes, and the sensors may participate in the measurement procedures by providing values ​​of the monitored quantities exemplified above, or by providing values ​​of other physical quantities, from which the software 2910, 2940 may calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 2916 may include message formats, retransmission settings, preferred routing, etc., and the reconfiguration need not affect the base station 2918 and may be unknown or imperceptible to the base station 2918. Such procedures and functionality may be known and practiced in the art. According to some embodiments, measurements may have unique UE signaling that facilitates measurements of the host computer 2902 throughput, propagation time, latency, etc. Measurements may be implemented in that the software 2910 and 2940 cause messages, particularly empty or "dummy" messages, to be sent using the OTT connection 2916 while monitoring propagation times, errors, etc.

[0192] FIG. 30 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described in connection with FIG. 28 and FIG. 29. To simplify the disclosure, only the figures that refer to FIG. 30 are included in this section. In step 3000, the host computer provides user data. In sub-step 3002 (which may be optional) of step 3000, the host computer provides the user data by executing a host application. In step 3004, the host computer initiates a transmission carrying the user data to the UE. In step 3006 (which may be optional), the base station transmits the user data carried in the host computer initiated transmission to the UE according to the teachings of the embodiments described throughout this disclosure. In step 3008 (which may be optional), the UE executes a client application associated with the host application executed by the host computer.

[0193] FIG. 31 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described in connection with FIG. 28 and FIG. 29. To simplify the disclosure, only the figures that refer to FIG. 31 are included in this section. In step 3100 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In step 3102, the host computer initiates a transmission carrying the user data to the UE. The transmitted signal may be passed through the base station according to the teachings of the embodiments described throughout this disclosure. In step 3104 (which may be optional), the UE receives the user data carried by the transmitted signal.

[0194] FIG. 32 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described in connection with FIG. 28 and FIG. 29. To simplify the disclosure, only the figures that refer to FIG. 32 are included in this section. In step 3200 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 3202, the UE provides user data. In sub-step 3204 (which may be optional) of step 3200, the UE provides the user data by executing a client application. In sub-step 3206 (which may be optional) of step 3202, the UE executes a client application that provides the user data in response to the received input data provided by the host computer. In providing the user data, the executed client application may further take into account user input received from a user. Regardless of the particular manner in which the user data is provided, the UE performs sub-step 3208. (May be optional) In step 3210 of the method, the host computer receives the user data transmitted from the UE according to the teachings of the embodiments described throughout this disclosure.

[0195] FIG. 33 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described in connection with FIG. 28 and FIG. 29. To simplify this disclosure, only the figures that refer to FIG. 33 are included in this section. In step 3300 (which may be optional), the base station receives user data from the UE according to the teachings of the embodiments described throughout this disclosure. In step 3302 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 3304 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0196] Any suitable step, method, feature, function, or benefit disclosed herein may be performed via one or more functional units or modules of one or more virtual devices. Each virtual device may comprise several of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), dedicated digital logic, and the like. The processing circuitry may be configured to execute program code stored in a memory, which may have one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, and the like. The program code stored in the memory has program instructions for executing one or more communication and / or data communication protocols, as well as instructions for executing one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional units to perform the corresponding functions in accordance with one or more embodiments of the present disclosure.

[0197] Although the processes in the figures may indicate a particular order of operations performed by certain embodiments of the present disclosure, it is to be understood that such orders are exemplary (e.g., alternative embodiments may perform operations in different orders, combine certain operations, overlap certain operations, etc.).

[0198] Embodiment

[0199] Group A Embodiments

[0200] EMBODIMENT 1: A method performed by a wireless device for enabling power control of multiple transmit reception points, multiple TRPs, comprising: receiving 1300 a plurality of Physical Uplink Control Channel (PUCCH) transmit power control (TPC) commands, where each of the TPC commands is associated with one of the TRPs; receiving 1302 a plurality of Physical Uplink Shared Channel (PUSCH) TPC commands, where each of the TPC commands is associated with one of the TRPs; and receiving 1303 a plurality of Physical Uplink Shared Channel (PUSCH) TPC commands, where each of the TPC commands is associated with one of the TRPs. and at least one of receiving first and second TPC commands and first and second spatial relationships for a first uplink (UL) transmission and a second UL transmission, respectively, in digital coordinate information (DCI) (1304); estimating first and second transmit powers based on the first and second spatial relationships, respectively (1306); and applying the first and second transmit powers to the first and second UL transmissions, respectively (1308).

[0201] Embodiment 2: The method of any of the preceding embodiments, wherein the multiple TRPs are identified by a spatial relationship and / or a sounding reference signal, SRS, resource indicator, SRI, or transmission configuration indicator, TCI state.

[0202] Embodiment 3: The method according to any of the preceding embodiments, wherein receiving a plurality of PUCCH TPC commands includes receiving a plurality of PUCCH TPC commands in a DL DCI that trigger a plurality of PUCCH transmissions to a plurality of TRPs.

[0203]

[0023] Embodiment 4: The method of any of the preceding embodiments, wherein receiving a plurality of PUSCH TPC commands includes receiving a plurality of PUSCH TPC commands in an UL DCI that schedules a plurality of PUSCH transmissions for a plurality of TRPs.

[0204] Embodiment 5: The method of any of the preceding embodiments, wherein the first and second spatial relationships are associated with first and second DL or UL reference signals.

[0205] Embodiment 6: The method according to any of the preceding embodiments, wherein the first and second DL or UL reference signals are one of CSI-RS, SSB, or SRS.

[0206] Embodiment 7: The method of any of the preceding embodiments, wherein the first and second DL or UL reference signals are different.

[0207] Embodiment 8: The method of any of the preceding embodiments, wherein the DCI is a DL DCI in one of DCI format 1_1 or DCI format 1_embodiment 2.

[0208] Embodiment 9: The method according to any of the preceding embodiments, wherein the first and second UL transmissions are first and second PUCCH transmissions, respectively.

[0209] Embodiment 10: The method according to any of the preceding embodiments, wherein the first and second spatial relationships are associated with one or more PUCCH resources.

[0210] Embodiment 11: The method of any of the preceding embodiments, wherein the DCI is a UL DCI of one of DCI format 0_1 ​​or DCI format 0_embodiment 2.

[0211]

[0036] Embodiment 12: The method according to any of the preceding embodiments, wherein the first and second UL transmissions are first and second PUSCH transmissions, respectively.

[0212] Embodiment 13: A method according to any of the preceding embodiments, wherein the first and second spatial relationships are associated with first and second SRIs, respectively, indicated in the DCI.

[0213] Embodiment 14: The method of any of the preceding embodiments, wherein the method further includes calculating first and second PHRs based on the first and second transmit powers, respectively, and reporting one of the first PHR, the second PHR, the maximum value of the first and second PHRs, the minimum value of the first and second PHRs, or both the first and second PHRs in a PHR report for the first and second PUSCH transmissions.

[0214] Embodiment 15: The method of any of the preceding embodiments, wherein the first and second spatial relationships are associated with first and second UL TCI states, respectively, indicated in the DCI.

[0215] Embodiment 16: A method according to any of the preceding embodiments, wherein the first and second spatial relationships are associated with first and second sets of power control parameters, respectively.

[0216] Embodiment 17: The method of any of the preceding embodiments, wherein estimating the first and second transmit powers includes calculating first and second open-loop power adjustments based on the first and second sets of power control parameters, respectively, and calculating first and second closed-loop power adjustments based on the first and second TPC commands, respectively.

[0217] Embodiment 18: The method of any of the preceding embodiments, wherein the first and second spatial relationships are associated with first and second TRPs, respectively.

[0218] Embodiment 19: The method according to any of the previous embodiments, wherein the first and second TPC commands are jointly encoded.

[0219] Embodiment 20: The method of any of the previous embodiments, wherein the number of TPC commands in the DCI is determined based on one or more of the group consisting of: the number of TPC command fields in the DCI, determined by the number of TCI states indicated in the DCI and the maximum number of spatial relationships (or UL TCI states) activated for all PUCCH resources configured in the corresponding BWP of the UL carrier; the number of SRIs (or UL TCI states) indicated in the DCI; and the maximum number of SRIs (or UL TCI states) associated with PUSCH transmissions configured in the corresponding BWP of the UL carrier.

[0220] Embodiment 21: The method of any of the preceding embodiments, wherein closed loops associated with different TRPs are jointly indexed.

[0221] Embodiment 22: For group-based TPC commands in DCI format 2_2 and / or DCI format 2_3, each block for a wireless device may include one or more TPC commands and associated closed-loop indicators. method .

[0222] Embodiment 23: The method according to any of the preceding embodiments, wherein the number of bits of the closed loop indicator is based on the maximum number of closed loops configured for the corresponding PUSCH, PUCCH, or SRS.

[0223]

[0046] Embodiment 24: The method according to any of the preceding embodiments, in which multiple PHRs are calculated when the PHR report is based on an actual PUSCH and is carried on a PUSCH that is repeated towards multiple TRPs.

[0224] Embodiment 25: The method according to any of the preceding embodiments, wherein each calculated PHR becomes a TRP based on one PUSCH opportunity, and reports at least one of the minimum, maximum, or average of the multiple calculated PHRs.

[0225] Embodiment 26: The method of any of the preceding embodiments, further comprising providing user data and transferring the user data to the base station via transmission to the host computer.

[0226] Group B Embodiments

[0227] 27. A method performed by a base station for enabling power control of multiple transmit reception points (TRPs), the method comprising: transmitting a plurality of PUCCH TPC commands to a wireless device (1400), where each of the plurality of TPC commands is associated with one of a plurality of TRPs; transmitting a plurality of PUSCH TPC commands to the wireless device (1402), where each of the plurality of TPC commands is associated with one of the plurality of TRPs; transmitting a first TPC command and a second TPC command and a first spatial relationship and a second spatial relationship for a first UL transmission and a second UL transmission, respectively, to the wireless device in a DCI (1404); estimating a first transmit power and a second transmit power based on the first spatial relationship and the second spatial relationship, respectively (1406); receiving the first UL transmission and the second UL transmission using the first transmit power and the second transmit power, respectively (1408). The method comprises at least one of the following:

[0228] Embodiment 28: The method of any of the preceding embodiments, wherein the multiple TRPs are identified by a spatial relationship and / or a sounding reference signal, SRS, resource indicator, SRI, or transmission configuration indicator, TCI state.

[0229]

[0046] Embodiment 29: The method according to any of the preceding embodiments, wherein transmitting a plurality of PUCCH TPC commands includes transmitting a plurality of PUCCH TPC commands in a DL DCI triggering a plurality of PUCCH transmissions for a plurality of TRPs.

[0230]

[0046] Embodiment 30: The method according to any of the preceding embodiments, wherein transmitting a plurality of PUSCH TPC commands includes transmitting a plurality of PUSCH TPC commands in an UL DCI that schedules a plurality of PUSCH transmissions for a plurality of TRPs.

[0231] Embodiment 31: The method of any of the preceding embodiments, wherein the first and second spatial relationships are associated with first and second DL or UL reference signals.

[0232] Embodiment 32: The method according to any of the preceding embodiments, wherein the first and second DL or UL reference signals are one of CSI-RS, SSB, or SRS.

[0233] Embodiment 33: The method of any of the preceding embodiments, wherein the first and second DL or UL reference signals are different.

[0234] Embodiment 34: The method of any of the preceding embodiments, wherein the DCI is a DL DCI of one of DCI format 1_1 or DCI format 1_embodiment 2.

[0235]

[0046] Embodiment 35: The method according to any of the preceding embodiments, wherein the first and second UL transmissions are first and second PUCCH transmissions, respectively.

[0236]

[0046] Embodiment 36: The method according to any of the preceding embodiments, wherein the first and second spatial relationships are associated with one or more PUCCH resources.

[0237] Embodiment 37: The method of any of the preceding embodiments, wherein the DCI is a UL DCI of one of DCI format 0_1 ​​or DCI format 0_embodiment 2.

[0238]

[0046] Embodiment 38: The method according to any of the preceding embodiments, wherein the first and second UL transmissions are first and second PUSCH transmissions, respectively.

[0239] Embodiment 39: A method according to any of the preceding embodiments, wherein the first and second spatial relationships are associated with first and second SRIs, respectively, indicated in the DCI.

[0240] Embodiment 40: The method of any of the preceding embodiments, further comprising: the first and second PHRs being calculated based on the first and second transmit powers, respectively; and receiving one of the first PHR, the second PHR, a maximum value of the first and second PHRs, a minimum value of the first and second PHRs, or both the first and second PHRs in a PHR report in the first and second PUSCH transmissions.

[0241] Embodiment 41: The method of any of the preceding embodiments, wherein the first and second spatial relationships are associated with first and second UL TCI states, respectively, indicated in the DCI.

[0242] Embodiment 42: A method according to any of the preceding embodiments, wherein the first and second spatial relationships are associated with first and second sets of power control parameters, respectively.

[0243] Embodiment 43: The method of any of the preceding embodiments, wherein estimating the first and second transmit powers includes calculating first and second open-loop power adjustments based on first and second sets of power control parameters, respectively, and the first and second closed-loop power adjustments are based on first and second TPC commands, respectively.

[0244] Embodiment 44: The method of any of the preceding embodiments, wherein the first and second spatial relationships are associated with first and second TRPs, respectively.

[0245] Embodiment 45: The method according to any of the previous embodiments, wherein the first and second TPC commands are jointly encoded.

[0246] Embodiment 46: The method of any of the previous embodiments, wherein the number of TPC commands in the DCI is determined based on one or more of the group consisting of: the number of TCI states indicated in the DCI, the number of TPC command fields in the DCI determined by the maximum number of spatial relationships (or UL TCI states) activated for all PUCCH resources configured in the corresponding BWP of the UL carrier, the number of SRIs (or UL TCI states) indicated in the DCI, and the maximum number of SRIs (or UL TCI states) associated with PUSCH transmissions configured in the corresponding BWP of the UL carrier.

[0247] Embodiment 47: The method of any of the preceding embodiments, wherein closed loops associated with different TRPs are jointly indexed.

[0248] Embodiment 48: For group-based TPC commands in DCI format 2_2 and / or DCI format 2_3, the method described in any of the preceding embodiments, wherein each block for a wireless device may include one or more TPC commands and associated closed-loop indicators.

[0249]

[0081] Embodiment 49: The method according to any of the preceding embodiments, wherein the number of bits of the closed loop indicator is based on the maximum number of closed loops configured for the corresponding PUSCH, PUCCH, or SRS.

[0250]

[0081] Embodiment 50: The method according to any of the preceding embodiments, in which multiple PHRs are calculated when the PHR report is based on an actual PUSCH and is carried on a PUSCH that is repeated towards multiple TRPs.

[0251] Embodiment 51: The method according to any of the preceding embodiments, wherein each calculated PHR becomes a TRP based on one PUSCH opportunity, and reports at least one of the minimum, maximum, or average of the multiple calculated PHRs.

[0252] Embodiment 52: The method of any of the preceding embodiments, further comprising obtaining user data and transferring the user data to a host computer or wireless device.

[0253] Group C Embodiments

[0254] Embodiment 53: A wireless device for enabling power control of multiple transmit receive points (TRPs), comprising: a processing circuit configured to perform any of the steps of any of the embodiments of Group A; and a power supply circuit configured to supply power to the wireless device.

[0255] Embodiment 54: A base station for enabling power control of multiple transmit receive points (TRPs), comprising: a processing circuit configured to perform any of the steps of any of the Group B embodiments; and a power supply circuit configured to supply power to the base station.

[0256] Embodiment 55: A user equipment (UE) for enabling power control of multiple transmit receive points (TRPs), comprising: an antenna configured to transmit and receive radio signals; a radio front-end circuit connected to the antenna and the processing circuit and configured to condition signals communicated between the antenna and the processing circuit; a processing circuit configured to perform any of the steps of any of the embodiments of Group A; an input interface connected to the processing circuit and configured to enable input of information to the UE to be processed by the processing circuit; an output interface connected to the processing circuit and configured to output information from the UE processed by the processing circuit; and a storage battery connected to the processing circuit and configured to supply power to the UE.

[0257] Embodiment 56: A communications system including a host computer having a processing circuit configured to provide user data and a communications interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), the cellular network comprising a base station having a radio interface and a processing circuit, the processing circuit of the base station configured to perform any of the steps of any of the Group B embodiments.

[0258] Embodiment 57: The communication system of the previous embodiment, further comprising a base station.

[0259] Embodiment 58: The communication system of the previous two embodiments, further including a UE, the UE configured to communicate with the base station.

[0260] Embodiment 59: The communications system of the previous three embodiments, wherein the processing circuitry of the host computer is configured to execute a host application thereby providing user data, and the UE comprises processing circuitry configured to execute a client application associated with the host application.

[0261] Embodiment 60: A method implemented in a communications system including a host computer, a base station, a user equipment, and a UE, the method comprising: providing user data at the host computer; and initiating a transmission at the host computer conveying the user data to the UE via a cellular network including the base station, the base station performing any of the steps of any of the Group B embodiments.

[0262]

[0046] Embodiment 61: The method of the embodiment further includes, at the base station, transmitting the user data.

[0263] Embodiment 62: The method of the previous two embodiments, wherein the user data is provided in the host computer by executing a host application, and the method further includes executing, in the UE, a client application associated with the host application.

[0264] Embodiment 63: A user equipment, UE, configured to communicate with a base station, comprising a radio interface and a processing circuit configured to perform the methods of the previous three embodiments.

[0265] Embodiment 64: A communications system including a host computer having a processing circuit configured to provide user data and a communications interface configured to transfer the user data to a cellular network for transmission to a user equipment (UE), the UE having a wireless interface and a processing circuit, the components of the UE being configured to perform any of the steps of any of the embodiments of Group A.

[0266]

[0046] Embodiment 65: The communication system of any preceding embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.

[0267] Embodiment 66: A communication system of the previous two embodiments, wherein the processing circuitry of the host computer is configured to execute a host application thereby to provide user data, and the processing circuitry of the UE is configured to execute a client application associated with the host application.

[0268] Embodiment 67: A method implemented in a communication system including a host computer, a base station, and a user equipment, UE, comprising: providing user data at the host computer; and initiating a transmission at the host computer conveying the user data to the UE via a cellular network including the base station, wherein the UE performs any of the steps of any of the embodiments of Group A.

[0269]

[0046] Embodiment 68: The method of the previous embodiment, further comprising: receiving, at the UE, user data from the base station.

[0270] Embodiment 69: A communications system including a host computer having a user equipment, a communications interface configured to receive user data originating from a transmission from the UE to a base station, the UE having a radio interface and processing circuitry, the processing circuitry of the UE being configured to perform any of the steps of any of the embodiments of Group A.

[0271] Embodiment 70: The communication system of the previous embodiment, further comprising a UE.

[0272] Embodiment 71: The communication system of the previous two embodiments, further including a base station, the base station comprising a radio interface configured to communicate with the UE, and a communication interface configured to transfer user data carried by transmissions from the UE to the base station to a host computer.

[0273] Embodiment 72: A communication system according to any of the previous three embodiments, wherein the processing circuitry of the host computer is configured to execute a host application, and the processing circuitry of the UE is configured to execute a client application associated with the host application, thereby providing user data.

[0274] Embodiment 73: The communication system of the previous four embodiments, wherein the processing circuitry of the host computer is configured to execute a host application and thereby provide the requested data, and the processing circuitry of the UE is configured to execute a client application associated with the host application and thereby provide user data in response to the requested data.

[0275] Embodiment 74: A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method including: receiving, at the host computer, user data transmitted from the UE to the base station, the UE performing any of the steps of any of the embodiments of Group A.

[0276]

[0081] Embodiment 75: The method of the embodiment further includes, at the UE, providing the user data to the base station.

[0277] Embodiment 76: The method of the previous two embodiments, further comprising: executing, in the UE, a client application thereby providing user data to be transmitted; and executing, in the host computer, a host application associated with the client application.

[0278] Embodiment 77: The method of the previous three embodiments, further comprising: executing a client application in the UE; and receiving input data for the client application in the UE, the input data being provided in the host computer by executing a host application associated with the client application, and the user data to be transmitted being provided by the client application in response to the input data.

[0279] Embodiment 78: A communications system including a host computer having a communications interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, the base station having a radio interface and processing circuitry, the processing circuitry of the base station configured to perform any of the steps of any of the Group B embodiments.

[0280]

[0046] Embodiment 79: The communication system of the previous embodiment, further comprising a base station.

[0281] Embodiment 80: The communication system of the previous two embodiments, further including a UE, the UE configured to communicate with the base station.

[0282] Embodiment 81: The communications system of the previous three embodiments, wherein the processing circuitry of the host computer is configured to execute a host application and the UE is configured to execute a client application associated with the host application, thereby providing user data to be received by the host computer.

[0283] Embodiment 82: A method implemented in a communications system including a host computer, a base station, and a user equipment, UE, the method including receiving, at the host computer, from the base station, user data originating from a transmission received by the base station from the UE, the UE performing any of the steps of any of the embodiments of Group A.

[0284]

[0081] Embodiment 83: The method of the previous embodiment, further comprising receiving, at the base station, user data from the UE.

[0285] Embodiment 84: The method of the previous two embodiments, further comprising initiating, at the base station, transmission of the received user data to the host computer.

[0286] In this disclosure, at least some of the following abbreviations may be used. In case of discrepancies between the abbreviations, how it is used above shall prevail. If listed multiple times below, the first listing shall prevail over any subsequent listings. 3GPP(R): Third Generation Partnership Project 5G: Fifth Generation 5GC: 5th generation core 5GS: 5th generation system AF: Application Features AMF: Access and Mobility Features AN: Access Network AP: Access Point ASIC: Application Specific Integrated Circuit AUSF: Authentication Server Function BWP: Bandwidth Part CE: Control element CG: Pre-configured Grant CORESET: Control resource set CP: Cyclic Prefix CP-OFDM: Cyclic prefix orthogonal frequency division multiplexing CPU: Central Processing Unit CSI-RS channel state information reference signal DCI: Downlink Control Information DFT: Discrete Fourier Transform DL: Downlink DMRS: Demodulation Reference Signal DN: Data Network DSP: Digital Signal Processor eNB: Enhanced or evolved Node B FPGA: Field Programmable Gate Array FR1: Frequency range 1 FR2: Frequency range 2 gNB: New Radio Base Station gNB-CU: New Radio Base Station Central Unit gNB-DU: New Radio Base Station Distributed Unit HARQ: Hybrid Automatic Repeat Request HSS: Home Subscriber Server ID: Identification information IE: Information Element IoT: Internet of Things IP: Internet Protocol LTE: Long Term Evolution MAC: Medium Access Control MCS: Modulation and Coding Scheme MME: Mobility Management Entity MTC: Machine Type Communication M-TRP: Multi-Transmit-Receive Point NEF: Network Publishing Facility NF: Network Function NG-RAN: Next Generation Radio Access Network NR: New Radio NRF: Network Function Repository Facility NSSF: Network Slice Selection Function OFDM: Orthogonal Frequency Division Multiplexing OTT: Over the Top PBCH: Physical Broadcast Channel PC: Personal Computer PCF: Policy Control Facility PDCCH: Physical Downlink Control Channel PDSCH: Physical Downlink Shared Channel P-GW: Packet Data Network Gateway PHR: Power Headroom PUSCH: Physical Uplink Shared Channel QCL: Quasi-identical placement QoS: Quality of Service RAM: Random Access Memory RAN: Radio Access Network RB: Resource Block RE: Resource element RF: Radio Frequency RTI: Temporary Wireless Network Identifier Information ROM: Read-Only Memory RRC: Radio Resource Control RRH: Remote Radio Head RS: Reference signal RTT: Round Trip Time Rx: Receive SCFE: Service Capability Exposure Function SMF: Session Management Facility SPS: Semi-persistent schedule SRI: Signal Resource Indicator SRS: Sounding Reference Signal SS: Synchronization signal SSB: Synchronous signal block TCI: Transmission Configuration Indicator TP: Transmission point TPC: Transmit Power Control TRP: Transmission Receiving Point TRS: Tracking Reference Signal UDM: Unified Data Management Facility UE: User Equipment UL: Uplink UPF: User Plane Function URLLC: Ultra-reliable low-latency communication

[0287] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure, and all such improvements and modifications are deemed to be within the scope of the concepts disclosed herein.

Claims

1. 1. A method performed by a wireless device that enables uplink (UL) power control per transmit receiving point (TRP) for UL physical channels transmitted to a plurality of transmit receiving points (TRPs), the method comprising: receiving a first transmit power control (TPC) command, a second TPC command, and an indication of a first transmission of the physical channel to a first TRP associated with a first closed loop and a second transmission of the physical channel to a second TRP associated with a second closed loop in a downlink control information (DCI) (1300); determining 1302 a first transmit power and a second transmit power based on the first and second TPC commands, respectively; applying the first transmit power and the second transmit power to the first UL transmission and the second UL transmission, respectively (1304); The method according to claim 1,

2. 2. The method of claim 1, wherein the physical channel may be one of a physical uplink shared channel (PUSCH) and a physical uplink control channel (PUCCH).

3. 2. The method of claim 1, wherein the first and second TPC commands indicate power adjustments associated with the first and second closed loops, respectively.

4. 2. The method of claim 1, wherein each of the first and second TRPs is identified by a spatial relationship, a sounding reference signal (SRS), a resource indicator (SRI), or a transmission configuration indicator (TCI) state.

5. 5. The method of claim 1 , wherein the DCI is a DL DCI for scheduling a Physical Downlink Shared Channel (PDSCH), the DCI also indicates a PUCCH resource for carrying a Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) associated with the PDSCH, and the PUCCH resource is activated with a first and a second spatial relationship.

6. 6. The method of claim 1, wherein the first and second spatial relationships are associated with the first and second TRPs, respectively, and the first and second transmissions are PUCCH transmissions.

7. 6. The method of claim 1, wherein the indices of the first and second closed loops are indicated in the first and second spatial relationships, respectively.

8. 2. The method of claim 1, wherein the DCI is a UL DCI that schedules a PUSCH, and the first and second transmissions are PUSCH transmissions.

9. The method of claims 1 and 8, wherein the UL DCI comprises first and second SRIs associated with the first and second TRPs, respectively.

10. 9. The method of claims 1 and 8, wherein the indexes of the first and second closed loops are indicated through the first and second SRIs, respectively.

11. 9. The method of claim 1, wherein the first and second spatial relationships are associated with first and second DL or UL reference signals.

12. 12. The method of claim 11, wherein the first and second DL or UL reference signals are one of a CSI-RS, an SSB, or an SRS.

13. 13. The method of any one of claims 11 to 12, wherein the first and second DL or UL reference signals are different.

14. The method according to claim 1 , wherein the DCI is a DL DCI in one of DCI format 1_1 or DCI format 1_2.

15. 15. The method of claim 1, wherein the first and second UL transmissions are first and second PUCCH transmissions, respectively.

16. 16. The method of claim 1, wherein the first and second spatial relationships are associated with one or more PUCCH resources.

17. 17. The method according to claim 1, wherein the DCI is a UL DCI of one of DCI format 0_1 ​​or DCI format 0_2.

18. 15. The method of claim 1, wherein the first and second UL transmissions are first and second PUSCH transmissions, respectively.

19. 19. The method of claim 1, wherein the first and second spatial relationships are associated with first and second SRIs, respectively, indicated in the DCI.

20. 20. The method of any one of claims 1 to 19, further comprising: calculating first and second power headrooms (PH) based on the first and second transmit powers, respectively; reporting one of the first PH, the second PH, a maximum of the first and second PH, a minimum of the first and second PH, an average of the first and second PH, or both the first and second PH in a power headroom report (PHR) carried in the first and second PUSCH transmissions; The method according to claim 1,

21. 21. The method of claim 1, wherein the first and second transmissions are associated with first and second UL TCI states, respectively, indicated in the DCI.

22. 22. The method of claim 1, wherein the first and second transmissions are associated with first and second sets of power control parameters, respectively.

23. 23. The method of claim 1, wherein the first and second sets of power control parameters are configured for the first and second spatial relationship, SRI, or TCI conditions, respectively.

24. 23. The method of claim 1, wherein the first and second sets of power control parameters include at least an index for the first and second closed loops, respectively.

25. 23. The method of claim 1, wherein estimating the first and second transmit powers comprises: calculating first and second open loop power adjustments based on the first and second sets of power control parameters, respectively; and calculating first and second closed loop power adjustments based on the first and second TPC commands, respectively.

26. 26. The method of any one of claims 1 to 25, wherein the first and second TPC commands are jointly encoded.

27. 27. The method according to claim 1, wherein the number of TPC commands in the DCI is: the number of TCI states indicated in the DCI; and the number of TPC command fields in the DCI determined by the maximum number of spatial relationships (or UL TCI states) activated for all PUCCH resources configured in the corresponding BWP of the UL carrier; and The number of SRIs (or UL TCI states) indicated in the DCI; and the maximum number of SRIs (or UL TCI states) associated to a PUSCH transmission configured in the corresponding BWP of a UL carrier; and The method of claim 1, wherein the first and second parameters are determined based on one or more of the group consisting of:

28. 28. The method of any one of claims 1 to 27, wherein closed loops associated with different TRPs are indexed together.

29. 29. The method of claim 1, wherein in case of group-based TPC commands in DCI format 2_2 and / or DCI format 2_3, each block for the wireless device may include one or more TPC commands and associated closed-loop indicators.

30. 30. The method of claim 1, wherein a number of bits of the closed loop indicator is based on a maximum number of closed loops configured for the corresponding PUSCH, PUCCH, or SRS.

31. 31. The method of any one of claims 1 to 30, wherein the wireless device operates in a New Radio (NR) communications network.

32. 1. A method performed by a base station for enabling uplink (UL) power control per TRP of UL physical channels to be transmitted by a wireless device towards a plurality of transmit reception points (TRPs), the method comprising: Transmitting (1400) configurations of first and second power control closed loops associated with first and second TRPs, respectively, to the wireless device; Transmitting a first transmit power control (TPC) command, a second TPC command, and an indication of a first UL transmission of the physical channel to a first TRP and a second UL transmission of the physical channel to a second TRP in a DCI to the wireless device (1402); Receiving a first UL transmission using a first transmission power in the first TRP and a second UL transmission using a second transmission power in the second TRP (1404); The method according to claim 1,

33. 33. The method of claim 32, wherein the physical channel may be one of a physical uplink shared channel (PUSCH) and a physical uplink control channel (PUCCH).

34. 33. The method of claim 32, wherein the first and second TPC commands indicate power adjustments associated with the first and second closed loops, respectively.

35. 33. The method of claim 32, wherein each of the first and second TRPs is identified by a spatial relationship, a sounding reference signal (SRS), a resource indicator (SRI), or a transmission configuration indicator (TCI) state.

36. 36. The method of claim 32, wherein the DCI is a DL DCI for scheduling a physical downlink shared channel (PDSCH), the DCI also indicates PUCCH resources for carrying a hybrid automatic repeat request acknowledgement (HARQ-ACK) associated with the PDSCH, the PUCCH resources being activated with a first and second spatial relationship.

37. 37. The method of claim 32, wherein the first and second spatial relationships are associated with the first and second TRPs, respectively, and the first and second transmissions are PUCCH transmissions.

38. 37. A method according to any one of claims 32 to 36, wherein the indices of the first and second closed loops are indicated in the first and second spatial relationships, respectively.

39. 37. The method of claim 32, wherein the DCI is a UL DCI that schedules a PUSCH, and the first and second transmissions are PUSCH transmissions.

40. 40. The method of claims 32 and 39, wherein the UL DCI includes first and second SRIs associated with the first and second TRPs, respectively.

41. 40. The method of claims 32 and 39, wherein the first and second closed loop indices are indicated through the first and second SRIs, respectively.

42. 40. The method of any one of claims 32 to 39, wherein the first and second spatial relationships are associated with first and second DL or UL reference signals.

43. 43. The method of any one of claims 32 to 42, wherein the first and second DL or UL reference signals are one of a CSI-RS, an SSB, or an SRS.

44. 44. The method of any one of claims 32 to 43, wherein the first and second DL or UL reference signals are different.

45. 45. The method of claim 32, wherein the DCI is a DL DCI in one of DCI format 1_1 or DCI format 1_2.

46. 46. ​​The method of any one of claims 32 to 45, wherein the first and second spatial relationships are associated with one or more PUCCH resources.

47. 47. The method of any one of claims 32 to 46, wherein the DCI is a UL DCI of one of DCI format 0_1 ​​or DCI format 0_2.

48. 48. The method of any one of claims 32 to 47, further comprising: receiving a power headroom report (PHR) for the first and second PUSCH transmissions, where the PHR includes one of a first power headroom (PH), a second PH, a maximum of the first and second PH, a minimum of the first and second PH, an average of the first and second PH, and both the first and second PH, and the first and second PH are calculated based on the first and second transmit powers, respectively.

49. 50. The method of claim 32, wherein the first and second transmissions are associated with first and second UL TCI states, respectively, indicated in the DCI.

50. 50. The method of any one of claims 32 to 49, wherein the first and second transmissions are associated with first and second sets of power control parameters, respectively.

51. 51. The method of any one of claims 32 to 50, wherein the first and second sets of power control parameters are configured for the first and second spatial relationship, SRI, or TCI conditions, respectively.

52. 51. A method according to any one of claims 32 to 50, wherein the first and second sets of power control parameters include at least an index for the first and second closed loops, respectively.

53. 51. The method of any one of claims 32 to 50, wherein the first and second transmit powers include first and second open loop power adjustments based on the first and second sets of power control parameters, respectively, and first and second closed loop power adjustments based on the first and second TPC commands, respectively.

54. 54. The method of any one of claims 32 to 53, wherein the first and second TPC commands are jointly encoded.

55. 55. The method according to any one of claims 32 to 54, wherein the number of TPC commands in the DCI is: the number of TCI states indicated in the DCI; and the number of TPC command fields in the DCI determined by the maximum number of spatial relationships (or UL TCI states) activated for all PUCCH resources configured in the corresponding BWP of the UL carrier; and The number of SRIs (or UL TCI states) indicated in the DCI; and the maximum number of SRIs (or UL TCI states) associated to a PUSCH transmission configured in the corresponding BWP of a UL carrier; and The method of claim 1, wherein the first and second parameters are determined based on one or more of the group consisting of:

56. 56. The method of any one of claims 32 to 55, wherein closed loops associated with different TRPs are indexed together.

57. 57. The method of claim 32, wherein in the case of group-based TPC commands in DCI format 2_2 and / or DCI format 2_3, each block for the wireless device may include one or more TPC commands and an associated closed-loop indicator.

58. 58. The method of any one of claims 32 to 57, wherein a number of bits of the closed loop indicator is based on a maximum number of closed loops configured for the corresponding PUSCH, PUCCH, or SRS.

59. 59. The method of any one of claims 32 to 58, wherein the base station operates in a New Radio (NR) communications network.

60. 1. A wireless device (2600) for enabling power control of multiple transmit receive points (TRPs), comprising: One or more transmitters (2608); One or more receivers (2610); and a processing circuit (2602) associated with the one or more transmitters (2608) and the one or more receivers (2610), the processing circuit (2602) being configured to: receiving, in downlink control information (DCI), a first transmit power control (TPC) command, a second TPC command, and an indication of a first uplink (UL) transmission of the physical channel to a first TRP associated with a first closed loop, and a second UL transmission of the physical channel to the first TRP associated with the first closed loop; determining a first transmission power and a second transmission power based on the first and second TPC commands, respectively; applying the first transmit power and the second transmit power to the first UL transmission and the second UL transmission, respectively; Wireless devices.

61. 61. The wireless device (2600) of claim 60, wherein the processing circuit (2602) is further configured to cause the wireless device (2600) to perform a method according to any one of claims 4 to 31.

62. A base station (2300) for enabling uplink (UL) power control for UL physical channels transmitted to a plurality of transmit receiving points (TRPs), comprising: One or more transmitters (2312); One or more receivers (2314); and a processing circuit (2304) associated with the one or more transmitters (2312) and the one or more receivers (2314), the processing circuit (2304) being configured to: transmitting to the wireless device configurations of first and second power control closed loops for the physical channel, where the first and second power control closed loops are associated with first and second TRPs, respectively; causing the wireless device to transmit, in a DCI, a first transmit power control (TPC) command, a second TPC command, and an indication of a first UL transmission of the physical channel to the first TRP and a second UL transmission of the physical channel to the second TRP; having the first UL transmission received on the first TRP at a first transmission power and having the second UL transmission received on the second TRP at a second transmission power; Base station.

63. 63. A base station (2300) according to claim 62, wherein said processing circuit (2304) is further configured to cause said base station (2300) to perform a method according to any one of claims 28 to 54.

Images