Transmission power control (TPC) for uplink transmissions during a time domain window (TDW)

Abstract

The present disclosure relates to transmit power control (TPC) for uplink transmissions during a time domain window (TDW). A user equipment (UE) for implementing a set of transmit power control (TPC) commands during a time domain window (TDW) including multiple physical uplink shared channel (PUSCH) transmissions is provided. The UE can receive a configuration from a base station to configure the UE to support a power control mode and timeline measurement related to PUSCH transmissions. The UE can receive a set of TPC commands during the TDW, determine whether a TPC command in the set of TPC commands satisfies a time constraint based on the timeline measurement, determine a valid TPC command of the set of TPC commands based on one or more TPC commands that satisfy the time constraint, determine a valid delay of the valid TPC command based on the timeline measurement, and further apply the valid TPC command to a PUSCH transmission determined based on the valid delay of the valid TPC command.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 333,911, filed April 22, 2022, which is incorporated herein by reference in its entirety. Technical Field

[0003] The aspects described herein relate generally to wireless communication systems, including transmit power control (TPC) for uplink transmissions of user equipment (UE) during a time-domain window (TDW). Background Technology

[0004] Wireless communication systems can include fifth-generation (5G) systems, new radio (NR) systems, long-term evolution (LTE) systems, combinations thereof, or some other wireless systems. Furthermore, wireless communication systems can support a wide range of use cases, such as enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), ultra-reliable and low-latency communications (URLLC), and enhanced vehicle-to-everything (eV2X). For wireless communication systems, transmit power control (TPC), or sometimes called dynamic power control (DPC), is a mechanism used to reduce the power of a radio transmitter to the necessary level while maintaining a link with a specific quality. TPC can be used to avoid interference with other devices and / or extend battery life. Implementing TPC commands can present various challenges. Summary of the Invention

[0005] Some aspects of this disclosure relate to apparatus and methods for providing a user equipment (UE) with a transmit power control (TPC) command set during a time-domain window (TDW) comprising multiple physical uplink shared channel (PUSCH) transmissions. The TDW can be configured by the network. Within the TDW, it is desirable for the UE to maintain power consistency and phase continuity between multiple PUSCH transmissions. The implemented techniques are applicable to many wireless systems, such as wireless communication systems based on 3GPP Release 15 (Rel-15), Release 16 (Rel-16), Release 17 (Rel-17), etc.

[0006] Some aspects of this disclosure relate to a UE. The UE may include: a transceiver configured to enable communication with a base station via a wireless network; and a processor communicatively coupled to the transceiver. The processor may be configured to receive configuration from the base station to configure the UE to support power control modes and timeline measurements related to PUSCH transmissions. The processor may be further configured to transmit a first PUSCH transmission during a TDW (Time-of-War) including multiple PUSCH transmissions, and to receive a set of TPC commands during the TDW. In some embodiments, the set of TPC commands may include TPC commands scheduled by downlink control information (DCI) for a group of UEs including the UE, or TPC commands scheduled by a physical downlink control channel (PDCCH) for the UE. In some embodiments, the power control mode may be configured as a cumulative power control mode or an absolute power control mode. In some implementations, the timeline measurement may be determined based on the interval between two adjacent PUSCH transmissions within the TDW, between the Physical Downlink Control Channel (PDCCH) and a PUSCH transmission immediately adjacent to and scheduled by the PDCCH, or between a PUSCH transmission and a time instance configured by the configuration authorization of the PUSCH transmission. In some implementations, the processor may be configured to report to the base station the UE's ability to support the timeline measurement related to PUSCH transmissions.

[0007] According to some aspects, the processor may be further configured to determine, based on the timeline measurement, whether a TPC command in the TPC command set satisfies a time constraint; to determine a valid TPC command in the TPC command set based on one or more TPC commands that satisfy the time constraint; and to further determine the effective delay of the valid TPC command based on the timeline measurement. Furthermore, the processor may be configured to apply the valid TPC command to a second PUSCH transmission determined based on the effective delay of the valid TPC command.

[0008] According to some aspects, when the power control mode is the cumulative power control mode, the effective TPC command may include a new TPC command that is equivalent to the accumulation of all TPC commands in the TPC command set that satisfy the time constraint, and the second PUSCH transmission may occur in a subsequent TDW following the first TDW. In some embodiments, when the power control mode is the cumulative power control mode, the TPC command is scheduled by downlink control information (DCI) for a group of UEs including the UE, the first PUSCH transmission is of a configured grant type, the first PUSCH transmission may occur in a first actual TDW, and the second PUSCH transmission may occur in a second actual TDW within the first TDW.

[0009] In some implementations, when the power control mode is configured as the cumulative power control mode, the TPC command is scheduled by the physical downlink control channel (PDCCH) for the UE, the first PUSCH transmission is of the configuration grant type without uplink grant, and the second PUSCH transmission is outside the TDW. In some implementations, when the power control mode is the absolute power control mode, the valid TPC command may include the most recently received TPC command in the TPC command set that satisfies the time constraint, and the second PUSCH transmission may be outside the TDW.

[0010] In some implementations, when the power control mode is configured to the cumulative power control mode, the first PUSCH transmission is of the dynamic licensing type, the valid TPC commands of the TPC command set may include new TPC commands that are equivalent to the accumulation of all such TPC commands in the TPC command set that satisfy the time constraint, and the second PUSCH transmission may be outside the TDW.

[0011] According to some aspects, when the power control mode is the cumulative absolute power control mode, the TPC command is scheduled by downlink control information (DCI) for a set of UEs including the UE, and the valid TPC command of the TPC command set can be determined without considering the TPC command scheduled by the DCI.

[0012] The content of this invention is provided for illustrative purposes only, to provide an understanding of the subject matter described herein. Therefore, the features described above are merely illustrative and should not be construed as narrowing the scope or substance of the subject matter of this disclosure. Other features, aspects, and advantages of this disclosure will become apparent from the following detailed description, the accompanying drawings, and the claims. Attached Figure Description

[0013] The accompanying drawings, which are incorporated herein and form part of this specification, illustrate the present disclosure and, together with the specification, further serve to explain the principles of the disclosure and enable those skilled in the art to make and use the disclosure.

[0014] Figure 1 A wireless system according to some aspects of this disclosure is shown, including a user equipment (UE) for implementing a transmit power control (TPC) command set during a time-domain window (TDW).

[0015] Figure 2 A block diagram of a UE including a transceiver and a processor is shown according to some aspects of this disclosure.

[0016] Figure 3An exemplary procedure for implementing a TPC command set during TDW, performed by a UE according to some aspects of this disclosure, is shown.

[0017] Figures 4A to 4F Exemplary specific implementations of a TPC command set executed by a UE during TDW are shown, according to some aspects of this disclosure.

[0018] Figure 5 It is an exemplary computer system for implementing some aspects or parts of the disclosure provided herein.

[0019] This disclosure is described with reference to the accompanying drawings. In the drawings, the same reference numerals generally indicate the same or similarly functional elements. Furthermore, the leftmost numeral of the reference numerals generally appears first in the drawings. Detailed Implementation

[0020] With the development of mobile communication networks, some wireless systems, such as fifth-generation (5G) networks, can use higher frequency bands, resulting in higher propagation loss, weaker diffraction capabilities, and limited and shortened coverage. As the frequency band increases, the difference between uplink and downlink coverage becomes more pronounced, and uplink coverage becomes more restricted. Therefore, uplink coverage enhancement techniques can be used to improve the coverage and performance of such wireless networks.

[0021] According to some aspects, one such uplink coverage enhancement technique can be demodulation reference signal (DMRS) bundling. In conventional wireless systems, channel estimation for data demodulation is based on DMRS symbols in time slots. Typically, there is no need for consistency regarding DMRS symbols in different time slots or repeated transmissions of DMRS symbols. Using DMRS bundling, additional DMRS symbols can exist in one or more time slots. The UE can transmit the same or coherent DMRS symbols in multiple time slots, which can form a time-domain window (TDW) comprising multiple Physical Uplink Shared Channel (PUSCH) transmissions. In some implementations, PUSCH transmissions within multiple PUSCH transmissions can also be referred to as PUSCH repetition. DMRS symbols transmitted in different time slots can have power consistency and phase continuity, which is referred to as DMRS bundling. Within the TDW, it is expected that the UE will maintain power consistency and phase continuity between PUSCH transmissions or repetitions, enabling uplink coverage enhancement techniques such as DMRS bundling.

[0022] According to some aspects, transmit power control (TPC) is a mechanism used to control the power of a radio transmitter used for wireless transmission to avoid interference with other devices and / or extend battery life. In some implementations, multiple PUSCH transmissions may exist during TDW, and a set of TPC commands is received to control PUSCH transmissions. TPC commands can be scheduled by downlink control information (DCI) for a group of UEs including the UE, or by a physical downlink control channel (PDCCH) used only for that UE and not for other UEs. Implementing TPC commands within TDW can be challenging.

[0023] In some implementations, the UE may be configured to receive configuration from the base station to configure the UE to support power control modes and timeline measurements related to PUSCH transmissions. The UE may be further configured to transmit a first PUSCH transmission during a TDW that includes multiple PUSCH transmissions and to receive a TPC command set during the TDW. In some implementations, the power control mode may be configured as a cumulative power control mode or an absolute power control mode. In some implementations, timeline measurements may be determined based on the interval between two adjacent PUSCH transmissions within the TDW, between the Physical Downlink Control Channel (PDCCH) and a PUSCH transmission immediately adjacent to and scheduled by the PDCCH, or between a PUSCH transmission and a time instance of the configuration authorization configuration of the PUSCH transmission.

[0024] The embodiments described herein can determine the valid TPC commands of a TPC command set based on one or more TPC commands that satisfy time constraints. In some embodiments, valid TPC commands can be selected from the received TPC command set. In some other embodiments, the valid TPC command can be a new TPC command that is equivalent to the accumulation of all TPC commands in the TPC command set that satisfy the time constraints. The valid TPC command may have an effective delay determined based on timeline measurements. The UE can apply the valid TPC command to a second PUSCH transmission determined based on the effective delay of the valid TPC command.

[0025] Figure 1A wireless system 100 is illustrated, comprising a UE 101 implementing a TPC command set during TDW, according to some aspects of this disclosure. The wireless system 100 is provided for illustrative purposes only and is not intended to limit the aspects disclosed. The wireless system 100 may include, but is not limited to, UE 101, base station 103, and base station 105, all communicatively coupled to the core network 110. Other network entities, such as network controllers and relay stations, may be present. The wireless system may be referred to as a wireless network, a wireless communication system, or some other name known to those skilled in the art. In some wireless systems, only one base station 103 serving UE 101 may exist, instead of both base stations 103 and 105.

[0026] In some examples, wireless system 100 can be an NR system, an LTE system, a 5G system, or another wireless system. Furthermore, wireless system 100 can support a wide range of use cases, such as enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), ultra-reliable and low-latency communications (URLLC), and enhanced vehicle-to-everything communications (eV2X).

[0027] Depending on some aspects, base station 103 or base station 105 can be a fixed station or a mobile station. Base station 103 or base station 105 may also be referred to by other names, such as base transceiver system (BTS), access point (AP), transmit / receive point (TRP), evolved NodeB (eNB), next-generation node B (gNB), 5G node B (NB), or some other equivalent term.

[0028] Depending on some aspects, UE 101 can be fixed or mobile. UE 101 can be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a desktop computer, a cordless phone, a wireless local loop station, a tablet computer, a camera, a gaming device, a netbook, an ultrabook, a medical device or equipment, a biometric sensor or device, a wearable device (smartwatch, smart clothing, smart glasses, smart wristband, smart jewelry such as a smart ring or smart bracelet), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicle component, a smart meter, industrial manufacturing equipment, a GPS device, an Internet of Things (IoT) device, a machine-type communication (MTC) device, an evolved or enhanced machine-type communication (eMTC) device, or any other suitable device configured to communicate via a wireless medium. For example, MTC and eMTC devices may include robots, drones, location tags, etc.

[0029] According to some aspects, base station 103 may provide wireless coverage for cell 102, while base station 105 may provide wireless coverage for cell 104, which is contained within cell 102. In some other embodiments, cell 102 may partially overlap with cell 104. Cells 102 and 104 may be macrocells, picocells, femtocells, and / or another type of cell. In contrast, macrocells can cover relatively large geographic areas, such as a radius of several kilometers, while femtocells can cover relatively small geographic areas, such as a home, and the area covered by a picocell is smaller than the area covered by a macrocell but larger than the area covered by a femtocell. For example, cell 102 may be a macrocell, while cell 104 may be a picocell or a femtocell. Alternatively, cell 102 may be a picocell, while cell 104 may be a femtocell. In some examples, the geographic area of ​​the cell may shift depending on the location of the mobile base station. In some examples, base stations 103 and 105 can be interconnected with each other and / or interconnected to other base stations or network nodes in the network via various types of backhaul interfaces (such as direct physical connections, virtual networks, etc.) (not shown). In some implementations, wireless system 100 can be a wireless system with carrier aggregation. For UE 101, cell 102 can be the primary cell, and cell 104 can be the secondary cell. Other types of cells can exist, such as in Figure 1 Primary and secondary cells are not shown in the text.

[0030] According to some aspects, it can be based on, such as Figure 2 The block diagram shown implements UE 101. (Reference) Figure 2 UE 101 may have an antenna panel 217 comprising one or more antenna elements to form various transmission beams, such as beam 213, which are coupled to transceiver 203 and controlled by processor 209. Transceiver 203 and antenna panel 217 (using beam 213) may be configured to enable wireless communication in a wireless network. Specifically, transceiver 203 may include radio frequency (RF) circuitry 216, transmitting circuitry 212, and receiving circuitry 214. RF circuitry 216 may include multiple parallel RF chains for performing one or more of the transmitting or receiving functions, each RF chain being connected to one or more antenna elements in the antenna panel. Additionally, processor 209 may be communicatively coupled to memory 201, which is further coupled to transceiver 203. Various data may be stored in memory 201.

[0031] In some examples, memory 201 may store configuration 121, which may include power control mode 123 and timeline measurement 125 related to PUSCH transmission. Configuration 121 may be received from base station 103 to configure UE 101 to support power control mode 123 and timeline measurement 125. Additionally, memory 201 may store a TPC command set 131, which may include valid TPC commands 133 of the TPC command set and valid delays 135 of the valid TPC commands 133 based on timeline measurement 125. Memory 201 may store information about TDW 141 and multiple PUSCH transmissions (e.g., PUSCH transmissions 143 and 145 transmitted to base station 101 during TDW 151).

[0032] In some implementations, the TPC command set 131 may include TPC commands scheduled by a DCI for a group of UEs including UE 101 or by a PDCCH for UE 101. In some implementations, the power control mode 123 may be configured as a cumulative power control mode or an absolute power control mode. In some implementations, the timeline measurement 125 may be determined based on the interval between two adjacent PUSCH transmissions within the TDW, between a PDCCH and a PUSCH transmission immediately adjacent to and scheduled by that PDCCH, or between a PUSCH transmission and a time instance configured by the configuration authorization of that PUSCH transmission. In some implementations, the processor 209 may be configured to report to the base station 101 the ability of UE 101 to support the timeline measurement 125 related to PUSCH transmissions.

[0033] In some implementations, memory 201 may include instructions that, when executed by processor 209, perform the operations described herein, for example, Figure 3 The process 300 described herein is for implementing the TPC command set 131 during TDW 141. Alternatively, the processor 209 may be "hard-coded" to perform the uplink transmit beam selection function described herein.

[0034] Figure 3 The following illustrates a process 300 performed by the UE for implementing a TPC command set during TDW, according to some aspects of this disclosure. According to some aspects, such as Figure 3 As shown, process 300 can be executed by UE 101 or processor 209.

[0035] At point 301, UE 101 can receive configuration from the base station to configure the UE to support power control modes and timeline measurements related to PUSCH transmission. For example, as Figure 1As shown, UE 101 can receive configuration 121 from base station 103 to configure UE 101 to support power control mode 123 and timeline measurement 125 related to PUSCH transmission. More details of an example of timeline measurement 125 are provided in... Figures 4A to 4F As shown in the image.

[0036] At 303, UE 101 can transmit the first PUSCH transmission during TDW, which includes multiple PUSCH transmissions. For example, as Figure 1 As shown, UE 101 can transmit PUSCH transmission 143 during TDW 141, which includes multiple PUSCH transmissions. More details on examples of TDW including multiple PUSCH transmissions are available in [link to documentation]. Figures 4A to 4F As shown in the image.

[0037] At point 305, UE 101 can receive a set of TPC commands during TDW. For example, as Figure 1 As shown, UE 101 can receive TPC command set 131 during TDW 141. More details on examples of TPC command sets received during TDW are available in... Figures 4A to 4F As shown in the image.

[0038] At point 306, UE 101 can determine whether a TPC command in the TPC command set meets time constraints based on timeline measurements. For example, as Figure 1 As shown, UE 101 can determine whether a TPC command in the TPC command set 131 satisfies a time constraint based on timeline measurement 125. More details on examples of determining TPC commands that satisfy time constraints based on timeline measurement are provided in... Figures 4A to 4F As shown in the image.

[0039] At 307, UE 101 can determine the valid TPC commands in the TPC command set based on one or more TPC commands that satisfy the time constraint. For example, such as Figure 1 As shown, UE 101 can determine the valid TPC command 133 of TPC command set 131 based on one or more TPC commands that satisfy time constraints. More details on examples of determining the valid TPC commands of a TPC command set are provided in [link to documentation]. Figures 4A to 4F As shown in the image.

[0040] At point 308, UE 101 can determine the effective delay of a valid TPC command based on timeline measurements. For example, as Figure 1 As shown, UE 101 can determine the effective delay 135 of a valid TPC command 133 based on timeline measurement 125. More details of the example of determining the effective delay of a valid TPC command based on timeline measurement are available in [link to documentation]. Figures 4A to 4F As shown in the image.

[0041] At 309, UE 101 can apply a valid TPC command to a second PUSCH transmission determined based on the valid delay of the valid TPC command. For example, as Figure 1 As shown, UE 101 can apply a valid TPC command 133 to a PUSCH transmission 145 determined based on the valid delay 135 of the valid TPC command 133. Further details of an example of applying a valid TPC command to a second PUSCH transmission determined based on the valid delay of the valid TPC command are provided in [the relevant section]. Figures 4A to 4F As shown in the image.

[0042] Figures 4A to 4F An exemplary specific implementation of a TPC command set performed by UE 101 during TDW is shown, according to some aspects of this disclosure.

[0043] Figure 4A An exemplary specific implementation of a TPC command set executed by UE 101 during TDW 411 is shown. TDW 411 includes PUSCH1, PUSCH2, PUSCH3, and PUSCH4. PUSCH1 may be referred to as the first repetition of TDW 411, PUSCH2 as the second repetition of TDW 411, PUSCH3 as the third repetition of TDW 411, and PUSCH4 as the fourth repetition of TDW 411. TDW 412 is a subsequent TDW following TDW 411 and includes PUSCH5, PUSCH6, PUSCH7, and PUSCH8. In some implementations, PUSCH1, PUSCH2, PUSCH3, PUSCH4, PUSCH5, PUSCH6, PUSCH7, and PUSCH8 may be configuration-authorized PUSCHs without uplink (UL) authorization, such as PUSCH configuration authorization type 1. Therefore, TDW 411 and TDW 412 can be referred to as Configuring TDW.

[0044] In some implementations, the TPC command set may include TPC command 413 (δ) A ) and TPC command 414 (δ B Both are scheduled by a DCI for a group of UEs including UE 101. In some implementations, TPC command 413 or TPC command 414 is scheduled by a DCI of DCI format 2_2, which may be referred to as a group common TPC command.

[0045] In some implementations, UE 101 can be configured in cumulative power control mode. The effective TPC command 415 of the TPC command set within TDW 411 (which includes TPC command 413 and TPC command 414) can be a new TPC command equivalent to the accumulation of all TPC commands in the TPC command set that satisfy the time constraints. For example, if TPC command 413 indicates an increase of 3dB in the power of UE 101, and TPC command 414 indicates an increase of 2dB in the power of UE 101, then the effective TPC command 415 for TPC commands 413 and 414 would be an increase of 5dB = 3dB + 2dB in the power of the UE.

[0046] In some implementations, UE 101 may accumulate TPC commands without making them effective during the current configured TDW. Therefore, TPC commands 413 and 414 are not effective within TDW 411. Thus, if a TPC command satisfies the TPC application timeline of the first transmission after TDW, a valid TPC command 415 becomes effective after the current configured TDW 411. Therefore, valid TPC command 415 can be effective during TDW 412 (i.e., the subsequent TDW after TDW 411) and is applied to PUSCH5, PUSCH6, PUSCH7, and PUSCH8 within TDW 412.

[0047] In some implementations, for a PUSCH configuration license type 1 PUSCH transmission without UL authorization, the timeline measurement 416 related to the PUSCH transmission can be represented as K. PUSCH (1) is the time difference between the start symbol of the PUSCH transmission and the time instance of the configuration authorization configuration transmitted by the PUSCH. Timeline measurement 416 can be used to determine the TPC command application timeline, e.g., which time slot the TPC command will be applied to. This timeline measurement 416 can follow the same guidelines in Rel-15 regarding the configuration authorization timeline. In some implementations, K PUSCH (1) can be K PUSCH，min The number of symbols, which is equal to the product of the number of symbols per time slot (which can be 14 symbols) and the minimum value provided by K2 in PUSCH-ConfgCommon, for example, K PUSCH (1) = K2 * 14 symbols. Additionally, the timeline measurement 417 can be determined based on the interval between two adjacent PUSCH emissions within the TDW (e.g., between the middle symbol of PUSCH1 and the start symbol of PUSCH2), denoted as K. PUSCH (2). Similarly, K can be defined for x = 3, 4, 5, 6, 7, 8. PUSCH (x). In some implementations, K PUSCH (x) can be equal to KPUSCH (1).

[0048] In some implementations, TDW 411 is followed by TDW 412, and TPC command 413 (δ) A ) and TPC command 414 (δ B This is received in TDW 4111 but will not be applied in TDW 411. Additionally, TPC command 413 (δ) A ) or TPC command 414 (δ B Satisfying timeline-based measurements such as K PUSCH (4) and K PUSCH (5) Time constraints. For example, TPC command 413 (δ A ) and TPC command 414 (δ B All are received within the accumulation window 418 represented by T_TDW2, which starts from K of TDW 411. PUSCH (1) Start, to K of TDW 412 PUSCH (5). Therefore, a valid TPC command 415, which is equivalent to TPC command 413 (δ), can be applied to PUSCH5, PUSCH6, PUSCH7 and PUSCH8 in TDW 412. A ) and TPC command 414 (δ B The effective delay of a valid TPC command 415 can be defined as the time difference between PUSCH5 and the endpoint of a reference time point such as the cumulative window 418.

[0049] Figure 4B An exemplary specific implementation of a TPC command set executed by UE 101 during TDW 421 is shown. TDW 421 includes PUSCH1, PUSCH2, PUSCH3, and PUSCH4. In some implementations, PUSCH1, PUSCH2, PUSCH3, and PUSCH4 may be configuration-authorized PUSCHs without UL authorization, such as PUSCH configuration authorization type 1.

[0050] In some implementations, the TPC command set may include TPC command 423 (δ) A ) and TPC command 425 (δ C Both are scheduled by a DCI for a group of UEs including UE 101. In some embodiments, TPC commands 423 and 425 are scheduled by a DCI of DCI format 2_2 as a group common TPC command. Additionally, the TPC command set may include TPC command 424 (δ) scheduled by a PDCCH for UE 101. BThe PDCCH can be further scheduled to transmit PUSCH after or outside of TDW 421, for example, PUSCH5.

[0051] In some implementations, UE 101 may be configured in cumulative power control mode. Valid TPC command 422 of the TPC command set within TDW 421 (which includes TPC command 423, TPC command 424, and TPC command 425) may be a new TPC command that is equivalent to the accumulation of all TPC commands in the TPC command set that satisfy the time constraints.

[0052] In some implementations, the timeline measurement 426 related to PUSCH transmission can be represented as K. PUSCH (1) is the time difference between the PUSCH transmission and the time instance of the configuration authorized configuration transmitted by the PUSCH. Additionally, the timeline measurement 427 can be determined based on the interval between two adjacent PUSCH transmissions within the TDW (e.g., between PUSCH1 and PUSCH2), denoted as K. PUSCH (2). Similarly, K can be defined for x = 3 and 4. PUSCH (x). In some implementations, K PUSCH (2) K PUSCH (3) and K PUSCH (4) can be equal to K PUSCH (1). Additionally, timeline measurement 429 can be based on TPC command 424 (δ). B The interval between the PDCCH and the PUSCH5 transmission immediately following it and scheduled by the PDCCH is determined. The PDCCH can schedule more than one PUSCH, such as PUSCH5 and other PUSCH transmissions following PUSCH5 (not shown). Additionally, TDW 421 may include other PUSCH transmissions between the PDCCH and PUSCH5, such as PUSCH3 and PUSCH4, where PUSCH3 and PUSCH4 are not scheduled by the PDCCH.

[0053] In some implementations, the time constraint can be shown as an accumulation window 428 based on timeline measurement 429. TPC commands 423 and 424 satisfy the time constraint shown as an accumulation window 428 based on timeline measurement 429. However, TPC command 425 is outside the accumulation window 428 based on timeline measurement 429. The effective TPC command 422 of the TPC command set within TDW 421 (which includes TPC command 423, TPC command 424, and TPC command 425) is equivalent to the accumulation of TPC commands 423 and 424, since only TPC commands 423 and 424 satisfy the time constraint. Therefore, for PUSCH transmit power determination, applying δA and δ B Because both TPC commands are within the cumulative window, and δ C It can be used outside the window and in PUSCH after PUSCH5, but not in PUSCH5 itself.

[0054] Figure 4C An exemplary specific implementation of a TPC command set executed by a UE during TDW 431 is shown. TDW 431 includes PUSCH1, PUSCH2, PUSCH3, and PUSCH4. In some implementations, PUSCH1, PUSCH2, PUSCH3, and PUSCH4 may be configuration-authorized PUSCHs with UL authorization scheduled by PDCCH 435, such as PUSCH configuration authorization type 2. The TPC command set may include TPC command 433(δ) scheduled by a DCI for a group of UEs including UE 101, such as a DCI scheduled by DCI format 2_2. A In some implementations, UE 101 may be configured in cumulative power control mode. Valid TPC command 432 of the TPC command set within TDW 431 (which includes TPC command 433) may be a new TPC command that is equivalent to the accumulation of all TPC commands in the TPC command set that satisfy the time constraints.

[0055] In some implementations, the timeline measurement 436 related to PUSCH transmission can be represented as K. PUSCH (1), which is the time difference between PUSCH1 transmission and PDCCH 435. PUSCH (1) This can be the number of symbols following the last symbol received by the corresponding PDCCH and preceding the first symbol transmitted by the PUSCH. Additionally, the timeline measurement 437 can be determined based on the interval between two adjacent PUSCH transmissions within the TDW (e.g., between PUSCH1 and PUSCH2), denoted as K. PUSCH (2). Similarly, K can be defined for x = 3 and 4. PUSCH (x). In some implementations, K PUSCH (2) K PUSCH (3) and K PUSCH (4) can be equal to K PUSCH (1).

[0056] Figure 4DAn exemplary specific implementation of a TPC command set executed by a UE during TDW 441 is shown. TDW 441 includes PUSCH1, PUSCH2, PUSCH3, and PUSCH4. In some implementations, PUSCH1, PUSCH2, PUSCH3, and PUSCH4 may be configuration-authorized PUSCHs with UL authorization scheduled by PDCCH 445, such as PUSCH configuration authorization type 2. The TPC command set may include TPC command 443 (δ) scheduled by DCI for a group of UEs including UE 101, such as DCI format 2_2. A In some implementations, UE 101 may be configured in cumulative power control mode. Valid TPC command 442 of the TPC command set within TDW 441 (which includes TPC command 443) may be a new TPC command that is equivalent to the accumulation of all time-constrained TPC commands in the TPC command set.

[0057] In some implementations, the timeline measurement 446 related to PUSCH transmission can be represented as K. PUSCH (1) This can be the time difference between the PUSCH1 emission and the time instance 448 configured by the configuration authorization. In some implementations, K PUSCH (1) can be K PUSCH，min The number of symbols, which is equal to the product of the number of symbols per slot, such as 14, and the minimum value provided by K2 in PUSCH-ConfgCommon, for example, K PUSCH (1) = K2 * 14 symbols. Additionally, the timeline measurement 447 can be determined based on the interval between two adjacent PUSCH emissions within the TDW (e.g., between PUSCH1 and PUSCH2), denoted as K. PUSCH (2). Similarly, K can be defined for x = 3 and 4. PUSCH (x). In some implementations, K PUSCH (2) K PUSCH (3) and K PUSCH (4) can be equal to K PUSCH (1).

[0058] Figure 4EAn exemplary specific implementation of a TPC command set executed by the UE during TDW 451 is shown. TDW 451 includes PUSCH1, PUSCH2, PUSCH3, and PUSCH4. In some implementations, PUSCH1, PUSCH2, PUSCH3, and PUSCH4 may be configuration-authorized PUSCHs with UL authorization scheduled by PDCCH 455, such as PUSCH configuration authorization type 2. The TPC command set includes TPC command 453 (δ) scheduled by DCI for a group of UEs including UE 101, such as DCI format 2_2. A In some implementations, UE 101 may be configured in cumulative power control mode. Valid TPC command 452 of the TPC command set within TDW 451 (which includes TPC command 453) may be a new TPC command that is equivalent to the accumulation of all TPC commands in the TPC command set that satisfy the time constraints.

[0059] In some implementations, the timeline measurement 456 related to PUSCH transmission can be represented as K. PUSCH (1) is the time difference between the transmissions of PDCCH 455 and PUSCH1, which is immediately adjacent to PDCCH 455 and scheduled by PDCCH 455. Specifically, K... PUSCH (1) can be the number of symbols after the last symbol received by the corresponding PDCCH 455 and before the first symbol transmitted by PUSCH1.

[0060] Additionally, timeline measurement 457 can be determined based on the interval between two adjacent PUSCH emissions within the TDW (e.g., between PUSCH1 and PUSCH2), denoted as K. PUSCH (2). Similarly, K can be defined for x = 3 and 4. PUSCH (x). In some implementations, K PUSCH (3) and K PUSCH (4) can be equal to K PUSCH (2), which may be different from K PUSCH (1). In some implementation schemes, K PUSCH (2) can be K PUSCH，min The number of symbols, which is equal to the product of the number of symbols per slot, such as 14, and the minimum value provided by K2 in PUSCH-ConfgCommon, for example, K. PUSCH (2) = K2 * 14 symbols.

[0061] Figure 4C , Figure 4D and Figure 4EThe implementation shown has different methods for configuring timeline measurements, which can be indicated by configuration 121. Configuration 121 can be configured via RRC signaling from base station 103 to indicate what can be applied by UE 101. Figure 4C , Figure 4D and Figure 4E Which of these situations applies? Furthermore, different timeline measurements can lead to different effective delays for valid TPC commands, such as... Figures 4C to 4E As shown.

[0062] Figure 4F An exemplary specific implementation of a TPC command set executed by the UE during TDW 461 is shown. TDW 461 includes PUSCH1, PUSCH2, PUSCH3, and PUSCH4. In some implementations, PUSCH1, PUSCH2, PUSCH3, and PUSCH4 may be configuration-authorized PUSCHs with UL authorization scheduled by PDCCH 465, such as PUSCH configuration authorization type 2. In some other implementations, PUSCH1, PUSCH2, PUSCH3, and PUSCH4 may be configuration-authorized PUSCH type 1 without UL authorization. In some implementations, UE 101 may be configured in cumulative power control mode.

[0063] The TPC command set includes TPC command 463 (δ) for DCI scheduling of a group of UEs including UE 101, such as DCI scheduling by DCI format 2_2. A For both PUSCH configuration authorization types 1 and 2, if the UE receives a group common TPC command, such as TPC command 463 (δ), in TDW 461 A If this occurs, UE 101 can consider it an event leading to inconsistent transmit power and phase discontinuity, therefore DMRS is bundled and interrupted in TDW 461. TPC command 463 (δ A In K PUSCH (3) was previously launched, therefore TPC command 463 (δ) A This can be applied to PUSCH3. The TWD 461, which can be referred to as the nominal TWD at the time slot, can be divided into two actual TDWs: a first actual TDW including PUSCH1 and PUSCH2, and a second actual TDW including PUSCH3 and PUSCH4, wherein PUSCH3 and PUSCH4 in the second actual TDW are based on TPC command 463 (δ). A It is certain.

[0064] In some implementations, the timeline measurement 466 related to PUSCH transmission can be represented as K. PUSCH(1) is the time difference between PDCCH 465 and PUSCH1, which is immediately adjacent to PDCCH 465 and scheduled by PDCCH 465. In detail, timeline measurement 466 can be defined as the time difference between the last symbol of PDCCH 465 and the first symbol of PUSCH1.

[0065] Additionally, timeline measurement 467 can be determined based on the interval between two adjacent PUSCH emissions within the TDW (e.g., between PUSCH1 and PUSCH2), denoted as K. PUSCH (2). Similarly, K can be defined for x = 3 and 4. PUSCH (x). In some implementations, K PUSCH (3) and K PUSCH (4) can be equal to K PUSCH (2), which may be different from K PUSCH (1). In some implementation schemes, K PUSCH (2) can be K PUSCH，min The number of symbols, which is equal to the product of the number of symbols per slot, such as 14, and the minimum value provided by K2 in PUSCH-ConfgCommon, for example, K. PUSCH (2) = K2*14 symbols. Different configurations of timeline measurements, such as timeline measurement 466 or timeline measurement 467, can be indicated by configuration 121. Configuration 121 can be configured by RRC signaling from base station 103 to UE 101.

[0066] In some implementations, other methods may exist to implement configuration 121 for UE 101. In some implementations, PUSCH transmissions in the TDW can be scheduled via dynamic authorization. The specific implementation of the TPC command set in such a TDW can be similar to the specific implementation of TPC commands in a configured TDW, wherein PUSCH transmissions are configured rather than dynamically authorized. If UE 101 receives a TPC command set in a TDW that includes PUSCH transmissions scheduled by dynamic authorization, UE 101 may accumulate the TPC command set without making it effective during the current configured TDW. If the TPC commands satisfy the TPC application timeline of the first transmission after the TDW, the TPC command set may become effective after the current configured TDW.

[0067] In some implementations, UE 101 may report its ability to support UL power control. In some implementations, UE 101 may determine that a group TPC command cannot be applied to every PUSCH repetition and report this to base station 103, thus ensuring that PUSCH transmissions maintain the same power for all repetitions. In some other implementations, UE 101 may report to base station 103 that UE 101 can use K... PUSCH(1) Applied to each PUSCH emission as a timeline measurement. In some implementations, K PUSCH (i) can be K PUSCH，min The number of symbols. Configuration 121 can be configured by RRC signaling from base station 103 to indicate which timeline measurement (e.g., K) is performed. PUSCH (1) or K PUSCH (i) is repeatedly associated with PUSCH.

[0068] In some implementations, for PUSCH transmissions within a dynamically licensed TDW, group common TPC commands within the TDW can be considered events leading to inconsistent transmit power and phase discontinuities, thus causing DMRS bundle interruptions. Therefore, a similar set of group common TPC commands scheduled in DCI format can be implemented across multiple actual TDWs within the TDW.

[0069] In some implementations, for PUSCH transmissions in a TDW scheduled by dynamic granting or configuration granting, UE 101 may report the ability to apply group common TPC commands during DMRS bundling, utilizing either cumulative power control mode or absolute power control mode. If UE 101 does not support this capability, in some implementations, UE 101 does not expect to receive group common TPC commands during DMRS bundling. Determining whether a group common TPC command is sent to UE 101 depends on base station 103. If base station 103 intends to gain DMRS bundling gain, a TPC command will not be sent. In some implementations, if base station 103 deems transmit power adjustment important and urgent, a group common TPC command may be sent. UE 101 may adjust transmit power based on the TPC command without maintaining power consistency within the TDW.

[0070] In some implementations, UE 101 may assume that the value of the TPC command in the group common TPC command is 0dB. The cumulative TPC command or the last absolute TPC command may be applied to the PUSCH transmission after repetition. In some implementations, when it is difficult to disable the transmission of TPC commands in DCI format 2_2 for a UE configured with DMRS bundling, UE 101 may assume that the value of the TPC command in the group common TPC command is 0dB. In some implementations, UE 101 may ignore or discard the group common TPC command, and UE 101 may not change the transmit power during DMRS bundling.

[0071] In some implementations, UE 101 may utilize DMRS bundling to perform absolute power control and operate in absolute power control mode. The latest TPC command that takes effect within the configured TDW will supersede all previous TPC commands that take effect within that configured TDW. Therefore, if a TPC command satisfies the TPC application timeline of the first transmission after the TDW, only the last TPC command is applied by the UE after the current configured TDW. If subsequent PUSCH transmissions are scheduled via DCI, the dynamically authorized PUSCH timeline can be applied to determine the number of symbols from PDCCH to PUSCH. If the subsequent PUSCH transmission is another TDW, the timeline measurement can be determined by the various mechanisms disclosed in this specification. In some implementations, K PUSCH (2) can be K PUSCH，min The number of symbols.

[0072] One or more computer systems (such as...) can be used, for example. Figure 5 The computer system 500 shown herein implements various aspects. The computer system 500 can be any computer capable of performing the functions described herein, such as the operations described for processor 209 or process 300, as... Figure 1 and Figure 2 The UE 101, base station 103 or base station 105 shown, and further in Figures 4A to 4F As shown in the diagram. Computer system 500 includes one or more processors (also referred to as central processing units or CPUs), such as processor 504. Processor 504 is connected to communication infrastructure 506 (e.g., a bus). Computer system 500 also includes user input / output devices 503, such as a monitor, keyboard, pointing device, etc., that communicate with communication infrastructure 506 via user input / output interface 502. Computer system 500 also includes main memory or primary memory 508, such as random access memory (RAM). Main memory 508 may include one or more levels of cache. Main memory 508 stores control logic components (e.g., computer software) and / or data.

[0073] The computer system 500 may also include one or more auxiliary storage devices or memories 510. Auxiliary storage 510 may include, for example, a hard disk drive 512 and / or a removable storage device or drive 514. The removable storage drive 514 may be a floppy disk drive, tape drive, optical disk drive, optical storage device, tape backup device, and / or any other storage device / drive.

[0074] Removable storage drive 514 can interact with removable storage unit 518. Removable storage unit 518 includes a computer-usable or readable storage device on which computer software (control logic components) and / or data are stored. Removable storage unit 518 can be a floppy disk, magnetic tape, optical disc, DVD, optical storage disk, and / or any other computer data storage device. Removable storage drive 514 reads from and / or writes to removable storage unit 518 in a well-known manner.

[0075] According to some aspects, auxiliary storage 510 may include other means, tools, or other methods for allowing computer programs and / or other instructions and / or data to be accessed by computer system 500. Such means, tools, or other methods may include, for example, removable storage unit 522 and interface 520. Examples of removable storage unit 522 and interface 520 may include program boxes and box interfaces (such as those found in video game devices), removable memory chips (such as EPROM or PROM) and associated sockets, memory sticks and USB ports, memory cards and associated memory card slots, and / or any other removable storage unit and associated interface.

[0076] In some examples, main memory 508, removable storage unit 518, and removable storage unit 522 can store instructions that, when executed by processor 504, cause processor 504 to perform actions targeting the UE or base station (e.g., such as...). Figure 1 and Figure 2 The operation of the UE 101, base station 103, or base station 105 shown is for the operation described for the processor 209 or process 300, and further in Figures 4A to 4F As shown in the image.

[0077] Computer system 500 may also include a communication or network interface 524. Communication interface 524 enables computer system 500 to communicate and interact with any combination of remote devices, remote networks, remote entities, etc. (individually and collectively referred to by reference numeral 528). For example, communication interface 524 may allow computer system 500 to communicate with remote device 528 via communication path 526, which may be wired and / or wireless, and may include any combination of LAN, WAN, Internet, etc. Control logic components and / or data may be transmitted to and from computer system 500 via communication path 526. Operation of communication interface 524 may be performed by a wireless controller and / or a cellular controller. The cellular controller may be a separate controller to manage communications according to different wireless communication technologies. The operations in the foregoing aspects can be implemented in various configurations and architectures. Therefore, some or all of the operations in the foregoing aspects may be performed in hardware, software, or both. In some aspects, tangible, non-transitory devices or articles of art include tangible, non-transitory computer-usable or readable media on which control logic components (software) are stored, also referred to herein as computer program products or program storage devices. This includes, but is not limited to, computer system 500, main memory 508, secondary memory 510, and removable storage units 518 and 522, and tangible articles embodying any combination thereof. Such control logic components, when executed by one or more data processing devices (such as computer system 500), cause such data processing devices to operate as described herein.

[0078] Based on the teachings contained in this disclosure, it will be apparent to those skilled in the art how to use [other methods]. Figure 5 Other data processing devices, computer systems, and / or computer architectures besides those shown may be used to make and use aspects of this disclosure. In particular, aspects may operate in conjunction with software, hardware, and / or operating system implementations other than those described herein.

[0079] It should be understood that the Detailed Description section, rather than the Summary and Abstract section, is intended to be used to interpret the claims. The Summary and Abstract section may set forth one or more, but not all, exemplary aspects of this disclosure as contemplated by the inventors, and is therefore not intended to limit this disclosure or the appended claims in any way.

[0080] Although this disclosure has been described herein with reference to exemplary aspects of exemplary fields and applications, it should be understood that this disclosure is not limited thereto. Other aspects and modifications are possible and are within the scope and spirit of this disclosure. For example, and without limiting the generality of this paragraph, the aspects are not limited to the software, hardware, firmware, and / or entities shown in the figures and / or described herein. Furthermore, the aspects (whether explicitly described herein or not) have significant utility for fields and applications beyond those described herein.

[0081] The aspects have been described here using functional building blocks that illustrate specific implementations of functions and their relationships. For ease of description, the boundaries of these functional building blocks have been arbitrarily defined herein. Alternative boundaries may be defined as long as the specified functions and relationships (or their equivalents) are performed appropriately. Furthermore, alternative aspects may perform functional blocks, steps, operations, methods, etc., in an order different from that described herein.

[0082] References to “an implementation,” “implementation,” “exemplary implementation,” or similar phrases herein indicate that the described implementation may include specific feature structures, structures, or characteristics, but each implementation may not necessarily include such feature structures, structures, or characteristics. Furthermore, such terminology does not necessarily refer to the same implementation. Additionally, when a specific feature, structure, or characteristic is described in connection with an implementation, whether or not it is explicitly mentioned or described herein, the integration of such feature, structure, or characteristic into other aspects is within the knowledge of a person skilled in the art.

[0083] The breadth and scope of this disclosure should not be limited by any of the foregoing exemplary aspects, but should be defined solely by the following claims and their equivalents.

[0084] For one or more embodiments or examples, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods as described in the Examples section below. For example, circuitry associated with one or more of the threaded devices, routers, network elements, etc., described above in conjunction with the foregoing figures may be configured to operate according to one or more of the examples shown in the Examples section below.

[0085] This disclosure assumes that entities responsible for collecting, analyzing, disclosing, transmitting, storing, or otherwise using such personal information data will comply with established privacy policies and / or privacy practices. Specifically, such entities should implement and adhere to privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as data collection and / or use change. Personal information from users should be collected for the entity's lawful and reasonable purposes and not shared or sold outside of these lawful uses. Furthermore, such collection / sharing should only occur upon receiving informed consent from users. Additionally, such entities should consider taking any necessary steps to protect and safeguard access to such personal information data and ensure that others with access to such personal information data comply with their privacy policies and processes. Furthermore, such entities may be subject to third-party evaluations to demonstrate their compliance with widely accepted privacy policies and practices. Additionally, policies and practices should be adapted to the specific types of personal information data collected and / or accessed, and to applicable laws and standards, including specific considerations regarding jurisdiction. For example, in the United States, the collection or access to certain health data may be governed by federal and / or state laws, such as the Health Insurance Transfer and Accountability Act (HIPAA); while in other countries, health data may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy practices should be maintained for different types of personal data in each country.

Claims

1. A method for performing wireless communication by a user equipment (UE), the method comprising: Receive configuration from the base station to configure the UE to support power control modes and timeline measurements related to Physical Uplink Shared Channel (PUSCH) transmission; The first PUSCH transmission is transmitted during a time-domain window (TDW) that includes multiple PUSCH transmissions; During the TDW, a set of transmit power control (TPC) commands is received; Based on the timeline measurement, determine whether the TPC commands in the TPC command set meet the time constraints; The valid TPC commands of the TPC command set are determined based on one or more TPC commands that satisfy the time constraints. The effective delay of the valid TPC command is determined based on the timeline measurement. as well as The valid TPC command is applied to the second PUSCH transmission determined based on the valid delay of the valid TPC command.

2. The method of claim 1, wherein the TPC command set includes TPC commands scheduled by downlink control information (DCI) for a group of UEs including the UE, or TPC commands scheduled by physical downlink control channel (PDCCH) for the UE.

3. The method of claim 1, wherein the timeline measurement is determined based on the interval between two adjacent PUSCH transmissions within the TDW, between the Physical Downlink Control Channel (PDCCH) and a PUSCH transmission adjacent to the PDCCH and scheduled by the PDCCH, or between a PUSCH transmission and a time instance of the configuration authorization configuration of the PUSCH transmission.

4. The method of claim 1, wherein the power control mode is configured as a cumulative power control mode or an absolute power control mode.

5. The method of claim 4, wherein the power control mode is configured as the cumulative power control mode, the effective TPC command includes the accumulation of all TPC commands in the TPC command set that satisfy the time constraint, the second PUSCH transmission occurs in a subsequent TDW after the TDW, and a first timeline measurement relating to the first PUSCH transmission in the TDW and a second timeline measurement relating to the second PUSCH transmission in the subsequent TDW have the same value.

6. The method of claim 4, wherein the power control mode is configured as the cumulative power control mode, the TPC command is scheduled by the physical downlink control channel (PDCCH) for the UE, the first PUSCH transmission is a configuration grant type without uplink grant, the second PUSCH transmission is outside the TDW, a first timeline measurement related to the first PUSCH transmission within the TDW and a third timeline measurement related to the third PUSCH transmission within the TDW have the same value, a second timeline measurement related to the second PUSCH transmission is determined by the PDCCH that schedules the second PUSCH transmission, and the valid TPC command includes the accumulation of all TPC commands in the TPC command set that satisfy the time constraint based on the second timeline measurement.

7. The method of claim 4, wherein the power control mode is configured as the cumulative power control mode, the TPC command is scheduled by downlink control information (DCI) for a group of UEs including the UE, the first PUSCH transmission is configured with a license type, the first PUSCH transmission is in a first actual TDW, the second PUSCH transmission is in a second actual TDW within the TDW, and a first timeline measurement relating to the first PUSCH transmission in the first actual TDW and a second timeline measurement relating to the second PUSCH transmission in the second actual TDW have the same value.

8. The method of claim 4, wherein the power control mode is configured as the cumulative power control mode, the first PUSCH transmission is dynamically authorized, the valid TPC commands of the TPC command set include the accumulation of all TPC commands in the TPC command set that satisfy the time constraint, the second PUSCH transmission is outside the TDW, and a first timeline measurement related to the first PUSCH transmission within the TDW and a second timeline measurement related to the second PUSCH transmission outside the TDW have the same value.

9. The method of claim 4, wherein the power control mode is configured as the cumulative power control mode or the absolute power control mode, the TPC command is scheduled by downlink control information (DCI) for a set of UEs including the UE, and the valid TPC command of the TPC command set is determined by considering the TPC command scheduled by the DCI.

10. The method of claim 4, wherein the power control mode is configured as the absolute power control mode, the valid TPC command includes the most recently received TPC command in the TPC command set that satisfies the time constraint, and the second PUSCH is transmitted outside the TDW.

11. The method of claim 4, wherein the power control mode is configured as the cumulative power control mode or the absolute power control mode, the TPC command is scheduled by downlink control information (DCI) for a group of UEs including the UE, and the TPC command is not applied to the first PUSCH transmission or the second PUSCH transmission.

12. The method according to claim 1, further comprising: The UE reports to the base station its ability to support the timeline measurements related to PUSCH transmission.

13. A user equipment (UE), comprising: A transceiver configured to enable wireless communication with a base station via a wireless network; as well as A processor, communicatively coupled to the transceiver and configured to: Receive configuration from the base station to configure the UE to support power control modes and timeline measurements related to Physical Uplink Shared Channel (PUSCH) transmission; The first PUSCH transmission is transmitted during a time-domain window (TDW) that includes multiple PUSCH transmissions; Receive transmit power control (TPC) command set during the first TDW; Based on the timeline measurement, determine whether the TPC commands in the TPC command set meet the time constraints; The valid TPC commands of the TPC command set are determined based on one or more TPC commands that satisfy the time constraints. The effective delay of the valid TPC command is determined based on the timeline measurement. as well as The valid TPC command is applied to the second PUSCH transmission determined based on the valid delay of the valid TPC command.

14. The UE of claim 13, wherein the timeline measurement is determined based on the interval between two adjacent PUSCH transmissions within the TDW, between the Physical Downlink Control Channel (PDCCH) and a PUSCH transmission adjacent to the PDCCH and scheduled by the PDCCH, or between a PUSCH transmission and a time instance of a configuration authorization configuration of the PUSCH transmission.

15. The UE of claim 13, wherein the power control mode is configured as a cumulative power control mode or an absolute power control mode.

16. The UE of claim 15, wherein the power control mode is configured as the cumulative power control mode, the effective TPC command includes a new TPC command, the new TPC command being equivalent to the accumulation of all TPC commands in the TPC command set that satisfy the time constraint, and the second PUSCH is transmitted in a subsequent TDW after the TDW.

17. The UE of claim 15, wherein the power control mode is configured as the cumulative power control mode, the TPC command is scheduled by downlink control information (DCI) for a group of UEs including the UE, the first PUSCH transmission is configured with a license type, the first PUSCH transmission is in a first actual TDW, and the second PUSCH transmission is in a second actual TDW within the TDW.

18. The UE of claim 15, wherein the power control mode is configured as the cumulative power control mode, the first PUSCH transmission is of the dynamic grant type, the valid TPC commands of the TPC command set include new TPC commands, the new TPC commands being equivalent to the accumulation of all TPC commands in the TPC command set that satisfy the time constraint, and the second PUSCH transmission is outside the TDW.

19. A non-transitory computer-readable medium storing instructions that, when executed by a processor of a user equipment (UE), cause the UE to perform operations, the operations including: Receive configuration from the base station to configure the UE to support power control modes and timeline measurements related to Physical Uplink Shared Channel (PUSCH) transmission; The first PUSCH transmission is transmitted during a time-domain window (TDW) that includes multiple PUSCH transmissions; Receive transmit power control (TPC) command set during the first TDW; Based on the timeline measurement, determine whether the TPC commands in the TPC command set meet the time constraints; The valid TPC commands of the TPC command set are determined based on one or more TPC commands that satisfy the time constraints. The effective delay of the valid TPC command is determined based on the timeline measurement. as well as The valid TPC command is applied to the second PUSCH transmission determined based on the valid delay of the valid TPC command.

20. The non-transitory computer-readable medium of claim 19, wherein the TPC command set includes TPC commands scheduled by downlink control information (DCI) for a group of UEs including the UE, or by TPC commands scheduled by physical downlink control channel (PDCCH) for the UE.

Images