JP7323615B2 - Terminal and wireless communication method - Google Patents

Description

TECHNICAL FIELD The present disclosure relates to a terminal and a wireless communication method in a next-generation mobile communication system.

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

Successor systems of LTE (for example, 5th generation mobile communication system (5G), 5G+ (plus), New Radio (NR), 3GPP Rel. 15 and later) are also being considered.

3GPP TS 36.300 V8.12.0 "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)", April 2010

Future wireless communication systems (eg, NR) are considering supporting codebook-based transmission with precoding matrices. Methods are also being considered for user terminals to transmit at full power in the uplink.

However, in studies on full-power transmission so far, studies have not progressed on cases in which uplink shared channels corresponding to different numbers of ports are dynamically designated. Unless a method for dealing with this case is clearly defined, the UE may not be able to properly perform uplink shared channel transmission, and an increase in communication throughput may be suppressed.

Therefore, one object of the present disclosure is to provide a terminal and a wireless communication method that can appropriately control UL transmission.

A terminal according to an aspect of the present disclosure schedules information for scheduling a first uplink shared channel (Physical Uplink Shared Channel (PUSCH)) and a second PUSCH that starts temporally later than the first PUSCH. and a receiving unit that receives information, and a control unit that assumes that there is a guard period between the first PUSCH and the second PUSCH, and the control unit receives the first PUSCH and the second PUSCH are both scheduled by DCI format 0_1, a guard period is assumed between the first PUSCH and the second PUSCH, and the control unit controls the The number of SRS ports associated with the SRS resource specified by the Sounding Reference Signal (SRS) resource index for the first PUSCH is associated with the SRS resource specified by the SRS resource index for the first PUSCH. A guard period is assumed between the first PUSCH and the second PUSCH if it is greater than the number of SRS ports .

According to one aspect of the present disclosure, it is possible to appropriately control UL transmission.

FIG. 1 is a diagram showing an example of association between precoder types and TPMI indexes. FIG. 2 is a diagram showing an example of a UE configuration assumed by UE capabilities 1-3 related to full power transmission. FIG. 3 is a diagram illustrating an example of an SRS resource set configured for a Mode 2 UE. 4A and 4B are diagrams showing an example of a problem when the number of ports between PUSCHs is changed. FIG. 5 is a diagram illustrating an example of a guard period between PUSCHs according to the first embodiment. FIG. 6 is a diagram showing an example of the length of the guard period in embodiment 1.1. 7A-7D are diagrams of an example MAC CE for guard period activation. 8A and 8B are diagrams showing an example of positions of guard periods in Embodiment 1.1. FIG. 9 is a diagram showing an example of the length of the guard period in embodiment 1.2. 10A and 10B are diagrams showing an example of positions of guard periods in Embodiment 1.1. 11A-11C are diagrams showing an example of positions of guard periods in Embodiment 1.3. 12A and 12B are diagrams illustrating an example of an SRS resource set according to Embodiment 2.1. 13A-13C are diagrams illustrating an example of MAC CE according to Embodiment 2.2. 14A-14C are diagrams illustrating another example of MAC CE according to Embodiment 2.2. 15A and 15B are diagrams illustrating an example of MAC CE for SRS resource sets according to embodiment 2.2. 16A and 16B are diagrams illustrating another example of MAC CE for SRS resource sets according to embodiment 2.2. FIG. 17 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment; FIG. 18 is a diagram illustrating an example of the configuration of a base station according to one embodiment. FIG. 19 is a diagram illustrating an example of the configuration of a user terminal according to one embodiment. FIG. 20 is a diagram illustrating an example of hardware configurations of a base station and a user terminal according to one embodiment.

(PUSCH precoder)
In NR, it is considered that the UE supports Codebook (CB) and/or Non-Codebook (NCB) based transmission.

For example, the UE uses at least a measurement reference signal (Sounding Reference Signal (SRS)) resource index (SRS Resource Index (SRI)), at least one of the CB-based and NCB-based uplink shared channel (Physical Uplink Shared Channel (PUSCH )) to determine the precoder (precoding matrix) for transmission.

In the case of CB-based transmission, the UE determines the precoder for PUSCH transmission based on SRI, Transmitted Rank Indicator (TRI) and Transmitted Precoding Matrix Indicator (TPMI), etc. You may The UE may determine the precoder for PUSCH transmission based on the SRI for NCB-based transmission.

SRI, TRI, TPMI, etc. may be notified to the UE using downlink control information (DCI). The SRI may be specified by the SRS Resource Indicator field (SRI field) of the DCI, or specified by the parameter "srs-ResourceIndicator" included in the RRC information element "ConfiguredGrantConfig" of the configured grant PUSCH. may TRI and TPMI may be specified by the DCI's "Precoding information and number of layers" field.

The UE may report UE capability information about the precoder type and be configured with the precoder type based on the UE capability information by higher layer signaling from the base station. The UE capability information may be precoder type information (which may be represented by the RRC parameter “pusch-TransCoherence”) that the UE uses in PUSCH transmission.

In the present disclosure, higher layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, etc., or a combination thereof.

MAC signaling may use, for example, MAC Control Elements (MAC CEs), MAC Protocol Data Units (PDUs), and the like. The broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), or the like.

The UE is based on the precoder type information (which may be represented by the RRC parameter "codebookSubset") included in the PUSCH configuration information ("PUSCH-Config" information element of RRC signaling) notified by higher layer signaling, A precoder to be used for PUSCH transmission may be determined. The UE may be configured with the subset of PMI specified by TPMI by codebookSubset.

Note that the precoder type is either full coherent, fully coherent, coherent, partial coherent, non coherent, or a combination of at least two of these (for example, "complete and fullyAndPartialAndNonCoherent”, “partialAndNonCoherent”, etc.).

Perfect coherence may mean that all antenna ports used for transmission are synchronized (may be expressed as being able to match the phase, applying the same precoder, etc.). Partial coherence may mean that some of the antenna ports used for transmission are synchronized, but some of the antenna ports are not synchronized with other ports. Non-coherent may mean that each antenna port used for transmission is not synchronized.

Note that a UE that supports fully coherent precoder types may be assumed to support partially coherent and non-coherent precoder types. A UE that supports a partially coherent precoder type may be assumed to support a non-coherent precoder type.

The precoder type may be read as coherency, PUSCH transmission coherence, coherence type, coherence type, codebook type, codebook subset, codebook subset type, and the like.

The UE determines a precoding matrix corresponding to the TPMI index obtained from the DCI that schedules the UL transmission from multiple precoders (which may be referred to as precoding matrices, codebooks, etc.) for CB-based transmission. good too.

FIG. 1 is a diagram showing an example of association between precoder types and TPMI indexes. FIG. 1 corresponds to a table of precoding matrix W for single layer transmission using 4 antenna ports in DFT-s-OFDM (Discrete Fourier Transform spread OFDM, transform precoding is effective).

In FIG. 1, if the precoder type (codebookSubset) is fullyAndPartialAndNonCoherent, the UE is signaled any TPMI from 0 to 27 for single layer transmission. Also, if the precoder type is partialAndNonCoherent, the UE is configured with any TPMI from 0 to 11 for single layer transmission. If the precoder type is nonCoherent, the UE is set to any TPMI from 0 to 3 for single layer transmission.

FIG. 1 is a table defined in the current Rel-15 NR. In this table, if the fully coherent transmission power corresponding to indexes 12 to 27 is 1 (=(1/2) ² *4), the partial coherent transmission power corresponding to indexes 4 to 11 is 1/2 ( =(1/2) ² *2), and the non-coherent transmission power corresponding to indices 0 to 3 is 1/4 (=(1/2) ² *1).

That is, according to the current Rel-15 NR specifications, when the UE uses multiple ports for codebook-based transmission, using some codebooks results in lower transmission power than in the case of a single port. (Full power transmission is not possible).

In addition, as shown in FIG. 1, a precoding matrix in which only one component in each column is not 0 may be called a non-coherent codebook. A precoding matrix in which a predetermined number (but not all) of the entries in each column are non-zero may be referred to as a partially coherent codebook. A precoding matrix whose elements in each column are not all zeros may be called a fully coherent codebook.

Note that in this disclosure, a partially coherent codebook is designated by DCI for codebook-based transmission for UEs configured with a partially coherent codebook subset (e.g., RRC parameter “codebookSubset”=“partialAndNonCoherent”). Among codebooks (precoding matrices) corresponding to TPMI, excluding codebooks corresponding to TPMI in which a UE configured with a non-coherent codebook subset (e.g., RRC parameter “codebookSubset” = “nonCoherent”) is designated (ie, TPMI=4 to 11 codebooks for single layer transmission with 4 antenna ports).

Note that in this disclosure, a fully coherent codebook is designated by DCI for codebook-based transmission for UEs configured with a fully coherent codebook subset (e.g., RRC parameter “codebookSubset”=“fullyAndPartialAndNonCoherent”). Among codebooks (precoding matrices) corresponding to TPMI, excluding codebooks corresponding to TPMI in which a UE configured with a partially coherent codebook subset (e.g., RRC parameter “codebookSubset”=“partialAndNonCoherent”) is designated (ie, TPMI=12 to 27 codebooks for single layer transmission with 4 antenna ports).

(UE capability for full power transmission)
Even with codebooks, it is preferable to have full power UL transmissions properly. For this reason, NR considers UE capabilities related to codebook-based full-power UL transmissions with multiple Power Amplifiers (PAs). In previous NR discussions, the following UE Capabilities 1-3 have been proposed:
- UE capability 1: supports (or has) a PA (full rated PA) capable of outputting the maximum rated power in each transmission chain (Tx chain),
UE capability 2: none of the transmit chains support full-rated PA;
• UE Capability 3: A subset (part) of the transmit chain supports full-rated PA.

Note that a UE having at least one of said UE capabilities 1-3 may imply that it supports full power for UL transmission. The UE may report capability information to the network (eg, base station) indicating that it supports UL full power transmission capability, apart from UE capabilities 1-3. The UE may be configured by the network to support full power transmission.

The UE capability 1/2/3 may be read as UE capability 1/2/3 for full power transmission, full power transmission type 1/2/3, power allocation type 1/2/3, etc., respectively. In the present disclosure, types, modes, capabilities, etc. may be read interchangeably. Also, in this disclosure, 1/2/3 may be read as any set of numbers or letters such as A/B/C.

FIG. 2 is a diagram showing an example of a UE configuration assumed by UE capabilities 1-3 related to full power transmission. FIG. 2 simply shows only PAs and transmission antenna ports (which may be read as transmission antennas) as the configuration of the UE. An example in which the number of PAs and transmission antenna ports is four is shown, but the present invention is not limited to this.

P indicates the UE maximum output power [dBm], and _PPA indicates the PA maximum output power [dBm]. Note that P may be, for example, 23 dBm for a power class 3 UE and 26 dBm for a power class 2 UE. Although the present disclosure assumes P _PA ≦P, embodiments of the present disclosure may be applied when P _PA >P.

A UE capability 1 configuration is assumed to be costly to implement, but allows full power transmission using one or more arbitrary antenna ports. The configuration of UE capability 2 includes only non-fully rated PAs and is expected to be inexpensive to implement, but since full power transmission cannot be performed using only one antenna port, the phase of the signal input to each PA, It is required to control the amplitude and the like.

The UE Capability 3 configuration is intermediate between the UE Capability 1 configuration and the UE Capability 2 configuration. Antenna ports capable of full power transmission (transmitting antennas #0 and #2 in this example) and antenna ports not capable of full power transmission (transmitting antennas #1 and #3 in this example) are mixed.

Note that the index, number, etc. of antenna ports capable of full-power transmission of UE capability 3 are not limited to this. Also, in this example, it is assumed that P _PA =P/2 for the non-fluted PA, but the value of P _PA is not limited to this.

By the way, it is considered that UEs supporting UE Capabilities 2 or 3 are configured in at least one of two modes (modes 1, 2) for full power transmission operation. Modes 1 and 2 may be referred to as operational modes 1, 2, etc., respectively.

Here, mode 1 is a mode in which the UE is configured such that one or more SRS resources included in one SRS resource set with usage "codebook" have the same number of SRS ports ( for example, which may be referred to as a first full power transmission mode). A UE operating in Mode 1 may transmit at full power using all antenna ports.

A UE operating in Mode 1 may be configured by the network to use a subset of TPMI that combines ports within one layer to achieve full power transmission. A new codebook subset may be introduced only for rank values that contain TPMI precoders corresponding to “fullyAndPartialAndNonCoherent” defined in Rel-15 NR and are not available for full power transmission.

On the other hand, mode 2 is a mode in which the UE is configured such that one or more SRS resources included in one SRS resource set with usage "codebook" have different numbers of SRS ports (e.g. , which may be referred to as a second full power transmission mode). A UE operating in Mode 2 may transmit at full power using some but not all antenna ports.

A UE operating in Mode 2 may transmit PUSCH and SRS in the same manner regardless of whether antenna virtualization is used. For Mode 2 UEs, the set of TPMIs to achieve full power transmission may be signaled to support more than 1 port SRS resources. In mode 2, 2 or 3 SRS resources may be configured for one SRS resource set (up to 2 in Rel-15 NR).

Mode 1 has the advantage over mode 2 that the size of the required SRI field is smaller (full power transmission is possible with one SRS resource).

Mode 2 has an advantage over mode 1 in that single-port transmission and multi-port transmission can be dynamically switched by DCI. Moreover, since full power transmission is possible with some antenna ports, for example, full power transmission can be performed using only antennas having a fully rated PA, or full power transmission can be performed using only coherent antennas.

A UE operating in mode 2 can dynamically change (switch) the number of ports used for PUSCH transmission by SRI of DCI. However, there are issues with port switching. The problem will be described below. We assume here that the UE is configured with the SRS resource set of FIG.

FIG. 3 is a diagram illustrating an example of an SRS resource set configured for a Mode 2 UE. This example shows one SRS resource set (SRS resource set #0) with codebook usage configured for the UE by higher layer signaling (eg, RRC signaling). SRS resource set #0 includes SRS resource #0 with one SRS port (nrofSRS-Ports=1) and SRS resource #1 with four SRS ports (nrofSRS-Ports=4). That is, SRS resource set #0 corresponds to mode 2.

Assume that SRS resource #0 corresponds to SRI #0 (eg, SRI field value=0) and SRS resource #1 corresponds to SRI #1.

4A and 4B are diagrams showing an example of a problem when the number of ports between PUSCHs is changed. As a case in which the SRS resource set #0 as shown in FIG. 3 is configured, for example, as shown in FIG. 4A, PUSCH is connected by multi-TRP.

Since TRP#0 is relatively close to the UE, the PUSCH for TRP#0 (PUSCH#0) may be transmitted on one antenna port. In this example, DCI#0 that schedules PUSCH#0 may indicate SRI#0 corresponding to one SRS port.

Since TRP#1 is relatively far from the UE, the PUSCH for TRP#1 (PUSCH#1) may be transmitted on multiple antenna ports. In this example, DCI#1 that schedules PUSCH#1 may indicate SRI#1 corresponding to four SRS ports.

In FIG. 4A, DCI#0 that schedules PUSCH#0 is transmitted from TRP#0, and DCI#1 that schedules PUSCH#1 is transmitted from TRP#1, but the present invention is not limited to this. Each DCI may be sent from either TRP.

FIG. 4B shows an example of a PUSCH timeline corresponding to each DCI. In this example, the UE receives DCI#0 in slot #0 and DCI#1 in slot #1. DCI#0 schedules PUSCH#0 to be transmitted in the second half of slot #1. DCI#1 schedules PUSCH#1 to be transmitted in all of slot #2.

The UE may perform full power PUSCH transmission based on the designated SRS resources (or SRS ports).

Since one port is used for transmission of PUSCH#0, ports unnecessary for transmission must be inactive when transmitting PUSCH#0 (the power may be switched off or unavailable). could be. On the other hand, since four ports are used for transmission of PUSCH#1, if there is a port that is not operating, it takes time to activate the port. If the time interval between PUSCH#0 and PUSCH#1 is short (there is no interval in FIG. 4B), PUSCH#1 may not be transmitted as scheduled.

Such a case in which PUSCHs corresponding to different numbers of SRS ports are dynamically designated has not yet been studied. Unless a method for dealing with this case is clearly defined, there is a risk that the UE will not be able to perform PUSCH transmission appropriately, and an increase in communication throughput will be suppressed.

Therefore, the present inventors came up with a control method for properly performing UL transmission.

Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. The wireless communication method according to each embodiment may be applied independently, or may be applied in combination.

Note that "antenna" and "antenna port" in the following embodiments may be read interchangeably.

In this disclosure, "full power" may be read as "power boosting", "maximum power", "enhanced power", "high power compared to Rel-15 UE", and the like.

Also, in this disclosure, having UE capability X (X=1, 2, 3) is interchangeable with reporting UE capability X, being able to perform full power transmission using the configuration of UE capability X, etc. may be

In the present disclosure, having a coherent capability (e.g., fully coherent, partially coherent, non-coherent) may be read interchangeably as reporting that capability, setting that coherence, and the like.

Also, a non-coherent UE, a partially coherent UE, and a fully coherent UE may be interchanged with a UE having non-coherent capabilities, a UE having partial coherent capabilities, and a UE having full coherent capabilities, respectively.

Also, a non-coherent UE, a partially coherent UE, and a fully coherent UE use codebook subsets of "nonCoherent", "partialAndNonCoherent", "fullyAndPartialAndNonCoherent", respectively. It may mean a UE configured in higher layers. Note that in the present disclosure, the codebook subset and codebook may be read interchangeably.

A non-coherent UE, a partially coherent UE, and a fully coherent UE may refer to a UE capable of transmitting with a non-coherent codebook, a partially coherent codebook, and a fully coherent codebook, respectively.

In the following embodiments, it is assumed that an SRS resource set whose usage is "codebook" is set, but the present invention is not limited to this. Usage = "codebook" in the present disclosure may be read as other usages (non-codebook, antenna switching, etc.).

The UEs in the following embodiments assume UEs that have reported information indicating support for full power UL transmissions, but may apply to UEs that do not report this. Also, the UE in each embodiment is assumed to be a UE configured with one or more SRS resource sets including multiple SRS resources corresponding to different numbers of SRS ports, but is not limited to this.

In addition, in the present disclosure, the same timeline as in FIG. 4B may be used in the following description, but the order of receiving DCI #0 and DCI #1 may be DCI #0 first, or DCI #1. may be first. That is, even in a case where DCI #1 is received before DCI #0 and PUSCH #1 corresponding to DCI #1 is transmitted after PUSCH #0 corresponding to DCI #0, each implementation of the present disclosure Morphology is applicable.

The number of SRS ports of the present disclosure may be given by a higher layer parameter nrofSRS-Ports that is set corresponding to SRS resources.

(Wireless communication method)
<First embodiment>
In the first embodiment, when the UE reports UE capability information indicating that it supports mode 2 to the network, or when mode 2 is configured, there is a guard period between PUSCHs can be assumed.

In addition, in the present disclosure, reporting UE capability information indicating that the UE supports mode 2 and that the UE is configured for mode 2 may be read interchangeably.

A guard period may also be called a non-transmission period, a PUSCH switching period, a port switching period, or the like.

It may be assumed that the UE does not transmit any signaling in the guard periods before and/or after the PUSCH. It should be noted that only a specific channel (for example, PUSCH) may be restricted in transmission during the guard period, and other signals (such as reference signals) may be allowed to be transmitted.

It may be assumed that the UE does not transmit any signal during the guard period in the slots where PUSCH is transmitted. Note that the guard period may span slots, or may exist in a slot adjacent to the slot in which the PUSCH is transmitted.

The UE may use the guard period to turn on (which may also be referred to as activation, activation, etc.) antenna ports to be used (or designated) for the next PUSCH.

FIG. 5 is a diagram illustrating an example of a guard period between PUSCHs according to the first embodiment. FIG. 5 is an example in which a guard period is introduced in FIG. 4B, and redundant description will not be repeated.

In FIG. 5, it is assumed that there is a guard period before PUSCH#1. Therefore, the UE controls not to transmit PUSCH#0 during the guard period. The position, length, designation method, etc. of the guard period will be described later.

Several embodiments are described below.
(Embodiment 1.1) When a UE is configured with mode 2 and multiple PUSCHs are scheduled with DCI format 0_1, a guard period is assumed between the multiple PUSCHs.
(Embodiment 1.2) When the UE is configured with mode 2 and multiple PUSCHs are scheduled with DCI formats 0_0 and 0_1 respectively, assume a guard period between the multiple PUSCHs.
(Embodiment 1.3) The UE is configured for mode 2 and multiple PUSCHs are scheduled with DCI format 0_1 and the number of SRS ports associated with the SRS resources specified by the SRI for the second PUSCH is , greater than the number of SRS ports for the first PUSCH, assume a guard period between the PUSCHs.

In other words, the UE schedules multiple PUSCHs based on the DCI format (for example, the type of DCI format. DCI format 0_0 or 0_1, etc.), the guard period to apply between the multiple PUSCHs can be judged.

In these embodiments, among the plurality of PUSCHs, the PUSCH that starts earlier in time is also expressed as the first PUSCH, and the PUSCH that starts later in time (newer) is also expressed as the second PUSCH. . Note that the first PUSCH and the second PUSCH may or may not overlap in time.

PUSCH scheduled by DCI format 0_1 may be read as configured grant PUSCH. In this case, the SRI included in DCI format 0_1 may be replaced with the SRI specified by the parameter "srs-ResourceIndicator" included in "ConfiguredGrantConfig".

[Embodiment 1.1]
Embodiment 1.1 assumes that the UE is configured with mode 2 and multiple PUSCHs are scheduled with DCI format 0_1.

In embodiment 1.1, the UE may determine the length of the guard period based on at least one (i.e., any or a combination thereof) of the following:
- one or both of the number of antenna ports for the first PUSCH and the number of antenna ports for the second PUSCH;
- one or both of the SubCarrier Spacing (SCS) for the first PUSCH and the SCS for the second PUSCH;
• One or both of the length of the first PUSCH (number of PUSCH symbols) and the length of the second PUSCH.

The correspondence relationship between these parameters and the length of the guard period may be defined in advance by specifications, or may be set in the UE by higher layer signaling. Also, the length of the guard period may be expressed in units of symbols, slots, seconds, or the like.

Note that the number of antenna ports for PUSCH may be specified by SRI. In the present disclosure, an example in which PUSCH is basically scheduled by DCI (SRI is included in the DCI) will be described, but PUSCH of the present disclosure may include configured grant PUSCH.

FIG. 6 is a diagram showing an example of the length of the guard period in embodiment 1.1. FIG. 6 shows the correspondence relationship between the combination of the number of SRS ports for the first PUSCH and the number of SRS ports for the second PUSCH and the length of the guard period (X symbols).

Note that the number of SRS ports for PUSCH may refer to the number of SRS ports associated with the SRS resources indicated by the SRI for PUSCH. Also, hereinafter, the X symbol may be read as a predetermined period length (for example, a guard period value set by higher layer signaling).

In FIG. 6, for example, when the number of SRS ports for the first PUSCH=1 and the number of SRS ports for the second PUSCH=4, the length of the guard period X=2 applied between these PUSCHs It is derived that

As shown in FIG. 6, the UE assumes that X=0 if the number of SRS ports for the first PUSCH≦the number of SRS ports for the second PUSCH, otherwise X>0. You may If the number of SRS ports for the first PUSCH ≤ the number of SRS ports for the second PUSCH, for example, it is assumed that at least part of the transmission antenna ports of the first PUSCH are used as the transmission antenna ports of the second PUSCH. This is because the guard period is unnecessary.

Even if the number of SRS ports for the first PUSCH ≤ the number of SRS ports for the second PUSCH, the transmission antenna port for the second PUSCH is different from the transmission antenna port for the first PUSCH. The UE may assume X>0 since it is preferable to have a guard period if the antenna port is assumed to be used.

An example in which the UE determines the length of the guard period based on the SCS is, for example, based on the SCS for the first or second PUSCH, X = 1 (when SCS = 15 kHz), X = 2 ( (when SCS=30 kHz), X=3 (when SCS=60 kHz), X=4 (when SCS=120 kHz), and so on. In the UE, the correspondence relationship as shown in FIG. 6 above is defined or set for each of the SCS value for the first PUSCH and the SCS value for the second PUSCH or a combination thereof. can be assumed.

As an example in which the UE determines the length of the guard period based on the number of PUSCH symbols, for example, if the number of symbols of the first or second PUSCH is a predetermined number (eg, 7 symbols) or more, X >0 may be assumed.

UE, the length of the guard period is the same as the threshold for antenna switching of SRS (minimum guard period Y (Y = 1 or 2 symbols) between SRS resources shown in 3GPP TS 38.214 Table 6.2.1.2-1) or derived based on that Y. For example, Y=1 (for SCS=15, 30, 60 kHz), Y=2 (for SCS=120 kHz), etc., and the length of the guard period X is such that X=Y (where SCS is SCS used for transmitting the first PUSCH or the second PUSCH).

<<MAC CE>>
The UE may be configured with the length of the guard period by higher layer signaling or may be activated with the guard period (or setting of the guard period) by MAC CE.

7A-7D are diagrams of an example MAC CE for guard period activation. Each example shows a bit string that constitutes MAC CE, each represented by 2 octets (8 bits×2=16 bits). Note that the number of bits of the MAC CE is not limited to this.

The MAC CE may include information such as the applicable serving cell ID (“Serving Cell ID” field), BWP ID (“BWP ID” field), GP (guard period) field, and the like. A reserved (“R”) field may also be included, which may mean reserved bits for future extensions. The GP field may also be referred to as a GP flag field, or the like.

The MAC CE of FIG. 7A includes a 1-bit GP field (GP). For example, if the GP field = 0, the UE may not expect a guard period between PUSCHs (it may assume guard period = 0, or no guard period is needed). If GP field = 1, the UE may assume that the guard period between PUSCH is X symbols. The value of X may be derived based on the correspondence relationship as described above, or may be set by higher layer signaling.

The MAC CE of FIG. 7B includes a 2-bit GP field (GP). For example, if GP field = {00}, the UE may not expect guard periods between PUSCHs. For GP field = {01}, {10}, {11}, the UE may assume that the guard period between PUSCH is X, X+1, X+2 symbols, respectively. The value of X may be derived based on the correspondence relationship as described above, or may be set by higher layer signaling. Also, the value of the offset to X, such as "+1", "+2", may be set by higher layer signaling.

The value of the guard period may be explicitly indicated by the MAC CE. For example, the MAC CE may indicate a guard period value for each SCS. The MAC CE in FIG. 7C includes multiple 2-bit GP fields (GP#0-#3). GP#0-#3 may correspond to different SCS guard periods. For example, GP#0, #1, #2 and #3 may correspond to GPs with SCS=15, 30, 60 and 120 kHz, respectively.

For the individual GP fields in FIG. 7C, GP fields = {00}, {01}, {10} and {11} imply guard period = 0, 1, 2 and 3 symbols respectively. good.

In view of the above, for example, {GP#3, GP#2, GP#1, GP#0}={00000001} means that guard period length=0 symbols (SCS=30, 60, 120 kHz), Guard period length = 1 symbol (for SCS = 15 kHz). Also, {GP#3, GP#2, GP#1, GP#0}={11111111} means guard period length=3 symbols (when SCS=15, 30, 60, 120 kHz). good too.

Although the GP fields are arranged as adjacent bits in FIG. 7C, they may be arranged as separate bits. For example, GP#0-#3 may be included in the 2nd-5th octets of MAC CE, respectively.

The MAC CE of FIG. 7D includes an 8-bit GP field (GP). For example, when a plurality of corresponding relationships between GP indices and guard period values are set by higher layer signaling, the GP field may indicate the GP index. The GP field may also include a field for each SCS as shown in FIG. 7C.

<<Position of guard period>>
In embodiment 1.1, the UE is configured such that during the guard period following the first PUSCH, the symbol of the second PUSCH (or any other symbol; the same substitutions may apply hereinafter) is transmitted. should not be expected. In other words, the UE may assume that the symbols of the second PUSCH are not scheduled to be transmitted during the guard period following the first PUSCH (with such scheduling restrictions).

In this case, the guard period corresponds to the period after the end of the last symbol of the first PUSCH. The UE may assume that the symbols of the second PUSCH in the guard period following the first PUSCH are punctured or rate matched.

In embodiment 1.1, the UE is transmitted a symbol of the first PUSCH (or any other symbol; the same translations may apply hereinafter) during the guard period before the second PUSCH. You don't have to expect it. In other words, the UE may assume that the symbols of the first PUSCH are not scheduled to be transmitted during the guard period before the second PUSCH (with such scheduling restrictions).

In this case, the guard period corresponds to the period before the beginning of the start symbol of the second PUSCH. The UE may assume that the symbols of the first PUSCH in the guard period before the second PUSCH are punctured or rate matched.

Note that the guard period may be defined by a combination of the period following the first PUSCH and the period preceding the second PUSCH. In this case, the UE may assume that both the first PUSCH symbol and the second symbol are punctured or rate matched.

8A and 8B are diagrams showing an example of positions of guard periods in Embodiment 1.1. FIGS. 8A and 8B are examples similar to FIG. 5, and redundant description will not be repeated.

In FIG. 8A, it is assumed that there is a guard period after the first PUSCH (PUSCH#0). In FIG. 8B, it is assumed that there is a guard period before the second PUSCH (PUSCH#1).

[Embodiment 1.2]
Embodiment 1.2 assumes that the UE is configured with Mode 2 and multiple PUSCHs are scheduled with DCI formats 0_0 and 0_1 respectively.

In embodiment 1.2, if the first PUSCH is scheduled with DCI format 0_0 and the second PUSCH is scheduled with DCI format 0_1, the UE determines the length of the guard period based on at least one of the following: can be judged.
- the number of antenna ports for the second PUSCH,
- SCS for the second PUSCH;
• The length of the second PUSCH.

The correspondence relationship between these parameters and the length of the guard period may be defined in advance by specifications, or may be set in the UE by higher layer signaling.

FIG. 9 is a diagram showing an example of the length of the guard period in embodiment 1.2. FIG. 9 shows the correspondence between the number of SRS ports for the second PUSCH and the length of the guard period (X symbols).

In FIG. 9, for example, when the number of SRS ports for the second PUSCH=4, it is derived that the length of the guard period X=2 applied between the first PUSCH and the second PUSCH.

An example in which the UE determines the length of the guard period based on the SCS is, for example, based on the SCS for the second PUSCH, X = 1 (when SCS = 15 kHz), X = 2 (when SCS = 30 kHz ), X=3 (when SCS=60 kHz), X=4 (when SCS=120 kHz), and so on. The UE may assume that the correspondence relationship shown in FIG. 9 above is defined or configured for each SCS value for the second PUSCH.

As an example in which the UE determines the length of the guard period based on the number of PUSCH symbols, for example, if the number of symbols of the second PUSCH is equal to or less than a predetermined number (eg, 7 symbols), X>0 It may be assumed that there are

UE, the length of the guard period is the same as the threshold for antenna switching of SRS (minimum guard period Y (Y = 1 or 2 symbols) between SRS resources shown in 3GPP TS 38.214 Table 6.2.1.2-1) or derived based on that Y. For example, Y=1 (for SCS=15, 30, 60 kHz), Y=2 (for SCS=120 kHz), etc., and the length of the guard period X is such that X=Y (where SCS is SCS used for transmission of the second PUSCH) may be derived.

In embodiment 1.2, if the first PUSCH is scheduled with DCI format 0_1 and the second PUSCH is scheduled with DCI format 0_0, the UE will set the length of the guard period to a predetermined value (e.g., 0). may be determined to be Since the PUSCH scheduled by DCI format 0_0 is transmitted with a single port, for example, assuming that at least part of the transmission antenna ports of the first PUSCH are used as the transmission antenna ports of the second PUSCH, the guard period is This is because it is unnecessary.

Note that, as described in Embodiment 1.1, the UE may assume that there is a guard period even in such a case. The predetermined value may be defined in advance by the specification, or may be set in the UE by higher layer signaling.

<<MAC CE>>
As also mentioned in embodiment 1.1, the UE may be configured with the length of the guard period by higher layer signaling, or the guard period (or configuration of the guard period) may be activated by the MAC CE. As for the MAC CE, etc., the configurations already described may be used, and redundant description will not be repeated.

<<Position of guard period>>
In embodiment 1.2, the UE may not expect the symbols of the second PUSCH to be transmitted during the guard period following the first PUSCH. In other words, the UE may assume that the symbols of the second PUSCH are not scheduled to be transmitted during the guard period following the first PUSCH (with such scheduling restrictions).

In this case, the guard period corresponds to the period after the end of the last symbol of the first PUSCH. The UE may assume that the symbols of the second PUSCH in the guard period following the first PUSCH are punctured or rate matched.

In embodiment 1.2, the UE may not expect the symbols of the first PUSCH to be transmitted during the guard period before the second PUSCH. In other words, the UE may assume that the symbols of the first PUSCH are not scheduled to be transmitted during the guard period before the second PUSCH (with such scheduling restrictions).

In this case, the guard period corresponds to the period before the beginning of the start symbol of the second PUSCH. The UE may assume that the symbols of the first PUSCH in the guard period before the second PUSCH are punctured or rate matched.

Note that the guard period may be defined by a combination of the period following the first PUSCH and the period preceding the second PUSCH. In this case, the UE may assume that both the first PUSCH symbol and the second symbol are punctured or rate matched.

10A and 10B are diagrams showing an example of positions of guard periods in Embodiment 1.1. 10A and 10B are examples similar to FIG. 5, so redundant description will not be repeated.

In FIG. 10A, the first PUSCH (PUSCH#0) is scheduled with DCI format 0_0 and the second PUSCH (PUSCH#1) is scheduled with DCI format 0_1. The UE may assume that there is a guard period after PUSCH#0 and/or before PUSCH#1 (after PUSCH#0 in FIG. 10A).

In FIG. 10B, the first PUSCH (PUSCH#0) is scheduled with DCI format 0_1 and the second PUSCH (PUSCH#1) is scheduled with DCI format 0_0. The UE may assume that there is no guard period between PUSCH#0 and PUSCH#1.

[Embodiment 1.3]
Embodiment 1.3 assumes that the UE is configured with mode 2 and multiple PUSCHs are scheduled with DCI format 0_1 and the number of SRS ports associated with the SRS resources specified by the SRI for the second PUSCH is , is greater than the number of SRS ports for the first PUSCH.

In embodiment 1.3, the UE may assume that there is a guard period of predetermined length between the first PUSCH and the second PUSCH. The predetermined length may be defined in advance by the specification, or may be set in the UE by higher layer signaling.

The UE determines that there is a guard period of a predetermined length between the first PUSCH and the second PUSCH when the SRS port for the first PUSCH is included in the SRS port for the second PUSCH. can be assumed.

For example, the number of SRS ports for the first PUSCH is 1, the number of SRS ports for the second PUSCH is 2 or 4, and the SRS port for the first PUSCH is the second PUSCH. The UE may assume that there is a guard period of predetermined length between the first PUSCH and the second PUSCH when included in the SRS port for the UE.

The number of SRS ports for the first PUSCH is 2, the number of SRS ports for the second PUSCH is 4, and the SRS port for the first PUSCH is the SRS port for the second PUSCH. , the UE may assume that there is a guard period of predetermined length between the first PUSCH and the second PUSCH.

In addition, when the SRS port for the first PUSCH is not included in the SRS port for the second PUSCH, the UE has a guard period of a predetermined length between the first PUSCH and the second PUSCH. can be assumed to exist.

Also, when the SRS port for the second PUSCH is not included or included in the SRS port for the first PUSCH, the UE may be configured to have a predetermined length between the first PUSCH and the second PUSCH. It may be assumed that there is a guard period of

<<Position of guard period>>
In embodiment 1.3, the UE may not expect the symbols of the second PUSCH to be transmitted during the guard period following the first PUSCH. In other words, the UE may assume that the symbols of the second PUSCH are not scheduled to be transmitted during the guard period following the first PUSCH (with such scheduling restrictions).

In this case, the guard period corresponds to the period after the end of the last symbol of the first PUSCH. The UE may assume that the symbols of the second PUSCH in the guard period following the first PUSCH are punctured or rate matched.

In embodiment 1.2, the UE may not expect the symbols of the first PUSCH to be transmitted during the guard period before the second PUSCH. In other words, the UE may assume that the symbols of the first PUSCH are not scheduled to be transmitted during the guard period before the second PUSCH (with such scheduling restrictions).

In this case, the guard period corresponds to the period before the beginning of the start symbol of the second PUSCH. The UE may assume that the symbols of the first PUSCH in the guard period before the second PUSCH are punctured or rate matched.

Note that the guard period may be defined by a combination of the period following the first PUSCH and the period preceding the second PUSCH. In this case, the UE may assume that both the first PUSCH symbol and the second symbol are punctured or rate matched.

11A-11C are diagrams showing an example of positions of guard periods in Embodiment 1.3. FIGS. 11A-11C are examples similar to FIG. 5, and redundant description will not be repeated. In this example, it is assumed that the SRS resource set of FIG. 3 is configured.

In FIG. 11A, DCI#0 that schedules the first PUSCH (PUSCH#0) indicates SRI#0, and DCI#1 that schedules the second PUSCH (PUSCH#1) indicates SRI#1. ing. In this case, the number of SRS ports for the first PUSCH is 1, the number of SRS ports for the second PUSCH is 4, and the number of SRS ports for the second PUSCH is the number for the first PUSCH. Since it is greater than the number of SRS ports, the UE may assume that there is a guard period after PUSCH#0 and/or before PUSCH#1 (after PUSCH#0 in FIG. 11A).

In FIG. 11B, DCI#0 that schedules the first PUSCH (PUSCH#0) indicates SRI#0, and DCI#1 that schedules the second PUSCH (PUSCH#1) indicates SRI#0. ing. In this case, the number of SRS ports for the first PUSCH is 1, the number of SRS ports for the second PUSCH is 1, and the number of SRS ports for the second PUSCH is the number for the first PUSCH. The UE may assume that there is no guard period between PUSCH#0 and PUSCH#1 since it is the same as the number of SRS ports.

In FIG. 11C, DCI#0 that schedules the first PUSCH (PUSCH#0) indicates SRI#1, and DCI#1 that schedules the second PUSCH (PUSCH#1) indicates SRI#2. ing. In this case, the number of SRS ports for the first PUSCH is 4, the number of SRS ports for the second PUSCH is 1, and the number of SRS ports for the second PUSCH is the number for the first PUSCH. Since it is less than the number of SRS ports, the UE may assume that there is no guard period between PUSCH#0 and PUSCH#1.

According to the first embodiment described above, the UE uses one SRS resource in an SRS resource set containing three or more SRS resources using an SRI field with a size larger than the SRI field of Rel-15 NR. can be suitably determined.

<Second embodiment>
The existing Rel-15 NR SRS resource set contains up to two SRS resources. Therefore, when using the existing Rel-15 NR SRS resource set when mode 2 is configured, the UE can only use one beam per number of SRS ports.

Therefore, the present inventors came up with the second embodiment.

In a second embodiment, it may be assumed that a UE configured with Mode 2 is configured with a specific SRS resource set that includes three or more SRS resources. The particular SRS resource set includes multiple SRS resources corresponding to different SRS port numbers, and may be an SRS resource set including multiple SRS resources for at least one SRS port number. When using such an SRS resource set, the UE can use multiple beams for each number of SRS ports.

In the second embodiment, it may be assumed that a UE configured with Mode 2 is configured with multiple SRS resource sets per use. Each SRS resource set may include up to two SRS resources, or may correspond to a specific SRS resource set as described above.

Several embodiments are described below.
(Embodiment 2.1) The UE assumes that the size of the SRI field is larger than that of Rel-15 NR.
(Embodiment 2.2) The UE assumes that the size of the SRI field is the same as or not larger than the SRI field of Rel-15 NR.

Note that in Rel-15 NR, the size of the SRI field is a maximum of 1 bit when codebook-based transmission (RRC parameter "txConfig" = 'codebook') is set, and non-codebook-based transmission (RRC parameter "txConfig" = 'codebook'). = 'nonCodebook'), the maximum is 2 bits.

Also, the UE of the second embodiment may be a UE set to mode 2 and codebook-based transmission, or a UE set to mode 2 and non-codebook-based transmission.

[Embodiment 2.1]
A UE configured with Mode 2 may determine that the size of the SRI field included in the DCI is X bits larger than the size of the existing SRI field.

For example, a UE configured for Mode 2 and codebook based transmission (RRC parameter “txConfig”='codebook') may determine that X=2. A UE configured for Mode 2 and non-codebook based transmission (RRC parameter “txConfig”='nonCodebook') may determine that X=3.

The value of X may be determined based on the number of SRS resources included in an SRS resource set for a predetermined application (for example, application = codebook), may be set by higher layer signaling, or may be set according to specifications. It may be predetermined.

Also, the value of X is determined based on the number of SRS ports corresponding to each SRS resource in the SRS resource set (which may also be referred to as the number _Nt of SRS ports available in the SRS resource set). may For example, it may be obtained by X= _Nt .

If the SRS resource set includes an SRS resource with one SRS port and an SRS resource with two SRS ports, it may be determined that N _t =2. Also, if the SRS resource set includes an SRS resource with one SRS port, an SRS resource with two SRS ports, and an SRS resource with four SRS ports, it may be determined that N _t =3.

The UE may determine SRS resources based on the value of the SRI field. The value of the SRI field may directly indicate the SRS resource index, or the SRS resource index may be derived from the value of the SRI field based on a predetermined correspondence relationship.

12A and 12B are diagrams illustrating an example of an SRS resource set according to Embodiment 2.1. FIG. 12A corresponds to N _t =2 and FIG. 12B corresponds to N _t =3. In this example, SRS resource set #0 is configured to include two SRS resources per SRS port.

SRI field values arranged in ascending order (for example, {00, 01, 10, 11} in FIG. 12A) correspond to SRS resource IDs arranged in ascending order (for example, {#0, #1, #2, #3 in FIG. 12A). }), respectively.

The SRI field values arranged in ascending order may respectively correspond to the SRS resource IDs arranged in descending order.

The SRI field values arranged in ascending order may respectively correspond to the numbers of SRS ports (and corresponding SRS resources) arranged in ascending or descending order.

The SRI field values arranged in ascending order may correspond to the SRS port numbers (the corresponding SRS resources) arranged in ascending or descending order, and the SRS resource IDs arranged in ascending or descending order for the same SRS port numbers, respectively. .

For example, as shown in FIG. 12B, the SRI field values arranged in ascending order (eg, {000, 001, 010, 011, 100, 101} in FIG. 12B) are arranged in ascending order of SRS port number, and the same SRS port number may correspond to the SRS resource IDs arranged in ascending order. In FIG. 12B, for SRS port number=1, SRS resource #0 with a smaller SRS resource ID corresponds to SRI={000}, and SRS resource #1 with a larger SRS resource ID corresponds to SRI={001}. .

[Embodiment 2.2]
A UE configured with Mode 2 may assume that the size of the SRI field included in the DCI is equal to or less than the size of the existing SRI field.

<<When a specific SRS resource set including three or more SRS resources is configured>>
In embodiment 2.2, a UE configured with an SRS resource set including three or more (in other words, more than two) SRS resources by RRC signaling uses MAC CE to set two SRS resource sets for one SRS resource set. Up to 10 SRS resources may be activated.

The UE may determine one SRS resource from up to two activated SRS resources based on the SRI field included in the DCI. The UE may assume that no SRI is signaled if only one SRS resource is activated, or may ignore the signaled SRI.

The MAC CE may specify an SRS resource ID to activate or deactivate. The MAC CE may be called an SRS resource activation/deactivation MAC CE (SRS resource activation/deactivation MAC CE) or the like.

13A-13C are diagrams illustrating an example of MAC CE according to Embodiment 2.2. In this example, it is assumed that the SRS resource set in FIG. 13A has been configured (the same SRS resource set as in FIG. 12A).

FIG. 13B shows a bit string forming the MAC CE. Note that the number of MAC CE bits is not limited to this.

The MAC CE may include information such as the Serving Cell ID ("Serving Cell ID" field) to which it applies, the BWP ID ("BWP ID" field), the SRS Resource ID field associated with a specific SRS port number, and so on. A reserved (“R”) field may also be included, which may mean reserved bits for future extensions.

The MAC CE of FIG. 13B includes SRS resource ID fields for smaller SRS port numbers and SRS resource ID fields for larger SRS port numbers as SRS resource ID fields associated with specific SRS port numbers. there is Under the configuration of FIG. 13A, the SRS resource ID field for smaller SRS port number corresponds to SRS resource ID with SRS port number=1, and the SRS resource ID field for larger SRS port number is SRS port number=4. corresponds to the SRS resource ID of

FIG. 13C shows an example of identifying SRS resources activated by a MAC CE by a 1-bit SRI. In this example, the MAC CE of FIG. 13B activates SRS resource ID #1 as the SRS resource ID for the smaller number of SRS ports and activates SRS resource ID #2 as the SRS resource ID for the larger number of SRS ports. Assume that

For example, SRI={0} indicates SRS resource ID #1 corresponding to a smaller SRS resource ID among activated SRS resource IDs, and SRI={1} corresponds to a larger SRS resource ID. SRS resource ID #1 may be indicated.

The SRS resource ID field associated with a specific SRS port number may be represented by multiple bits (eg, 6 bits) as shown in FIG. 13B, or may be represented by 1 bit. When represented by 1 bit, the field value '0' may indicate a smaller SRS resource ID among the SRS resource IDs associated with the specific SRS port number, and the field value '1' may indicate the specific SRS. Among SRS resource IDs associated with the number of ports, a larger SRS resource ID may be indicated.

14A-14C are diagrams illustrating another example of MAC CE according to Embodiment 2.2. In this example, it is assumed that the SRS resource set in FIG. 14A has been configured (the same SRS resource set as in FIG. 12A).

FIG. 14B shows a bit string forming the MAC CE. FIG. 14B is similar to FIG. 13B, except that the SRS resource ID field associated with each particular SRS port number is represented by 1 bit.

In this example, the SRS resource ID field for a smaller number of SRS ports={0} indicates the smaller ID (SRS resource ID #0) among the SRS resource IDs with the number of SRS ports=1, and the field={1 } indicates a larger ID (SRS resource ID #1) among the SRS resource IDs with the number of SRS ports=1.

In this example, the SRS resource ID field for a larger number of SRS ports={0} indicates the smaller ID (SRS resource ID #2) among the SRS resource IDs with the number of SRS ports=4, and the field={1 } indicates a larger ID (SRS resource ID #3) among the SRS resource IDs with the number of SRS ports=4.

FIG. 14C shows an example of identifying SRS resources activated by MAC CE by 1-bit SRI. In this example, the MAC CE of FIG. 14B activates SRS resource ID #1 as the SRS resource ID for the smaller number of SRS ports and activates SRS resource ID #2 as the SRS resource ID for the larger number of SRS ports. Assume that

For example, SRI={0} indicates SRS resource ID #1 corresponding to a smaller SRS resource ID among activated SRS resource IDs, and SRI={1} corresponds to a larger SRS resource ID. SRS resource ID #1 may be indicated.

<<When multiple SRS resource sets are configured for one application>>
In embodiment 2.2, a UE configured with multiple SRS resource sets for one use by RRC signaling may use MAC CE to activate one SRS resource set among the multiple SRS resource sets. good.

The UE may determine one SRS resource from up to two SRS resources included in the activated SRS resource set based on the SRI field included in the DCI.

The MAC CE may specify an SRS resource set ID to activate or deactivate. The MAC CE may be called an SRS resource set activation/deactivation MAC CE (SRS resource set Activation/Deactivation MAC CE) or the like.

In addition, in the case where the SRS resource set that can be activated includes more than two SRS resources, the MAC CE may also serve as the SRS resource activation/deactivation MAC CE as described above. That is, the MAC CE may specify the SRS resource set to be activated and the SRS resource to be activated within the SRS resource set.

15A and 15B are diagrams illustrating an example of MAC CE for SRS resource sets according to embodiment 2.2. In this example, it is assumed that the SRS resource set of FIG. 15A is configured. In this example, the UE is configured with multiple SRS resource sets including multiple SRS resources corresponding to different numbers of SRS ports (SRS resource sets #0 and #1).

FIG. 15B shows a bit string forming the MAC CE. Note that the number of MAC CE bits is not limited to this.

The MAC CE may include information such as the applicable serving cell ID (“Serving Cell ID” field), BWP ID (“BWP ID” field), SRS resource set ID field, and the like.

If the maximum number of SRS resource sets that can be configured is, for example, 16, the SRS resource set ID field may be 4 bits as shown in FIG. 15B.

Based on the SRI of the size of the SRI field of Rel-15 NR (eg, 1 bit for codebook-based transmission), the UE selects any SRS resource among the SRS resources activated by MAC CE for PUSCH transmission. It may be determined as an SRS resource.

For example, a UE with SRS resource set ID#1 activated by MAC CE in FIG. 15B indicates SRS resource #1 of SRS resource set ID#1 with SRI={0}, It may be determined to instruct SRS resource #5 of resource set ID #1.

Note that the SRS resource set to activate may be specified by a bitmap for the SRS resource set ID included in the MAC CE.

16A and 16B are diagrams illustrating another example of MAC CE for SRS resource sets according to embodiment 2.2. In this example, it is assumed that the SRS resource set of FIG. 15A is configured. In this example, the UE is configured with multiple SRS resource sets including multiple SRS resources corresponding to different numbers of SRS ports (SRS resource sets #0 and #1).

FIG. 15B shows a bit string forming the MAC CE. Note that the number of MAC CE bits is not limited to this.

The MAC CE may include information such as the applicable serving cell ID (“Serving Cell ID” field), BWP ID (“BWP ID” field), SRS resource set IDs field, and the like.

The SRS resource set IDs field may represent a bitmap of {S ₁₅ S ₁₄ S ₁₃ S ₁₂ S ₁₁ S ₁₀ S ₉ S 8 S ₇ S ₆ S ₅ S ₄ S ₃ S ₂ S ₁ S _{0 }} . Here, if some S _i indicates '1', the UE may determine that the SRS resource set ID #i is activated. Note that the correspondence relationship between the bitmap and the SRS resource set ID is not limited to this. Also, if there are more than 16 SRS resource sets that can be configured, the number of bits of the SRS resource set IDs field may be greater than 16.

For example, the SRS resource set IDs field={0000000100000001} may indicate to activate SRS resource sets #0 and #8. The SRS resource set IDs field = {0000000100000110} may indicate to activate SRS resource sets #1, #2 and #8.

The UE may determine any SRS resource included in the SRS resource set activated by MAC CE as the SRS resource for PUSCH transmission based on the SRI.

According to the second embodiment described above, the UE uses an SRI field of the same size as the SRI field of Rel-15 NR to select one SRS resource in an SRS resource set containing three or more SRS resources. can be determined to

<Others>
In the above-described embodiment, the description was made assuming two modes, but the present invention is not limited to this. For example, three or more modes may be defined.

Also, in each of the above-described embodiments, the UL transmission using the antenna port has been described assuming PUSCH, but in addition to or instead of PUSCH, full power transmission of at least one of other signals and channels may be controlled.

That is, the antenna port in each of the above-described embodiments, PUSCH (and PUSCH demodulation reference signal (DeModulation Reference Signal (DMRS)), phase tracking reference signal (Phase Tracking Reference Signal (PTRS))), uplink control channel ( Physical Uplink Control Channel (PUCCH), Physical Random Access Channel (PRACH), SRS, etc., at least one antenna port, and full power transmission is on at least one of these signals and channels. may be applied.

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

FIG. 17 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment; The wireless communication system 1 may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc. specified by the Third Generation Partnership Project (3GPP). .

The radio communication system 1 may also support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC is dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E -UTRA Dual Connectivity (NE-DC)), etc.

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

The wireless communication system 1 has dual connectivity between multiple base stations in the same RAT (for example, dual connectivity (NR-NR Dual Connectivity (NN-DC) in which both MN and SN are NR base stations (gNB) )) may be supported.

A wireless communication system 1 includes a base station 11 forming a macrocell C1 with a relatively wide coverage, and base stations 12 (12a-12c) arranged in the macrocell C1 and forming a small cell C2 narrower than the macrocell C1. You may prepare. A user terminal 20 may be located within at least one cell. The arrangement, number, etc. of each cell and user terminals 20 are not limited to the embodiment shown in the figure. Hereinafter, the base stations 11 and 12 are collectively referred to as the base station 10 when not distinguished.

A user terminal 20 may be connected to at least one of a plurality of base stations 10 . The user terminal 20 may utilize at least one of carrier aggregation (CA) using a plurality of component carriers (Component Carrier (CC)) and dual connectivity (DC).

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

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

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

A base station 10 may be connected to the core network 30 via other base stations 10 or directly. Core network 30 may include, for example, at least one of Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), and the like.

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

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

A radio access scheme may be referred to as a waveform. Note that in the radio communication system 1, other radio access schemes (for example, other single-carrier transmission schemes and other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.

In the radio communication system 1, as downlink channels, a downlink shared channel (Physical Downlink Shared Channel (PDSCH)) shared by each user terminal 20, a broadcast channel (Physical Broadcast Channel (PBCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)) or the like may be used.

Further, in the radio communication system 1, as uplink channels, an uplink shared channel (PUSCH) shared by each user terminal 20, an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)) or the like may be used.

User data, higher layer control information, System Information Block (SIB), etc. are transmitted by the PDSCH. User data, higher layer control information, and the like may be transmitted by PUSCH. Also, a Master Information Block (MIB) may be transmitted by the PBCH.

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

Note that DCI for scheduling PDSCH may be called DL assignment, DL DCI, etc., and DCI for scheduling PUSCH may be called UL grant, UL DCI, etc. FIG. PDSCH may be replaced with DL data, and PUSCH may be replaced with UL data.

A control resource set (COntrol REsource SET (CORESET)) and a search space may be used for PDCCH detection. CORESET corresponds to a resource searching for DCI. A search space corresponds to a search area and search method for PDCCH candidates. A CORESET may be associated with one or more search spaces. The UE may monitor CORESETs associated with certain search spaces based on the search space settings.

One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be referred to as a search space set. Note that "search space", "search space set", "search space setting", "search space set setting", "CORESET", "CORESET setting", etc. in the present disclosure may be read interchangeably.

By PUCCH, channel state information (Channel State Information (CSI)), acknowledgment information (for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK/NACK, etc.) and scheduling request (Scheduling Request ( SR)) may be transmitted. A random access preamble for connection establishment with a cell may be transmitted by the PRACH.

Note that, in the present disclosure, downlink, uplink, etc. may be expressed without "link". Also, various channels may be expressed without adding "Physical" to the head.

In the radio communication system 1, a synchronization signal (SS), a downlink reference signal (DL-RS), etc. may be transmitted. In the radio communication system 1, the DL-RS includes a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DeModulation Reference Signal (DMRS)), Positioning Reference Signal (PRS), Phase Tracking Reference Signal (PTRS), etc. may be transmitted.

The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may also be called SS/PBCH block, SS Block (SSB), and so on. Note that SS, SSB, etc. may also be referred to as reference signals.

Further, in the radio communication system 1, as the uplink reference signal (UL-RS), the reference signal for measurement (Sounding Reference Signal (SRS)), the reference signal for demodulation (DMRS), etc. are transmitted. good. Note that DMRS may also be called a user terminal-specific reference signal (UE-specific reference signal).

(base station)
FIG. 18 is a diagram illustrating an example of the configuration of a base station according to one embodiment. The base station 10 comprises a control section 110 , a transmission/reception section 120 , a transmission/reception antenna 130 and a transmission line interface 140 . One or more of each of the control unit 110, the transmitting/receiving unit 120, the transmitting/receiving antenna 130, and the transmission path interface 140 may be provided.

It should be noted that this example mainly shows the functional blocks characteristic of the present embodiment, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. A part of the processing of each unit described below may be omitted.

The control unit 110 controls the base station 10 as a whole. The control unit 110 can be configured from a controller, a control circuit, and the like, which are explained based on common recognition in the technical field according to the present disclosure.

The control unit 110 may control signal generation, scheduling (for example, resource allocation, mapping), and the like. The control unit 110 may control transmission/reception, measurement, etc. using the transmission/reception unit 120 , the transmission/reception antenna 130 and the transmission line interface 140 . The control unit 110 may generate data to be transmitted as a signal, control information, a sequence, etc., and transfer them to the transmission/reception unit 120 . The control unit 110 may perform call processing (setup, release, etc.) of communication channels, state management of the base station 10, management of radio resources, and the like.

The transceiver unit 120 may include a baseband unit 121 , a radio frequency (RF) unit 122 and a measurement unit 123 . The baseband section 121 may include a transmission processing section 1211 and a reception processing section 1212 . The transmitting/receiving unit 120 includes a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measuring circuit, a transmitting/receiving circuit, etc., which are explained based on common recognition in the technical field according to the present disclosure. be able to.

The transmitting/receiving section 120 may be configured as an integrated transmitting/receiving section, or may be configured from a transmitting section and a receiving section. The transmission section may be composed of the transmission processing section 1211 and the RF section 122 . The receiving section may be composed of a reception processing section 1212 , an RF section 122 and a measurement section 123 .

The transmitting/receiving antenna 130 can be configured from an antenna, such as an array antenna, described based on common understanding in the technical field related to the present disclosure.

The transmitting/receiving unit 120 may transmit the above-described downlink channel, synchronization signal, downlink reference signal, and the like. The transmitting/receiving unit 120 may receive the above-described uplink channel, uplink reference signal, and the like.

The transceiver 120 may form at least one of the transmit beam and the receive beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), or the like.

The transmission/reception unit 120 (transmission processing unit 1211) performs Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (for example, RLC retransmission control), Medium Access Control (MAC) layer processing (for example, HARQ retransmission control), etc. may be performed to generate a bit string to be transmitted.

Transmitting/receiving section 120 (transmission processing section 1211) performs channel coding (which may include error correction coding), modulation, mapping, filtering, and discrete Fourier transform (DFT) on a bit string to be transmitted. Processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, transmission processing such as digital-to-analog conversion, etc. may be performed to output the baseband signal.

The transmitting/receiving unit 120 (RF unit 122) may perform modulation to a radio frequency band, filter processing, amplification, and the like on the baseband signal, and may transmit the radio frequency band signal via the transmitting/receiving antenna 130. .

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

Transmitter/receiver 120 (reception processor 1212) performs analog-to-digital conversion, Fast Fourier Transform (FFT) processing, and Inverse Discrete Fourier Transform (IDFT) on the acquired baseband signal. )) processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing and PDCP layer processing. User data and the like may be acquired.

The transmitter/receiver 120 (measuring unit 123) may measure the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurement, Channel State Information (CSI) measurement, etc. based on the received signal. Measurement section 123, received power (eg, Reference Signal Received Power (RSRP)), received quality (eg, Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)) , signal strength (eg, Received Signal Strength Indicator (RSSI)), channel information (eg, CSI), etc. may be measured. The measurement result may be output to control section 110 .

The transmission path interface 140 transmits and receives signals (backhaul signaling) to and from devices included in the core network 30, other base stations 10, etc., and user data (user plane data) for the user terminal 20, control plane data, and the like. Data and the like may be obtained, transmitted, and the like.

In addition, the transmitter and receiver of the base station 10 in the present disclosure may be configured by at least one of the transmitter/receiver 120 , the transmitter/receiver antenna 130 and the transmission line interface 140 .

Note that the transmitting/receiving unit 120 includes information (for example, DCI, configured grant PUSCH setting information, etc.) for scheduling the first uplink shared channel (Physical Uplink Shared Channel (PUSCH)), and and information (same as above) that schedules a second PUSCH that starts later in time than the first PUSCH.

(user terminal)
FIG. 19 is a diagram illustrating an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control section 210 , a transmission/reception section 220 and a transmission/reception antenna 230 . One or more of each of the control unit 210, the transmitting/receiving unit 220, and the transmitting/receiving antenna 230 may be provided.

It should be noted that this example mainly shows the functional blocks that characterize the present embodiment, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. A part of the processing of each unit described below may be omitted.

The control unit 210 controls the user terminal 20 as a whole. The control unit 210 can be configured from a controller, a control circuit, and the like, which are explained based on common recognition in the technical field according to the present disclosure.

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

The transmitting/receiving section 220 may include a baseband section 221 , an RF section 222 and a measurement section 223 . The baseband section 221 may include a transmission processing section 2211 and a reception processing section 2212 . The transmitting/receiving unit 220 can be configured from a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measuring circuit, a transmitting/receiving circuit, etc., which are explained based on common recognition in the technical field according to the present disclosure.

The transmitting/receiving section 220 may be configured as an integrated transmitting/receiving section, or may be configured from a transmitting section and a receiving section. The transmission section may be composed of a transmission processing section 2211 and an RF section 222 . The receiving section may include a reception processing section 2212 , an RF section 222 and a measurement section 223 .

The transmitting/receiving antenna 230 can be configured from an antenna described based on common understanding in the technical field related to the present disclosure, such as an array antenna.

The transceiver 220 may receive the downlink channel, synchronization signal, downlink reference signal, etc. described above. The transmitting/receiving unit 220 may transmit the above-described uplink channel, uplink reference signal, and the like.

The transceiver 220 may form at least one of the transmit beam and the receive beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), or the like.

The transmitting/receiving unit 220 (transmission processing unit 2211) performs PDCP layer processing, RLC layer processing (eg, RLC retransmission control), MAC layer processing (eg, , HARQ retransmission control) and the like may be performed to generate a bit string to be transmitted.

The transmission/reception unit 220 (transmission processing unit 2211) performs channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), and IFFT processing on a bit string to be transmitted. , precoding, digital-analog conversion, and other transmission processing may be performed, and the baseband signal may be output.

Note that whether or not to apply the DFT process may be based on transform precoding settings. Transmitting/receiving unit 220 (transmission processing unit 2211), for a certain channel (for example, PUSCH), if transform precoding is enabled, the above to transmit the channel using the DFT-s-OFDM waveform The DFT process may be performed as the transmission process, or otherwise the DFT process may not be performed as the transmission process.

The transmitting/receiving unit 220 (RF unit 222) may perform modulation to a radio frequency band, filter processing, amplification, and the like on the baseband signal, and may transmit the radio frequency band signal via the transmitting/receiving antenna 230. .

On the other hand, the transmitting/receiving section 220 (RF section 222) may perform amplification, filtering, demodulation to a baseband signal, and the like on the radio frequency band signal received by the transmitting/receiving antenna 230. FIG.

The transmission/reception unit 220 (reception processing unit 2212) performs analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (error correction) on the acquired baseband signal. decoding), MAC layer processing, RLC layer processing, PDCP layer processing, and other reception processing may be applied to acquire user data and the like.

Transmitter/receiver 220 (measuring unit 223) may measure the received signal. For example, the measurement unit 223 may perform RRM measurement, CSI measurement, etc. based on the received signal. The measuring unit 223 may measure received power (eg, RSRP), received quality (eg, RSRQ, SINR, SNR), signal strength (eg, RSSI), channel information (eg, CSI), and the like. The measurement result may be output to control section 210 .

Note that the transmitter and receiver of the user terminal 20 in the present disclosure may be configured by at least one of the transmitter/receiver 220 and the transmitter/receiver antenna 230 .

In addition, the transmitting/receiving unit 220 includes information for scheduling the first physical uplink shared channel (PUSCH) (for example, DCI, configured grant PUSCH setting information, etc.) and time from the first PUSCH. and information (ditto) scheduling a second PUSCH to start at a later time.

The control unit 220 may assume that there is a guard period between the first PUSCH and the second PUSCH. The control unit 220 may assume that there is a guard period between the first PUSCH and the second PUSCH when a specific condition is satisfied. The specific conditions may correspond to the conditions described in the first embodiment above.

For example, the control unit 220 assumes a guard period between the first PUSCH and the second PUSCH when both the first PUSCH and the second PUSCH are scheduled by DCI format 0_1. may

The control unit 220 is associated with an SRS resource specified by a measurement reference signal (SRS) resource index (SRS Resource Index (SRI), SRS Resource Indicator (SRI)) for the second PUSCH. a guard period between the first PUSCH and the second PUSCH if the number of SRS ports associated with the SRS resource index for the first PUSCH is greater than the number of SRS ports associated with the SRS resource specified by the SRS resource index for the first PUSCH; can be assumed.

When the first PUSCH is scheduled according to DCI format 0_0 and the second PUSCH is scheduled according to DCI format 0_1, the control unit 220 sets a guard period between the first PUSCH and the second PUSCH. can be assumed.

The control unit 220 includes a plurality of SRS resources corresponding to different numbers of measurement reference signal (SRS) ports, and is configured with an SRS resource set including a plurality of SRS resources for at least one number of SRS ports. In some cases, up to two SRS resources may be activated based on a Medium Access Control (MAC) control element for activating SRS resources.

(Hardware configuration)
It should be noted that the block diagrams used in the description of the above embodiments show blocks in units of functions. These functional blocks (components) are implemented by any combination of at least one of hardware and software. Also, the method of realizing each functional block is not particularly limited. That is, each functional block may be implemented using one device physically or logically coupled, or directly or indirectly using two or more physically or logically separated devices (e.g. , wired, wireless, etc.) and may be implemented using these multiple devices. A functional block may be implemented by combining software in the one device or the plurality of devices.

where function includes judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, deem , broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc. Not limited. For example, a functional block (component) responsible for transmission may be referred to as a transmitting unit, transmitter, or the like. In either case, as described above, the implementation method is not particularly limited.

For example, a base station, a user terminal, or the like in an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. FIG. 20 is a diagram illustrating an example of hardware configurations of a base station and a 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, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like. .

In the present disclosure, terms such as apparatus, circuit, device, section, and unit can be read interchangeably. The hardware configuration of the base station 10 and the user terminal 20 may be configured to include one or more of each device shown in the figure, or may be configured without some devices.

For example, although only one processor 1001 is shown, there may be multiple processors. Also, processing may be performed by one processor, or processing may be performed by two or more processors concurrently, serially, or otherwise. Note that processor 1001 may be implemented by one or more chips.

Each function in the base station 10 and the user terminal 20, for example, by loading predetermined software (program) on hardware such as a processor 1001 and a memory 1002, the processor 1001 performs calculations, communication via the communication device 1004 and at least one of reading and writing data in the memory 1002 and the storage 1003 .

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

The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 to the memory 1002, and executes various processes according to these. As the program, a program that causes a computer to execute at least part of the operations described in the above embodiments is used. 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 similarly implemented.

Memory 1002 is a computer-readable storage medium, such as Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), or any other suitable storage medium. may be configured by one. The memory 1002 may also be called a register, cache, main memory (main storage device), or the like. The memory 1002 can store executable programs (program code), software modules, etc. for implementing a wireless communication method according to an embodiment of the present disclosure.

The storage 1003 is a computer-readable recording medium, such as a flexible disk, a floppy (registered trademark) disk, a magneto-optical disk (for example, a compact disk (Compact Disc ROM (CD-ROM), etc.), a digital versatile disk, Blu-ray disc), removable disc, hard disk drive, smart card, flash memory device (e.g., card, stick, key drive), magnetic stripe, database, server, or other suitable storage medium may be configured by Storage 1003 may also be called an auxiliary storage device.

The communication device 1004 is hardware (transmitting/receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also called a network device, a network controller, a network card, a communication module, or the like. The communication device 1004 includes, for example, a high frequency switch, duplexer, filter, frequency synthesizer, etc. in order to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). may be configured to include For example, the transmitting/receiving unit 120 (220), the transmitting/receiving antenna 130 (230), and the like described above may be realized by the communication device 1004. FIG. The transmitter/receiver 120 (220) may be physically or logically separated into a transmitter 120a (220a) and a receiver 120b (220b).

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

Devices such as the processor 1001 and the memory 1002 are connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between devices.

In addition, the base station 10 and the user terminal 20 include a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable gate array (FPGA), etc. It may be configured including hardware, and a part or all of each functional block may be realized using the hardware. For example, processor 1001 may be implemented using at least one of these pieces of hardware.

(Modification)
The terms explained in this disclosure and the terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol and signal (signal or signaling) may be interchanged. A signal may also be a message. A reference signal may be abbreviated as RS, and may also be called a pilot, a pilot signal, etc., depending on the applicable standard. A component carrier (CC) may also be called a cell, a frequency carrier, a carrier frequency, or the like.

A radio frame may consist of one or more periods (frames) in the time domain. Each of the one or more periods (frames) that make up a radio frame may be called a subframe. Furthermore, a subframe may consist of one or more slots in the time domain. A subframe may be a fixed time length (eg, 1 ms) independent of numerology.

Here, a numerology may be a communication parameter that applies to the transmission and/or reception of a signal or channel. Numerology, for example, subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure , a particular filtering process performed by the transceiver in the frequency domain, a particular windowing process performed by the transceiver in the time domain, and/or the like.

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

A slot may include multiple minislots. Each minislot may consist of one or more symbols in the time domain. A minislot may also be referred to as a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in time units larger than a minislot may be referred to as PDSCH (PUSCH) Mapping Type A. PDSCH (or PUSCH) transmitted using minislots may be referred to as PDSCH (PUSCH) mapping type B.

Radio frames, subframes, slots, minislots and symbols all represent units of time in which signals are transmitted. Radio frames, subframes, slots, minislots and symbols may be referred to by other corresponding designations. Note that time units such as frames, subframes, slots, minislots, and symbols in the present disclosure may be read interchangeably.

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

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

The TTI may be a transmission time unit of channel-encoded data packets (transport blocks), code blocks, codewords, or the like, or may be a processing unit of scheduling, link adaptation, or the like. Note that when a TTI is given, the time interval (for example, the number of symbols) in which transport blocks, code blocks, codewords, etc. are actually mapped may be shorter than the TTI.

Note that when one slot or one minislot is called a TTI, one or more TTIs (that is, one or more slots or one or more minislots) may be the minimum scheduling time unit. Also, the number of slots (the number of mini-slots) constituting the minimum time unit of the scheduling may be controlled.

A TTI having a time length of 1 ms may also be called a normal TTI (TTI in 3GPP Rel. 8-12), normal TTI, long TTI, normal subframe, normal subframe, long subframe, slot, and so on. A TTI that is shorter than a regular TTI may also be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a minislot, a subslot, a slot, and so on.

Note that the long TTI (e.g., normal TTI, subframe, etc.) may be replaced with a TTI having a time length exceeding 1 ms, and the short TTI (e.g., shortened TTI, etc.) is less than the TTI length of the long TTI and 1 ms A TTI having the above TTI length may be read instead.

A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers (subcarriers) in the frequency domain. The number of subcarriers included in the RB may be the same regardless of the neumerology, eg twelve. The number of subcarriers included in an RB may be determined based on neumerology.

Also, an RB may contain one or more symbols in the time domain and may be 1 slot, 1 minislot, 1 subframe or 1 TTI long. One TTI, one subframe, etc. may each be configured with one or more resource blocks.

In addition, one or more RB is a physical resource block (Physical RB (PRB)), sub-carrier group (Sub-Carrier Group (SCG)), resource element group (Resource Element Group (REG)), PRB pair, RB Also called a pair.

Also, a resource block may be composed of one or more resource elements (Resource Element (RE)). For example, 1 RE may be a radio resource region of 1 subcarrier and 1 symbol.

A Bandwidth Part (BWP) (which may also be referred to as a Bandwidth Part) represents a subset of contiguous common resource blocks (RBs) for a neuron on a carrier. good too. Here, the common RB may be identified by an RB index based on the common reference point of the carrier. PRBs may be defined in a BWP and numbered within that BWP.

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

At least one of the configured BWPs may be active and the UE may not expect to transmit or receive a given signal/channel outside the active BWP. Note that "cell", "carrier", etc. in the present disclosure may be read as "BWP".

It should be noted that the above structures such as radio frames, subframes, slots, minislots and symbols are only examples. For example, the number of subframes contained in a radio frame, the number of slots per subframe or radio frame, the number of minislots contained within a slot, the number of symbols and RBs contained in a slot or minislot, the number of Configurations such as the number of subcarriers and the number of symbols in a TTI, symbol length, cyclic prefix (CP) length, etc. can be varied.

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

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

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

Also, information, signals, etc. may be output from higher layers to lower layers and/or from lower layers to higher layers. Information, signals, etc. may be input and output through multiple network nodes.

Input/output information, signals, and the like may be stored in a specific location (for example, memory), or may be managed using a management table. Input and output information, signals, etc. may be overwritten, updated or appended. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to other devices.

Notification of information is not limited to the aspects/embodiments described in this disclosure, and may be performed using other methods. For example, the notification of information in the present disclosure includes physical layer signaling (e.g., downlink control information (DCI), uplink control information (Uplink Control Information (UCI))), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB), etc.), Medium Access Control (MAC) signaling), other signals or combinations thereof may be performed by

The physical layer signaling may also be called Layer 1/Layer 2 (L1/L2) control information (L1/L2 control signal), L1 control information (L1 control signal), and the like. RRC signaling may also be called an RRC message, and may be, for example, an RRC connection setup message, an RRC connection reconfiguration message, or the like. Also, MAC signaling may be notified using, for example, a MAC Control Element (CE).

In addition, notification of predetermined information (for example, notification of “being X”) is not limited to explicit notification, but implicit notification (for example, by not notifying the predetermined information or by providing another information by notice of

The determination may be made by a value (0 or 1) represented by 1 bit, or by a boolean value represented by true or false. , may be performed by numerical comparison (eg, comparison with a predetermined value).

Software, whether referred to as software, firmware, middleware, microcode, hardware description language or otherwise, includes instructions, instruction sets, code, code segments, program code, programs, subprograms, and software modules. , applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, and the like.

Software, instructions, information, etc. may also be sent and received over a transmission medium. For example, the software uses wired technology (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), etc.) and/or wireless technology (infrared, microwave, etc.) to access the website. , a server, or other remote source, these wired and/or wireless technologies are included within the definition of transmission media.

As used in this disclosure, the terms "system" and "network" may be used interchangeably. A “network” may refer to devices (eg, base stations) included in a network.

In the present disclosure, "precoding", "precoder", "weight (precoding weight)", "Quasi-Co-Location (QCL)", "Transmission Configuration Indication state (TCI state)", "spatial "spatial relation", "spatial domain filter", "transmission power", "phase rotation", "antenna port", "antenna port group", "layer", "number of layers", Terms such as "rank", "resource", "resource set", "resource group", "beam", "beam width", "beam angle", "antenna", "antenna element", "panel" are interchangeable. can be used as intended.

In the present disclosure, "Base Station (BS)", "Radio Base Station", "Fixed Station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "Access point", "Transmission Point (TP)", "Reception Point (RP)", "Transmission/Reception Point (TRP)", "Panel" , “cell,” “sector,” “cell group,” “carrier,” “component carrier,” etc. may be used interchangeably. A base station may also be referred to by terms such as macrocell, small cell, femtocell, picocell, and the like.

A base station may serve one or more (eg, three) cells. When a base station accommodates multiple cells, the overall coverage area of the base station can be partitioned into multiple smaller areas, each smaller area being a base station subsystem (e.g., a small indoor base station (Remote Radio Station)). Head (RRH))) may also provide communication services. The terms "cell" or "sector" refer to part or all of the coverage area of at least one of the base stations and base station subsystems that serve communication within such coverage.

In this disclosure, terms such as “Mobile Station (MS),” “user terminal,” “User Equipment (UE),” and “terminal” are used interchangeably. can be

Mobile stations include subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals. , a handset, a user agent, a mobile client, a client, or some other suitable term.

At least one of a base station and a mobile station may also be called a transmitting device, a receiving device, a wireless communication device, and so on. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, or the like. The mobile object may be a vehicle (e.g., car, airplane, etc.), an unmanned mobile object (e.g., drone, self-driving car, etc.), or a robot (manned or unmanned ). Note that at least one of the base station and the mobile station includes devices that do not necessarily move during communication operations. For example, at least one of the base station and mobile station may be an Internet of Things (IoT) device such as a sensor.

Also, the base station in the present disclosure may be read as a user terminal. For example, communication between a base station and a user terminal is replaced with communication between multiple user terminals (for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.) Regarding the configuration, each aspect/embodiment of the present disclosure may be applied. In this case, the user terminal 20 may have the functions of the base station 10 described above. Also, words such as "up" and "down" may be replaced with words corresponding to inter-terminal communication (for example, "side"). For example, uplink channels, downlink channels, etc. may be read as side channels.

Similarly, user terminals in the present disclosure may be read as base stations. In this case, the base station 10 may have the functions of the user terminal 20 described above.

In this disclosure, operations described as being performed by a base station may also be performed by its upper node in some cases. In a network that includes one or more network nodes with a base station, various operations performed for communication with a terminal may involve the base station, one or more network nodes other than the base station (e.g., Obviously, this could be done by a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc.) or a combination thereof.

Each aspect/embodiment described in the present disclosure may be used alone, may be used in combination, or may be used by switching according to execution. Also, the processing procedures, sequences, flowcharts, etc. of each aspect/embodiment described in the present disclosure may be rearranged as long as there is no contradiction. For example, the methods described in this disclosure present elements of the various steps using a sample order, and are not limited to the specific order presented.

Each aspect/embodiment described in this disclosure is applicable to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system ( 4G), 5th generation mobile communication system (5G), 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), IEEE 802.16 (WiMAX). 20, Ultra-WideBand (UWB), Bluetooth (registered trademark), and other appropriate wireless communication methods, and extended next-generation systems based on these. Also, multiple systems may be applied in combination (for example, a combination of LTE or LTE-A and 5G).

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

Any reference to elements using the "first," "second," etc. designations used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, references to 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.

The term "determining" as used in this disclosure may encompass a wide variety of actions. For example, "determining" includes judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring ( For example, looking up in a table, database, or another data structure), ascertaining, etc. may be considered to be "determining."

Also, "determining (deciding)" includes receiving (e.g., receiving information), transmitting (e.g., transmitting information), input, output, access ( accessing (e.g., accessing data in memory), etc.

Also, "determining" is considered to be "determining" resolving, selecting, choosing, establishing, comparing, etc. good too. That is, "determining (determining)" may be regarded as "determining (determining)" some action.

Also, "judgment (decision)" may be read as "assuming", "expecting", "considering", or the like.

“Maximum transmit power” in the context of this disclosure may mean the maximum value of transmit power, may mean the nominal UE maximum transmit power, or may refer to the rated maximum transmit power (the rated UE maximum transmit power).

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

In this disclosure, when two elements are connected, using one or more wires, cables, printed electrical connections, etc., and as some non-limiting and non-exhaustive examples, radio frequency domain, microwave They can be considered to be “connected” or “coupled” together using the domain, electromagnetic energy having wavelengths in the optical (both visible and invisible) domain, and the like.

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

Where "include," "including," and variations thereof are used in this disclosure, these terms are inclusive, as is the term "comprising." is intended. Furthermore, the term "or" as used in this disclosure is not intended to be an exclusive OR.

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

Although the invention according to the present disclosure has been described in detail above, it will be apparent to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in this disclosure. The invention according to the present disclosure can be implemented as modifications and changes without departing from the spirit and scope of the invention determined based on the description of the claims. Therefore, the description of the present disclosure is for illustrative purposes and does not impose any limitation on the invention according to the present disclosure.

Claims (3)

a receiving unit that receives information for scheduling a first physical uplink shared channel (PUSCH) and information for scheduling a second PUSCH that starts temporally later than the first PUSCH;
a control unit that assumes that there is a guard period between the first PUSCH and the second PUSCH ;
The control unit assumes a guard period between the first PUSCH and the second PUSCH when both the first PUSCH and the second PUSCH are scheduled with DCI format 0_1;
The control unit determines that the number of SRS ports associated with SRS resources specified by the measurement reference signal (SRS) resource index for the second PUSCH is equal to the number of SRS ports for the first PUSCH. A terminal that assumes a guard period between the first PUSCH and the second PUSCH if greater than the number of SRS ports associated with an SRS resource specified by a resource index. When the first PUSCH is scheduled according to DCI format 0_0 and the second PUSCH is scheduled according to DCI format 0_1, the control unit configures a guard period between the first PUSCH and the second PUSCH. 2. A terminal according to claim 1, characterized in that it assumes . receiving information to schedule a first Physical Uplink Shared Channel (PUSCH) and information to schedule a second PUSCH that starts temporally later than the first PUSCH;
and assuming that there is a guard period between the first PUSCH and the second PUSCH ;
the assuming step assumes a guard period between the first PUSCH and the second PUSCH when both the first PUSCH and the second PUSCH are scheduled with DCI format 0_1;
In the step of assuming, the number of SRS ports associated with the SRS resources specified by the measurement reference signal (SRS) resource index for the second PUSCH is equal to the number of SRS ports for the first PUSCH. A wireless communication method for a terminal, wherein a guard period is assumed between the first PUSCH and the second PUSCH when the number of SRS ports associated with an SRS resource specified by an SRS resource index is greater than the number of SRS ports.

Images