Terminals, wireless communication methods, base stations and systems

Abstract

A terminal according to one aspect of the present disclosure comprises: a control unit which determines a sounding reference signal resource indicator (SRI) to apply to the first physical uplink shared channel (PUSCH) among a plurality of PUSCHs and which determines the order of SRIs to apply to each PUSCH; and a transmission unit which transmits the plurality of PUSCHs. An aspect of this disclosure makes it possible to appropriately control repeated PUSCH transmission even when multi-TRP is applied.

Description

Technical Field

[0001] This disclosure relates to a terminal, a wireless communication method, 、 a base station and system in a next-generation mobile communication system.

Background Art

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

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

Prior Art Documents

Non-Patent Documents

[0004]

Non-Patent Document 1

Summary of the Invention

[0005] 3GPP Rel.15 supports repeated transmissions on UL data channels (e.g., Physical Uplink Shared Channels (PUSCH)). The UE controls the transmission of PUSCHs across multiple slots (e.g., K consecutive slots) based on a repeat factor K set by the network (e.g., base station). In other words, when repeated transmissions are performed, each PUSCH is transmitted in a different slot (e.g., per slot).

[0006] On the other hand, in Rel.16 and later, when repeatedly transmitting PUSCH signals, it is being considered to transmit multiple PUSCH signals within a single slot. In other words, each PUSCH signal will be transmitted in units shorter than a slot (for example, in sub-slot units or mini-slot units).

[0007] Furthermore, in Rel.16 and later, dynamic switching between single PUSCH transmissions and repeated PUSCH transmissions is being considered.

[0008] Furthermore, NR is considering communication using one or more transmission / reception points (TRPs) (multi-TRPs).

[0009] However, current NR specifications have not adequately addressed how to control repeated transmissions of PUSCH signals in multi-panel / TRP environments. If repeated transmissions of PUSCH signals in multi-TRP environments are not properly handled, it may lead to reduced throughput or degraded communication quality.

[0010] Therefore, this disclosure provides a terminal and wireless communication method that can appropriately control PUSCH repeated transmission. 、 base station and system One of the objectives is to provide [this]. [Means for solving the problem]

[0011] A terminal according to one aspect of the present disclosure receives downlink control information (DCI) which includes a field indicating whether to transmit a first iteration of a physical uplink shared channel (PUSCH) applying a single sounding reference signal (SRS) resource indicator (SRI) field, or a second iteration of a PUSCH applying multiple SRI fields. Furthermore, the field is a field that is different from both the single SRI field and the multiple SRI fields. The device comprises a receiving unit and a control unit that determines, based on the field, whether to transmit the first repetition or the second repetition, wherein, if the field indicates the second repetition, the control unit determines, based on the field, the SRS resource set and SRI field to be used for the first transmission of the second repetition. [Effects of the Invention]

[0012] According to one aspect of this disclosure, PUSCH repeated transmissions can be appropriately controlled even when multi-TRP is applied. [Brief explanation of the drawing]

[0013] [Figure 1] Figures 1A and 1B show an example of repeated transmission of PUSCH. [Figure 2] Figures 2A and 2B show examples of invalid symbol patterns. [Figure 3] Figures 3A and 3B show examples of nominal repetitions and actual repetitions. [Figure 4] Figure 4 shows an example of repeated transmission of PUSCH in a multi-TRP. [Figure 5] Figures 5A-5C show examples of a single PUSCH transmission, repeated PUSCH transmissions for a single TRP, and repeated PUSCH transmissions for multiple TRPs. [Figure 6] FIG. 6A and FIG. 6B are diagrams illustrating an example of repeated transmission of PUSCH for single and multiple TRPs according to Option 1. [Figure 7] FIG. 7 is a diagram illustrating an example of repeated transmission of PUSCH for a single TRP according to Option 2. [Figure 8] FIG. 8 is a diagram illustrating an example of repeated transmission of PUSCH for multiple TRPs according to Option 2. [Figure 9] FIGS. 9A - 9C are diagrams illustrating an example of the correspondence between multiple SRIs and multiple repeated transmissions. [Figure 10] FIGS. 10A and 10B are diagrams illustrating an example of the order of multiple TRPs. [Figure 11] FIG. 11 is a diagram illustrating an example of the order of multiple SRI fields according to Embodiment 1 - 1. [Figure 12] FIGS. 12A and 12B are diagrams illustrating an example of the order of multiple SRI fields according to Embodiment 1 - 2. [Figure 13] FIG. 13 is a diagram illustrating an example of the order of multiple TRPs according to a modification of the first embodiment. [Figure 14] FIG. 14 is a diagram illustrating an example of a DCI field used for instructing the order of multiple SRI fields according to Embodiment 3 - 1. [Figure 15] FIG. 15 is a diagram illustrating an example of a DCI field used for instructing the order of multiple SRI fields according to Embodiment 3 - 2. [Figure 16] FIG. 16 is a diagram illustrating an example of the correspondence between the TPMI field / TPC command field according to Embodiment 4 - 1 and the repeated transmission of PUSCH. [Figure 17] FIG. 17 is a diagram illustrating an example of the correspondence between the TPMI field / TPC command field according to Embodiment 4 - 2 and the repeated transmission of PUSCH. [Figure 18] FIG. 18 is a diagram illustrating an example of the schematic configuration of a wireless communication system according to an embodiment. [Figure 19] FIG. 19 is a diagram illustrating an example of the configuration of a base station according to an embodiment. [Figure 20] Figure 20 shows an example of the configuration of a user terminal according to one embodiment. [Figure 21] Figure 21 shows an example of the hardware configuration of a base station and a user terminal according to one embodiment. [Modes for carrying out the invention]

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

[0015] Figure 1A shows an example of repeated PUSCH transmission. Figure 1A shows an example in which a predetermined number of repeated PUSCH transmissions are scheduled by a single DCI. The number of repetitions is also called the repetition factor K or aggregation factor K.

[0016] In Figure 1A, the repetition coefficient K=4, but the value of K is not limited to this. Furthermore, the nth repetition may also be called the nth transmission occasion and may be identified by a repetition index k (0≦k≦K-1). Also, while Figure 1A shows repeated transmissions of a dynamically scheduled PUSCH in DCI (e.g., a dynamic grant-based PUSCH), it may also be applied to repeated transmissions of a configured grant-based PUSCH.

[0017] For example, in Figure 1A, the UE receives information indicating the repetition coefficient K (e.g., aggregationFactorUL or aggregationFactorDL) quasi-statically via upper-layer signaling. Here, the upper-layer signaling may be any of the following, or a combination thereof: RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast information, etc.

[0018] MAC signaling may use, for example, MAC control elements (MAC CEs) or MAC Protocol Data Units (MAC PDUs). Broadcast information may also be, for example, Master Information Blocks (MIBs), System Information Blocks (SIBs), or Remaining Minimum System Information (RMSIs).

[0019] The UE controls the receive processing of PDSCH (e.g., at least one of receive, demapping, demodulation, or decoding) or the transmit processing of PUSCH (e.g., transmit, mapping, modulation, or coding) in K consecutive slots based on at least one of the following field values ​​in DCI (or the information indicated by that field value): • Allocation of time domain resources (e.g., starting symbol, number of symbols in each slot, etc.) • Allocation of frequency domain resources (e.g., a predetermined number of resource blocks (RB), a predetermined number of resource block groups (RBG)), • Modulation and Coding Scheme (MCS) Index • Configuration of the Demodulation Reference Signal (DMRS) for Push. • The spatial relation information of PUSCH, or the status of the Transmission Configuration Indication (TCI) or Transmission Configuration Indicator (TCI-state).

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

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

[0022] On the other hand, among the K consecutive slots, the Redundancy Version (RV) applied to the TB based on the same data may be the same, or at least partially different. For example, the RV applied to the TB in the nth slot (transmission opportunity, repetition) may be determined based on the value of a predetermined field in the DCI (e.g., the RV field).

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

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

[0025] In Figure 1B, the repetition coefficient K=4, but the value of K is not limited to this. The nth repetition is also called the nth transmission occasion and may be identified by a repetition index k (0≦k≦K-1). Furthermore, while Figure 1B shows repeated transmissions of a dynamically scheduled PUSCH in DCI (e.g., a dynamic grant-based PUSCH), it may also be applied to repeated transmissions of a configured grant-based PUSCH.

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

[0027] The UE may dynamically receive information indicating the repetition coefficient K (e.g., numberofrepetitions) via downstream control information. The repetition coefficient may be determined based on the value m of a predetermined field in the DCI (e.g., the TDRA field). For example, a table may be supported that defines the correspondence between bit values ​​notified in the DCI and the repetition coefficient K, the starting symbol S, and the number of symbols L.

[0028] The slot-based repetition transmission shown in Figure 1A may be called repetition transmission type A (e.g., PUSCH repetition Type A), and the sub-slot-based repetition transmission shown in Figure 1B may be called repetition transmission type B (e.g., PUSCH repetition Type B).

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

[0030] For each DCI format used to schedule a PUSCH, either recurring transmission type A or recurring transmission type B may be set as the UE.

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

[0032] Furthermore, in Rel.16 and later, dynamic switching between single PUSCH transmissions and repeated PUSCH transmissions is being considered.

[0033] When a higher-layer parameter for time domain allocation of a PUSCH is set for the UE (e.g., push-TimeDomainAllocationListDCI-0-1-r16 or push-TimeDomainAllocationListDCI-0-2-r16), the number of repetitions (e.g., 1, 2, 3, 4, 7, 8, 12, or 16) may be set by a parameter for the number of PUSCH repetitions included in that higher-layer parameter (e.g., numberOfRepetitions-r16). The UE may determine the number of PUSCH repetitions scheduled by the DCI based on the DCI's time domain resource allocation field. When the number of repetitions is set / specified as 1, the UE may make a single PUSCH transmission.

[0034] (Invalid symbol pattern) When applying repeat transmission type B to a PUSCH transmission, it is also being considered to notify the UE of information regarding symbols (or symbol patterns) that cannot be used for PUSCH transmissions. Symbol patterns that cannot be used for PUSCH transmissions may also be called invalid symbol patterns, invalid symbol patterns, etc.

[0035] It is being considered to notify invalid symbol patterns using at least one of upper-layer signaling and DCI. The DCI may be a predetermined DCI format (for example, at least one of DCI formats 0_1 and 0_2).

[0036] For example, the first upper-layer parameter is used to notify the UE of invalid symbol patterns that cannot be used for PUSCH transmission. Alternatively, the DCI may be used to notify the UE whether or not to apply the information regarding the invalid symbol patterns. In this case, a bit field (a field for notifying whether or not to apply the invalid symbol pattern) may be set in the DCI to indicate whether or not to apply the information regarding the invalid symbol patterns.

[0037] Furthermore, the UE may be notified of the presence or absence of notification fields (or additional bits) in the DCI using a second higher-layer parameter. In other words, if the UE is notified of information regarding an invalid symbol pattern by the first higher-layer parameter, it may decide whether or not to apply the information regarding that invalid symbol pattern based on the second higher-layer parameter and the DCI.

[0038] If the first upper layer parameter is not notified or set, the UE may control the transmission of PUSCH without considering invalid symbol patterns. If the first upper layer parameter is notified or set, the UE may determine whether to apply invalid symbol patterns based on the second upper layer parameter and DCI. For example, if the second upper layer parameter instructs the DCI to add an additional bit (or a predetermined field) indicating whether to apply invalid symbol patterns, the UE may determine whether to apply invalid symbol patterns based on that predetermined field.

[0039] The first upper-layer parameter can be any information that notifies of a symbol pattern that is invalid for PUSCH transmission, and may be in the form of a bitmap, for example (see Figure 2A). Figure 2A shows an example where the invalid symbol pattern is defined as a bitmap (1-D bitmap) in the time domain. Based on the information about the invalid symbol pattern, the UE may determine the resources available for PUSCH transmission in one or more frequency bandwidths (e.g., BWP) (see Figure 2B).

[0040] This example shows how to apply one or a common invalid symbol pattern to multiple BWPs, but different invalid symbol patterns may be set or applied to each BWP.

[0041] (Nominal repetitions / Actual repetitions) When repeat transmission type B is applied and repeated transmission is performed on a sub-slot basis, depending on the repetition coefficient (K) and the data allocation unit, there may be cases where a certain repeat transmission crosses the slot boundary.

[0042] Figure 3A shows an example of applying repeat transmission type B when the repetition coefficient (K) is 4 and the push length (L) is 4. In Figure 3A, a push with k=3 is placed across a slot boundary. In such a case, the push may be divided (or segmented) based on the slot boundary for transmission (see Figure 3B).

[0043] Furthermore, it is conceivable that a slot may contain symbols that cannot be used for PUSCH transmission (e.g., DL symbols or invalid symbols). Figure 3A shows a case where some of the symbols in which k=1 PUSCH is placed contain symbols that cannot be used for that PUSCH transmission (in this case, DL symbols). In such cases, the PUSCH transmission may be performed using symbols excluding the DL symbol (see Figure 3B).

[0044] If a PUSCH assignment symbol includes DL symbols (or invalid symbols) in all symbols except those at the ends, the PUSCH transmission may be performed using the symbols other than the DL symbol portion. In this case, the PUSCH may be split (or segmented).

[0045] Figure 3B shows the case in subslot-based repeat transmission where a PUSCH of k=1 (Rep#2) is split into two by the DL symbol (Rep#2-1 and #2-2), and a PUSCH of k=3 (Rep#4) is split into two by the slot boundary (Rep#4-1 and #4-2).

[0046] Note that repeated transmissions before considering DL symbols, invalid symbols, or slot boundaries (Figure 3A) may be called nominal repetitions. Repeated transmissions that take DL symbols, invalid symbols, or slot boundaries into consideration (Figure 3B) may be called actual repetitions.

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

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

[0049] A single SRS resource set may be associated with a predetermined number of SRS resources (a predetermined number of SRS resources may be grouped together). Each SRS resource may be identified by an SRS Resource Indicator (SRI) or an SRS Resource Identifier.

[0050] 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., one of Periodic SRS, Semi-Persistent SRS, or Aperiodic SRS), and information on the usage of the SRS.

[0051] Here, the SRS resource type may be one of the following: Periodic SRS (P-SRS), Semi-Persistent SRS (SP-SRS), or Aperiodic CSI (A-SRS). The UE may send P-SRS and SP-SRS periodically (or periodically after activation), and A-SRS based on DCI's SRS request.

[0052] Furthermore, the application (RRC parameter "usage", L1 (Layer-1) parameter "SRS-SetUse") may include, for example, beam management, codebook (CB), noncodebook (NCB), antenna switching, etc. SRS for codebook or noncodebook applications may be used to determine the precoder for codebook-based or noncodebook-based PUSCH transmissions based on SRI.

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

[0054] SRS resource information may include SRS resource ID (SRS-ResourceId), number of SRS ports, SRS port number, transmit comb, SRS resource mapping (e.g., time and / or frequency resource location, resource offset, resource period, number of repetitions, number of SRS symbols, SRS bandwidth, etc.), hopping-related information, SRS resource type, sequence ID, SRS spatial relationship information, etc.

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

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

[0057] In this disclosure, the terms SSB index, SSB resource ID, and SSB Resource Indicator (SSBRI) may be interpreted interchangeably. Similarly, the terms CSI-RS index, CSI-RS resource ID, and CSI-RS Resource Indicator (CRI) may be interpreted interchangeably. Furthermore, the terms SRS index, SRS resource ID, and SRI may be interpreted interchangeably.

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

[0059] If a UE configures spatial relationship information regarding an SSB or CSI-RS and an SRS resource, it may transmit the SRS resource using the same spatial domain filter (spatial domain transmit filter) as the spatial domain filter (spatial domain receive filter) used 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.

[0060] If a UE sets spatial relationship information regarding a target SRS resource and another SRS (reference SRS), it may transmit the target SRS resource using the same spatial domain filter (spatial domain transmit filter) as the one used for transmitting the reference SRS. In other words, in this case, the UE may assume that the UE transmit beam for the reference SRS and the UE transmit beam for the target SRS are the same.

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

[0062] When using codebook-based transmission for PUSCH, the UE may configure two SRS resources per SRS resource set via RRC, 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 configure four SRS resources per SRS resource set via RRC, and one of the four SRS resources may be indicated by DCI (2-bit SRI field).

[0063] (TPMI and transmission rank) In Rel.16, it is being considered that for codebook-based PUSCH transmissions, the Transmitted Precoding Matrix Indicator (TPMI) and transmit rank will be specified by specific fields (e.g., precoding information and layer number field) included in the downlink control information (e.g., DCI format 0_1).

[0064] The precoder used by the UE for codebook-based push transmission may be selected from uplink codebooks having the same number of antenna ports as the value set by the higher-layer parameter (e.g., nrofSRS-Ports) configured for the SRS resource.

[0065] The size (number of bits) of the particular field is variable, depending on the number of antenna ports for PUSCH (e.g., the number of ports indicated by nrofSRS-Ports above) and several higher-layer parameters.

[0066] The relevant field may be 0 bits if a higher-layer parameter (e.g., txConfig) set for the UE is set to nonCodebook.

[0067] Furthermore, this particular field may be 0 bits if a higher-layer parameter (e.g., txConfig) set for the UE is set in the codebook for a single antenna port.

[0068] Furthermore, the specific field may have a bit length of 2 to 6 bits for each of the four antenna ports, based on at least one of the following: a higher-layer parameter set for the UE (e.g., txConfig) is set in the codebook, and the presence or absence of a transform precoder (enabled or disabled).

[0069] Furthermore, the specific field may have a bit length of 1 to 4 bits for two antenna ports, based on at least one of the following: a higher-layer parameter set for the UE (e.g., txConfig) is set in the codebook, and the presence or absence of a transform precoder (enabled or disabled).

[0070] The other higher-layer parameter may be at least one of the following: a parameter for specifying the UL's full-power transmission mode (e.g., ul-FullPowerTransmission), a parameter indicating the maximum transmission rank of the UL (e.g., maxRank), a parameter indicating a subset of a certain precoding matrix indicator (PMI) (e.g., codebookSubset), or a parameter for specifying a transform precoder (e.g., transformPrecoder).

[0071] (Multi-TRP) In NR, it is being considered that one or more transmission / reception points (TRPs) (multi-TRPs) will use one or more panels (multi-panels) to perform DL transmissions to the UE. Furthermore, it is being considered that the UE will perform UL transmissions to one or more TRPs (see Figure 4).

[0072] Multiple TRPs may correspond to the same cell identifier (Cell Identifier (ID)) or to different cell IDs. This cell ID may be a physical cell ID or a virtual cell ID.

[0073] Figures 5A-5C illustrate examples of a single push transmission, repeated push transmissions for a single TRP, and repeated push transmissions for multiple TRPs. In the example shown in Figure 5A, the UE performs a single push transmission using a first SRI determined from a first SRI field. In the example shown in Figure 5B, the UE performs repeated push transmissions for a single TRP using a first SRI determined from a first SRI field. In the example shown in Figure 5C, the UE performs repeated push transmissions for multiple TRPs using a first SRI determined from a first SRI field and a second SRI determined from a second SRI field.

[0074] In NRs Rel.16 and later, dynamic switching between repeated PUSCH transmissions for a single PUSCH signal / single TRP and repeated PUSCH transmissions for multiple (e.g., two) TRPs is being considered.

[0075] When performing dynamic switching between a single PUSCH transmission / repeated PUSCH transmission for a single TRP and repeated PUSCH transmission for multiple (e.g., two) TRPs, at least one of the following options 1 and 2 may be applied.

[0076] [Option 1] Of the multiple SRI fields instructed / notified to the UE, each SRI field contains an "inapplicable code point." The UE decides whether to repeatedly send for a single TRP or multiple TRPs, based on whether an inapplicable code point is indicated for each of the multiple SRI fields.

[0077] More specifically, when an "inapplicable code point" is indicated in any of the multiple SRI fields, the UE decides to perform a single PUSCH transmission / repeated PUSCH transmissions for a single TRP. Also, when the application of multiple valid SRS resources (SRIs) is indicated in each of the multiple SRI fields, the UE decides to perform repeated PUSCH transmissions for multiple TRPs.

[0078] Figure 6A shows an example of repeated PUSCH transmissions for a single TRP related to Option 1. In Figure 6A, two SRI fields (SRI field #1 and SRI field #2) are set for the UE. In the example shown in Figure 6A, the number of repetitions specified for the UE is 4.

[0079] In the example shown in Figure 6A, the UE is instructed to select SRS resource #1 from SRI field #1 and an SRI marked "Not applied" from SRI field #2. Since the SRS resource indicated in one SRI field is an SRI that is not applied, the UE decides to repeatedly send PUSCH messages for a single TRP using SRS resource #1.

[0080] Figure 6B shows an example of repeated PUSCH transmissions for multiple TRPs related to Option 1. In Figure 6B, two SRI fields (SRI field #1 and SRI field #2) are set for the UE. In the example shown in Figure 6B, the number of repetitions specified for the UE is 4.

[0081] In the example shown in Figure 6B, the UE is instructed to select SRS resource #1 from SRI field #1 and SRS resource #3 from SRI field #2. Since the SRS resources indicated in each of the two SRI fields are not SRIs that are not applied, the UE decides to repeatedly send PUSCH signals across multiple TRPs.

[0082] [Option 2] The UE decides whether to perform repeated transmissions for a single TRP or multiple TRPs based on a specific field included in the DCI. This specific field may be a field indicating TPMI in a codebook-based PUSCH (TPMI field), a field indicating SRI in a non-codebook-based PUSCH (SRI field), or a new specific field defined in Rel. 17 or later.

[0083] More specifically, if a particular field included in the DCI indicates that one of several (e.g., two) SRI fields (e.g., a first SRI field, a second SRI field) should be applied, either the first SRI field or the second SRI field, the UE may decide to repeatedly send PUSCH in a single TRP.

[0084] Furthermore, if a specific field included in the DCI indicates that both of several SRI fields should be applied, the UE will decide to repeatedly send PUSCH across multiple TRPs.

[0085] Figure 7 shows an example of repeated PUSCH transmissions for a single TRP under Option 2. In Figure 7, two SRI fields (SRI field #1 and SRI field #2) are set for the UE. In the example shown in Figure 7, the number of repetitions specified for the UE is 4.

[0086] In the example shown in Figure 7, the UE is instructed to apply SRI field #1 and the corresponding SRS resource / SRS resource set based on the fields included in the DCI. The UE is also instructed to select SRS resource #1 from SRI field #1 and SRS resource #3 from SRI field #2. Based on the fields in the DCI, the UE decides to repeatedly send PUSCH messages for a single TRP using SRS resource #1.

[0087] Figure 8 shows an example of repeated PUSCH transmissions for multiple TRPs related to Option 2. In Figure 8, two SRI fields (SRI field #1 and SRI field #2) are set for the UE. In the example shown in Figure 8, the number of repetitions specified for the UE is 4.

[0088] In the example shown in Figure 8, the UE is instructed to apply SRI field #1 and SRI field #2 based on the fields included in the DCI. The UE is also instructed to select SRS resource #1 from SRI field #1 and SRS resource #3 from SRI field #2. Based on the fields in the DCI, the UE decides to repeatedly send PUSCH messages to multiple TRPs using SRS resource #1 and SRS resource #3.

[0089] (Mapping pattern) When a UE decides to repeatedly send PUSCH to multiple TRPs, it may determine that multiple SRIs and multiple repeated transmissions correspond to each other based on a specific rule. This rule may be called a mapping pattern, mapping rule, correspondence pattern, correspondence relationship, etc.

[0090] For example, when a UE decides to repeatedly send PUSCH signals to multiple TRPs, it may determine that multiple SRIs correspond cyclically to multiple repeated transmissions. This correspondence may be called a cyclic mapping, cyclic pattern, or cyclic correspondence.

[0091] Figure 9A shows an example of a cyclical correspondence between multiple SRIs and multiple repeated transmissions. In Figure 9A, the UE is specified as having 6 repetitions and performs repeated PUSCH transmissions using the first SRI and the second SRI. In the example shown in Figure 9A, the UE cyclically performs PUSCH transmissions using the first SRI and PUSCH transmissions using the second SRI. For example, the first SRI may be applied to odd-numbered repetitions (repetitions #1, #3, #5), and the second SRI may be applied to even-numbered repetitions (repetitions #0, #2, #4).

[0092] For example, when a UE decides to repeatedly send a PUSCH in multiple TRPs, it may determine that multiple SRIs correspond sequentially to multiple repeated transmissions in a specific number (e.g., two). This correspondence may be called a sequential mapping, sequential pattern, sequential correspondence, etc.

[0093] Figure 9B shows an example of a sequential correspondence between multiple SRIs and multiple repeated transmissions. In Figure 9B, the UE is specified as having 6 repetitions and performs repeated PUSCH transmissions using the first SRI and the second SRI. In the example shown in Figure 9B, the UE sequentially performs two PUSCH transmissions using the first SRI and two PUSCH transmissions using the second SRI.

[0094] For example, when a UE decides to repeatedly transmit a PUSCH in multiple TRPs, multiple SRIs and multiple repeated transmissions may correspond sequentially such that the number of repetitions roughly matches the number of SRIs divided by the number of SRIs. If the number of SRIs is 2, this correspondence may be called a half-half pattern (mapping).

[0095] Figure 9C shows an example of using a half-half pattern to correspond multiple SRIs with multiple repeated transmissions. In Figure 9C, the UE is specified as having 6 repetitions and performs repeated PUSCH transmissions using the first SRI and the second SRI. In the example shown in Figure 9C, the UE performs PUSCH transmissions using the first SRI in the first three PUSCH transmission opportunities and uses the second SRI in the subsequent three PUSCH transmission opportunities.

[0096] Furthermore, one of the multiple mapping patterns described using Figures 9A-9C above may be defined in the specification. Alternatively, if multiple mapping patterns are defined in the specification, the UE may be configured / instructed to apply a mapping pattern using at least one of the upper-layer signaling and physical-layer signaling. The UE may also report to the NW its capability regarding which of the multiple mapping patterns it supports.

[0097] Note that the number of PUSCH transmission repetitions, SRI count, etc. shown in Figures 9A to 9C are merely examples and are not limited to these. Also, the number of PUSCH transmission repetitions, number of code points / code point names for each field, number of bits, SRI count, etc. in the following diagrams are merely examples and are not limited to these examples.

[0098] Incidentally, previous NR specifications have not adequately considered how to control the repeated transmission of PUSCH signals in multi-panel / TRP (when multi-panel / TRP is configured). If repeated transmission of PUSCH signals in multi-TRP is not properly handled, there is a risk of reduced throughput or deterioration of communication quality.

[0099] More specifically, in cases where options 1 and 2 above apply, there is insufficient consideration of whether or not to dynamically switch (change) the order of multiple (e.g., two) TRPs used (which may be referred to as a multiple TRP order in this disclosure), and how to dynamically switch the order of multiple TRPs used. If these considerations are not sufficiently carried out and repeated transmission of PUSCH in a multi-TRP configuration is not performed properly, there is a risk of reduced throughput or deterioration of communication quality.

[0100] For example, there are two possible scenarios: one where a UL transmission is performed first for TRP#1, as shown in Figure 10A, and then for TRP#2; and another where a UL transmission is performed first for TRP#2, as shown in Figure 10B. Note that while Figures 10A and 10B show cyclic mapping, sequential mapping or a half-half pattern are also acceptable.

[0101] Therefore, the inventors devised a control method for repeated PUSCH transmission that solves the above problem.

[0102] The embodiments of this disclosure will be described in detail below with reference to the drawings. Each wireless communication method according to the embodiments may be applied individually or in combination.

[0103] In this disclosure, the terms port, panel, beam, Uplink (UL) transmit entity, TRP, spatial relation information (SRI), spatial relation, control resource set (CORESET), PDSCH, codeword, base station, predetermined antenna port (e.g., demodulation reference signal (DMRS) port), predetermined antenna port group (e.g., DMRS port group), predetermined group (e.g., code division multiplexing (CDM) group, predetermined reference signal group, CORESET group, panel group, beam group, spatial relation group, PUCCH group), and CORESET pool may be interpreted as interchangeable. Also, panel identifier (ID) and panel may be interpreted as interchangeable. TRP ID and TRP may be interpreted as interchangeable.

[0104] In this disclosure, the terms index, ID, indicator, and resource ID may be interpreted as interchangeable.

[0105] In this disclosure, “A / B” may mean “at least one of A and B.” Also, in this disclosure, “A / B / C” may mean “at least one of A, B, and C.”

[0106] In this disclosure, lists, groups, clusters, subsets, etc., may be interpreted interchangeably. In this disclosure, spatial relation information (SRI), SRS resource indicators (SRI, or SRI fields), SRS resources, SRS resource sets, precoders, etc., may be interpreted interchangeably.

[0107] In this disclosure, spatial relation information (SRI), combinations of SRI, SRI for codebook-based transmission, combinations of non-codebook-based SRI, spatialRelationInfo, UL TCI, TCI status, Unified TCI, QCL, etc., may be interpreted interchangeably.

[0108] In this disclosure, the first TRP and the second TRP may be interpreted as the first PUSCH and the second PUSCH, the first PUSCH transmission opportunity and the second PUSCH transmission opportunity, the first SRI and the second SRI, and so on.

[0109] In the following embodiments, repeated transmission of PUSCH to multiple TRPs may be interpreted as PUSCH across multiple TRPs, repeated PUSCH across multiple TRPs, simply repeated PUSCH, repeated transmission, multiple PUSCH transmissions, etc. Also, a single PUSCH transmission to a single TRP may be simply called a single PUSCH transmission, a PUSCH transmission at a single TRP, etc.

[0110] In this disclosure, repeated transmission of a PUSCH for a single TRP may mean repeated transmission of multiple PUSCHs transmitted using the same SRI / beam / precoder.

[0111] In this disclosure, repeated transmission of PUSCH to multiple TRPs may mean repeated transmission of multiple PUSCH transmitted using multiple different SRI / beam / precoders. Such repeated transmissions and multiple SRI / beam / precoders may correspond cyclically, sequentially in specific numbers, or using a half-half pattern (mapping), as detailed in the mapping patterns described above.

[0112] In each embodiment of this disclosure, we will describe examples of push transmissions to multiple TRPs using a single DCI and codebook (CB)-based push transmissions, but these may also be applied to non-codebook (NCB)-based push transmissions, and the push transmissions to which each embodiment can be applied are not limited to these. When each embodiment of this disclosure is applied to a non-codebook-based push transmission, one or more SRS resources (SRIs) may be indicated to the UE by each SRI field. Furthermore, common or different embodiments may be applied to codebook-based push transmissions and non-codebook-based push transmissions.

[0113] Furthermore, while the embodiments described in this disclosure primarily describe cases where there are two TRPs, SRIs, etc., these numbers may be three or more. Also, the term "dynamic switch" in this disclosure may mean "a switch that uses at least one of upper-layer signaling and physical-layer signaling." In addition, the term "switch" in this disclosure may be interpreted as switching, change, changing, applying, etc.

[0114] Furthermore, in this disclosure, the term "inapplicable code point" may be interpreted as "unapplicable code point," "reserved code point," "not applied code point," etc. For example, an inapplicable code point may be a reserved code point in the SRI field in Rel. 16. Also, "Not applied" in this disclosure may be interpreted as "Not Applicable," "Not Available," "N / A," "Not Valid," etc.

[0115] In the following embodiments of this disclosure, SRI will be described, but the instructions for PUSCH's TPMI / TPC commands can also be appropriately applied to each embodiment. In this disclosure, the field that indicates TPMI included in DCI may be called the TPMI field. Also in this disclosure, the field that indicates TPC commands included in DCI may be called the TPC command field.

[0116] Furthermore, each embodiment of the present disclosure can be appropriately applied to the repeated transmission of any UL signal / channel to multiple TRPs, and PUSCH in the present disclosure may be interpreted as any UL signal / channel. For example, each embodiment of the present disclosure can be appropriately applied to the repeated transmission of PUCCH to multiple TRPs, and PUSCH in the present disclosure may be interpreted as PUCCH.

[0117] (Wireless communication method) <First Embodiment> In the first embodiment, dynamic switching (changing) of the order of multiple (e.g., two) TRPs used is not required. In other words, the specification does not need to support dynamic switching of the order of multiple TRPs.

[0118] Embodiment 1-1 In the first embodiment, the UE may assume that a particular SRI field / SRS resource set / TRP is predefined / fixed as the "first beam". This particular SRI field / SRS resource set / TRP may have the smallest / largest / xth (where x is an integer) index, or it may be the first / last / xth SRI field / SRS resource set / TRP.

[0119] In the embodiments described herein, “first beam” may mean the SRI field / SRS resource set / TRP used in the first transmission of a repeated transmission performed by the UE. In the embodiments described herein, the correspondence between repeated transmissions of PUSCH to multiple TRPs and multiple SRI fields / SRS resource sets / TRPs may be cyclic, sequential, or a half-half pattern (mapping), as detailed in the mapping patterns described above.

[0120] Figure 11 shows an example of the order of multiple SRI fields according to Embodiment 1-1. In the example shown in Figure 11, repeated transmission and multiple SRI fields correspond in a cyclic way, and sequentially, they correspond in a specific number (two in this case) in a sequential way.

[0121] In the example shown in Figure 11, the UE assumes that SRI field #1, which has the smallest index, is fixed as the first SRI. In the example of cyclic mapping shown in Figure 11, the UE first makes one PUSCH transmission using SRI field #1, and then one PUSCH transmission using SRI field #2. Thereafter, it alternates between making one PUSCH transmission using SRI field #1 and one PUSCH transmission using SRI field #2. In the example of sequential mapping shown in Figure 11, the UE first makes two PUSCH transmissions using SRI field #1, and then two PUSCH transmissions using SRI field #2.

[0122] Embodiment 1-2 In the first embodiment, the UE may be notified of information about the SRI field / SRS resource set / TRP, which is set as the “first beam,” by higher-layer signaling (e.g., RRC signaling).

[0123] The UE may configure whether the first SRI field / SRS resource set / TRP or the second SRI field / SRS resource set / TRP is the "first beam" via higher-layer signaling (e.g., RRC signaling) (Embodiment 1-2-1). In Embodiment 1-2-1, the UE may be notified of information for configuring the mapping pattern (whether the first SRI field / SRS resource set / TRP or the second SRI field / SRS resource set / TRP is the "first beam") via higher-layer signaling (e.g., RRC information element for mapping pattern configuration).

[0124] The UE may, via upper-layer signaling, determine whether the corresponding SRI field / SRS resource set / TRP is the "first beam" for each SRS resource set of the CB / NCB (e.g., resource sets configured by upper-layer parameters (e.g., SRS-Config)) (Embodiment 1-2-2).

[0125] The UE may determine which SRI field / SRS resource set / TRP is the "first beam" based on the mapping pattern information notified by the RRC information element for mapping pattern setting (Embodiment 1-2-3). In other words, the UE may receive information specifying a mapping pattern that sets the "first beam" to be the first SRI field / SRS resource set / TRP (first mapping pattern information), or information specifying a mapping pattern that sets the "first beam" to be the second SRI field / SRS resource set / TRP (second mapping pattern information). The first mapping pattern information and the second mapping pattern information may be different.

[0126] For example, if a parameter indicating cyclic mapping type 1 (e.g., CyclicalMappingType1) is set as the first mapping pattern information for the UE, the UE may determine that the first SRI field / SRS resource set / TRP is the "first beam". Also, for example, if a parameter indicating cyclic mapping type 2 (e.g., CyclicalMappingType2) is set as the second mapping pattern information for the UE, the UE may determine that the second SRI field / SRS resource set / TRP is the "first beam".

[0127] Although the above describes cases where cyclic mapping is applied, cyclic mapping may also be sequential mapping or a half-half pattern. Furthermore, the UE may be notified of information indicating at least one of cyclic mapping, sequential mapping, and a half-half pattern as mapping pattern information. Multiple first / second mapping pattern information entries may be defined, and at least one of them may be set in the UE. For example, in addition to or instead of the above-mentioned CyclicalMappingType1 / 2, sequential mapping type 1 / 2 (SequentialMappingType1 / 2), half-half mapping type 1 / 2 (half-half mappingType1 / 2), etc., may be set in the UE. Also, the various settings (upper layer parameters) shown in Embodiment 1-2 may be included in RRC information elements other than the above-mentioned RRC information elements (RRC information elements for mapping pattern settings, SRS-Config, etc.), or they may be included in new RRC information elements defined in Rel. 17 and later.

[0128] Figures 12A and 12B show examples of the order of multiple SRI fields according to Embodiment 1-2. In the examples shown in Figures 12A and 12B, a cyclic mapping example is shown where repeated transmissions and multiple SRI fields correspond cyclically, and a sequential mapping example is shown where a specific number (in this case, two) of fields correspond sequentially.

[0129] In the example shown in Figure 12A, the UE sets SRI field #1 as the first SRI. In the example of cyclic mapping shown in Figure 12A, the UE first makes one PUSCH transmission using SRI field #1, and then one PUSCH transmission using SRI field #2. Thereafter, it alternates between making one PUSCH transmission using SRI field #1 and one PUSCH transmission using SRI field #2. In the example of sequential mapping shown in Figure 12A, the UE first makes two PUSCH transmissions using SRI field #1, and then two PUSCH transmissions using SRI field #2.

[0130] In the example shown in Figure 12B, the UE sets SRI field #2 as the first SRI. In the example of cyclic mapping shown in Figure 12B, the UE first makes one PUSCH transmission using SRI field #2, and then one PUSCH transmission using SRI field #1. Thereafter, it alternates between making one PUSCH transmission using SRI field #2 and one using SRI field #1. In the example of sequential mapping shown in Figure 12B, the UE first makes two PUSCH transmissions using SRI field #2, and then two PUSCH transmissions using SRI field #1.

[0131] Modified form of the first embodiment [Variation of Option 1] A single SRI field may be notified to the UE. Based on this single SRI field, the UE may decide to either repeatedly send messages for a single TRP or repeatedly send messages for multiple TRPs.

[0132] If the UE decides to make repeated transmissions to multiple TRPs, it may determine which SRI is the "first beam" based on the code point of the indicated SRI field.

[0133] Figure 13 shows an example of the sequence of multiple TRPs according to a modification of the first embodiment. In the example shown in Figure 13, the UE is notified of one SRI field. In the correspondence of the SRI fields shown in Figure 13, the code point "00" of the SRI field corresponds to "SRS resource #1, SRS resource #2", the code point "01" of the SRI field corresponds to "SRS resource #2, SRS resource #1", the code point "10" of the SRI field corresponds to "SRS resource #1", and the code point "11" of the SRI field corresponds to "SRS resource #2". Note that the example shown in Figure 13 applies cyclic mapping.

[0134] The code points "00" and "01" in the SRI field support repeated transmissions for multiple TRPs, while the code points "10" and "11" support single PUSCH transmissions / repeated PUSCH transmissions for a single TRP.

[0135] When the UE receives the code point "00" in the SRI field, it decides to perform repeated transmissions to multiple TRPs (using SRS resource #1 and SRS resource #2), and determines that the first (leftmost) SRS resource of that code point (in this case, SRS resource #1) is the "first beam".

[0136] When the UE receives code point "01" in the SRI field, it decides to perform repeated transmissions to multiple TRPs (using SRS resource #1 and SRS resource #2), and determines that the first (leftmost) SRS resource of that code point (in this case, SRS resource #2) is the "first beam".

[0137] In the example shown in Figure 13, the UE identifies the first (leftmost) SRS resource in the code point as the "first beam." However, the UE may also identify the last (rightmost) SRS resource in the code point as the "first beam."

[0138] According to the first embodiment described above, even if there is no dynamic switching (change) of the order of multiple (e.g., two) TRPs used, it becomes possible to appropriately determine which TRP to use first in repeated transmissions.

[0139] <Second Embodiment> In the second embodiment, the UE may indicate / update in the MAC CE which SRI field / SRS resource set / TRP is the “first beam”.

[0140] Embodiment 2-1 The MAC CE notified to the UE may include an instruction field indicating which SRI field / SRS resource set / TRP is the "first beam".

[0141] The indicator field may have a specific number of bits (e.g., 1). For example, when the indicator field indicates a first value (e.g., 0), the UE may determine that the first SRI field / SRS resource set / TRP is the "first beam". Also, when the indicator field indicates a second value (e.g., 1), the UE may determine that the second SRI field / SRS resource set / TRP is the "first beam".

[0142] In this disclosure, the first value and the second value may be interpreted as mutually interchangeable. Also, in this disclosure, the first value and the second value may be interpreted as the value of x (where x is any integer).

[0143] Furthermore, the instruction field may be set to a specific number of bits (e.g., 1) for each CB / NCB SRS resource set. For example, for a CB / NCB SRS resource set in which the instruction field indicates a first value (e.g., 0), the UE may determine that the SRS resource set / the SRI field / TRP corresponding to that SRS resource set is the "first beam". Also, for a CB / NCB SRS resource set in which the instruction field indicates a second value (e.g., 1), the UE may determine that the SRS resource set / the SRI field / TRP corresponding to that SRS resource set is not the "first beam".

[0144] The UE may determine which SRI field / SRS resource set / TRP is the "first beam" based on the mapping pattern indication field notified by the MAC CE. In other words, the UE may receive an indication field in the MAC CE for a mapping pattern indicating that the "first beam" is the first SRI field / SRS resource set / TRP (first mapping pattern indication field), or an indication field for a mapping pattern indicating that the "first beam" is the second SRI field / SRS resource set / TRP (second mapping pattern indication field). The UE may then determine which mapping pattern to apply to repeated transmissions based on whether the indication field indicates a specific value (e.g., 0 or 1).

[0145] For example, when the first mapping pattern indicator field indicates a second value (e.g., 1), the UE applies cyclic mapping type 1 (e.g., CyclicalMappingType1). In this case, the UE may determine that the first SRI field / SRS resource set / TRP is the "first beam".

[0146] Furthermore, for example, when the second mapping pattern indicator field indicates a second value (e.g., 1), the UE applies cyclic mapping type 2 (e.g., CyclicalMappingType2). In this case, the UE may determine that the second SRI field / SRS resource set / TRP is the "first beam".

[0147] While the above describes cases where cyclic mapping is applied, cyclic mapping can also be sequential mapping or a half-half pattern.

[0148] Embodiment 2-2 An indicator field that indicates which SRI field / SRS resource set / TRP is the "first beam" may be included in the MAC CE used for SRS activation / deactivation. This indicator field may also be included in the MAC CE that indicates the spatial relationships of the SRS.

[0149] If the UE supports receiving MAC CEs that instruct / update mapping patterns (or the UE supports specifying / updating mapping patterns via MAC CEs), such MAC CEs (e.g., SRS activation / deactivation MAC CEs, SRS spatial relationship instruction MAC CEs) may include an instruction field that indicates which SRI field / SRS resource set / TRP is the "first beam".

[0150] Furthermore, the instruction field indicating which SRI field / SRS resource set / TRP is the "first beam" may be included in MAC CEs other than those mentioned above, or in new MAC CEs defined in Rel. 17 or later (for example, MAC CEs that indicate / update mapping patterns).

[0151] The notification methods for the instruction field described in Embodiments 2-1 and 2-2 above may be used in any combination. In this embodiment, the same operation as the UE operation described using Figures 12A and 12B above is possible.

[0152] According to the second embodiment described above, MAC CE can be used to appropriately determine which TRP to use first in repeated transmissions to multiple (e.g., two) TRPs.

[0153] <Third Embodiment> In the third embodiment, the UE may indicate in the DCI which SRI field / SRS resource set / TRP is the “first beam”.

[0154] Embodiment 3-1 The indicator field that indicates which SRI field / SRS resource set / TRP is the "first beam" may be included in (or be the same as) the DCI field used for dynamic switching between a single push transmission / repeated push transmission for a single TRP and repeated push transmission for multiple TRPs. In other words, the UE may determine / decide based on a specific DCI field whether to perform a single push transmission / repeated push transmission for a single TRP or repeated push transmission for multiple TRPs, and, if repeated push transmission for multiple TRPs is performed, which SRI field / SRS resource set / TRP is the "first beam".

[0155] In Embodiment 3-1, the specific DCI field may be a specific DCI field as shown in Option 2 above.

[0156] Furthermore, in Embodiment 3-1, the specific field may be a DCI field defined up to Rel. 16, or a new DCI field defined in Rel. 17 or later.

[0157] Furthermore, Embodiment 3-1 is preferably applied when Option 2 is in operation. Also, when multiple TRPs are specified, it is necessary to specify valid SRS resource / TPMI / TPC command values ​​in all of the multiple SRI fields / TPMI fields / TPC command fields. Therefore, Embodiment 3-1 is preferably applied when DCI fields other than the SRI fields / TPMI fields / TPC command fields are used for PUSCH transmissions for a single TRP and repeated PUSCH transmissions for multiple TRPs, and when multiple SRI fields / TPMI fields / TPC command fields indicate valid SRS resources.

[0158] Figure 14 shows an example of a DCI field used to indicate the order of multiple SRI fields according to Embodiment 3-1. Based on the DCI field as shown in Figure 14, the UE decides whether to repeatedly transmit a PUSCH for a single TRP or repeatedly transmit a PUSCH for multiple TRPs, and if it chooses to repeatedly transmit a PUSCH for multiple TRPs, it determines which SRI field / SRS resource set / TRP is the "first beam".

[0159] For example, if the DCI field indicates "00", the UE will repeatedly send / single PUSCH messages to TRP#1 using SRI field #1. If the DCI field indicates "01", the UE will repeatedly send / single PUSCH messages to TRP#2 using SRI field #2.

[0160] If the DCI field indicates "10", the UE decides to repeatedly transmit PUSCH signals to multiple TRPs (TRP#1 using SRI field #1 and TRP#2 using SRI field #2) where the "first beam" is SRI field #1. If the DCI field indicates "11", the UE decides to repeatedly transmit PUSCH signals to multiple TRPs (TRP#1 using SRI field #1 and TRP#2 using SRI field #2) where the "first beam" is SRI field #2.

[0161] Embodiment 3-2 An indicator field that indicates which SRI field / SRS resource set / TRP is the "first beam" may be set separately (independently) from the DCI field used for dynamic switching between a single push transmission / repeated push transmission for a single TRP and repeated push transmission for multiple TRPs. In other words, the UE may determine, based on the first DCI field, whether to perform a single push transmission / repeated push transmission for a single TRP or repeated push transmission for multiple TRPs, and then, if performing repeated push transmission for multiple TRPs, determine, based on the second DCI field, which SRI field / SRS resource set / TRP is the "first beam".

[0162] In Embodiment 3-2, the specific field may be a DCI field defined up to Rel. 16, or a new DCI field defined in Rel. 17 or later.

[0163] In Embodiment 3-2, if the UE is instructed to repeatedly send a single PUSCH transmission / single TRP using the first DCI field, the UE may ignore the second DCI field.

[0164] Furthermore, when options 1 / 2 above are applied, such as when a dynamic switch is used between repeated transmission of a PUSCH signal for a single TRP and repeated transmission of a PUSCH signal for multiple TRPs, embodiment 3-2 is preferred.

[0165] Figure 15 shows an example of a DCI field used to indicate the order of multiple SRI fields according to Embodiment 3-2. First, the UE is instructed to apply SRI field #1 and SRI field #2 as shown in Figure 8. Next, the UE determines which SRI field / SRS resource set / TRP is the "first beam" based on the DCI field shown in Figure 15.

[0166] If the DCI field indicates "0", the UE decides to repeatedly transmit PUSCH signals to multiple TRPs (TRP#1 using SRI field #1 and TRP#2 using SRI field #2) where the "first beam" is SRI field #1. If the DCI field indicates "1", the UE decides to repeatedly transmit PUSCH signals to multiple TRPs (TRP#1 using SRI field #1 and TRP#2 using SRI field #2) where the "first beam" is SRI field #2.

[0167] In this embodiment, the same operations as those described using Figures 12A and 12B above are possible.

[0168] According to the third embodiment described above, DCI can be used to appropriately determine which TRP to use first in a series of repeated transmissions to multiple (e.g., two) TRPs.

[0169] <Fourth Embodiment> In a fourth embodiment, when the UE is instructed to repeatedly send PUSCH to multiple TRPs and is instructed to send multiple (e.g., two) SRI fields / TPMI fields / TPC command fields, it may determine the correspondence between the repeated PUSCH transmissions and the TPMI fields / TPC command fields based on certain rules. Such certain rules may conform to at least one of Embodiments 4-1 and 4-2 described below.

[0170] Embodiment 4-1 Each of the multiple SRI fields / TPMI fields / TPC command fields may have a one-to-one correspondence. In other words, a TPMI field / TPC command field with the x-th index (where x is an integer) may correspond to an SRI field / SRS resource set field / TRP with the x-th index.

[0171] In this embodiment, the correspondence between the repeated transmission / transmission opportunity of PUSCH and the SRI field / SRS resource set field / TRP may be determined according to the method described in the second and third embodiments above.

[0172] In Embodiment 4-1, the UE may apply the TPMI field / TPC command field to the repeated transmission / transmission opportunity of a PUSCH that utilizes the SRI field / SRS resource set / TRP corresponding to the TPMI field / TPC command field.

[0173] Figure 16 shows an example of the correspondence between TPMI fields / TPC command fields and repeated PUSCH transmissions according to Embodiment 4-1. In Figure 16, examples are shown for the case where the "first beam" is SRI field #1 and the case where it is SRI field #2. In each example, the UE applies TPMI field #1 / TPC command field #1 to PUSCH transmissions using SRI field #1, and applies TPMI field #2 / TPC command field #2 to PUSCH transmissions using SRI field #2.

[0174] Embodiment 4-2 The correspondence between multiple TPMI fields / TPC command fields and repeated PUSCH transmissions may be determined based on a mapping pattern. In other words, the correspondence between multiple TPMI fields / TPC command fields and repeated PUSCH transmissions may be determined according to at least one of the cyclic mapping, sequential mapping, and half-half patterns described above.

[0175] In this embodiment, the correspondence between repeated PUSCH transmissions / transmission opportunities and SRI fields / SRS resource set fields / TRPs may be determined according to the methods described in the second and third embodiments above. In addition, in this embodiment, the correspondence between multiple TPMI fields / TPC command fields and repeated PUSCH transmissions may be set / instructed separately from the correspondence between repeated PUSCH transmissions and SRI fields / SRS resource set fields / TRPs.

[0176] In this embodiment, the UE may receive information that sets up / instructs the correspondence between multiple TPMI fields / TPC command fields and repeated PUSCH transmissions using at least one of upper-layer signaling and physical-layer signaling.

[0177] Figure 17 shows an example of the correspondence between TPMI fields / TPC command fields and repeated PUSCH transmissions according to Embodiment 4-2. In Figure 17, examples are shown for the case where the "first beam" is SRI field #1 and the case where it is SRI field #2. In each example shown in Figure 17, the UE is configured / instructed to apply a cyclic mapping as the correspondence between multiple TPMI fields / TPC command fields and repeated PUSCH transmissions.

[0178] In each example shown in Figure 17, the UE applies TPMI field #1 / TPC command field #1 to the first PUSCH transmission and TPMI field #2 / TPC command field #2 to the next PUSCH transmission. Thereafter, the UE alternates between using TPMI field #1 / TPC command field #1 and using TPMI field #1 / TPC command field #1 once each.

[0179] In this embodiment, an example of cyclic mapping is shown, but sequential mapping and half-half patterns can also be applied as appropriate.

[0180] According to the fourth embodiment described above, even if the TRP used first in a repeated transmission to multiple (e.g., two) TRPs is changed, it becomes possible to appropriately apply TPMI / TPC commands.

[0181] <Fifth Embodiment> In a fifth embodiment, UE capability related to each embodiment of the present disclosure is described. The UE may report (transmit) to the NW whether it has such capability.

[0182] The UE capabilities associated with each embodiment of this disclosure may be defined as whether or not repeated transmission of PUSCH to multiple TRPs is supported.

[0183] The UE capabilities associated with each embodiment of this disclosure may be defined as whether or not repeated transmission of PUSCH for multiple TRPs is supported for PUSCH repeated transmission type A / type B.

[0184] The UE capabilities associated with each embodiment of this disclosure may be defined as whether or not dynamic switching between a single PUSCH transmission and repeated PUSCH transmissions for multiple TRPs is supported.

[0185] The UE capabilities associated with each embodiment of this disclosure may be defined as whether or not dynamic switching between repeated transmission of PUSCH for a single TRP and repeated transmission of PUSCH for multiple TRPs is supported.

[0186] The UE capabilities associated with each embodiment of this disclosure may be defined as whether or not dynamic switching of the order of multiple TRPs is supported.

[0187] The UE capability associated with each embodiment of this disclosure may be defined as whether or not dynamic switching of the sequence of multiple TRPs based on MAC CE is supported.

[0188] The UE capability associated with each embodiment of this disclosure may be defined as whether or not dynamic switching of the sequence of multiple TRPs based on DCI is supported.

[0189] The UE capabilities associated with each embodiment of this disclosure may be defined as whether or not the above-described UE capabilities are supported for CB / NCB-based PUSCH.

[0190] Each embodiment of the present disclosure may apply under at least one of the following conditions: the UE reports to the NW a UE capability corresponding to at least one of the above; and the UE is configured / activated / instructed by upper-layer signaling for at least one of the above UE capabilities. Each embodiment of the present disclosure may also apply to the UE when a specific upper-layer parameter is configured / activated / instructed.

[0191] According to the fifth embodiment described above, the UE can realize the functions of each embodiment described above while maintaining compatibility with existing specifications.

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

[0193] Figure 18 shows an example of a schematic configuration of a wireless communication system according to one 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), etc., as specified by the Third Generation Partnership Project (3GPP).

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

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

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

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

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

[0199] Each CC may be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). A macrocell C1 may be included in FR1, and a 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 fall in a frequency band higher than FR2.

[0200] Furthermore, the user terminal 20 may communicate using at least one of the following methods at each CC: Time Division Duplex (TDD) and Frequency Division Duplex (FDD).

[0201] Multiple base stations (e.g., RRHs) 10 may be connected by wire (e.g., optical fiber compliant with Common Public Radio Interface (CPRI), X2 interface, etc.) or wireless (e.g., NR communication). For example, if NR communication is used as backhaul between base stations 11 and 12, base station 11, which is the upstream station, may be called an Integrated Access Backhaul (IAB) donor, and base station 12, which is the relay station, may be called an IAB node.

[0202] Base station 10 may be connected to the core network 30 via other base stations 10 or directly. The core network 30 may include at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), etc.

[0203] The user terminal 20 may be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.

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

[0205] The wireless access method may also be called a waveform. In wireless communication system 1, other wireless access methods (for example, other single-carrier transmission methods, other multi-carrier transmission methods) may be used for the UL and DL wireless access methods.

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

[0207] Furthermore, in the wireless communication system 1, the uplink channel may include a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), a Physical Random Access Channel (PRACH), or the like, all of which are shared by each user terminal 20.

[0208] User data, higher-layer control information, and System Information Blocks (SIBs) are transmitted via PDSCH. User data and higher-layer control information may also be transmitted via PUSCH. Furthermore, Master Information Blocks (MIBs) may be transmitted via PBCH.

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

[0210] Furthermore, the DCI that schedules PDSCH may be called a DL assignment or DL ​​DCI, and the DCI that schedules PUSCH may be called a UL grant or UL DCI. Furthermore, PDSCH may be interpreted as DL data, and PUSCH may be interpreted as UL data.

[0211] PDCCH detection may utilize a Control Resource Set (CORESET) and a search space. A CORESET corresponds to the resources used to search for DCIs. A search space corresponds to the search area and search method for PDCCH candidates. A single CORESET may be associated with one or more search spaces. The UE may monitor CORESETs associated with a particular search space based on the search space configuration.

[0212] A single search space may correspond to one or more PDCCH candidates corresponding to aggregation levels. One or more search spaces may be referred to as a search space set. In this disclosure, "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," and "CORESET configuration" may be interpreted interchangeably.

[0213] PUCCH may transmit uplink control information (UCI) which includes at least one of the following: channel state information (CSI), delivery acknowledgment (e.g., Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). PRACH may transmit a random access preamble for establishing a connection with the cell.

[0214] In this disclosure, downlinks, uplinks, etc., may be expressed without the prefix "link." Also, the prefix "physical" may be omitted when describing various channels.

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

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

[0217] Furthermore, in the wireless communication system 1, the Uplink Reference Signal (UL-RS) may transmit the Sounding Reference Signal (SRS), Demodulation Reference Signal (DMRS), etc. The DMRS may also be called the User-Specific Reference Signal (UE-specific Reference Signal).

[0218] (base station) Figure 19 shows an example of the configuration of a base station according to one 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 the control unit 110, transceiver unit 120, transceiver antenna 130, and transmission line interface 140 may be provided.

[0219] In this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. Some of the processing of each part described below may be omitted.

[0220] The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, control circuit, etc., as described based on common understanding in the art relating to this disclosure.

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

[0222] The transmitting / receiving 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 transmitting / receiving unit 120 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0223] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 1211 and an RF unit 122. The receiving unit may consist of a receiving processing unit 1212, an RF unit 122 and a measuring unit 123.

[0224] The transmitting and receiving antenna 130 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

[0225] The transmitting / receiving unit 120 may transmit the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 120 may also receive the uplink channel, uplink reference signal, etc.

[0226] The transmitting / receiving unit 120 may form at least one of the transmitting beam and the receiving beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

[0227] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform processing on data and control information acquired from the control unit 110, for example, at the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer (e.g., RLC retransmission control), the Medium Access Control (MAC) layer (e.g., HARQ retransmission control), etc., to generate a bit sequence to be transmitted.

[0228] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform transmission processing on the bit sequence to be transmitted, 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, and output a baseband signal.

[0229] The transmitting / receiving unit 120 (RF unit 122) may perform modulation, filtering, amplification, etc., of the baseband signal to the radio frequency band and transmit the signal in the radio frequency band via the transmitting / receiving antenna 130.

[0230] On the other hand, the transmitting / receiving unit 120 (RF unit 122) may perform amplification, filtering, demodulation to a baseband signal, etc., on the radio frequency band signal received by the transmitting / receiving antenna 130.

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

[0232] The transmitting / receiving unit 120 (measurement unit 123) may perform measurements related to 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 also measure received power (e.g., Reference Signal Received Power (RSRP)), reception 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.

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

[0234] In this disclosure, the transmitting and receiving units of the base station 10 may consist of at least one of a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission path interface 140.

[0235] The transmitting / receiving unit 120 may transmit information used to determine the Sounding Reference Signal Resource Indicator (SRI) to be applied to the first of the multiple Physical Uplink Shared Channels (PUSCHs), and to determine the order in which the SRIs to be applied to each PUSCH. The control unit 110 may control the reception of the multiple PUSCHs (in the first to third embodiments).

[0236] (User terminal) Figure 20 shows an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Note that one or more of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may be provided.

[0237] In this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. Some of the processing of each part described below may be omitted.

[0238] The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., as described based on common understanding in the technical field related to this disclosure.

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

[0240] 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 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0241] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 2211 and an RF unit 222. The receiving unit may consist of a receiving processing unit 2212, an RF unit 222 and a measuring unit 223.

[0242] The transmitting and receiving antenna 230 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

[0243] The transmitting / receiving unit 220 may receive the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 220 may also transmit the uplink channel, uplink reference signal, etc.

[0244] The transmitting / receiving unit 220 may form at least one of the transmitting beam and the receiving beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

[0245] The transmitting / receiving 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 and control information acquired from the control unit 210, etc., to generate a bit sequence to be transmitted.

[0246] The transmitting / receiving unit 220 (transmission processing unit 2211) may perform transmission processing on the bit sequence to be transmitted, 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, and output a baseband signal.

[0247] Whether or not to apply DFT processing may be based on the transform precoding settings. The transmitting / receiving unit 220 (transmission processing unit 2211) may perform DFT processing as part of the transmission process to transmit a channel (for example, PUSCH) using a DFT-s-OFDM waveform if transform precoding is enabled for that channel, or it may not perform DFT processing as part of the transmission process if transform precoding is not enabled for that channel.

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

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

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

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

[0252] In this disclosure, the transmitting and receiving units of the user terminal 20 may consist of at least one of a transmitting / receiving unit 220 and a transmitting / receiving antenna 230.

[0253] The control unit 210 may determine which Sounding Reference Signal Resource Indicator (SRI) to apply to the first of the multiple Physical Uplink Shared Channels (PUSCHs), and may also determine the order in which the SRIs to be applied to each PUSCH. The transmitting / receiving unit 220 may transmit the multiple PUSCHs (in the first to third embodiments).

[0254] The control unit 210 may determine, based on wireless resource control signaling, the SRI to be applied to the first PUSCH and the order in which the SRIs to be applied to each PUSCH are applied (first embodiment).

[0255] The control unit 210 may determine, based on the media access control element, the SRI to be applied to the first PUSCH and the order in which the SRIs to be applied to each PUSCH are applied (second embodiment).

[0256] The control unit 210 may determine, based on the downlink control information, the SRI to be applied to the first PUSCH and the order in which the SRIs to be applied to each PUSCH are applied (third embodiment).

[0257] (Hardware configuration) The block diagrams used in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software.

[0258] Here, functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission may be called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

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

[0260] In this disclosure, terms such as apparatus, circuit, device, section, and unit are interchangeable. The hardware configuration of the base station 10 and the user terminal 20 may include one or more of the devices shown in the figure, or it may be configured to omit some of the devices.

[0261] For example, although only one processor 1001 is shown in the diagram, there may be multiple processors. Furthermore, processing may be performed by one processor, or by two or more processors simultaneously, sequentially, or by other means. Note that processor 1001 may be implemented using one or more chips.

[0262] Each function in the base station 10 and the user terminal 20 is realized, for example, by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations and control communication via the communication device 1004, or to control at least one of the reading and writing of data in the memory 1002 and storage 1003.

[0263] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, etc. For example, at least a part of the control unit 110 (210) and the transmitting / receiving unit 120 (220) described above may be implemented by the processor 1001.

[0264] Furthermore, the processor 1001 reads programs (program code), 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 accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly.

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

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

[0267] The communication device 1004 is hardware (a transceiver device) for performing communication between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may include, for example, a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-described transceiver unit 120 (220), transceiver antenna 130 (230), etc. may be implemented by the communication device 1004. The transceiver unit 120 (220) may be physically or logically separated and implemented by a transmission unit 120a (220a) and a reception unit 120b (220b).

[0268] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives an external input. The output device 1006 is an output device (for example, a display, a speaker, a Light Emitting Diode (LED) lamp, etc.) that performs an output to the outside. Note that the input device 1005 and the output device 1006 may have an integrated configuration (for example, a touch panel).

[0269] Also, 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 for each device.

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

[0271] (modified version) In addition, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) may be used interchangeably. Also, a signal may be a message. A reference signal may be abbreviated as RS and may be called a pilot, pilot signal, etc., depending on the applicable standard. Also, a component carrier (CC) may be called a cell, frequency carrier, carrier frequency, etc.

[0272] A wireless frame may consist of one or more periods (frames) in the time domain. Each of these periods (frames) constituting a wireless frame may be called a subframe. Furthermore, a subframe may consist 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.

[0273] Here, the neuralelogy may be communication parameters applied to at least one of the transmission and reception of a signal or channel. The neuralelogy may be, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, or specific windowing processes performed by the transceiver in the time domain.

[0274] A slot may consist of one or more symbols in the time domain (such as Orthogonal Frequency Division Multiplexing (OFDM) symbols or Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols). Alternatively, a slot may be a time unit based on neurology.

[0275] A slot may include multiple mini-slots. Each mini-slot may consist of one or more symbols in the time domain. Mini-slots may also be called sub-slots. Mini-slots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may be called a PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may be called a PDSCH (PUSCH) mapping type B.

[0276] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Wireless frames, subframes, slots, minislots, and symbols may each be referred to by different names. Furthermore, the units of time such as frames, subframes, slots, minislots, and symbols in this disclosure may be interpreted as interchangeable.

[0277] For example, one subframe may be called TTI, multiple consecutive subframes may be called TTI, or one slot or one mini-slot may be called TTI. In other words, at least one of the subframe and TTI may be a subframe (1ms) in existing LTE, a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. Note that the unit representing TTI may be called a slot, mini-slot, etc., instead of a subframe.

[0278] Here, TTI refers to, for example, the smallest unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0279] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Given a TTI, the actual time interval (e.g., number of symbols) to which the transport block, code block, code word, etc. are mapped may be shorter than the given TTI.

[0280] Furthermore, if one slot or one mini-slot is referred to as TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit of scheduling. In addition, the number of slots (number of mini-slots) that constitute the minimum time unit of scheduling may be controlled.

[0281] A TTI with a time length of 1 ms may also be called a normal TTI (TTI in 3GPP Rel.8-12), a long TTI, a normal subframe, a long subframe, or a slot. A TTI shorter than a normal TTI may also be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini slot, a sub slot, or a slot.

[0282] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

[0283] A Resource Block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology.

[0284] Furthermore, an RB may contain one or more symbols in the time domain and may have the length of one slot, one minislot, one subframe, or one TTI. Each TTI, subframe, etc., may consist of one or more resource blocks.

[0285] One or more RBs may be referred to as a Physical Resource Block (PRB), a Sub-Carrier Group (SCG), a Resource Element Group (REG), a PRB pair, an RB pair, etc.

[0286] Also, a resource block may be composed of one or more Resource Elements (REs). For example, 1 RE may be a radio resource area of 1 sub-carrier and 1 symbol.

[0287] A Bandwidth Part (BWP) (which may also be referred to as a partial bandwidth, etc.) may represent a subset of consecutive common resource blocks (common RBs) for a certain numerology in a certain carrier. Here, the common RB may be specified by the index of the RB based on the common reference point of the carrier. The PRB is defined in a certain BWP and may be numbered within the BWP.

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

[0289] At least one of the set BWPs may be active, and the UE may not be assumed to transmit and receive a predetermined signal / channel outside the active BWP. Note that "cell", "carrier", etc. in the present disclosure may be read as "BWP".

[0290] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative examples. For instance, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots within a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

[0291] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or corresponding other information. For example, wireless resources may be indicated by a predetermined index.

[0292] The names used for parameters and other elements in this disclosure are not restrictive in any way. Furthermore, mathematical formulas and other elements that use these parameters may differ from those expressly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

[0293] The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. 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 voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0294] Furthermore, information, signals, etc., can be output from upper layers to lower layers and from lower layers to upper layers, or to at least one of the two. Information, signals, etc., may also be input and output via multiple network nodes.

[0295] Input and output information and signals may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information and signals may be overwritten, updated, or appended to. Output information and signals may be deleted. Input information and signals may be transmitted to other devices.

[0296] Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification in this disclosure may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof).

[0297] Physical layer signaling may also be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. RRC signaling may also be called RRC messages, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc. MAC signaling may also be communicated using, for example, MAC Control Element (CE).

[0298] Furthermore, notification of the specified information (for example, notification that "X is the case") is not limited to explicit notification, but may also be made implicitly (for example, by not notifying the specified information or by notifying other information).

[0299] The determination may be made by a value represented by 1 bit (0 or 1), by a boolean value represented as true or false, or by a numerical comparison (for example, a comparison with a predetermined value).

[0300] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0301] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or Digital Subscriber Line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0302] The terms “system” and “network” as used in this disclosure may be used interchangeably. “Network” may also mean the equipment included in the network (e.g., base stations).

[0303] 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," and "panel" may be used interchangeably.

[0304] In this disclosure, terms such as "Base Station (BS)", "wireless base station", "fixed station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "access point", "Transmission Point (TP)", "Reception Point (RP)", "Transmission / Reception Point (TRP)", "panel", "cell", "sector", "cell group", "carrier", and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0305] A base station can house one or more (e.g., three) cells. If a base station houses multiple cells, the entire coverage area of ​​the base station can be divided into several smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0306] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.

[0307] A mobile station may also be called 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 appropriate term.

[0308] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, etc. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile 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 be 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.

[0309] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple user terminals (which may be called, for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may have the functions that the base station 10 has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc., may be interpreted as side channel.

[0310] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station 10 may be configured to have the same functions as the user terminal 20 described above.

[0311] In this disclosure, operations performed by a base station may, in some cases, be performed by its upper node. In a network including one or more network nodes with base stations, it is clear that various operations performed for communication with terminals may be performed by the base station, one or more network nodes other than the base station (for example, a Mobility Management Entity (MME), a Serving Gateway (S-GW), etc., but not limited to these), or a combination thereof.

[0312] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between during execution. Furthermore, the processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be rearranged in order, provided they are consistent. For example, the methods described in this disclosure present various step elements in an exemplary order and are not limited to that specific order.

[0313] Each aspect / embodiment described in this disclosure includes 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 (where x is, for example, an integer or 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®), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), and IEEE This may be applied to systems utilizing 802.20, Ultra-WideBand (UWB), Bluetooth®, or other appropriate wireless communication methods, as well as next-generation systems that extend these. It may also be applied in combination with multiple systems (for example, a combination of LTE or LTE-A and 5G).

[0314] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0315] Any reference to elements using the designations “first,” “second,” etc., as 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 way to distinguish between two or more elements. Accordingly, the references to the first and second elements do not imply that only two elements may be employed or that the first element must precede the second element in any way.

[0316] The term “determining” as used in this disclosure may encompass a wide variety of actions. For example, “determining” may be considered to include judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiry (e.g., searching in tables, databases, or other data structures), ascertaining, etc.

[0317] Furthermore, "judgment (decision)" may be considered as "judging (deciding)" things like receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory).

[0318] Furthermore, "judgment (decision)" can be considered as "judging (deciding)" something like resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment (decision)" can be considered as "judging (deciding)" something about an action.

[0319] Furthermore, "judgment (decision)" can be replaced with "assuming," "expecting," or "considering."

[0320] As used in this disclosure, the terms “connected,” “coupled,” and any variations thereof mean any direct or indirect connection or coupling between two or more elements, and may include one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be replaced with “access.”

[0321] In this disclosure, when two elements are connected, they can be considered to be “connected” or “coupled” to each other using one or more wires, cables, printed electrical connections, etc., and, in some non-exclusive and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, or optical domain (both visible and invisible).

[0322] In this 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 "combine" may be interpreted similarly to "different."

[0323] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0324] In this disclosure, if articles are added by translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0325] Although the invention described herein has been explained in detail above, it will be clear to those skilled in the art that the invention described herein is not limited to the embodiments described herein. The invention described herein can be implemented in modified and altered forms without departing from the spirit and scope of the invention as defined in the claims. Therefore, the descriptions herein are for illustrative purposes only and do not imply any limitation on the invention described herein.

[0326] This application is based on Japanese Patent Application No. 2021-016785, filed on February 4, 2021. All of its contents are included here.

Claims

1. A receiving unit receives downlink control information (DCI) which includes a field indicating whether to transmit a first iteration of a physical uplink shared channel (PUSCH) applying a single sounding reference signal (SRS) resource indicator (SRI) field, or a second iteration of a PUSCH applying multiple SRI fields, wherein the field is different from both the single SRI field and the multiple SRI fields. The system includes a control unit that determines whether to transmit the first repetition or the second repetition based on the field, If the field indicates the second repetition, the control unit determines, based on the field, the SRS resource set and SRI field to be used for the first transmission of the second repetition.

2. The terminal according to claim 1, wherein, when the field indicates the second repetition, the control unit determines that the first Transmitted Precoding Matrix Indicator (TPMI) instruction field included in the DCI corresponds to the first SRI field among the plurality of SRI fields and the first SRS resource set, and the second TPMI instruction field included in the DCI corresponds to the second SRI field among the plurality of SRI fields and the second SRS resource set.

3. Steps include receiving downlink control information (DCI) which includes a field indicating whether to transmit a first iteration of a physical uplink shared channel (PUSCH) applying a single sounding reference signal (SRS) resource indicator (SRI) field, or a second iteration of a PUSCH applying multiple SRI fields, wherein the field is different from both the single SRI field and the multiple SRI fields, The step of determining whether to send the first repetition or the second repetition based on the field, A wireless communication method for a terminal, wherein, if the field indicates the second repetition, the terminal determines, based on the field, the SRS resource set and SRI field to be used for the first transmission of the second repetition.

4. A transmitter transmits downlink control information (DCI) which includes a field indicating whether to transmit a first iteration of a physical uplink shared channel (PUSCH) applying a single sounding reference signal (SRS) resource indicator (SRI) field, or a second iteration of a PUSCH applying multiple SRI fields, wherein the field is different from both the single SRI field and the multiple SRI fields. The system includes a control unit that uses the field to instruct whether to transmit the first repetition or the second repetition, If the field indicates the second repetition, the field is used to determine the SRS resource set and SRI field to be used for the first transmission of the second repetition, the base station.

5. A system having a base station and a terminal, The aforementioned base station is A transmitter has a field that indicates whether to transmit a first iteration of a physical uplink shared channel (PUSCH) applying a single sounding reference signal (SRS) resource indicator (SRI) field or a second iteration of a PUSCH applying multiple SRI fields, wherein the field is different from both the single SRI field and the multiple SRI fields. The aforementioned terminal is A receiving unit that receives the DCI, The system includes a control unit that determines whether to transmit the first repetition or the second repetition based on the field, If the field indicates the second repetition, the control unit determines, based on the field, the SRS resource set and SRI field to be used for the first transmission of the second repetition.

Images