Terminal, wireless communication method, and base station

Abstract

A terminal according to one embodiment of the present disclosure is provided with: a transmission unit that transmits capability information pertaining to a dynamic transform precoder instruction in an operation that supports the use of a plurality of component carriers in one band; and a control unit that controls reception of the setting indicated by the dynamic conversion precoder.

Description

Technical Field

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

[0002] In Universal Mobile Telecommunications System (UMTS) networks, Long Term Evolution (LTE) was standardized with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). Furthermore, LTE-Advanced (3GPP Rel. 10-14) was standardized with the aim of further increasing capacity and improving upon LTE (Third Generation Partnership Project) (3GPP (registered trademark)) Releases (Rel.) 8 and 9.

[0003] The research is also on successor systems to LTE (e.g., also known as the 5th generation mobile communication system (5G), 5G+ (plus), the 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel.15 and later, etc.).

[0004] Existing technical documents

[0005] Non-patent literature

[0006] 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 Summary of the Invention

[0007] The problem that the invention aims to solve

[0008] In future wireless communication systems, research is underway to support not only Discrete Fourier Transform-Spread-Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) waveforms as single-carrier waveforms, but also Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) waveforms as multi-carrier waveforms.

[0009] However, since waveform settings were previously performed through Radio Resource Control (RRC), RRC reconstruction was required to switch waveforms. This raises concerns about increased signaling overhead and reduced communication throughput.

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

[0011] Methods for solving problems

[0012] One aspect of this disclosure relates to a terminal comprising: a transmitting unit for transmitting capability information related to a dynamic transformation precoder indication in operation supporting the use of multiple component carriers within a band domain; and a control unit for controlling the reception of settings of the dynamic transformation precoder indication.

[0013] Invention Effects

[0014] According to one method of this disclosure, waveform switching can be performed appropriately. Attached Figure Description

[0015] Figure 1 This is a graph representing the DCI size for option 1-1.

[0016] Figure 2 This is a graph representing the DCI size for options 1-2.

[0017] Figure 3 This is a flowchart illustrating an example of the processing in Implementation 0.1.

[0018] Figure 4 This is a flowchart illustrating an example of the processing in Implementation 0.2.

[0019] Figure 5This is a diagram representing the definition of PTRS-DMRS association and DMRS sequence initialization for DCI fields.

[0020] Figure 6 This is a diagram illustrating an example of the setting modes for useInterlacePUCCH-PUSCH, resourceAllocation, and RA type.

[0021] Figure 7 This is a flowchart illustrating an example of the processing in Implementation Method 3.

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

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

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

[0025] Figure 11 This is a diagram showing an example of a backoff parameter value.

[0026] Figure 12 This is a diagram representing an example of the antenna port field in DCI format 0_1.

[0027] Figure 13 This is a diagram illustrating an example of DMRS type settings when dynamic waveform switching is configured.

[0028] Figure 14A as well as Figure 14B This diagram illustrates an example of how the code points of a specific field of the DCI are interpreted when dynamic waveform switching is set and DMRS type 2 is set.

[0029] Figure 15 This is a diagram illustrating an example of the RRC IE involved in implementation method A1.

[0030] Figure 16 This is a diagram illustrating an example of the DCI involved in implementation method A4.

[0031] Figure 17A as well as Figure 17B This is a diagram illustrating an example of multicarrier scheduling.

[0032] Figure 18A as well as Figure 18BThis is a diagram illustrating another example of multicarrier scheduling.

[0033] Figure 19 This is a diagram illustrating an example of a 1-bit DWS field in multi-carrier DCI.

[0034] Figure 20 This is a diagram illustrating an example of the waveforms indicated for multiple cells according to implementation method B5.

[0035] Figure 21 This is a diagram illustrating an example of an N-bit DWS field in multi-carrier DCI.

[0036] Figure 22 This is a diagram illustrating an example of UE capabilities related to DWS.

[0037] Figure 23 This represents an example of multiple values ​​of MPR for consecutive CA within the band field.

[0038] Figure 24 This is a diagram illustrating an example of the schematic structure of a wireless communication system according to one embodiment.

[0039] Figure 25 This is a diagram illustrating an example of the structure of a base station according to one embodiment.

[0040] Figure 26 This is a diagram illustrating an example of the structure of a user terminal according to one embodiment.

[0041] Figure 27 This is a diagram illustrating an example of the hardware structure of a base station and a user terminal according to one embodiment.

[0042] Figure 28 This is a diagram illustrating an example of a vehicle according to one embodiment. Detailed Implementation

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

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

[0045] Regarding CP-OFDM, frequency resource allocation can be more flexible. For example, it allows for both contiguous Physical Resource Block (PRB) allocation and non-contiguous PRB allocation. Furthermore, contiguous PRB allocation is not limited to multiples of 2, 3, or 5. It is also possible to use Frequency Division Multiplexing (FDM) in the Demodulation Reference Signal (DMRS) and PUSCH when applying CP-OFDM.

[0046] Regarding DFT-s-OFDM (or DFT-S-OFDM / DFTS-OFDM), although frequency resource allocation is more constrained, the peak to average power ratio (PAPR) is lower, making it suitable for power-limited UEs.

[0047] Furthermore, regarding communication throughput without considering PAPR, CP-OFDM has higher communication throughput than DFT-s-OFDM. Regarding communication throughput considering PAPR, with a high SNR (MCS) (modulation coding scheme of 16QAM or 64QAM), CP-OFDM has a higher communication throughput than DFT-s-OFDM. However, with a low SNR (MCS) (modulation coding scheme of QPSK), DFT-s-OFDM has higher communication throughput than CP-OFDM. In other words, the preferred waveform varies depending on the SNR (MCS).

[0048] Typically, network (NW) switches waveforms based on the signal-to-noise ratio (SNR). Switching between DFT-s-OFDM and CP-OFDM is achieved via the transform precoder in the Radio Resource Control (RRC) signaling's Uplink Shared Channel (PUSCH) configuration (PUSCH-Config). When the transform precoder is disabled, CP-OFDM is applied; when it is enabled, DFT-s-OFDM is applied. Waveform switching requires RRC reconstruction. This raises concerns about increased signaling overhead and decreased communication throughput.

[0049] To achieve more flexible throughput control, the dynamic switching between CP-OFDM and DFT-s-OFDM via DCI / MAC CE is considered. However, research on such dynamic switching has not yet progressed.

[0050] For example, in existing specifications (e.g., 3GPP Rel.16), as shown in (1) to (6) below, the size of several DCI fields in the DCI format (e.g., DCI format 0_0 / 0_1 / 0_2) is affected by the switching of the waveform.

[0051] (1) In the "Precoding information and number of layers" field, use different tables for the two waveforms.

[0052] (2) In the "Antenna ports" field, use different tables for the two waveforms.

[0053] (3) In the "DMRS sequence initialization" field, it is 0 bits when the transformation precoder is valid and 1 bit when it is invalid.

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

[0055] (5) In "Frequency domain resource assignment", the DCI size varies depending on the resource assignment type. In addition, different resource assignments are supported 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.

[0056] (6) In the "Frequency hopping flag" field, the DCI size varies depending on the resource allocation type. As mentioned above, the supported resource allocations differ depending on the waveform.

[0057] (Dynamic switching between deactivation and activation of the transform precoder)

[0058] The UE can also receive settings indicating the deactivation or activation of the transform precoder for the PUSCH via dynamic switching through DCI / MAC CE. The UE can then also receive instructions indicating the activation or deactivation of the transform precoder for the PUSCH via DCI / MAC CE. Hereinafter, dynamic switching based on DCI / MAC CE will sometimes be abbreviated as dynamic switching. Alternatively, the UE can also have the dynamic switching of the waveform / transform precoder preset (enabled to switch) via higher-layer signaling, etc. It is also possible to perform dynamic switching of the transform precoder via DCI / MAC CE regardless of the presence or absence of such settings.

[0059] For example, dynamic waveform switching based on DCI signaling can be performed implicitly or explicitly. For instance, a 1-bit field representing the CP-OFDM or DFT-s-OFDM waveform used for PUSCH can also be included in the DCI (explicit signaling). Alternatively, the UE can determine / identify the CP-OFDM or DFT-s-OFDM waveform used for PUSCH based on specific conditions such as scheduling information in the DCI (implicit signaling). In this case, the existing DCI format remains unchanged. The DCI representing dynamic UL waveform switching for PUSCH can also schedule the PUSCH.

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

[0061] The DCI format in this disclosure can represent, for example, DCI format 0_0 / 0_1 / 0_2, or other formats (e.g., DCI format 0_3 used to notify waveform switching). As other formats, a group common DCI such as DCI format 2_x can also be used. In this case, the UE can also apply waveform switching a certain time after receiving DCI format 2_x and sending an ACK.

[0062] The switching of deactivation and activation of the transform precoder in this disclosure (waveform switching) can also be waveform switching within the same BWP (switching waveforms without switching BWPs). For example, since different transform precoders can be set for each BWP, it is also possible to switch the transform precoder by switching BWPs. However, since BWP switching introduces a delay, the switching of deactivation and activation of the transform precoder is performed within the same BWP, thereby suppressing the delay.

[0063] Alternatively, when the deactivation and activation of the transform precoder for PUSCH are set via dynamic switching through DCI / MAC CE, the UE receives an indication of activation or deactivation of the transform precoder for PUSCH via DCI / MAC CE, and switches the waveform (CP-OFDM / DFT-s-OFDM) for PUSCH based on the indication.

[0064] The total DCI size in the DCI format can be fixed, independent of the deactivation and activation of the transform precoder. The DCI size can also be set / determined via higher-layer signaling (RRC). In other words, the DCI size can be independent of the DCI / MAC CE.

[0065] However, within a subset of the DCI fields, the size of each DCI field can vary depending on the deactivation and activation of the transform precoder. 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 instance, as shown in (1) to (6) of the existing specifications above, the DCI sizes can also differ.

[0066] [Option 1-1]

[0067] When the dynamic switching of the transform precoder corresponding to PUSCH (based on the switching of DCI / MAC CE) is set for PUSCH, the total size of each DCI format can be the larger of the size of each DCI format when the transform precoder is invalid and the size of each DCI format when the transform precoder is valid.

[0068] When the transformation precoder is deactivated / activated via MAC CE, the UE can also read each DCI field from the least significant bit (LSB) according to the size of each DCI field. Alternatively, the UE can also read each DCI field from the most significant bit (MSB).

[0069] Figure 1 This is a graph representing the DCI size for option 1-1. According to... Figure 1 When the transformation precoder is invalid, the total number of DCI bits (DCIFields #1 to #4) is 10 bits, and when the transformation precoder is valid, the total number of DCI bits is 7 bits. In this case, the total DCI size, which is set as the dynamic switching of the transformation precoder, is 10 bits, which is the larger DCI size.

[0070] exist Figure 1 In this process, the smaller DCI bits (DCI bits when the transformation precoder is active) are filled from the left (least significant bit) of the mapping, but they can also be filled from the right (most significant bit). That is, the UE can read each DCI field from either the least significant bit or the most significant bit.

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

[0072] [Options 1-2]

[0073] Alternatively, when the dynamic switching of the transform precoder corresponding to PUSCH is set for PUSCH, for each DCI format, the larger of the size of the DCI field when the transform precoder is invalid and the size of the DCI field when the transform precoder is valid is determined for each field, and the total size of the DCI format is the sum of the larger of the sizes of all DCI fields.

[0074] In other words, when the number of fields in a certain DCI format is set to N, the total size of the DCI format is calculated as follows.

[0075] Total size of DCI format = Σ(MAX(size of DCI field i when the transform precoder is invalid, size of DCI field i when the transform precoder is valid))(i=1~N)

[0076] When the transformation precoder is deactivated / activated via MAC CE, the UE can also read each DCI field from the least significant bit (LSB) based on the size of each DCI field. Alternatively, the UE can also read each DCI field from the most significant bit (MSB).

[0077] Figure 2 This is a graph representing the DCI values ​​for options 1-2. According to... Figure 2 In DCI field #1, the larger of the following sizes—2 bits for when the transform precoder is inactive and 1 bit for when the transform precoder is active—is 2 bits. Similarly, the larger of these sizes is 3 bits for DCI field #2, 2 bits for DCI field #3, and 4 bits for DCI field #4. These sizes are summed (2+3+2+4=11), resulting in a total DCI size of 11 bits when the dynamic switching of the transform precoder is set.

[0078] exist Figure 2 In this system, the DCI bits of the smaller field are filled from the left (least significant bit) in the mapping, but they can also be filled from the right (most significant bit). In other words, the UE can read each DCI field from either the least significant bit or the most significant bit.

[0079] exist Figure 2 In the example, the starting bit position (for the bit range of each field) is the same in both the invalid and valid cases of the transformation precoder. For example, the starting bit position of DCI field #1 is the 1st bit, the starting bit position of DCI field #2 is the 3rd bit, the starting bit position of DCI field #3 is the 6th bit, and the starting bit position of DCI field #4 is the 8th bit. Therefore, the detection processing of each field of the UE can be easily performed.

[0080] In options 1-2, even if the active / inactive state of the transformation precoder is switched, the increase in the processing load of the UE can be suppressed because the detected DCI size is the same.

[0081] (FDRA type)

[0082] In NR, as a Frequency Domain Resource Allocation (FDRA) type, it supports three types: Type 0, Type 1, and Type 2.

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

[0084] Type 1: Continuous allocation based on resource indication value (RIV).

[0085] Type 2: Interleaved configuration (for NR-unlicensed(U)).

[0086] The following are the application support options for each type that depend on the PUSCH waveform.

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

[0088] Type 1: Applicable to both CP-OFDM and DFTS-OFDM.

[0089] Type 2: Applicable to both CP-OFDM and DFTS-OFDM.

[0090] When the RRC parameter `useInterlacePUCCH-PUSCH` is not set, type 0 or type 1 is used according to the RRC parameter `resourceAllocation`. When sending type 1 UL data without permission, `resourceAllocation` is set to either `resourceAllocationType0` or `resourceAllocationType1`. If `resourceAllocationType0` is set, type 0 is used; if `resourceAllocationType1` is set, type 1 is used. When `dynamicSwitch` is set, type 0 or type 1 is indicated by the scheduling DCI (MSB of FDRA). When `useInterlacePUCCH-PUSCH` is set, type 2 is used.

[0091] (DMRS)

[0092] The front-loaded DMRS is the initial DMRS (first symbol or nearby symbols) used for earlier demodulation. For high-speed mobile UEs or high modulation and coding scheme (MCS) / rank, an additional DMRS can be set via RRC. The frequency position of the additional DMRS is the same as the front-loaded DMRS.

[0093] For the time domain, DMRS mapping type A or B is set. In DMRS mapping type A, DMRS position l_0 is counted using the symbol index within the time slot. l_0 is set using the parameter (dmrs-TypeA-Position) in the MIB or ServingCellConfigCommon. DMRS position 0 (reference point l) signifies the initial symbol of the time slot or each frequency hopping. In DMRS mapping type B, DMRS position l_0 is counted using the symbol index within the PDSCH / PUSCH. l_0 is always 0. DMRS position 0 (reference point l) signifies the initial symbol of the PDSCH / PUSCH or each frequency hopping.

[0094] The location of DMRS is specified through a table in the specification, depending on the duration of PDSCH / PUSCH. The location of additional DMRS is fixed.

[0095] For the frequency domain, set DMRS setting type 1 or 2 (PDSCH / PUSCH). DMRS setting type 1 has a comb structure and can be applied to both CP-OFDM (transport precoding=disabled) and DFT-S-OFDM (transport precoding=enabled). DMRS setting type 1 maps the DMRS sequence to one subcarrier every two subcarriers in the frequency domain, thus enabling FDM of up to two DMRS. DMRS setting type 2 can only be applied to CP-OFDM. DMRS setting type 2 maps the DMRS sequence to two consecutive subcarriers every six subcarriers in the frequency domain, thus enabling FDM of up to three DMRS.

[0096] Set either single-symbol DMRS or dual-symbol DMRS.

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

[0098] Dual-symbol DMRS is used for more DMRS ports (especially MU-MIMO). In dual-symbol DMRS, the number of appended DMRS (symbols) is {0, 1}. Dual-symbol DMRS supports the case where frequency hopping is invalid. If the maximum number (maxLength) in the uplink DMRS configuration (DMRS-UplinkConfig) is 2 (len2), the choice between single-symbol DMRS and dual-symbol DMRS is determined by DCI or configured grant.

[0099] Based on the above, the following combinations of possible configuration patterns for DMRS should be considered.

[0100] • DMRS setting type 1, DMRS mapping type A, single-symbol DMRS

[0101] • DMRS setting type 1, DMRS mapping type A, dual-symbol DMRS

[0102] • DMRS setting type 1, DMRS mapping type B, single-symbol DMRS

[0103] • DMRS setting type 1, DMRS mapping type B, dual-symbol DMRS

[0104] • DMRS setting type 2, DMRS mapping type A, single-symbol DMRS

[0105] • DMRS setting type 2, DMRS mapping type A, dual-symbol DMRS

[0106] • DMRS setting type 2, DMRS mapping type B, single-symbol DMRS

[0107] • DMRS setting type 2, DMRS mapping type B, dual-symbol DMRS

[0108] Multiple DMRS ports mapped to the same RE (time and frequency resource) are called DMRS code division multiplexing (CDM) groups.

[0109] 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 via FD OCC of length 2. Between multiple DMRS CDM groups (two DMRS CDM groups), the two DMRS ports are multiplexed via FDM.

[0110] For DMRS configuration type 1 and dual-symbol DMRS, eight DMRS ports can be used. Within each DMRS CDM group, two DMRS ports are multiplexed via FD OCC of length 2, and two DMRS ports are multiplexed via TD OCC. Among multiple DMRSCDM groups (two DMRS CDM groups), two DMRS ports are multiplexed via FDM.

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

[0112] For DMRS configuration type 2 and dual-symbol DMRS, 12 DMRS ports can be used. Within each DMRS CDM group, 2 DMRS ports are multiplexed via FD OCC of length 2, and 2 DMRS ports are multiplexed via TD OCC. Among multiple DMRS CDM groups (3 DMRS CDM groups), 3 DMRS ports are multiplexed via FDM.

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

[0114] In the parameters used 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.

[0115] In the parameters used 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.

[0116] (Reference signal port)

[0117] For orthogonalization of the MIMO layer, reference signals from multiple ports are used (e.g., DeModulation Reference Signal (DMRS) and CSI-RS).

[0118] For example, for Single User MIMO (SU-MIMO), different DMRS ports / CSI-RS ports can be set for each layer. For Multi User MIMO (MU-MIMO), different DMRS ports / CSI-RS ports can be set for each layer within a single UE and for each UE.

[0119] Additionally, if a larger value for the number of CSI-RS ports is used than the number of layers used in the data, it is expected that more accurate channel state measurements can be performed based on that CSI-RS, contributing to improved throughput.

[0120] In Rel.15 NR, multiple ports of DMRS can be configured using frequency division multiplexing (FDM), frequency domain orthogonal cover code (FD-OCC), and time domain OCC (TD-OCC). If it is a type 1 DMRS (in other words, DMRS is set to type 1), it supports a maximum of 8 ports, and if it is a type 2 DMRS (in other words, DMRS is set to type 2), it supports a maximum of 12 ports.

[0121] In Rel.15 NR, the aforementioned FDM uses a comb-shaped pattern of transmit frequencies (comb-shaped resource set). The aforementioned FD-OCC uses cyclic shift (CS). Furthermore, the aforementioned TD-OCC can only be applied to dual-symbol DMRS.

[0122] The OCC disclosed herein can also be rewritten as orthogonal code, orthogonalization, cyclic shift, etc.

[0123] In addition, the type of DMRS can also be called the DMRS configuration type.

[0124] In DMRS, a DMRS in which resources are mapped in units of consecutive (adjacent) 2 symbols can also be called a dual-symbol DMRS, and a DMRS in which resources are mapped in units of 1 symbol can also be called a single-symbol DMRS.

[0125] Each type of DMRS can be mapped to more than one symbol in a time slot, depending on the length of the data channel. A DMRS mapped to the beginning of a data symbol position can also be called a front-loaded DMRS, and a DMRS that is additionally mapped to other positions can also be called an additional DMRS.

[0126] When DMRS is set to type 1 and single-symbol DMRS is used, Comb and CS can also be used for orthogonalization. For example, two types of Comb and two types of CS (Comb2+2CS) can also be used to support a maximum of four antenna ports (APs).

[0127] In the case of DMRS setting type 1 and dual-symbol DMRS, Comb, CS, and TD-OCC can also be used for orthogonalization. For example, a maximum of 8 APs can be supported by using 2 types of Comb, 2 types of CS, and TD-OCC ({1,1} and {1,-1}).

[0128] In the case of DMRS setting type 2 and single-symbol DMRS, FD-OCC can also be used for orthogonalization. For example, orthogonal codes (2-FD-OCC) can be applied to two adjacent resource elements (REs) in the frequency direction to support a maximum of 6 APs.

[0129] In the case of DMRS setting type 2 and dual-symbol DMRS, FD-OCC and TD-OCC can also be used for orthogonalization. For example, orthogonal codes (2-FD-OCC) can be applied to two adjacent REs in the frequency direction, and TD-OCC ({1, 1} and {1, -1}) can be applied to two adjacent REs in the time direction, thereby supporting a maximum of 12 APs.

[0130] Furthermore, in Rel.15 NR, multi-port CSI-RS can also support up to 32 ports by using FDM, Time Division Multiplexing (TDM), Frequency Domain OCC, Time Domain OCC, etc. The same methods as those used for DMRS can also be applied to the orthogonalization of CSI-RS.

[0131] Additionally, groups of DMRS ports orthogonalized via FD-OCC / TD-OCC as described above can also be referred to as code division multiplexing (CDM) groups.

[0132] Different CDM groups are orthogonal because they are FDM-enabled. On the other hand, within the same CDM group, the orthogonality of the applied OCC can sometimes deteriorate due to channel variations, etc. In this case, if signals within the same CDM group are received with different receiving powers, there is a concern that distance issues may arise, and orthogonality cannot be guaranteed.

[0133] Here, the TD-OCC / FD-OCC of the DMRS in Rel.15 NR is explained. The DMRS mapped to a resource element (RE) can also be equivalent to the DMRS sequence multiplied by the FD-OCC parameters (which can also be called sequence elements, etc.) w. f (k') and the parameters of TD-OCC (which can also be referred to as sequence elements, etc.) w t The sequence of (l').

[0134] Each of the TD-OCC and FD-OCC of the DMRS in Rel.15 NR is equivalent to an OCC with a sequence length (also known as an OCC length) of 2. Therefore, the possible values ​​for k' and l' are 0 and 1, respectively. By multiplying the FD-OCC by a single phase of RE, two-port DMRS can be multiplexed using the same time and frequency resources (2RE). If both the FD-OCC and TD-OCC are applied, four-port DMRS can be multiplexed using the same time and frequency resources (4RE).

[0135] The two Rel.15 DMRS port tables (antenna port index (number) and parameter association) used in the aforementioned PDSCH correspond to DMRS setting type 1 and type 2, respectively. Additionally, p represents the antenna port number, and Δ represents the parameter used to shift (offset) the frequency resources.

[0136] 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}, thus being orthogonalized using FD-OCC.

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

[0138] For antenna ports 1000-1003 and 1004-1007 of type 1, by applying {w t (0), w t (1)}={+1,+1} and {w t (0), w t (1)}={+1, -1}, thus being orthogonalized using TD-OCC. Thus, antenna ports 1000-1007 (or 1000-1011) corresponding to dual symbol DMRS are orthogonalized using FD-OCC, TD-OCC and FDM.

[0139] For CP-OFDM only, the following is being studied: specifying (without increasing DMRS overhead) a greater number of orthogonal DMRS ports for DL / UL MU-MIMO, setting a common design between DL and UL DMRS, a maximum of 24 orthogonal DMRS ports, and doubling the maximum number of orthogonal DMRS ports for each applicable DMRS configuration type for both single-symbol DMRS and dual-symbol DMRS.

[0140] In Rel.15, the following scenarios 1 through 4 can be set.

[0141] [Scenario 1] DMRS setting type 1 single-code DMRS

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

[0143] [Scenario 2] DMRS setting type 1 dual-symbol DMRS

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

[0145] [Scenario 3] DMRS setting type 2 single-code DMRS

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

[0147] [Scenario 4] DMRS setting type 2 dual-symbol DMRS

[0148] The total number of DMRS ports is 3 (comb-based) × 2 (FD OCC-based) × 2 (TD OCC-based) = 12 ports.

[0149] In Rel.18, it is being studied that for cases 1, 2, 3, and 4, the total number of DMRS ports will be increased to twice that of 8, 16, 12, and 24, respectively.

[0150] To increase the number of DMRS ports, the following 5 options (methods to increase the number of DMRS ports) are being explored.

[0151] <Option 1>

[0152] • Import a new OCC that is longer than the existing OCC (e.g., 4 or 6).

[0153] Option 1 lists the potential for performance degradation under conditions of large latency expansion, the possibility of scheduling limitations, and backward compatibility as research projects.

[0154] <Option 2>

[0155] • Utilization of TD-OCC on multiple discontinuous DMRS symbols (e.g., TD-OCC on front-loaded DMRS / additional DMRS).

[0156] Option 2 lists the following as research items: the possibility of performance degradation when the UE speed is high, the possibility of scheduling limitations (e.g., frequency hopping application methods), the possibility of DMRS settings being limited (e.g., the number of additional DMRS is limited), and backward compatibility.

[0157] <Option 3>

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

[0159] Option 3 cites the possibility of performance degradation and backward compatibility as research projects.

[0160] <Option 4>

[0161] • Reuse the symbols of the appended DMRS and add orthogonal DMRS ports.

[0162] Option 4 lists the possibility of performance degradation when the UE speed is high, the possibility of DMRS settings being limited (e.g., the number of additional DMRS is limited), and backward compatibility as research items.

[0163] <Option 5>

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

[0165] Option 5 lists the following as research items: the possibility of performance degradation when the UE speed is high, the possibility of scheduling limitations (e.g., frequency hopping application methods), the possibility of DMRS settings being limited (e.g., the number of additional DMRS is limited), and backward compatibility.

[0166] In Option 1, the new FD-OCC for DMRS of PDSCH / PUSCH for DMRS extension type 1 may also follow at least one of the following options.

[0167] <<Option 1-1>> Apply a new FD-OCC of length 6 to the 6RE of the DMRS within a PRB in a CDM group.

[0168] <<Options 1-2>> Within a CDM group, apply a new FD-OCC of length 4 to the 4RE of the DMRS within a PRB or across multiple consecutive PRBs.

[0169] In Option 1, the new FD-OCC used for the DMRS of PDSCH / PUSCH for DMRS extension type 2 applies a new FD-OCC of length 4 to the 4RE of the DMRS within a PRB of a CDM group. A new FD-OCC of length 6 is also supported for DMRS extension type 2.

[0170] In this disclosure, it is also possible to have an existing FD-OCC#0 = [+1 +1] or an existing FD-OCC#1 = [+1 -1].

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

[0172] [OCC1-1]

[0173] Based on a 4x4 Walsh matrix (sequence) with an OCC of length 4. For an OCC index i = {0, 1, 2, 3}, four sequences are obtained.

[0174] [OCC1-2]

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

[0176] In OCC1-1 and OCC1-2, each of the first and second halves of OCC#0 and #1 of length 4 (and the OCCs corresponding to OCC indices 0 and 1) is the same as OCC#0 and #1 of length 2 (and the OCCs corresponding to OCC indices 0 and 1).

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

[0178] A portion of multiple sequences of the new FD-OCC can also be associated with the Rel.15 DMRS port index.

[0179] When using an FD-OCC with a length of 2, the Rel.15 DMRS port table for DMRS configuration type 1 and the Rel.15 DMRS port table for DMRS configuration type 2 can also be used.

[0180] Extended DMRS Setting Type 1 uses the frequency domain configuration of DMRS Setting Type 1 and the new FD-OCC. Extended DMRS Setting Type 2 uses the frequency domain configuration of DMRS Setting Type 2 and the new FD-OCC.

[0181] In this disclosure, DMRS setting type 1, DMRS type 1, DMRS type = 1, and DMRS Type 1 can be interchanged. In this disclosure, DMRS setting type 2, DMRS type 2, DMRS type = 2, and DMRS Type 2 can also be interchanged.

[0182] In this disclosure, Extended DMRS Setting Type 1, DMRS Extended Type 1, DMRS Extended Type = 1, DMRS eType 1, and Rel.18DMRS Type 1 can also be overridden with each other. In this disclosure, Extended DMRS Setting Type 2, DMRS Extended Type 2, DMRS Extended Type = 2, DMRS eType 2, and Rel.18DMRS Type 2 can also be overridden with each other.

[0183] In this disclosure, the maximum length of DMRS and maxLength can be rewritten interchangeably.

[0184] In this disclosure, there are existing FD-OCCs, FD-OCCs with a length of 2, Rel.15 FD-OCCs, and w f (k') can also be rewritten. In various implementations, the new FD-OCC, the FD-OCC longer than 2, the Rel.18 FD-OCC, and w f (k') can also be rewritten.

[0185] The Rel.18 DMRS port table can also represent DMRS ports corresponding to the new FD-OCC (p is 0 or higher). At least some of the p values ​​in the Rel.18 DMRS port table can also be duplicates of the p values ​​in the Rel.15 DMRS port table. The UE can use the Rel.18 DMRS port table when the new FD-OCC is configured / indicated, and can use the Rel.15 DMRS port table when the new FD-OCC is not configured / indicated.

[0186] For DMRS ports of DMRS extension type 1 that come with new FD-OCC#0, 1, the same DMRS port indices (DMRS ports 0 to 7) as those for Rel.15 DMRS ports can also be used. For DMRS ports that come with new FD-OCC#2, 3, different DMRS port indices (DMRS ports 8 to 15) than those for Rel.15 DMRS ports can also be used.

[0187] For DMRS ports of DMRS extension type 2, which are accompanied by new FD-OCC#0 and 1, the same DMRS port indices (DMRS ports 0 to 11) as those for Rel.15 DMRS ports can also be used. For DMRS ports accompanied by new FD-OCC#2 and 3, different DMRS port indices (DMRS ports 12 to 23) as those for Rel.15 DMRS ports can also be used.

[0188] (analyze)

[0189] Since waveform settings were previously performed via Radio Resource Control (RRC), RRC reconstruction was required to switch waveforms. This led to concerns about increased signaling overhead and reduced communication throughput. Therefore, as mentioned above, waveform switching can be easily (and quickly) implemented by dynamically switching the PUSCH transform precoder (based on DCI / MAC CE switching). However, in this case, as shown in issues 0-4 below, there are ambiguities regarding various settings / controls.

[0190] Therefore, the inventors of this invention conceived of a way to appropriately and dynamically switch the deactivation and activation (waveform switching) terminals of the transform precoder for PUSCH.

[0191] (Various rewrites, etc.)

[0192] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The wireless communication methods involved in each embodiment can be applied individually or in combination.

[0193] In this disclosure, "A / B" and "at least one of A and B" may be rewritten as each other. In addition, in this disclosure, "A / B / C" may also mean "at least one of A, B and C".

[0194] In this disclosure, terms such as notification, activation, deactivation, indication (or indication), selection, configuration, update, and determination can be overridden. Similarly, terms such as support, control, ability to control, operation, and ability to operate can also be overridden.

[0195] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-level parameters, fields, Information Elements (IE), settings, etc., can also be modified interchangeably. In this disclosure, Medium Access Control (MAC) elements (MAC ControlElement (CE)), update commands, activation / deactivation commands, etc., can also be modified interchangeably.

[0196] In this disclosure, higher-level signaling may be, for example, any one or a combination of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, etc.

[0197] In this disclosure, MAC signaling may also use, for example, a MAC Control Element (MACCE) or a MAC Protocol Data Unit (PDU). Broadcast information may also be, for example, a Master Information Block (MIB), a System Information Block (SIB), a Minimum System Information (Remaining Minimum System Information (RMSI)), or Other System Information (OSI).

[0198] In this disclosure, physical layer signaling may also be, for example, downlink control information (DCI), uplink control information (UCI), etc.

[0199] In this disclosure, "having the ability to..." can also be interchanged with "the ability to support / report...".

[0200] In this disclosure, ceil(x), the ceiling function, and the ceiling function can be rewritten interchangeably. In this disclosure, floor(x), the floor function, and the floor level function can also be rewritten interchangeably. In this disclosure, sqrt(x) and the square root (radical) can also be rewritten interchangeably. In this disclosure, x mod y, mod(x,y), the mod function, and the modulo operation can also be rewritten interchangeably. In this disclosure, Σ... i=M N f(i), the summation of f(i) across i = M, M+1, ..., N, and f(M) + f(M+1) + ... + f(N) can also be rewritten. C(n,k) can also be used with the combinational coefficient and binomial coefficients of the number of combinations of k values ​​chosen from n values. n C k C n k Mutual rewriting.

[0201] In this disclosure, a b a, a_b, and the addition of the marker b to the lower right of a can also be interchanged. In this disclosure, a c a^c, and adding a 'c' to the upper right of 'a' can also be interchanged. In this disclosure, a b c The notations a_b^c, a_b^c, and a_b^c with b appended to the lower right and c appended to the upper right can also be interchanged. In this disclosure, x ~ A tilde (~) can be appended to x to represent a wavy line (x tilde). In this disclosure, x - It can be represented by appending a hyphen (-) above x, and can also be called an x ​​bar.

[0202] In this disclosure, the frequency range corresponding to FR1 can also be 410-7125MHz. In this disclosure, FR2 can include FR2-1 and FR2-2, the frequency range corresponding to FR2-1 can be 24250-52600MHz, and the frequency range corresponding to FR2-1 can also be 52600-71000MHz.

[0203] In this disclosure, the application / use of CP-OFDM and the disable (deactivated) of the transform precoder can also be rewritten. The application / use of DFT-s-OFDM and the enable (activated) of the transform precoder can also be rewritten. The deactivation / activation of the transform precoder, the switching of the transform precoder, and the switching waveform (CP-OFDM / DFT-s-OFDM) can also be rewritten. The PUSCH waveform, the waveform, and the transform precoder can also be rewritten. CP-OFDM and CP-OFDM waveforms can also be rewritten. DFT-s-OFDM and DFT-s-OFDM waveforms can also be rewritten. Enable and on can also be rewritten. Disable and off can also be rewritten.

[0204] In this disclosure, the PUSCH waveform can be dynamically switched, the PUSCH waveform can be set to be dynamically switched, the DWS can be set, and the DWS can be enabled, which can also be rewritten.

[0205] In this disclosure, the DMRS type, the DMRS type within the uplink DMRS configuration (dmrs-Type within DMRS-UplinkConfig), and the DMRS configuration type can be interchanged. In this disclosure, DMRS type 1, which is for 1 RB in the frequency domain and can configure DMRS to 6 REs, can also be interchanged. In this disclosure, DMRS type 2, which is for 1 RB in the frequency domain and can configure DMRS to 4 REs, can also be interchanged.

[0206] In this disclosure, DMRS Type 1 and Extended DMRS Type 1 (Enhanced DMRS Type 1, DMRS-eType 1) can also be rewritten in relation to each other. Similarly, DMRS Type 2 and Extended DMRS Type 2 (Enhanced DMRS Type 2, DMRS-eType 2) can also be rewritten in relation to each other. In other words, implementations applicable to DMRS Type 1 and 2 can also be applied to DMRS Type 1 and 2.

[0207] In the DCI format 0_X disclosed herein, X can be 0 / 1 / 2 / 3, or a combination of numbers and letters.

[0208] 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 can also be overridden.

[0209] In this disclosure, the second field, the DWS field, the DWS indicator, the DWS indicator, and the DWS indicator can also be overridden.

[0210] In this disclosure, at least one of the following fields may be overwritten: the third field, the specific field, the specific DCI field, the DMRS sequence initialization, the PTRS-DMRS association, the antenna port, and the TPMI (precoding information and layer number).

[0211] In this disclosure, the DWS setting, the 'enabled' DWS setting, and the higher-level parameters dynamicTransformPrecoderIndicationDCI-0-1 / dynamicTransformPrecoderIndicationDCI-0-2 can be interchanged. In this disclosure, the DWS indicator, the DWS indicator within the DCI, the DWS field, and the transform precoder indicator field can also be interchanged. In this disclosure, the DWS indicator with a bit value of 0, the transform precoder enabled indicator, and the DFT-s-OFDM indicator can also be interchanged. In this disclosure, the DWS indicator with a bit value of 1, the transform precoder disabled indicator, and the CP-OFDM indicator can also be interchanged.

[0212] (Wireless communication method)

[0213] As described above, the UE can also receive a setting indicating that the transform precoder for the PUSCH is dynamically switched via the DCI / MAC CE for deactivation or activation. Then, the UE can also receive an indication via the DCI / MAC CE indicating that the transform precoder for the PUSCH is activated or deactivated. That is, the UE can also dynamically switch the PUSCH waveform. In this case, at least one of the following several implementation methods can be applied.

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

[0215] <Problem Point X0>

[0216] Even with the ability to dynamically switch PUSCH waveforms, the values ​​for the RRC parameters `transformPrecoder` and `maxRank` are not yet clearly defined. For example, for `transformPrecoder`, it is expected to correspond to a value that is valid (i.e., DFT-s-OFDM), invalid (i.e., CP-OFDM), or unrestricted. However, since the setting of the RRC parameter `transformPrecoder` affects the DCI value, which in turn affects the UE's processing load and communication overhead, it is preferable to define it explicitly.

[0217] <Implementation Method X0.1>

[0218] When the UE can dynamically switch the PUSCH waveform, any of the following settings can be applied to the RRC parameter transformation precoder.

[0219] [Method 1]

[0220] When the PUSCH waveform can be dynamically switched, the RRC parameter transformPrecoder can also be enabled. This reduces the DCI size desired by the UE. In other words, since the NW (base station, gNB) can set a smaller DCI size, communication overhead can be suppressed.

[0221] [Method 2]

[0222] When the PUSCH waveform can be dynamically switched, the RRC parameter transformPrecoder can also be set to disabled. Therefore, even if the PUSCH waveform is switched to DFT-s-OFDM, the UE's processing load can be reduced because the UE is designed to have the same DCI size as CP-OFDM.

[0223] [Method 3]

[0224] When the PUSCH waveform can be dynamically switched, the RRC parameter transformPrecoder can also be ignored. In other words, the limitation of transformPrecoder can also be eliminated.

[0225] Figure 3This is a flowchart illustrating an example of the processing in implementation X0.1. When the UE receives a setting indicating that dynamic switching of the PUSCH waveform is possible (step S101), it receives the RRC parameter transformPrecoder, which is set to be valid / invalid (step S102).

[0226] As an RRC parameter, although there are multiple transformPrecoders, the transformPrecoder referenced by the UE can be different for each case (each timing). For example, options 1 and 2 below can also be applied. In the case of dynamic switching of the PUSCH waveform being set, the processing of options 1 and 2 below can also be applied at the timing before the dynamic switching indication of the PUSCH waveform.

[0227] [Option 1]

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

[0229] [Option 2]

[0230] Regardless of the type of PUSCH, the UE can also refer to / consider the transformPrecoder within a specific RRC IE (e.g., msg3-transformPrecoder of RACH-ConfigCommon, etc.). This option can also be applied to the UE prior to dedicated (UE-specific) RRC settings.

[0231] According to this embodiment, for the RRC parameter transformPrecoder that can dynamically switch the PUSCH waveform, the set value and the UE operation can be clearly defined.

[0232] <Implementation Method X0.2>

[0233] When the UE can dynamically switch the PUSCH waveform, the UE can also receive a value / setting based on any of the following methods / options as the maximum rank (maxRank) of the RRC parameter. That is, for the value / setting of maxRank, the UE can also envision the application of any of the following methods / options. maxRank is a parameter representing the maximum value of the transmission rank (layer) of the UL (PUSCH). The UE controls the transmission of PUSCH based on maxRank.

[0234] [Method 1]

[0235] The setting of maxRank can also be unrestricted. That is to say, even when setting dynamic switching of the PUSCH waveform, any value can be set for maxRank.

[0236] [Method 2]

[0237] For maxRank, a specific value or a value less than a specific value can also be set. The specific value can be determined by the specification (fixed). Alternatively, the specific value can be set / indicated via RRC / MAC CE / DCI. For example, when dynamic switching of the PUSCH waveform is set, maxRank (the specific value) can also be 1.

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

[0239] Figure 4 This is a flowchart illustrating an example of the processing in implementation method X0.2. Figure 4 An example of the above method 2 is shown. When the UE receives a setting indicating that dynamic switching of the PUSCH waveform is possible (step S201), it receives a setting indicating a specific value or a value less than a specific value as the value of the RRC parameter maxRank (step S202).

[0240] According to this embodiment, the RRC parameter maxRank can be explicitly set to a value when the PUSCH waveform can be dynamically switched.

[0241] <Problem Point X1>

[0242] It is still unclear how to handle the DCI field, which has a presence (more than 1 bit) and a non-existence (0 bit) depending on the PUSCH waveform, when the PUSCH waveform can be dynamically switched. This DCI field could be, for example, PTRS-DMRS association and DMRS sequence initialization.

[0243] Figure 5This is a diagram representing the definitions of PTRS-DMRS association and DMRS sequence initialization for DCI fields. (Example) Figure 5 As shown, 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, DMRS sequence initialization is 0 bits; otherwise, it is 2 bits. When DFTS-OFDM is applied, DMRS sequence initialization is 0 bits; when CP-OFDM is applied, DMRS sequence initialization is 1 bit.

[0244] <Implementation Method X1>

[0245] When the PUSCH waveform can be dynamically switched, and a specific waveform is indicated for the PUSCH, the UE can also process (ideally) specific fields of the PUSCH scheduling DCI based on specific rules.

[0246] The specific fields of DCI can also be at least one of the following: DeModulation Reference Signal (DMRS) sequence initialization field and Phase Tracking Reference Signal (PTRS)-DMRS association field.

[0247] Specific rules can also be used to allow the UE to ignore specific fields of the DCI.

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

[0249] For example, when the UE receives the DCI, it can dynamically switch the PUSCH waveform, and when the PUSCH is indicated to be DFT-s-OFDM, it ignores at least one of the DMRS sequence initialization field and the PTRS-DMRS association field of the DCI.

[0250] Not limited to the examples above, it could also be that, when the following conditions are met... Figure 5 If the DMRS sequence initialization field or the PTRS-DMRS association field is 0 bits, the UE ignores this field. This reduces the processing load on the UE.

[0251] In implementation X1, when the PUSCH waveform is dynamically switched, regardless of the correct waveform used by the UE, the number of bits per DCI field / the overall size of the DCI follows the rules for CP-OFDM. Alternatively, the number of bits per DCI field / the overall size of the DCI may not follow the rules for CP-OFDM.

[0252] <Problem Point X2>

[0253] As explained above (FDRA type), since type 0 RA cannot be used for DFT-s-OFDM, type 1 or type 2 must be used when the PUSCH waveform is switched to DFT-s-OFDM. For example, the RRC parameter representing the PUSCH waveform preferably always corresponds to the setting / indication of type FDRA. However, it is not yet clear what the setting of FDRA and the useInterlacePUCCH-PUSCH indication should be when the PUSCH waveform is dynamically switched.

[0254] <Implementation Method X2>

[0255] With the ability to dynamically switch PUSCH waveforms, and given that a specific waveform is indicated for the PUSCH, the UE can also receive specific fields of the DCI and specific RRC parameters corresponding to the PUSCH scheduling based on specific rules (it is also conceivable that the specific fields of the DCI and specific RRC parameters can be received). The UE can also control PUSCH transmission based on the specific fields of the received DCI and specific RRC parameters.

[0256] Specific fields of DCI can be FDRA or frequency hopping flag.

[0257] Specific RRC parameters can also be resource allocation, or useInterlacePUCCH-PUSCH instructions.

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

[0259] The specific rule can also be either resourceAllocation set to resourceAllocationType1 or dynamicSwitch. When resourceAllocation is set to dynamicSwitch, the most significant bit (MSB) of the FDRA must be "1". That is, it must indicate FDRA type 1. This specific rule can be applied if useInterlacePUCCH-PUSCH is not set.

[0260] A specific rule can also be that resourceAllocation is resourceAllcationType1.

[0261] The specific rules may also be that the frequency hopping flag follows at least one of the resource allocation and FDRA rules based on the specific rules mentioned above.

[0262] Specific rules can also be set to enabled (enabled: enabled) for the use of interlace PUCCH and PUSCH.

[0263] [Specific example]

[0264] For example, when the PUSCH waveform can be dynamically switched, and the PUSCH is indicated with DFT-s-OFDM, the UE can also receive (and can be assumed to receive) dynamic switch indication as resource allocation setting information (RRC parameters) and indication type 1 as FDRA indication information (DCI). The UE can also control PUSCH transmission based on this setting information and indication information.

[0265] For example, when the PUSCH waveform can be dynamically switched, and the PUSCH is indicated with DFT-s-OFDM, the UE can also receive (and can be assumed to receive) indication type 1 (resourceAllcationType 1) as resourceAllocation setting information (RRC parameter). The UE can also control PUSCH transmission based on this setting information.

[0266] For example, when the PUSCH waveform can be dynamically switched, and DFT-s-OFDM is indicated for the PUSCH, the UE can also receive (and can be conceived of receiving) a setting information indicating that useInterlacePUCCH-PUSCH (the interleaving of PUCCH and PUSCH) is enabled. The UE can also control PUSCH transmission based on this setting information.

[0267] Figure 6 This diagram illustrates an example of the setting modes for useInterlacePUCCH-PUSCH, resourceAllocation, and RA type. It shows how dynamic waveform switching is possible. Figure 6 The setting mode shown can also be applied to the following (1) and (2).

[0268] (1) Alternatively, when the default value of transformPrecoder is invalid (CP-OFDM is indicated / used), the UE can expect any mode, but when it is valid (DFT-s-OFDM is indicated / used), modes 1-1 and 1-3 cannot be applied.

[0269] (2) Alternatively, if the default value of transformPrecoder is valid, the UE can expect modes other than mode 1-1 and 1-3 of DCI with application representation type 0, but expect any mode if CP-OFDM is indicated / used.

[0270] The processing described in this embodiment can also be applied regardless of the waveform indicated for the PUSCH. That is, when the PUSCH waveform can be dynamically switched, the UE can also perform control based on the specific rules for the specific fields of the DCI corresponding to the PUSCH scheduling and the specific RRC parameters mentioned above.

[0271] According to this embodiment, even when the PUSCH waveform is dynamically switched, it is possible to avoid erroneous situations (e.g., FDRA set to type 0 when DFT-s-OFDM is applied).

[0272] <Problem Point X3>

[0273] It is unclear what types of PUSCHs can be applied when dynamically switching PUSCH waveforms is possible. For example, it is unclear whether message 3 (Msg3) or message A (msg3-TransformPrecoder / msgA-TransformPrecoder) can be used as this PUSCH. Furthermore, it is unclear whether CG-PUSCH (ConfiguredGrantConfig's transformPrecoder) can be used as this PUSCH. Moreover, it is unclear how to handle situations where dynamically switching PUSCH waveforms is supported for these PUSCHs.

[0274] <Implementation Method X3>

[0275] The UE can also apply dynamic switching of the PUSCH waveform only to a specific type of PUSCH. That is, the UE can also control the dynamic switching of the PUSCH waveform upon receiving a setting indicating dynamic switching of the PUSCH waveform so that dynamic switching is performed only for a specific type of PUSCH based on DCI / MAC CE. The specific type of PUSCH can be, for example, at least one of the following (1) to (4).

[0276] (1) DCI Grant (DG) - PUSCH (PUSCH scheduled via DCI).

[0277] (2) Type 1 Configuration Grant (CG) - PUSCH (sent via higher-level signaling configured PUSCH).

[0278] (3) Type 2 CG-PUSCH (PUSCH sent by being set via higher layer signaling and activated / deactivated via DCI).

[0279] (4) The PUSCH scheduled via a Random Access Response (RAR) (Message 3 PUSCH or Message A PUSCH). This RAR can also be a Contention-based Random Access (CBRA) RAR or a Contention-Free Random Access (CFRA) RAR. For example, in CFRA, since the base station (gNB) knows the UE and its channel state, it can adjust the waveform appropriately.

[0280] Figure 7This is a flowchart illustrating an example of the processing in implementation X3. When the UE receives a setting indicating that dynamic switching of the PUSCH waveform is possible (step S301), it controls the system to perform dynamic switching based on DCI / MAC CE only for waveforms of a specific type of PUSCH (step S302).

[0281] <Implementation Method X4.1>

[0282] Alternatively, dynamic switching of the CG-PUSCH waveform (transmitted via PUSCH configured by higher-layer signaling) of application type 1 can be performed, supporting at least one of the methods (1-1) to (1-4) below. As a specific method of (1-1) to (1-4) below, the method described above (dynamic switching of deactivation and activation of the transformation precoder) can also be applied.

[0283] (1-1) The UE may also receive explicit DCI-based indications (explicit signaling) indicating whether the transformPrecoder is valid or invalid (DFT-s-OFDM / CP-OFDM).

[0284] (1-2) The UE can also receive DCI-based implicit indications (implicit signaling) indicating the validity / invalidity of the transformPrecoder (DFT-s-OFDM / CP-OFDM).

[0285] (1-3) The UE may also receive explicit indications (explicit signaling) based on MAC CE indicating whether the transformPrecoder is valid or invalid (DFT-s-OFDM / CP-OFDM).

[0286] (1-4) The UE may also receive implicit indications (implicit signaling) based on MAC CE indicating the validity / invalidity of the transformPrecoder (DFT-s-OFDM / CP-OFDM).

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

[0288] For the conventional Type 1 CG-PUSCH, DCI is not used in scheduling. Therefore, when (1-1) and (1-2) above are applied, it is preferable to redefine DCI. For example, as the DCI in (1-1) and (1-2) above, either (2-1) or (2-2) below can also be applied.

[0289] (2-1) DCI can also be used to schedule unicast data of UL / DL. In addition, the UL / DL-SCH scheduled by DCI may not actually exist.

[0290] (2-2) DCIs can also be applied to scheduling other than unicast data. For example, the DCI can also be applied when using a group common DCI.

[0291] According to this embodiment, it is possible to clearly understand the processing when dynamic switching of the CG-PUSCH waveform of type 1 is applied.

[0292] <Implementation Method X4.2>

[0293] Alternatively, dynamic switching of the CG-PUSCH waveform (PUSCH transmission that is set by higher-layer signaling and activated / deactivated by DCI) of application type 2 can be supported, supporting at least one of the methods (1-1) to (1-4) of implementation method X4.1.

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

[0295] Since the DCI used for activation / deactivation was used in the previous Type 2 CG-PUSCH, this DCI can also be reused. Specifically, as the DCIs (1-1) and (1-2) above, either (2-1) or (2-2) below can also be applied.

[0296] (2-1) A DCI that schedules unicast data for UL / DL can also be applied. Furthermore, the UL / DL-SCH scheduled by the DCI may not actually exist. For example, a DCI that performs activation / deactivation of type 2 CG-PUSCH can also be applied.

[0297] (2-2) DCIs can also be applied to scheduling other than unicast data. For example, the DCI can also be applied when using a group common DCI.

[0298] According to this embodiment, it is possible to clearly understand the processing when dynamic switching of the CG-PUSCH waveform of type 2 is applied.

[0299] <Implementation Method X5>

[0300] Alternatively, dynamic switching of the waveform of application message 3 / message A PUSCH (PUSCH scheduled via random access response (RAR)) can be used, supporting at least one of the methods in implementation X4.1 (1-1) to (1-4). Alternatively, the following (1-5) can also be applied.

[0301] (1-5) The UE may also receive explicit / implicit RAR-based indications of whether the transformPrecoder is valid / invalid (DFT-s-OFDM / CP-OFDM).

[0302] For message 3 / message A PUSCH, methods (1-1) to (1-5) can also be applied separately from other types of PUSCH (type 1 / type 2 CG-PUSCH, DG-PUSCH). Alternatively, as with methods (1-1) to (1-5), the same methods as those for other types of PUSCH can be applied to message 3 / message A PUSCH.

[0303] Since the DCI used for activation / deactivation was used in the previous message 3 / message A PUSCH, it can be reused. Specifically, as the DCI in (1-1) and (1-2) above, either (2-1) or (2-2) below can also be applied.

[0304] (2-1) A DCI that schedules unicast data for UL / DL can also be applied. Furthermore, the UL / DL-SCH scheduled by the DCI may not actually exist. For example, the DCI could also be a DCI 1_0 with a Cyclic Redundancy Check (CRC) scrambled by the RA Radio Network Temporary Identifier (RNTI) or message B RNTI.

[0305] (2-2) DCIs can also be applied to scheduling other than unicast data. For example, the DCI can also be applied when using a group common DCI.

[0306] Regarding dynamic waveform switching for message 3 / message A PUSCH, at least one of the following (3-1) and (3-2) related to RAR-based indication can also be supported. The UE can also dynamically switch the waveform of message 3 PUSCH or message A PUSCH based on at least one of the MAC sub-header or MAC payload used for RAR.

[0307] (3-1) Alternatively, the reserved bits (R) in the MAC subheader / MAC payload used for RAR can be removed and used for dynamic waveform switching. For example, Figure 8 The "R" in the 1st octet of the MAC payload (i.e., adjacent to the Timing Advance Command) can also indicate dynamic waveform switching.

[0308] (3-2) can also be based on Figure 9 The existing RAR license field (UL Grant: UL License) shown implicitly indicates this. For example, it could also be that the Modulation and Coding Scheme (MCS) in the UL Grant indicates a specific MCS, setting the valid / invalid transformerPrecoder for message 3 / message A PUSCH. For example, it could also be the value corresponding to the TPC command for message 3PUSCH in the UL Grant ( Figure 9 , Figure 10 When the value is a specific value or is greater than / less than a specific threshold, the valid / invalid state of transformPrecoder is set for message 3 / message A PUSCH.

[0309] Alternatively, it could be the backoff parameter value corresponding to the Backoff Indicator (BI) field included in the MAC sub-header used for RAR. Figure 11The `transformPrecoder` is enabled / disabled for message 3 / message A PUSCH if the value is specific or greater / less than a specific threshold. Alternatively, the `transformPrecoder` is enabled / disabled for message 3 / message A PUSCH if the `Extension(E)` field, `Type(T)` field, and `Random Access Preamble IDentifier(RAPID)` field in the MAC sub-header used for RAR are specific.

[0310] This implementation can also be applied under specific conditions. One such condition is that the PRACH trigger for RAR is sent via a specific RA resource based on the RACH resource partition configuration.

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

[0312] <Problem Point X4>

[0313] In existing systems (e.g., prior to Rel. 17 NR), in the antenna port field contained in DCI format 0_1 / 0_2, DMRS type 2 (e.g., dmrs-Type=2) is not envisioned when the transform precoder is active (e.g., when DFT-S-OFDM is applied to a scheduled PUSCH) (see [reference]). Figure 12 DMRS type 2 is only considered / applied when the transformation precoder is invalid (e.g., when CP-OFDM is applied to a scheduled PUSCH).

[0314] When dynamic waveform switching is supported, waveform switching between CP-OFDM and DFT-S-OFDM can be performed according to the DCI instructions.

[0315] On the other hand, the type of PUSCH DMRS (dmrs-Type 1 or dmrs-Type 2) is set via RRC. In this case, for CP-OFDM, it is possible to set DMRS type 2 (or DMRS type 1) (as is the case with existing systems (e.g., prior to Rel. 17 NR)).

[0316] However, for DFT-S-OFDM, although DMRS type 2 cannot be set in the existing system, a situation can arise where DMRS type 2 is set for DFT-S-OFDM if dynamic waveform switching is set / supported. This is because DCI indications (e.g., waveform switching) are more dynamic than RRC setting changes (DMRS type setting).

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

[0318] <Implementation Method X6>

[0319] When dynamic waveform switching (DWS) is set, a specific DMRS type (dmrs-Type) for PUSCH DMRS can also be applied / set.

[0320] For example, when dynamic waveform switching is set, the UE can control the application of a specific DMRS type (e.g., DMRS type 1) regardless of the waveform indicated by DCI (CP-OFDM or DFT-S-OFDM) or the DMRS type set by RRC. This suppresses the increase in the combination of {waveform, DMRS type} that the UE needs to consider during PUSCH transmission. As a result, it suppresses the increase in implementation inconsistencies within the UE.

[0321] For the DMRS type (dmrs-Type) of PUSCH DMRS, the UE may also envision / apply at least one of the following options 6-1 to 6-2. Additionally, in this disclosure, the dynamic waveform switching setting can also be rewritten as dynamic waveform switching activation / activation.

[0322] [Option 6-1]

[0323] When dynamic waveform switching is set, as a DMRS type (dmrs-Type), it is also possible to set only type 1 (see reference). Figure 13 ).

[0324] The base station can also control the setting to assign only Type 1 as the DMRS type for PUSCH to the UE when dynamic waveform switching is configured. In other words, when dynamic waveform switching is configured, the setting of RRC-based DMRS Type 2 can also be restricted / disabled.

[0325] In this case, DMRS Type 1 can be applied regardless of the waveform indicated by DCI (CP-OFDM or DFT-S-OFDM). The UE can also control the application of DMRS Type 1 for either waveform (CP-OFDM and DFT-S-OFDM) when dynamic waveform switching is set. Furthermore, the UE can also assume / expect / determine that DMRS Type 1 is set for PUSCH DMRS when dynamic waveform switching is set.

[0326] When dynamic waveform switching is set, the setting of DMRS type for RRC-based PUSCH can also be omitted.

[0327] In this way, by setting only specific DMRS types, it is possible to suppress the increase in the combination of {waveform, DMRS type} that the UE needs to envision during PUSCH transmission. As a result, it is possible to suppress the increase in implementation inconsistencies in the UE.

[0328] [Option 6-2]

[0329] When dynamic waveform switching is set, as a DMRS type, it is also possible to support / allow settings for DMRS type 1 and DMRS type 2 (see [reference]). Figure 13 ).

[0330] The base station can also control the setting of DMRS type 1 or DMRS type 2 as the DMRS type for PUSCH to the UE when dynamic waveform switching is configured. In other words, even when dynamic waveform switching is configured, setting DMRS type 2 based on RRC is also allowed.

[0331] When DMRS type 2 is set and dynamic waveform switching is set, the UE can also interpret it as type 1 being set as the DMRS type for PUSCH (e.g., dmrs-Type). In other words, the UE can also ignore the setting of DMRS type 2 and apply DMRS type 1.

[0332] Thus, when dynamic waveform switching is set, DMRS type 1 can be applied regardless of the DMRS type set via RRC.

[0333] In this way, by setting the applied DMRS type to a specific DMRS type, it is possible to suppress the increase in the combination of {waveform, DMRS type} that the UE needs to envision during PUSCH transmission. As a result, it is possible to suppress the increase in implementation inconsistencies in the UE.

[0334] <Implementation Method X7>

[0335] Alternatively, when dynamic waveform switching (DWS) is set, for PUSCH DMRS, the DMRS type (dmrs-Type) to be applied is determined based on the waveform indicated by DCI.

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

[0337] The UE may also, when dynamic waveform switching is set and DFT-S-OFDM is indicated via DCI, envision / apply at least one of the following options 7-1 to 7-2 for the DMRS type (dmrs-Type) of PUSCH DMRS. The DCI used for indicating DFT-S-OFDM can also be the DCI used for PUSCH scheduling.

[0338] [Option 7-1]

[0339] Alternatively, when dynamic waveform switching is set and DFT-S-OFDM is indicated via DCI, only type 1 is applied / set as DMRS type.

[0340] The base station can also control the setting of DMRS type 1 as PUSCH to be assigned to the UE only when dynamic waveform switching is configured. In other words, when dynamic waveform switching is configured, the setting of DMRS type 2 based on RRC can also be restricted / disabled.

[0341] In this case, DMRS Type 1 can be applied regardless of the waveform indicated by DCI (CP-OFDM or DFT-S-OFDM). The UE can also control the application of DMRS Type 1 for either waveform (CP-OFDM and DFT-S-OFDM) when dynamic waveform switching is set. Furthermore, the UE can also assume / expect / determine that DMRS Type 1 is set for PUSCH DMRS when dynamic waveform switching is set.

[0342] When dynamic waveform switching is set, the setting of DMRS type for RRC-based PUSCH can also be omitted.

[0343] In this way, by setting only specific DMRS types, it is possible to suppress the increase in the combination of {waveform, DMRS type} that the UE needs to envision during PUSCH transmission. As a result, it is possible to suppress the increase in implementation inconsistencies in the UE.

[0344] [Option 7-2]

[0345] When dynamic waveform switching is set and DFT-S-OFDM is indicated via DCI, DMRS type 1 and DMRS type 2 settings can also be supported / allowed as DMRS type.

[0346] The base station can also control the setting of DMRS type 1 or DMRS type 2 as the DMRS type for PUSCH to the UE when dynamic waveform switching is configured. In other words, even when dynamic waveform switching is configured, setting DMRS type 2 based on RRC is also allowed.

[0347] When DMRS type 2 is set, dynamic waveform switching is set, and DFT-S-OFDM is indicated via DCI, the UE can also interpret it as type 1 being set as the DMRS type for PUSCH (e.g., dmrs-Type). In other words, the UE can also ignore the setting of DMRS type 2 and apply DMRS type 1 when DFT-S-OFDM is indicated via DCI.

[0348] On the other hand, when DMRS type 2 is set, dynamic waveform switching is set, and DFT-S-OFDM is not indicated via DCI (e.g., CP-OFDM is indicated), the UE can also interpret DMRS type 2 as being set as the DMRS type of PUSCH (e.g., dmrs-Type). That is, the UE can also apply DMRS type 2 even when DFT-S-OFDM is not indicated via DCI (e.g., CP-OFDM is indicated).

[0349] Thus, it is also possible to determine whether DMRS type 2 is applied based on the waveform indicated by the DCI when dynamic waveform switching is set and DMRS type 2 is set via RRC. Alternatively, it is also possible to control the application of DMRS type 1 regardless of the waveform indicated by the DCI when dynamic waveform switching is set and DMRS type 1 is set via RRC.

[0350] Therefore, when CP-OFDM is instructed via DCI, DMRS type 2 can be applied, thus allowing for flexible control over the type of DMRS applied based on the waveform.

[0351] <Implementation Method X8>

[0352] Alternatively, when dynamic waveform switching (DWS) is set and DMRS type 2 is set as the DMRS type (e.g., dmrs-Type), specific fields contained in the DCI (e.g., antenna port field) are interpreted based on specific rules.

[0353] When dynamic waveform switching is configured and DMRS type 2 is configured, the UE can also interpret specific fields contained in the DCI (e.g., antenna port field) based on specific rules. The DCI can also be a DCI used for PUSCH scheduling. Specific rules can also apply, for example, at least one of the following options 8-1 to 8-2.

[0354] [Option 8-1]

[0355] The bit width of the antenna port field can also be determined with reference to dmrs-Type being DMRS type 2 (that is, following the setting of dmrs-Type), but the UE can also interpret only a portion of the bits (or use a portion of the bits) to interpret the indication made by the antenna port field.

[0356] The number of bits in a portion can also be the same as the number of antenna port fields (or, number of bits / code points) set to type 2 for DMRS-Type 1. In this disclosure, a portion of bits / a portion of bits can also be rewritten as a portion of DCI code points / a portion of DCI code points.

[0357] In this case, the determination of the bit width of the antenna port field of the DCI and the interpretation of the antenna port field can also be different. That is, the bit width / code point number of the DCI antenna port field can also be determined based on DMRS type 2, and the interpretation of the DCI antenna port field can also be assumed to be DMRS type 1.

[0358] The number of DCI code points can also be the same as the number of antenna port fields (or, number of bits / code points) set to type 2 for dmrs-Type 1.

[0359] Therefore, when DMRS type 2 is set, the UE can properly interpret the antenna port field of the DCI even when DMRS type 1 is applied.

[0360] [Option 8-2]

[0361] Alternatively, the bit width of the antenna port field can be determined with respect to dmrs-Type being DMRS type 1 (that is, ignoring the setting of dmrs-Type), and the UE can interpret the indication made by the antenna port field with respect to dmrs-Type being DMRS type 1.

[0362] In this case, the determination of the bit width of the antenna port field of the DCI and the interpretation of the antenna port field can also be the same. That is, the bit width of the antenna port field of the DCI can also be determined based on DMRS type 1, and the interpretation of the antenna port field of the DCI can also be assumed to be DMRS type 1.

[0363] Therefore, when DMRS type 2 is set, and DMRS type 1 is used, both the bit width and interpretation of the antenna port field can be assumed to be handled by DMRS type 1. Furthermore, the increase in overhead of the antenna port field can be suppressed.

[0364] <Implementation Method X9>

[0365] When dynamic waveform switching (DWS) is set, DMRS type 2 is set as the DMRS type (e.g., dmrs-Type), and DFT-S-OFDM is indicated by DCI, specific fields contained in the DCI (e.g., antenna port field) can also be interpreted based on specific rules.

[0366] When dynamic waveform switching is configured, DMRS type 2 is configured, and DFT-S-OFDM is indicated via DCI, the UE can also interpret specific fields contained in the DCI (e.g., antenna port field) based on specific rules. The DCI can also be a DCI used for PUSCH scheduling. Specific rules can also be applied, for example, at least one of the following options 9-1 to 9-2.

[0367] [Option 9-1]

[0368] The bit width of the antenna port field is determined with reference to dmrs-Type being DMRS type 2 (that is, following the setting of dmrs-Type), but the UE may also interpret only a portion of the bits (or use a portion of the bits) to interpret the indication made by the antenna port field.

[0369] The number of bits in a portion can also be the same as the number of antenna port fields (or, number of bits / code points) set to type 2 for DMRS-Type 1. In this disclosure, a portion of bits / a portion of bits can also be rewritten as a portion of DCI code points / a portion of DCI code points.

[0370] In this case, the determination of the bit width of the antenna port field of the DCI and the interpretation of the antenna port field can also be different. That is, the bit width of the antenna port field of the DCI can also be determined based on DMRS type 2, and the interpretation of the antenna port field of the DCI can also be assumed to be DMRS type 1.

[0371] The number of DCI code points can also be the same as the number of antenna port fields (or, number of bits / code points) set to type 2 for dmrs-Type 1.

[0372] Therefore, even when DMRS type 2 is set and DFT-S-OFDM is indicated via DCI, the UE can properly interpret the antenna port field of DCI, even when DMRS type 1 is applied.

[0373] In addition, when DMRS type 2 is set and CP-OFDM is indicated by DCI, the determination of the bit width of the antenna port field of DCI and the interpretation of the antenna port field can also be based on DMRS type 2.

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

[0375] Example 1 of Antenna Port Field

[0376] When the DCI via the scheduling PUSCH is instructed to use DFT-S-OFDM, the bit width (or the number of bits in the field) can also be set to 3 bits. In this case, the UE can be interpreted in the same way as when Type 1 is set as the DMRS type (e.g., dmrs-Type). For example, only the 2-bit least significant bit (LSB) can be interpreted (see [reference]). Figure 14A ).

[0377] When a DCI not indicated via scheduling PUSCH is designated as DFT-S-OFDM (e.g., CP-OFDM is indicated), the bit width (or the number of bits in the field) can also be set to 3 bits. In this case, the UE can be interpreted in the same way as when Type 2 is set as the DMRS type (e.g., dmrs-Type). For example, it can also be interpreted using all 3 bits.

[0378] Example 2 of Antenna Port Field

[0379] When the DCI via the scheduling PUSCH is instructed to use DFT-S-OFDM, the bit width (or, the number of bits in the field) can also be set to 3 bits. In this case, the UE can also interpret the data using a specific number (in this case, 5) of the 8 code points generated using 3 bits. In this case, the remaining 3 code points / fields can also be set as reserved bits / reserved code points (see [reference]). Figure 14B ).

[0380] When the DCI is not indicated by the scheduling PUSCH to be DFT-S-OFDM (e.g., when CP-OFDM is indicated), the bit width (or the number of bits in the field) can also be set to 3 bits. In this case, the UE can also interpret the code points generated by the 3 bits (here, 8).

[0381] In this way, with dynamic waveform switching set, the determination / interpretation of the bit width of the antenna port field of the DCI can be flexibly controlled based on the waveform indicated by the DCI, thereby enabling appropriate PUSCH DMRS transmission.

[0382] [Option 9-2]

[0383] Alternatively, the bit width of the antenna port field can be determined with respect to dmrs-Type being DMRS type 1 (that is, ignoring the setting of dmrs-Type), and the UE can interpret the indication made by the antenna port field with respect to dmrs-Type being type 1.

[0384] In this case, the determination of the bit width of the antenna port field of the DCI and the interpretation of the antenna port field can also be the same. That is, the bit width of the antenna port field of the DCI can also be determined based on DMRS type 1, and the interpretation of the antenna port field of the DCI can also be assumed to be DMRS type 1.

[0385] Therefore, when DMRS type 2 is set and DFT-S-OFDM is indicated via DCI (for example, when DMRS type 1 is applied), it is conceivable that DMRS type 1 can be used for both the bit width and interpretation of the antenna port field. Furthermore, the increase in overhead of the antenna port field can be suppressed.

[0386] <Analysis A1>

[0387] The investigation is ongoing regarding the lack of support for DWS in Type 1 and Type 2 configured grant (CG) PUSCH, with support only in dynamic grant (DG).

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

[0389] In DCI format 0_1 ​​size alignment accompanied by CRC scrambled via C-RNTI or CS-RNTI, the following constraints must be satisfied:

[0390] - The bit width (size) of any field in DCI format 0_1 ​​(using C-RNTI) accompanied by CRC scrambling via C-RNTI is greater than the bit width of that field in DCI format 0_1 ​​(using CS-RNTI) accompanied by CRC scrambling via CS-RNTI. If the bit width of that field in DCI format 0_1 ​​using CS-RNTI is less than the bit width of that field in DCI format 0_1 ​​using C-RNTI, the bit width of that field in DCI format 0_1 ​​using CS-RNTI is made equal to the bit width of that field in DCI format 0_1 ​​using C-RNTI by padding that field with 0.

[0391] For DG-PUSCH and CG-PUSCH, there are separate DMRS settings. The PUSCH settings (DG-PUSCH, PUSCH-Config) can also include the uplink DMRS settings (DMRS-UplinkConfig) for dmrs-UplinkForPUSCH-MappingTypeA / dmrs-UplinkForPUSCH-MappingTypeB. The CG-PUSCH settings (ConfiguredGranConfig) can also include the uplink DMRS settings (DMRS-UplinkConfig) for cg-DMRS-Configuration.

[0392] 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, with the transform precoder invalid, DMRS type 1, and DMRS maximum length 1, the antenna port field size is 3 bits; with the transform precoder invalid, DMRS type 1, and DMRS maximum length 2, the antenna port field size is 4 bits. On the other hand, with the transform precoder invalid, DMRS type 2, and DMRS maximum length 1, the antenna port field size is 4 bits; with the transform precoder invalid, DMRS type 2, and DMRS maximum length 2, the antenna port field size is 5 bits.

[0393] <Problem Point A1>

[0394] In Rel.17, for PUSCH, simultaneous setting of DFT-s-OFDM and DMRS type 2 is not supported.

[0395] In DG-PUSCH, if DWS is set, the scheduling DCI carries a new 1-bit to indicate waveform switching. The issue of the setting possibility of DMRS type 2 is addressed in problem point 1 and implementation method X1.

[0396] DWS is not supported in type 2CG-PUSCH.

[0397] Type 2CG Activated DCI (Type 2CG-PUSCH Activated 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 the size of that field in Type 2CG-PUSCH Activated DCI.

[0398] When the DWS for DG-PUSCH is set, consider the following scenarios for the DMRS setting for Type 2CG-PUSCH:

[0399] - Scenario 1: If DWS is set and DMRS type 1 is set, it becomes a question whether there are constraints related to the DMRS type of CG-PUSCH.

[0400] - Scenario 2: If DWS is set and DMRS type 2 is set, it becomes a question whether there are constraints related to the DMRS type of CG-PUSCH.

[0401] <Implementation Method A1>

[0402] This implementation method involves problem point A1.

[0403] Alternatively, with DWS configured, DMRS type 1 can be set for both DG-PUSCH and CG-PUSCH. This setting eliminates the need for complex UE operations to interpret the DMRS type and determine the DCI size for DG and CG activations.

[0404] Example 1: The following operations can also be specified in the specification.

[0405] When dynamic waveform switching is configured, the UE expects dmrs-Type=1 to be set in both PUSCH-Config and ConfiguredGrantConfig (on the same serving cell / BWP).

[0406] Figure 15 This illustrates an example of the RRC IE described in implementation A1. In this example, the UE receives the DWS settings, dmrs-Type=1 in PUSCH-Config, and dmrs-Type=1 in ConfiguredGrantConfig.

[0407] Example 2: The following operations can also be specified in the specification.

[0408] When dynamic waveform switching is configured, the UE does not expect dmrs-Type=2 to be set in either PUSCH-Config or ConfiguredGrantConfig (on the same serving cell / BWP).

[0409] <Implementation Method A2>

[0410] This implementation method involves problem point A1.

[0411] When DWS is configured, DMRS type 1 or 2 can be configured for DG-PUSCH, and DMRS type 1 can be configured for CG-PUSCH. Based on this configuration, the UE does not need to read DWS bits to identify the size of the activated DCI for type 2 CG-PUSCH. Furthermore, flexible DMRS configuration is possible for DG-PUSCH.

[0412] Example 1: The following operations can also be specified in the specification.

[0413] When dynamic waveform switching is configured, the UE expects dmrs-Type=1 to be set in ConfiguredGrantConfig (on the same serving cell / BWP).

[0414] Example 2: The following operations can also be specified in the specification.

[0415] When dynamic waveform switching is configured, the UE does not expect dmrs-Type=2 to be set in ConfiguredGrantConfig (on the same serving cell / BWP).

[0416] <Implementation Method A3>

[0417] This implementation method involves problem point A1.

[0418] Alternatively, with DWS configured, DMRS type 1 or 2 can be set for both DG-PUSCH and CG-PUSCH. This setting allows for flexible DMRS configuration for both DG-PUSCH and CG-PUSCH.

[0419] - Implementation method A3-1

[0420] Alternatively, if the DWS field indicates DFT-s-OFDM and DMRS type 2 is set for DG-PUSCH, the UE interprets it as DMRS being set to DMRS type 1. According to this operation, the UE can follow existing implementations for DMRS. That is, DMRS type 2 can also be set only for CP-OFDM. This operation can also follow implementation method X7.

[0421] - Implementation method A3-2

[0422] Alternatively, if the DWS field in the DCI of the activated / deactivated type 2 CG-PUSCH indicates DFT-s-OFDM, and DMRS type 2 is set for CG-PUSCH, the UE interprets it as DMRS type 1. This operation allows maintaining the same DCI size for both DG and CG-PUSCH activation, while providing flexibility in DMRS settings.

[0423] Alternatively, if the DWS indicator in the DCI of the activation / deactivation type 2CG-PUSCH indicates transformation precoding, the UE interprets it as dmrs-Type in ConfiguredGrantConfig being equal to 1.

[0424] The following operations can also be specified.

[0425] -- UE does not expect type 2CG-PUSCH activation / deactivation. The DWS indicator in the DCI indicates that the transform precoding is valid.

[0426] <Problem Point A2>

[0427] As mentioned above, the specification does not consider DCI fields that have a non-zero bit width in the DCI accompanied by CRC scrambling via CS-RNTI and a zero bit width in the DCI accompanied by CRC scrambling via C-RNTI.

[0428] Future specifications may include new DCI fields with the following characteristics.

[0429] - In the case of an invalid transform precoder, its bit width is zero, and

[0430] - When the transform precoder is active, its bit width is non-zero.

[0431] The following situations are error scenarios, which can also be explicitly avoided.

[0432] - This new DCI field has been set for both DG-PUSCH and CG-PUSCH, and

[0433] - For DG-PUSCH, the transformation precoder is invalid, and

[0434] - For CG-PUSCH, the transformation precoder is effective.

[0435] <Problem Point A3>

[0436] In addition to issue A2, the DCI field size may differ based on the DWS indicator. Depending on the DWS indicator, the error scenario described in issue A2 may occur.

[0437] <Implementation Method A4>

[0438] This implementation method involves problem point A2.

[0439] In this disclosure, the DCI field that exists only in the scheduling of PUSCH accompanying DFT-s-OFDM, the DCI field that is 0 bits when the transform precoder is invalid and X (X>0) bits in other cases, the DCI field that has a non-zero bit width for DFT-s-OFDM and a zero bit width for CP-OFDM, the new DCI field, and the specific DCI field can also be rewritten to each other.

[0440] exist Figure 16 In the example, the DCI used for scheduling PUSCH accompanying DFT-s-OFDM includes a specific DCI field, while the DCI used for scheduling PUSCH accompanying CP-OFDM does not include a specific DCI field.

[0441] When the DCI field, which exists only in the scheduling of PUSCH accompanying DFT-s-OFDM, is set, the settings for the transform precoder for DG-PUSCH and the transform precoder for CG-PUSCH can also be the same. According to this setting, since the field size is the same between DG-PUSCH and CG-PUSCH, no additional DCI size alignment rules are required.

[0442] <Implementation Method A5>

[0443] This implementation method involves problem point A2.

[0444] The transform precoder for CG-PUSCH can also be disabled if the DCI field, which exists only in the scheduling of PUSCH accompanying DFT-s-OFDM, is set. According to this setting, since the field size is the same between DG-PUSCH and CG-PUSCH, no additional DCI size alignment rules are required.

[0445] <Implementation Method A6>

[0446] This implementation method involves problem point A2.

[0447] Alternatively, if the DCI field is set only in the scheduling of PUSCH accompanying DFT-s-OFDM, the field is not present in the DCI accompanying CRC scrambled via CS-RNTI. With this setting, since the field size is the same between DG-PUSCH and CG-PUSCH, no additional DCI size alignment rules are needed.

[0448] <Implementation Method A7>

[0449] This implementation method involves problem point A2.

[0450] Alternatively, if the DCI field is set only in the scheduling of PUSCH accompanying DFT-s-OFDM, and the transform precoder for DG-PUSCH is invalid, while the transform precoder for CG-PUSCH is valid, the bit width of this field is aligned between DG-PUSCH and CG-PUSCH based on specific rules.

[0451] This particular rule may also follow at least one of the following rules.

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

[0453] - The size of this field is aligned with the smaller of the sizes for DG-PUSCH and CG-PUSCH. For example, it is also possible that, for codepoints corresponding to the larger size, the number of codepoints is reduced to below the number of codepoints in the field with the smaller size by narrowing their range, decreasing their maximum value, increasing their minimum value, or thinning them. For example, it is also possible, similar to implementation X9 (option 9-1), to reduce the number of codepoints corresponding to the larger size.

[0454] - The size of this field is aligned with the size of the field in the DCI (DG-PUSCH scheduling DCI) that is accompanied by the CRC scrambled via C-RNTI.

[0455] - The size of this field is aligned with the size of the DCI (the DCI of CG-PUSCH activation / deactivation) that accompanies the CRC scrambled by CS-RNTI.

[0456] This operation enables flexible settings for the transformation precoder and DCI fields for DG-PUSCH and CG-PUSCH.

[0457] <Implementation Method A8>

[0458] This implementation method involves problem point A3.

[0459] The DCI field and DWS, which exist only in the scheduling of PUSCH accompanying DFT-s-OFDM, may not be set simultaneously.

[0460] The following operations can also be specified in the standard.

[0461] - The UE does not expect the DCI field and DWS to be set simultaneously for scheduling that only exists in the PUSCH accompanying DFT-s-OFDM.

[0462] With this setting, the DCI size alignment rules become simple.

[0463] <Implementation Method A9>

[0464] This implementation method involves problem point A3.

[0465] Alternatively, if the DCI field and DWS, which exist only in the scheduling of PUSCH accompanying DFT-s-OFDM, are set simultaneously, the transform precoder is set to invalid for CG-PUSCH.

[0466] With this setting, the DCI size alignment rules become simple.

[0467] <Implementation Method A10>

[0468] This implementation method involves problem point A3.

[0469] Alternatively, if the DCI field and DWS, which exist only in the scheduling of PUSCH accompanying DFT-s-OFDM, are set simultaneously, at least one of the following constraints may be applied.

[0470] - The DWS indicator may also simply represent CP-OFDM. The DWS indicator may also not represent DFT-s-OFDM. The following operations may also be specified in the specification.

[0471] -- The UE does not expect the DWS indicator to indicate that the transformation precoder is valid.

[0472] - The DWS indicator can also represent the same waveform as the waveform set for CG-PUSCH. The DWS indicator can also represent a waveform different from the waveform set for CG-PUSCH. The following operations can also be specified in the specification.

[0473] -- The UE does not expect the DWS indicator to indicate a different setting than the transformation precoder setting within the setting permission settings.

[0474] With this setting, the DCI size alignment rules become simple.

[0475] <Implementation Method A11>

[0476] This implementation method involves problem point A3.

[0477] Alternatively, if the DCI field and DWS, which exist only in the scheduling of PUSCH accompanying DFT-s-OFDM, are set simultaneously, the bit width of the field is aligned between DG-PUSCH and CG-PUSCH based on specific rules.

[0478] This particular rule may also follow at least one of the following rules.

[0479] - The size of this field is aligned to the larger of the sizes for DG-PUSCH and CG-PUSCH. For example, the MSB of a field with a smaller size can also be padded with bits having a value of '0'.

[0480] - The size of this field is aligned to the smaller of the sizes for DG-PUSCH and CG-PUSCH. For example, it is also possible that, for codepoints corresponding to the larger size, the number of codepoints is reduced to below the number of codepoints in the field with the smaller size by narrowing their range, decreasing their maximum value, increasing their minimum value, or thinning them. For example, it is also possible, similar to implementation X9 (option 9-1), to reduce the number of codepoints corresponding to the larger size.

[0481] - The size of this field is aligned to the size of the field in the DCI (DG-PUSCH scheduling DCI) that is accompanied by the CRC scrambled by C-RNTI.

[0482] - The size of this field is aligned to the size of the DCI (the DCI of CG-PUSCH activation / deactivation) that scrambles the CRC via CS-RNTI.

[0483] This operation enables flexible setting / instruction of the transformation precoder, as well as DCI fields for DG-PUSCH and CG-PUSCH.

[0484] <Multi-carrier DCI>

[0485] In Rel.18, a new DCI format is being researched to support scheduling of multiple PDSCHs across multiple CCs or multiple PUSCHs across multiple CCs.

[0486] The DCI format can also be at least one of the following.

[0487] - Schedule DCI format 0_X for multiple PUSCHs across multiple CCs.

[0488] - Schedule DCI format 1_X for multiple PDSCHs across multiple CCs.

[0489] Each DCI field in DCI format 0_X / 1_X can also be classified as at least one of the following types.

[0490] - Type 1

[0491] -- Type 1A: A single field within a DCI format. It indicates all common information for multiple CCs (all co-scheduled CCs). Figure 17A This is an example of DCI format 0_X for scheduling PUSCH type 1A. DCI format 1_X for scheduling PDSCH type 1A can also be the same as this example.

[0492] -- Type 1B: A single field within a DCI format. It indicates different information for different CCs via a joint instruction (indicating separate information for each of the multiple CCs that are jointly scheduled). Figure 17B This is an example of DCI format 0_X for scheduling PUSCH type 1B. DCI format 1_X for scheduling PDSCH type 1B can also be the same as this example.

[0493] -- Type 1C: A single field within a DCI format. It indicates information for only one of multiple co-scheduled CCs. Figure 18A This is an example of DCI format 0_X for scheduling PUSCH type 1C. DCI format 1_X for scheduling PDSCH type 1C can also be the same as this example.

[0494] - Type 2: Multiple fields within a DCI format. Each of these multiple fields (separate fields) independently indicates information for each CC. Figure 18B This is an example of DCI format 0_X for type 2 scheduling of PUSCH. DCI format 1_X for type 2 scheduling of PDSCH can also be the same as this example.

[0495] - Type 3: Depends on explicit settings, and can be any of the following: common for multiple co-scheduled CCs, individual for each of the multiple co-scheduled CCs, or individual for each subgroup. For example, either Type 1A or Type 2 can also be set. A subgroup contains a subset of multiple co-scheduled cells. Here, a single field is commonly applied to co-scheduled cells belonging to the same subgroup.

[0496] <Analysis B1>

[0497] The following questions can be considered.

[0498] - Q1: Does it support DWS indicated in DCI format 0_X?

[0499] - Q2: In the case of supporting DWS indicated in DCI format 0_X, how many bits are indicated for the purpose of DWS in DCI format 0_X?

[0500] Q3: How to handle RRC settings affected by precise waveforms when supporting DWS indicated in DCI format 0_X? RRC settings include, for example, transform precoder, maximum rank, FDRA type, DMRS type, etc.

[0501] The main point is that in the DCI size alignment for DCI format 0_1, the antenna port, TPMI, DMRS-PTRS association, DMRS sequence initialization, and frequency hopping flag can follow at least one of implementation methods X0 to X6, and the DMRS type can also follow at least one of implementation methods X7 to X9.

[0502] <Implementation Method B0>

[0503] For DCI format 0_X, DWS can be supported and configured. According to this embodiment, the waveform for PUSCH scheduled via DCI format 0_X can be dynamically selected based on the situation. The DWS for DCI format 0_X can also follow at least one of the following options.

[0504] - Option 1: Setting Method

[0505] For DWS settings in DCI format 0_X, at least one of the following options can also be followed.

[0506] -- Option 1-1: A separate new RRC parameter for DCI format 0_X. This parameter allows for independent settings related to the on / off state of DWS for each DCI format.

[0507] -- Option 1-2: Reuse / repurpose of RRC parameters for other purposes. No additional signaling is required based on this parameter. For example, RRC parameters for other purposes can also set the DWS on / off of at least one of DCI formats 0_1 and 0_2.

[0508] - Option 2

[0509] The number of bits used to indicate DWS can also follow at least one of the following options.

[0510] -- Option 2-1: 1 bit.

[0511] -- Option 2-2: N bits. Here, N can also be the number of cells being co-scheduled. A one-to-one mapping between bits and cells can also be applied.

[0512] -- Option 2-3: N1 bits. Here, it can also be 1 < N1 < N.

[0513] --- For example, N1 can also be the number of cells that are configured and jointly scheduled by DWS.

[0514] --- For example, N1 can also be the maximum number of cells co-scheduled in a cell combination. In this case, multiple cell combinations can also be set via RRC parameters.

[0515] --- For example, N1 can also be the maximum number of cells from a cell combination that are configured with DWS and jointly scheduled. In this case, multiple cell combinations can also be configured via RRC parameters.

[0516] <Implementation Method B1>

[0517] When DWS is set in DCI format 0_X, the RRC setting (transformPrecoder) of the transformation precoder can also follow at least one of the following methods.

[0518] - Method 1-1

[0519] For any of the cells being co-scheduled, this setting is "invalid". Based on this setting, the interpretation of the 1-bit DWS in DCI format 0_X becomes simple.

[0520] - Method 1-2

[0521] This setting is the same across all co-scheduled cells. This setting can also be either "invalid" or "valid". Based on this setting, the interpretation of the 1-bit DWS in DCI format 0_X becomes simple, enabling the use of both CP-OFDM and DFT-s-OFDM.

[0522] - Methods 1-3

[0523] This setting differs among the different cells included in a co-scheduled cell network. Depending on this setting, there are possibilities for maintaining the Rel.17 waveform for each cell.

[0524] According to this implementation, even when DWS is set in DCI format 0_X, the transformation precoder can be set appropriately.

[0525] <Implementation Method B2>

[0526] When DWS is set in DCI format 0_X, the maximum rank RRC setting (maxRank) can also follow at least one of the following methods.

[0527] - Method 2-1

[0528] This setting is the same across all cells that are jointly scheduled.

[0529] - Method 2-1a

[0530] This setting is '1' for all cells under joint scheduling.

[0531] - Method 2-2

[0532] The settings differ across cells that are jointly dispatched.

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

[0534] <Implementation Method B3>

[0535] When DWS is set in DCI format 0_X, the RRC setting (resource allocation) of FDRA type can also follow at least one of the following methods.

[0536] - Method 3-1

[0537] This setting is the same across all cells that are jointly scheduled.

[0538] - Method 3-1a

[0539] Across all co-scheduled cells, this setting is FDRA type 1 ('resourceAllocationType1').

[0540] - Method 3-1b

[0541] This setting enables dynamic handover across all co-scheduled cells.

[0542] - Method 3-1c

[0543] This setting applies to all cells that are co-scheduled, except for FDRA type 0 ('resourceAllocationType0').

[0544] - Method 3-2

[0545] The settings differ across all cells that are jointly dispatched.

[0546] - Method 3-3

[0547] This setting differs across all cells that are jointly scheduled, and is except for 'resourceAllocationType0'.

[0548] According to this implementation, the FDRA type can be appropriately set even when DWS in DCI format 0_X is set. Simultaneous setting of DFT-s-OFDM and FDRA type 0 is not required.

[0549] <Implementation Method B4>

[0550] When DWS is set in DCI format 0_X, the RRC setting (dmrs-Type) of DMRS type can also follow at least one of the following methods.

[0551] - Method 4-1

[0552] This setting is the same across all cells that are jointly scheduled.

[0553] - Method 4-1a

[0554] This setting is not set for any of the cells that are jointly scheduled. This also implies that DMRS type 1 is set for any of the cells that are jointly scheduled.

[0555] - Method 4-1b

[0556] For any of the cells that are jointly scheduled, this setting is not type 2.

[0557] - Method 4-2

[0558] The setting differs for all cells that are jointly dispatched.

[0559] According to this implementation, even when DWS is set in DCI format 0_X, the DMRS type can be set appropriately.

[0560] <Analysis B2>

[0561] For DCI format 0_X which includes the DWS field, how to achieve DCI size alignment becomes a problem. This DCI size alignment can also rely on at least one of the following guidelines. DCI fields that need to be considered for alignment may also be antenna port, TPMI, PTRS-DMRS association, DMRS sequence initialization, and frequency hopping flag.

[0562] The details of the DWS field within DCI format 0_X can also follow at least one of the following guidelines.

[0563] - Guideline 1: The DWS field in DCI format 0_X is 1 bit. This DWS field can also be type 1A.

[0564] - Guideline 2: The DWS field in DCI format 0_X is N (>1) bits. This DWS field can also be type 2.

[0565] - Policy 3: The DWS field in DCI format 0_X can be set between Policy 1 and Policy 2. In this case, the DWS field can also be type 3.

[0566] - Other guidelines: The DWS field in DCI format 0_X can also be of type 1B / 1C.

[0567] Implementation methods B0 to B4 can be applied regardless of whether policy 1 to 3 are followed.

[0568] Implementation methods B5 to B7 can also be based on policy 1.

[0569] Implementation methods B8 to B10 can also be based on policy 2.

[0570] <Implementation Method B5>

[0571] In the case where a 1-bit DWS field is set for DCI format 0_X ( Figure 19 The interpretation of a 1-bit indication can also follow at least one of the following methods.

[0572] - Method 5-1

[0573] For any of the co-scheduled cells, '0' indicates CP-OFDM (transform precoder invalid), and '1' indicates DFT-s-OFDM (transform precoder valid). According to this interpretation, complex waveform combinations are avoided across co-scheduled cells.

[0574] - Method 5-2

[0575] For any of the co-scheduled cells, '0' indicates the waveform set in the RRC parameters, and '1' indicates a waveform switch from the waveform set in the RRC parameters. Based on this interpretation, it is possible to switch waveforms using only 1 bit for all co-scheduled cells. This can be considered in conjunction with implementation method B1. For example, in mode 1-1, complex waveform indications can be avoided by restricting the transformation precoder to invalid.

[0576] - Method 5-3

[0577] For any of the co-scheduled cells, '0' indicates the waveform set in the RRC parameters for one of the co-scheduled cells, and '1' indicates a waveform switch from the waveform set in the RRC parameters for one of the co-scheduled cells. According to this interpretation, complex waveform combinations can be avoided across co-scheduled cells.

[0578] Alternatively, you can set only the cells that are valid for joint scheduling in DWS, using methods 5-1 / 5-2 / 5-3.

[0579] In methods 5-1 / 5-2 / 5-3, the interpretations of '0' and '1' can also be reversed.

[0580] In mode 5-3, one of the cells being jointly scheduled can be one of the following definitions, or a combination of two or more.

[0581] - The cell being dispatched.

[0582] - Reference cell for counting the size of blind decoding (BD) / control channel element (CCE) / DCI.

[0583] - The cell is set for the search space (SS) set for DCI format 0_X.

[0584] - The cell accompanied by the minimum or maximum serving cell index.

[0585] - Cells indicated via DCI.

[0586] - Cells configured via RRC IE.

[0587] - Cells indicated via MAC CE.

[0588] - The cell where DWS is set.

[0589] A combination of two or more definitions can also be, for example, a cell that is jointly scheduled and has a DWS set, accompanied by a minimum serving cell index.

[0590] exist Figure 20 In the example, the waveforms set by RRC 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.

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

[0592] In method 5-2, when the value of the DWS field is 0, CP-OFDM, DFT-s-OFDM, CP-OFDM, and CP-OFDM are used for the PUSCH of cell indices #0, #1, #2, and #3, 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 the PUSCH of cell indices #0, #1, #2, and #3, respectively.

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

[0594] According to this implementation, even if the DWS field in the DCI format 0_X is 1 bit, it is still possible to properly indicate the waveforms of multiple cells.

[0595] <Implementation Method B6>

[0596] When a 1-bit DWS field is set for DCI format 0_X, the existence of a specific DCI field within DCI format 0_X can also be based on a rule. This rule can also follow at least one of the following options.

[0597] - Option 1: The specific DCI field can also be at least one of the following options.

[0598] -- Option 1-1: DMRS sequence initialization.

[0599] -- Option 1-2: PTRS-DMRS association.

[0600] - Option 2: The rule can also be at least one of the following options.

[0601] -- Option 2-1: Specific DCI fields always exist.

[0602] -- Option 2-2: The specific DCI field does not exist at all.

[0603] -- Option 2-3: The specific DCI field of the co-scheduled cell always exists.

[0604] -- Option 2-4: For cells included in the co-scheduled cells and with DWS set, the specific DCI field always exists.

[0605] -- Option 2-5: Determine whether a specific DCI field exists based on the DWS bits for all co-scheduled cells. For example, if the DWS indicates CP-OFDM for all co-scheduled cells, the specific DCI field for all co-scheduled cells exists; otherwise, the specific DCI field does not exist.

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

[0607] <Implementation Method B7>

[0608] When a 1-bit DWS field is set for DCI format 0_X, the size (bit width) of a specific DCI field within DCI format 0_X can also be based on a rule. This rule can also follow at least one of the following options.

[0609] - Option 1: The specific DCI field can also be at least one of the following options.

[0610] -- Option 1-1: Antenna port.

[0611] -- Option 1-2: TPMI (Precoding Information and Number of Layers).

[0612] In options 1-1 / 1-2, the size of at least one of the first and second specific DCI fields can also be considered / determined. For example, the size of both the "Precoding Information and Layer Number" field and the "Second Precoding Information" field can also be considered / determined.

[0613] - Option 2: The rule may also follow at least one of the following options.

[0614] -- Option 2-1: Regardless of the RRC setting of the transformation precoder, this rule assumes that the transformation precoder is invalid (or valid) to determine the size of a specific DCI field.

[0615] -- Option 2-2: Regardless of the DWS indication content, this rule assumes that the transformation precoder is invalid (or valid) to determine the size of a specific DCI field.

[0616] -- Option 2-3: This rule determines the size of a specific DCI field based on the transform precoder set by RRC for a specific CC.

[0617] -- Option 2-4: This rule determines the size of a specific DCI field based on the transform precoder set by RRC for all co-scheduled cells. In this option, the transform precoder can also be common across multiple co-scheduled cells.

[0618] -- Option 2-5: This rule determines the size of a specific DCI field based on the DWS indication content.

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

[0620] <Implementation Method B8>

[0621] In the case where N bits of the DWS field are set for the DCI format 0_X of scheduling N CCs ( Figure 21 The interpretation of this N-bit indication can also follow at least one of the following methods.

[0622] - Method 8-1

[0623] Alternatively, for the corresponding cell, '0' indicates CP-OFDM (transform precoder invalid), and '1' indicates DFT-s-OFDM (transform precoder valid). According to this interpretation, complex waveform combinations can be avoided across co-scheduled cells.

[0624] - Method 8-2

[0625] Alternatively, for the corresponding cell, '0' indicates the waveform set in the RRC parameters, and '1' indicates a waveform switch from the waveform set in the RRC parameters. This scenario can be considered in conjunction with implementation method B1. For example, in mode 1-1, complex waveform indications are avoided by limiting the transformation precoder to invalid.

[0626] In methods 8-1 / 8-2, the interpretations of '0' and '1' can also be reversed.

[0627] The N bits of DWS can also follow the following options.

[0628] - Option 1: The relationship between the N bits of the DWS and the N cells that are co-scheduled can also follow at least one of the following options.

[0629] -- Option 1-1: The least significant bit (LSB) corresponds to the CC with the lowest or highest index. For example, in N=4, if we assume N bits {ABCD} in the DWS field, then 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.

[0630] -- Option 1-2: The relationship (mapping) is defined in the specification.

[0631] -- Options 1-3: This relationship (mapping) is set via RRC IE.

[0632] -- Options 1-4: The relationship (mapping) is indicated via DCI / MAC CE.

[0633] -- Options 1-5: A set of multiple relations (mappings) is set via RRC IE, and a relation within that set is indicated via DCI / MAC CE.

[0634] According to this implementation, the N-bit DWS field in the DCI format 0_X of scheduling N CCs can be properly interpreted.

[0635] <Implementation Method B9>

[0636] When an N-bit DWS field is set for a DCI format 0_X that schedules N CCs, the existence of a specific DCI field within that DCI format 0_X can also be based on a rule. This rule can also follow at least one of the following options.

[0637] - Option 1: The specific DCI field can also be at least one of the following options.

[0638] -- Option 1-1: DMRS sequence initialization.

[0639] -- Option 1-2: PTRS-DMRS association.

[0640] - Option 2: The rule can also be at least one of the following options.

[0641] -- Option 2-1: Specific DCI fields always exist.

[0642] -- Option 2-2: The specific DCI field does not exist at all.

[0643] -- Option 2-3: The specific DCI field of the co-scheduled cell always exists.

[0644] -- Option 2-4: For cells included in the co-scheduled cells and with DWS set, the specific DCI field always exists.

[0645] -- Option 2-5: Determine whether a specific DCI field exists based on the DWS bits for all co-scheduled cells in the index. For example, if a cell with index 0 in a co-scheduled cell has CP-OFDM indicated by DWS, a specific DCI field (e.g., DMRS sequence initialization field) for that cell exists; otherwise, the specific DCI field does not exist.

[0646] According to this implementation, when the DWS field in the DCI format 0_X of scheduling N CCs is N bits, it is possible to appropriately determine whether a specific DCI field exists.

[0647] <Implementation Method B10>

[0648] Alternatively, if an N-bit DWS field is set for a DCI format 0_X that schedules N CCs, the size (bit width) of a specific DCI field within that DCI format 0_X is based on a rule. This rule may also follow at least one of the following options.

[0649] - Option 1: The specific DCI field can also be at least one of the following options.

[0650] -- Option 1-1: Antenna Port Field.

[0651] -- Option 1-2: TPMI (Precoding Information and Number of Layers).

[0652] In options 1-1 / 1-2, the size of at least one of the first and second specific DCI fields can also be considered / determined. For example, the size of both the "Precoding Information and Layer Number" field and the "Second Precoding Information" field can also be considered / determined.

[0653] - Option 2: The rule may also follow at least one of the following options.

[0654] -- Option 2-1: Regardless of the RRC setting of the transformation precoder, this rule assumes that the transformation precoder is invalid (or valid) to determine the size of a specific DCI field.

[0655] -- Option 2-2: Regardless of the DWS indication content, this rule is envisioned to determine the size of a specific DCI field by changing whether the precoder is invalid (or valid).

[0656] -- Option 2-3: This rule determines the size of a specific DCI field based on the transform precoder set by RRC for a specific CC.

[0657] -- Option 2-4: This rule determines the size of a specific DCI field based on the transform precoder set by RRC for all co-scheduled cells. In this option, the transform precoder can also be common across multiple co-scheduled cells.

[0658] -- Option 2-5: This rule determines the size of a specific DCI field based on the DWS indication content.

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

[0660] <Types of Multicarrier Operation>

[0661] As types of multi-carrier operation, there are carrier aggregation (CA) and dual connectivity (DC).

[0662] CA can be classified into the following categories.

[0663] - Scenario 1: Intra-band continuous CA. This uses multiple consecutive CCs within a single band. For these multiple CCs, consider a single power amplifier (PA).

[0664] - Scenario 2: Non-contiguous CA within a single band. This uses multiple non-contiguous CCs within a single band. For these multiple CCs, multiple PAs are envisioned.

[0665] - Scenario 3: Inter-band CA. This uses multiple CCs spanning multiple bands. For these multiple CCs, multiple PAs are envisioned.

[0666] DC is essentially the same as Case 3 of CA, using multiple CCs across multiple band domains. For these multiple CCs, multiple PAs are envisioned.

[0667] <Analysis C>

[0668] Using different waveforms for multiple control circles (CCs) associated with a single power amplifier (PA) is not very beneficial. This is because even when DFT-S-OFDM is used only for a portion of the multiple CCs, the PAPR characteristics considered in the PA are affected by the remaining CCs using CP-OFDM.

[0669] Different waveforms are used for different CCs associated with different PAs, just like with a single carrier. As long as the waveform of each PA is consistent, the PAPR characteristics are the same as those of a single carrier using either DFT-S-OFDM or CP-OFDM.

[0670] In Rel.18, DCI-based waveform switching (DWS) is being investigated to support DFT-S-OFDM and CP-OFDM. The consideration is to use a single waveform across all multiple carriers associated with a single PA. However, whether DWS is supported in this multi-carrier operation scenario has not been fully investigated.

[0671] <Implementation Method C1>

[0672] This implementation involves the relationship between DWS and multicarrier operation.

[0673] DCI-based waveform switching (DWS) can also support specific multi-carrier operations. The UE can also support DWS in specific multi-carrier operations. Therefore, the advantages of DWS can be obtained in multi-carrier operations.

[0674] This implementation may also follow at least one of the following options.

[0675] <<Option 1>>

[0676] A specific multicarrier operation can also be at least one of the following options 1-x.

[0677] - Option 1-1: Case 1 (continuous CA within the domain).

[0678] - Option 1-2: Case 2 (Discontinuous CA within the band domain).

[0679] - Options 1-3: Case 3 (with inter-domain CA).

[0680] - Options 1-4: Multicarrier operation is not supported in DWS.

[0681] Option 1 may also follow at least one of the following examples.

[0682] - Example 1-1: DWS only supports scenarios 2 and 3. DWS may not be supported in consecutive CA within the same band. It can also be specified that: when multiple bands that support DWS are set as consecutive CA within the same band, DWS is not expected to be set in those multiple bands (UE does not expect DWS to be set in those multiple bands).

[0683] - Example 1-2: DWS only supports scenario 3. DWS may not be supported in in-band CA. It can also be specified that: if multiple bands supporting DWS are set as in-band CAs, DWS is not expected to be set in those multiple bands (the UE does not expect DWS to be set in those multiple bands).

[0684] - Example 1-3: DWS does not support operation using multiple carriers. It can also be specified that: when multiple CCs used for PUSCH transmission are set, DWS is not expected to be set in those multiple CCs (UE does not expect DWS to be set in those multiple CCs).

[0685] <<Option 2>>

[0686] The constraints related to DWS and multicarrier operation (e.g., the constraints of option 1) may also be at least one of the following options 2-x.

[0687] - Option 2-1: This constraint is always applied. For UEs that support DWS, the constraint on multi-carrier operation in DWS can also be always applied.

[0688] - Option 2-2: This constraint is based on finer-grained UE capabilities. This constraint can also be based on the RRC signaling corresponding to the UE capability. Alternatively, UE capabilities for DWS can be defined for each feature set (feature setper component-carrier / cell, FSPC) per CC.

[0689] - Options 2-3: This constraint relies on coarser-grained UE capabilities. This constraint can also be based on RRC signaling corresponding to the UE capability. Multiple UE capabilities can also be defined / supported / reported for reporting DWS-related capabilities. One of these multiple UE capabilities can also report DWS support per UE or per band domain. Another of these multiple UE capabilities can also report DWS support in multi-carrier scenarios per UE or per band domain.

[0690] Option 2 may also follow at least one of the following examples.

[0691] Example 2-1: Define / report the UE capabilities supported by DWS for each FSPC. Based on the reported UE capabilities, the NW / BS can identify in which band and in which scenario DWS is configured / executed.

[0692] Example 2-2: For each UE, define / report UE capability A for reporting DWS support, and define / report UE capability B for reporting DWS support in multi-carrier scenarios. For example... Figure 22 As shown, at least one of the following results may also depend on ability A and ability B.

[0693] -- If neither capability A nor capability B is supported, DWS (within this band) is not supported.

[0694] -- If capability A is supported but capability B is not supported, and multiple ULCCs are set within the DWS-supporting band, then DWS (within that band) is supported.

[0695] -- If both capability A and capability B are supported, DWS (within this band) is supported in both single CC operation and multi CC operation.

[0696] According to this implementation, the UE / BS can appropriately identify whether DWS is supported / executed in multi-carrier operation.

[0697] <Implementation Method C2>

[0698] This implementation involves continuous CA within the band (Case 1).

[0699] When consecutive CAs are configured within the band domain, UEs supporting DWS can also support specific behaviors corresponding to the DWS indication in the CCs associated with the consecutive CAs within the band domain. The multiple CCs included in the consecutive CAs within the band domain can also be consecutive and located within the same band domain.

[0700] <<Option 1>>

[0701] A specific behavior can also be at least one of the following options 1-x.

[0702] - Option 1-1: The UE does not expect different waveforms to be simultaneously indicated / set / determined on any two CCs belonging to consecutive CAs within the band (Case 1).

[0703] - Option 1-2: When different waveforms are simultaneously indicated / set / determined on multiple control surfaces (CCs) belonging to Case 1, the UE applies the waveform determined on a specific CC within those multiple CCs. In this case, the UE can apply the waveform determined on the specific CC to all of the multiple CCs, or it can apply it only to the specific CC. The specific CC can also be at least one of the following CCs.

[0704] -- A CC that can be sent by PUCCH.

[0705] -- PDCCH can be sent as a CC.

[0706] In options 1-2, a specific CC can also be a CC with a higher / highest priority among the multiple CCs belonging to case 1. The priority of multiple CCs can also be determined by at least one of the following options.

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

[0708] - Option 2: Priority is determined based on whether a DWS is set on the CC. For example, a CC with a DWS set has a higher priority than a CC without a DWS set.

[0709] - Option 3: Priority is determined based on the index of the CC. For example, a smaller CC index results in higher priority. Conversely, a larger CC index results in higher priority.

[0710] - Option 4: Priority is determined based on RRC settings. For example, priority can also be assigned to each of multiple CCs via RRC IE. For example, via RRC IE, a CC with a set priority takes precedence over a CC without a set priority (has higher priority).

[0711] According to this implementation, the UE / BS can appropriately execute DWS in continuous CA within the band domain.

[0712] <Implementation Method C3>

[0713] This implementation involves UE capabilities.

[0714] UE capabilities may also follow at least one of the following options.

[0715] <<Option 1>>

[0716] Each UE's or each band's UE capability signaling can also report DWS support in at least one of the following scenarios.

[0717] - The case of a single carrier.

[0718] - In the case of multiple carriers.

[0719] <<Option 2>>

[0720] Each UE's or each band's UE capability signaling can also report DWS support in the following scenarios.

[0721] - This is accompanied by the limitation of always applying the same waveform across multiple CCs, and the situation of multiple carriers shared by PAs (e.g., continuous CAs within the band).

[0722] <<Option 3>>

[0723] UE capability signaling can also report DWS support in the following situations.

[0724] - Cases involving multiple carriers shared by PA without any restrictions (e.g., continuous CA within the band).

[0725] The structure of UE capabilities can also follow at least one of the following examples.

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

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

[0728] According to this implementation, the UE / BS is able to report / identify the appropriate UE capabilities associated with the DWS.

[0729] <Changes to Implementation Method C>

[0730] The UE can also support the options in options 1-1 to 1-4 of implementation method C1 that depend on the UE's capabilities. Different options in options 1-1 to 1-4 of implementation method C1 can also be supported by different UEs.

[0731] The UE can also support options 2-1 to 2-3 of implementation C1 that depend on the situation in option 1. Different options from options 1-1 to 1-4 can also be supported for different options from options 2-1 to 2-3 of implementation C1.

[0732] In at least one of embodiments C1 to C3, the CA type (one of cases 1 to 3) may also be determined based on at least one of the following pieces of information.

[0733] - Signaling from the BS. It can also be at least one of RRC settings, MAC CE indication, and DCI indication.

[0734] - A report from the UE. It can also be at least one of capability or assistance information.

[0735] - Both of the above pieces of information. For example, the CA type can also be determined based on the capability report from the UE used for CA, and the settings / instructions from the BS for CA.

[0736] Instead of the distinction between scenarios 1 / 2 / 3, at least one of the following can be imported: signaling from the BS and reports from the UE, indicating whether the combination of bands / CCs shares a single PA. Alternatively, at least one of implementation methods C1 to C3 can be applied by replacing scenario 1 with "the scenario where a single PA is shared" and scenario 2 / 3 with "the scenario where a PA is implemented for each carrier / CC / band."

[0737] <Analysis D1>

[0738] We are currently researching UE capability signaling for DWS.

[0739] Supporting multiple CC operations in DWS is no easy task, especially supporting intra-domain (continuous) CA.

[0740] To enable the UE to choose whether to support DWS in in-band CA operation, consider DWS using UE capabilities based on at least one of the following definitions.

[0741] ◇Definition 1: This capability is defined as the capability of each band domain. The UE can report whether DWS is supported on a per-band domain basis.

[0742] ◇Definition 2: In a band where the UE reports support for DWS, at least one of several restrictions is imposed on the number of CCs that can be configured to perform DWS within that band.

[0743] ―◇Option 1: In order for the UE to support / execute DWS, one of the following CCs can be set in this band.

[0744] ―◇Option 2: The UE reports the number of CCs that support / execute DWS within this band.

[0745] With only option 1 imposed, the UE is completely unable to support DWS in the in-band CA.

[0746] When only Option 2 is applied, the signaling for the report must consider the maximum number of CCs within the band, resulting in greater reporting overhead. In other words, the reported size (bit width, overhead) of the number of CCs for the DWS within the UE-supported band depends on the maximum number of CCs within the UE-supported band. For example, if the number of CCs in the UE-supported band is 4, the report size is 2 bits because there are 4 candidate values ​​for the reported number of CCs for the DWS within the UE-supported band. Option 2 is essentially equivalent to defining the capability signaling for each FSPC.

[0747] <Implementation Method D1>

[0748] This implementation involves analyzing D1.

[0749] UE capability signaling supporting DWS can also be defined for UE reporting operations using multiple CCs within a single band domain. This UE capability can also be defined separately from UE capabilities supporting DWS for reporting other operations. An operation using multiple CCs within a single band domain (Operation 1) can be an intra-band CA, and can include at least one of intra-band consecutive CAs (in the case of consecutive CCs) and intra-band discontinuous CAs (in the case of discontinuous CCs). Other operations (Operation 2) can be operations other than Operation 1, or operations using multiple CCs across multiple band domains. Operations using multiple CCs across multiple band domains can also be inter-band CAs.

[0750] According to this implementation, the reporting overhead for supporting basic DWS functions can be minimized. According to this implementation, the UE can support DWS operation using multiple CCs within a single band domain.

[0751] This implementation may also follow at least one of the following options.

[0752] ◇Option 1: One or more components within this capability signaling may also include at least one of the following options 1-x.

[0753] ―◇Option 1-1: The number N of CCs N supported by the UE for DWS within the band domain (the number N of CCs N supported for DWS within the band domain). This component can also correspond to Option 2 mentioned above. The band domain can also be the band domain where capability signaling is reported. The value of N can also depend on the scenario. Different values ​​of N can be reported for different scenarios. Different scenarios can be operations using continuous CCs (e.g., CA within the band domain) or operations using discontinuous CCs (e.g., CA within the band domain).

[0754] ―◇Options 1-2: The number of consecutive CCs N1 supported by the UE for DWS within the band (the number of consecutive CCs N1 supported for DWS within the band).

[0755] ―◇Options 1-3: The number of discontinuous CCs N2 supported by the UE for DWS in the band (the number of discontinuous CCs N2 supported for DWS in the band).

[0756] Option 2: Constraints associated with more than one component may also follow at least one of the following options 2-x.

[0757] ―◇Option 2-1: N is greater than 1. DWS support in the case of N=1 can also be reported via other UE capability signaling. Other UE capability signaling can, for example, indicate support for basic DWS functions.

[0758] ―◇Option 2-2: N1 is greater than 1.

[0759] ―◇Option 2-2a: N1 is 1 or higher.

[0760] ―◇Options 2-3: N2 is greater than 1.

[0761] ―◇Options 2-4: The relationship between N1 and N2. This relationship can also include any one of N1≤N2, N1<N2, N1≥N2, and N1>N2.

[0762] For both continuous CA and discontinuous CA within the band domain, separate / individual UE capability signaling can also be considered / defined. This implementation can also be applied to at least one of continuous CA and discontinuous CA within the band domain.

[0763] <MPR Calculation in Multicarrier Operation>

[0764] Due to higher-order modulation and transmission bandwidth settings, the UE is allowed to reduce its maximum output power.

[0765] For various multi-carrier (multiple CC) operations, the maximum power reduction (MPR) calculation is defined in the specification. Multiple MPR values ​​specific to consecutive CAs within the band are defined. Figure 23 An example of multiple MPR values ​​corresponding to continuous CA, power level 3, and continuous RB configurations within the band is shown (Table M-1). In this table, each MPR value is associated with a combination of waveform type (DFT-s-OFDM or CP-OFDM) and modulation order (Pi / 2 BPSK, QPSK, etc.).

[0766] When the modulation format or waveform type (DFT-s-OFDM or CP-OFDM) differs on different CCs, the requirements are set by applying rules to the waveform type and modulation order used within the setting of the maximum (worst) MPR.

[0767] For MPR with discontinuous CA within the band domain, the following cases apply.

[0768] ◇Scenario 1: The MPR in the case where UL transmissions across multiple CCs are not performed simultaneously is the same as the MPR for a single CC operation.

[0769] ◇Scenario 2: In cases where this is not the case, define multiple values ​​for the MPR specific to the operation (with discontinuous CA within the domain). These multiple values ​​for the MPR are completely different from the MPR used for a single CC operation.

[0770] The MPR for inter-domain CA is the same as the MPR for a single CC operation.

[0771] In this disclosure, the worst MPR value and the highest MPR value can also be rewritten to each other.

[0772] <Analysis D2>

[0773] As mentioned above, for consecutive CAs within a band, the worst MPR value across multiple corresponding CCs is considered. For example, if DFT-s-OFDM is set for CC#1 and CP-OFDM is set for CC#2, the worst MPR across CC#1 and CC#2 is considered (e.g., the MPR for CP-OPDM). If DFT-s-OFDM is not considered in the MPR determination when DWS is indicated, the advantage of DFT-s-OFDM (smaller MPR) cannot be obtained according to the rule of worst MPR value across multiple CCs.

[0774] In discontinuous CA within the band, this rule does not exist (the determination of MPR follows the method for determining MPR for a single CC case, or a method that does not depend on the waveform).

[0775] <Implementation Method D2>

[0776] This implementation involves the analysis of D2.

[0777] Alternatively, specific constraints (conditions) can be applied when a UE reports support for DWS in operation using multiple CCs within a single band (multi-carrier operation). Specific constraints (conditions) can also be applied to UEs reporting support for DWS in operation using multiple CCs within a single band. According to this implementation, no overhead is incurred for DWS UE capability signaling for specific (meaningless) scenarios. Specific scenarios could be scenarios where the advantages of DWS (DFT-s-OFDM) cannot be obtained, or DWS in consecutive CAs within a band.

[0778] This implementation may also follow at least one of the following options.

[0779] ◇Option 1: Specific constraints may also include at least one of the following options 1-x.

[0780] ―◇Option 1-1: The multiple CCs are not consecutive.

[0781] ―◇Options 1-2: More than one CC within the multiple CCs simultaneously transports ULs with non-zero bandwidth.

[0782] ◇Option 2: UE behavior may also follow at least one of the following options 2-x when specific constraints are not guaranteed (not satisfied).

[0783] ―◇Option 2-1: UE ignores DWS settings.

[0784] ―◇Option 2-2: UE ignores DWS indication on DCI.

[0785] ―◇Option 2-3: The UE ignores indication information transmitted on the DCI that has a Transform Precoder Indicator (TPI) field (DWS field). The UE may also ignore the TPI field or indication information other than the TPI field. Indication information other than the TPI field may be, for example, PUSCH scheduling information. Through this UE behavior, the UE may also not send PUSCH scheduled through this DCI.

[0786] ―◇Options 2-4: Specific constraints are always guaranteed (satisfied). It can also be specified in the specification that "UE does not expect PUSCH to be scheduled with TPI field if specific conditions (specific constraints) are not met". In order to guarantee specific constraints, it is also possible to restrict (1) multiple CCs used for UL transmission, (2) more than one time slot used for UL transmission, and (3) at least one of the contents of TPI field.

[0787] Under certain conditions that are guaranteed (satisfied), the UE may also receive at least one of DWS setting (valid DWS setting) and DWS indication (DCI containing DWS indication).

[0788] Option 1 / 2 of this implementation can also be applied to at least one of the following objects.

[0789] ◇Object 1: All CC operations in this set of multiple CC operations.

[0790] ◇Object 2: The scheduling CC. This CC can also be a CC that sends (receives) a DCI with a DWS indication.

[0791] ◇Object 3: Scheduled CC. This CC can also be a CC that is scheduled (sent) a PUSCH via a DCI with a DWS indication.

[0792] ◇Object 4: All CC operations among the multiple CC operations set by DWS.

[0793] <Supplement>

[0794] [Information notification to UE]

[0795] The notification of any information from the Network (NW) (e.g., from the Base Station (BS)) to the UE (in other words, the reception of any information from the BS in the UE) in the above-described embodiments can also be performed using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PDCCH, PDSCH, reference signals), or combinations thereof.

[0796] In the case where the above notification is made via MAC CE, the MAC CE can also be identified by including a new Logical Channel ID (LCID) in the MAC subheader that is not specified in the existing specifications.

[0797] When the above notification is made through a DCI, the notification may also be made through specific fields of the DCI, the Radio Network Temporary Identifier (RNTI) used in the scrambling of the Cyclic Redundancy Check (CRC) bits assigned to the DCI, the format of the DCI, etc.

[0798] Furthermore, the notification of any information to the UE in the above embodiments can also be carried out periodically, semi-persistently, or non-periodically.

[0799] [Notification from UE]

[0800] The notification of any information from the UE (to the NW) in the above embodiments (in other words, the transmission / reporting of any information from the UE to the BS) can also 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 combinations thereof.

[0801] In the case where the above notification is made via MAC CE, the MAC CE can also be identified by including a new LCID, which is not specified in the existing specifications, in the MAC subheader.

[0802] In the case where the above notification is made through UCI, the above notification may also be sent using PUCCH or PUSCH.

[0803] Furthermore, the notification of any information from the UE in the above embodiments can also be performed periodically, semi-persistently, or non-periodically.

[0804] [Regarding the application of each implementation method]

[0805] At least one of the above-described implementation methods can also be applied under certain conditions. These conditions can be specified in the specification or communicated to the UE / BS using higher-layer signaling / physical layer signaling.

[0806] This specific condition can be one of the following conditions, or it can be specified by an AND / OR combination of two or more of the following conditions.

[0807] ◇UE reports specific UE capabilities (at least one function of the above implementation).

[0808] ◇The UE is configured with at least one function of the above-described implementation method.

[0809] At least one of the above-described implementation methods may also be applied only to UEs that have reported a specific UE capability or support that specific UE capability.

[0810] This specific UE capability can also represent at least one of the following:

[0811] ◇Supports specific processing / operation / control / information for at least one of the above embodiments.

[0812] Furthermore, the aforementioned specific UE capabilities can be applied across the entire frequency spectrum (commonly regardless of frequency), or per frequency (e.g., one or a combination of cells, bands, band combinations, BWPs, component carriers, etc.), per frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), per subcarrier spacing (SCS), or per feature set (FS) or per feature set per component carrier (FSPC).

[0813] Furthermore, the aforementioned specific UE capabilities can be either the ability to be applied across all full-duplex modes (which are common regardless of the duplex mode) or the capability for each duplex mode (e.g., Time Division Duplex (TDD) and Frequency Division Duplex (FDD)).

[0814] Furthermore, at least one of the above-described embodiments can also be applied when the UE is configured / activated / triggered by specific information associated with the above-described embodiments (or the operation of the above-described embodiments is implemented) via higher-layer signaling / physical layer signaling. This specific information can also represent at least one of the following:

[0815] ◇Indicates information about activating / deactivating the above-described implementation method.

[0816] ◇ RRC parameters for specific versions (e.g., Rel.18 / 19). These RRC parameters can also have names that append "r18" / "r19" to the name of an existing RRC parameter.

[0817] Even if the UE does not support at least one of the aforementioned specific UE capabilities or is not configured with the aforementioned specific information, operations such as Rel.15 / 16 can still be applied.

[0818] (Postscript)

[0819] With respect to one embodiment of this disclosure, the following invention is noted.

[0820] [Postscript 1]

[0821] The terminal has:

[0822] The transmitting unit transmits capability information related to the dynamic transform precoder indication used in operation with multiple component carriers within a single band domain; and

[0823] The control unit controls the reception of the settings indicated by the dynamic transformation pre-encoder.

[0824] [Postscript 2]

[0825] The terminal as described in Appendix 1,

[0826] The capability information includes at least one of the following: the number of component carriers supporting the dynamic transform precoder indication, the number of consecutive component carriers supporting the dynamic transform precoder indication, and the number of non-consecutive component carriers supporting the dynamic transform precoder indication.

[0827] [Postscript 3]

[0828] The terminal as described in Appendix 1 or Appendix 2,

[0829] If at least one of the following conditions is met: the multiple component carriers are discontinuous, or more than one of the multiple component carriers simultaneously transports uplinks with non-zero bandwidth, then at least one of the settings and the dynamic transformation precoder indication is received.

[0830] [Postscript 4]

[0831] The terminal described in any of Notes 1 to 3,

[0832] If the conditions of discontinuous component carriers, simultaneous uplink transmission of more than one component carrier with non-zero bandwidth within the multiple component carriers are not met, and the dynamic change precoder indication is received, the control unit ignores at least one of the following: the setting, the dynamic change precoder indication, and downlink control information containing the dynamic change precoder indication.

[0833] (Wireless communication system)

[0834] The structure 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 one or a combination of the wireless communication methods according to the above embodiments of this disclosure.

[0835] Figure 24 This is a diagram illustrating an example of the schematic structure of a wireless communication system according to one embodiment. The wireless communication system 1 (or simply system 1) may also be a system that uses Long Term Evolution (LTE) or 5th generation mobile communication system New Radio (5G NR) as standardized through the Third Generation Partnership Project (3GPP) to achieve communication.

[0836] Furthermore, the wireless communication system 1 can also support dual connectivity between multiple radio access technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC can also include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), etc.

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

[0838] Wireless communication system 1 can also support dual connectivity between multiple base stations within the same RAT (e.g., MN and SN are dual connectivity between NR base stations (gNB) (NR-NR Dual Connectivity (NN-DC))).

[0839] The wireless communication system 1 may also include a base station 11 forming a macro cell C1 with a relatively wide coverage area, and a base station 12 (12a-12c) configured within the macro cell C1 and forming a small cell C2 narrower than the macro cell C1. The user terminal 20 may also be located within at least one cell. The configuration and number of each cell and the user terminal 20 are not limited to the arrangement shown in the figure. Hereinafter, without distinguishing between base stations 11 and 12, they will be collectively referred to as base station 10.

[0840] User terminal 20 may also connect to at least one of multiple base stations 10. User terminal 20 may also utilize at least one of carrier aggregation (CA) using multiple component carriers (CC) and dual connectivity (DC).

[0841] Each CC can also be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). Macro cell C1 can also be included in FR1, and small cell C2 can also be included in FR2. For example, FR1 can also be a frequency band below 6 GHz (sub-6 GHz), and FR2 can also be a frequency band above 24 GHz (above-24 GHz). In addition, the frequency bands, definitions, etc. of FR1 and FR2 are not limited to these; for example, FR1 can also be equivalent to a frequency band higher than FR2.

[0842] In addition, user terminal 20 can also use at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) to communicate in each CC.

[0843] Multiple base stations 10 can also be connected via wired (e.g., fiber optic, X2 interface, etc. based on Common Public Radio Interface (CPRI)) or wireless (e.g., NR communication). For example, when NR communication between base stations 11 and 12 is used as a backhaul, base station 11, which is equivalent to a host station, can also be referred to as an Integrated Access Backhaul (IAB) donor, and base station 12, which is equivalent to a relay station, can also be referred to as an IAB node.

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

[0845] The core network 30 may also include, for example, network functions 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). Furthermore, multiple functions can be provided through a single network node. Additionally, communication with external networks (e.g., networks) can also be achieved via the DN.

[0846] User terminal 20 can also be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.

[0847] In wireless communication system 1, wireless access methods based on Orthogonal Frequency Division Multiplexing (OFDM) can also be used. For example, in at least one of the downlink (DL) and uplink (UL) links, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), and Single Carrier Frequency Division Multiple Access (SC-FDMA) can also be used.

[0848] The wireless access method can also be referred to as a waveform. In addition, in the wireless communication system 1, other wireless access methods (e.g., other single-carrier transmission methods, other multi-carrier transmission methods) can also be used in the wireless access methods of UL and DL.

[0849] As a downlink channel, the wireless communication system 1 can also use downlink shared channels (Physical Downlink Shared Channel (PDSCH)), broadcast channels (Physical Broadcast Channel (PBCH)), downlink control channels (Physical Downlink Control Channel (PDCCH)) and so on, which are shared among the user terminals 20.

[0850] In addition, as uplink channels, the wireless communication system 1 may also use uplink shared channels (Physical Uplink Shared Channel (PUSCH)), uplink control channels (Physical Uplink Control Channel (PUCCH)), random access channels (Physical Random Access Channel (PRACH)) and so on, which are shared by each user terminal 20.

[0851] User data, high-level control information, and System Information Blocks (SIBs) are transmitted via the PDSCH. User data and high-level control information can also be transmitted via the PUSCH. In addition, the Master Information Block (MIB) can also be transmitted via the PBCH.

[0852] Lower-layer control information can also be transmitted via PDCCH. Lower-layer control information may include, for example, downlink control information (DCI), which includes scheduling information for at least one of PDSCH and PUSCH.

[0853] Additionally, the DCI that schedules PDSCH can also be called DL allocation, DL DCI, etc., and the DCI that schedules PUSCH can also be called UL authorization, UL DCI, etc. Furthermore, PDSCH can be rewritten as DL data, and PUSCH can be rewritten as UL data.

[0854] In PDCCH detection, a Control Resource Set (CORESET) and a search space can also be utilized. A CORESET corresponds to the resources used to search for DCIs. The search space corresponds to the search area and search method for PDCCH candidates. A CORESET can also be associated with one or more search spaces. The UE can also monitor CORESETs associated with a specific search space based on search space settings.

[0855] A search space can also correspond to one or more PDCCH candidates equivalent to one or more aggregation levels. One or more search spaces can also be referred to as a search space set. In addition, the terms "search space", "search space set", "search space setting", "search space set setting", "CORESET", and "CORESET setting" in this disclosure can be rewritten interchangeably.

[0856] The PUCCH can also transmit uplink control information (uplink control information (UCI)) that includes at least one of the following: Channel State Information (CSI), delivery confirmation information (e.g., also known as Hybrid Automatic Repeat Request ACK Knowledge (HARQ-ACK), ACK / NACK, etc.), and Scheduling Request (SR). The PRACH can also transmit random access preambles used for establishing connections with the cell.

[0857] In addition, in this disclosure, downlink, uplink, etc., can also be described without the word "link". Furthermore, they can also be described without the word "physical" at the beginning of various channels.

[0858] In wireless communication system 1, synchronization signals (SS) and downlink reference signals (DL-RS) can also be transmitted. As DL-RS, wireless communication system 1 can also transmit cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), positioning reference signals (PRS), phase tracking reference signals (PTRS), etc.

[0859] Synchronization signals can be, for example, at least one of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS). A signal block containing SS (PSS, SSS) and PBCH (and DMRS for PBCH) can also be called an SS / PBCH block, SS block (SSB), etc. In addition, SS, SSB, etc. can also be called reference signals.

[0860] Furthermore, in wireless communication system 1, the uplink reference signal (UL-RS) can also transmit measurement reference signals (sounding reference signals (SRS)) and demodulation reference signals (DMRS). Additionally, DMRS can also be referred to as user terminal-specific reference signals (UE-specific reference signals).

[0861] (Base station)

[0862] Figure 25 This diagram illustrates an example of the structure of a base station according to one embodiment. The base station 10 includes a control unit 110, a transmit / receive unit 120, a transmit / receive antenna 130, and a transmission path interface (transmission line interface) 140. Alternatively, the control unit 110, the transmit / receive unit 120, the transmit / receive antenna 130, and the transmission path interface 140 may each be provided in more than one manner.

[0863] Furthermore, while this example primarily illustrates the functional blocks of the characteristic portions of this embodiment, it is also conceivable that the base station 10 may also have other functional blocks required for wireless communication. Some of the processing of each unit described below may also be omitted.

[0864] The control unit 110 performs overall control of the base station 10. The control unit 110 can be composed of a controller, control circuit, etc., which are described based on common knowledge in the art to which this disclosure pertains.

[0865] The control unit 110 can also control signal generation and scheduling (e.g., resource allocation, mapping). The control unit 110 can also control transmission, reception, and measurement using the transmit / receive unit 120, transmit / receive antenna 130, and transmission path interface 140. The control unit 110 can also generate data, control information, sequences, etc., to be transmitted as signals and forward them to the transmit / receive unit 120. The control unit 110 can also perform call processing (setting, releasing, etc.) of the communication channel, status management of the base station 10, and management of wireless resources.

[0866] The transmitting / receiving unit 120 may also include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may also include a transmitting processing unit 1211 and a receiving processing unit 1212. The transmitting / receiving unit 120 may be composed of transmitters / receivers, RF circuits, baseband circuits, filters, phase shifters, measurement circuits, transmitting / receiving circuits, etc., as described based on common knowledge in the art to which this disclosure pertains.

[0867] The transmitting and receiving unit 120 can be configured as a single integrated transmitting and receiving unit, or it can be composed of a transmitting unit and a receiving unit. The transmitting unit can also be composed of a transmitting processing unit 1211 and an RF unit 122. The receiving unit can also be composed of a receiving processing unit 1212, an RF unit 122, and a measurement unit 123.

[0868] The transmitting and receiving antenna 130 can be constructed from an antenna, such as an array antenna, as described based on common knowledge in the art to which this disclosure pertains.

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

[0870] The transmitting and receiving unit 120 may also use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc. to form at least one of the transmitting beam and the receiving beam.

[0871] The transmitting and receiving unit 120 (transmitting processing unit 1211) may, for example, process the data and control information obtained from the control unit 110 through the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer (e.g., RLC retransmission control), and the Medium Access Control (MAC) layer (e.g., HARQ retransmission control) to generate the bit string to be transmitted.

[0872] The transmitting and receiving unit 120 (transmitting processing unit 1211) can also perform channel coding (which may include error correction coding), modulation, mapping, filter processing (filtering processing), Discrete Fourier Transform (DFT) processing (as needed), Inverse Fast Fourier Transform (IFFT) processing, precoding, digital-to-analog conversion, and other transmission processing on the bit string to be transmitted, and output the baseband signal.

[0873] The transmitting and receiving unit 120 (RF unit 122) can also perform modulation, filtering, amplification, etc. on the baseband signal to the wireless frequency band, and transmit the wireless frequency band signal through the transmitting and receiving antenna 130.

[0874] On the other hand, the transmitting and receiving unit 120 (RF unit 122) can also amplify, filter (filter) and demodulate the baseband signal received by the transmitting and receiving antenna 130 in the wireless frequency band.

[0875] The transmitting and receiving unit 120 (receiving and processing unit 1212) can also perform receiving and processing on the acquired baseband signal, including analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, and acquire user data, etc.

[0876] The transmitting / receiving unit 120 (measurement unit 123) can also perform measurements related to the received signal. For example, the measurement unit 123 can also perform radio resource management (RRM) measurements, channel state information (CSI) measurements, etc., based on the received signal. The measurement unit 123 can also measure received power (e.g., Reference Signal Received Power (RSRP)), received quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results can also be output to the control unit 110.

[0877] The transmission path interface 140 can also transmit and receive signals (backhaul signaling) between the device included in the core network 30 (e.g., a network node providing NF), other base stations 10, etc., and acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

[0878] In addition, the transmitting unit and receiving unit of the base station 10 in this disclosure may also be composed of at least one of a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission path interface 140.

[0879] The transmit / receive unit 120 can also receive capability information related to a dynamic transform precoder indication used in operation supporting multiple component carriers within a single band. The control unit 110 can also control the transmission of settings for the dynamic transform precoder indication.

[0880] (User terminal)

[0881] Figure 26 This diagram illustrates an example of the structure 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. Alternatively, more than one of each of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may be included.

[0882] Furthermore, while this example primarily illustrates the functional blocks of the characteristic portions of this embodiment, it is also conceivable that the user terminal 20 may also have other functional blocks required for wireless communication. Some of the processing of each unit described below may also be omitted.

[0883] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., which are described based on common knowledge in the technical field to which this disclosure pertains.

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

[0885] The transmitting / receiving unit 220 may also include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may also include a transmitting processing unit 2211 and a receiving processing unit 2212. The transmitting / receiving unit 220 may be composed of transmitters / receivers, RF circuits, baseband circuits, filters, phase shifters, measurement circuits, transmitting / receiving circuits, etc., as described based on common knowledge in the art to which this disclosure pertains.

[0886] The transmitting and receiving unit 220 can be configured as a single integrated transmitting and receiving unit, or it can be composed of a transmitting unit and a receiving unit. The transmitting unit can also be composed of a transmitting processing unit 2211 and an RF unit 222. The receiving unit can also be composed of a receiving processing unit 2212, an RF unit 222, and a measurement unit 223.

[0887] The transmitting and receiving antenna 230 can be constructed from an antenna, such as an array antenna, as described based on common knowledge in the art to which this disclosure pertains.

[0888] The transmitting / receiving unit 220 can also receive the downlink channel, synchronization signal, downlink reference signal, etc., mentioned above. The transmitting / receiving unit 220 can also transmit the uplink channel, uplink reference signal, etc., mentioned above.

[0889] The transmitting and receiving unit 220 may also use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc., to form at least one of the transmitting beam and the receiving beam.

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

[0891] The transmitting and receiving unit 220 (transmitting processing unit 2211) can also perform channel coding (which may include error correction coding), modulation, mapping, filter processing (filtering processing), DFT processing (as needed), IFFT processing, precoding, digital-to-analog conversion and other transmission processing on the bit string to be transmitted, and output the baseband signal.

[0892] Furthermore, whether or not to apply DFT processing can be based on the settings of transform precoding. For a certain channel (e.g., PUSCH), if transform precoding is enabled, the transmit / receive unit 220 (transmit processing unit 2211) can perform DFT processing as described above in order to transmit the channel using the DFT-s-OFDM waveform; otherwise, the transmit / receive unit 220 (transmit processing unit 2211) can perform DFT processing as described above without performing DFT processing.

[0893] The transmitting and receiving unit 220 (RF unit 222) can also perform modulation, filtering (filtering), amplification, etc. on the baseband signal to the wireless frequency band, and transmit the wireless frequency band signal through the transmitting and receiving antenna 230.

[0894] On the other hand, the transmitting and receiving unit 220 (RF unit 222) can also amplify, filter (filter) and demodulate the baseband signal received by the wireless frequency band through the transmitting and receiving antenna 230.

[0895] The transmitting and receiving unit 220 (receiving and processing unit 2212) can also perform receiving and processing on the acquired baseband signal, such as analog-to-digital conversion, FFT processing, IDFT processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, and acquire user data.

[0896] The transmitting / receiving unit 220 (measurement unit 223) can also perform measurements related to the received signal. For example, the measurement unit 223 can also perform RRM measurements, CSI measurements, etc., based on the received signal. The measurement unit 223 can 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 can also be output to the control unit 210.

[0897] Alternatively, the transmitting and receiving units of the user terminal 20 in this disclosure may also be composed of at least one transmitting / receiving unit 220 and transmitting / receiving antenna 230.

[0898] The transmit / receive unit 220 can also transmit capability information related to a dynamic transform precoder indication used in operation with multiple component carriers within a single band. The control unit 210 can also control the reception of settings for the dynamic transform precoder indication.

[0899] The capability information may also include at least one of the following: the number of component carriers supporting the dynamic transformation precoder indication, the number of consecutive component carriers supporting the dynamic transformation precoder indication, and the number of non-consecutive component carriers supporting the dynamic transformation precoder indication.

[0900] Alternatively, in the case that the plurality of component carriers are discontinuous, or that more than one of the plurality of component carriers simultaneously transports at least one uplink with non-zero bandwidth, at least one of the settings and the dynamic transformation precoder indication is received.

[0901] Alternatively, if the conditions of discontinuous component carriers, simultaneous transmission of at least one uplink with non-zero bandwidth by more than one component carrier within the multiple component carriers are not met, and the dynamic change precoder indication is received, the control unit 210 may ignore at least one of the following: the setting, the dynamic change precoder indication, and downlink control information containing the dynamic change precoder indication.

[0902] (Hardware structure)

[0903] Furthermore, the block diagrams used in the description of the above embodiments illustrate functional units. These functional blocks (structural units) are implemented through any combination of at least one of hardware and software. Moreover, the implementation method of each functional block is not particularly limited. That is, each functional block can be implemented using a single device that is physically or logically combined, or it can be implemented by directly or indirectly (e.g., using wired, wireless, etc.) connecting two or more physically or logically separate devices. A functional block can also be implemented by combining the aforementioned single device or multiple devices with software.

[0904] Here, the functions include judgment, decision, determination, calculation, calculation, processing, export, investigation, search, confirmation, receiving, sending, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, regard as, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning, but are not limited to these. For example, a functional block (structural unit) that implements the sending function can also be called a transmitting unit, transmitter, etc. Each of these, as described above, is not particularly limited in its implementation method.

[0905] For example, in one embodiment of this disclosure, the base station, user terminal, etc., can also function as a computer for processing the wireless communication method of this disclosure. Figure 27 This diagram illustrates an example of the hardware structure of a base station and a user terminal according to one embodiment. The base station 10 and the user terminal 20 described above can also be physically configured as a computer device including a processor 1001, a memory 1002, a storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0906] Furthermore, in this disclosure, terms such as apparatus, circuit, device, section, and unit can be interchanged. The hardware structure of base station 10 and user terminal 20 can be configured to include one or more of the apparatuses shown in the figures, or it can be configured not to include some of the apparatuses.

[0907] For example, only one processor 1001 is shown, but there can be multiple processors. Furthermore, processing can be performed by one processor, or simultaneously, sequentially, or by two or more processors using other methods. Additionally, processor 1001 can be implemented using more than one chip.

[0908] The functions of the base station 10 and the user terminal 20 are implemented, for example, by reading specific software (programs) into hardware such as the processor 1001 and the memory 1002, so that the processor 1001 performs calculations and controls communication via the communication device 1004, or controls at least one of reading and writing data in the memory 1002 and the storage device 1003.

[0909] The processor 1001 enables the operating system to operate and control the computer as a whole. The processor 1001 may also be a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic devices, registers, etc. For example, at least a portion of the control unit 110 (210), the transmit / receive unit 120 (220), etc., described above may also be implemented by the processor 1001.

[0910] 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 performs various processes accordingly. As a program, a program that causes the computer to perform at least a portion of the operations described in the above embodiments can be used. For example, the control unit 110 (210) can also be implemented by a control program stored in the memory 1002 and operable in the processor 1001; similar implementations can be made for other functional blocks.

[0911] The memory 1002 may also be a computer-readable recording medium, such as being composed of at least one of a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), or other suitable storage media. The memory 1002 may also be referred to as a register, cache, main memory (main storage device), etc. The memory 1002 is capable of storing executable programs (program code), software modules, etc., for implementing the wireless communication method according to an embodiment of this disclosure.

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

[0913] The communication device 1004 is hardware (transmitting and receiving device) used for communication 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 interface card (NIC), communication module, etc. To implement at least one of, for example, Frequency Division Duplex (FDD) and Time Division Duplex (TDD), the communication device 1004 may also be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. For example, the aforementioned transmitting and receiving unit 120 (220) and transmitting and receiving antenna 130 (230) may also be implemented by the communication device 1004. The transmitting and receiving unit 120 (220) may also be physically or logically separated by a transmitting unit 120a (220a) and a receiving unit 120b (220b).

[0914] Input device 1005 is an input device that receives input from external sources (e.g., keyboard, mouse, microphone, switch, button, sensor, etc.). Output device 1006 is an output device that performs output to external sources (e.g., display, speaker, light-emitting diode (LED) lamp, etc.). Alternatively, input device 1005 and output device 1006 can also be an integrated structure (e.g., a touch panel).

[0915] Furthermore, the processor 1001, memory 1002, and other devices are connected via a bus 1007 for communicating information. The bus 1007 can be configured as a single bus or as different buses between the devices.

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

[0917] (Modified example)

[0918] Furthermore, the terms described in this disclosure, as well as those necessary for understanding this disclosure, may be replaced with terms that have the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) may be interchanged. Additionally, a signal may also be a message. A reference signal may also be abbreviated as RS, and may be referred to as pilot, pilot signal, etc., depending on the applied standard. Furthermore, a component carrier (CC) may also be referred to as cell, frequency carrier, carrier frequency, etc.

[0919] A radio frame can also be composed of one or more periods (frames) in the time domain. Each of these periods (frames) that constitutes a radio frame can also be called a subframe. Furthermore, a subframe can also be composed of one or more time slots in the time domain. A subframe can also be a fixed time length (e.g., 1 ms) independent of the parameter set (numerology).

[0920] Here, the parameter set can also be communication parameters applied in at least one of the transmission and reception of a signal or channel. For example, the parameter set can also represent 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 structure, specific filtering processing performed by the transmitter and receiver in the frequency domain, and specific windowing processing performed by the transmitter and receiver in the time domain.

[0921] In the time domain, a time slot can also be composed of one or more symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.). In addition, a time slot can also be a time unit based on a set of parameters.

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

[0923] Radio frames, subframes, time slots, mini-time slots, and symbols all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-time slots, and symbols can also use their respective other names. Furthermore, the time units such as frames, subframes, time slots, mini-time slots, and symbols in this disclosure can be interchanged.

[0924] For example, a subframe can also be called a TTI, multiple consecutive subframes can also be called a TTI, and a time slot or a mini-time slot can also be called a TTI. That is, at least one of a subframe and a TTI can be a subframe in existing LTE (1ms), a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. In addition, the unit representing TTI may not be called a subframe, but rather a time slot, mini-time slot, etc.

[0925] Here, TTI refers, for example, to the smallest unit of time for scheduling in wireless communication. For instance, in an LTE system, the base station schedules radio resources (frequency bandwidth, transmit power, etc., available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0926] TTI can also be a unit of time for transmitting channel-coded data packets (transmission blocks), code blocks, codewords, etc., and can also be a unit of processing such as scheduling and link adaptation. In addition, when a TTI is given, the actual time interval (e.g., the number of symbols) mapped to transmission blocks, code blocks, codewords, etc. can be shorter than the TTI.

[0927] Additionally, where a time slot or a mini-time slot is referred to as a TTI, more than one TTI (i.e., more than one time slot or more than one mini-time slot) can also serve as the minimum time unit for scheduling. Furthermore, the number of time slots (mini-time slots) constituting the minimum time unit of the schedule can also be controlled.

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

[0929] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) can also be rewritten as a TTI with a duration of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) can also be rewritten as a TTI with a duration of less than a long TTI but more than 1 ms.

[0930] A resource block (RB) is a unit of resource allocation in both the time and frequency domains. In the frequency domain, it can also contain one or more consecutive subcarriers. The number of subcarriers in an RB can be the same regardless of the parameter set, for example, it can be 12. The number of subcarriers in an RB can also be determined based on the parameter set.

[0931] Furthermore, an RB can contain one or more symbols in the time domain, and can also be a time slot, a mini-time slot, a subframe, or the length of a TTI. A TTI, a subframe, etc., can also be composed of one or more resource blocks.

[0932] In addition, one or more RBs can also be referred to as Physical Resource Blocks (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

[0933] In addition, a resource block can also consist of one or more resource elements (REs). For example, an RE can also be a radio resource area consisting of a subcarrier and a symbol.

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

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

[0936] Alternatively, at least one of the configured BWPs may be activated, and the UE may not intend to transmit or receive specific signals / channels outside of the activated BWPs. Furthermore, terms such as "cell" and "carrier" in this disclosure may be rewritten as "BWP".

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

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

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

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

[0941] Furthermore, information, signals, etc., can be output in at least one of the following directions: from higher level (upper layer) to lower level (lower layer), and from lower layer to higher level. Information, signals, etc., can also be input and output via multiple network nodes.

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

[0943] The notification of information is not limited to the methods / implementations described in this disclosure, and may also be carried out by other methods. For example, the notification of information in this disclosure may also be implemented by physical layer signaling (e.g., downlink control information (DCI), uplink control information (UCI), etc.), higher layer signaling (e.g., radio resource control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB) etc.), medium access control (MAC) signaling), other signals, or combinations thereof.

[0944] In addition, physical layer signaling can also be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. Furthermore, RRC signaling can also be referred to as RRC messages, such as RRC connection setup messages, RRC connection reconfiguration messages, etc. Additionally, MAC signaling can also be notified using, for example, the MAC control element (CE).

[0945] Furthermore, notification of specific information (e.g., a notification that “is X”) is not limited to explicit notification, but can also be implicit (e.g., by not providing that specific information, or by providing other information).

[0946] The determination can be made by a value represented by a single bit (0 or 1), by a true or false value (boolean), or by a numerical comparison (e.g., a comparison with a specific value).

[0947] Whether software is called software, firmware, middleware, microcode, hardware description language, or any other name, it should be broadly interpreted to refer to 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, etc.

[0948] Furthermore, software, instructions, and information can also be sent and received via a transmission medium. For example, when software is sent from a website, server, or other remote source using at least one of wired technologies (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL) etc.) and wireless technologies (infrared, microwave, etc.), at least one of these wired and wireless technologies is included within the definition of a transmission medium.

[0949] The terms “system” and “network” as used in this disclosure are interchangeable. “Network” may also mean devices included in a network (e.g., base stations).

[0950] In this disclosure, the terms "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", "beamwidth", "beam angle", "antenna", "antenna element", and "panel" are used interchangeably.

[0951] In this disclosure, the terms "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" are used interchangeably. There are also instances where the terms macro cell, small cell, femtocell, and picocell are used to refer to a base station.

[0952] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, each of which can also provide communication services through a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). Terms such as "cell" or "sector" refer to a portion or all of the coverage area of ​​at least one of the base station and base station subsystem providing communication services within that coverage area.

[0953] In this disclosure, the base station sends information to the terminal, which can also be interchanged with the base station instructing the terminal to perform control / operation based on that information.

[0954] In this disclosure, the terms “Mobile Station (MS)”, “user terminal”, “user equipment (UE)”, and “terminal” are used interchangeably.

[0955] There are also instances where mobile stations are referred to as subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, handsets, user agents, mobile clients, clients, or several other appropriate terms.

[0956] At least one of the base station and the mobile station can also be referred to as a transmitting device, a receiving device, a wireless communication device, etc. Additionally, at least one of the base station and the mobile station can also be a device mounted on a moving object, the moving object itself, etc.

[0957] The term "mobile body" refers to a movable object whose speed is arbitrary, including situations where the body is stationary. Examples of such mobile bodies include vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, loading shovels, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, trolleys, rickshaws, ships (ships and other watercraft), airplanes, rockets, satellites, drones, multicopters, quadcopters, hot air balloons, and objects carried by them, but are not limited to these. Furthermore, the mobile body can also be a mobile body that moves autonomously based on operational commands.

[0958] The mobile entity can be a means of transportation (e.g., a vehicle, an airplane, etc.), a mobile entity moving in an unmanned manner (e.g., a drone, an autonomous vehicle, etc.), or a robot (humanized or unmanned). Additionally, at least one of the base station and the mobile station also includes a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station can also be an Internet of Things (IoT) device such as a sensor.

[0959] Figure 28 This is a diagram illustrating 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 speed sensor 51, a bar 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.

[0960] The drive unit 41 is comprised of at least one of an engine, a motor, or a combination of an engine and a motor. The steering unit 42 is configured to include at least a steering wheel (also called a steering handle) that steers at least one of the front wheels 46 and the rear wheels 47 based on operation of the steering wheel by the user.

[0961] The electronic control unit 49 consists of a microprocessor 61, a memory (ROM, RAM) 62, and a communication port (e.g., an input / output (IO) port) 63). Signals from various sensors 50-58 present in the vehicle are input to the electronic control unit 49. The electronic control unit 49 can also be referred to as an electronic control unit (ECU).

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

[0963] The information service unit 59 consists of various devices such as a navigation system, audio system, speakers, display, television, and radio, used to provide (output) various information such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices. The information service unit 59 uses information obtained from external devices via the communication module 60, etc., to provide various information / services (e.g., multimedia information / multimedia services) to the occupants of the vehicle 40.

[0964] 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.) or output devices that implement output to the outside (e.g., display, speaker, LED light, touch panel, etc.).

[0965] The driver assistance system unit 64 comprises various devices that provide functions for preventing accidents or reducing the driver's workload, such as millimeter-wave radar, light detection and ranging (LiDAR), cameras, locators (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyroscope systems (e.g., Inertial Measurement Unit (IMU)) and Inertial Navigation System (INS)), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. Furthermore, the driver assistance system unit 64 sends and receives various information via communication module 60 to realize driver assistance functions or autonomous driving functions.

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

[0967] The communication module 60, controlled by the microprocessor 61 of the electronic control unit 49, is a communication device capable of communicating with external devices. For example, it can transmit and receive various types of information wirelessly with external devices. The communication module 60 can be located both inside and outside the electronic control unit 49. External devices can be, for example, the aforementioned base station 10, user terminal 20, etc. Furthermore, the communication module 60 can be, for example, at least one of the aforementioned base station 10 and user terminal 20 (or function as at least one of the base station 10 and user terminal 20).

[0968] The communication module 60 can also wirelessly transmit at least one of the following to an external device: signals from the various sensors 50-58 input to the electronic control unit 49, information obtained based on these signals, and information based on input from an external (user) unit obtained via the information service unit 59. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc., can also be referred to as input units that receive input. For example, the PUSCH transmitted via the communication module 60 can also contain information based on the aforementioned input.

[0969] The communication module 60 receives various types of information (traffic information, traffic light information, workshop information, etc.) sent from external devices and displays them on the vehicle's information service unit 59. The information service unit 59 can also be referred to as an output unit for outputting information (e.g., information based on the PDSCH received through the communication module 60 (or data / information decoded according to the PDSCH) and outputting it to devices such as displays and speakers).

[0970] Furthermore, the communication module 60 stores various types of information received from external devices into a memory 62 that can be utilized by the microprocessor 61. Based on the information stored in the memory 62, the microprocessor 61 can also control the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, gear shift lever 45, left and right front wheels 46, left and right rear wheels 47, axle 48, and various sensors 50-58, etc., of the vehicle 40.

[0971] Furthermore, the base station in this disclosure can also be rewritten as a user terminal. For example, various methods / implementations of this disclosure can be applied to structures where communication between the base station and the user terminal is replaced by communication between multiple user terminals (e.g., also referred to as device-to-device (D2D) or vehicle-to-everything (V2X)). In this case, it can also be configured such that the user terminal 20 has the functions of the base station 10 described above. In addition, terms such as "uplink" and "downlink" can be rewritten as terms corresponding to inter-terminal communication (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can also be rewritten as sidelink channel.

[0972] Similarly, the user terminal in this disclosure can also be rewritten as a base station. In this case, it can also be configured such that the base station 10 has the functions of the user terminal 20 described above.

[0973] In this disclosure, actions purported to be performed by a base station may sometimes also be performed by its upper node, depending on the circumstances. Clearly, in a network comprising one or more network nodes having a base station, various operations performed for communication with a terminal can be performed by the base station, one or more network nodes other than the base station (e.g., consider a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc., but not limited to these), or combinations thereof.

[0974] The various methods / implementations described in this disclosure can be used individually, in combination, or switched as needed during execution. Furthermore, the processing procedures, timing sequences, flowcharts, etc., of the various methods / implementations described in this disclosure can be rearranged as long as they do not contradict each other. For example, regarding the methods described in this disclosure, the illustrated order is used to indicate various steps, but the order is not limited to the specific order indicated.

[0975] The various methods / implementations described in this disclosure can also be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG, where x is, for example, an integer or a decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Futuregeneration radio access (FX), Global System for Mobile Communications (GSM, a registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), and IEEE This includes 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-Wideband (UWB)), Bluetooth (registered trademark), systems utilizing other suitable wireless communication methods, and next-generation systems derived from, modified, generated, or specified based on these methods. Furthermore, multiple systems can be combined (e.g., LTE or LTE-A, combinations with 5G, etc.) for application.

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

[0977] Any reference to an element using the designations "first," "second," etc., as used in this disclosure does not comprehensively limit the quantity or order of these elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, reference to the first and second elements does not imply that only two elements may be used, or that the first element must take precedence over the second element in some form.

[0978] The term "determining" as used in this disclosure can encompass a wide variety of actions. For example, "determining" can also refer to judging, calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, database, or other data structure), and ascertaining.

[0979] In addition, "judgment (decision)" can also refer to receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, accessing (e.g., accessing data in memory), etc., as situations where "judgment (decision)" is performed.

[0980] Furthermore, "judgment (decision)" can also refer to situations where resolving, selecting, choosing, establishing, or comparing are considered as making a "judgment (decision)". That is, "judgment (decision)" can also refer to certain actions as situations where a "judgment (decision)" is made.

[0981] In addition, "judgment (decision)" can also be rewritten as "assuming", "expecting", "considering", etc.

[0982] The term "maximum transmit power" as used in this disclosure may refer to the maximum value of the transmit power, the nominal maximum transmit power, or the rated maximum transmit power.

[0983] As used in this disclosure, the terms “connected,” “coupled,” or all variations thereof, refer to all direct or indirect connections or combinations between two or more elements, and can include cases where there is one or more intermediate elements between two mutually “connected” or “coupled” elements. The connections or combinations between elements can be physical, logical, or a combination thereof. For example, “connection” can also be rewritten as “access.”

[0984] In this disclosure, when two elements are connected, it is possible to consider using more than one wire, cable, printed electrical connection, etc. to be "connected" or "combined" with each other, and as several non-limiting and non-inclusive examples, electromagnetic energy with wavelengths in the wireless frequency domain, microwave region, light (both visible and invisible) region can be used to be "connected" or "combined" with each other.

[0985] In this disclosure, the term "A is different from B" can also mean "A and B are different from each other." Additionally, the term can also mean "A and B are each different from C." Terms such as "separate" and "combined" can also be interpreted in the same way as "different."

[0986] When the terms "include," "including," and variations thereof are used in this disclosure, these terms, like the term "comprising," mean inclusive. Furthermore, the term "or" as used in this disclosure does not mean XOR.

[0987] In this disclosure, for example, in cases where articles are added through translation, such as a, an, and the in English, the disclosure may also include cases where the noun following these articles is in a plural form.

[0988] In this disclosure, terms such as "below," "less than," "above," "more than," and "equal to" can be interchanged. Furthermore, in this disclosure, terms meaning "good," "bad," "large," "small," "high," "low," "early," "late," "wide," and "narrow" are not limited to the positive, comparative, and superlative degrees and can be interchanged. Additionally, in this disclosure, expressions that prescribe "i" (where i is any integer) to terms meaning "good," "bad," "large," "small," "high," "low," "early," "late," "wide," and "narrow" are not limited to the positive, comparative, and superlative degrees and can be interchanged (for example, "highest" and "i-th highest" can also be interchanged).

[0989] In this disclosure, the terms “of,” “for,” “regarding,” “related to,” and “associated with” can be interchanged.

[0990] The invention disclosed herein has been described in detail above. However, it will be apparent to those skilled in the art that the invention is not limited to the embodiments described herein. The invention can be implemented as modifications and variations without departing from the spirit and scope of the invention as defined by the claims. Therefore, the description herein is for illustrative purposes and does not imply any limitation on the invention.

[0991] This application is based on Japanese Special Application 2023-192789, filed on November 13, 2023. Its contents are incorporated herein in their entirety.

Claims

1. A terminal, comprising: The transmitting unit transmits capability information related to the dynamic transform precoder indication used in operation with multiple component carriers within a single band domain; and The control unit controls the reception of the settings indicated by the dynamic transformation pre-encoder.

2. The terminal according to claim 1, wherein, The capability information includes at least one of the following: the number of component carriers supporting the dynamic transform precoder indication, the number of consecutive component carriers supporting the dynamic transform precoder indication, and the number of non-consecutive component carriers supporting the dynamic transform precoder indication.

3. The terminal according to claim 1, wherein, If at least one of the following conditions is met: the multiple component carriers are discontinuous, or more than one of the multiple component carriers simultaneously transports uplinks with non-zero bandwidth, then at least one of the settings and the dynamic transformation precoder indication is received.

4. The terminal according to claim 1, wherein, If the conditions of discontinuous component carriers, simultaneous uplink transmission of more than one component carrier with non-zero bandwidth within the multiple component carriers are not met, and the dynamic change precoder indication is received, the control unit ignores at least one of the following: the setting, the dynamic change precoder indication, and downlink control information containing the dynamic change precoder indication.

5. A wireless communication method, which is a wireless communication method for a terminal, comprising: The steps of transmitting and supporting dynamic transform precoder indication of relevant capability information in operation using multiple component carriers within a single band domain; and The steps for receiving the settings indicated by the dynamic transformation precoder.

6. A base station, comprising: The receiving unit receives capability information related to the dynamic transform precoder indication used in operation with multiple component carriers within a single band; and The control unit controls the transmission of the settings indicated by the dynamic transformation pre-encoder.

Images