Terminal, wireless communication method, and base station

Abstract

A terminal according to one aspect of the present disclosure has a reception unit that receives a first setting for a dynamic conversion precoder instruction and a control unit that, on the basis of whether the terminal has reported specific capability information, determines whether a specific frequency domain (FD)-orthogonal cover code (OCC) that is longer than 2 is to be applied to a demodulation reference signal (DMRS) for a physical uplink shared channel (PUSCH).

Description

Terminal, wireless communication method and base station

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

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

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

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

[0005] For layer orthogonalization, a multi-port reference signal (for example, a demodulation reference signal (DMRS)) is used.

[0006] In future wireless communication systems, it is being considered to increase the number of DMRS ports compared to the existing specifications. However, the configuration and application of DMRS in this case has not been sufficiently considered. If DMRS is not configured and applied appropriately, there is a risk that communication throughput and communication quality will deteriorate.

[0007] Therefore, one of the objects of the present disclosure is to provide a terminal, a wireless communication method, and a base station that apply an appropriate DMRS.

[0008] A terminal according to one aspect of the present disclosure includes a receiving unit that receives a first setting of a dynamic conversion precoder indication, and a control unit that determines whether a specific frequency domain (FD)-orthogonal cover code (OCC) longer than 2 is applied to a demodulation reference signal (DMRS) for a physical uplink shared channel (PUSCH) based on whether the terminal reports specific capability information.

[0009] According to one aspect of the present disclosure, an appropriate DMRS can be applied.

[0010] FIGS. 1A-1B show an example of a legacy DMRS port table for DMRS configuration type 1 / 2 for PDSCH. FIGS. 2A-2B show an example of a legacy DMRS port table for DMRS configuration type 1 / 2 for PUSCH. FIGS. 3A-3B show an example of associations between CDM groups, DMRS ports, and OCCs for Extension Type 1 / Extended Type 2. FIG. 4 shows an example of parameters for PDSCH DMRS configuration type 1. FIG. 5 shows an example of parameters for PDSCH DMRS configuration type 2. FIG. 6 shows an example of parameters for PUSCH DMRS configuration type 1. FIG. 7 shows an example of parameters for PUSCH DMRS configuration type 2. FIGS. 8A-8B show an example of mapping of DMRS and FD-OCC to REs for DMRS Extension Type 1. FIGS. 9A-9B show an example of mapping of DMRS and FD-OCC to REs for DMRS Extension Type 2. FIG. 10 shows another example of mapping of DMRS and FD-OCC of DMRS extension type 2 to REs. FIG. 11A is a diagram showing an example of processing time for PDSCH processing capability 1. FIG. 11B is a diagram showing an example of processing time for PDSCH processing capability 2. FIG. 12 is a diagram showing an example of a description of specifications related to the PDSCH processing procedure time of a UE. FIG. 13 shows an example of a part of procedure C. FIG. 14 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 15 is a diagram showing an example of a configuration of a base station according to an embodiment. FIG. 16 is a diagram showing an example of a configuration of a user terminal according to an embodiment. FIG. 17 is a diagram showing an example of the hardware configuration of a base station and a user terminal according to an embodiment. FIG. 18 is a diagram showing an example of a vehicle according to an embodiment.

[0011] (DMRS) The front-loaded Demodulation Reference Signal (DMRS) is the first (first symbol or symbol close to the first) DMRS for faster demodulation. An additional DMRS can be configured by RRC for high-speed mobile terminals (user terminals, User Equipment (UE)) or high modulation and coding schemes (MCS) / ranks. The frequency location of the additional DMRS is the same as that of the front-loaded DMRS.

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

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

[0014] For the frequency domain, (PDSCH / PUSCH) DMRS configuration type 1 or 2 is configured. DMRS configuration type 1 has a comb structure and is applicable to both CP-OFDM (transport precoding=disabled) and DFT-S-OFDM (transport precoding=enabled). DMRS configuration type 2 is applicable only to CP-OFDM.

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

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

[0017] Double-symbol DMRS is used for more DMRS ports (especially Multi-User Multiple Input Multiple Output (MU-MIMO)). In double-symbol DMRS, the number of additional DMRS (symbols) is {0, 1}. Double-symbol DMRS is supported when frequency hopping is disabled. If the maximum number (maxLength) in the uplink DMRS configuration (DMRS-UplinkConfig) is 2 (len2), whether it is single-symbol DMRS or double-symbol DMRS is determined by DCI or configured grant.

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

[0019] Multiple DMRS ports that are mapped to the same resource element (RE, time and frequency resource) are called a DMRS Code Division Multiplexing (CDM) group.

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

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

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

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

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

[0025] In the parameters for PDSCH DMRS (existing table, existing DMRS port table, FIG. 1), 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.

[0026] In the parameters for PUSCH DMRS (existing table, existing DMRS port table, FIG. 2), 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.

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

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

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

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

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

[0032] In the present disclosure, OCC, orthogonal code, orthogonalization, and cyclic shift may be read interchangeably.

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

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

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

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

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

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

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

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

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

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

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

[0044] The TD-OCC and FD-OCC of the DMRS in Rel. 15 NR both correspond to OCCs with a sequence length (which may also be referred to as OCC length) of 2. For example, Rel. 15 Type 1 / Type 2 DMRS ports (e.g., rel. 15 Type 1 / Type 2 DMRS ports) may be defined as DMRS ports with an FD-OCC length of 2 (e.g., DMRS ports with FD-OCC length = 2).

[0045] Therefore, the possible values ​​of k' and l' are both 0 and 1. By multiplying this FD-OCC in units of RE, it is possible to multiplex two-port DMRS using the same time and frequency resource (2 RE). When both this FD-OCC and TD-OCC are applied, it is possible to multiplex four-port DMRS using the same time and frequency resource (4 RE).

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

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

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

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

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

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

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

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

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

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

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

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

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

[0059] Options 1 / 3 may be supported. In addition, TD OCC may be supported. The difference between options 2 and 5 may be whether semi-static switching based on RRC or dynamic switching based on DCI is supported between FD-OCC and TD-OCC.

[0060] In option 5 of the aforementioned method for increasing the number of DMRS ports, a new FD-OCC of length 4 is applied, and a new TD-OCC of length 2 is applied to multiple discontinuous DMRS symbols, so that the number of DMRS ports in one CDM group may be 4. In this case, the receiving side can separate signals by decoding either the FD-OCC or the TD-OCC, which is advantageous compared to option 1 / 3. For example, if using a TD-OCC causes problems such as degradation of characteristics (orthogonality) during high-speed movement, or channel estimation cannot be initiated even when only the leading DMRS symbol is received, and additional DMRS symbols must be received, resulting in a delay in PDSCH decoding, the receiving side can decode using only the FD-OCC. For example, if using an FD-OCC causes problems such as degradation of characteristics (orthogonality) when the delay spread is large, the receiving side can decode using only the TD-OCC.

[0061] In the aforementioned option 5 for increasing the number of DMRS ports, a new FD-OCC of length 6 may be applied, and a new TD-OCC of length 2 may be applied to multiple non-consecutive DMRS symbols.

[0062] Thus, new FD-OCCs longer than 2 are supported in Rel. 18 and later. DMRS ports for Type 1 / Type 2 for Rel. 18 and later may be referred to as Rel. 18 enhanced type 1 / enhanced type 2 DMRS ports, for example. Enhanced type 1 / enhanced type 2 may be referred to as eType 1 / eType 2.

[0063] For example, a Rel. 18 eType1 / eType2 DMRS port may be defined with an FD-OCC length greater than 2. For example, the FD-OCC length of a Rel. 18 eType1 / eType2 DMRS port may be 4.

[0064] Note that a Type 1 / Type 2 DMRS port with FD-OCC length = 2 defined in Rel. 15 may be referred to as a Rel. 15 Type 1 / Type 2 DMRS port.

[0065] Rel. 18 e Type 1 DMRS ports may have port index p=#1000-1015. For example, the same DMRS port index (DMRS port #1000-#1007) as the Rel. 15 DMRS ports may be used for DMRS ports with new FD-OCCs #0 and #1. DMRS ports with new FD-OCCs #2 and #3 may use different DMRS port indexes (DMRS port #1008-#1015, Rel. 18 DMRS ports) from the Rel. 15 DMRS ports.

[0066] Rel. 18 e Type 2 DMRS ports may have port index p = #1000-1023. For DMRS ports with new FD-OCCs #0 and #1, the same DMRS port index (DMRS ports #1000-#1011) as for Rel. 15 DMRS ports may be used. For DMRS ports with new FD-OCCs #2 and #3, different DMRS port indexes (DMRS ports #1012-#1023, Rel. 18 DMRS ports) may be used.

[0067] In Rel. 18, a length-4 FD-OCC is supported as a new OCC for DMRS (enhanced type 1 / enhanced type 2 DMRS) of PDSCH / PUSCH.

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

[0069] Some of the sequences of the new FD-OCC may be associated with Rel. 15 DMRS port numbers / indexes.

[0070] In the present disclosure, legacy DMRS, legacy DMRS function, legacy DMRS type, legacy DMRS configuration type, dmrs-Type, DMRS configuration type 1 / 2, DMRS with FD-OCC of length 2, and Rel. 15 DMRS type may be interchangeable. In the present disclosure, the terms "the legacy DMRS configuration type is configured," "the legacy DMRS configuration type 1 or 2 is configured," and "the extended DMRS type is not configured" may be interchangeable. In the present disclosure, the terms "DMRS configuration type 1," "DMRS type 1," "DMRS type = 1," "DMRS type 1," and "dmrs-Type set to type 2 is not configured" may be interchangeable. In the present disclosure, the terms "DMRS configuration type 2," "DMRS type 2," "DMRS type = 2," "DMRS type 2," and "dmrs-Type set to type 2 is configured" may be interchangeable.

[0071] In the present disclosure, the terms "extended DMRS," "extended DMRS capability," "extended DMRS type," "extended DMRS configuration type," "configuration / upper layer parameters for extended DMRS type," "extended DMRS type," "enhanced-dmrs-Type_r18," "dmrs-TypeEnh," "extended DMRS configuration type 1 / 2," "DMRS with FD-OCC of length 4," and "Rel. 18 DMRS type" may be interchangeable. In the present disclosure, the terms "extended DMRS configuration type is configured," "enhanced-dmrs-Type_r18 is configured," "extended DMRS configuration type 1 or 2 is configured," and "extended DMRS type is configured" may be interchangeable. In the present disclosure, the terms "extended DMRS configuration type 1," "DMRS extension type 1," "DMRS extension type=1," "DMRS eType 1," "the extended DMRS type is configured and dmrs-Type set to type 2 is not configured" may be interchangeable. In the present disclosure, extended DMRS setting type 2, DMRS extended type 2, DMRS extended type = 2, DMRS eType 2, an extended DMRS type is set and a dmrs-Type set to type 2 is set, may be read interchangeably.

[0072] The extended DMRS configuration type 1 (DMRS extension type 1, DMRS extension type = 1, DMRS eType 1) uses the frequency domain configuration of the DMRS configuration type 1 (DMRS type 1, DMRS type = 1, DMRS Type 1) and a new FD-OCC. The extended DMRS configuration type 2 (DMRS extension type 2, DMRS extension type = 2, DMRS eType 2) uses the frequency domain configuration of the DMRS configuration type 2 (DMRS type 2, DMRS type = 2, DMRS Type 2) and a new FD-OCC.

[0073] In the present disclosure, the maximum DMRS length, maxLength, and the maximum number of OFDM symbols for a front loaded DMRS may be read interchangeably.

[0074] In this disclosure, FD-OCC, w f (k') may be read interchangeably. t (l'), a TD-OCC of length 2, may be read interchangeably.

[0075] In this disclosure, the terms existing OCC, existing FD-OCC, FD-OCC of length 2, and Rel. 15 FD-OCC may be interchangeable. In this disclosure, the terms new OCC, new FD-OCC, FD-OCC longer than 2, Rel. 18 FD-OCC, and w f (k'), FD-OCC of length 4, may be read interchangeably.

[0076] In the present disclosure, the terms "existing DMRS port," "Rel. 15 DMRS port," "DMRS port to which the existing FD-OCC is applied," "DMRS port within the port number range of the existing DMRS," "existing DMRS port," and "existing DMRS" may be interchangeable. In the present disclosure, the terms "new DMRS port," "Rel. 18 DMRS port," "DMRS port to which the new FD-OCC is applied," "DMRS port outside the port number range of the existing DMRS," "extended DMRS port," and "extended DMRS" may be interchangeable.

[0077] (Configuration of Extended DMRS Configuration Type) RRC parameters for configuration of Rel. 18 DMRS (Extended Type 1 / 2) are under consideration.

[0078] The PDSCH configuration (PDSCH-Config) may include a downlink (DL) DMRS configuration (DMRS-DownlinkConfig) for configuring DMRS for the PDSCH. DMRS-DownlinkConfig may include dmrs-Type, dmrs-AdditionalPosition, maxLength, scramblingID0, scramblingID1, phaseTrackingRS, and dmrs-Downlink-r16, and may further include enhanced-dmrs-Type_r18. dmrs-Downlink-r16 indicates whether low-PAPR DMRS is used. If dmrs-Downlink-r16 is set to 'enabled', low-PAPR DMRS is used.

[0079] enhanced-dmrs-Type_r18 is the selection of the enhanced DMRS type. If the enhanced-dmrs-Type_r18 field is not present, the UE uses legacy DMRS type 1 or legacy DMRS type 2 depending on the dmrs-Type. If the enhanced-dmrs-Type_r18 field is present, and if the dmrs-Type field set to type 2 is not present in the DMRS-DownlinkConfig, the UE uses enhanced DMRS type 1, and if the dmrs-Type field set to type 2 is present in the DMRS-DownlinkConfig, the UE uses enhanced DMRS type 2.

[0080] The PUSCH configuration (PUSCH-Config) may include an uplink (UL) DMRS configuration (DMRS-UplinkConfig) for configuring DMRS for the PUSCH. DMRS-UplinkConfig may include dmrs-Type, dmrs-AdditionalPosition, maxLength, transformPrecodingDisabled, and transformPrecodingEnabled. transformPrecodingDisabled may include scramblingID0, scramblingID1, and dmrs-Uplink-r16, and may further include enhanced-dmrs-Type_r18. dmrs-Uplink-r16 indicates whether low-PAPR DMRS is used. If dmrs-Uplink-r16 is set to 'enabled', low-PAPR DMRS is used.

[0081] enhanced-dmrs-Type_r18 is the selection of the enhanced DMRS type. If the enhanced-dmrs-Type_r18 field is not present, the UE uses legacy DMRS type 1 or legacy DMRS type 2 depending on the dmrs-Type. If the enhanced-dmrs-Type_r18 field is present, the UE uses enhanced DMRS type 1 if the dmrs-Type field set to type 2 is not present in the DMRS-UplinkConfig, and the UE uses enhanced DMRS type 2 if the dmrs-Type field set to type 2 is present in the DMRS-UplinkConfig.

[0082] For a PDSCH of PDSCH mapping type A / B, if the DMRS downlink configuration (DMRS-DownlinkConfig) corresponding to that mapping type does not have dmrs-Type set to type 2, the UE applies DMRS configuration type 1 to the DMRS of that PDSCH, and if the DMRS downlink configuration (DMRS-DownlinkConfig) corresponding to that mapping type has dmrs-Type set to type 2, the UE applies DMRS configuration type 2 to the DMRS of that PDSCH. For a PUSCH of PUSCH mapping type A / B, if the DMRS uplink configuration (DMRS-UplinkConfig) corresponding to that mapping type does not have dmrs-Type set to type 2, the UE applies DMRS configuration type 1 to the DMRS of that PUSCH, and if the DMRS-UplinkConfig corresponding to that mapping type has dmrs-Type set to type 2, the UE applies DMRS configuration type 2 to the DMRS of that PUSCH.

[0083] (CDM Group) As mentioned above, multiple DMRS ports that are mapped to the same RE (time and frequency resource) may be referred to as a DMRS CDM group.

[0084] 3A is a diagram showing an example of association between CDM groups, DMRS ports, and OCCs in Extended Type 1. FIG. 3B is a diagram showing an example of association between CDM groups, DMRS ports, and OCCs in Extended Type 2. The DMRS ports in FIG. 3A and FIG. 3B may be referred to as extended DMRS ports. Note that FIG. 3A and FIG. 3B are applicable to both single-symbol DMRS and double-symbol DMRS.

[0085] As shown in Figure 3A, eight DMRS ports (ports #0-3, 8-11) can be used for DMRS configuration extension type 1 and single-symbol DMRS. Within each DMRS CDM group (CDM group #0-1), four DMRS ports (ports #0-1, 8-9, port #2-3, 10-11) are multiplexed using a length-4 FD-OCC (FD-OCC #0-3). Between multiple DMRS CDM groups (two DMRS CDM groups (CDM group #0-1)), two DMRS ports are multiplexed using FDM.

[0086] Also, as shown in FIG. 3A , in the case of DMRS configuration extension type 1 and double-symbol DMRS, eight more DMRS ports (ports #4-7, 12-15) can be used. Within each DMRS CDM group (CDM group #0-1), four DMRS ports (ports #4-5, 12-13, port #6-7, 14-15) are multiplexed using a FD-OCC #0-3 of length 4. Between multiple DMRS CDM groups (two DMRS CDM groups (CDM group #0-1)), two DMRS ports are multiplexed using FDM. Furthermore, two DMRS ports in the time direction are multiplexed using a TD-OCC #0-1 of length 2. That is, multiple (two) CDM groups with the same index are multiplexed using TDM.

[0087] In the extension type 1 shown in FIG. 3A, the DMRS ports corresponding to CDM group #0 are {port#0,1,8,9} and {port#4,5,12,13}, and the DMRS ports corresponding to CDM group #1 are {port#2,3,10,11} and {port#6,7,14,15}.

[0088] As shown in Figure 3B, 12 DMRS ports (ports #0-5, 12-17) can be used for DMRS configuration extension type 2 and single-symbol DMRS. Within each DMRS CDM group (CDM group #0-2), four DMRS ports (ports #0-1, 12-13, port #2-3, 14-15, port #4-5, 16-17) are multiplexed using a length-4 FD-OCC (FD-OCC #0-3). Between multiple DMRS CDM groups (three DMRS CDM groups (CDM group #0-2)), three DMRS ports are multiplexed using FDM.

[0089] Also, as shown in FIG. 3B , in the case of DMRS configuration extension type 2 and double-symbol DMRS, an additional 12 DMRS ports (ports #6-11, 18-23) can be used. Within each DMRS CDM group (CDM group #0-2), four DMRS ports (ports #6-7, 18-19, port #8-9, 20-21, port #10-11, 22-23) are multiplexed using a FD-OCC #0-3 of length 4. Between multiple DMRS CDM groups (three DMRS CDM groups (CDM group #0-2)), three DMRS ports are multiplexed using FDM. Furthermore, two DMRS ports in the time direction are multiplexed using a TD-OCC #0-1 of length 2. That is, multiple (two) CDM groups with the same index are multiplexed using TDM.

[0090] In the extended type 2 shown in Figure 3B, the DMRS ports corresponding to CDM group #0 are {port #0, 1, 12, 13} and {port #6, 7, 18, 19}, the DMRS ports corresponding to CDM group #1 are {port #2, 3, 14, 15} and {port #8, 9, 20, 21}, and the DMRS ports corresponding to CDM group #2 are {port #4, 5, 16, 17} and {port #10, 11, 22, 23}.

[0091] (DMRS Port Combinations) In the antenna port indication of DMRS ports for PUSCH with DMRS maximum length = 1 / 2, Extended Type 1, and Extended Type 2, it is considered that all of the following categories of DMRS port combinations can be indicated: (Category 1) Combinations of multiple indices of existing DMRS ports (p = 0 to 7 for Extended Type 1, p = 0 to 11 for Extended Type 2). (Category 2) Combinations of multiple indices of new DMRS ports (p = 8 to 15 for Extended Type 1, p = 12 to 23 for Extended Type 2). (Category 3) Combinations of existing DMRS port indices and new DMRS port indices within one CDM group with at least DMRS max length = 1 (for Extended Type 1, at least one combination of up to 4 ports from p = {0,1,8,9} and up to 4 ports from p = {2,3,10,11}; for Extended Type 2, at least one combination of up to 4 ports from p = {0,1,12,13} and up to 4 ports from p = {2,3,14,15}). For up to 4 ranks, only one CDM group is used. For more than 4 ranks, more than one CDM group can be used.

[0092] Similarly, the DMRS port for the PDSCH is determined by p+1000.

[0093] It is being considered that maximum DMRS length = 1 and rank = 5, 6, 7, 8 will be supported in the DMRS port of Extended Type 1 / Extended Type 2 for PDSCH / PUSCH.

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

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

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

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

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

[0099] (Enabling and Disabling Transform Precoding: Physical layer procedures for data / Physical uplink shared channel related procedure / UE procedure for transmitting the physical uplink shared channel / UE procedure for applying transform precoding on PUSCH) For a PUSCH scheduled by a PDCCH with CRC scrambled by a CS-RNTI, C-RNTI, MCS-C-RNTI or SP-CSI-RNTI with new data indicator (NDI) = 1, the UE shall follow the following procedures: - If a DCI with a scheduling grant is received using DCI format 0_0, the UE shall consider transform precoding as enabled or disabled for this PUSCH transmission according to the parameter msg3-transformPrecoder set by higher layers. - If a DCI with a scheduling grant is not received using DCI format 0_0, the UE shall follow the following procedures: -- If a DCI with a scheduling grant is received using DCI format 0_1 ​​or 0_2 with a CRC scrambled by a C-RNTI, an MCS-C-RNTI, or a CS-RNTI with NDI=1, and the UE is configured with the upper layer parameter dynamicTransformPrecoderIndicationDCI-0-1 in pusch-Config for DCI format 0_1 ​​or the upper layer parameter dynamicTransformPrecoderIndicationDCI-0-2 in pusch-Config for DCI format 0_2, and the upper layer parameter is set to enabled ('enabled'), the UE shall consider transform precoding to be enabled or disabled for this PUSH transmission according to the transform precoder indicator field in the DCI with the scheduling grant.--- For pusch-TimeDomainAllocationListForMultiPUSCH in pusch-Config, the UE enables or disables transform precoding for all PUSCH transmissions according to the transform precoder indicator field in DCI format 0_1 ​​with scheduling grant. --- Otherwise, the UE follows the following procedure: --- If the UE is configured with the upper layer parameter transformPrecoder in pusch-Config, the UE enables or disables transform precoding for this PUSCH transmission according to this parameter. --- If the UE is not configured with the upper layer parameter transformPrecoder in pusch-Config, the UE enables or disables transform precoding for this PUSCH transmission according to the upper layer parameter msg3-transformPrecoder.

[0100] (Dynamic Switching Between Disabling and Enabling the Transform Precoder) For more flexible throughput control, it is conceivable to dynamically switch between CP-OFDM and DFT-s-OFDM using DCI / MAC CE. However, such dynamic switching has not yet been studied.

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

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

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

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

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

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

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

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

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

[0110] (Issues) It is being considered that the Rel. 18 DMRS extension be applied only to CP-OFDM. However, the relationship between the transform precoder setting and the DMRS setting has not been fully considered, including which procedure is defined and which RRC parameters are used for setting. If such a relationship is not fully considered, it may result in an increase in PAPR and a decrease in communication quality / throughput.

[0111] Therefore, the present inventors came up with a method for setting DMRS.

[0112] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. Each of the following embodiments (e.g., each case) may be used alone or in combination of at least two of them.

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

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

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

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

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

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

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

[0120] In this disclosure, a b , a_b, and a with b added to the bottom right of a may be read interchangeably. c , a^c, and the notation of a with c added to the upper right of a may be read interchangeably. b c, a_b^c, a notation with b added to the bottom right of a and c added to the top right, may be read as interchangeable. In the present disclosure, ceil(x), ceiling function, and ceiling function may be read as interchangeable. In the present disclosure, floor(x), floor function, and floor function may be read as interchangeable. In the present disclosure, sqrt(x), square root (root), may be read as interchangeable. In the present disclosure, x ~ may be expressed by adding 〜 to the x, or may be referred to as x tilde. - may be represented by placing a minus sign (-) above x, or may be referred to as x bar. In this disclosure, x mod y, mod(x,y), mod function, and modulo operation may be interchangeable.

[0121] In the present disclosure, the terms port, antenna port, and DMRS port may be read interchangeably.

[0122] In the present disclosure, the DMRS port (number) p for PUSCH and the DMRS port (number) 1000+p for PDSCH may be read as interchangeable.

[0123] In the present disclosure, dynamic switching of a waveform (CP-OFDM or DFT-s-OFDM), dynamic waveform switching (DWS), dynamic indication of enabling / disabling a transform precoder, and dynamic transform precoder indication may be read as interchangeable. In the present disclosure, dynamic waveform switching setting, dynamic transform precoder indication setting, dynamicTransformPrecoderIndicationDCI-0-1 or dynamicTransformPrecoderIndicationDCI-0-2 may be read as interchangeable.

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

[0125] In the present disclosure, dynamic waveform switching (DWS), Rel. 18 DWS, and dynamic transform precoder indication may be interchangeable. In the present disclosure, the terms "dynamically switching the PUSCH waveform is possible," "dynamically switching the PUSCH waveform is configured," "DWS is configured," and "DWS is enabled" may be interchangeable.

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

[0127] (Wireless Communication Method) Table D-1 shown in Fig. 4 shows an example of parameters for PDSCH DMRS configuration type 1. Table D-2 shown in Fig. 5 shows an example of parameters for PDSCH DMRS configuration type 2. Table U-1 shown in Fig. 6 shows an example of parameters for PUSCH DMRS configuration type 1. Table U-2 shown in Fig. 7 shows an example of parameters for PUSCH DMRS configuration type 2. The parameters in each table are assigned to PDSCH DMRS port p or PUSCH DMRS port p. ~ , CDM group λ, Δ for frequency offset, FD-OCC W f (k'), TD-OCC W t (l'), including

[0128] The UE assigns each DMRS port p or p in the DMRS port combination corresponding to the antenna port field value. ~ , for λ, Δ, W f (k'), W t If the enhanced DMRS type (enhanced-dmrs-Type_r18 or dmrs-TypeEnh) is not configured, the FD-OCC W of length 2 corresponding to k'=0,1 is applied. f(k') is applied to DMRS. When the enhanced DMRS type (enhanced-dmrs-Type_r18 or dmrs-TypeEnh) is configured, the FD-OCC W of length 4 corresponding to k'=0, 1, 2, 3 is applied. f (k') is applied to DMRS.

[0129] DMRS port p / p in DMRS setting type 1 / 2 for PDSCH / PUSCH ~ The existing DMRS port is a DMRS port within the range of the port number of the existing DMRS, and p=1000-1007 in the PDSCH DMRS configuration type 1 and p=1000-1007 in the PUSCH DMRS configuration type 1. ~ = 0-7, p = 1000-1011 in PDSCH DMRS setting type 2, p = 1000-1011 in PUSCH DMRS setting type 2 ~ The new DMRS port is a DMRS port outside the range of port numbers of the existing DMRS, and p = 1008-1015 in the PDSCH DMRS configuration type 1, and p = 1008-1015 in the PUSCH DMRS configuration type 1. ~ = 8-15, p = 1012-1023 in PDSCH DMRS setting type 2, p = 1012-1023 in PUSCH DMRS setting type 2 ~ =12-23.

[0130] For a certain configuration type, the first length 2 (k' = 0, 1) FD-OCC among the length 4 (k' = 0, 1, 2, 3) FD-OCCs corresponding to a certain port number of an existing DMRS port is the same as the length 2 FD-OCC corresponding to the same port number for the same configuration type of the existing DMRS (Rel. 15).

[0131] If the enhanced DMRS type (enhanced-dmrs-Type_r18 or dmrs-TypeEnh) is not configured, the antenna port field value indicates a DMRS port combination from only existing DMRS ports. If the enhanced DMRS type (enhanced-dmrs-Type_r18 or dmrs-TypeEnh) is configured, the antenna port field value indicates a DMRS port combination from existing DMRS ports and new DMRS ports.

[0132] FIG. 8A shows the DMRS and FD-OCC (W f (0),W f (1), W f (2), W f 8B shows an example of mapping of DMRS and FD-OCC (W f (0),W f (1), W f (2), W f DMRS ports #0 and #2 correspond to CDM groups #0 and #1, respectively, and are mapped to different REs and FDM-multiplexed.

[0133] FIG. 9A shows the DMRS and FD-OCC (W f (0),W f (1), W f (2), W f 9B shows an example of mapping of DMRS and FD-OCC (W f (0),W f (1), W f (2), W f 10 shows an example of mapping of DMRS and FD-OCC (W f (0),W f (1), W f (2), W fDMRS ports #0, #2, and #4 correspond to different CDM groups #0, #1, and #2, respectively, and are mapped to different REs and FDM-multiplexed.

[0134] <Embodiment 1> This embodiment relates to the PDSCH processing procedure time of the UE.

[0135] In the present disclosure, the PDSCH processing procedure time and the PDSCH processing time may be read interchangeably.

[0136] In the present disclosure, capability 1 / capability 2 may be interchangeably read as UE processing capability 1 / UE processing capability 2 for PDSCH.

[0137] (PDSCH Processing Time) With regard to the PDSCH processing time, two capabilities (Capability 1 / Capability 2) are defined in the current specifications.

[0138] In existing specifications (e.g., Rel. 15 NR), the PDSCH processing time is classified into two: the processing time for UE capability 1 and the processing time for UE capability 2. The processing time for UE capability 2 is shorter than the processing time for UE capability 1.

[0139] On the other hand, Rel. 18 DMRS targets supporting higher MU-MIMO layers in high-speed and high-capacity (e.g., enhanced Mobile Broadband (eMBB)) scenarios.

[0140] However, the FD-OCC with length 4 has poor performance for channel estimation, and the channel estimation itself is a complex process. Therefore, it is not very suitable to apply Rel. 18 DMRS in ultra-reliable and low-latency communications (URLLC) scenarios.

[0141] That is, it is not very desirable for a UE to simultaneously support PDSCH processing capabilities (especially UE processing capability 2) and DMRS of Rel. 18. Therefore, the UE needs to report / indicate to the network (e.g., base station) whether it simultaneously supports UE processing capability 2 and DMRS of Rel. 18.

[0142] More specifically, it is necessary for the UE not to simultaneously support UE processing capability 2 and Rel. 18 DMRS, or to introduce a UE capability that indicates whether the UE simultaneously supports UE processing capability 2 and Rel. 18 DMRS.

[0143] With the introduction of a UE feature group (FG) that indicates whether a UE simultaneously supports UE processing capability 2 and Rel. 18 DMRS, the UE can additionally report a relaxation of processing delay (computation delay) for PDSCH processing capability 2 within the UE feature group.

[0144] For example, if the UE reports (the capability for) processing delay mitigation, the processing delay mitigation may be used for the calculation of the PDSCH processing delay.

[0145] Furthermore, the mitigation of processing delays for UE processing capability 1 is not clearly defined.

[0146] Here, as a new parameter corresponding to the reduction of the processing delay, d ３ A new parameter d ３ may be referred to as a processing delay parameter and may be added to the processing delay calculation formula described below.

[0147] If the processing delay parameter is not implemented, processing delay mitigation may not be supported.

[0148] Details will be described later. ３ Candidate values ​​for may include at least 0 (for UE processing capability 1).

[0149] (Example of description of specifications) Below, a specific example of description of specifications will be described. The following description is merely an example, and the names of corresponding specific UE capabilities, etc., can be changed as appropriate. The UE may control processing / calculation related to the PDSCH based on the following example description. Fig. 11A is a diagram showing an example of processing time for PDSCH processing capability 1. Fig. 11B is a diagram showing an example of processing time for PDSCH processing capability 2. Fig. 12 is a diagram showing an example of description of specifications related to the PDSCH processing procedure time of the UE.

[0150] The UE shall provide a valid HARQ-ACK message after a certain timing (e.g. after the end of the last symbol of the PDSCH carrying the acknowledged transport block (TB)) if the following conditions are met: The first uplink symbol of the PUCCH carrying HARQ-ACK information is within the symbol L １ If you don't start earlier than that.

[0151] Here, the HARQ-ACK information (first UL symbol) is assigned HARQ-ACK timing K １ and K ｏｆｆｓｅｔ This is defined by the PUCCH resource used (if configured) and may include the effect / impact of timing advance.

[0152] K １ and K. ｏｆｆｓｅｔ may be a higher layer parameter related to (the offset of) the HARQ-ACK timing.

[0153] The above-mentioned L １ is a processing time T ｐｒｏｃ，１ is defined as the next upstream symbol after which the cyclic prefix (CP) starts, where T ｐｒｏｃ，１ is calculated by the following formula: ｐｒｏｃ，１ = (N １ +d １，１ +d ２ +d ３ )(2048+144)・κ2 －μ ・T Ｃ +T ｅｘｔ

[0154] Here, N１ may be determined based on μ in FIG. 11A (processing capacity 1) and FIG. 11B (processing capacity 2). μ is the maximum T ｐｒｏｃ，１ μ ＰＤＣＣＨ , μ ＰＤＳＣＨ , μ ＵＬ corresponds to either of the following:

[0155] For example, μ ＰＤＣＣＨ μ corresponds to the subcarrier spacing of the PDCCH that schedules the PDSCH. ＰＤＳＣＨ corresponds to the subcarrier spacing of the scheduled PDSCH. ＵＬ corresponds to the subcarrier spacing of a certain uplink channel.

[0156] Here, an uplink channel is an uplink channel on which HARQ-ACK is assumed to be transmitted, regardless of whether PDSCH reception provides a transport block of a HARQ process with disabled HARQ-ACK information, as indicated by HARQ-feedbackEnabling-disablingperHARQprocess (if set).

[0157] HARQ-feedbackEnabling-disablingperHARQprocess may be a higher layer parameter related to the setting indicating whether or not HARQ feedback is enabled in the HARQ process.

[0158] κ is T Ｓ and T Ｃ κ is a constant that indicates the ratio between Ｓ / T Ｃ = 64, where T Ｓ denotes the basic time unit for LTE, and T Ｃ denotes the base time for NR.

[0159] d １，１ , d ２ may be a value determined based on the PDSCH processing capability, the PDSCH mapping type, the corresponding PDCCH, and the number of PDSCH symbols.

[0160] As shown in FIG. 12, for a UE processing capacity of 2, d３ The value of d may be determined according to the following: ３ The value of may be determined / judged / recognized.

[0161] If the UE is not indicated with a specific UE capability (any UE capability name), the UE is not expected to have the higher layer parameter (processingType2Enabled) enabled (set to "enable") and the higher layer parameter (enhanced-dmrs-Type_r18) configured at the same time. In this case, the additional processing delay d ３ =0.

[0162] If the UE is indicated with a specific UE capability (any UE capability name), then: if the UE is simultaneously configured with higher layer parameters (enhanced-dmrs-Type_r18), then an additional processing delay d ３ may be indicated by a specific UE capability (any UE capability name); otherwise, additional processing delay d ３ =0.

[0163] On the other hand, for UE processing capability 1 (excluding UE processing capability 2), d ３ = 0. That is, when the UE applies (supports) UE processing capability 1, d ３ It may be determined / judged / recognized that =0.

[0164] For shared spectrum channel access operation in FR1, T ｅｘｔ is calculated according to a predetermined rule, and may be 0 otherwise. ｅｘｔ may be, for example, the value applied to the first UL transmission scheduled by the scheduling DCI.

[0165] (Modification) The above-mentioned certain processing time T ｐｒｏｃ，１ = (N １ +d １，１ +d ２ +d ３ )(2048+144)・κ2 －μ ・T Ｃ +T ｅｘｔmay be replaced by the following:

[0166] (Example 1) For 1 / 2 UE processing capacity, T ｐｒｏｃ，１ = (N １ +d １，１ +d ２ )(2048+144)・κ2 －μ ・T Ｃ +T ｅｘｔ , otherwise (for UE processing capability 2 / 1), T ｐｒｏｃ，１ = (N １ +d １，１ +d ２ +d ３ )(2048+144)・κ2 －μ ・T Ｃ +T ｅｘｔ .

[0167] (Example 2) Except for UE processing capability 2, T ｐｒｏｃ，１ = (N １ +d １，１ +d ２ )(2048+144)・κ2 －μ ・T Ｃ +T ｅｘｔ , for UE processing capacity 2, T ｐｒｏｃ，１ = (N １ +d １，１ +d ２ +d ３ )(2048+144)・κ2 －μ ・T Ｃ +T ｅｘｔ .

[0168] <Other> If a UE is not indicated with a specific UE capability (any UE capability name), the UE is not expected to have the upper layer parameter (processingType2Enabled) enabled (set to "enable") and the upper layer parameter (enhanced-dmrs-Type_r18) configured at the same time.

[0169] If the UE is indicated with a specific UE capability (any UE capability name), the UE is simultaneously configured with the higher layer parameter (enhanced-dmrs-Type_r18), and ２ plus an additional processing delay d ３ may be indicated by a specific UE capability (any UE capability name).

[0170] In the first embodiment, PDSCH can be read as PUSCH and applied.

[0171] According to the first embodiment, the UE can control the PDSCH processing by taking into account a new parameter corresponding to the mitigation of the processing delay, i.e., the UE can apply an appropriate DMRS according to its capability.

[0172] Second Embodiment This embodiment relates to DMRS of PUSCH.

[0173] For UEs to support joint configuration of Rel. 18 DMRS ports and dynamic switching (DWS) between DFT-S-OFDM and CP-OFDM in Rel. 18 PUSCH, several strategies are considered:

[0174] - Strategy 1: If the UE is configured with the higher layer parameter enhanced-dmrs-Type_r18 in DMRS-UplinkConfig and the scheduling DCI indicates that transform precoding is enabled, the UE ignores the higher layer parameter enhanced-dmrs-Type_r18 in DMRS-UplinkConfig.

[0175] - Strategy 2: A new UE capability is introduced to indicate whether the UE supports joint configuration of Rel. 18 DMRS ports and dynamic switching between DFT-S-OFDM and CP-OFDM in Rel. 18 PUSCH.

[0176] - Strategy 3: In the case where both a Rel. 18 DMRS port and DWS for PUSCH are configured and the scheduling DCI indicates DFT-S-OFDM, and the DMRS type of the scheduled PUSCH is unclear, the UE may ignore the higher layer parameter enhanced-dmrs-Type_r18 in DMRS-UplinkConfig, as follows:

[0177] Procedure B: For a PUSCH scheduled by a PDCCH with CRC scrambled by CS-RNTI, C-RNTI, MCS-C-RNTI or SP-CSI-RNTI with NDI=1, the UE may follow at least one of several procedures Bx below: - Procedure B1: If a DCI with a scheduling grant is received using DCI format 0_0, the UE shall consider transform precoding as enabled or disabled for this PUSCH transmission according to the parameter msg3-transformPrecoder configured by higher layers. - Procedure B2: If a DCI with a scheduling grant is not received using DCI format 0_0, the UE may follow at least one of the following procedures B2-x. -- Procedure B2-1: If a DCI with a scheduling grant is received using DCI format 0_1 ​​or 0_2 with a CRC scrambled by a C-RNTI, an MCS-C-RNTI, or a CS-RNTI with NDI=1, and if the UE is configured with the higher layer parameter dynamicTransformPrecoderIndicationDCI-0-1 in pusch-Config for DCI format 0_1 ​​or the higher layer parameter dynamicTransformPrecoderIndicationDCI-0-2 in pusch-Config for DCI format 0_2 and these higher layer parameters are set to enabled, the UE shall consider transform precoding as enabled or disabled for this PUSCH transmission according to the Transform Precoder Indicator field in the DCI with the scheduling grant. The UE may follow at least one of the following procedures B2-1-x. --- Procedure B2-1-1: For pusch-TimeDomainAllocationListForMultiPUSCH in pusch-Config, the UE shall consider transform precoding as enabled or disabled for all PUSCH transmissions according to the transform precoder indicator field in DCI format 0_1 ​​with scheduling grant.--- Procedure B2-1-2: If the UE is configured with the higher layer parameter enhanced-dmrs-Type_r18 in DMRS-UplinkConfig and the scheduling grant indicates that transform precoding is enabled for the scheduled PUSCH transmission, the UE shall ignore the higher layer parameter enhanced-dmrs-Type_r18 in DMRS-UplinkConfig if it is configured for the DMRS transmission of the scheduled PUSCH transmission. --- Procedure B2-2: Otherwise (if the conditions of procedure B2-1 are not fulfilled), the UE may follow at least one of the following procedures B2-2-x: --- Procedure B2-2-1: If the UE is configured with the higher layer parameter transformPrecoder in pusch-Config, the UE shall consider transform precoding as enabled or disabled for this PUSCH transmission according to this parameter. --- Procedure B2-2-2: If the UE does not have the upper layer parameter transformPrecoder configured in pusch-Config, the UE shall consider transform precoding to be enabled or disabled for this PUSH transmission according to the upper layer parameter msg3-transformPrecoder.

[0178] To clarify the new UE capabilities, the UE may follow Policy C below.

[0179] Policy C: If the UE supports the new UE capability (the UE reports support for the new UE capability), the UE may perform procedure B. If the UE does not support the new UE capability (the UE does not report support for the new UE capability), the UE may perform policy A / procedure A below.

[0180] Strategy A: The UE may exclude joint configuration of Rel. 18 DMRS ports and Rel. 18 DWS. If dynamic switching between DFT-S-OFDM and CP-OFDM is configured for PUSCH, the UE does not expect / assume that the higher layer parameter enhanced-dmrs-Type_r18 in DMRS-UplinkConfig is configured. For Strategy A, the following procedure A may be defined in the specification.

[0181] Procedure A: The UE may follow several of the following procedures Ax: - Procedure A1: In PUSCH repetition type B, the DMRS transmission procedure is applied separately for each actual repetition based on the allocation duration of the actual repetition. The UE does not expect / assume to be instructed to an antenna port configuration that is invalid for the allocation duration of any actual repetition. - Procedure A2: If the UE is configured with the higher layer parameter dynamicTransformPrecoderIndicationDCI-0-1 in pusch-Config for DCI format 0_1 ​​or the higher layer parameter dynamicTransformPrecoderIndicationDCI-0-2 in pusch-Config for DCI format 0_2, and the higher layer parameter is set to 'enabled', the UE does not expect / assume to be configured with the higher layer parameter enhanced-dmrs-Type_r18 in DMRS-UplinkConfig.

[0182] With respect to policy C, the following procedure C may be defined in the specification.

[0183] Procedure C may be defined by replacing procedure B2-1-2 in the above procedure B with at least one of the following procedures B2-1-2x: --- Procedure B2-1-2a: If the UE has not indicated / reported new UE capabilities, and if the upper layer parameter dynamicTransformPrecoderIndicationDCI-0-1 in pusch-Config for DCI format 0_1 ​​or the upper layer parameter dynamicTransformPrecoderIndicationDCI-0-2 in pusch-Config for DCI format 0_2 is configured and the upper layer parameter is set to enabled ('enabled'), the UE does not expect / assume that the upper layer parameter enhanced-dmrs-Type_r18 in DMRS-UplinkConfig is configured. --- Procedure B2-1-2b: If the UE indicates / reports new UE capabilities, and the UE is configured with the higher layer parameter enhanced-dmrs-Type_r18 in DMRS-UplinkConfig and the scheduling grant indicates that transform precoding is enabled for the scheduled PUSCH transmission, the UE shall ignore the higher layer parameter enhanced-dmrs-Type_r18 in DMRS-UplinkConfig if it is configured for the DMRS transmission of that scheduled PUSCH transmission.

[0184] FIG. 13 shows an example of a part of procedure C.

[0185] In step B2-1 of procedure C, if the conditions of step B2-1 are met (S110: Y), the UE performs step B2-1-1 if necessary. If the UE has not reported new UE capabilities (S120: N), if the conditions of step B2-1-2a are met, the UE does not expect the extended DMRS type to be configured (S130). If the UE has reported new UE capabilities (S120: Y), if the conditions of step B2-1-2b are met, the UE ignores the configuration of the extended DMRS type (S140).

[0186] In step B2-1 of procedure C, if the conditions of step B2-1 are not satisfied (S110: N), the UE performs step B2-2 (S150).

[0187] If the conditions of procedure B2-1-2a or the conditions of procedure B2-1-2b are met, the UE may apply the legacy DMRS port (legacy FD-OCC, FD-OCC of length 2) to the DMRS of the PUSH.

[0188] According to this embodiment, the UE can apply the appropriate DMRS depending on its capabilities.

[0189] <Supplementary Information> [Notification of Information to UE] In the above-described embodiments, any information may be notified to the UE (from a network (NW) (e.g., a base station (BS))) (in other words, reception of any information from the BS by the UE) using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.

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

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

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

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

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

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

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

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

[0198] At least one of the above embodiments may be applied only to UEs that have reported or support a specific UE capability. The specific UE capability may indicate at least one of the following: - That the UE supports specific processing / operation / control / information for at least one of the above embodiments. - That an extended DMRS port corresponding to a certain DCI format is applicable. The UE capability for each DCI format may indicate whether an extended DMRS port is applicable to a PDSCH scheduled by that DCI format. For example, apart from the UE capability indicating whether an extended DMRS port is applicable to a PDSCH scheduled by DCI format 1_1 / 1_2, at least one of the following may be defined / reported: a UE capability indicating whether an extended DMRS port is applicable to a PDSCH scheduled by DCI format 1_3; and a UE capability indicating whether an extended DMRS port is applicable to a PDSCH scheduled by DCI format 4_2. - That an extended DMRS port corresponding to all DCI formats for PDSCH scheduling is applicable. One UE capability may indicate whether the extended DMRS port is applicable to the PDSCH scheduled by all DCI formats for PDSCH scheduling. The UE supports capability 1 / capability 2 for PDSCH / PUSCH processing time.

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

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

[0201] Furthermore, at least one of the above-described embodiments may be applied when a UE configures / activates / triggers specific information related to the above-described embodiment (or performs the operation of the above-described embodiment) through higher layer signaling / physical layer signaling. The specific information may indicate at least one of the following: - Information indicating enabling / disabling the operation of the above-described embodiment; - RRC parameters for a specific release (e.g., Rel. 18 / 19). In Rel. YY (e.g., YY is 18 or greater), the RRC parameter enabling operation XXX may be expressed as XXX_rYY (XXX-rYY). - The higher layer parameter enhanced-dmrs-Type_r18 in DMRS-UplinkConfig; - The higher layer parameter dynamicTransformPrecoderIndicationDCI-0-1 in pusch-Config; - The higher layer parameter dynamicTransformPrecoderIndicationDCI-0-2 in pusch-Config.

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

[0203] (Supplementary Notes) The following inventions are supplemented with respect to one embodiment of the present disclosure. [Supplementary Note 1] A terminal having: a transmitting unit that reports capability 1 or capability 2 for a processing time of a shared channel; and a control unit that determines application of a parameter corresponding to relaxation of the processing time based on the type of capability for the processing time of the shared channel. [Supplementary Note 2] The terminal according to Supplementary Note 1, in which, if a specific terminal capability corresponding to capability 2 is not indicated, the control unit does not expect that capability 2 will be enabled and an enhanced demodulation reference signal (DMRS) type will be configured simultaneously. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, in which, if a specific terminal capability corresponding to capability 2 is not indicated or if a specific terminal capability corresponding to capability 2 is indicated, the control unit determines that the parameter is 0. [Supplementary Note 4] The terminal according to any of Supplements 1 to 3, in which, if capability 1 is applied, the control unit determines that the parameter is 0.

[0204] (Supplementary Notes) The following inventions are supplemented with respect to one embodiment of the present disclosure. [Supplementary Note 1] A terminal comprising: a receiving unit that receives a first setting of a dynamic transformation precoder indication; and a control unit that determines whether a specific frequency domain (FD)-orthogonal cover code (OCC) longer than two is applied to a demodulation reference signal (DMRS) for a physical uplink shared channel (PUSCH) based on whether the terminal has reported specific capability information. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein, if the terminal has not reported specific capability information, the control unit determines not to transmit a second setting indicating that the specific FD-OCC is applied to the DMRS. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein, if the terminal has reported specific capability information and the second setting indicating that the specific FD-OCC is applied to the DMRS has been received, and downlink control information indicating that a transformation precoder is enabled and scheduling the PUSCH has been received, the control unit ignores the second setting. [Supplementary Note 4] The terminal according to any one of Supplementary Note 1 to Supplementary Note 3, wherein the control unit applies an FD-OCC of length 2 to the DMRS in the following cases: a case in which the terminal does not report specific capability information; and a case in which the terminal reports specific capability information, a second setting indicating that the specific FD-OCC is applied to the DMRS is received, and downlink control information indicating that a transform precoder is enabled and scheduling the PUSCH is received.

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

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

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

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

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

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

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

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

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

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

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

[0216] The core network 30 may include network functions (Network Functions (NF)) such as a User Plane Function (UPF), an Access and Mobility management Function (AMF), a Session Management Function (SMF), a Unified Data Management (UDM), an Application Function (AF), a Data Network (DN), a Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). A single network node may provide multiple functions. Communication with an external network (e.g., the Internet) may also be performed via the DN.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0249] The transmitting / receiving unit 120 may receive a report of capacity 1 or capacity 2 for the processing time of the shared channel. The control unit 110 may determine whether to apply a parameter corresponding to relaxation of the processing time based on the type of capacity for the processing time of the shared channel.

[0250] The transceiver unit 120 may transmit a first setting of the dynamic conversion precoder instruction. The control unit 110 may determine whether a specific frequency domain (FD)-orthogonal cover code (OCC) longer than 2 is applied to a demodulation reference signal (DMRS) for a physical uplink shared channel (PUSCH) based on whether specific capability information is reported.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0267] The measurement unit 223 may derive channel measurements for CSI calculation based on the channel measurement resources. The channel measurement resources may be, for example, non-zero power (NZP) CSI-RS resources. The measurement unit 223 may also derive interference measurements for CSI calculation based on the interference measurement resources. The interference measurement resources may be at least one of an NZP CSI-RS resource for interference measurement, a CSI-Interference Measurement (IM) resource, etc. Note that CSI-IM may be referred to as CSI-Interference Management (IM) or may be interchangeably read as Zero Power (ZP) CSI-RS. Note that in the present disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc. may be interchangeably read as interchangeable.

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

[0269] The transceiver unit 220 may report capability 1 or capability 2 for the processing time of the shared channel. The control unit 210 may determine whether to apply a parameter corresponding to relaxation of the processing time based on the type of capability for the processing time of the shared channel. If a specific terminal capability corresponding to capability 2 is not indicated, the control unit 210 may not expect that the activation of capability 2 and an enhanced demodulation reference signal (DMRS) type are configured simultaneously. If a specific terminal capability corresponding to capability 2 is not indicated or if a specific terminal capability corresponding to capability 2 is indicated, the control unit 210 may determine that the parameter is 0. If capability 1 is to be applied, the control unit 210 may determine that the parameter is 0.

[0270] The transceiver unit 220 may receive a first setting of a dynamic transformation precoder indication (e.g., a dynamic transformation precoder indication setting). The control unit 210 may determine whether a specific frequency domain (FD)-orthogonal cover code (OCC) (e.g., an extended DMRS port or an extended DMRS type) longer than two is applied to a demodulation reference signal (DMRS) for a physical uplink shared channel (PUSCH) based on whether the terminal reports specific capability information (e.g., new UE capabilities).

[0271] If the terminal does not report specific capability information, the control unit 210 may determine that a second setting (e.g., an extended DMRS type setting) indicating that the specific FD-OCC is applied to the DMRS is not transmitted.

[0272] If the terminal reports specific capability information, and a second setting indicating that the specific FD-OCC is applied to the DMRS is received, and downlink control information indicating that a conversion precoder is enabled and scheduling the PUSH is received, the control unit 210 may ignore the second setting.

[0273] In a case where the terminal does not report specific capability information, and a case where the terminal reports specific capability information and a second setting indicating that the specific FD-OCC is applied to the DMRS is received, and downlink control information indicating that a conversion precoder is enabled and scheduling the PUSH is received, the control unit 210 may apply an FD-OCC of length 2 (e.g., an existing DMRS port, an existing DMRS type) to the DMRS.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0321] In the present disclosure, the term "antenna port" may be interchangeably read as an antenna port for any signal / channel (e.g., a demodulation reference signal (DMRS) port). In the present disclosure, the term "resource" may be interchangeably read as a resource for any signal / channel (e.g., a reference signal resource, an SRS resource, etc.). The resource may include time / frequency / code / space / power resources. Furthermore, the spatial domain transmission filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.

[0322] The group may include, for example, at least one of a spatial relationship group, a Code Division Multiplexing (CDM) group, a Reference Signal (RS) group, a Control Resource Set (CORESET) group, a PUCCH group, an antenna port group (e.g., a DMRS port group), a layer group, a resource group, a beam group, an antenna group, a panel group, and the like.

[0323] In addition, in the present disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, codeword (CW), transport block (TB), RS, etc. may be read as interchangeable terms.

[0324] In addition, in the present disclosure, the terms TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, joint TCI state, etc. may be read interchangeably.

[0325] Furthermore, in the present disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) property," and "specific QCL type (e.g., Type A, Type D)" may be interchangeable.

[0326] In the present disclosure, terms such as index, identifier (ID), indicator, indication, and resource ID may be interchangeable. In the present disclosure, terms such as sequence, list, set, group, cluster, and subset may be interchangeable.

[0327] Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and the spatial relationship information (TCI state) may be interchangeable. The "spatial relationship information (TCI state)" may be interchangeable with "set of spatial relationship information (TCI state)", "one or more pieces of spatial relationship information", etc. The TCI state and the TCI may be interchangeable. The spatial relationship information and the spatial relationship may be interchangeable.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0352] Each aspect / embodiment described in the present disclosure may be a technology other than Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (x is, for example, an integer or decimal number)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802. The present invention may be applied to systems that use IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable wireless communication methods, or to next-generation systems that are expanded, modified, created, or defined based on these. Furthermore, the present invention may be applied to a combination of multiple systems (e.g., a combination of LTE or LTE-A and 5G).

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

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

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

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

[0357] Furthermore, "determination" may be considered to be "determining" resolving, selecting, choosing, establishing, comparing, etc. In other words, "determination" may be considered to be "determining" some kind of action. In the present disclosure, "determination" may be read interchangeably with the above-mentioned actions.

[0358] Furthermore, in this disclosure, "determine / determining" may be interchangeably read as "assume / assuming," "expect / expecting," "consider / considering," etc. Furthermore, in this disclosure, "does not expect to do..." may be interchangeably read as "assumes not to do...."

[0359] In the present disclosure, "expect" may be interchangeably read as "be expected." For example, "expect(s) ..." ("..." may be expressed, for example, as a that clause, a to-infinitive, etc.) may be interchangeably read as "be expected ...." "does not expect ..." may be interchangeably read as "be not expected ...." Furthermore, "An apparatus A is not expected ..." may be interchangeably read as "an apparatus B other than apparatus A does not expect ... from apparatus A" (e.g., if apparatus A is a UE, apparatus B may be a base station).

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

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

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

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

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

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

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

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

[0368] In the present disclosure, terms such as "when A, B," "if A, (then) B," "B upon A," "B in response to A," "B based on A," "B during / while A," "B before A," "B at (the same time as) / on A," "B after A," "B since A," and "B until A" may be interchangeable. Note that A, B, and the like herein may be replaced with appropriate expressions such as nouns, gerunds, and regular sentences, depending on the context. Note that the time difference between A and B may be approximately zero (immediately after or immediately before). A time offset may also be applied to the time at which A occurs. For example, "A" may be interchangeable with "before / after a time offset at which A occurs." The time offset (eg, one or more symbols / slots) may be predefined or may be specified by the UE based on signaled information.

[0369] In the present disclosure, timing, time, duration, time instance, any time unit (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc. may be read interchangeably.

[0370] Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The description of the present disclosure is for illustrative purposes only and does not impose any limiting meaning on the invention according to the present disclosure.

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

Claims

1. A terminal having: a receiving unit that receives a first setting of a dynamic conversion precoder indication; and a control unit that determines whether a specific frequency domain (FD)-orthogonal cover code (OCC) longer than 2 is applied to a demodulation reference signal (DMRS) for a physical uplink shared channel (PUSCH) based on whether the terminal reports specific capability information.

2. The terminal according to claim 1, wherein, if the terminal does not report specific capability information, the control unit determines that a second setting indicating that the specific FD-OCC is applied to the DMRS is not transmitted.

3. The terminal of claim 1, wherein, when the terminal reports specific capability information, a second setting indicating that the specific FD-OCC is applied to the DMRS is received, and downlink control information indicating that a conversion precoder is enabled and scheduling the PUSH is received, the control unit ignores the second setting.

4. The terminal of claim 1, wherein the control unit applies an FD-OCC of length 2 to the DMRS in a case where the terminal does not report specific capability information, and a case where the terminal reports specific capability information and a second setting indicating that the specific FD-OCC is applied to the DMRS is received, and downlink control information indicating that a conversion precoder is enabled and scheduling the PUSH is received.

5. A wireless communication method for a terminal, comprising: a step of receiving a first setting of a dynamic conversion precoder indication; and a step of determining whether a specific frequency domain (FD)-orthogonal cover code (OCC) longer than 2 is applied to a demodulation reference signal (DMRS) for a physical uplink shared channel (PUSCH) based on whether the terminal reports specific capability information.

6. A base station having a transmitting unit that transmits a first setting of a dynamic conversion precoder instruction, and a control unit that determines whether a specific frequency domain (FD)-orthogonal cover code (OCC) longer than 2 is applied to a demodulation reference signal (DMRS) for a physical uplink shared channel (PUSCH) based on whether specific capability information is reported.

Images