Terminal, wireless communication method, and base station

Abstract

A terminal according to one embodiment of the present disclosure includes a reception unit that receives a first setting indicating whether or not first transform precoding is effective for a first uplink shared channel based on dynamic grant, a second setting indicating whether or not second transform precoding is effective for a second uplink shared channel based on configured grant, and first downlink control information scheduling the first uplink shared channel and including a specific field; and a control unit that controls transmission of the first uplink shared channel based on the first setting and the downlink control information, the specific field being present in a case where the first setting indicates that the first transform precoding is effective, and the specific field being absent in a case where the first setting indicates that the first transform precoding is ineffective.

Description

TECHNICAL FIELD

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

[0002] In a Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) is standardized for the purpose of further high-speed data rates, low latency, and so on (Non-Patent Literature 1). Further, LTE-Advanced (3GPP Rel. 10-14) is standardized for the purpose of further large capacity, higher, and so on of LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9).

[0003] A subsequent system of LTE (for example, also referred to as a 5th generation mobile communication system (5G), 5G+, a 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 onwards, and so on) is also being studied.

[0004] Prior Art Documents

[0005] Non-Patent Literature

[0006] Non-Patent Literature 1: 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010 SUMMARY

[0007] PROBLEMS TO BE SOLVED BY THE INVENTION

[0008] In a future wireless communication system, a Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) waveform, which is a multicarrier waveform, is being studied in addition to a Discrete Fourier Transform-Spread-Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) waveform, which is a single-carrier waveform.

[0009] However, since the setting of the conventional waveform is performed by Radio Resource Control (RRC), reconfiguration of the RRC is required in order to switch the waveform. Thus, there is a concern that the overhead of signaling increases and the communication throughput decreases.

[0010] Therefore, an object of the present disclosure is to provide a terminal, a wireless communication method, and a base station capable of appropriately performing switching of a waveform.

[0011] Means for solving the problem

[0012] A terminal according to an aspect of the present disclosure includes a reception unit that receives a first setting indicating whether or not first transform precoding is valid for a first uplink shared channel based on dynamic grant and a second setting indicating whether or not second transform precoding is valid for a second uplink shared channel based on configured grant, and receives first downlink control information scheduling the first uplink shared channel and including a specific field; and a control unit that controls transmission of the first uplink shared channel based on the first setting and the downlink control information, the specific field being present in a case where the first setting indicates that the first transform precoding is valid, and the specific field being absent in a case where the first setting indicates that the first transform precoding is not valid.

[0013] Effects of the Invention

[0014] According to an aspect of the present disclosure, switching of a waveform can be appropriately performed. BRIEF DESCRIPTION OF DRAWINGS

[0015] Figure 1 is a diagram illustrating a DCI size of Option 1-1.

[0016] Figure 2 is a diagram illustrating a DCI size of Option 1-2.

[0017] Figure 3is a flowchart showing an example of the process of Embodiment 0.1.

[0018] Figure 4 is a flowchart showing an example of the process of Embodiment 0.2.

[0019] Figure 5 is a diagram showing definitions of PTRS-DMRS association and DMRS sequence initialization of a DCI field.

[0020] Figure 6 is a diagram showing an example of a configuration mode of useInterlacePUCCH-PUSCH, resourceAllocation, and RA type.

[0021] Figure 7 is a flowchart showing an example of the process of Embodiment 3.

[0022] Figure 8 is a diagram showing an example of a MAC payload.

[0023] Figure 9 is a diagram showing an example of the number of bits of a RAR grant field.

[0024] Figure 10 is a diagram showing an example of a value of a TPC command.

[0025] Figure 11 is a diagram showing an example of a Backoff Parameter value.

[0026] Figure 12 is a diagram showing an example of an antenna port field of a DCI format 0_1.

[0027] Figure 13 is a diagram showing an example of a configuration of a DMRS type in a case where dynamic waveform switching is configured.

[0028] Figure 14A and Figure 14B is a diagram showing an example of an interpretation method of a codepoint of a specific field of a DCI in a case where dynamic waveform switching is configured and a DMRS type 2 is configured.

[0029] Figure 15 is a diagram showing an example of an RRC IE related to Embodiment A1.

[0030] Figure 16 is a diagram showing an example of a DCI related to Embodiment A4.

[0031] Figure 17 FIG. 1 is a diagram illustrating an example of an outline configuration of a wireless communication system according to an embodiment.

[0032] Figure 18 FIG. 2 is a diagram illustrating an example of a configuration of a base station according to an embodiment.

[0033] Figure 19 FIG. 3 is a diagram illustrating an example of a configuration of a user terminal according to an embodiment.

[0034] Figure 20 FIG. 4 is a diagram illustrating an example of a hardware configuration of a base station and a user terminal according to an embodiment.

[0035] Figure 21 FIG. 5 is a diagram illustrating an example of a vehicle according to an embodiment. DETAILED DESCRIPTION

[0036] (CP-OFDM and DFT-s-OFDM)

[0037] In the uplink (UL) of a wireless communication system (e.g., NR), in addition to a Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) waveform as a multicarrier waveform, a Discrete Fourier Transform-Spread-Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) waveform as a single-carrier waveform is also supported. “Waveform” in the present disclosure indicates at least one of a CP-OFDM waveform (a waveform based on CP-OFDM), a DFT-s-OFDM waveform (a waveform based on DFT-s-OFDM).

[0038] CP-OFDM enables more flexible frequency resource allocation. For example, both contiguous Physical Resource Block (PRB) allocation and non-contiguous PRB allocation are allowed. In addition, contiguous PRB allocation is not limited to multiples of 2, 3, 5. In the case where CP-OFDM is applied, Frequency Division Multiplexing (FDM) can also be used in DeModulation Reference Signal (DMRS) and PUSCH.

[0039] DFT-s-OFDM (or, DFT-S-OFDM / DFTS-OFDM) has a large restriction on frequency resource allocation, but has a low peak to average power ratio (PAPR), and is suitable for a UE whose power is limited.

[0040] In addition, for a communication throughput not considering PAPR, CP-OFDM has a higher communication throughput than DFT-s-OFDM. For a communication throughput considering PAPP, in a case where SNR (MCS) is high (modulation and coding scheme is 16QAM or 64QAM), the communication throughput of CP-OFDM becomes a value higher than that of DFT-s-OFDM, but in a case where SNR (MCS) is low (modulation and coding scheme is QPSK), DFT-s-OFDM has a higher communication throughput than CP-OFDM. That is, a preferred waveform differs depending on SNR (MCS).

[0041] Generally, a network (NW) switches a waveform based on a signal to noise ratio (SNR). Switching of DFT-s-OFDM and CP-OFDM is switched by transform precoder "transformPrecoder" of uplink shared channel (Physical Uplink Shared Channel (PUSCH)) setting (PUSCH-Config) of radio resource control (RRC) signaling. CP-OFDM is applied in a case where transform precoder is disabled, and DFT-s-OFDM is applied in a case where transform precoder is enabled. Switching of the waveform requires reconfiguration of RRC. Thus, there is a concern that overhead of signaling increases and communication throughput decreases.

[0042] In order to control throughput more flexibly, it is considered to dynamically switch CP-OFDM and DFT-s-OFDM by DCI / MAC CE. However, for such dynamic switching, research has not progressed.

[0043] For example, in an existing specification (for example, 3GPP Rel. 16), as shown in (1) to (6) below, the size of some DCI fields of a DCI format (for example, DCI format 0_0 / 0_1 / 0_2) is affected by switching of the waveform.

[0044] (1) In the "Precoding information and number of layers" field, different tables are used for 2 waveforms.

[0045] (2) In the "Antenna ports" field, different tables are used for 2 waveforms.

[0046] (3) In the "DMRS sequence initialization" field, it becomes 0 bit in case of valid transform precoder, and 1 bit in case of invalid transform precoder.

[0047] (4) In the "PTRS-DMRS association" field, the DCI size is affected by the transform precoder.

[0048] (5) In the "Frequency domain resource assignment", the DCI size is different according to the resource allocation type. In addition, the supported resource allocation is different according to the waveform. CP-OFDM supports resource allocation type 0, 1, 2, and DFT-s-OFDM supports resource allocation type 1, 2.

[0049] (6) In the "Frequency hopping flag" field, the DCI size is different according to the resource allocation type. As described above, the supported resource allocation is different according to the waveform.

[0050] (Dynamic switching of deactivation and activation of transform precoder)

[0051] The UE can also receive a configuration indicating that the deactivation and activation of the transform precoder for PUSCH is dynamically switched by DCI / MAC CE. Also, the UE can also receive an indication indicating the activation or deactivation of the transform precoder for PUSCH by DCI / MAC CE. Hereinafter, the dynamic switching based on DCI / MAC CE is sometimes referred to simply as dynamic switching. In addition, the UE can also be pre-configured by higher layer signaling for the dynamic switching of the waveform / transform precoder (switching is possible). The dynamic switching of the transform precoder based on DCI / MAC CE is possible regardless of the presence or absence of the configuration.

[0052] For example, the dynamic waveform switching based on DCI signaling can be performed implicitly or explicitly. For example, a field of 1 bit indicating the CP-OFDM or DFT-s-OFDM waveform for PUSCH can be included in the DCI (explicit signaling). For example, the UE can decide / recognize the CP-OFDM or DFT-s-OFDM waveform for PUSCH according to a specific condition in the scheduling information or the like in the DCI (implicit signaling). In this case, the existing DCI format is not changed.

[0053] Alternatively, dynamic UL waveform switching based on MAC CE signaling can also be performed. For example, a 1-bit field (explicit signaling) indicating CP-OFDM or DFT-s-OFDM waveform for PUSCH can also be included in the MAC CE. Alternatively, the UE can also determine / identify CP-OFDM or DFT-s-OFDM for PUSCH based on an existing field of the MAC CE (implicit signaling).

[0054] The DCI format in the present disclosure can indicate, for example, DCI format 0_0 / 0_1 / 0_2, or other formats (e.g., DCI format 0_3 for notifying waveform switching). As the other formats, for example, a group common DCI such as DCI format 2_x can also be utilized. In this case, the waveform switching can also be applied after a certain time from when the UE receives the DCI format 2_x and transmits ACK.

[0055] The switching of the deactivation and activation of the transform precoder (switching of the waveform) in the present disclosure can also be waveform switching in the same BWP (switching of the waveform without switching of the BWP). For example, since different transform precoders can be set for each BWP, switching of the transform precoder by BWP switching can also be considered, but since a delay caused by BWP switching occurs, by performing the switching of the deactivation and activation of the transform precoder in the same BWP, the delay can be suppressed.

[0056] In the case where the deactivation and activation of the transform precoder for PUSCH by DCI / MAC CE dynamic switching is set, the UE can also receive an indication indicating the activation or deactivation of the transform precoder for PUSCH from the DCI / MAC CE, and based on the indication, switch the waveform (CP-OFDM / DFT-s-OFDM) for PUSCH.

[0057] The total DCI size of the DCI format can also be constant regardless of the deactivation and activation of the transform precoder. The size of the DCI format can also be set / determined by higher layer signaling (RRC). That is, the size of the DCI format can also be independent of the DCI / MAC CE.

[0058] However, in a part of the DCI fields, the size of each DCI field can also be different depending on the deactivation and activation of the transform precoder. The part of the DCI fields is, for example, "Precoding information and number of layers", "Antenna ports", "DMRS sequence initialization", "PTRS-DMRS association", "Frequency resource assignment", "Frequency hopping flag". For example, as shown in the existing specifications (1) to (6) described above, the DCI size can also be different.

[0059] [Option 1-1]

[0060] In a case where the dynamic switching of the transform precoder (DCI / MAC CE-based switching) for the PUSCH is configured to the PUSCH, the total size of the DCI format can also be the larger one between the size of each DCI format in a case where the transform precoder is inactive and the size of each DCI format in a case where the transform precoder is active, for each DCI format.

[0061] In a case where the transform precoder is deactivated / activated by the MAC CE, the UE can also read each DCI field from the least significant bit (Least Significant Bit (LSB)) according to the size of each DCI field. Alternatively, the UE can also read each DCI field from the most significant bit (Most Significant bit (MSB)).

[0062] Figure 1 is a diagram showing the DCI size of Option 1-1. According to Figure 1 , the number of DCI bits in a case where the transform precoder is inactive (the total of DCI Field #1 to #4) is 10 bits, and the number of DCI bits in a case where the transform precoder is active is 7 bits. In this case, as the DCI total size in a case where the dynamic switching of the transform precoder is configured, the larger DCI size, that is, 10 bits is used.

[0063] In a case where the dynamic switching of the transform precoder (DCI / MAC CE-based switching) for the PUSCH is configured to the PUSCH, the total size of the DCI format can also be the larger one between the size of each DCI format in a case where the transform precoder is inactive and the size of each DCI format in a case where the transform precoder is active, for each DCI format. Figure 1In the middle, the smaller DCI bits (DCI bits in the case where the transform precoder is valid) are mapped from the left side (the least significant bits) but can also be mapped from the right side (the most significant bits). That is, the UE can read each DCI field from the least significant bits or from the most significant bits.

[0064] In Option 1-1, the DCI total size can be reduced compared to Option 1-2 described later.

[0065] [Option 1-2]

[0066] Also, in the case where the dynamic switching of the transform precoder for the PUSCH is set to the PUSCH, for each DCI format, the total size of the DCI format is the total value of the larger size of the size of the DCI field in the case where the transform precoder is invalid and the size of the DCI field in the case where the transform precoder is valid, per field.

[0067] That is, in the case where the number of fields of a certain DCI format is set to N, the total size of the DCI format is calculated as follows.

[0068] Total size of the DCI format =∑(MAX (size of DCI field i in the case where the transform precoder is invalid, size of DCI field i in the case where the transform precoder is valid)) (i = 1 ~ N)

[0069] In the case where the transform precoder is deactivated / activated by the MAC CE, the UE can also read each DCI field from the least significant bits (LSB) according to the size of each DCI field. Alternatively, the UE can also read each DCI field from the most significant bits (MSB).

[0070] Figure 2 is a diagram showing the DCI size of Option 1-2. According to Figure 2 In the DCI field #1 (DCI Field #1), the larger size of the size of the DCI field in the case where the transform precoder is invalid (2 bits) and the size of the DCI field in the case where the transform precoder is valid (1 bit) is 2 bits. Similarly, for the DCI field #2 (DCI Field #2), the larger size is 3 bits, for the DCI field #3 (DCI Field #3), the larger size is 2 bits, and for the DCI field #4 (DCI Field #4), the larger size is 4 bits. By totaling these sizes (2 + 3 + 2 + 4 = 11), 11 bits are used as the DCI total size in the case where the dynamic switching of the transform precoder is set.

[0071] In Figure 2 In each field, a smaller DCI bit fills the mapping from the left side (the least significant bit) but can also fill the mapping from the right side (the most significant bit). That is, the UE can read each DCI field from the least significant bit or from the most significant bit.

[0072] In Figure 2 In the example, in the case where the transform precoder is invalid and in the case where it is valid, the bit of the start position of each field (the bit range for each field) is the same. For example, the start position of DCI field #1 is the 1st bit, the start position of DCI field #2 is the 3rd bit, the start position of DCI field #3 is the 6th bit, and the start position of DCI field #4 is the 8th bit. Thus, it is possible to make the detection processing of each field of the UE easy to perform.

[0073] In Option 1-2, even if the valid / invalid of the transform precoder is switched, the size of the detected DCI is the same, and thus it is possible to suppress an increase in the processing load of the UE.

[0074] (FDRA type)

[0075] In NR, as a Frequency Domain Resource Allocation (FDRA) type, the following three types of Type 0, Type 1, and Type 2 are supported.

[0076] Type 0: Bitmap-based allocation (i.e., can also be non-contiguous).

[0077] Type 1: Contiguous allocation based on a Resource Indication Value (RIV).

[0078] Type 2: Interlace configuration (for NR-unlicensed (NR-U)).

[0079] The applicability of each type depending on the PUSCH waveform can also be supported as follows.

[0080] Type 0: Only CP-OFDM can be applied.

[0081] Type 1: Can be applied to both CP-OFDM and DFTS-OFDM.

[0082] Type 2: Can be applied to both CP-OFDM and DFTS-OFDM.

[0083] In case that RRC parameter useInterlacePUCCH-PUSCH is not set, Type 0 or Type 1 is used according to RRC parameter resourceAllocation. In case of transmitting Type 1 UL data without grant, resourceAllocation is set to resourceAllocationType0 or resourceAllocationType1. In case of resourceAllocationType0 is set, Type 0 is used, in case of resourceAllocationType1 is set, Type 1 is used. In case of dynamicSwitch is set, Type 0 or Type 1 is indicated by scheduling DCI (MSB of FDRA). In case of useInterlacePUCCH-PUSCH is set, Type 2 is used.

[0084] (DMRS)

[0085] Front-loaded DMRS is the first (1st symbol or 1st adjacent symbol) DMRS for earlier demodulation. Additional DMRS can be configured by RRC for high speed mobile UE or high order modulation and coding scheme (MCS) / rank. The frequency location of additional DMRS is the same as front-loaded DMRS.

[0086] For time domain, DMRS mapping type A or B is configured. In DMRS mapping type A, DMRS position l_0 is counted by symbol index within a slot. l_0 is configured by parameter (dmrs-TypeA-Position) within MIB or common serving cell configuration (ServingCellConfigCommon). DMRS position 0 (reference point l) means the first symbol of a slot or each frequency hop. In DMRS mapping type B, DMRS position l_0 is counted by symbol index within PDSCH / PUSCH. l_0 is always 0. DMRS position 0 (reference point l) means the first symbol of PDSCH / PUSCH or each frequency hop.

[0087] DMRS position is specified by the specification, depending on the duration of PDSCH / PUSCH. The position of additional DMRS is fixed.

[0088] For the frequency domain, set (PDSCH / PUSCH) DMRS set type 1 or 2. DMRS set type 1 has a comb structure, which can be applied to both CP-OFDM (transport precoding = disabled) and DFT-S-OFDM (transport precoding = enabled). DMRS set type 1 maps a DMRS sequence to 1 subcarrier per 2 subcarriers in the frequency domain, so at most 2 DMRSs can be FDMed. DMRS set type 2 can be applied only to CP-OFDM. DMRS set type 2 maps a DMRS sequence to 2 consecutive subcarriers per 6 subcarriers in the frequency domain, so at most 3 DMRSs can be FDMed.

[0089] Set single-symbol DMRS or double-symbol DMRS.

[0090] Single-symbol DMRS is generally used (mandatory in Rel. 15). In single-symbol DMRS, the number of additional DMRS (symbols) is {0, 1, 2, 3}. Single-symbol DMRS supports both cases where frequency hopping is enabled and disabled. If the maximum number (maxLength) in the uplink DMRS setting (DMRS-UplinkConfig) is not set, single-symbol DMRS is used.

[0091] Double-symbol DMRS is used for more DMRS ports (especially MU-MIMO). In double-symbol DMRS, the number of additional DMRS (symbols) is {0, 1}. Double-symbol DMRS supports the case where frequency hopping is disabled. If the maximum number (maxLength) in the uplink DMRS setting (DMRS-UplinkConfig) is 2 (len2), it is determined by DCI or configured grant whether single-symbol DMRS or double-symbol DMRS is used.

[0092] According to the above, possible setting patterns of DMRS can consider the following combinations.

[0093] • DMRS set type 1, DMRS mapping type A, single-symbol DMRS

[0094] • DMRS set type 1, DMRS mapping type A, double-symbol DMRS

[0095] • DMRS set type 1, DMRS mapping type B, single-symbol DMRS

[0096] • DMRS configuration type 1, DMRS mapping type B, double-symbol DMRS

[0097] • DMRS configuration type 2, DMRS mapping type A, single-symbol DMRS

[0098] • DMRS configuration type 2, DMRS mapping type A, double-symbol DMRS

[0099] • DMRS configuration type 2, DMRS mapping type B, single-symbol DMRS

[0100] • DMRS configuration type 2, DMRS mapping type B, double-symbol DMRS

[0101] Multiple DMRS ports mapped to the same RE (time and frequency resources) are referred to as a DMRS code division multiplexing (CDM) group.

[0102] For DMRS configuration type 1 and single-symbol DMRS, 4 DMRS ports can be used. Within each DMRS CDM group, 2 DMRS ports are multiplexed by length-2 FD OCC. Between multiple DMRS CDM groups (2 DMRS CDM groups), 2 DMRS ports are multiplexed by FDM.

[0103] For DMRS configuration type 1 and double-symbol DMRS, 8 DMRS ports can be used. Within each DMRS CDM group, 2 DMRS ports are multiplexed by length-2 FD OCC and 2 DMRS ports are multiplexed by TD OCC. Between multiple DMRS CDM groups (2 DMRS CDM groups), 2 DMRS ports are multiplexed by FDM.

[0104] For DMRS configuration type 2 and single-symbol DMRS, 6 DMRS ports can be used. Within each DMRS CDM group, 2 DMRS ports are multiplexed by length-2 FD OCC. Between multiple DMRS CDM groups (3 DMRS CDM groups), 3 DMRS ports are multiplexed by FDM.

[0105] For DMRS configuration type 2 and double-symbol DMRS, 12 DMRS ports can be used. Within each DMRS CDM group, 2 DMRS ports are multiplexed by length-2 FD OCC and 2 DMRS ports are multiplexed by TD OCC. Between multiple DMRS CDM groups (3 DMRS CDM groups), 3 DMRS ports are multiplexed by FDM.

[0106] An example of DMRS mapping type B is shown here, but the same applies to DMRS mapping type A.

[0107] In the parameters for PDSCH DMRS (existing DMRS port table, Rel. 15 DMRS port table), DMRS ports 1000-1007 can be used for DMRS configuration type 1, and DMRS ports 1000-1011 can be used for DMRS configuration type 2.

[0108] In the parameters for PUSCH DMRS (existing DMRS port table, Rel. 15 DMRS port table), DMRS ports 0-7 can be used for DMRS configuration type 1, and DMRS ports 0-11 can be used for DMRS configuration type 2.

[0109] (Ports of reference signals)

[0110] For orthogonalization of MIMO layers and the like, a reference signal using multiple ports (for example, DeModulation Reference Signal (DMRS), CSI-RS) is used.

[0111] For example, for Single User MIMO (SU-MIMO), different DMRS ports / CSI-RS ports can also be configured per layer. For Multi User MIMO (MU-MIMO), different DMRS ports / CSI-RS ports can also be configured per layer within 1 UE and per UE.

[0112] In addition, if the number of CSI-RS ports is used that is greater than the number of layers used in data, more accurate channel state measurement can be performed based on the CSI-RS, and improvement in throughput is expected.

[0113] In Rel. 15 NR, DMRS of multiple ports is supported by using Frequency Division Multiplexing (FDM), Frequency Domain Orthogonal Cover Code (FD-OCC), Time Domain OCC (TD-OCC), and the like, with a maximum of 8 ports for type 1 DMRS (in other words, DMRS configuration type 1) and a maximum of 12 ports for type 2 DMRS (in other words, DMRS configuration type 2).

[0114] In Rel. 15 NR, as the above-described FDM, a mode of transmission frequencies in a comb shape (a resource set in a comb shape) is used. As the above-described FD-OCC, a cyclic shift (CS) is used. Further, the above-described TD-OCC can be applied only to a double-symbol DMRS.

[0115] The OCC of the present disclosure can also be mutually rewritten with orthogonal code, orthogonalization, cyclic shift, and the like.

[0116] In addition, the type of DMRS can also be referred to as a DMRS configuration (structure) type (DMRS configuration type).

[0117] In the DMRS, a DMRS that is subjected to resource mapping in units of 2 consecutive (adjacent) symbols can also be referred to as a double-symbol DMRS, and a DMRS that is subjected to resource mapping in units of 1 symbol can also be referred to as a single-symbol DMRS.

[0118] Any DMRS can be mapped to more than one symbol per 1 slot according to the length of a data channel. A DMRS that is mapped to the start position of a data symbol can also be referred to as a front-loaded DMRS, and a DMRS that is additionally mapped to a position other than this can also be referred to as an additional DMRS.

[0119] In the case of DMRS configuration type 1 and a single-symbol DMRS, a comb (Comb) and a CS can also be used for orthogonalization. For example, a maximum of 4 antenna ports (APs) can be supported by using 2 kinds of combs (Comb2+2CS), 2 kinds of CSs.

[0120] In the case of DMRS configuration type 1 and a double-symbol DMRS, a comb (Comb), a CS, and a TD-OCC can also be used for orthogonalization. For example, a maximum of 8 APs can be supported by using 2 kinds of Combs, 2 kinds of CSs, and a TD-OCC ({1, 1} and {1, -1}).

[0121] In the case of DMRS configuration type 2 and a single-symbol DMRS, an FD-OCC can also be used for orthogonalization. For example, a maximum of 6 APs can be supported by applying an orthogonal code (2-FD-OCC) to 2 resource elements (REs) that are adjacent to each other in the frequency direction.

[0122] In the case of DMRS configuration type 2 and double-symbol DMRS, FD-OCC and TD-OCC can also be used for orthogonalization. For example, a maximum of 12 APs can be supported by applying an orthogonal code (2-FD-OCC) to 2 REs adjacent in the frequency direction and applying TD-OCC ({1, 1} and {1, -1}) to 2 REs adjacent in the time direction.

[0123] Further, in Rel. 15 NR, a maximum of 32 ports are supported for a plurality of port CSI-RS by using FDM, Time Division Multiplexing (TDM), frequency domain OCC, time domain OCC, and the like. For orthogonalization of the CSI-RS, the same method as the above-described DMRS can also be applied.

[0124] In summary, the group of DMRS ports orthogonalized by FD-OCC / TD-OCC as described above is also referred to as a Code Division Multiplexing (CDM) group.

[0125] Different CDM groups are orthogonal because FDM is performed therebetween. On the other hand, within the same CDM group, the orthogonality of the applied OCC is sometimes destroyed due to channel variation or the like. In this case, if signals within the same CDM group are received at different reception powers, a near-far problem occurs, and there is a concern that the orthogonality cannot be guaranteed.

[0126] Here, the TD-OCC / FD-OCC of the DMRS of Rel. 15 NR is described. The DMRS mapped to a Resource Element (RE) can be equivalent to a sequence obtained by multiplying a DMRS sequence by a parameter (which can also be referred to as a sequence element or the like) w f (k') of the TD-OCC (which can also be referred to as a sequence element or the like) w t (l').

[0127] The TD-OCC and the FD-OCC of the DMRS of Rel. 15 NR are both equivalent to OCC with a sequence length (which can also be referred to as an OCC length) = 2. Therefore, the values that k' and l' can take are both 0 and 1. By multiplying this FD-OCC in units of RE, it is possible to multiplex 2-port DMRS using the same time and frequency resources (2 REs). If both the FD-OCC and the TD-OCC are applied, it is possible to multiplex 4-port DMRS using the same time and frequency resources (4 REs).

[0128] The aforementioned 2 Rel. 15 DMRS port tables for PDSCH (association of antenna port index (number) and parameter) correspond to DMRS configuration type 1 and type 2, respectively. In addition, p denotes the number of antenna ports, and Δ denotes a parameter for shifting (offsetting) frequency resources.

[0129] For example, for antenna ports 1000 and 1001, {w f (0), w f (1)} = {+1, +1} and {w f (0), w f (1)} = {+1, -1} are applied, respectively, so as to be orthogonalized using FD-OCC.

[0130] For antenna ports 1000-1001, antenna ports 1002-1003 (and antenna ports 1004-1005 in the case of type 2), different values of Δ are applied, so as to be applied FDM. Thus, antenna ports 1000-1003 (or 1000-1005) corresponding to single-symbol DMRS are orthogonalized using FD-OCC and FDM.

[0131] For antenna ports 1000-1003 of type 1, antenna ports 1004-1007, {w t (0), w t (1)} = {+1, +1} and {w t (0), w t (1)} = {+1, -1} are applied, respectively, so as to be orthogonalized using TD-OCC. Thus, antenna ports 1000-1007 (or 1000-1011) corresponding to double-symbol DMRS are orthogonalized using FD-OCC, TD-OCC, and FDM.

[0132] Only for CP-OFDM, it is under study to: (without increasing DMRS overhead,) specify a larger number of orthogonal DMRS ports for DL / UL MU-MIMO, design so as to be common between DMRS in DL and UL, up to 24 orthogonal DMRS ports, double the maximum number of orthogonal DMRS ports for both single-symbol DMRS and double-symbol DMRS for each DMRS configuration type that can be applied.

[0133] In Rel. 15, the following cases 1 to 4 can be set.

[0134] [Case 1] Single-symbol DMRS of DMRS configuration type 1

[0135] The total number of DMRS ports is (based on comb / FDM) 2 x (based on FD OCC) 2 = 4 ports.

[0136] [Case 2] Two-symbol DMRS of DMRS configuration type 1

[0137] The total number of DMRS ports is (based on comb / FDM) 2 x (based on FD OCC) 2 x (based on TD OCC) 2 = 8 ports.

[0138] [Case 3] One-symbol DMRS of DMRS configuration type 2

[0139] The total number of DMRS ports is (based on FDM) 3 x (based on FD OCC) 2 = 6 ports.

[0140] [Case 4] Two-symbol DMRS of DMRS configuration type 2

[0141] The total number of DMRS ports is (based on comb) 3 x (based on FD OCC) 2 x (based on TD OCC) 2 = 12 ports.

[0142] In Rel. 18, for cases 1, 2, 3, 4, it is being studied to increase the total number of DMRS ports to 2 times 8, 16, 12, 24, respectively.

[0143] In order to increase the number of DMRS ports, the following 5 options (DMRS port number increasing methods) are being studied.

[0144] < Option 1 >

[0145] • Introduction of a new OCC larger than the length of the existing OCC (e.g., 4 or 6).

[0146] In Option 1, the possibility of performance degradation in the case of a large delay spread, the possibility of scheduling restrictions, and backward compatibility, etc. are cited as research items.

[0147] < Option 2 >

[0148] • Use of TD-OCC on multiple DMRS symbols that are not continuous (e.g., TD-OCC on front-loaded DMRS / additional DMRS).

[0149] In Option 2, the possibility of performance degradation in the case of fast UE speed, the possibility of scheduling restrictions (example: application method of frequency hopping), the possibility of DMRS configuration being limited (example: the number of additional DMRS is limited), and backward compatibility, etc. are cited as research items.

[0150] < Option 3 >

[0151] • Increase the number of CDM groups (e.g., increase the number of combs / FDM).

[0152] In Option 3, the possibility of performance degradation in the case of large delay spread, and backward compatibility, etc. are cited as research items.

[0153] < Option 4 >

[0154] • Reuse symbols of additional DMRS to increase orthogonal DMRS ports.

[0155] In Option 4, the possibility of performance degradation in the case of fast UE speed, the possibility of DMRS configuration being limited (e.g., the number of additional DMRS is limited), and backward compatibility, etc. are cited as research items.

[0156] < Option 5 >

[0157] • Utilization of TD-OCC on discontinuous multiple DMRS symbols in combination with FD-OCC / FDM (reuse symbols of additional DMRS to improve channel estimation performance).

[0158] In Option 5, the possibility of performance degradation in the case of fast UE speed, the possibility of scheduling restriction (e.g., application method of frequency hopping), the possibility of DMRS configuration being limited (e.g., the number of additional DMRS is limited), and backward compatibility, etc. are cited as research items.

[0159] In Option 1, the new FD-OCC for DMRS of PDSCH / PUSCH for DMRS spreading type 1 can also follow at least one of the following several options.

[0160] < < Option 1-1 > > Apply a new FD-OCC of length 6 to 6 REs of DMRS within one PRB within one CDM group.

[0161] < < Option 1-2 > > Apply a new FD-OCC of length 4 to 4 REs of DMRS within one PRB, or across multiple PRBs, within one CDM group.

[0162] In Option 1, the new FD-OCC for DMRS of PDSCH / PUSCH for DMRS spreading type 2 applies a new FD-OCC of length 4 to 4 REs of DMRS within one PRB within one CDM group. For DMRS spreading type 2, a new FD-OCC of length 6 can also be supported.

[0163] In the present disclosure, the existing FD-OCC #0 = [+1 +1], the existing FD-OCC #1 = [+1 -1] can also be.

[0164] The new FD-OCC can also be any one of the following several OCCs.

[0165] [OCC1-1]

[0166] OCC of length 4 based on a 4-row 4-column Walsh matrix (sequence). For OCC index i = {0, 1, 2, 3}, 4 sequences are obtained by using cyclic shifts {i·0, i·π / 2, i·π, i·3π / 2}.

[0167] [OCC1-2]

[0168] OCC of length 4 based on cyclic shifts. For OCC index i = {0, 1, 2, 3}, 4 sequences are obtained by using cyclic shifts {i·0, i·π / 2, i·π, i·3π / 2}.

[0169] In OCC1-1 and OCC1-2, the first half and the second half of OCC #0, #1 (OCCs corresponding to OCC indexes 0, 1) of length 4 are each the same as OCC #0, #1 (OCCs corresponding to OCC indexes 0, 1) of length 2.

[0170] In the present disclosure, the OCC (FD-OCC / TD-OCC) corresponding to OCC index i can also be referred to as OCC #i.

[0171] A part of the plurality of sequences of the new FD-OCC can also be associated with the Rel.15 DMRS port index.

[0172] In the case of using FD-OCC of length 2, the Rel.15 DMRS port table for DMRS configuration type 1 and the Rel.15 DMRS port table for DMRS configuration type 2 can also be used.

[0173] The extended DMRS configuration type 1 uses the frequency domain configuration of the DMRS configuration type 1 and the new FD-OCC. The extended DMRS configuration type 2 uses the frequency domain configuration of the DMRS configuration type 2 and the new FD-OCC.

[0174] In the present disclosure, DMRS configuration type 1, DMRS type 1, DMRS type = 1, DMRS type (Type) 1 can also be mutually overwritten. In the present disclosure, DMRS configuration type 2, DMRS type 2, DMRS type = 2, DMRS type (Type) 2 can also be mutually overwritten.

[0175] In the present disclosure, the extended DMRS configuration Type 1, DMRS extension Type 1, DMRS extension Type = 1, DMRS eType1, Rel.18 DMRS Type 1 can also be mutually rewritten.

[0176] In the present disclosure, the DMRS maximum length, maxLength can also be mutually rewritten.

[0177] In the present disclosure, the existing FD-OCC, FD-OCC of length 2, Rel.15 FD-OCC, w f (k') can also be mutually rewritten. In each embodiment, the new FD-OCC, FD-OCC longer than 2, Rel.18 FD-OCC, w f (k') can also be mutually rewritten.

[0178] The Rel.18 DMRS port table can also indicate the DMRS port corresponding to the new FD-OCC (p is 0 or more). At least a part of the value of p in the Rel.18 DMRS port table can also be repeated with the value of p in the Rel.15 DMRS port table. The UE can also use the Rel.18 DMRS port table in the case where the use of the new FD-OCC is configured / indicated, and the UE can also use the Rel.15 DMRS port table in the case where the use of the new FD-OCC is configured / indicated.

[0179] For the DMRS port accompanying the new FD-OCC #0, 1 of the DMRS extension Type 1, the same DMRS port index as the Rel.15 DMRS port (DMRS ports 0 to 7) can also be used. For the DMRS port accompanying the new FD-OCC #2, 3, a different DMRS port index from the Rel.15 DMRS port (DMRS ports 8 to 15) can also be used.

[0180] For the DMRS port accompanying the new FD-OCC #0, 1 of the DMRS extension Type 2, the same DMRS port index as the Rel.15 DMRS port (DMRS ports 0 to 11) can also be used. For the DMRS port accompanying the new FD-OCC #2, 3, a different DMRS port index from the Rel.15 DMRS port (DMRS ports 12 to 23) can also be used.

[0181] (Analysis)

[0182] The setting of the waveform in the past is performed by Radio Resource Control (RRC), and thus, in order to switch the waveform, reconfiguration of RRC is required. Thereby, there is a concern that the overhead of signaling increases and the communication throughput decreases. Therefore, as described above, by performing dynamic switching of the transform precoder for PUSCH (switching based on DCI / MAC CE), it is possible to easily (quickly) implement switching of the waveform. However, in this case, as shown in the following problem points 0 to 4, there are points that are not clear with respect to various settings / controls.

[0183] Therefore, the inventors of the present application have conceived a terminal that appropriately dynamically switches deactivation and activation of the transform precoder for PUSCH (switching of the waveform).

[0184] Hereinafter, the embodiments related to the present disclosure will be described in detail with reference to the drawings. The wireless communication method related to each of the embodiments can be applied individually or in combination.

[0185] In the present disclosure, "A / B" and "at least one of A and B" can also be rewritten with each other. Furthermore, in the present disclosure, "A / B / C" can also mean "at least one of A, B, and C".

[0186] In the present disclosure, notification, activation, deactivation, indication (or indicate), selection (select), configuration, update, determination, and the like can also be rewritten with each other. In the present disclosure, support, control, controllable, operation, operable, and the like can also be rewritten with each other.

[0187] In the present disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher layer parameters, fields, Information Elements (IEs), configurations, and the like can also be rewritten with each other. In the present disclosure, Medium Access Control (MAC Control Element (CE)), update commands, activation / deactivation commands, and the like can also be rewritten with each other.

[0188] In the present disclosure, higher layer signaling can also be any one or a combination of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, and the like, for example.

[0189] In the disclosure, MAC signaling may, for example, also use a MAC control element (MAC Control Element (MAC CE)), a MAC protocol data unit (MAC Protocol Data Unit (PDU)), and the like. Broadcast information may, for example, also be a Master Information Block (MIB), a System Information Block (SIB), minimum system information (Remaining Minimum System Information (RMSI)), Other System Information (OSI), and the like.

[0190] In the disclosure, physical layer signaling may, for example, also be Downlink Control Information (DCI), Uplink Control Information (UCI), and the like.

[0191] In the disclosure, an index, an Identifier (ID), an indicator, a resource ID, and the like may be rewritten with each other. In the disclosure, a sequence, a list, a set, a group, a cluster, a subset, and the like may be rewritten with each other.

[0192] In the disclosure, application / use of CP-OFDM, transformPrecoder being Disabled (deactivated) may be rewritten with each other. Application / use of DFT-s-OFDM, transformPrecoder being Enabled (activated) may be rewritten with each other. TransformPrecoder being deactivated / activated, transformPrecoder being switched, switching a waveform (CP-OFDM / DFT-s-OFDM) may be rewritten with each other. PUSCH waveform, waveform, transformPrecoder may be rewritten with each other. CP-OFDM, CP-OFDM waveform may be rewritten with each other. DFT-s-OFDM, DFT-s-OFDM waveform may be rewritten with each other. Enabled, on may be rewritten with each other. Disabled, off may be rewritten with each other.

[0193] In the disclosure, being able to dynamically switch a PUSCH waveform, being configured to dynamically switch a PUSCH waveform, being configured a DWS, DWS being Enabled may be rewritten with each other.

[0194] In the disclosure, a DWS field, a DWS indicator, a DWS indication may be rewritten with each other.

[0195] In this disclosure, the DMRS type, the DMRS type within the uplink DMRS configuration (DMRS-Type within DMRS-UplinkConfig), and the DMRS configuration type can be interchanged. In this disclosure, DMRS type 1, the type that can configure DMRS from 1RB to 6RE in the frequency domain, can also be interchanged. In this disclosure, DMRS type 2, the type that can configure DMRS from 1RB to 4RE in the frequency domain, can also be interchanged.

[0196] In this disclosure, DMRS type 1 and enhanced DMRS type 1 (DMRS-eType1) can also be rewritten as each other. Similarly, DMRS type 2 and enhanced DMRS type 2 (DMRS-eType2) can also be rewritten as each other. In other words, implementations applicable to DMRS type 1 and 2 can also be applied to enhanced DMRS type 1 and 2.

[0197] (Wireless communication method)

[0198] As described above, the UE can also receive settings indicating the dynamic switching of the transform precoder for the PUSCH via the DCI / MAC CE for deactivation and activation. Furthermore, the UE can also receive instructions indicating the activation or deactivation of the transform precoder for the PUSCH via the DCI / MAC CE. That is, the UE can also dynamically switch the PUSCH waveform. In this case, at least one of the following implementation methods can be applied.

[0199] In this disclosure, at least one of the methods described above (dynamic switching of deactivation and activation of the transform precoder) can also be applied when the PUSCH waveform can be dynamically switched.

[0200] <Problem Point 0>

[0201] When the PUSCH waveform can be dynamically switched, the value set for the RRC parameter `transformPrecoder` and `maxRank` is unclear. For example, in `transformPrecoder`, it is expected to correspond to any of the following: valid (i.e., DFT-s-OFDM), invalid (i.e., CP-OFDM), or unrestricted. For example, the setting of the RRC parameter `transformPrecoder` affects the DCI value, and thus the UE's processing load and communication overhead; therefore, it is preferable to specify the value.

[0202] <Embodiment 0.1>

[0203] In a case where the PUSCH waveform can be dynamically switched, the UE can also apply the setting of any one of the following modes in the RRC parameter transformPrecoder.

[0204] [Mode 1]

[0205] In a case where the PUSCH waveform can be dynamically switched, the RRC parameter transformPrecoder can also be set to be Enabled. Thereby, the DCI size assumed by the UE becomes smaller. That is, the NW (base station, gNB) can set the DCI size to be small, and thus it is possible to suppress the communication overhead.

[0206] [Mode 2]

[0207] In a case where the PUSCH waveform can be dynamically switched, the RRC parameter transformPrecoder can also be set to be Disabled. Thereby, even if the PUSCH waveform is switched to DFT-s-OFDM, since the UE assumes the same DCI size as CP-OFDM, it is possible to reduce the processing load of the UE.

[0208] [Mode 3]

[0209] In a case where the PUSCH waveform can be dynamically switched, the RRC parameter transformPrecoder can also be ignored. That is, it is also possible to have no restriction of transformPrecoder.

[0210] Figure 3 is a flowchart showing an example of the processing of Embodiment 0.1. The UE receives the RRC parameter transformPrecoder set to be Enabled / Disabled in a case where a setting indicating that dynamic switching of the PUSCH waveform is possible is received (step S101), (step S102).

[0211] Although there are a plurality of transformPrecoders as the RRC parameter, the transformPrecoder referred to by the UE can also differ for each case (each timing). For example, the following Options 1 and 2 can also be applied. The processing of the following Options 1 and 2 can also be applied in a timing before the indication of the dynamic switching of the PUSCH waveform in a case where the dynamic switching of the PUSCH waveform is set.

[0212] [Option 1]

[0213] The UE can also refer / consider transformPrecoder within RRC IE (e.g., PUSCH-Config, or ConfiguredGrantConfig) corresponding to the transmitted PUSCH. This option can also be applied to the UE before dedicated (UE-specific) RRC configuration.

[0214] [Option 2]

[0215] It can also be that the UE refers / considers transformPrecoder within a specific RRC IE regardless of the type of PUSCH (e.g., msg3-transformPrecoder of RACH-ConfigCommon, etc.). This option can also be applied to the UE before dedicated (UE-specific) RRC configuration.

[0216] According to the present embodiment, for the RRC parameter transformPrecoder in the case where the PUSCH waveform can be dynamically switched, the value that can be explicitly configured, the operation of the UE can be clarified.

[0217] <Embodiment 0.2>

[0218] In the case where the PUSCH waveform can be dynamically switched, the UE can also receive a value / setting based on any one of the following modes / options as the RRC parameter maxRank (maximum rank). That is, for the value / setting of maxRank, the UE can also assume the application of any one of the following modes / options. The maxRank is a parameter indicating the maximum value of the transmission rank (layer) of UL (PUSCH). The UE controls the transmission of PUSCH based on the maxRank.

[0219] [Mode 1]

[0220] The setting of maxRank can also have no limit. That is, even in the case where the dynamic switching of the PUSCH waveform is configured, maxRank can be set to an arbitrary value.

[0221] [Mode 2]

[0222] maxRank can also be set to a specific value, or a value smaller than the specific value. The specific value can also be determined (fixed) by the specification, for example. Alternatively, the specific value can also be configured / indicated by RRC / MAC CE / DCI. For example, in the case where the dynamic switching of the PUSCH waveform is configured, maxRank (specific value) can also be 1.

[0223] In a case where the maxRank is limited, for example, if only 1 can be set to the maxRank, the bit width of the transmitted precoding matrix indicator (TPMI) is the same regardless of the waveform of the PUSCH. That is, the DCI size is the same, and thus it is possible to reduce the processing load of the UE.

[0224] Figure 4 is a flowchart showing an example of the process of Embodiment 0.2. Figure 4 An example of the above-described Mode 2 is shown. The UE receives a setting indicating that dynamic switching of the PUSCH waveform is possible (step S201), and receives a setting indicating a specific value, or a value smaller than the specific value, as the value of the RRC parameter maxRank (step S202).

[0225] According to the present embodiment, for the RRC parameter maxRank in a case where the PUSCH waveform can be dynamically switched, the value that can be definitely set is indicated.

[0226] <Problem Point 1>

[0227] In a case where the PUSCH waveform can be dynamically switched, it is not clear how to handle the DCI field that is sometimes present (1 bit or more) and sometimes not present (0 bit) depending on the waveform of the PUSCH. The DCI field is, for example, the PTRS-DMRS association and the DMRS sequence initialization.

[0228] Figure 5 is a diagram showing the definition of the PTRS-DMRS association and the DMRS sequence initialization of the DCI field. As Figure 5As shown, DMRS sequence initialization (DMRS sequence initialization) is 0 bit in case PTRS (PTRS-UplinkConfig) is not configured and CP-OFDM is applied (transform precoder is disabled), in case DFTS-OFDM is applied (if transform precoder is enabled), or in case maxRank = 1, otherwise it is 2 bit. DMRS sequence initialization (DMRS sequence initialization) is 0 bit in case DFTS-OFDM is applied, and 1 bit in case CP-OFDM is applied.

[0229] Embodiment 1

[0230] In case the PUSCH waveform is dynamically switchable and a specific waveform is indicated for the PUSCH, the UE can also process (contemplate) a specific field of the scheduling DCI for the PUSCH based on a specific rule.

[0231] The specific field of the DCI can also be at least one of a DeModulation Reference Signal (DMRS) sequence initialization (DMRS sequence initialization) field, a Phase Tracking Reference Signal (PTRS) - DMRS association (PTRS-DMRS association) field.

[0232] The specific rule can also be that the UE ignores the specific field of the DCI.

[0233] The specific waveform can also be DFT-s-OFDM or CP-OFDM.

[0234] For example, the UE receives a DCI, and in case the PUSCH waveform is dynamically switchable and DFT-s-OFDM is indicated for the PUSCH, the UE ignores at least one of the DMRS sequence initialization (DMRS sequence initialization) field and the PTRS-DMRS association (PTRS-DMRS association) field of the DCI.

[0235] Without being limited to the above examples, in case Figure 5In a case where the DMRS sequence initialization (DMRS sequence initialization) field or the PTRS-DMRS association (PTRS-DMRS association) field becomes 0 bits under the condition, the UE can also ignore the field. Thereby, it is possible to reduce the processing load of the UE.

[0236] In Embodiment 1, in a case where the PUSCH waveform is dynamically switched, the bit number of each DCI field / DCI overall size can also follow the rule in the case of CP-OFDM regardless of the accurate waveform used by the UE. Alternatively, the bit number of each DCI field / DCI overall size can also not follow the rule in the case of CP-OFDM.

[0237] <Question Point 2>

[0238] As explained in the above (FDRA type), type 0 RA cannot be used for DFT-s-OFDM, and thus, in a case where the PUSCH waveform is switched to DFT-s-OFDM, it is necessary to use type 1 or type 2. For example, it is preferable that an RRC parameter indicating the PUSCH waveform always corresponds to the setting / indication of the FDRA type. However, in a case where the PUSCH waveform is dynamically switched, the setting of the FDRA, the useInterlacePUCCH-PUSCH indicating the interleaving is not clear.

[0239] <Embodiment 2>

[0240] In a case where the PUSCH waveform can be dynamically switched, and a specific waveform is indicated to the PUSCH, the UE can also receive a specific field of the DCI corresponding to the scheduling of the PUSCH and a specific RRC parameter based on a specific rule (reception of the specific field of the DCI and the specific RRC parameter can also be assumed). The UE can also control the PUSCH transmission based on the received specific field of the DCI and the specific RRC parameter.

[0241] The specific field of the DCI can be the FDRA or the frequency hopping flag.

[0242] The specific RRC parameter can also be the resourceAllocation or the useInterlacePUCCH-PUSCH indicating the interleaving of the PUCCH and the PUSCH.

[0243] The specific waveform can also be DFT-s-OFDM or CP-OFDM.

[0244] The specific rule can also be that resourceAllocation is one of resourceAllcationType1 or dynamicSwitch. In the case where resourceAllocation is dynamicSwitch, the highest bit (Most Significant bit (MSB)) of FDRA must be "1". That is, Type 1 of FDRA must be indicated. This specific rule can be applied in the case where useInterlacePUCCH-PUSCH is not set.

[0245] The specific rule can also be that resourceAllocation is resourceAllcationType1.

[0246] The specific rule can also be that a frequency hopping flag is decided in accordance with at least one of resourceAllocation and FDRA based on the above specific rule.

[0247] The specific rule can also be that useInterlacePUCCH-PUSCH (use of interlacing for PUCCH and PUSCH) is set to be enabled (use of interlacing for PUCCH and PUSCH).

[0248] [Specific Example]

[0249] For example, in the case where the PUSCH waveform can be dynamically switched and the PUSCH is instructed DFT-s-OFDM, the UE can also receive (may also be assumed to receive) setting information (RRC parameter) indicating dynamic switching (dynamicSwitch) as resourceAllocation, and indication information (DCI) indicating Type 1 as FDRA. The UE can also control the PUSCH transmission based on the setting information and the indication information.

[0250] For example, in the case where the PUSCH waveform can be dynamically switched and the PUSCH is instructed DFT-s-OFDM, the UE can also receive (may also be assumed to receive) setting information (RRC parameter) indicating Type 1 (resourceAllcationType1) as resourceAllocation. The UE can also control the PUSCH transmission based on the setting information.

[0251] For example, in a case where the PUSCH waveform is dynamically switchable, and the PUSCH is instructed with the DFT-s-OFDM, the UE can also receive (may also be assumed to receive) setting information indicating that useInterlacePUCCH-PUSCH (use of interlacing for the PUCCH and the PUSCH) is enabled. The UE can also control the PUSCH transmission based on the setting information.

[0252] Figure 6 is a diagram illustrating an example of a setting pattern of useInterlacePUCCH-PUSCH, resourceAllocation, and RA type. In a case where dynamic waveform switching is possible, for Figure 6 The following (1) and (2) can also be applied to the setting pattern illustrated in

[0253] (1) It can also be that, in a case where the default value of transformPrecoder is invalid (CP-OFDM is instructed / used), the UE can expect any pattern, but in a case where it is valid (DFT-s-OFDM is instructed / used), patterns 1-1 and 1-3 cannot be applied.

[0254] (2) It can also be that, in a case where the default value of transformPrecoder is valid, the UE can expect to apply patterns other than 1-1 and 1-3 indicating type 0 DCI, but in a case where CP-OFDM is instructed / used, any pattern is expected.

[0255] The processing of the present embodiment can also be applied regardless of the waveform instructed to the PUSCH. That is, in a case where the PUSCH waveform is dynamically switchable, the UE can also control the above-described specific field of the DCI corresponding to the scheduling of the PUSCH and the above-described specific RRC parameter based on the above-described specific rule.

[0256] According to the present embodiment, even in a case where the PUSCH waveform is dynamically switched, it is possible to avoid a situation that becomes an error (for example, in a case where DFT-s-OFDM is applied, type 0 FDRA is set).

[0257] <Problem Point 3>

[0258] In a case where the PUSCH waveform can be dynamically switched, the kind of PUSCH to which the application can be applied is not clear. For example, it is not clear whether or not a message 3 (Msg3) / message A (msg3-TransformPrecoder / msgA-TransformPrecoder) can be applied as the PUSCH. In addition, it is not clear whether or not a CG-PUSCH (transformPrecoder of ConfiguredGrantConfig) can be applied as the PUSCH. In addition, in a case where the dynamic switching of the PUSCH waveform is supported for these PUSCHs, it is not clear what kind of processing is performed.

[0259] <Embodiment 3>

[0260] The UE can also apply the dynamic switching of the PUSCH waveform only to a specific kind of PUSCH. That is, the UE, in a case where a setting indicating the dynamic switching of the PUSCH waveform is received, can also perform control to dynamically switch only a specific kind of PUSCH based on the DCI / MAC CE. The specific kind of PUSCH may, for example, be at least one of the following (1) to (4).

[0261] (1) DCI grant (DG) -PUSCH (PUSCH scheduled by DCI).

[0262] (2) Type 1 configured grant (CG) -PUSCH (PUSCH transmission set by higher layer signaling).

[0263] (3) Type 2 CG-PUSCH (PUSCH transmission set by higher layer signaling and activated / deactivated by DCI).

[0264] (4) PUSCH scheduled by random access response (RAR) (message 3 PUSCH or message A PUSCH). The RAR can be an RAR of a contention-based random access (Contention based Random Access (CBRA)) or an RAR of a contention-free random access (Contention-Free Random Access (CFRA)). For example, in the CFRA, the base station (gNB) knows the UE and its channel state, and thus can appropriately adjust the waveform.

[0265] Figure 7is a flowchart showing an example of the process of Embodiment 3. The UE, in a case where a configuration indicating that dynamic switching of a PUSCH waveform is possible is received (step S301), performs control to dynamically switch the waveform of only a specific type of PUSCH based on DCI / MAC CE (step S302).

[0266] <Embodiment 4.1>

[0267] It is also possible to apply dynamic switching of the waveform of CG-PUSCH of Type 1 (PUSCH transmission set by higher layer signaling) and support at least one of the following (1-1) to (1-4). As a specific method of the following (1-1) to (1-4), the method of the above (dynamic switching of deactivation and activation of transform precoder) can also be applied.

[0268] (1-1) The UE can also receive explicit indication (explicit signaling) based on DCI indicating valid / invalid (DFT-s-OFDM / CP-OFDM) of transformPrecoder.

[0269] (1-2) The UE can also receive implicit indication (implicit signaling) based on DCI indicating valid / invalid (DFT-s-OFDM / CP-OFDM) of transformPrecoder.

[0270] (1-3) The UE can also receive explicit indication (explicit signaling) based on MAC CE indicating valid / invalid (DFT-s-OFDM / CP-OFDM) of transformPrecoder.

[0271] (1-4) The UE can also receive implicit indication (implicit signaling) based on MAC CE indicating valid / invalid (DFT-s-OFDM / CP-OFDM) of transformPrecoder.

[0272] The methods of (1-1) to (1-4) can also be applied to Type 1 CG-PUSCH separately from other types of PUSCH (Type 2 CG-PUSCH, DG-PUSCH). Alternatively, as the methods of (1-1) to (1-4), the same methods as those for other types of PUSCH can also be applied to Type 1 CG-PUSCH.

[0273] In the conventional Type 1 CG-PUSCH, DCI is not used in scheduling. Therefore, in the case where the above (1-1), (1-2) are applied, it is preferable to newly define DCI. For example, as the DCI of the above (1-1), (1-2), any one of the following (2-1), (2-2) can be applied.

[0274] (2-1) DCI that schedules unicast data of UL / DL can be applied. In addition, UL / DL-SCH actually scheduled by the DCI can not exist.

[0275] (2-2) DCI for scheduling other than unicast data can be applied. For example, in the case where group common DCI is used, the DCI can be applied.

[0276] According to the present embodiment, processing in the case where dynamic switching of the Type 1 CG-PUSCH waveform is explicitly applied can be clarified.

[0277] <Embodiment 4.2>

[0278] It can also be that, in the case where dynamic switching of the Type 2 CG-PUSCH (PUSCH transmission that is configured by higher layer signaling and activated / deactivated by DCI) waveform is applied, at least one of the methods of (1-1) to (1-4) of Embodiment 4.1 is supported.

[0279] The methods of (1-1) to (1-4) can be applied to the Type 2 CG-PUSCH separately from other types of PUSCH (Type 1 CG-PUSCH, DG-PUSCH). Alternatively, as the methods of (1-1) to (1-4), the same methods as those for other types of PUSCH can be applied to the Type 2 CG-PUSCH.

[0280] In the conventional Type 2 CG-PUSCH, DCI for activation / deactivation is used, and therefore the DCI can be reused. Specifically, as the DCI of the above (1-1), (1-2), any one of the following (2-1), (2-2) can be applied.

[0281] (2-1) DCI that schedules unicast data of UL / DL can be applied. In addition, UL / DL-SCH actually scheduled by the DCI can not exist. For example, DCI that activates / deactivates the Type 2 CG-PUSCH can be applied.

[0282] (2-2) DCI for scheduling other than unicast data can be applied. For example, in the case where group common DCI is used, the DCI can be applied.

[0283] According to the present embodiment, it is possible to explicitly apply the processing in the case of dynamic switching of the CG-PUSCH waveform of Type 2.

[0284] <Embodiment 5>

[0285] Also, dynamic switching of the Message 3 / Message A PUSCH (PUSCH scheduled by Random Access Response (RAR)) waveform can be applied, and at least one of the methods of (1-1) to (1-4) of Embodiment 4.1 can be supported. Alternatively, the following (1-5) can also be applied.

[0286] (1-5) The UE can also receive explicit / implicit indication based on RAR indicating valid / invalid (DFT-s-OFDM / CP-OFDM) of transformPrecoder.

[0287] The methods of (1-1) to (1-5) can also be applied to the Message 3 / Message A PUSCH separately from other types of PUSCH (Type 1 / Type 2 CG-PUSCH, DG-PUSCH). Alternatively, as the methods of (1-1) to (1-5), the same methods as those for other types of PUSCH can also be applied to the Message 3 / Message A PUSCH.

[0288] In the conventional Message 3 / Message A PUSCH, DCI for activation / deactivation is used, and thus this DCI can also be reused. Specifically, as the DCI of (1-1), (1-2) above, any one of the following (2-1), (2-2) can also be applied.

[0289] (2-1) DCI scheduling unicast data of UL / DL can also be applied. In addition, the UL / DL-SCH actually scheduled by the DCI can not exist. For example, the DCI can be DCI 1_0 having a Cyclic Redundancy Check (CRC) scrambled by a Random Access Radio Network Temporary Identifier (RNTI) or a Message B RNTI.

[0290] (2-2) DCI for scheduling other than unicast data can also be applied. For example, this DCI can also be applied in the case of using group common DCI.

[0291] For dynamic waveform switching of Msg3 / MsgA PUSCH, at least one of the following (3-1), (3-2) related to RAR-based indication can also be supported. The UE can also dynamically switch the waveform of Msg3 PUSCH or MsgA PUSCH based on at least one of the MAC subheader or MAC payload for RAR.

[0292] (3-1) It can also be that a reserved bit (R) of the MAC subheader / MAC payload for RAR is released to be used for dynamic waveform switching. For example, Figure 8 The "R" of the 1st octet of the MAC payload (i.e. next to the Timing Advance Command) shown can also indicate dynamic waveform switching.

[0293] (3-2) It can also be implicitly indicated based on Figure 9 the existing RAR grant field (UL Grant) shown. For example, in the case that the Modulation and Coding Scheme (MCS) in the UL Grant indicates a specific MCS, the validity / invalidity of transformPrecoder for Msg3 / MsgA PUSCH can also be set. For example, in the case that the value corresponding to the TPC command for Msg3 PUSCH in the UL Grant is a specific value (e.g. 0), or is greater than / less than a specific threshold value, the validity / invalidity of transformPrecoder for Msg3 / MsgA PUSCH can also be set. Figure 9 , Figure 10

[0294] The Backoff Parameter value (BI) corresponding to the Backoff Indicator (BI) field included in the MAC subheader for RAR (e.g. 0) Figure 11 ​The validity / invalidity of transformPrecoder for the message 3 / message A PUSCH can also be set in a case where an extension (E) field, a type (T) field, a random access preamble identifier (RAPID) field included in a MAC subheader for the RAR are specific values. Alternatively, the validity / invalidity of transformPrecoder for the message 3 / message A PUSCH can also be set in a case where the PRACH that triggers the RAR is transmitted in a specific RA resource based on a RACH resource partition structure.

[0295] The present embodiment can also be applied in a case where a specific condition is satisfied. The specific condition can also be that the PRACH that triggers the RAR is transmitted in a specific RA resource based on a RACH resource partition structure.

[0296] According to the present embodiment, it is possible to explicitly apply processing in a case where dynamic switching of the message 3 / message A PUSCH waveform is applied. Furthermore, with the dynamic waveform switching of the message 3 / message A PUSCH, since the existing MAC subheader / payload can be used in a case where the indication based on the RAR is used, it is possible to suppress an increase in communication overhead.

[0297] <Problem Point 4>

[0298] In the existing system (for example, before Rel. 17 NR), in the antenna port field included in the DCI format 0_1 / 0_2, in a case where the transform precoder becomes valid (for example, in a case where DFT-S-OFDM is applied to the scheduled PUSCH), DMRS type 2 (for example, dmrs-Type = 2) is not assumed (refer to Figure 12 ). DMRS type 2 is only considered / applied in a case where the transform precoder is invalid (for example, in a case where CP-OFDM is applied to the scheduled PUSCH).

[0299] In a case where dynamic waveform switching (for example, dynamic waveform switching) is supported, it is possible to perform switching of the waveform between CP-OFDM and DFT-S-OFDM according to the indication of the DCI.

[0300] On the other hand, the type of PUSCH DMRS (dmrs-Type 1 or dmrs-Type 2) is set by RRC. In this case, for CP-OFDM, DMRS type 2 (or, DMRS type 1) can be set (same as the existing system (e.g., before Rel. 17 NR)).

[0301] However, for DFT-S-OFDM, DMRS type 2 cannot be set in the existing system, but in the case where dynamic waveform switching is set / supported, a case where DMRS type 2 is set for DFT-S-OFDM is transmitted. This is because the DCI indication (e.g., waveform switching) changes (DMRS type setting) dynamically by RRC setting.

[0302] As such, how the setting of the type of PUSCH DMRS is performed in the case where dynamic waveform switching is supported is not clear.

[0303] <Embodiment 6>

[0304] In the case where dynamic waveform switching (dynamic waveform switching (DWS)) is set, a specific DMRS type (dmrs-Type) can also be applied / set for the PUSCH DMRS.

[0305] For example, in the case where dynamic waveform switching is set, the UE can also perform control to apply a specific DMRS type (e.g., DMRS type 1) regardless of the waveform (CP-OFDM or DFT-S-OFDM) indicated by the DCI / DMRS type set by RRC. Thereby, it is possible to suppress an increase in the combination of {waveform, DMRS type} that the UE needs to assume in PUSCH transmission. As a result, it is possible to suppress an increase in the UE that cannot be implemented.

[0306] The UE can also assume / apply at least one of the following options 6-1 to 6-2 for the DMRS type (dmrs-Type) of the PUSCH DMRS. In addition, in the present disclosure, the setting of dynamic waveform switching can also be rewritten as the activation / activation (activate) of dynamic waveform switching.

[0307] [Option 6-1]

[0308] In the case where dynamic waveform switching is set, only type 1 can also be set as the DMRS type (dmrs-Type) (see Figure 13 ).

[0309] In a case where dynamic waveform switching is set, the base station can also control to set only Type 1 to the UE as the DMRS type of the PUSCH. That is, in a case where dynamic waveform switching is set, the setting of DMRS Type 2 based on RRC can also be limited / prohibited.

[0310] In this case, DMRS Type 1 can also be applied regardless of the waveform (CP-OFDM or DFT-S-OFDM) indicated by the DCI. In a case where dynamic waveform switching is set, the UE can also control to apply DMRS Type 1 to any waveform (CP-OFDM and DFT-S-OFDM). Further, in a case where dynamic waveform switching is set, the UE can also assume / expect / judge that DMRS Type 1 is set for the PUSCH DMRS.

[0311] In a case where dynamic waveform switching is set, the setting of the DMRS type of the PUSCH based on RRC can also be omitted.

[0312] As such, by setting only a specific DMRS type, it is possible to suppress an increase in the combination of {waveform, DMRS type} that the UE needs to assume in the PUSCH transmission. As a result, it is possible to suppress an increase in the unachievable in the UE.

[0313] [Option 6-2]

[0314] In a case where dynamic waveform switching is set, as the DMRS type, the setting of DMRS Type 1 and DMRS Type 2 can also be supported / allowed (refer to Figure 13 ).

[0315] In a case where dynamic waveform switching is set, the base station can also control to set DMRS Type 1 or DMRS Type 2 to the UE as the DMRS type of the PUSCH. That is, in a case where dynamic waveform switching is set, the setting of DMRS Type 2 based on RRC can also be allowed.

[0316] In a case where DMRS Type 2 is set and dynamic waveform switching is set, the UE can also interpret that Type 1 is set as the DMRS type (for example, dmrs-Type) of the PUSCH. That is, the UE can also ignore the setting of DMRS Type 2 and apply DMRS Type 1.

[0317] As such, in a case where dynamic waveform switching is set, DMRS Type 1 can also be applied regardless of the DMRS type set by RRC.

[0318] In this way, by setting the DMRS type applied to a specific DMRS type, it is possible to suppress an increase in the combination of {waveform, DMRS type} that the UE needs to assume in PUSCH transmission. As a result, it is possible to suppress an increase in the UE that cannot be implemented.

[0319] <Embodiment 7>

[0320] In the case where dynamic waveform switching (DWS) is set, for the PUSCH DMRS, the DMRS type (dmrs-Type) applied can also be decided based on the waveform indicated by the DCI.

[0321] For example, in the case where dynamic waveform switching is set, the UE can also judge the DMRS type applied based on the waveform (CP-OFDM or DFT-S-OFDM) indicated by the DCI / the DMRS type set by RRC.

[0322] In the case where dynamic waveform switching is set and DFT-S-OFDM is indicated by the DCI, the UE can also assume / apply at least one of the following options 7-1 to 7-2 for the DMRS type (dmrs-Type) of the PUSCH DMRS. The DCI for the indication of DFT-S-OFDM can also be the DCI for the scheduling of the PUSCH.

[0323] [Option 7-1]

[0324] In the case where dynamic waveform switching is set and DFT-S-OFDM is indicated by the DCI, only Type 1 can also be applied / set as the DMRS type.

[0325] In the case where dynamic waveform switching is set, the base station can also control to set only Type 1 to the UE as the DMRS type of the PUSCH. That is, in the case where dynamic waveform switching is set, the setting of DMRS Type 2 based on RRC can also be limited / prohibited.

[0326] In this case, DMRS Type 1 can also be applied regardless of the waveform (CP-OFDM or DFT-S-OFDM) indicated by the DCI. In the case where dynamic waveform switching is set, the UE can also control to apply DMRS Type 1 to any waveform (CP-OFDM and DFT-S-OFDM). Furthermore, in the case where dynamic waveform switching is set, the UE can also assume / expect / judge that DMRS Type 1 is set for the PUSCH DMRS.

[0327] In a case where dynamic waveform switching is configured, the configuration of the DMRS type of the PUSCH based on RRC can also be omitted.

[0328] In this way, by configuring only a specific DMRS type, it is possible to suppress an increase in the combination of {waveform, DMRS type} that the UE needs to assume in PUSCH transmission. As a result, it is possible to suppress an increase in the UE that cannot be implemented.

[0329] [Option 7-2]

[0330] In a case where dynamic waveform switching is configured and DFT-S-OFDM is instructed by DCI, the configuration of DMRS type 1 and DMRS type 2 can also be supported / allowed as the DMRS type.

[0331] In a case where dynamic waveform switching is configured, the base station can also control to configure the UE with DMRS type 1 or DMRS type 2 as the DMRS type of the PUSCH. That is, in a case where dynamic waveform switching is configured, the configuration of DMRS type 2 based on RRC can also be allowed.

[0332] In a case where DMRS type 2 is configured, dynamic waveform switching is configured, and DFT-S-OFDM is instructed by DCI, the UE can also interpret that type 1 is configured as the DMRS type (for example, dmrs-Type) of the PUSCH. That is, in a case where DFT-S-OFDM is instructed by DCI, the UE can also ignore the configuration of DMRS type 2 and apply DMRS type 1.

[0333] On the other hand, in a case where DMRS type 2 is configured, dynamic waveform switching is configured, and DFT-S-OFDM is not instructed by DCI (for example, in a case where CP-OFDM is instructed), the UE can also interpret that DMRS type 2 is configured as the DMRS type (for example, dmrs-Type) of the PUSCH. That is, in a case where DFT-S-OFDM is not instructed by DCI (for example, in a case where CP-OFDM is instructed), the UE can also apply DMRS type 2.

[0334] In this way, in a case where dynamic waveform switching is configured and DMRS type 2 is configured by RRC, it is also possible to determine whether to apply DMRS type 2 based on the waveform instructed by DCI. In addition, in a case where dynamic waveform switching is configured and DMRS type 1 is configured by RRC, it is also possible to control to apply DMRS type 1 regardless of the waveform instructed by DCI.

[0335] Thus, in a case where CP-OFDM is instructed by the DCI, DMRS Type 2 can be applied, and thus the applied DMRS type can be flexibly controlled in accordance with the waveform.

[0336] <Embodiment 8>

[0337] In a case where dynamic waveform switching (DWS) is set and DMRS Type 2 is set as the DMRS type (for example, dmrs-Type), a specific field (for example, an antenna port field) included in the DCI can also be interpreted based on a specific rule.

[0338] In a case where dynamic waveform switching is set and DMRS Type 2 is set, the UE can also interpret a specific field (for example, an antenna port field) included in the DCI based on a specific rule. The DCI can also be a DCI for scheduling of PUSCH. The specific rule can also apply at least one of the following Option 8-1 to Option 8-2, for example.

[0339] [Option 8-1]

[0340] The bit width (for example, bitwidth) of the antenna port field is decided in consideration of the fact that the dmrs-Type is DMRS Type 2 (that is, following the setting of the dmrs-Type), but the UE can also interpret only a part of the bits (or use a part of the bits) to interpret the indication based on the antenna port field.

[0341] The number of the part of the bits can also be the same as the number (or the number of bits / codewords) of the antenna port field set to Type 2 for dmrs-Type 1. In the present disclosure, the part of the bits / part of the bits can also be rewritten as a part of the DCI codewords / part of the DCI codewords.

[0342] In this case, the decision of the bit width of the antenna port field of the DCI and the interpretation of the antenna port field of the DCI can also be different. That is, it can also be that the bit width / codeword number of the antenna port field of the DCI is decided based on DMRS Type 2, and the interpretation of the antenna port field of the DCI is performed assuming DMRS Type 1.

[0343] The number of the part of the DCI codewords can also be the same as the number (or the number of bits / codewords) of the antenna port field set to Type 2 for dmrs-Type 1.

[0344] Thus, in a case where DMRS Type 2 is set, the UE can also appropriately perform the interpretation of the antenna port field of the DCI even in a case where DMRS Type 1 is applied. Thus, in a case where CP-OFDM is instructed by the DCI, DMRS Type 2 can be applied, and thus the applied DMRS type can be flexibly controlled in accordance with the waveform.

[0345] [Option 8-2]

[0346] The bit width of the antenna port field is decided considering that the dmrs-Type is DMRS type 1 (i.e., ignoring the setting of the dmrs-Type), and the UE can also interpret the indication based on the antenna port field considering that the dmrs-Type is DMRS type 1.

[0347] In this case, the decision of the bit width of the antenna port field of the DCI and the interpretation of the antenna port field can also be the same. That is, it can also be that the bit width of the antenna port field of the DCI is decided based on DMRS type 1, and the interpretation of the antenna port field of the DCI is also performed assuming DMRS type 1.

[0348] Thus, in the case where DMRS type 2 is set, in the case where DMRS type 1 is applied, both the bit width and the interpretation of the antenna port field can be performed assuming DMRS type 1. Further, it is possible to suppress an increase in the overhead of the antenna port field.

[0349] <Embodiment 9>

[0350] In the case where dynamic waveform switching (DWS) is set, and DMRS type 2 is set as the DMRS type (e.g., dmrs-Type), and DFT-S-OFDM is indicated by the DCI, a specific field (e.g., the antenna port field) included in the DCI can also be interpreted based on a specific rule.

[0351] In the case where dynamic waveform switching is set, and DMRS type 2 is set, and DFT-S-OFDM is indicated by the DCI, the UE can also interpret a specific field (e.g., the antenna port field) included in the DCI based on a specific rule. The DCI can also be used for scheduling of the PUSCH. The specific rule can also apply at least one of the following options 9-1 to 9-2, for example.

[0352] [Option 9-1]

[0353] The bit width of the antenna port field is decided considering that the dmrs-Type is DMRS type 2 (i.e., following the setting of the dmrs-Type), but the UE can also interpret the indication based on the antenna port field using only a part of the bits (or using a part of the bits).

[0354] The number of the part of bits can also be the same as the number of the antenna port field (or the number of bits / code points) of the type 2 configured for the dmrs-Type 1. In the present disclosure, the part of bits / part of bits can also be rewritten as the part of DCI code points / part of DCI code points.

[0355] In this case, the determination of the bit width of the antenna port field of the DCI and the interpretation of the antenna port field of the DCI can also be different. That is, it can also be that the bit width of the antenna port field of the DCI is determined based on the DMRS type 2, and the interpretation of the antenna port field of the DCI is made assuming the DMRS type 1.

[0356] The number of the part of DCI code points can also be the same as the number of the antenna port field (or the number of bits / code points) of the type 2 configured for the dmrs-Type 1.

[0357] Thus, in the case where the DMRS type 2 is configured and the DFT-S-OFDM is indicated by the DCI, even in the case where the DMRS type 1 is applied, the UE can appropriately make the interpretation of the antenna port field of the DCI.

[0358] In addition, in the case where the DMRS type 2 is configured and the CP-OFDM is indicated by the DCI, the determination of the bit width of the antenna port field of the DCI and the interpretation of the antenna port field can also be made based on the DMRS type 2.

[0359] In Figure 14A An example of the antenna port field of the DCI in the case where the dynamic waveform switching is configured and the type 2 is configured as the DMRS type (for example, dmrs-Type) is shown in B.

[0360] Antenna port field example 1

[0361] In the case where the DFT-S-OFDM is indicated by the DCI that schedules the PUSCH, the bit width (or the number of bits of the field) can also be configured as 3 bits. In this case, the UE can also make the interpretation in the same manner as in the case where the type 1 is configured as the DMRS type (for example, dmrs-Type). For example, only the 2 bits of the least significant bits (LSB) can be interpreted (refer to Figure 14A ).

[0362] In a case where DFT-S-OFDM is not indicated by the DCI scheduling the PUSCH (for example, in a case where CP-OFDM is indicated), the bit width (or, the number of bits of the field) can also be set to 3 bits. In this case, the UE can also be configured to interpret the case where Type 2 is set as the DMRS type (for example, dmrs-Type) identically. For example, all 3 bits can also be interpreted.

[0363] Antenna port field example 2

[0364] In a case where DFT-S-OFDM is indicated by the DCI scheduling the PUSCH, the bit width (or, the number of bits of the field) can also be set to 3 bits. In this case, the UE can also interpret a specific number (here, 5) of the 8 codepoints generated by 3 bits. In this case, the remaining 3 codepoints / fields can also be set as reserved bits / reserved codepoints (refer to Figure 14B ).

[0365] In a case where DFT-S-OFDM is not indicated by the DCI scheduling the PUSCH (for example, in a case where CP-OFDM is indicated), the bit width (or, the number of bits of the field) can also be set to 3 bits. In this case, the UE can also interpret all the codepoints (here, 8) generated by 3 bits.

[0366] As such, in a case where dynamic waveform switching is configured, the decision / interpretation of the bit width of the antenna port field of the DCI is flexibly controlled based on the waveform indicated by the DCI, and thus the PUSCH DMRS transmission can be appropriately performed.

[0367] [Option 9-2]

[0368] The bit width of the antenna port field (for example, bit width) is decided considering that the dmrs-Type is DMRS Type 1 (that is, the configuration of the dmrs-Type is ignored), and the UE can also interpret the indication based on the antenna port field considering that the dmrs-Type is Type 1.

[0369] In this case, the decision of the bit width of the antenna port field of the DCI and the interpretation of the antenna port field can also be the same. That is, it can also be that the bit width of the antenna port field of the DCI is decided based on DMRS Type 1, and the interpretation of the antenna port field of the DCI is also performed assuming DMRS Type 1.

[0370] Thus, in a case where DMRS type 2 is set and DFT-S-OFDM is indicated by DCI (for example, in a case where DMRS type 1 is applied), both the bit width and the interpretation of the antenna port field can be assumed to be DMRS type 1. In addition, an increase in the overhead of the antenna port field can be suppressed.

[0371] <Analysis A1>

[0372] It is under study that DWS is not supported in Type 1 and Type 2 configured grant (CG) PUSCH but only in dynamic grant (DG).

[0373] A UE does not expect the bit width of a certain field within DCI format 0_1 with CRC scrambled by CS-RNTI to be greater than the corresponding bit width of the same field within DCI format 0_1 with CRC scrambled by C-RNTI for the same serving cell. In a case where the bit width of a certain field within DCI format 0_1 with CRC scrambled by CS-RNTI is not equal to the bit width of the corresponding field within DCI format 0_1 with CRC scrambled by C-RNTI for the same serving cell, a few most significant bits (MSBs) with a value set to "0" are inserted to the field within DCI format 0_1 with CRC scrambled by CS-RNTI until the bit width becomes equal to the bit width of the corresponding field within DCI format 0_1 with CRC scrambled by C-RNTI for the same serving cell.

[0374] In the size alignment of DCI format 0_1 with CRC scrambled by C-RNTI or CS-RNTI, the following restrictions are satisfied:

[0375] - The bit width (size) of any field within DCI format 0_1 with CRC scrambled by C-RNTI (using C-RNTI) is equal to or greater than the bit width of the field within DCI format 0_1 with CRC scrambled by CS-RNTI (using CS-RNTI). If the bit width of the field within DCI format 0_1 using CS-RNTI is smaller than the bit width of the field within DCI format 0_1 using C-RNTI, the bit width of the field within DCI format 0_1 using CS-RNTI is made equal to the bit width of the field within DCI format 0_1 using C-RNTI by padding 0s to the field within DCI format 0_1 using CS-RNTI.

[0376] A dedicated DMRS configuration is applied for DG-PUSCH and CG-PUSCH. PUSCH configuration (DG-PUSCH, PUSCH-Config) can also contain uplink DMRS configuration (DMRS-UplinkConfig) of dmrs-UplinkForPUSCH-MappingTypeA / dmrs-UplinkForPUSCH-MappingTypeB. CG-PUSCH configuration (ConfiguredGranConfig) can also contain uplink DMRS configuration (DMRS-UplinkConfig) of cg-DMRS-Configuration.

[0377] DMRS configuration affects DCI field size. The size of the antenna port field in the case of DMRS Type 2 is larger than that in the case of DMRS Type 1. For example, in the case of no transform precoder, DMRS Type 1, and DMRS maximum length 1, the size of the antenna port field is 3 bits, and in the case of no transform precoder, DMRS Type 1, and DMRS maximum length 2, the size of the antenna port field is 4 bits. On the other hand, in the case of no transform precoder, DMRS Type 2, and DMRS maximum length 1, the size of the antenna port field is 4 bits, and in the case of no transform precoder, DMRS Type 2, and DMRS maximum length 2, the size of the antenna port field is 5 bits.

[0378] <Problem Point A1>

[0379] In Rel. 17, for PUSCH, simultaneous configuration of DFT-s-OFDM and DMRS Type 2 is not supported.

[0380] In DG-PUSCH, in the case of DWS being configured, a new 1-bit for indicating waveform switching is transmitted by scheduling DCI. The problem of the possibility of configuration of DMRS Type 2 is handled in Problem Point 1 and Embodiment 1.

[0381] In Type 2 CG-PUSCH, DWS is not supported.

[0382] Type 2 CG activation DCI (Type 2 CG-PUSCH activation DCI) and DG-DCI (DG-PUSCH scheduling DCI) share the same DCI format with the same size. The size of any field in the DG-DCI is the size of the field in the Type 2 CG-PUSCH activation DCI or more.

[0383] As for the DMRS configuration for Type 2 CG-PUSCH in the case where DWS is configured for DG-PUSCH, consider the following several cases:

[0384] - Case 1: In the case where DWS is configured, and DMRS Type 1 is configured, whether there is a restriction related to the DMRS type of CG-PUSCH becomes a problem.

[0385] - Case 1: In the case where DWS is configured, and DMRS Type 2 is configured, whether there is a restriction related to the DMRS type of CG-PUSCH becomes a problem.

[0386] <Embodiment A1>

[0387] This embodiment relates to the problem point A1.

[0388] In the case where DWS is configured, it is also possible to configure DMRS Type 1 for both DG-PUSCH and CG-PUSCH. According to this configuration, there is no need for complex UE operations for interpretation of the DMRS type and determination of the DCI size for activation of DG and CG.

[0389] - Example 1: It is also possible to specify the following operation in the specification.

[0390] In the case where dynamic waveform switching is configured, the UE expects that dmrs-Type = 1 is configured in both PUSCH-Config and ConfiguredGrantConfig (on the same serving cell / BWP).

[0391] Figure 15 An example of the RRC IE related to Embodiment A1 is shown. In this example, the UE receives the configuration of DWS, DMRS-Type = 1 in PUSCH-Config, and DMRS-Type = 1 in ConfiguredGrantConfig.

[0392] - Example 2: It is also possible to specify the following operation in the specification.

[0393] In the case where dynamic waveform switching is configured, the UE does not expect that dmrs-Type = 2 is configured in either of PUSCH-Config and ConfiguredGrantConfig (on the same serving cell / BWP).

[0394] <Embodiment A2>

[0395] This embodiment relates to the problem point A1.

[0396] In case of DWS being configured, DMRS type 1 or 2 can also be configured for DG-PUSCH, and DMRS type 1 can also be configured for CG-PUSCH. According to this configuration, UE does not need to read DWS bit to identify the size of type 2 CG-PUSCH activation DCI. In addition, for DG-PUSCH, flexible DMRS configuration is possible.

[0397] - Example 1: The following operation can also be specified in the specification.

[0398] In case of dynamic waveform switching being configured, UE expects dmrs-Type=1 is configured within ConfiguredGrantConfig (on the same serving cell / BWP).

[0399] - Example 2: The following operation can also be specified in the specification.

[0400] In case of dynamic waveform switching being configured, UE does not expect dmrs-Type=2 is configured within ConfiguredGrantConfig (on the same serving cell / BWP).

[0401] <Embodiment A3>

[0402] This embodiment relates to the problem point A1.

[0403] In case of DWS being configured, DMRS type 1 or 2 can also be configured for DG-PUSCH and CG-PUSCH. According to this configuration, flexible DMRS configuration is possible for both DG-PUSCH and CG-PUSCH.

[0404] - Embodiment 3-1

[0405] In case of DWS field indicating DFT-s-OFDM and DMRS type 2 being configured for DG-PUSCH, UE can also interpret that DMRS is configured as DMRS type 1. According to this operation, UE can follow the existing implementation for DMRS. That is, DMRS type 2 can also be configured only for CP-OFDM. This operation can also follow Embodiment 7.

[0406] - Embodiment 3-2

[0407] In case of DWS field indicating DFT-s-OFDM within DCI activating / deactivating type 2 CG-PUSCH and DMRS type 2 being configured for CG-PUSCH, UE can also interpret that DMRS is configured as DMRS type 1. According to this operation, the same DCI size for DG and CG-PUSCH activation can be maintained, and flexibility of DMRS configuration is obtained.

[0408] In case the DWS indicator within the DCI activating / deactivating Type 2 CG-PUSCH indicates transform precoding, the UE can also interpret DMRS-Type within ConfiguredGrantConfig as equal to 1.

[0409] The following operation can also be specified.

[0410] - The UE does not expect the DWS indicator within the Type 2 CG-PUSCH activation / deactivation DCI to indicate transform precoding as valid.

[0411] <Problem Point A2>

[0412] As mentioned before, the specification does not consider a DCI field with non-zero bit width in DCI with CRC scrambled by CS-RNTI and zero bit width in DCI with CRC scrambled by C-RNTI.

[0413] In future specifications, a new DCI field with the following characteristics can be specified.

[0414] - In case the transform precoder is inactive, it has zero bit width, and,

[0415] - In case the transform precoder is active, it has non-zero bit width.

[0416] The following condition is an error case, which can also be avoided explicitly.

[0417] - The new DCI field is set for both DG-PUSCH and CG-PUSCH, and,

[0418] - For DG-PUSCH, the transform precoder is inactive, and,

[0419] - For CG-PUSCH, the transform precoder is active.

[0420] <Problem Point A3>

[0421] In addition to Problem Point A2, the DCI field size can be different based on the DWS indication. Depending on the DWS indicator, the error case in Problem Point A2 can occur.

[0422] <Implementation A4>

[0423] This implementation relates to Problem Point A2.

[0424] In the present disclosure, the DCI field present only in the scheduling of PUSCH with DFT-s-OFDM, the DCI field of which is 0 bits in the case where the transform precoder is invalid and X (X > 0) bits in the case where it is not, the DCI field of which has a bit width of non-zero for DFT-s-OFDM and zero for CP-OFDM, the new DCI field, and the specific DCI field can also overwrite each other.

[0425] In Figure 16 In the example of the present embodiment, the DCI for the scheduling of PUSCH with DFT-s-OFDM contains the specific DCI field, and the DCI for the scheduling of PUSCH with CP-OFDM does not contain the specific DCI field.

[0426] In the case where the DCI field present only in the scheduling of PUSCH with DFT-s-OFDM is set, the setting of the transform precoder for DG-PUSCH can also be the same as the setting of the transform precoder for CG-PUSCH. According to this setting, the size of this field is the same between DG-PUSCH and CG-PUSCH, and thus there is no need for an additional DCI size alignment rule.

[0427] <Embodiment A5>

[0428] This embodiment relates to the point A2.

[0429] In the case where the DCI field present only in the scheduling of PUSCH with DFT-s-OFDM is set, the transform precoder for CG-PUSCH can also be invalid. According to this setting, the size of this field is the same between DG-PUSCH and CG-PUSCH, and thus there is no need for an additional DCI size alignment rule.

[0430] <Embodiment A6>

[0431] This embodiment relates to the point A2.

[0432] In the case where the DCI field present only in the scheduling of PUSCH with DFT-s-OFDM is set, this field can also not be present within the DCI with CRC scrambled by CS-RNTI. According to this setting, the size of this field is the same between DG-PUSCH and CG-PUSCH, and thus there is no need for an additional DCI size alignment rule.

[0433] <Embodiment A7>

[0434] This embodiment relates to the point A2.

[0435] In a case where the DCI field present only in scheduling of PUSCH with DFT-s-OFDM is set, and the transform precoder for DG-PUSCH is invalid, and the transform precoder for CG-PUSCH is valid, the bit width of the field can also be aligned between the DG-PUSCH and the CG-PUSCH based on a certain rule.

[0436] The certain rule can also follow at least one of the following several rules.

[0437] - The size of the field is consistent with the larger one of the size for DG-PUSCH and the size for CG-PUSCH. For example, the MSB of the field with the smaller size can also be padded with bits of value "0".

[0438] - The size of the field is consistent with the smaller one of the size for DG-PUSCH and the size for CG-PUSCH. For example, the number of codepoints corresponding to the larger size can also be reduced to below the number of codepoints of the field with the smaller size by down-scoping, reducing the maximum value, increasing the minimum value, or puncturing the codepoints. For example, the number of codepoints corresponding to the larger size can also be reduced as in Embodiment 9 (Option 9-1).

[0439] - The size of the field is consistent with the size of the field of the DCI (scheduling DCI of DG-PUSCH) with CRC scrambled by C-RNTI.

[0440] - The size of the field is consistent with the size of the field of the DCI (DCI for activation / deactivation of CG-PUSCH) with CRC scrambled by CS-RNTI.

[0441] According to the operation, flexible setting of the transform precoder and the DCI field for DG-PUSCH and CG-PUSCH can be achieved.

[0442] <Embodiment A8>

[0443] This embodiment relates to the problem point A3.

[0444] The DCI field present only in scheduling of PUSCH with DFT-s-OFDM and DWS can also not be set simultaneously.

[0445] The following operation can also be specified in the specification.

[0446] - The UE does not expect the DCI field present only in scheduling of PUSCH with DFT-s-OFDM and DWS to be set simultaneously.

[0447] According to this setting, the DCI size alignment rule becomes simple.

[0448] <Embodiment A9>

[0449] This embodiment relates to the point A3.

[0450] In the case where the DCI field and the DWS are simultaneously set only in the scheduling of the PUSCH with DFT-s-OFDM, the transform precoder can also be set to be invalid for the CG-PUSCH.

[0451] According to this setting, the DCI size alignment rule becomes simple.

[0452] <Embodiment A10>

[0453] This embodiment relates to the point A3.

[0454] In the case where the DCI field and the DWS are simultaneously set only in the scheduling of the PUSCH with DFT-s-OFDM, at least one of the following several restrictions can also be referred to.

[0455] The DWS indicator can also indicate only CP-OFDM. The DWS indicator can also not indicate DFT-s-OFDM. The following operation can also be specified in the specification.

[0456] The UE does not expect the DWS indicator to indicate the transform precoder to be valid.

[0457] The DWS indicator can also indicate the same waveform as that set for the CG-PUSCH. The DWS indicator can also not indicate a waveform different from that set for the CG-PUSCH. The following operation can also be specified in the specification.

[0458] The UE does not expect the indication of the DWS indicator to be different from the setting of the setting of the transform precoder within the permitted setting.

[0459] According to this setting, the DCI size alignment rule becomes simple.

[0460] <Embodiment A11>

[0461] This embodiment relates to the point A3.

[0462] In the case where the DCI field and the DWS are simultaneously set only in the scheduling of the PUSCH with DFT-s-OFDM, the bit width of the field can also be aligned between the DG-PUSCH and the CG-PUSCH based on a specific rule.

[0463] The specific rule can also follow at least one of the following several rules.

[0464] - The size of this field is consistent with the larger one of the size for DG-PUSCH and the size for CG-PUSCH. For example, the MSB for the field having the smaller size can also be padded with bits having a value of "0".

[0465] - The size of this field is consistent with the smaller one of the size for DG-PUSCH and the size for CG-PUSCH. For example, the number of codepoints corresponding to the larger size can also be reduced to below the number of codepoints of the field having the smaller size by range-reducing, reducing the maximum value, increasing the minimum value, or puncturing the codepoints. For example, the number of codepoints corresponding to the larger size can also be reduced as in Embodiment 9 (Option 9-1).

[0466] - The size of this field is consistent with the size of this field of the DCI (scheduling DCI for DG-PUSCH) accompanied by CRC scrambled by C-RNTI.

[0467] - The size of this field is consistent with the size of this field of the DCI (DCI for activation / deactivation of CG-PUSCH) accompanied by CRC scrambled by CS-RNTI.

[0468] According to this operation, flexible setting / indication of a transform precoder and DCI fields for DG-PUSCH and CG-PUSCH can be realized.

[0469] <Supplement>

[0470] [Notification of information to UE]

[0471] The notification of arbitrary information from a network (Network (NW)) (e.g., a base station (Base Station (BS))) to a UE (in other words, the reception of arbitrary information from a BS in a UE) in the above-described embodiments can also be performed using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.

[0472] In the case where the above-described notification is performed by a MAC CE, the MAC CE can also be identified by being included in a MAC subheader by a new logical channel ID (Logical Channel ID (LCID)) not specified in the existing standard.

[0473] In a case where the above notification is made through the DCI, the above notification can also be made through a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used for scrambling of Cyclic Redundancy Check (CRC) bits assigned to the DCI, a format of the DCI, and the like.

[0474] Further, the notification of the arbitrary information from the UE in the above-described embodiments can be made periodically, semi-persistently, or aperiodically.

[0475] [Notification of information from UE]

[0476] The notification of the arbitrary information from the UE (in other words, the transmission / reporting of the arbitrary information in the UE to the BS) in the above-described embodiments can also be made using physical layer signaling (for example, UCI), higher layer signaling (for example, RRC signaling, MAC CE), a specific signal / channel (for example, PUCCH, PUSCH, PRACH, reference signal), or a combination thereof.

[0477] In a case where the above notification is made through the MAC CE, the MAC CE can also be identified by being included in a MAC subheader through a new LCID not specified in the existing standard.

[0478] In a case where the above notification is made through the UCI, the above notification can also be transmitted using the PUCCH or the PUSCH.

[0479] Further, the notification of the arbitrary information from the UE in the above-described embodiments can be made periodically, semi-persistently, or aperiodically.

[0480] [Application with respect to each embodiment]

[0481] At least one of the above-described embodiments can also be applied in a case where a specific condition is satisfied. The specific condition can be specified in the standard or can be notified to the UE / BS using higher layer signaling / physical layer signaling.

[0482] The specific condition can be specified by one of the following conditions, or by a sum and / or (AND / OR) of 2 or more of the following conditions.

[0483] • DWS is set. For example, a DWS field exists.

[0484] • DWS is indicated. For example, a waveform is set through an RRC parameter, and switching is indicated through a DCI.

[0485] • Set DMRS Type 1 for DG-PUSCH.

[0486] • Set DMRS Type 2 for DG-PUSCH.

[0487] At least one of the above-described embodiments can also be applied only to a UE that reports or supports a specific UE capability.

[0488] The specific UE capability can also mean at least one of the following:

[0489] • Support for a specific processing / operation / control / information for at least one of the above-described embodiments.

[0490] • Support for a restriction on the DMRS type of DG-PUSCH using DWS considering CG-PUSCH (Embodiment A1 / A2).

[0491] • Support for an interpretation of the DMRS type of DG-PUSCH using DWS considering CG-PUSCH (Embodiment A3).

[0492] • Support for a restriction on the DCT field dedicated to DFT-s-OFDM of CG-PUSCH, DG-PUSCH using DWS (Embodiment A4 / A5 / A6 / A8 / A9 / A10).

[0493] • Support for bit width alignment for the DCT field dedicated to DFT-s-OFDM of CG-PUSCH, DG-PUSCH using DWS (Embodiment A7 / A11).

[0494] In addition, the above-described specific UE capability can be a capability applied across all frequencies (commonly regardless of frequency), a capability per frequency (e.g., one or a combination of a cell, a band, a band combination, a BWP, a component carrier, etc.), a capability per frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), a capability per SubCarrier Spacing (SCS), or a capability per Feature Set (FS) or Feature Set Per Component-carrier (FSPC).

[0495] Moreover, the above-described specific UE capability can be a capability applied commonly irrespective of the duplexing mode (full duplex mode) or a capability for each duplexing mode (e.g., Time Division Duplex (TDD), Frequency Division Duplex (FDD)).

[0496] Moreover, at least one of the above-described embodiments can also be applied in a case where the UE is configured / activated / triggered with specific information associated with the above-described embodiments (or implements the operation of the above-described embodiments) by higher layer signaling / physical layer signaling. For example, the specific information can also be any RRC parameter or the like for a specific version (e.g., Rel. 18 / 19).

[0497] In Rel. YY (e.g., YY is 18 or more), the RRC parameter for activating the operation XXX can also be denoted as XXX_rYY (XXX-rYY)

[0498] The UE can also apply the operation of Rel. 15 / 16 in a case where at least one of the above-described specific UE capability is not supported or the above-described specific information is not configured.

[0499] (Postscript)

[0500] With regard to an embodiment of the present disclosure, the following invention is postscripted.

[0501] [Postscript 1]

[0502] A terminal has:

[0503] a reception unit that receives a first demodulation reference signal (DMRS) type for a first uplink shared channel based on a dynamic grant, a second DMRS type for a second uplink shared channel based on a configured grant, and a configuration of dynamic waveform switching; and

[0504] a control unit that applies a specific value of a DMRS type to a specific uplink shared channel that is any one of the first uplink shared channel and the second uplink shared channel, based on the configuration.

[0505] [Postscript 2]

[0506] The terminal described in Postscript 1, in which the configuration indicates that the first DMRS type is 1 and the configuration indicates that the second DMRS type is 1.

[0507] [Postscript 3]

[0508] The terminal according to any one of <1> to <3>, wherein the specific value is 1 in a case where the setting indicates the DMRS type 2.

[0509] [Para 4]

[0510] The terminal according to any one of <1> to <3>, wherein the specific value is 1 in a case where the setting indicates the DMRS type 2.

[0511] (Para)

[0512] With respect to an embodiment of the present disclosure, the invention of the following paras is made.

[0513] [Para 1]

[0514] A terminal has:

[0515] a receiving unit that receives a first setting indicating whether or not first transform precoding is effective for a first uplink shared channel based on dynamic grant, a second setting indicating whether or not second transform precoding is effective for a second uplink shared channel based on configured grant, and a first downlink control information scheduling the first uplink shared channel and containing a specific field; and

[0516] a control unit that controls transmission of the first uplink shared channel based on the first setting and the downlink control information,

[0517] the specific field is present in a case where the first setting indicates that the first transform precoding is effective,

[0518] the specific field is absent in a case where the first setting indicates that the first transform precoding is ineffective.

[0519] [Para 2]

[0520] The terminal according to <1>, wherein a size of the specific field in second downlink control information indicating activation or deactivation of the second uplink shared channel is equal to a size of the specific field in the first downlink control information.

[0521] [Para 3]

[0522] The terminal according to <1> or <2>, wherein dynamic waveform switching is not set.

[0523] [Para 4]

[0524] The terminal according to any one of <1> to <3>, wherein dynamic waveform switching is set.

[0525] (Wireless communication system)

[0526] Hereinafter, a configuration of a wireless communication system according to an embodiment of the present disclosure will be described. In the wireless communication system, any one of the wireless communication methods according to the above-described embodiments of the present disclosure or a combination thereof is used for communication.

[0527] Figure 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 simply referred to as system 1) can also be a system that realizes communication using Long Term Evolution (LTE) standardized by the Third Generation Partnership Project (3GPP), 5th generation mobile communication system New Radio (5G NR), or the like.

[0528] Further, the wireless communication system 1 can also support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). The MR-DC can include E-UTRA-NR Dual Connectivity (EN-DC) of LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR, NR-E-UTRA Dual Connectivity (NE-DC) of NR and LTE, and the like.

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

[0530] The wireless communication system 1 can also support dual connectivity between multiple base stations within the same RAT (for example, dual connectivity of both an MN and an SN being base stations (gNBs) of NR (NR-NR Dual Connectivity (NN-DC))).

[0531] The wireless communication system 1 can also have the base station 11 that forms a macro cell C1 with a wider coverage, and the base station 12 (12a-12c) that is configured within the macro cell C1 and forms a small cell C2 that is narrower than the macro cell C1. The user terminal 20 can also be located within at least one cell. The configuration, number, and the like of the cells and the user terminal 20 are not limited to the manner shown in the drawing. Hereinafter, the base stations 11 and 12 are collectively referred to as base stations 10 without distinction.

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

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

[0534] Furthermore, the user terminal 20 can use at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC to perform communication.

[0535] The plurality of base stations 10 can be connected by wire (for example, optical fiber based on Common Public Radio Interface (CPRI), X2 interface, or the like) or wirelessly (for example, NR communication). For example, when NR communication is used as a backhaul between the base stations 11 and 12, the base station 11 that corresponds to a higher station can be referred to as an Integrated Access Backhaul (IAB) donor, and the base station 12 that corresponds to a relay station (relay) can be referred to as an IAB node.

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

[0537] The core network 30 can include, for example, at least one of a User Plane Function (UPF), an Access and Mobility management Function (AMF), a Session Management Function (SMF), a Unified Data Management (UDM), an Application Function (AF), a Data Network (DN), a Location Management Function (LMF), a network function (Network Functions (NF)) for maintenance operation management (Operation, Administration and Maintenance (Management) (OAM)), and the like. In addition, a plurality of functions can be provided by one network node. Furthermore, communication with an external network (for example, the Internet) can be performed via a DN.

[0538] The user terminal 20 can also be a terminal that supports at least one of LTE, LTE-A, 5G, and the like.

[0539] In the wireless communication system 1, a wireless access scheme based on Orthogonal Frequency Division Multiplexing (OFDM) can also be used. For example, in at least one of Downlink (DL) and 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), and the like can also be used.

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

[0541] In the wireless communication system 1, as a downlink channel, a downlink shared channel (Physical Downlink Shared Channel (PDSCH)), a broadcast channel (Physical Broadcast Channel (PBCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), and the like, which are shared among the user terminals 20, can also be used.

[0542] Furthermore, in the wireless communication system 1, as an uplink channel, an uplink shared channel (Physical Uplink Shared Channel (PUSCH)), an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)), and the like, which are shared among the user terminals 20, can also be used.

[0543] Through the PDSCH, user data, higher layer control information, a System Information Block (SIB), and the like are transmitted. Through the PUSCH, user data, higher layer control information, and the like can also be transmitted. Further, through the PBCH, a Master Information Block (MIB) can also be transmitted.

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

[0545] In addition, the DCI that schedules the PDSCH can also be referred to as a DL assignment, a DL DCI, and the like, and the DCI that schedules the PUSCH can also be referred to as a UL grant, a UL DCI, and the like. In addition, the PDSCH can also be rewritten as DL data, and the PUSCH can also be rewritten as UL data.

[0546] In the detection of the PDCCH, a Control REsource SET (CORESET) and a search space can also be utilized. The CORESET corresponds to a resource in which the DCI is searched for. The search space corresponds to a search area and a search method of the PDCCH candidates. One CORESET can also be associated with one or a plurality of search spaces. The UE can monitor the CORESET associated with a certain search space based on a search space setting.

[0547] One search space can also correspond to the PDCCH candidates corresponding to one or a plurality of aggregation levels. One or a plurality of search spaces can also be referred to as a search space set. In addition, the "search space", "search space set", "search space setting", "search space set setting", "CORESET", "CORESET setting", and the like of the present disclosure can also be rewritten with each other.

[0548] Through the PUCCH, uplink control information (Uplink Control Information (UCI)) including at least one of Channel State Information (CSI), delivery acknowledgement information (for example, also referred to as Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, and the like), and a Scheduling Request (SR) can also be transmitted. Through the PRACH, a random access preamble for establishing a connection with a cell can also be transmitted.

[0549] In addition, in the present disclosure, downlink, uplink, and the like can also be described without "link". Furthermore, it can also be described without "Physical" at the beginning of various channels.

[0550] In the wireless communication system 1, a Synchronization Signal (SS), a Downlink Reference Signal (DL-RS), and the like can also be transmitted. In the wireless communication system 1, as the DL-RS, a Cell-specific Reference Signal (CRS), a Channel State Information Reference Signal (CSI-RS), a DeModulation Reference Signal (DMRS), a Positioning Reference Signal (PRS), a Phase Tracking Reference Signal (PTRS), and the like can also be transmitted.

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

[0552] Further, in the wireless communication system 1, as the uplink reference signal (Uplink Reference Signal (UL-RS)), a measurement reference signal (Sounding Reference Signal (SRS)), a demodulation reference signal (DMRS), and the like can also be transmitted. In addition, the DMRS can also be referred to as a user terminal-specific reference signal (UE-specific Reference Signal).

[0553] Further, in the present example, the functional blocks of the characteristic portions in the present embodiment are mainly shown, and it can also be conceived that the base station 10 also has other functional blocks required for wireless communication. A part of the processing of each unit described below can also be omitted.

[0554] The control unit 110 implements control of the entire base station 10. The control unit 110 can be constituted by a controller, a control circuit, or the like described based on common knowledge in the technical field to which the present disclosure pertains.

[0555] The control unit 110 can also control generation of signals, scheduling (for example, resource allocation, mapping), and the like. The control unit 110 can also control transmission and reception, measurement, and the like using the transmission and reception unit 120, the transmission and reception antenna 130, and the transmission path interface 140. The control unit 110 can also generate data, control information, a sequence, and the like transmitted as signals, and forward to the transmission and reception unit 120. The control unit 110 can also perform call processing (setting, release, and the like) of a communication channel, state management of the base station 10, management of wireless resources, and the like.

[0556] The transmission and reception unit 120 can also include a baseband unit 121, a Radio Frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 can also include a transmission processing unit 1211 and a reception processing unit 1212. The transmission and reception unit 120 can be constituted by a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmission and reception circuit, and the like described based on common knowledge in the technical field to which the present disclosure pertains.

[0557] The transmission and reception unit 120 can be constituted as an integrated transmission and reception unit, or can be constituted by a transmission unit and a reception unit. The transmission unit can be constituted by the transmission processing unit 1211 and the RF unit 122. The reception unit can be constituted by the reception processing unit 1212, the RF unit 122, and the measurement unit 123.

[0558] The transmission / reception antenna 130 can be constituted by an antenna such as an array antenna and the like, which can be explained based on common knowledge in the technical field to which the present disclosure pertains.

[0559] The transmission / reception unit 120 can also transmit the downlink channel, the synchronization signal, the downlink reference signal, and the like described above. The transmission / reception unit 120 can also receive the uplink channel, the uplink reference signal, and the like described above.

[0560] The transmission / reception unit 120 can also form at least one of a transmission beam and a reception beam using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), and the like.

[0561] The transmission / reception unit 120 (transmission processing unit 1211) can also, for example, generate a bit string to be transmitted by performing processing of a Packet Data Convergence Protocol (PDCP) layer, processing of a Radio Link Control (RLC) layer (for example, RLC retransmission control), processing of a Medium Access Control (MAC) layer (for example, HARQ retransmission control), and the like, with respect to data, control information, and the like acquired from the control unit 110.

[0562] The transmission / reception unit 120 (transmission processing unit 1211) can also perform transmission processing of channel coding (which can include error correction coding), modulation, mapping, filter processing (filtering processing), Discrete Fourier Transform (DFT) processing (as necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, digital-analog conversion, and the like, with respect to the bit string to be transmitted, and output a baseband signal.

[0563] The transmission / reception unit 120 (RF unit 122) can also perform modulation to a wireless band, filter processing, amplification, and the like with respect to the baseband signal, and transmit a signal of the wireless band via the transmission / reception antenna 130.

[0564] On the other hand, the transmission / reception unit 120 (RF unit 122) can also perform amplification, filter processing, demodulation to a baseband signal, and the like with respect to a signal of the wireless band received by the transmission / reception antenna 130.

[0565] The transmission / reception unit 120 (reception processing unit 1212) can also apply, to the acquired baseband signal, reception processing such as analog-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (as necessary), filter processing, demapping, demodulation, decoding (which can also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, and the like, and acquire user data and the like.

[0566] The transmission / reception unit 120 (measurement unit 123) can also perform measurements related to the received signal. For example, the measurement unit 123 can also perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, and the like, based on the received signal. The measurement unit 123 can also perform measurements with respect to received power (for example, Reference Signal Received Power (RSRP)), received quality (for example, Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (for example, Received Signal Strength Indicator (RSSI)), propagation path information (for example, CSI), and the like. The measurement results can also be output to the control unit 110.

[0567] The transport path interface 140 can also transmit and receive signals (backhaul signaling) between apparatuses included in the core network 30 (for example, network nodes that provide NFs), other base stations 10, and the like, and can acquire, transmit, and the like, user data (user plane data), control plane data, and the like, for the user terminals 20.

[0568] In addition, the transmission unit and the reception unit of the base station 10 in the present disclosure can also be constituted by at least one of the transmission / reception unit 120, the transmission / reception antenna 130, and the transport path interface 140.

[0569] The transmission / reception unit 120 can also transmit a first demodulation reference signal (DMRS) type for a first uplink shared channel based on a dynamic grant, a second DMRS type for a second uplink shared channel based on a configured grant, a configuration of dynamic waveform switching. The control unit 110 can also apply a specific value of the DMRS type to reception of a specific uplink shared channel that is either of the first uplink shared channel and the second uplink shared channel, based on the configuration.

[0570] The transmission / reception unit 120 can also transmit a first configuration indicating whether or not a first transform precoding is effective for a first uplink shared channel based on a dynamic grant, a second configuration indicating whether or not a second transform precoding is effective for a second uplink shared channel based on a configured grant, and transmit a first downlink control information scheduling the first uplink shared channel and containing a specific field. The control unit 110 can also control reception of the first uplink shared channel based on the first configuration and the downlink control information. The specific field can be present in a case where the first configuration indicates that the first transform precoding is effective. The specific field can be absent in a case where the first configuration indicates that the first transform precoding is ineffective.

[0571] (user terminal)

[0572] Figure 19 is a diagram showing an example of a structure of a user terminal according to an embodiment. The user terminal 20 is provided with a control unit 210, a transmission / reception unit 220, and a transmission / reception antenna 230. In addition, one or more of the control unit 210, the transmission / reception unit 220, and the transmission / reception antenna 230 can be provided.

[0573] In addition, in this example, mainly functional blocks of characteristic parts in the present embodiment are shown, and it can be also assumed that the user terminal 20 has other functional blocks necessary for wireless communication. A part of the processing of each unit described below can be omitted.

[0574] The control unit 210 implements control of the entire user terminal 20. The control unit 210 can be constituted by a controller, a control circuit, or the like based on common knowledge in the technical field to which the present disclosure pertains.

[0575] The control unit 210 can also control generation, mapping, and the like of a signal. The control unit 210 can also control transmission / reception, measurement, and the like using the transmission / reception unit 220 and the transmission / reception antenna 230. The control unit 210 can also generate data, control information, a sequence, and the like transmitted as a signal, and forward to the transmission / reception unit 220.

[0576] The transmission / reception unit 220 can also include a baseband unit 221, an RF unit 222, a measurement unit 223. The baseband unit 221 can also include a transmission processing unit 2211, a reception processing unit 2212. The transmission / reception unit 220 can be constituted by a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmission / reception circuit and the like which can be explained based on common knowledge in the technical field to which the present disclosure pertains.

[0577] The transmission / reception unit 220 can be constituted as an integrated transmission / reception unit, or can be constituted by a transmission unit and a reception unit. The transmission unit can be constituted by the transmission processing unit 2211, the RF unit 222. The reception unit can be constituted by the reception processing unit 2212, the RF unit 222, the measurement unit 223.

[0578] The transmission / reception antenna 230 can be constituted by an antenna, for example, an array antenna and the like which can be explained based on common knowledge in the technical field to which the present disclosure pertains.

[0579] The transmission / reception unit 220 can receive the downlink channel, the synchronization signal, the downlink reference signal and the like described above. The transmission / reception unit 220 can transmit the uplink channel, the uplink reference signal and the like described above.

[0580] The transmission / reception unit 220 can use digital beamforming (for example, precoding), analog beamforming (for example, phase rotation) and the like to form at least one of a transmission beam and a reception beam.

[0581] The transmission / reception unit 220 (transmission processing unit 2211) can also perform, for example, processing at the PDCP layer, processing at the RLC layer (for example, RLC retransmission control), processing at the MAC layer (for example, HARQ retransmission control) and the like with respect to data, control information and the like acquired from the control unit 210, and generate a bit string to be transmitted.

[0582] The transmission / reception unit 220 (transmission processing unit 2211) can also perform channel coding (which can include error correction coding), modulation, mapping, filter processing, DFT processing (as necessary), IFFT processing, precoding, digital-analog conversion and the like transmission processing with respect to the bit string to be transmitted, and output a baseband signal.

[0583] In addition, as to whether or not to apply the DFT processing, the setting of the transform precoding can also be based. With respect to a certain channel (e.g., PUSCH), in a case where the transform precoding is effective (enabled), the transmission / reception unit 220 (transmission processing unit 2211) can also perform the DFT processing as the above-described transmission processing in order to transmit the channel with the DFT-s-OFDM waveform, and in a case where it is not, the transmission / reception unit 220 (transmission processing unit 2211) can also not perform the DFT processing as the above-described transmission processing.

[0584] The transmission / reception unit 220 (RF unit 222) can also perform modulation to the wireless band, filter processing, amplification, and the like with respect to the baseband signal, and transmit the signal of the wireless band via the transmission / reception antenna 230.

[0585] On the other hand, the transmission / reception unit 220 (RF unit 222) can also perform amplification, filter processing, demodulation to the baseband signal, and the like with respect to the signal of the wireless band received by the transmission / reception antenna 230.

[0586] The transmission / reception unit 220 (reception processing unit 2212) can also apply reception processing such as analog-digital conversion, FFT processing, IDFT processing (as necessary), filter processing, demapping, demodulation, decoding (may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, and the like with respect to the acquired baseband signal, and acquire user data and the like.

[0587] The transmission / reception unit 220 (measurement unit 223) can also perform measurement related to the received signal. For example, the measurement unit 223 can also perform RRM measurement, CSI measurement, and the like based on the received signal. The measurement unit 223 can also perform measurement with respect to the reception power (e.g., RSRP), reception quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), and the like. The measurement result can also be output to the control unit 210.

[0588] In addition, the transmission unit and the reception unit of the user terminal 20 in the present disclosure can also be constituted by at least one of the transmission / reception unit 220 and the transmission / reception antenna 230.

[0589] The transmission / reception unit 220 can also receive a first demodulation reference signal (DMRS) type for a first uplink shared channel based on a dynamic grant, a second DMRS type for a second uplink shared channel based on a configured grant, a configuration of dynamic waveform switching. The control unit 210 can also apply a specific value of the DMRS type to a specific uplink shared channel that is either of the first uplink shared channel and the second uplink shared channel, based on the configuration.

[0590] The configuration can also indicate that the first DMRS type is 1, and the configuration can also indicate that the second DMRS type is 1.

[0591] The configuration can also indicate that the first DMRS type is 1 or 2, and the configuration can also indicate that the second DMRS type is 1.

[0592] In a case where the configuration indicates the DMRS type 2, the specific value can also be 1.

[0593] The transmission / reception unit 220 can also receive a first configuration indicating whether or not a first transform precoding is effective for a first uplink shared channel based on a dynamic grant, a second configuration indicating whether or not a second transform precoding is effective for a second uplink shared channel based on a configured grant, and receive a first downlink control information scheduling the first uplink shared channel and containing a specific field. The control unit 210 can also control transmission of the first uplink shared channel based on the first configuration and the downlink control information. In a case where the first configuration indicates that the first transform precoding is effective, the specific field can also exist. In a case where the first configuration indicates that the first transform precoding is ineffective, the specific field can also not exist.

[0594] The size of the specific field in the second downlink control information indicating activation or deactivation of the second uplink shared channel can also be equal to the size of the specific field in the first downlink control information.

[0595] Dynamic waveform switching can also not be configured.

[0596] Dynamic waveform switching can also be configured.

[0597] (Hardware structure)

[0598] Further, the block diagrams used in the description of the embodiments above illustrate functional units. These functional units (structural units) are implemented by any combination of hardware and software, and the implementation method of each functional unit is not particularly limited. That is, each functional unit can be implemented by one device physically or logically integrated, or by two or more devices physically or logically separated and connected directly or indirectly (for example, by wire, wireless, or the like). Each functional unit can be implemented by combining the above one device or the above plurality of devices with software.

[0599] Here, among the functions, there are judgment, decision, determination, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, and the like, but are not limited to these. For example, a functional block (structural unit) that implements a transmission function can also be referred to as a transmitting unit, a transmitter, or the like. Any one of these is as described above, and the implementation method is not particularly limited.

[0600] For example, the base station, the user terminal, and the like in an embodiment of the present disclosure can also function as a computer that performs processing of the wireless communication method of the present disclosure. Figure 20 is a diagram showing an example of a hardware structure of a base station and a user terminal according to an embodiment. The base station 10 and the user terminal 20 described above can also 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, and a bus 1007.

[0601] Further, in the present disclosure, the terms of device, circuit, equipment, section, unit, and the like can be rewritten with each other. The hardware structure of the base station 10 and the user terminal 20 can be configured to include one or more of each device shown in the diagram, or can be configured not to include a part of the devices.

[0602] For example, the processor 1001 is only illustrated one, but there can be a plurality of processors. Further, the processing can be executed by one processor, or can be executed by two or more processors simultaneously, sequentially, or with other methods. In addition, the processor 1001 can be realized by one or more chips.

[0603] As for each function in the base station 10 and the user terminal 20, for example, by reading a specific software (program) into the processor 1001, the memory 1002, and the like hardware, the processor 1001 performs an operation and controls communication via the communication device 1004, or by controlling at least one of reading and writing of data in the memory 1002 and the storage 1003.

[0604] The processor 1001, for example, causes an operating system to operate to control the entire computer. The processor 1001 can also be constituted by a central processing device (Central Processing Unit (CPU)) including an interface with a peripheral device, a control device, an arithmetic device, a register, and the like. For example, at least a part of the above-described control unit 110 (210), the transmission and reception unit 120 (220), and the like can also be realized by the processor 1001.

[0605] Further, the processor 1001 reads out a program (program code), a software module, data, and the like from at least one of the storage 1003 and the communication device 1004 to the memory 1002, and performs various processing according to them. As the program, a program that causes a computer to execute at least a part of the operations described in the above-described embodiments can be used. For example, the control unit 110 (210) can also be realized by a control program stored in the memory 1002 and operated in the processor 1001, and the same can be applied to other functional blocks.

[0606] The memory 1002 can also be a computer-readable recording medium, for example, constituted by at least one of a Read Only Memory (ROM), an Erasable Programmable ROM (EPROM), an Electrically EPROM (EEPROM), a Random Access Memory (RAM), other appropriate storage medium. The memory 1002 can also be referred to as a register, a cache, a main storage (main storage device), and the like. The memory 1002 can hold a program (program code), a software module, and the like that can be executed in order to implement a wireless communication method related to an embodiment of the present disclosure.

[0607] The storage 1003 can also be a computer-readable recording medium such as at least one of a flexible disc, a floppy (registered trademark) disc, a magneto-optical disc (e.g., a compact disc read-only memory (CD-ROM) and the like), a digital versatile disc, a Blu-ray (registered trademark) disc), a removable disc, a hard disc drive, an intelligent disk (e.g., a card, a stick, a key drive), a magnetic stripe, a database, a server, and the like. The storage 1003 can also be referred to as an auxiliary storage device.

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

[0609] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, and the like) that receives an input from an outside. The output device 1006 is an output device (e.g., a display, a speaker, a Light Emitting Diode (LED) lamp, and the like) that performs an output to an outside. In addition, the input device 1005 and the output device 1006 can also be a structure that is integrated (e.g., a touch panel).

[0610] Furthermore, the processor 1001, the memory 1002, and the like are connected through a bus 1007 for communicating information. The bus 1007 can be configured with a single bus, or different buses can be configured between the devices.

[0611] Furthermore, the base station 10 and the user terminal 20 can also be configured to 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), or the like hardware, and a part or all of each functional block can also be implemented using the hardware. For example, the processor 1001 can also be implemented using at least one of these hardware.

[0612] (Modified example)

[0613] In addition, the terms described in the present disclosure and the terms necessary for understanding the present disclosure can also be rewritten as terms having the same or similar meanings. For example, a channel, a symbol, and a signal (a signal or signaling) can also be rewritten to each other. In addition, a signal can also be a message. A reference signal (RS) can also be simply referred to as RS, and can also be referred to as a pilot, a pilot signal, or the like depending on the applied standard. In addition, a component carrier (CC) can also be referred to as a cell, a frequency carrier, a carrier frequency, or the like.

[0614] A radio frame can also be configured by one or more periods (frames) in the time domain. Each period (frame) of the one or more periods (frames) configuring the radio frame can also be referred to as a subframe. Further, a subframe can also be configured by one or more slots in the time domain. A subframe can also be a fixed time length (for example, 1 ms) independent of numerology.

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

[0616] A slot can also be composed of one or a plurality of symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, and the like) in the time domain. Furthermore, a slot can also be a time unit based on a numerology.

[0617] A slot can also include a plurality of mini-slots. Each mini-slot can also be composed of one or a plurality of symbols in the time domain. Furthermore, a mini-slot can also be referred to as a sub-slot. A mini-slot can also be composed of a smaller number of symbols than a slot. A PDSCH (or PUSCH) transmitted in a larger time unit than a mini-slot can also be referred to as PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot can also be referred to as PDSCH (PUSCH) mapping type B.

[0618] A radio frame, a subframe, a slot, a mini-slot, and a symbol each represent a time unit for transmitting a signal. A radio frame, a subframe, a slot, a mini-slot, and a symbol can also be referred to by other names respectively corresponding thereto. In addition, a time unit of a frame, a subframe, a slot, a mini-slot, a symbol, and the like in the present disclosure can also be overwritten with each other.

[0619] For example, one subframe can also be referred to as a TTI, a plurality of consecutive subframes can also be referred to as a TTI, one slot or one mini-slot can also be referred to as a TTI. That is, at least one of a subframe and a TTI can be a subframe (1 ms) in the existing LTE, can be a period shorter than 1 ms (for example, 1-13 symbols), or can be a period longer than 1 ms. In addition, a unit representing a TTI can also not be referred to as a subframe, but can be referred to as a slot, a mini-slot, or the like.

[0620] Here, a TTI, for example, refers to a minimum time unit of scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling of allocating a radio resource (a frequency bandwidth, a transmission power, and the like that can be used in each user terminal) to each user terminal in a TTI unit. In addition, the definition of a TTI is not limited thereto.

[0621] A TTI can also be a transmission time unit of a data packet (a transport block), a code block, a codeword, and the like that have been channel-encoded, and can also become a processing unit of scheduling, link adaptation, and the like. In addition, when a TTI is given, a time interval (for example, a number of symbols) to which a transport block, a code block, a codeword, and the like are actually mapped can be shorter than the TTI.

[0622] In addition, in a case where one slot or one mini-slot is referred to as a TTI, one or more TTIs (i.e., one or more slots or one or more mini-slots) can also be a minimum time unit of scheduling. In addition, the number of slots (mini-slots) constituting the minimum time unit of scheduling can also be controlled.

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

[0624] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) can also be rewritten as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) can also be rewritten as a TTI having a TTI length of less than a long TTI and a TTI length of 1 ms or more.

[0625] A resource block (Resource Block (RB)) is a resource allocation unit in a time domain and a frequency domain, and can also include one or more contiguous subcarriers (subcarriers) in the frequency domain. The number of subcarriers included in the RB can also be the same regardless of a numerology, for example, can also be 12. The number of subcarriers included in the RB can also be determined based on a numerology.

[0626] In addition, the RB can also include one or more symbols in the time domain, and can also be a length of one slot, one mini-slot, one subframe, or one TTI. One TTI, one subframe, etc. can also be constituted by one or more resource blocks, respectively.

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

[0628] In addition, a resource block can also be constituted by one or more resource elements (Resource Element (RE)). For example, one RE can also be a wireless resource area of one subcarrier and one symbol.

[0629] The Bandwidth Part (BWP) (also referred to as partial bandwidth, etc.) can also represent a subset of consecutive common resource blocks (RBs) used for a certain parameter set in a certain carrier. Here, common RBs can also be determined by the index of RBs based on the common reference point of the carrier. PRBs can also be defined in a BWP and appended with numbers within that BWP.

[0630] A BWP can also include a UL BWP (the BWP used by UL) and a DL BWP (the BWP used by DL). For a UE, one or more BWPs can also be set within a single carrier.

[0631] At least one of the configured BWPs can be active, and the UE may not intend to transmit or receive specific signals / channels outside of the active BWPs. Additionally, terms such as "cell" and "carrier" in this disclosure may be replaced with "BWP".

[0632] Furthermore, the structures described above, such as radio frames, subframes, time slots, mini-time slots, and symbols, are merely illustrative. For example, the number of subframes contained in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-time slots contained within a time slot, the number of symbols and RBs contained in a time slot or mini-time slot, the number of subcarriers contained in an RB, and the number of symbols in a TTI, symbol length, and cyclic prefix (CP) length can be varied in many ways.

[0633] Furthermore, the information, parameters, etc., described in this disclosure can be represented by absolute values, relative values ​​with respect to a specific value, or other corresponding information. For example, wireless resources can also be indicated by a specific index.

[0634] In this disclosure, the names used for parameters, etc., are not limiting names in any respect. Furthermore, the mathematical expressions, etc., using these parameters may differ from those explicitly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name; therefore, the various names assigned to these various channels and information elements are not limiting names in any respect.

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

[0636] Further, information, a signal, and the like can be output in at least one of physical (hard) and / or logical (soft) forms. Further, the information, the signal, and the like can be output in at least one of the following: from higher layers (upper layers) to lower layers (lower layers), and from lower layers to higher layers. The information, the signal, and the like can be input and output via a plurality of network nodes.

[0637] The information, the signal, and the like that are input and output can be stored in a specific location (for example, a memory) and can be managed by a management table. The information, the signal, and the like that are input and output can be overwritten, updated, or added. The information, the signal, and the like that are output can be deleted. The information, the signal, and the like that are input can be transmitted to other devices.

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

[0639] In addition, the physical layer signaling can also be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), and the like. Further, the RRC signaling can also be referred to as an RRC message, and can also be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, and the like. Further, the MAC signaling can also be notified using, for example, a MAC Control Element (CE).

[0640] Further, the notification of specific information (for example, the notification of “X is”) is not limited to explicit notification, and can be performed implicitly (for example, by not performing the notification of the specific information, or by the notification of other information).

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

[0642] Software, regardless of the term used, such as software, firmware, middle-ware, microcode, hardware description language, or by other names, should be interpreted broadly to mean instructions, instruction sets, code (code), code segments, program code, programs, sub-programs, software modules, applications, software applications, software packages, routines, sub-routines, objects, executable files, execution threads, processes, functions, and the like.

[0643] In addition, software, instructions, information, and the like can also be transmitted and received via a transmission medium. For example, in the case where software is transmitted from a website, a server, or other remote source (remote source) using at least one of wired technology (coaxial cable, optical fiber cable, twisted pair cable, Digital Subscriber Line (DSL), and the like) and wireless technology (infrared rays, microwaves, and the like), at least one of these wired technology and wireless technology is included in the definition of the transmission medium.

[0644] The terms "system" and "network" used in the present disclosure can be used interchangeably. The "network" can also mean a device (for example, a base station) included in the network.

[0645] In the present disclosure, the terms of “precoding”, “precoder”, “weight (precoding weight)”, “Quasi-Co-Location (QCL)”, “Transmission Configuration Indication state (TCI state)”, “spatial relation”, “spatial domain filter”, “transmission power”, “phase rotation”, “antenna port”, “antenna port group”, “layer”, “number of layers”, “rank”, “resource”, “resource set”, “resource group”, “beam”, “beam width”, “beam angle”, “antenna”, “antenna element”, “panel”, and the like can be used interchangeably.

[0646] In the present disclosure, the terms of “Base Station (BS)”, “wireless base station”, “fixed station”, “NodeB”, “eNB (eNodeB)”, “gNB (gNodeB)”, “access point”, “Transmission Point (TP)”, “Reception Point (RP)”, “Transmission / Reception Point (TRP)”, “panel”, “cell”, “sector”, “cell group”, “carrier”, “component carrier”, and the like can be used interchangeably. There is also a case where the base station is called with the terms of macro cell, small cell, femto cell, pico cell, and the like.

[0647] The base station can accommodate one or plural (for example, three) cells. In a case where the base station accommodates plural cells, the coverage area of the base station as a whole can be divided into plural smaller areas, and each of the smaller areas can also be provided with a communication service by a base station subsystem (for example, a small base station for indoor use (Remote Radio Head (RRH))). The term of “cell” or “sector” refers to a part or the whole of the coverage area of at least one of the base station and the base station subsystem that provides a communication service in the coverage.

[0648] In the present disclosure, the fact that the base station transmits information to the terminal can also be mutually overwritten with the fact that the base station instructs the control / operation based on the information for the terminal.

[0649] In the present disclosure, the terms "mobile station (MS)", "user terminal", "user equipment (UE)", "terminal" and the like can be used interchangeably.

[0650] There are also instances where the mobile station is called a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a hand set, a user agent, a mobile client, a client, or by some other suitable terminology.

[0651] At least one of the base station and the mobile station can also be called a transmission device, a reception device, a wireless communication device, and the like. In addition, at least one of the base station and the mobile station can also be a device mounted on a moving object, a moving object body, and the like.

[0652] The moving object refers to an object that is movable, and the moving speed is arbitrary, and of course, includes a case where the moving object is stopped. The moving object includes, for example, a vehicle, a transport vehicle, an automobile, a motorcycle, a bicycle, a Connected Car, a shovel, a bulldozer, a wheel loader, a dump truck, a forklift, a train, a bus, a trailer, a rickshaw, a ship (a ship and other watercraft), an airplane, a rocket, an artificial satellite, a drone, a multicopter, a quadcopter, a hot air balloon, and an object mounted thereon, but is not limited to these. In addition, the moving object can also be a moving object that autonomously travels based on a travel instruction.

[0653] The moving object can be a vehicle (for example, a vehicle, an airplane, and the like), can be a moving object that moves in a unmanned manner (for example, a drone, an autonomous vehicle, and the like), and can be a robot (a manned type or an unmanned type). In addition, at least one of the base station and the mobile station also includes a device that does not necessarily move at the time of a communication operation. For example, at least one of the base station and the mobile station can also be an Internet of Things (IoT) device such as a sensor.

[0654] Figure 21is a drawing showing an example of a vehicle according to an embodiment. The vehicle 40 is provided with a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, front wheels 46 on the left and right, rear wheels 47 on the left and right, an axle 48, an electronic control unit 49, various sensors (including a current sensor 50, a rotation speed sensor 51, an air pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58), an information service unit 59, and a communication module 60.

[0655] The drive unit 41 is constituted by at least one of an engine, a motor, a hybrid of an engine and a motor, for example. The steering unit 42 is constituted to include at least a steering wheel (also called a handle), and at least one of the front wheels 46 and the rear wheels 47 is steered based on an operation of the steering wheel operated by a user.

[0656] The electronic control unit 49 is constituted by a microprocessor 61, a memory (ROM, RAM) 62, a communication port (for example, an Input / Output (IO) port) 63. Signals from the various sensors 50-58 provided in the vehicle are input to the electronic control unit 49. The electronic control unit 49 can also be called an Electronic Control Unit (ECU).

[0657] As the signals from the various sensors 50-58, there are the following signals and the like: a current signal from the current sensor 50 that senses a current of a motor, a rotation speed signal of the front wheels 46 / rear wheels 47 acquired by the rotation speed sensor 51, an air pressure signal of the front wheels 46 / rear wheels 47 acquired by the air pressure sensor 52, a vehicle speed signal acquired by the vehicle speed sensor 53, an acceleration signal acquired by the acceleration sensor 54, a depression amount signal of the accelerator pedal 43 acquired by the accelerator pedal sensor 55, a depression amount signal of the brake pedal 44 acquired by the brake pedal sensor 56, an operation signal of the shift lever 45 acquired by the shift lever sensor 57, a detection signal for detecting an obstacle, a vehicle, a pedestrian, and the like acquired by the object detection sensor 58.

[0658] The information service unit 59 is constituted by a navigation system, an audio system, a speaker, a display, a television, a radio, and various devices for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices. The information service unit 59 provides various information / services (for example, multimedia information / multimedia services) to an occupant of the vehicle 40 using information acquired from an external device via the communication module 60 and the like.

[0659] The information service unit 59 can include an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that receives input from the outside, and can include an output device (e.g., a display, a speaker, an LED lamp, a touch panel, etc.) that implements output to the outside.

[0660] The drive assist system unit 64 is constituted by one or more ECUs of various devices for providing a function for preventing an accident from occurring or reducing a driving burden on a driver, such as a millimeter wave radar, a Light Detection and Ranging (LiDAR), a camera, a positioning detector (e.g., a Global Navigation Satellite System (GNSS), etc.), map information (e.g., a High Definition (HD) map, an Autonomous Vehicle (AV) map, etc.), a gyro system (e.g., an Inertial Measurement Device (Inertial Measurement Unit (IMU)), an Inertial Navigation Device (Inertial Navigation System (INS)), etc.), an Artificial Intelligence (AI) chip, an AI processor, and a control of these devices. Further, the drive assist system unit 64 transmits and receives various information via the communication module 60, and implements a drive assist function or an autonomous driving function.

[0661] The communication module 60 is capable of communicating with the microprocessor 61 and the structural elements of the vehicle 40 via the communication port 63. For example, the communication module 60 transmits and receives data (information) between the microprocessor 61 and the memory (ROM, RAM) 62, and various sensors 50-58 in the drive unit 41, the steering unit 42, the accelerator pedal 43, the brake pedal 44, the shift lever 45, the front wheels 46, the rear wheels 47, the axle 48, the electronic control unit 49, and the like provided in the vehicle 40 via the communication port 63.

[0662] The communication module 60 is capable of being controlled by the microprocessor 61 of the electronic control unit 49, and is a communication device capable of communicating with an external device. For example, various information is transmitted and received between the external device via wireless communication. The communication module 60 can be inside and outside the electronic control unit 49. The external device can be, for example, the base station 10, the user terminal 20, and the like described above. Further, the communication module 60 can be, for example, at least one of the base station 10 and the user terminal 20 described above (may function as at least one of the base station 10 and the user terminal 20).

[0663] The communication module 60 can also transmit at least one of the signals from the various sensors 50-58 described above input to the electronic control unit 49, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 59 to the external device via wireless communication. The electronic control unit 49, the various sensors 50-58, the information service unit 59, and the like can also be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 60 can also contain information based on the above input.

[0664] The communication module 60 receives various information (traffic information, signal information, inter-vehicle information, and the like) transmitted from the external device and displays it on the information service unit 59 provided in the vehicle. The information service unit 59 can also be referred to as an output unit that outputs information (for example, outputs information to a display, a speaker, and the like based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 60) to a device.

[0665] Furthermore, the communication module 60 stores various information received from the external device in the memory 62 that can be used by the microprocessor 61. Based on the information stored in the memory 62, the microprocessor 61 can also control the drive unit 41, the steering unit 42, the accelerator pedal 43, the brake pedal 44, the shift lever 45, the front wheels 46 on the left and right, the rear wheels 47 on the left and right, the axles 48, the various sensors 50-58, and the like provided in the vehicle 40.

[0666] Furthermore, the base station in the present disclosure can also be rewritten as a user terminal. For example, the structures in which the communication between the base station and the user terminal is replaced with communication between a plurality of user terminals (for example, can also be referred to as Device-to-Device (D2D), Vehicle-to-Everything (V2X), and the like) can also apply the various modes / embodiments of the present disclosure. In this case, it can also be configured to have the functions of the base station 10 described above by the user terminal 20. Furthermore, the terms such as "uplink", "downlink", and the like can also be rewritten as terms corresponding to inter-terminal communication (for example, "sidelink"). For example, the uplink channel, the downlink channel, and the like can also be rewritten as a sidelink channel.

[0667] Likewise, the user terminal in the present disclosure can also be rewritten as a base station. In this case, it can also be configured to have the functions of the user terminal 20 described above by the base station 10.

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

[0669] The modes / embodiments explained in the present disclosure can be used alone or in combination, and can also be used in switching as execution proceeds. Furthermore, the processing procedure, timing, flowchart, and the like of the modes / embodiments explained in the present disclosure can also be changed in order as long as there is no contradiction. For example, for the methods explained in the present disclosure, the elements of various steps are prompted using the order of the examples, but are not limited to the specific order prompted.

[0670] The modes / embodiments explained in the present disclosure can also be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (x is an integer, a fraction)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), systems using other appropriate wireless communication methods, next-generation systems extended, modified, created, or specified based on them, and the like. Furthermore, a plurality of systems can also be combined (for example, LTE or LTE-A, in combination with 5G, and the like) to be applied.

[0671] The recitation "based on" used in the present disclosure does not mean "only based on" unless specifically written. In other words, the recitation "based on" means both "only based on" and "at least based on".

[0672] Any reference to an element or apparatus using a designation such as "first," "second," and so on does not limit the quantity or order of those elements, nor does it limit the number of those elements. These designations are used in this disclosure as a convenient method of distinguishing between two or more elements or instances of an element. Thus, a reference to the first and second elements does not mean that only two elements can be employed, or that the first element must precede the second element.

[0673] The term "determining" as used in this disclosure can encompass a wide variety of actions. For example, "determining" can include calculating, computing, processing, deriving, investigating, looking up (such as looking up in a table, a database or another data structure), ascertaining and the like.

[0674] Determining" can also include receiving (e.g., receiving information), transmitting (e.g., transmitting information), inputting, outputting, accessing (e.g., accessing data in a memory) and the like.

[0675] Determining" can also include resolving, selecting, choosing, establishing and the like.

[0676] Determining" can also be reworded as "assuming," "expecting," "considering" and the like.

[0677] The "maximum transmit power" described in this disclosure can mean the maximum value of the transmit power, the nominal maximum transmit power (the nominal UE maximum transmit power), or the rated maximum transmit power (the rated UE maximum transmit power).

[0678] In the present disclosure, the term "connected", "coupled", or all modifications thereof used in the present disclosure mean all connections or couplings between two or more elements directly or indirectly, and can include a case where one or more intermediate elements exist between two elements "connected" or "coupled" with each other. The coupling or connection between elements can be physical, logical, or a combination thereof. For example, "connected" can be rewritten as "accessed".

[0679] In the present disclosure, in a case where two elements are connected, one or more electric wires, cables, printed electric connections, and the like can be considered to be used, and as several non-limiting and non-inclusive examples, electromagnetic energy having a wavelength in a radio frequency domain, a microwave region, an optical (both visible and non-visible) region, and the like is used to be "connected" or "coupled" with each other.

[0680] In the present disclosure, the term "A is different from B" can also mean "A and B are different from each other". In addition, the term can also mean "A and B are different from C, respectively". The terms "separated", "coupled", and the like can also be interpreted in the same manner as "different".

[0681] In the present disclosure, in a case where "include", "including", and modifications thereof are used, these terms mean the same as the term "comprising" and are inclusive. Further, in the present disclosure, the term "or" does not mean the same as "exclusive or".

[0682] In the present disclosure, for example, in a case where an article is added by translation such as a, an, and the in English, the present disclosure can also include a case where a noun following the article is plural.

[0683] In the present disclosure, "below", "less than", "above", "more than", "equal to", and the like can be rewritten with each other. In addition, in the present disclosure, the terms meaning "good", "bad", "large", "small", "high", "low", "early", "late", "wide", "narrow", and the like are not limited to the primary comparative degree and the superlative degree, and can be rewritten with each other. In addition, in the present disclosure, the terms meaning "good", "bad", "large", "small", "high", "low", "early", "late", "wide", "narrow", and the like are not limited to the primary comparative degree and the superlative degree as expressions with "i-th" (i is an arbitrary integer), and can be rewritten with each other (for example, "the highest" can be rewritten with "the i-th highest").

[0684] In the present disclosure, "of", "for", "regarding", "related to", "associated with", and the like can be rewritten to each other.

[0685] The application related to the present disclosure has been described in detail above, but it is obvious to those skilled in the art that the application related to the present disclosure is not limited to the embodiments described in the present disclosure. The application related to the present disclosure can be implemented as a modification and a change without departing from the spirit and scope of the application determined based on the recitations of the claims. Therefore, the recitations of the present disclosure are intended for the purpose of illustrative explanation, and do not have any limiting meaning on the application related to the present disclosure.

Claims

1. A terminal having: a reception unit that receives a first setting indicating whether or not first transform precoding is effective for a first uplink shared channel based on dynamic grant, a second setting indicating whether or not second transform precoding is effective for a second uplink shared channel based on configured grant, and receives first downlink control information that schedules the first uplink shared channel and includes a specific field; and a control unit that controls transmission of the first uplink shared channel based on the first setting and the downlink control information, the specific field being present in a case where the first setting indicates that the first transform precoding is effective, the specific field being absent in a case where the first setting indicates that the first transform precoding is ineffective.

2. The terminal according to claim 1, wherein a size of the specific field within second downlink control information indicating activation or deactivation of the second uplink shared channel is equal to a size of the specific field within the first downlink control information.

3. The terminal according to claim 1, wherein dynamic waveform switching is not set.

4. The terminal according to claim 1, wherein dynamic waveform switching is set.

5. A wireless communication method of a terminal having: a step of receiving a first setting indicating whether or not first transform precoding is effective for a first uplink shared channel based on dynamic grant, and a second setting indicating whether or not second transform precoding is effective for a second uplink shared channel based on configured grant; a step of receiving first downlink control information that schedules the first uplink shared channel and includes a specific field; and a step of controlling transmission of the first uplink shared channel based on the first setting and the downlink control information, the specific field being present in a case where the first setting indicates that the first transform precoding is effective, the specific field being absent in a case where the first setting indicates that the first transform precoding is ineffective.

6. A base station having: a transmission unit that transmits a first setting indicating whether or not first transform precoding is effective for a first uplink shared channel based on dynamic grant, a second setting indicating whether or not second transform precoding is effective for a second uplink shared channel based on configured grant, and transmits first downlink control information that schedules the first uplink shared channel and includes a specific field; and a control unit that controls reception of the first uplink shared channel based on the first setting and the downlink control information, the specific field being present in a case where the first setting indicates that the first transform precoding is effective, the specific field being absent in a case where the first setting indicates that the first transform precoding is ineffective. ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​

Images