Terminal, wireless communication method and base station

Abstract

A terminal involved in one embodiment of the present disclosure includes: a receiving unit that receives information related to the correspondence between the value of the Sounding Reference Signal (SRS) resource indicator (SRS Resource Indicator (SRI)) field of the detected downlink control information (Downlink Control Information (DCI)) and the spatial relationship information for each control resource set (COntrol REsource SET (CORESET)) pool index; and a control unit that, in determining the spatial relationship information for the uplink shared channel (Physical Uplink Shared Channel (PUSCH)) of the DCI detected in the CORESET corresponding to a certain CORESET pool index, refers to the correspondence for the CORESET pool index to determine the spatial relationship information for the PUSCH. According to one embodiment of the present disclosure, UL transmission can be properly controlled even when multiple TRPs are used.

Description

Technical Field

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

[0002] In the Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) is standardized for the purpose of further high-speed data rate, low latency, etc. (Non-Patent Document 1). In addition, LTE-Advanced (3GPP Rel. 10-14) is standardized for the purpose of further increasing the capacity and sophistication of LTE (Release (Rel.) 8, 9) (Third Generation Partnership Project) (3GPP).

[0003] Successor systems of LTE (also known as, for example, 5th generation mobile communication system (5G), 5G+(plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel.15 and later, etc.) are also being studied.

[0004] Prior art literature

[0005] Non-patent literature

[0006] 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

[0007] Problems to be solved by the invention

[0008] In 3GPP Rel.15, repeated transmission is supported for UL data channels (e.g., uplink shared channels (Physical Uplink Shared Channel (PUSCH))). The UE controls so that the PUSCH is transmitted across multiple time slots (e.g., K consecutive time slots) based on the repetition factor K set by the network (e.g., base station). That is, in the case of repeated transmission, each PUSCH is transmitted through a different time slot (e.g., time slot unit).

[0009] On the other hand, in Rel. 16 and later, when repeatedly transmitting PUSCH, multiple PUSCH transmissions are being studied in one slot. That is, each PUSCH is transmitted in a unit shorter than a slot (for example, a subslot unit or a minislot unit).

[0010] In addition, in NR, communication using one or more transmission / reception points (Transmission / Reception Point (TRP)) (multi-TRP) is being studied.

[0011] However, in the NR specifications to date, how to control the repeated transmission of PUSCH in multiple TRPs has not been fully studied. In addition, not only limited to repeated transmission, research on methods for properly performing UL transmission for multiple TRPs has not made any progress. If UL transmission across multiple TRPs cannot be properly performed, a decrease in throughput or degradation in communication quality may occur.

[0012] Therefore, one of the objects of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can properly control UL transmission even when using multiple TRPs.

[0013] Means for solving problems

[0014] A terminal involved in one method of the present disclosure comprises: a receiving unit, which receives information related to the correspondence between the value of the sounding reference signal (SRS) resource indicator (SRS Resource Indicator (SRI)) field of the downlink control information (DownlinkControl Information (DCI)) detected for each control resource set (COntrol REsource SET (CORESET)) pool index and the spatial relationship information; and a control unit, which, in determining the spatial relationship information for an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) based on the DCI detected in a CORESET corresponding to a certain CORESET pool index, refers to the correspondence for the CORESET pool index to determine the spatial relationship information for the PUSCH.

[0015] Effects of the Invention

[0016] According to one method of the present disclosure, UL transmission can be properly controlled even when using multiple TRPs. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1A as well as Figure 1B This is a diagram showing an example of repeated transmission of the PUSCH.

[0018] Figure 2A as well as Figure 2B This is a diagram showing an example of an invalid symbol pattern.

[0019] Figure 3A as well as Figure 3B This is a diagram showing an example of nominal repetitions and actual repetitions.

[0020] Figure 4 This is a diagram showing an example of repeated transmission of PUSCH in multiple TRPs.

[0021] Figure 5A-5D This is a diagram showing an example of the correspondence between the value of the SRI field involved in the first embodiment and the SRI used for PUCCH repetition.

[0022] Fig. 6A as well as Figure 6B This is a diagram showing an example of parameters applied to each iteration when the number of instructed parameters is the same as or different from the number of iterations.

[0023] Figure 7 This is a diagram showing an example of determination of the number of repetitions based on the number of specific parameters.

[0024] Fig. 8A as well as Figure 8B This is a diagram showing an example of the TPMI instruction according to the first embodiment.

[0025] Fig. 9A as well as Fig. 9B This is a diagram showing an example of determining a UL beam for repeated PUSCH according to the second embodiment.

[0026] Fig. 10A as well as Fig. 10B This is a diagram showing an example of the correspondence relationship between the SRI fields of each CORESET pool index involved in the third embodiment.

[0027] Fig.11A as well as Fig. 11B This is a diagram showing an example of the structure of an SRS resource set and SRS resources involved in Implementation 3.1.

[0028] Fig.12 This is a diagram showing an example of the structure of an SRS resource set and SRS resources involved in Implementation 3.2.

[0029] Fig.13A as well as Fig. 13B This is a diagram showing an example of the structure of an SRS resource set and SRS resources involved in Implementation 3.3.

[0030] Fig.14A as well as Fig. 14B It is a diagram showing an example of a MAC CE for updating the spatial relationship of SRS according to the third embodiment.

[0031] Fig.15 This is a diagram showing an example of transmission of the same TB based on multiple DCIs according to the fourth embodiment.

[0032] Fig.16 This is a diagram showing an example of transmission of the same UCI based on multiple DCIs according to the fourth embodiment.

[0033] Fig.17 This is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment.

[0034] Fig.18 This is a diagram showing an example of the configuration of a base station according to an embodiment.

[0035] Fig.19This is a diagram showing an example of a configuration of a user terminal according to an embodiment.

[0036] Fig. 20 This is a diagram showing an example of the hardware configuration of a base station and a user terminal involved in one embodiment. DETAILED DESCRIPTION

[0037] (Repeatedly send)

[0038] In Rel.15, repeated transmission is supported in data transmission. For example, the base station (network (NW), gNB) can repeatedly transmit DL data (e.g., downlink shared channel (PDSCH)) a specific number of times. Or, the UE can repeatedly transmit UL data (e.g., uplink shared channel (PUSCH)) a specific number of times.

[0039] Figure 1A FIG. 1 is a diagram showing an example of repeated transmission of PUSCH. Figure 1A , an example of scheduling a specific number of repeated PUSCHs by a single DCI is shown. The number of repetitions is also called a repetition factor K or an aggregation factor K.

[0040] exist Figure 1A In , the repetition coefficient K=4, but the value of K is not limited thereto. In addition, the nth repetition is also called the nth transmission opportunity (transmission occasion), etc., and can also be identified by the repetition index k (0≤k≤K-1). In addition, Figure 1A , the repeated transmission of a PUSCH dynamically scheduled by DCI (for example, a PUSCH based on a dynamic grant) is shown, but it can also be applied to the repeated transmission of a PUSCH based on a set grant.

[0041] For example, in Figure 1A In the present invention, the UE semi-statically receives information indicating the repetition coefficient K (e.g., aggregation factor UL (aggregationFactorUL) or aggregation factor DL ​​(aggregationFactorDL)) through high-layer signaling. Here, the high-layer signaling may be, for example, RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast information, etc., or a combination thereof.

[0042] MAC signaling may use, for example, MAC control elements (MAC CE (Control Element)), MAC PDU (Protocol Data Unit), etc. Broadcast information may also be, for example, a master information block (MIB: Master Information Block), a system information block (SIB: System Information Block), minimum system information (remaining minimum system information (RMSI: Remaining Minimum System Information)), etc.

[0043] The UE controls the reception processing (e.g., at least one of reception, demapping, demodulation, and decoding) of the PDSCH in K consecutive time slots or the transmission processing (e.g., at least one of transmission, mapping, modulation, and coding) of the PUSCH based on at least one of the following field values ​​(or information represented by the field value) in the DCI:

[0044] Allocation of time domain resources (e.g., starting symbol, number of symbols in each time slot, etc.),

[0045] Allocation of frequency domain resources (e.g., a specific number of resource blocks (RBs), a specific number of resource block groups (RBGs)),

[0046] Modulation and Coding Scheme (MCS) index,

[0047] · The structure (configuration, setting, configuration) of the demodulation reference signal (DMRS) of PUSCH,

[0048] The state (TCI-state) of the spatial relation information (spatial relation info) of the PUSCH or the transmission structure indication (TCI: Transmission Configuration Indication or Transmission Configuration Indicator).

[0049] The same symbol allocation can also be applied between consecutive K time slots. Figure 1A, the PUSCH in each slot is allocated to a specific number of symbols from the beginning of the slot. The same symbol allocation between slots can also be determined as described in the above-mentioned time domain resource allocation.

[0050] For example, the UE may determine the allocation of symbols in each time slot based on the starting symbol S and the number of symbols L (e.g., Start and Length Indicator (SLIV)) determined based on the value m of a specific field (e.g., TDRA field) in the DCI. In addition, the UE may determine the initial time slot based on K2 information determined based on the value m of a specific field (e.g., TDRA field) in the DCI.

[0051] On the other hand, between the consecutive K time slots, the redundancy version (RV) applied to the TB based on the same data may be the same, or may be at least partially different. For example, the RV applied to the TB in the nth time slot (transmission opportunity, repetition) may also be determined based on the value of a specific field (e.g., RV field) in the DCI.

[0052] For resources allocated in K consecutive time slots, on at least one codeword, when the communication direction of each time slot is different from UL, DL or flexible (Flexible) specified by at least one of the uplink and downlink communication direction indication information for TDD control (for example, "TDD-UL-DL-ConfigCommon", "TDD-UL-DL-ConfigDedicated" of RRC IE) and the time slot format identifier (Slotformat indicator) of DCI (for example, DCI format 2_0), the resources of the time slot containing the codeword may not be sent (or received).

[0053] In Rel.15, Figure 1A As shown, PUSCH is repeatedly transmitted across multiple time slots (in time slot units), but after Rel.16, it is assumed that PUSCH is repeatedly transmitted in units shorter than time slots (for example, sub-time slot units, mini-time slot units, or specific code number units) (refer to Figure 1B ).

[0054] exist Figure 1B In , the repetition coefficient K=4, but the value of K is not limited thereto. In addition, the nth repetition is also called the nth transmission opportunity (transmission occasion), etc., and can also be identified by the repetition index k (0≤k≤K-1). In addition, Figure 1B, the repeated transmission of a PUSCH dynamically scheduled by DCI (for example, a PUSCH based on a dynamic grant) is shown, but it can also be applied to the repeated transmission of a PUSCH based on a set grant.

[0055] The UE may also determine the symbol allocation for PUSCH transmission (e.g., PUSCH with k=0) in a specific time slot based on the starting symbol S and the number of symbols L (e.g., StartSymbol and length) determined by the value m of a specific field (e.g., TDRA field) in the DCI of the PUSCH. In addition, the UE may also determine the specific time slot based on the Ks information determined by the value m of a specific field (e.g., TDRA field) in the DCI.

[0056] The UE may also dynamically receive information indicating the repetition coefficient K (e.g., number of repetitions) through downlink control information. The repetition coefficient may also be determined based on the value m of a specific field (e.g., TDRA field) in the DCI. For example, a table defining the correspondence between the bit value notified through the DCI, the repetition coefficient K, and the start symbol S and the number of symbols L may also be supported.

[0057] Figure 1A The slot-based repetition transmission shown may also be referred to as repetition transmission type A (eg, PUSCH repetition type A). Figure 1B The sub-slot based repetition transmission shown may also be referred to as repetition transmission Type B (eg, PUSCH repetition Type B).

[0058] The UE may be configured to apply at least one of repetition type A and repetition type B. For example, the repetition type applied by the UE may be notified from the base station to the UE through higher layer signaling (eg, PUSCH repetition type indicator (PUSCHRepTypeIndicator)).

[0059] One of repetitive transmission type A and repetitive transmission type B may be set for the UE for each DCI format for scheduling the PUSCH.

[0060] For example, for the first DCI format (e.g., DCI format 0_1), when the higher layer signaling (e.g., PUSCH RepTypeIndicator-AorDCIFormat0_1) is set to repetition transmission type B (e.g., PUSCH-RepTypeB), the UE applies repetition transmission type B to the PUSCH repetition transmission scheduled by the first DCI format. In other cases (e.g., when PUSCH-RepTypeB is not set, or when PUSCH-RepTypA is set), the UE applies repetition transmission type A to the PUSCH repetition transmission scheduled by the first DCI format.

[0061] (Invalid code mode)

[0062] It is also under study to notify the UE of information related to symbols (or symbol patterns) that cannot be used for PUSCH transmission when repeated transmission type B is applied for PUSCH transmission. The symbol pattern that cannot be used for PUSCH transmission may also be referred to as an invalid symbol pattern, an invalid symbol pattern, an unaccepted symbol pattern, etc.

[0063] The use of at least one of higher layer signaling and DCI to notify the invalid symbol pattern is under study. The DCI may also be a specific DCI format (eg, at least one of DCI formats 0_1 and 0_2).

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

[0065] In addition, the second high-level parameter may be used to notify the UE of the configuration of the notification field (or additional bit) in the DCI. That is, when the information related to the invalid symbol pattern is notified through the first high-level parameter, the UE may also determine whether the information related to the invalid symbol pattern is applied based on the second high-level parameter and the DCI.

[0066] In the case where the first high-level parameter is not notified or set, the UE may also control the transmission of the PUSCH without considering the invalid symbol pattern. In the case where the first high-level parameter is notified or set, the UE may also determine whether the invalid symbol pattern is applied based on the second high-level parameter and the DCI. For example, in the case where an additional bit (or a specific field) for indicating whether the invalid symbol pattern is applied is added to the DCI through the second high-level parameter indication, the UE may also determine whether the invalid symbol pattern is applied based on the specific field.

[0067] The first higher layer parameter may be information for notifying a symbol pattern that becomes invalid in PUSCH transmission, and for example, a bitmap format may be used (see Figure 2A ). Figure 2A This is a diagram showing an example of a case where an invalid symbol pattern is defined by a bitmap (1-D bitmap) for the time domain. The UE may also determine the resources that can be used for PUSCH transmission in one or more frequency bands (e.g., BWP) based on the information related to the invalid symbol pattern (see Figure 2B ).

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

[0069] (Nominal repetitions / Actual repetitions)

[0070] When repetition transmission type B is applied to perform repetition transmission in sub-slot units, a certain repetition transmission may cross a slot boundary depending on the repetition coefficient (K) and the data allocation unit.

[0071] Figure 3A An example is shown when the repetition coefficient (K) is 4 and the PUSCH length (L) is 4 and the repetition transmission type B is applied. Figure 3A In this case, the PUSCH with k=3 is configured across the time slot boundary. In this case, the PUSCH may be divided (or segmented) based on the time slot boundary and transmitted (see Figure 3B ).

[0072] In addition, it is also assumed that a time slot contains symbols that cannot be used for PUSCH transmission (for example, DL symbols or invalid symbols). Figure 3A, a case where a part of the symbols configured for the PUSCH with k=1 includes symbols (here, DL symbols) that cannot be used for the PUSCH transmission is shown. In this case, symbols other than the DL symbols may be used for PUSCH transmission (see Figure 3B ).

[0073] When symbols other than the two ends of the allocated symbols of a certain PUSCH include DL symbols (or invalid symbols), PUSCH transmission may be performed using symbols other than the DL symbol portion. In this case, the PUSCH may be divided (or segmented).

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

[0075] In addition, consider the repeated transmission before the DL symbol, invalid symbol or time slot boundary ( Figure 3A ) can also be called nominal repetitions. It takes into account the repetition of DL symbols, invalid symbols or time slot boundaries ( Figure 3B ) can also be called actual repetitions.

[0076] (Spatial relationship between SRS and PUSCH)

[0077] In Rel.15NR, the UE can also receive information (SRS setting information, such as parameters in the "SRS-Config" of the RRC control element) for sending a reference signal for measurement (e.g., a Sounding Reference Signal (SRS)).

[0078] Specifically, the UE may also receive at least one of information related to one or more SRS resource sets (SRS resource set information, for example, "SRS-ResourceSet" of the RRC control element) and information related to one or more SRS resources (SRS resource information, for example, "SRS-Resource" of the RRC control element).

[0079] An SRS resource set may also be associated with a specific number of SRS resources (a specific number of SRS resources may also be grouped into one set). Each SRS resource may also be identified according to an SRS resource identifier (SRS Resource Indicator (SRI)) or an SRS resource ID (Identifier).

[0080] The SRS resource set information may also include the SRS resource set ID (SRS-ResourceSetId), a list of SRS resource IDs (SRS-ResourceId) used in the resource set, the SRS resource type (for example, one of periodic SRS (Periodic SRS), semi-persistent SRS (Semi-Persistent SRS), aperiodic CSI (Aperiodic SRS)), and information on the usage of SRS.

[0081] Here, the SRS resource type may also represent one of periodic SRS (P-SRS), semi-persistent SRS (SP-SRS), and aperiodic CSI (A-SRS). In addition, the UE may also periodically (or periodically after activation) send P-SRS and SP-SRS, and send A-SRS based on the SRS request of the DCI.

[0082] In addition, the usage (RRC parameter "usage", L1 (Layer-1) parameter "SRS-SetUse") may be, for example, beam management, codebook (CB), noncodebook (NCB), antenna switching, etc. SRS for codebook or non-codebook purposes may also be used to determine the precoder for codebook-based or non-codebook-based PUSCH transmission based on SRI.

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

[0084] SRS resource information may also include SRS resource ID (SRS-ResourceId), number of SRS ports, SRS port number, send comb, SRS resource mapping (for example, time and / or frequency resource location, resource offset, resource period, number of repetitions, number of SRS code elements, SRS bandwidth, etc.), hopping association information, SRS resource type, sequence ID, SRS spatial relationship information, etc.

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

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

[0087] In addition, in the present disclosure, the SSB index, SSB resource ID, and SSB resource indicator (SSBRI) may also be replaced with each other. In addition, the CSI-RS index, CSI-RS resource ID, and CSI-RS resource indicator (CSI-RS Resource Indicator (CRI)) may also be replaced with each other. In addition, the SRS index, SRS resource ID, and SRI may also be replaced with each other.

[0088] The spatial relationship information of the SRS may also include a serving cell index, a BWP index (BWP ID), etc. corresponding to the above-mentioned specific reference signal.

[0089] When spatial relationship information related to SSB or CSI-RS and SRS is set for a certain SRS resource, the UE may also transmit the SRS resource using the same spatial domain filter (spatial domain transmit filter) as the spatial domain filter (spatial domain receive filter) used to receive the SSB or CSI-RS. In this case, the UE may also assume that the UE receive beam of the SSB or CSI-RS is the same as the UE transmit beam of the SRS.

[0090] When spatial relationship information related to other SRS (reference SRS) and the SRS (target SRS) is set for a certain SRS (target SRS) resource, the UE may also transmit the target SRS resource using the same spatial domain filter (spatial domain transmission filter) as the spatial domain filter (spatial domain transmission filter) used to transmit the reference SRS. That is, in this case, the UE may also assume that the UE transmission beam of the reference SRS is the same as the UE transmission beam of the target SRS.

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

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

[0093] (Multiple TRP)

[0094] In NR, one or more transmission / reception points (Transmission / Reception Point (TRP)) (Multi-TRP (M-TRP)) are being studied to use one or more panels (multi-panels) to perform DL transmission to the UE. In addition, the UE is studying to perform UL transmission to one or more TRPs (refer to Figure 4 ).

[0095] Regarding the above-mentioned repeated transmission type A and repeated transmission type B PUSCH transmission, if it is possible to transmit across the M-TRP, a considerable performance improvement can be expected compared to single PUSCH transmission. However, research on how to control the repeated transmission of PUSCH across the M-TRP has not made any progress. Not only repeated transmission, but also research on methods for properly performing UL transmission (PUSCH, PUCCH, etc.) to the M-TRP has not made any progress. If UL transmission across the M-TRP cannot be properly performed, a decrease in throughput or degradation in communication quality may occur.

[0096] Therefore, the inventors of the present invention have come up with a control method for UL transmission across M-TRP. According to one method of the present disclosure, for example, the UE can use different beams to perform UL transmission for multiple TRPs.

[0097] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The wireless communication methods according to the embodiments may be applied individually or in combination.

[0098] In addition, in the present disclosure, "A / B" may also mean "at least one of A and B".

[0099] In the present disclosure, activation, deactivation, indication (or indication), selection, configuration, update, determination, etc. may also be used interchangeably. In addition, in the present disclosure, sequence, list, set, group, etc. may also be used interchangeably.

[0100] In the present disclosure, panel, beam, panel group, beam group, uplink (UL) transmitting entity, TRP, spatial relationship information (SRI), spatial relationship, control resource set (CORESET), physical downlink shared channel (PDSCH), codeword, base station, specific antenna port (for example, demodulation reference signal (DMRS)) port), specific antenna port group (for example, DMRS port group), specific group (for example, code division multiplexing (CDM)) group, specific reference signal group, CORESET group), specific resource (for example, specific reference signal resource), specific resource set (for example, specific 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), unified TCI state (unifiedTCI state), etc. can also be replaced with each other.

[0101] In addition, for a single DCI, the i-th TRP (TRP#i) may also mean the i-th TCI state, the i-th CDM group, etc. (i is an integer).

[0102] In addition, for multi-DCI, the i-th TRP (TRP#i) may also mean the CORESET corresponding to the CORESET pool index = i, the i-th TCI state, the i-th CDM group, etc. (i is an integer).

[0103] The panel may also be associated with at least one of a group index of an SSB / CSI-RS group, a group index of a group-based beam report, and a group index of an SSB / CSI-RS group for a group-based beam report.

[0104] In addition, the panel identifier (Identifier (ID)) and the panel can also be replaced with each other. That is, the TRP ID and the TRP, the CORESET group ID and the CORESET group, etc. can also be replaced with each other.

[0105] In the present disclosure, index, ID, indicator, resource ID may also be replaced with each other. In the present disclosure, list, group, cluster, subset, etc. may also be replaced with each other.

[0106] The repetition disclosed in the present invention may also be interchangeable with MTRP-based repetition, Rel.17 repetition, repetition with different spatial relationships, repeated PUSCH, repeated PUCCH, repeated transmission, etc. In addition, the repeated transmission in the following embodiments may also be equivalent to at least one of repeated transmission type A, repeated transmission type B, and other repeated transmission types.

[0107] In addition, the SRS resource set in the following embodiments may be replaced by an SRS resource set for a codebook or non-codebook purpose, or may be replaced by an SRS resource set for other purposes.

[0108] (Wireless Communication Method)

[0109] <First Embodiment>

[0110] In the first embodiment, the UE determines specific parameters for a plurality of PUSCH transmission opportunities in a repeated PUSCH based on one DCI.

[0111] The above specific parameters may also be equivalent to at least one of the following parameters:

[0112] TPMI,

[0113] UL beam parameters (e.g., SRI, spatial relationship, UL TCI status),

[0114] Transmit Power Control (TPC) related parameters (e.g., TPC command, α, P0, closed loop power control state, Pathloss Reference Signal (PL-RS)).

[0115] The UE may determine that the size of the DCI field indicating the above-mentioned specific parameter is the same as the size of the DCI field indicating the same parameter of Rel.15 / 16NR, or may determine that it is M times the size of the DCI field indicating the same parameter of Rel.15 / 16NR. For example, if M-TRP is set to be sent repeatedly (or an extension of the DCI field indicating the above-mentioned specific parameter) through high-layer signaling, the UE may also determine that the size of the DCI field indicating the above-mentioned specific parameter is M times the size of the DCI field indicating the same parameter of Rel.15 / 16NR.

[0116] The value of M can be pre-specified by the specification, set to the UE through high-level signaling, or determined based on UE capabilities. M can also be replaced with the number of TRPs, the number of SRIs, the number of TPMIs, the number of TPC-related parameters, etc.

[0117] In addition, in the first embodiment, the UE may be configured / instructed to send a repeated PUSCH with a repetition count of K, and the repeated PUSCH may be sent to multiple (different) TRPs. The repetition count K may be configured by RRC or indicated by MAC CE / DCI.

[0118] The RV sequence can be fixed throughout the K iterations (also using the same RV) or it can be cycled.

[0119] The assumption / setting of the spatial relationship may be different for each repetition or for each RV within the repetition. For example, the spatial relationship of the DMRS for the PUSCH of each repetition / each RV may be set by the UE through RRC or indicated through MAC CE / DCI. Alternatively, at least one of the repetition index and the RV index may be associated with the TCI state ID.

[0120] The repeated PUSCH may be transmitted based on at least one of a dynamic grant and a set grant. In addition, these contents may also be the same in other embodiments of the present disclosure using the repeated PUSCH.

[0121] Reference Figure 5A-5D , the DCI field indicating the above-mentioned specific parameters is explained. In each example, an example of specifying the SRI of the repeated PUSCH by the SRI field is shown, but other parameters such as TPMI and TPC-related parameters can also be replaced in the same way. Each example shows an example in which the codebook-based PUSCH transmission is set to the UE, but the non-codebook-based PUSCH transmission can also be understood in the same way.

[0122] Figure 5A-5D This is a diagram showing an example of the correspondence between the value of the SRI field involved in the first embodiment and the SRI used for PUCCH repetition. In each example, SRI#X_i, SRI#Y_i (where i is a number), etc. can also be set / activated / indicated by higher layer signaling.

[0123] Figure 5A This is the above correspondence relationship when the SRI corresponding to the purpose of Rel.15NR = codebook is specified. The value of a certain SRI field corresponds to one SRI.

[0124] Figure 5BThis is the above correspondence when the SRI field is composed of 2 bits, which is twice the Rel.15NR, in the first embodiment. The value of a certain SRI field corresponds to 2 SRIs. PUSCH#i (the ith PUSCH) (i is an integer) can mean either the SRI corresponding to the ith TRP or the SRI corresponding to the ith repetition. PUSCH#i can also be replaced with the ith SRI. In addition, the present disclosure can also be applied to the case of specifying the third and subsequent PUSCHs.

[0125] Figure 5C This is the above correspondence relationship when the SRI field is configured with the same number of bits (1 bit) as Rel.15NR in the first embodiment. A certain SRI field value corresponds to two SRIs. Figure 5C and Figure 5B Although the number of groups that can be expressed is limited compared to SRI, an increase in the number of DCI bits can be suppressed.

[0126] Figure 5D This is the above correspondence relationship when the SRI field is composed of the same number of bits (1 bit) as Rel.15NR in the first embodiment. Figure 5D and Figure 5C The difference is that PUSCH#1 and PUSCH#2 are not distinguished. Figure 5D In the corresponding relationship, all values ​​of SRI#X_i and SRI#Y_i can be notified all the time, or some values ​​can be not notified (that is, there can be values ​​of the SRI field corresponding to one SRI and values ​​of the SRI field corresponding to multiple SRIs).

[0127] The above-mentioned specific parameter set applied to repeated transmission may also be referred to as a sequence (eg, SRI sequence, TPMI sequence, etc.).

[0128] [Number of repetitions]

[0129] The number of the above-mentioned specific parameters indicated by the above-mentioned DCI field (in Figure 5B In the example, 2) can be the same as or different from the number of repetitions.

[0130] When the number of indicated parameters is the same as the number of iterations, the indicated parameters may be applied in the order from the first iteration (transmission opportunity) to the last iteration (in other words, in the order of the transmission opportunities from the earliest to the latest (in ascending order)). For example, when {SRI#1, SRI#2, SRI#3, SRI#4} is indicated for 4 iterations, the UE may allocate SRI#1, SRI#2, SRI#3, SRI#4 to the 1st to 4th iterations (PUSCH#1-#4), respectively. Fig. 6A). In addition, conversely, the indicated parameters may be applied in the order of the transmission opportunity from the latest to the earliest (descending order).

[0131] When the number of parameters indicated is smaller than the number of iterations, the indicated parameters may be applied to each iteration according to a specific rule. For example, when {SRI#1, SRI#2} is indicated for 4 iterations, the UE may allocate SRI#1, SRI#2, SRI#1, SRI#2 (PUSCH#1-#4) to the 1st to 4th iterations, respectively. Figure 6B ), or SRI#1, SRI#1, SRI#2, SRI#2 can be allocated separately.

[0132] When the number of indicated parameters is greater than the number of iterations, the indicated parameters may be applied to each iteration according to a specific rule. For example, when {SRI#1, SRI#2, SRI#3, SRI#4} is indicated for two iterations, the UE may allocate SRI#1 and SRI#2 or SRI#3 and SRI#4 for the first to second iterations.

[0133] The UE may not assume that the number of the specific parameters indicated by the DCI field is different from the number of repetitions. In this case, the complexity of UE implementation can be reduced.

[0134] The UE may also determine the number of iterations based on the number of the specific parameters indicated by the DCI field. Figure 7 This is a diagram showing an example of determining the number of iterations based on the number of specific parameters. In this example, the value of the SRI field = 0 corresponds to one SRI (SRI#1), and the value of the SRI field = 1 corresponds to two SRIs (SRI#1, #2). In this case, if the value of the designated SRI field = 0, the UE can determine the number of iterations to be 1, and if the value of the designated SRI field = 1, the UE can determine the number of iterations to be 2.

[0135] In addition, even in the case where the above-mentioned specific parameters are set / indicated through higher layer signaling rather than being set / indicated through DCI, the UE can determine the number of iterations based on the number of the specific parameters.

[0136] In the first embodiment, the number of iterations K may be provided to the UE in the same manner as Rel. 15 / 16.

[0137] [High-layer signaling settings and MAC CE]

[0138] As in the first embodiment, in order to set or activate a plurality of SRS resources corresponding to the SRI field, it is preferable to study the setting of higher layer signaling and MAC CE.

[0139] As for the high-layer signaling settings and MAC CE for the i-th PUSCH / SRI of the first embodiment, the method of replacing the CORESET pool index or SRS resource set ID with the i-th PUSCH / SRI in the description of the high-layer signaling settings associated with the CORESET pool index and the MAC CE associated with the SRS resource set in the third embodiment to be described later can also be applied.

[0140] For example, the CORESET pool index = 0, 1 in the description of the configuration of the high-layer signaling of the third embodiment described later may be replaced by the contents of the first and second PUSCH / SRI, respectively. The first and second SRS resource sets in the description of the MAC CE of the third embodiment described later may be replaced by the contents of the first and second PUSCH / SRI, respectively.

[0141] [TPMI]

[0142] The TPMI indication for the above-mentioned i-th PUSCH is described below. Hereinafter, the case where the DCI for the first PUSCH and the second PUSCH is indicated to the UE is described as an example.

[0143] As the DCI field for indicating TPMI, the precoding information and number of layers field may be used as in Rel. 15 / 16, or another field may be used. Here, the DCI field for indicating TPMI is simply referred to as the TPMI field.

[0144] The DCI may also include a TPMI field for the first PUSCH (TPMI field #1) and a TPMI field for the second PUSCH (TPMI field #2) ( Fig. 8A ). According to this structure, the TPMI used for the first and second PUSCHs can be flexibly specified.

[0145] The DCI may include one TPMI field indicating the TPMI for the first PUSCH and the TPMI for the second PUSCH. According to this configuration, it is possible to suppress an increase in the size of the DCI.

[0146] The UE may also apply a designated TPMI equally to each PUSCH.

[0147] The UE may apply a designated TPMI to the first PUSCH and determine the TPMI to be applied to the second PUSCH according to a specific rule (for example, using a specific transformation formula or randomly). According to this structure, for example, a random precoder can be applied to the second PUSCH.

[0148] The UE may also apply a designated TPMI to the first PUSCH and determine the TPMI to be applied to the second PUSCH based on the designated TPMI. For example, the UE may also determine the TPMI to be applied to the second PUSCH as a value obtained by adding or subtracting an offset value from the designated TPMI. The offset value may be pre-specified by the specification, set to the UE by high-layer signaling, specified by DCI, or determined based on UE capabilities.

[0149] The UE may also apply a designated TPMI to the first PUSCH and determine the TPMI to be applied to the second PUSCH according to the configuration of the higher layer signaling. This configuration is suitable for the case where, for example, the precoder of the second PUSCH does not need to be changed.

[0150] The UE may also determine the TPMI applied to each PUSCH based on the correspondence between the value of a designated TPMI field and the TPMI applied to the first PUSCH and the second PUSCH. The correspondence may be specified in advance by the specification, set to the UE by high-layer signaling, specified by the DCI, or determined based on the UE capability. According to this structure, the TPMI of each PUSCH can be appropriately and flexibly indicated while suppressing the increase in the size of the DCI.

[0151] Figure 8B TPMI#0 and TPMI#1 are respectively determined as TPMIs corresponding to the first and second PUSCHs when the value of the TPMI field is 00.

[0152] According to the first embodiment described above, it is possible to appropriately implement repeated transmission for M-TRP based on a single DCI.

[0153] <Second Embodiment>

[0154] In the second embodiment, the UE determines the spatial relationship (UL beam) for repeated PUSCH based on the activated TCI state for a specific downlink channel / downlink reference signal. According to this structure, the preferred beam for DL ​​reception can be commonly used for UL transmission.

[0155] The specific downlink channel / downlink reference signal may be, for example, at least one of PDSCH, PDCCH, DMRS, CSI-RS, etc.

[0156] For example, the SRI field included in the DCI for scheduling the repeated PUSCH may also be associated with a set of specific TCI states in the activated TCI states for the PDSCH. The specific TCI state may also be a TCI state equivalent to a specific Quasi-Co-Location (QCL) type (e.g., QCL type D, QCL type A, etc.).

[0157] The set of the specific TCI state may also correspond to at least one of the following:

[0158] (A) a set of TCI states corresponding to the smallest N code points among the code points of the TCI field included in the DCI that schedules the PDSCH,

[0159] (B) a set of TCI states corresponding to the minimum N code points in which at least one DCI code point indicates two or more activated TCI states among the code points of the TCI field included in the DCI for scheduling the PDSCH,

[0160] (C) A set of TCI states corresponding to the minimum N code points in which each DCI code point indicates two or more activated TCI states among the code points of the TCI field included in the DCI that schedules the PDSCH.

[0161] The value of N can be pre-defined by the specification, set to the UE by high-level signaling, or determined based on the UE capability. In addition, the smallest (in other words, starting from the smallest) N code points can also be the largest (in other words, starting from the largest) N code points.

[0162] In addition, the value of N may be the number of SRS resources included in an SRS resource set set to use (usage) = codebook or non-codebook (for example, in Rel. 15, if use = codebook, it is 2, and if use = non-codebook, it is 4). In this case, the size of the SRI field can be made common in the DCI for scheduling PUSCH for a single TRP and the DCI for scheduling PUSCH for an M-TRP.

[0163] The UE may also determine the spatial relationship (UL beam) for the repeated PUSCH based on one or more TCI states selected from the set of specific TCI states according to the value of the SRI field. According to such a structure, the optimal TCI state can be applied to the repeated PUSCH as SRI without the need for additional high-level control for PUSCH. This is based on the following two situations: it can be considered that the use cases of M-TRP repetition of PUSCH and PDSCH are close, and it can be expected (assumed) to set the optimal TCI state in the TCI state list for PDSCH.

[0164] Fig. 9A as well as Fig. 9B This is a diagram showing an example of determining a UL beam for repeated PUSCH according to the second embodiment. Fig. 9A The left side of represents the correspondence between the value of the TCI field of the DCI (e.g., DCI format 1_1) that schedules the PDSCH and the specified TCI state in the activated TCI state. For example, TCI field = 000 represents one TCI state (TCI state #0), and TCI field = 001 represents two TCI states (TCI states #0, #1).

[0165] When N=2 as described above and following (A) or (B), the specific set of TCI states is the set of TCI states corresponding to the smallest 2 code points (000, 001) (one is {TCI state #0} and the other is {TCI state #0, #1}). Fig. 9A The right side of shows an example of associating the set of specific TCI states with the value of the SRI field in ascending order. In addition, the association between the set of specific TCI states and the value of the SRI field is not limited to this, and for example, they can also be associated in descending order.

[0166] In being carried out Fig. 9A In the case of association, if Fig. 9B As shown, if the value of the SRI field of the DCI (e.g., DCI format 0_1) that is designated to schedule repeated PUSCH is 1, the UE applies a beam based on {TCI state #0, #1} to the repeated PUSCH. In addition, when the number of parameters indicated (SRI number, TCI number) is the same as or different from the number of repetitions, the UE can also decide which parameter to apply to each repetition as described in the first embodiment.

[0167] In addition, as in Fig. 9AThe method of deriving the correspondence of the SRI field from the list of TCI states for PDSCH described in can also be limited to the case of M-TRP based on a single DCI. In other words, in the case where at least one of the code points in the TCI field indicates more than two activated TCI states, the method described in Fig. 9A The method for deriving the correspondence of the SRI field from the list of TCI states for PDSCH is described in.

[0168] In the case where the UE does not / cannot derive the correspondence of the SRI field from the list of TCI states for PDSCH, the correspondence of the SRI field (for example, the correspondence between the value of the SRI field and SRI / UL-TCI) can be pre-defined through specifications or set through high-level signaling.

[0169] When the UE does not / cannot derive the correspondence of the SRI field from the list of TCI states for PDSCH, the UE may either assume that repeated PUSCH across M-TRP is not expected (not configured), or send repeated PUSCH based on the same SRI as in Rel.15 / 16.

[0170] In addition, even in the case where the UE derives / is able to derive the correspondence of the SRI field from the list of TCI states for PDSCH, when the correspondence of the SRI field (for example, the correspondence between the value of the SRI field and SRI / UL-TCI) is set through high-layer signaling, the UE may follow the setting of the high-layer signaling (which may also be given priority).

[0171] According to the second embodiment described above, the transmission beam of the PUSCH can be determined based on the preferred DL beam.

[0172] <Third Embodiment>

[0173] The third embodiment describes the case where multiple DCIs are used for M-TRP. In this case, at least one CORESET having a CORESET pool index (RRC parameter "CORESETPoolIndex") having one or more values ​​is set for the UE.

[0174] In addition, the third embodiment is not limited to repeated PUSCH. When repeated PUSCH is used, the following contents can also be applied in combination with the first and second embodiments described above.

[0175] According to the existing Rel.16NR specification, the value of the SRI field in the DCI format detected for each value of the CORESET pool index (for each CORESET) corresponds to the SRI in the same SRS resource set. Therefore, it is difficult to change the UL beam indication for each CORESET.

[0176] Therefore, in the third embodiment, the SRI (spatial relationship) of the PUSCH of each TRP (each CORESET pool index) is set for the UE through high-layer signaling.

[0177] Fig. 10A as well as Fig. 10B This is a diagram showing an example of the correspondence relationship between the SRI fields of each CORESET pool index involved in the third embodiment. Fig. 10A Indicates the correspondence between the SRI fields of the DCI detected in the CORESET that is set to the CORESET pool index = 0 or the CORESET pool index is not set. Fig. 10B Indicates the correspondence of the SRI field of the DCI detected in the CORESET set to the CORESET pool index = 1.

[0178] In addition, in the present disclosure, hereinafter, “is set to CORESET pool index = 0” may be replaced with “is set to CORESET pool index = 0 or is not set to CORESET pool index”.

[0179] For a PUSCH scheduled via a CORESET with a CORESET pool index set to 0, the UE refers to Fig. 10A As shown, the SRI (SRI#0_0, SRI#0_1) set for the CORESET is determined by the higher layer signaling.

[0180] For a PUSCH scheduled via a CORESET with a CORESET pool index set to 1, the UE refers to Fig. 10B As shown, the SRI (SRI#1_0, SRI#1_1) set for the CORESET is determined by the higher layer signaling.

[0181] [High-layer signaling settings]

[0182] In Rel.15, the maximum number of SRS resource sets with purpose = code book (CB) is one, and the maximum number of SRS resources included in the SRS resource set with purpose = code book is 2. The maximum number of SRS resource sets with purpose = non-code book (NCB) is one, and the maximum number of SRS resources included in the SRS resource set with purpose = non-code book is 4.

[0183] Therefore, in the above-mentioned setting of SRI per TRP (per CORESET pool index), it is necessary to eliminate (or relax) the limitation on the number of SRS resources or the number of SRS resource sets.

[0184] The following embodiments are described respectively.

[0185] Implementation 3.1: It is defined that the maximum number of SRS resource sets is P, the maximum number of SRS resources in each SRS resource set is 2,

[0186] Implementation 3.2: It is defined that the maximum number of SRS resource sets is one, and the maximum number of SRS resources in each SRS resource set is 2P.

[0187] · Implementation 3.3: It is defined that the number of SRS resource sets is not limited, and the maximum number of SRS resources in each SRS resource set is 2P.

[0188] Here, the value of P may be equivalent to the number of TRPs or the number of different CORESET pool indexes set for the UE (or the maximum CORESET pool index set for the UE + 1). For example, in the case of a CORESET with a CORESET pool index = 1, P may be 2. The value of P is of course not limited to 2.

[0189] In addition, in embodiments 3.1-3.3, unless otherwise specified, the SRS resource set and SRS resources for use = CB are described on the premise of P = 2, but the SRS resource set and SRS resources for use = NCB or other uses may also be replaced. For example, when replaced with the SRS resource set and SRS resources for use = NCB, the number of SRS resource sets may be the same value, but the number of SRS resources in each SRS resource set may also be replaced with a value twice the number of SRS resources for use = CB (for example, 4 in the case of embodiment 3.1, and 4P in the case of embodiments 3.2-3.3).

[0190] [[Implementation 3.1]]

[0191] In implementation 3.1, one SRS resource set corresponds to one TRP (CORESET pool index). The correspondence between the CORESET pool index and the SRS resource set ID can be explicitly set through high-level signaling, or can be associated with the CORESET pool index = 0, 1, ... in order starting from the smallest SRS resource set ID. In addition, the "starting from the smallest" in the present disclosure can also be replaced with "starting from the largest".

[0192] Fig.11Aas well as Fig. 11B This is a diagram showing an example of the structure of an SRS resource set and SRS resources involved in Implementation 3.1. Fig.11A Indicates the SRS resources associated with SRS resource set ID = 0, Fig. 11B Indicates the SRS resources associated with the SRS resource set ID=1.

[0193] Here, SRS#x_y may also mean the SRS resource of the yth (or y+1)th entry of SRS resource set ID=x (the same applies to subsequent figures). In addition, the SRS resource set ID and SRS resource ID shown in the figure are just examples and are not limited to these values ​​(the same applies to subsequent figures).

[0194] SRS resource set ID=0 may also be used to specify the SRI of a CORESET whose CORESET pool index is set to 0. SRS resource set ID=1 may also be used to specify the SRI of a CORESET whose CORESET pool index is set to 1.

[0195] In this example, Fig. 10A The SRI#0_0 and SRI#0_1 shown may be SRS#0_0 (SRS resource corresponding to SRS resource ID=0) and SRS#0_1 (SRS resource corresponding to SRS resource ID=1), respectively.

[0196] also, Fig. 10B The SRI#1_0 and SRI#1_1 shown may be SRS#1_0 (SRS resource corresponding to SRS resource ID=2) and SRS#1_1 (SRS resource corresponding to SRS resource ID=2), respectively.

[0197] [[Implementation 3.2]]

[0198] In implementation 3.2, W SRS resources included in one SRS resource set correspond to one TRP (CORESET pool index). The correspondence between the CORESET pool index and the SRS resource ID can be explicitly set through high-layer signaling, or can be associated with CORESET pool index = 0, 1, ... in sequence starting from the smallest SRS resource ID.

[0199] In addition, the value of W may also be the number of SRS resources that determines the size of the SRI field of the DCI. For example, it may be the value obtained by applying a floor function (floor function) or a ceiling function (roof function) to the value obtained by dividing the number of SRS resources in the SRS resource set whose purpose = CB / NCB by P.

[0200] Fig.12 This is a diagram showing an example of the structure of an SRS resource set and SRS resources involved in Implementation 3.2. Fig.12 It indicates the SRS resources associated with the SRS resource set ID = 0. In this example, the SRS resource set with the SRS resource set ID = 0 is associated with 2P = 4 SRS resources. In this case, W = 2.

[0201] Alternatively, the first W=2 SRS resources in SRS resource set ID=0, starting from the smallest one, may be used to specify the SRI of the CORESET with CORESET pool index=0. Alternatively, the next W=2 SRS resources in SRS resource set ID=0, starting from the smallest one, may be used to specify the SRI of the CORESET with CORESET pool index=1.

[0202] In this example, Fig. 10A The SRI#0_0 and SRI#0_1 shown may be SRS#0_0 (SRS resource corresponding to SRS resource ID=0) and SRS#0_1 (SRS resource corresponding to SRS resource ID=1), respectively.

[0203] also, Fig. 10B The SRI#1_0 and SRI#1_1 shown may be SRS#0_2 (SRS resource corresponding to SRS resource ID=2) and SRS#0_3 (SRS resource corresponding to SRS resource ID=3), respectively.

[0204] [[Implementation 3.3]]

[0205] In implementation 3.3, W SRS resources included in one or more SRS resource sets correspond to one TRP (CORESET pool index). The correspondence between the CORESET pool index, the SRS resource set ID, and the SRS resource ID can also be explicitly set through high-layer signaling. In addition, with regard to the correspondence, it can also be associated with CORESET pool index = 0, 1, ... in order starting from the smallest SRS resource set ID and then starting from the smallest SRS resource ID, every W are sequentially associated with CORESET pool index = 0, 1, ...

[0206] In addition, the value of W may also be the number of SRS resources that determines the size of the SRI field of the DCI. For example, it may be the value obtained by applying a floor function (floor function) or a ceiling function (roof function) to the value obtained by dividing the number of SRS resources in the SRS resource set whose purpose = CB / NCB by P.

[0207] In implementation 3.3, it is also possible to allow the SRS resources corresponding to a certain CORESET pool index to be configured across multiple SRS resource sets. In other words, the UE may determine that the SRS resources configured across multiple SRS resource sets correspond to the same CORESET pool index.

[0208] Fig.13A as well as Fig. 13B This is a diagram showing an example of the structure of an SRS resource set and SRS resources involved in Implementation 3.3. Fig.13A Indicates the SRS resources associated with SRS resource set ID = 0, Fig. 13B Indicates the SRS resources associated with SRS resource set ID = 1. In this example, for each SRS resource set, a maximum of 2P = 4 SRS resources can be associated. Fig.13A In the example, three SRS resources are associated. Fig. 13B In this example, 1 SRS resource is associated.

[0209] Alternatively, W=2 SRS resources starting from the smallest one in SRS resource set ID=0 may be used to specify the SRI of the CORESET with CORESET pool index=0. Since there is only one remaining SRS resource in SRS resource set ID=0, this SRS resource and an SRS resource in SRS resource set ID=1, a total of W=2 SRS resources may be used to specify the SRI of the CORESET with CORESET pool index=1.

[0210] In this example, Fig. 10A The SRI#0_0 and SRI#0_1 shown may be SRS#0_0 (SRS resource corresponding to SRS resource ID=0) and SRS#0_1 (SRS resource corresponding to SRS resource ID=1), respectively.

[0211] also, Fig. 10B The SRI#1_0 and SRI#1_1 shown may be SRS#0_2 (SRS resource corresponding to SRS resource ID=2) and SRS#1_0 (SRS resource corresponding to SRS resource ID=3), respectively.

[0212] [MAC CE]

[0213] The updating of the spatial relationship corresponding to SRI according to the third embodiment will be described.

[0214] For the UE, the reference signal resources used to derive the spatial relationship of the SRS resources included in a certain SRS resource set may also be activated through the MAC CE. Such activation may also be referred to as updating (or overriding) the spatial relationship (SRI) corresponding to the SRS resources. In addition, in the present disclosure, activation, deactivation, indication, selection, update, determination, etc. may also be interchangeable.

[0215] The UE may also assume that, in the transmission of a specific signal / channel (eg, PUSCH, SRS), the spatial relationship (SRI) activated by the above-mentioned MAC CE is applied to the SRS resource specified by the DCI.

[0216] Fig.14A as well as Fig. 14B It is a diagram showing an example of a MAC CE used for updating the spatial relationship of the SRS involved in the third embodiment.

[0217] Fig.14A This shows an example of a MAC CE that can be used to update the spatial relationship of the SRS resource level (class) for one SRS resource set. This MAC CE is the Enhanced SP / AP SRS Spatial Relation Indication MAC CE specified in Rel.16NR.

[0218] The MAC CE may include information indicating whether to activate or deactivate ("A / D" field), a cell ID for identifying a cell containing an SRS resource set of an activation object, a BWP ID corresponding to the UL bandwidth part (Bandwidth Part (BWP)) of the SRS resource set containing the activation object, a P-SRS resource set ID of the activation object, an activation object carrier ("SUL" field), a reference signal resource ID corresponding to the spatial relationship of the SRS resource, etc. The MAC CE may also include a serving cell ID corresponding to the reference signal resource ID, a BWP ID, etc. (whether these are included may also be indicated by the "C" field). In addition, "R" indicates a reserved field.

[0219] The reference signal resource ID for the i-th SRS resource in the SRS resource set corresponds to "Resource Id i ". In addition, the reference signal resource ID may also be at least one of a non-zero power CSI-RS resource index, an SSB index, an SRS resource ID, a CORESETID, etc.

[0220] F i Can also be used to identify "Resource Idi " corresponds to which reference signal (e.g., CSI-RS, SSB, SRS (P-SRS, SP-SRS, A-SRS), CORESET). Regarding "Resource Id i " corresponds to which reference signal, or according to F i and "Resource Id i " is judged by the combination of its own specific bits.

[0221] It can also be, Fig.14A The MAC CE can be applied to at least one (e.g., all) of the SRS resource sets for purposes of codebook, non-codebook, beam management, and antenna switching.

[0222] Fig. 14B An example of a MAC CE that can be used to update the spatial relationship of the SRS resource levels of multiple SRS resource sets is shown. The MAC CE is similar to Fig.14A , but the difference is that Fig.14A The same structure from octet (Octet (Oct)) 2 to 2N+2 is included in multiple. The spatial relationship of the SRS resource levels for different SRS resource sets can also be specified through each octet set.

[0223] In addition, Fig. 14B It contains information about 2 SRS resource sets, but it can also contain more than 3.

[0224] The X field shown in the figure (recorded in Oct 2N+3) may also indicate whether it contains more than 1 SRS resource set spatial relationship indication. For example, if X=1, it may also mean that there is a field thereafter (for example, after Oct 2N+4), and if X=0, it may also mean that there is no field thereafter.

[0225] In addition, the X field may also be located at Oct 2 (e.g., the position of the upper left R field). In this case, the X field may also mean, for example: if X=1, there is a field subsequent to the spatial relationship indication of the SRS resource set (e.g., after Oct 2N+3), and if X=0, there is no field afterwards.

[0226] In addition, the X field may not be explicitly specified.

[0227] The octet containing the SRS resource set ID field (e.g., Oct 2N+3, Oct 2) may also be omitted. If the UE determines that the MAC CE contains an information set (set) equivalent to the spatial relationship indication of multiple SRS resource sets, it may also be assumed that these information sets are applied in order starting from the smallest SRS resource set ID.

[0228] It is also possible not to include a part of the fields (or octets) for the second SRS resource set. In this case, it is also possible to determine that the value of the field that is not included (not notified) is the same as the value that was previously (in the past) notified / set for the second SRS resource set (maintained, not updated value). In addition, it is also possible to determine that the value of the field that is not included (not notified) is the same as the value that was notified / set for the first SRS resource set in the same MAC CE. According to these structures, the increase in the overhead of the MACCE can be suppressed.

[0229] [Supplement to the third embodiment]

[0230] The above-mentioned restrictions on the number of SRS resources and the number of SRS resource sets of Rel.15 can also be used when at least one of the following two situations is met: any RRC parameter for a specific release (e.g., Rel.17) is not set to the UE; the CORESET pool index (different value of CORESET pool index or CORESET pool index = 1) is not notified. Otherwise, at least one of the number of SRS resources and the number of SRS resource sets in implementation modes 3.1-3.3 can also be applied.

[0231] In addition, although SRI is described in the third embodiment, other parameters such as TPMI, UL beam parameters, TPC associated parameters, etc. can also be replaced in the same manner. These parameters (or the correspondence between these parameters and DCI fields) can also be set / specified / determined per TRP (CORESET pool index).

[0232] At least one of the third embodiments may also be applied only to UEs that report a specific UE capability or support the specific UE capability.

[0233] The specific UE capability may also represent at least one of the following:

[0234] Whether to support the association of SRIs for each CORESET pool (or CORESET pool index),

[0235] The maximum number of CORESET pools (or CORESET pool indexes) supported,

[0236] The maximum number of SRS resource sets supported (or the maximum number of SRS resource sets supported for a specific purpose),

[0237] The maximum number of SRS resources supported (or the maximum number of SRS resources supported for a specific purpose).

[0238] According to the third embodiment described above, the spatial relationship for M-TRP can be appropriately determined based on multiple DCIs.

[0239] <Fourth Embodiment>

[0240] The fourth embodiment describes the case where multiple DCI is used for M-TRP. The fourth embodiment is not limited to repeated PUSCH.

[0241] Consider the case where DCI1 and DCI2 for scheduling PUSCH are detected in different CORESETs respectively.

[0242] When DCI1 and DCI2 are associated with the same HARQ process ID (or HARQ process number) and represent the same value of the New Data Indicator (NDI) field, and the UE receives the DCI2 that schedules other PUSCHs before the PUSCH scheduled by the DCI1, the UE may also send the same transport block (Transport Block (TB)) in all these PUSCHs. In this case, for example, the PUSCH of the same TB can be sent (retransmitted, repeatedly sent) at short intervals using different beams.

[0243] This operation may be permitted only when the above-mentioned DCI1 and DCI2 are detected in CORESETs with different CORESET pool indexes, or may be permitted regardless of whether the CORESET pool indexes are different.

[0244] This operation may be permitted only when one or both of the DCI1 and DCI2 schedule a repeated PUSCH, or may be permitted also when both schedule a non-repeated PUSCH.

[0245] Fig.15 This is a diagram showing an example of transmission of the same TB based on multiple DCIs according to the fourth embodiment. For DCI1 and DCI2 shown in the figure, the values ​​of the HARQ process number field, NDI field, etc. are related to each other (for example, the same). In this example, DCI1 schedules repeated PUSCH (PUSCH#1, #2) using SRI#0. DCI2 schedules repeated PUSCH (PUSCH#3, #4) using SRI#1.

[0246] The UE detects DCI1 in the CORESET with CORESET pool index = 0. In addition, the UE detects DCI2 in the CORESET with CORESET pool index = 1 after receiving DCI1 and before starting to transmit PUSCH#1.

[0247] In this example, the UE transmits the same TB in PUSCH#1 to #4. In essence, it is possible to implement repetitive transmission more than the original repetition number 2 by using different SRIs.

[0248] Next, consider the case where DCI1 and DCI2 that trigger PUCCH are detected in different CORESETs. In addition, the PUCCH (uplink control information (Uplink Control Information (UCI))) triggered by these DCIs may also be, for example, a hybrid automatic repeat request acknowledgment (HARQ-ACK) for PDSCH, a non-periodic CSI report, etc.

[0249] In the case where DCI1 and DCI2 have specific DCI fields, the UE may also use the PUCCH triggered by the DCI2 to send the same UCI as the UCI sent by the PUCCH triggered by the DCI1. In this case, for example, the PUCCH of the same UCI can be sent (retransmitted, repeatedly sent) at short intervals using different beams.

[0250] In addition, the specific DCI field may be a field indicating the transmission of the same UCI or another field. In addition, the values ​​of the specific DCI fields of DCI1 and DCI2 may be assumed to be the same or may be different. For example, the specific DCI field may be a TCI field, and the above operation may be allowed even when the values ​​of the TCI field are different in DCI1 and DCI2.

[0251] The above operation may be permitted only when the above DCI1 and DCI2 are detected in CORESETs with different CORESET pool indexes, or may be permitted regardless of whether the CORESET pool indexes are different.

[0252] The above operation may be permitted only when one or both of the DCI1 and DCI2 trigger a repeated PUCCH, or may be permitted also when both trigger a non-repeated PUCCH.

[0253] The above operation may also be allowed when the UE receives the DCI2 for triggering other PUCCHs before the PUCCH triggered by the DCI1. The above operation may also be allowed when the UE receives the DCI2 for triggering other PUCCHs after the PUCCH triggered by the DCI1.

[0254] Fig.16 This is a diagram showing an example of transmission of the same UCI based on multiple DCIs according to the fourth embodiment. For DCI1 and DCI2 shown in the figure, the values ​​of specific DCI fields are related to each other (for example, the same). In this example, DCI1 triggers PUCCH#1 using SRI#0 (spatial relationship #0). DCI2 triggers PUCCH#2 using SRI#1 (spatial relationship #1).

[0255] The UE detects DCI1 in the CORESET with CORESET pool index = 0. In addition, the UE detects DCI2 in the CORESET with CORESET pool index = 1 after receiving DCI1 and before starting to send PUCCH#1.

[0256] In this example, the UE transmits the same UCI in PUCCH#1-#2. In essence, it is possible to implement repeated transmission of PUCCH using different SRIs.

[0257] For example, the UE may send a HARQ-ACK for the PDSCH scheduled by DCI1 in PUCCH#1, and also send the same HARQ-ACK in PUCCH#2.

[0258] In addition, the UE may send only the UCI of PUCCH#1 in PUCCH#2, or may send UCI including at least the UCI of PUCCH#1 (for example, in addition to the UCI of PUCCH#1, there is also UCI triggered by DCI2).

[0259] The resources of PUCCH#2 may be controlled (specified) by DCI2, may be derived from the resources of PUCCH#1, or may be controlled by combining DCI1 and DCI2.

[0260] According to the fourth embodiment described above, it is possible to appropriately determine the transmission of the same TB / UCI for M-TRP based on multiple DCIs.

[0261] <Others>

[0262] At least one of the above-mentioned implementation modes may also be applied only to a UE that reports a specific UE capability (UE capability) or supports the specific UE capability.

[0263] The specific UE capability may also represent at least one of the following:

[0264] Whether PUSCH repetition is supported,

[0265] Whether different spatial relationships for PUSCH repetition are supported,

[0266] Whether PUCCH repetition is supported,

[0267] Whether different spatial relationships for PUCCH repetition are supported,

[0268] The number (or maximum number) of repetitions or spatial relationships supported.

[0269] In addition, at least one of the above-mentioned embodiments may also be applied to a case where the UE is configured with specific information associated with the above-mentioned embodiments through high-layer signaling (if not configured, operations such as Rel.15 / 16 are applied). For example, the specific information may also be information indicating activation of different spatial relationships for PUSCH repetition, arbitrary RRC parameters for a specific version (e.g., Rel.17), etc.

[0270] In addition, the above-mentioned embodiments can be applied to situations where multiple TRPs or multiple panels (operations) are set for the UE, and can also be applied to situations where it is not the case.

[0271] (Wireless Communication System)

[0272] Hereinafter, a configuration of a wireless communication system according to an embodiment of the present disclosure will be described. In the wireless communication system, communication is performed using one of the wireless communication methods according to the above embodiments of the present disclosure or a combination thereof.

[0273] Fig.17 A diagram showing an example of a schematic structure of a wireless communication system according to an embodiment. The wireless communication system 1 may be a system that implements communication using Long Term Evolution (LTE) standardized by the Third Generation Partnership Project (3GPP), the fifth generation mobile communication system New Radio (5G NR), or the like.

[0274] In addition, the wireless communication system 1 can also support dual connectivity (Multi-RAT Dual Connectivity (MR-DC)) between multiple radio access technologies (Radio Access Technology (RAT)). MR-DC can also include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA))) and NR (E-UTRA-NR Dual Connectivity (E-UTRA-NR Dual Connectivity (EN-DC))), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NR-E-UTRA Dual Connectivity (NE-DC))), etc.

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

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

[0277] The wireless communication system 1 may also include a base station 11 that forms a macro cell C1 with a relatively wide coverage, and a base station 12 (12a-12c) that is configured in the macro cell C1 and forms a small cell C2 that is narrower than the macro cell C1. The user terminal 20 may also be located in at least one cell. The configuration and number of each cell and the user terminal 20 are not limited to the illustrated method. Hereinafter, when the base stations 11 and 12 are not distinguished, they are collectively referred to as the base station 10.

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

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

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

[0281] Multiple base stations 10 can also be connected by wire (for example, optical fiber, X2 interface, etc. in accordance with Common Public Radio Interface (CPRI)) or wireless (for example, NR communication). For example, when NR communication between base stations 11 and 12 is used as a backhaul, the base station 11 equivalent to the upper station can also be called an Integrated Access Backhaul (IAB) host, and the base station 12 equivalent to a relay station (relay) can also be called an IAB node.

[0282] The base station 10 may also be connected to the core network 30 via other base stations 10 or directly. The core network 30 may also 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.

[0283] The user terminal 20 may also be a terminal that supports at least one of communication methods such as LTE, LTE-A, and 5G.

[0284] In the wireless communication system 1, a wireless access method based on orthogonal frequency division multiplexing (OFDM) may be used. For example, in at least one of the downlink (DL) and the uplink (UL), cyclic prefix OFDM (CP-OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), etc. may be used.

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

[0286] As downlink channels, the wireless communication system 1 may use 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.

[0287] In addition, as uplink channels, 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)) and the like can also be used in the wireless communication system 1.

[0288] User data, high-layer control information, system information block (SIB), etc. are transmitted through PDSCH. User data, high-layer control information, etc. can also be transmitted through PUSCH. In addition, master information block (MIB) can also be transmitted through PBCH.

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

[0290] In addition, the DCI for scheduling the PDSCH may also be referred to as DL allocation, DL DCI, etc., and the DCI for scheduling the PUSCH may also be referred to as UL grant, UL DCI, etc. In addition, the PDSCH may also be replaced by DL data, and the PUSCH may also be replaced by UL data.

[0291] In the detection of PDCCH, the control resource set (CORESET) and the search space can also be used. CORESET corresponds to the resources for searching DCI. The search space corresponds to the search area and search method for PDCCH candidates. A CORESET can also be associated with one or more search spaces. The UE can also monitor the CORESET associated with a search space based on the search space setting.

[0292] A search space may also correspond to a PDCCH candidate corresponding to one or more aggregation levels. One or more search spaces may also be referred to as a search space set. In addition, the "search space", "search space set", "search space setting", "search space set setting", "CORESET", "CORESET setting" and the like in the present disclosure may also be interchangeable.

[0293] Uplink control information (uplink control information (UCI)) including at least one of channel state information (CSI), delivery confirmation information (e.g., also known as hybrid automatic repeat request confirmation (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR) can also be transmitted through PUCCH. The random access preamble used to establish a connection with a cell can also be transmitted through PRACH.

[0294] In the present disclosure, downlink, uplink, etc. may be expressed without adding "link". In addition, various channels may be expressed without adding "Physical" at the beginning.

[0295] In the wireless communication system 1, a synchronization signal (Synchronization Signal (SS)), a downlink reference signal (Downlink Reference Signal (DL-RS)), etc. may also be transmitted. In the wireless communication system 1, as DL-RS, a cell-specific reference signal (Cell-specific Reference Signal (CRS)), a channel state information reference signal (Channel State Information Reference Signal (CSI-RS)), a demodulation reference signal (DeModulation Reference Signal (DMRS)), a positioning reference signal (Positioning Reference Signal (PRS)), a phase tracking reference signal (Phase Tracking Reference Signal (PTRS)), etc. may also be transmitted.

[0296] 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 SS (PSS, SSS) and PBCH (and DMRS for PBCH) may also be referred to as SS / PBCH block, SS Block (SSB), etc. In addition, SS, SSB, etc. may also be referred to as reference signals.

[0297] In addition, in the wireless communication system 1, as an uplink reference signal (UL-RS), a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. may also be transmitted. In addition, DMRS may also be called a user terminal specific reference signal (UE-specific ReferenceSignal).

[0298] (Base Station)

[0299] Fig.18 1 is a diagram showing an example of a configuration of a base station according to an embodiment. The base station 10 includes a control unit 110, a transmitting and receiving unit 120, a transmitting and receiving antenna 130, and a transmission line interface 140. In addition, the control unit 110, the transmitting and receiving unit 120, the transmitting and receiving antenna 130, and the transmission line interface 140 may each be provided with more than one.

[0300] In addition, in this example, the functional blocks of the characteristic parts in this embodiment are mainly shown, and it is also possible to assume that the base station 10 also has other functional blocks required for wireless communication. Part of the processing of each unit described below may also be omitted.

[0301] The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, a control circuit, and the like that are described based on common knowledge in the technical field to which the present disclosure relates.

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

[0303] The transmitting and receiving unit 120 may also include a baseband unit 121, a radio frequency (RF) unit 122, and a measuring unit 123. The baseband unit 121 may also include a transmitting processing unit 1211 and a receiving processing unit 1212. The transmitting and receiving unit 120 may be composed of a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measuring circuit, a transmitting and receiving circuit, etc., which are described based on the common knowledge in the technical field involved in the present disclosure.

[0304] The transmitting and receiving unit 120 may be configured as an integrated transmitting and receiving unit, or may be configured as a transmitting unit and a receiving unit. The transmitting unit may also be configured as a transmitting processing unit 1211 and an RF unit 122. The receiving unit may also be configured as a receiving processing unit 1212, an RF unit 122, and a measuring unit 123.

[0305] The transmitting / receiving antenna 130 can be constituted by an antenna described based on common knowledge in the technical field involved in the present disclosure, such as an array antenna.

[0306] The transmitting and receiving unit 120 may also transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitting and receiving unit 120 may also receive the above-mentioned uplink channel, uplink reference signal, etc.

[0307] The transmitting and receiving unit 120 may also form at least one of a transmitting beam and a receiving beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), or the like.

[0308] The sending and receiving unit 120 (sending processing unit 1211), for example, may also perform Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (for example, RLC retransmission control), Medium Access Control (MAC) layer processing (for example, HARQ retransmission control), etc. on the data and control information obtained from the control unit 110 to generate a bit string to be sent.

[0309] The transmitting and receiving unit 120 (transmitting processing unit 1211) can also perform channel coding (which may also include error correction coding), modulation, mapping, filter processing, discrete Fourier transform (DFT) processing (as needed), inverse fast Fourier transform (IFFT) processing), precoding, digital-to-analog conversion and other transmission processing on the bit string to be sent, and output a baseband signal.

[0310] The transmitting and receiving unit 120 (RF unit 122 ) may also perform modulation, filter processing, amplification, etc. on the baseband signal to a radio frequency band, and transmit the signal in the radio frequency band via the transmitting and receiving antenna 130 .

[0311] On the other hand, the transmitting and receiving unit 120 (RF unit 122 ) may also perform amplification, filter processing, demodulation to a baseband signal, etc. on the signal in the radio frequency band received by the transmitting and receiving antenna 130 .

[0312] The sending and receiving unit 120 (receiving processing unit 1212) can also apply analog-to-digital conversion, fast Fourier transform (FFT) processing, inverse discrete Fourier transform (IDFT) processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to obtain user data, etc.

[0313] The transmitting and receiving unit 120 (measuring unit 123) may also implement measurements related to the received signal. For example, the measuring unit 123 may also perform radio resource management (Radio Resource Management (RRM)) measurement, channel state information (CSI) measurement, etc. based on the received signal. The measuring unit 123 may also measure the received power (e.g., reference signal received power (Reference Signal Received Power (RSRP))), received quality (e.g., reference signal received quality (Reference Signal Received Quality (RSRQ)), signal to interference plus noise ratio (Signal to Interference plus Noise Ratio (SINR)), signal to noise ratio (Signal to Noise Ratio (SNR))), signal strength (e.g., received signal strength indicator (Received Signal Strength Indicator (RSSI))), propagation path information (e.g., CSI), etc. The measurement result may also be output to the control unit 110.

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

[0315] In addition, the transmitting unit and the receiving unit of the base station 10 in the present disclosure may also be constituted by at least one of the transmitting and receiving unit 120 , the transmitting and receiving antenna 130 , and the transmission path interface 140 .

[0316] In addition, the transmitting and receiving unit 120 may transmit one downlink control information (Downlink Control Information (DCI)) (single DCI) for determining spatial relationship information for a plurality of uplink shared channels (Physical Uplink Shared Channel (PUSCH)) to the user terminal 20 .

[0317] The transmitting and receiving unit 120 may also receive the plurality of PUSCHs transmitted by the user terminal 20 using a spatial domain transmit filter based on the spatial relationship information.

[0318] In addition, the sending and receiving unit 120 can also send to the user terminal 20 information related to the correspondence between the value of the measurement reference signal (Sounding Reference Signal (SRS)) resource indicator (SRS Resource Indicator (SRI)) field of the detected downlink control information (Downlink Control Information (DCI)) indexed by each control resource set (ControlResource SET (CORESET)) pool and the spatial relationship information.

[0319] The control unit 110 can also be imagined that the user terminal 20, in determining the spatial relationship information for the uplink shared channel (Physical Uplink Shared Channel (PUSCH)) based on the DCI detected in the CORESET equivalent to a certain CORESET pool index, refers to the corresponding relationship for the CORESET pool index, determines the spatial relationship information for the PUSCH, and receives the multiple PUSCHs sent by the user terminal 20 using the spatial domain transmit filter based on the spatial relationship information.

[0320] (User Terminal)

[0321] Fig.19 2 is a diagram showing an example of a configuration of a user terminal according to an embodiment. The user terminal 20 includes a control unit 210, a transmission / reception unit 220, and a transmission / reception antenna 230. In addition, the control unit 210, the transmission / reception unit 220, and the transmission / reception antenna 230 may each be provided in one or more pieces.

[0322] In addition, in this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, and the user terminal 20 may also be assumed to have other functional blocks required for wireless communication. Part of the processing of each unit described below may also be omitted.

[0323] The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, a control circuit, and the like that are described based on common knowledge in the technical field to which the present disclosure relates.

[0324] The control unit 210 may also control signal generation, mapping, etc. The control unit 210 may also control transmission, reception, measurement, etc. using the transmission and reception unit 220 and the transmission and reception antenna 230. The control unit 210 may also generate data, control information, sequences, etc. to be sent as signals, and forward them to the transmission and reception unit 220.

[0325] The transmitting and receiving unit 220 may also include a baseband unit 221, an RF unit 222, and a measuring unit 223. The baseband unit 221 may also include a transmitting processing unit 2211 and a receiving processing unit 2212. The transmitting and receiving unit 220 may be composed of a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measuring circuit, a transmitting and receiving circuit, etc., which are explained based on the common knowledge in the technical field involved in the present disclosure.

[0326] The transmitting and receiving unit 220 may be configured as an integrated transmitting and receiving unit, or may be configured as a transmitting unit and a receiving unit. The transmitting unit may also be configured as a transmitting processing unit 2211 and an RF unit 222. The receiving unit may also be configured as a receiving processing unit 2212, an RF unit 222, and a measuring unit 223.

[0327] The transmitting / receiving antenna 230 can be constituted by an antenna described based on common knowledge in the technical field involved in the present disclosure, such as a matrix antenna.

[0328] The transmitting and receiving unit 220 may also receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitting and receiving unit 220 may also transmit the above-mentioned uplink channel, uplink reference signal, etc.

[0329] The transmitting and receiving unit 220 may also use digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), etc. to form at least one of a transmitting beam and a receiving beam.

[0330] The sending and receiving unit 220 (sending processing unit 2211) may also perform PDCP layer processing, RLC layer processing (for example, RLC retransmission control), MAC layer processing (for example, HARQ retransmission control), etc. on the data and control information obtained from the control unit 210, to generate a bit string to be sent.

[0331] The transmitting and receiving unit 220 (transmitting processing unit 2211) can also perform channel coding (which may also include error correction coding), modulation, mapping, filter processing, DFT processing (as needed), IFFT processing, precoding, digital-to-analog conversion and other transmission processing on the bit string to be sent, and output a baseband signal.

[0332] In addition, whether to apply DFT processing may also be based on the setting of transform precoding. When transform precoding is enabled for a certain channel (e.g., PUSCH), the transmitting and receiving unit 220 (transmitting processing unit 2211) may perform DFT processing as the above-mentioned transmission processing in order to transmit the channel using a DFT-s-OFDM waveform, and when it is not the above-mentioned case, DFT processing is not performed as the above-mentioned transmission processing.

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

[0334] On the other hand, the transmitting and receiving unit 220 (RF unit 222) may also perform amplification, filter processing, demodulation to a baseband signal, etc. on the signal in the radio frequency band received by the transmitting and receiving antenna 230.

[0335] The sending and receiving unit 220 (receiving processing unit 2212) can also apply analog-to-digital conversion, FFT processing, IDFT processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the obtained baseband signal to obtain user data, etc.

[0336] The transmitting and receiving unit 220 (measuring unit 223) may also perform measurements related to the received signal. For example, the measuring unit 223 may also perform RRM measurements, CSI measurements, etc. based on the received signal. The measuring unit 223 may also 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 also be output to the control unit 210.

[0337] In addition, the transmitting unit and the receiving unit of the user terminal 20 in the present disclosure may also be composed of at least one of the transmitting and receiving unit 220 and the transmitting and receiving antenna 230 .

[0338] In addition, the control unit 210 may also use one downlink control information (Downlink Control Information (DCI)) to determine the spatial relationship information for multiple uplink shared channels (Physical Uplink Shared Channel (PUSCH)) .

[0339] The transmitting and receiving unit 220 may also use a spatial domain transmit filter based on the spatial relationship information to transmit the multiple PUSCHs.

[0340] The control unit 210 may also determine the spatial relationship information based on a Sounding Reference Signal (SRS) Resource Indicator (SRI) field of the DCI whose number of bits is extended according to Radio Resource Control (RRC) signaling.

[0341] The control unit 210 may also determine the number of the plurality of PUSCHs based on the number of SRIs corresponding to the value of the SRI field.

[0342] The control unit 210 may also determine the spatial relationship information based on one or more TCI states selected from a set of specific TCI states in an activated transmission structure indication (Transmission Configuration Indication (TCI)) state according to the value of the Sounding Reference Signal (SRS) resource indicator (SRS Resource Indicator (SRI)) field of the DCI.

[0343] In addition, the sending and receiving unit 220 can also receive information related to the correspondence between the value of the sounding reference signal (SRS) resource indicator (SRS Resource Indicator (SRI)) field of the detected downlink control information (Downlink Control Information (DCI)) indexed by each control resource set (Control Resource SET (CORESET)) pool and the spatial relationship information.

[0344] The control unit 210 may also determine the spatial relationship information for the uplink shared channel (Physical Uplink Shared Channel (PUSCH)) based on the DCI detected in the CORESET corresponding to the CORESET pool index, by referring to the corresponding relationship for the CORESET pool index.

[0345] If the number of different CORESET pool indexes to be set is set to P, the control unit 210 can also determine that the maximum number of SRS resource sets set for specific purposes is P, and the maximum number of SRS resources in each of the SRS resource sets is 2.

[0346] If the number of different CORESET pool indexes to be set is set to P, the control unit 210 can also determine that the maximum number of SRS resource sets set for a specific purpose is 1, and the maximum number of SRS resources in each SRS resource set is 2P.

[0347] The control unit 210 may also determine that the SRS resources configured to span across multiple SRS resource sets correspond to the same CORESET pool index.

[0348] (Hardware Structure)

[0349] In addition, the block diagram used for the description of the above-mentioned embodiment represents a block of a functional unit. These functional blocks (structural units) are implemented by any combination of at least one of hardware and software. In addition, the implementation method of each functional block is not particularly limited. That is, each functional block can be implemented using a device that is physically or logically combined, or two or more devices that are physically or logically separated can be directly or indirectly (for example, using wired, wireless, etc.) connected and implemented using these multiple devices. The functional block can also be implemented by combining software for the above-mentioned one device or the above-mentioned multiple devices.

[0350] Here, the functions include judging, determining, judging, calculating, calculating, processing, deriving, investigating, searching, confirming, receiving, sending, outputting, accessing, solving, selecting, selecting, establishing, comparing, assuming, expecting, regarding, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc., but are not limited to these. For example, a functional block (structural unit) that performs a sending function may also be referred to as a transmitting unit, a transmitter, etc. As described above, the implementation method is not particularly limited.

[0351] For example, a base station, a user terminal, etc. in one embodiment of the present disclosure may also function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 201001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc.

[0352] In addition, in the present disclosure, the words such as device, circuit, equipment, section, unit, etc. can be used interchangeably. The hardware structure of the base station 10 and the user terminal 20 can be configured to include one or more of the devices shown in the figure, or can be configured to exclude some of the devices.

[0353] For example, only one processor 1001 is shown, but there may be multiple processors. In addition, the processing may be performed by one processor, or by two or more processors simultaneously, sequentially, or using other methods. In addition, the processor 1001 may also be implemented by one or more chips.

[0354] The various functions in the base station 10 and the user terminal 20 are achieved, for example, by reading specific software (program) into hardware such as the processor 1001 and the memory 1002, so that the processor 1001 performs calculations, controls communication via the communication device 1004, or controls at least one of the reading and writing of data in the memory 1002 and the storage 1003.

[0355] The processor 1001 controls the entire computer by, for example, operating an operating system. The processor 1001 may also be configured by a central processing unit (CPU) including an interface with a peripheral device, a control device, an arithmetic device, a register, etc. For example, at least a portion of the above-mentioned control unit 110 (210), the sending and receiving unit 120 (220), etc. may also be implemented by the processor 1001.

[0356] In addition, the processor 1001 reads the program (program code), software module, data, etc. from at least one of the storage 1003 and the communication device 1004 to the memory 1002, and performs various processes according to them. As the program, a program that causes the computer to execute at least a part of the operations described in the above-mentioned embodiments is used. For example, the control unit 110 (210) can also be implemented by a control program stored in the memory 1002 and operated in the processor 1001, and the same can be achieved for other functional blocks.

[0357] The memory 1002 is a computer-readable recording medium, and may be composed of at least one of a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically EPROM (EEPROM), a random access memory (RAM), and other appropriate storage media. The memory 1002 may also be referred to as a register, a cache, a main memory (main storage device), etc. The memory 1002 can store executable programs (program codes), software modules, etc. for implementing the wireless communication method involved in one embodiment of the present disclosure.

[0358] The storage 1003 is a computer-readable recording medium, and may be composed of at least one of a flexible disk, a floppy (registered trademark) disk, an optical disk (e.g., a compact disk (Compact Disc ROM (CD-ROM)), a digital versatile disk, a Blu-ray (registered trademark) disk), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, a stick, a key drive), a magnetic stripe, a database, a server, and other appropriate storage media. The storage 1003 may also be referred to as an auxiliary storage device.

[0359] The communication device 1004 is hardware (transmitting and receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also called a network device, a network controller, a network card, a communication module, etc. In order to realize at least one of frequency division duplex (Frequency Division Duplex (FDD)) and time division duplex (Time Division Duplex (TDD)), the communication device 1004 may include, for example, a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. For example, the above-mentioned transmitting and receiving unit 120 (220), the transmitting and receiving antenna 130 (230), etc. may also be realized by the communication device 1004. The transmitting and receiving unit 120 (220) may also realize the physical or logical separation of the transmitting unit 120a (220a) and the receiving unit 120b (220b).

[0360] The input device 1005 is an input device that receives input from the outside (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.). The output device 1006 is an output device that implements output to the outside (e.g., a display, a speaker, a light emitting diode (LED) lamp, etc.). In addition, the input device 1005 and the output device 1006 may also be an integrated structure (e.g., a touch panel).

[0361] In addition, the processor 1001, the memory 1002 and other devices are connected via a bus 1007 for communicating information. The bus 1007 may be configured using a single bus or different buses between the devices.

[0362] In addition, the base station 10 and the user terminal 20 may also 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), and a field programmable gate array (FPGA), and the hardware may be used to implement a part or all of each functional block. For example, the processor 1001 may also be implemented using at least one of these hardware.

[0363] (Variation Example)

[0364] In addition, the terms described in the present disclosure and the terms required for understanding the present disclosure may also be replaced with terms having the same or similar meanings. For example, channels, code elements, and signals (signals or signaling) may also be replaced with each other. In addition, a signal may also be a message. A reference signal may also be referred to as RS, or may be referred to as a pilot, a pilot signal, etc., depending on the standard applied. In addition, a component carrier (CC) may also be referred to as a cell, a frequency carrier, a carrier frequency, etc.

[0365] A wireless frame may also be composed of one or more periods (frames) in the time domain. Each period (frame) of the one or more periods (frames) constituting a wireless frame may also be referred to as a subframe. Furthermore, a subframe may also be composed of one or more time slots in the time domain. A subframe may also be a fixed time length (e.g., 1 ms) that is not dependent on a parameter set (numerology).

[0366] Here, a parameter set (numerology) may also be a communication parameter applied to at least one of the transmission and reception of a certain signal or channel. For example, a parameter set (numerology) may also represent at least one of a subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, wireless frame structure, specific filtering processing performed by a transmitter and receiver in the frequency domain, and specific windowing processing performed by a transmitter and receiver in the time domain.

[0367] A time slot may also be composed of one or more symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.) in the time domain. In addition, a time slot may also be a time unit based on a parameter set.

[0368] A time slot may also include multiple mini-slots. Each mini-slot may also be composed of one or more symbols in the time domain. In addition, a mini-slot may also be called a sub-slot. A mini-slot may also be composed of a smaller number of symbols than a time slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may also be referred to as a PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may also be referred to as a PDSCH (PUSCH) mapping type B.

[0369] Radio frames, subframes, time slots, mini-time slots, and symbols all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-time slots, and symbols may also be referred to by other names corresponding to them. In addition, time units such as frames, subframes, time slots, mini-time slots, and symbols in the present disclosure may also be interchangeable.

[0370] For example, one subframe may be referred to as a TTI, multiple consecutive subframes may be referred to as a TTI, and one time slot or one mini time slot 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 (e.g., 1-13 symbols), or a period longer than 1 ms. In addition, the unit representing a TTI may also be referred to as a time slot, a mini time slot, etc., instead of a subframe.

[0371] Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in the LTE system, the base station schedules each user terminal to allocate wireless resources (frequency bandwidth, transmission power, etc. that can be used in each user terminal) in TTI units. In addition, the definition of TTI is not limited to this.

[0372] TTI can be a transmission time unit for data packets (transport blocks), code blocks, code words, etc. after channel coding, and can also be a processing unit for scheduling, link adaptation, etc. In addition, when a TTI is given, the time interval (for example, the number of symbols) to which a transport block, code block, code word, etc. is actually mapped can also be shorter than the TTI.

[0373] In addition, when one time slot or one mini time slot is called TTI, one or more TTIs (i.e., one or more time slots or one or more mini time slots) can also be the minimum time unit of scheduling. In addition, the number of time slots (the number of mini time slots) constituting the minimum time unit of scheduling can also be controlled.

[0374] A TTI having a time length of 1 ms may also be referred to as a normal TTI (TTI in 3GPP Rel.8-12), a standard TTI, a long TTI, a normal subframe, a standard subframe, a long subframe, a time slot, etc. A TTI shorter than a normal TTI may also be referred to as a shortened TTI, a short TTI, a partial TTI (partial or fractional TTI), a shortened subframe, a short subframe, a mini time slot, a sub time slot, a time slot, etc.

[0375] In addition, a long TTI (e.g., normal TTI, subframe, etc.) may be replaced by a TTI having a time length exceeding 1 ms, and a short TTI (e.g., shortened TTI, etc.) may be replaced by a TTI having a TTI length shorter than that of the long TTI and longer than 1 ms.

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

[0377] In addition, in the time domain, an RB may include one or more symbols, and may be of the length of one slot, one mini slot, one subframe, or one TTI. One TTI, one subframe, etc. may also be composed of one or more resource blocks.

[0378] In addition, one or more RBs may also be referred to as a physical resource block (Physical RB (PRB)), a sub-carrier group (Sub-Carrier Group (SCG)), a resource element group (Resource Element Group (REG)), a PRB pair, an RB pair, etc.

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

[0380] Bandwidth Part (BWP) (also referred to as partial bandwidth, etc.) may also represent a subset of contiguous common RBs (common resource blocks) for a numerology in a carrier. Here, common RBs may also be identified by the index of the RB based on the common reference point of the carrier. PRBs may also be defined in a BWP and numbered within the BWP.

[0381] The BWP may include a UL BWP (BWP for UL) and a DL BWP (BWP for DL). For a UE, one or more BWPs may be configured in one carrier.

[0382] At least one of the configured BWPs may also be activated, and the UE may not assume that a specific channel / signal is transmitted or received outside the activated BWP. In addition, "cell", "carrier", etc. in the present disclosure may also be replaced by "BWP".

[0383] In addition, the structures of the radio frame, subframe, time slot, mini-time slot and symbol described above are merely examples. For example, the number of subframes included in a radio frame, the number of time slots per subframe or radio frame, the number of mini-time slots included in a time slot, the number of symbols and RBs included in a time slot or mini-time slot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, and the like can be changed in various ways.

[0384] In addition, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, relative values ​​relative to a specific value, or other corresponding information. For example, wireless resources may also be indicated by a specific index.

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

[0386] Information, signals, etc. described in this disclosure may also be represented using one of a variety of different techniques. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be mentioned throughout the above description may also be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination thereof.

[0387] In addition, information, signals, etc. can be output in at least one of the following directions: from a higher layer (upper layer) to a lower layer (lower layer), and from a lower layer to a higher layer. Information, signals, etc. can also be input and output via multiple network nodes.

[0388] The input and output information, signals, etc. can be saved in a specific location (e.g., a memory) or managed using a management table. The input and output information, signals, etc. can be overwritten, updated, or recorded. The output information, signals, etc. can also be deleted. The input information, signals, etc. can also be sent to other devices.

[0389] The notification of information is not limited to the method / implementation method described in the present disclosure, and other methods may also be used. For example, the notification of information in the present disclosure may also be implemented through physical layer signaling (e.g., downlink control information (downlink control information: Downlink Control Information (DCI)), uplink control information (uplink control information: Uplink Control Information (UCI))), high-level signaling (e.g., Radio Resource Control (RRC)) signaling, broadcast information (Master Information Block (MIB)), System Information Block (System Information Block (SIB)), etc.), Medium Access Control (MAC) signaling), other signals or a combination thereof.

[0390] In addition, physical layer signaling may also be referred to as layer 1 / layer 2 (Layer 1 / Layer 2 (L1 / L2)) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. In addition, RRC signaling may also be referred to as an RRC message, such as an RRC connection setup (RRC Connection Setup) message, an RRC connection reconstruction (RRC Connection Reconfiguration) message, etc. In addition, MAC signaling may also be notified using, for example, a MAC control element (MACControl Element (CE)).

[0391] Furthermore, notification of specific information (eg, notification of “it is X”) is not limited to explicit notification, but may be performed implicitly (eg, by not notifying the specific information or by notifying other information).

[0392] The determination can be made by a value represented by 1 bit (0 or 1), by a true or false value (Boolean value) represented by true (true) or false (false), or by comparison of numerical values ​​(for example, comparison with a specific value).

[0393] Whether software is referred to as software, firmware, middleware, microcode, hardware description language, or by other names, it shall be interpreted broadly to mean instructions, instruction sets, codes, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, execution threads, procedures, functions, or the like.

[0394] In addition, software, instructions, information, etc. may also be sent and received via transmission media. For example, when the software is sent from a website, server, or other remote source using at least one of wired technology (coaxial cable, optical cable, twisted pair, digital subscriber line (DSL), etc.) and wireless technology (infrared, microwave, etc.), at least one of these wired technology and wireless technology is included in the definition of transmission medium.

[0395] The terms "system" and "network" used in the present disclosure can be used interchangeably. "Network" may also mean a device (eg, a base station) included in the network.

[0396] 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", "transmission 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", and "panel" can be used interchangeably.

[0397] In the present disclosure, terms such as "base station (BS)", "wireless 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", and "component carrier" can be used interchangeably. Base stations are sometimes also referred to as macro cells, small cells, micro cells, micro cells, and other terms.

[0398] A base station can accommodate one or more (for example, 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 also be provided with communication services by a base station subsystem (for example, a small base station for indoor use (Remote Radio Head (RRH))). Terms such as "cell" or "sector" refer to a part or the entirety of the coverage area of ​​at least one of a base station and a base station subsystem that provides communication services within the coverage area.

[0399] In the present disclosure, terms such as “mobile station (MS)”, “user terminal”, “user device (User Equipment (UE))”, and “terminal” can be used interchangeably.

[0400] A mobile station is also sometimes called a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a hand set, a user agent, a mobile client, a client or some other appropriate terminology.

[0401] At least one of the base station and the mobile station may also be referred to as a transmitting device, a receiving device, a wireless communication device, etc. In addition, at least one of the base station and the mobile station may also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body may be a means of transportation (e.g., a car, an airplane, etc.), a mobile body that moves in an unmanned manner (e.g., a drone, an autonomous driving car, etc.), or a robot (manned or unmanned). In addition, at least one of the base station and the mobile station also includes a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may also be an Internet of Things (IoT) machine such as a sensor.

[0402] In addition, the base station in the present disclosure may also be replaced by a user terminal. For example, the various methods / implementations of the present disclosure may also be applied to a structure in which the communication between a base station and a user terminal is replaced by the communication between multiple user terminals (for example, may also be referred to as device-to-device (D2D)), vehicle-to-everything (V2X), etc.). In this case, the user terminal 20 may also be configured to have the functions of the above-mentioned base station 10. In addition, the language such as "uplink" and "downlink" may also be replaced by the language corresponding to the communication between terminals (for example, "side"). For example, the uplink channel, the downlink channel, etc. may also be replaced by the side channel.

[0403] Likewise, the user terminal in the present disclosure may be replaced by a base station. In this case, the base station 10 may have the functions of the user terminal 20 described above.

[0404] In the present disclosure, operations that are set to be performed by a base station may also be performed by its upper node depending on the situation. In a network including one or more network nodes having a base station, various operations performed for communication with a terminal can obviously be performed by a base station, one or more network nodes other than the base station (for example, consider (Mobility Management Entity (MME)), Serving-Gateway (S-GW), etc., but not limited to this) or a combination thereof.

[0405] Each method / implementation method described in this disclosure may be used alone, in combination, or switched during execution. In addition, the processing procedures, sequences, flow charts, etc. of each method / implementation method described in this disclosure may be swapped in order as long as there is no contradiction. For example, for the method described in this disclosure, various elements of the steps are presented in an illustrative order, and are not limited to the specific order presented.

[0406] The various modes / implementations described in the present disclosure may also be applied 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 (Ultra Mobile Broadband), etc. MobileBroadband (UMB)), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB)), Bluetooth (Bluetooth (registered trademark)), systems using other appropriate wireless communication methods, and next-generation systems based on them. In addition, multiple systems can also be combined (for example, a combination of LTE or LTE-A and 5G, etc.) for application.

[0407] The phrase “based on” used in the present disclosure does not mean “based only on” unless otherwise explicitly stated. In other words, the phrase “based on” means both “based only on” and “based at least on”.

[0408] Any reference to an element using the designations "first", "second", etc. used in this disclosure does not fully define the amount or order of these elements. These designations can 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 mean that only two elements can be used or that the first element must precede the second element in some form.

[0409] The term "determining" as used in this disclosure sometimes includes a variety of operations. For example, "determining" can also be considered as "judging", calculating, computing, processing, deriving, investigating, searching (looking up, searching, inquiry) (e.g., searching in a table, database or other data structure), ascertaining, etc.

[0410] In addition, "judgment (decision)" can also be regarded as a situation of "judgment (decision)" on receiving (for example, receiving information), sending (for example, transmitting) (for example, sending information), input (input), output (output), accessing (for example, accessing data in a memory), etc.

[0411] In addition, "judgment (decision)" can also be regarded as "judgment (decision)" on resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment (decision)" can also be regarded as "judgment (decision)" on certain operations.

[0412] In addition, “judgment (decision)” can also be replaced by “assuming (assuming)”, “expecting (expecting)”, “considering (considering)” and the like.

[0413] The terms "connected" and "coupled" or any variation thereof used in this disclosure mean any direct or indirect connection or combination between two or more elements, including the case where one or more intermediate elements exist between the two elements that are "connected" or "coupled" to each other. The combination or connection between elements may also be physical, logical, or a combination thereof. For example, "connected" may also be replaced by "connected".

[0414] In the present disclosure, when connecting two elements, it is possible to consider using one or more wires, cables, printed electrical connections, etc., and as some non-limiting and non-inclusive examples, using electromagnetic energy with wavelengths in the wireless frequency domain, microwave domain, light (visible light and invisible light) domain, etc., the two elements are "connected" or "combined" with each other.

[0415] In the present disclosure, the term "A is different from B" may also mean "A and B are different from each other". In addition, the term may also mean "A and B are different from C, respectively". The terms "separate" and "combined" may also be interpreted in the same way as "different".

[0416] When the terms “include,” “including,” and variations thereof are used in the present disclosure, these terms, like the term “comprising,” mean inclusive. Furthermore, the term “or” used in the present disclosure does not mean exclusive or.

[0417] In the present disclosure, when an article is added by translation like a, an, and the in English, for example, the present disclosure may also include that the noun following the article is in a plural form.

[0418] The invention involved in the present disclosure has been described in detail above, but it is obvious to those skilled in the art that the invention involved in the present disclosure is not limited to the embodiments described in the present disclosure. The invention involved in the present disclosure can be implemented as a modified and altered mode without departing from the purpose and scope of the invention determined based on the description of the claims. Therefore, the description of the present disclosure is for the purpose of illustrative description and has no restrictive meaning on the invention involved in the present disclosure.

Claims

1. A terminal having: A control unit, using one downlink control information, namely DCI, determines a plurality of transmission precoding matrix indicators, namely a plurality of TPMIs, for repeated transmission of an uplink shared channel PUSCH for a plurality of transmission and reception points, namely a plurality of TRPs; and a transmitting unit, which repeatedly transmits the PUSCH based on the multiple TPMIs, When a specific PUSCH repetition transmission type is set, the control unit applies the plurality of TPMIs to repetition transmission of the PUSCH arranged across a time slot boundary.

2. The terminal according to claim 1, wherein: When the number of TPMIs indicated by the DCI is the same as the number of repeated transmissions of the PUSCH, the control unit applies the TPMI in a sequence from the initial repetition to the final repetition of the PUSCH or from the final repetition to the initial repetition; when the number of TPMIs is less than the number of repeated transmissions of the PUSCH, the control unit applies the TPMI cyclically or continuously for each repetition of the PUSCH based on a specific rule.

3. The terminal according to claim 2, wherein: When the number of TPMIs is 2 and the number of repeated transmissions of the PUSCH is 4, the control unit applies the first TPMI for the first and third repetitions of the PUSCH and the second TPMI for the second and fourth repetitions of the PUSCH, or applies the first TPMI for the first and second repetitions of the PUSCH and the second TPMI for the third and fourth repetitions of the PUSCH.

4. The terminal according to claim 1, wherein: The control unit determines the plurality of TPMIs based on a plurality of DCIs detected for each control resource set CORESET pool index.

5. The terminal according to claim 1, wherein: The DCI includes: a first TPMI field for indicating a first TPMI among the plurality of TPMIs, and a second TPMI field for indicating a second TPMI among the plurality of TPMIs.

6. A wireless communication method of a terminal, comprising: The step of determining multiple transmission precoding matrix indicators (TPMIs) for repeated transmission of an uplink shared channel PUSCH to multiple transmission and reception points (TRPs) using one downlink control information (DCI); and When a specific PUSCH repetition transmission type is set, applying the multiple TPMIs to the repetition transmission of the PUSCH configured across time slot boundaries; The step of repeatedly transmitting the PUSCH arranged across the time slot boundary is performed based on the multiple TPMIs.

7. A base station, comprising: A transmitting unit, which transmits one downlink control information (DCI) to the terminal, wherein the DCI is used to determine multiple transmission precoding matrix indicators (TPMIs) for repeated transmission of an uplink shared channel PUSCH for multiple transmission and reception points (TRPs); and a receiving unit, receiving repeated transmission of the PUSCH transmitted by the terminal based on the plurality of TPMIs, When a specific PUSCH repetition transmission type is set for the terminal, the receiving unit receives repetition transmission of the PUSCH arranged across a slot boundary to which the plurality of TPMIs are applied.

8. A system having a terminal and a base station, The terminal has: A control unit, using one downlink control information, namely DCI, determines a plurality of transmission precoding matrix indicators, namely a plurality of TPMIs, for repeated transmission of an uplink shared channel PUSCH for a plurality of transmission and reception points, namely a plurality of TRPs; and a transmitting unit, which repeatedly transmits the PUSCH based on the multiple TPMIs, When a specific PUSCH repetition transmission type is set, the control unit applies the multiple TPMIs to the repetition transmission of the PUSCH configured across time slot boundaries, The base station has: A sending unit, sending the DCI to the terminal; and The receiving unit receives the repeated transmission of the PUSCH configured across the time slot boundary.

Images