Terminal, wireless communication method, and base station

Abstract

A terminal according to an aspect of the present disclosure comprises: a transmission unit that transmits capability information relating to supporting a dynamic conversion precoder instruction in an operation which uses a plurality of component carriers in one band; and a control unit that controls reception of the setting of the dynamic conversion precoder instruction.

Description

Terminal, wireless communication method and base station

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

[0002] Long Term Evolution (LTE) has been specified for the Universal Mobile Telecommunications System (UMTS) network with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). Also, LTE-Advanced (3GPP Rel. 10-14) has been specified with the aim of achieving higher capacity and more advanced features than LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9).

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

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

[0005] In future wireless communication systems, support for a multi-carrier waveform, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM), in addition to a single-carrier waveform, Discrete Fourier Transform-Spread-Orthogonal Frequency Division Multiplexing (DFT-s-OFDM), is being considered.

[0006] However, since conventional waveform configuration is performed by Radio Resource Control (RRC), switching waveforms requires reconfiguration of the RRC, which increases signaling overhead and may reduce communication throughput.

[0007] Therefore, one of the objects of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately switch waveforms.

[0008] A terminal according to one aspect of the present disclosure has a transmitting unit that transmits capability information related to supporting dynamic conversion precoder indication in operation using multiple component carriers within one band, and a control unit that controls reception of the setting of the dynamic conversion precoder indication.

[0009] According to one aspect of the present disclosure, waveform switching can be performed appropriately.

[0010] FIG. 1 is a diagram showing the DCI size of option 1-1. FIG. 2 is a diagram showing the DCI size of option 1-2. FIG. 3 is a flowchart showing an example of processing according to embodiment 0.1. FIG. 4 is a flowchart showing an example of processing according to embodiment 0.2. FIG. 5 is a diagram showing definitions of PTRS-DMRS association and DMRS sequence initialization in the DCI field. FIG. 6 is a diagram showing example configuration patterns for useInterlacePUCCH-PUSCH, resourceAllocation, and RA type. FIG. 7 is a flowchart showing an example of processing according to embodiment 3. FIG. 8 is a diagram showing an example of a MAC payload. FIG. 9 is a diagram showing an example of the number of bits in the RAR grant field. FIG. 10 is a diagram showing example values ​​of a TPC command. FIG. 11 is a diagram showing an example of a Backoff Parameter value. FIG. 12 is a diagram showing an example of an antenna port field in DCI format 0_1. FIG. 13 is a diagram showing an example of DMRS type configuration when dynamic waveform switching is configured. FIGS. 14A and 14B are diagrams showing an example of a method of interpreting code points in predetermined fields of DCI when dynamic waveform switching is configured and DMRS type 2 is configured. FIG. 15 is a diagram illustrating an example of an RRC IE according to embodiment A1. FIG. 16 is a diagram illustrating an example of DCI according to embodiment A4. FIGs. 17A and 17B are diagrams illustrating an example of multicarrier scheduling. FIGs. 18A and 18B are diagrams illustrating another example of multicarrier scheduling. FIG. 19 is a diagram illustrating an example of a 1-bit DWS field in multicarrier DCI. FIG. 20 is a diagram illustrating an example of a waveform indicated for multiple cells according to embodiment B5. FIG. 21 is a diagram illustrating an example of an N-bit DWS field in multicarrier DCI. FIG. 22 is a diagram illustrating an example of UE capabilities related to DWS. FIG. 23 illustrates an example of multiple values ​​of MPR for in-band continuous CA. FIG. 24 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 25 is a diagram illustrating an example of a configuration of a base station according to an embodiment. FIG. 26 is a diagram illustrating an example of a configuration of a user terminal according to an embodiment.Fig. 27 is a diagram illustrating an example of a hardware configuration of a base station and a user terminal according to an embodiment. Fig. 28 is a diagram illustrating an example of a vehicle according to an embodiment.

[0011] (CP-OFDM and DFT-s-OFDM) In the uplink (UL) of a wireless communication system (for example, NR), in addition to a multi-carrier waveform, a Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) waveform, a single-carrier waveform, a Discrete Fourier Transform-Spread-Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) waveform is supported. In this disclosure, "waveform" refers to at least one of a CP-OFDM waveform (a CP-OFDM-based waveform) and a DFT-s-OFDM waveform (a DFT-s-OFDM-based waveform).

[0012] CP-OFDM allows for more flexible frequency resource allocation. For example, both contiguous and non-contiguous Physical Resource Block (PRB) allocation is allowed. Furthermore, contiguous PRB allocation is not limited to multiples of 2, 3, or 5. When CP-OFDM is applied, frequency division multiplexing (FDM) may be used for the demodulation reference signal (DMRS) and the PUSCH.

[0013] DFT-s-OFDM (or DFT-S-OFDM / DFTS-OFDM) has a high frequency resource allocation constraint, but has a low Peak to Average Power Ratio (PAPR), making it suitable for power-limited UEs.

[0014] In addition, with regard to communication throughput without considering PAPR, CP-OFDM has a higher communication throughput than DFT-s-OFDM. With regard to communication throughput with PAPR taken into consideration, when the SNR (MCS) is high (the modulation and coding method is 16QAM or 64QAM), the communication throughput of CP-OFDM is higher than that of DFT-s-OFDM, but when the SNR (MCS) is low (the modulation and coding method is QPSK), the communication throughput of DFT-s-OFDM is higher than that of CP-OFDM. In other words, the preferred waveform differs depending on the SNR (MCS).

[0015] Typically, the network (NW) switches waveforms based on the signal-to-noise ratio (SNR). Switching between DFT-s-OFDM and CP-OFDM is performed by the transform precoder "transformPrecoder" in the uplink shared channel (Physical Uplink Shared Channel (PUSCH)) configuration (PUSCH-Config) of Radio Resource Control (RRC) signaling. When the transform precoder is disabled, CP-OFDM is applied, and when it is enabled, DFT-s-OFDM is applied. Waveform switching requires RRC reconfiguration. This increases signaling overhead and may reduce communication throughput.

[0016] For more flexible throughput control, it is conceivable to dynamically switch between CP-OFDM and DFT-s-OFDM using DCI / MAC CE, but such dynamic switching has not yet been studied.

[0017] For example, in existing specifications (e.g., 3GPP Rel. 16), the sizes of some DCI fields in DCI formats (e.g., DCI formats 0_0 / 0_1 / 0_2) are affected by waveform switching, as shown in the following (1) to (6): (1) In the "Precoding information and number of layers" field, different tables are used for the two waveforms. (2) In the "Antenna ports" field, different tables are used for the two waveforms. (3) In the "DMRS sequence initialization" field, a 0 bit is set when the transform precoder is enabled, and a 1 bit is set when the transform precoder is disabled. (4) In the "PTRS-DMRS association" field, the DCI size is affected by the transform precoder. (5) In the "Frequency domain resource assignment," the DCI size varies depending on the resource allocation type. Also, different waveforms support different resource allocations. CP-OFDM supports resource allocation types 0, 1, and 2, while DFT-s-OFDM supports resource allocation types 1 and 2. (6) In the "Frequency hopping flag" field, the DCI size varies depending on the resource allocation type. As described above, different waveforms support different resource allocations.

[0018] (Dynamic Switching Between Disabling and Activating a Transform Precoder) The UE may receive a configuration indicating dynamic switching of disabling or enabling of a transform precoder for a PUSCH by DCI / MAC CE. Then, the UE may receive an instruction indicating activation or deactivation of a transform precoder for a PUSCH by DCI / MAC CE. Hereinafter, dynamic switching by DCI / MAC CE may be simply referred to as dynamic switching. Note that the UE may be configured in advance by higher layer signaling or the like to dynamically switch (be able to switch) the waveform / transform precoder. Regardless of whether or not such a configuration is present, dynamic switching of the transform precoder by DCI / MAC CE may be possible.

[0019] For example, DCI signaling-based dynamic waveform switching may be performed implicitly or explicitly. For example, a one-bit field indicating the CP-OFDM or DFT-s-OFDM waveform to be used for the PUSCH may be included in the DCI (explicit signaling). For example, the UE may determine / identify the CP-OFDM or DFT-s-OFDM waveform to be used for the PUSCH depending on specific conditions, such as scheduling information in the DCI (implicit signaling). In this case, the existing DCI format remains unchanged. A DCI indicating dynamic UL waveform switching for the PUSCH may schedule the PUSCH.

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

[0021] The DCI format in the present disclosure may indicate, for example, DCI format 0_0 / 0_1 / 0_2, or may be another format (for example, DCI format 0_3 for notifying waveform switching). As another format, for example, a group-wide DCI such as DCI format 2_x may be used. In this case, waveform switching may be applied a certain time after the UE receives DCI format 2_x and transmits an ACK.

[0022] In the present disclosure, the switching between disabling and enabling the transform precoder (waveform switching) may be waveform switching within the same BWP (waveform switching without switching the BWP). For example, since a different transform precoder can be set for each BWP, it is conceivable to switch the transform precoder by BWP switching. However, since a delay occurs due to the BWP switching, the delay can be suppressed by switching between disabling and enabling the transform precoder within the same BWP.

[0023] When the DCI / MAC CE is configured to dynamically switch between disabling and enabling the transform precoder for the PUSCH, the UE may receive an instruction indicating the enabling or disabling of the transform precoder for the PUSCH via the DCI / MAC CE, and may switch the waveform (CP-OFDM / DFT-s-OFDM) used for the PUSCH based on the instruction.

[0024] The total DCI size of the DCI format may be constant regardless of whether the transform precoder is disabled or enabled. The size of the DCI format may be configured / determined by higher layer signaling (RRC). That is, the size of the DCI format may not depend on the DCI / MAC CE.

[0025] However, the size of some DCI fields may differ depending on whether a transform precoder is disabled or enabled. Examples of such DCI fields include "Precoding information and number of layers," "Antenna ports," "DMRS sequence initialization," "PTRS-DMRS association," "Frequency resource assignment," and "Frequency hopping flag." For example, the DCI sizes may differ as shown in (1) to (6) of the existing specifications.

[0026] [Option 1-1] When dynamic switching of transform precoder for PUSCH (switching by DCI / MAC CE) is configured for PUSCH, for each DCI format, the total size of the DCI format may be the larger of the size of each DCI format when the transform precoder is disabled and the size of each DCI format when the transform precoder is enabled.

[0027] If the transform precoder is disabled / enabled by the MAC CE, the UE may read each DCI field starting from the least significant bit (LSB) or most significant bit (MSB), depending on the size of each DCI field.

[0028] Fig. 1 is a diagram showing the DCI size of Option 1-1. According to Fig. 1, the number of DCI bits (total of DCIFields #1 to #4) when the transform precoder is disabled is 10 bits, and the number of DCI bits when the transform precoder is enabled is 7 bits. In this case, the larger DCI size of 10 bits is used as the total DCI size when dynamic switching of the transform precoder is set.

[0029] In Figure 1, the smaller DCI bits (DCI bits when the transform precoder is enabled) are mapped from the left (least significant bit) but may also be mapped from the right (most significant bit), i.e. the UE may read each DCI field from the least significant bit or from the most significant bit.

[0030] Option 1-1 allows the total DCI size to be reduced compared to Option 1-2 described below.

[0031] [Option 1-2] When dynamic switching of transform precoder for PUSCH is configured for PUSCH, for each DCI format, the larger of the size of the DCI field when the transform precoder is disabled and the size of the DCI field when the transform precoder is enabled is determined for each field, and the total size of the DCI format may be the sum of the larger sizes of all DCI fields.

[0032] That is, when the number of fields in a certain DCI format is N, the total size of the DCI format is calculated as follows: Total size of DCI format = Σ (MAX (size of DCI field i when transform precoder is disabled, size of DCI field i when transform precoder is enabled)) (i = 1 to N).

[0033] If the transform precoder is disabled / enabled by the MAC CE, the UE may read each DCI field starting from the least significant bit (LSB) or the most significant bit (MSB), depending on the size of each DCI field.

[0034] Figure 2 shows the DCI size for Option 1-2. According to Figure 2, in DCI Field #1, the larger of the DCI field size when the transform precoder is disabled (2 bits) and the DCI field size when the transform precoder is enabled (1 bit) is 2 bits. Similarly, the larger size is 3 bits for DCI Field #2, 2 bits for DCI Field #3, and 4 bits for DCI Field #4. By adding these sizes together (2 + 3 + 2 + 4 = 11), a total DCI size of 11 bits is used when dynamic transform precoder switching is configured.

[0035] In Figure 2, in each field, the smaller DCI bits are mapped from the left (least significant bit) to the right (most significant bit) to the left, but they may also be mapped from the right (most significant bit) to the left, i.e., the UE may read each DCI field from the least significant bit or from the most significant bit.

[0036] In the example of Figure 2, the starting bit of each field (the bit range used for each field) is the same whether the transform precoder is enabled or disabled. For example, DCI Field #1 starts at the first bit, DCI Field #2 starts at the third bit, DCI Field #3 starts at the sixth bit, and DCI Field #4 starts at the eighth bit. This facilitates the UE's detection of each field.

[0037] In option 1-2, even if the transform precoder is switched between enabled and disabled, the detected DCI size remains the same, so the increase in the processing load on the UE can be suppressed.

[0038] (FDRA Types) NR supports three types of Frequency Domain Resource Allocation (FDRA): Type 0, Type 1, and Type 2. Type 0: Allocation based on a bitmap (i.e., may be non-contiguous). Type 1: Contiguous allocation based on a Resource Indication Value (RIV). Type 2: Interlaced arrangement (for NR-unlicensed (U)).

[0039] The applicability of each type, which depends on the PUSCH waveform, is supported as follows: Type 0: Applicable to CP-OFDM only. Type 1: Applicable to both CP-OFDM and DFTS-OFDM. Type 2: Applicable to both CP-OFDM and DFTS-OFDM.

[0040] If the RRC parameter useInterlacePUCCH-PUSCH is not configured, Type 0 or Type 1 is used according to the RRC parameter resourceAllocation. When Type 1 UL data is transmitted without a grant, resourceAllocation is set to resourceAllocationType0 or resourceAllocationType1. If resourceAllocationType0 is set, Type 0 is used, and if resourceAllocationType1 is set, Type 1 is used. If dynamicSwitch is set, Type 0 or Type 1 is indicated by the scheduling DCI (MSB of FDRA). If useInterlacePUCCH-PUSCH is set, Type 2 is used.

[0041] (DMRS) The front-loaded DMRS is the first DMRS (at or near the first symbol) for faster demodulation. An additional DMRS can be configured by RRC for fast-moving UEs or high modulation and coding scheme (MCS) / rank. The frequency location of the additional DMRS is the same as that of the front-loaded DMRS.

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

[0043] The DMRS location is defined by a table in the specification and depends on the duration of the PDSCH / PUSCH. The location of the additional DMRS is fixed.

[0044] In the frequency domain, (PDSCH / PUSCH) DMRS configuration type 1 or 2 is configured. DMRS configuration type 1 has a comb structure and is applicable to both CP-OFDM (transport precoding disabled) and DFT-S-OFDM (transport precoding enabled). DMRS configuration type 1 maps a DMRS sequence to one subcarrier for every two subcarriers in the frequency domain, allowing up to two DMRSs to be FDM-multiplexed. DMRS configuration type 2 is applicable only to CP-OFDM. DMRS configuration type 2 maps a DMRS sequence to two consecutive subcarriers for every six subcarriers in the frequency domain, allowing up to three DMRSs to be FDM-multiplexed.

[0045] Single symbol DMRS or double symbol DMRS is configured.

[0046] Single-symbol DMRS is normally used (it is a mandatory feature in Rel. 15). In single-symbol DMRS, the number of additional DMRS (symbols) is {0, 1, 2, 3}. Single-symbol DMRS supports both frequency hopping enabled and disabled. If the maximum number (maxLength) in the uplink DMRS configuration (DMRS-UplinkConfig) is not configured, single-symbol DMRS is used.

[0047] 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 is supported when frequency hopping is disabled. If the maximum number (maxLength) in the uplink DMRS configuration (DMRS-UplinkConfig) is 2 (len2), whether single-symbol DMRS or double-symbol DMRS is used is determined by the DCI or configured grant.

[0048] From the above, the possible DMRS configuration patterns are the following combinations: DMRS configuration type 1, DMRS mapping type A, single symbol DMRS DMRS configuration type 1, DMRS mapping type A, double symbol DMRS DMRS configuration type 1, DMRS mapping type B, single symbol DMRS DMRS configuration type 1, DMRS mapping type B, double symbol DMRS DMRS configuration type 2, DMRS mapping type A, single symbol DMRS DMRS configuration type 2, DMRS mapping type A, double symbol DMRS DMRS configuration type 2, DMRS mapping type B, single symbol DMRS DMRS configuration type 2, DMRS mapping type B, double symbol DMRS

[0049] Multiple DMRS ports that are mapped to the same RE (time and frequency resource) are called a DMRS code division multiplexing (CDM) group.

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

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

[0052] For DMRS configuration type 2 and single-symbol DMRS, six DMRS ports can be used. Within each DMRS CDM group, two DMRS ports are multiplexed using an FD OCC of length 2. Between multiple DMRS CDM groups (three DMRS CDM groups), three DMRS ports are multiplexed using FDM.

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

[0054] Here, an example of DMRS mapping type B is shown, but DMRS mapping type A is also similar.

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

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

[0057] (Ports of Reference Signals) For orthogonalization of MIMO layers, reference signals of multiple ports (for example, demodulation reference signals (DMRS) and CSI-RS) are used.

[0058] For example, for single user MIMO (SU-MIMO), a different DMRS port / CSI-RS port may be set for each layer. For multi user MIMO (MU-MIMO), a different DMRS port / CSI-RS port may be set for each layer within one UE and for each UE.

[0059] In addition, if the number of CSI-RS ports is greater than the number of layers used for data, it is possible to measure the channel state more accurately based on this CSI-RS, which is expected to contribute to improving throughput.

[0060] In Rel. 15 NR, multiple-port DMRS is supported using frequency division multiplexing (FDM), frequency domain orthogonal cover code (FD-OCC), time domain OCC (TD-OCC), etc., with up to eight ports for Type 1 DMRS (i.e., DMRS configuration type 1) and up to 12 ports for Type 2 DMRS (i.e., DMRS configuration type 2).

[0061] In Rel. 15 NR, a comb-like transmission frequency pattern (comb-like resource set) is used for the FDM. Cyclic Shift (CS) is used for the FD-OCC. Furthermore, the TD-OCC can only be applied to double-symbol DMRS.

[0062] The OCC in the present disclosure may be interchangeably read as orthogonal code, orthogonalization, cyclic shift, and the like.

[0063] The type of DMRS may be referred to as a DMRS configuration type.

[0064] Among DMRSs, DMRSs that are resource mapped in units of two consecutive (adjacent) symbols may be called double-symbol DMRSs, and DMRSs that are resource mapped in units of one symbol may be called single-symbol DMRSs.

[0065] Either DMRS may be mapped to one or more symbols per slot depending on the length of the data channel. A DMRS mapped to the beginning of a data symbol may be called a front-loaded DMRS, and a DMRS additionally mapped to other positions may be called an additional DMRS.

[0066] In the case of DMRS configuration type 1 and single-symbol DMRS, Comb and CS may be used for orthogonalization. For example, up to four antenna ports (APs) may be supported by using two types of Comb and two types of CS (Comb2+2CS).

[0067] In the case of DMRS configuration type 1 and double-symbol DMRS, the comb, CS, and TD-OCC may be used for orthogonalization. For example, up to eight APs may be supported using two types of comb, two types of CS, and TD-OCC ({1,1} and {1,-1}).

[0068] In the case of DMRS configuration type 2 and single-symbol DMRS, FD-OCC may be used for orthogonalization. For example, up to six APs may be supported by applying an orthogonal code (2-FD-OCC) to two adjacent resource elements (REs) in the frequency direction.

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

[0070] In addition, in Rel. 15 NR, a maximum of 32 ports of the multi-port CSI-RS are supported by using FDM, time division multiplexing (TDM), frequency domain OCC, time domain OCC, etc. The same method as that for the above-mentioned DMRS may also be applied to orthogonalization of the CSI-RS.

[0071] Now, a group of DMRS ports orthogonalized by the FD-OCC / TD-OCC as described above is also called a Code Division Multiplexing (CDM) group.

[0072] Different CDM groups are orthogonal because they are FDM-encoded. However, within the same CDM group, the orthogonality of the applied OCC may be lost due to channel fluctuations, etc. In this case, if signals within the same CDM group are received with different reception powers, a near-far problem may occur, and orthogonality may not be guaranteed.

[0073] Here, we will explain the TD-OCC / FD-OCC of DMRS in Rel. 15 NR. The DMRS mapped to a resource element (RE) is a DMRS sequence with FD-OCC parameters (which may also be called sequence elements) w ｆ(k') and the TD-OCC parameters (which may also be called sequence elements) w ｔ (l') and may correspond to a sequence obtained by multiplying (l') and (l').

[0074] The TD-OCC and FD-OCC of the DMRS of Rel. 15 NR both correspond to OCCs with a sequence length (which may also be referred to as the OCC length) of 2. Therefore, the possible values ​​of k' and l' above are both 0 and 1. By multiplying this FD-OCC in RE units, two-port DMRS can be multiplexed using the same time and frequency resources (2 RE). When both the FD-OCC and TD-OCC are applied, four-port DMRS can be multiplexed using the same time and frequency resources (4 RE).

[0075] The two Rel. 15 DMRS port tables for PDSCH (association of antenna port indexes (numbers) with parameters) described above correspond to DMRS configuration type 1 and type 2, respectively. Note that p indicates the antenna port number, and Δ indicates a parameter for shifting (offsetting) the frequency resource.

[0076] For example, for antenna ports 1000 and 1001, {w ｆ (0), w ｆ (1)} = {+1, +1} and {w ｆ (0), w ｆ (1)}={+1, -1} is applied to the vectors, and the vectors are orthogonalized using FD-OCC.

[0077] FDM is applied to antenna ports 1000-1001 and antenna ports 1002-1003 (and also antenna ports 1004-1005 in the case of Type 2) by applying different values ​​of Δ. Thus, antenna ports 1000-1003 (or 1000-1005) corresponding to single-symbol DMRS are orthogonalized using FD-OCC and FDM.

[0078] For the antenna ports 1000-1003 and the antenna ports 1004-1007 of type 1, {w ｔ (0), w ｔ(1)} = {+1, +1} and {w ｔ (0), w ｔ (1)}={+1, −1} is applied, and thus the antenna ports 1000-1007 (or 1000-1011) corresponding to the double-symbol DMRS are orthogonalized using FD-OCC, TD-OCC, and FDM.

[0079] For CP-OFDM only, it is considered to specify a larger number of orthogonal DMRS ports for DL / UL MU-MIMO (without increasing DMRS overhead), a common design between DL and UL DMRS, up to 24 orthogonal DMRS ports, and doubling the maximum number of orthogonal DMRS ports for both single-symbol DMRS and double-symbol DMRS for each applicable DMRS configuration type.

[0080] In Rel. 15, the following Cases 1 to 4 can be configured. [Case 1] The total number of single-symbol DMRS ports in DMRS configuration type 1 is 2 (by comb / FDM) × (by FD OCC) 2 = 4 ports. [Case 2] The total number of double-symbol DMRS ports in DMRS configuration type 1 is 2 (by comb / FDM) × (by FD OCC) 2 × (by TD OCC) 2 = 8 ports. [Case 3] The total number of single-symbol DMRS ports in DMRS configuration type 2 is 3 (by FDM) × (by FD OCC) 2 = 6 ports. [Case 4] The total number of double-symbol DMRS ports in DMRS configuration type 2 is 3 (by comb) × (by FD OCC) 2 × (by TD OCC) 2 = 12 ports.

[0081] In Rel. 18, it is considered to double the total number of DMRS ports to 8, 16, 12, and 24 for Cases 1, 2, 3, and 4, respectively.

[0082] To increase the number of DMRS ports, the following five options (methods for increasing the number of DMRS ports) are being considered.

[0083] <Option 1> - Introducing a new OCC with a length greater than that of the existing OCC (for example, 4 or 6). In Option 1, the following issues need to be considered: possible performance degradation when the delay spread is large, possible scheduling restrictions, and backward compatibility.

[0084] <Option 2> Use of TD-OCC on multiple discontinuous DMRS symbols (e.g., TD-OCC on front-loaded DMRS / additional DMRS). Option 2 addresses the following issues: possible performance degradation when UE speed is high, possible scheduling limitations (e.g., frequency hopping application method), possible limitations on DMRS configuration (e.g., limited number of additional DMRS), and backward compatibility.

[0085] <Option 3> - Increase the number of CDM groups (for example, increase the number of comb / FDM). In option 3, the possibility of performance degradation when the delay spread is large and backward compatibility are considered.

[0086] <Option 4> Reuse symbols for additional DMRS and increase the number of orthogonal DMRS ports. Option 4 has several issues to consider, including the possibility of performance degradation when UE speed is high, the possibility of DMRS configuration being limited (e.g., the number of additional DMRS is limited), and backward compatibility.

[0087] <Option 5> Use of TD-OCC on discontinuous multiple DMRS symbols combined with FD-OCC / FDM (reusing symbols of additional DMRS to improve channel estimation performance). Option 5 addresses the following issues: possible performance degradation at high UE speeds, possible scheduling limitations (e.g., frequency hopping application method), possible limitations on DMRS configuration (e.g., limited number of additional DMRS), and backward compatibility.

[0088] In Option 1, the new FD-OCC for DMRS of PDSCH / PUSCH may follow at least one of the following options for DMRS Extension Type 1: <<Option 1-1>> A new FD-OCC of length 6 is applied to 6 REs of DMRS in one PRB in one CDM group. <<Option 1-2>> A new FD-OCC of length 4 is applied to 4 REs of DMRS in one PRB or across multiple consecutive PRBs in one CDM group.

[0089] In Option 1, the new FD-OCC for DMRS of PDSCH / PUSCH has a length of 4 and is applied to 4 REs of DMRS in one PRB in one CDM group for DMRS Extension Type 2. A new FD-OCC of length 6 may also be supported for DMRS Extension Type 2.

[0090] In the present disclosure, existing FD-OCC#0=[+1 +1] and existing FD-OCC#1=[+1 -1] may also be used.

[0091] The new FD-OCC may be any of several OCCs:

[0092] [OCC1-1] OCC of length 4 based on a 4x4 Walsh matrix (sequence). Four sequences are obtained for OCC index i={0,1,2,3}.

[0093] [OCC1-2] Length-4 OCC based on cyclic shift. For OCC index i={0,1,2,3}, four sequences are obtained by using cyclic shifts {i·0,i·π / 2,i·π,i·3π / 2}.

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

[0095] In this disclosure, the OCC (FD-OCC / TD-OCC) corresponding to OCC index i may be referred to as OCC#i.

[0096] Some of the sequences of the new FD-OCC may be associated with a Rel. 15 DMRS port index.

[0097] When a length 2 FD-OCC is used, the Rel. 15 DMRS port table for DMRS configuration type 1 and the Rel. 15 DMRS port table for DMRS configuration type 2 may be used.

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

[0099] In the present disclosure, DMRS setting type 1, DMRS type 1, DMRS type = 1, and DMRS Type 1 may be interchangeable. In the present disclosure, DMRS setting type 2, DMRS type 2, DMRS type = 2, and DMRS Type 2 may be interchangeable.

[0100] In the present disclosure, extended DMRS configuration type 1, DMRS extended type 1, DMRS extended type=1, DMRS eType 1, and Rel. 18 DMRS type 1 may be interchangeable. In the present disclosure, extended DMRS configuration type 2, DMRS extended type 2, DMRS extended type=2, DMRS eType 2, and Rel. 18 DMRS type 2 may be interchangeable.

[0101] In the present disclosure, the DMRS maximum length and maxLength may be read interchangeably.

[0102] In this disclosure, existing FD-OCC, length 2 FD-OCC, Rel. 15 FD-OCC, w f (k') may be interchangeable. In each embodiment, the new FD-OCC, the FD-OCC longer than 2, the Rel. 18 FD-OCC, w f (k') may be read interchangeably.

[0103] The Rel. 18 DMRS port table may indicate the DMRS port (p is 0 or greater) corresponding to the new FD-OCC. At least some of the values ​​of p in the Rel. 18 DMRS port table may overlap with the values ​​of p in the Rel. 15 DMRS port table. If the UE is configured / instructed to use the new FD-OCC, the UE may use the Rel. 18 DMRS port table; if the UE is not configured / instructed to use the new FD-OCC, the UE may use the Rel. 15 DMRS port table.

[0104] For DMRS ports with new FD-OCC#0 and #1 in DMRS Extension Type 1, the same DMRS port indexes as those of Rel. 15 DMRS ports (DMRS ports 0 to 7) may be used. For DMRS ports with new FD-OCC#2 and #3, different DMRS port indexes (DMRS ports 8 to 15) may be used.

[0105] For DMRS ports with new FD-OCC#0 and #1 in DMRS Extension Type 2, the same DMRS port indexes (DMRS ports 0 to 11) as those of Rel. 15 DMRS ports may be used. For DMRS ports with new FD-OCC#2 and #3, different DMRS port indexes (DMRS ports 12 to 23) may be used.

[0106] (Analysis) Conventionally, waveform configuration was performed by Radio Resource Control (RRC), so RRC reconfiguration was required to switch waveforms. This increases signaling overhead and may reduce communication throughput. Therefore, as described above, dynamic switching of the conversion precoder for PUSCH (switching by DCI / MAC CE) can easily (fastly) switch waveforms. However, in this case, various settings / controls are not clearly defined, as shown in the following problems 0 to 4.

[0107] Therefore, the present inventors came up with the idea of ​​a terminal that appropriately and dynamically switches between disabling and enabling a transform precoder for PUSCH (switching of waveforms).

[0108] (Various Replacements, etc.) Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. Wireless communication methods according to the embodiments may be applied independently or in combination.

[0109] In the present disclosure, "A / B" and "at least one of A and B" may be interpreted interchangeably. Also, in the present disclosure, "A / B / C" may mean "at least one of A, B, and C."

[0110] In the present disclosure, terms such as notify, activate, deactivate, indicate (or indicate), select, configure, update, and determine may be read interchangeably. In the present disclosure, terms such as support, control, controllable, operate, and operate may be read interchangeably.

[0111] In the present disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher layer parameters, fields, information elements (IEs), settings, etc. may be interchangeable. In the present disclosure, Medium Access Control (MAC) control elements (CEs), update commands, activation / deactivation commands, etc. may be interchangeable.

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

[0113] In the present disclosure, MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. Broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.

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

[0115] In this disclosure, "having the capability of..." may be read interchangeably as "supporting / reporting the capability of...".

[0116] In the present disclosure, ceil(x), ceiling function, and ceiling function may be interchangeable. In the present disclosure, floor(x), floor function, and floor function may be interchangeable. In the present disclosure, sqrt(x) and square root may be interchangeable. In the present disclosure, x mod y, mod(x,y), mod function, and modulo operation may be interchangeable. In the present disclosure, Σ i=M N f(i), the summation of f(i) over i = M, M+1,...,N, and f(M) + f(M+1) +... + f(N) can be interpreted interchangeably. C(n,k) is the number of combinations of k values ​​from n values ​​(combinatorial coefficient), binomial coefficient, n C k , C n k, may be read interchangeably.

[0117] In this disclosure, a b , a_b, and a with b added to the bottom right of a may be read interchangeably. c , a^c, and the notation of a with c added to the upper right of a may be read interchangeably. b c , a_b^c, and the notation in which b is added to the bottom right of a and c is added to the top right may be read interchangeably. ~ may be expressed by adding 〜 to the x, or may be referred to as x tilde. - may be represented by an x ​​with a - or may be called an x-bar.

[0118] In the present disclosure, the frequency range corresponding to FR1 may be 410-7125 MHz. In the present disclosure, FR2 may include FR2-1 and FR2-2, and the frequency range corresponding to FR2-1 may be 24250-52600 MHz, and the frequency range corresponding to FR2-1 may be 52600-71000 MHz.

[0119] In the present disclosure, the application / use of CP-OFDM and the disablement (disablement) of the transform precoder may be interchangeable. The application / use of DFT-s-OFDM and the enablement (enablement) of the transform precoder may be interchangeable. The disablement / enablement of the transform precoder, the switching of the transform precoder, and the switching of the waveform (CP-OFDM / DFT-s-OFDM) may be interchangeable. The PUSCH waveform, waveform, and transform precoder may be interchangeable. The CP-OFDM and CP-OFDM waveform may be interchangeable. The DFT-s-OFDM and DFT-s-OFDM waveform may be interchangeable. Enabled and on may be interchangeable. Disabled and off may be interchangeable.

[0120] In the present disclosure, the terms "it is possible to dynamically switch the PUSH waveform," "the PUSH waveform is configured to be dynamically switched," "DWS is configured," and "DWS is enabled" may be interpreted as interchangeable.

[0121] In the present disclosure, the DMRS type, the DMRS type in the uplink DMRS configuration (dmrs-Type in DMRS-UplinkConfig), and the DMRS configuration type (DMRS configuration type) may be interchangeable. In the present disclosure, the DMRS type 1, a type in which a DMRS can be allocated to 6 REs per 1 RB in the frequency domain, may be interchangeable. In the present disclosure, the DMRS type 2, a type in which a DMRS can be allocated to 4 REs per 1 RB in the frequency domain, may be interchangeable.

[0122] In the present disclosure, DMRS Type 1 and enhanced DMRS Type 1 (DMRS-eType1) may be interchangeable. In the present disclosure, DMRS Type 2 and enhanced DMRS Type 2 (DMRS-eType2) may be interchangeable. In other words, embodiments applicable to DMRS Types 1 and 2 may be applicable to enhanced DMRS Types 1 and 2.

[0123] In the DCI format 0_X of the present disclosure, X may be 0 / 1 / 2 / 3 or a combination of numbers and letters.

[0124] In the present disclosure, the first field, the field for multicarrier scheduling, and the field for time domain resource assignment / allocation (TDRA) / frequency domain resource assignment / allocation (FDRA) for multicarrier scheduling may be read as interchangeable.

[0125] In the present disclosure, the terms second field, DWS field, DWS indicator, DWS indication, and DWS instruction may be read interchangeably.

[0126] In the present disclosure, the third field, the specific field, the specific DCI field, and at least one field of DMRS sequence initialization, PTRS-DMRS association, antenna port, and TPMI (precoding information and number of layers) may be read as interchangeable.

[0127] In the present disclosure, the DWS setting, the DWS setting of 'enabled', and the upper layer parameters dynamicTransformPrecoderIndicationDCI-0-1 / dynamicTransformPrecoderIndicationDCI-0-2 may be interchangeable. In the present disclosure, the DWS indication, the DWS indication in DCI, the DWS field, and the transform precoder indicator field may be interchangeable. In the present disclosure, the DWS indication of a bit value of 0, the indication that the transform precoder is enabled, and the indication of DFT-s-OFDM may be interchangeable. In the present disclosure, the DWS indication of a bit value of 1, the indication that the transform precoder is disabled, and the indication of CP-OFDM may be interchangeable.

[0128] (Wireless Communication Method) As described above, the UE may receive a configuration indicating dynamic switching of disabling or enabling of a transform precoder for a PUSCH by a DCI / MAC CE. Then, the UE may receive an instruction indicating the enabling or disabling of a transform precoder for a PUSCH by a DCI / MAC CE. That is, the UE may be able to dynamically switch the PUSCH waveform. In this case, at least one of the processes of several embodiments below may be applied.

[0129] In the present disclosure, if the PUSCH waveform can be dynamically switched, at least one of the methods described above (dynamically switching between disabling and enabling the transform precoder) may be applied.

[0130] <Problem X0> When the PUSCH waveform can be dynamically switched, it is not clear what values ​​are set to the RRC parameters transformPrecoder and maxRank. For example, transformPrecoder is expected to have a value corresponding to either enabled (i.e., DFT-s-OFDM), disabled (i.e., CP-OFDM), or no restriction. For example, the setting of the RRC parameter transformPrecoder affects the DCI size, which in turn affects the UE processing load and communication overhead, so it is preferable to clarify this.

[0131] <Embodiment X0.1> When a UE is capable of dynamically switching the PUSCH waveform, any of the following configurations may be applied to an RRC parameter transform precoder (transformPrecoder).

[0132] [Aspect 1] When the PUSCH waveform can be dynamically switched, the RRC parameter transformPrecoder may be set to enabled. This reduces the DCI size assumed by the UE. That is, the NW (base station, gNB) can set the DCI size to be small, thereby suppressing communication overhead.

[0133] [Aspect 2] When the PUSCH waveform can be dynamically switched, the RRC parameter transformPrecoder may be set to disabled. As a result, even if the PUSCH waveform is switched to DFT-s-OFDM, the UE assumes the same DCI size as CP-OFDM, thereby reducing the processing load on the UE.

[0134] [Aspect 3] When the PUSCH waveform can be dynamically switched, the RRC parameter transformPrecoder may be ignored, that is, there may be no restriction on transformPrecoder.

[0135] 3 is a flowchart illustrating an example of a process of embodiment X0.1. When a UE receives a setting indicating that dynamic switching of a PUSCH waveform is possible (step S101), the UE receives an RRC parameter transformPrecoder in which enabled / disabled is set (step S102).

[0136] There are multiple transformPrecoders as RRC parameters, but the transformPrecoder referenced by the UE may differ for each case (each timing). For example, the following options 1 and 2 may be applied. When dynamic switching of the PUSCH waveform is configured, the processing of the following options 1 and 2 may be applied at a timing before an instruction to dynamically switch the PUSCH waveform is issued.

[0137] [Option 1] The UE may refer to / consider the transformPrecoder in the RRC IE (e.g., PUSCH-Config or ConfiguredGrantConfig) corresponding to the PUSCH to be transmitted. This option may be applied to the UE after dedicated (UE-specific) RRC configuration.

[0138] [Option 2] The UE may refer to / consider the transformPrecoder in a specific RRC IE (e.g., msg3-transformPrecoder in RACH-ConfigCommon) regardless of the PUSCH type. This option may be applied to the UE before dedicated (UE-specific) RRC configuration.

[0139] According to the present embodiment, it is possible to clarify the value to be set and the operation of the UE for the RRC parameter transformPrecoder when it is possible to dynamically switch the PUSCH waveform.

[0140] <Embodiment X0.2> When a UE can dynamically switch PUSCH waveforms, the UE may receive a value / setting based on any of the following aspects / options as the maximum rank (maxRank) of an RRC parameter. That is, the UE may assume application of any of the following aspects / options for the value / setting of maxRank. 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 maxRank.

[0141] [Aspect 1] There may be no restrictions on the setting of maxRank. In other words, even if dynamic switching of PUSCH waveforms is configured, any value may be set to maxRank.

[0142] [Aspect 2] maxRank may be set to a specific value or a value smaller than a specific value. The specific value may be determined (fixed) by specifications, for example. Alternatively, the specific value may be set / indicated by RRC / MAC CE / DCI. For example, when dynamic switching of PUSCH waveforms is configured, maxRank (specific value) may be 1.

[0143] When maxRank is limited, for example, if maxRank can only be set to 1, the bit width of the Transmitted Precoding Matrix Indicator (TPMI) is the same regardless of the waveform of the PUSCH. In other words, the DCI size is the same, so the processing load of the UE can be reduced.

[0144] 4 is a flowchart showing an example of a process of embodiment X0.2. FIG. 4 shows an example of the above-mentioned aspect 2. When the UE receives a configuration indicating that dynamic switching of the PUSCH waveform is possible (step S201), the UE receives a configuration indicating a specific value or a value smaller than the specific value as the value of the RRC parameter maxRank (step S202).

[0145] According to this embodiment, it is possible to clarify the value to be set for the RRC parameter maxRank when it is possible to dynamically switch the PUSCH waveform.

[0146] <Problem X1> When the PUSCH waveform can be dynamically switched, it is unclear how to handle DCI fields that may be present (1 bit or more) or absent (0 bit) depending on the PUSCH waveform. The DCI fields are, for example, PTRS-DMRS association and DMRS sequence initialization.

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

[0148] <Embodiment X1> When the PUSCH waveform is dynamically switchable and a specific waveform is instructed for the PUSCH, the UE may process (assume) a specific field of the scheduling DCI for the PUSCH based on a specific rule.

[0149] The specific field of the DCI may be at least one of a Demodulation Reference Signal (DMRS) sequence initialization field, a Phase Tracking Reference Signal (PTRS)-DMRS association field.

[0150] A particular rule may be that the UE ignores certain fields of the DCI.

[0151] The particular waveform may be DFT-s-OFDM or CP-OFDM.

[0152] For example, if a UE receives a DCI in which the PUSH waveform is dynamically switchable and DFT-s-OFDM is indicated for the PUSH, the UE ignores at least one of the DMRS sequence initialization field and the PTRS-DMRS association field of the DCI.

[0153] Without being limited to the above example, if the condition that the DMRS sequence initialization field or the PTRS-DMRS association field in Fig. 5 is 0 is satisfied, the UE may ignore that field, thereby reducing the processing load on the UE.

[0154] In embodiment X1, when the PUSCH waveform is dynamically switched, regardless of the exact waveform used by the UE, the number of bits in each DCI field / total DCI size may follow the rules for CP-OFDM, or the number of bits in each DCI field / total DCI size may not follow the rules for CP-OFDM.

[0155] <Problem X2> As explained above (FDRA type), Type 0 RA cannot be used for DFT-s-OFDM, so when the PUSCH waveform is switched to DFT-s-OFDM, Type 1 or Type 2 must be used. For example, it is preferable that the RRC parameters indicating the PUSCH waveform always correspond to the setting / instruction of the FDRA type. However, when the PUSCH waveform is dynamically switched, the setting of FDRA and the interlace use instruction (useInterlacePUCCH-PUSCH) is not clear.

[0156] <Embodiment X2> When the PUSCH waveform is dynamically switchable and a specific waveform is instructed for the PUSCH, the UE may receive specific fields of DCI and specific RRC parameters corresponding to scheduling of the PUSCH based on a specific rule (or may assume reception of the specific fields of the DCI and the specific RRC parameters). The UE may control PUSCH transmission based on the specific fields of the received DCI and the specific RRC parameters.

[0157] The particular field of the DCI may be the FDRA or frequency hopping flag.

[0158] The specific RRC parameter may be resource allocation (resourceAllocation) or interlace usage indication for PUCCH and PUSCH (useInterlacePUCCH-PUSCH).

[0159] The particular waveform may be DFT-s-OFDM or CP-OFDM.

[0160] A specific rule may be that resourceAllocation is either resourceAllocationType1 or dynamicSwitch. If resourceAllocation is dynamicSwitch, the most significant bit (MSB) of FDRA must be "1". That is, type 1 of FDRA must be indicated. This specific rule may be applied when useInterlacePUCCH-PUSCH is not configured.

[0161] A specific rule may be that resourceAllocation is of resourceAllocationType1.

[0162] The specific rule may be that the frequency hopping flag is determined according to at least one of resourceAllocation and FDRA based on the specific rule.

[0163] The specific rule may be that useInterlacePUCCH-PUSCH (use of interlace for PUCCH and PUSCH) is set to enabled (use of interlace for PUCCH and PUSCH).

[0164] [Specific Example] For example, when the PUSCH waveform is dynamically switchable and DFT-s-OFDM is instructed for the PUSCH, the UE may receive (or may assume reception of) configuration information (RRC parameters) indicating dynamic switching (dynamicSwitch) as resourceAllocation and instruction information (DCI) indicating Type 1 as FDRA. The UE may control PUSCH transmission based on the configuration information and instruction information.

[0165] For example, when the PUSCH waveform is dynamically switchable and DFT-s-OFDM is instructed for the PUSCH, the UE may receive (or may assume to receive) configuration information (RRC parameters) indicating type 1 (resourceAllocationType1) as resourceAllocation. The UE may control PUSCH transmission based on the configuration information.

[0166] For example, the UE may receive (or may assume reception of) configuration information indicating that useInterlacePUCCH-PUSCH (use of interlace for PUCCH and PUSCH) is enabled when the PUSCH waveform is dynamically switchable and DFT-s-OFDM is indicated for PUSCH. The UE may control PUSCH transmission based on the configuration information.

[0167] 6 is a diagram showing example configuration patterns of useInterlacePUCCH-PUSCH, resourceAllocation, and RA type. When dynamic waveform switching is possible, the following (1) and (2) may be applied to the configuration patterns shown in FIG. 6. (1) When the default value of transformPrecoder is disabled (CP-OFDM is indicated / used), the UE can expect any pattern, but when it is enabled (DFT-s-OFDM is indicated / used), patterns 1-1 and 1-3 may not be applicable. (2) When the default value of transformPrecoder is enabled, the UE can expect patterns other than patterns 1-1 and 1-3 that apply DCI indicating type 0, but when CP-OFDM is indicated / used, any pattern may be expected.

[0168] The process of this embodiment may be applied regardless of the waveform specified for the PUSCH. That is, when the PUSCH waveform is dynamically switchable, the UE may control the specific fields of the DCI corresponding to the scheduling of the PUSCH and the specific RRC parameters based on the specific rules.

[0169] According to this embodiment, even when the PUSH waveform is dynamically switched, it is possible to avoid cases in which an error occurs (for example, when DFT-s-OFDM is applied, FDRA of type 0 is set).

[0170] <Problem X3> When the PUSCH waveform can be dynamically switched, the type of PUSCH that can be applied is not clear. For example, it is not clear whether message 3 (Msg3) / message A (msg3-TransformPrecoder / msgA-TransformPrecoder) can be applied as the PUSCH. Also, it is not clear whether CG-PUSCH (transformPrecoder of ConfiguredGrantConfig) can be applied as the PUSCH. Furthermore, when dynamic switching of the PUSCH waveform is supported for these PUSCHs, it is not clear what processing is performed.

[0171] <Embodiment X3> The UE may apply dynamic switching of PUSCH waveforms only to a specific type of PUSCH. That is, when the UE receives a configuration indicating dynamic switching of PUSCH waveforms, the UE may control dynamic switching of only the specific type of PUSCH based on DCI / MAC CE. The specific type of PUSCH may be, for example, at least one of (1) to (4) below.

[0172] (1) DCI Grant (DG)-PUSCH (PUSCH scheduled by DCI); (2) Type 1 Configured Grant (CG)-PUSCH (PUSCH transmission configured by higher layer signaling); (3) Type 2 CG-PUSCH (PUSCH transmission configured by higher layer signaling and activated / deactivated by DCI); (4) Random Access Response (RAR)-scheduled PUSCH (Message 3 PUSCH or Message A PUSCH). This RAR can be a contention-based random access (CBRA) RAR or a contention-free random access (CFRA) RAR. For example, in CFRA, the base station (gNB) knows the UE and its channel conditions and can adjust the waveform appropriately.

[0173] 7 is a flowchart illustrating an example of a process of embodiment X3. When the UE receives a setting indicating that dynamic switching of the PUSCH waveform is possible (step S301), the UE controls so that only the waveform of a specific type of PUSCH is dynamically switched based on DCI / MAC CE (step S302).

[0174] <Embodiment X4.1> Dynamic switching of a Type 1 CG-PUSCH (PUSCH transmission configured by higher layer signaling) waveform may be applied, and at least one of the following methods (1-1) to (1-4) may be supported. As a specific method of the following methods (1-1) to (1-4), the above-mentioned method (dynamic switching of disabling and enabling of a transform precoder) may be applied.

[0175] (1-1) The UE may receive an explicit indication by a DCI indicating whether transformPrecoder is enabled / disabled (DFT-s-OFDM / CP-OFDM) (explicit signaling). (1-2) The UE may receive an implicit indication by a DCI indicating whether transformPrecoder is enabled / disabled (DFT-s-OFDM / CP-OFDM) (implicit signaling). (1-3) The UE may receive an explicit indication by a MAC CE indicating whether transformPrecoder is enabled / disabled (DFT-s-OFDM / CP-OFDM) (explicit signaling). (1-4) The UE may receive an implicit indication by a MAC CE indicating whether transformPrecoder is enabled / disabled (DFT-s-OFDM / CP-OFDM) (implicit signaling).

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

[0177] In the conventional type 1 CG-PUSCH, DCI is not used for scheduling. Therefore, when the above (1-1) and (1-2) are applied, it is preferable to newly define DCI. For example, either of the following (2-1) or (2-2) may be applied as the DCI of the above (1-1) and (1-2).

[0178] (2-1) A DCI for scheduling UL / DL unicast data may be applied. Note that the UL / DL-SCH that the DCI actually schedules may not actually exist. (2-2) A DCI for scheduling data other than unicast data may be applied. For example, this DCI may be applied when a group-common DCI is used.

[0179] According to this embodiment, it is possible to clarify the processing when dynamic switching of Type 1 CG-PUSCH waveform is applied.

[0180] <Embodiment X4.2> Dynamic switching of Type 2 CG-PUSCH (PUSCH transmission configured by higher layer signaling and activated / deactivated by DCI) waveform may be applied, and at least one of the methods (1-1) to (1-4) of embodiment X4.1 may be supported.

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

[0182] Since DCI for activation / deactivation is used in conventional type 2 CG-PUSCH, that DCI may be reused. Specifically, either of the following (2-1) or (2-2) may be applied as the DCI of the above (1-1) or (1-2).

[0183] (2-1) A DCI for scheduling UL / DL unicast data may be applied. Note that the UL / DL-SCH that the DCI actually schedules may not exist. For example, a DCI for activating / deactivating a Type 2 CG-PUSCH may be applied. (2-2) A DCI for scheduling data other than unicast data may be applied. For example, this DCI may be applied when a group-common DCI is used.

[0184] According to this embodiment, it is possible to clarify the processing when dynamic switching of Type 2 CG-PUSCH waveform is applied.

[0185] <Embodiment X5> Dynamic switching of the waveform of the message 3 / message A PUSCH (PUSCH scheduled by a random access response (RAR)) may be applied, and at least one of the methods (1-1) to (1-4) of embodiment X4.1 may be supported. Alternatively, the following (1-5) may be applied.

[0186] (1-5) The UE may receive an explicit / implicit indication via the RAR indicating whether transformPrecoder is enabled / disabled (DFT-s-OFDM / CP-OFDM).

[0187] The methods (1-1) to (1-5) may 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 methods (1-1) to (1-5), the same methods as the methods for other types of PUSCH may be applied to the message 3 / message A PUSCH.

[0188] Since DCI for activation / deactivation is used in the conventional message 3 / message A PUSCH, that DCI may be reused. Specifically, either of the following (2-1) or (2-2) may be applied as the DCI of the above (1-1) or (1-2).

[0189] (2-1) A DCI for scheduling UL / DL unicast data may be applied. Note that the UL / DL-SCH that the DCI actually schedules may not exist. For example, the DCI may be DCI 1_0 having a cyclic redundancy check (CRC) scrambled by an RA Radio Network Temporary Identifier (RNTI) or a message B RNTI. (2-2) A DCI for scheduling data other than unicast data may be applied. For example, this DCI may be applied when a group-common DCI is used.

[0190] For dynamic waveform switching of the Message 3 / Message A PUSCH, the UE may support at least one of the following (3-1) and (3-2) regarding RAR-based instructions: The UE may dynamically switch the waveform of the Message 3 PUSCH or the Message A PUSCH based on at least one of the MAC subheader or the MAC payload for the RAR.

[0191] (3-1) The reserved bit (R) in the MAC subheader / MAC payload for RAR may be cleared and used for dynamic waveform switching. For example, the "R" in the first octet of the MAC payload (i.e., next to the Timing Advance Command) shown in FIG. 8 may indicate dynamic waveform switching. (3-2) Dynamic waveform switching may be implicitly indicated based on the existing RAR grant field (UL Grant) shown in FIG. 9. For example, if the Modulation and Coding Scheme (MCS) in the UL Grant indicates a specific MCS, the enable / disable of the transformPrecoder may be set for the Message 3 / Message A PUSCH. For example, if the value corresponding to the TPC command for the Message 3 PUSCH in the UL Grant (FIGS. 9 and 10) is a specific value or is greater than / less than a specific threshold, the enable / disable of the transformPrecoder may be set for the Message 3 / Message A PUSCH.

[0192] When a Backoff Parameter value (FIG. 11) corresponding to a Backoff Indicator (BI) field included in the MAC subheader for RAR is a specific value or is greater than / less than a specific threshold, the enable / disable of the transformPrecoder may be set for the message 3 / message A PUSCH. Alternatively, when the Extension (E) field, Type (T) field, and Random Access Preamble IDentifier (RAPID) field included in the MAC subheader for RAR are specific values, the enable / disable of the transformPrecoder may be set for the message 3 / message A PUSCH.

[0193] This embodiment may be applied when a specific condition is met, which may be that the PRACH that triggers the RAR is transmitted on a specific RA resource based on the RACH resource partition configuration.

[0194] According to this embodiment, it is possible to clarify the processing when dynamic switching of the PUSCH waveform of message 3 / message A is applied. Furthermore, when an RAR-based instruction is used for dynamic switching of the PUSCH waveform of message 3 / message A, it is possible to use the existing MAC subheader / payload, thereby suppressing an increase in communication overhead.

[0195] <Problem X4> In existing systems (e.g., Rel. 17 NR or earlier), in the antenna port field included in DCI format 0_1 / 0_2, when a transform precoder is enabled (e.g., when DFT-S-OFDM is applied to the scheduled PUSCH), DMRS type 2 (e.g., dmrs-Type=2) is not assumed (see FIG. 12). DMRS type 2 is considered / applied only when the transform precoder is disabled (e.g., when CP-OFDM is applied to the scheduled PUSCH).

[0196] If dynamic waveform switching is supported, the DCI may indicate switching between CP-OFDM and DFT-S-OFDM waveforms.

[0197] On the other hand, the type of PUSCH DMRS (dmrs-Type 1 or dmrs-Type 2) is configured by RRC. In this case, DMRS Type 2 (or DMRS Type 1) can be configured for CP-OFDM (similar to existing systems (e.g., Rel. 17 NR and earlier)).

[0198] However, for DFT-S-OFDM, DMRS type 2 cannot be configured in existing systems, but when dynamic waveform switching is configured / supported, DMRS type 2 may be configured for DFT-S-OFDM because the DCI instruction (e.g., waveform switching) is dynamically performed by the RRC configuration change (DMRS type configuration).

[0199] As such, it is not clear how the PUSCH DMRS type is configured when dynamic waveform switching is supported.

[0200] <Embodiment X6> When dynamic waveform switching (DWS) is configured, a specific DMRS type (dmrs-Type) may be applied / configured for the PUSCH DMRS.

[0201] For example, when dynamic waveform switching is configured, the UE may be controlled to apply a specific DMRS type (e.g., DMRS type 1) regardless of the waveform (CP-OFDM or DFT-S-OFDM) indicated by DCI / DMRS type configured by RRC. This can prevent an increase in the number of {waveform, DMRS type} combinations that the UE needs to consider in PUSCH transmission. As a result, it is possible to prevent an increase in implementation limitations in the UE.

[0202] The UE may assume / apply at least one of the following options 6-1 to 6-2 for the DMRS type (dmrs-Type) of the PUSCH DMRS. Note that in the present disclosure, the dynamic waveform switching setting may be interpreted as enabling / activating dynamic waveform switching.

[0203] [Option 6-1] When dynamic waveform switching is set, only Type 1 may be set as the DMRS type (dmrs-Type) (see FIG. 13).

[0204] When dynamic waveform switching is configured, the base station may control the UE to configure only Type 1 as the DMRS type of the PUSCH. In other words, when dynamic waveform switching is configured, the configuration of DMRS Type 2 by RRC may be restricted / prohibited.

[0205] In this case, DMRS Type 1 may be applied regardless of the waveform (CP-OFDM or DFT-S-OFDM) indicated by the DCI. When dynamic waveform switching is configured, the UE may control to apply DMRS Type 1 to both waveforms (CP-OFDM and DFT-S-OFDM). Furthermore, when dynamic waveform switching is configured, the UE may assume / expect / determine that DMRS Type 1 is configured for the PUSCH DMRS.

[0206] When dynamic waveform switching is configured, the setting of the DMRS type of the PUSCH by RRC may be omitted.

[0207] In this way, by configuring only a specific DMRS type, it is possible to prevent an increase in the number of combinations of {waveform, DMRS type} that a UE needs to consider in PUSCH transmission. As a result, it is possible to prevent an increase in the number of implementations that cannot be implemented in a UE.

[0208] [Option 6-2] When dynamic waveform switching is configured, the DMRS type may be supported / allowed to be configured as DMRS type 1 and DMRS type 2 (see FIG. 13).

[0209] When dynamic waveform switching is configured, the base station may control the UE to configure DMRS type 1 or DMRS type 2 as the DMRS type of the PUSCH. In other words, when dynamic waveform switching is configured, the configuration of DMRS type 2 by RRC may be permitted.

[0210] When DMRS Type 2 is configured and dynamic waveform switching is configured, the UE may interpret the DMRS type (e.g., dmrs-Type) of the PUSCH as being configured as Type 1. In other words, the UE may ignore the DMRS Type 2 configuration and apply DMRS Type 1.

[0211] In this way, when dynamic waveform switching is configured, DMRS type 1 may be applied regardless of the DMRS type configured in RRC.

[0212] In this way, by specifying a specific DMRS type as the applied DMRS type, it is possible to prevent an increase in the number of combinations of {waveform, DMRS type} that a UE needs to consider in PUSCH transmission. As a result, it is possible to prevent an increase in the number of implementations that cannot be implemented in a UE.

[0213] <Embodiment X7> When dynamic waveform switching (DWS) is configured, the DMRS type (dmrs-Type) to be applied to the PUSCH DMRS may be determined based on the waveform indicated by the DCI.

[0214] For example, when dynamic waveform switching is configured, the UE may determine the DMRS type to apply based on the waveform (CP-OFDM or DFT-S-OFDM) indicated by the DCI / DMRS type configured in RRC.

[0215] When dynamic waveform switching is configured and DFT-S-OFDM is indicated by DCI, the UE may 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 used to indicate DFT-S-OFDM may be the DCI used to schedule the PUSCH.

[0216] [Option 7-1] When dynamic waveform switching is configured and DFT-S-OFDM is indicated by DCI, only Type 1 may be applied / configured as the DMRS type.

[0217] When dynamic waveform switching is configured, the base station may control the UE to configure only Type 1 as the DMRS type of the PUSCH. In other words, when dynamic waveform switching is configured, the configuration of DMRS Type 2 by RRC may be restricted / prohibited.

[0218] In this case, DMRS Type 1 may be applied regardless of the waveform (CP-OFDM or DFT-S-OFDM) indicated by the DCI. When dynamic waveform switching is configured, the UE may control to apply DMRS Type 1 to both waveforms (CP-OFDM and DFT-S-OFDM). Furthermore, when dynamic waveform switching is configured, the UE may assume / expect / determine that DMRS Type 1 is configured for the PUSCH DMRS.

[0219] When dynamic waveform switching is configured, the setting of the DMRS type of the PUSCH by RRC may be omitted.

[0220] In this way, by configuring only a specific DMRS type, it is possible to prevent an increase in the number of combinations of {waveform, DMRS type} that a UE needs to consider in PUSCH transmission. As a result, it is possible to prevent an increase in the number of implementations that cannot be implemented in a UE.

[0221] [Option 7-2] When dynamic waveform switching is configured and DFT-S-OFDM is indicated by DCI, the configuration of DMRS type 1 and DMRS type 2 may be supported / allowed as the DMRS type.

[0222] When dynamic waveform switching is configured, the base station may control the UE to configure DMRS type 1 or DMRS type 2 as the DMRS type of the PUSCH. In other words, when dynamic waveform switching is configured, the configuration of DMRS type 2 by RRC may be permitted.

[0223] When DMRS Type 2 is configured, dynamic waveform switching is configured, and DFT-S-OFDM is indicated by DCI, the UE may interpret the DMRS type (e.g., dmrs-Type) of the PUSCH as being configured as Type 1. In other words, when DFT-S-OFDM is indicated by DCI, the UE may ignore the DMRS Type 2 configuration and apply DMRS Type 1.

[0224] On the other hand, when DMRS type 2 is configured, dynamic waveform switching is configured, and DFT-S-OFDM is not indicated by DCI (for example, when CP-OFDM is indicated), the UE may interpret that DMRS type 2 is configured as the DMRS type (for example, dmrs-Type) of the PUSCH. In other words, when DFT-S-OFDM is not indicated by DCI (for example, when CP-OFDM is indicated), the UE may apply DMRS type 2.

[0225] In this way, when dynamic waveform switching is configured and DMRS Type 2 is configured by RRC, whether or not DMRS Type 2 is applied may be determined based on the waveform specified by DCI. Note that when dynamic waveform switching is configured and DMRS Type 1 is configured by RRC, control may be performed to apply DMRS Type 1 regardless of the waveform specified by DCI.

[0226] This allows DMRS type 2 to be applied when CP-OFDM is indicated by DCI, making it possible to flexibly control the DMRS type to be applied depending on the waveform.

[0227] <Embodiment X8> When dynamic waveform switching (DWS) is configured and DMRS type 2 is configured as the DMRS type (e.g., dmrs-Type), a predetermined field (e.g., antenna port field) included in the DCI may be interpreted based on a predetermined rule.

[0228] When dynamic waveform switching is configured and DMRS Type 2 is configured, the UE may interpret a predetermined field (e.g., an antenna port field) included in the DCI based on a predetermined rule. The DCI may be a DCI used for scheduling a PUSCH. The predetermined rule may be, for example, at least one of Option 8-1 to Option 8-2 below.

[0229] [Option 8-1] The bit width (e.g., bitwidth) of the antenna port field is determined taking into account that the dmrs-Type is DMRS type 2 (i.e., according to the setting of dmrs-Type), but the UE may interpret the indication by the antenna port field by interpreting only some of the bits (or using some of the bits).

[0230] The number of some bits may be the same as the number of antenna port fields (or the number of bits / code points) in which Type 2 is set for dmrs-Type 1. In the present disclosure, some / some of the bits may be read as some / some of the DCI code points.

[0231] In this case, the determination of the bit width of the antenna port field of the DCI may differ from the interpretation of the antenna port field, i.e., the bit width / number of code points of the antenna port field of the DCI may be determined based on DMRS Type 2, and the interpretation of the antenna port field of the DCI may be performed assuming DMRS Type 1.

[0232] The number of DCI codepoints may be the same as the number of antenna port fields (or number of bits / number of codepoints) for which Type 2 is set for dmrs-Type 1.

[0233] This allows the UE to properly interpret the antenna port field of the DCI even when DMRS type 1 is applied in a case where DMRS type 2 is configured.

[0234] [Option 8-2] The bit width (e.g., bitwidth) of the antenna port field is determined taking into account that the dmrs-Type is DMRS type 1 (i.e., ignoring the setting of dmrs-Type), and the UE may interpret the indication by the antenna port field taking into account that the dmrs-Type is DMRS type 1.

[0235] 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 may be the same. That is, the bit width of the antenna port field of the DCI may be determined based on DMRS Type 1, and the interpretation of the antenna port field of the DCI may also be performed assuming DMRS Type 1.

[0236] As a result, when DMRS Type 1 is applied in a case where DMRS Type 2 is configured, both the bit width and interpretation of the antenna port field can be performed assuming DMRS Type 1. Also, it is possible to suppress an increase in overhead of the antenna port field.

[0237] <Embodiment X9> When dynamic waveform switching (DWS) is configured, DMRS type 2 is configured as the DMRS type (e.g., dmrs-Type), and DFT-S-OFDM is indicated by DCI, a predetermined field (e.g., antenna port field) included in the DCI may be interpreted based on a predetermined rule.

[0238] When dynamic waveform switching is configured, DMRS Type 2 is configured, and DFT-S-OFDM is indicated by the DCI, the UE may interpret a predetermined field (e.g., an antenna port field) included in the DCI based on a predetermined rule. The DCI may be a DCI used for scheduling a PUSCH. The predetermined rule may be, for example, at least one of Option 9-1 to Option 9-2 below.

[0239] [Option 9-1] The bit width (e.g., bitwidth) of the antenna port field is determined taking into account that the dmrs-Type is DMRS type 2 (i.e., according to the setting of dmrs-Type), but the UE may interpret the indication by the antenna port field by interpreting only some of the bits (or using some of the bits).

[0240] The number of some bits may be the same as the number of antenna port fields (or the number of bits / code points) in which Type 2 is set for dmrs-Type 1. In the present disclosure, some / some of the bits may be read as some / some of the DCI code points.

[0241] In this case, the determination of the bit width of the antenna port field of the DCI may differ from the interpretation of the antenna port field, i.e., the bit width of the antenna port field of the DCI may be determined based on DMRS Type 2, and the interpretation of the antenna port field of the DCI may be performed assuming DMRS Type 1.

[0242] The number of DCI codepoints may be the same as the number of antenna port fields (or number of bits / number of codepoints) for which Type 2 is set for dmrs-Type 1.

[0243] This enables the UE to properly interpret the antenna port field of the DCI even when DMRS type 1 is applied in a case where DMRS type 2 is configured and DFT-S-OFDM is indicated by the DCI.

[0244] In addition, in cases where DMRS type 2 is set and CP-OFDM is indicated by DCI, the bit width of the antenna port field of the DCI and the interpretation of the antenna port field may be determined based on DMRS type 2.

[0245] 14A and 14B show an example of the antenna port field of DCI when dynamic waveform switching is configured and Type 2 is configured as the DMRS type (e.g., dmrs-Type).

[0246] <Antenna Port Field Example 1> When DFT-S-OFDM is indicated by the DCI scheduling the PUSCH, the bit width (or the number of bits of the field) may be set to 3 bits. In this case, the UE may interpret it in the same way as when Type 1 is set as the DMRS type (e.g., dmrs-Type). For example, the UE may interpret only the 2 least significant bits (LSBs) (see FIG. 14A).

[0247] If DFT-S-OFDM is not indicated by the DCI scheduling the PUSCH (for example, if CP-OFDM is indicated), the bit width (or the number of bits of the field) may be set to 3 bits. In this case, the UE may interpret it in the same way as when Type 2 is set as the DMRS type (for example, dmrs-Type). For example, the UE may interpret it using all 3 bits.

[0248] <Antenna Port Field Example 2> When DFT-S-OFDM is indicated by the DCI scheduling the PUSCH, the bit width (or the number of bits of the field) may be set to 3 bits. In this case, the UE may interpret the 8 code points generated by the 3 bits using a predetermined number (here, 5). In this case, the remaining 3 code points / fields may be reserved bits / reserved code points (see FIG. 14B).

[0249] If DFT-S-OFDM is not indicated by the DCI scheduling the PUSCH (for example, if CP-OFDM is indicated), the bit width (or the number of bits of the field) may be set to 3. In this case, the UE may interpret using all code points (here, 8) generated by the 3 bits.

[0250] In this way, when dynamic waveform switching is configured, the PUSCH DMRS transmission can be appropriately performed by flexibly controlling the determination / interpretation of the bit width of the antenna port field of the DCI based on the waveform indicated by the DCI.

[0251] [Option 9-2] The bit width (e.g., bitwidth) of the antenna port field is determined taking into account that the dmrs-Type is DMRS type 1 (i.e., ignoring the setting of dmrs-Type), and the UE may interpret the indication by the antenna port field taking into account that the dmrs-Type is type 1.

[0252] 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 may be the same. That is, the bit width of the antenna port field of the DCI may be determined based on DMRS Type 1, and the interpretation of the antenna port field of the DCI may also be performed assuming DMRS Type 1.

[0253] As a result, in a case where DMRS type 2 is configured and DFT-S-OFDM is indicated by DCI (for example, when DMRS type 1 is applied), both the bit width and interpretation of the antenna port field can be performed assuming DMRS type 1. Also, it is possible to suppress an increase in the overhead of the antenna port field.

[0254] <Analysis A1> It is being considered that DWS is not supported in type 1 and type 2 configured grants (CG) PUSCH, but is supported only in dynamic grants (DG).

[0255] The UE does not expect the bit width of a field in DCI format 0_1 ​​with CRC scrambled by CS-RNTI to be larger than the corresponding bit width of the same field in DCI format 0_1 ​​with CRC scrambled by C-RNTI for the same serving cell. If the bit width of a field in DCI format 0_1 ​​with CRC scrambled by CS-RNTI is not equal to the bit width of the corresponding field in DCI format 0_1 ​​with CRC scrambled by C-RNTI for the same serving cell, some most significant bits (MSBs) with values ​​set to '0' are inserted into that field in DCI format 0_1 ​​with CRC scrambled by CS-RNTI until its bit width is equal to the bit width of the corresponding field in DCI format 0_1 ​​with CRC scrambled by C-RNTI for the same serving cell.

[0256] The size alignment of DCI format 0_1 ​​with CRC scrambled by C-RNTI or CS-RNTI satisfies the following constraints: The bit width (size) of any field in DCI format 0_1 ​​(using C-RNTI) with CRC scrambled by C-RNTI is equal to or greater than the bit width of that field in DCI format 0_1 ​​(using CS-RNTI) with CRC scrambled by CS-RNTI. If the bit width of that field in DCI format 0_1 ​​using CS-RNTI is smaller than the bit width of that field in DCI format 0_1 ​​using C-RNTI, the bit width of that field in DCI format 0_1 ​​using CS-RNTI is made equal to the bit width of that field in DCI format 0_1 ​​using C-RNTI by padding the field with zeros.

[0257] There are separate DMRS configurations for DG-PUSCH and CG-PUSCH. The PUSCH configuration (DG-PUSCH, PUSCH-Config) may include an uplink DMRS configuration (DMRS-UplinkConfig) of dmrs-UplinkForPUSCH-MappingTypeA / dmrs-UplinkForPUSCH-MappingTypeB. The CG-PUSCH configuration (ConfiguredGranConfig) may include an uplink DMRS configuration (DMRS-UplinkConfig) of cg-DMRS-Configuration.

[0258] The DMRS configuration affects the DCI field size. The size of the antenna port field when DMRS type 2 is configured is one bit larger than the size of the antenna port field when DMRS type 1 is configured. For example, when the transform precoder is disabled, the DMRS type is 1, and the DMRS maximum length is 1, the size of the antenna port field is 3 bits, and when the transform precoder is disabled, the DMRS type is 1, and the DMRS maximum length is 2, the size of the antenna port field is 4 bits. On the other hand, when the transform precoder is disabled, the DMRS type is 2, and the DMRS maximum length is 1, the size of the antenna port field is 4 bits, and when the transform precoder is disabled, the DMRS type is 2, and the DMRS maximum length is 2, the size of the antenna port field is 5 bits.

[0259] <Problem A1> In Rel. 17, simultaneous configuration of DFT-s-OFDM and DMRS type 2 for PUSCH is not supported.

[0260] In DG-PUSCH, if DWS is configured, the scheduling DCI carries one new bit to indicate waveform switching. The configurability issue of DMRS type 2 is addressed in Problem 1 and embodiment X1.

[0261] DWS is not supported in Type 2 CG-PUSCH.

[0262] The Type 2 CG activation DCI (Type 2 CG-PUSCH activation DCI) and the 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 equal to or greater than the size of that field in the Type 2 CG-PUSCH activation DCI.

[0263] When DWS for DG-PUSCH is configured, the following cases can be considered for the DMRS configuration for Type 2 CG-PUSCH: - Case 1: If DWS is configured and DMRS Type 1 is configured, the question arises as to whether there are any restrictions on the DMRS type for CG-PUSCH. - Case 2: If DWS is configured and DMRS Type 2 is configured, the question arises as to whether there are any restrictions on the DMRS type for CG-PUSCH.

[0264] <Embodiment A1> This embodiment relates to problem A1.

[0265] When DWS is configured, DMRS type 1 may be configured for both DG-PUSCH and CG-PUSCH, with this configuration no complex UE operations are required for interpreting the DMRS type and determining the DCI size for DG and CG activation.

[0266] - Example 1: The following behavior may be specified in the specification: If dynamic waveform switching is configured, the UE expects dmrs-Type=1 to be set in both the PUSCH-Config and the ConfiguredGrantConfig (on the same serving cell / BWP).

[0267] 15 illustrates an example of an RRC IE according to embodiment A1. In this example, the UE receives a DWS configuration, dmrs-Type=1 in the PUSCH-Config, and dmrs-Type=1 in the ConfiguredGrantConfig.

[0268] - Example 2: The following behavior may be specified in the specification: If dynamic waveform switching is configured, the UE does not expect dmrs-Type=2 to be configured in either the PUSCH-Config or the ConfiguredGrantConfig (on the same serving cell / BWP).

[0269] <Embodiment A2> This embodiment relates to problem A1.

[0270] When DWS is configured, DMRS type 1 or 2 may be configured for DG-PUSCH, and DMRS type 1 may be configured for CG-PUSCH. With this configuration, the UE does not need to read the DWS bit to recognize the size of the Type 2 CG-PUSCH activation DCI. Also, flexible DMRS configuration is possible for DG-PUSCH.

[0271] - Example 1: The following behavior may be specified in the specification: If dynamic waveform switching is configured, the UE expects dmrs-Type=1 to be set in the ConfiguredGrantConfig (on the same serving cell / BWP).

[0272] - Example 2: The following behavior may be specified in the specification: If dynamic waveform switching is configured, the UE does not expect dmrs-Type=2 to be configured in the ConfiguredGrantConfig (on the same serving cell / BWP).

[0273] <Embodiment A3> This embodiment relates to problem A1.

[0274] When DWS is configured, DMRS type 1 or 2 may be configured for DG-PUSCH and CG-PUSCH. This configuration enables flexible DMRS configuration for both DG-PUSCH and CG-PUSCH.

[0275] - Embodiment A3-1 When the DWS field indicates DFT-s-OFDM and DMRS type 2 is configured for DG-PUSCH, the UE may interpret the DMRS configuration as DMRS type 1. This operation allows the UE to follow existing implementation for DMRS. That is, DMRS type 2 may be configured for CP-OFDM only. This operation may also comply with embodiment X7.

[0276] - Embodiment A3-2: If the DWS field in a DCI for activating / deactivating Type 2 CG-PUSCH indicates DFT-s-OFDM and DMRS Type 2 is configured for CG-PUSCH, the UE may interpret the DMRS configuration as DMRS Type 1. This operation allows flexibility in DMRS configuration while maintaining the same DCI size for DG and CG-PUSCH activation.

[0277] If the DWS indicator in the DCI for activating / deactivating Type 2 CG-PUSCH indicates transform precoding, the UE may interpret dmrs-Type in ConfiguredGrantConfig as equal to 1.

[0278] The following behaviors may be defined: -- The UE does not expect the DWS indicator in the Type 2 CG-PUSCH activation / deactivation DCI to indicate that transform precoding is enabled.

[0279] <Problem A2> As mentioned above, the specifications do not consider DCI fields that have a non-zero bit width in DCI with CRC scrambled by CS-RNTI and a zero bit width in DCI with CRC scrambled by C-RNTI.

[0280] In future specifications, a new DCI field may be defined with the following characteristics: - if the transform precoder is disabled, its bit width is zero, and - if the transform precoder is enabled, its bit width is non-zero.

[0281] The following situations are error cases, which may be explicitly avoided: - for both DG-PUSCH and CG-PUSCH the new DCI field is configured, and - for DG-PUSCH the transform precoder is disabled, and - for CG-PUSCH the transform precoder is enabled.

[0282] <Problem A3> In addition to problem A2, the DCI field size may differ depending on the DWS indication. Depending on the DWS indicator, the error case in problem A2 may occur.

[0283] <Embodiment A4> This embodiment relates to problem A2.

[0284] In the present disclosure, a DCI field that exists only in scheduling of a PUSH with DFT-s-OFDM, a DCI field that is 0 bits when the transform precoder is disabled and X (X>0) bits when it is not, a DCI field that has a non-zero bit width for DFT-s-OFDM and a zero bit width for CP-OFDM, a new DCI field, and a specific DCI field may be read as interchangeable.

[0285] In the example of FIG. 16, the DCI for scheduling a PUSCH with DFT-s-OFDM includes a specific DCI field, and the DCI for scheduling a PUSCH with CP-OFDM does not include a specific DCI field.

[0286] If a DCI field that is present only in scheduling of PUSCH with DFT-s-OFDM is configured, the configuration of the transform precoder for DG-PUSCH and the configuration of the transform precoder for CG-PUSCH may be the same, with this configuration no additional DCI size alignment rule is needed since the size of the field is the same between DG-PUSCH and CG-PUSCH.

[0287] <Embodiment A5> This embodiment relates to problem A2.

[0288] If a DCI field that is present only in scheduling of PUSCH with DFT-s-OFDM is configured, the transform precoder for CG-PUSCH may be disabled. With this configuration, no additional DCI size alignment rule is needed because the size of the field is the same between DG-PUSCH and CG-PUSCH.

[0289] <Embodiment A6> This embodiment relates to problem A2.

[0290] If a DCI field that is present only in scheduling of PUSCH with DFT-s-OFDM is configured, that field may not be present in DCI with CRC scrambled by CS-RNTI, and with this configuration, no additional DCI size alignment rule is needed, since the size of that field is the same between DG-PUSCH and CG-PUSCH.

[0291] <Embodiment A7> This embodiment relates to problem A2.

[0292] When a DCI field that exists only in scheduling of a PUSH with DFT-s-OFDM is set, and the transform precoder for the DG-PUSH is disabled, and the transform precoder for the CG-PUSH is enabled, the bit width of the field may be adjusted between the DG-PUSH and the CG-PUSH based on specific rules.

[0293] The specific rule may follow at least one of the following rules: - The size of the field is adjusted to the larger of the sizes for DG-PUSCH and CG-PUSCH. For example, the MSB of the field having the smaller size may be stuffed with bits having a value of '0'. - The size of the field is adjusted to the smaller of the sizes for DG-PUSCH and CG-PUSCH. For example, the number of code points corresponding to the larger size may be reduced to be equal to or less than the number of code points of the field having the smaller size by narrowing the range, decreasing the maximum value, increasing the minimum value, or thinning out the code points. For example, the number of code points corresponding to the larger size may be reduced in the same manner as in embodiment X9 (option 9-1). - The size of the field is adjusted to the size of the field of the DCI with CRC scrambled by the C-RNTI (the scheduling DCI for DG-PUSCH). The size of the field is adapted to the size of the field of the DCI with CRC scrambled by the CS-RNTI (DCI for activation / deactivation of CG-PUSCH).

[0294] This operation allows flexible configuration of the transform precoder and DCI fields for DG-PUSCH and CG-PUSCH.

[0295] <Embodiment A8> This embodiment relates to problem A3.

[0296] The DCI field that exists only in scheduling of PUSH with DFT-s-OFDM and the DWS may not be set at the same time.

[0297] The following behavior may be defined in the specification: - The UE does not expect DCI fields present only in scheduling of PUSCH with DFT-s-OFDM and DWS to be set at the same time.

[0298] This setting simplifies the DCI size alignment rules.

[0299] <Embodiment A9> This embodiment relates to problem A3.

[0300] When a DCI field that exists only in scheduling of a PUSCH with DFT-s-OFDM and a DWS are set at the same time, the transform precoder may be set to be disabled for the CG-PUSCH.

[0301] This setting simplifies the DCI size alignment rules.

[0302] <Embodiment A10> This embodiment relates to problem A3.

[0303] When DCI fields that are only present in scheduling of PUSCH with DFT-s-OFDM and DWS are configured simultaneously, at least one of the following restrictions may apply:

[0304] - The DWS indicator may indicate only CP-OFDM. The DWS indicator may not indicate DFT-s-OFDM. The following behavior may be specified in the specification: - The UE does not expect the DWS indicator to indicate that the transform precoder is enabled.

[0305] - The DWS indicator may indicate the same waveform as the waveform configured for CG-PUSCH. The DWS indicator may not indicate a waveform different from the waveform configured for CG-PUSCH. The following behavior may be specified in the specification: - The UE does not expect the indication of the DWS indicator to be different from the configuration of the transform precoder in the configuration grant configuration.

[0306] This setting simplifies the DCI size alignment rules.

[0307] <Embodiment A11> This embodiment relates to problem A3.

[0308] When a DCI field that exists only in scheduling of a PUSH with DFT-s-OFDM and a DWS are configured simultaneously, the bit width of the field may be adjusted between DG-PUSH and CG-PUSH based on specific rules.

[0309] The specific rule may follow at least one of the following rules: - The size of the field is adjusted to the larger of the sizes for DG-PUSCH and CG-PUSCH. For example, the MSB of the field having the smaller size may be stuffed with bits having a value of '0'. - The size of the field is adjusted to the smaller of the sizes for DG-PUSCH and CG-PUSCH. For example, the number of code points corresponding to the larger size may be reduced to be equal to or less than the number of code points of the field having the smaller size by narrowing the range, decreasing the maximum value, increasing the minimum value, or thinning out the code points. For example, the number of code points corresponding to the larger size may be reduced in the same manner as in embodiment X9 (option 9-1). - The size of the field is adjusted to the size of the field of the DCI with CRC scrambled by the C-RNTI (the scheduling DCI for DG-PUSCH). The size of the field is adapted to the size of the field of the DCI with CRC scrambled by the CS-RNTI (DCI for activation / deactivation of CG-PUSCH).

[0310] This operation allows flexible configuration / indication of transform precoder and DCI fields for DG-PUSCH and CG-PUSCH.

[0311] <Multi-Carrier DCI> In Rel. 18, support for a new DCI format for scheduling multiple PDSCHs across multiple CCs or multiple PUSCHs across multiple CCs is being considered.

[0312] The DCI format may be at least one of the following: DCI format 0_X for scheduling multiple PUSCHs across multiple CCs, or DCI format 1_X for scheduling multiple PDSCHs across multiple CCs.

[0313] Each DCI field in DCI format 0_X / 1_X may be categorized as at least one of several types:

[0314] - Type 1 -- Type 1A: A single field within one DCI format. It indicates information common to all CCs (all co-scheduled CCs). Figure 17A shows an example of Type 1A DCI format 0_X for scheduling a PUSCH. Type 1A DCI format 1_X for scheduling a PDSCH may be similar to this example. -- Type 1B: A single field within one DCI format. It indicates different information for different CCs via joint indication (indicating separate information for each of the co-scheduled CCs). Figure 17B shows an example of Type 1B DCI format 0_X for scheduling a PUSCH. Type 1B DCI format 1_X for scheduling a PDSCH may be similar to this example. -- Type 1C: A single field within one DCI format. It indicates information for only one of the co-scheduled CCs. 18A shows an example of Type 1C DCI format 0_X for scheduling PUSCH. Type 1C DCI format 1_X for scheduling PDSCH may be similar to this example.

[0315] - Type 2: Multiple fields within one DCI format. Each of the multiple fields (separate fields) independently indicates information for each CC. Figure 18B shows an example of Type 2 DCI format 0_X for scheduling PUSCH. Type 2 DCI format 1_X for scheduling PDSCH may be similar to this example.

[0316] - Type 3: Depending on the explicit configuration, either common to multiple co-scheduled CCs, individual for each of the co-scheduled CCs, or individual for each subgroup. For example, either Type 1A or Type 2 may be configured. A subgroup includes a subset of co-scheduled cells. Here, a single field is commonly applied to co-scheduled cells belonging to the same subgroup.

[0317] <Analysis B1> The following several issues can be considered: - Q1: Is the DWS indicated in DCI format 0_X supported? - Q2: If the DWS indicated in DCI format 0_X is supported, how many bits are indicated for the purpose of the DWS in DCI format 0_X? - Q3: If the DWS indicated in DCI format 0_X is supported, how are the RRC settings affected by the exact waveform handled? The RRC settings are, for example, transform precoder, maximum rank, FDRA type, DMRS type, etc.

[0318] Mainly in DCI size alignment for DCI format 0_1, the antenna port, TPMI, DMRS-PTRS association, DMRS sequence initialization, and frequency hopping flag may be in accordance with at least one of embodiments X0 to X6, and the DMRS type may be in accordance with at least one of embodiments X7 to X9.

[0319] <Embodiment B0> DWS may be supported or configured for DCI format 0_X. According to this embodiment, the waveform for the PUSCH scheduled by DCI format 0_X can be dynamically selected depending on the situation. DWS for DCI format 0_X may follow at least one of the following options:

[0320] - Option 1: Configuration approach The configuration of DWS for DCI format 0_X may follow at least one of the following options: -- Option 1-1: New RRC parameters separate for DCI format 0_X. This parameter allows independent configuration of DWS on / off for each DCI format. -- Option 1-2: Reuse / repurpose of RRC parameters for other applications. This parameter eliminates the need for additional signaling. For example, RRC parameters for other applications may configure DWS on / off for at least one of DCI formats 0_1 and 0_2.

[0321] - Option 2 The number of bits for indicating DWS may follow at least one of the following options: -- Option 2-1: 1 bit. -- Option 2-2: N bits, where N may be the number of co-scheduled cells. A one-to-one mapping between bits and cells may be applied. -- Option 2-3: N1 bits, where 1 < N1 < N may be used. -- For example, N1 may be the number of co-scheduled cells with DWS configured. -- For example, N1 may be the maximum number of co-scheduled cells from a cell combination. In this case, multiple combinations of cells may be configured by an RRC parameter. -- For example, N1 may be the maximum number of co-scheduled cells with DWS configured from a cell combination. In this case, multiple combinations of cells may be configured by an RRC parameter.

[0322] <Embodiment B1> When DWS in DCI format 0_X is configured, the RRC configuration of the transform precoder (transformPrecoder) may follow at least one of the following forms.

[0323] - Configuration 1-1: For any of the co-scheduled cells, the setting is "disabled." This setting simplifies the interpretation of the 1-bit DWS in DCI format 0_X.

[0324] - Configuration 1-2: The setting is the same across all co-scheduled cells. The setting may be either "disabled" or "enabled." This setting simplifies the interpretation of the 1-bit DWS in DCI format 0_X, and both CP-OFDM and DFT-s-OFDM can be used.

[0325] - Configuration 1-3: Different cells included in a co-scheduled cell group have different configurations, which maintains the configurability of Rel. 17 waveforms per cell.

[0326] According to this embodiment, even when DWS in DCI format 0_X is configured, the transform precoder can be configured appropriately.

[0327] <Embodiment B2> When DWS in DCI format 0_X is configured, the RRC configuration of the maximum rank (maxRank) may follow at least one of the following forms.

[0328] - Configuration 2-1: The configuration is the same across all co-scheduled cells.

[0329] - Configuration 2-1a: The setting is '1' across all co-scheduled cells.

[0330] - Configuration 2-2 The settings are different across co-scheduled cells.

[0331] According to this embodiment, even when DWS in DCI format 0_X is set, the maximum rank can be set appropriately.

[0332] <Embodiment B3> When DWS in DCI format 0_X is configured, the FDRA-type RRC configuration (resource allocation) may follow at least one of the following forms.

[0333] - Configuration 3-1: The setting is the same across all co-scheduled cells.

[0334] - Configuration 3-1a: Across all co-scheduled cells, the setting is FDRA type 1 ('resourceAllocationType1').

[0335] - Configuration 3-1b: Across all co-scheduled cells, the setting is dynamic switching ('dynamicSwitching').

[0336] - Configuration 3-1c: Across all co-scheduled cells, the setting is other than FDRA type 0 ('resourceAllocationType0').

[0337] - Configuration 3-2: The settings are different across all co-scheduled cells.

[0338] - Configuration 3-3: The setting is different across all co-scheduled cells and is other than 'resourceAllocationType0'.

[0339] According to this embodiment, even when DWS in DCI format 0_X is configured, the FDRA type can be appropriately configured. There is no need to support simultaneous configuration of DFT-s-OFDM and FDRA type 0.

[0340] <Embodiment B4> When DWS in DCI format 0_X is configured, the RRC configuration of the DMRS type (dmrs-Type) may follow at least one of the following forms.

[0341] - Configuration 4-1: The setting is the same across all co-scheduled cells.

[0342] - Configuration 4-1a: The configuration is not configured for any of the co-scheduled cells, which may imply that DMRS Type 1 is configured for any of the co-scheduled cells.

[0343] - Configuration 4-1b: For any of the co-scheduled cells, the configuration is not type 2 ('type2').

[0344] - Configuration 4-2: For all co-scheduled cells, the settings are different.

[0345] According to this embodiment, even when DWS in DCI format 0_X is configured, the DMRS type can be appropriately configured.

[0346] <Analysis B2> For DCI format 0_X including the DWS field, the question is how to achieve DCI size alignment. The DCI size alignment may depend on at least one of the following policies. The DCI fields that require alignment consideration may be antenna port, TPMI, PTRS-DMRS association, DMRS sequence initialization, and frequency hopping flag.

[0347] The details of the DWS field in DCI format 0_X may follow at least one of the following strategies: - Strategy 1: The DWS field in DCI format 0_X is 1 bit. This DWS field may be Type 1A. - Strategy 2: The DWS field in DCI format 0_X is N (>1) bits. This DWS field may be Type 2. - Strategy 3: The DWS field in DCI format 0_X can be set between Strategies 1 and 2. The DWS field in this case may be Type 3. - Other strategies: The DWS field in DCI format 0_X may be Type 1B / 1C.

[0348] Embodiments B0 to B4 may be applied regardless of strategies 1 to 3.

[0349] Embodiments B5 to B7 may be based on strategy 1.

[0350] Embodiments B8 to B10 may be based on strategy 2.

[0351] <Embodiment B5> When a 1-bit DWS field is set for DCI format 0_X (FIG. 19), the interpretation of the 1-bit indication may follow at least one of the following forms.

[0352] - Configuration 5-1: For any co-scheduled cell, '0' indicates CP-OFDM (transform precoder disabled) and '1' indicates DFT-s-OFDM (transform precoder enabled). This interpretation avoids complex waveform combinations across co-scheduled cells.

[0353] - Configuration 5-2: For any co-scheduled cell, '0' indicates the waveform configured in the RRC parameters, and '1' indicates that the waveform is switched from the waveform configured in the RRC parameters. According to this interpretation, waveform switching can be achieved using only one bit for all co-scheduled cells. This case can be considered together with embodiment B1. For example, in configuration 1-1, the transform precoder is restricted to be disabled, thereby avoiding the indication of a complex waveform.

[0354] - Configuration 5-3: For any of the co-scheduled cells, a '0' indicates the waveform configured in the RRC parameters for one of the co-scheduled cells, and a '1' indicates that the waveform is switched from the waveform configured in the RRC parameters for one of the co-scheduled cells. This interpretation avoids complex combinations of waveforms across co-scheduled cells.

[0355] Configurations 5-1 / 5-2 / 5-3 may be applied only to co-scheduled cells with DWS configuration enabled.

[0356] In the forms 5-1 / 5-2 / 5-3, the interpretation of '0' and '1' may be reversed.

[0357] In form 5-3, one of the co-scheduled cells may be one of the following definitions, or a combination of two or more: - A scheduled cell. - A reference cell for counting the size of blind decoding (BD) / control channel element (CCE) / DCI. - A cell in which a search space (SS) set for DCI format 0_X is configured. - A cell with the minimum or maximum serving cell index. - A cell indicated by DCI. - A cell configured by RRC IE. - A cell indicated by MAC CE. - A cell in which DWS is configured.

[0358] A combination of two or more definitions may be, for example, the cell with the smallest serving cell index among the cells that are co-scheduled and configured for DWS.

[0359] In the example of Figure 20, the RRC-configured waveforms for cell indexes #0, #1, #2, and #3 are CP-OFDM (CP), DFT-s-OFDM (DFT-s), CP-OFDM (CP), and CP-OFDM (CP), respectively.

[0360] In form 5-1, if the value of the DWS field is 0, CP-OFDM is used for all (PUSHs) of cell indexes #0, #1, #2, and #3, and if the value of the DWS field is 1, DFT-s-OFDM is used for all (PUSHs) of cell indexes #0, #1, #2, and #3.

[0361] In form 5-2, when the value of the DWS field is 0, CP-OFDM, DFT-s-OFDM, CP-OFDM, and CP-OFDM are used for cell indexes #0, #1, #2, and #3 (PUSCH), respectively, and when the value of the DWS field is 1, DFT-s-OFDM, CP-OFDM, DFT-s-OFDM, and DFT-s-OFDM are used for cell indexes #0, #1, #2, and #3 (PUSCH), respectively.

[0362] In form 5-3, if the value of the DWS field is 0, CP-OFDM is used for all (PUSHs) of cell indexes #0, #1, #2, and #3, and if the value of the DWS field is 1, DFT-s-OFDM is used for all (PUSHs) of cell indexes #0, #1, #2, and #3.

[0363] According to this embodiment, even if the DWS field in DCI format 0_X is one bit, the waveform of multiple cells can be properly indicated.

[0364] <Embodiment B6> When the 1-bit DWS field is set for DCI format 0_X, the presence or absence of a specific DCI field in that DCI format 0_X may be based on a rule, which may follow at least one of the following options:

[0365] - Option 1: The specific DCI field may be at least one of several options below: -- Option 1-1: DMRS sequence initialization. -- Option 1-2: PTRS-DMRS association.

[0366] - Option 2: The rule may be at least one of the following options: -- Option 2-1: The specific DCI field is always present. -- Option 2-2: The specific DCI field is not present at all. -- Option 2-3: The specific DCI field of a co-scheduled cell is always present. -- Option 2-4: The specific DCI field is always present for a cell that is included in a co-scheduled cell and has DWS configured. -- Option 2-5: The presence of the specific DCI field is determined based on the DWS bits for all co-scheduled cells. For example, if the DWS indicates CP-OFDM for all co-scheduled cells, the specific DCI field for all co-scheduled cells is present, otherwise the specific DCI field is not present.

[0367] According to this embodiment, if the DWS field in DCI format 0_X is 1 bit, it can be properly determined whether a specific DCI field exists.

[0368] <Embodiment B7> When the 1-bit DWS field is set for DCI format 0_X, the size (bit width) of a specific DCI field within that DCI format 0_X may be based on a rule, which may follow at least one of the following options:

[0369] - Option 1: The specific DCI field may be at least one of several options below: -- Option 1-1: Antenna port. -- Option 1-2: TPMI (precoding information and number of layers).

[0370] In Option 1-1 / 1-2, (the size of) at least one of the first specific DCI field and the second specific DCI field may be considered / determined. For example, (the size of) both the "precoding information and number of layers" field and the "second precoding information" field may be considered / determined.

[0371] - Option 2: The rule may follow at least one of the following options: -- Option 2-1: Regardless of the RRC configuration of the transform precoder, the rule determines the size of the specific DCI field assuming that the transform precoder is disabled (or enabled). -- Option 2-2: Regardless of the DWS instruction, the rule determines the size of the specific DCI field assuming that the transform precoder is disabled (or enabled). -- Option 2-3: The rule determines the size of the specific DCI field based on the RRC-configured transform precoder (transformPrecoder) for a specific CC. -- Option 2-4: The rule determines the size of the specific DCI field based on the RRC-configured transform precoder (transformPrecoder) for all co-scheduled cells. In this option, transformPrecoder may be common across multiple co-scheduled cells. -- Option 2-5: The rule determines the size of the specific DCI field based on the DWS instruction.

[0372] According to this embodiment, when the DWS field in DCI format 0_X is 1 bit, the size of a specific DCI field can be appropriately determined.

[0373] <Embodiment B8> When the N-bit DWS field is set for DCI format 0_X scheduling N CCs (Figure 21), the interpretation of the N-bit indication may follow at least one of the following forms.

[0374] - Configuration 8-1: For the corresponding cell, '0' may indicate CP-OFDM (transform precoder disabled) and '1' may indicate DFT-s-OFDM (transform precoder enabled). This interpretation avoids complex waveform combinations across co-scheduled cells.

[0375] - Configuration 8-2 For the corresponding cell, '0' may indicate the waveform configured in the RRC parameters, and '1' may indicate that the waveform is switched from the waveform configured in the RRC parameters. This case can be considered together with embodiment B1. For example, in configuration 1-1, indicating a complex waveform is avoided by restricting the transform precoder to be disabled.

[0376] In the form 8-1 / 8-2, the interpretation of '0' and '1' may be reversed.

[0377] The N bits of the DWS may follow the following options: - Option 1: The relationship between the N bits of the DWS and the N co-scheduled cells may follow at least one of the following options: -- Option 1-1: The least significant bit (LSB) corresponds to the CC with the lowest or highest index. For example, assuming N bits {ABCD} in the DWS field, where N=4, the CC with index 0 corresponds to bit D, the CC with index 1 corresponds to bit C, the CC with index 2 corresponds to bit B, and the CC with index 3 corresponds to bit A. -- Option 1-2: The relationship (mapping) is defined in the specification. -- Option 1-3: The relationship (mapping) is set by the RRC IE. -- Option 1-4: The relationship (mapping) is indicated by the DCI / MAC CE. -- Option 1-5: A set of multiple relationships (mappings) is configured by the RRC IE, and one relationship in the set is indicated by the DCI / MAC CE.

[0378] According to this embodiment, the N-bit DWS field in DCI format 0_X that schedules N CCs can be interpreted appropriately.

[0379] <Embodiment B9> When the N-bit DWS field is set for DCI format 0_X scheduling N CCs, the presence or absence of a specific DCI field in that DCI format 0_X may be based on a rule, which may follow at least one of the following options:

[0380] - Option 1: The specific DCI field may be at least one of several options below: -- Option 1-1: DMRS sequence initialization. -- Option 1-2: PTRS-DMRS association.

[0381] - Option 2: The rule may be at least one of the following options: -- Option 2-1: The specific DCI field is always present. -- Option 2-2: The specific DCI field is not present at all. -- Option 2-3: The specific DCI field of a co-scheduled cell is always present. -- Option 2-4: The specific DCI field is always present for a co-scheduled cell that has DWS configured. -- Option 2-5: The presence of the specific DCI field is determined based on the DWS bits for all co-scheduled cells. For example, if the DWS indicates CP-OFDM for a co-scheduled cell with index 0, the specific DCI field for that cell (e.g., the DMRS sequence initialization field) is present; otherwise, the specific DCI field is not present.

[0382] According to this embodiment, when the DWS field in DCI format 0_X that schedules N CCs is N bits, it can be appropriately determined whether a specific DCI field exists.

[0383] <Embodiment B10> When an N-bit DWS field is configured for DCI format 0_X that schedules N CCs, the size (bit width) of a specific DCI field in that DCI format 0_X may be based on a rule, which may follow at least one of the following options:

[0384] - Option 1: The specific DCI field may be at least one of several options below: -- Option 1-1: Antenna port field. -- Option 1-2: TPMI (precoding information and number of layers).

[0385] In Option 1-1 / 1-2, (the size of) at least one of the first specific DCI field and the second specific DCI field may be considered / determined. For example, (the size of) both the "precoding information and number of layers" field and the "second precoding information" field may be considered / determined.

[0386] - Option 2: The rule may follow at least one of the following options: -- Option 2-1: Regardless of the RRC configuration of the transform precoder, the rule determines the size of the specific DCI field assuming that the transform precoder is disabled (or enabled). -- Option 2-2: Regardless of the DWS instruction, the rule determines the size of the specific DCI field assuming that the transform precoder is disabled (or enabled). -- Option 2-3: The rule determines the size of the specific DCI field based on the RRC-configured transform precoder (transformPrecoder) for a specific CC. -- Option 2-4: The rule determines the size of the specific DCI field based on the RRC-configured transform precoder (transformPrecoder) for all co-scheduled cells. In this option, transformPrecoder may be common across multiple co-scheduled cells. -- Option 2-5: The rule determines the size of the specific DCI field based on the DWS instruction.

[0387] According to this embodiment, when the DWS field in DCI format 0_X that schedules N CCs is N bits, the size of a specific DCI field can be appropriately determined.

[0388] <Types of Multi-Carrier Operation> Types of multi-carrier operation include carrier aggregation (CA) and dual connectivity (DC).

[0389] CA can be classified into the following cases: - Case 1: Intra-band contiguous CA, which uses multiple contiguous CCs within a single band. A single power amplifier (PA) is assumed for the multiple CCs. - Case 2: Intra-band non-contiguous CA, which uses multiple non-contiguous CCs within a single band. Multiple PAs are assumed for the multiple CCs. - Case 3: Inter-band CA, which uses multiple CCs across multiple bands. Multiple PAs are assumed for the multiple CCs.

[0390] DC is basically the same as CA Case 3, and uses multiple CCs across multiple bands. Multiple PAs are assumed for the multiple CCs.

[0391] Analysis C: Using different waveforms for different CCs associated with a single PA is not very beneficial because even if only some of the CCs use DFT-S-OFDM, the PAPR characteristics considered in the PA are affected by the remaining CCs that use CP-OFDM.

[0392] Using different waveforms for different CCs associated with different PAs is similar to a single carrier. As long as the waveforms per PA are uniform, the PAPR performance is similar to a single carrier using either DFT-S-OFDM or CP-OFDM.

[0393] In Rel. 18, DCI-based waveform switching (DWS) between DFT-S-OFDM and CP-OFDM is considered to be supported. It is assumed that a single waveform is used for all CCs associated with a single PA. However, it has not been fully considered whether DWS will be supported in the case of multi-carrier operation.

[0394] <Embodiment C1> This embodiment relates to the relationship between DWS and multi-carrier operation.

[0395] DCI-based waveform switching (DWS) may support certain multi-carrier operations, and the UE may support DWS in certain multi-carrier operations, thereby obtaining the benefits of DWS in multi-carrier operations.

[0396] This embodiment may follow at least one of several options:

[0397] <<Option 1>> The specific multi-carrier operation may be at least one of several options 1-x below: - Option 1-1: Case 1 (intra-band contiguous CA) - Option 1-2: Case 2 (intra-band discontinuous CA) - Option 1-3: Case 3 (inter-band CA) - Option 1-4: Multi-carrier operation is not supported in DWS.

[0398] Option 1 may follow at least one of the following examples:

[0399] Example 1-1: DWS supports only Case 2 and Case 3. DWS may not be supported in intra-band continuous CA. When multiple bands supporting DWS are configured for intra-band continuous CA, it may be specified that DWS is not expected to be configured in those multiple bands (the UE does not expect DWS to be configured in those multiple bands).

[0400] Example 1-2: DWS supports only Case 3. DWS may not be supported in intra-band CA. When multiple bands supporting DWS are configured for intra-band CA, it may be specified that DWS is not expected to be configured in those multiple bands (the UE does not expect DWS to be configured in those multiple bands).

[0401] Example 1-3: DWS does not support operation using multiple carriers. When multiple CCs for PUSCH transmission are configured, it may be specified that DWS is not expected to be configured on those multiple CCs (the UE does not expect DWS to be configured on those multiple CCs).

[0402] <<Option 2>> The constraints on DWS and multi-carrier operation (eg, the constraints of Option 1) may be at least one of several of the following Options 2-x.

[0403] - Option 2-1: The restriction is always applied. For UEs that support DWS, the restriction on multi-carrier operation in DWS may always be applied.

[0404] - Option 2-2: The restriction is based on finer granularity of UE capabilities. The restriction may be based on RRC signaling corresponding to the UE capabilities. UE capabilities for DWS per feature set per component-carrier / cell (FSPC) may be defined.

[0405] - Option 2-3: The constraint depends on the UE capabilities at a coarser granularity. The constraint may be based on RRC signaling corresponding to the UE capabilities. Multiple UE capabilities for reporting DWS-related capabilities may be defined / supported / reported. One of the multiple UE capabilities may report support for DWS on a per-UE or per-band basis. Another of the multiple UE capabilities may report support for DWS in the multi-carrier case on a per-UE or per-band basis.

[0406] Option 2 may follow at least one of the following examples:

[0407] Example 2-1: UE capability for reporting DWS support is defined / reported for each FSPC. This UE capability report allows the NW / BS to identify in which band and in which case DWS is configured / executed.

[0408] - Example 2-2: For each UE, UE capability A is defined / reported for reporting support for DWS, and UE capability B is defined / reported for reporting support for DWS for the multi-carrier case. As shown in Figure 22, at least one of the following results may depend on capability A and capability B: -- If capability A is not supported and capability B is not supported, DWS (within that band) is not supported. -- If capability A is supported and capability B is not supported, DWS (within that band) is supported if multiple UL CCs (included in a band that supports DWS) are configured. -- If capability A is supported and capability B is supported, DWS (within that band) is supported in both single-CC operation and multi-CC operation.

[0409] According to this embodiment, the UE / BS can properly recognize whether DWS is supported / implemented in multi-carrier operation.

[0410] <Embodiment C2> This embodiment relates to intra-band continuous CA (Case 1).

[0411] When intra-band continuous CA is configured, a UE that supports DWS may support specific behavior for DWS indications on CCs associated with the intra-band continuous CA, where the CCs included in the intra-band continuous CA may be contiguous and within the same band.

[0412] <<Option 1>> The specific behavior may be at least one of several options 1-x below.

[0413] - Option 1-1: The UE does not expect different waveforms to be simultaneously indicated / configured / determined on any two CCs belonging to intra-band contiguous CA (Case 1).

[0414] - Option 1-2: When different waveforms are simultaneously indicated / configured / determined on multiple CCs belonging to Case 1, the UE applies the waveform determined on a specific CC among the multiple CCs. In this case, the UE may apply the waveform determined on a specific CC to all of the multiple CCs, or to only the specific CC. The specific CC may be at least one of the following CCs: -- One CC on which PUCCH can be transmitted. -- One CC on which PDCCH can be transmitted.

[0415] In Option 1-2, the specific CC may be the CC with the higher / highest priority among the multiple CCs belonging to Case 1. The priority for the multiple CCs may be determined according to at least one of the following options:

[0416] - Option 1: Priority is determined based on the (simultaneous) multiple UL channels on the multiple CCs. For example, the priority of a CC with a PUSCH scheduled by a DCI (dynamic grant, DG) is higher than the priority of a PUSCH with a configured (configured, configured grant, CG) PUSCH. For example, the priority of a CC with a PUSCH scheduled by a DCI and configured for DWS is higher than the priority of a CC with a PUSCH scheduled by a DCI and not configured for DWS. For example, the priority of a CC with a PUSCH scheduled by a DCI indicating DWS is higher than the priority of a PUSCH scheduled by a DCI not indicating DWS.

[0417] Option 2: Priority is determined based on whether DWS is configured on the CC, e.g., a CC with DWS configured has a higher priority than a CC without DWS configured.

[0418] - Option 3: The priority is determined based on the index of that CC. For example, the smaller the CC index, the higher the priority. For example, the larger the CC index, the higher the priority.

[0419] - Option 4: Priority is determined based on RRC configuration. For example, a priority may be set for each of multiple CCs by an RRC IE. For example, a CC for which a priority is set by an RRC IE is prioritized (has a higher priority) than a CC for which a priority is not set.

[0420] According to this embodiment, the UE / BS can properly perform DWS in in-band continuous CA.

[0421] <Embodiment C3> This embodiment relates to UE capabilities.

[0422] The UE capabilities may be according to at least one of several options:

[0423] <<Option 1>> Per-UE or per-band UE capability signaling may report support for DWS in at least one of the following cases: - Single-carrier case. - Multi-carrier case.

[0424] Option 2: Per-UE or per-band UE capability signaling may report support for DWS in the following cases: - Multi-carrier case with PA sharing (e.g. intra-band continuous CA) with the restriction that the same waveform is always applied across CCs.

[0425] <<Option 3>> UE capability signaling may report support for DWS in the following cases: - Multi-carrier case with PA sharing without any restrictions (e.g. intra-band continuous CA).

[0426] The structure of the UE capabilities may follow at least one of the following examples:

[0427] Example 1: Option 1 / 2 may be defined as a single basic feature in DWS (of Rel. 18). Option 3 may be defined as a separate feature from the basic feature in DWS (of Rel. 18), or as an advanced feature. The basic feature may be defined as a Functional Group (FG) that is a prerequisite for the advanced feature. The reporting granularity of the advanced feature may be finer than that of the basic feature, for example, per FSPC.

[0428] Example 2: Option 1 may be defined as a single basic feature in DWS (Rel. 18). Option 2 / 3 may be defined as separate features from the basic feature in DWS (Rel. 18), or as advanced features. The basic feature may be defined as a prerequisite feature group (FG) that is a prerequisite for the advanced feature. The reporting granularity of the advanced feature may be finer than that of the basic feature, for example, per FSPC.

[0429] According to this embodiment, the UE / BS can report / know the appropriate UE capabilities for DWS.

[0430] <Variations of Embodiment C> The UE may support options 1-1 to 1-4 of embodiment C1 depending on the UE capabilities. Different options among options 1-1 to 1-4 of embodiment C1 may be supported by different UEs.

[0431] The UE may support options from options 2-1 to 2-3 of embodiment C1 depending on the case in option 1. For different options from options 1-1 to 1-4, different options from options 2-1 to 2-3 of embodiment C1 may be supported.

[0432] In at least one of embodiments C1 to C3, the CA type (one of cases 1 to 3) may be determined based on at least one of the following pieces of information: - signaling from the BS, which may be at least one of an RRC configuration, a MAC CE indication, and a DCI indication; - a report from the UE, which may be at least one of capabilities and assistance information; - both of the above two pieces of information. For example, the CA type may be determined based on a capability report from the UE for CA and a configuration / instruction from the BS for CA.

[0433] Instead of distinguishing between Cases 1, 2, and 3, at least one of signaling from the BS and a report from the UE indicating whether a band / CC combination shares a single PA may be introduced. By replacing Case 1 with "a case in which a single PA is shared" and Cases 2 and 3 with "a case in which a PA per carrier / CC / band is implemented," at least one of Embodiments C1 to C3 may be applied.

[0434] <Analysis D1> UE capability signaling for DWS is considered.

[0435] DWS does not easily support multi-CC operation, especially in-band (continuous) CA.

[0436] In order to enable the UE to select whether to support DWS in intra-band CA operation, it is considered that the UE capability for DWS is based on at least one of the following definitions: ◇Definition 1: The capability is defined as a per-band capability. The UE can report whether it supports DWS for each band. ◇Definition 2: In the band in which the UE reports support for DWS, at least one of several restrictions is imposed on the number of CCs that can be configured to perform DWS within that band. -◇Option 1: No more than one CC can be configured within that band for the UE to support / perform DWS. -◇Option 2: The UE reports the number of CCs that support / perform DWS within that band.

[0437] In the case where only the constraints of option 1 are imposed, the UE cannot support DWS in in-band CA at all.

[0438] In the case where only the constraint of Option 2 is imposed, the signaling of the report should take into account the maximum number of CCs in the band, which causes larger reporting overhead. That is, the size (bit width, overhead) of the report of the number of CCs of DWS in the band supported by the UE depends on the number (maximum number) of CCs in the band supported by the UE. For example, if the number of CCs in the band supported by the UE is 4, the report of the number of CCs of DWS in the band supported by the UE has four candidates, so the size of the report is 2 bits. Option 2 is essentially equivalent to defining capability signaling for each FSPC.

[0439] <Embodiment D1> This embodiment relates to analysis D1.

[0440] UE capability signaling may be defined for a UE to report support for DWS in operation using multiple CCs in one band. This UE capability may be defined separately from UE capabilities for reporting support for DWS in another operation. The operation using multiple CCs in one band (first operation) may be intra-band CA or may include at least one of intra-band contiguous CA (where multiple CCs are contiguous) and intra-band discontinuous CA (where multiple CCs are not contiguous). The other operation (second operation) may be other than the first operation or may be an operation using multiple CCs across multiple bands. The operation using multiple CCs across multiple bands may be inter-band CA.

[0441] This embodiment minimizes reporting overhead for supporting basic DWS functionality, and allows the UE to support DWS in operation with multiple CCs within one band.

[0442] This embodiment may follow at least one of several options:

[0443] ◇Option 1: One or more components in the capability signaling may include at least one of several options 1-x below. - ◇Option 1-1: The number N of CCs in a band on which the UE supports DWS (the number N of CCs supported for DWS in a band). This component may correspond to option 2 above. The band may be the band on which the capability signaling is reported. The value of N may depend on the scenario. Different values ​​of N may be reported for different scenarios. The different scenarios may be operation using contiguous CCs (e.g., intra-band CA) or operation using discontinuous CCs (e.g., intra-band CA). - ◇Option 1-2: The number N1 of contiguous CCs in a band on which the UE supports DWS (the number N1 of contiguous CCs supported for DWS in a band). - ◇Option 1-3: The number N2 of discontinuous CCs in a band on which the UE supports DWS (the number N2 of discontinuous CCs supported for DWS in a band).

[0444] ◇Option 2: Constraints on the one or more components may follow at least one of the following several options 2-x: - ◇Option 2-1: N is greater than 1. Support for DWS in the case of N=1 may be reported via separate UE capability signaling. The separate UE capability signaling may, for example, indicate support for basic DWS functions. - ◇Option 2-2: N1 is greater than 1. - ◇Option 2-2a: N1 is greater than or equal to 1. - ◇Option 2-3: N2 is greater than 1. - ◇Option 2-4: Relationship between N1 and N2. The relationship may include any of N1≦N2, N1<N2, N1≧N2, or N1>N2.

[0445] Separate / separate UE capability signaling may be considered / defined for intra-band contiguous CA and intra-band discontinuous CA. This embodiment may be applied to at least one of intra-band contiguous CA and intra-band discontinuous CA.

[0446] MPR Calculation in Multi-Carrier Operation The UE is allowed to reduce its maximum output power due to higher order modulation and transmission bandwidth settings.

[0447] The specification defines maximum power reduction (MPR) calculations for various multi-carrier (multiple CC) operations. Multiple MPR values ​​specific to intra-band continuous CA are defined. Figure 23 shows an example (Table M-1) of multiple MPR values ​​for intra-band continuous CA, power class 3, and contiguous RB placement. In this table, each MPR value is associated with a combination of waveform type (DFT-s-OFDM or CP-OFDM) and modulation order (Pi / 2 BPSK, QPSK, etc.).

[0448] If the modulation formats or waveform types (DFT-s-OFDM or CP-OFDM) are different on different CCs, the requirements are set by the rules that apply to the waveform type and modulation order used in the configuration with the maximum (worst) MPR.

[0449] The MPR for intra-band discontinuous CA follows several cases: ◇Case 1: In the case where UL transmissions across multiple CCs are not performed simultaneously, the MPR is the same as the MPR for single-CC operation. ◇Case 2: In other cases, multiple values ​​of the MPR specific to this operation (intra-band discontinuous CA) are defined. The multiple values ​​of the MPR are completely different from the MPR for single-CC operation.

[0450] The MPR for inter-band CA is the same as the MPR for single CC operation.

[0451] In the present disclosure, the worst MPR value and the highest MPR value may be read interchangeably.

[0452] <Analysis D2> As described above, for intra-band contiguous CA, the worst-case MPR value across multiple corresponding CCs is considered. For example, if DFT-s-OFDM is configured for CC #1 and CP-OFDM is configured for CC #1, the worst-case MPR across CC #1 and CC #2 (e.g., the MPR for CP-OPDM) is considered. When DFT-s-OFDM is indicated via DWS, if DFT-s-OFDM is not considered in determining the MPR, the advantage of DFT-s-OFDM (smaller MPR) cannot be obtained according to the worst-case MPR value across multiple CCs rule.

[0453] In intra-band discontinuous CA, there is no such rule (MPR determination follows the MPR determination method for the single CC case or a waveform-independent method).

[0454] <Embodiment D2> This embodiment relates to analysis D2.

[0455] When a UE reports support for DWS in operation using multiple CCs in one band (multi-carrier operation), certain restrictions (conditions) may apply. Certain restrictions (conditions) may apply to a UE reporting support for DWS in operation using multiple CCs in one band. According to this embodiment, no overhead is generated for DWS UE capability signaling for certain (non-meaningful) scenarios. The certain scenarios may be scenarios where the benefits of DWS (DFT-s-OFDM) cannot be obtained, or DWS in intra-band continuous CA.

[0456] This embodiment may follow at least one of several options:

[0457] ◇Option 1: The specific constraint may include at least one of the following several options 1-x: -◇Option 1-1: The multiple CCs are non-contiguous. -◇Option 1-2: More than one CC of the multiple CCs simultaneously carries UL with non-zero bandwidth.

[0458] ◇Option 2: When a specific constraint is not guaranteed (satisfied), the UE behavior may follow at least one of the following several options 2-x. -◇Option 2-1: The UE ignores the DWS configuration. -◇Option 2-2: The UE ignores the DWS indication on the DCI. -◇Option 2-3: The UE ignores the indication information carried on the DCI with the Transform Precoder Indicator (TPI) field (DWS field). The UE may ignore the TPI field and indication information other than the TPI field. The indication information other than the TPI field may be, for example, PUSCH scheduling information. This UE behavior may cause the UE not to transmit a PUSCH scheduled by that DCI. -◇Option 2-4: The specific constraint is always guaranteed (satisfied). The specification may specify that "the UE does not expect a PUSCH transmission to be scheduled with the TPI field unless a specific condition (specific constraint) is met." To ensure certain constraints, at least one of (1) the number of CCs to be used for UL transmission, (2) one or more slots to be used for UL transmission, and (3) the content of the TPI field may be restricted.

[0459] If certain constraints are guaranteed (met), the UE may receive at least one of a DWS configuration (a setting that enables DWS) and a DWS indication (a DCI that includes a DWS indication).

[0460] Option 1 / 2 of this embodiment may be applied to at least one of the following targets: ◇ Target 1: All CCs in the multi-CC operation. ◇ Target 2: Scheduling CC. The CC may be a CC on which a DCI with a DWS indication is transmitted (received). ◇ Target 3: Scheduled CC. The CC may be a CC on which a PUSCH is scheduled (transmitted) by a DCI with a DWS indication. ◇ Target 4: All CCs in the multi-CC operation on which DWS is configured.

[0461] <Supplementary Information> [Notification of Information to UE] In the above-described embodiments, any information may be notified to the UE (from a network (NW) (e.g., a base station (BS))) (in other words, reception of any information from the BS by the UE) 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.

[0462] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new Logical Channel ID (LCID) in the MAC subheader, which is not defined in existing standards.

[0463] When the notification is made by DCI, the notification may be made by a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used to scramble Cyclic Redundancy Check (CRC) bits assigned to the DCI, the format of the DCI, etc.

[0464] Furthermore, notification of any information to the UE in the above embodiments may be performed periodically, semi-persistently, or aperiodically.

[0465] [Notification of Information from UE] In the above-described embodiments, notification of any information from the UE (to the NW) (in other words, transmission / report of any information from the UE to the BS) may be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PUCCH, PUSCH, PRACH, reference signal), or a combination thereof.

[0466] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new LCID, which is not defined in existing standards, in the MAC subheader.

[0467] If the notification is made by UCI, the notification may be transmitted using PUCCH or PUSCH.

[0468] Furthermore, any information in the above-described embodiments may be notified from the UE periodically, semi-persistently, or aperiodically.

[0469] [Application of Each Embodiment] At least one of the above-described embodiments may be applied when a specific condition is met. The specific condition may be defined in a standard or may be notified to a UE / BS using higher layer signaling / physical layer signaling.

[0470] The specific condition may be one of the following conditions, or may be defined by AND / OR of two or more of the following conditions: ◇ The UE reports a specific UE capability (at least one function of the above-mentioned embodiments). ◇ The UE is configured with at least one function of the above-mentioned embodiments.

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

[0472] The specific UE capabilities may indicate at least one of the following: Supporting specific processing / operations / control / information for at least one of the above embodiments.

[0473] Furthermore, the above-mentioned specific UE capability may be a capability that is applied across all frequencies (commonly regardless of frequency), or may be a capability for each frequency (e.g., one or a combination of a cell, a band, a band combination, a BWP, a component carrier, etc.), or may be a capability for each frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), or may be a capability for each subcarrier spacing (SubCarrier Spacing (SCS)), or may be a capability for each Feature Set (FS) or Feature Set Per Component-carrier (FSPC).

[0474] Furthermore, the specific UE capability may be a capability that is applied to all duplexing methods (commonly regardless of the duplexing method), or may be a capability for each duplexing method (e.g., Time Division Duplex (TDD) or Frequency Division Duplex (FDD)).

[0475] Furthermore, at least one of the above-described embodiments may be applied when a UE configures / activates / triggers specific information related to the above-described embodiments (or performs the operations of the above-described embodiments) through higher layer signaling / physical layer signaling. The specific information may indicate at least one of the following: ◇ Information indicating enabling / disabling the operations of the above-described embodiments. ◇ RRC parameters for a specific release (e.g., Rel. 18 / 19). The RRC parameters may have names that are the names of existing RRC parameters with "r18" / "r19" added.

[0476] If the UE does not support at least one of the specific UE capabilities or is not configured with the specific information, the UE may apply, for example, Rel. 15 / 16 behavior.

[0477] (Supplementary Notes) The following inventions are supplemented with respect to one embodiment of the present disclosure. [Supplementary Note 1] A terminal comprising: a transmitter unit that transmits capability information related to supporting a dynamic transformation precoder indication in operation using multiple component carriers in one band; and a controller that controls reception of a configuration of the dynamic transformation precoder indication. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein the capability information includes at least one of: a number of component carriers that support the dynamic transformation precoder indication, a number of contiguous component carriers that support the dynamic transformation precoder indication, and a number of discontinuous component carriers that support the dynamic transformation precoder indication. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein at least one of the configuration and the dynamic transformation precoder indication is received when at least one of the multiple component carriers are discontinuous and more than one component carrier among the multiple component carriers simultaneously carries an uplink with a non-zero bandwidth is satisfied. [Supplementary Note 4] The terminal according to any one of Supplementary Note 1 to Supplementary Note 3, wherein, when at least one of the following conditions is not met: the plurality of component carriers are discontinuous; and more than one of the plurality of component carriers simultaneously carries an uplink with a non-zero bandwidth; and the dynamic conversion precoder indication is received, the controller ignores at least one of the configuration, the dynamic conversion precoder indication, and downlink control information including the dynamic conversion precoder indication.

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

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

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

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

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

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

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

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

[0486] Furthermore, the user terminal 20 may perform communication using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.

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

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

[0489] The core network 30 may include network functions (Network Functions (NF)) such as 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), and Operation, Administration and Maintenance (Management) (OAM). A single network node may provide multiple functions. Communication with an external network (e.g., the Internet) may also be performed via the DN.

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

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

[0492] The radio access scheme may also be called a waveform. Note that in the wireless communication system 1, other radio access schemes (e.g., other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.

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

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

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

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

[0497] Note that the DCI for scheduling the PDSCH may be referred to as a DL assignment, a DL DCI, etc., and the DCI for scheduling the PUSCH may be referred to as a UL grant, a UL DCI, etc. Note that the PDSCH may be replaced with DL data, and the PUSCH may be replaced with UL data.

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

[0499] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be referred to as a search space set. Note that the terms "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," "CORESET configuration," and the like in the present disclosure may be read interchangeably.

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

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

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

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

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

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

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

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

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

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

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

[0511] The transmitting and receiving antenna 130 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure relates, such as an array antenna.

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

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

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

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

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

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

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

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

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

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

[0522] The transceiver unit 120 may receive capability information related to supporting dynamic transformation precoder indication in operation using multiple component carriers within one band. The control unit 110 may control transmission of the configuration of the dynamic transformation precoder indication.

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

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

[0525] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be configured from a controller, a control circuit, etc., which are described based on common understanding in the technical field to which the present disclosure relates.

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

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

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

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

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

[0531] The transceiver unit 220 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

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

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

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

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

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

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

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

[0539] The transmitting unit and receiving unit of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting / receiving unit 220 and the transmitting / receiving antenna 230.

[0540] The transceiver unit 220 may transmit capability information related to supporting dynamic transformation precoder indication in operation using multiple component carriers in one band. The control unit 210 may control reception of the setting of the dynamic transformation precoder indication.

[0541] The capability information may include at least one of the number of component carriers that support the dynamic transformation precoder indication, the number of consecutive component carriers that support the dynamic transformation precoder indication, and the number of non-consecutive component carriers that support the dynamic transformation precoder indication.

[0542] At least one of the configuration and the dynamic conversion precoder indication may be received when at least one of the following conditions is met: the plurality of component carriers are discontinuous; and more than one of the plurality of component carriers simultaneously carries an uplink with a non-zero bandwidth.

[0543] If at least one of the following conditions is not met: the plurality of component carriers are discontinuous; and more than one of the plurality of component carriers simultaneously carries an uplink with a non-zero bandwidth; and the dynamic conversion precoder indication is received, the control unit 210 may ignore at least one of the setting, the dynamic conversion precoder indication, and downlink control information including the dynamic conversion precoder indication.

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

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

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

[0547] In the present disclosure, the terms apparatus, circuit, device, section, unit, etc. may be used interchangeably. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.

[0548] For example, although only one processor 1001 is shown, there may be multiple processors. Furthermore, processing may be performed by one processor, or processing may be performed by two or more processors simultaneously, serially, or in other ways. Furthermore, processor 1001 may be implemented by one or more chips.

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

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

[0551] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and the other functional blocks may be implemented in a similar manner.

[0552] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EEPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. The memory 1002 may also be referred to as a register, cache, main memory, etc. The memory 1002 may store executable programs (program codes), software modules, etc. for implementing a wireless communication method according to an embodiment of the present disclosure.

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

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

[0555] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, a light emitting diode (LED) lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

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

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

[0558] (Modifications) Note that terms described in the present disclosure and terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, a channel, a symbol, and a signal (signal or signaling) may be interchangeable. A signal may also be a message. A reference signal may be abbreviated as RS, and may also be called a pilot, pilot signal, etc. depending on the applicable standard. A component carrier (CC) may also be called a cell, frequency carrier, carrier frequency, etc.

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

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

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

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

[0563] A radio frame, a subframe, a slot, a minislot, and a symbol all represent time units for transmitting signals. The radio frame, the subframe, the slot, the minislot, and the symbol may be referred to by other names corresponding to the radio frame, the subframe, the slot, the minislot, and the symbol. Note that the time units such as a frame, a subframe, a slot, a minislot, and a symbol in the present disclosure may be interchangeable.

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

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

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

[0567] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

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

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

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

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

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

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

[0574] A Bandwidth Part (BWP), which may also be referred to as a partial bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a Common Reference Point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

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

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

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

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

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

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

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

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

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

[0584] Note that the physical layer signaling may be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be referred to as an RRC message, such as an RRC Connection Setup message or an RRC Connection Reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, a MAC Control Element (CE).

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

[0586] The determination may be made by a value represented by one bit (0 or 1), by a Boolean value represented by true or false, or by a comparison of numerical values ​​(e.g., comparison with a predetermined value).

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

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

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

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

[0591] In the present disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNB (eNodeB)," "gNB (gNodeB)," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "cell," "sector," "cell group," "carrier," "component carrier," etc. may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.

[0592] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication service within that coverage.

[0593] In the present disclosure, a base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control / operate based on the information.

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

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

[0596] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. Note that at least one of the base station and the mobile station may be a device mounted on a moving object, the moving object itself, etc.

[0597] The mobile body is a movable object that can move at any speed and naturally includes cases where the mobile body is stationary. Examples of the mobile body include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and objects mounted thereon. The mobile body may also be a mobile body that moves autonomously based on an operation command.

[0598] The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Note that at least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0599] 28 is a diagram showing an example of a vehicle according to an embodiment. The vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, an electronic control unit 49, various sensors (including a current sensor 50, an RPM 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.

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

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

[0602] The signals from the various sensors 50-58 include a current signal from a current sensor 50 that senses the current of the motor, a rotation speed signal of the front wheels 46 / rear wheels 47 obtained by a rotation speed sensor 51, an air pressure signal of the front wheels 46 / rear wheels 47 obtained by an air pressure sensor 52, a vehicle speed signal obtained by a vehicle speed sensor 53, an acceleration signal obtained by an acceleration sensor 54, a depression amount signal of the accelerator pedal 43 obtained by an accelerator pedal sensor 55, a depression amount signal of the brake pedal 44 obtained by a brake pedal sensor 56, an operation signal of the shift lever 45 obtained by a shift lever sensor 57, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 58.

[0603] The information service unit 59 is composed of various devices, such as a car navigation system, an audio system, speakers, a display, a television, and a radio, for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 59 uses information acquired from external devices via the communication module 60 or the like to provide various information / services (e.g., multimedia information / multimedia services) to the occupants of the vehicle 40.

[0604] The information service unit 59 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

[0605] The driving assistance system unit 64 includes various devices for providing functions to prevent accidents and reduce the driver's driving burden, such as millimeter-wave radar, Light Detection and Ranging (LiDAR), cameras, positioning locators (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyro systems (e.g., Inertial Measurement Units (IMUs), Inertial Navigation Systems (INSs)), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driving assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driving assistance functions or autonomous driving functions.

[0606] The communication module 60 can communicate with the microprocessor 61 and components of the vehicle 40 via the communication port 63. For example, the communication module 60 transmits and receives data (information) via the communication port 63 to and from the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and the various sensors 50-58, which are provided in the vehicle 40.

[0607] The communication module 60 is a communication device that can be controlled by the microprocessor 61 of the electronic control unit 49 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 60 may be located either inside or outside the electronic control unit 49. The external device may be, for example, the base station 10 or the user terminal 20 described above. Furthermore, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 described above (or may function as at least one of the base station 10 and the user terminal 20).

[0608] The communication module 60 may transmit at least one of signals from the above-mentioned various sensors 50-58 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 an external device via wireless communication. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 60 may include information based on the above-mentioned input.

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

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

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

[0612] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station 10 may be configured to have the functions of the user terminal 20 described above.

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

[0614] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, the order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0615] Each aspect / embodiment described in the present disclosure may be a technology other than 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, for example, an integer or decimal number)), 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.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802. The present invention may be applied to systems that use IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable wireless communication methods, or to next-generation systems that are expanded, modified, created, or defined based on these. Furthermore, the present invention may be applied to a combination of multiple systems (e.g., a combination of LTE or LTE-A and 5G).

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

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

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

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

[0620] Also, "determination" may be considered to be "deciding" resolving, selecting, choosing, establishing, comparing, etc. In other words, "determination" may be considered to be "deciding" some action.

[0621] Furthermore, "judgment (decision)" may be read as "assuming," "expecting," "considering," or the like.

[0622] The "maximum transmit power" in this disclosure may mean the maximum value of transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

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

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

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

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

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

[0628] In the present disclosure, terms such as "less than or equal to," "less than," "greater than," "more than," "equal to," etc. may be interchangeable. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative, as expressions with "i-th" (i is an arbitrary integer) attached (for example, "highest" may be interchangeable with "i-th highest").

[0629] In this disclosure, the terms "of," "for," "regarding," "related to," "associated with," etc. may be read interchangeably.

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

[0631] This application is based on Japanese Patent Application No. 2023-192789, filed November 13, 2023, the contents of which are incorporated herein in their entirety.

Claims

1. A terminal having a transmitting unit that transmits capability information regarding supporting a dynamic conversion precoder instruction in operation using multiple component carriers in one band; and a control unit that controls reception of the setting of the dynamic conversion precoder instruction.

2. The terminal according to claim 1, wherein the capability information includes at least one of the number of component carriers that support the dynamic conversion precoder indication, the number of consecutive component carriers that support the dynamic conversion precoder indication, and the number of discontinuous component carriers that support the dynamic conversion precoder indication.

3. The terminal of claim 1, wherein at least one of the configuration and the dynamic conversion precoder indication is received when at least one of the following conditions is met: the plurality of component carriers are non-contiguous; and more than one of the plurality of component carriers simultaneously carries an uplink with a non-zero bandwidth.

4. The terminal of claim 1, wherein when at least one of the following conditions is not met: the plurality of component carriers are discontinuous; and more than one of the plurality of component carriers simultaneously carries an uplink with a non-zero bandwidth; and the dynamic conversion precoder indication is received, the control unit ignores at least one of the setting, the dynamic conversion precoder indication, and downlink control information including the dynamic conversion precoder indication.

5. A wireless communication method for a terminal, comprising: a step of transmitting capability information regarding supporting a dynamic conversion precoder indication in operation using multiple component carriers in one band; and a step of controlling reception of the setting of the dynamic conversion precoder indication.

6. A base station having: a receiving unit that receives capability information regarding supporting a dynamic conversion precoder indication in operation using multiple component carriers in one band; and a control unit that controls transmission of settings of the dynamic conversion precoder indication.

Images