Terminal, wireless communication method, and base station

Abstract

A terminal according to one embodiment of the present disclosure is provided with: a transmission unit that reports a capability 1 or a capability 2 for a processing time for a shared channel; and a control unit that determines the application of a parameter corresponding to the relaxation of the processing time on the basis of the type of capability for the processing time of the shared channel.

Description

Technical Field

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

[0002] In Universal Mobile Telecommunications System (UMTS) networks, Long Term Evolution (LTE) was standardized for the purpose of further increasing data rates and reducing latency (Non-Patent Document 1). Furthermore, LTE-Advanced (3GPP Rel. 10-14) was standardized for the purpose of further increasing capacity and advancing LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9).

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

[0004] Existing technical documents

[0005] Non-patent literature

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

[0007] The problem that the invention aims to solve

[0008] For purposes such as layer orthogonality, reference signals from multiple ports are used (e.g., demodulation reference signals (DMRS)).

[0009] In future wireless communication systems, there is research into increasing the number of DMRS ports beyond existing specifications. However, the configuration and application of DMRS at this stage are not yet fully studied. If DMRS is not properly configured and applied, there are concerns about reduced communication throughput and quality.

[0010] Therefore, one of the purposes of this disclosure is to provide terminals, wireless communication methods, and base stations that apply appropriate DMRS.

[0011] Methods for solving problems

[0012] One aspect of this disclosure relates to a terminal comprising: a transmitting unit capable of reporting processing time for a shared channel, either capability 1 or capability 2; and a control unit capable of determining the application of parameters corresponding to a relaxation of processing time based on the type of capability for processing time of the shared channel.

[0013] Invention Effects

[0014] According to one method of this disclosure, appropriate DMRS can be applied. Attached Figure Description

[0015] Figures 1A-1B This represents an example of an existing DMRS port table for DMRS configuration type 1 / 2 used for PDSCH.

[0016] Figures 2A-2B This represents an example of an existing DMRS port table for DMRS configuration type 1 / 2 used for PUSCH.

[0017] Figures 3A-3B This represents an example of the association between CDM group, DMRS port, and OCC in Enhancement Type 1 / Enhancement Type 2.

[0018] Figure 4 This represents an example of a parameter used for PDSCH DMRS setting type 1.

[0019] Figure 5 This represents an example of a parameter used for PDSCH DMRS setting type 2.

[0020] Figure 6 This represents an example of a parameter used for setting type 1 of PUSCH DMRS.

[0021] Figure 7 This represents an example of a parameter used for PUSCH DMRS setting type 2.

[0022] Figures 8A-8B This represents an example of DMRS enhancement type 1 and the mapping from FD-OCC to RE.

[0023] Figures 9A-9B This represents an example of DMRS enhancement type 2 and the mapping from FD-OCC to RE.

[0024] Figure 10 This represents another example of DMRS enhancement type 2 and the mapping of FD-OCC to RE.

[0025] Figure 11A This is a graph representing an example of the processing time for a processing capacity of 1 for PDSCH. Figure 11B This is a graph representing an example of the processing time for PDSCH processing capacity 2.

[0026] Figure 12 This is a diagram illustrating a specification related to the PDSCH processing time of the UE.

[0027] Figure 13 An example representing a part of process C.

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

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

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

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

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

[0033] (DMRS)

[0034] The front-loaded demodulation reference signal (DMRS) is the initial DMRS for earlier demodulation (the first symbol or near the first symbol). An additional DMRS can be set via RRC for high-speed mobile terminals (terminals, user terminals, user equipment (UEs)) or high-modulation and coding schemes (MCS) / ranks. The frequency position of the additional DMRS is the same as the front-loaded DMRS.

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

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

[0037] For the frequency domain, set DMRS setting type 1 or 2 (PDSCH / PUSCH). DMRS setting type 1 has a comb structure and can be applied to both CP-OFDM (transport precoding-disabled) and DFT-S-OFDM (transport precoding-enabled). DMRS setting type 2 can only be applied to CP-OFDM.

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

[0039] Single-symbol DMRS is widely used (it is a mandatory feature in Rel. 15). In single-symbol DMRS, the number of appended DMRS symbols is "1, 2, 3, 4". Single-symbol DMRS supports both active and inactive frequency hopping. Single-symbol DMRS is used if the maximum value (maxLengTh) in the uplink DMRS setting (DMRS-UplinkConfig) is not set.

[0040] Dual-symbol DMRS is used for more DMRS ports (especially Multi-User Multi-Input Multi-Output (MU-MIMO)). In dual-symbol DMRS, the number of appended DMRS (symbols) is "0, 1". Dual-symbol DMRS supports situations where frequency hopping is invalid. If the maximum value (maxLength) in the uplink DMRS configuration (DMRS-UplinkConfig) is 2 (len2), whether it is single-symbol DMRS or dual-symbol DMRS is determined by the DCI or configured grant.

[0041] Based on the above, the following combinations should be considered for feasible configuration modes of DMRS.

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

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

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

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

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

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

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

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

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

[0051] Setting DMRS to Type 1 and Single Symbol DMRS allows the use of 4 DMRS ports. Within each DMRS CDM group, 2 DMRS ports are multiplexed using a 2-length FD OCC (Frequency Domain OCC). Between multiple DMRS CDM groups (2 DMRS CDM groups), 2 DMRS ports are multiplexed using Frequency Division Multiplexing (FDM).

[0052] By configuring DMRS type 1 and dual-symbol DMRS, eight DMRS ports can be utilized. Within each DMRS CDM group, two DMRS ports are multiplexed via FD OCCs of length 2, and two DMRS ports are multiplexed via TD OCCs (Time Domain OCCs). Between multiple DMRS CDM groups (two DMRS CDM groups), two DMRS ports are multiplexed via FDM.

[0053] With DMRS configured as Type 2 and Single Symbol DMRS, six DMRS ports can be utilized. Within each DMRS CDM group, two DMRS ports are multiplexed using FD OCCs of length 2. Among multiple DMRS CDM groups (three DMRS CDM groups), three DMRS ports are multiplexed using FDM.

[0054] With DMRS configured as Type 2 and dual-symbol DMRS, 12 DMRS ports can be utilized. Within each DMRS CDM group, two DMRS ports are multiplexed via FD OCCs of length 2, and two DMRS ports are multiplexed via TD OCCs. Among multiple DMRS CDM groups (3 DMRS CDM groups), three DMRS ports are multiplexed via FDM.

[0055] Here, an example of DMRS mapping type B is shown, but the same applies to DMRS mapping type A.

[0056] In the parameters used for PDSCH DMRS (existing table, existing DMRS port table, Figure 1), DMRS configuration type 1 can utilize DMRS ports 1000-1007, and DMRS configuration type 2 can utilize DMRS ports 1000-1011.

[0057] In the parameters used for PUSCH DMRS (existing table, existing DMRS port table, Figure 2), DMRS configuration type 1 can utilize DMRS ports 0-7, and DMRS configuration type 2 can utilize DMRS ports 0-11.

[0058] (Reference signal port)

[0059] For orthogonalization of the MIMO layer, reference signals from multiple ports are used (e.g., demodulation reference signal (DMRS) and CSI-RS).

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

[0061] Furthermore, if a larger value for the number of CSI-RS ports is used than the number of layers used in the data, more accurate channel conditions can be measured based on this CSI-RS, which is expected to contribute to improved throughput.

[0062] In Rel-15 NR, multiple-port DMRS utilizes Frequency Division Multiplexing (FDM), Frequency Domain Orthogonal Cover Code (FD-OCC), and Time Domain OCC (TD-OCC) to support a maximum of 8 ports in Type 1 DMRS (in other words, DMRS is set to Type 1) and a maximum of 12 ports in Type 2 DMRS (in other words, DMRS is set to Type 2).

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

[0064] In this disclosure, OCC, orthogonal codes, orthogonalization, and cyclic shift can be rewritten in different ways.

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

[0066] In DMRS, a DMRS in which two consecutive (adjacent) symbol units are mapped to resources can be called a dual-symbol DMRS, and a DMRS in which one symbol unit is mapped to resources can be called a single-symbol DMRS.

[0067] Regardless of the type of DMRS, it can be mapped to more than one symbol in each time slot, depending on the length of the data channel. A DMRS mapped to the beginning of a data symbol can be called a front-loaded DMRS, and a DMRS that is appended to other positions can be called an additional DMRS.

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

[0069] When DMRS is set to type 1 and dual-symbol DMRS is used, Comb, CS, and TD-OCC are used for orthogonalization. For example, up to 8 antenna ports (APs) can be supported using two types of Comb, two types of CS, and TD-OCC ({1, 1} and {1, -1}).

[0070] When DMRS is set to type 2 and single-symbol DMRS is used, FD-OCC is used for orthogonalization. For example, orthogonal codes (2-FD-OCC) can be applied to two adjacent resource elements (REs) in the frequency direction to support up to 6 APs.

[0071] When DMRS is set to type 2 and dual-symbol DMRS is used, FD-OCC and TD-OCC are used for orthogonalization. For example, orthogonal codes (2-FD-OCC) can be applied to two adjacent REs in the frequency direction, and TD-OCC ({1, 1} and {1, -1}) can be applied to two adjacent REs in the time direction, thereby supporting up to 12 APs.

[0072] Furthermore, in Rel-15 NR, multi-port CSI-RS can support up to 32 ports by utilizing FDM, Time Division Multiplexing (TDM), frequency domain OCC, and time domain OCC. The orthogonalization of CSI-RS can also be achieved using the same methods as described above for DMRS.

[0073] Among them, the group of DMRS ports that are orthogonalized by FD-OCC / TD-OCC as described above can also be called a code division multiplexing (CDM) group.

[0074] Because different CDM groups are subjected to FDM, they are orthogonal. On the other hand, within the same CDM group, the orthogonality of the applied OCC can sometimes be disrupted by channel fluctuations, etc. In this case, if signals within the same CDM group are received using different receiving powers, distance issues arise, raising concerns that orthogonality cannot be guaranteed.

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

[0076] For Rel. 15 NR, both the TD-OCC and FD-OCC of the DMRS are equivalent to an OCC with a sequence length (also 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) can also be defined by DMRS ports with an FD-OCC length of 2 (e.g., DMRS ports with FD-OCC length=2).

[0077] Therefore, the possible values ​​for k' and l' are 0 and 1, respectively. By multiplying the FD-OCC in units of RE, a 2-port DMRS can be multiplexed using the same time and frequency resources (2RE). If both the FD-OCC and TD-OCC are used, a 4-port DMRS can be multiplexed using the same time and frequency resources (4RE).

[0078] The two known DMRS port tables used in the PDSCH (correspondence between antenna port numbers and parameters) correspond to DMRS setting type 1 and type 2, respectively. Additionally, p represents the antenna port number, and ∆ represents the parameter used to shift (offset) the frequency resource.

[0079] For example, for antenna ports 1000 and 1001, by applying {w f (0), w f(1)}={+1, +1}and{w f (0), w f (1)}={+1, -1} is used to perform orthogonalization using FD-OCC.

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

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

[0082] For CP-OFDM research only: (without increasing DMRS overhead) specify a greater number of orthogonal DMRS ports for MU-MIMO in DL / UL; implement a common design between DL and UL DMRS; and double the maximum number of orthogonal DMRS ports for a maximum of 24 orthogonal DMRS ports and various DMRS configuration types that can be applied, for both single-symbol DMRS and dual-symbol DMRS.

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

[0084] [Scenario 1] DMRS setting type 1 single-symbol DMRS

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

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

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

[0088] [Scenario 3] Single-code DMRS of DMRS setting type 2

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

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

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

[0092] In Rel. 18, the study examines cases 1, 2, 3, and 4, with the total number of DMRS ports increased by a factor of 2 to 8, 16, 12, and 24, respectively.

[0093] To increase the number of DMRS ports, explore the following five options (methods to increase the number of DMRS ports).

[0094] <Option 1>

[0095] • Introduce new OCCs with a longer length than existing OCCs (e.g., 4 or 6).

[0096] In option 1, as a research project, one could mention the possibility of performance degradation when latency increases, the possibility of scheduling limitations, and backward compatibility.

[0097] <Option 2>

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

[0099] In option 2, as research items, one could mention the possibility of performance degradation when the UE speed is high, the possibility of scheduling limitations (e.g., frequency hopping application methods), the possibility of DMRS settings being limited (e.g., the number of additional DMRSs being limited), and backward compatibility, etc.

[0100] <Option 3>

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

[0102] In option 3, as research topics, one could cite the possibility of performance degradation when latency is large, as well as backward compatibility.

[0103] <Option 4>

[0104] • Reuse the symbols of the appended DMRS to add orthogonal DMRS ports.

[0105] In option 4, as research items, one could cite the possibility of performance degradation when the UE speed is high, the possibility of DMRS settings being limited (e.g., the number of DMRS that can be added is limited), and backward compatibility, etc.

[0106] <Option 5>

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

[0108] In option 5, as a research item, one could cite the possibility of performance degradation when the UE speed is high, the possibility of scheduling limitations (e.g., frequency hopping application methods), the possibility of DMRS settings being limited (e.g., the number of DMRSs that can be added is limited), and backward compatibility, etc.

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

[0110] In Option 5 of the aforementioned method for increasing the number of DMRS ports, a new FD-OCC of length 4 can also be applied, and a new TD-OCC of length 2 is applied to multiple discontinuous DMRS symbols, resulting in 4 DMRS ports within a CDM group. In this case, the receiver can separate the signal by decoding either the FD-OCC or the TD-OCC, which is advantageous compared to Options 1 / 3. For example, by using the TD-OCC, the receiver can decode using only the FD-OCC when problems such as deterioration of characteristics (orthogonality) occur during high-speed movement; channel estimation cannot begin even when only the preceding DMRS is received, requiring the reception of additional DMRS symbols, thus delaying PDSCH decoding. Conversely, by using the FD-OCC, when problems such as deterioration of characteristics (orthogonality) occur due to large delay spread, the receiver can decode using only the TD-OCC.

[0111] In Option 5, which is used to increase the number of DMRS ports, a new FD-OCC of length 6 can be applied, and a new TD-OCC of length 2 is applied to multiple non-contiguous DMRS symbols.

[0112] Thus, in Rel. 18 and later, FD-OCC with a length greater than 2 is supported. DMRS ports used for Type 1 / Type 2 in Rel. 18 and later can also be referred to as Rel. 18 Enhanced Type 1 / Enhanced Type 2 DMRS ports. Enhanced Type 1 / Enhanced Type 2 can also be referred to as e-Type 1 / e-Type 2.

[0113] For example, a Rel. 18 e Type 1 / e Type 2 DMRS port can also be defined as a DMRS port with an FD-OCC length greater than 2 (e.g., DMRS ports with FD-OCC length > 2). For example, it could also be a Rel. 18 e Type 1 / e Type 2 DMRS port with an FD-OCC length of 4.

[0114] Additionally, the Type 1 / Type 2 DMRS port with FD-OCC length = 2, defined starting from Rel. 15, can also be referred to as the Rel. 15 Type 1 / Type 2 DMRS port.

[0115] Rel. 18 e Type 1 DMRS ports can also use port indices p=#1000-1015. For example, for DMRS ports with new FD-OCC#0,1, the same DMRS port indices as Rel. 15 DMRS ports (DMRS port #1000-#1007) can be used. For DMRS ports with new FD-OCC#2,3, different DMRS port indices than Rel. 15 DMRS ports (DMRS port #1008-#1015, Rel. 18 DMRS ports) can be used.

[0116] Rel. 18 e Type 2 DMRS ports can also use port indices p=#1000-1023. For example, for DMRS ports with new FD-OCC#0,1, the same DMRS port indices as Rel. 15 DMRS ports (DMRS port #1000-#1011) can be used. For DMRS ports with new FD-OCC#2,3, different DMRS port indices than Rel. 15 DMRS ports (DMRS port #1012-#1023, Rel. 18 DMRS ports) can be used.

[0117] In Rel. 18, a new OCC for DMRS (Enhanced Type 1 / Enhanced Type 2 DMRS) of PDSCH / PUSCH is introduced, supporting FD-OCCs of length 4.

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

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

[0120] In this disclosure, the terms "existing DMRS," "existing DMRS function," "existing DMRS type," "existing DMRS setting type," "dmrs-Type," "DMRS setting type 1 / 2," "DMRS with FD-OCC of length 2," and "Rel. 15 DMRS type" can be interchanged. In this disclosure, the terms "setting an existing DMRS setting type," "setting an existing DMRS setting type 1 or 2," and "not setting an enhanced DMRS type" can also be interchanged. In this disclosure, the terms "DMRS setting type 1," "DMRS type 1," "DMRS type = 1," "DMRS type 1," and "dmrs-Type not set but set to type 2" can also be interchanged. In this disclosure, the terms "DMRS setting type 2," "DMRS type 2," "DMRS type = 2," "DMRS Type 2," and "dmrs-Type set to type 2" can also be interchanged.

[0121] In this disclosure, the terms "enhanced DMRS," "enhanced DMRS functionality," "enhanced DMRS type," "enhanced DMRS setting type," "setting / high-level parameters for enhanced DMRS type," "enhanced DMRS type," "enhanced-dmrs-Type_r18," "dmrs-TypeEnh," "enhanced DMRS setting type 1 / 2," "DMRS with FD-OCC of length 4," and "Rel. 18 DMRS type" can be overridden with each other. In this disclosure, the terms "setting enhanced DMRS setting type," "setting enhanced-dmrs-Type_r18," "setting enhanced DMRS setting type 1 or 2," and "setting enhanced DMRS type" can also be overridden with each other. In this disclosure, the terms "enhanced DMRS type 1," "DMRS enhanced type 1," "DMRS enhanced type = 1," "DMRS eType 1," and "setting enhanced DMRS type and not setting dmrs-Type to type 2" can also be overridden with each other. In this disclosure, the enhanced DMRS setting type 2, DMRS enhancement type 2, DMRS enhancement type = 2, DMRS eType 2, and setting the enhanced DMRS type and setting the dmrs-Type to type2 can be overridden with each other.

[0122] Enhanced DMRS Setting Type 1 (DMRS Enhanced Type 1, DMRS Enhanced Type = 1, DMRS eType 1) utilizes the frequency domain configuration of DMRS Setting Type 1 (DMRS Type 1, DMRS Type = 1, DMRS Type 1) and the new FD-OCC. Enhanced DMRS Setting Type 2 (DMRS Enhanced Type 2, DMRS Enhanced Type = 2, DMRS eType 2) utilizes the frequency domain configuration of DMRS Setting Type 2 (DMRS Type 2, DMRS Type = 2, DMRS Type 2) and the new FD-OCC.

[0123] In this disclosure, the maximum length of the DMRS, maxLength, and the maximum number of OFDM symbols in the front-loaded DMRS can be rewritten in different ways.

[0124] In this disclosure, FD-OCC, w f (k') can also be interchanged. In this disclosure, TD-OCC, w t (l') and TD-OCC of length 2 can also be rewritten to each other.

[0125] In this disclosure, existing OCCs, existing FD-OCCs, FD-OCCs of length 2, and Rel. 15 FD-OCCs can be rewritten. In this disclosure, new OCCs, new FD-OCCs, FD-OCCs of length greater than 2, Rel. 18 FD-OCCs, and w... f (k') and FD-OCC of length 4 can also be rewritten to each other.

[0126] In this disclosure, existing DMRS ports, Rel. 15 DMRS ports, DMRS ports using existing FD-OCC, DMRS ports within the port number range of existing DMRS, existing DMRS ports, and existing DMRS can all be interchanged. In this disclosure, new DMRS ports, Rel. 18 DMRS ports, DMRS ports using new FD-OCC, DMRS ports outside the port number range of existing DMRS, enhanced DMRS ports, and enhanced DMRS can also be interchanged.

[0127] (Enhanced DMRS setting type settings)

[0128] The study examines the RRC parameters used for setting Rel. 18 DMRS (Enhanced Type 1 / 2).

[0129] The PDSCH configuration (PDSCH-Config) can include the downlink (DL) DMRS configuration (DMRS-DownlinkConfig) for setting up DMRS for PDSCH. DMRS-DownlinkConfig can include dmrs-Type, dmrs-AdditionalPosition, maxLength, scrapblingID0, scrapblingID1, phaseTrackingRS, dmrs-Downlink-r16, and can further include enhanced-dmrs-Type_r18. dmrs-Downlink-r16 indicates whether to utilize low PAPR DMRS. When dmrs-Downlink-r16 is set to "enabled", low PAPR DMRS is used.

[0130] Enhanced-dmrs-Type_r18 is the selection of the enhanced DMRS type. If the enhanced-dmrs-Type_r18 field is absent, the UE utilizes either the existing DMRS type 1 or the existing DMRS type 2 based on the dmrs-Type. If the enhanced-dmrs-Type_r18 field exists: if there is no dmrs-Type field set to type 2 in DMRS-DownlinkConfig, the UE utilizes enhanced DMRS type 1; if there is a dmrs-Type field set to type 2 in DMRS-DownlinkConfig, the UE utilizes enhanced DMRS type 2.

[0131] The PUSCH configuration (PUSCH-Config) can include the uplink (UL) DMRS configuration (DMRS-UplinkConfig) for PUSCH DMRS settings. DMRS-UplinkConfig can include dmrs-Type, dmrs-AdditionalPosition, maxLength, transformPrecodingDisabled, and transformPrecodingEnabled. transformPrecodingDisabled can include scrapblingID0, scrapblingID1, and dmrs-Uplink-r16, and can further include enhanced-dmrs-Type_r18. dmrs-Uplink-r16 indicates whether to utilize low PAPR DMRS. When dmrs-Uplink-r16 is set to "enabled", low PAPR DMRS is utilized.

[0132] Enhanced-dmrs-Type_r18 is the selection of the enhanced DMRS type. If the enhanced-dmrs-Type_r18 field is absent, the UE uses either the existing DMRS type 1 or the existing DMRS type 2 based on the dmrs-Type. If the enhanced-dmrs-Type_r18 field exists: if there is no dmrs-Type field set to type 2 in DMRS-UplinkConfig, the UE uses enhanced DMRS type 1; if there is a dmrs-Type field set to type 2 in DMRS-UplinkConfig, the UE uses enhanced DMRS type 2.

[0133] For PDSCHs with PDSCH mapping types A / B, the UE can also apply DMRS setting type 1 to the PDSCH if there is no dmrs-Type set to type 2 in the DMRS downlink configuration (DMRS-DownlinkConfig) corresponding to its mapping type; and apply DMRS setting type 2 to the PDSCH if there is a dmrs-Type set to type 2 in the DMRS-DownlinkConfig corresponding to its mapping type. Similarly, for PUSCHs with PUSCH mapping types A / B, the UE can also apply DMRS setting type 1 to the PUSCH if there is no dmrs-Type set to type 2 in the DMRS uplink configuration (DMRS-UpConfig) corresponding to its mapping type; and apply DMRS setting type 2 to the PUSCH if there is a dmrs-Type set to type 2 in the DMRS-UpConfig corresponding to its mapping type.

[0134] (CDM Group)

[0135] As mentioned above, DMRS ports mapped to the same RE (time and frequency resource) can also be referred to as DMRSCDM groups.

[0136] Figure 3A This is a diagram illustrating an example of the association between CDM group, DMRS port, and OCC in Enhancement Type 1. Figure 3B This is a diagram illustrating an example of the association between CDM group, DMRS port, and OCC in Enhancement Type 2. Figure 3A as well as Figure 3B The DMRS port can also be called an enhanced DMRS port. Additionally, in Figure 3A as well as Figure 3B It can be applied to both single-symbol DMRS and dual-symbol DMRS.

[0137] like Figure 3A As shown, by configuring DMRS with Enhancement Type 1 and Single Symbol DMRS, eight DMRS ports (ports #0-3 and #8-11) can be utilized. Within each DMRS CDM group (CDM group #0-1), four DMRS ports (ports #0-1 and #8-9, and ports #2-3 and #10-11) are multiplexed using FD OCCs of length 4 (FD-OCC #0-3). Between multiple DMRS CDM groups (two DMRS CDM groups (CDM group #0-1)), two DMRS ports are multiplexed using FDM.

[0138] In addition, such as Figure 3A As shown, with DMRS configured as Enhancement Type 1 and Dual Symbol DMRS, eight DMRS ports (ports #4-7 and #12-15) can be further utilized. Within each DMRS CDM group (CDM group #0-1), four DMRS ports (ports #4-5 and #12-13, and ports #6-7 and #14-15) are multiplexed via FD OCCs of length 4 (FD-OCC#0-3). Between multiple DMRS CDM groups (two DMRS CDM groups (CDM group #0-1)), two DMRS ports are multiplexed via FDM. Furthermore, two DMRS ports in the time direction are multiplexed via TD OCCs of length 2 (TD-OCC#0-1). That is, multiple (two) CDM groups with the same index are multiplexed via TDM.

[0139] exist Figure 3A In the enhancement type 1 shown, 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}.

[0140] like Figure 3B As shown, for DMRS configuration enhancement type 2 and single-symbol DMRS, 12 DMRS ports (ports #0-5 and #12-17) can be utilized. Within each DMRS CDM group (CDM group #0-2), four DMRS ports (ports #0-1 and #12-13, port #2-3 and #14-15, port #4-5 and #16-17) are multiplexed via FD OCCs of length 4 (FD-OCC #0-3). Among multiple DMRS CDM groups (three DMRS CDM groups (CDM group #0-2)), three DMRS ports are multiplexed via FDM.

[0141] In addition, such as Figure 3BAs shown, with DMRS configured as Enhancement Type 2 and Dual Symbol DMRS, 12 DMRS ports (ports #6-11 and #18-23) can be further utilized. Within each DMRS CDM group (CDM group #0-2), four DMRS ports (ports #6-7 and #18-19, port #8-9 and #20-21, port #10-11 and #22-23) are multiplexed using FD OCCs of length 4 (FD-OCC#0-3). Among multiple DMRS CDM groups (three DMRS CDM groups (CDM group #0-2)), three DMRS ports are multiplexed using FDM. Two DMRS ports in the time direction are further multiplexed using TD OCCs of length 2 (TD-OCC#0-1). That is, multiple (two) CDM groups with the same index are multiplexed using TDM.

[0142] exist Figure 3B In the enhancement type 2 shown, 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, 4, 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}.

[0143] (DMRS port combination)

[0144] The study examines the antenna port indication for a DMRS port with a maximum DMRS length of 1 / 2 enhancement type 1 / enhancement type 2 for a PUSCH, which can indicate all of the following categories of DMRS port combinations.

[0145] (Category 1) A combination of multiple indices of an existing DMRS port (p=0 to 7 for Enhancement Type 1 and p=0 to 11 for Enhancement Type 2).

[0146] (Category 2) Combinations of multiple indices for the new DMRS port (p=8 to 15 for Enhancement Type 1, and p=12 to 23 for Enhancement Type 2).

[0147] (Category 3) A combination of existing DMRS port indices and new DMRS port indices within a CDM group with a maximum DMRS length of at least 1 (for Enhancement Type 1, this is a combination of at least one of the maximum 4 ports from p={0, 1, 8, 9} and the maximum 4 ports from p={2, 3, 10, 11}; for Enhancement Type 2, this is a combination of at least one of the maximum 4 ports from p={0, 1, 12, 13} and the maximum 4 ports from p={2, 3, 14, 15}). For ranks below 4, only one CDM group is used. For ranks greater than 4, more than one CDM group can be used.

[0148] Similarly, the DMRS port used by PDSCH is determined by p+1000.

[0149] The study investigates the support for a maximum DMRS length of 1 and rank of 5, 6, 7, or 8 in the enhanced type 1 / enhanced type 2 DMRS ports used in PDSCH / PUSCH.

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

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

[0152] CP-OFDM enables more flexible frequency resource allocation. For example, it allows for the allocation of both contiguous Physical Resource Blocks (PRBs) and non-contiguous PRBs. Furthermore, the allocation of contiguous PRBs is not limited to 2, 3, or 5 times. With CP-OFDM, frequency division multiplexing (FDM) can also be used for the demodulation reference signal (DMRS) and PUSCH.

[0153] DFT-s-OFDM (or DFT-s-OFDM / DFTS-OFDM) has significant limitations in frequency resource allocation, but a low peak to average power ratio (PAPR), making it suitable for UEs with limited power.

[0154] Furthermore, regarding communication throughput without considering PAPR, CP-OFDM has a higher communication throughput than DFT-s-OFDM. Regarding communication throughput considering PAPR, when SNR (MCS) is high (modulation coding scheme is 16QAM or 64QAM), CP-OFDM's communication throughput becomes higher than DFT-s-OFDM's; however, when SNR (MCS) is low (modulation coding scheme is QPSK), DFT-s-OFDM's communication throughput becomes higher than CP-OFDM's. That is, the preferred waveform varies depending on SNR (MCS).

[0155] Typically, network-wide (NW) waveform switching is based on signal-to-noise ratio (SNR). Switching between DFT-s-OFDM and CP-OFDM is achieved via the transform precoder in the Radio Resource Control (RRC) signaling's uplink shared channel (PUSCH) configuration (PUSCH-Config). CP-OFDM is applied when the transform precoder is disabled, and DFT-s-OFDM is applied when it is enabled. Waveform switching requires RRC reconstruction. This increases signaling overhead and raises concerns about reduced communication throughput.

[0156] (Activation and deactivation of 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)

[0157] For PUSCH scheduled via PDCCH, the UE performs the following procedure, wherein the PDCCH has a CRC scrambled by CS-RNTI, C-RNTI, MCS-C-RNTI, or SP-CSI-RNTI with new data indicator (NDI) = 1.

[0158] - If a DCI with scheduling permission is received using DCI format 0_0, the UE sends the PUSCH and considers the transform precoding valid or invalid according to the parameter msg3-transformPrecoder set by the higher layer.

[0159] - If a DCI with scheduling permission is not received using DCI format 0_0, the UE follows the procedure below.

[0160] -- When a DCI with scheduling permission is received using DCI format 0_1 ​​or 0_2, and the DCI format 0_1 ​​or 0_2 has a CRC that is scrambled by C-RNTI, MCS-C-RNTI, or CS-RNTI with NDI=1, and the UE has the higher-layer parameter dynamicTransformPrecoderIndicationDCI-0-1 set in the pusch-Config for DCI format 0_1, or dynamicTransformPrecoderIndicationDCI-0-2 set in the pusch-Config for DCI format 0_2, and the higher-layer parameter is set to "enabled", the UE transmits the PUSCH and considers the transformation precoding as valid or invalid according to the transform precoder indicator field in the DCI with scheduling permission.

[0161] --- For pushch-TimeDomainAllocationListForMultiPUSCH in pushch-Config, the UE sends all PUSCHs and considers the transformation precoding as valid or invalid based on the transformation precoder indicator field in DCI format 0_1 ​​with scheduling permission.

[0162] -- Otherwise, the UE follows the procedure below.

[0163] --- When the UE is configured with the higher-level parameter transformPrecoder in pusch-Config, the UE sends the PUSCH and, based on this parameter, considers the transform precoding valid or invalid.

[0164] --- If the UE has not set the higher-layer parameter transformPrecoder in pusch-Config, the UE will send the PUSCH and the transform precoding will be considered valid or invalid based on the higher-layer parameter msg3-transformPrecoder.

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

[0166] For more flexible throughput control, dynamic switching between CP-OFDM and DFT-s-OFDM is considered via DCI / MAC CE. However, such dynamic switching has not yet been studied.

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

[0168] (1) Use different tables for the two waveforms in the “Precoding information and number of layers” field.

[0169] (2) In the “Antenna ports” field, use different tables for the two waveforms.

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

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

[0172] (5) In “Frequency domain resource assignment”, the DCI size varies depending on the resource assignment type. Furthermore, the supported resource assignments differ depending on the waveform. CP-OFDM supports resource assignment types 0, 1, and 2, while DFT-s-OFDM supports resource assignment types 1 and 2.

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

[0174] The UE can receive settings indicating the dynamic switching of the transform precoder for the PUSCH via DCI / MAC CE for deactivation or activation. The UE can also receive indications indicating the activation or deactivation of the transform precoder for the PUSCH via DCI / MAC CE. Hereinafter, dynamic switching based on DCI / MAC CE will sometimes be simply referred to as dynamic switching. Alternatively, the UE can also have the dynamic switching of the waveform / transform precoder pre-configured in advance via higher-layer signaling, etc. (enabling switching). Dynamic switching of the transform precoder based on DCI / MAC CE can also be performed regardless of whether this configuration is present.

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

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

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

[0178] The switching between deactivation and activation of the transform precoder in this disclosure (waveform switching) can also be waveform switching within the same BWP (switching waveforms without switching the BWP). For example, since each BWP can be configured with a different transform precoder, switching the transform precoder via BWP switching is also considered. However, delays caused by BWP switching occur. Therefore, within the same BWP, by switching between deactivation and activation of the transform precoder, the delay can be suppressed.

[0179] When the deactivation and activation of the transform precoder for PUSCH are dynamically configured via DCI / MAC CE, the UE can also receive an indication of activation or deactivation of the transform precoder for PUSCH via DCI / MAC CE, and switch the waveform (CP-OFDM / DFT-s-OFDM) used for PUSCH based on the indication.

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

[0181] Among these, the size of each DCI field can vary depending on whether the transform precoder is deactivated or activated. These DCI fields include, for example, "Precoding information and number of layers," "Antenna ports," "DMRS sequence initialization," "PTRS-DMRS association," "Frequency resource assignment," and "Frequency hopping flag." For instance, as shown in (1) to (6) of the existing specifications above, the DCI sizes can also differ.

[0182] (argument)

[0183] The study only applies Rel. 18 DMRS to CP-OFDM. However, the relationship between the transformation precoder settings and DMRS settings, including the definition process and the RRC parameter used for setting, has not been fully investigated. If this relationship is not adequately studied, there are concerns that it could lead to increased PAPR and decreased communication quality / throughput.

[0184] Therefore, the inventors of this invention conceived of a method for setting DMRS.

[0185] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. Furthermore, the following embodiments (e.g., various scenarios) can be used individually or in combination of at least two.

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

[0187] In this disclosure, the terms "activate," "deactivate," "indicate," "select," "configure," "update," and "determine" can be overridden. Similarly, the terms "support," "control," "capable of control," "operate," and "capable of operation" can also be overridden.

[0188] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-level parameters, information elements (IEs), settings, etc., can also be modified interchangeably. In this disclosure, Medium Access Control (MAC) control elements (MAC control elements (CEs), update commands, activation / deactivation commands, etc., can also be modified interchangeably.

[0189] In this disclosure, higher-layer signaling may be any one or a combination of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, etc. In this disclosure, RRC signaling, RRC IE, RRC parameters, and higher-layer parameters may also be rewritten.

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

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

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

[0193] In this disclosure, a b The expressions a, b, and b appended to the right of a can also be rewritten. In this disclosure, a c The expressions a^c and a with c appended to the upper right of a can also be rewritten interchangeably. In this disclosure, a b c The expressions `a_b^c`, `append b to the lower right of a`, and `append c to the upper right of a` can also be rewritten. In this disclosure, `ceil(x)`, the floor function (rounding up), and the floor function can also be rewritten. In this disclosure, `floor(x)`, the floor function (rounding down), and the floor function can also be rewritten. In this disclosure, `sqrt(x)` and the square root function can also be rewritten. In this disclosure, x... ~ This can be represented by appending a tilde (~) above x, and can be called an x-shaped tilde. In this disclosure, x - This can be represented by appending a hyphen (-) above x, which can be called an x-bar. In this disclosure, x mod y, mod(x, y), the mod function, and the modulo operation can also be rewritten interchangeably.

[0194] In this disclosure, the port, antenna port, and DMRS port can also be interchanged.

[0195] In this disclosure, PUSCH uses DMRS port (number) p and PDSCH uses DMRS port (number) 1000+p, which can also be rewritten to each other.

[0196] In this disclosure, the dynamic switching of waveforms (CP-OFDM or DFT-s-OFDM), dynamic waveform switching (DWS), dynamic activation / deactivation indication of the transform precoder, and dynamic transform precoder indication can also be rewritten. In this disclosure, the settings for dynamic waveform switching, the settings for dynamic transform precoder indication, and dynamicTransformPrecoderIndicationDCI-0-1 or dynamicTransformPrecoderIndicationDCI-0-2 can also be rewritten.

[0197] In this disclosure, the application / use of CP-OFDM and the transformation precoder being disabled (deactivated) can also be rewritten interchangeably. The application / use of DFT-s-OFDM and the transformation precoder being enabled (activated) can also be rewritten interchangeably. In this disclosure, the transformation precoder being deactivated / activated, the transformation precoder being switched, and the waveform switching (CP-OFDM / DFT-s-OFDM) can also be rewritten interchangeably. The PUSCH waveform, waveform, and transformation precoder can also be rewritten interchangeably. CP-OFDM and CP-OFDM waveforms can also be rewritten interchangeably. DFT-s-OFDM and DFT-s-OFDM waveforms can also be rewritten interchangeably. "Enabled" and "On" can also be rewritten interchangeably. "Disabled" and "Off" can also be rewritten interchangeably.

[0198] In this disclosure, dynamic waveform switching (DWS), Rel. 18 DWS, and dynamic transform precoder indication can also be overridden. In this disclosure, the ability to dynamically switch PUSCH waveforms, to be set to dynamically switch PUSCH waveforms, to set DWS, and to enable DWS can also be overridden.

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

[0200] (Wireless communication method)

[0201] Figure 4 The table D-1 shown represents an example of parameters used for PDSCH DMRS setting type 1. Figure 5 The table D-2 shown represents an example of parameters used for PDSCH DMRS setting type 2. Figure 6 The table U-1 shown represents an example of parameters used for PUSCH DMRS setting type 1. Figure 7 Table U-2 shown is an example of parameters used for PUSCH DMRS setting type 2. The parameters in each table include PDSCH DMRS port p or PUSCH DMRS port p. ~ CDM group λ, frequency offset-related Δ, FD-OCC W f (k'), and TD-OCC W t (l').

[0202] The UE assigns each DMRS port p or p within the DMRS port combination corresponding to the antenna port field value. ~ Application of λ, Δ, W f (k'), and W t (l'). Without an enhanced DMRS type (enhanced-dmrs-Type_r18 or dmrs-TypeEnh), the FD-OCC W of length 2 corresponds to k'=0, 1. f (k') is applied to the DMRS. When the enhanced DMRS type is set (enhanced-dmrs-Type_r18 or dmrs-TypeEnh), the FD-OCC W of length 4 corresponds to k'=0, 1, 2, 3. f (k') is applied to DMRS.

[0203] As for the DMRS port p / p in DMRS configuration type 1 / 2 for PDSCH / PUSCH ~ There are existing DMRS ports and new DMRS ports. Existing DMRS ports are those within the range of existing DMRS port numbers, specifically p=1000-1007 in PDSCH DMRS setting type 1 and p in PUSCH DMRS setting type 1. ~ =0-7, p=1000-1011 in PDSCH DMRS setting type 2, p in PUSCH DMRS setting type 2 ~ =0-11. The new DMRS port is a DMRS port outside the existing DMRS port number range. It is p=1008-1015 in PDSCH DMRS setting type 1, or p in PUSCH DMRS setting 1. ~ =8-15, p=1012-1023 in PDSCH DMRS setting type 2, p in PUSCH DMRS setting type 2 ~ =12-23.

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

[0205] Without an enhanced DMRS type (enhanced-dmrs-Type_r18 or dmrs-TypeEnh), the antenna port field value indicates a combination of DMRS ports consisting only of existing DMRS ports. With an enhanced DMRS type (enhanced-dmrs-Type_r18 or dmrs-TypeEnh), the antenna port field value indicates a combination of DMRS ports from both existing and new DMRS ports.

[0206] Figure 8A This indicates the DMRS and FD-OCC (W) for DMRS port #0 of DMRS enhancement type 1. f (0), W f (1), W f (2), W f (3) is an example of a mapping. Figure 8B This indicates DMRS and FD-OCC (W) for DMRS port #2 of DMRS enhancement type 1. f (0), W f(1), W f (2), W f (3)) is an example of mapping. DMRS ports #0 and #2 correspond to CDM groups #0 and #1, respectively, and are mapped to different REs for FDM.

[0207] Figure 9A This indicates the DMRS and FD-OCC (W) for DMRS port #0 of DMRS enhancement type 2. f (0), W f (1), W f (2), W f (3) is an example of a mapping. Figure 9B This indicates DMRS and FD-OCC (W) for DMRS port #2 of DMRS enhancement type 2. f (0), W f (1), W f (2), W f (3) is an example of a mapping. Figure 10 This indicates DMRS and FD-OCC (W) for DMRS port #4 of DMRS enhancement type 2. f (0), W f (1), W f (2), W f (3)) is an example of mapping. DMRS ports #0, #2, and #4 correspond to different CDM groups #0, #1, and #2, respectively, and are mapped to different REs for FDM.

[0208] <Implementation Method 1>

[0209] This implementation involves the PDSCH processing procedure time of the UE.

[0210] In this disclosure, the PDSCH processing time and PDSCH processing duration can also be rewritten.

[0211] In this disclosure, capability 1 / capability 2 can also be rewritten with UE processing capability 1 / UE processing capability 2 for PDSCH.

[0212] (PDSCH processing time)

[0213] Regarding PDSCH processing time, the current specification defines two capabilities (Capability 1 / Capability 2).

[0214] In existing specifications (such as Rel. 15 NR), PDSCH processing time is divided into two types: processing time used by UE capability 1 and processing time used by UE capability 2. The processing time used by UE capability 2 is shorter than the processing time used by UE capability 1.

[0215] On the other hand, the goal of Rel. 18's DMRS is to support higher MU-MIMO layers in high-speed and high-capacity scenarios (e.g., enhanced Mobile Broadband (eMBB)).

[0216] However, in FD-OCC of length 4, in addition to the poor performance of channel estimation, channel estimation itself becomes a complex process. Therefore, applying Rel. 18 DMRS is not suitable for ultra-reliable and low-latency communications (e.g., Ultra Reliable and Low Latency Communications (URLLC)) scenarios.

[0217] That is, it is not preferred that the UE simultaneously supports PDSCH processing capabilities (especially UE processing capability 2) and Rel. 18 DMRS. Therefore, the UE needs to report / indicate to the NW (e.g., the base station) whether it simultaneously supports UE processing capability 2 and Rel. 18 DMRS.

[0218] More specifically, it is necessary to introduce UE capabilities that indicate whether the UE does not simultaneously support UE processing capability 2 and Rel. 18 DMRS, or whether the UE simultaneously supports UE processing capability and Rel. 18 DMRS.

[0219] When a UE feature group (FG) is introduced to indicate whether the UE simultaneously supports UE processing capability 2 and Rel. 18 DMRS, the UE can additionally report a relaxation of processing latency (computation latency) for PDSCH processing capability 2 within that UE feature group.

[0220] For example, in the case of a relaxation of UE report processing latency (for which this capability exists), this relaxation of processing latency can be used for the calculation of PDSCH processing latency.

[0221] Furthermore, there are no explicit provisions regarding the relaxation of processing latency for UE processing capability 1.

[0222] Here, d3 is introduced as a new parameter corresponding to the relaxation of this processing latency. The new parameter d3 can be called the processing latency parameter, or it can be appended to the formula for calculating the processing latency described later.

[0223] Without introducing this processing latency parameter, it is also possible to not support relaxing the processing latency.

[0224] The details will be described later, but the candidate values ​​for d3 can include at least 0 (in the case of UE processing capability 1).

[0225] (Example of a standard record)

[0226] The following is a specific example of the specification. This is merely an example; the names of specific UE capabilities may be changed as appropriate. The UE can use this example to control the processing / calculation related to PDSCH. Figure 11A This is an example of the processing time for a processing capacity of 1 for PDSCH. Figure 11B This is a graph representing an example of the processing time for PDSCH processing capacity 2. Figure 12 This is a diagram illustrating a specification related to the PDSCH processing time of the UE.

[0227] The UE needs to provide a valid HARQ-ACK message after a certain time interval (e.g., after the last symbol of the PDSCH for loading the acknowledged transport block (TB)) if the following conditions are met.

[0228] • The initial uplink symbol of the PUCCH that loads HARQ-ACK information does not begin before symbol L1.

[0229] Here, the HARQ-ACK information (the initial UL symbol) is based on the assigned HARQ-ACK timing K1 and K offset (If configured), and defined by the PUCCH resources used, it can include the effect / impact of timing advance.

[0230] K1 and K offset It can also be a higher-level parameter related to the HARQ-ACK timing (offset).

[0231] The L1 mentioned above can also be defined as the time interval T during a certain processing time. proc, 1 Then the next uplink symbol of the cyclic prefix (CP) begins. Here, T proc, 1 The following formula can be used to calculate it.

[0232]

[0233] Here, N1 can be based on Figure 11A (Processing capacity 1) and Figure 11B The value of μ (processing capacity 2) is determined by the amount of T. μ corresponds to the value that brings the maximum T. proc, 1 μPDCCH μ PDSCH μ UL Any one of them.

[0234] For example, μ PDCCH The subcarrier spacing corresponding to the PDCCH that schedules the PDSCH. μ PDSCH The subcarrier spacing corresponding to the scheduled PDSCH. μ UL The subcarrier spacing corresponding to a certain uplink channel.

[0235] Here, an uplink channel, if represented by HARQ-feedbackEnabling-disablingperHARQprocess (if configured), is envisioned as an uplink channel that sends HARQ-ACK regardless of whether the PDSCH receives a transport block of a HARQ process with deactivated HARQ-ACK information.

[0236] HARQ-feedbackEnabling-disablingperHARQprocess can also be a high-level parameter related to the setting of whether HARQ feedback is enabled or disabled in the HARQ process.

[0237] κ represents T S And T C The constant of the ratio between them is κ=T S / T C =64. Here, T S T represents the basic time unit for LTE. C This represents the basic time for NR.

[0238] d 1,1 d2 can also be a value determined by the processing capability of PDSCH, the PDSCH mapping type, the corresponding PDCCH, and the number of symbols in PDSCH.

[0239] like Figure 12 As shown, for UE processing capability 2, the value of d3 can be determined as follows. That is, the UE can determine / judge / identify the value of d3 as follows.

[0240] If the UE does not display a specific UE capability (any UE capability name), the UE does not expect to be activated (set to "enable") by the higher-level parameter (processingType2Enabled), but is simultaneously set by the higher-level parameter (enhanced-dmrs-Type_r18). In this case, the additional processing delay d3=0.

[0241] When the UE displays a specific UE capability (any UE capability name),

[0242] - When the UE is also configured with the higher-level parameter (enhanced-dmrs-Type_r18), the additional processing delay d3 can also be indicated based on the specific UE capability (any UE capability name).

[0243] - Otherwise, the additional processing delay d3=0.

[0244] On the other hand, for UE processing capability 1 (excluding UE processing capability 2), d3 can also be 0. That is, when the UE applies (supports) UE processing capability 1, it can decide / judge / identify that d3=0.

[0245] In the case of shared spectrum channel access in FR1, T ext It is calculated according to specific rules, otherwise it is 0. ext For example, it could also be the value applied in the initial UL transmission that is scheduled by scheduling DCI.

[0246] (Modified example)

[0247] The aforementioned processing time T proc, 1 =(N1+d 1, 1 +d2+d3)(2048+144)·κ2 -μ ·T C +T ext It can also be replaced as follows.

[0248] (Example 1) For UE processing capacity 1 / 2, T proc, 1 =(N1+d 1, 1 +d2)(2048+144)·κ2 -μ ·T C +T ext Otherwise (for UE processing capacity 2 / 1) is T proc, 1 =(N1+d 1, 1 +d2+d3)(2048+144)·κ2 -μ ·T C +T ext .

[0249] (Example 2) In addition to UE processing capability 2, it is T proc, 1 =(N1+d 1, 1 +d2)(2048+144)·κ2 -μ ·T C +T ext The UE processing capability 2 is T proc, 1 =(N1+d 1, 1 +d2+d3)(2048+144)·κ2-μ ·T C +T ext .

[0250] <Other>

[0251] If the UE does not show a specific UE capability (any UE capability name), the UE does not expect the higher-layer parameter (processingType2Enabled) to be activated (set to "enable"), and at the same time the higher-layer parameter (enhanced-dmrs-Type_r18) is set.

[0252] When the UE displays a specific UE capability (any UE capability name), the UE is simultaneously set with higher-layer parameters (enhanced-dmrs-Type_r18), and in addition to d2, the additional processing delay d3 can also be indicated by the specific UE capability (any UE capability name).

[0253] In implementation 1, PDSCH can be replaced with PUSCH.

[0254] According to Implementation Method 1, the UE can control PDSCH processing by considering new parameters corresponding to the relaxation of processing latency. That is, the UE can apply appropriate DMRS according to its capabilities.

[0255] <Implementation Method 2>

[0256] This implementation relates to PUSCH's DMRS.

[0257] To enable the UE to support the joint configuration of dynamic handover (DWS) between the Rel. 18 DMRS port and the Rel. 18 PUSCH between DFT-s-OFDM and CP-OFDM, the following guidelines are studied.

[0258] - Policy 1: If the UE has the higher-level parameter enhanced-dmrs-Type_r18 set in DMRS-UplinkConfig and is indicated to have valid transformation precoding via scheduling DCI, the UE ignores the higher-level parameter enhanced-dmrs-Type_r18 in DMRS-UplinkConfig.

[0259] - Policy 2: The UE is introduced with a new UE capability to indicate joint configuration supporting dynamic handover between the Rel. 18 DMRS port and the Rel. 18 PUSCH for DFT-s-OFDM and CP-OFDM.

[0260] - Policy 3: When both the Rel. 18 DMRS port and the DWS for the PUSCH are configured, and the scheduling DCI indicates DFT-s-OFDM, the DMRS type of the scheduled PUSCH is ambiguous. To address the issue of the UE ignoring the higher-level parameter enhanced-dmrs-Type_r18 in DMRS-UplinkConfig in this case, the following procedure B can be defined in the specification.

[0261] Procedure B: For PUSCH scheduled via PDCCH, the UE may also follow at least one of the following procedures Bx, wherein the PDCCH has a CRC scrambled by CS-RNTI, C-RNTI, MCS-C-RNTI, or SP-CSI-RNTI with NDI=1.

[0262] - Procedure B1: When a DCI with scheduling permission is received using DCI format 0_0, the UE sends the PUSCH and considers the transformation precoding as valid or invalid according to the parameter msg3-transformPrecoder set by the higher layer.

[0263] - Procedure B2: If the UE does not receive a DCI with scheduling permission using DCI format 0_0, it may also follow at least one of the following procedures B2-x.

[0264] -- Procedure B2-1: When the UE receives a DCI with scheduling permission using DCI format 0_1 ​​or 0_2, and the DCI format 0_1 ​​or 0_2 has a CRC scrambled by C-RNTI, MCS-C-RNTI, or CS-RNTI with NDI=1, and the UE sets the higher-level parameter dynamicTransformPrecoderIndicationDCI-0-1 in the pusch-Config for DCI format 0_1, or sets the higher-level parameter dynamicTransformPrecoderIndicationDCI-0-2 in the pusch-Config for DCI format 0_2, and the higher-level parameter is set to "enabled", the UE transmits the PUSCH and considers the transform precoding as enabled or invalid based on the transform precoder indicator field in the DCI with scheduling permission. The UE may also follow at least one of the following procedures B2-1-x.

[0265] --- Procedure B2-1-1: For push-TimeDomainAllocationListForMultiPUSCH in push-Config, the UE sends all PUSCHs and considers the transformation precoding as valid or invalid based on the transformation precoder indicator field in DCI format 0_1 ​​with scheduling permission.

[0266] --- Procedure B2-1-2: If the UE has the higher-layer parameter enhanced-dmrs-Type_r18 set in DMRS-UplinkConfig, and the scheduling permission indicates that the transformation precoding is valid for the scheduled PUSCH transmission, the UE will ignore the higher-layer parameter if the higher-layer parameter enhanced-dmrs-Type_r18 is set in DMRS-UplinkConfig for the scheduled PUSCH transmission.

[0267] -- Procedure B2-2: Otherwise (if the conditions of procedure B2-1 are not met), the UE may also follow at least one of the following procedures B2-2-x.

[0268] --- Procedure B2-2-1: When the UE is configured with the higher-layer parameter transformPrecoder in the pusch-Config, the UE sends the PUSCH and considers the transform precoding as valid or invalid based on this parameter.

[0269] --- Process B2-2-2: If the UE is not configured with the higher-layer parameter transformPrecoder in pusch-Config, the UE will send the PUSCH and the transform precoding will be considered valid or invalid based on the higher-layer parameter msg3-transformPrecoder.

[0270] To clarify the capabilities of the new UE, the UE can also follow the following guidelines C.

[0271] Policy C: If the UE supports the new UE capability (the UE reports support for the new UE capability), the UE can also proceed to 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 can also proceed to Policy A / Procedure A.

[0272] Policy A: The UE can also exclude the joint configuration of the Rel. 18 DMRS port and Rel. 18 DWS. When dynamic switching between DFT-s-OFDM and CP-OFDM is configured for the PUSCH, the UE may also not expect / intend to have the higher-level parameter enhanced-dmrs-Type_r18 set in DMRS-UplinkConfig. Regarding Policy A, the following procedure A can also be defined in the specification.

[0273] Process A: The UE can also follow several processes Ax.

[0274] - Procedure A1: In PUSCH repetition type B, the DMRS transmission procedure is applied separately for each actual repetition based on the allocation duration. The UE does not expect / intend to be indicated with an invalid antenna port setting for any actual repetition allocation duration.

[0275] - Procedure A2: When the UE has the higher-level parameter dynamicTransformPrecoderIndicationDCI-0-1 set in pusch-Config for DCI format 0_1, or the higher-level parameter dynamicTransformPrecoderIndicationDCI-0-2 set in pusch-Config for DCI format 0_2, and the higher-level parameter is set to "enabled", the UE does not expect / intend to have the higher-level parameter enhanced-dmrs-Type_r18 set in DMRS-UplinkConfig.

[0276] Regarding policy C, the following process C can also be defined in the specification.

[0277] Process C can also be defined by replacing process B2-1-2 in process B with at least one of the following processes B2-1-2x.

[0278] --- Procedure B2-1-2a: When the UE does not show / report new UE capabilities, and the higher-level parameter dynamicTransformPrecoderIndicationDCI-0-1 in pusch-Config is set for DCI format 0_1, or the higher-level parameter dynamicTransformPrecoderIndicationDCI-0-2 in pusch-Config is set for DCI format 0_2, and the higher-level parameter is set to "enabled", the UE does not expect / intend the higher-level parameter enhanced-dmrs-Type_r18 in DMRS-UplinkConfig to be set.

[0279] --- Procedure B2-1-2b: If the UE demonstrates / reports a new UE capability, and the UE has the higher-layer parameter enhanced-dmrs-Type_r18 set in DMRS-UplinkConfig, and the scheduling permission indicates that the transformation precoding is valid for the scheduled PUSCH transmission, then if the UE has the higher-layer parameter enhanced-dmrs-Type_r18 set in DMRS-UplinkConfig for the DMRS transmission of the scheduled PUSCH transmission, then the higher-layer parameter is ignored.

[0280] Figure 13 An example representing a part of process C.

[0281] In process B2-1 of process C, if the conditions of process B2-1 are met (S110: Yes), the UE will proceed to process B2-1-1 if needed. If the UE does not report a new UE capability (S120: No), the UE does not expect to be set to the enhanced DMRS type when the conditions of process B2-1-2a are met (S130). If the UE reports a new UE capability (S120: Yes), the UE ignores the setting of the enhanced DMRS type when the conditions of process B2-1-2b are met (S140).

[0282] In process B2-1 of process C, if the conditions of process B2-1 are not met (S110: No), the UE proceeds to process B2-2 (S150).

[0283] If either the conditions of procedure B2-1-2a or procedure B2-1-2b are met, the UE may also apply an existing DMRS port (existing FD-OCC, FD-OCC of length 2) to the DMRS of the PUSCH.

[0284] According to this implementation, the UE can apply appropriate DMRS based on its capabilities.

[0285] <Supplement>

[0286] [Information notification to UE]

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

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

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

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

[0291] [Notification from UE]

[0292] The notification of any information from the UE (to the NW) in the above embodiments (in other words, the transmission / reporting of any information from the UE to the BS) can also be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PUCCH, PUSCH, PRACH, reference signals), or combinations thereof.

[0293] In the case where the above notification is delivered via MAC CE, the MAC CE can also be identified by including a new LCID in the MAC sub-header that is not specified in the existing standard.

[0294] In cases where the above notification is sent via UCI, the above notification may also be sent using PUCCH or PUSCH.

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

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

[0297] At least one of the above-described implementation methods can also be applied under specific conditions. These specific conditions can be specified in the standard or communicated to the UE / BS using higher-layer signaling / physical-layer signaling. The specific conditions can also represent at least one of the following:

[0298] - Activated by setting at least one of the above-described embodiments.

[0299] At least one of the above-described implementations may also be applied only to UEs that have reported a specific UE capability or support that specific UE capability. This specific UE capability may also represent at least one of the following:

[0300] - The UE supports specific processing / operation / control / information for at least one of the above embodiments.

[0301] - The ability to apply an enhanced DMRS port corresponding to a specific DCI format. The UE capability for each DCI format may also indicate whether an enhanced DMRS port can be applied to PDSCHs scheduled via that DCI format. For example, at least one of the following UE capabilities may be defined / reported separately from the UE capability indicating whether an enhanced DMRS port can be applied to PDSCHs scheduled via DCI formats 1_1 / 1_2: UE capability indicating whether an enhanced DMRS port can be applied to PDSCHs scheduled via DCI format 1_3, and UE capability indicating whether an enhanced DMRS port can be applied to PDSCHs scheduled via DCI format 4_2.

[0302] - Enhanced DMRS ports can be applied to all DCI formats used for PDSCH scheduling. A UE capability can also indicate whether enhanced DMRS ports can be applied to PDSCH scheduled through all DCI formats used for PDSCH scheduling.

[0303] - The UE supports processing time for PDSCH / PUSCH, capability 1 / capability 2.

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

[0305] Furthermore, the aforementioned specific UE capabilities can be either capabilities that apply to all duplex modes (commonly regardless of the duplex mode) or capabilities that apply to each duplex mode (e.g., Time Division Duplex (TDD) and Frequency Division Duplex (FDD)).

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

[0307] - Information indicating the operation of activating / deactivating the above implementation method.

[0308] - RRC parameters for a specific version (e.g., Rel. 18 / 19). In Rel. YY (e.g., YY is 18 or higher), the RRC parameter for activation operation XXX can also be represented as XXX_rYY (XXX-rYY).

[0309] - The high-level parameter enhanced-dmrs-Type_r18 in DMRS-UplinkConfig.

[0310] - The high-level parameter dynamicTransformPrecoderIndicationDCI-0-1 in pusch-Config.

[0311] - The high-level parameter dynamicTransformPrecoderIndicationDCI-0-2 in pusch-Config.

[0312] The UE may also apply operations such as Rel.15 / 16 if it does not support at least one of the specific UE capabilities mentioned above, or if the specific information mentioned above is not set.

[0313] (Postscript)

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

[0315] [Postscript 1]

[0316] A terminal having:

[0317] The transmitting unit reports either capability 1 or capability 2 for the processing time of the shared channel; and

[0318] The control unit determines the application of parameters corresponding to the relaxation of processing time based on the type of processing time capability of the shared channel.

[0319] [Postscript 2]

[0320] The terminal as described in Appendix 1, wherein,

[0321] Without showing a specific terminal capability corresponding to capability 2, the control unit does not expect to be simultaneously set to activate capability 2 and enhance the demodulation reference signal (DMRS) type.

[0322] [Postscript 3]

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

[0324] If the specific terminal capability corresponding to capability 2 is not shown, or if the specific terminal capability corresponding to capability 2 is shown, the control unit determines that the parameter is 0.

[0325] [Postscript 4]

[0326] The terminal as described in any one of Annexes 1 to 3, wherein,

[0327] When capability 1 is applied, the control unit determines that the parameter is 0.

[0328] (Postscript)

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

[0330] [Postscript 1]

[0331] A terminal having:

[0332] The receiving unit receives a first setting indicated by the dynamic transformation precoder; and

[0333] The control unit determines, based on whether the terminal has reported specific capability information, whether to apply a specific frequency domain (FD)-orthogonal cover code (OCC) with a length greater than 2 to the demodulation reference signal (DMRS) used for the Physical Uplink Shared Channel (PUSCH).

[0334] [Postscript 2]

[0335] The terminal as described in Appendix 1, wherein,

[0336] If the terminal does not report specific capability information, the control unit determines that the second setting indicating the application of the specific FD-OCC to the DMRS is not sent.

[0337] [Postscript 3]

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

[0339] When the terminal reports specific capability information and receives a second setting indicating that the specific FD-OCC is applied to the DMRS, and receives downlink control information indicating that the transformation precoder is valid and the PUSCH is scheduled, the control unit ignores the second setting.

[0340] [Postscript 4]

[0341] The terminal as described in any one of Annexes 1 to 3, wherein,

[0342] The control unit applies a 2-length FD-OCC to the DMRS in the following two scenarios: when the terminal does not report specific capability information; and when the terminal reports specific capability information, receives a second setting indicating that the specific FD-OCC is applied to the DMRS, and receives downlink control information indicating that the transformation precoder is valid and the PUSCH is scheduled.

[0343] (Wireless communication system)

[0344] The structure of a wireless communication system according to one embodiment of this disclosure will now be described. In this wireless communication system, communication is performed using any one or a combination of the wireless communication methods according to the above embodiments of this disclosure.

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

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

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

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

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

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

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

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

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

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

[0355] The core network 30 may also include, for example, user plane functions (UPF), access and mobility management functions (AMF), session management functions (SMF), unified data management (UDM), application functions (AF), data network (DN), location management functions (LMF), and network functions (NF) such as operation, administration and maintenance (OAM). Alternatively, multiple functions can be provided through a single network node. Furthermore, communication with external networks (e.g., the Internet) can also be achieved via the DN.

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

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

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

[0359] In the wireless communication system 1, the downlink channel can also be a shared downlink channel (Physical Downlink Shared Channel (PDSCH)), a broadcast channel (Physical Broadcast Channel (PBCH)), or a downlink control channel (Physical Downlink Control Channel (PDCCH)) shared by each user terminal 20.

[0360] In addition, in the wireless communication system 1, the uplink channel can also be the shared uplink channel (Physical Uplink Shared Channel (PUSCH)), the uplink control channel (Physical Uplink Control Channel (PUCCH)), the random access channel (Physical Random Access Channel (PRACH)) shared by each user terminal 20, etc.

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

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

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

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

[0365] A search space can also correspond to a PDCCH candidate corresponding to one or more aggregation levels. One or more search spaces can also be referred to as a search space set. In addition, the terms "search space", "search space set", "search space setting", "search space set setting", "CORESET", "CORESET setting" etc. disclosed herein can be rewritten interchangeably.

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

[0367] Additionally, in this disclosure, downlink, uplink, etc., may be described without the word "link". Furthermore, it may be stated that the word "physical" is not included at the beginning of various channels.

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

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

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

[0371] (Base station)

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

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

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

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

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

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

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

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

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

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

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

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

[0384] On the other hand, the transmitting and receiving unit 120 (RF unit 122) can also amplify, filter, and demodulate the signals of the wireless frequency band received through the transmitting and receiving antenna 130 into the baseband signal.

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

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

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

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

[0389] The transmitting / receiving unit 120 can also receive either capability 1 or capability 2 for the processing time of the shared channel. The control unit 110 can also determine the application of parameters corresponding to the relaxation of the processing time based on the type of capability for the processing time of the shared channel.

[0390] The transmitting and receiving unit 120 can also transmit a first setting of the dynamic transformation precoder indication. The control unit 110 can also determine, based on whether specific capability information is reported, whether a specific frequency domain (FD)-orthogonal coverage code (OCC) of length greater than 2 is applied to the demodulation reference signal (DMRS) used for the Physical Uplink Shared Channel (PUSCH).

[0391] (User terminal)

[0392] Figure 16 This diagram illustrates an example of the structure of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Alternatively, the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may each be provided as one or more.

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

[0394] The control unit 210 implements control over all user terminals 20. The control unit 210 can be composed of controllers, control circuits, etc., described based on common knowledge in the technical field to which this disclosure pertains.

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

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

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

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

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

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

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

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

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

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

[0405] On the other hand, the transmitting and receiving unit 220 (RF unit 222) can also amplify, filter, demodulate, etc., the signals of the wireless frequency band received by the transmitting and receiving antenna 230.

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

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

[0408] Additionally, the measurement unit 223 can also derive channel measurements for CSI calculation based on channel measurement resources. Channel measurement resources can be, for example, non-zero power (NZP) CSI-RS resources. Furthermore, the measurement unit 223 can also derive interference measurements for CSI calculation based on interference measurement resources. Interference measurement resources can be at least one of NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, etc. Additionally, CSI-IM can also be referred to as CSI-Interference Management (IM), and can be interchanged with zero power (ZP) CSI-RS. Furthermore, in this disclosure, CSI-RS, NZPCSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc., can also be interchanged.

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

[0410] The transmit / receive unit 220 can also report capability 1 or capability 2 for the processing time of the shared channel. The control unit 201 can also determine the application of a parameter corresponding to the 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 shown, the control unit 210 may not expect to simultaneously set the activation of capability 2 and the enhanced demodulation reference signal (DMRS) type. If a specific terminal capability corresponding to capability 2 is not shown, or if a specific terminal capability corresponding to capability 2 is shown, the control unit 210 may determine that the parameter is 0. Alternatively, if capability 1 is applied, the control unit 210 may determine that the parameter is 0.

[0411] The transmitting and receiving unit 220 may also receive a first setting of the dynamic transformation precoder indication (e.g., dynamic transformation precoder indication setting). The control unit 210 may also determine, based on whether the terminal has reported specific capability information, whether a specific frequency domain (FD)-orthogonal coverage code (OCC) with a length greater than 2 is applied to the demodulation reference signal (DMRS) for the Physical Uplink Shared Channel (PUSCH) (e.g., enhanced DMRS port, enhanced DMRS type).

[0412] If the terminal does not report specific capability information, the control unit 210 may also determine that the second setting (e.g., enhanced DMRS type setting) for indicating the application of the specific FD-OCC to the DMRS is not sent.

[0413] If the terminal reports specific capability information and receives a second setting indicating that the specific FD-OCC is applied to the DMRS, and receives downlink control information indicating that the transformation precoder is valid and the PUSCH is scheduled, the control unit 210 may also ignore the second setting.

[0414] The control unit 210 may also apply a 2-length FD-OCC to the DMRS in the following two scenarios (e.g., existing DMRS port, existing DMRS type): when the terminal does not report specific capability information; and when the terminal reports specific capability information and receives a second setting indicating that the specific FD-OCC is applied to the DMRS, and receives downlink control information indicating that the transformation precoder is valid and the PUSCH is scheduled.

[0415] (Hardware structure)

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

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

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

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

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

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

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

[0423] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and performs various processes accordingly. As a program, a program that causes the computer to perform at least a portion of the operations described in the above embodiments can be used. For example, the control unit 110 (210) can also be implemented by a control program stored in the memory 1002 and operated in the processor 1001; similar implementations can be made for other functional blocks.

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

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

[0426] The communication device 1004 is hardware (transmitting and receiving device) used for communication between computers via at least one of a wired network and a wireless network. It is also referred to as a network device, network controller, network interface card (NIC), communication module, etc. To implement at least one of, for example, Frequency Division Duplex (FDD) and Time Division Duplex (TDD), the communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. For example, the aforementioned transmit / receive unit 120 (220) and transmit / receive antenna 130 (230) may also be implemented by the communication device 1004. The transmit / receive unit 120 (220) may also be implemented by physically or logically separating the transmit unit 120a (220a) and the receive unit 120b (220b).

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

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

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

[0430] (Modified example)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0460] Whether software is called software, firmware, middleware, microcode, hardware description language, or any other name, it should be broadly interpreted to refer to instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc.

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

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

[0463] In this disclosure, the terms “precoding”, “precoder”, “weight (precoding weight)”, “quasi-co-location (QCL)”, “transmission configuration indication state (TCI state)”, “spatial relation”, “spatial domain filter”, “transmit power”, “phase rotation”, “antenna port”, “layer”, “number of layers”, “rank”, “resource”, “resource set”, “beam”, “beamwidth”, “beam angle”, “antenna”, “antenna element”, “panel”, “UE panel”, “transmitting entity”, and “receiving entity” are used interchangeably.

[0464] Furthermore, in this disclosure, the antenna port can also be rewritten with an antenna port used for any signal / channel (e.g., a DeModulation Reference Signal (DMRS) port). In this disclosure, resources can also be rewritten with resources used for any signal / channel (e.g., reference signal resources, SRS resources, etc.). Additionally, resources can also include time / frequency / code / spatial / power resources. Moreover, the spatial domain transmission filter can also include at least one of a spatial domain transmission filter and a spatial domain reception filter.

[0465] The aforementioned groups may include, for example, at least one of the following: spatial relation group, code division multiplexing (CDM) group, reference signal (RS) group, control resource set (CORESET) group, PUCCH group, antenna port group (e.g., DMRS port group), layer group, resource group, beam group, antenna group, panel group, etc.

[0466] Furthermore, in this disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, Codeword (CW), Transport Block (TB), RS, etc., can also be rewritten to each other.

[0467] Furthermore, in this disclosure, the TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, and joint TCI state can also be rewritten to each other.

[0468] Furthermore, in this disclosure, terms such as "QCL", "QCL concept", "QCL relationship", "QCL type information", "QCL property (QCLproperty / properties)", "specific QCL type (e.g., type A, type D) property", and "specific QCL type (e.g., type A, type D)" can be rewritten interchangeably.

[0469] In this disclosure, indexes, identifiers (IDs), indicators, indications, resource IDs, etc., can be interchanged. Sequences, lists, sets, groups, clusters, subsets, etc., can also be interchanged.

[0470] Furthermore, the spatial relationship information Identifier (ID) (TCI state ID) and spatial relationship information (TCI state) can be interchanged. "Spatial relationship information (TCI state)" can also be interchanged with "a set of spatial relationship information (TCI states)," "one or more spatial relationship information," etc. TCI state and TCI can also be interchanged. Spatial relationship information and spatial relationships can also be interchanged.

[0471] In this disclosure, the terms "Base Station (BS)", "Wireless Base Station", "Fixed Station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "Access Point", "Transmission Point (TP)", "Reception Point (RP)", "Transmission / Reception Point (TRP)", "Panel", "Cell", "Sector", "Cell Group", "Carrier", and "Component Carrier" are used interchangeably. There are also instances where the terms macro cell, small cell, femtocell, and picocell are used to refer to a base station.

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

[0473] In this disclosure, the act of a base station sending information to a terminal can also be rewritten in relation to the act of the base station instructing the terminal to perform control / operation based on that information.

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

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

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

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

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

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

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

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

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

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

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

[0485] The driver assistance system unit 64 comprises various devices used to provide functions for preventing accidents or reducing the driver's workload, such as millimeter-wave radar, light detection and ranging (LiDAR), cameras, positioning detectors (e.g., Global Navigation Satellite System (GNSS), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyroscope systems (e.g., Inertial Measurement Unit (IMU), Inertial Navigation System (INS)), artificial intelligence (AI) chips, and AI processors, and one or more ECUs that control these devices. Furthermore, the driver assistance system unit 64 sends and receives various information via communication module 60 to realize driver assistance functions or autonomous driving functions.

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

[0487] The communication module 60 can be controlled by the microprocessor 61 of the electronic control unit 49 and is a communication device capable of communicating with external devices. For example, it can transmit and receive various types of information with external devices via wireless communication. The communication module 60 can be located both inside and outside the electronic control unit 49. The external device can be, for example, the aforementioned base station 10, user terminal 20, etc. Furthermore, the communication module 60 can be, for example, at least one of the aforementioned base station 10 and user terminal 20 (or it can function as at least one of the base station 10 and user terminal 20).

[0488] The communication module 60 can also wirelessly transmit at least one of the signals input to the electronic control unit 49 from the various sensors 50-58 described above, the information obtained based on these signals, and the information based on input from an external (user) source obtained via the information service unit 59 to an external device. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc., can also be referred to as input units that receive input. For example, the PUSCH transmitted via the communication module 60 can also contain information based on the aforementioned inputs.

[0489] The communication module 60 receives various information (traffic information, signal information, workshop information, etc.) sent from external devices and displays it on the vehicle's information service unit 59. The information service unit 59 can also be referred to as an output unit that outputs information (for example, outputs information to devices such as displays and speakers based on the PDSCH received by the communication module 60 (or the data / information decoded from the PDSCH).

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

[0491] Furthermore, the base station in this disclosure can also be rewritten as a user terminal. For example, various methods / implementations of this disclosure can be applied to structures where communication between the base station and the user terminal is replaced by communication between multiple user terminals (e.g., also referred to as device-to-device (D2D) or vehicle-to-everything (V2X)). In this case, it can also be configured such that the user terminal 20 has the functions of the base station 10 described above. In addition, terms such as "uplink" and "downlink" can be rewritten as terms corresponding to inter-terminal communication (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can also be rewritten as sidelink channel.

[0492] Similarly, the user terminal in this disclosure can also be rewritten as a base station. In this case, it can also be configured such that the base station 10 has the functions of the user terminal 20 described above.

[0493] In this disclosure, operations are assumed to be performed by the base station, and sometimes, depending on the circumstances, by its upper node. In a network containing one or more network nodes having a base station, the various operations performed for communication with a terminal can obviously be performed by the base station, one or more network nodes other than the base station (e.g., considering a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc., but not limited to these), or combinations thereof.

[0494] The various methods / implementations described in this disclosure can be used individually or in combination, and can be switched as needed during execution. Furthermore, the processing procedures, timing sequences, flowcharts, etc., of the various methods / implementations described in this disclosure can be rearranged as long as they do not contradict each other. For example, for the method described in this disclosure, the illustrated order is used to indicate various steps, but the order in which they are indicated is not limited.

[0495] The various methods / implementations described in this disclosure can also be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG, where x is, for example, an integer or a decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Futuregeneration Radio Access (FX), Global System for Mobile Communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE This includes 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-Wideband (UWB)), Bluetooth (registered trademark), systems utilizing other suitable wireless communication methods, and next-generation systems derived from, modified, generated, or specified based on these methods. Furthermore, multiple systems can be combined (e.g., LTE or LTE-A, combinations with 5G, etc.) for application.

[0496] As used in this disclosure, the term "based on" does not mean "based on only" unless otherwise specified. In other words, the term "based on" means both "based on only" and "based on at least".

[0497] Any reference to an element using the designations "first," "second," etc., as used in this disclosure does not comprehensively limit the quantity or order of these elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, reference to the first and second elements does not imply that only two elements may be used, or that the first element must take precedence over the second element in some form.

[0498] The term "determining" as used in this disclosure can encompass a wide variety of operations. For example, "determining" can also refer to judging, calculating, computing, processing, deriving, investigating, looking up (search, inquiry) (e.g., searching in a table, database or other data structure), and ascertaining.

[0499] In addition, "judgment (decision)" can also refer to receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, accessing (e.g., accessing data in memory), etc., as situations where "judgment (decision)" is performed.

[0500] Furthermore, "judgment (decision)" can also refer to situations where resolving, selecting, choosing, establishing, or comparing are considered as making a "judgment (decision)". That is, "judgment (decision)" can also refer to certain actions as situations where a "judgment (decision)" is made. In this disclosure, "judgment (decision)" can also be rewritten in relation to the aforementioned actions.

[0501] Furthermore, in this disclosure, "determine / determining" can also be interchanged with "assume / assuming," "expect / expecting," "consider / considering," etc. Additionally, in this disclosure, "not assuming to proceed..." can also be interchanged with "assuming not to proceed..."

[0502] In this disclosure, "expect" can also be interchanged with "be expected." For example, "expect(s) ..." (where "..." can also be expressed using a that clause, to infinitive, etc.) can also be interchanged with "be expected ...." "Does not expect..." can also be interchanged with "be not expected...". Furthermore, "An apparatus A is not expected..." can also be interchanged with "Apparatus B other than apparatus A does not expect..." (for example, if apparatus A is a UE, apparatus B can also be a base station).

[0503] The term "maximum transmit power" as used in this disclosure may refer to the maximum value of the transmit power, the nominal maximum transmit power (the nominal UE maximum transmit power), or the rated maximum transmit power (the rated UE maximum transmit power).

[0504] As used in this disclosure, the terms “connected,” “coupled,” or all variations thereof, refer to all direct or indirect connections or combinations between two or more elements, and can include cases where there is one or more intermediate elements between two mutually “connected” or “coupled” elements. The connections or combinations between elements can be physical, logical, or a combination thereof. For example, “connection” can also be rewritten as “access.”

[0505] In this disclosure, when two elements are connected, it is possible to consider using more than one wire, cable, printed electrical connection, etc. to be "connected" or "combined" with each other, and as several non-limiting and non-exclusive examples, to use electromagnetic energy with wavelengths having wireless frequency domain, microwave region, light (both visible and invisible) region to be "connected" or "combined" with each other.

[0506] In this disclosure, the term "A is different from B" can also mean "A and B are different from each other." Additionally, the term can also mean "A and B are each different from C." Terms such as "separate" and "combined" can also be interpreted in the same way as "different."

[0507] When the terms "include," "including," and variations thereof are used in this disclosure, these terms, like the term "comprising," mean inclusive. Furthermore, the term "or" as used in this disclosure does not mean XOR.

[0508] In this disclosure, for example, in cases where articles are added through translation, such as a, an, and the in English, the disclosure may also include cases where the noun following these articles is in a plural form.

[0509] In this disclosure, words such as "below," "less than," "above," "more," and "equal to" can be interchanged. Furthermore, in this disclosure, words meaning "good," "bad," "large," "small," "high," "low," "early," "late," "wide," and "narrow," etc., are not limited to the positive, comparative, and superlative degrees, and can be interchanged. Additionally, in this disclosure, words meaning "good," "bad," "large," "small," "high," "low," "early," "late," "wide," and "narrow," etc., as expressions with "i" appended (i being any integer), are not limited to the positive, comparative, and superlative degrees, and can be interchanged (for example, "highest" can also be interchanged with "i-th highest").

[0510] In this disclosure, "of", "for", "regarding", "related to", "associated with", etc., can also be rewritten interchangeably.

[0511] In this disclosure, phrases such as "when A, B", "if A, then B", "B upon A", "B in response to A", "based on A", "B during / while A", "before A", "at the same time as / on A", "after A", "since A", and "until A" can be rewritten interchangeably. Furthermore, A and B can be replaced with appropriate expressions such as nouns, gerunds, or ordinary sentences depending on the context. Additionally, the time difference between A and B can be approximately 0 (immediately following or immediately preceding). Moreover, a time offset can be applied to the time when A occurs. For example, "A" can also be rewritten interchangeably with "before / after the time offset of A". This time offset (e.g., more than one symbol / slot) can be predetermined or determined by the UE based on the information it is notified of.

[0512] In this disclosure, timing, moment, time, time instance, arbitrary time unit (e.g., time slot, sub-time slot, symbol, subframe), period, opportunity, resource, etc., can also be overridden.

[0513] The inventions disclosed herein have been described in detail above. However, it will be apparent to those skilled in the art that the inventions disclosed herein are not limited to the embodiments described herein. The description herein is for illustrative purposes only and is not intended to limit the inventions disclosed herein in any way.

[0514] This application is based on Special Application 2023-195364, filed on November 16, 2023. The entire contents of that application are contained herein.

Claims

1. A terminal, comprising: The transmitting unit reports either capability 1 or capability 2 for the processing time of the shared channel; and The control unit determines the application of parameters corresponding to the relaxation of processing time based on the type of processing time capability of the shared channel.

2. The terminal as described in claim 1, wherein, Without showing a specific terminal capability corresponding to capability 2, the control unit does not expect to be simultaneously set to activate capability 2 and enhance the demodulation reference signal (DMRS) type.

3. The terminal as described in claim 1, wherein, If the specific terminal capability corresponding to capability 2 is not shown, or if the specific terminal capability corresponding to capability 2 is shown, the control unit determines that the parameter is 0.

4. The terminal as described in claim 1, wherein, When capability 1 is applied, the control unit determines that the parameter is 0.

5. A wireless communication method for a terminal, comprising: Report the steps for capability 1 or capability 2 of the shared channel processing time; and Based on the type of processing time capability of the shared channel, the steps for determining the application of parameters corresponding to the relaxation of processing time are as follows.

6. A base station, comprising: The receiving unit is capable of receiving either capability 1 or capability 2 for processing time of the shared channel; and The control unit determines the application of parameters corresponding to the relaxation of processing time based on the type of processing time capability of the shared channel.

Images