Terminal, wireless communication method, base station and system

Abstract

A terminal according to an aspect of the present disclosure comprises: a control unit that, when the transmission of a Power Headroom Report (PHR) Medium Access Control (MAC) control element in a serving cell temporally overlaps a Physical Uplink Shared Channel (PUSCH) repetitive transmission using a plurality of Sounding Reference Signal Resource Indicators (SRIs) in another serving cell, determines one or two PHRs for the other serving cell that are to be included in the PHR MAC control element; and a transmission unit that transmits the PHR MAC control element. According to an aspect of the present disclosure, a PHR reporting in the case of using an MTRP PUSCH repetition can be appropriately implemented.

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 Universal Mobile Telecommunications System (UMTS) networks, Long Term Evolution (LTE) was specified with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). Also, LTE-Advanced (3GPP Rel. 10-14) was specified with the aim of achieving higher capacity and more advanced features than 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) 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) containing 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.

[0006] In NR, it is considered that one or more Transmission / Reception Points (TRPs) (Multi-TRPs (MTRPs)) perform DL transmission to a UE, and 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 PHR for MTRP PUSCH repetition. If 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 that can appropriately perform 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 one aspect of the present disclosure includes: a first transmission / reception point (TRP) corresponding to a first power headroom report (PHR) and a second transmission / reception point (TRP) corresponding to a second TRP; and downlink control information (DCI). a receiving unit for receiving the When the DCI does not indicate physical uplink shared channel (PUSCH) transmission for the first TRP and the second TRP, First reference for the first TRP TeruP USC H delivery a control unit that calculates the first PHR based on a reference PUSCH transmission for the second TRP and calculates the second PHR based on a second reference PUSCH transmission for the second TRP; and a transmission unit that transmits a Medium Access Control (MAC) control element including a field indicating the first PHR and a field indicating the second PHR. [Effects 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 explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a diagram illustrating an example of a single-entry PHR MAC CE in Rel. 16 NR. [Figure 2] FIG. 2 is a diagram showing an example of a multiple-entry PHR MAC CE in Rel. 16 NR. [Figure 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. [Figure 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 relating 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 INVENTION

[0013] (PHR) In future wireless communication systems (e.g., NR), a UE will transmit a Power Headroom Report (PHR) containing 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 MAC (Medium Access Control) signaling using a PUSCH (Physical Uplink Shared Channel). For example, the PHR is notified using a PHR MAC CE (Control Element) included in a MAC PDU (Protocol Data Unit).

[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 consists of two octets (=16 bits). 'R' in Figure 1 indicates a 1-bit reserved field, and is set to a value of '0', for example.

[0017] 1, 'PH(Type 1, PCell)' denotes a 6-bit field indicating an index for a Type 1 PH of a 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 PUSCH (e.g., taking into account only the power of PUSCH), Type 2 PH may be a PH that takes into account PUCCH (e.g., taking into account the power of both PUSCH and PUCCH), and Type 3 PH may be a PH that takes into account a measurement reference signal (Sounding Reference Signal (SRS)) (e.g., taking into account the power of PUSCH and SRS).

[0019] 'P' in Figure 1 CMAX,f,c ' indicates a 6-bit field, and is the P used in calculating the PH field above.CMAX,f,c This shows the index for the P CMAX,f,c The index for P 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. 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 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 'R' fields depending on the configuration using higher layer signaling to the UE.

[0021] NR also supports a multiple entry PHR MAC CE that includes multiple entries of data similar to the single entry (2 octets) described above. 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 also be called special cells (SpCells).

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

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

[0024] 'P' in Figure 2 CMAX,c The 6-bit field containing the word ' is the P 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 less than 8. If it is 8 or more, the MAC CE can indicate serving cells up to i=31, for example. i ' field may be included.

[0025] In addition, the number attached to the "serving cell" in the PH field and P CMAX,c The number assigned to the field does not necessarily mean the serving cell index, but 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 ' field, 'MPE' field, etc. may be omitted.

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

[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 thereof.

[0029] The MAC signaling may use, 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, one or more Transmission / Reception Points (TRPs) (Multi-TRPs (M-TRPs)) are considered to perform DL transmission to a UE using one or more panels (multi-panels). Also, it is considered that a UE performs UL transmission to one or more TRPs.

[0031] 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, in the case of codebook-based transmission, 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 non-codebook-based transmission, the UE may determine a precoder for PUSCH transmission based on the SRI. Note that the SRI may be specified to the UE by the DCI or may be provided by a higher layer parameter.

[0033] If 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 a field indicating multiple (e.g., two) SRI / TPMIs. 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 be the correspondence specified up to Rel. 16, or may be the correspondence specified in Rel. 17 or later. The correspondence between the SRI / TPMI fields and the SRI / TPMI values ​​may differ for each of the multiple SRI / TPMI fields.

[0035] In option 2, a codepoint 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 being considered that a DCI may dynamically indicate / switch between single PUSCH transmission / repeated PUSCH transmission using a single TRP (Single TRP (STRP)) and repeated PUSCH transmission using multiple TRPs (Multi TRP (MTRP)). This dynamic switching 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] Furthermore, the term "dynamic switch" in the present disclosure may refer to a "switch that uses at least one of higher layer signaling and physical layer signaling." Furthermore, 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 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 interchangeably.

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

[0043] In the present disclosure, RRC, RRC parameter, RRC message, RRC signaling, higher layer parameter, information element (IE), and configuration may be interchangeable. In the present disclosure, MAC CE, update command, and activation / deactivation command 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 (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), TCI state, unified TCI state, common TCI state, QCL, QCL assumption, etc. may be read interchangeably.

[0045] Furthermore, the TCI status identifier (ID) and the TCI status may be interchangeable. The TCI status and the 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, group, cluster, and subset may be interchangeable.

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

[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 the present disclosure, for a single DCI, the i-th TRP (TRP#i) may refer to the i-th TCI state, the i-th CDM group, etc. (i is an integer). For a multi-DCI, the i-th TRP (TRP#i) may refer to the CORESET corresponding to CORESET pool index=i, the i-th TCI state, the i-th 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 multiple PUSCHs (corresponding to different SRIs) using one DCI, sDCI-based MTRP transmission, and activating two TCI states on at least one TCI codepoint may be read interchangeably.

[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) using two DCIs, and setting two CORESET pool indices or CORESET pool index=1 (or a value greater than or equal to 1) may be read interchangeably.

[0053] The repetition in the present disclosure may be interchangeably read as MTRP-based repetition, Rel.17 repetition, repetition applying a different spatial relationship, repetition PUSCH, repetition PUCCH, repetition transmission, etc. Furthermore, the repetition transmission in the following embodiments may correspond to at least one of repetition transmission type A, repetition transmission type B, and other repetition 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 interchangeably 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 interchangeably 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, etc.

[0056] In the present disclosure, 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 (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 a PUSCH transmission transmitted using one SRI / power control parameter set / beam / precoder.

[0058] Note that PUSCH repetition / PUSCH transmission for 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 for 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 also be referred to as STRP PUSCH repetition, PUSCH transmission using a single TRP, repeated PUSCH transmission for a single TRP, PUSCH across a single TRP, repeated PUSCH across a single TRP, single PUSCH transmission for a single TRP, simply single PUSCH transmission, PUSCH transmission in a single TRP, PUSCH transmission using a single SRI, etc.

[0062] Note that 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. However, 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. Furthermore, common or different embodiments may be applied to codebook-based PUSCH transmission and non-codebook-based PUSCH transmission. Furthermore, UL transmission is not limited to PUSCH, and each embodiment of the present disclosure can also be applied to PUCCH as appropriate (PUSCH may be read as PUCCH).

[0063] In addition, in each embodiment of the present disclosure, the case where the number of TRPs, 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 the present disclosure, "CORESET pool index is set to 0" may be read interchangeably 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 the present disclosure, "PHR" may be interchangeably read as "PH," "PH field," "PH value," etc.

[0067] Note that, although each of the embodiments described below is based on the premise that MTRP PUSCH repetition is enabled for the UE by a higher layer parameter, the present invention is not limited to this.

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

[0069] Furthermore, 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 certain serving cell. Hereinafter, in the present disclosure, this case is also referred to as "Case 1." Furthermore, the case where MTRP PUSCH repetition is specified by DCI for a certain serving cell is also referred to as "Case 2."

[0070] Note that the case where STRP PUSCH repetition is specified by DCI for a serving cell is also referred to as "Case 1a," and the case where single transmission is specified by DCI for a serving cell is also referred to as "Case 1b." Case 1 encompasses Cases 1a and 1b. "Case 1" in the present disclosure may be interchangeably read as "Case 1a / Case 1b."

[0071] In the first embodiment, "reporting one / two PHRs" may mean "reporting one / two PHRs for a serving cell for 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 to be 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 association with 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 to be reported, one PHR for TRP2 is to be reported, or two PHRs are to be 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 a 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] Furthermore, of the two reported PHRs, a Type 1 PHR for the other TRP is reported 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). 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 the present disclosure, the power control parameter is P CMAX,f,c The power control parameters may be at least one of 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], and Δ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 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 association with 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 illustrating an example of a single-entry PHR MAC CE in the first embodiment. Figures 3A, 3B, and 3C correspond to embodiment 1.1, embodiment 1.2.1, and embodiment 1.2.2, respectively. Differences from FIG. 1 are described below, and the same points are not 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 Figure 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, if X=1, the size of this MAC CE is 3 octets, and if X=0, it is 2 octets, 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] 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 represented 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 a 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 a 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] 4A-4C are diagrams illustrating 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 FIG. 2 are described, and the same descriptions are not 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 the PHR for TRP1 and the PHR for TRP2, respectively.

[0094] In Figure 4A, 'X i ' field corresponds to the field indicating that one or two PHRs are reported as described above, and C i 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] 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). The C0 field may be an R field. The same may be true for the subsequent 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] Figure 4B differs from Figure 2 in that an octet containing each PHR_j,2 is present. 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_j,1 and PHR_j,2 to 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 the V field corresponding to PHR_j,2, but since PHR_j,2 is the same as PHR_j,1 (in Case 1) or actually corresponds to a PHR (in Case 2), an R field would also work. 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 containing 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 the field indicating whether the PHR for a certain TRP described above is a virtual PHR, 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 properly generate / transmit a PHR report including the actual PHR.

[0101] <Second embodiment> The second embodiment relates to reporting of Type 1 PHR based on 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 both a virtual PHR and an actual PHR.

[0102] The second embodiment may be applied when at least one of case 1 and case 2 applies, or when 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 the serving cell that reports the virtual PHR." The reported one / two PHRs may be Type 1 PHs or other types of PHs.

[0104] The second embodiment is roughly 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 being reported (in other words, whether this PHR MAC CE actually includes a PHR). This field may be included for each serving cell, or may be included in association with a specific serving cell. For example, this field may be the V field of the PHR MAC CE specified 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 based on new default power control parameters.

[0110] In embodiment 2.2.2, for two reported virtual PHRs, 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 embodiments 2.1 and 2.2, this MAC CE may be used in both case 1 and case 2.

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

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

[0115] In embodiment 2.1, PHR_j,2 may actually represent the PHR. In embodiment 2.2.1, PHR_j,1 and PHR_j,2 are the same value, while 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 actual 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 on carrier f1 of serving cell 1 is the same as the SCS setting μ2 of the active UL BWP b2 on 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 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] Note that the Type 1 PHR of serving cell 2 is transmitted using a 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 that overlaps with the slot for reporting the PHR of serving cell 1 (hereinafter also referred to as a PHR reporting slot) is one of the MTRP PUSCH repetitions. Note that one unit of repetition may be referred to as a repetition opportunity, a PUSCH opportunity, etc. In the present disclosure, the first PUSCH may be referred to as a first PUSCH repetition, a first PUSCH opportunity, etc. Also, in the present disclosure, "first" may be read interchangeably with "initial."

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

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

[0125] Embodiment 3.1 is roughly divided into embodiment 3.1.1 in which the UE reports one PHR as the PHR of serving cell 2, and 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 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 of 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 reporting 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, embodiments 3.1.1-4, 3.1.1-5, 3.1.1-6 and 3.1.2-2 may be applied to the PHR of serving cell 1 (the serving cell that transmits the PHR) by replacing serving cell 2 with serving cell 1.

[0129] Note 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 the slot of serving cell 2 that overlaps with the 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 one PUSCH repeat is a repeat 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 repeats are all TRP1 repeats. Case B3: These two or more PUSCH repetitions are all repetitions for TRP2.

[0130] Of 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 serving cells 1 and 2 have the same SCS, the slot lengths of these cells are the same. In serving cell 2, MTRP PUSCH repeated transmission is performed so as to overlap with the PHR report slot of serving cell 1. The number of repetitions is 4, and four slots (PUSCH1-4) are shown repeated. 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 TRP1 and TRP2) are mapped for the first and second repetitions, and the same mapping is applied to the remaining repetitions. Note that, as the mapping pattern, sequential mapping, half-half mapping, etc. may also be applied.

[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, when embodiment 3.1.1-1 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. 7A, when 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.

[0135] In the example of Fig. 7B, when 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 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 embodiment 3.1.2-2 is followed, the UE reports two PHRs (PHR for PUSCH1 and PUSCH2) in the PHR reporting slot for serving cell 2.

[0136] 8A and 8B are diagrams illustrating an example of Case B of embodiment 3.1. Serving cells 1 and 2 have the same SCS, so the slot lengths of these cells are the same. Serving cell 2 performs MTRP PUSCH repetition transmission overlapping with the PHR report slot of serving cell 1. The number of repetitions is four, and four repetitions (PUSCH1-4) are shown. Note that cyclic mapping is applied to these MTRP repetitions. 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 embodiment 3.1.1-1 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. 8A, when embodiment 3.1.2-1 / 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.

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

[0140] [Embodiment 3.2] Embodiment 3.2 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 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, the UE provides Type 1 PHR for the first PUSCH in the 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 a PUSCH in the slot of serving cell 1. The Type 1 PHR of serving cell 2 is based on the 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] Figure 9 is a diagram showing an example of embodiment 3.2. The SCS of serving cell 1 is smaller than the SCS of serving cell 2, and in this example, the latter is twice the former (for example, the SCS of serving cell 1 = 15 kHz and the SCS of serving cell 2 = 30 kHz). Therefore, the actual time length of a slot of serving cell 1 is twice the actual time length of a slot of serving cell 2. The same applies to the drawings used to explain embodiment 3.2 unless otherwise specified.

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

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

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

[0146] Embodiments 3.2.1 and 3.2.2 may be embodiments obtained by reinterpreting the above-described embodiments 3.1.1 and 3.1.2 as follows: Embodiment 3.2.1a / 3.2.2a: "a slot of serving cell 2 that overlaps with a PHR reporting slot of serving cell 1" is read as "a first slot of serving cell 2 that completely overlaps with a 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 replaced with "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 "overlap." 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 multiple slots of serving cell 2."

[0148] Hereinafter, embodiments 3.2.1a / 3.2.2a will be collectively referred to as embodiment 3.2a. Also, embodiments 3.2.1b / 3.2.2b will be collectively referred to as embodiment 3.2b. 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 "a slot of serving cell 2 that overlaps with a 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 serving cell 2, MTRP PUSCH repeat transmission is performed overlapping with the PHR report slot of 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 reporting 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 reporting slot.

[0152] 10B corresponds to embodiment 3.2b, and "slots of serving cell 2 that completely overlap with the PHR reporting slot of serving cell 1" are hatched. These slots correspond to the slots of PUSCH1 and PUSCH2 that overlap with the PHR reporting 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 the embodiments 3.2a and 3.2b may be applied to one or more of the 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 reporting slot of 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 in the same manner) is followed, the UE reports one PHR (a 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 (no reinterpretation) is followed, the UE reports two PHRs (a PHR for PUSCH1 and a PHR for PUSCH2) for serving cell 2 in the PHR reporting slot.

[0156] In the example of FIG. 11B, when 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 embodiment 3.2.1-4a (without any rephrasing) 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 embodiment 3.2.2-2a (without any rephrasing) is followed, the UE reports two PHRs (PHR for PUSCH1 and 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 the SCS of serving cell 2, the slot length of serving cell 1 is twice the slot length of serving cell 2. In serving cell 2, MTRP PUSCH repeated transmission (four times) is performed, overlapping with the PHR reporting slot of serving cell 1. One repetition period corresponds to a half slot (or sub-slot, multiple symbols) of the slot of serving cell 2.

[0158] Furthermore, 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 at the same timing as the slot of PUSCH3).

[0159] In the example of Fig. 12A, when following 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, when following 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 embodiment 3.2.1-1a is followed, the UE reports one PHR (PHR for PUSCH3) for serving cell 2 in the PHR reporting slot. Furthermore, in the example of FIG. 12B , when embodiment 3.2.1-4a (without any rephrasing) is followed, the UE reports one PHR (PHR for PUSCH1) for serving cell 2 in the PHR reporting slot. Furthermore, in the example of FIG. 12B , when embodiment 3.2.2-1a is followed, the UE reports two PHRs (PHR for PUSCH3 and PHR for PUSCH4) for serving cell 2 in the PHR reporting slot. Furthermore, in the example of FIG. 12B , when embodiment 3.2.2-2a (without any rephrasing) is followed, the UE reports two PHRs (PHR for PUSCH1 and PUSCH2) for serving cell 2 in the PHR reporting 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 redundant description will not be repeated.

[0162] In the example of FIG. 13, when embodiment 3.2.1-1a is followed, the UE reports one PHR (PHR for PUSCH2) for serving cell 2 in the PHR reporting slot. Also, in the example of FIG. 13, when embodiment 3.2.1-4a (without any reinterpretation) is followed, the UE reports one PHR (PHR for PUSCH1) for serving cell 2 in the PHR reporting slot. Also, in the example of FIG. 13, when embodiment 3.2.2-1a is followed, the UE reports two PHRs (PHR for PUSCH2 and PHR for PUSCH3) for serving cell 2 in the PHR reporting slot. Also, in the example of FIG. 13, when embodiment 3.2.2-2a (without any reinterpretation) is followed, the UE reports two PHRs (PHR for PUSCH1 and PHR for PUSCH2) for serving cell 2 in the PHR reporting 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 across multiple slots in active UL BWP b1, which PUSCH transmission overlaps 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 a PUSCH in a slot of serving cell 1. The Type 1 PHR of serving cell 2 is also based on actual PUSCH transmission. Furthermore, the first PUSCH in the first slot that overlaps with the nominal repetition slots of serving cell 1 (the multiple slots may also be referred to as PHR reporting slots) is one of the MTRP PUSCH repetitions.

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

[0166] Embodiments 3.3.1 and 3.3.2 may be embodiments obtained by reinterpreting the above-described embodiments 3.1.1 and 3.1.2 as follows: Embodiments 3.3.1a / 3.3.2a: "a slot of serving cell 2 that overlaps with a PHR reporting slot of serving cell 1" is replaced with "a 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: "Slots of serving cell 2 that overlap with PHR reporting slots of serving cell 1" is replaced with "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 multiple slots of serving cell 2."

[0168] Note that embodiment 3.3.1a / 3.3.2a are collectively referred to as embodiment 3.3a. Also, embodiment 3.3.1b / 3.3.2b are 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 "a slot of serving cell 2 that overlaps with a PHR reporting slot of serving cell 1" does not appear.

[0169] [PHR MAC CE of the third embodiment] 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 association with 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. 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. This PHR MAC CE may have the configuration of, for example, FIG. 4A.

[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 that serving cell (this value may be calculated according to the "reported" actual PHR). This PHR MAC CE may have the configuration shown in Figure 4B, for example.

[0172] Also, in the third embodiment, the PHR MAC CE may always include two PHR fields for each serving cell. If it is determined that one actual PHR is "reported" for a serving cell based on the third embodiment, the PHR MAC CE may include two PHR fields for the serving cell. One of these PHR fields may indicate the 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 in embodiment 1.2.2 above, 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. Unless otherwise specified, the PHR MAC CE may follow embodiment 1.2.2. This PHR MAC CE may have the configuration shown in FIG. 4C, for example.

[0173] According to the third embodiment described above, the UE can appropriately generate / transmit a PHR report when PUSCH transmissions from multiple cells overlap.

[0174] According to the third embodiment described above, the UE can preferably trigger 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) for different TRPs is supported, and may be applied regardless of the support of separate power control.

[0176] In Rel.16 NR, one of the triggering events for PHR is a path loss variation-based event. 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 has varied 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," "last path loss," "path loss measured in 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 the 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 in 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 designated for the current transmission is calculated based on the actual transmission, while the current path loss for the TRP not designated 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. On the other hand, the final path loss for the TRP not designated for the final transmission may be calculated based on the reference PUSCH transmission (i.e., 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 final path loss is case x3), the final path loss for TRP1 / 2 may be calculated based on the reference PUSCH transmission. Note that for cases y7-y9 (i.e., the final path loss is case x3), the final 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 prior to the last transmission of the PHR based on the reference PUSCH. FIG. 14 illustrates an example of calculation of 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 at this MAC entity is depicted with a dashed line, and the final path loss for TRP1 / 2 may be calculated based on this reference PUSCH. On the other hand, the final path loss for TRP1 / 2 may be derived based on the actual PUSCH for TRP1 / 2 prior to this last transmission. In this case, the path loss variation for TRP1 / 2 (the difference between the last path loss and the current path loss) may be calculated 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 transmission for TRP1 / 2 when the PHR was last reported, or the actual PUSCH transmission 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] For the path loss calculated based on the reference PUSCH transmission, different default PL-RSs may be used for TRP1 and TRP2 (for example, a PL-RS corresponding to pusch-PathlossReferenceRS-Id = the first value and a PL-RS corresponding to pusch-PathlossReferenceRS-Id = the second value), or a common default PL-RS (for example, 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 PUSCH repetition to TRP1 or the path loss variation of PUSCH repetition to TRP2 is greater than a threshold. Condition z2: Both the path loss variation of PUSCH repetition to TRP1 and the path loss variation of PUSCH repetition to TRP2 are greater than their respective thresholds. Condition z3: The path loss variation of the PUSCH repetition to TRP1 is greater than the 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 may be given by, for example, an upper layer parameter phr-Tx-PowerFactorChange. Note that the threshold 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 apply to a serving cell, the UE may trigger PHR if at least one of the above conditions z1-z4 is satisfied. Note that in case y9, the UE may trigger PHR if a condition other than the above conditions z1-z4 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 reference PUSCH transmission to derive a path loss variation. If this path loss variation is greater than a threshold (e.g., phr-Tx-PowerFactorChange), PHR may be triggered.

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

[0192] If cases y4 and y6 apply to a serving cell, the UE may trigger PHR if at least one of the above conditions z1-z4 and z6 is satisfied. Note that in case y6, the UE may trigger 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 this path loss variation is greater than a threshold (e.g., phr-Tx-PowerFactorChange), PHR may be triggered.

[0193] If case y5 applies to a serving cell, the UE may trigger PHR if at least one of the above conditions z1-z6 is satisfied. Note that in case y5, the UE may also trigger PHR if a condition other than the above conditions z1-z6 is satisfied. For example, the UE may derive a path loss variation by comparing 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. If this path loss variation is greater than a threshold (e.g., phr-Tx-PowerFactorChange), PHR may be triggered.

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

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

[0196] In relation to the TRP, the inhibit 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 a PHR for any TRP will not be 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, a 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, thereby reducing the complexity of the UE.

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

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

[0200] In the case of embodiment 5.2, the UE may trigger PHR when at least one condition (trigger event) is met, for example, that the path loss variation exceeds a threshold, as shown in the fourth embodiment, and one or a combination of the following is met: The first prohibit timer or the second prohibit timer expires or has expired; Both the first prohibit timer and the second prohibit timer expire or have expired; The first prohibit timer expires or has expired, The second prohibit timer expires or has expired, The prohibit timer for the TRP specified for the current transmission expires or has expired, The prohibit 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 restart if any of the following is met: - PHR (PHR MAC CE) for any TRP is sent, - A PHR for the TRP is sent, The actual PHR for that 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 related to the prohibit timer of the fifth embodiment. Figures 15A and 15B illustrate cases in which the UE utilizes the prohibit 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, and no PHRs for any TRPs will be triggered / sent until this inhibit timer expires.

[0206] In Figure 15B, when a PHR for TRP1 is sent, the prohibition timer for TRP1 starts again. A PHR for TRP1 will not be triggered until this prohibition timer expires. On the other hand, a 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 for 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), indicated by physical layer signaling (e.g., DCI), determined based on a combination of these, or 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 may decide to report two PHRs if MTRP repetition is specified (case 2).

[0211] The 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 if a virtual PHR is reported, and decide to report two PHRs if 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 specific 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., 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.

[0214] This condition may be, for example, whether MTRP repetition, STRP repetition, or single transmission is specified. For example, when STRP repetition or single transmission is specified (Case 1), the UE may decide to report a real PHR for one TRP designated (or corresponding) for PUSCH transmission, and to report a virtual PHR for the other TRP. Also, the above 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 specific serving cell) may be determined by triggering the PHR based on a specific trigger event for path loss variation (embodiment 6.1).

[0218] In embodiment 6.1, for example, if a PHR is triggered because both the path loss variation of the PUSCH repetition to TRP1 and the path loss variation of the PUSCH repetition to TRP2 are 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 specific serving cell) may be determined by whether the PHR is triggered under a specific 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, if the reporting of two PHRs is determined by embodiment 6.1 and the reporting of one PHR is determined by embodiment 6.2, or if 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] Also, 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 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 per-TRP PHR triggering (e.g., based on path loss variation) · Whether to support per-TRP prohibit timer.

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

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

[0230] The above-described embodiment may be applied to a 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) The 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 thereof.

[0233] 16 is a diagram illustrating 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) or 5th generation mobile communication system New Radio (5G NR) specified by the Third Generation Partnership Project (3GPP).

[0234] The wireless communication system 1 may also support dual connectivity between multiple 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)), etc.

[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 within 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 located within the macrocell C1 and form small cells C2 that are smaller than the macrocell C1. A user terminal 20 may be located within at least one of the cells. The locations and numbers of the cells and user terminals 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 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 be a frequency band higher than FR2.

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

[0241] The multiple base stations 10 may be connected by wire (for example, optical fiber conforming to the Common Public Radio Interface (CPRI), an X2 interface, or the like) or wirelessly (for example, 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, for example, at least one of 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] An Orthogonal Frequency Division Multiplexing (OFDM)-based radio access scheme may be used in the radio communication system 1. For example, 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), or the like may be used in at least one of the downlink (DL) and uplink (UL).

[0245] The radio access scheme may also be called a waveform. Note that 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 the downlink channel.

[0247] Furthermore, 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, System Information Block (SIB), etc. The PUSCH may transmit user data, higher layer control information, etc. Furthermore, the PBCH may transmit 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 for at least one of the PDSCH and the PUSCH.

[0250] Note that the DCI for scheduling the PDSCH may be referred to as a DL assignment, a DL DCI, etc., and the DCI for scheduling the PUSCH may be referred to as an UL grant, a UL DCI, etc. Note that the PDSCH may be interpreted as DL data, and the PUSCH may be interpreted as 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 more 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," "CORESET setting," etc. in the present disclosure may be read interchangeably.

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

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

[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, 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 as DL-RS.

[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 DMRS for the PBCH) may be referred to as an SS / PBCH block, an SS Block (SSB), or the like. Note that the SS, SSB, and the like may also be referred to as reference signals.

[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 also 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 the base station may include one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140.

[0259] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. Some of the processing 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 from 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 transceiver unit 120, the transceiver antenna 130, and the transmission path interface 140, measurement, etc. The control unit 110 may generate data to be transmitted as signals, control information, sequences, etc., and transfer them to the transceiver unit 120. The control unit 110 may perform call processing (setting up, releasing, 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 composed of a transmitting unit and a receiving unit. The transmitting unit may be composed of a transmission processing unit 1211 and an RF unit 122. The receiving unit may be composed of a reception processing unit 1212, an RF unit 122, and a measurement unit 123.

[0264] The transmitting and receiving antenna 130 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure pertains, 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 (for example, precoding), analog beamforming (for example, 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 processor 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 transmitting / receiving unit 120 (RF unit 122) may perform modulation to a radio frequency band, filtering, amplification, etc. on the baseband signal, and transmit the radio frequency band signal via the transmitting / receiving antenna .

[0270] On the other hand, the transmitting / receiving unit 120 (RF unit 122) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transmitting / receiving 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), control plane data, etc. for the user terminal 20.

[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 that includes 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. This information may be at least one piece of information such as phr-ProhibitTimer, phr-PeriodicTimer, and phr-Tx-PowerFactorChange. This information may be included in the PHR configuration information.

[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] The transceiver 120 may also 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 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.

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

[0281] Note that this example mainly shows functional blocks of the characteristic parts of the present embodiment, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. Some of the processing 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 from 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 also control transmission and reception, measurement, etc. using the transceiver unit 220 and the transceiver antenna 230. The control unit 210 may generate data, control information, sequences, etc. to be transmitted as signals, and transfer them to the transceiver unit 220.

[0284] The transceiver 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 transceiver unit 220 may be configured from 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.

[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 configured as an antenna described based on common understanding in the technical field to which the present 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 (for example, precoding), analog beamforming (for example, phase rotation), or the like.

[0289] The transceiver 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 processor 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 string to be transmitted, and output a baseband signal.

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

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

[0293] On the other hand, the transmitting / receiving unit 220 (RF unit 222) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transmitting / receiving 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 to 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 measurement, CSI measurement, 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] The transmitting section and 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] Note that the transceiver 220 may perform Physical Uplink Shared Channel (PUSCH) transmission using one Sounding Reference Signal Resource Indicator (SRI) for a certain serving cell.

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

[0299] Furthermore, 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] Furthermore, 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 the 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. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining the single device or 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, election, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission may be called a transmitting unit, transmitter, etc. As mentioned above, the implementation method of each is not particularly limited.

[0305] For example, a base station, a user terminal, etc. according to 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 illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. The above-described 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, terms such as apparatus, circuit, device, section, unit, etc. may 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. Furthermore, processing may be performed by one processor, or processing may be performed by two or more processors simultaneously, serially, or in other ways. Furthermore, 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 predetermined software (programs) onto hardware such as a processor 1001 and a memory 1002, causing the processor 1001 to perform calculations, control communication via the communication device 1004, and control at least one of reading and writing data in the memory 1002 and the storage 1003.

[0309] The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as 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] The processor 1001 also reads 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 in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 110 (210) may be realized by a control program stored in the memory 1002 and running on 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 read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), or other suitable storage medium. The memory 1002 may also be referred to as a register, a cache, a main memory, or the like. The memory 1002 may store executable programs (program codes), software modules, and the like for implementing 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 disc (e.g., a Compact Disc ROM (CD-ROM)), a digital versatile disc, a Blu-ray disc), 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 a secondary storage device.

[0313] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. 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 (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, a light emitting diode (LED) lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

[0315] Furthermore, 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), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized using such hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0317] (Variation) Note that terms explained in the present disclosure and terms necessary for understanding the present 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 interchangeable. A signal may also be a message. A reference signal may be abbreviated as RS, and may also be called a pilot, pilot signal, etc. depending on the applicable standard. A component carrier (CC) may also be called a cell, frequency carrier, 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 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), the 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 in the time domain (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol), and may be a time unit based on numerology.

[0321] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist 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 all represent time units for transmitting signals. The radio frame, the subframe, the slot, the minislot, and the symbol may be referred to by other names corresponding to 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 interchangeable.

[0323] For example, one subframe may be referred to as a TTI, or multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. That is, at least one of a subframe and a TTI may be a subframe (1 ms) in 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 smallest 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. However, 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) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

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

[0327] A TTI having a time length of 1 ms may be called a regular TTI (TTI in 3GPP Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, 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 of more than 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 numerology, for example, 12. The number of subcarriers included in an RB may also be determined based on 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. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

[0331] Note that one or more RBs may also 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 given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.

[0334] The BWP may include an 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-described structures of radio frames, subframes, slots, minislots, symbols, etc. 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, etc. may be changed in various ways.

[0337] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed 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 intended to be limiting in any way. Furthermore, the mathematical expressions 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 intended to be 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, 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 multiple network nodes.

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

[0342] Notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, 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] Note that 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. Furthermore, the RRC signaling may be called an RRC message, such as an RRC connection setup message or an RRC connection reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, 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 by a value represented by one bit (0 or 1), by a Boolean value represented by true or false, or by a comparison of numerical values ​​(e.g., comparison 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] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if 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), 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 the present 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," etc. 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. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.

[0351] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication service within 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 mobile object, or the mobile object itself. The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (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 also include devices that do not necessarily move during communication operations. 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, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments 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 multiple 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, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0356] Similarly, the user terminal in the present disclosure may be read as a base station, in which 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 described as being performed by a base station may be performed by its upper node in some cases. It is apparent that in a network including one or more network nodes having a base station, various operations performed for communication with a terminal 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 depending on the implementation. Furthermore, the order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed 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 specific order presented.

[0359] Each aspect / embodiment described in the present disclosure may be related to 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 that use 802.20, Ultra-Wide Band (UWB), Bluetooth (registered trademark), or other appropriate wireless communication methods, or to next-generation systems that are based on and extend these systems. Furthermore, 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] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. 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 in some way precede the second element.

[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, etc.

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

[0364] Also, "decision" may be considered to be "deciding" resolving, selecting, choosing, establishing, comparing, etc. In other words, "decision" may be considered to be "deciding" on some action.

[0365] Furthermore, "judgment (decision)" may be interpreted as "assuming," "expecting," "considering," or the like.

[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 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, etc., as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range, light (both visible and invisible) range, etc., 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 used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, similar to the term "comprising." Furthermore, when used in this disclosure, the term "or" is not intended to be an exclusive or.

[0370] In this disclosure, where articles are 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 in modified and altered forms without departing from the spirit and scope of the invention as defined by the description of the claims. Therefore, the description of the present disclosure is intended to be illustrative and explanatory and does not impose any limiting meaning on the invention according to the present disclosure.

Claims

1. A receiver that receives higher layer parameters indicating the activation of a first Power Headroom Report (PHR) corresponding to a first transmission / reception point (TRP) and a second PHR corresponding to a second TRP, and downlink control information (DCI); A control unit that calculates the first PHR based on a first reference PUSCH transmission for the first TRP and the second TRP when the DCI does not indicate a Physical Uplink Shared Channel (PUSCH) transmission for the first TRP and the second TRP, and calculates the second PHR based on a second reference PUSCH transmission for the second TRP; A terminal comprising: a transmitter that transmits a Medium Access Control (MAC) control element including a field indicating the first PHR and a field indicating the second PHR.

2. The terminal of claim 1 , wherein a plurality of default power control parameters for calculating the first PHR and a plurality of default power control parameters for calculating the second PHR are different.

3. receiving a higher layer parameter indicating activation of a first Power Headroom Report (PHR) corresponding to a first Transmission / Reception Point (TRP) and a second PHR corresponding to a second TRP, and downlink control information (DCI); When the DCI does not indicate a Physical Uplink Shared Channel (PUSCH) transmission for the first TRP and the second TRP, calculating the first PHR based on a first reference PUSCH transmission for the first TRP and calculating the second PHR based on a second reference PUSCH transmission for the second TRP; and transmitting a Medium Access Control (MAC) control element including a field indicating the first PHR and a field indicating the second PHR.

4. a transmitter for transmitting higher layer parameters indicating the activation of a first Power Headroom Report (PHR) corresponding to a first transmission / reception point (TRP) and a second PHR corresponding to a second TRP, and downlink control information (DCI); A control unit that determines that, when the DCI does not instruct Physical Uplink Shared Channel (PUSCH) transmission for the first TRP and the second TRP, the terminal calculates the first PHR based on a first reference PUSCH transmission for the first TRP and calculates the second PHR based on a second reference PUSCH transmission for the second TRP; A base station comprising: a receiving unit that receives a Medium Access Control (MAC CE) including a field indicating the first PHR and a field indicating the second PHR.

5. A system having a terminal and a base station, The terminal A receiver that receives higher layer parameters indicating the activation of a first Power Headroom Report (PHR) corresponding to a first transmission / reception point (TRP) and a second PHR corresponding to a second TRP, and downlink control information (DCI); A control unit that calculates the first PHR based on a first reference PUSCH transmission for the first TRP and the second TRP when the DCI does not indicate a Physical Uplink Shared Channel (PUSCH) transmission for the first TRP and the second TRP, and calculates the second PHR based on a second reference PUSCH transmission for the second TRP; a transmitter configured to transmit a Medium Access Control (MAC) control element including a field indicating the first PHR and a field indicating the second PHR; The base station A system having a receiver for receiving said MAC control element.

Images