Terminal, wireless communication method, base station and system

The terminal and wireless communication method address the challenge of controlling UL transmission over multiple TRPs by using DCI to manage TPMIs for PUSCH repetitions, enhancing throughput and quality in NR systems.

JP7578695B2Active Publication Date: 2024-11-06NTT DOCOMO INC
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
JP2022539987
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2020-07-31
Publication Date
2024-11-06
Estimated Expiration
2040-07-31

AI Technical Summary

Technical Problem

Existing NR specifications do not adequately address how to control uplink (UL) transmission over multiple transmission/reception points (TRPs), which can lead to decreased throughput and deteriorated communication quality.

Method used

A terminal and wireless communication method that uses downlink control information (DCI) to determine Transmitted Precoding Matrix Indicators (TPMI) for repeated Physical Uplink Shared Channel (PUSCH) transmissions across multiple TRPs, applying these TPMIs across slot boundaries to manage UL transmission effectively.

Benefits of technology

Enables appropriate control of UL transmission over multiple TRPs, improving throughput and communication quality by optimizing PUSCH repetitions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007578695000001
    Figure 0007578695000001
  • Figure 0007578695000002
    Figure 0007578695000002
  • Figure 0007578695000003
    Figure 0007578695000003
Patent Text Reader

Abstract

A terminal according to one embodiment of this disclosure includes: a reception unit that receives information relating to the correspondence relationship between spatial relationship information and a value of a Sounding Reference Signal (SRS) Resource Indicator (SRI) field of detected Downlink Control Information (DCI), for each COntrol REsource SET (CORESET) pool index; and a control unit that, in the determination of spatial relationship information for a Physical Uplink Shared Channel (PUSCH) based on the DCI detected for a CORESET of a given CORESET pool index, determines the spatial relationship information for the PUSCH by referencing the correspondence relationship for the CORESET pool index. According to this embodiment of the present disclosure, uplink transmissions can be appropriately controlled even when multiple TRPs are used.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

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

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

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

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

[0005] In 3GPP Rel.15, repeated transmission is supported for a UL data channel (e.g., an uplink shared channel (Physical Uplink Shared Channel (PUSCH))). The UE controls the transmission of PUSCH over multiple slots (e.g., K consecutive slots) based on a repetition factor K set by the network (e.g., a base station). In other words, when repeated transmission is performed, each PUSCH is transmitted in a different slot (e.g., slot unit).

[0006] On the other hand, in Rel.16 and later, when PUSCH is repeatedly transmitted, it is considered to transmit multiple PUSCHs within one slot. In other words, each PUSCH is transmitted in units shorter than a slot (for example, in units of subslots or minislots).

[0007] In addition, in NR, communications using one or multiple transmission / reception points (TRP) (multi-TRP) are being considered.

[0008] However, in the NR specifications up to now, there has been no sufficient study on how to control the repeated transmission of PUSCH in multi-TRP. In addition, not limited to repeated transmission, a method of appropriately performing UL transmission for multi-TRP has not yet been studied. If UL transmission across multi-TRP is not performed appropriately, there is a risk of a decrease in throughput or deterioration of communication quality.

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

[0010] A terminal according to an embodiment of the present disclosure includes a control unit that determines a plurality of Transmitted Precoding Matrix Indicators (TPMIs) for repeated transmission of an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) for a plurality of transmission / reception points (Transmission / Reception Points (TRPs)) by using one Downlink Control Information (Downlink Control Information (DCI)), and a transmission unit that performs repeated transmission of the PUSCH based on the plurality of TPMIs. The control unit applies the plurality of TPMIs to the repeated transmission of the PUSCH arranged across a slot boundary when a specific PUSCH repeated transmission type is set. do. Effect of the Invention

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

[0012] [Figure 1] 1A and 1B are diagrams illustrating an example of repeated transmission of a PUSCH. [Diagram 2] 2A and 2B are diagrams showing an example of an invalid symbol pattern. [Diagram 3] 3A and 3B are diagrams showing an example of nominal repetitions and actual repetitions. [Figure 4] FIG. 4 is a diagram illustrating an example of repeated transmission of PUSCH in multi-TRP. [Diagram 5] 5A to 5D are diagrams illustrating an example of a correspondence relationship between the value of the SRI field and the SRI for PUCCH repetition according to the first embodiment. [Figure 6] 6A and 6B are diagrams showing an example of parameters applied to each iteration when the number of parameters specified is the same / different than the number of iterations. [Figure 7] FIG. 7 is a diagram illustrating an example of determining the number of iterations based on the number of specific parameters. [Figure 8] 8A and 8B are diagrams illustrating an example of a TPMI instruction according to the first embodiment. [Figure 9] 9A and 9B are diagrams illustrating an example of determining a UL beam for a repetitive PUSCH according to the second embodiment. [Figure 10] 10A and 10B are diagrams illustrating an example of a correspondence relationship of the SRI field for each CORESET pool index according to the third embodiment. [Figure 11] 11A and 11B are diagrams illustrating an example of the configuration of an SRS resource set and an SRS resource according to embodiment 3.1. [Figure 12] FIG. 12 is a diagram illustrating an example of a configuration of an SRS resource set and an SRS resource according to embodiment 3.2. [Figure 13] 13A and 13B are diagrams illustrating an example of the configuration of an SRS resource set and an SRS resource according to embodiment 3.3. [Figure 14] 14A and 14B are diagrams illustrating an example of a MAC CE for updating a spatial relationship of an SRS according to the third embodiment. [Figure 15] FIG. 15 is a diagram illustrating an example of transmission of the same TB based on multiple DCIs according to the fourth embodiment. [Figure 16] FIG. 16 is a diagram illustrating an example of transmission of the same UCI based on multiple DCIs according to the fourth embodiment. [Figure 17] FIG. 17 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 18] FIG. 18 is a diagram illustrating an example of the configuration of a base station according to an embodiment. [Figure 19] FIG. 19 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. [Figure 20] FIG. 20 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] (Repeat sending) In Rel.15, repeated transmission is supported for data transmission. For example, a base station (network (NW), gNB) repeats DL data (e.g., downlink shared channel (PDSCH)) a predetermined number of times. Alternatively, a UE repeats UL data (e.g., uplink shared channel (PUSCH)) a predetermined number of times.

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

[0015] In FIG. 1A, the repetition factor K=4, but the value of K is not limited to this. In addition, the n-th repetition may be called the n-th transmission occasion, etc., and may be identified by a repetition index k (0≦k≦K-1). In addition, FIG. 1A shows repeated transmission of a PUSCH dynamically scheduled by DCI (e.g., a dynamic grant-based PUSCH), but may be applied to repeated transmission of a configuration grant-based PUSCH.

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

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

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

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

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

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

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

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

[0024] In FIG. 1B, the repetition factor K=4, but the value of K is not limited to this. In addition, the n-th repetition may be called the n-th transmission occasion, etc., and may be identified by a repetition index k (0≦k≦K-1). In addition, FIG. 1B shows repeated transmission of a PUSCH dynamically scheduled by DCI (e.g., a dynamic grant-based PUSCH), but may be applied to repeated transmission of a configuration grant-based PUSCH.

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

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

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

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

[0029] Either repetitive transmission type A or repetitive transmission type B may be configured in the UE for each DCI format for which the PUSCH is scheduled.

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

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

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

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

[0034] Also, the second higher layer parameter may be used to notify the UE of whether or not a notification field (or additional bit) in the DCI is set. In other words, when the UE is notified of information on an invalid symbol pattern by the first higher layer parameter, the UE may determine whether or not to apply the information on the invalid symbol pattern based on the second higher layer parameter and the DCI.

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

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

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

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

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

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

[0041] In the case where DL symbols (or invalid symbols) are included in symbols other than both ends of the assigned symbols of a certain PUSCH, PUSCH transmission may be performed using symbols other than the DL symbol portion. In this case, the PUSCH may be divided (or segmented).

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

[0043] Note that the repetitive transmission before considering DL symbols, invalid symbols, or slot boundaries (FIG. 3A) may be called nominal repetitions. The repetitive transmission after considering DL symbols, invalid symbols, or slot boundaries (FIG. 3B) may be called actual repetitions.

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

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

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

[0047] The SRS resource set information may include an SRS resource set ID (SRS-ResourceSetId), a list of SRS resource IDs (SRS-ResourceId) used in the resource set, an SRS resource type (e.g., Periodic SRS, Semi-Persistent SRS, or Aperiodic SRS), and information on SRS usage.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0061] For the above-mentioned repetitive transmission type A and repetitive transmission type B PUSCH transmission, if it can be transmitted over the M-TRP, a significant improvement in performance can be expected compared to single PUSCH transmission. However, there has been little progress in studying how to control the PUSCH repetitive transmission over the M-TRP. There has been little progress in studying a method for appropriately performing UL transmission (PUSCH, PUCCH, etc.) on the M-TRP, not limited to the repetitive transmission. If UL transmission over the M-TRP is not performed appropriately, there is a risk of a decrease in throughput or deterioration of communication quality.

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

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

[0064] In the present disclosure, "A / B" may mean "at least one of A and B."

[0065] In the present disclosure, terms such as activate, deactivate, indicate, select, configure, update, and determine may be interchangeable. Additionally, terms such as sequence, list, set, group, and set may be interchangeable.

[0066] In the present disclosure, panel, beam, panel group, beam group, Uplink (UL) transmitting entity, TRP, spatial relationship information (SRI), spatial relationship, control resource set (COntrol REsource SET (CORESET)), Physical Downlink Shared Channel (PDSCH), codeword, base station, a specific antenna port (e.g., a DeModulation Reference Signal (DMRS) port), a specific antenna port group (e.g., a DMRS port group), a specific group (e.g., a Code Division Multiplexing (CDM) group, a specific reference signal group, a CORESET group), a specific resource (e.g., a specific reference signal resource), a specific resource set (e.g., a specific reference signal resource set), a CORESET pool, a PUCCH group (PUCCH resource group), spatial relationship group, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, etc. may be read as interchangeable.

[0067] Note that for a single DCI, the i-th TRP (TRP#i) may refer to the i-th TCI state, the i-th CDM group, etc. (i is an integer).

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

[0069] The panel may 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 group-based beam reporting.

[0070] In addition, a panel identifier (ID) and a panel may be interchangeable. That is, a TRP ID and a TRP, a CORESET group ID and a CORESET group, etc. may be interchangeable.

[0071] In the present disclosure, the terms index, ID, indicator, and resource ID may be interchangeable. In the present disclosure, the terms list, group, cluster, and subset may be interchangeable.

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

[0073] Furthermore, the SRS resource set in the following embodiments may be interpreted as an SRS resource set whose purpose is a codebook or a non-codebook, or may be interpreted as an SRS resource set whose purpose is another purpose.

[0074] (Wireless communication method) <First embodiment> In the first embodiment, the UE determines certain parameters for multiple PUSCH transmission opportunities of a recurring PUSCH based on one DCI.

[0075] The particular parameter may correspond to at least one of the following parameters: ·TPMI, UL beam parameters (e.g. SRI, spatial relationship, UL TCI state), Transmit Power Control (TPC) related parameters (e.g. TPC command, α, P0, closed loop power control state, Pathloss Reference Signal (PL-RS)).

[0076] The UE may determine that the size of the DCI field indicating the specific parameter is the same as the size of the DCI field indicating the same parameter in Rel.15 / 16 NR, or may determine that the size is M times the size of the DCI field indicating the same parameter in Rel.15 / 16 NR. For example, when M-TRP repeat transmission (or extension of the DCI field indicating the specific parameter) is configured by higher layer signaling, the UE may determine that the size of the DCI field indicating the specific parameter is M times the size of the DCI field indicating the same parameter in Rel.15 / 16 NR.

[0077] The value of M may be specified in advance by a specification, may be set in the UE by higher layer signaling, or may be determined based on the UE capabilities. M may be replaced with the number of TRPs, the number of SRIs, the number of TPMIs, the number of TPC-related parameters, etc.

[0078] In the first embodiment, the UE may be configured / instructed to transmit a repetitive PUSCH with a repetition count of K to a plurality of (different) TRPs. The repetition count K may be configured by RRC or may be instructed by MAC CE / DCI.

[0079] The RV sequence may be fixed (using the same RV) or may be rotated over the K iterations.

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

[0081] The repetitive PUSCH may be transmitted based on at least one of a dynamic grant and a configuration grant. Note that these contents may be similar to other embodiments of the present disclosure that use the repetitive PUSCH.

[0082] With reference to Figures 5A-5D, the DCI field indicating the above specific parameters will be described. Each example shows an example in which the SRI of the PUSCH is repeatedly specified by the SRI field, but other parameters such as TPMI and TPC related parameters can be interpreted in the same way. Each example shows an example in which codebook-based PUSCH transmission is configured in the UE, but non-codebook-based PUSCH transmission can be understood in the same way.

[0083] 5A-5D are diagrams showing an example of a correspondence relationship between values ​​of the SRI field and SRI for PUCCH repetition according to the first embodiment. In each example, SRI#X_i, SRI#Y_i (where i is a number), etc. may be set / activated / indicated by higher layer signaling.

[0084] 5A shows the above-mentioned correspondence relationship when specifying an SRI corresponding to a Rel.15 NR usage=codebook. A value of a certain SRI field corresponds to one SRI.

[0085] FIG. 5B shows the above-mentioned correspondence relationship in the first embodiment when the SRI field is configured with 2 bits, which is twice the number of bits in Rel. 15 NR. A certain SRI field value corresponds to two SRIs. PUSCH#i (i-th PUSCH) (i is an integer) may mean the SRI corresponding to the i-th TRP, or may mean the SRI corresponding to the i-th repetition. PUSCH#i may be read as the i-th SRI. Note that the present disclosure can also be applied to cases where the third and subsequent PUSCHs are specified.

[0086] Fig. 5C shows the above-mentioned correspondence relationship in the first embodiment when the SRI field is configured with the same number of bits (1 bit) as Rel.15 NR. A certain SRI field value corresponds to two SRIs. Fig. 5C limits the set of SRIs that can be expressed compared to Fig. 5B, but can suppress an increase in the number of DCI bits.

[0087] Fig. 5D shows the above-mentioned correspondence relationship in the first embodiment when the SRI field is configured with the same number of bits (1 bit) as Rel. 15 NR. Fig. 5D differs from Fig. 5C in that PUSCH#1 and PUSCH#2 are not distinguished. In the correspondence relationship in Fig. 5D, all values ​​of SRI#X_i and SRI#Y_i may always be notified, or some values ​​may not be notified (that is, there may be an SRI field value corresponding to one SRI and an SRI field value corresponding to multiple SRIs).

[0088] The above specific set of parameters applied to the repeated transmission may be referred to as a sequence (eg, an SRI sequence, a TPMI sequence, etc.).

[0089] [Repetition count] The number of the specific parameters indicated by the DCI field (two in the example of FIG. 5B) may be the same as or different from the number of repetitions.

[0090] When the number of parameters to be specified is the same as the number of repetitions, the specified parameters may be applied in the order of the first repetition (transmission opportunity) to the last repetition (in other words, in the order of the earliest transmission opportunity). For example, when {SRI#1, SRI#2, SRI#3, SRI#4} are specified for four repetitions, the UE may assign SRI#1, SRI#2, SRI#3, SRI#4 to the first to fourth repetitions (PUSCH#1-#4), respectively (FIG. 6A). Conversely, the specified parameters may be applied in the order of the latest transmission opportunity.

[0091] If the number of indicated parameters is smaller than the number of repetitions, the indicated parameters may be applied to each repetition based on a certain rule. For example, if {SRI#1, SRI#2} is indicated for 4 repetitions, the UE may assign SRI#1, SRI#2, SRI#1, and SRI#2 to the first to fourth repetitions (PUSCH#1-#4), respectively (FIG. 6B), or may assign SRI#1, SRI#1, SRI#2, and SRI#2, respectively.

[0092] If the number of indicated parameters is greater than the number of repetitions, the indicated parameters may be applied to each repetition according to a certain rule. For example, if {SRI#1, SRI#2, SRI#3, SRI#4} is indicated for two repetitions, the UE may assign SRI#1 and SRI#2 to the first and second repetitions, respectively, or may assign SRI#3 and SRI#4 to the second repetitions, respectively.

[0093] The UE does not need to assume that the number of the specific parameters indicated by the DCI field is different from the number of repetitions, which can reduce the complexity of the UE implementation.

[0094] The UE may determine the number of repetitions based on the number of the specific parameters indicated by the DCI field. Figure 7 is a diagram showing an example of determining the number of repetitions 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, the UE may determine that the number of repetitions is 1 when the value of the SRI field = 0 is specified, and that the number of repetitions is 2 when the value of the SRI field = 1 is specified.

[0095] In addition, even if the above-mentioned specific parameters are set / indicated by higher layer signaling rather than DCI, the UE may determine the number of repetitions based on the number of the specific parameters.

[0096] In the first embodiment, the number of repetitions K may be given to the UE in a similar manner to Rel.15 / 16.

[0097] [Higher Layer Signaling Configuration and MAC CE] In order to configure or activate many SRS resources corresponding to the SRI field as in the first embodiment, it is preferable to consider the configuration of higher layer signaling and MAC CE.

[0098] Regarding the higher layer signaling configuration and MAC CE for the i-th PUSCH / SRI in the first embodiment, in the description of the higher layer signaling configuration related to the CORESET pool index and the MAC CE related to the SRS resource set in the third embodiment described later, an aspect in which the CORESET pool index or the SRS resource set ID is replaced with the i-th PUSCH / SRI may be applied.

[0099] For example, in the description of the configuration of higher layer signaling in the third embodiment described later, the CORESET pool indexes = 0 and 1 may be replaced with the first and second PUSCH / SRI, respectively. In the description of the MAC CE in the third embodiment described later, the first and second SRS resource sets may be replaced with the first and second PUSCH / SRI, respectively.

[0100] [TPMI] The above-mentioned TPMI indication for the i-th PUSCH will be described below. In the following, a case where DCI for the first PUSCH and the second PUSCH is indicated to the UE will be described as an example.

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

[0102] The DCI may include a TPMI field for the first PUSCH (TPMI field #1) and a TPMI field for the second PUSCH (TPMI field #2) (FIG. 8A). With this configuration, the TPMI for the first and second PUSCHs can be flexibly specified.

[0103] The DCI may include one TPMI field indicating the TPMI for the first PUSCH and the TPMI for the second PUSCH. This configuration can prevent an increase in the size of the DCI.

[0104] The UE may apply one designated TPMI equally to each PUSCH.

[0105] The UE may apply one designated TPMI to the first PUSCH and determine the TPMI to be applied to the second PUSCH based on a specific rule (for example, using a predetermined conversion formula or randomly). With this configuration, for example, a random precoder can be applied to the second PUSCH.

[0106] The UE may apply one designated TPMI to the first PUSCH and determine a TPMI to be applied to the second PUSCH based on the one designated TPMI. For example, the UE may determine that the TPMI to be applied to the second PUSCH is a value obtained by adding or subtracting an offset value to the one designated TPMI. The offset value may be predefined by a specification, may be configured in the UE by higher layer signaling, may be designated by DCI, or may be determined based on UE capabilities.

[0107] The UE may apply one designated TPMI to the first PUSCH and determine the TPMI to be applied to the second PUSCH based on the configuration of higher layer signaling. This configuration is suitable, for example, when there is no need to change the precoder of the second PUSCH.

[0108] The UE may determine the TPMI to be applied to each PUSCH based on the correspondence between the value of the specified one TPMI field and the TPMI to be applied to the first PUSCH and the second PUSCH. The correspondence may be specified in advance by a specification, may be set in the UE by higher layer signaling, may be specified by DCI, or may be determined based on UE capabilities. According to this configuration, the TPMI of each PUSCH can be appropriately and flexibly indicated while suppressing an increase in the size of the DCI.

[0109] 8B is a diagram showing an example of the correspondence relationship. For example, when the value of the TPMI field is 00, the TPMIs corresponding to the first and second PUSCHs are determined to be TPMI#0 and #1, respectively.

[0110] According to the first embodiment described above, repeated transmission for M-TRP can be appropriately performed based on a single DCI.

[0111] <Second embodiment> In a second embodiment, the UE determines the spatial relationship (UL beam) for the recurring PUSCH based on the active TCI state for a particular downlink channel / downlink reference signal. With this configuration, the preferred beam for DL ​​reception can be commonly used for UL transmission.

[0112] The particular downlink channel / downlink reference signal may be, for example, at least one of a PDSCH, a PDCCH, a DMRS, a CSI-RS, and the like.

[0113] For example, the SRI field included in the DCI that schedules the recurring PUSCH may be mapped to a set of specific TCI states among the active TCI states for the PDSCH, which may be TCI states corresponding to a specific Quasi-Co-Location (QCL) type (e.g., QCL Type D, QCL Type A, etc.).

[0114] The particular set of TCI conditions may correspond to at least one of the following: (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; (B) a set of TCI states corresponding to a minimum of N code points of the TCI field included in the DCI scheduling the PDSCH, where at least one DCI code point indicates two or more active TCI states; (C) A set of TCI states corresponding to the smallest N codepoints of the TCI field included in the DCI that schedules the PDSCH, where each DCI codepoint indicates two or more active TCI states.

[0115] The value of N may be predefined by a specification, may be configured in the UE by higher layer signaling, or may be determined based on UE capabilities, and the minimum (i.e., smallest) N code points may be the maximum (i.e., largest) N code points.

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

[0117] The UE may determine a spatial relationship (UL beam) for the repetitive PUSCH based on one or more TCI states selected by the value of the SRI field from the set of the specific TCI states. With this configuration, the best TCI state can be applied to the repetitive PUSCH as the SRI without additional higher layer control for the PUSCH. This is based on the fact that the M-TRP repetition of the PUSCH and the PDSCH is considered to be a similar use case, and the best TCI state is expected to be set in the TCI state list for the PDSCH.

[0118] 9A and 9B are diagrams showing an example of UL beam determination for a recurring PUSCH according to the second embodiment. The left side of FIG. 9A shows the correspondence between the value of the TCI field of the DCI (e.g., DCI format 1_1) that schedules the PDSCH and the designated TCI state among the active TCI states. For example, TCI field=000 indicates one TCI state (TCI state #0), and TCI field=001 indicates two TCI states (TCI states #0, #1).

[0119] When the above N=2 and (A) or (B) is followed, the specific set of TCI states is a set of TCI states (one is {TCI state #0}, the other is {TCI state #0, #1}) that corresponds to the smallest two code points (000, 001). The right side of Fig. 9A shows an example in which the specific set of TCI states is associated with the values ​​of the SRI field in ascending order. Note that the association between the specific set of TCI states and the values ​​of the SRI field is not limited to this, and may be associated with each other in descending order, for example.

[0120] In the case of the correspondence in Fig. 9A, when the value of the SRI field of the DCI (e.g., DCI format 0_1) that schedules the repetitive PUSCH as in Fig. 9B is specified as 1, the UE applies a beam based on {TCI state #0, #1} to the repetitive PUSCH. Note that, when the number of parameters (the number of SRIs, the number of TCIs) specified is the same as or different from the number of repetitions, the UE may determine which parameter is applied to each repetition in the same manner as described in the first embodiment.

[0121] In addition, the manner of deriving the correspondence relationship of the SRI field from the list of TCI states for the PDSCH as described in Fig. 9A may be applied only to the case of the single DCI-based M-TRP. In other words, when at least one of the code points of the TCI field indicates two or more active TCI states, the manner of deriving the correspondence relationship of the SRI field from the list of TCI states for the PDSCH as described in Fig. 9A may be used.

[0122] If the UE does not / cannot derive the correspondence of the SRI field from the list of TCI states for the PDSCH, the correspondence of the SRI field (e.g., the correspondence between the value of the SRI field and the SRI / UL-TCI) may be predefined in the specifications or may be set by higher layer signaling.

[0123] If the UE does not / cannot derive the correspondence of the SRI field from the list of TCI states for the PDSCH, the UE may assume that no recurring PUSCH over the M-TRP is expected (not configured) and may transmit the recurring PUSCH based on the same SRI as in Rel. 15 / 16.

[0124] In addition, even if the UE can / is able to derive the correspondence of the SRI field from the list of TCI states for the PDSCH, if the correspondence of the SRI field (e.g., the correspondence between the value of the SRI field and the SRI / UL-TCI) is set by higher layer signaling, the UE may follow (or prioritize) the setting of the higher layer signaling.

[0125] According to the second embodiment described above, the transmission beam for the PUSCH can be determined based on a preferable DL beam.

[0126] <Third embodiment> The third embodiment describes a case where multiple DCIs are used for M-TRP. In this case, at least one CORESET having a CORESET pool index (RRC parameter "CORESETPoolIndex") of 1 or more is configured for the UE.

[0127] Note that the third embodiment is not limited to the repetitive PUSCH. When the repetitive PUSCH is used, the following content may be applied in combination with the above-described first and second embodiments.

[0128] In the previous Rel.16 NR specification, the value of the SRI field in the DCI format detected for each CORESET pool index value (for each CORESET) corresponds to the SRI in the same SRS resource set, making it difficult to change the UL beam direction for each CORESET.

[0129] Therefore, in the third embodiment, the SRI (spatial relationship) of the PUSCH for each TRP (for each CORESET pool index) is configured in the UE by higher layer signaling.

[0130] 10A and 10B are diagrams showing an example of a correspondence relationship of SRI fields for each CORESET pool index according to the third embodiment. Fig. 10A shows a correspondence relationship of SRI fields of DCI detected in a CORESET in which a CORESET pool index is set to 0 or a CORESET pool index is not set. Fig. 10B shows a correspondence relationship of SRI fields of DCI detected in a CORESET in which a CORESET pool index is set to 1.

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

[0132] For a PUSCH scheduled via a CORESET with CORESET pool index = 0, the UE determines the SRI by referring to the SRI (SRI#0_0, SRI#0_1) set by higher layer signaling for that CORESET as shown in Figure 10A.

[0133] For a PUSCH scheduled via a CORESET with CORESET pool index = 1, the UE determines the SRI by referring to the SRI (SRI#1_0, SRI#1_1) set for that CORESET by higher layer signaling, as shown in Figure 10B.

[0134] [Higher Layer Signaling Settings] In Rel.15, the number of SRS resource sets for use = codebook (CB) was limited to a maximum of 1, the number of SRS resources included in an SRS resource set for use = codebook was limited to a maximum of 2, the number of SRS resource sets for use = non-codebook (NCB) was limited to a maximum of 1, and the number of SRS resources included in an SRS resource set for use = non-codebook was limited to a maximum of 4.

[0135] For this reason, when setting the SRI for each TRP (for each CORESET pool index) described above, it is necessary to eliminate (or relax) the constraint on the number of SRS resources or the number of SRS resource sets.

[0136] Each of the following embodiments will be described. Embodiment 3.1: The number of SRS resource sets is defined as a maximum of P, and the number of SRS resources per SRS resource set is defined as a maximum of 2. -Embodiment 3.2: The number of SRS resource sets is defined as a maximum of 1, and the number of SRS resources per SRS resource set is defined as a maximum of 2P. · Embodiment 3.3: No restriction on the number of SRS resource sets, and the number of SRS resources per SRS resource set is defined as a maximum of 2P.

[0137] Here, the value of P may correspond to the number of TRPs, or may correspond to the number of different CORESET pool indexes configured in the UE (or the maximum CORESET pool index+1 configured in the UE). For example, when a CORESET with CORESET pool index=1 is configured, P may be 2. Of course, the value of P is not limited to 2.

[0138] In addition, in the embodiments 3.1 to 3.3, unless otherwise specified, the SRS resource set and SRS resources for use=CB will be described on the assumption that P=2, but the SRS resource set and SRS resources for use=NCB or other uses may be interpreted as such. For example, when interpreting 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 per SRS resource set may be interpreted as twice the number of SRS resources for use=CB (for example, 4 in the embodiment 3.1, and 4P in the embodiments 3.2 to 3.3).

[0139] [[Embodiment 3.1]] In embodiment 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 may be explicitly set by higher layer signaling, or the CORESET pool index may be associated with the SRS resource set ID in ascending order of the SRS resource set ID, i.e., 0, 1, .... Note that "from the smallest" in the present disclosure may be read as "from the largest".

[0140] 11A and 11B are diagrams showing an example of the configuration of an SRS resource set and an SRS resource according to embodiment 3.1. Fig. 11A shows an SRS resource associated with an SRS resource set ID=0, and Fig. 11B shows an SRS resource associated with an SRS resource set ID=1.

[0141] Here, SRS#x_y may mean the SRS resource of the y (or y+1)th entry of the SRS resource set ID=x (this also applies to the following drawings). Also, the SRS resource set IDs and SRS resource IDs shown in the drawing are merely examples and are not limited to these values ​​(this also applies to the following drawings).

[0142] The SRS resource set ID=0 may be used to specify the SRI of a CORESET to which the CORESET pool index=0 is set. The SRS resource set ID=1 may be used to specify the SRI of a CORESET to which the CORESET pool index=1 is set.

[0143] In this example, SRI#0_0 and SRI#0_1 shown in FIG. 10A 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.

[0144] Furthermore, SRI#1_0 and SRI#1_1 shown in FIG. 10B 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.

[0145] [[Embodiment 3.2]] In embodiment 3.2, W SRS resources included in one SRS resource set correspond to one TRP (CORESET pool index). The correspondence relationship between the CORESET pool index and the SRS resource ID may be explicitly set by higher layer signaling, or the CORESET pool index may be associated with the SRS resource ID in order of W from the smallest to the largest, with 0, 1, ....

[0146] The value of W may be the number of SRS resources that determines the SRI field size of the DCI, for example, a value obtained by dividing the number of SRS resources in the SRS resource set with usage = CB / NCB by P and applying a floor function or ceiling function to the value.

[0147] Fig. 12 is a diagram showing an example of the configuration of an SRS resource set and an SRS resource according to embodiment 3.2. Fig. 12 shows an SRS resource associated with an SRS resource set ID=0. In this example, the SRS resource set with an SRS resource set ID=0 is associated with 2P=4 SRS resources. In this case, W=2.

[0148] Among the SRS resource set ID=0, the smallest W=2 SRS resources may be used to specify the SRI of the CORESET to which the CORESET pool index=0 is set. Among the SRS resource set ID=0, the next smallest W=2 SRS resources may be used to specify the SRI of the CORESET to which the CORESET pool index=1 is set.

[0149] In this example, SRI#0_0 and SRI#0_1 shown in FIG. 10A 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.

[0150] Furthermore, SRI#1_0 and SRI#1_1 shown in FIG. 10B 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.

[0151] [[Embodiment 3.3]] In embodiment 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 and the SRS resource set ID and the SRS resource ID may be explicitly set by upper layer signaling. In addition, the correspondence may be associated with CORESET pool index=0, 1, ... in ascending order of SRS resource set ID and further in descending order of SRS resource ID for each W pieces.

[0152] The value of W may be the number of SRS resources that determines the SRI field size of the DCI, for example, a value obtained by dividing the number of SRS resources in the SRS resource set with usage = CB / NCB by P and applying a floor function or ceiling function to the value.

[0153] In embodiment 3.3, an SRS resource corresponding to a certain CORESET pool index may be allowed 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.

[0154] 13A and 13B are diagrams showing an example of the configuration of an SRS resource set and an SRS resource according to embodiment 3.3. Fig. 13A shows an SRS resource associated with an SRS resource set ID=0, and Fig. 13B shows an SRS resource associated with an SRS resource set ID=1. In this example, a maximum of 2P=4 SRS resources can be associated with one SRS resource set, but Fig. 13A shows three SRS resources, and Fig. 13B shows one SRS resource. In this example, W=2.

[0155] Of the SRS resource set ID=0, the smallest W=2 SRS resources may be used to specify the SRI of the CORESET to which CORESET pool index=0 is set. Since there is only one remaining SRS resource in the SRS resource set ID=0, a total of W=2 SRS resources, including that SRS resource and one SRS resource in the SRS resource set ID=1, may be used to specify the SRI of the CORESET to which CORESET pool index=1 is set.

[0156] In this example, SRI#0_0 and SRI#0_1 shown in FIG. 10A 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.

[0157] Furthermore, SRI#1_0 and SRI#1_1 shown in FIG. 10B 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.

[0158] [MAC CE] The update of the spatial relationship corresponding to the SRI according to the third embodiment will be described.

[0159] The UE may be activated by the MAC CE with reference signal resources used to derive spatial relationships of SRS resources included in an SRS resource set. Such activation may be referred to as updating (or overriding) spatial relationships (SRIs) corresponding to the SRS resources. In the present disclosure, terms such as activate, deactivate, indicate, select, update, and determine may be interchangeable.

[0160] The UE may assume that for transmission of a given signal / channel (e.g., PUSCH, SRS), the spatial relationship (SRI) activated by the MAC CE as described above applies with respect to the SRS resources specified by the DCI.

[0161] 14A and 14B are diagrams illustrating an example of a MAC CE for updating a spatial relationship of an SRS according to the third embodiment.

[0162] 14A shows an example of a MAC CE that can be used to update the SRS resource level spatial relationship for one SRS resource set. The MAC CE is the Enhanced SP / AP SRS Spatial Relation Indication MAC CE defined in Rel.16 NR.

[0163] The MAC CE may include information indicating activation or deactivation ("A / D" field), a cell ID for identifying a cell including an SRS resource set to be activated, a BWP ID corresponding to a UL bandwidth part (BWP) including an SRS resource set to be activated, a P-SRS resource set ID to be activated, a carrier to be activated ("SUL" field), a reference signal resource ID corresponding to a spatial relationship of SRS resources, etc. The MAC CE may include a serving cell ID, a BWP ID, etc. corresponding to a reference signal resource ID (whether these are included may be indicated by a "C" field). Note that "R" indicates a reserved field.

[0164] The reference signal resource ID for the i-th SRS resource in the SRS resource set is “Resource ID i The reference signal resource ID may be, for example, at least one of a non-zero power CSI-RS resource index, an SSB index, an SRS resource ID, a CORESET ID, and the like.

[0165] F i "Resource ID i " may be used to identify which reference signal (e.g., CSI-RS, SSB, SRS (P-SRS, SP-SRS, A-SRS), CORESET) the "Resource ID" corresponds to. i The reference signal that corresponds to F i and “Resource ID i The determination may be based on a combination with a specific bit of " " itself.

[0166] The MAC CE of FIG. 14A may be applicable to at least one (eg, all) of the SRS resource sets for codebook, non-codebook, beam management, and antenna switching applications.

[0167] Figure 14B shows an example of a MAC CE that can be used to update SRS resource level spatial relationships for multiple SRS resource sets. The MAC CE is similar to Figure 14A, except that it includes multiple configurations similar to Octet (Oct) 2 to 2N+2 in Figure 14A. Each set of octets may specify SRS resource level spatial relationships for different SRS resource sets.

[0168] Although information on two SRS resource sets is included in FIG. 14B, three or more may be included.

[0169] The illustrated X field (listed in Oct 2N+3) may indicate whether more than one SRS resource set spatial relationship indication is included. For example, X=1 may mean that the field exists after this point (e.g., after Oct 2N+4), and X=0 may mean that the field does not exist after this point.

[0170] The X field may be located in Oct 2 (e.g., the position of the R field in the upper left). In this case, if X=1, the X field may mean that a field exists next to the spatial relationship indication of this SRS resource set (e.g., after Oct 2N+3), and if X=0, the X field may mean that no field exists next.

[0171] Also, the X field does not have to be explicitly specified.

[0172] The octets containing the SRS resource set ID fields (e.g., Oct 2N+3, Oct 2) may be omitted. If the UE determines that the MAC CE includes spatial relationship indication information sets that correspond to multiple SRS resource sets, the UE may assume that these information sets are applied in order of decreasing SRS resource set ID.

[0173] Some fields (or octets) for the second SRS resource set may not be included. In this case, it may be determined that the values ​​of the fields that are not included (not notified) are equal to the values ​​previously notified / configured for the second SRS resource set (the values ​​are maintained and not updated). Also, it may be determined that the values ​​of the fields that are not included (not notified) are equal to the values ​​notified / configured for the first SRS resource set in the same MAC CE. With these configurations, it is possible to suppress an increase in overhead of the MAC CE.

[0174] [Supplementary Note on the Third Embodiment] The above-mentioned constraints on the number of SRS resources and the number of SRS resource sets in Rel.15 may be used when at least one of the following conditions is satisfied: any RRC parameters for a specific release (e.g., Rel.17) are not configured in the UE, and a CORESET pool index (different value of CORESET pool index or CORESET pool index=1) is not notified. Otherwise, at least one of the SRS resource numbers and the SRS resource sets numbers in embodiments 3.1-3.3 may be applied.

[0175] Although the third embodiment describes SRI, other parameters such as TPMI, UL beam parameters, TPC-related parameters, etc. may be similarly interpreted. These parameters (or the correspondence between these parameters and DCI fields) may be set / specified / determined for each TRP (CORESET pool index).

[0176] At least one of the third embodiments may be applied only to UEs that have reported or support a particular UE capability.

[0177] The specific UE capabilities may indicate at least one of the following: Whether to support association of SRIs with each CORESET pool (or CORESET pool index); The maximum number of supported CORESET pools (or CORESET pool indexes), The maximum number of SRS resource sets supported (or the maximum number of SRS resource sets for a particular purpose supported), The maximum number of SRS resources supported (or the maximum number of SRS resources of a particular purpose supported).

[0178] According to the third embodiment described above, it is possible to appropriately determine the spatial relationship for the M-TRP based on the multi-DCI.

[0179] <Fourth embodiment> The fourth embodiment describes a case where multiple DCIs are used for the M-TRP. The fourth embodiment is not limited to the repetitive PUSCH.

[0180] Consider the case where DCI1 and DCI2, which schedule PUSCHs, are detected in different CORESETs.

[0181] If DCI1 and DCI2 are associated with the same HARQ process ID (or HARQ process number) and indicate the same New Data Indicator (NDI) field value, and the UE receives DCI2 that schedules another PUSCH before the PUSCH scheduled by DCI1, the UE may transmit the same Transport Block (TB) in all these PUSCHs. In this case, for example, PUSCHs with the same TB can be transmitted (retransmitted, repeatedly transmitted) using different beams at short intervals.

[0182] This operation may be allowed only if DCI1 and DCI2 are found in CORESETs with different CORESET pool indices, or may be allowed regardless of whether the CORESET pool indices are different or not.

[0183] This operation may be allowed only when one or both of DCI1 and DCI2 schedule a repetitive PUSCH, or may be allowed also when both schedule a non-repetitive PUSCH.

[0184] 15 is a diagram illustrating an example of transmission of the same TB based on multiple DCIs according to the fourth embodiment. The illustrated DCI1 and DCI2 are related (e.g., the same) in values ​​of the HARQ process number field, NDI field, etc. In this example, DCI1 schedules a repeating PUSCH (PUSCH#1, #2) using SRI#0. DCI2 schedules a repeating PUSCH (PUSCH#3, #4) using SRI#1.

[0185] The UE detected DCI1 in a CORESET with a CORESET pool index = 0. In addition, the UE detected DCI2 in a CORESET with a CORESET pool index = 1 after receiving DCI1 and before starting transmission of PUSCH #1.

[0186] In this example, the UE transmits the same TB on PUSCH#1-#4, and effectively achieves repeat transmission with more than the original repeat count of 2 by using different SRIs.

[0187] Next, consider a case where DCI1 and DCI2, which each trigger a PUCCH, are detected in different CORESETs. Note that the PUCCH (uplink control information (UCI)) triggered by these DCIs may be, for example, a hybrid automatic repeat reQuest ACKnowledgement (HARQ-ACK) for a PDSCH, an aperiodic CSI report, or the like.

[0188] When DCI1 and DCI2 have a specific DCI field, the UE may transmit the same UCI as that transmitted using the PUCCH triggered by DCI1 using the PUCCH triggered by DCI2. In this case, for example, the PUCCH of the same UCI can be transmitted (retransmitted, repeatedly transmitted) using different beams at short intervals.

[0189] The specific DCI field may be a field that indicates transmission of the same UCI, or may be another field. Also, it may be assumed that the values ​​of the specific DCI field of DCI1 and DCI2 must be the same, or may be different. For example, the specific DCI field may be a TCI field, and the above operation may be permitted when the values ​​of the TCI field of DCI1 and DCI2 are different.

[0190] The above operation may be allowed only if DCI1 and DCI2 are found in CORESETs with different CORESET pool indices, or may be allowed regardless of whether the CORESET pool indices are different or not.

[0191] The above operation may be allowed only if one or both of DCI1 and DCI2 trigger a repetitive PUCCH, or may also be allowed if both trigger a non-repetitive PUCCH.

[0192] The operation may be allowed if the UE receives the DCI 2 that triggers another PUCCH before the PUCCH that DCI 1 triggers. The operation may be allowed if the UE receives the DCI 2 that triggers another PUCCH after the PUCCH that DCI 1 triggers.

[0193] 16 is a diagram illustrating an example of transmission of the same UCI based on multiple DCIs according to the fourth embodiment. The illustrated DCI1 and DCI2 are related (e.g., the same) in the values ​​of certain DCI fields. In this example, DCI1 triggers PUCCH#1 with SRI#0 (spatial relationship#0). DCI2 triggers PUCCH#2 with SRI#1 (spatial relationship#1).

[0194] The UE detects DCI1 in a CORESET with a CORESET pool index = 0. In addition, the UE detects DCI2 in a CORESET with a CORESET pool index = 1 after receiving DCI1 and before starting transmission of PUCCH #1.

[0195] In this example, the UE transmits the same UCI in PUCCH #1-#2, which essentially realizes PUCCH repeated transmission using different SRIs.

[0196] A UE may, for example, send a HARQ-ACK for a PDSCH scheduled by DCI1 on PUCCH#1 and send the same HARQ-ACK on PUCCH#2.

[0197] In addition, the UE may transmit only the UCI of PUCCH #1 in PUCCH #2, or may transmit UCI that includes at least the UCI of PUCCH #1 (for example, UCI whose transmission is triggered by DCI2 in addition to the UCI of PUCCH #1).

[0198] 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 a combination of DCI1 and DCI2.

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

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

[0201] The specific UE capabilities may indicate at least one of the following: Whether to support PUSCH repetition; Whether to support different spatial relationships for PUSCH repetitions; Whether to support PUCCH repetition; Whether to support different spatial relationships for PUCCH repetitions; The number (or maximum) of repetitions or spatial relationships to support.

[0202] Also, at least one of the above-described embodiments may be applied when the UE is configured with specific information related to the above-described embodiments by higher layer signaling (if not configured, for example, the operation of Rel. 15 / 16 is applied). For example, the specific information may be information indicating enabling different spatial relationships for PUSCH repetition, any RRC parameters for a specific release (e.g., Rel. 17), etc.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0247] In addition, the transmission / reception unit 120 may transmit, to the user terminal 20, one piece of Downlink Control Information (DCI) (single DCI) used to determine spatial relationship information for multiple uplink shared channels (Physical Uplink Shared Channels (PUSCHs)).

[0248] The transceiver 120 may receive the multiple PUSCHs transmitted by the user terminal 20 using a spatial domain transmit filter based on the spatial relationship information.

[0249] In addition, the transceiver 120 may transmit, for each control resource set (COntrol REsource SET (CORESET)) pool index, information regarding the correspondence between the value of a sounding reference signal (SRS) resource indicator (SRI) field of detected downlink control information (DCI) and spatial relationship information, to the user terminal 20.

[0250] The control unit 110 assumes that the user terminal 20, when determining spatial relationship information for an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) based on DCI detected in a CORESET corresponding to a certain CORESET pool index, determines the spatial relationship information for the PUSCH by referring to the correspondence for the CORESET pool index, and may receive the multiple PUSCHs transmitted by the user terminal 20 using a spatial domain transmit filter based on the spatial relationship information.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0268] Note that control unit 210 may determine spatial relationship information for a plurality of uplink shared channels (Physical Uplink Shared Channels (PUSCHs)) using one piece of Downlink Control Information (DCI).

[0269] The transceiver 220 may transmit the multiple PUSCHs using a spatial domain transmit filter based on the spatial relationship information.

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

[0271] The control unit 210 may determine the number of the plurality of PUSCHs to be the number of SRIs corresponding to the value of the SRI field.

[0272] The control unit 210 may determine the spatial relationship information based on one or more Sounding Reference Signal (SRS) Resource Indicator (SRI) field values ​​of the DCI from a set of active Transmission Configuration Indication (TCI) states.

[0273] In addition, the transceiver 220 may receive information regarding the correspondence between the value of a sounding reference signal (SRS) resource indicator (SRI) field of detected downlink control information (DCI) and spatial relationship information for each control resource set (COntrol REsource SET (CORESET)) pool index.

[0274] When determining spatial relationship information for an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) based on DCI detected in a CORESET corresponding to a certain CORESET pool index, the control unit 210 may determine the spatial relationship information for the PUSCH by referring to the correspondence relationship for the CORESET pool index.

[0275] The control unit 210 may determine that, when the number of different CORESET pool indexes to be set is P, the number of SRS resource sets for specific purposes to be set is a maximum of P, and the number of SRS resources per SRS resource set is a maximum of two.

[0276] The control unit 210 may determine that, when the number of different CORESET pool indexes to be set is P, the number of SRS resource sets for a specific purpose to be set is a maximum of 1, and the number of SRS resources per SRS resource set is a maximum of 2P.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A control unit that determines a plurality of Transmitted Precoding Matrix Indicators (TPMIs) for repeated transmission of an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) for a plurality of transmission / reception points (Transmission / Reception Points (TRPs)) by using one Downlink Control Information (DCI); A transmission unit that repeatedly transmits the PUSCH based on the plurality of TPMIs, The control unit applies the multiple TPMIs to the repeated transmission of the PUSCH arranged across a slot boundary when a specific PUSCH repeated transmission type is set.

2. The terminal of claim 1, wherein when the number of TPMIs indicated by the DCI is the same as the number of repeated transmissions of the PUSH, the control unit applies the TPMIs in the order of the first repetition to the last repetition of the PUSH or the last repetition to the first repetition, and when the number of TPMIs is smaller than the number of repeated transmissions of the PUSH, the control unit applies the TPMIs in a circular or consecutive manner to each repetition of the PUSH 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 a first TPMI to a first repetition and a third repetition of the PUSCH and applies a second TPMI to a second repetition and a fourth repetition of the PUSCH, or applies a first TPMI to a first repetition and a second repetition of the PUSCH and applies a second TPMI to a third repetition and a fourth repetition 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 (COntrol REsource SET (CORESET)) pool index.

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

6. determining a plurality of Transmitted Precoding Matrix Indicators (TPMIs) for repeated transmission of an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) for a plurality of Transmission / Reception Points (TRPs) using one Downlink Control Information (DCI); When a specific PUSCH repeat transmission type is configured, applying the plurality of TPMIs to the repeat transmission of the PUSCH arranged across a slot boundary; and repeating transmission of the PUSCH arranged across the slot boundary based on the multiple TPMIs.

7. A transmitter that transmits one Downlink Control Information (DCI) to a terminal, the DCI being used to determine a plurality of Transmitted Precoding Matrix Indicators (TPMIs) for repeated transmission of an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) for a plurality of Transmission / Reception Points (TRPs); A receiving unit that receives repeated transmission of the PUSCH transmitted by the terminal based on the plurality of TPMIs, The receiving unit is a base station that receives repeated transmission of the PUSCH arranged across a slot boundary to which the multiple TPMIs are applied when a specific PUSCH repeated transmission type is configured in the terminal.

8. A system having a terminal and a base station, The terminal includes a control unit that determines a plurality of transmitted precoding matrix indicators (TPMIs) for repeated transmission of an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) for a plurality of transmission / reception points (Transmission / Reception Points (TRPs)) using one downlink control information (Downlink Control Information (DCI)); A transmission unit that repeatedly transmits the PUSCH based on the plurality of TPMIs, When a specific PUSCH repeat transmission type is set, the control unit applies the multiple TPMIs to the repeat transmission of the PUSCH arranged across a slot boundary, The base station includes a transmitter that transmits the DCI to the terminal; A system having a receiving unit that receives repeated transmissions of the PUSCH arranged across the slot boundary.

Citation Information

Patent Citations

  • Signaling information transmission method and device, communication node and storage medium

    CN110535614A

  • Method and user equipment for multi-transmission / reception point operations

    WO2021227958A1