Terminal, wireless communication method, and base station

Abstract

To provide a terminal, wireless communication method, and base station capable of appropriately switching waveforms. [Solution] In a next-generation mobile communication system, the transmitting / receiving unit 220 of the user terminal 20 receives downlink control information including a first field for scheduling multiple uplink sharing channels transmitted on multiple cells and a second field relating to waveforms. Based on the received downlink control information, the control unit 210 determines multiple waveforms to be applied to each of the multiple uplink sharing channels.

Description

[Technical Field]

[0001] This disclosure relates to terminals, wireless communication methods, and base stations in next-generation mobile communication systems. [Background technology]

[0002] Long Term Evolution (LTE) was specified for Universal Mobile Telecommunications System (UMTS) networks with the aim of achieving even higher data rates and lower latency (Non-Patent Literature 1). Furthermore, LTE-Advanced (3GPP Rel.10-14) was specified for the aim of further increasing capacity and sophistication of LTE (Third Generation Partnership Project (3GPP®) Release (Rel.) 8, 9).

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

[0004] [Non-Patent Document 1] 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010 [Overview of the project] [Problems that the invention aims to solve]

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

[0006] However, since conventional waveform settings were handled by Radio Resource Control (RRC), switching waveforms required RRC reconfiguration. This increased signaling overhead and could potentially reduce communication throughput.

[0007] Therefore, one of the objectives of this disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately perform waveform switching. [Means for solving the problem]

[0008] A terminal according to one aspect of the present disclosure includes a receiving unit that receives downlink control information including a first field for scheduling multiple uplink sharing channels transmitted on multiple cells and a second field relating to waveforms, and a control unit that determines multiple waveforms to be applied to each of the multiple uplink sharing channels based on the downlink control information. [Effects of the Invention]

[0009] According to one aspect of this disclosure, waveform switching can be performed appropriately. [Brief explanation of the drawing]

[0010] [Figure 1] Figure 1 is a diagram showing the DCI size of Option 1-1. [Figure 2] Figure 2 is a diagram showing the DCI size of Option 1-2. [Figure 3] Figure 3 is a flowchart showing an example of the process of Embodiment 0.1. [Figure 4] Figure 4 is a flowchart showing an example of the process of Embodiment 0.2. [Figure 5] Figure 5 is a diagram showing the definition of PTRS-DMRS association and DMRS sequence initialization of the DCI field. [Figure 6] Figure 6 is a diagram showing an example of the setting pattern of useInterlacePUCCH-PUSCH, resourceAllocation, and RA type. [Figure 7] Figure 7 is a flowchart showing an example of the process of Embodiment 3. [Figure 8] Figure 8 is a diagram showing an example of the MAC payload. [Figure 9] Figure 9 is a diagram showing an example of the number of bits of the RAR grant field. [Figure 10] Figure 10 is a diagram showing an example of the value of the TPC command. [Figure 11] Figure 11 is a diagram showing an example of the Backoff Parameter value. [Figure 12] Figure 12 is a diagram showing an example of the antenna port field of DCI format 0_1. [Figure 13] Figure 13 is a diagram showing an example of the setting of the DMRS type when dynamic waveform switching is set. [Figure 14] Figures 14A and 14B are diagrams showing an example of the method of interpreting the code point of a predetermined field of DCI when dynamic waveform switching is set and DMRS type 2 is set. [Figure 15] Figure 15 is a diagram showing an example of the RRC IE according to Embodiment A1. [Figure 16] FIG. 16 is a diagram showing an example of DCI according to Embodiment A4. [Figure 17] FIGS. 17A and 17B are diagrams showing an example of multi-carrier scheduling. [Figure 18] FIGS. 18A and 18B are diagrams showing another example of multi-carrier scheduling. [Figure 19] FIG. 19 is a diagram showing an example of a 1-bit DWS field in multi-carrier DCI. [Figure 20] FIG. 20 is a diagram showing an example of a waveform instructed for a plurality of cells according to Embodiment B5. [Figure 21] FIG. 21 is a diagram showing an example of an N-bit DWS field in multi-carrier DCI. [Figure 22] FIG. 22 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 23] FIG. 23 is a diagram showing an example of a configuration of a base station according to an embodiment. [Figure 24] FIG. 24 is a diagram showing an example of a configuration of a user terminal according to an embodiment. [Figure 25] FIG. 25 is a diagram showing an example of a hardware configuration of a base station and a user terminal according to an embodiment. [Figure 26] FIG. 26 is a diagram showing an example of a vehicle according to an embodiment.

Mode for Carrying Out the Invention

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

[0012] CP-OFDM allows for more flexible frequency resource allocation. For example, both continuous and non-continuous Physical Resource Block (PRB) allocations are permitted. Furthermore, continuous PRB allocations are not limited to multiples of 2, 3, or 5. When applying CP-OFDM, frequency division multiplexing (FDM) may be used for the DeModulation Reference Signal (DMRS) and PUSCH.

[0013] DFT-s-OFDM (or DFT-S-OFDM / DFTS-OFDM) has significant constraints on frequency resource allocation, but it has a low Peak to Average Power Ratio (PAPR) and is suitable for power-constrained UEs.

[0014] Regarding communication throughput without considering PAPR, CP-OFDM has higher communication throughput than DFT-s-OFDM. Regarding communication throughput considering PAPP, when the SNR(MCS) is high (modulation coding scheme is 16QAM or 64QAM), the communication throughput of CP-OFDM is higher than that of DFT-s-OFDM. However, when the SNR(MCS) is low (modulation coding scheme is QPSK), DFT-s-OFDM has higher communication throughput than CP-OFDM. In other words, the preferred waveform differs depending on the SNR(MCS).

[0015] Typically, networks (NW) switch waveforms based on the Signal to Noise Ratio (SNR). The switching between DFT-s-OFDM and CP-OFDM is controlled by the "transformPrecoder" in the Radio Resource Control (RRC) signaling uplink shared channel (PUSCH) setting (PUSCH-Config). When the transformPrecoder is disabled, CP-OFDM is applied; when enabled, DFT-s-OFDM is applied. Switching waveforms requires RRC reconfiguration, which can increase signaling overhead and potentially 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. However, such dynamic switching has not yet been thoroughly investigated.

[0017] For example, in existing specifications (e.g., 3GPP Rel.16), the size of several DCI fields in the DCI format (e.g., DCI format 0_0 / 0_1 / 0_2) is affected by waveform switching, as shown in (1) to (6) below. (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, it will be 0 bits if the conversion precoder is enabled, and 1 bit if it is disabled. (4) In the "PTRS-DMRS association" field, the DCI size is affected by the conversion precoder. (5) In "Frequency domain resource assignment," the DCI size varies depending on the resource assignment type. Also, the supported resource assignments differ depending on the waveform. CP-OFDM supports resource assignment types 0, 1, and 2, while DFT-s-OFDM supports resource assignment types 1 and 2. (6) In the "Frequency hopping flag" field, the DCI size varies depending on the resource allocation type. As mentioned above, different waveforms support different resource allocations.

[0018] (Dynamic switching of disabling and enabling the conversion precoder) The UE may receive a setting indicating that the conversion precoder for PUSCH should be dynamically switched between being disabled and enabled via DCI / MAC CE. The UE may also receive instructions via DCI / MAC CE indicating whether to enable or disable the conversion precoder for PUSCH. Hereinafter, dynamic switching via DCI / MAC CE may be simply referred to as dynamic switching. The UE may also pre-configure the dynamic switching of waveforms / conversion precoders (that switching is possible) in the upper layer signaling, etc. Dynamic switching of the conversion precoder via DCI / MAC CE may be possible regardless of whether such a setting exists.

[0019] For example, DCI signaling-based dynamic waveform switching may be implicit or explicit. For example, a 1-bit field indicating the CP-OFDM or DFT-s-OFDM waveform used for PUSCH may be included in the DCI (explicit signaling). For example, the UE may determine / identify the CP-OFDM or DFT-s-OFDM waveform used for PUSCH based on specific conditions among scheduling information in the DCI (implicit signaling). In this case, the existing DCI format is not changed.

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

[0021] The DCI format in this disclosure may refer to, for example, DCI formats 0_0 / 0_1 / 0_2, or other formats (e.g., DCI format 0_3 for notifying waveform switching). As other formats, a group common DCI such as DCI format 2_x may be used. In this case, the waveform switching may be applied a certain time after the UE receives DCI format 2_x and sends an ACK.

[0022] In this disclosure, switching between disabling and enabling the conversion precoder (switching the waveform) may also be a waveform switch within the same BWP (switching the waveform without switching the BWP). For example, since different conversion precoders can be set for each BWP, it is conceivable to switch the conversion precoder by switching the BWP, but since switching the BWP causes a delay, the delay can be suppressed by switching between disabling and enabling the conversion precoder within the same BWP.

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

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

[0025] However, for some DCI fields, the size of each DCI field may differ depending on whether the conversion precoder is disabled or enabled. These DCI fields include, for example, "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 above.

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

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

[0028] Figure 1 shows the DCI size for option 1-1. According to Figure 1, the number of DCI bits (total of DCIField#1~#4) when the conversion precoder is disabled is 10 bits, and the number of DCI bits when the conversion 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 conversion precoder is set.

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

[0030] Option 1-1 allows for a smaller total DCI size compared to Option 1-2, which will be discussed later.

[0031] [Options 1-2] If dynamic switching of the conversion precoder for PUSCH is set to PUSCH, for each DCI format, the larger of the size of the DCI field when the conversion precoder is disabled and the size of the DCI field when the conversion precoder is enabled is determined for each field, and the total size of the DCI format may be the sum of the larger of these sizes for all DCI fields.

[0032] In other words, if N is the number of fields in a given DCI format, the total size of the DCI format is calculated as follows: The total size of the DCI format = Σ(MAX(size of DCI field i when the conversion precoder is disabled, size of DCI field i when the conversion precoder is enabled))(i=1~N)

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

[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 conversion precoder is disabled (2 bits) and the DCI field size when the conversion 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 summing these sizes (2+3+2+4=11), a total DCI size of 11 bits is used when dynamic switching of the conversion precoder is enabled.

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

[0036] In the example in Figure 2, the starting bit of each field (the bit range used for each field) is the same whether the conversion precoder is disabled or enabled. For example, the starting bit of DCI Field #1 is the 1st bit, the starting bit of DCI Field #2 is the 3rd bit, the starting bit of DCI Field #3 is the 6th bit, and the starting bit of DCI Field #4 is the 8th bit. Therefore, the detection process for each field of the UE can be easily performed.

[0037] In options 1-2, the DCI size detected remains the same even if the conversion precoder is enabled or disabled, thus suppressing the increase in the UE's processing load.

[0038] (FDRA type) 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., it may be non-contiguous). Type 1: Continuous allocation based on Resource Indication Value (RIV). Type 2: Interlaced layout (for NR-unlicensed(U)).

[0039] The applicability, which depends on the type of PUSCH waveform, is supported as follows: Type 0: Applicable only to CP-OFDM. 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 set, type 0 or type 1 is used depending on the RRC parameter resourceAllocation. When sending type 1 UL data without grants, resourceAllocation is set to resourceAllocationType0 or resourceAllocationType1. If resourceAllocationType0 is set, type 0 is used; 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 (first symbol or near the first symbol) DMRS for faster demodulation. Additional DMRS can be set by the RRC for fast-moving UEs or high modulation and coding scheme (MCS) / rank. The frequency position of the additional DMRS is the same as that of the front-loaded DMRS.

[0042] For the time domain, either 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 set by a parameter (dmrs-TypeA-Position) in the MIB or Common Serving Cell Configuration (ServingCellConfigCommon). DMRS position 0 (reference point l) means the first symbol in 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) means the first symbol in the PDSCH / PUSCH or each frequency hop.

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

[0044] For each frequency domain, either (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). In DMRS configuration type 1, a DMRS sequence is mapped to one subcarrier for every two subcarriers in the frequency domain, allowing up to two DMRSs to be FDM'd. DMRS configuration type 2 is applicable only to CP-OFDM. In DMRS configuration type 2, a DMRS sequence is mapped to two consecutive subcarriers for every six subcarriers in the frequency domain, allowing up to three DMRSs to be FDM'd.

[0045] Single-symbol DMRS or double-symbol DMRS is set.

[0046] Single-symbol DMRS is commonly 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 cases where frequency hopping is enabled and disabled. If the maximum number (maxLength) in the uplink DMRS configuration (DMRS-UplinkConfig) is not set, 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 supports cases where frequency hopping is disabled. If the maximum number (maxLength) in the uplink DMRS configuration (DMRS-UplinkConfig) is 2 (len2), whether it is single-symbol DMRS or double-symbol DMRS is determined by DCI or configured grant.

[0048] Based on the above, the following combinations of DMRS configuration patterns are possible. • 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 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 by a length 2 FD OCC. Between multiple DMRS CDM groups (two DMRS CDM groups), two DMRS ports are multiplexed by 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 a length 2 FD OCC, 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] Six DMRS ports can be used for DMRS configuration type 2 and single-symbol DMRS. Within each DMRS CDM group, two DMRS ports are multiplexed by a length 2 FD OCC. Between multiple DMRS CDM groups (three DMRS CDM groups), three DMRS ports are multiplexed by FDM.

[0053] Twelve DMRS ports can be used for DMRS configuration type 2 and double-symbol DMRS. Within each DMRS CDM group, two DMRS ports are multiplexed by a length 2 FD OCC, 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, we have shown an example of DMRS mapping type B, but DMRS mapping type A is 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] (Reference signal port) Multiple port reference signals (e.g., Demodulation Reference Signal (DMRS), CSI-RS) are used for purposes such as orthogonalizing the MIMO layer.

[0058] For example, for Single User MIMO (SU-MIMO), different DMRS ports / CSI-RS ports may be configured for each layer. For Multi User MIMO (MU-MIMO), different DMRS ports / CSI-RS ports may be configured for each layer within a single UE, and for each UE as well.

[0059] Furthermore, using a number of CSI-RS ports greater than the number of layers used in the data is expected to enable more accurate measurement of channel status based on the CSI-RS, thereby contributing to improved throughput.

[0060] In Rel.15 NR, multi-port DMRS can support up to 8 ports for Type 1 DMRS (in other words, DMRS configuration type 1) and up to 12 ports for Type 2 DMRS (in other words, DMRS configuration type 2) by using technologies such as Frequency Division Multiplexing (FDM), Frequency Domain Orthogonal Cover Code (FD-OCC), and Time Domain OCC (TD-OCC).

[0061] In Rel.15 NR, the above FDM uses a comb-shaped transmission frequency pattern (comb-shaped resource set). The above FD-OCC uses cyclic shift (CS). Furthermore, the above TD-OCC can only be applied to double-symbol DMRS.

[0062] The terms OCC in this disclosure may be interpreted interchangeably with orthogonal codes, orthogonalization, cyclic shifts, and the like.

[0063] The DMRS type may also be called the DMRS Configuration type.

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

[0065] Both DMRSs 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, while a DMRS mapped additionally to any other position 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, Comb, CS, and TD-OCC may be used for orthogonalization. For example, up to 8 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 orthogonal codes (2-FD-OCC) to two Resource Elements (REs) that are adjacent to each other 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 orthogonal codes (2-FD-OCC) to two frequency-adjacent REs and TD-OCC ({1,1} and {1,-1}) to two time-adjacent REs.

[0070] Furthermore, in Rel.15 NR, multi-port CSI-RS supports up to 32 ports by using methods such as FDM, Time Division Multiplexing (TDM), Frequency Domain OCC, and Time Domain OCC. The same methods as those used for DMRS described above may also be applied to orthogonalize the CSI-RS.

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

[0072] Different CDM groups are orthogonal due to FDM. However, within the same CDM group, channel variations may disrupt the orthogonality of the applied OCC. In this case, receiving signals within the same CDM group at different receiving powers may cause a near-far problem, potentially compromising orthogonality.

[0073] Here, we will explain the TD-OCC / FD-OCC of DMRS in Rel.15 NR. DMRS mapped to a Resource Element (RE) is a DMRS series with FD-OCC parameters (which may also be called series elements, etc.) w f (k') and the TD-OCC parameters (which may also be called sequence elements, etc.) w t It may also be a sequence obtained by multiplying (l') by .

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

[0075] The two Rel.15 DMRS port tables for PDSCH mentioned above (associating antenna port index (number) with parameters) correspond to DMRS configuration types 1 and 2, respectively. Note that 'p' indicates the antenna port number, and 'Δ' indicates the parameter for shifting (offsetting) frequency resources.

[0076] For example, for antenna ports 1000 and 1001, by applying {w f (0), w f (1)} = {+1, +1} and {w f (0), w f (1)} = {+1, -1} respectively, they are orthogonalized using FD-OCC.

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

[0078] For type 1 antenna ports 1000 - 1003 and antenna ports 1004 - 1007, by applying {w t (0), w t (1)} = {+1, +1} and {w t (0), w t (1)} = {+1, -1} respectively, they are orthogonalized using TD-OCC. Therefore, the antenna ports 1000 - 1007 (or 1000 - 1011) corresponding to double-symbol DMRS are orthogonalized using FD-OCC, TD-OCC and FDM.

[0079] For CP-OFDM only, (without increasing the DMRS overhead,) defining more orthogonal DMRS ports for DL / UL MU-MIMO, making the design common between DL and UL DMRS, up to 24 orthogonal DMRS ports, doubling the maximum number of orthogonal DMRS ports for both single-symbol DMRS and double-symbol DMRS for each applicable DMRS setting type, are being considered.

[0080] In Rel.15, the following cases 1 to 4 can be set. [Case 1] Single Symbol DMRS with DMRS Configuration Type 1 The total number of DMRS ports is 2 (by comb / FDM) × 2 (by FD OCC) = 4 ports. [Case 2] Double symbol DMRS with DMRS configuration type 1 The total number of DMRS ports is 2 (by comb / FDM) × 2 (by FD OCC) × 2 (by TD OCC) = 8 ports. [Case 3] Single Symbol DMRS with DMRS Configuration Type 2 The total number of DMRS ports is 3 (by FDM) × 2 (by FD OCC) = 6 ports. [Case 4] Double symbol DMRS with DMRS configuration type 2 The total number of DMRS ports is 3 (by comb) × 2 (by FD OCC) × 2 (by TD OCC) = 12 ports.

[0081] In Rel.18, it is being considered to double the total number of DMRS ports for cases 1, 2, 3, and 4, to 8, 16, 12, and 24, 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> • Introduction of new OCCs with a longer length than existing OCCs (e.g., 4 or 6). Option 1 involves considering factors such as the potential for performance degradation with large delay spreads, potential scheduling limitations, 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 involves considering potential performance degradation at high UE speeds, scheduling limitations (e.g., how frequency hopping is applied), potential limitations on DMRS configuration (e.g., the number of additional DMRSs is limited), and backward compatibility.

[0085] <Option 3> • Increase the number of CDM groups (for example, increase the number of comb / FDM groups). Option 3 considers factors such as the potential for performance degradation when the delay spread is large, and backward compatibility.

[0086] <Option 4> • Reuse symbols for additional DMRS to increase the number of orthogonal DMRS ports. Option 4 raises several points to consider, including the possibility of performance degradation at high UE speeds, potential limitations on DMRS settings (e.g., a limit on the number of additional DMRSs), and backward compatibility.

[0087] <Option 5> • Use of TD-OCC on discontinuous multiple DMRS symbols in combination with FD-OCC / FDM (reusing additional DMRS symbols to improve channel estimation performance). Option 5 involves considering potential performance degradation at high UE speeds, scheduling limitations (e.g., how frequency hopping is applied), potential limitations on DMRS configuration (e.g., the number of additional DMRSs is limited), and backward compatibility.

[0088] In Option 1, the new FD-OCC for DMRS of PDSCH / PUSCH may conform to 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 6RE of DMRS within one PRB in one CDM group. <<Option 1-2>> Within a single CDM group, a new FD-OCC of length 4 is applied to 4REs of DMRS, either within a single PRB or spanning multiple consecutive PRBs.

[0089] In Option 1, the new FD-OCC for PDSCH / PUSCH DMRS applies to DMRS extension type 2, with a length of 4 applied to 4REs of DMRS within one PRB in one CDM group. A new FD-OCC of length 6 may also be supported for DMRS extension type 2.

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

[0091] A new FD-OCC may be any of the following OCCs:

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

[0093] [OCC1-2] An OCC of length 4 based on cyclic shifts. Four sequences can be obtained by using the cyclic shifts {i·0,i·π / 2,i·π,i·3π / 2} with OCC index i={0,1,2,3}.

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

[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 new FD-OCC series may be associated with the Rel.15 DMRS port index.

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

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

[0099] In this disclosure, DMRS configuration type 1, DMRS type 1, DMRS type=1, and DMRS Type 1 may be interpreted interchangeably. In this disclosure, DMRS configuration type 2, DMRS type 2, DMRS type=2, and DMRS Type 2 may be interpreted interchangeably.

[0100] In this disclosure, Extended DMRS configuration type 1, DMRS extension type 1, DMRS extension type=1, DMRS eType 1, and Rel.18 DMRS type 1 may be interpreted interchangeably. In this disclosure, Extended DMRS configuration type 2, DMRS extension type 2, DMRS extension type=2, DMRS eType 2, and Rel.18 DMRS type 2 may be interpreted interchangeably.

[0101] In this disclosure, DMRS maximum length and maxLength may be interpreted as mutually exclusive.

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

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

[0104] For DMRS ports with new FD-OCC#0 and 1 under DMRS extension type 1, the same DMRS port index (DMRS ports 0 to 7) as for Rel.15 DMRS ports may be used. For DMRS ports with new FD-OCC#2 and 3, a different DMRS port index (DMRS ports 8 to 15) than that for Rel.15 DMRS ports may be used.

[0105] For DMRS ports with new FD-OCC#0 and 1 under DMRS extension type 2, the same DMRS port index (DMRS ports 0 to 11) as for Rel.15 DMRS ports may be used. For DMRS ports with new FD-OCC#2 and 3, a different DMRS port index (DMRS ports 12 to 23) than that for Rel.15 DMRS ports may be used.

[0106] (analysis) Conventional waveform settings were performed using Radio Resource Control (RRC), requiring RRC reconfiguration to switch waveforms. This increased signaling overhead and potentially reduced communication throughput. Therefore, as described above, dynamic switching of the conversion precoder for PUSCH (switching via DCI / MAC CE) allows for easy (high-speed) waveform switching. However, in this case, as shown in problems 0-4 below, there are unclear aspects regarding various settings and controls.

[0107] Therefore, the inventors conceived of a terminal that appropriately and dynamically switches between disabling and enabling (switching waveforms) the conversion precoder for PUSCH.

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

[0109] In this disclosure, "A / B" and "at least one of A and B" may be interpreted as mutually exclusive. In this disclosure, "A / B / C" may mean "at least one of A, B, and C".

[0110] In this disclosure, terms such as notice, activate, deactivate, indicate, select, configure, update, and determine may be interpreted interchangeably. In this disclosure, terms such as support, control, controllable, operate, and operable may be interpreted interchangeably.

[0111] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-layer parameters, fields, Information Elements (IE), settings, etc., may be interpreted interchangeably. In this disclosure, Medium Access Control elements (MAC Control Element (CE)), update commands, activation / deactivation commands, etc., may be interpreted interchangeably.

[0112] In this disclosure, the upper-layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, or a combination thereof.

[0113] In this disclosure, MAC signaling may include, for example, MAC Control Elements (MAC CEs) and MAC Protocol Data Units (PDUs). Broadcast information may include, for example, Master Information Blocks (MIBs), System Information Blocks (SIBs), Remaining Minimum System Information (RMSIs), and Other System Information (OSIs).

[0114] In this disclosure, physical layer signaling may include, for example, Downlink Control Information (DCI) and Uplink Control Information (UCI).

[0115] In this disclosure, terms such as index, identifier (ID), indicator, and resource ID may be interpreted interchangeably. In this disclosure, terms such as sequence, list, set, group, cluster, and subset may be interpreted interchangeably.

[0116] In this disclosure, the application / use of CP-OFDM and the disabled status of the transformPrecoder may be interpreted as mutually exclusive. The application / use of DFT-s-OFDM and the enabled status of the transformPrecoder may be interpreted as mutually exclusive. The disabling / enabling of the transformPrecoder, the switching of the transformPrecoder, and the switching of waveforms (CP-OFDM / DFT-s-OFDM) may be interpreted as mutually exclusive. The PUSCH waveform, waveform, and transformPrecoder may be interpreted as mutually exclusive. CP-OFDM and CP-OFDM waveform may be interpreted as mutually exclusive. DFT-s-OFDM and DFT-s-OFDM waveform may be interpreted as mutually exclusive. Enabled and on may be interpreted as mutually exclusive. Disabled and off may be interpreted as mutually exclusive.

[0117] In this disclosure, the phrases "the PUSCH waveform can be dynamically switched," "the PUSCH waveform is set to be dynamically switched," "DWS is set," and "DWS is enabled" may be interpreted as being interchangeable.

[0118] In this disclosure, DMRS type, DMRS type in uplink DMRS configuration (dmrs-Type in DMRS-UplinkConfig), and DMRS configuration type may be interpreted interchangeably. In this disclosure, DMRS type 1, a type that allows DMRS to be placed in 6 REs for 1 RB in a frequency domain, may be interpreted interchangeably. In this disclosure, DMRS type 2, a type that allows DMRS to be placed in 4 REs for 1 RB in a frequency domain, may be interpreted interchangeably.

[0119] In this disclosure, DMRS Type 1 and Enhanced DMRS Type 1 (DMRS-eType1) may be interpreted interchangeably. In this disclosure, DMRS Type 2 and Enhanced DMRS Type 2 (DMRS-eType2) may be interpreted interchangeably. In other words, embodiments applicable to DMRS Types 1 and 2 may also apply to Enhanced DMRS Types 1 and 2.

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

[0121] In this disclosure, the first field, the field for multi-carrier scheduling, and the fields for time domain resource assignment / allocation (TDRA) / frequency domain resource assignment / allocation (FDRA) for multi-carrier scheduling may be interpreted as interchangeable.

[0122] In this disclosure, the terms "second field," "DWS field," "DWS indicator," "DWS indication," and "DWS instruction" may be interpreted as interchangeable.

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

[0124] (Wireless communication method) As described above, the UE may receive a setting indicating that the DCI / MAC CE will dynamically switch between disabling and enabling the conversion precoder for PUSCH. The UE may also receive an instruction from the DCI / MAC CE indicating whether to enable or disable the conversion precoder for PUSCH. In other words, the UE may be able to dynamically switch the PUSCH waveform. In this case, at least one of the processing methods of some of the following embodiments may be applied.

[0125] In this disclosure, if the PUSCH waveform can be dynamically switched, at least one of the methods described above (dynamic switching of disabling and enabling the conversion precoder) may be applied.

[0126] <Problem 0> When the PUSCH waveform can be dynamically switched, it is unclear what values ​​should be set for 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 unrestricted. It is preferable to clarify this because, for example, the setting of the RRC parameter transformPrecoder affects the DCI size, which in turn affects the processing load and communication overhead of the UE.

[0127] <Embodiment 0.1> If the UE can dynamically switch the PUSCH waveform, the RRC parameter transformation precoder (transformPrecoder) may be configured in one of the following ways:

[0128] [Aspect 1] If 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. In other words, the NW (base station, gNB) can set a smaller DCI size, thereby suppressing communication overhead.

[0129] [Aspect 2] If the PUSCH waveform can be dynamically switched, the RRC parameter transformPrecoder may be set to Disabled. This reduces the processing load on the UE because, even when the PUSCH waveform is switched to DFT-s-OFDM, the UE assumes the same DCI size as CP-OFDM.

[0130] [Aspect 3] If the PUSCH waveform can be dynamically switched, the RRC parameter transformPrecoder may be ignored. In other words, there may be no limitations on transformPrecoder.

[0131] Figure 3 is a flowchart showing an example of the processing in Embodiment 0.1. When the UE receives a setting indicating that the PUSCH waveform is dynamically switchable (step S101), it receives the RRC parameter transformPrecoder, which has been set to enable / disable (step S102).

[0132] Although multiple transformPrecoders exist as RRC parameters, the transformPrecoder referenced by the UE may differ for each case (each timing). For example, options 1 and 2 below may be applied. The processing of options 1 and 2 below may also be applied at the timing before the dynamic switching instruction for the PUSCH waveform is given, if dynamic switching of the PUSCH waveform is set.

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

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

[0135] According to this embodiment, when it is possible to dynamically switch the PUSCH waveform, the set value for the RRC parameter transformPrecoder and the operation of the UE can be clearly defined.

[0136] <Embodiment 0.2> If the UE can dynamically switch the PUSCH waveform, the UE may receive a value / setting based on one of the following modes / options as the maximum rank (maxRank) of the RRC parameter. In other words, the UE may assume that one of the following modes / options is applied to the value / setting of maxRank. maxRank is a parameter that indicates the maximum transmit rank (layer) of the UL (PUSCH). The UE controls the transmission of the PUSCH based on maxRank.

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

[0138] [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 the specifications, for example. Alternatively, the specific value may be set / indicated by RRC / MAC CE / DCI. For example, if dynamic switching of the PUSCH waveform is set, maxRank (the specific value) may be 1.

[0139] If maxRank is limited, for example, if maxRank can only be set to 1, the bit width of the Transmitted Precoding Matrix Indicator (TPMI) will be the same regardless of the PUSCH waveform. In other words, the DCI size will be the same, which can reduce the processing load on the UE.

[0140] Figure 4 is a flowchart showing an example of the processing in Embodiment 0.2. Figure 4 shows an example of Embodiment 2 described above. When the UE receives a setting indicating that the PUSCH waveform is dynamically switchable (step S201), it receives a setting indicating a specific value or a value smaller than the specific value as the value of the RRC parameter maxRank (step S202).

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

[0142] <Problem 1> When the PUSCH waveform can be dynamically switched, it is unclear how to handle DCI fields, which may be present (1 or more bits) or absent (0 bits) depending on the PUSCH waveform. These DCI fields include, for example, the PTRS-DMRS association and DMRS sequence initialization.

[0143] Figure 5 shows the definitions of the PTRS-DMRS association and DMRS sequence initialization in the DCI field. As shown in Figure 5, the DMRS sequence initialization is 0 bits when PTRS (PTRS-UplinkConfig) is not set and CP-OFDM is applied (transform precoder is disabled), when DFTS-OFDM is applied (if transform precoder is enabled), or when maxRank=1, and 2 bits otherwise. The DMRS sequence initialization is 0 bits when DFTS-OFDM is applied, and 1 bit when CP-OFDM is applied.

[0144] <Embodiment 1> If the PUSCH waveform is dynamically switchable and a specific waveform is instructed to the PUSCH, the UE may process (assume) certain fields of the PUSCH's scheduling DCI based on certain rules.

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

[0146] Certain rules may include the UE ignoring specific fields in the DCI.

[0147] The specific waveform may be DFT-s-OFDM or CP-OFDM.

[0148] For example, if the UE receives a DCI and the PUSCH waveform is dynamically switchable, and PUSCH is instructed to use DFT-s-OFDM, it will ignore at least one of the DCI's DMRS sequence initialization field and PTRS-DMRS association field.

[0149] The UE may ignore the DMRS sequence initialization field or the PTRS-DMRS association field in Figure 5 if the conditions for the DMRS sequence initialization field or PTRS-DMRS association field to be 0 bits are met, even if the UE is not limited to the examples above. This can reduce the processing load on the UE.

[0150] In Embodiment 1, when the PUSCH waveform is dynamically switched, the number of bits per DCI field / total DCI size may follow the rules for CP-OFDM, regardless of the exact waveform used by the UE. Alternatively, the number of bits per DCI field / total DCI size may not follow the rules for CP-OFDM.

[0151] <Problem 2> As explained above (FDRA type), type 0 RA cannot be used for DFT-s-OFDM; therefore, if the PUSCH waveform switches to DFT-s-OFDM, type 1 or type 2 must be used. For example, it is preferable that the RRC parameter indicating the PUSCH waveform always corresponds to the FDRA type setting / indication. However, when the PUSCH waveform is dynamically switched, the settings for FDRA and the interlace usage indication (useInterlacePUCCH-PUSCH) are unclear.

[0152] <Embodiment 2> If the PUSCH waveform is dynamically switchable and a specific waveform is instructed to PUSCH, the UE may receive specific fields of the DCI and specific RRC parameters corresponding to the PUSCH scheduling based on specific rules (it may be assumed that the UE will receive the specific fields of the DCI and specific RRC parameters). The UE may control the PUSCH transmission based on the received specific fields of the DCI and specific RRC parameters.

[0153] A specific field in DCI may be either FDRA or a frequency hopping flag.

[0154] The specific RRC parameter may be resource allocation or useInterlacePUCCH-PUSCH.

[0155] The specific waveform may be DFT-s-OFDM or CP-OFDM.

[0156] The specific rule may be that resourceAllocation is either resourceAllocationType1 or dynamicSwitch. If resourceAllocation is dynamicSwitch, the most significant bit (MSB) of the FDRA must be "1", that is, FDRA type 1 must be indicated. This specific rule may apply if useInterlacePUCCH-PUSCH is not set.

[0157] A specific rule may also be that resourceAllocation is resourceAllocationType1.

[0158] A specific rule may stipulate that the frequency hopping flag is determined according to at least one of resource allocation and FDRA based on the specific rule described above.

[0159] Certain rules may also require that useInterlacePUCCH-PUSCH (use of interlacing for PUCCH and PUSCH) be enabled (use of interlacing for PUCCH and PUSCH).

[0160] [Specific example] For example, if the PUSCH waveform is dynamically switchable and DFT-s-OFDM is instructed for PUSCH, the UE may receive (or is expected to receive) configuration information (RRC parameters) indicating dynamic switching as resource allocation and instruction information (DCI) indicating type 1 as FDRA. The UE may control PUSCH transmission based on this configuration information and instruction information.

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

[0162] The UE may receive (or expect to receive) configuration information indicating that useInterlacePUCCH-PUSCH (use of interlacing for PUCCH and PUSCH) is enabled, for example, if the PUSCH waveform is dynamically switchable and DFT-s-OFDM is instructed for PUSCH. The UE may control PUSCH transmission based on this configuration information.

[0163] Figure 6 shows an example of the setting patterns for useInterlacePUCCH-PUSCH, resourceAllocation, and RA type. If dynamic waveform switching is possible, the following (1) and (2) may be applied to the setting patterns shown in Figure 6. (1) If the default value of transformPrecoder is invalid (CP-OFDM is specified / used), the UE can expect any pattern, but if it is valid (DFT-s-OFDM is specified / used), patterns 1-1 and 1-3 may not be applicable. (2) If the default value of transformPrecoder is enabled, the UE may expect patterns other than patterns 1-1 and 1-3 which apply DCI indicating type 0, but may expect any pattern if CP-OFDM is indicated / used.

[0164] The processing in this embodiment may be applied independently of the waveform instructed to PUSCH. That is, if the PUSCH waveform is dynamically switchable, the UE may control the above-mentioned specific fields of the DCI and the above-mentioned specific RRC parameters corresponding to the scheduling of PUSCH based on the above-mentioned specific rules.

[0165] According to this embodiment, even when the PUSCH waveform is dynamically switched, it is possible to avoid cases that result in errors (for example, when DFT-s-OFDM is applied, a type 0 FDRA is set).

[0166] <Problem 3> When the PUSCH waveform is dynamically switchable, the applicable types of PUSCH are unclear. For example, it is unclear whether message 3 (Msg3) / message A (msg3-TransformPrecoder / msgA-TransformPrecoder) can be applied as such a PUSCH. Also, it is unclear whether CG-PUSCH (ConfiguredGrantConfig's transformPrecoder) can be applied as such a PUSCH. Furthermore, if these PUSCHs support dynamic switching of the PUSCH waveform, it is unclear what processing will be performed.

[0167] <Embodiment 3> The UE may apply dynamic switching of PUSCH waveforms to only specific types of PUSCH. That is, if the UE receives a setting indicating that PUSCH waveforms should be dynamically switched, it may control only specific types of PUSCH to be dynamically switched based on DCI / MAC CE. Specific types of PUSCH may be, for example, at least one of (1) to (4) below.

[0168] (1) DCI Grant (DG) - PUSCH (PUSCH scheduled by DCI). (2) Type 1 configured grant (CG) - PUSCH (PUSCH transmission configured by upper layer signaling). (3) Type 2 CG-PUSCH (PUSCH transmission configured by upper-layer signaling and activated / deactivated by DCI). (4) A PUSCH scheduled by a Random Access Response (RAR) (Message 3 PUSCH or Message A PUSCH). This RAR may 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 state, so it can adjust the waveform appropriately.

[0169] Figure 7 is a flowchart showing an example of the processing in Embodiment 3. When the UE receives a setting indicating that the PUSCH waveform is dynamically switchable (step S301), it controls the system to dynamically switch only the waveforms of a specific type of PUSCH based on the DCI / MAC CE (step S302).

[0170] <Embodiment 4.1> Dynamic switching of Type 1 CG-PUSCH (PUSCH transmission configured by upper-layer signaling) waveforms is applied, and at least one of the following methods (1-1) to (1-4) may be supported. As a specific method of (1-1) to (1-4) below, the method described above (dynamic switching of disabling and enabling the conversion precoder) may be applied.

[0171] (1-1) The UE may receive explicit instructions from DCI indicating whether transformPrecoder is enabled or disabled (DFT-s-OFDM / CP-OFDM) (explicit signaling). (1-2) The UE may receive implicit instructions from DCI indicating whether transformPrecoder is enabled or disabled (DFT-s-OFDM / CP-OFDM) (implicit signaling). (1-3) The UE may receive explicit instructions from the MAC CE indicating whether the transformPrecoder is enabled or disabled (DFT-s-OFDM / CP-OFDM) (explicit signaling). (1-4) The UE may receive implicit instructions from the MAC CE indicating whether the transformPrecoder is enabled or disabled (DFT-s-OFDM / CP-OFDM) (implicit signaling).

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

[0173] Conventional Type 1 CG-PUSCH does not use DCI for scheduling. Therefore, when (1-1) and (1-2) above apply, it is preferable to define a new DCI. For example, either (2-1) or (2-2) below may be applied as the DCI for (1-1) and (1-2) above.

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

[0175] According to this embodiment, the processing when dynamic switching of type 1 CG-PUSCH waveforms is applied can be clarified.

[0176] <Embodiment 4.2> Dynamic switching of Type 2 CG-PUSCH (PUSCH transmission configured by upper-layer signaling and activated / deactivated by DCI) waveforms may be applied, and at least one of the methods (1-1) to (1-4) of Embodiment 4.1 may be supported.

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

[0178] Conventional Type 2 CG-PUSCHs use a DCI for activation / deactivation, and that DCI may be reused. Specifically, either of the following (2-1) or (2-2) may be applied as the DCI in (1-1) and (1-2) above.

[0179] (2-1) A DCI that schedules UL / DL unicast data may be applied. Note that the UL / DL-SCH that the DCI actually schedules does not have to exist. For example, a DCI that performs activation / deactivation of a type 2 CG-PUSCH may be applied. (2-2) A DCI may be applied for scheduling other than unicast data. For example, this DCI may be applied when using a group common DCI.

[0180] According to this embodiment, the processing when dynamic switching of type 2 CG-PUSCH waveforms is applied can be clarified.

[0181] <Embodiment 5> Dynamic switching of the Message 3 / Message A PUSCH (PUSCH scheduled by Random Access Response (RAR)) waveform is applied, and at least one of the methods (1-1) to (1-4) of Embodiment 4.1 may be supported. Alternatively, (1-5) below may be applied.

[0182] (1-5) The UE may receive explicit or implicit instructions from the RAR indicating whether the transformPrecoder is enabled or disabled (DFT-s-OFDM / CP-OFDM).

[0183] Methods (1-1) to (1-5) may be applied to message 3 / message A PUSCH separately from other types of PUSCH (type 1 / type 2 CG-PUSCH, DG-PUSCH). Alternatively, methods (1-1) to (1-5) may be applied to message 3 / message A PUSCH in the same way as methods for other types of PUSCH.

[0184] Since the conventional Message 3 / Message A PUSCH uses a DCI for activation / deactivation, that DCI may be reused. Specifically, either (2-1) or (2-2) below may be applied as the DCI in (1-1) and (1-2) above.

[0185] (2-1) A DCI may be applied to schedule UL / DL unicast data. Note that the UL / DL-SCH that the DCI actually schedules does not have to exist. For example, the DCI may be DCI 1_0 which has a Cyclic Redundancy Check (CRC) that is scrambled by an RA Radio Network Temporary Identifier (RNTI) or message B RNTI. (2-2) A DCI may be applied for scheduling other than unicast data. For example, this DCI may be applied when using a group common DCI.

[0186] With regard to dynamic waveform switching for message 3 / message A PUSCH, at least one of the following (3-1) and (3-2) regarding RAR-based instructions may be supported. The UE may dynamically switch the waveform of message 3 PUSCH or message A PUSCH based on at least one of the MAC subheader or MAC payload for RAR.

[0187] (3-1) Reserved bits (R) in the MAC subheader / MAC payload for RAR may be released and used for dynamic waveform switching. For example, the "R" in the first octet of the MAC payload shown in Figure 8 (i.e., next to the Timing Advance Command) may indicate dynamic waveform switching. (3-2) It may be implicitly indicated based on the existing RAR grant field (UL Grant) shown in Figure 9. For example, if the Modulation and Coding Scheme (MCS) in the UL Grant indicates a specific MCS, transformPrecoder may be enabled or disabled for message 3 / message A PUSCH. For example, transformPrecoder may be enabled or disabled for message 3 / message A PUSCH if the value corresponding to the TPC command for message 3PUSCH in the UL Grant (Figures 9 and 10) is a specific value or is greater than / less than a specific threshold.

[0188] The transformPrecoder may be enabled or disabled for message 3 / message A PUSCH if the Backoff Parameter value (Figure 11) corresponding to the Backoff Indicator (BI) field in the MAC subheader for RAR is a specific value or greater than / less than a specific threshold. Alternatively, the transformPrecoder may be enabled or disabled for message 3 / message A PUSCH if the Extension (E), Type (T), or Random Access Preamble IDentifier (RAPID) fields in the MAC subheader for RAR are specific values.

[0189] This embodiment may be applied when certain conditions are met. These conditions may include the PRACH that triggers the RAR being sent on a specific RA resource based on the RACH resource partition configuration.

[0190] According to this embodiment, the processing when dynamic switching of the message 3 / message A PUSCH waveform is applied can be clarified. Furthermore, when using RAR-based instructions for dynamic waveform switching of message 3 / message A PUSCH, the existing MAC subheader / payload can be used, thus suppressing an increase in communication overhead.

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

[0192] If dynamic waveform switching is supported, DCI can initiate the switching between CP-OFDM and DFT-S-OFDM waveforms.

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

[0194] However, while DMRS type 2 cannot be set for DFT-S-OFDM in existing systems, there are cases where DMRS type 2 is set for DFT-S-OFDM if dynamic waveform switching is set / supported. This is because DCI instructions (e.g., waveform switching) are performed more dynamically than RRC setting changes (DMRS type settings).

[0195] Thus, it is unclear how to configure the PUSCH DMRS type when dynamic waveform switching is supported.

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

[0197] For example, if 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) / DMRS type set by the DCI / RRC. This can suppress the increase in the number of {waveform, DMRS type} combinations that the UE needs to consider in push transmissions. As a result, the increase in implementation limitations for the UE can be suppressed.

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

[0199] [Option 6-1] If dynamic waveform switching is configured, only Type 1 may be set as the DMRS type (dmrs-Type) (see Figure 13).

[0200] When dynamic waveform switching is configured, the base station may be controlled to set only Type 1 as the DMRS type for PUSCH to UE. In other words, when dynamic waveform switching is configured, setting DMRS Type 2 by RRC may be restricted / prohibited.

[0201] In this case, DMRS type 1 may be applied regardless of the waveform indicated by DCI (CP-OFDM or DFT-S-OFDM). The UE may control the system to apply DMRS type 1 to both waveforms (CP-OFDM and DFT-S-OFDM) if dynamic waveform switching is enabled. The UE may also assume / expect / determine that DMRS type 1 is enabled for PUSCH DMRS if dynamic waveform switching is enabled.

[0202] If dynamic waveform switching is enabled, setting the DMRS type of PUSCH via RRC may be omitted.

[0203] In this way, by setting only specific DMRS types, it is possible to suppress the increase in the number of {waveform, DMRS type} combinations that the UE needs to anticipate during push transmission. As a result, the increase in implementation limitations for the UE can be suppressed.

[0204] [Option 6-2] When dynamic waveform switching is configured, DMRS type 1 and DMRS type 2 settings may be supported / allowed as DMRS types (see Figure 13).

[0205] When dynamic waveform switching is configured, the base station may be controlled to set the UE to DMRS type 1 or DMRS type 2 as the DMRS type for PUSCH. In other words, when dynamic waveform switching is configured, setting DMRS type 2 by RRC may be permitted.

[0206] If DMRS type 2 is set and dynamic waveform switching is set, the UE may interpret the DMRS type of the pusher (e.g., dmrs-Type) as being set to type 1. In other words, the UE may ignore the DMRS type 2 setting and apply DMRS type 1.

[0207] Thus, when dynamic waveform switching is configured, DMRS type 1 may be applied regardless of the DMRS type set in RRC.

[0208] In this way, by specifying a particular DMRS type to apply, it is possible to suppress the increase in the number of {waveform, DMRS type} combinations that the UE needs to consider during push transmission. As a result, the increase in implementation limitations for the UE can be suppressed.

[0209] <Embodiment 7> If dynamic waveform switching (DWS) is configured, the DMRS type to be applied for PUSCH DMRS may be determined based on the waveform indicated by DCI.

[0210] For example, if dynamic waveform switching is configured, the UE may determine the applicable DMRS type based on the DMRS type set by the waveform (CP-OFDM or DFT-S-OFDM) / RRC indicated by DCI.

[0211] If 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 same DCI used for scheduling the PUSCH.

[0212] [Option 7-1] If dynamic waveform switching is enabled and DCI indicates DFT-S-OFDM, only Type 1 may be applied / set as the DMRS type.

[0213] When dynamic waveform switching is configured, the base station may be controlled to set only Type 1 as the DMRS type for PUSCH to UE. In other words, when dynamic waveform switching is configured, setting DMRS Type 2 by RRC may be restricted / prohibited.

[0214] In this case, DMRS type 1 may be applied regardless of the waveform indicated by DCI (CP-OFDM or DFT-S-OFDM). The UE may control the system to apply DMRS type 1 to both waveforms (CP-OFDM and DFT-S-OFDM) if dynamic waveform switching is enabled. The UE may also assume / expect / determine that DMRS type 1 is enabled for PUSCH DMRS if dynamic waveform switching is enabled.

[0215] If dynamic waveform switching is enabled, setting the DMRS type of PUSCH via RRC may be omitted.

[0216] In this way, by setting only specific DMRS types, it is possible to suppress the increase in the number of {waveform, DMRS type} combinations that the UE needs to anticipate during push transmission. As a result, the increase in implementation limitations for the UE can be suppressed.

[0217] [Option 7-2] When dynamic waveform switching is enabled and DCI indicates DFT-S-OFDM, the following DMRS types may be supported / allowed: DMRS type 1 and DMRS type 2.

[0218] When dynamic waveform switching is configured, the base station may be controlled to set the UE to DMRS type 1 or DMRS type 2 as the DMRS type for PUSCH. In other words, when dynamic waveform switching is configured, setting DMRS type 2 by RRC may be permitted.

[0219] If DMRS type 2 is set, dynamic waveform switching is set, and DFT-S-OFDM is indicated by DCI, the UE may interpret the DMRS type of PUSCH (e.g., dmrs-Type) as being set to type 1. In other words, if DFT-S-OFDM is indicated by DCI, the UE may ignore the DMRS type 2 setting and apply DMRS type 1.

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

[0221] Thus, when dynamic waveform switching is set and DMRS type 2 is set in RRC, the decision on whether or not to apply DMRS type 2 may be made based on the waveform indicated by DCI. Furthermore, when dynamic waveform switching is set and DMRS type 1 is set in RRC, control may be made to apply DMRS type 1 regardless of the waveform indicated by DCI.

[0222] This allows DMRS type 2 to be applied when CP-OFDM is indicated by DCI, enabling flexible control of the applied DMRS type depending on the waveform.

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

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

[0225] [Option 8-1] The bit width of the antenna port field (e.g., bitwidth) is determined considering that dmrs-Type is DMRS type 2 (i.e., according to the dmrs-Type setting), however, the UE may interpret the indications from the antenna port field by interpreting only a portion of the bits (or using only some of the bits).

[0226] The number of some bits may be the same as the number of antenna port fields (or number of bits / number of code points) that Type 2 sets for dmrs-Type 1. In this disclosure, some bits may be interpreted as some DCI code points.

[0227] In this case, the determination of the bit width of the DCI antenna port field and the interpretation of the said antenna port field may differ. That is, the bit width / number of code points of the DCI antenna port field may be determined based on DMRS Type 2, while the interpretation of the DCI antenna port field may be based on DMRS Type 1.

[0228] Some of the DCI code points may be the same as the number of antenna port fields (or number of bits / number of code points) that Type 2 sets for dmrs-Type 1.

[0229] This allows the UE to properly interpret the DCI antenna port field even when DMRS Type 1 is applied in cases where DMRS Type 2 is configured.

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

[0231] In this case, the determination of the bit width of the DCI antenna port field and the interpretation of the said antenna port field may be the same. That is, the bit width of the DCI antenna port field may be determined based on DMRS type 1, and the interpretation of the DCI antenna port field may also be performed assuming DMRS type 1.

[0232] This allows DMRS Type 1 to be applied when DMRS Type 2 is configured, enabling both the bit width and interpretation of the antenna port field to be assumed to be DMRS Type 1. Furthermore, it helps to suppress the increase in antenna port field overhead.

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

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

[0235] [Option 9-1] The bit width of the antenna port field (e.g., bitwidth) is determined considering that dmrs-Type is DMRS type 2 (i.e., according to the dmrs-Type setting), however, the UE may interpret the indications from the antenna port field by interpreting only a portion of the bits (or using only some of the bits).

[0236] The number of some bits may be the same as the number of antenna port fields (or number of bits / number of code points) that Type 2 sets for dmrs-Type 1. In this disclosure, some bits may be interpreted as some DCI code points.

[0237] In this case, the determination of the bit width of the DCI antenna port field and the interpretation of the said antenna port field may differ. That is, the bit width of the DCI antenna port field may be determined based on DMRS type 2, while the interpretation of the DCI antenna port field may be based on DMRS type 1.

[0238] Some of the DCI code points may be the same as the number of antenna port fields (or number of bits / number of code points) that Type 2 sets for dmrs-Type 1.

[0239] Thus, in a case where DMRS type 2 is set and DFT-S-OFDM is indicated by DCI, even when DMRS type 1 is applied, the UE can appropriately interpret the antenna port field of the DCI.

[0240] Note that in a case where DMRS type 2 is set and CP-OFDM is indicated by DCI, the determination of the bit width of the antenna port field of the DCI and the interpretation of the antenna port field may be performed based on DMRS type 2.

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

[0242] 《Example of Antenna Port Field 1》 When DFT-S-OFDM is indicated by the DCI that schedules 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, only the 2 least significant bits (LSBs) may be interpreted (see FIG. 14A).

[0243] When DFT-S-OFDM is not indicated by the DCI that schedules PUSCH (e.g., when 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 (e.g., dmrs-Type). For example, all 3 bits may be used for interpretation.

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

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

[0246] Thus, when dynamic waveform switching is configured, push-directed DMRS transmission can be properly performed by flexibly controlling the determination / interpretation of the bit width of the DCI antenna port field based on the waveform indicated by the DCI.

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

[0248] In this case, the determination of the bit width of the DCI antenna port field and the interpretation of the said antenna port field may be the same. That is, the bit width of the DCI antenna port field may be determined based on DMRS type 1, and the interpretation of the DCI antenna port field may also be performed assuming DMRS type 1.

[0249] This allows for the assumption of DMRS Type 1 for both the bit width and interpretation of the antenna port field in cases where DMRS Type 2 is configured and DCI indicates DFT-S-OFDM (for example, when applying DMRS Type 1). It also helps to suppress the increase in antenna port field overhead.

[0250] <Analysis A1> It is being considered that DWS will not be supported in Type 1 and Type 2 configured grant (CG) pushes, but will only be supported in dynamic grants (DG).

[0251] The UE does not expect the bit width of a field in DCI format 0_1 ​​with CRC scrambled by CS-RNTI to be greater 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, several 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 becomes 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.

[0252] In the size alignment of DCI format 0_1 ​​with CRC scrambled by C-RNTI or CS-RNTI, the following constraints are met: - The bit width (size) of any field in DCI format 0_1 ​​(using C-RNTI) with a CRC scrambled by C-RNTI is greater than or equal to the bit width of that field in DCI format 0_1 ​​(using CS-RNTI) with a 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), then 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 that field with zeros.

[0253] There are separate DMRS settings for DG-PUSCH and CG-PUSCH. The PUSCH settings (DG-PUSCH, PUSCH-Config) may include the uplink DMRS settings (DMRS-UplinkConfig) for dmrs-UplinkForPUSCH-MappingTypeA / dmrs-UplinkForPUSCH-MappingTypeB. The CG-PUSCH settings (ConfiguredGranConfig) may include the uplink DMRS settings (DMRS-UplinkConfig) for cg-DMRS-Configuration.

[0254] The DMRS setting affects the DCI field size. When DMRS type 2 is set, the antenna port field size is 1 bit larger than when DMRS type 1 is set. For example, if the conversion precoder is disabled, DMRS type is 1, and DMRS maximum length is 1, the antenna port field size is 3 bits. If the conversion precoder is disabled, DMRS type is 1, and DMRS maximum length is 2, the antenna port field size is 4 bits. On the other hand, if the conversion precoder is disabled, DMRS type is 2, and DMRS maximum length is 1, the antenna port field size is 4 bits. If the conversion precoder is disabled, DMRS type is 2, and DMRS maximum length is 2, the antenna port field size is 5 bits.

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

[0256] In DG-PUSCH, if DWS is configured, the scheduling DCI carries a new bit to indicate waveform switching. The configurability issues of DMRS type 2 are addressed in Problem 1 and Embodiment 1.

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

[0258] Type 2CG Activation DCI (Type 2CG-PUSCH Activation DCI) and DG-DCI (DG-PUSCH Scheduling DCI) share the same DCI format with the same size. The size of any field in DG-DCI is greater than or equal to the size of that field in Type 2CG-PUSCH Activation DCI.

[0259] When DWS is configured for DG-PUSCH, the following are some possible DMRS settings for Type 2CG-PUSCH: - Case 1: If DWS is configured and DMRS type 1 is configured, it becomes a problem whether there are restrictions on the DMRS type of CG-PUSCH. - Case 2: If DWS is configured and DMRS type 2 is configured, it becomes a problem whether there are restrictions on the DMRS type of CG-PUSCH.

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

[0261] When DWS is configured, DMRS type 1 may be configured for both DG-PUSCH and CG-PUSCH. According to this configuration, complex UE operations are not required for the interpretation of the DMRS type and the determination of the DCI size for DG and CG activations.

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

[0263] FIG. 15 shows an example of an RRC IE according to Embodiment A1. In this example, the UE receives the configuration of DWS, dmrs-Type=1 in PUSCH-Config, and dmrs-Type=1 in ConfiguredGrantConfig.

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

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

[0266] 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. This configuration eliminates the need for the UE to read the DWS bit to recognize the size of the type 2 CG-PUSCH activation DCI. It also allows for more flexible DMRS configuration for DG-PUSCH.

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

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

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

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

[0271] - Embodiment 3-1 If the DWS field indicates DFT-s-OFDM and DMRS type 2 is set for DG-PUSCH, the UE may interpret the DMRS setting as DMRS type 1. This behavior allows the UE to follow existing implementations for DMRS, i.e., DMRS type 2 may be set only for CP-OFDM. This behavior may also be according to Embodiment 7.

[0272] - Embodiment 3-2 If the DWS field in the DCI used to activate / deactivate a Type 2 CG-PUSCH indicates DFT-s-OFDM, and DMRS Type 2 is set for the CG-PUSCH, the UE may interpret the DMRS setting as DMRS Type 1. This behavior allows for flexibility in DMRS settings while maintaining the same DCI size for DG and CG-PUSCH activations.

[0273] If the DWS indicator in DCI that activates / deactivates type 2CG-PUSCH indicates a conversion precoding, the UE may interpret this as dmrs-Type in ConfiguredGrantConfig being equal to 1.

[0274] The following actions may be specified. -- The UE does not expect the DWS indicator in the Type 2CG-PUSCH activation / deactivation DCI to indicate that the conversion precoding is enabled.

[0275] <Problem A2> As mentioned above, the specification does not take into account DCI fields that have a non-zero bit width in DCI with CRC scrambled by CS-RNTI, and that have a zero bit width in DCI with CRC scrambled by C-RNTI.

[0276] Future specifications may define new DCI fields with the following characteristics: - If the conversion precoder is disabled, its bit width is zero, and, - If a conversion precoder is enabled, its bit width is non-zero.

[0277] The following situations are error cases and may be explicitly avoided. - The new DCI field is set for both DG-PUSCH and CG-PUSCH, and, - The conversion precoder is ineffective for DG-PUSCH, and, - The conversion precoder is effective for CG-PUSCH.

[0278] <Problem A3> In addition to issue A2, the DCI field size may differ based on the DWS indicator. Error cases related to issue A2 may occur depending on the DWS indicator.

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

[0280] In this disclosure, the DCI field that exists only in the scheduling of PUSCH with DFT-s-OFDM, the DCI field that is 0 bits when the conversion precoder is disabled and X (X>0) bits otherwise, the DCI field whose bit width for DFT-s-OFDM is non-zero and whose bit width for CP-OFDM is zero, the novel DCI field, and the specific DCI field may be interpreted as mutually exclusive.

[0281] In the example in Figure 16, the DCI for scheduling PUSCH with DFT-s-OFDM includes a specific DCI field, while the DCI for scheduling PUSCH with CP-OFDM does not include a specific DCI field.

[0282] If a DCI field exists only in the scheduling of a PUSCH with DFT-s-OFDM, the conversion precoder settings for DG-PUSCH and the conversion precoder settings for CG-PUSCH may be the same. With this setting, the field size is the same between DG-PUSCH and CG-PUSCH, so no additional DCI size alignment rules are required.

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

[0284] If a DCI field is configured only for scheduling with DFT-s-OFDM, the conversion precoder for CG-PUSCH may be disabled. This configuration eliminates the need for additional DCI size alignment rules because the field size is the same between DG-PUSCH and CG-PUSCH.

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

[0286] If a DCI field exists only in the scheduling of a PUSCH with DFT-s-OFDM, that field does not need to exist in the DCI with CRC scrambled by CS-RNTI. With this setting, the size of the field is the same between DG-PUSCH and CG-PUSCH, so no additional DCI size alignment rules are required.

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

[0288] If a DCI field exists only in the scheduling of a PUSCH with DFT-s-OFDM, and the conversion precoder for DG-PUSCH is disabled, and the conversion precoder for CG-PUSCH is enabled, then the bit width of that field may be matched between DG-PUSCH and CG-PUSCH based on certain rules.

[0289] That specific rule may follow at least one of the following rules: - The size of the field is adjusted to match the larger of the size for DG-PUSCH and the size for CG-PUSCH. For example, the MSB of a field with a smaller size may be padded with bits that have the value '0'. - The size of the field is adjusted to the smaller of the size for DG-PUSCH and the size for CG-PUSCH. For example, the number of code points corresponding to the larger size may be reduced to less than or equal to the number of code points in the field having the smaller size by narrowing the range of code points, reducing the maximum value, increasing the minimum value, or decimating the code points. For example, the number of code points corresponding to the larger size may be reduced, similar to Embodiment 9 (Option 9-1). - The size of that field is adjusted to match the size of that field in the DCI (DG-PUSCH scheduling DCI) with the CRC that is scrambled by C-RNTI. - The size of that field is adjusted to match the size of that field in the DCI (DCI for CG-PUSCH activation / deactivation) with the CRC scrambled by CS-RNTI.

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

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

[0292] The DCI field, which exists only in PUSCH scheduling with DFT-s-OFDM, and the DWS do not need to be set simultaneously.

[0293] The following behaviors may be specified in the specifications. - The UE does not expect the DCI field, which exists only in PUSCH scheduling with DFT-s-OFDM, and the DWS to be set simultaneously.

[0294] This configuration simplifies the DCI size alignment rules.

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

[0296] If the DCI field, which exists only in the scheduling of PUSCH with DFT-s-OFDM, and DWS are set simultaneously, the conversion precoder may be disabled for CG-PUSCH.

[0297] This configuration simplifies the DCI size alignment rules.

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

[0299] When the DCI field, which exists only in PUSCH scheduling with DFT-s-OFDM, and the DWS are set simultaneously, at least one of the following constraints may apply.

[0300] - The DWS indicator may show only CP-OFDM. The DWS indicator does not have to show DFT-s-OFDM. The following behavior may be specified in the specification. -- UE does not expect the DWS indicator to show that the conversion precoder is enabled.

[0301] - The DWS indicator may display the same waveform as the waveform set for CG-PUSCH. The DWS indicator does not have to display a different waveform than the waveform set for CG-PUSCH. The following behavior may be specified in the specification. -- The UE does not expect the DWS indicator to indicate something different from the conversion precoder setting in the configuration grant setting.

[0302] This configuration simplifies the DCI size alignment rules.

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

[0304] When the DCI field, which exists only in the scheduling of a PUSCH with DFT-s-OFDM, and the DWS are set simultaneously, the bit width of the field may be matched between DG-PUSCH and CG-PUSCH based on certain rules.

[0305] That specific rule may follow at least one of the following rules: - The size of the field is adjusted to match the larger of the size for DG-PUSCH and the size for CG-PUSCH. For example, the MSB of a field with a smaller size may be padded with bits that have the value '0'. - The size of the field is adjusted to the smaller of the size for DG-PUSCH and the size for CG-PUSCH. For example, the number of code points corresponding to the larger size may be reduced to less than or equal to the number of code points in the field having the smaller size by narrowing the range of code points, reducing the maximum value, increasing the minimum value, or decimating the code points. For example, the number of code points corresponding to the larger size may be reduced, similar to Embodiment 9 (Option 9-1). - The size of that field is adjusted to match the size of that field in the DCI (DG-PUSCH scheduling DCI) with the CRC that is scrambled by C-RNTI. - The size of that field is adjusted to match the size of that field in the DCI (DCI for CG-PUSCH activation / deactivation) with the CRC scrambled by CS-RNTI.

[0306] This operation allows for flexible configuration / instruction of the conversion precoder, as well as DCI fields for DG-PUSCH and CG-PUSCH.

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

[0308] The DCI format may be at least one of the following: - DCI format 0_X for scheduling multiple pushes across multiple CCs. - DCI format 1_X for scheduling multiple PDSCHs across multiple CCs.

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

[0310] - Type 1 -- Type 1A: A single field within a single DCI format. It directs information common to all multiple CCs (all co-scheduled multiple CCs). Figure 17A shows an example of a Type 1A DCI format 0_X for scheduling a PUSCH. A Type 1A DCI format 1_X for scheduling a PDSCH may be similar to this example. -- Type 1B: A single field within a single DCI format. It directs different information to different CCs via joint instructions (directing separate information to each of multiple CCs that are jointly scheduled). Figure 17B shows an example of a Type 1B DCI format 0_X for scheduling a PUSCH. A Type 1B DCI format 1_X for scheduling a PDSCH may be similar to this example. -- Type 1C: A single field within a single DCI format. It directs information to only one of multiple CCs that are jointly scheduled. Figure 18A shows an example of a Type 1C DCI format 0_X for scheduling a PUSCH. A Type 1C DCI format 1_X for scheduling a PDSCH may be similar to this example.

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

[0312] - Type 3: Depends on explicit settings and can be common to multiple co-scheduled CCs, individual to each of the multiple co-scheduled CCs, or individual to each subgroup. For example, either Type 1A or Type 2 may be set. One subgroup contains a subset of multiple co-scheduled cells, where a single field applies in common to the co-scheduled cells belonging to the same subgroup.

[0313] <Analysis B1> The following several problems are possible. - Q1: Is the DWS specified within DCI format 0_X supported? - Q2: If DWS indicated within DCI format 0_X is supported, how many bits are indicated for the purpose of DWS within DCI format 0_X? - Q3: If DWS is supported as indicated within DCI format 0_X, how are RRC settings affected by the exact waveform handled? RRC settings include, for example, conversion precoder, maximum rank, FDRA type, DMRS type, etc.

[0314] In DCI size alignment, primarily for DCI format 0_1, the antenna port, TPMI, DMRS-PTRS association, DMRS sequence initialization, and frequency hopping flag may conform to at least one of embodiments 0 to 6, and the DMRS type may conform to at least one of embodiments 7 to 9.

[0315] <Embodiment B0> DWS may be supported or configured for DCI format 0_X. According to this embodiment, the waveform for PUSCH scheduled by DCI format 0_X can be dynamically selected in a context-dependent manner. DWS for DCI format 0_X may follow at least one of the following options:

[0316] - Option 1: Configuration approach The DWS settings for DCI format 0_X may follow at least one of the following options: -- Option 1-1: A new, separate RRC parameter for DCI format 0_X. This parameter allows for independent settings regarding DWS on / off for each DCI format. -- Option 1-2: Reuse / adaptation of RRC parameters for other purposes. This parameter eliminates the need for additional signaling. For example, an RRC parameter for other purposes may set the on / off status of at least one DWS for DCI formats 0_1 and 0_2.

[0317] - Option 2 The number of bits used to indicate 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 cells being co-scheduled. A one-to-one mapping between bits and cells may be applied. -- Option 2-3: N1 bit. Here, 1 <N1<Nであってもよい。 --- For example, N1 may be the number of cells in which DWS is set up and jointly scheduled. --- For example, N1 may be the maximum number of cells co-scheduled from a cell combination. In this case, multiple cell combinations may be set by the RRC parameter. --- For example, N1 may be the maximum number of cells from a cell combination that are co-scheduled with DWS settings. In this case, multiple cell combinations may be set by the RRC parameter.

[0318] <Embodiment B1> If DWS is set in DCI format 0_X, the RRC setting (transformPrecoder) of the transform precoder may follow at least one of the following forms:

[0319] - Form 1-1 For any of the jointly scheduled cells, the setting is "disabled". This setting simplifies the interpretation of 1-bit DWS in DCI format 0_X.

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

[0321] - Form 1-3 The settings differ for different cells within a jointly scheduled cell. This setting maintains the configurability of the Rel.17 waveform for each cell.

[0322] According to this embodiment, the conversion precoder can be properly configured even when DWS is set in DCI format 0_X.

[0323] <Embodiment B2> If DWS is set in DCI format 0_X, the maximum rank RRC setting (maxRank) may follow at least one of the following forms:

[0324] - Form 2-1 The settings are the same across all jointly scheduled cells.

[0325] - Form 2-1a Across all jointly scheduled cells, the setting is '1'.

[0326] - Form 2-2 The settings differ across the jointly scheduled cells.

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

[0328] <Embodiment B3> If DWS is configured in DCI format 0_X, the RRC setting (resource allocation) for FDRA type may follow at least one of the following forms:

[0329] - Form 3-1 The settings are the same across all jointly scheduled cells.

[0330] - Form 3-1a Across all jointly scheduled cells, the setting is FDRA type 1 ('resourceAllocationType1').

[0331] - Form 3-1b Across all co-scheduled cells, the setting is dynamic switching.

[0332] - Form 3-1c Across all jointly scheduled cells, the setting is anything other than FDRA type 0 ('resourceAllocationType0').

[0333] - Form 3-2 The settings differ across all jointly scheduled cells.

[0334] - Form 3-3 Across all jointly scheduled cells, the setting is different and is not 'resourceAllocationType0'.

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

[0336] <Embodiment B4> If DWS is configured in DCI format 0_X, the RRC setting (dmrs-Type) for DMRS type may follow at least one of the following forms:

[0337] - Form 4-1 The settings are the same across all jointly scheduled cells.

[0338] - Form 4-1a The setting is not applied to any of the jointly scheduled cells. This may imply that DMRS Type 1 is applied to any of the jointly scheduled cells.

[0339] - Form 4-1b For any of the jointly scheduled cells, the setting is not type 2 ('type2').

[0340] - Form 4-2 The settings differ for each jointly scheduled cell.

[0341] According to this embodiment, the DMRS type can be properly set even when DWS is set in DCI format 0_X.

[0342] <Analysis B2> The problem lies in how to achieve DCI size alignment for DCI format 0_X that includes DWS fields. This DCI size alignment may depend on at least one of several approaches. DCI fields that require alignment consideration may include antenna ports, TPMI, PTRS-DMRS associations, DMRS sequence initialization, and frequency hopping flags.

[0343] Details of the DWS field within DCI format 0_X may follow at least one of the following guidelines. - Policy 1: The DWS field in DCI format 0_X is 1 bit. This DWS field may be of type 1A. - Policy 2: The DWS field in DCI format 0_X is N(>1) bits. This DWS field may be of type 2. - Policy 3: The DWS field in DCI format 0_X can be set between policies 1 and 2. In this case, the DWS field may be of type 3. - Other policy: The DWS field in DCI format 0_X may be of type 1B / 1C.

[0344] Embodiments B0 to B4 may be applied regardless of policies 1 to 3.

[0345] Embodiments B5 to B7 may be based on Policy 1.

[0346] Embodiments B8 to B10 may be based on policy 2.

[0347] <Embodiment B5> If a 1-bit DWS field is set for DCI format 0_X (Figure 19), the interpretation of the 1-bit instruction may follow at least one of the following forms:

[0348] - Form 5-1 For any of the co-scheduled cells, '0' indicates CP-OFDM (transformation precoder disabled), and '1' indicates DFT-s-OFDM (transformation precoder enabled). This interpretation avoids complex waveform combinations across co-scheduled cells.

[0349] - Form 5-2 For any of the co-scheduled cells, '0' indicates the waveform set in the RRC parameter, and '1' indicates that the waveform should be switched from the waveform set in the RRC parameter. According to this interpretation, it is possible to switch waveforms for all co-scheduled cells using only one bit. This case can be considered together with Embodiment B1. For example, in Embodiment 1-1, complex waveform indications are avoided by restricting the conversion precoder to be disabled.

[0350] - Form 5-3 For any of the co-scheduled cells, '0' indicates the waveform set in the RRC parameter for one of the co-scheduled cells, and '1' indicates that the waveform will be switched from the waveform set in the RRC parameter for one of the co-scheduled cells. This interpretation avoids complex combinations of waveforms across co-scheduled cells.

[0351] Forms 5-1 / 5-2 / 5-3 may apply only to co-scheduled cells where the DWS setting is enabled.

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

[0353] In Form 5-3, one of the jointly scheduled cells may be one of the following definitions, or a combination of two or more. - The cell to be scheduled. - 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. - The cell with the minimum or maximum serving cell index. - Cells designated by DCI. - Cells set by RRC IE. - A cell designated by MAC CE. - Cells where DWS is set.

[0354] A combination of two or more definitions may include, for example, a cell with the minimum serving cell index among cells that are jointly scheduled and have DWS set.

[0355] In the example in Figure 20, the RRC-set waveforms for cell indices #0, #1, #2, and #3 are CP-OFDM(CP), DFT-s-OFDM(DFT-s), CP-OFDM(CP), and CP-OFDM(CP), respectively.

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

[0357] 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 indices #0, #1, #2, and #3 (PUSCH), respectively. 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 indices #0, #1, #2, and #3 (PUSCH), respectively.

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

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

[0360] <Embodiment B6> If a 1-bit DWS field is set for DCI format 0_X, whether or not a specific DCI field exists within that DCI format 0_X may be determined by a rule. That rule may follow at least one of the following options:

[0361] - Option 1: The specific DCI field may be at least one of the following options. -- Option 1-1: Initialize DMRS series. -- Option 1-2: PTRS-DMRS association.

[0362] - Option 2: The rule may be at least one of the following options. -- Option 2-1: The specific DCI field always exists. -- Option 2-2: The specific DCI field does not exist at all. -- Option 2-3: The specific DCI field for the jointly scheduled cells is always present. -- Option 2-4: For cells that are included in a jointly scheduled cell and have DWS set, the specific DCI field is always present. -- Option 2-5: The existence of a specific DCI field is determined based on the DWS bit for all co-scheduled cells. For example, if the DWS indicates CP-OFDM for all co-scheduled cells, then a specific DCI field exists for all co-scheduled cells; otherwise, the specific DCI field does not exist.

[0363] According to this embodiment, when the DWS field in DCI format 0_X is 1 bit, it is possible to appropriately determine whether or not a specific DCI field exists.

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

[0365] - Option 1: The specific DCI field may be at least one of the following options. -- Option 1-1: Antenna port. -- Option 1-2: TPMI (Precoding Information and Number of Layers).

[0366] In options 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 Layer Count" field and the "Second Precoding Information" field may be considered / determined.

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

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

[0369] <Embodiment B8> If an N-bit DWS field is set for DCI format 0_X that schedules N CCs (Figure 21), the interpretation of the N-bit instruction may follow at least one of the following forms:

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

[0371] - Form 8-2 For the corresponding cell, '0' may indicate the waveform set in the RRC parameter, and '1' may indicate that the waveform is switched from the waveform set in the RRC parameter. This case can be considered together with Embodiment B1. For example, in Embodiment 1-1, complex waveform indications are avoided by restricting the conversion precoder to be disabled.

[0372] In forms 8-1 / 8-2, the interpretations of '0' and '1' may be reversed.

[0373] 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 cells that are co-scheduled 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 for 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. -- Options 1-3: The relationship (mapping) is set by the RRC IE. -- Options 1-4: The relationship (mapping) is indicated by DCI / MAC CE. -- Options 1-5: A set of multiple relationships (mappings) is set up by the RRC IE, and one of the relationships in that set is indicated by the DCI / MAC CE.

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

[0375] <Embodiment B9> If an N-bit DWS field is set for a DCI format 0_X that schedules N CCs, whether or not a particular DCI field exists within that DCI format 0_X may be based on a rule. That rule may follow at least one of the following options:

[0376] - Option 1: The specific DCI field may be at least one of the following options. -- Option 1-1: Initialize DMRS series. -- Option 1-2: PTRS-DMRS association.

[0377] - Option 2: The rule may be at least one of the following options. -- Option 2-1: The specific DCI field always exists. -- Option 2-2: The specific DCI field does not exist at all. -- Option 2-3: The specific DCI field for the jointly scheduled cells is always present. -- Option 2-4: For cells that are included in a jointly scheduled cell and have DWS set, the specific DCI field is always present. -- Option 2-5: Based on the DWS bits for all co-scheduled cells, it is determined whether a specific DCI field exists. For example, if the DWS indicates CP-OFDM for a cell with index 0 among the co-scheduled cells, then a specific DCI field (e.g., the DMRS sequence initialization field) exists for that cell; otherwise, the specific DCI field does not exist.

[0378] According to this embodiment, when the DWS field in DCI format 0_X for scheduling N CCs is N bits, it is possible to appropriately determine whether or not a particular DCI field exists.

[0379] <Embodiment B10> If an N-bit DWS field is set for a DCI format 0_X that schedules N CCs, the size (bit width) of a particular DCI field within that DCI format 0_X may be based on a rule. That rule may follow at least one of the following options:

[0380] - Option 1: The specific DCI field may be at least one of the following options. -- Option 1-1: Antenna port field. -- Option 1-2: TPMI (Precoding Information and Number of Layers).

[0381] In options 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 Layer Count" field and the "Second Precoding Information" field may be considered / determined.

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

[0383] According to this embodiment, when the DWS field in DCI format 0_X for scheduling N CCs is N bits, the size of a particular DCI field can be appropriately determined.

[0384] <Supplement> [Notification of information to UE] In the embodiments described above, notification of any information from a Network (NW) (e.g., a Base Station (BS)) to a UE (in other words, reception of any information from a BS at the UE) may be performed using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.

[0385] If the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new Logical Channel ID (LCID) not defined in existing standards in the MAC subheader.

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

[0387] Furthermore, the notification of any information to the UE in the above-described embodiment may be periodic, semi-persistent, or aperiodic.

[0388] [Notification of information from UE] In the embodiments described above, notification of any information from the UE (to the NW) (in other words, transmission / reporting 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), specific signals / channels (e.g., PUCCH, PUSCH, PRACH, reference signals), or a combination thereof.

[0389] If the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new LCID, not specified in existing standards, in the MAC subheader.

[0390] If the above notice is issued by the UCI, the notice may be sent using PUCCH or PUSCH.

[0391] Furthermore, the notification of any information from the UE in the above-described embodiments may be periodic, semi-persistent, or aperiodic.

[0392] [Regarding the application of each embodiment] At least one of the embodiments described above may be applied if certain conditions are met. These conditions may be specified in a standard or notified to the UE / BS using upper-layer signaling / physical layer signaling.

[0393] The specific condition in question may be one of the following conditions, or it may be defined by an AND / OR of two or more of the following conditions. • DWS must be configured. For example, the DWS field must exist. • DWS is instructed. For example, the waveform is set by the RRC parameter and the switching is instructed by DCI.

[0394] At least one of the embodiments described above may apply only to a UE that has reported or supports a particular UE capability.

[0395] The specific UE capability may represent at least one of the following: • To support specific processing / operation / control / information for at least one of the above embodiments. • Supports DWS instruction types 1A / 1B / 1C / 2 / 3 within DCI format 0_X. • To support Embodiments B5 / B8 when the DWS instruction in DCI format 0_X is of type 3. • To support Embodiments B6 / B9 when the DWS instruction in DCI format 0_X is of type 3. • To support Embodiments B7 / B10 when the DWS instruction in DCI format 0_X is of type 3.

[0396] The specific UE capabilities described above may also be UE capabilities that are reported separately between DCI format 0_1 ​​and DCI format 0_X (e.g., 0_2).

[0397] Furthermore, the above-mentioned specific UE capabilities may be based on the premise that support for DWS instruction in DCI format 0_1 ​​is supported in DCI format 0_X.

[0398] Furthermore, the above-mentioned specific UE capabilities may be capabilities that apply across all frequencies (commonly regardless of frequency), capabilities per frequency (e.g., one or a combination thereof, such as cell, band, band combination, BWP, component carrier, etc.), capabilities per frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), capabilities per subcarrier spacing (SCS), or capabilities per feature set (FS) or feature set per component-carrier (FSPC).

[0399] Furthermore, the specific UE capabilities described above may be capabilities that apply across all duplexing schemes (common to all duplexing schemes), or they may be capabilities specific to each duplexing scheme (e.g., Time Division Duplex (TDD), Frequency Division Duplex (FDD)).

[0400] Furthermore, at least one of the embodiments described above may be applied when the UE is configured / activated / triggered by upper layer signaling / physical layer signaling to perform certain information (or the actions of the embodiments described above) related to the embodiments described above. For example, such certain information may be arbitrary RRC parameters for a particular release (e.g., Rel.18 / 19).

[0401] In Rel.YY (for example, YY is 18 or greater), the RRC parameter that enables operation XXX may be expressed as XXX_rYY(XXX-rYY).

[0402] If the UE does not support at least one of the above-mentioned specific UE capabilities or does not have the above-mentioned specific information configured, the behavior of, for example, Rel.15 / 16 may be applied.

[0403] (Note) The following invention is added with respect to one embodiment of this disclosure. [Note 1] A receiving unit receives the settings for multiple uplink shared channels transmitted on multiple cells, and receives downlink control information including a first field for scheduling the multiple uplink shared channels and a second field relating to the waveform. A terminal having a control unit that controls the transmission of the multiple uplink shared channels based on the above settings and the downlink control information. [Note 2] The aforementioned setting is the terminal described in Appendix 1, which shows the same value for the multiple cells. [Note 3] The aforementioned setting is a terminal as described in Appendix 1 or Appendix 2, which indicates multiple values ​​corresponding to each of the multiple cells. [Note 4] The aforementioned settings are those of a terminal as described in any of Appendix 1 to 3, which specify values ​​relating to at least one of the following: conversion precoder, maximum rank, frequency domain resource allocation type, and demodulation reference signal type.

[0404] (Note) The following invention is added with respect to one embodiment of this disclosure. [Note 1] A receiving unit that receives downlink control information including a first field for scheduling multiple uplink shared channels transmitted on multiple cells, and a second field relating to the waveform, A terminal having a control unit that determines multiple waveforms to be applied to each of the multiple uplink shared channels based on the downlink control information. [Note 2] The terminal described in Appendix 1, wherein the second field indicates, for at least one of the plurality of cells, whether or not the conversion precoder is enabled, or whether or not to change the state set by the higher layer parameter. [Note 3] The size of the second field is 1 bit, as specified in Appendix 1 or Appendix 2 of the terminal. [Note 4] The size of the second field is the number of bits of the multiple cells, as specified in any of the terminals listed in Appendix 1 to Appendix 3.

[0405] (Note) The following invention is added with respect to one embodiment of this disclosure. [Note 1] A receiving unit that receives downlink control information including a first field for scheduling multiple uplink shared channels transmitted on multiple cells, and a second field relating to the waveform, A terminal having a control unit that determines whether the downlink control information includes a specific field relating to at least one of the following: sequence initialization of demodulation reference signals (DMRS) and association between the DMRS and phase-following reference signals (PTRS). [Note 2] The terminal as described in Appendix 1, wherein the control unit determines whether the downlink control information includes the specific field for at least one of the plurality of cells. [Note 3] The size of the second field is 1 bit, as specified in Appendix 1 or Appendix 2 of the terminal. [Note 4] The size of the second field is the number of bits of the multiple cells, as specified in any of the terminals listed in Appendix 1 to Appendix 3.

[0406] (Note) The following invention is added with respect to one embodiment of this disclosure. [Note 1] A receiving unit that receives downlink control information including a first field for scheduling multiple uplink shared channels transmitted on multiple cells, a second field relating to the waveform, and a specific field relating to at least one of the following: an antenna port, precoding information, and the number of layers. A terminal having a control unit that determines the size of the specific field. [Note 2] The terminal as described in Appendix 1, wherein the control unit determines the size of the specific field based on whether or not a conversion precoder is enabled for at least one of the plurality of cells. [Note 3] The size of the second field is 1 bit, as specified in Appendix 1 or Appendix 2 of the terminal. [Note 4] The size of the second field is the number of bits of the multiple cells, as specified in any of the terminals listed in Appendix 1 to Appendix 3.

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

[0408] Figure 22 shows an example of a schematic configuration of a wireless communication system according to one embodiment. Wireless communication system 1 (which may also be simply called system 1) may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc., as specified by the Third Generation Partnership Project (3GPP).

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

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

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

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

[0413] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of Carrier Aggregation (CA) using multiple Component Carriers (CC) and Dual Connectivity (DC).

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

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

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

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

[0418] The core network 30 may include network functions (NF) such as User Plane Function (UPF), Access and Mobility Management Function (AMF), Session Management Function (SMF), Unified Data Management (UDM), Application Function (AF), Data Network (DN), Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). Multiple functions may be provided by a single network node. Furthermore, communication with an external network (e.g., the Internet) may occur via the DN.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0438] The transmitting / receiving unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transmitting / receiving unit 120 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

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

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

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

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

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

[0444] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform transmission processing on the bit sequence to be transmitted, such as channel coding (which may include error correction coding), modulation, mapping, filtering, discrete Fourier transform (DFT) processing (if necessary), inverse fast Fourier transform (IFFT) processing, precoding, and digital-to-analog conversion, and output a baseband signal.

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

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

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

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

[0449] The transmission path interface 140 may send and receive signals (backhaul signaling) with devices included in the core network 30 (e.g., network nodes providing 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.

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

[0451] The transmitting / receiving unit 120 may receive the settings for multiple uplink shared channels transmitted on multiple cells and transmit downlink control information including a first field for scheduling the multiple uplink shared channels and a second field relating to the waveform. The control unit 110 may control the reception of the multiple uplink shared channels based on the settings and the downlink control information.

[0452] The transmitting / receiving unit 120 may transmit downlink control information including a first field for scheduling multiple uplink shared channels transmitted on multiple cells, and a second field relating to waveforms. The control unit 110 may control the reception of the multiple uplink shared channels. Multiple waveforms determined based on the second field may be applied to the multiple uplink shared channels.

[0453] The control unit 110 may include in the downlink control information a first field for scheduling multiple uplink shared channels transmitted on multiple cells, and a second field relating to waveforms, and may decide whether or not to include a specific field relating to at least one of the following in the downlink control information: sequence initialization of demodulation reference signals (DMRS) and association between the DMRS and phase-following reference signals (PTRS). The transmitting / receiving unit 120 may transmit the downlink control information.

[0454] The control unit 110 determines the size of a specific field relating to at least one of the antenna port, precoding information, and the number of layers, and may include a first field for scheduling multiple uplink shared channels transmitted on multiple cells, a second field relating to the waveform, and the aforementioned specific field in the downlink control information. The transmitting / receiving unit 120 may transmit the downlink control information.

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

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

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

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

[0459] The transmitting / receiving unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transmitting / receiving unit 220 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

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

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

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

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

[0464] The transmitting / receiving unit 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc., on data and control information acquired from the control unit 210, etc., to generate a bit sequence to be transmitted.

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

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

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

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

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

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

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

[0472] The transmitting / receiving unit 220 may receive settings for multiple uplink shared channels transmitted on multiple cells, and may also receive downlink control information including a first field for scheduling the multiple uplink shared channels and a second field relating to the waveform. The control unit 210 may control the transmission of the multiple uplink shared channels based on the settings and the downlink control information.

[0473] The aforementioned setting may indicate the same value for the multiple cells.

[0474] The above setting may indicate multiple values ​​corresponding to each of the multiple cells.

[0475] The aforementioned settings may represent values ​​for at least one of the following: conversion precoder, maximum rank, frequency domain resource allocation type, and demodulation reference signal type.

[0476] The transmitting / receiving unit 220 may receive downlink control information including a first field for scheduling multiple uplink shared channels transmitted on multiple cells, and a second field relating to waveforms. The control unit 210 may determine multiple waveforms to be applied to each of the multiple uplink shared channels based on the downlink control information.

[0477] The second field may indicate, for at least one of the plurality of cells, whether or not the conversion precoder is enabled, or whether or not to change the state set by the higher layer parameter.

[0478] The size of the second field may be 1 bit.

[0479] The size of the second field may be the number of bits equal to the number of cells.

[0480] The transmitting / receiving unit 220 may receive downlink control information which includes a first field for scheduling multiple uplink shared channels transmitted on multiple cells, and a second field relating to waveforms. The control unit 210 may determine whether the downlink control information includes a specific field relating to at least one of the following: sequence initialization of demodulation reference signals (DMRS) and association between the DMRS and phase-following reference signals (PTRS).

[0481] The control unit 210 may determine whether the downlink control information includes the specific field for at least one of the plurality of cells.

[0482] The size of the second field may be 1 bit.

[0483] The size of the second field may be the number of bits equal to the number of cells.

[0484] The transmitting / receiving unit 220 may receive downlink control information which includes a first field for scheduling multiple uplink shared channels transmitted on multiple cells, a second field relating to the waveform, and a specific field relating to at least one of the following: the antenna port, precoding information, and the number of layers. The control unit 210 may determine the size of the specific field.

[0485] The control unit 210 may determine the size of the specific field based on whether or not the conversion precoder is enabled for at least one of the plurality of cells.

[0486] The size of the second field may be 1 bit.

[0487] The size of the second field may be the number of bits equal to the number of cells.

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

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

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

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

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

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

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

[0495] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly.

[0496] Memory 1002 is a computer-readable recording medium and may consist of at least one of the following: Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. Memory 1002 may also be called a register, cache, or main memory. Memory 1002 can store executable programs (program code), software modules, etc., for carrying out a wireless communication method according to one embodiment of this disclosure.

[0497] Storage 1003 is a computer-readable recording medium and may consist of at least one of the following: a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disk (Compact Disc ROM (CD-ROM)), a digital multipurpose disk, a Blu-ray disk), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, stick, key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be called an auxiliary storage device.

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

[0499] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, light-emitting diode (LED) lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0516] One or more RBs may also be called Physical RBs (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

[0517] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0518] A Bandwidth Part (BWP) (also called a partial bandwidth) may represent a subset of consecutive common resource blocks (RBs) for a given neurology in a given carrier. Here, the common RBs may be identified by an index of the RBs relative to the carrier's common reference point. PRBs may be defined and numbered within a BWP.

[0519] A BWP may include UL BWPs (BWPs for UL) and DL BWPs (BWPs for DL). One or more BWPs may be configured within a single carrier for a UE.

[0520] At least one of the configured BWPs may be active, and the UE does not need to assume that it will send or receive a given signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

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

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

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

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

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

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

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

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

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

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

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

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

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

[0534] In this disclosure, terms such as "precoding," "precoder," "weight (precoding weight)," "quasi-co-location (QCL)," "transmission configuration indication state (TCI state)," "spatial relation," "spatial domain filter," "transmit power," "phase rotation," "antenna port," "antenna port group," "layer," "number of layers," "rank," "resource," "resource set," "resource group," "beam," "beam width," "beam angle," "antenna," "antenna element," and "panel" may be used interchangeably.

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

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

[0537] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform a control / operation based on said information.

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

[0539] A mobile station may also be called a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other appropriate term.

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

[0541] The term "mobile object" refers to any movable object, regardless of its speed, and naturally includes cases where the mobile object is stationary. Examples of such mobile objects include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and items carried on them. Furthermore, such mobile objects may be autonomously driven objects operating based on operational commands.

[0542] The mobile entity may be a vehicle (e.g., a car, an airplane), an unmanned mobile entity (e.g., a drone, an autonomous vehicle), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication 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.

[0543] Figure 26 shows an example of a vehicle according to one 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, an axle 48, an electronic control unit 49, various sensors (including a current sensor 50, a rotation speed sensor 51, a pneumatic 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.

[0544] The drive unit 41 consists of, for example, at least one of an engine, a motor, or an engine-motor hybrid. 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 the user.

[0545] The electronic control unit 49 consists of a microprocessor 61, memory (ROM, RAM) 62, and communication ports (e.g., input / output (IO) ports) 63. Signals from various sensors 50-58 installed in the vehicle are input to the electronic control unit 49. The electronic control unit 49 may also be called an Electronic Control Unit (ECU).

[0546] Signals from various sensors 50-58 include current signals from current sensor 50 for sensing motor current, rotational speed signals of front wheels 46 / rear wheels 47 acquired by rotational speed sensor 51, air pressure signals of front wheels 46 / rear wheels 47 acquired by air pressure sensor 52, vehicle speed signals acquired by vehicle speed sensor 53, acceleration signals acquired by acceleration sensor 54, accelerator pedal depression signal of accelerator pedal 43 acquired by accelerator pedal sensor 55, brake pedal depression signal of brake pedal 44 acquired by brake pedal sensor 56, operation signals of shift lever 45 acquired by shift lever sensor 57, and detection signals for detecting obstacles, vehicles, pedestrians, etc., acquired by object detection sensor 58.

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

[0548] The information service unit 59 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) and output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.).

[0549] The driver assistance system unit 64 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, 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 Unit (IMU), Inertial Navigation System (INS)), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driver assistance functions or autonomous driving functions.

[0550] 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 sends and receives data (information) via the communication port 63 to 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, axle 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and various sensors 50-58 provided in the vehicle 40.

[0551] 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 external devices. For example, it can send and receive various types of information to and from external devices 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. Alternatively, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 (it may function as at least one of the base station 10 and the user terminal 20).

[0552] The communication module 60 may transmit at least one of the following to an external device via wireless communication: signals from the various sensors 50-58 input to the electronic control unit 49, information obtained based on said signals, and information based on input from an external source (user) obtained via the information service unit 59. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc., may also be called input units that accept input. For example, the PUSCH transmitted by the communication module 60 may include information based on the above input.

[0553] The communication module 60 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 59 installed in the vehicle. The information service unit 59 may also be called an output unit, which outputs information (for example, it outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 60).

[0554] 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, axle 48, various sensors 50-58, etc., which are provided in the vehicle 40.

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

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

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

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

[0559] Each aspect / embodiment described in this disclosure includes Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (where x is, for example, an integer or decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM®), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), and IEEE This may apply to systems utilizing 802.20, Ultra-WideBand (UWB), Bluetooth®, or other appropriate wireless communication methods, as well as next-generation systems that are extended, modified, created, or defined based on these. It may also apply to combinations of multiple systems (e.g., a combination of LTE or LTE-A and 5G).

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

[0561] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, the references to the first and second elements do not imply that only two elements may be employed or that the first element must precede the second element in any way.

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

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

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

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

[0566] The term "maximum transmit power" as used in this disclosure may mean the maximum transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

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

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

[0569] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

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

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

[0572] In this disclosure, terms such as "less than or equal to," "less than," "greater than or equal to," "more than," and "equal to" may be interpreted interchangeably. In addition, in this disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees. Furthermore, in this disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees, by adding "i-th" (where i is any integer) to the expression (for example, "highest" may be interpreted interchangeably with "i-th highest").

[0573] In this disclosure, "of," "for," "regarding," "related to," and "associated with" may be interpreted as being interchangeable.

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

Claims

1. A receiving unit that receives downlink control information including a first field for scheduling multiple uplink shared channels transmitted on multiple cells, and a second field relating to the waveform, A terminal having a control unit that determines multiple waveforms to be applied to each of the multiple uplink shared channels based on the downlink control information.

2. The terminal according to claim 1, wherein the second field indicates, for at least one of the plurality of cells, whether or not the conversion precoder is enabled, or whether or not to change the state set by the higher layer parameter.

3. The terminal according to claim 1, wherein the size of the second field is 1 bit.

4. The terminal according to claim 1, wherein the size of the second field is the number of bits equal to the number of cells.

5. The steps include receiving downlink control information which includes a first field for scheduling multiple uplink shared channels transmitted on multiple cells, and a second field relating to the waveform, A wireless communication method for a terminal, comprising the step of determining a plurality of waveforms to be applied to each of the plurality of uplink sharing channels based on the downlink control information.

6. A transmission unit that transmits downlink control information including a first field for scheduling multiple uplink shared channels transmitted on multiple cells, and a second field relating to the waveform, It includes a control unit that controls the reception of the multiple uplink shared channels, A base station in which multiple waveforms determined based on the second field are applied to the multiple uplink sharing channels.

Images