Terminal, wireless communication method, base station and system

Abstract

A terminal according to an embodiment of this disclosure includes: a controller that calculates, for a serving cell, each of a first pathloss in the last transmission of a power headroom report (PHR) and a second pathloss in the current new uplink transmission by determining whether the pathloss is based on physical uplink shared channel (PUSCH) transmission using one sounding reference signal resource indicator (SRI), PUSCH repetition transmission using multiple SRIs, or reference PUSCH transmission; and a transmitter that transmits a PHR medium access control (MAC) control element related to a PHR triggered on the basis of the first pathloss and the second pathloss. An embodiment of this disclosure makes it possible to properly perform a PHR report when MTRP PUSCH repetition is used.

Description

[Technical field]

[0001] The present disclosure relates to a terminal and a wireless communication method in a next-generation mobile communication system. 、 base station and systems Regarding. [Background technology]

[0002] In the Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) has been specified for the purpose of achieving higher data rates and lower latency (Non-Patent Document 1). In addition, LTE-Advanced (3GPP Rel. 10-14) has been specified for the purpose of achieving higher capacity and greater sophistication of LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9).

[0003] Successor systems to LTE (e.g., 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 or later, etc.) are also being considered. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010 Summary of the Invention [Problem to be solved by the invention]

[0005] In future wireless communication systems (e.g., NR), a user terminal (User Equipment (UE)) will transmit a Power Headroom Report (PHR) including information on the power headroom (PH) of each serving cell to a network. The network can use the PHR to control the uplink transmission power of the UE.

[0006] In NR, one or more transmission / reception points (TRPs) (multi-TRPs (MTRPs)) are considered to perform DL transmission to a UE. In addition, it is also considered that a UE performs UL transmission to one or more TRPs.

[0007] Furthermore, in future wireless systems (for example, NR after Rel. 17), repeated transmission of MTRP via a Physical Uplink Shared Channel (PUSCH) is being considered.

[0008] However, the current standard does not specify how to control the PHR for MTRP PUSCH repetition. If the PHR is not triggered / generated / transmitted appropriately, communication throughput and communication quality may be degraded.

[0009] Therefore, the present disclosure provides a terminal and a wireless communication method capable of appropriately performing PHR reporting when MTRP PUSCH repetition is used. 、 base station and systems One of the aims is to provide. [Means for solving the problem]

[0010] A terminal according to an embodiment of the present disclosure includes a control unit that determines whether a first path loss in a last transmission of a Power Headroom Report (PHR) and a second path loss in a current new uplink transmission are based on a Physical Uplink Shared Channel (PUSCH) transmission using one Sounding Reference Signal Resource Indicator (SRI), a PUSCH repeated transmission using multiple SRIs, or a reference PUSCH transmission, and calculates the first path loss and the second path loss for a certain serving cell, respectively; 、 and a transmitter for transmitting a Medium Access Control (MAC) control element. Effect of the Invention

[0011] According to one aspect of the present disclosure, PHR reporting can be appropriately performed when MTRP PUSCH repetition is used. [Brief description of the drawings]

[0012] [Figure 1] FIG. 1 is a diagram showing an example of a single-entry PHR MAC CE in Rel.16 NR. [Diagram 2] FIG. 2 is a diagram showing an example of a multiple entry PHR MAC CE in Rel.16 NR. [Diagram 3] 3A to 3C are diagrams illustrating an example of a single-entry PHR MAC CE in the first embodiment. [Figure 4] 4A to 4C are diagrams illustrating an example of a multiple entry PHR MAC CE in the first embodiment. [Diagram 5] FIG. 5 is a diagram illustrating an example of a multiple entry PHR MAC CE in the second embodiment. [Figure 6] FIG. 6 is a diagram showing an example of embodiment 3.1. [Figure 7]7A and 7B are diagrams showing an example of case A of embodiment 3.1. [Figure 8] 8A and 8B are diagrams showing an example of case B of embodiment 3.1. [Figure 9] FIG. 9 is a diagram showing an example of embodiment 3.2. [Figure 10] 10A and 10B are diagrams illustrating an example of the difference between embodiments 3.2a and 3.2b. [Figure 11] 11A and 11B show an example of case A of embodiment 3.2a. [Figure 12] 12A and 12B are diagrams showing an example of case B of embodiment 3.2. [Figure 13] FIG. 13 is a diagram showing another example of case B in embodiment 3.2. [Figure 14] FIG. 14 is a diagram illustrating an example of calculation of path loss variation for each TRP in case y7. [Figure 15] 15A and 15B are diagrams illustrating an example of control related to a prohibition timer according to the fifth embodiment. [Figure 16] FIG. 16 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 17] FIG. 17 is a diagram illustrating an example of the configuration of a base station according to an embodiment. [Figure 18] FIG. 18 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. [Figure 19] FIG. 19 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] (PHR) In future wireless communication systems (e.g., NR), a UE will transmit a Power Headroom Report (PHR) including information on the power headroom (PH) of each serving cell to the network. The network can use the PHR to control the uplink transmission power of the UE.

[0014] The PHR may be transmitted by Medium Access Control (MAC) signaling using a Physical Uplink Shared Channel (PUSCH). For example, the PHR is notified by using a PHR MAC Control Element (CE) included in a MAC Protocol Data Unit (PDU).

[0015] In NR, a single entry PHR MAC CE for a primary cell (PCell) is supported.

[0016] Figure 1 shows an example of a single-entry PHR MAC CE in Rel.16 NR. The MAC CE is composed of 2 octets (=16 bits). Each 'R' in Figure 1 indicates a reserved field of 1 bit, and is set to a value of '0', for example.

[0017] 1, 'PH(Type 1, PCell)' indicates a 6-bit field, which indicates an index for a type 1 PH of a primary cell (Primary Cell (PCell)). The index for the PH is associated with a specific PH value (in decibels (dB)) (or level).

[0018] For example, Type 1 PH may be a PH that takes into account the PUSCH (e.g., taking into account only the power of the PUSCH), Type 2 PH may be a PH that takes into account the PUCCH (e.g., taking into account the power of both the PUSCH and the PUCCH), and Type 3 PH may be a PH that takes into account the measurement reference signal (Sounding Reference Signal (SRS)) (e.g., taking into account the power of the PUSCH and the SRS).

[0019] 'P in Figure 1 CMAX,f,c ' indicates a 6-bit field, P used in the calculation of the PH field above. CMAX,f,c The index for the P CMAX,f,c The index for is associated with a specific UE transmit power level (dB). CMAX,f,c may be referred to as the configured maximum transmit power (maximum allowed transmit power) of the UE for serving cell c of carrier f. Hereinafter, P CMAX,f,c is simply P CMAX It can also be written as:

[0020] 'P' in FIG. 1 may be a field related to Power Management Maximum Power Reduction (P-MPR) or Maximum Permitted UE Output Power Reduction for the serving cell c, or may be a field related to Maximum Permitted Exposure (MPE). 'MPE' in FIG. 1 may be a field related to MPE. Fields such as 'P' and 'MPE' may be replaced with an 'R' field depending on the configuration using higher layer signaling to the UE.

[0021] In NR, multiple entry PHR MAC CE including multiple data similar to the above-mentioned single entry (2 octets) is also supported. The multiple entry PHR MAC CE may include a PH field for a Primary Secondary Cell (PSCell) and a Secondary Cell (SCell). Note that the PCell and PSCell may be called Special Cells (SpCells).

[0022] Figure 2 is a diagram showing an example of a multiple entry PHR MAC CE in Rel.16 NR. The description of the same fields as in Figure 1 will not be repeated. The 6-bit fields including the word 'PH' in Figure 2 indicate the PH field for the corresponding type (e.g., types 1-3 described above) and cell.

[0023] Note that the presence of the Type 2 PH field for the SpCell of another MAC entity may be set by the higher layer parameter phr-Type2OtherCell being true.

[0024] 'P in Figure 2 CMAX,c The 6-bit field containing the word ' is the P field used in the calculation of the previous PH field. CMAX,c P indicates CMAX,c It is a field. i ' is a field indicating whether the PH field of the serving cell corresponding to the serving cell index i is included in the PHR. Note that FIG. 2 shows the case where the maximum serving cell index is smaller than 8. If the maximum serving cell index is 8 or more, the MAC CE can indicate serving cells up to i=31, for example. i ' fields may be included.

[0025] In addition, the number and P CMAX,cThe number assigned to the field does not have to mean the serving cell index, and may simply mean the ordinal number of the value included in the MAC CE.

[0026] 'V' in FIG. 2 is a field that indicates whether the value of the PH corresponding to the immediately following PH field is based on real transmission (V=0) or on a reference format (V=1). A PH based on a reference format may be called a virtual PH. Note that when V=1, the corresponding 'P CMAX,c The ', 'MPE' fields etc. may be omitted.

[0027] The network may transmit PHR configuration information regarding the conditions for triggering the PHR to the UE. Here, the PHR configuration information may include, for example, a prohibit timer, a periodic timer, a path loss change threshold, etc. For the notification, higher layer signaling may be used. If the PHR trigger conditions are met, the UE triggers the PHR.

[0028] In the present disclosure, the higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, and the like, or a combination of these.

[0029] The MAC signaling may be, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. The broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.

[0030] (Multi-TRP) In NR, it is considered that one or more transmission / reception points (TRPs) (multi-TRPs (M-TRPs)) will perform DL transmission to a UE using one or more panels (multi-panels). It is also considered that a UE will perform UL transmission to one or more TRPs.

[0031] Meanwhile, in future wireless systems (e.g., NR after Rel. 17), it is being considered to indicate multiple (e.g., two) SRS resource indicators (SRIs) / transmitted precoding matrix indicators (TPMIs) using a single DCI for performing PUSCH repetition transmission of multiple TRPs (MTRP PUSCH repetition).

[0032] For example, the UE may determine a precoder for PUSCH transmission based on the SRI, a Transmitted Rank Indicator (TRI), and the TPMI in the case of codebook-based transmission. The UE may determine a precoder for PUSCH transmission based on the SRI in the case of non-codebook-based transmission. Note that the SRI may be specified to the UE by the DCI or may be provided by a higher layer parameter.

[0033] When a single DCI indicates multiple SRIs / TPMIs, either Option 1 or Option 2 below may be considered; Option 1: SRI / TPMI (values) for multiple (e.g., two) TRPs are indicated using multiple (e.g., two) SRI / TPMI indication fields; · Option 2: A field indicating one SRI / TPMI is specified, and code points corresponding to multiple (e.g., two) SRI / TPMI values ​​are set in the field indicating the SRI / TPMI.

[0034] In option 1, each code point of multiple SRI / TPMI fields may correspond to one TPMI value. The correspondence (association) between the SRI / TPMI fields and the SRI / TPMI values ​​may be defined in advance in the specifications. Furthermore, the correspondence (association) between the SRI / TPMI fields and the SRI / TPMI values ​​may use the correspondence defined up to Rel. 16, or may be the correspondence defined in Rel. 17 or later. The correspondence between the SRI / TPMI fields and the SRI / TPMI values ​​may be different for each of multiple SRI / TPMI fields.

[0035] In option 2, a code point indicating one SRI / TPMI field may correspond to multiple (e.g., two) SRI / TPMI values. The correspondence (association) between the SRI / TPMI field and the SRI / TPMI value may be defined in advance in a specification, or may be notified / configured / activated by RRC signaling / MAC CE.

[0036] It is considered that the repeat transmission of PUSCH using a single PUSCH transmission / single TRP (Single TRP (STRP)) and the repeat transmission of PUSCH using multiple TRPs (Multi TRP (MTRP)) are dynamically indicated / switched by DCI. The dynamic switch may utilize a specific field included in DCI defined up to Rel. 16, or may utilize a specific field (e.g., a field for specifying STRP or MTRP operation) defined in Rel. 17 or later.

[0037] In addition, the term "dynamic switch" in the present disclosure may mean "a switch that uses at least one of higher layer signaling and physical layer signaling." In addition, the term "switch" in the present disclosure may be interchangeably read as switching, change, changing, applying, instructing, setting, and the like.

[0038] However, the current standard does not specify how to control PHR for MTRP PUSCH repetition. If the PHR is not triggered / generated / transmitted appropriately, communication throughput and communication quality may be degraded.

[0039] Therefore, the present inventors have conceived a method for appropriately performing PHR reporting when MTRP PUSCH repetition is used.

[0040] Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. Wireless communication methods according to the embodiments may be applied independently or in combination.

[0041] In the present disclosure, "A / B" and "at least one of A and B" may be read as interchangeable.

[0042] In the present disclosure, the terms activate, deactivate, indicate, select, configure, update, determine, etc. may be read as interchangeable terms.

[0043] In the present disclosure, RRC, RRC parameters, RRC messages, RRC signaling, higher layer parameters, information elements (IEs), and configurations may be interchangeable. In the present disclosure, MAC CE, update commands, and activation / deactivation commands may be interchangeable. In the present disclosure, support, control, controllable, operate, and operable may be interchangeable.

[0044] In the present disclosure, the terms panel, beam, panel group, beam group, precoder, uplink (UL) transmitting entity, TRP, spatial relationship information (SRI), spatial relationship, SRS Resource Indicator (SRI), SRS resource, control resource set (COntrol REsource SET (CORESET)), Physical Downlink Shared Channel (PDSCH), codeword, base station, predetermined antenna port (e.g., DeModulation Reference Signal (DMRS) port), predetermined antenna port group (e.g., DMRS port group), predetermined group (e.g., Code Division Multiplexing (CDM) group, predetermined reference signal group, CORESET group), predetermined resource (e.g., predetermined reference signal resource), predetermined resource set (e.g., predetermined reference signal resource set), CORESET pool, PUCCH group (PUCCH resource group), spatial relationship group, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), The terms TCI state, unified TCI state, common TCI state, QCL, QCL assumption, etc. may be read interchangeably.

[0045] In addition, a TCI status identifier (ID) and a TCI status may be interchangeable. A TCI status and a TCI may be interchangeable.

[0046] In this disclosure, the terms index, ID, indicator, and resource ID may be interchangeable. In this disclosure, the terms sequence, list, set, group, cluster, and subset may be interchangeable.

[0047] In the present disclosure, the TRP index, CORESET pool index (CORESETPoolIndex), pool index, group index, etc. may be read as interchangeable.

[0048] In the present disclosure, a single PDCCH (DCI) may be referred to as a PDCCH (DCI) of a first scheduling type (e.g., scheduling type A (or type 1)), and a multi-PDCCH (DCI) may be referred to as a PDCCH (DCI) of a second scheduling type (e.g., scheduling type B (or type 2)).

[0049] In this disclosure, for a single DCI, the ith TRP (TRP#i) may refer to the ith TCI state, the ith CDM group, etc. (i is an integer). For a multi-DCI, the ith TRP (TRP#i) may refer to the CORESET corresponding to CORESET pool index=i, the ith TCI state, the ith CDM group, etc. (i is an integer).

[0050] In the present disclosure, multi-TRP (MTRP, M-TRP), multi-TRP system, multi-TRP transmission, and multi-PDSCH may be read as interchangeable.

[0051] In the present disclosure, single DCI (sDCI), single PDCCH, multi-TRP system based on single DCI, sDCI-based MTRP, scheduling of multiple PUSCHs (corresponding to different SRIs) by one DCI, sDCI-based MTRP transmission, and activation of two TCI states on at least one TCI codepoint may be read as interchangeable.

[0052] In the present disclosure, multi-DCI (mDCI), multi-PDCCH, multi-TRP system based on multi-DCI, mDCI-based MTRP, mDCI-based MTRP transmission, use of multi-DCI for MTRP, scheduling of multiple PUSCHs (corresponding to different SRIs) by two DCIs, and setting of two CORESET pool indices or CORESET pool index=1 (or a value greater than or equal to 1) may be read as interchangeable.

[0053] The repetition in the present disclosure may be interchangeably read as MTRP-based repetition, Rel.17 repetition, repetition applying different spatial relationships, repetitive PUSCH, repetitive PUCCH, repetitive transmission, etc. Furthermore, the repetitive transmission in the following embodiments may correspond to at least one of repetitive transmission type A, repetitive transmission type B, and other repetitive transmission types.

[0054] In addition, in a repetitive PUSCH, the same codeword / transport block may be transmitted in each PUSCH (each repetition). A repetitive PUSCH may be interpreted as multiple PUSCHs having the same content (e.g., data / codeword / transport block).

[0055] In the present disclosure, the first TRP and the second TRP may be read as the first PUSCH and the second PUSCH, the first PUSCH transmission opportunity and the second PUSCH transmission opportunity, the first SRI and the second SRI, and the like.

[0056] In the present disclosure, the MTRP PUSCH repetition may be interchangeably read as two PUCCH repetitions for two TRPs, two PUSCH repetitions using two SRIs, two PUSCH repetitions using two sets of power control parameters (the power control parameters are described below), etc.

[0057] In this disclosure, repetition of STRP PUSCH may refer to repeated transmission of multiple PUSCHs transmitted using one (same) SRI / power control parameter set / beam / precoder, and single transmission may refer to PUSCH transmission transmitted using one SRI / power control parameter set / beam / precoder.

[0058] In addition, PUSCH repetition / PUSCH transmission to TRP1 may mean PUSCH repetition / PUSCH transmission using the first SRI (or SRI field) / first power control parameter set.

[0059] Furthermore, PUSCH repetition / PUSCH transmission to TRP2 may mean PUSCH repetition / PUSCH transmission using a second SRI (or SRI field) / second power control parameter set.

[0060] In the following embodiments, repeated transmission of PUSCH using multiple TRPs may be interchangeably referred to as MTRP PUSCH repetition, PUSCH transmission using multiple TRPs, repeated transmission of PUSCH for multiple TRPs, PUSCH across multiple TRPs, repeated PUSCH across multiple TRPs, simply repeated PUSCH, repeated transmission, multiple PUSCH transmission, PUSCH transmission using multiple SRIs, etc.

[0061] In addition, PUSCH transmission using a single TRP may be referred to as STRP PUSCH repetition, PUSCH transmission using a single TRP, repeated transmission of PUSCH for a single TRP, PUSCH across a single TRP, repeated PUSCH across a single TRP, a single PUSCH transmission for a single TRP, simply a single PUSCH transmission, PUSCH transmission in a single TRP, PUSCH transmission using a single SRI, etc.

[0062] In each embodiment of the present disclosure, PUSCH transmission for single / multiple TRPs using one DCI and codebook-based PUSCH transmission are described as examples of UL transmission, but non-codebook-based PUSCH transmission may also be applied, and PUSCH transmission to which each embodiment can be applied is not limited to these. When each embodiment of the present disclosure is applied to non-codebook-based PUSCH transmission, one or more SRS resources (SRIs) may be indicated to the UE by each SRI field. In addition, common or different embodiments may be applied to codebook-based PUSCH transmission and non-codebook-based PUSCH transmission. In addition, UL transmission is not limited to PUSCH, and each embodiment of the present disclosure can be appropriately applied to PUCCH (PUSCH may be replaced with PUCCH).

[0063] In addition, in each embodiment of the present disclosure, the case where the number of multiple TRPs, multiple SRIs, etc. is two is mainly described as an example, but the number of these may be three or more. In other words, "two" in the present disclosure may be read as "multiple."

[0064] In addition, in the present disclosure, "CORESET pool index is set to 0" may be read as "CORESET pool index is set to 0 or CORESET pool index is not set".

[0065] Furthermore, in the present disclosure, the CORESET pool index, the PUSCH repetition index, and the higher layer index may be read as interchangeable.

[0066] In this disclosure, "PHR" may be interchangeably read as "PH," "PH field," "PH value," etc.

[0067] Note that, although each embodiment described below is premised on a case where MTRP PUSCH repetition is enabled for a UE by a higher layer parameter, this is not limiting.

[0068] (Wireless communication method) <First embodiment> The first embodiment relates to a PHR report that includes at least one Type 1 PHR (which may be referred to as actual PHR, real PHR, etc.) that is based on an actual PUSCH transmission.

[0069] Also, the first embodiment may be applied to a case where STRP PUSCH repetition or single transmission (in other words, PUSCH transmission without repetition) is specified by DCI for a serving cell. Hereinafter, in the present disclosure, this case is also called "Case 1". Also, the case where MTRP PUSCH repetition is specified by DCI for a serving cell is also called "Case 2".

[0070] In addition, the case where STRP PUSCH repetition is specified by DCI for a serving cell is also called "case 1a", and the case where single transmission is specified by DCI for a serving cell is also called "case 1b". Case 1 includes cases 1a and 1b. "Case 1" in the present disclosure may be read as "Case 1a / Case 1b" interchangeably.

[0071] In the first embodiment, "reporting one / two PHRs" may mean "reporting one / two PHRs for a serving cell in which STRP PUSCH repetition / single transmission / MTRP PUSCH repetition is specified by DCI." In the present disclosure, the reported one / two PHRs may be type 1 PHs or other types of PHs.

[0072] The first embodiment is roughly divided into embodiment 1.1 in which the UE reports one PHR in case 1, and embodiment 1.2 in which the UE reports two PHRs in case 1.

[0073] [Embodiment 1.1] In embodiment 1.1, the single PHR reported in case 1 may be calculated based on the actual PUSCH transmission in a similar manner as already specified in Rel.15 / 16 NR.

[0074] In embodiment 1.1, the UE may report two PHRs in case 2. Note that the UE may report one or two PHRs in case 2. This will also be mentioned in the third embodiment described later.

[0075] In embodiment 1.1, the PHR MAC CE may include a field indicating that one or two PHRs are reported (in other words, whether this PHR MAC CE is for case 1 or case 2). This field may be represented by one bit. This field may be included for each serving cell, or may be included in relation to a specific serving cell. Note that this field may be represented by two bits, in which case this field may indicate that one PHR for TRP1 is reported, one PHR for TRP2 is reported, or two PHRs are reported.

[0076] [Embodiment 1.2] In embodiment 1.2, for a serving cell where MTRP PUSCH repetition is enabled by higher layer parameters, two PHRs are always reported by the PHR MAC CE regardless of case 1 or case 2.

[0077] Embodiment 1.2 is further divided into two (embodiments 1.2.1 and 1.2.2).

[0078] In embodiment 1.2.1, the two PHRs reported in case 1 are the same value. This same value may be calculated based on the power control parameters for PUSCH repetition / PUSCH transmission.

[0079] In embodiment 1.2.2, among the two PHRs reported in case 1, an actual PHR is reported for the PHR for the TRP for which PUSCH repetition / PUSCH transmission is specified by DCI. This actual PHR may be calculated based on the power control parameters for the PUSCH repetition / PUSCH transmission.

[0080] In addition, of the two reported PHRs, a type 1 PHR based on a reference PUSCH transmission (which may be referred to as a reference PHR, a virtual PHR, a PHR conforming to a reference format, etc. in this disclosure) is reported for the PHR for the other TRP. This virtual PHR may be calculated based on default power control parameters already specified in Rel.15 / 16 NR, or may be calculated based on new default power control parameters.

[0081] In this disclosure, the power control parameter is P CMAX,f,c , Maximum Power Reduction (MPR), P-MPR, Additional Maximum Power Reduction (A-MPR), ΔTc, P0, alpha, Pathloss Reference Signal (PL-RS), and Closed Loop Index (l). For example, in Rel. 16 NR, the default power control parameters are MPR=0[dB], A-MPR=0[dB], P-MPR=0[dB], ΔT C = 0 [dB], and P0 and alpha are 0_NOMIANAL_PUSCH、f、c (0) and upper layer parameter p0-PUSCH-AlphaSetId=0, and the downlink path loss estimation is obtained using upper layer parameter pusch-PathlossReferenceRS-Id=0, with l=0.

[0082] In addition, in embodiment 1.2.2, the PHR MAC CE may include a field indicating whether a PHR for a certain TRP is a virtual PHR. This field may be represented by 1 bit. This field may be included for each serving cell, or may be included in relation to a specific serving cell.

[0083] The default power control parameters for calculating the virtual PHR in embodiment 1.2.2 may be different for each TRP or may be the same (common). Also, in the present disclosure, different default power control parameters for different TRPs may mean that some of the power control parameters are different and the rest are common.

[0084] [Specific example of PHR MAC CE in the first embodiment] 3A-3C are diagrams showing an example of a single-entry PHR MAC CE in the first embodiment. FIGs. 3A, 3B and 3C correspond to embodiment 1.1, embodiment 1.2.1 and embodiment 1.2.2, respectively. For each, differences from FIG. 1 will be described, and the same description will not be repeated. PHR_1 and PHR_2 correspond to the first and second PHRs reported by the PHR MAC CE, respectively, and may be type 1 PH. PHR_1 and PHR_2 may indicate the PHR for TRP1 and the PHR for TRP2, respectively.

[0085] In Fig. 3A, the 'X' field corresponds to the field indicating that one or two PHRs are reported, and indicates whether an octet (one string of 8 bits shown in the figure) including PHR_2 exists or not. For example, X=1 may mean existence, and X=0 may mean non-existence (or vice versa). In other words, the size of this MAC CE is 3 octets if X=1, and 2 octets if X=0, which is the same as the existing single-entry PHR MAC CE.

[0086] In case 1, the UE may report the PHR using a 2-octet MAC CE indicating X=0, and in case 2, the UE may report the PHR using a 3-octet MAC CE indicating X=1.

[0087] FIG. 3B shows a 3-octet MAC CE. In embodiment 1.2.1, this MAC CE may be used in both case 1 and case 2. In case 1, the UE generates the MAC CE by setting PHR_1 and PHR_2 to the same value. In case 2, the UE can set PHR_1 and PHR_2 to different values.

[0088] Figure 3C shows a 3-octet MAC CE. In embodiment 1.2.2, this MAC CE may be used in both case 1 and case 2. The 'V1' and 'V2' fields in Figure 3C correspond to the fields indicating whether the PHR for a certain TRP is a virtual PHR or not, and the PHR field immediately following them indicates whether it is a real PHR or a virtual PHR. 'V1' and 'V2' may be simply indicated by 'V'.

[0089] For example, V=1 may mean that the immediately following PHR field is a virtual PHR, and V=0 may mean that the immediately following PHR field is a real PHR (or vice versa).

[0090] In case 1, when transmission to TRP1 is instructed, the UE may report the actual PHR for TRP1 via PHR_1 and the virtual PHR for TRP2 via PHR_2 using a 3-octet MAC CE indicating V1=0 and V2=1.

[0091] In case 1, when transmission to TRP2 is instructed, the UE may report a virtual PHR for TRP1 via PHR_1 and an actual PHR for TRP2 via PHR_2 using a 3-octet MAC CE indicating V1=1 and V2=0.

[0092] In case 2, the UE may report the actual PHR for TRP1 via PHR_1 and the actual PHR for TRP2 via PHR_2 using a 3-octet MAC CE indicating V1=0 and V2=0.

[0093] Figures 4A-4C are diagrams showing an example of a multiple entry PHR MAC CE in the first embodiment. Figures 4A, 4B and 4C correspond to embodiment 1.1, embodiment 1.2.1 and embodiment 1.2.2, respectively. For each, differences from Figure 2 will be described, and the same description will not be repeated. PHR_j,1 and PHR_j,2 (j is an integer) correspond to the j-th first and second PHRs reported by the PHR MAC CE, respectively, and may be type 1 PH. PHR_j,1 and PHR_j,2 may indicate PHRs for TRP1 and TRP2, respectively.

[0094] In FIG. 4A, 'X i ' field corresponds to the field indicating that one or two PHRs are reported as described above, and C i It indicates whether or not an octet (a string of 8 bits as shown) containing PHR_j,2 corresponding to the field exists. For example, X i = 1 exists, X i =0 may mean not present (and vice versa).

[0095] In addition, the X0 field may correspond to a field indicating that one or two PHRs are reported for serving cell index=0 (or PCell or SpCell). Also, the C0 field may be an R field. The same may be true for the following drawings.

[0096] In case 1, the UE i = 0 using MAC CE i In case 2, one PHR may be reported for X i = 1 using MAC CE iTwo PHRs may be reported for

[0097] FIG. 4B differs from FIG. 2 in that there is an octet containing each PHR_j,2. In embodiment 1.2.1, this MAC CE may be used in both case 1 and case 2. In case 1, the UE generates the MAC CE with PHR_j,1 and PHR_j,2 being the same value. In case 2, the UE can set PHR_j,1 and PHR_j,2 to different values. The R field before PHR_j,2 may be a V field corresponding to PHR_j,2, but it also works as an R field since PHR_j,2 is the same as PHR_j,1 (case 1) or actually corresponds to a PHR (case 2). Therefore, one or two R fields before PHR_j,2 may be used as separate fields.

[0098] Figure 4C differs from Figure 2 in that there is an octet including each PHR_j,2. In embodiment 1.2.2, this MAC CE may be used in both case 1 and case 2. The 'V' field in Figure 4C corresponds to a field indicating whether the PHR for a certain TRP described above is a virtual PHR or not, and the PHR field immediately following it indicates whether it is a real PHR or a virtual PHR.

[0099] For example, V=1 may mean that the immediately following PHR field is a virtual PHR, and V=0 may mean that the immediately following PHR field is a real PHR (or vice versa).

[0100] According to the first embodiment described above, the UE can appropriately generate / transmit a PHR report including the actual PHR.

[0101] <Second embodiment> The second embodiment relates to a type 1 PHR report based on a reference PUSCH transmission. Note that the second embodiment may correspond to a PHR report that does not include an actual PHR (in other words, includes only a virtual PHR), or may correspond to a PHR report that includes a virtual PHR and an actual PHR.

[0102] The second embodiment may be applied to cases where at least one of case 1 and case 2 applies, or where neither applies (for example, when PUSCH repetition / PUSCH transmission is not specified by DCI).

[0103] In the second embodiment, "reporting one / two PHRs" may mean "reporting one / two PHRs for a serving cell that reports a virtual PHR." In addition, the reported one / two PHRs may be type 1 PHs or other types of PHs.

[0104] The second embodiment is broadly divided into embodiment 2.1 in which the UE reports one PHR and embodiment 2.2 in which the UE reports two PHRs.

[0105] [Embodiment 2.1] In embodiment 2.1, the single reported PHR may be calculated based on the reference PUSCH transmission in a similar manner as already specified in Rel.15 / 16 NR.

[0106] In embodiment 2.1, the PHR MAC CE may include a 1-bit field indicating that one or two PHRs are reported (in other words, whether this PHR MAC CE actually includes a PHR or not). This field may be included for each serving cell, or may be included in relation to a specific serving cell. For example, this field may be the V field of the PHR MAC CE defined in Rel.15 / 16 NR.

[0107] [Embodiment 2.2] In embodiment 2.2, for a serving cell where MTRP PUSCH repetition is enabled by higher layer parameters, two virtual PHRs are always reported by the PHR MAC CE.

[0108] Embodiment 2.2 is further divided into two (embodiments 2.2.1 and 2.2.2).

[0109] In embodiment 2.2.1, the two reported virtual PHRs are the same value, which may be calculated based on the default power control parameters already specified in Rel.15 / 16 NR, or may be calculated based on new default power control parameters.

[0110] In embodiment 2.2.2, for two virtual PHRs reported, the default power control parameters for calculating the PHR for one TRP (e.g., TRP1) are different from the default power control parameters for calculating the PHR for another TRP (e.g., TRP2).

[0111] [Specific example of PHR MAC CE in the second embodiment] FIG. 5 is a diagram showing an example of a multiple entry PHR MAC CE in the second embodiment. FIG. 5 corresponds to embodiment 2.1 and embodiment 2.2. Differences from FIG. 2 will be described, and the same points will not be described repeatedly. PHR_j,1 and PHR_j,2 (j is an integer) correspond to the j-th first and second PHRs reported by the PHR MAC CE, respectively, and may be type 1 PH. PHR_j,1 and PHR_j,2 may indicate the PHR for TRP1 and the PHR for TRP2, respectively.

[0112] Fig. 5 has the same configuration as Fig. 4B. In the embodiment 2.1 and the embodiment 2.2, this MAC CE may be used in both case 1 and case 2.

[0113] The 'V' field in Figure 5 corresponds to a field indicating that one or two PHRs as described above are reported in embodiment 2.1, and indicates whether or not an octet (one string of 8 bits as shown in the figure) containing PHR_j,2 corresponding to the immediately following PHR_j,1 field is present.

[0114] For example, V=1 may mean that the octet containing the corresponding PHR_j,2 immediately following the PHR_j,1 field is not present, whereas V=0 may mean that it is present (or vice versa).

[0115] In embodiment 2.1, PHR_j,2 may actually indicate the PHR. In embodiment 2.2.1, PHR_j,1 and PHR_j,2 are the same value, and in embodiment 2.2.2, PHR_j,1 and PHR_j,2 can be different values.

[0116] In embodiment 2.2, the V' field may be the R field or may be used as a separate field. Note that, in FIG. 5, if V=1 in embodiment 2.2, both PHR_j,1 and PHR_j,2 may represent virtual PHRs, and if V=0, both PHR_j,1 and PHR_j,2 may represent real PHRs for MTRP repetition.

[0117] Note that a part of the configuration in FIG. 5 may also be used for the single-entry PHR MAC CE.

[0118] According to the second embodiment described above, the UE can appropriately generate / transmit a PHR report including a virtual PHR.

[0119] <Third embodiment> The third embodiment relates to the case where the PHR of a second serving cell (serving cell 2) is transmitted using a PHR MAC CE in the PUSCH of a first serving cell (serving cell 1), where the PHR of serving cell 2 is based on the actual PUSCH transmission of the MTRP PUSCH repetition.

[0120] The third embodiment is broadly divided into embodiments 3.1 to 3.3.

[0121] [Embodiment 3.1] Embodiment 3.1 applies to the case where a UE is configured with multiple cells for PUSCH transmission, and the SCS setting μ1 of the active UL BWP b1 of carrier f1 of serving cell 1 is the same as the SCS setting μ2 of the active UL BWP b2 of carrier f2 of serving cell 2 (in simple terms, the SubCarrier Spacing (SCS) of serving cell 1 is the same as the SCS of serving cell 2), and if the UE provides Type 1 PHR for PUSCH transmission in a slot in b1, then the UE also provides Type 1 PHR for the first PUSCH in a slot in b2 that overlaps with this slot.

[0122] In addition, the Type 1 PHR of the serving cell 2 is transmitted using PUSCH in the slot of the serving cell 1. In addition, the Type 1 PHR of the serving cell 2 is based on actual PUSCH transmission. Furthermore, the above-mentioned first PUSCH overlapping with the slot for reporting the PHR of the serving cell 1 (hereinafter also referred to as a PHR report slot) is one of the MTRP PUSCH repetitions. In addition, one unit of repetition may be referred to as a repetition opportunity, a PUSCH opportunity, etc. In the present disclosure, the above-mentioned first PUSCH may be referred to as a first PUSCH repetition, a first PUSCH opportunity, etc. In addition, in the present disclosure, "first" may be read as "initial" or the like.

[0123] FIG. 6 is a diagram showing an example of embodiment 3.1. Since the SCS of serving cells 1 and 2 is the same, the slot lengths of these cells are the same. In serving cell 2, MTRP PUSCH repeated transmission is performed overlapping with the PHR report slot (slot described as "PUSCH with PHR") of serving cell 1. The number of repetitions is 2, and two slots (PUSCH1, PUSCH2) are shown. In the following drawings, PUSCHi may also mean the i-th repetition in the MTRP repetition.

[0124] Moreover, the first PUSCH corresponds to PUSCH1 that overlaps with the PHR reporting slot of the serving cell 1. The PHR of PUSCH1 of the serving cell 2 is reported in the PHR reporting slot of the serving cell 1.

[0125] The embodiment 3.1 is broadly divided into an embodiment 3.1.1 in which the UE reports one PHR as the PHR of the serving cell 2, and an embodiment 3.1.2 in which the UE reports two PHRs.

[0126] One PHR reported in embodiment 3.1.1 may be any of the following: Embodiment 3.1.1-1: PHR of the first PUSCH repetition in a slot of serving cell 2 that overlaps with a PHR reporting slot of serving cell 1; Embodiment 3.1.1-2: PHR of the first PUSCH repetition to TRP1 in a slot of serving cell 2 that overlaps with a PHR reporting slot of serving cell 1; Embodiment 3.1.1-3: PHR of the first PUSCH repetition to TRP2 in a slot of serving cell 2 that overlaps with a PHR reporting slot of serving cell 1; Embodiment 3.1.1-4: PHR of the first PUSCH repetition of the PUSCH of the serving cell 2; Embodiment 3.1.1-5: PHR of the first PUSCH repetition to TRP1 of the PUSCH of the serving cell 2; · Embodiment 3.1.1-6: PHR of the first PUSCH repetition to TRP2 for the PUSCH of serving cell 2.

[0127] The two PHRs reported in embodiment 3.1.2 may be either: Embodiment 3.1.2-1: PHR of the first PUSCH repetition to TRP1 and the first PUSCH repetition to TRP2 in a slot of serving cell 2 that overlaps with a PHR report slot of serving cell 1; Embodiment 3.1.2-2: PHR of the first PUSCH repetition to TRP1 and the first PUSCH repetition to TRP2 of the PUSCH of serving cell 2.

[0128] In addition, in embodiments 3.1.1-4, 3.1.1-5, 3.1.1-6, and 3.1.2-2, serving cell 2 may be replaced with serving cell 1 and the embodiments may be applied to the PHR of serving cell 1 (the serving cell that transmits the PHR).

[0129] It should be noted that each of the embodiments 3.1.1 and 3.1.2 may be applied to at least one of the following cases: Case A: There is only one PUSCH repetition in a slot of serving cell 2 that overlaps with a PHR reporting slot of serving cell 1; Case A1: This one PUSCH repetition is a repetition for any TRP, Case A2: This one PUSCH repeat is a repeat for TRP1. Case A3: This PUSCH repetition is for TRP2. Case B: There are two or more PUSCH repetitions in a slot of serving cell 2 that overlaps with a PHR reporting slot of serving cell 1; Case B1: The two or more PUSCH repetitions include repetitions for multiple TRPs, Case B2: The two or more PUSCH repetitions are all repetitions for TRP1. · Case B3: These two or more PUSCH repetitions are both repetitions for TRP2.

[0130] It should be noted that among the embodiments shown in embodiments 3.1.1 and 3.1.2, the same embodiment may be applied to one or more of the above cases, or different embodiments may be applied to different cases.

[0131] 7A and 7B are diagrams showing an example of case A of embodiment 3.1. Since the SCS of serving cells 1 and 2 is the same, the slot lengths of these cells are the same. In serving cell 2, MTRP PUSCH repeated transmission is performed overlapping with the PHR report slot of serving cell 1. The number of repetitions is 4, and 4 slot repetitions (PUSCH1-4) are shown. Note that cyclic mapping is applied to this MTRP repetition.

[0132] Cyclic mapping is a mapping pattern (or method) in which TRP1 and TRP2 (beams for) are mapped to the first and second repetitions, and the same mapping is applied to the remaining repetitions. Note that sequential mapping, half-half mapping, etc. may be applied as the mapping pattern.

[0133] Also, the PHR reporting slot of serving cell 1 overlaps with PUSCH1 in FIG. 7A and with PUSCH2 in FIG. 7B.

[0134] In the example of Fig. 7A, in the case of embodiment 3.1.1-1, the UE reports one PHR (PHR for PUSCH1) in the PHR reporting slot for serving cell 2. In the example of Fig. 7A, in the case of embodiment 3.1.2-2, the UE reports two PHRs (PHR for PUSCH1 and PHR for PUSCH2) in the PHR reporting slot for serving cell 2.

[0135] In the example of Fig. 7B, when the embodiment 3.1.1-1 is followed, the UE reports one PHR (PHR for PUSCH2) in the PHR reporting slot for serving cell 2. Also, in the example of Fig. 7B, when the embodiment 3.1.1-4 is followed, the UE reports one PHR (PHR for PUSCH1) in the PHR reporting slot for serving cell 2. Also, in the example of Fig. 7B, when the embodiment 3.1.2-2 is followed, the UE reports two PHRs (PHR for PUSCH1 and PHR for PUSCH2) in the PHR reporting slot for serving cell 2.

[0136] 8A and 8B are diagrams showing an example of case B of embodiment 3.1. Since the SCS of serving cells 1 and 2 is the same, the slot lengths of these cells are the same. In serving cell 2, MTRP PUSCH repeated transmission is performed overlapping with the PHR report slot of serving cell 1. The number of repetitions is 4, and four repetitions (PUSCH1-4) are shown. Note that cyclic mapping is applied to this MTRP repetition. One repetition period corresponds to a half slot (or sub-slot, multiple symbols).

[0137] Also, the PHR reporting slot of serving cell 1 overlaps with PUSCHs 1 and 2 in FIG. 8A, and with PUSCHs 3 and 4 in FIG. 8B.

[0138] In the example of Fig. 8A, when following embodiment 3.1.1-1, the UE reports one PHR (PHR for PUSCH1) in the PHR reporting slot for serving cell 2. Also, in the example of Fig. 8A, when following embodiment 3.1.2-1 / 3.1.2-2, the UE reports two PHRs (PHR for PUSCH1 and PHR for PUSCH2) in the PHR reporting slot for serving cell 2.

[0139] In the example of FIG. 8B, when the embodiment 3.1.1-1 is followed, the UE reports one PHR (PHR for PUSCH3) for the serving cell 2 in the PHR report slot. Also, in the example of FIG. 8B, when the embodiment 3.1.1-4 is followed, the UE reports one PHR (PHR for PUSCH1) for the serving cell 2 in the PHR report slot. Also, in the example of FIG. 8B, when the embodiment 3.1.2-1 is followed, the UE reports two PHRs (PHR for PUSCH3 and PHR for PUSCH4) for the serving cell 2 in the PHR report slot. Also, in the example of FIG. 8B, when the embodiment 3.1.2-2 is followed, the UE reports two PHRs (PHR for PUSCH1 and PHR for PUSCH2) for the serving cell 2 in the PHR report slot.

[0140] [Embodiment 3.2] Embodiment 3.2 applies to the case where multiple cells are configured in a UE for PUSCH transmission, and the SCS setting μ1 of the active UL BWP b1 of carrier f1 of serving cell 1 is smaller than the SCS setting μ2 of the active UL BWP b2 of carrier f2 of serving cell 2 (in simple terms, the SCS of serving cell 1 is smaller than the SCS of serving cell 2), and the UE provides Type 1 PHR for PUSCH transmission in a slot (PHR reporting slot) in b1 that overlaps with multiple slots in b2, then the UE provides Type 1 PHR for a first PUSCH in a first slot of the multiple slots in b2 that fully overlaps with this PHR reporting slot.

[0141] Note that the Type 1 PHR of serving cell 2 is transmitted using PUSCH in the slot of serving cell 1. Also, the Type 1 PHR of serving cell 2 is based on actual PUSCH transmission. Furthermore, the first PUSCH in the first slot that completely overlaps with the PHR reporting slot of serving cell 1 is one of the MTRP PUSCH repetitions.

[0142] FIG. 9 is a diagram showing an example of embodiment 3.2. The SCS of serving cell 1 is smaller than that of serving cell 2, and in this example, the latter is twice as long as the former (for example, SCS of serving cell 1=15 kHz and SCS of serving cell 2=30 kHz). Therefore, the actual time length of a slot of serving cell 1 is twice as long as that of serving cell 2. The same applies to the drawings for explaining embodiment 3.2 unless otherwise specified.

[0143] In the serving cell 2, MTRP PUSCH repeated transmission is performed so as to overlap with the PHR report slot (slot marked "PUSCH with PHR") of the serving cell 1. The number of repetitions is 3, and three slots (PUSCH1-3) are shown to be repeated.

[0144] Moreover, the first PUSCH corresponds to PUSCH1 in a first slot in a plurality of slots that completely overlap with the PHR reporting slot of the serving cell 1. The PHR of PUSCH1 of the serving cell 2 may be reported in the PHR reporting slot of the serving cell 1.

[0145] The embodiment 3.2 is broadly divided into an embodiment 3.2.1 in which the UE reports one PHR as the PHR of the serving cell 2, and an embodiment 3.2.2 in which the UE reports two PHRs.

[0146] The embodiments 3.2.1 and 3.2.2 may be embodiments in which the above-mentioned embodiments 3.1.1 and 3.1.2 are read as follows: In the embodiment 3.2.1a / 3.2.2a, "the slot of serving cell 2 that overlaps with the PHR reporting slot of serving cell 1" is read as "the first slot of serving cell 2 that completely overlaps with the PHR reporting slot of serving cell 1", -Embodiment 3.2.1b / 3.2.2b: "A slot of serving cell 2 that overlaps with the PHR reporting slot of serving cell 1" is read as "multiple slots of serving cell 2 that completely overlap with the PHR reporting slot of serving cell 1."

[0147] In addition, in the embodiments 3.2.1a / 3.2.2a and 3.2.1b / 3.2.2b, the above-mentioned replacement "completely overlap" may be replaced with "overlapping." Also, the "first slot of serving cell 2" in the embodiments 3.2.1a / 3.2.2a may be replaced with "the first slot of the multiple slots of serving cell 2."

[0148] Hereinafter, the embodiment 3.2.1a / 3.2.2a will be collectively referred to as the embodiment 3.2a. The embodiment 3.2.1b / 3.2.2b will be collectively referred to as the embodiment 3.2b. The embodiment that does not require reinterpretation may be used as it is. For example, the embodiments 3.1.1-4 to 3.1.1-6 and 3.1.2-2 can be applied as it is because "the slot of serving cell 2 that overlaps with the PHR reporting slot of serving cell 1" does not appear.

[0149] 10A and 10B are diagrams illustrating an example of the difference between embodiments 3.2a and 3.2b.

[0150] In the serving cell 2, MTRP PUSCH repeated transmission is performed so as to overlap with the PHR report slot of the serving cell 1. The number of repetitions is 4, and 4 slots (PUSCH1-3) are shown to be repeated. Note that cyclic mapping is applied to this MTRP repetition.

[0151] 10A corresponds to embodiment 3.2a, and "the first slot of serving cell 2 that completely overlaps with the PHR report slot of serving cell 1" is hatched. This first slot corresponds to the PUSCH1 slot among the PUSCH1 slot and the PUSCH2 slot that overlap with the PHR report slot.

[0152] 10B corresponds to embodiment 3.2b, and "slots of serving cell 2 that completely overlap with the PHR report slot of serving cell 1" are hatched. These slots correspond to the slots of PUSCH1 and PUSCH2 that overlap with the PHR report slot.

[0153] Each of the embodiments 3.2a and 3.2b may be applied to at least one of the cases A, A1-A3, B, and B1-B3 described in the embodiment 3.1. The same embodiment of each of the embodiments 3.2a and 3.2b may be applied to one or more of the above cases, or different embodiments may be applied to different cases.

[0154] 11A and 11B are diagrams illustrating an example of Case A of embodiment 3.2a. The PHR report slot of the serving cell 1 overlaps with the slots of PUSCH1 and PUSCH2 in FIG. 11A, and overlaps with the slots of PUSCH2 and PUSCH3 in FIG. 11B.

[0155] In the example of Fig. 11A, when embodiment 3.2.1-1a (an embodiment in which embodiment 3.1.1-1 is reinterpreted based on embodiment 3.2a; hereinafter referred to by the same rule) is followed, the UE reports one PHR (PHR for PUSCH1) in the PHR reporting slot for serving cell 2. Also, in the example of Fig. 11A, when embodiment 3.2.2-2a (but without reinterpretation) is followed, the UE reports two PHRs (PHR for PUSCH1 and PHR for PUSCH2) in the PHR reporting slot for serving cell 2.

[0156] In the example of FIG. 11B, when the embodiment 3.2.1-1a is followed, the UE reports one PHR (PHR for PUSCH2) in the PHR reporting slot for serving cell 2. Also, in the example of FIG. 11B, when the embodiment 3.2.1-4a (but without any modification) is followed, the UE reports one PHR (PHR for PUSCH1) in the PHR reporting slot for serving cell 2. Also, in the example of FIG. 11B, when the embodiment 3.2.2-2a (but without any modification) is followed, the UE reports two PHRs (PHR for PUSCH1 and PHR for PUSCH2) in the PHR reporting slot for serving cell 2.

[0157] 12A and 12B are diagrams showing an example of case B of embodiment 3.2. Since the SCS of serving cell 1 is half that of serving cell 2, the slot length of serving cell 1 is twice that of serving cell 2. In serving cell 2, MTRP PUSCH repeated transmission (four times) is performed, overlapping with the PHR report slot of serving cell 1. One repetition period corresponds to a half slot (or sub-slot, multiple symbols) for the slot of serving cell 2.

[0158] Also, the PHR reporting slot of serving cell 1 overlaps with all of the slots of PUSCH1-4 in FIG. 12A, and overlaps with PUSCH3 and 4 in FIG. 12B (starting timing is the same as the slot of PUSCH3).

[0159] In the example of Fig. 12A, in accordance with embodiment 3.2.1-1a, the UE reports one PHR (PHR for PUSCH1) in the PHR reporting slot for serving cell 2. Also, in the example of Fig. 12A, in accordance with embodiment 3.2.2-1a / 3.2.2-2a, the UE reports two PHRs (PHR for PUSCH1 and PHR for PUSCH2) in the PHR reporting slot for serving cell 2.

[0160] In the example of FIG. 12B, when the embodiment 3.2.1-1a is followed, the UE reports one PHR (PHR for PUSCH3) for the serving cell 2 in the PHR report slot. Also, in the example of FIG. 12B, when the embodiment 3.2.1-4a (but without any modification) is followed, the UE reports one PHR (PHR for PUSCH1) for the serving cell 2 in the PHR report slot. Also, in the example of FIG. 12B, when the embodiment 3.2.2-1a is followed, the UE reports two PHRs (PHR for PUSCH3 and PHR for PUSCH4) for the serving cell 2 in the PHR report slot. Also, in the example of FIG. 12B, when the embodiment 3.2.2-2a (but without any modification) is followed, the UE reports two PHRs (PHR for PUSCH1 and PHR for PUSCH2) for the serving cell 2 in the PHR report slot.

[0161] Fig. 13 is a diagram showing another example of case B of embodiment 3.2. The example of Fig. 13 has the same configuration as the example of Fig. 11B, so duplicated description will not be repeated.

[0162] In the example of FIG. 13, when the embodiment 3.2.1-1a is followed, the UE reports one PHR (PHR for PUSCH2) for the serving cell 2 in the PHR report slot. Also, in the example of FIG. 13, when the embodiment 3.2.1-4a (but without any reinterpretation) is followed, the UE reports one PHR (PHR for PUSCH1) for the serving cell 2 in the PHR report slot. Also, in the example of FIG. 13, when the embodiment 3.2.2-1a is followed, the UE reports two PHRs (PHR for PUSCH2 and PHR for PUSCH3) for the serving cell 2 in the PHR report slot. Also, in the example of FIG. 13, when the embodiment 3.2.2-2a (but without any reinterpretation) is followed, the UE reports two PHRs (PHR for PUSCH1 and PHR for PUSCH2) for the serving cell 2 in the PHR report slot.

[0163] [Embodiment 3.3] Embodiment 3.3 applies to the case where a UE is configured with multiple cells for PUSCH transmission and the UE provides Type 1 PHR for PUSCH transmission using PUSCH repetition type B with nominal repetition over multiple slots in active UL BWP b1 and overlapping with one or more slots in active UL BWP b2, the UE provides Type 1 PHR for a first PUSCH in a first slot of the one or more slots in b2 that overlap with the multiple slots in b1.

[0164] Note that the Type 1 PHR of serving cell 2 is transmitted using PUSCH in a slot of serving cell 1. Also, the Type 1 PHR of serving cell 2 is based on actual PUSCH transmission. Furthermore, the first PUSCH in the first slot that overlaps with the multiple slots of the nominal repetition of serving cell 1 (the multiple slots may be called PHR report slots) is one of the MTRP PUSCH repetitions.

[0165] The embodiment 3.3 is broadly divided into an embodiment 3.3.1 in which the UE reports one PHR as the PHR of the serving cell 2, and an embodiment 3.3.2 in which the UE reports two PHRs.

[0166] The embodiments 3.3.1 and 3.3.2 may be embodiments in which the above-mentioned embodiments 3.1.1 and 3.1.2 are read as follows: In the embodiment 3.3.1a / 3.3.2a, "the slot of serving cell 2 that overlaps with the PHR reporting slot of serving cell 1" is read as "the first slot of serving cell 2 that completely overlaps with multiple nominal repeat slots of serving cell 1", -Embodiment 3.3.1b / 3.3.2b: "A slot of serving cell 2 that overlaps with a PHR reporting slot of serving cell 1" is read as "multiple slots of serving cell 2 that completely overlap with multiple nominal repeat slots of serving cell 1".

[0167] In addition, in the embodiments 3.3.1a / 3.3.2a and 3.3.1b / 3.3.2b, the above-mentioned replacement "completely overlap" may be replaced with "overlapping." Also, the "first slot of serving cell 2" in the embodiments 3.3.1a / 3.3.2a may be replaced with "the first slot of the multiple slots of serving cell 2."

[0168] Note that embodiment 3.3.1a / 3.3.2a is collectively referred to as embodiment 3.3a. Also, embodiment 3.3.1b / 3.3.2b is collectively referred to as embodiment 3.3b. Note that embodiments that do not require reinterpretation may be used as is. For example, embodiments 3.1.1-4 to 3.1.1-6, 3.1.2-2, etc. can be applied as is because "slots of serving cell 2 that overlap with PHR reporting slots of serving cell 1" do not appear.

[0169] [Third embodiment PHR MAC CE] In a third embodiment, the UE may report one or two actual PHRs per serving cell.

[0170] In the third embodiment, the PHR MAC CE may include one or two PHR fields for each serving cell. The PHR MAC CE may include a field indicating that one or two PHRs are reported. This field may be represented by one bit. This field may be included for each serving cell or may be included in relation to a specific serving cell. It should be noted that this field may be represented by two bits, in which case this field may indicate that one PHR for TRP1 is reported, one PHR for TRP2 is reported, or two PHRs are reported. If one or two actual PHRs are "reported" for a serving cell according to the third embodiment, the PHR MAC CE may include one or two PHR fields for the serving cell. The PHR MAC CE may have the configuration of FIG. 4A, for example.

[0171] Also, in the third embodiment, the PHR MAC CE may always include two PHR fields for each serving cell. For a serving cell, if one actual PHR is "reported" according to the third embodiment, the PHR MAC CE may include two PHR fields with the same value for the serving cell (this value may be calculated according to the "reported" actual PHR). This PHR MAC CE may have the configuration of FIG. 4B, for example.

[0172] Also, in the third embodiment, the PHR MAC CE may always include two PHR fields for each serving cell. If for a serving cell, it is determined that one actual PHR is "reported" based on the third embodiment, the PHR MAC CE may include two PHR fields for the serving cell. Of these PHR fields, one may indicate an actual PHR for the TRP for which the actual PHR is "reported", and the other may indicate a virtual TRP for the other TRP. As described above in embodiment 1.2.2, this virtual PHR may be calculated based on default power control parameters, and the PHR MAC CE may include a field indicating whether the PHR for a TRP is a virtual PHR or not. Unless otherwise noted, the embodiment 1.2.2 may be followed. This PHAR MAC CE may have the configuration of FIG. 4C, for example.

[0173] According to the third embodiment described above, the UE can appropriately generate / transmit a PHR report in a case where PUSCH transmissions of a plurality of cells overlap.

[0174] According to the third embodiment described above, the UE can suitably trigger the PHR MAC CE transmission.

[0175] <Fourth embodiment> The fourth embodiment relates to the case where MTRP PUSCH repetition is supported and separate power control (e.g., using separate PL-RS) is supported for different TRPs. Note that the fourth embodiment may be applied regardless of the support of separate power control.

[0176] In Rel.16 NR, one of the triggering events of PHR is an event based on path loss variation. For example, PHR may be triggered if the path loss for at least one activated serving cell of any MAC entity used as a path loss reference for UL transmission varies beyond a certain threshold since the last transmission of PHR. The path loss variation may be the difference between the path loss in this last transmission and the path loss in this UL transmission.

[0177] In the fourth embodiment, the path loss at the last transmission of a PHR in the MAC entity (hereinafter also referred to as the “path loss of the last transmission”, the “last path loss”, the “path loss measured at the path loss reference at the time of the last transmission of the PHR”, etc.) may be any of the following: Case x1: based on actual PUSCH transmission and based on MTRP PUSCH repetition (e.g., MTRP repetition is specified by DCI); Case x2: Based on actual PUSCH transmission, based on STRP PUSCH repetition or single transmission (e.g. STRP repetition is specified by DCI or repetition number=1 is specified by DCI); · Case x3: Based on reference PUSCH transmission.

[0178] In addition, in the fourth embodiment, the path loss in a current new UL transmission in the MAC entity (hereinafter also referred to as "path loss of the current transmission", "current path loss", "path loss measured at the path loss reference at the present time", etc.) may also fall into any of the above cases x1 to x3.

[0179] Therefore, when determining the path loss variation of the serving cell, the following nine cases y1-y9 are considered, which are combinations of the last path loss cases x1-x3 and the current path loss cases x1-x3: Case y1: The last path loss is case x1 and the current path loss is case x1. Case y2: The last path loss is case x1 and the current path loss is case x2. Case y3: The last path loss is case x1 and the current path loss is case x3. Case y4: The last path loss is case x2 and the current path loss is case x1. Case y5: The last path loss is case x2 and the current path loss is case x2. Case y6: The last path loss is case x2 and the current path loss is case x3. Case y7: The last path loss is case x3 and the current path loss is case x1. Case y8: The last path loss is case x3 and the current path loss is case x2. Case y9: The last path loss is case x3, and the current path loss is case x3.

[0180] In either case, the path loss for the PUSCH repetition of TRP1 / 2 of the current transmission is compared with the path loss for the PUSCH repetition of TRP1 / 2 of the last transmission to determine the path loss variation for PHR triggering.

[0181] For cases y1, y4 and y7 (ie, the current path loss is case x1), the current path loss for TRP1 / 2 is calculated based on the actual transmission.

[0182] For cases y2, y5, and y8 (i.e., the current path loss is case x2), the current path loss for the TRP specified for the current transmission is calculated based on the actual transmission, while the current path loss for the TRP not specified for the current transmission is calculated based on the reference PUSCH transmission (in other words, similar to the virtual PHR calculation).

[0183] For cases y3, y6 and y9 (ie, the current path loss is case x3), the current path loss for TRP1 / 2 is calculated based on the reference PUSCH transmission.

[0184] For cases y1-y3 (i.e., the final path loss is case x1), the final path loss for TRP1 / 2 is calculated based on the actual transmission.

[0185] For cases y4-y6 (i.e., the final path loss is case x2), the final path loss for the TRP designated for the final transmission is calculated based on the actual transmission. Meanwhile, the final path loss for the TRP not designated for the final transmission may be calculated based on the reference PUSCH transmission (in other words, similar to the virtual PHR calculation). Note that for a TRP not designated for the final transmission, the current path loss for that TRP may be compared with the final path loss for the TRP designated for the final transmission.

[0186] For cases y7-y9 (i.e., the last path loss is case x3), the last path loss for TRP1 / 2 may be calculated based on the reference PUSCH transmission. Note that for cases y7-y9 (i.e., the last path loss is case x3), the last path loss for TRP1 / 2 may be calculated based on the last transmission of the PHR based on the actual PUSCH transmission for TRP1 / 2 before the last transmission of the PHR based on the reference PUSCH. Figure 14 is a diagram showing an example of the calculation of the path loss variation for each TRP in case y7. The illustrated "PUSCH with MTRP" is the current transmission corresponding to the MTRP PUSCH repetition. The last transmission of the PHR in this MAC entity is depicted with a dashed line, and the last path loss for TRP1 / 2 may be calculated based on this reference PUSCH. Meanwhile, the last path loss for TRP1 / 2 may be derived based on the actual PUSCH of TRP1 / 2 before this last transmission. In this case, the path loss fluctuation for TRP1 / 2 (the difference between the last path loss and the current path loss) may be obtained based on the current actual PUSCH transmission for TRP1 / 2 and the previous actual PUSCH transmission for TRP1 / 2. These "previous actual PUSCH transmissions" may be the actual PUSCH transmissions for TRP1 / 2 when the PHR was last reported, or the actual PUSCH transmissions for TRP1 / 2 corresponding to the PHR when the PHR for TRP1 / 2 was last reported. For case y8, "PUSCH with MTRP" in FIG. 14 may be replaced with "PUSCH with STRP".

[0187] In addition, for the path loss calculated based on the reference PUSCH transmission, different default PL-RSs (e.g., a PL-RS corresponding to pusch-PathlossReferenceRS-Id = the first value and a PL-RS corresponding to pusch-PathlossReferenceRS-Id = the second value) may be used for TRP1 and TRP2, or a common default PL-RS (e.g., a PL-RS corresponding to pusch-PathlossReferenceRS-Id = 0) may be used for both TRP1 and TRP2.

[0188] For a serving cell, a PHR may be triggered if at least one of the following conditions z1-z6 is met: Condition z1: The path loss variation of the PUSCH repeat to TRP1 or the path loss variation of the PUSCH repeat to TRP2 is greater than a threshold value. Condition z2: Both the path loss variation of the PUSCH repeat to TRP1 and the path loss variation of the PUSCH repeat to TRP2 are greater than the respective thresholds. Condition z3: The path loss variation of the PUSCH repetition to TRP1 is greater than a threshold. Condition z4: The path loss variation of the PUSCH repetition to TRP2 is greater than the threshold. Condition z5: The path loss variation for the TRP specified for the current transmission is greater than a threshold. · Condition z6: The path loss variation for the TRP specified for the last transmission is greater than a threshold.

[0189] The threshold value may be given by, for example, an upper layer parameter phr-Tx-PowerFactorChange. Note that the threshold value may be set to different values ​​(independently) for TRP1 and TRP2, or a single value may be set and applied to both TRP1 and TRP2.

[0190] For example, when cases y1, y3, y7, and y9 are followed for a serving cell, the UE may trigger a PHR if at least one of the above conditions z1-z4 is satisfied. Note that in case y9, the UE may trigger a PHR if a condition other than the above conditions z1-z4 is satisfied. For example, the UE may compare a current path loss based on a reference PUSCH transmission with a last path loss based on a reference PUSCH transmission to derive a path loss variation. If the path loss variation is greater than a threshold (e.g., phr-Tx-PowerFactorChange), the PHR may be triggered.

[0191] If cases y2 and y8 are followed for a serving cell, the UE may trigger a PHR if at least one of the above conditions z1-z5 is satisfied. In case y8, the UE may trigger a PHR if a condition other than the above conditions z1-z5 is satisfied. For example, the UE may compare a current path loss based on an actual PUSCH transmission with a last path loss based on a reference PUSCH transmission, regardless of which TRP is specified for the current transmission, to derive a path loss variation. If the path loss variation is greater than a threshold (e.g., phr-Tx-PowerFactorChange), a PHR may be triggered.

[0192] If cases y4 and y6 are followed for a serving cell, the UE may trigger a PHR if at least one of the above conditions z1-z4 and z6 is satisfied. In case y6, the UE may trigger a PHR if a condition other than the above conditions z1-z4 and z6 is satisfied. For example, the UE may compare the current path loss based on the reference PUSCH transmission with the last path loss based on the actual transmission, regardless of which TRP is specified for the past transmission, to derive a path loss variation. If the path loss variation is greater than a threshold (e.g., phr-Tx-PowerFactorChange), a PHR may be triggered.

[0193] If case y5 is followed for a serving cell, the UE may trigger a PHR if at least one of the above conditions z1-z6 is satisfied. In case y5, the UE may trigger a PHR if a condition other than the above conditions z1-z6 is satisfied. For example, the UE may compare the current path loss based on the actual transmission with the last path loss based on the actual transmission regardless of which TRP is specified for the current / last transmission, and derive a path loss variation. If the path loss variation is greater than a threshold (e.g., phr-Tx-PowerFactorChange), a PHR may be triggered.

[0194] According to the fourth embodiment described above, the UE can suitably trigger the transmission of a PHR to the TRP based on a path loss variation.

[0195] <Fifth embodiment> The fifth embodiment relates to a prohibit timer (eg, phr-ProhibitTimer).

[0196] In conjunction with a TRP, a prohibit timer may satisfy at least one of the following: Embodiment 5.1: One inhibit timer is set and maintained (or utilized or applied) for all TRPs; · Embodiment 5.2: One prohibit timer is set and maintained (or utilized or applied) for one TRP.

[0197] In the case of embodiment 5.1, the UE may assume that no PHR for any TRP is triggered while the prohibition timer is running. If the prohibition timer expires or has expired, and at least one condition (trigger event) is met, for example, the path loss variation exceeds a threshold as shown in the fourth embodiment, the PHR may be triggered. When a PHR (PHR MAC CE) for any TRP is transmitted, the prohibition timer may be restarted. According to embodiment 5.1, there is no need to manage multiple prohibition timers for multiple TRPs, which reduces the complexity of the UE.

[0198] In addition, in the present disclosure, "the timer starts (or restarts)" may be read as "the MAC entity of the UE starts (or restarts) the timer".

[0199] In the case of embodiment 5.2, different prohibition timers may be set for the two TRPs. For example, a first prohibition timer (phr-ProhibitTimer-1) may be set for TRP1, and a second prohibition timer (phr-ProhibitTimer-2) may be set for TRP2. The values ​​of these timers may be the same or different. For example, the UE may assume that a PHR for a certain TRP is not triggered while the prohibition timer for that TRP is running.

[0200] In the case of embodiment 5.2, the UE may trigger a PHR when at least one condition (trigger event) is satisfied, for example, that the path loss variation exceeds a threshold, as shown in the fourth embodiment, and any one or a combination of the following is satisfied: the first prohibition timer or the second prohibition timer expires or has expired; Both the first and second prohibit timers expire or have expired; A first prohibit timer expires or has expired, A second prohibit timer expires or has expired, The prohibition timer for the TRP specified for the current transmission expires or has expired, · The prohibition timer for the TRP specified for the last transmission expires or has expired.

[0201] Of these prohibition timer conditions, the same condition may be applied to one or more trigger events shown in the fourth embodiment, or different conditions may be applied to different trigger events.

[0202] For embodiment 5.2, the inhibit timer for a TRP may be restarted if any of the following is met: - A PHR (PHR MAC CE) for any TRP is sent, - A PHR for the relevant TRP is sent, The actual PHR for that particular TRP is sent.

[0203] According to embodiment 5.2, it is possible to reduce cases in which PHR transmission for one TRP inhibits PHR transmission for other TRPs.

[0204] 15A and 15B are diagrams illustrating an example of control regarding the prohibition timer of the fifth embodiment. FIGs. 15A and 15B illustrate cases in which the UE utilizes the prohibition timer of the embodiments 5.1 and 5.2, respectively.

[0205] In Figure 15A, when the PHR for TRP1 is sent, the inhibit timer starts again. No PHR for any TRP will be triggered / sent until this inhibit timer expires.

[0206] In Figure 15B, when the PHR for TRP1 is sent, the prohibition timer for TRP1 starts again. Until this prohibition timer expires, the PHR for TRP1 will not be triggered. Meanwhile, the PHR for TRP2 may be triggered / sent even if the prohibition timer for TRP1 is running.

[0207] According to the fifth embodiment described above, the UE can suitably trigger the transmission of a PHR to a TRP based on the prohibition timer.

[0208] Sixth embodiment The sixth embodiment relates to the number of PHRs to report.

[0209] Whether to report one or two PHRs for each serving cell (or for a particular serving cell) may be configured by higher layer signaling (e.g., RRC parameters), may be indicated by physical layer signaling (e.g., DCI), may be determined based on a combination of these, or may be determined by the UE based on conditions.

[0210] This condition may be, for example, whether MTRP repetition, STRP repetition, or single transmission is specified. For example, the UE may decide to report one PHR if STRP repetition or single transmission is specified (case 1), and decide to report two PHRs if MTRP repetition is specified (case 2).

[0211] The above condition may also be whether the reported PHR is a real PHR or a virtual PHR. For example, the UE may decide to report one PHR when a virtual PHR is reported, and decide to report two PHRs when a real PHR is reported.

[0212] Also, the above conditions may control PHR reporting according to any embodiment / case of the third embodiment described above.

[0213] When it is configured / instructed / decided to report two PHRs per serving cell (or for a particular serving cell), the type of each PHR (in other words, whether the PHR is an actual PHR or a virtual PHR) may be configured by higher layer signaling (e.g., an RRC parameter), may be indicated by physical layer signaling (e.g., a DCI), may be determined based on a combination of these, or may be determined by the UE based on conditions.

[0214] The condition may be, for example, whether MTRP repetition, STRP repetition, or single transmission is specified. For example, the UE may decide to report a real PHR for one TRP designated (or corresponding) for PUSCH transmission and a virtual PHR for another TRP when STRP repetition or single transmission is specified (case 1). Also, the condition may be whether the reported PHR is a real PHR or a virtual PHR.

[0215] Also, the above conditions may control PHR reporting according to any embodiment / case of the third embodiment described above.

[0216] Whether to report one or two PHRs per serving cell (or for a particular serving cell) may be determined based on a triggering event.

[0217] Whether to report one or two PHRs for each serving cell (or for a particular serving cell) may be determined by the PHR being triggered based on a particular trigger event for path loss variation (embodiment 6.1).

[0218] In embodiment 6.1, for example, if a PHR is triggered by both the path loss variation of a PUSCH repetition to TRP1 and the path loss variation of a PUSCH repetition to TRP2 being greater than a threshold (condition z2 above), the UE may report two PHRs for the PUSCHs for the two TRPs.

[0219] In embodiment 6.1, for example, if a PHR is triggered by the path loss variation of a PUSCH repetition to TRP1 or the path loss variation of a PUSCH repetition to TRP2 being greater than a threshold (condition z1 above), the UE may report two PHRs for the PUSCHs for the two TRPs, or may report one PHR for the TRP whose path loss variation is greater than the threshold.

[0220] Whether to report one or two PHRs for each serving cell (or for a particular serving cell) may be determined by whether the PHR is triggered under a particular prohibition timer condition (embodiment 6.2).

[0221] In embodiment 6.2, for example, if a PHR is triggered when both the first and second prohibition timers expire or expire, the UE may report two PHRs for PUSCHs for two TRPs.

[0222] In embodiment 6.2, for example, if a PHR is triggered when the first or second prohibition timer expires or has expired, the UE may report two PHRs for PUSCHs for the two TRPs, or may report one PHR for the TRP corresponding to the prohibition timer that expires / has expired.

[0223] In addition, when the reporting of two PHRs is determined by embodiment 6.1 and the reporting of one PHR is determined by embodiment 6.2, or when the reporting of one PHR is determined by embodiment 6.1 and the reporting of two PHRs is determined by embodiment 6.2, the UE may follow the decision of embodiment 6.1 or the decision of embodiment 6.2.

[0224] In addition, if the reporting of one PHR is determined by embodiment 6.1 and the reporting of one PHR is determined by embodiment 6.2, and these PHRs are PHRs for different TRPs, the UE may follow the decision of embodiment 6.1, may follow the decision of embodiment 6.2, or may report these two PHRs for the two TRPs.

[0225] According to the sixth embodiment described above, the UE can appropriately determine how many PHRs to report.

[0226] <Other> It should be noted that at least one of the above-described embodiments may be applied only to UEs that have reported or support a particular UE capability.

[0227] The specific UE capabilities may indicate at least one of the following: Whether to support PUSCH repetition for multiple TRPs; ·Whether to support PHR for each TRP; ·Whether to support actual PHR for each TRP; · Whether to support virtual PHR for each TRP; Whether to support PHR triggering per TRP (e.g. based on path loss variation) · Whether to support per-TRP prohibit timers.

[0228] In addition, the above specific UE capabilities may be determined for each serving cell.

[0229] Also, at least one of the above-mentioned embodiments may be applied when the UE is configured with specific information related to the above-mentioned embodiments by higher layer signaling (when not configured, for example, the operation of Rel.15 / 16 is applied). For example, the specific information may be information indicating that PUSCH repetition of multi-TRP is enabled, information indicating that PHR / actual PHR / virtual PHR / PHR triggering / prohibition timer is enabled / configured for each TRP, any RRC parameter for a specific release (e.g., Rel.17), etc. Also, the UE may be configured using higher layer parameters as to which of the above-mentioned embodiments / cases / conditions the PHR control is based on.

[0230] Note that the above-described embodiment may be applied to the case where PUSCH repetition type A / type B is used.

[0231] It should be noted that the above-described embodiment may be applied when a specific mapping pattern of MTRP repetition (cyclical, sequential, half-half, etc.) is used.

[0232] (Wireless communication system) A configuration of a wireless communication system according to an embodiment of the present disclosure will be described below. In this wireless communication system, communication is performed using any one of the wireless communication methods according to the above embodiments of the present disclosure or a combination of these methods.

[0233] 16 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. The wireless communication system 1 may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), or the like, which are specified by the Third Generation Partnership Project (3GPP).

[0234] Furthermore, the wireless communication system 1 may support dual connectivity between a plurality of Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), and the like.

[0235] In EN-DC, the LTE (E-UTRA) base station (eNB) is the master node (MN) and the NR base station (gNB) is the secondary node (SN). In NE-DC, the NR base station (gNB) is the MN and the LTE (E-UTRA) base station (eNB) is the SN.

[0236] The wireless communication system 1 may support dual connectivity between multiple base stations in the same RAT (for example, dual connectivity in which both the MN and the SN are NR base stations (gNBs) (NR-NR Dual Connectivity (NN-DC))).

[0237] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with a relatively wide coverage, and base stations 12 (12a-12c) that are arranged in the macrocell C1 and form a small cell C2 that is narrower than the macrocell C1. A user terminal 20 may be located in at least one of the cells. The arrangement and number of each cell and user terminal 20 are not limited to the embodiment shown in the figure. Hereinafter, when there is no need to distinguish between the base stations 11 and 12, they will be collectively referred to as a base station 10.

[0238] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of carrier aggregation (CA) using multiple component carriers (CC) and dual connectivity (DC).

[0239] Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)). The macro cell C1 may be included in FR1, and the small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and FR2 may be a frequency band above 24 GHz (above-24 GHz). Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may correspond to a frequency band higher than FR2.

[0240] Furthermore, the user terminal 20 may perform communication in each CC using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD).

[0241] The multiple base stations 10 may be connected by wire (e.g., optical fiber conforming to Common Public Radio Interface (CPRI), X2 interface, etc.) or wirelessly (e.g., NR communication). For example, when NR communication is used as a backhaul between the base stations 11 and 12, the base station 11 corresponding to the upper station may be called an Integrated Access Backhaul (IAB) donor, and the base station 12 corresponding to the relay station (relay) may be called an IAB node.

[0242] The base station 10 may be connected to the core network 30 directly or via another base station 10. The core network 30 may include at least one of, for example, an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a Next Generation Core (NGC), and the like.

[0243] The user terminal 20 may be a terminal compatible with at least one of communication methods such as LTE, LTE-A, and 5G.

[0244] In the wireless communication system 1, a wireless access scheme based on Orthogonal Frequency Division Multiplexing (OFDM) may be used. For example, in at least one of the downlink (DL) and the uplink (UL), Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), etc. may be used.

[0245] The radio access scheme may be called a waveform. In the wireless communication system 1, other radio access schemes (for example, other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.

[0246] In the wireless communication system 1, a downlink shared channel (Physical Downlink Shared Channel (PDSCH)) shared by each user terminal 20, a broadcast channel (Physical Broadcast Channel (PBCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), etc. may be used as a downlink channel.

[0247] In addition, in the wireless communication system 1, an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) shared by each user terminal 20, an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)), etc. may be used as an uplink channel.

[0248] The PDSCH transmits user data, higher layer control information, a System Information Block (SIB), etc. The PUSCH may transmit user data, higher layer control information, etc. Furthermore, the PBCH may transmit a Master Information Block (MIB).

[0249] Lower layer control information may be transmitted by the PDCCH. The lower layer control information may include, for example, Downlink Control Information (DCI) including scheduling information of at least one of the PDSCH and the PUSCH.

[0250] In addition, DCI for scheduling PDSCH may be called DL assignment, DL DCI, etc., and DCI for scheduling PUSCH may be called UL grant, UL DCI, etc. In addition, PDSCH may be replaced with DL data, and PUSCH may be replaced with UL data.

[0251] A control resource set (CORESET) and a search space may be used to detect the PDCCH. The CORESET corresponds to resources to search for DCI. The search space corresponds to a search region and a search method for PDCCH candidates. One CORESET may be associated with one or multiple search spaces. The UE may monitor a CORESET associated with a certain search space based on the search space configuration.

[0252] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be called a search space set. Note that the terms "search space," "search space set," "search space setting," "search space set setting," "CORESET," and "CORESET setting" in the present disclosure may be read as interchangeable terms.

[0253] The PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), delivery acknowledgement information (which may be called, for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and a scheduling request (SR). The PRACH may transmit a random access preamble for establishing a connection with a cell.

[0254] In the present disclosure, a downlink, an uplink, etc. may be expressed without adding "link." Also, various channels may be expressed without adding "Physical" to the beginning of the channels.

[0255] In the wireless communication system 1, a synchronization signal (SS), a downlink reference signal (DL-RS), etc. may be transmitted. In the wireless communication system 1, as the DL-RS, a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc. may be transmitted.

[0256] The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including the SS (PSS, SSS) and the PBCH (and the DMRS for the PBCH) may be called an SS / PBCH block, an SS Block (SSB), or the like. In addition, the SS, SSB, and the like may also be called a reference signal.

[0257] Furthermore, in the wireless communication system 1, a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. may be transmitted as an uplink reference signal (UL-RS). Note that the DMRS may be called a user equipment specific reference signal (UE-specific reference signal).

[0258] (base station) 17 is a diagram showing an example of the configuration of a base station according to an embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140 may be provided.

[0259] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and the base station 10 may be assumed to have other functional blocks necessary for wireless communication. Some of the processes of each unit described below may be omitted.

[0260] The control unit 110 performs overall control of the base station 10. The control unit 110 can be configured with a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

[0261] The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may control transmission and reception using the transmission and reception unit 120, the transmission and reception antenna 130, and the transmission path interface 140, measurement, etc. The control unit 110 may generate data, control information, sequences, etc. to be transmitted as signals, and transfer them to the transmission and reception unit 120. The control unit 110 may perform call processing (setting, release, etc.) of communication channels, status management of the base station 10, management of radio resources, etc.

[0262] The transceiver unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transceiver unit 120 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

[0263] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or may be configured from a transmitting unit and a receiving unit. The transmitting unit may be configured from a transmission processing unit 1211 and an RF unit 122. The receiving unit may be configured from a reception processing unit 1212, an RF unit 122, and a measurement unit 123.

[0264] The transmitting / receiving antenna 130 can be composed of an antenna described based on common understanding in the technical field to which the present disclosure relates, such as an array antenna.

[0265] The transceiver 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 120 may receive the above-mentioned uplink channel, uplink reference signal, etc.

[0266] The transceiver 120 may form at least one of a transmission beam and a reception beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), or the like.

[0267] The transceiver 120 (transmission processing unit 1211) may perform Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (e.g., RLC retransmission control), Medium Access Control (MAC) layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 110, and generate a bit string to be transmitted.

[0268] The transceiver 120 (transmission processing unit 1211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, Discrete Fourier Transform (DFT) processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.

[0269] The transceiver unit 120 (RF unit 122) may perform modulation to a radio frequency band, filtering, amplification, and the like on the baseband signal, and transmit the radio frequency band signal via the transceiver antenna .

[0270] On the other hand, the transceiver unit 120 (RF unit 122) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency signal received by the transceiver antenna .

[0271] The transceiver 120 (reception processing unit 1212) may apply reception processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, thereby acquiring user data, etc.

[0272] The transceiver 120 (measurement unit 123) may perform measurements on the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc., based on the received signal. The measurement unit 123 may measure received power (e.g., Reference Signal Received Power (RSRP)), received quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 110.

[0273] The transmission path interface 140 may transmit and receive signals (backhaul signaling) between devices included in the core network 30, other base stations 10, etc., and may acquire and transmit user data (user plane data) for the user terminal 20, control plane data, etc.

[0274] The transmitting section and receiving section of the base station 10 in the present disclosure may be configured by at least one of the transmitting / receiving section 120, the transmitting / receiving antenna 130, and the transmission path interface 140.

[0275] In addition, the transceiver 120 may transmit, to the user terminal 20, downlink control information (DCI) for scheduling Physical Uplink Shared Channel (PUSCH) transmission using one sounding reference signal resource indicator (SRI) for a certain serving cell.

[0276] The transceiver 120 may receive a Power Headroom Report (PHR) Medium Access Control (MAC) control element including information indicating whether one or two PHRs are reported for the serving cell.

[0277] Furthermore, the transceiver 120 may transmit configuration information for transmitting a Power Headroom Report (PHR) Medium Access Control (MAC) control element in a certain serving cell to the user terminal 20. The information may be at least one piece of information such as phr-ProhibitTimer, phr-PeriodicTimer, and phr-Tx-PowerFactorChange. The information may be included in the configuration information of the PHR.

[0278] The transceiver 120 may receive the PHR MAC CE including one or two PHRs for another serving cell when the transmission of the MAC control element overlaps in time with repeated Physical Uplink Shared Channel (PUSCH) transmission using multiple Sounding Reference Signal Resource Indicators (SRIs) in the other serving cell.

[0279] In addition, the transceiver 120 may receive a PHR MAC control element for the PHR that is triggered based on a first path loss in the last transmission of the PHR and a second path loss in a current new uplink transmission for the serving cell, which are calculated by determining whether the PHR is based on a Physical Uplink Shared Channel (PUSCH) transmission using one sounding reference signal resource indicator (SRI), based on a PUSCH repeated transmission using multiple SRIs, or based on a reference PUSCH transmission.

[0280] (User terminal) 18 is a diagram showing an example of the configuration of a user terminal according to an embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Note that the user terminal 20 may include one or more of each of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230.

[0281] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and the user terminal 20 may be assumed to have other functional blocks necessary for wireless communication. Some of the processes of each unit described below may be omitted.

[0282] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be configured with a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

[0283] The control unit 210 may control signal generation, mapping, etc. The control unit 210 may control transmission / reception, measurement, etc. using the transmission / reception unit 220 and the transmission / reception antenna 230. The control unit 210 may generate data, control information, sequences, etc. to be transmitted as signals, and transfer them to the transmission / reception unit 220.

[0284] The transmitting / receiving unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transmitting / receiving unit 220 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmitting / receiving circuit, and the like, which are described based on common understanding in the technical field related to the present disclosure.

[0285] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may be composed of a transmission processing unit 2211 and an RF unit 222. The receiving unit may be composed of a reception processing unit 2212, an RF unit 222, and a measurement unit 223.

[0286] The transmitting / receiving antenna 230 can be composed of an antenna described based on common understanding in the technical field to which this disclosure pertains, such as an array antenna.

[0287] The transceiver 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 220 may transmit the above-mentioned uplink channel, uplink reference signal, etc.

[0288] The transceiver 220 may form at least one of a transmission beam and a reception beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), or the like.

[0289] The transceiver unit 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 210, and generate a bit string to be transmitted.

[0290] The transceiver 220 (transmission processing unit 2211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion on the bit sequence to be transmitted, and output a baseband signal.

[0291] Whether or not to apply the DFT process may be based on the setting of transform precoding. When transform precoding is enabled for a certain channel (e.g., PUSCH), the transceiver 220 (transmission processor 2211) may perform the DFT process as the transmission process to transmit the channel using a DFT-s-OFDM waveform, and may not perform the DFT process as the transmission process if transform precoding is enabled for the channel.

[0292] The transceiver unit 220 (RF unit 222) may perform modulation to a radio frequency band, filtering, amplification, and the like on the baseband signal, and transmit the radio frequency band signal via the transceiver antenna 230.

[0293] On the other hand, the transceiver unit 220 (RF unit 222) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency signal received by the transceiver antenna 230.

[0294] The transceiver 220 (reception processing unit 2212) may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, and acquire user data, etc.

[0295] The transceiver 220 (measurement unit 223) may perform measurements on the received signal. For example, the measurement unit 223 may perform RRM measurements, CSI measurements, etc. based on the received signal. The measurement unit 223 may measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 210.

[0296] In addition, the transmitting section and the receiving section of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting / receiving section 220 and the transmitting / receiving antenna 230.

[0297] The transceiver 220 may transmit a Physical Uplink Shared Channel (PUSCH) using one sounding reference signal resource indicator (SRI) for a certain serving cell.

[0298] The control unit 210 may generate a Power Headroom Report (PHR) Medium Access Control (MAC) control element including information indicating whether one or two PHRs are reported for the serving cell.

[0299] In addition, when transmission of a Power Headroom Report (PHR) Medium Access Control (MAC) control element in a serving cell overlaps in time with repeated Physical Uplink Shared Channel (PUSCH) transmission using multiple Sounding Reference Signal Resource Indicators (SRIs) in another serving cell, the control unit 210 may determine one or two PHRs for the other serving cell to be included in the PHR MAC control element.

[0300] The transceiver 220 may transmit the PHR MAC control element.

[0301] In addition, for a certain serving cell, the control unit 210 may calculate a first path loss in the last transmission of a Power Headroom Report (PHR) and a second path loss in a current new uplink transmission by determining whether they are based on a Physical Uplink Shared Channel (PUSCH) transmission using one sounding reference signal resource indicator (SRI), a PUSCH repeated transmission using multiple SRIs, or a reference PUSCH transmission.

[0302] The transceiver unit 220 may transmit a PHR Medium Access Control (MAC) control element for a PHR triggered based on the first path loss and the second path loss.

[0303] (Hardware configuration) The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. The method of realizing each functional block is not particularly limited. That is, each functional block may be realized by using one device that is physically or logically combined, or may be realized by using two or more devices that are physically or logically separated and directly or indirectly connected (for example, by wire, wirelessly, etc.). The functional blocks may be realized by combining the one device or the multiple devices with software.

[0304] Here, the functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs the function of transmission may be called a transmitting unit, a transmitter, and the like. In either case, as described above, the method of realization is not particularly limited.

[0305] For example, a base station, a user terminal, etc. in an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 19 is a diagram showing an example of a hardware configuration of a base station and a user terminal according to an embodiment. The above-mentioned base station 10 and user terminal 20 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0306] In this disclosure, the terms "apparatus," "circuit," "device," "section," "unit," and the like can be read interchangeably. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.

[0307] For example, although only one processor 1001 is shown, there may be multiple processors. Also, the processes may be performed by one processor, or the processes may be performed by two or more processors simultaneously, sequentially, or in other manners. Also, the processor 1001 may be implemented by one or more chips.

[0308] Each function in the base station 10 and the user terminal 20 is realized, for example, by loading a specific software (program) onto hardware such as a processor 1001 and a memory 1002, so that the processor 1001 performs calculations, controls communications via a communication device 1004, and controls at least one of reading and writing of data in the memory 1002 and the storage 1003.

[0309] The processor 1001, for example, operates an operating system to control the entire computer. The processor 1001 may be configured with a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, at least a part of the above-mentioned control unit 110 (210), transmission / reception unit 120 (220), etc. may be realized by the processor 1001.

[0310] Moreover, the processor 1001 reads out programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes according to the programs. As the programs, programs that cause a computer to execute at least a part of the operations described in the above-mentioned embodiments are used. For example, the control unit 110 (210) may be realized by a control program stored in the memory 1002 and operated by the processor 1001, and the other functional blocks may be realized in a similar manner.

[0311] The memory 1002 is a computer-readable recording medium, and may be configured by at least one of, for example, a Read Only Memory (ROM), an Erasable Programmable ROM (EPROM), an Electrically EPROM (EEPROM), a Random Access Memory (RAM), and other suitable storage media. The memory 1002 may be called a register, a cache, a main memory (primary storage device), and the like. The memory 1002 can store a program (program code), a software module, and the like that is executable to implement a wireless communication method according to an embodiment of the present disclosure.

[0312] Storage 1003 is a computer-readable recording medium and may be constituted by at least one of, for example, a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disk (e.g., a Compact Disc ROM (CD-ROM)), a digital versatile disk, a Blu-ray disk), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, stick, key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be referred to as an auxiliary storage device.

[0313] The communication device 1004 is hardware (transmission / reception device) for performing communication between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., in order to realize at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD). For example, the above-mentioned transmission / reception unit 120 (220), transmission / reception antenna 130 (230), etc. may be realized by the communication device 1004. The transmission / reception unit 120 (220) may be implemented as a transmission unit 120a (220a) and a reception unit 120b (220b) that are physically or logically separated.

[0314] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, a Light Emitting Diode (LED) lamp, etc.) that performs output to the outside. The input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0315] In addition, each device such as the processor 1001 and the memory 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0316] Furthermore, the base station 10 and the user terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable gate array (FPGA), etc., and some or all of the functional blocks may be realized using the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0317] (Modification) In addition, the terms explained in this disclosure and the terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, a channel, a symbol, and a signal (signal or signaling) may be read as mutually interchangeable. A signal may also be a message. A reference signal may also be abbreviated as RS, and may also be called a pilot, pilot signal, etc. depending on the applied standard. A component carrier (CC) may also be called a cell, a frequency carrier, a carrier frequency, etc.

[0318] A radio frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting a radio frame may be called a subframe. Furthermore, a subframe may be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0319] Here, the numerology may be a communication parameter applied to at least one of the transmission and reception of a signal or channel, and may indicate at least one of, for example, a subcarrier spacing (SCS), a bandwidth, a symbol length, a cyclic prefix length, a transmission time interval (TTI), a number of symbols per TTI, a radio frame structure, a specific filtering process performed by a transceiver in the frequency domain, and a specific windowing process performed by a transceiver in the time domain.

[0320] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol, a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol, etc.) in the time domain. A slot may also be a time unit based on numerology.

[0321] A slot may include multiple minislots. Each minislot may be composed of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may be composed of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (PUSCH) mapping type B.

[0322] A radio frame, a subframe, a slot, a minislot, and a symbol each represent a time unit for transmitting a signal. A different name may be used for the radio frame, the subframe, the slot, the minislot, and the symbol. Note that the time units such as a frame, a subframe, a slot, a minislot, and a symbol in the present disclosure may be read as interchangeable with each other.

[0323] For example, one subframe may be called a TTI, multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in the existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

[0324] Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. Note that the definition of TTI is not limited to this.

[0325] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) in which a transport block, a code block, a code word, etc. are actually mapped may be shorter than the TTI.

[0326] In addition, when one slot or one minislot is called TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit of scheduling. Also, the number of slots (minislots) constituting the minimum time unit of scheduling may be controlled.

[0327] A TTI having a time length of 1 ms may be called a normal TTI (TTI in 3GPP Rel. 8-12), a normal TTI, a long TTI, a normal subframe, a normal subframe, a long subframe, a slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a minislot, a subslot, a slot, etc.

[0328] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length exceeding 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

[0329] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of the numerology, and may be, for example, 12. The number of subcarriers included in an RB may be determined based on the numerology.

[0330] In addition, an RB may include one or more symbols in the time domain, and may have a length of one slot, one minislot, one subframe, or one TTI. Each of one TTI, one subframe, etc. may be composed of one or more resource blocks.

[0331] In addition, one or more RBs may be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

[0332] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0333] A Bandwidth Part (BWP), which may also be referred to as a fractional bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a numerology on a carrier, where the common RBs may be identified by the index of the RBs relative to a common reference point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

[0334] The BWP may include a UL BWP (a BWP for UL) and a DL BWP (a BWP for DL). One or more BWPs may be configured for a UE within one carrier.

[0335] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given channel / signal outside the active BWP. Note that the terms "cell", "carrier", etc. in this disclosure may be replaced with "BWP".

[0336] The above-mentioned structures of radio frames, subframes, slots, minislots, and symbols are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, and other configurations can be changed in various ways.

[0337] In addition, the information, parameters, etc. described in the present disclosure may be represented using absolute values, may be represented using relative values ​​from a predetermined value, or may be represented using other corresponding information. For example, a radio resource may be indicated by a predetermined index.

[0338] The names used for parameters and the like in this disclosure are not limiting in any way. Furthermore, the formulas and the like using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not limiting in any way.

[0339] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0340] Furthermore, information, signals, etc. may be output from a higher layer to a lower layer and / or from a lower layer to a higher layer. Information, signals, etc. may be input / output via a plurality of network nodes.

[0341] Input and output information, signals, etc. may be stored in a specific location (e.g., memory) or may be managed using a management table. Input and output information, signals, etc. may be overwritten, updated, or added to. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.

[0342] The notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information in the present disclosure may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof.

[0343] The physical layer signaling may be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. The RRC signaling may be called an RRC message, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc. The MAC signaling may be notified, for example, by using a MAC Control Element (CE).

[0344] Furthermore, notification of specified information (e.g., notification that "it is X") is not limited to explicit notification, but may be made implicitly (e.g., by not notifying the specified information or by notifying other information).

[0345] The determination may be made based on a value represented by a single bit (0 or 1), a Boolean value represented as true or false, or by comparing numerical values ​​(e.g., with a predetermined value).

[0346] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0347] Additionally, software, instructions, information, etc. may be transmitted or received over a transmission medium. For example, if the software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave, etc.), then these wired and / or wireless technologies are included within the definition of transmission media.

[0348] As used in this disclosure, the terms "system" and "network" may be used interchangeably. A "network" may refer to devices included in the network (e.g., base stations).

[0349] In this disclosure, terms such as "precoding," "precoder," "weight (precoding weight)," "Quasi-Co-Location (QCL)," "Transmission Configuration Indication state (TCI state)," "spatial relation," "spatial domain filter," "transmit power," "phase rotation," "antenna port," "antenna port group," "layer," "number of layers," "rank," "resource," "resource set," "resource group," "beam," "beam width," "beam angle," "antenna," "antenna element," "panel," and the like may be used interchangeably.

[0350] In this disclosure, terms such as "Base Station (BS)", "radio base station", "fixed station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "access point", "Transmission Point (TP)", "Reception Point (RP)", "Transmission / Reception Point (TRP)", "panel", "cell", "sector", "cell group", "carrier", "component carrier", etc. may be used interchangeably. A base station may also be referred to by terms such as a macro cell, a small cell, a femto cell, a pico cell, etc.

[0351] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the entire coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a small base station for indoor use (Remote Radio Head (RRH))). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or a base station subsystem that provides communication services in this coverage.

[0352] In this disclosure, the terms "Mobile Station (MS)", "user terminal", "User Equipment (UE)", "terminal", etc. may be used interchangeably.

[0353] A mobile station may also be referred to as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0354] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. At least one of the base station and the mobile station may be a device mounted on a moving body, the moving body itself, etc. The moving body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned moving body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may include a device that does not necessarily move during communication operation. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0355] Furthermore, the base station in the present disclosure may be read as a user terminal. For example, each aspect / embodiment of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between a plurality of user terminals (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, an uplink channel, a downlink channel, etc. may be read as a side channel.

[0356] Similarly, the user terminal in the present disclosure may be interpreted as a base station. In this case, the base station 10 may be configured to have the functions of the user terminal 20 described above.

[0357] In the present disclosure, an operation performed by a base station may be performed by its upper node in some cases. It is clear that in a network including one or more network nodes having base stations, various operations performed for communication with terminals may be performed by the base station, one or more network nodes other than the base station (such as, but not limited to, a Mobility Management Entity (MME) and a Serving-Gateway (S-GW)), or a combination thereof.

[0358] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched according to implementation. In addition, the processing procedures, sequences, flow charts, etc. of each aspect / embodiment described in this disclosure may be reordered unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0359] Each aspect / embodiment described in the present disclosure may be implemented using any of a wide variety of standards, including Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE The present invention may be applied to systems using 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), other appropriate wireless communication methods, next-generation systems that are based on these, etc. Also, the present invention may be applied to a combination of multiple systems (for example, a combination of LTE or LTE-A and 5G).

[0360] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0361] Any reference to an element using a designation such as "first," "second," etc., used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must precede the second element in some way.

[0362] The term "determining" as used in this disclosure may encompass a wide variety of actions. For example, "determining" may be considered to be judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., looking up in a table, database, or another data structure), ascertaining, and the like.

[0363] A "determining" may also be considered to be "determining" receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in a memory), etc.

[0364] Also, "determination" may be considered to be "deciding" resolving, selecting, choosing, establishing, comparing, etc. That is, "determination" may be considered to be "deciding" to perform some action.

[0365] Additionally, "judgment (decision)" may be interpreted as "assuming," "expecting," "considering," etc.

[0366] As used in this disclosure, the terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between the elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access."

[0367] In this disclosure, when two elements are connected, they may be considered to be "connected" or "coupled" to one another using one or more wires, cables, printed electrical connections, and the like, as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range, light (both visible and invisible) range, and the like, as some non-limiting and non-exhaustive examples.

[0368] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0369] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Further, when used in this disclosure, the term "or" is not intended to be an exclusive or.

[0370] In this disclosure, where articles have been added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0371] Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The invention according to the present disclosure can be implemented as modified and altered forms without departing from the spirit and scope of the invention defined based on the description of the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the invention according to the present disclosure.

Claims

1. a control unit that determines whether a first path loss in a last transmission of a Power Headroom Report (PHR) and a second path loss in a current new uplink transmission are based on a Physical Uplink Shared Channel (PUSCH) transmission using one Sounding Reference Signal Resource Indicator (SRI), a PUSCH repeated transmission using multiple SRIs, or a reference PUSCH transmission, and calculates the first path loss and the second path loss in a current new uplink transmission for a certain serving cell; a transmitter configured to transmit a Medium Access Control (MAC) control element related to a PHR triggered based on the first path loss and the second path loss.

2. The terminal described in claim 1, wherein the PHR triggered based on the first path loss and the second path loss is triggered when the path loss variation between the first path loss and the second path loss is greater than a threshold set by an upper layer parameter.

3. calculating a first path loss in a last transmission of a Power Headroom Report (PHR) for a certain serving cell and a second path loss in a current new uplink transmission by determining whether the path loss is based on a Physical Uplink Shared Channel (PUSCH) transmission using one Sounding Reference Signal Resource Indicator (SRI), a PUSCH repeated transmission using multiple SRIs, or a reference PUSCH transmission; and transmitting a Medium Access Control (MAC) control element for PHR triggered based on the first path loss and the second path loss.

4. A control unit that determines whether the terminal calculates a first path loss in the last transmission of a Power Headroom Report (PHR) for a certain serving cell and a second path loss in a current new uplink transmission based on a Physical Uplink Shared Channel (PUSCH) transmission using one sounding reference signal resource indicator (SRI), a PUSCH repeated transmission using multiple SRIs, or a reference PUSCH transmission, a receiver for receiving a Medium Access Control (MAC) control element for PHR triggered based on the first path loss and the second path loss.

5. A system having a terminal and a base station, The terminal includes: a control unit that determines whether a first path loss in a last transmission of a Power Headroom Report (PHR) and a second path loss in a current new uplink transmission are based on a Physical Uplink Shared Channel (PUSCH) transmission using one Sounding Reference Signal Resource Indicator (SRI), a PUSCH repeated transmission using multiple SRIs, or a reference PUSCH transmission, and calculates the first path loss and the second path loss in a current new uplink transmission for a certain serving cell; a transmitter configured to transmit a Medium Access Control (MAC) control element related to a PHR triggered based on the first path loss and the second path loss; The base station, A system having a receiver for receiving the MAC control element.

Images