Terminal, wireless communication method, base station and system

Abstract

A terminal according to one embodiment of the present disclosure comprises: a receiving unit that receives information on a plurality of power control parameters corresponding to one code point in a sounding reference signal resource indicator (SRI) field; and a control unit that determines the transmission power for a physical uplink shared channel (PUSCH) using one of a plurality of power control parameters that are selected on the basis of the values in the SRI field of downlink control information (DCI) that schedules the PUSCH. According to one embodiment of the present disclosure, uplink transmissions can be appropriately controlled even when multiple TRPs are used.

Description

[Technical Field]

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

[0002] In 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 NR, communication using one or more transmission / reception points (TRP) (multi-TRP) is being considered.

[0006] However, if the existing Rel.15 / 16 specifications are used to transmit data for multiple TRPs, there will be limitations on performance, scheduling flexibility, etc. Therefore, if the existing Rel.15 / 16 specifications are used, UL transmission across M-TRPs will not be performed properly, which may result in a decrease in throughput or degradation of communication quality.

[0007] Therefore, the present disclosure provides a terminal and a wireless communication method that can appropriately control UL transmission even when multi-TRP is used. 、 base station and systems One of the aims is to provide [Means for solving the problem]

[0008] A terminal according to one embodiment of the present disclosure includes: a receiver that receives power control parameter configuration information, the power control parameter configuration information including a plurality of lists for setting a correspondence relationship between spatial relationship information and power control parameters; and Downlink Control Information (DCI) that schedules repeated transmission of a Physical Uplink Shared Channel (PUSCH) for a plurality of Transmission / Reception Points (TRPs); a controller that determines a plurality of pieces of spatial relationship information to be applied to the repeated transmission of the PUSCH based on values ​​of a plurality of Sounding Reference Signal Resource Indicator (SRI) fields included in the DCI, and determines a plurality of power control parameters to be applied to the repeated transmission of the PUSCH based on the plurality of lists associated with the plurality of TRPs and the determined plurality of pieces of spatial relationship information; and a transmitter that performs repeated transmission of the PUSCH using the plurality of power control parameters, respectively. The plurality of lists includes a first list corresponding to a first TRP among the plurality of TRPs and a second list corresponding to a second TRP among the plurality of TRPs, and the second list is a list for repeated transmission of the PUSCH for the plurality of TRPs. . [Effects of the Invention]

[0009] According to one aspect of the present disclosure, UL transmission can be appropriately controlled even when multi-TRP is used. [Brief explanation of the drawings]

[0010] [Figure 1] 1A and 1B are diagrams illustrating an example of repeated transmission of a PUSCH. [Figure 2] 2A and 2B are diagrams showing examples of invalid symbol patterns. [Figure 3] 3A and 3B are diagrams showing an example of nominal repetitions and actual repetitions. [Figure 4] FIG. 4 is a diagram illustrating an example of repeated transmission of PUSCH in multi-TRP. [Figure 5] 5A and 5B are diagrams showing an example of a problem that occurs when attempting to transmit to an M-TRP using the existing Rel. 15 / 16 specifications. [Figure 6] FIG. 6 is a diagram illustrating an example of SRI control of a PUSCH according to embodiment 1.1. [Figure 7] FIG. 7 is a diagram illustrating an example of SRI control of a PUSCH according to embodiment 1.2. [Figure 8] FIG. 8 is a diagram illustrating an example of SRI control of a PUSCH according to embodiment 1.3. [Figure 9] FIG. 9 is a diagram illustrating an example of power control parameter settings in the existing Rel. 15 / 16 NR. [Figure 10] 10A and 10B are diagrams illustrating an example of power control parameter settings according to the second embodiment. [Figure 11] FIG. 11 is a diagram illustrating another example of setting of power control parameters according to the second embodiment. [Figure 12] FIG. 12 is a diagram illustrating an example of specifying power control parameters of a PUSCH according to the second embodiment. [Figure 13] FIG. 13 is a diagram illustrating another example of designating power control parameters of a PUSCH according to the second embodiment. [Figure 14] FIG. 14 is a diagram illustrating yet another example of designating power control parameters of a PUSCH according to the second embodiment. [Figure 15] 15A to 15D are diagrams illustrating an example of a correspondence relationship between an SRS resource / SRS resource set and a power control parameter according to the third 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

[0011] (Repeated transmission) Rel. 15 supports repeated transmission in data transmission. For example, a base station (network (NW), gNB) repeats DL data (e.g., downlink shared channel (PDSCH)) transmission a predetermined number of times. Alternatively, a UE repeats UL data (e.g., uplink shared channel (PUSCH)) transmission a predetermined number of times.

[0012] 1A is a diagram illustrating an example of repeated transmission of a PUSCH. In FIG. 1A, an example is shown in which a predetermined number of repeated PUSCHs are scheduled by a single DCI. The number of repetitions is also called a repetition factor K or an aggregation factor K.

[0013] In FIG. 1A, the repetition factor K=4, but the value of K is not limited to this. Also, the nth repetition may be referred to as the nth transmission occasion, etc., and may be identified by a repetition index k (0≦k≦K−1). Also, while FIG. 1A shows repeated transmission of a PUSCH dynamically scheduled by DCI (e.g., a dynamic grant-based PUSCH), this may also be applied to repeated transmission of a configuration grant-based PUSCH.

[0014] For example, in Figure 1A, the UE semi-statically receives information indicating the repetition factor K (e.g., aggregationFactorUL or aggregationFactorDL) through higher layer signaling, where the higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, etc., or a combination thereof.

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

[0016] The UE controls reception processing (e.g., at least one of reception, demapping, demodulation, and decoding) of the PDSCH or transmission processing (e.g., at least one of transmission, mapping, modulation, and coding) of the PUSCH for K consecutive slots based on at least one of the following field values ​​(or information indicated by the field value) in the DCI: Allocation of time domain resources (e.g., starting symbol, number of symbols in each slot, etc.), Allocation of frequency domain resources (e.g., a predetermined number of resource blocks (RBs) and a predetermined number of resource block groups (RBGs)), Modulation and Coding Scheme (MCS) index, Configuration of the PUSCH demodulation reference signal (DMRS: Demodulation Reference Signal), PUSCH spatial relation info or Transmission Configuration Indication (TCI) state (TCI-state).

[0017] The same symbol allocation may be applied to K consecutive slots. Figure 1A shows a case where the PUSCH in each slot is allocated to a predetermined number of symbols from the beginning of the slot. The same symbol allocation between slots may be determined as described above in the time domain resource allocation.

[0018] For example, the UE may determine the symbol allocation in each slot based on the start symbol S and the number of symbols L (e.g., Start and Length Indicator (SLIV)) determined based on the value m of a predetermined field (e.g., the TDRA field) in the DCI. Note that the UE may determine the first slot based on K2 information determined based on the value m of a predetermined field (e.g., the TDRA field) in the DCI.

[0019] On the other hand, among the K consecutive slots, the redundancy versions (RVs) applied to TBs based on the same data may be the same or at least partially different. For example, the RV applied to the TB in the n-th slot (transmission opportunity, repetition) may be determined based on the value of a predetermined field (e.g., RV field) in the DCI.

[0020] If the communication direction of the resources allocated in K consecutive slots differs in at least one symbol from the UL, DL, or Flexible of each slot specified by at least one of the uplink / downlink communication direction indication information for TDD control (e.g., "TDD-UL-DL-ConfigCommon" or "TDD-UL-DL-ConfigDedicated" in the RRC IE) and the slot format indicator of the DCI (e.g., DCI format 2_0), the resources of the slot containing that symbol may not be transmitted (or received).

[0021] In Rel. 15, as shown in FIG. 1A, PUSCH is repeatedly transmitted across multiple slots (slot units), but in Rel. 16 and later, it is expected that PUSCH will be repeatedly transmitted in units shorter than slots (for example, subslot units, minislot units, or units of a predetermined number of symbols) (see FIG. 1B).

[0022] In FIG. 1B, the repetition factor K=4, but the value of K is not limited to this. Also, the nth repetition may be called the nth transmission occasion or the like, and may be identified by a repetition index k (0≦k≦K−1). Also, while FIG. 1B shows repeated transmission of a PUSCH dynamically scheduled by DCI (e.g., a dynamic grant-based PUSCH), this may also be applied to repeated transmission of a configuration grant-based PUSCH.

[0023] The UE may determine symbol allocation for PUSCH transmission (e.g., PUSCH with k=0) in a predetermined slot based on a start symbol S and the number of symbols L (e.g., StartSymbol and length) determined based on a value m of a predetermined field (e.g., a TDRA field) in DCI of the PUSCH. Note that the UE may determine the predetermined slot based on Ks information determined based on the value m of a predetermined field (e.g., a TDRA field) of DCI.

[0024] The UE may dynamically receive information indicating the repetition factor K (e.g., number of repetitions) via downlink control information. The repetition factor may be determined based on the value m of a predetermined field (e.g., the TDRA field) in the DCI. For example, a table may be supported that defines the correspondence between the bit value notified by the DCI, the repetition factor K, the start symbol S, and the number of symbols L.

[0025] The slot-based repetitive transmission shown in FIG. 1A may be referred to as repetitive transmission type A (e.g., PUSCH repetition Type A), and the subslot-based repetitive transmission shown in FIG. 1B may be referred to as repetitive transmission type B (e.g., PUSCH repetition Type B).

[0026] The UE may be configured to apply at least one of repetitive transmission type A and repetitive transmission type B. For example, the base station may notify the UE of the repetitive transmission type applied by the UE by higher layer signaling (e.g., PUSCHRepTypeIndicator).

[0027] Either repetitive transmission type A or repetitive transmission type B may be configured in the UE for each DCI format that schedules the PUSCH.

[0028] For example, for a first DCI format (e.g., DCI format 0_1), if higher layer signaling (e.g., PUSCHRepTypeIndicator-AorDCIFormat0_1) is set to repetitive transmission type B (e.g., PUSCH-RepTypeB), the UE applies repetitive transmission type B for PUSCH repetitive transmissions scheduled in the first DCI format. Otherwise (e.g., if PUSCH-RepTypeB is not set or if PUSCH-RepTypA is set), the UE applies repetitive transmission type A for PUSCH repetitive transmissions scheduled in the first DCI format.

[0029] (Invalid symbol pattern) When repetitive transmission type B is applied to PUSCH transmission, it is also considered to notify UE of information regarding symbols (or symbol patterns) that cannot be used for PUSCH transmission. A symbol pattern that cannot be used for PUSCH transmission may be called an invalid symbol pattern, an invalid symbol pattern, or the like.

[0030] It is being considered to notify the invalid symbol pattern using at least one of higher layer signaling and DCI, which may be in a predetermined DCI format (for example, at least one of DCI formats 0_1 and 0_2).

[0031] For example, information about an invalid symbol pattern that cannot be used for PUSCH transmission may be notified to the UE using a first higher layer parameter. Also, whether or not the information about the invalid symbol pattern is applied may be notified to the UE using DCI. In this case, a bit field (a field for notifying whether or not an invalid symbol pattern is applied) for indicating whether or not the information about the invalid symbol pattern is applied may be set in the DCI.

[0032] Furthermore, the second higher layer parameter may be used to notify the UE of whether the notification field (or additional bit) in the DCI is set. That is, when the UE is notified of information about an invalid symbol pattern by the first higher layer parameter, the UE may determine whether to apply the information about the invalid symbol pattern based on the second higher layer parameter and the DCI.

[0033] When the first upper layer parameter is not signaled or configured, the UE may control the transmission of the PUSCH without considering the invalid symbol pattern. When the first upper layer parameter is signaled or configured, the UE may determine whether to apply the invalid symbol pattern based on the second upper layer parameter and the DCI. For example, when the second upper layer parameter instructs the DCI to add an additional bit (or a predetermined field) indicating whether to apply the invalid symbol pattern, the UE may determine whether to apply the invalid symbol pattern based on the predetermined field.

[0034] The first higher layer parameter may be information indicating a symbol pattern that is disabled for PUSCH transmission, and may be in the form of a bitmap, for example (see FIG. 2A). FIG. 2A illustrates an example in which the disabled symbol pattern is defined by a bitmap (1-D bitmap) in the time domain. The UE may determine resources available for PUSCH transmission in one or more frequency bandwidths (e.g., Bandwidth Parts (BWPs)) based on the information regarding the disabled symbol pattern (see FIG. 2B).

[0035] Here, a case is shown in which one or a common invalid symbol pattern is applied to a plurality of BWPs, but a different invalid symbol pattern may be set or applied to each BWP.

[0036] (Nominal repetitions / Actual repetitions) When repeat transmission type B is applied and repeat transmission is performed in subslot units, there may be cases where a repeat transmission crosses a slot boundary depending on the repetition coefficient (K) and the data allocation unit.

[0037] 3A shows an example of applying repetition transmission type B when the repetition factor (K) is 4 and the PUSCH length (L) is 4. In FIG. 3A, a PUSCH with k=3 is arranged across a slot boundary. In this case, the PUSCH may be divided (or segmented) based on the slot boundary for transmission (see FIG. 3B).

[0038] Also, a case may be assumed in which a slot contains symbols that cannot be used for PUSCH transmission (for example, DL symbols or invalid symbols). FIG. 3A shows a case in which some symbols in which the PUSCH with k=1 is allocated contain symbols that cannot be used for the PUSCH transmission (here, DL symbols). In such a case, PUSCH transmission may be performed using symbols excluding the DL symbols (see FIG. 3B).

[0039] When DL symbols (or invalid symbols) are included in symbols other than both ends of a PUSCH's allocated symbols, PUSCH transmission may be performed using symbols other than the DL symbol portion. In this case, the PUSCH may be divided (or segmented).

[0040] Figure 3B shows a case where, in subslot-based repeated transmission, a PUSCH with k=1 (Rep#2) is divided into two by a DL symbol (Rep#2-1 and #2-2), and a PUSCH with k=3 (Rep#4) is divided into two by a slot boundary (Rep#4-1 and #4-2).

[0041] Note that repeated transmissions before considering DL symbols, invalid symbols, or slot boundaries (FIG. 3A) may be called nominal repetitions, and repeated transmissions after considering DL symbols, invalid symbols, or slot boundaries (FIG. 3B) may be called actual repetitions.

[0042] (Spatial relations for SRS, PUSCH) In Rel.15 NR, a UE may receive information (SRS configuration information, for example, parameters in the RRC control element "SRS-Config") used to transmit a measurement reference signal (e.g., a Sounding Reference Signal (SRS)).

[0043] Specifically, the UE may receive at least one of information about one or more SRS resource sets (SRS resource set information, e.g., the RRC control element "SRS-ResourceSet") and information about one or more SRS resources (SRS resource information, e.g., the RRC control element "SRS-Resource").

[0044] An SRS resource set may be associated with (or group together) a predetermined number of SRS resources, each of which may be identified by an SRS Resource Indicator (SRI) or SRS Resource Identifier (ID).

[0045] The SRS resource set information may include an SRS resource set ID (SRS-ResourceSetId), a list of SRS resource IDs (SRS-ResourceId) used in the resource set, an SRS resource type (e.g., periodic SRS, semi-persistent SRS, or aperiodic SRS), and information on SRS usage.

[0046] Here, the SRS resource type may indicate any one of periodic SRS (P-SRS), semi-persistent SRS (SP-SRS), and aperiodic SRS (A-SRS). Note that the UE may transmit P-SRS and SP-SRS periodically (or periodically after activation) and transmit A-SRS based on an SRS request in the DCI.

[0047] Furthermore, the use ("usage" of the RRC parameter, "SRS-SetUse" of the L1 (Layer-1) parameter) may be, for example, beam management, codebook (CB), non-codebook (NCB), antenna switching, etc. The SRS for codebook or non-codebook use may be used to determine a codebook-based or non-codebook-based precoder for PUSCH transmission based on the SRI.

[0048] For example, the UE may determine a precoder for PUSCH transmission based on the SRI, a Transmitted Rank Indicator (TRI), and a Transmitted Precoding Matrix Indicator (TPMI) in the case of codebook-based transmission. The UE may determine a precoder for PUSCH transmission based on the SRI in the case of non-codebook-based transmission.

[0049] The SRS resource information may include an SRS resource ID (SRS-ResourceId), an SRS port number, an SRS port number, a transmission comb, an SRS resource mapping (e.g., time and / or frequency resource position, resource offset, resource period, number of repetitions, number of SRS symbols, SRS bandwidth, etc.), hopping-related information, an SRS resource type, a sequence ID, spatial relationship information of the SRS, etc.

[0050] The spatial relationship information of the SRS (e.g., the RRC information element "spatialRelationInfo") may indicate spatial relationship information between a predetermined reference signal and the SRS. The predetermined reference signal may be at least one of a Synchronization Signal / Physical Broadcast Channel (SS / PBCH) block, a Channel State Information Reference Signal (CSI-RS), and an SRS (e.g., another SRS). The SS / PBCH block may be referred to as a Synchronization Signal Block (SSB).

[0051] The spatial relationship information of the SRS may include at least one of an SSB index, a CSI-RS resource ID, and an SRS resource ID as an index of the predetermined reference signal.

[0052] In the present disclosure, the SSB index, SSB resource ID, and SSB resource indicator (SSBRI) may be interchangeable. Also, the CSI-RS index, CSI-RS resource ID, and CSI-RS resource indicator (CRI) may be interchangeable. Also, the SRS index, SRS resource ID, and SRI may be interchangeable.

[0053] The spatial relationship information of the SRS may include a serving cell index, a BWP index (BWP ID), etc. corresponding to the predetermined reference signal.

[0054] When the UE is configured with spatial relationship information regarding the SSB or CSI-RS and the SRS for a certain SRS resource, the UE may transmit the SRS resource using the same spatial domain filter (spatial domain transmit filter) as the spatial domain filter for receiving the SSB or CSI-RS (spatial domain receive filter). In this case, the UE may assume that the UE receive beam for the SSB or CSI-RS and the UE transmit beam for the SRS are the same.

[0055] When spatial relationship information regarding a certain SRS (target SRS) resource is configured between another SRS (reference SRS) and the SRS (target SRS), the UE may transmit the target SRS resource using the same spatial domain filter (spatial domain transmit filter) as the spatial domain filter (spatial domain transmit filter) for transmitting the reference SRS. That is, in this case, the UE may assume that the UE transmit beam of the reference SRS and the UE transmit beam of the target SRS are the same.

[0056] The UE may determine the spatial relationship of the PUSCH scheduled by the DCI (e.g., DCI format 0_1) based on the value of a predetermined field (e.g., an SRS resource identifier (SRI) field). Specifically, the UE may use spatial relationship information of the SRS resource (e.g., the RRC information element "spatialRelationInfo") determined based on the value of the predetermined field (e.g., the SRI) for PUSCH transmission.

[0057] When codebook-based transmission is used for the PUSCH, the UE may be configured by RRC with two SRS resources per SRS resource set, and one of the two SRS resources may be indicated by DCI (a 1-bit SRI field).When non-codebook-based transmission is used for the PUSCH, the UE may be configured by RRC with four SRS resources per SRS resource set, and one of the four SRS resources may be indicated by DCI (a 2-bit SRI field).

[0058] (Multi-TRP) In NR, one or more Transmission / Reception Points (TRPs) (Multi-TRPs (M-TRPs)) will perform DL transmission to a UE using one or more panels (multi-panels), and a UE will perform UL transmission to one or more TRPs (see Figure 4).

[0059] However, if an attempt is made to transmit M-TRP using the existing Rel.15 / 16 specifications, there will be problems such as limitations on performance, scheduling flexibility, etc. Transmission for M-TRP corresponds to, for example, multiple PUSCH transmissions using different SRIs.

[0060] 5A and 5B are diagrams showing an example of a problem that occurs when attempting to transmit to an M-TRP using the existing Rel. 15 / 16 specifications. In this example, it is assumed that the value of the SRI field of the DCI = 0 corresponds to SRI #0, and the value of the SRI field = 0 corresponds to SRI #1.

[0061] 5A corresponds to a case where transmission for M-TRP is attempted using the existing specifications of Rel. 15. In this example, PUSCH #1 corresponding to SRI #0 is scheduled using one DCI (DCI1), and PUSCH #2 corresponding to SRI #1 is scheduled using another DCI (DCI2).

[0062] Here, DCI1 and DCI2 have the same HARQ process ID (or HARQ process number) and indicate the same value of the New Data Indicator (NDI) field. In other words, PUSCH #2 means a retransmission of the same data (transport block) as PUSCH #1. According to this example, PUSCHs of the same data can be transmitted (retransmitted, repeatedly transmitted) at short intervals using different beams (SRIs).

[0063] On the other hand, in Rel. 15, DCI2 for scheduling another PUSCH #2 cannot be issued (notified) until PUSCH #1 has been transmitted, which is not desirable when it is desired to transmit PUSCH #1 and #2 with a small time difference.

[0064] 5B corresponds to a case where transmission for M-TRP is attempted using the existing Rel. 16 specifications. In this example, PUSCH #1 corresponding to SRI #0 is scheduled using DCI (DCI1) detected in a CORESET with a control resource set (CONTROLLER REsource SET (CORESET)) pool index = 0, and PUSCH #2 corresponding to SRI #1 is scheduled using DCI (DCI2) detected in a CORESET with a CORESET pool index = 1.

[0065] In Rel. 16, when PUSCHs associated with different CORESET pool index values ​​are scheduled and a first PUSCH is scheduled by a CORESET (first PDCCH) with one CORESET pool index value, the UE may schedule a second PUSCH that starts before the end of the first PUSCH by a CORESET (second PDCCH) with the other CORESET pool index value that ends after the first PDCCH. Figure 5B shows this case.

[0066] In other words, in Rel.16, even before the transmission of PUSCH#1 scheduled by DCI#1 is completed, DCI#2 for scheduling another PUSCH#2 can be issued (notified) if the CORESET pool indices of these DCIs are different.

[0067] However, in the existing Rel.15 / 16 specifications, the correspondence between the SRI field and the SRI is set in common regardless of the CORESET pool index where the DCI is detected (corresponding to the SRI in the same SRS resource set), so flexible transmission for M-TRP cannot be realized. The same applies to the Transmit Power Control (TPC) related parameters corresponding to the SRI field.

[0068] Therefore, if the existing Rel. 15 / 16 specifications are followed, UL transmission across the M-TRP may not be performed properly, which may result in a decrease in throughput or degradation of communication quality.

[0069] Therefore, the present inventors have devised a method for controlling UL transmission across M-TRPs. According to one aspect of the present disclosure, for example, a UE can perform UL transmission for multiple TRPs using different beams.

[0070] 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.

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

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

[0073] 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.

[0074] 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.

[0075] Furthermore, the TCI status identifier (ID) and the TCI status may be interchangeable. The TCI status and the TCI may be interchangeable.

[0076] 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.

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

[0078] 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)).

[0079] 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).

[0080] In this disclosure, a single PDCCH may be assumed to be supported when multiple TRPs utilize an ideal backhaul, and multiple PDCCHs may be assumed to be supported when multiple TRPs utilize a non-ideal backhaul.

[0081] The ideal backhaul may be called DMRS port group type 1, reference signal associated group type 1, antenna port group type 1, CORESET pool type 1, etc. The non-ideal backhaul may be called DMRS port group type 2, reference signal associated group type 2, antenna port group type 2, CORESET pool type 2, etc. The names are not limited to these.

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

[0083] 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.

[0084] 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.

[0085] 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.

[0086] Note that, although the PUSCH in the following embodiments is assumed to be a repetitive PUSCH, it may not be a repetitive PUSCH (it may be a PUSCH that is transmitted once). Therefore, in the present disclosure, the repetitive PUSCH, the PUSCH repetition, and the PUSCH may be interchangeable. Note that in the repetitive PUSCH, the same codeword / transport block may be transmitted in each PUSCH (each repetition). The repetitive PUSCH may be interchangeable with multiple PUSCHs having the same content (for example, data / codeword / transport block).

[0087] Furthermore, the SRS resource set in the following embodiments may be interpreted as an SRS resource set used for a codebook or a non-codebook, or as an SRS resource set used for other purposes.

[0088] In the present disclosure, hereinafter, "the CORESET pool index is set to 0" may be read interchangeably as "the CORESET pool index is set to 0 or the CORESET pool index is not set."

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

[0090] (Wireless communication method) First Embodiment The first embodiment relates to repeated PUSCH transmission using one or more DCIs.

[0091] The first embodiment can be broadly divided into the following three types: Embodiment 1.1, suitable for mDCI-based MTRP, in which one SRI field per DCI is included; Embodiment 1.2, suitable for sDCI-based MTRP, includes multiple SRI fields per DCI; Embodiment 1.3, suitable for sDCI-based MTRP, includes one SRI field per DCI.

[0092] [Embodiment 1.1] In embodiment 1.1, the UE may determine the SRI to apply to the PUSCH based on at least one of the SRI field of the DCI that schedules the PUSCH and the CORESET pool index of the CORESET for the DCI (e.g., that detects the DCI).

[0093] In other words, the actual SRI specified by the value of the SRI field may be selected based on the CORESET pool index associated with the DCI.

[0094] 6 is a diagram illustrating an example of SRI control of a PUSCH according to embodiment 1.1. In this example, PUSCH #1 is scheduled using DCI (DCI1) detected in a CORESET with a CORESET pool index of 0, and PUSCH #2 is scheduled using DCI (DCI2) detected in a CORESET with a CORESET pool index of 1.

[0095] The correspondence between the value of the SRI field and the actual SRI differs for each CORESET pool index, as shown in the lower part of Fig. 6. In the present disclosure, SRI#i_j (where i and j are numbers) may mean the j-th SRI corresponding to the CORESET pool index = i, or may mean the j-th SRI in the i-th correspondence. SRI#i_j may be explicitly or implicitly associated with the CORESET pool index and set / activated by higher layer signaling, for example.

[0096] In this example, since the SRI field value of DCI1 is 0, the UE determines that the SRI applied to PUSCH#1 is SRI#0_0. Also, since the SRI field value of DCI2 is 0, the UE determines that the SRI applied to PUSCH#2 is SRI#1_0.

[0097] The SRI field size may be determined by the number of SRS resources included in one or more SRS resource sets for each associated CORESET pool index. For example, the SRI field size of DCI1 may be determined by the number of SRS resources included in one or more SRS resource sets associated with CORESET pool index=0.

[0098] Here, the correspondence between the SRS resource / SRS resource set and the associated CORESET pool index may be predetermined by a specification, may be notified to the UE by at least one of an RRC parameter, a MAC CE, and a DCI, or may be determined based on the UE capability. The correspondence may be set, for example, as shown in a third embodiment described later.

[0099] [Embodiment 1.2] In embodiment 1.2, the UE may determine the SRI to be applied to each PUSCH based on multiple SRI fields included in the DCI that schedules multiple PUSCHs.

[0100] For example, the SRI to be applied to the PUSCH may be determined based on the first SRI field (SRI field #1) if the scheduled PUSCH is the first transmission of the PUSCH repetition, or based on the second SRI field (SRI field #2) if not. More generally, when the PUSCH is in the ith repetition (i is an integer), the SRI to be applied to the PUSCH may be determined based on the {mod(i+1,N)+1}th SRI field (where mod(X,Y) is the remainder when X is divided by Y) (cyclic mapping), where N is the number of SRI fields. Alternatively, a sequential mapping may be used, where the first SRI field corresponds to the 1st to Nth repetitions, the second SRI field corresponds to the N+1st to 2Nth repetitions, and so on.

[0101] 7 is a diagram illustrating an example of SRI control of PUSCH according to embodiment 1.2. In this example, PUSCHs #1-#4 are scheduled using sDCI (DCI1). DCI1 has two SRI fields (SRI fields #1 and #2).

[0102] As shown in the lower part of FIG. 7, the correspondence between the value of the SRI field and the actual SRI differs for each PUSCH set (PUSCH#1 / #3 and PUSCH#2 / #4).

[0103] In this example, SRI field #1=0 may indicate that SRI #0_0 is applied to PUSCH #1 / #3, and SRI field #2=1 may indicate that SRI #1_1 is applied to PUSCH #2 / #4.

[0104] Here, the correspondence relationship between the SRS resource / SRS resource set and the i-th SRI (the set of SRI for the i-th PUSCH) may be determined in advance by a specification, may be notified to the UE by at least one of an RRC parameter, a MAC CE, and a DCI, or may be determined based on UE capabilities. The correspondence relationship may be set, for example, as shown in a third embodiment described later.

[0105] [Embodiment 1.3] In embodiment 1.3, the UE may determine the SRI to be applied to each PUSCH based on one SRI field included in the DCI that schedules multiple PUSCHs.

[0106] In embodiment 1.3, a UE may be configured with a predetermined number (e.g., M) of SRS resource lists associated with one SRS resource set through RRC signaling, where the predetermined number M may be, for example, 8, 64, or greater than 64. One or more SRS resource lists may be configured in an SRS resource set for a specific purpose (e.g., codebook or non-codebook).

[0107] When multiple SRS resource lists are configured in the UE, one or more SRS resource lists (subsets of the SRS resource lists) may be further activated using the MAC CE.

[0108] A maximum of R SRS resources may be associated with one SRS resource list, where R may correspond to the maximum number of TRPs for the PUSCH.

[0109] The SRI field of the DCI may be used to indicate to the UE one of the configured / activated SRS resource lists.

[0110] For example, the SRI to be applied to the PUSCH may be determined based on the first SRS resource in one indicated SRS resource list if the scheduled PUSCH is the first transmission of the PUSCH repetition, or may be determined based on the second SRS resource if not. More generally, when the PUSCH is the ith repetition (i is an integer), the SRI to be applied to the PUSCH may be determined based on the {mod(i+1,N)+1}th SRS resource (where mod(X,Y) is the remainder when X is divided by Y) (cyclic mapping), where N is the number of SRI fields. Alternatively, a sequential mapping may be used, where the first SRS resource corresponds to the 1st to Nth repetitions, the second SRS resource corresponds to the N+1st to 2Nth repetitions, and so on.

[0111] 8 is a diagram illustrating an example of SRI control of PUSCH according to embodiment 1.3. In this example, PUSCHs #1 to #4 are scheduled using sDCI (DCI1). DCI1 has one SRI field.

[0112] As shown at the bottom of FIG. 8, the value of the SRI field corresponds to an SRS resource list, which corresponds to one or more SRS resources.

[0113] In this example, an SRI field of 0 indicates that SRI based on SRS resource list #0 is applied to PUSCHs #1-#4. For PUSCHs #1 / #3, a first SRI based on the first SRS resource #0 in SRS resource list #0 may be applied. For PUSCHs #2 / #4, a second SRI based on the second SRS resource #1 in SRS resource list #0 may be applied.

[0114] According to the first embodiment described above, it is possible to appropriately determine the SRI to be applied to the PUSCH for the M-TRP.

[0115] <Second embodiment> In a second embodiment, the UE may determine the transmit power of the PUSCH based on the SRI field of the DCI that schedules the PUSCH. For example, the UE may determine transmit power control (TPC) related parameters of the PUSCH based on the SRI field of the DCI that schedules the PUSCH.

[0116] Here, the transmit power control (TPC) related parameters may be, for example, at least one of α, P0-PUSCH (also referred to as P0_PUSCH, P0, etc.), a closed-loop power control state, and a pathloss reference signal (PL-RS), or an index related to at least one of these. Hereinafter, the TPC related parameters are also referred to as power control parameters. It should be understood by those skilled in the art that the values ​​related to each parameter (α, P0-PUSCH, closed-loop power control state index, PL-RS index, etc.) are used in a formula for calculating the transmit power of the PUSCH.

[0117] Figure 9 is a diagram showing an example of power control parameter settings in the existing Rel.15 / 16 NR. This example is written using Abstract Syntax Notation One (ASN.1) notation (note that this is merely an example and may not be a complete description). The following drawings may also use ASN.1 notation.

[0118] In the present disclosure, a suffix indicating that the RRC information element, RRC parameter, etc. is introduced in a specific resource (e.g., "_r16", "_r17", "-r16", "-r17", etc.) may be added to the name of the RRC information element, RRC parameter, etc. The suffix may not be added, or a different word may be added.

[0119] In the existing Rel.15 / 16 NR, the configuration of PUSCH power control parameters (RRC information element "PUSCH-PowerControl") may include a list (sri-PUSCH-MappingToAddModList) for configuring the correspondence between the SRI and the power control parameters (SRI-PUSCH-PowerControl). The sri-PUSCH-MappingToAddModList associates the SRI field with the ID of the power control parameter (SRI-PUSCH-PowerControlId).

[0120] SRI-PUSCH-PowerControl may include an ID of a power control parameter, a parameter indicating the ID of the PL-RS (sri-PUSCH-PathlossReferenceRS-Id), a parameter indicating the ID of the set of P0-PUSCH and α (sri-P0-PUSCH-AlphaSetId), and a parameter indicating an index of the closed-loop power control state (sri-PUSCH-ClosedLoopIndex).

[0121] In the second embodiment, a different power control parameter is set for each SRI field or for each correspondence between the i-th PUSCH and the SRI as shown in the first embodiment. That is, in the second embodiment, a plurality of power control parameters corresponding to one code point (value) of the SRI field of the DCI may be set.

[0122] 10A and 10B are diagrams illustrating an example of power control parameter settings according to the second embodiment. In FIG. 10A, a plurality of sri-PUSCH-PathlossReferenceRS-Id, sri-P0-PUSCH-AlphaSetId, and sri-PUSCH-ClosedLoopIndex (for example, maxNrofTRP indicating the maximum number of TRPs) can be set for each of the sri-PUSCH-PathlossReferenceRS-Id, sri-P0-PUSCH-AlphaSetId, and sri-PUSCH-ClosedLoopIndex, which are each set to one for the SRI-PUSCH-PowerControl in FIG. 9. Note that maxNrofTRP may be, for example, 2. When the settings in FIG. 10A are adopted, no changes need to be made to the PUSCH-PowerControl from Rel. 15.

[0123] For multiple configured sri-PUSCH-PathlossReferenceRS-Id, sri-P0-PUSCH-AlphaSetId, and sri-PUSCH-ClosedLoopIndex, the i-th entry may correspond to the power control parameters for the i-th TRP.

[0124] Fig. 10B is a diagram showing an example of a correspondence relationship between the TRP, the SRI field, and the P0-PUSCH corresponding to the configuration of Fig. 10A. The ID, α, closed-loop power control state index, etc. of the PL-RS may have a similar relationship.

[0125] 10B indicates that P0-PUSCH#0-0 is obtained by the ID of the first entry of sri-P0-PUSCH-AlphaSetId that is set when SRI-PUSCH-PowerControlId=0, and P0-PUSCH#1-0 is obtained by the ID of the second entry. Also, indicates that P0-PUSCH#0-1 is obtained by the ID of the first entry of sri-P0-PUSCH-AlphaSetId that is set when SRI-PUSCH-PowerControlId=1, and P0-PUSCH#1-1 is obtained by the ID of the second entry.

[0126] Fig. 11 is a diagram showing another example of the setting of power control parameters according to the second embodiment. In this example, it is possible to set multiple sri-PUSCH-MappingToAddModLists (for example, maxNrofTRPs indicating the maximum number of TRPs; in this example, two) instead of the single sri-PUSCH-MappingToAddModList set in PUSCH-PowerControl in Fig. 9. When the setting in Fig. 10A is adopted, no changes need to be made to SRI-PUSCH-PowerControl from Rel. 15.

[0127] The existing sri-PUSCH-MappingToAddModList may be a list for setting a correspondence relationship between SRI and power control parameters for a first TRP (e.g., TRP#0). The new sri-PUSCH-MappingToAddModList-r17 may be a list for setting a correspondence relationship between SRI and power control parameters for a second TRP (e.g., TRP#1). In other words, the i-th sri-PUSCH-MappingToAddModList(-r17) included in PUSCH-PowerControl may correspond to the power control parameters for the i-th TRP.

[0128] When the configuration of FIG. 10B is realized using the configuration of FIG. 11, for example, P0-PUSCH#0-0 is obtained by the ID of sri-P0-PUSCH-AlphaSetId that is set for SRI-PUSCH-PowerControl with SRI-PUSCH-PowerControlId=0 included in sri-PUSCH-MappingToAddModList, and P0-PUSCH#1-0 is obtained by the ID of sri-P0-PUSCH-AlphaSetId that is set for SRI-PUSCH-PowerControl with SRI-PUSCH-PowerControlId=0 included in sri-PUSCH-MappingToAddModList-r17.

[0129] Fig. 12 is a diagram illustrating an example of designation of power control parameters of a PUSCH according to the second embodiment. This example is similar to the example in Fig. 6. In this example, it is assumed that the correspondence relationship in Fig. 10B is set (the same applies to Figs. 13 and 14 described later).

[0130] The UE derives the transmission power of PUSCH #1 corresponding to TRP #0 (CORESET pool index = 0) based on a first power control parameter associated with CORESET pool index = 0. The UE also derives the transmission power of PUSCH #2 corresponding to TRP #1 (CORESET pool index = 1) based on a second power control parameter associated with CORESET pool index = 1.

[0131] In this example, since the SRI field value of DCI1 is 0, the UE determines to use P0-PUSCH#0-0 to determine the transmit power of PUSCH#1. Also, since the SRI field value of DCI2 is 0, the UE determines to use P0-PUSCH#1-0 to determine the transmit power of PUSCH#1.

[0132] In addition, when the number of configured CORESET pool indices (or TRPs) is greater than two, the UE may derive the transmission power of the PUSCH whose SRI corresponds to CORESET pool index=i based on the power control parameters associated with CORESET pool index=i.

[0133] 13 is a diagram illustrating another example of designation of power control parameters of a PUSCH according to the second embodiment. This example is similar to the example in FIG.

[0134] The UE derives the transmit power of PUSCH #1 / #3 corresponding to TRP #0 (SRI field #1) based on the first power control parameter associated with TRP #0, and derives the transmit power of PUSCH #2 / #4 corresponding to TRP #1 (SRI field #2) based on the second power control parameter associated with TRP #1.

[0135] In this example, since the value of the SRI field #1 of DCI1 is 0, the UE determines to use P0-PUSCH #0-0 to determine the transmit power of PUSCH #1 / #3. Also, since the value of the SRI field #2 of DCI1 is 1, the UE determines to use P0-PUSCH #1-1 to determine the transmit power of PUSCH #2 / #4.

[0136] 14 is a diagram illustrating yet another example of designating power control parameters for a PUSCH according to the second embodiment. This example is similar to the example in FIG.

[0137] The UE derives the transmit power of PUSCH #1 / #3 corresponding to TRP #0 (first SRI) based on the first power control parameter associated with TRP #0, and derives the transmit power of PUSCH #2 / #4 corresponding to TRP #1 (second SRI) based on the second power control parameter associated with TRP #1.

[0138] In this example, since the SRI field of DCI1 is 0, the UE determines to use P0-PUSCH#0-0 to determine the transmit power of PUSCH#1 / #3, and determines to use P0-PUSCH#1-0 to determine the transmit power of PUSCH#2 / #4.

[0139] According to the second embodiment described above, the transmission power for the M-TRP can be appropriately determined.

[0140] <Third embodiment> In the third embodiment, the power control parameters as described above are associated with an SRS resource (in the case of codebook-based transmission) or a set of SRS resources (in the case of non-codebook-based transmission). Note that the set of SRS resources may be interpreted as one or more SRS resources.

[0141] That is, in the third embodiment, the correspondence between an SRS resource or a set of SRS resources and a power control parameter is configured / activated / notified using higher layer signaling, etc. The third embodiment may be used, for example, to configure the correspondence between an SRS resource or a set of SRS resources corresponding to an SRI and a power control parameter in the second embodiment.

[0142] In the third embodiment, the UE determines an SRS resource or a set of SRS resources from the SRI field of the DCI, and determines a power control parameter to be used for determining the transmission power of the PUSCH based on the determined SRS resource or set of SRS resources and the above-mentioned correspondence relationship.

[0143] 15A to 15D are diagrams illustrating an example of the correspondence relationship between SRS resources / SRS resource sets and power control parameters according to the third embodiment. In this example, P0_PUSCH is used as an example of the power control parameter, but other power control parameters may be used instead. Furthermore, the SRS resource set IDs and SRS resource IDs illustrated in the drawings are merely examples and are not limited to these values.

[0144] 15A shows an example of the correspondence relationship when one SRS resource set with usage=CB is configured for a CB-based PUSCH. In this example, SRS resource #i (i is an integer) is associated with P0_PUSCH #i.

[0145] 15B shows an example of a correspondence relationship when multiple SRS resource sets with usage=CB are configured for a CB-based PUSCH. In this example, SRS resource #i (i is an integer) is associated with P0_PUSCH #i. Note that one SRS resource set may or may not correspond to one TRP (CORESET pool index).

[0146] The correspondence relationship between P0_PUSCH and SRS resource sets (IDs) and SRS resources (IDs) may be explicitly set by higher layer signaling, or P0_PUSCH #0, #1, ... may be associated in ascending order of SRS resource set IDs (or SRS resource IDs). For example, the correspondence relationship may be such that P0_PUSCH #0, #1, ... are associated in ascending order of SRS resource set IDs, and further in ascending order of W SRS resource IDs. Note that "from smallest" in the present disclosure may be interchangeably read as "from largest".

[0147] The value of W may be the number of SRS resources that determines the SRI field size of the DCI, for example, W=2, 4, etc.

[0148] 15B, two SRS resources (SRS resources #0 and #1) of SRS resource set ID=0 (set #0) may be associated with P0_PUSCH #0 and #1, respectively. Also, two SRS resources (SRS resources #0 and #1) of SRS resource set ID=1 (set #1) may be associated with P0_PUSCH #2 and #3, respectively.

[0149] 15C shows an example of the correspondence relationship when one SRS resource set with usage=NCB is configured for the NCB-based PUSCH. In this example, the i-th SRS resource set (i is an integer) specified by the SRI field is associated with P0_PUSCH#i. In this example, the 0-th SRS resource set corresponds to SRS resource #0, the 1st SRS resource set corresponds to SRS resource #1, and the 2nd SRS resource set corresponds to {SRS resources #0, #1}.

[0150] For the NCB-based PUSCH, the beam and the number of PUSCH ports are selected simultaneously by the SRI field, so a set such as {SRS resource #0, #1} can be specified. A set such as {SRS resource #0, #1} may mean multiple SRS resources with different numbers of ports. According to this example, the power control parameters used for these multiple SRS resources can be associated with one common power control parameter.

[0151] 15D shows an example of a correspondence relationship when multiple SRS resource sets with NCB usage are configured for the NCB-based PUSCH. Note that one SRS resource set may or may not correspond to one TRP (CORESET pool index).

[0152] The correspondence relationship between P0_PUSCH and SRS resource sets (IDs) and SRS resources (IDs) may be explicitly set by higher layer signaling, or P0_PUSCH #0, #1, ... may be associated in ascending order of SRS resource set IDs (or SRS resource IDs). For example, the correspondence relationship may be P0_PUSCH #0, #1, ... in ascending order of SRS resource set IDs, and further in ascending order of W SRS resource sets having the smallest corresponding SRI field values.

[0153] The value of W may be the number of SRS resources that determines the SRI field size of the DCI, for example, W=2, 4, etc.

[0154] 15D, a set of SRS resources (SRS resource #0, SRS resource #1, {SRS resource #0, #1}) of SRS resource set ID=0 (set #0) may be associated with P0_PUSCH #0, #1, and #2, respectively. Also, for example, SRS resource #0 of the set of SRS resources of SRS resource set ID=1 (set #1) may be associated with P0_PUSCH #i.

[0155] According to the third embodiment described above, the UE can appropriately determine the power control parameters for the M-TRP.

[0156] <Other> At least one of the above embodiments may be applied only to UEs that support or have reported a particular UE capability.

[0157] The specific UE capabilities may indicate at least one of the following: Whether to support PUSCH repetitions with different spatial relationships (or SRIs), Whether to support sDCI-based PUSCH repetition with different spatial relationships (or SRIs), Whether to support mDCI-based PUSCH repetition for different CORESET pool indices; Maximum number of iterations / SRIs supported. - Maximum number of supported SRS resource sets / SRS resources.

[0158] 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 behavior of Rel. 15 / 16 applies). For example, the specific information may be information indicating that different spatial relationships for PUSCH repetitions are enabled, any RRC parameters for a specific release (e.g., Rel. 17), etc.

[0159] Note that each of the above-described embodiments may be applied when (the operation of) multi-TRP or multi-panel is set in the UE, or may be applied when not.

[0160] Note that the CORESET pool index in each embodiment of the present disclosure may be replaced with a TCI state ID or a CORESET ID.

[0161] (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.

[0162] 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).

[0163] 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.

[0164] 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.

[0165] 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))).

[0166] 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.

[0167] 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).

[0168] 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.

[0169] 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.

[0170] 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.

[0171] 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.

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

[0173] 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 the uplink (UL).

[0174] 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.

[0175] 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.

[0176] 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.

[0177] 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).

[0178] 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.

[0179] 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.

[0180] 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.

[0181] 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.

[0182] 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.

[0183] 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.

[0184] 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.

[0185] 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.

[0186] 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).

[0187] (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.

[0188] 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.

[0189] 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.

[0190] 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.

[0191] 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.

[0192] 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.

[0193] 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.

[0194] 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.

[0195] 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.

[0196] 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.

[0197] 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.

[0198] 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 .

[0199] 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 .

[0200] 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.

[0201] 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.

[0202] 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.

[0203] 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.

[0204] The transceiver 120 may transmit, to the user terminal 20, information on multiple power control parameters corresponding to one code point in a Sounding Reference Signal Resource Indicator (SRI) field. The information on the multiple power control parameters may be information on one or more SRS resource sets for a certain cell. The information on the multiple power control parameters may be multiple sri-PUSCH-MappingToAddModLists, multiple sri-PUSCH-PathlossReferenceRS-Ids, multiple sri-P0-PUSCH-AlphaSetIds, or multiple sri-PUSCH-ClosedLoopIndexes.

[0205] The transceiver 120 may receive a Physical Uplink Shared Channel (PUSCH) transmitted using a transmission power determined using one of the plurality of power control parameters selected by the user terminal 20 based on a value of the SRI field of Downlink Control Information (DCI) that schedules the PUSCH.

[0206] (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.

[0207] 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.

[0208] 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.

[0209] 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.

[0210] 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.

[0211] 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.

[0212] 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.

[0213] 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.

[0214] 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.

[0215] 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.

[0216] 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.

[0217] 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.

[0218] 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.

[0219] 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.

[0220] 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.

[0221] 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.

[0222] 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.

[0223] Note that the transceiver 220 may receive information on a plurality of power control parameters corresponding to one code point in a Sounding Reference Signal Resource Indicator (SRI) field.

[0224] The information on the plurality of power control parameters may be information on one or more SRS resource sets for a cell, or may be a plurality of sri-PUSCH-MappingToAddModLists, a plurality of sri-PUSCH-PathlossReferenceRS-Ids, a plurality of sri-P0-PUSCH-AlphaSetIds, or a plurality of sri-PUSCH-ClosedLoopIndexes.

[0225] The control unit 210 may determine the transmit power for the Physical Uplink Shared Channel (PUSCH) using one of the plurality of power control parameters selected based on the value of the SRI field of Downlink Control Information (DCI) that schedules the PUSCH.

[0226] The control unit 210 may determine the transmission power for the PUSCH using one of the plurality of power control parameters selected based on a CORESET pool index corresponding to the control resource set (COntrol REsource SET (CORESET)) in which the DCI is detected and the value of the SRI field.

[0227] When the DCI schedules a first PUSCH and a second PUSCH, the control unit 210 may determine the transmission power for the first PUSCH using one of the plurality of power control parameters selected based on the value of a first SRI field of the DCI, and may determine the transmission power for the second PUSCH using another of the plurality of power control parameters selected based on the value of a second SRI field of the DCI.

[0228] When the DCI schedules a first PUSCH (or a first SRI) and a second PUSCH (or a second SRI), the control unit 210 may determine the transmission power for the first PUSCH (or a first SRI) using one of the plurality of power control parameters selected based on the value of the SRI field, and may determine the transmission power for the second PUSCH (or a second SRI) using another of the plurality of power control parameters selected based on the same value of the SRI field.

[0229] (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.

[0230] 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.

[0231] 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.

[0232] 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.

[0233] 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.

[0234] 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.

[0235] 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.

[0236] 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.

[0237] 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.

[0238] 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.

[0239] 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.

[0240] 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).

[0241] 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.

[0242] 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.

[0243] (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.

[0244] 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.

[0245] 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.

[0246] 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.

[0247] 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.

[0248] 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.

[0249] 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.

[0250] 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.

[0251] 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.

[0252] 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.

[0253] 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.

[0254] 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.

[0255] 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.

[0256] 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.

[0257] 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.

[0258] 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.

[0259] 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.

[0260] 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.

[0261] 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."

[0262] 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.

[0263] 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.

[0264] 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.

[0265] 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.

[0266] 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.

[0267] 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.

[0268] 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.

[0269] 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).

[0270] 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).

[0271] 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).

[0272] 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.

[0273] 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.

[0274] 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).

[0275] 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.

[0276] 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.

[0277] 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.

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

[0279] 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.

[0280] 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.

[0281] 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.

[0282] 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.

[0283] 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.

[0284] 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.

[0285] 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).

[0286] 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."

[0287] 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.

[0288] 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.

[0289] 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.

[0290] 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.

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

[0292] 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."

[0293] 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.

[0294] 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."

[0295] 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.

[0296] 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.

[0297] 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 power control parameter setting information including a plurality of lists for setting a correspondence relationship between spatial relationship information and power control parameters, and Downlink Control Information (DCI) that schedules repeated transmission of a Physical Uplink Shared Channel (PUSCH) to a plurality of Transmission / Reception Points (TRPs); A control unit that determines a plurality of spatial relationship information to be applied to the repeated transmission of the PUSCH based on values ​​of a plurality of Sounding Reference Signal Resource Indicator (SRI) fields included in the DCI, and determines a plurality of power control parameters to be applied to the repeated transmission of the PUSCH based on the plurality of lists related to the plurality of TRPs and the determined plurality of spatial relationship information; A transmission unit that repeatedly transmits the PUSCH by using each of the plurality of power control parameters, The plurality of lists includes a first list corresponding to a first TRP among the plurality of TRPs, and a second list corresponding to a second TRP among the plurality of TRPs; A terminal, wherein the second list is a list for repeated transmission of the PUSH for the multiple TRPs.

2. The terminal according to claim 1, wherein the plurality of power control parameters include a parameter indicating an ID of a pathloss reference signal (PL-RS), a parameter indicating an ID of a set of P0-PUSCH and α, and a parameter indicating an index of a closed-loop power control state.

3. receiving power control parameter setting information including a plurality of lists for setting a correspondence relationship between spatial relationship information and power control parameters, and Downlink Control Information (DCI) for scheduling repeated transmission of a Physical Uplink Shared Channel (PUSCH) for a plurality of Transmission / Reception Points (TRPs); determining a plurality of spatial relationship information to be applied to the repeated transmission of the PUSCH based on values ​​of a plurality of Sounding Reference Signal Resource Indicator (SRI) fields included in the DCI, and determining a plurality of power control parameters to be applied to the repeated transmission of the PUSCH based on the plurality of lists associated with the plurality of TRPs and the determined plurality of spatial relationship information; Repeatedly transmitting the PUSCH using each of the plurality of power control parameters; The plurality of lists includes a first list corresponding to a first TRP among the plurality of TRPs, and a second list corresponding to a second TRP among the plurality of TRPs; A wireless communication method for a terminal, wherein the second list is a list for repeated transmission of the PUSH for the multiple TRPs.

4. A transmitter that transmits, to a terminal, power control parameter setting information including a plurality of lists for setting a correspondence relationship between spatial relationship information and power control parameters, and Downlink Control Information (DCI) that schedules repeated transmission of a Physical Uplink Shared Channel (PUSCH) for a plurality of Transmission / Reception Points (TRPs); A receiver that receives the repeated transmission of the PUSCH, each of which is transmitted using a plurality of power control parameters determined by the terminal based on the plurality of lists associated with the plurality of TRPs, and a plurality of spatial relationship information to be applied to the repeated transmission of the PUSCH determined by the terminal based on values ​​of a plurality of Sounding Reference Signal Resource Indicator (SRI) fields included in the DCI, The plurality of lists includes a first list corresponding to a first TRP among the plurality of TRPs, and a second list corresponding to a second TRP among the plurality of TRPs; A base station, wherein the second list is a list for repeated transmission of the PUSH for the multiple TRPs.

5. A system having a terminal and a base station, The terminal includes a receiving unit that receives power control parameter setting information including a plurality of lists for setting a correspondence relationship between spatial relationship information and power control parameters, and Downlink Control Information (DCI) that schedules repeated transmission of a Physical Uplink Shared Channel (PUSCH) for a plurality of Transmission / Reception Points (TRPs); A control unit that determines a plurality of spatial relationship information to be applied to the repeated transmission of the PUSCH based on values ​​of a plurality of Sounding Reference Signal Resource Indicator (SRI) fields included in the DCI, and determines a plurality of power control parameters to be applied to the repeated transmission of the PUSCH based on the plurality of lists related to the plurality of TRPs and the determined plurality of spatial relationship information; A transmission unit that repeatedly transmits the PUSCH by using each of the plurality of power control parameters, The base station includes a transmission unit that transmits the configuration information and the DCI to the terminal; A receiving unit that receives the repeated transmission of the PUSCH, The plurality of lists includes a first list corresponding to a first TRP among the plurality of TRPs, and a second list corresponding to a second TRP among the plurality of TRPs; A system in which the second list is a list for repeated transmission of the PUSH for the multiple TRPs.

Images