Terminal, wireless communication method, and base station

Abstract

To apply an appropriate DMRS.SOLUTION: A terminal according to one aspect of the present disclosure includes a receiving unit that receives a demodulation reference signal (DMRS) setting and receives a downlink control information (DCI) format for scheduling multiple physical uplink shared channels (PUSCHs) in multiple cells, having one PUSCH for each cell, and a control unit that determines, on the basis of the setting and the DCI format, whether a frequency domain (FD)-orthogonal cover code (OCC) of length 4 is applied to the DMRS for the multiple PUSCHs.SELECTED DRAWING: Figure 10

Description

[Technical Field]

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

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

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

[0004] [Non-Patent Document 1] 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010 Summary of the Invention [Problem to be solved by the invention]

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

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

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

[0008] A terminal according to one embodiment of the present disclosure includes a receiver that receives a demodulation reference signal (DMRS) configuration and receives a downlink control information (DCI) format for scheduling multiple physical uplink shared channels (PUSCHs) in multiple cells, each having one PUSCH per cell; and a controller that determines, based on the configuration and the DCI format, whether a frequency domain (FD)-orthogonal cover code (OCC) of length 4 is applied to the DMRS for the multiple PUSCHs. [Effects of the Invention]

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

[0010] [Figure 1] FIG. 1 shows an example of a preceding DMRS and an additional DMRS. [Figure 2] 2A and 2B show an example of a DMRS to DMRS mapping type. [Figure 3]FIG. 3 shows an example of parameters for PDSCH DMRS configuration type 1. [Figure 4] FIG. 4 shows an example of parameters for PUSCH DMRS configuration type 1. [Figure 5] FIG. 5 shows an example of an antenna port table AD-1 for PDSCH. [Figure 6] FIG. 6 shows an example of an antenna port table AU-8 for the PUSCH. [Figure 7] FIG. 7 shows an example of a multicast PDSCH. [Figure 8] FIG. 8 shows a first part of an example of an antenna port table AD-7 for the PDSCH when the extended DMRS type is configured. [Figure 9] FIG. 9 shows a second part of an example of antenna port table AD-7 for PDSCH when the extended DMRS type is configured. [Figure 10] FIG. 10 shows an example of antenna port table AU-38 for PUSCH when the extended DMRS type is configured. [Figure 11] FIG. 11 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 12] FIG. 12 is a diagram illustrating an example of the configuration of a base station according to an embodiment. [Figure 13] FIG. 13 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. [Figure 14] FIG. 14 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. [Figure 15] FIG. 15 is a diagram illustrating an example of a vehicle according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0011] (DMRS) The DMRS is used for channel estimation / data demodulation for the PDSCH / PUSCH.

[0012] The front-loaded Demodulation Reference Signal (DMRS) is the first DMRS (first symbol or symbol close to the first) for faster demodulation (reducing data demodulation time) (Fig. 1). For high-speed mobile terminals (user terminals, User Equipment (UE)) or high modulation and coding schemes (MCS) / ranks, {0, 1, 2, 3} additional DMRSs can be configured by the RRC IE. The additional DMRSs are useful for scenarios such as high Doppler frequencies and high MCSs. The frequency location of the additional DMRSs is the same as that of the front-loaded DMRSs.

[0013] For the frequency domain, (PDSCH / PUSCH) DMRS configuration type 1 or 2 is configured. DMRS configuration type 1 has a comb structure and is applicable to both CP-OFDM (transport precoding disabled) and DFT-S-OFDM (transport precoding enabled). The minimum RE (subcarrier) group in the frequency domain is one RE. For example, type 1 may be used for better coverage. ◆DMRS configuration type 2 is applicable only to CP-OFDM. The minimum RE group in the frequency domain is two consecutive REs. For example, type 2 may be used for higher ranks.

[0014] A single symbol DMRS or a double symbol DMRS is configured. ◆Single-symbol DMRS is normally used (it is a mandatory feature in Rel. 15). In single-symbol DMRS, the number of additional DMRS (symbols) is {0, 1, 2, 3}. Single-symbol DMRS is supported both when frequency hopping is enabled and when it is disabled. If the maximum number (maxLength) in the uplink DMRS configuration (DMRS-UplinkConfig) is not configured, single-symbol DMRS is used. In DMRS configuration type 1, DMRS is allocated to one RE out of every two consecutive REs in the frequency domain. In DMRS configuration type 2, DMRS is allocated to two consecutive REs out of every six consecutive REs in the frequency domain. ◆Double-symbol DMRS is used for more DMRS ports (especially Multi-User Multiple-Input Multiple-Output (MU-MIMO)). In double-symbol DMRS, the number of additional DMRS (symbols) is {0, 1}. Double-symbol DMRS is supported when frequency hopping is disabled. If the maximum number (maxLength) in the uplink DMRS configuration (DMRS-UplinkConfig) is 2 (len2), whether it is single-symbol DMRS or double-symbol DMRS is determined by DCI or configured grant. DMRS is allocated to one RE every two consecutive REs in the frequency domain. Figure 2A shows an example of DMRS configuration type 1 for double-symbol DMRS. In DMRS configuration type 2, DMRS is allocated to two consecutive REs every six consecutive REs in the frequency domain. Figure 2B shows an example of DMRS configuration type 2 for double-symbol DMRS.

[0015] For an additional DMRS [in the time domain], the additional DMRS position is set by the higher layer parameter dmrs-AdditionalPosition. For example, in the case of single symbol DMRS, mapping type A, dmrs-AdditionalPosition=pos0, the DMRS position is l0. For example, in the case of single symbol DMRS, mapping type A, dmrs-AdditionalPosition=pos1, l d For example, in the case of single symbol DMRS, mapping type A, dmrs-AdditionalPosition=pos3,l d For example, in the case of single symbol DMRS, mapping type B, dmrs-AdditionalPosition=pos3, l d In the case of =7, the DMRS position is l0,4. For example, in the case of double symbol DMRS, mapping type A, dmrs-AdditionalPosition=pos0, the DMRS position is l0. For example, in the case of double symbol DMRS, mapping type A, dmrs-AdditionalPosition=pos1, l d For example, in the case of double symbol DMRS, mapping type B, dmrs-AdditionalPosition=pos1,l, the DMRS position is l0,8. For example, in the case of double symbol DMRS, mapping type B, dmrs-AdditionalPosition=pos0, the DMRS position is l0. For example, in the case of double symbol DMRS, mapping type B, dmrs-AdditionalPosition=pos1,l d In the case of =10, the DMRS position is l0,7.

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

[0017] In contrast to the basic DMRS in Rel. 15, an extended DMRS is introduced in Rel. 18. The extended DMRS is configured by the upper layer parameter dmrs-TypeEnh.

[0018] There are several parameters for the DMRS port: ◆OCC type: Walsh matrix is ​​used for OCC for PDSCH. Cyclic shift is used for OCC for PUSCH. ◆FD-OCC: As two FD-OCCs for the basic DMRS, w f (k'), k'=0,1 to w f (1) is used. For the four FD-OCCs for the extended DMRS, w f (k'), where k'=0, 1, 2, 3 is used. ◆TD-OCC: As two TD-OCCs for double symbol DMRS, w t (l'), l'=0,1 is used.

[0019] There are several possible settings for DMRS: ◆ Setting 1: Basic DMRS, setting type 1, single symbol DMRS With two CDM groups of FDM and two FD-OCC (length 2) CDM in each CDM group, up to four DMRS ports are available. ◆ Setting 2: Basic DMRS, Setting Type 1, Double Symbol DMRS With FDM of two CDM groups and CDM using two FD-OCCs (length 2) and two TD-OCCs (length 2) in each CDM group, up to eight DMRS ports are available. ◆ Setting 3: Basic DMRS, setting type 2, single symbol DMRS With FDM of three CDM groups and CDM using two FD-OCCs (length 2) in each CDM group, up to six DMRS ports are available. ◆ Setting 4: Basic DMRS, Setting Type 2, Double Symbol DMRS With FDM of three CDM groups and CDM using two FD-OCCs (length 2) and two TD-OCCs (length 2) in each CDM group, up to 12 DMRS ports are available. ◆ Setting 5: Extended DMRS, setting type 1, single symbol DMRS With two CDM groups of FDM and four FD-OCC (length 4) CDM in each CDM group, up to eight DMRS ports are available. ◆ Setting 6: Extended DMRS, setting type 1, double symbol DMRS With FDM of two CDM groups and CDM using four FD-OCCs (length 4) and two TD-OCCs (length 2) within each CDM group, up to 16 DMRS ports are available. ◆ Setting 7: Extended DMRS, setting type 2, single symbol DMRS With FDM of three CDM groups and CDM using four FD-OCCs (length 4) in each CDM group, up to 12 DMRS ports are available. ◆ Setting 8: Extended DMRS, setting type 2, double symbol DMRS With FDM of three CDM groups and CDM using four FD-OCCs (length 4) and two TD-OCCs (length 2) within each CDM group, up to 24 DMRS ports are available.

[0020] In the present disclosure, legacy DMRS, basic DMRS, Rel. 15 DMRS, legacy DMRS function, legacy DMRS [configuration] type, basic DMRS [configuration] type, dmrs-Type, DMRS configuration type 1 / 2, DMRS with FD-OCC of length 2, Rel. 15 DMRS type, legacy DMRS port, Rel. 15 DMRS port, DMRS port to which legacy FD-OCC is applied, DMRS port within the port number range of legacy DMRS, legacy DMRS port, legacy DMRS configuration type is configured, legacy DMRS configuration type 1 or 2 is configured, extended DMRS type (dmrs-TypeEnh) is not configured, and legacy DMRS port is indicated may be read interchangeably.

[0021] In the present disclosure, DMRS [setting] type 1, DMRS type = 1, DMRS Type 1, and dmrs-Type set to type 2 are not set may be interpreted as interchangeable. In the present disclosure, DMRS [setting] type 2, DMRS type = 2, DMRS Type 2, and dmrs-Type set to type 2 are set may be interpreted as interchangeable.

[0022] In the present disclosure, new DMRS, enhanced DMRS, Rel. 18 DMRS, enhanced DMRS function, extended DMRS [configuration] type, configuration / upper layer parameters for extended DMRS type, enhanced-dmrs-Type_r18, dmrs-TypeEnh, extended DMRS configuration type 1 / 2, DMRS with FD-OCC of length 4, Rel. 18 DMRS type, new DMRS port, Rel. 18 DMRS port, DMRS port to which new FD-OCC is applied, DMRS port outside the port number range of existing DMRS, extended DMRS port, extended DMRS type (dmrs-TypeEnh) being configured, enhanced-dmrs-Type_r18 being configured, extended DMRS configuration type 1 or 2 being configured, extended DMRS type being configured, and extended DMRS port being indicated may be read as interchangeable.

[0023] In the present disclosure, extended DMRS [configuration] Type 1, DMRS extension Type 1, DMRS extension Type=1, DMRS eType 1, and the extended DMRS type is configured and dmrs-Type set to type 2 is not configured may be interpreted as interchangeable. In the present disclosure, extended DMRS [configuration] Type 2, DMRS extension Type 2, DMRS extension Type=2, DMRS eType 2, and the extended DMRS type is configured and dmrs-Type set to type 2 may be interpreted as interchangeable.

[0024] In this disclosure, the DMRS maximum length, maxLength, and the maximum number of OFDM symbols of a front-loaded DMRS may be interchangeable. In this disclosure, the maxLength values ​​{'len1', 'len2'} and maxLength={1, 2} [symbols] may be interchangeable.

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

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

[0027] In the present disclosure, the terms [antenna] port, DMRS port, DMRS port number, DMRS port index, and antenna port number -1000 may be read interchangeably.

[0028] In existing specifications, a DMRS configuration in the frequency domain is represented by a parameter k (subcarrier index of a DMRS RE), and a DMRS configuration in the time domain is represented by a parameter l (symbol index of a DMRS RE).

[0029] A table (DMRS parameter table, association) showing parameters for DMRS configuration type 1 or 2 of PUSCH or PDSCH is ~ and CDM group λ, Δ with respect to frequency offset, FD-OCC W f (k'), TD-OCC W t (l') indicates an association between at least one of

[0030] Table DD-1 shown in Figure 3 shows an example of parameters for PDSCH DMRS configuration type 1. Basic type 1 single-symbol DMRS uses ports 1000 to 1003. Basic type 1 double-symbol DMRS uses ports 1000 to 1007. Extended type 1 single-symbol DMRS uses ports 1000 to 1003 and 1008 to 1011. Extended type 1 double-symbol DMRS uses ports 1000 to 1015.

[0031] Table DU-1 shown in Figure 4 shows an example of parameters for PUSCH DMRS configuration type 1. Basic type 1 single-symbol DMRS uses ports 0 to 3. Basic type 1 double-symbol DMRS uses ports 0 to 7. Extended type 1 single-symbol DMRS uses ports 0 to 3 and 8 to 11. Extended type 1 double-symbol DMRS uses ports 0 to 15.

[0032] The symbol index l is l=l - +l'. -represents the position of the DMRS in the time domain. For single-symbol DMRS, l'=0. For double-symbol DMRS, l'=0,1.

[0033] v is the number of layers. j=0,1,...,v-1 is the layer index. p_j is the port number of layer j. μ is the subcarrier spacing (SCS) setting. Δ is related to the CDM group ID. CDM group 0 corresponds to Δ=0, CDM group 1 corresponds to Δ=1, and CDM group 2 corresponds to Δ=4. The DMRS sequence r(n) is expressed using a pseudorandom (pseudo noise) sequence c(n).

[0034] w f (k')(FD-OCC) and w t (l')(TD-OCC) is the orthogonal cover code defined in the specification. If the upper layer parameter dmrs-TypeEnh is set, the FD-OCC length is 4, otherwise the FD-OCC length is 2. The TD-OCC length is 2.

[0035] n=0,1,... is the index for each FD-OCC.

[0036] ((Notification of PDSCH DMRS port)) One or more DMRS ports used for PDSCH transmission are notified to the UE by the antenna port field in the DCI based on a table (antenna port table, association) for antenna port (DMRS port) indication [for DMRS configuration type 1 or 2 and DMRS maximum length 1 or 2]. Based on the antenna port table such as Table AD-1 in Figure 5, the value of the antenna port field notifies the UE of the index of one or more DMRS ports, the number of preceding DMRS symbols, and the number of DMRS CDM group(s) without data. The UE counts the number of REs based on the notified information.

[0037] For DCI formats that schedule PDSCH, the following [Antenna Port] tables are specified, which show the association between the value of the antenna port field, the number of DMRS CDM groups without data, the DMRS port number, and the [number of preceding symbols]. ◆Table AD-1, Table AD-1A: Case where DMRS type (dmrs-Type) = 1 is set, extended DMRS type (dmrs-TypeEnh) is not set, and DMRS maximum length (maxLength) = 1 is set. ◆Table AD-2, Table AD-2A: Case where DMRS type (dmrs-Type) = 1 is set, extended DMRS type (dmrs-TypeEnh) is not set, and DMRS maximum length (maxLength) = 2 is set. ◆Table AD-3, Table AD-3A: Case where DMRS type (dmrs-Type) = 2 is set, extended DMRS type (dmrs-TypeEnh) is not set, and DMRS maximum length (maxLength) = 1 is set. ◆Table AD-4, Table AD-4A: Case where DMRS type (dmrs-Type) = 2 is set, extended DMRS type (dmrs-TypeEnh) is not set, and DMRS maximum length (maxLength) = 2 is set. ◆Table AD-7, Table AD-7A: Case where DMRS type (dmrs-Type) = 1 is set, extended DMRS type (dmrs-TypeEnh) is set, and DMRS maximum length (maxLength) = 1 is set. ◆Table AD-8, Table AD-8A: Case where DMRS type (dmrs-Type) = 1 is set, extended DMRS type (dmrs-TypeEnh) is set, and DMRS maximum length (maxLength) = 2 is set. ◆Table AD-9, Table AD-9A: Case where DMRS type (dmrs-Type) = 2 is set, extended DMRS type (dmrs-TypeEnh) is set, and DMRS maximum length (maxLength) = 1 is set. ◆Table AD-10, Table AD-10A: Case where DMRS type (dmrs-Type) = 2 is set, extended DMRS type (dmrs-TypeEnh) is set, and DMRS maximum length (maxLength) = 2 is set.

[0038] If a UE that does not have dl-OrJointTCI-StateList configured for the antenna port field of DCI format 1_1 receives an activation command that maps at least one codepoint of the DCI field 'Transmission Configuration Indication' to two TCI states, or if a UE that has dl-OrJointTCI-StateList configured has two indicated TCI states, the UE shall use tables AD-1 / 2 / 3 / 4 / 7 / 8 / 9 / 10, otherwise the UE shall use tables AD-1A / 2A / 3A / 4A / 7A / 8A / 9A / 10A.

[0039] ((Notification of PUSCH DMRS port)) One or more DMRS ports used for PUSCH transmission are notified to the UE by the antenna port field in the DCI based on a table (antenna port table) for indicating antenna ports (DMRS ports) [for at least one of DMRS configuration type 1 or 2, DMRS max length 1 or 2, and rank]. Based on the antenna port table such as Table AU-8 in Figure 6, the value of the antenna port field notifies the UE of the index of one or more DMRS ports, the number of preceding DMRS symbols, and the number of DMRS CDM group(s) without data. The UE counts the number of REs based on the notified information.

[0040] For DCI formats that schedule PUSCH, the following [Antenna Port] tables are specified, which show the association between the value of the antenna port field, the number of DMRS CDM groups without data, the DMRS port number, and the [number of preceding symbols].

[0041] ◆Table AU-6: Case where both dmrs-UplinkTransformPrecoding and tp-pi2BPSK are configured, and the transform precoder is enabled, and DMRS type (dmrs-Type) = 1, and DMRS maximum length (maxLength) = 1, except that π / 2 BPSK modulation is used. ◆Table AU-6A: Case where the transform precoder is enabled, and both dmrs-UplinkTransformPrecoding and tp-pi2BPSK are configured, and π / 2 BPSK modulation is used, and DMRS type (dmrs-Type) = 1, and DMRS maximum length (maxLength) = 1. ◆Table AU-7: Case where both dmrs-UplinkTransformPrecoding and tp-pi2BPSK are configured, and the transform precoder is enabled, and DMRS type (dmrs-Type) = 1, and DMRS maximum length (maxLength) = 2, except that π / 2 BPSK modulation is used. ◆Table AU-7A: Case where the transform precoder is enabled, and both dmrs-UplinkTransformPrecoding and tp-pi2BPSK are configured, and π / 2 BPSK modulation is used, and DMRS type (dmrs-Type) = 1, and DMRS maximum length (maxLength) = 2.

[0042] ◆Table AU-8: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 1, and the extended DMRS type (dmrs-TypeEnh) is not set, and the DMRS maximum length (maxLength) = 1, and rank = 1. ◆Table AU-9: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 1, and the extended DMRS type (dmrs-TypeEnh) is not set, and the DMRS maximum length (maxLength) = 1, and rank = 2. ◆Table AU-10: Case where the transform precoder is disabled, and multipanelSchemeSDM is not set, and DMRS type (dmrs-Type) = 1, and extended DMRS type (dmrs-TypeEnh) is not set, and DMRS maximum length (maxLength) = 1, and rank = 3. ◆Table AU-10A: Case where the transform precoder is disabled, and multipanelSchemeSDM is set, and DMRS type (dmrs-Type) = 1, and extended DMRS type (dmrs-TypeEnh) is not set, and DMRS maximum length (maxLength) = 1, and rank = 3. ◆Table AU-11: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 1, and the extended DMRS type (dmrs-TypeEnh) is not set, and the DMRS maximum length (maxLength) = 1, and rank = 3.

[0043] ◆Table AU-12: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 1, and the extended DMRS type (dmrs-TypeEnh) is not set, and the DMRS maximum length (maxLength) = 2, and rank = 1. ◆Table AU-13: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 1, and the extended DMRS type (dmrs-TypeEnh) is not set, and the DMRS maximum length (maxLength) = 2, and rank = 2. ◆Table AU-14: Case where the transform precoder is disabled, and multipanelSchemeSDM is not set, and DMRS type (dmrs-Type) = 1, and extended DMRS type (dmrs-TypeEnh) is not set, and DMRS maximum length (maxLength) = 2, and rank = 3. ◆Table AU-14A: Case where the transform precoder is disabled, and multipanelSchemeSDM is set, and DMRS type (dmrs-Type) = 1, and extended DMRS type (dmrs-TypeEnh) is not set, and DMRS maximum length (maxLength) = 2, and rank = 3. ◆Table AU-15: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 1, and the extended DMRS type (dmrs-TypeEnh) is not set, and the DMRS maximum length (maxLength) = 2, and rank = 4. ◆Table AU-15A: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 1, and the extended DMRS type (dmrs-TypeEnh) is not set, and the DMRS maximum length (maxLength) = 2, and rank = 5. ◆Table AU-15B: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 1, and the extended DMRS type (dmrs-TypeEnh) is not set, and the DMRS maximum length (maxLength) = 2, and rank = 6. ◆Table AU-15C: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 1, and the extended DMRS type (dmrs-TypeEnh) is not set, and the DMRS maximum length (maxLength) = 2, and rank = 7. ◆Table AU-15D: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 1, and the extended DMRS type (dmrs-TypeEnh) is not set, and the DMRS maximum length (maxLength) = 2, and rank = 8.

[0044] ◆Table AU-16: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 2, and the extended DMRS type (dmrs-TypeEnh) is not set, and the DMRS maximum length (maxLength) = 1, and rank = 1. ◆Table AU-17: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 2, and the extended DMRS type (dmrs-TypeEnh) is not set, and the DMRS maximum length (maxLength) = 1, and rank = 2. ◆Table AU-18: Case where the transform precoder is disabled, and multipanelSchemeSDM is not set, and DMRS type (dmrs-Type) = 2, and extended DMRS type (dmrs-TypeEnh) is not set, and DMRS maximum length (maxLength) = 1, and rank = 3. ◆Table AU-18A: Case where the transform precoder is disabled, and multipanelSchemeSDM is set, and DMRS type (dmrs-Type) = 2, and extended DMRS type (dmrs-TypeEnh) is not set, and DMRS maximum length (maxLength) = 1, and rank = 3. ◆Table AU-19: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 2, and the extended DMRS type (dmrs-TypeEnh) is not set, and the DMRS maximum length (maxLength) = 1, and rank = 4. ◆Table AU-19A: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 2, and the extended DMRS type (dmrs-TypeEnh) is not set, and the DMRS maximum length (maxLength) = 1, and rank = 5. ◆Table AU-19B: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 2, and the extended DMRS type (dmrs-TypeEnh) is not set, and the DMRS maximum length (maxLength) = 1, and rank = 6.

[0045] ◆Table AU-20: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 2, and the extended DMRS type (dmrs-TypeEnh) is not set, and the DMRS maximum length (maxLength) = 2, and rank = 1. ◆Table AU-21: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 2, and the extended DMRS type (dmrs-TypeEnh) is not set, and the DMRS maximum length (maxLength) = 2, and rank = 2. ◆Table AU-22: Case where the transform precoder is disabled, and multipanelSchemeSDM is not set, and DMRS type (dmrs-Type) = 2, and extended DMRS type (dmrs-TypeEnh) is not set, and DMRS maximum length (maxLength) = 2, and rank = 3. ◆Table AU-22A: Case where the transform precoder is disabled, and multipanelSchemeSDM is set, and DMRS type (dmrs-Type) = 2, and extended DMRS type (dmrs-TypeEnh) is not set, and DMRS maximum length (maxLength) = 2, and rank = 3. ◆Table AU-23: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 2, and the extended DMRS type (dmrs-TypeEnh) is not set, and the DMRS maximum length (maxLength) = 2, and rank = 4. ◆Table AU-23A: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 2, and the extended DMRS type (dmrs-TypeEnh) is not set, and the DMRS maximum length (maxLength) = 2, and rank = 5. ◆Table AU-23B: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 2, and the extended DMRS type (dmrs-TypeEnh) is not set, and the DMRS maximum length (maxLength) = 2, and rank = 6. ◆Table AU-23C: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 2, and the extended DMRS type (dmrs-TypeEnh) is not set, and the DMRS maximum length (maxLength) = 2, and rank = 7. ◆Table AU-23D: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 2, and the extended DMRS type (dmrs-TypeEnh) is not set, and the DMRS maximum length (maxLength) = 2, and rank = 8.

[0046] ◆Table AU-38: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 1, and the extended DMRS type (dmrs-TypeEnh) is set, and the DMRS maximum length (maxLength) = 1, and rank = 1. ◆Table AU-39: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 1, and the extended DMRS type (dmrs-TypeEnh) is set, and the DMRS maximum length (maxLength) = 1, and rank = 2. ◆Table AU-40: Case where the transform precoder is disabled, and multipanelSchemeSDM is not set, and DMRS type (dmrs-Type) = 1, and extended DMRS type (dmrs-TypeEnh) is not set, and DMRS maximum length (maxLength) = 1, and rank = 3. ◆Table AU-40A: Case where the transform precoder is disabled, and multipanelSchemeSDM is set, and DMRS type (dmrs-Type) = 1, and extended DMRS type (dmrs-TypeEnh) is set, and DMRS maximum length (maxLength) = 1, and rank = 3.

[0047] ◆Table AU-41: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 1, and the extended DMRS type (dmrs-TypeEnh) is set, and the DMRS maximum length (maxLength) = 1, and rank = 4.

[0048] ◆Table AU-42: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 1, and the extended DMRS type (dmrs-TypeEnh) is set, and the DMRS maximum length (maxLength) = 1, and rank = 5.

[0049] ◆Table AU-43: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 1, and the extended DMRS type (dmrs-TypeEnh) is set, and the DMRS maximum length (maxLength) = 1, and rank = 6.

[0050] ◆Table AU-44: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 1, and the extended DMRS type (dmrs-TypeEnh) is set, and the DMRS maximum length (maxLength) = 1, and rank = 7.

[0051] ◆Table AU-45: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 1, and the extended DMRS type (dmrs-TypeEnh) is set, and the DMRS maximum length (maxLength) = 1, and rank = 8.

[0052] ◆Table AU-46: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 1, and the extended DMRS type (dmrs-TypeEnh) is set, and the DMRS maximum length (maxLength) = 2, and rank = 1. ◆Table AU-47: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 1, and the extended DMRS type (dmrs-TypeEnh) is set, and the DMRS maximum length (maxLength) = 2, and rank = 2. ◆Table AU-48: Case where the transform precoder is disabled, and multipanelSchemeSDM is not set, and DMRS type (dmrs-Type) = 1, and extended DMRS type (dmrs-TypeEnh) is set, and DMRS maximum length (maxLength) = 2, and rank = 3. ◆Table AU-48A: Case where the transform precoder is disabled, and multipanelSchemeSDM is set, and DMRS type (dmrs-Type) = 1, and extended DMRS type (dmrs-TypeEnh) is set, and DMRS maximum length (maxLength) = 2, and rank = 3. ◆Table AU-49: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 1, and the extended DMRS type (dmrs-TypeEnh) is set, and the DMRS maximum length (maxLength) = 2, and rank = 4. ◆Table AU-50: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 1, and the extended DMRS type (dmrs-TypeEnh) is set, and the DMRS maximum length (maxLength) = 2, and rank = 5. ◆Table AU-51: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 1, and the extended DMRS type (dmrs-TypeEnh) is set, and the DMRS maximum length (maxLength) = 2, and rank = 6. ◆Table AU-52: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 1, and the extended DMRS type (dmrs-TypeEnh) is set, and the DMRS maximum length (maxLength) = 2, and rank = 7. ◆Table AU-53: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 1, and the extended DMRS type (dmrs-TypeEnh) is set, and the DMRS maximum length (maxLength) = 2, and rank = 8.

[0053] ◆Table AU-54: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 2, and the extended DMRS type (dmrs-TypeEnh) is set, and the DMRS maximum length (maxLength) = 1, and rank = 1. ◆Table AU-55: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 2, and the extended DMRS type (dmrs-TypeEnh) is set, and the DMRS maximum length (maxLength) = 1, and rank = 2. ◆Table AU-56: Case where the transform precoder is disabled, and multipanelSchemeSDM is not set, and DMRS type (dmrs-Type) = 2, and extended DMRS type (dmrs-TypeEnh) is set, and DMRS maximum length (maxLength) = 1, and rank = 3. ◆Table AU-56A: Case where the transform precoder is disabled, and multipanelSchemeSDM is set, and DMRS type (dmrs-Type) = 2, and extended DMRS type (dmrs-TypeEnh) is set, and DMRS maximum length (maxLength) = 1, and rank = 3. ◆Table AU-57: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 2, and the extended DMRS type (dmrs-TypeEnh) is set, and the DMRS maximum length (maxLength) = 1, and rank = 4. ◆Table AU-58: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 2, and the extended DMRS type (dmrs-TypeEnh) is set, and the DMRS maximum length (maxLength) = 1, and rank = 5. ◆Table AU-59: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 2, and the extended DMRS type (dmrs-TypeEnh) is set, and the DMRS maximum length (maxLength) = 1, and rank = 6. ◆Table AU-60: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 2, and the extended DMRS type (dmrs-TypeEnh) is set, and the DMRS maximum length (maxLength) = 1, and rank = 7. ◆Table AU-61: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 2, and the extended DMRS type (dmrs-TypeEnh) is set, and the DMRS maximum length (maxLength) = 1, and rank = 8.

[0054] ◆Table AU-62: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 2, and the extended DMRS type (dmrs-TypeEnh) is set, and the DMRS maximum length (maxLength) = 2, and rank = 1. ◆Table AU-63: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 2, and the extended DMRS type (dmrs-TypeEnh) is set, and the DMRS maximum length (maxLength) = 2, and rank = 2. ◆Table AU-64: Case where the transform precoder is disabled, and multipanelSchemeSDM is not set, and DMRS type (dmrs-Type) = 2, and extended DMRS type (dmrs-TypeEnh) is set, and DMRS maximum length (maxLength) = 2, and rank = 3. ◆Table AU-64A: Case where the transform precoder is disabled, and multipanelSchemeSDM is set, and DMRS type (dmrs-Type) = 2, and extended DMRS type (dmrs-TypeEnh) is set, and DMRS maximum length (maxLength) = 2, and rank = 3. ◆Table AU-65: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 2, and the extended DMRS type (dmrs-TypeEnh) is set, and the DMRS maximum length (maxLength) = 2, and rank = 4. ◆Table AU-66: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 2, and the extended DMRS type (dmrs-TypeEnh) is set, and the DMRS maximum length (maxLength) = 2, and rank = 5. ◆Table AU-67: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 2, and the extended DMRS type (dmrs-TypeEnh) is set, and the DMRS maximum length (maxLength) = 2, and rank = 6. ◆Table AU-68: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 2, and the extended DMRS type (dmrs-TypeEnh) is set, and the DMRS maximum length (maxLength) = 2, and rank = 7. ◆Table AU-69: Case where the transform precoder is disabled, and the DMRS type (dmrs-Type) = 2, and the extended DMRS type (dmrs-TypeEnh) is set, and the DMRS maximum length (maxLength) = 2, and rank = 8.

[0055] (Physical Layer Procedures for Data) ((DMRS Reception Procedure)) In the specification of the physical layer procedures for data, the following steps 1-x are defined for the DMRS reception procedure.

[0056] ◆ Step 1-1: The DMRS reception procedure for a PDSCH scheduled by a PDCCH having DCI format 1_1 is similarly applied to a PDSCH scheduled by a PDCCH having DCI format 1_2, etc. The DMRS reception procedure for a PDSCH scheduled by a PDCCH having DCI format 1_1 is similarly applied to a PDSCH scheduled by a PDCCH having DCI format 1_3, and the DMRS reception procedure for a PDSCH scheduled by a PDCCH having DCI format 1_1 is similarly applied to a PDSCH scheduled by a PDCCH having DCI format 4_2, etc.

[0057] ◆Step 1-2: When receiving a PDSCH scheduled by DCI format 1_1 or 1_3 with a PDCCH having a CRC scrambled by C-RNTI, MCS-C-RNTI, or CS-RNTI, or scheduled by DCI format 4_2 with a PDCCH having a CRC scrambled by G-RNTI or G-CS-RNTI for multicast, the UE may configure the upper layer parameters dmrs-Type / dmrs-TypeEnh, and the configured DMRS configuration type is used to receive the PDSCH.

[0058] The specification of the physical layer procedures for data means that DCI format 1_3 can indicate Rel.18 DMRS for PDSCH reception, and simultaneous configuration of DCI format 1_3 and Rel.18 DMRS is supported.

[0059] (UE DMRS Transmission Procedure) In the specification of the physical layer procedures for data, the following steps 4-x are defined for the UE DMRS transmission procedure.

[0060] ◆ Step 4-1: The DMRS transmission procedure for a PUSCH scheduled by a PDCCH having DCI format 0_1 ​​is similarly applied to a PUSCH scheduled by a PDCCH having DCI format 0_2 by applying the parameters dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2 and dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2 instead of dmrs-UplinkForPUSCH-MappingTypeA and dmrs-UplinkForPUSCH-MappingTypeB. The DMRS transmission procedure for a PUSCH scheduled by a PDCCH having DCI format 0_1 ​​is similarly applied to a PUSCH scheduled by a PDCCH having DCI format 0_3.

[0061] (Multiplexing and Channel Coding) ((DCI format 1_3)) In the multiplexing and channel coding specification, the following steps 2-x are defined for [DCI] format 1_3.

[0062] ◆ Step 2-1: DCI format 1_3 is used for scheduling one PDSCH in one cell or for scheduling multiple PDSCHs in multiple cells with one PDSCH per cell.

[0063] ◆ Step 2-2: The following information is transmitted using DCI format 1_3 with a CRC scrambled by C-RNTI or MCS-C-RNTI.

[0064] -◆Step 2-2-1: Antenna Port [field]. The number of bits is determined by the following:

[0065] --◆Step 2-2-1-1: If antennaPortsDCI-1-3=type1a is set by the upper layer (MC-DCI-SetOfCells-r18 in mc-DCI-SetOfCellsToAddModList-r18 in RRC IE ServingCellConfig), ---The number of bits in the antenna port field is r∈{1,2,...,N cell DL,2}, max(M A (r)) bits, where N cell DL,2 is the number of cells in the scheduled cell set configured by the upper layer parameter scheduledCellListDCI-1-3 (list of scheduled cells), r is mapped to the cells in ascending order of serving cell index, r=1 corresponds to the cell with the smallest serving cell index, and M A (r) is defined as follows.

[0066] --◆Step 2-2-1-2: If antennaPortsDCI-1-3=type2 is set by the upper layer (MC-DCI-SetOfCells-r18), ---The number of bits in the antenna port field is block number 1, block number 2, ..., block number N cell DL , is. Each block corresponds to antenna port information for one cell, and the blocks are arranged in ascending order of serving cell index, with block number 1 corresponding to the antenna port information for the cell with the smallest serving cell index. Each block is defined as follows:

[0067] --◆Step 2-2-1-3: In the case of antennaPortsDCI-1-3=type1a, A(r) or in the case where antennaPortsDCI-1-3=type2, the above blocks are defined as follows: --- As defined by tables AD-1 / 2 / 3 / 4 and AD-1A / 2A / 3A / 4A, M A (r) or each block is 4, 5, or 6 bits, where the values ​​1, 2, and 3 for the number of CDM groups without data correspond to CDM groups {0}, {0,1}, and {0,1,2}, respectively. v-1} is determined according to the order of DMRS ports given by table AD-1 / 2 / 3 / 4 or table AD-1A / 2A / 3A / 4A.

[0068] --◆Step 2-2-1-4: If the UE is configured with both dmrs-DownlinkForPDSCH-MappingTypeA and dmrs-DownlinkForPDSCH-MappingTypeB, the bit width of this [Antenna Port] field is max{x A ,x B} where x A is the bit width of the "antenna port" [field] derived according to dmrs-DownlinkForPDSCH-MappingTypeA, and x B is the bit width of the "antenna port" [field] derived according to dmrs-DownlinkForPDSCH-MappingTypeB. If the PDSCH mapping type is x A and x B If the value corresponds to the smaller of |x, then the most significant bit (MSB) of this field contains |x A -x B The number of |'s is padded with zeros.

[0069] mc-DCI-SetOfCellsToAddModList is a list of up to N (N≦4) configurations of sets of cells for multi-cell PDSCH / PUSCH scheduling from its serving cell, where N is reported as UE capability, and up to four sets of cells can be configured per PUCCH group. If this field is set to an SCell, the PCell cannot be included in either ScheduledCellListDCI-1-3 or ScheduledCellListDCI-0-3.

[0070] In the multiplexing and channel coding specifications, DCI format 1_3 does not support scheduling of Rel.18 DMRS because it cannot indicate an antenna port table for Rel.18 DMRS, such as table AD-7 / 8 / 9 / 10.

[0071] ((DCI format 4_2)) In the multiplexing and channel coding specification, the following steps 3-x are defined for [DCI] format 4_2.

[0072] ◆ Step 3-1: DCI format 4_2 is used for scheduling PDSCH for multicast within a DL cell.

[0073] ◆Step 3-2: The following information is transmitted using DCI format 4_2 with a CRC scrambled by the G-RNTI for multicast or by the G-CS-RNTI set by MBS-RNTI-SpecificConfig.

[0074] -◆Step 3-2-1: Antenna Port [field]. The number of bits is determined by the following:

[0075] Step 3-2-1-1: The antenna port [field] is 4, 5, or 6 bits as defined by Table AD-1 / 2 / 3 / 4. Here, the values ​​1, 2, and 3 for the number of CDM groups without data correspond to CDM groups {0}, {0,1}, and {0,1,2}, respectively. The antenna ports {p0,...,p v-1} is determined according to the order of the DMRS ports given by Table AD-1 / 2 / 3 / 4.

[0076] --◆Step 3-2-1-2: If the UE is configured with both dmrs-DownlinkForPDSCH-MappingTypeA and dmrs-DownlinkForPDSCH-MappingTypeB, the bit width of this [Antenna Port] field is max{x A ,x B} where x A is the bit width of the "antenna port" [field] derived according to dmrs-DownlinkForPDSCH-MappingTypeA, and x B is the bit width of the "antenna port" [field] derived according to dmrs-DownlinkForPDSCH-MappingTypeB. If the PDSCH mapping type is x A and x B If the value corresponds to the smaller of |x, then the most significant bit (MSB) of this field contains |x A -x B The number of |'s is padded with zeros.

[0077] ((DCI format 0_1)) In the multiplexing and channel coding specification, the following steps 5-x are defined for [DCI] format 0_1.

[0078] ◆ Step 5-1: DCI format 0_1 ​​is used for scheduling PUSCH within one cell or for indicating configured grant (CG) DL feedback information (CG-DFI) to the UE.

[0079] ◆ Step 5-2: The following information is transmitted using DCI format 0_1 ​​with a CRC scrambled by C-RNTI or CS-RNTI or SP-CSI-RNTI or MCS-C-RNTI.

[0080] -◆Step 5-2-1: Antenna Port [field]. The number of bits is determined by the following:

[0081] ---◆Step 5-2-1-3-1: If the transform precoder is enabled and dmrs-Type=1 and maxLength=1, the antenna port [field] is 2 bits as defined in Table AU-6, unless both dmrs-UplinkTransformPrecoding and tp-pi2BPSK are set and π / 2 BPSK modulation is used.

[0082] ---◆ Step 5-2-1-3-2: If the transform precoder is enabled, and both dmrs-UplinkTransformPrecoding and tp-pi2BPSK are configured, and π / 2 BPSK modulation is used, and dmrs-Type=1, and maxLength=1, then the antenna port [field] is 2 bits as defined in Table AU-6A, where n SCID is the scrambling identity for the antenna port as defined in the physical channel and modulation specification.

[0083] ---◆Step 5-2-1-3-3: If the transform precoder is enabled and dmrs-Type=1 and maxLength=2, the antenna port [field] is 4 bits as defined in Table AU-7, except when both dmrs-UplinkTransformPrecoding and tp-pi2BPSK are set and π / 2 BPSK modulation is used.

[0084] ---◆ Step 5-2-1-3-4: If the transform precoder is enabled, and both dmrs-UplinkTransformPrecoding and tp-pi2BPSK are configured, and π / 2 BPSK modulation is used, and dmrs-Type=1, and maxLength=2, then the antenna port [field] is 4 bits as defined in Table AU-7A, where n SCID is the scrambling identity for the antenna port as defined in the physical channel and modulation specification.

[0085] ---◆Step 5-2-1-3-5: If the transform precoder is disabled, and dmrs-Type=1, and dmrs-TypeEnh is not set, and maxLength=1, the antenna port [field] is 3 bits as defined in table AU-8 / 9 / 10 / 10A / 11 according to the rank value.

[0086] ---◆Step 5-2-1-3-6: If the transform precoder is disabled, and dmrs-Type=1, and dmrs-TypeEnh is not set, and maxLength=2, the antenna port [field] is 4 bits as defined in table AU-12 / 13 / 14 / 14A / 15 / 15A / 15B / 15C / 15D according to the rank value.

[0087] ---◆Step 5-2-1-3-7: If the transform precoder is disabled, and dmrs-Type=2, and dmrs-TypeEnh is not set, and maxLength=1, the antenna port [field] is 4 bits as defined in table AU-16 / 17 / 18 / 18A / 19 / 19A / 19B according to the rank value.

[0088] ---◆Step 5-2-1-3-8: If the transform precoder is disabled and dmrs-Type=2 and dmrs-TypeEnh is not set and maxLength=2, the antenna port [field] is 5 bits as defined in table AU-20 / 21 / 22 / 22A / 23 / 23A / 23B / 23C / 23D according to the rank value.

[0089] ---◆Step 5-2-1-3-9: If the transform precoder is disabled, and dmrs-Type=1, and dmrs-TypeEnh is set, and maxLength=1, the antenna port [field] is 4 bits as defined in table AU-38 / 39 / 40 / 40A / 41 / 42 / 43 / 44 / 45 according to the rank value.

[0090] ---◆Step 5-2-1-3-10: If the transform precoder is disabled, and dmrs-Type=1, and dmrs-TypeEnh is set, and maxLength=2, the antenna port [field] is 5 bits as defined in table AU-46 / 47 / 48 / 48A / 49 / 50 / 51 / 52 / 53 according to the rank value.

[0091] ---◆Step 5-2-1-3-11: If the transform precoder is disabled, and dmrs-Type=2, and dmrs-TypeEnh is set, and maxLength=1, the antenna port [field] is 5 bits as defined in table AU-54 / 55 / 56 / 56A / 57 / 58 / 59 / 60 / 61 according to the rank value.

[0092] ---◆Step 5-2-1-3-12: If the transform precoder is disabled, and dmrs-Type=2, and dmrs-TypeEnh is set, and maxLength=2, the antenna port [field] is 6 bits as defined in table AU-62 / 63 / 64 / 64A / 65 / 66 / 67 / 68 / 69 according to the rank value.

[0093] -◆Step 5-2-2: Here, the values ​​1, 2, and 3 of the number of CDM groups without data in tables AD-1 / 2 / 3 / 4 or tables AU-6 to AU-23 refer to CDM groups {0}, {0,1}, and {0,1,2}, respectively. The rank values ​​are as follows:

[0094] --◆Step 5-2-2-1: If txConfig=nonCodebook, and multipanelSchemeSDM is set, and the SRS resource set indicator field is equal to "10", the rank value is the sum of the value determined according to the SRS resource set indicator field and the value determined according to the second SRS resource set indicator field.

[0095] --◆Step 5-2-2-2: If txConfig=Codebook and multipanelSchemeSDM is set and the SRS resource set indicator field is equal to "10", the rank value is the sum of the value determined according to the precoding information and layer number fields and the value determined according to the second SRS resource set indicator field.

[0096] --◆Step 5-2-2-3: If txConfig=nonCodebook and multipanelSchemeSDM is not set, or if txConfig=nonCodebook and multipanelSchemeSDM is set and the SRS resource set indicator field is equal to "00" or "01", or the rank value is determined according to the SRS resource set indicator field.

[0097] --◆Step 5-2-2-4: If txConfig=Codebook and multipanelSchemeSDM is not set, or if txConfig=Codebook and multipanelSchemeSDM is not set and the SRS resource set indicator field is equal to "00" or "01", the rank value is determined according to the precoding information and number of layers fields.

[0098] -◆Step 5-2-3: If the UE is configured with both dmrs-UplinkForPUSCH-MappingTypeA and dmrs-UplinkForPUSCH-MappingTypeB, the bit width of this [Antenna Port] field is max{x A ,x B} where x A is the bit width of the "antenna port" [field] derived according to dmrs-UplinkForPUSCH-MappingTypeA, and x B is the bit width of the "antenna port" [field] derived according to dmrs-UplinkForPUSCH-MappingTypeB. If the PDSCH mapping type is x A and x B If the value corresponds to the smaller of |x, then the most significant bit (MSB) of this field contains |x A -x B The number of |'s is padded with zeros.

[0099] -◆Step 5-2-4: When a transform precoder field is present, if the bit width of the antenna port field for the case where the transform precoder is enabled is not equal to the bit width of the antenna port field for the case where the transform precoder is disabled, then some MSBs with values ​​set to '0' are inserted into the antenna port field for the case with the smaller bit width until the bit widths of the antenna port fields for the two cases are the same.

[0100] ((DCI format 0_2)) In the multiplexing and channel coding specification, the following steps 6-x are defined for [DCI] format 0_2.

[0101] ◆Step 6-1: DCI format 0_2 is used for scheduling PUSCH within one cell.

[0102] ◆ Step 6-2: The following information is transmitted using DCI format 0_2 with a CRC scrambled by C-RNTI or CS-RNTI or SP-CSI-RNTI or MCS-C-RNTI.

[0103] -◆Step 6-2-1: Antenna Port [field]. The number of bits is determined by the following:

[0104] --◆Step 6-2-1-1: If the upper layer parameter antennaPortsFieldPresenceDCI-0-2 is not set, the antenna port [field] is 0 bit.

[0105] --◆Step 6-2-1-2: Otherwise, as in steps 5-2-1-1 to 5-2-1-12, the antenna port [field] is 2, 3, 4, 5, or 6 bits.

[0106] -◆Steps 6-2-2 to 6-2-4: Same as steps 5-2-2 to 5-2-4.

[0107] ((DCI format 0_3)) In the multiplexing and channel coding specification, the following steps 7-x are defined for [DCI] format 0_3.

[0108] ◆ Step 7-1: DCI format 0_3 is used for scheduling one PUSCH in one cell or for scheduling multiple PUSCHs in multiple cells with one PUSCH per cell.

[0109] ◆ Step 7-2: The following information is transmitted using DCI format 0_3 with a CRC scrambled by C-RNTI or MCS-C-RNTI.

[0110] -◆Step 7-2-1: Antenna Port [field]. The number of bits is determined by the following:

[0111] --◆Step 7-2-1-1: If antennaPortsDCI0-3=type1a is set by the upper layer (MC-DCI-SetOfCells-r18 in mc-DCI-SetOfCellsToAddModList-r18 in RRC IE ServingCellConfig), ---The number of bits in the antenna port field is r∈{1,2,...,N cell UL,2}, max(M A (r)) bits, where [N cell UL,2 is the number of cells in the scheduled cell set configured by the higher layer parameter scheduledCellListDCI-0-3 (list of scheduled cells), r is mapped to the cells in ascending order of serving cell index, r=1 corresponds to the cell with the smallest serving cell index, and M A (r) is defined as follows.

[0112] --◆Step 7-2-1-2: If antennaPortsDCI0-3=type2 is set by the upper layer (MC-DCI-SetOfCells-r18), ---The number of bits in the antenna port field is block number 1, block number 2, ..., block number N cell UL , is. Each block corresponds to antenna port information for one cell, and the blocks are arranged in ascending order of serving cell index, with block number 1 corresponding to the antenna port information for the cell with the smallest serving cell index. Each block is defined as follows:

[0113] --◆ Procedure 7-2-1-3: In the case of antennaPortsDCI0-3=type1a, A (r) or in the case where antennaPortsDCI0-3=type2, the above-mentioned blocks are defined as follows:

[0114] ---◆ Step 7-2-1-3-1: If the transform precoder is enabled, and dmrs-Type=1, and maxLength=1, M A (r) or each block is 2 bits as defined in Table AU-6.

[0115] ---◆ Step 7-2-1-3-2: If the transform precoder is enabled, and both dmrs-UplinkTransformPrecoding and tp-pi2BPSK are configured, and π / 2 BPSK modulation is used, and dmrs-Type=1, and maxLength=1, then M A (r) or each block is 2 bits as defined in Table AU-6A, where n SCID is the scrambling identity for the antenna port as defined in the physical channel and modulation specification.

[0116] ---◆ Step 7-2-1-3-3: If the transform precoder is enabled, and dmrs-Type=1, and maxLength=2, M A (r) or each block is 4 bits as defined in Table AU-7.

[0117] ---◆ Step 7-2-1-3-4: If the transform precoder is enabled, and both dmrs-UplinkTransformPrecoding and tp-pi2BPSK are configured, and π / 2 BPSK modulation is used, and dmrs-Type=1, and maxLength=2, then M A (r) or each block is 4 bits as defined in Table AU-7A, where n SCID is the scrambling identity for the antenna port as defined in the physical channel and modulation specification.

[0118] ---◆ Step 7-2-1-3-5: If the transform precoder is disabled, and dmrs-Type=1, and maxLength=1, and the rank value is determined according to the SRS resource set indicator field when the upper layer parameter txConfig=nonCodebook, or according to the precoding information and number of layers field when the upper layer parameter txConfig=codebook, then M A (r) or each block is 3 bits as defined in table AU-8 / 9 / 10 / 10A / 11 according to the value of the rank.

[0119] ---◆ Step 7-2-1-3-6: If the transform precoder is disabled, and dmrs-Type=1, and maxLength=2, and the rank value is determined according to the SRS resource set indicator field when the upper layer parameter txConfig=nonCodebook, or according to the precoding information and number of layers field when the upper layer parameter txConfig=codebook, then M A (r) or each block is 4 bits as defined in table AU-12 / 13 / 14 / 14A / 15 / 15A / 15B / 15C / 15D according to the value of rank.

[0120] ---◆ Step 7-2-1-3-7: If the transform precoder is disabled, and dmrs-Type=2, and maxLength=1, and the rank value is determined according to the SRS resource set indicator field when the upper layer parameter txConfig=nonCodebook, or according to the precoding information and number of layers field when the upper layer parameter txConfig=codebook, then M A (r) or each block is 4 bits as defined in table AU-16 / 17 / 18 / 18A / 19 / 19A / 19B according to the value of rank.

[0121] ---◆ Step 7-2-1-3-8: If the transform precoder is disabled, and dmrs-Type=2, and maxLength=2, and the rank value is determined according to the SRS resource set indicator field when the upper layer parameter txConfig=nonCodebook, or according to the precoding information and number of layers field when the upper layer parameter txConfig=codebook, then M A (r) or each block is 5 bits as defined in table AU-20 / 21 / 22 / 22A / 23 / 23A / 23B / 23C / 23D according to the value of rank.

[0122] -◆Step 7-2-2: Here, the values ​​1, 2 and 3 of the number of CDM groups without data in tables AD-1 / 2 / 3 / 4 or tables AU-6 to AU-23 refer to CDM groups {0}, {0,1} and {0,1,2}, respectively.

[0123] -◆ Step 7-2-3: If the UE is configured with both dmrs-UplinkForPUSCH-MappingTypeA and dmrs-UplinkForPUSCH-MappingTypeB, the bit width of this [Antenna Port] field is max{x A ,x B} where x A is the bit width of the "antenna port" [field] derived according to dmrs-UplinkForPUSCH-MappingTypeA, and x B is the bit width of the "antenna port" [field] derived according to dmrs-UplinkForPUSCH-MappingTypeB. If the PDSCH mapping type is x A and x B If the value corresponds to the smaller of |x, then the most significant bit (MSB) of this field contains |x A -x B The number of |'s is padded with zeros.

[0124] In the specification for data physical layer procedures, DCI format 0_3 can schedule multi-carrier PUSCH using Rel.18 DMRS ports, but in the specification for multiplexing and channel coding, DCI format 0_3 does not support Rel.18 DMRS ports.

[0125] (multicast) As shown in the example of Figure 7, after a random access (RA) procedure, the UE may receive a common frequency resource (CFR) [multicast] configuration and a PUCCH configuration [via a UE-specific RRC message]. The CFR configuration may include at least one of a CFR location and bandwidth (locationAndBandwidth), a PDCCH configuration, a PDSCH configuration, and an SPS configuration. The UE may then receive multicast traffic [scheduled using DCI format 4_1 / 4_2 with CRC scrambled by G-RNTI / G-CS-RNTI]. The UE may then send a HARQ-ACK for the multicast traffic.

[0126] (RRC protocol) The DL DMRS configuration (DMRS-DownlinkConfig) may include an extended DMRS type configuration (dmrsTypeEnh) to enable Rel. 18 DMRS for PDSCH.

[0127] DMRS-DownlinkConfig is configured in the PDSCH configuration (PDSCH-Config) in the DL BWP dedicated configuration (BWP-DownlinkDedicated). PDSCH-Config may include separate parameters for DCI formats 1_1 and 1_2 (dmrs-DownlinkForPDSCH-MappingTypeA / dmrs-DownlinkForPDSCH-MappingTypeB for DCI format 1_1 and dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2-r16 / dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2-r16 for DCI format 1_2). Therefore, it is possible that Rel.18 DMRS is configured for DCI format 1_1 and Rel.18 DMRS is not configured for DCI format 1_2.

[0128] Although the PDSCH configuration for DCI format 1_3 (pdsch-ConfigDCI-1-3-r18) can be configured in the PDSCH-Config, there is no DMRS-Downlink-Config configuration specific to DCI format 1_3. This means that DCI format 1_3 reuses the DMRS-Downlink-Config in the PDSCH-Config for DCI format 1_1. In other words, one RRC parameter enables the Rel. 18 DMRS port for the PDSCH scheduled by DCI formats 1_1 / 1_3.

[0129] For DCI format 4_2, PDSCH-Config is configured in the multicast PDSCH configuration (pdsch-ConfigMulticast-r17) in the CFR multicast configuration (CFR-ConfigMulticast-r17) in BWP-DownlinkDedicated. pdsch-ConfigMulticast is a UE-specific configuration of a group-common PDSCH for multicast / broadcast service (MBS) multicast for one CFR. This PDSCH-Config is an RRC parameter separate from the PDSCH-Config for DCI formats 1_1 / 1_2 / 1_3 and is an individual RRC parameter for DCI format 4_2.

[0130] That is, the following RRC parameters for PDSCH may enable Rel. 18 DMRS ports for PDSCH that are scheduled by the corresponding DCI format: ◆For DCI format 1_1 / 1_3, dmrs-TypeEnh in dmrs-DownlinkForPDSCH-MappingTypeA or dmrs-DownlinkForPDSCH-MappingTypeB (DMRS-DownlinkConfig) in PDSCH-Config in BWP-DownlinkDedicated. ◆For DCI format 1_2, dmrs-TypeEnh in dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2-r16 or dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2-r16 (DMRS-DownlinkConfig) in PDSCH-Config in BWP-DownlinkDedicated. ◆For DCI format 4_2, dmrs-DownlinkForPDSCH-MappingTypeA in pdsch-ConfigMulticast-r17(PDSCH-Config) in CFR-ConfigMulticast-r17 in BWP-DownlinkDedicated or dmrs-TypeEnh in dmrs-DownlinkForPDSCH-MappingTypeB(DMRS-DownlinkConfig).

[0131] Similarly, the following RRC parameters for PUSCH may enable Rel. 18 DMRS ports for PUSCH that are scheduled by the corresponding DCI format: ◆For DCI format 0_1 / 0_3, dmrs-TypeEnh in dmrs-UplinkForPUSCH-MappingTypeA or dmrs-UplinkForPUSCH-MappingTypeB (DMRS-UplinkConfig) in PUSCH-Config in BWP-UplinkDedicated. ◆For DCI format 0_2, dmrs-TypeEnh in dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2-r16 or dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2-r16 (DMRS-UplinkConfig) in PUSCH-Config in BWP-UplinkDedicated.

[0132] (UE ability) A UE capability of complexity regarding the maximum number of DMRS types configured for PDSCH across all DL DCI formats per cell may be reported by the UE. The UE capability component may include the maximum number of DMRS types configured for PDSCH across all DL DCI formats per cell. Candidate values ​​for this component may be {2, 3, 4}. If this UE capability is not reported, the maximum number of DMRS types configured for PDSCH across all DL DCI formats per cell is defined as the total number of different DMRS types reported.

[0133] (Issues) The interoperability between DCI formats 1_3 / 4_2 / 0_3 and Rel.18 DMRS has not been fully considered and is not fully defined in the specifications.

[0134] When Rel.18 DMRS is enabled or configured, UE complexity may increase in terms of enhanced DMRS channel estimation for processing the four new FD-OCC patterns. For example, associated parameter estimation may be required. In multi-carrier scheduling, the UE needs to process multiple PDSCHs from multiple scheduled cells. Therefore, simultaneous configuration of DCI format 1_3 and Rel.18 DMRS results in higher implementation complexity and higher UE processing capabilities. Because the Rel.18 DMRS feature is enabled through higher layer signaling, the corresponding processing resources are prepared based on the configuration. Similarly, PDCCH processing (e.g., CCE limit counting) for Rel.18 single DCI is performed based on the feature enablement / configuration. Therefore, regardless of whether dynamic scheduling for DCI format 1_1 or DCI format 1_3 is used, when both Rel.18 DMRS and Rel.18 single DCI features are configured by RRC, the corresponding processing resources are affected by both features. Simultaneous configuration of both Rel.18 DMRS and Rel.18 single DCI may incur additional preparation / processing in the UE implementation.

[0135] To solve this problem, a new UE capability is being considered to support simultaneous configuration of Rel.18 DMRS and Rel.18 single DCI. If the UE does not report this capability, and DCI format 1_3 is configured on the scheduling cell, neither the scheduling cell nor the scheduled cell can configure dmrs-TypeEnh with the value 'enabled'. As a result, DCI format 1_1 cannot indicate Rel.18 DMRS for the scheduled cell. Considering the flexibility of configuration and scheduling, the reporting granularity of the new capability is FeatureSet.

[0136] Thus, unless the functionality using Rel. 18 DMRS is thoroughly considered and defined, there is a risk that the UE will not be able to properly receive the PDSCH [DMRS].

[0137] Therefore, the present inventors have studied scheduling methods for PDSCH [DMRS] and have come up with the following embodiments.

[0138] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. Wireless communication methods according to the embodiments may be applied independently or in combination.

[0139] (Various reading changes) In this disclosure, words enclosed in "()" in a sentence may indicate an explanation of the immediately preceding wording (for example, an explanation of spelling), a paraphrase, a specific example, a supplementary explanation, etc. Also, in this disclosure, words enclosed in "[ ]" in a sentence may be interpreted including the meaning of the entire sentence, or may be interpreted excluding the meaning of the entire sentence (ignoring the meaning of the entire sentence). Note that "()" and "[ ]" may also be used for purposes / meanings other than those mentioned above.

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

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

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

[0143] In the present disclosure, the higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, other messages (e.g., messages from the core network such as positioning protocol (e.g., NR Positioning Protocol A (NRPPa) / LTE Positioning Protocol (LPP)) messages), or a combination thereof.

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

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

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

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

[0148] In the present disclosure, FR may be, for example, at least one of FR1, FR2, FR2-1, FR2-2, FR3, sub-terahertz, and terahertz. In the present disclosure, the frequency range corresponding to FR1 may be 410-7125 MHz. In the present disclosure, FR2 may include FR2-1 and FR2-2, and the frequency range corresponding to FR2-1 may be 24250-52600 MHz, and the frequency range corresponding to FR2-1 may be 52600-71000 MHz.

[0149] The following abbreviations may be used in this disclosure: ◆FDM: frequency division multiplexing ◆TDM: time division multiplexing ◆CDM:code division multiplexing

[0150] In the present disclosure, the terms indicate, report, and select may be read interchangeably.

[0151] In the present disclosure, antenna port, DMRS port, antenna port index (number) 1000+x, and DMRS port index (number) x may be read as interchangeable.

[0152] (Wireless communication method) The UE may receive a DMRS configuration (e.g., DMRS-DownlinkConfig / DMRS-UplinkConfig). The UE may receive DCI format [1_3] for scheduling one PDSCH in one cell or multiple PDSCHs in multiple cells with one PDSCH per cell. The UE may receive DCI format [4_2] for scheduling a PDSCH for multicast in a DL cell. The UE may receive DCI format [0_3] for scheduling one PUSCH in one cell or multiple PUSCHs in multiple cells with one PUSCH per cell.

[0153] The UE may determine, based on the configuration and the DCI format, whether a length-4 FD-OCC (e.g., extended DMRS type, Rel. 18 DMRS, Rel. 18 DMRS port) is applied to the DMRS for the multiple PDSCHs.

[0154] <Embodiment 1> The multiplexing and channel coding specifications mentioned above may be updated to support that DCI format 1_3 can schedule PDSCH using Rel.18 DMRS ports (FD-OCC of length 4).

[0155] In the above multiplexing and channel coding specifications, the following procedure 2-2-1-3A may be specified instead of procedure 2-2-1-3.

[0156] --◆ Procedure 2-2-1-3A: antennaPortsDCI-1-3 = type1a in the case of the above M A (r) or in the case where antennaPortsDCI-1-3=type2, the above blocks are defined as follows: --- As defined by tables AD-1 / 2 / 3 / 4 / 7 / 8 / 9 / 10 and AD-1A / 2A / 3A / 4A / 7A / 8A / 9A / 10A, MA (r) or each block is 4, 5, 6, 7, or 8 bits, where the values ​​1, 2, and 3 for the number of CDM groups without data correspond to CDM groups {0}, {0,1}, and {0,1,2}, respectively. v-1} is determined according to the order of DMRS ports given by table AD-1 / 2 / 3 / 4 / 7 / 8 / 9 / 10 or table AD-1A / 2A / 3A / 4A / 7A / 8A / 9A / 10A.

[0157] 8 and 9 show an example of an antenna port table (AD-7) for PDSCH when the extended DMRS type (dmrs-TypeEnh) is set.

[0158] In embodiment 1, no new UE capability may be introduced (or required) to support simultaneous configuration of Rel.18 DMRS and Rel.18 single DCI [as described above] [for DCI format 1_3].

[0159] In embodiment 1, DCI format 1_3 supports Rel.18 DMRS, and DCI format 1_3 and Rel.18 DMRS can be configured by the same RRC parameter (dmrs-TypeEnh in dmrs-DownlinkForPDSCH-MappingTypeA or dmrs-DownlinkForPDSCH-MappingTypeB) as DCI format 1_1 and Rel.18 DMRS, and no new UE capability for simultaneous configuration of Rel.18 DMRS and Rel.18 single DCI [for DCI format 1_3] may be required.

[0160] <<Variations>> In embodiment 1, simultaneous configuration of both Rel.18 DMRS and Rel.18 single DCI may increase the complexity / processing power of the UE, and new UE capabilities may be introduced (or required) to support simultaneous configuration of Rel.18 DMRS and Rel.18 single DCI [as described above] [for DCI format 1_3] or a combination of Rel.18 DMRS and Rel.18 single DCI [for DCI format 1_3].

[0161] <<Variations>> In embodiment 1, the UE may assume that dmrs-TypeEnh is not set [for PDSCHs scheduled by DCI format 1_3], or may not expect that dmrs-TypeEnh is set [for PDSCHs scheduled by DCI format 1_3].

[0162] <Embodiment 2> The aforementioned specification of the physical layer procedures for data may be updated to exclude that DCI format 1_3 can schedule PDSCH using Rel. 18 DMRS ports (FD-OCC of length 4).

[0163] In the above-mentioned specification of the data physical layer procedure, at least one of the following procedures 1-1A and 1-2A may be defined instead of procedures 1-1 and 1-2.

[0164] ◆ Step 1-1A: The DMRS reception procedure for a PDSCH scheduled by a PDCCH having DCI format 1_1 applies in the same way to a PDSCH scheduled by a PDCCH having DCI format 1_2, etc. The DMRS reception procedure for a PDSCH scheduled by a PDCCH having DCI format 1_1 applies in the same way to a PDSCH scheduled by a PDCCH having DCI format 1_3, except for the setting of dmrs-TypeEnh (when the higher layer parameter dmrs-TypeEnh is set). When receiving a PDSCH scheduled by a PDCCH having DCI format 1_3, the UE ignores dmrs-TypeEnh. The DMRS reception procedure for a PDSCH scheduled by a PDCCH having DCI format 1_1 applies in the same way to a PDSCH scheduled by a PDCCH having DCI format 4_2, etc.

[0165] ◆Step 1-2A: When receiving a PDSCH scheduled by DCI format 1_1 with a PDCCH having a CRC scrambled by C-RNTI, MCS-C-RNTI, or CS-RNTI, or scheduled by DCI format 4_2 with a PDCCH having a CRC scrambled by G-RNTI or G-CS-RNTI for multicast, the UE may configure the upper layer parameters dmrs-Type / dmrs-TypeEnh, and the configured DMRS configuration type is used to receive the PDSCH.

[0166] In embodiment 2, simultaneous configuration of both Rel.18 DMRS and Rel.18 single DCI may increase the complexity / processing capability of the UE, and new UE capabilities may be introduced (or may be required) to support simultaneous configuration of Rel.18 DMRS and Rel.18 single DCI [as described above] [for DCI format 1_3].

[0167] In embodiment 2, DCI format 1_3 does not support Rel.18 DMRS, and new UE capabilities for simultaneous configuration of Rel.18 DMRS and Rel.18 single DCI [as described above] [for DCI format 1_3] may be required.

[0168] <<Variations>>

[0169] "Ignore dmrs-TypeEnh" in step 1-1A may be replaced with "assume dmrs-TypeEnh is not set" or "do not expect dmrs-TypeEnh to be set."

[0170] <<Variations>> In embodiment 2, no new UE capability may be introduced (or required) to support simultaneous configuration of Rel.18 DMRS and Rel.18 single DCI [as described above] [for DCI formats 1_3].

[0171] <Embodiment 3> The multiplexing and channel coding specifications mentioned above may be updated to support that DCI format 4_2 can schedule PDSCH using Rel.18 DMRS ports (FD-OCC of length 4).

[0172] In the above-mentioned multiplexing and channel coding specifications, the following procedure 3-2-1-1A may be specified instead of procedure 3-2-1-1.

[0173] --◆Step 3-2-1-1A: The antenna port [field] is 4, 5, 6, 7, or 8 bits as defined by Table AD-1 / 2 / 3 / 4 / 7 / 8 / 9 / 10. Here, the values ​​1, 2, and 3 for the number of CDM groups without data correspond to CDM groups {0}, {0,1}, and {0,1,2}, respectively. The antenna ports {p0,...,p v-1} is determined according to the order of DMRS ports given by Table AD-1 / 2 / 3 / 4 / 7 / 8 / 9 / 10.

[0174] In embodiment 3, a new UE capability for supporting simultaneous configuration of Rel.18 DMRS and Rel.18 single DCI for DCI format 4_2 may not be introduced (may not be required).

[0175] In embodiment 1, DCI format 4_2 supports Rel.18 DMRS, and DCI format 4_2 and Rel.18 DMRS can be configured by the same RRC parameters (dmrs-TypeEnh in dmrs-DownlinkForPDSCH-MappingTypeA or dmrs-DownlinkForPDSCH-MappingTypeB) as DCI format 1_1 and Rel.18 DMRS, and no new UE capability may be required for simultaneous configuration of Rel.18 DMRS and Rel.18 single DCI [for DCI format 4_2].

[0176] <<Variations>> In embodiment 3, simultaneous configuration of both Rel.18 DMRS and Rel.18 single DCI may increase the complexity / processing power of the UE, and new UE capabilities to support simultaneous configuration of Rel.18 DMRS and Rel.18 single DCI for DCI format 4_2, or new UE capabilities for the combination of Rel.18 DMRS and DCI format 4_2 may be introduced (or may be required).

[0177] <<Variations>> In embodiment 3, the UE may assume that dmrs-TypeEnh is not set [for PDSCHs scheduled by DCI format 4_2], or may not expect that dmrs-TypeEnh is set [for PDSCHs scheduled by DCI format 4_2].

[0178] <Embodiment 4> The aforementioned specification of the physical layer procedures for data may be updated to exclude that DCI format 4_2 can schedule PDSCH using Rel.18 DMRS ports (FD-OCC of length 4).

[0179] In the above-mentioned specification of the data physical layer procedure, at least one of the following procedures 1-1B and 1-2B may be defined instead of procedures 1-1 and 1-2.

[0180] ◆ Step 1-1B: The DMRS reception procedure for a PDSCH scheduled by a PDCCH having DCI format 1_1 applies similarly to a PDSCH scheduled by a PDCCH having DCI format 1_2, etc. The DMRS reception procedure for a PDSCH scheduled by a PDCCH having DCI format 1_1 applies similarly to a PDSCH scheduled by a PDCCH having DCI format 1_3, except for the setting of dmrs-TypeEnh (when the higher layer parameter dmrs-TypeEnh is set). When receiving a PDSCH scheduled by DCI format 1_3 by a PDCCH having a CRC scrambled by C-RNTI, MCS-C-RNTI, or CS-RNTI, or a PDSCH scheduled by DCI format 4_2 by a PDCCH having a CRC scrambled by G-RNTI or G-CS-RNTI for multicast, the UE ignores dmrs-TypeEnh. The DMRS reception procedure for a PDSCH scheduled by a PDCCH with DCI format 1_1 applies similarly to a PDSCH scheduled by a PDCCH with DCI format 4_2, etc.

[0181] ◆Step 1-2B: When receiving a PDSCH scheduled by DCI format 1_1 using a PDCCH having a CRC scrambled by C-RNTI, MCS-C-RNTI, or CS-RNTI, the UE may configure the upper layer parameters dmrs-Type / dmrs-TypeEnh, and the configured DMRS configuration type is used to receive the PDSCH.

[0182] In embodiment 4, simultaneous configuration of both Rel.18 DMRS and Rel.18 single DCI may increase the complexity / processing capability of the UE, and new UE capabilities may be introduced (or may be required) to support simultaneous configuration of Rel.18 DMRS and Rel.18 single DCI for DCI format 4_2.

[0183] In embodiment 4, DCI format 4_2 does not support Rel.18 DMRS, and new UE capabilities for simultaneous configuration of Rel.18 DMRS and Rel.18 single DCI [as described above] [for DCI format 4_2] may be required.

[0184] <<Variations>>

[0185] In step 1-1B, "ignore dmrs-TypeEnh" may be replaced with "assume dmrs-TypeEnh is not set" or "do not expect dmrs-TypeEnh to be set."

[0186] <<Variations>> In embodiment 4, no new UE capability may be introduced (or required) to support simultaneous configuration of Rel.18 DMRS and Rel.18 single DCI [for DCI format 4_2].

[0187] <Embodiment 5> The multiplexing and channel coding specifications mentioned above may be updated to support that DCI format 0_3 can schedule PUSCH using Rel. 18 DMRS ports (FD-OCC of length 4).

[0188] In the above-mentioned multiplexing and channel coding specifications, the following steps 7-2-1-3-5A to 7-2-1-3-12A may be defined instead of steps 7-2-1-3-5 to 7-2-1-3-8.

[0189] ---◆ Procedure 7-2-1-3-5A: If the transform precoder is disabled, and dmrs-Type=1, and dmrs-TypeEnh is not set, and maxLength=1, and the rank value is determined according to the SRS resource set indicator field when the upper layer parameter txConfig=nonCodebook, or according to the precoding information and number of layers field when the upper layer parameter txConfig=codebook, then M A (r) or each block is 3 bits as defined in table AU-8 / 9 / 10 / 10A / 11 according to the value of the rank.

[0190] ---◆ Procedure 7-2-1-3-6A: If the transform precoder is disabled, and dmrs-Type=1, and dmrs-TypeEnh is not set, and maxLength=2, and the rank value is determined according to the SRS resource set indicator field when the upper layer parameter txConfig=nonCodebook, or according to the precoding information and number of layers field when the upper layer parameter txConfig=codebook, then M A (r) or each block is 4 bits as defined in table AU-12 / 13 / 14 / 14A / 15 / 15A / 15B / 15C / 15D according to the value of rank.

[0191] ---◆ Procedure 7-2-1-3-7A: If the transform precoder is disabled, and dmrs-Type=2, and dmrs-TypeEnh is not set, and maxLength=1, and the rank value is determined according to the SRS resource set indicator field when the upper layer parameter txConfig=nonCodebook, or according to the precoding information and number of layers field when the upper layer parameter txConfig=codebook, then M A (r) or each block is 4 bits as defined in table AU-16 / 17 / 18 / 18A / 19 / 19A / 19B according to the value of rank.

[0192] ---◆ Procedure 7-2-1-3-8A: If the transform precoder is disabled, and dmrs-Type=2, and dmrs-TypeEnh is not set, and maxLength=2, and the rank value is determined according to the SRS resource set indicator field when the upper layer parameter txConfig=nonCodebook, or according to the precoding information and number of layers field when the upper layer parameter txConfig=codebook, then M A (r) or each block is 5 bits as defined in table AU-20 / 21 / 22 / 22A / 23 / 23A / 23B / 23C / 23D according to the value of rank.

[0193] ---◆ Procedure 7-2-1-3-9A: If the transform precoder is disabled, and dmrs-Type=1, and dmrs-TypeEnh is set, and maxLength=1, and the rank value is determined according to the SRS resource set indicator field when the upper layer parameter txConfig=nonCodebook, or according to the precoding information and number of layers field when the upper layer parameter txConfig=codebook, then M A(r) or each block is 4 bits as defined in table AU-38 / 39 / 40 / 40A / 41 / 42 / 43 / 44 / 45 according to the value of rank.

[0194] ---◆ Step 7-2-1-3-10A: If the transform precoder is disabled, and dmrs-Type=1, and dmrs-TypeEnh is set, and maxLength=2, and the rank value is determined according to the SRS resource set indicator field when the upper layer parameter txConfig=nonCodebook, or according to the precoding information and number of layers field when the upper layer parameter txConfig=codebook, then M A (r) or each block is 5 bits as defined in table AU-46 / 47 / 48 / 48A / 49 / 50 / 51 / 52 / 53 according to the value of rank.

[0195] ---◆ Procedure 7-2-1-3-11A: If the transform precoder is disabled, and dmrs-Type=2, and dmrs-TypeEnh is set, and maxLength=1, and the rank value is determined according to the SRS resource set indicator field when the upper layer parameter txConfig=nonCodebook, or according to the precoding information and number of layers field when the upper layer parameter txConfig=codebook, then M A (r) or each block is 5 bits as defined in table AU-54 / 55 / 56 / 56A / 57 / 58 / 59 / 60 / 61 according to the value of rank.

[0196] ---◆ Procedure 7-2-1-3-12A: If the transform precoder is disabled, and dmrs-Type=2, and dmrs-TypeEnh is set, and maxLength=2, and the rank value is determined according to the SRS resource set indicator field when the upper layer parameter txConfig=nonCodebook, or according to the precoding information and number of layers field when the upper layer parameter txConfig=codebook, then M A (r) or each block is 6 bits as defined in table AU-62 / 63 / 64 / 64A / 65 / 66 / 67 / 68 / 69 according to the value of rank.

[0197] FIG. 10 shows an example of an antenna port table (AU-38) for PUSCH when the extended DMRS type (dmrs-TypeEnh) is configured.

[0198] In embodiment 5, a new UE capability for supporting simultaneous configuration of Rel.18 DMRS and Rel.18 single DCI for DCI format 0_3 may not be introduced (may not be required).

[0199] In embodiment 5, DCI format 0_3 supports Rel.18 DMRS, and DCI format 0_3 and Rel.18 DMRS can be configured by the same RRC parameter (dmrs-TypeEnh in dmrs-UplinkForPUSCH-MappingTypeA or dmrs-UplinkForPUSCH-MappingTypeB) as DCI format 0_1 ​​and Rel.18 DMRS, and no new UE capability for simultaneous configuration of Rel.18 DMRS and Rel.18 single DCI [for DCI format 0_3] may be required.

[0200] <<Variations>> In embodiment 5, simultaneous configuration of both Rel.18 DMRS and Rel.18 single DCI may increase the complexity / processing power of the UE, and new UE capabilities to support simultaneous configuration of Rel.18 DMRS and Rel.18 single DCI for DCI format 0_3, or new UE capabilities for the combination of Rel.18 DMRS and DCI format 0_3 may be introduced (or may be required).

[0201] <<Variations>> In embodiment 5, the UE may assume that dmrs-TypeEnh is not set [for PUSCHs scheduled by DCI format 0_3], or may not expect that dmrs-TypeEnh is set [for PUSCHs scheduled by DCI format 0_3].

[0202] <<Variations>> A new UE capability may be reported by the UE, which indicates the maximum number of new DMRS types (extended DMRS types) configured for one DCI format 0_3.

[0203] <<Variations>>

[0204] Instead of steps 7-2-1-3-9A to 7-2-1-3-12A, the following steps 7-2-1-3-9B to 7-2-1-3-12B may be specified.

[0205] ---◆ Step 7-2-1-3-9B: If the conversion precoder is disabled, and dmrs-Type=1, and dmrs-TypeEnh is set, and maxLength=1, then M A (r) or each block is 4 bits as defined in table AU-38 / 39 / 40 / 40A / 41 / 42 / 43 / 44 / 45 according to the value of rank.

[0206] ---◆ Step 7-2-1-3-10B: If the conversion precoder is disabled, and dmrs-Type=1, and dmrs-TypeEnh is set, and maxLength=2, then M A (r) or each block is 5 bits as defined in table AU-46 / 47 / 48 / 48A / 49 / 50 / 51 / 52 / 53 according to the value of rank.

[0207] ---◆ Step 7-2-1-3-11B: If the conversion precoder is disabled, and dmrs-Type=2, and dmrs-TypeEnh is set, and maxLength=1, M A (r) or each block is 5 bits as defined in table AU-54 / 55 / 56 / 56A / 57 / 58 / 59 / 60 / 61 according to the value of rank.

[0208] ---◆ Step 7-2-1-3-12B: If the conversion precoder is disabled, and dmrs-Type=2, and dmrs-TypeEnh is set, and maxLength=2, then M A (r) or each block is 6 bits as defined in table AU-62 / 63 / 64 / 64A / 65 / 66 / 67 / 68 / 69 according to the value of rank.

[0209] <Embodiment 6> The aforementioned specification of the physical layer procedures for data may be updated to exclude that DCI format 0_3 can schedule PUSCH using Rel. 18 DMRS ports (FD-OCC of length 4).

[0210] In the above-mentioned specification of the data physical layer procedure, the following procedure 4-1A may be specified instead of procedure 4-1.

[0211] ◆ Step 4-1A: The DMRS transmission procedure for a PUSCH scheduled by a PDCCH having DCI format 0_1 ​​is similarly applied to a PUSCH scheduled by a PDCCH having DCI format 0_2 by applying the parameters dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2 and dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2 instead of dmrs-UplinkForPUSCH-MappingTypeA and dmrs-UplinkForPUSCH-MappingTypeB. The DMRS transmission procedure for a PUSCH scheduled by a PDCCH having DCI format 0_1 ​​is similarly applied to a PUSCH scheduled by a PDCCH having DCI format 0_3, except for the setting of dmrs-TypeEnh (when dmrs-TypeEnh is set). The UE ignores dmrs-TypeEnh when transmitting a PUSCH scheduled by a PDCCH having DCI format 0_3.

[0212] In embodiment 6, simultaneous configuration of both Rel.18 DMRS and Rel.18 single DCI may increase the complexity / processing capability of the UE, and new UE capabilities may be introduced (or may be required) to support simultaneous configuration of Rel.18 DMRS and Rel.18 single DCI for DCI format 0_3.

[0213] In embodiment 6, DCI format 0_3 does not support Rel.18 DMRS, and a new UE capability for simultaneous configuration of Rel.18 DMRS and Rel.18 single DCI [as described above] [for DCI format 0_3] may be required.

[0214] <<Variations>>

[0215] "Ignore dmrs-TypeEnh" in Procedure 4-1A may be replaced with "Assume dmrs-TypeEnh is not set" or "Do not expect dmrs-TypeEnh to be set".

[0216] <<Variation>> In Embodiment 6, new UE capabilities for supporting the simultaneous configuration of Rel.18 DMRS and Rel.18 single DCI for [DCI format 0_3] may not (need not) be introduced.

[0217] <Supplementary Note> <<Notification of Information to UE>> Notification of any information from a [Network (NW) (e.g., Base Station (BS))] to a UE in the above embodiments (or in other words, reception of any information from a BS by a UE) may be performed using physical layer signaling (e.g., DCI), upper layer signaling (e.g., RRC signaling, MAC CE, RRC message, LTE positioning protocol (LPP) message), a specific signal / channel (e.g., DCI, PDCCH, PDSCH, reference signal), or a combination thereof.

[0218] When the above notification is performed by a MAC CE, the MAC CE may be identified by including a new Logical Channel ID (LCID) that is not defined in the existing standard in the MAC subheader. The MAC CE may be an extension of an existing MAC CE. For example, the MAC CE may introduce a new octet to an existing MAC CE.

[0219] When the notification is performed by DCI, the notification may be performed by a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used to scramble Cyclic Redundancy Check (CRC) bits assigned to the DCI, the format of the DCI, etc. The specific field may be an existing DCI field or a new DCI field. The RNTI may be an existing RNTI or a new RNTI. The format of the DCI may be an existing DCI format or a new DCI format.

[0220] Furthermore, notification of any information to the UE in the above embodiments may be periodic, semi-persistent (triggered by the UE or the gNB), or aperiodic (triggered by the UE or the gNB).

[0221] In the above embodiment, the UE may receive information of at least one of the following several QCL rules from the NW: ◆QCL Type A ◆QCL Type B ◆QCL Type C ◆QCL Type D

[0222] In the above-described embodiments, the QCL source RS for each QCL type may be at least one of the following several RSs: ◆SSB ◆CSI-RS with / without repetition ◆TRS ◆DMRS for PDCCH / PDSCH

[0223] In the above embodiment, the information from the NW may be set / instructed by the following method. ◆Common to multiple UEs or individual UEs ◆ Cell specific or common to multiple cells ◆Per UE / Per CC / Per BWP / Per Band / Per Cell / Per cell group (CG)

[0224] <<Notification of Information from UE>> The notification of any information from the UE to the [NW] in the above-described embodiment (in other words, the transmission / reporting of any information from the UE to the BS) may be performed using physical layer signaling (e.g., UCI), upper layer signaling (e.g., RRC signaling, MAC CE, RRC message, LPP message), a specific signal / channel (e.g., UCI, PUCCH, PUSCH, PRACH, reference signal), or a combination thereof.

[0225] When the above notification is performed by MAC CE, the MAC CE may be identified by including a new LCID not defined in the existing standard in the MAC sub-header. The MAC CE may be an extension of an existing MAC CE. For example, the MAC CE may be one obtained by introducing a new octet into an existing MAC CE.

[0226] When the above notification is performed by UCI, the above notification may be transmitted using PUCCH or PUSCH.

[0227] Also, the notification of any information from the UE in the above-described embodiment may be performed periodically, semi-persistently (triggered by the UE or gNB), or aperiodically (triggered by the UE or gNB).

[0228] <<Regarding the Application of Each Embodiment>> In the UE / BS, specific (one or more) processing / operations / controls / assumptions / information regarding at least one of the above-described embodiments may be applied (used) when any one or a plurality of the following conditions are satisfied: ◆An upper layer parameter indicating the above specific processing / operation / control / assumption / information is set ◆The above specific processing / action / control / assuming / information is determined based on the relevant upper layer parameters, ◆The above specific processing / action / control / assuming / information is instructed / specified / activated / triggered by MAC CE / DCI / UCI / resource / channel / RS, Reporting or supporting specific UE capabilities that indicate (or relate to) the specific processes / operations / controls / assumptions / information mentioned above; ◆The application of the above specific processing / action / control / assumption / information is determined based on specific conditions.

[0229] The specific UE capabilities may indicate at least one of the following: ◆Supporting the above specific processing / action / control / assuming / information, ◆ Capabilities of each embodiment. * Capabilities of each option in each embodiment, or capabilities of a combination of multiple options in each embodiment. ◆The capabilities of each option in each embodiment, or the capabilities of a combination of multiple options in each embodiment.

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

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

[0232] If the above conditions are not met, the UE / BS may follow the behavior specified in existing 3GPP releases.

[0233] Information on whether one or more of the above embodiments / options / choices / examples apply / are used, or which of the above embodiments / options / choices / examples apply / are used, may be based on several of the following methods: ◆The information is configured by one or more higher layer parameters / RRC IEs. ◆The information is determined by one or more relevant higher layer parameters / RRC IEs. ◆The information is indicated by the MAC CE / DCI. The information is determined based on one or more UE capabilities. ◆The information is described / defined in the specification. ◆The information is based on the conditions described / defined in the specification. ◆The information is determined by a combination of several pieces of information above. For example, the information is determined by upper layer parameters / MAC CE / DCI settings / indications, and reported by UE capabilities.

[0234] The above embodiments / options / choices may be combined into one embodiment / option / choice.

[0235] In the above embodiments, the RS to be measured may be a QCL source RS in an active TCI state / indicated / unified TCI state.

[0236] (Addendum) The following inventions are added to the embodiment (3 / 4) of the present disclosure. <Appendix 1> a receiving unit for receiving a demodulation reference signal (DMRS) configuration and a downlink control information (DCI) format for scheduling a physical downlink shared channel (PDSCH) for multicast within a downlink cell; and a control unit that determines, based on the configuration and the DCI format, whether a frequency domain (FD)-orthogonal cover code (OCC) of length 4 is applied to the DMRS for the plurality of PDSCHs. <Appendix 2> The terminal according to Supplementary Note 1, wherein the control unit determines the number of bits of the antenna port field based on an association between a value of the antenna port field in the DCI format and a DMRS port number to which the FD-OCC of length 4 is applied. <Appendix 3> 3. The terminal of claim 1 or 2, wherein the controller determines that the FD-OCC of length 4 is not applied to the DMRS. <Appendix 4> The terminal according to any one of Supplementary Note 1 to Supplementary Note 3, wherein the control unit controls reporting of capability information indicating support for simultaneous configuration of the DMRS to which the FD-OCC of length 4 is applied and the DCI format. <Supplementary information> The receiving unit may be the transceiver unit 220. The control unit may be the control unit 210. The DCI format may be DCI format 4_2. The association may be Table AD-7 / 8 / 9 / 10. Determining that the length 4 FD-OCC is not applied to the DMRS may be interpreted as ignoring dmrs-TypeEnh, assuming that dmrs-TypeEnh is not set, or not expecting that dmrs-TypeEnh is set. The DMRS to which the length 4 FD-OCC is applied may be interpreted as Rel. 18 DMRS, and dmrs-TypeEnh is set. <Appendix A> a transmitter for transmitting a demodulation reference signal (DMRS) configuration and a downlink control information (DCI) format for scheduling a physical downlink shared channel (PDSCH) for multicast within a downlink cell; and a control unit that determines whether a frequency domain (FD)-orthogonal cover code (OCC) of length 4 is applied to the DMRS for the plurality of PDSCHs based on the configuration and the DCI format. <Supplementary information> The transmitting unit may be the transceiver unit 120. The control unit may be the control unit 110.

[0237] (Addendum) The following inventions are added to the embodiments (5 / 6) of the present disclosure. <Appendix 1> a receiver configured to receive a demodulation reference signal (DMRS) configuration and to receive a downlink control information (DCI) format for scheduling a plurality of physical uplink shared channels (PUSCHs) in a plurality of cells, each PUSCH having one PUSCH; and a controller that determines, based on the configuration and the DCI format, whether a frequency domain (FD)-orthogonal cover code (OCC) of length 4 is applied to the DMRS for the multiple PUSCHs. <Appendix 2> The terminal according to Supplementary Note 1, wherein the control unit determines the number of bits of the antenna port field based on an association between a value of the antenna port field in the DCI format and a DMRS port number to which the FD-OCC of length 4 is applied. <Appendix 3> 3. The terminal of claim 1 or 2, wherein the controller determines that the FD-OCC of length 4 is not applied to the DMRS. <Appendix 4> The terminal according to any one of Supplementary Note 1 to Supplementary Note 3, wherein the control unit controls reporting of capability information indicating support for simultaneous configuration of the DMRS to which the FD-OCC of length 4 is applied and the DCI format. <Supplementary information> The receiver may be the transceiver 220. The controller may be the controller 210. The DCI format may be DCI format 0-3. The association may be table AU-38 / 39 / 40 / 40A / 41 / 42 / 43 / 44 / 45 / 46 / 47 / 48 / 48A / 49 / 50 / 51 / 52 / 53 / 54 / 55 / 56 / 56A / 57 / 58 / 59 / 60 / 61 / 62 / 63 / 64 / 64A / 65 / 66 / 67 / 68 / 69. The number of bits in the antenna port field may be M A (r), or each block in the antenna port field. Determining that the length-4 FD-OCC does not apply to the DMRS may be interpreted as ignoring dmrs-TypeEnh, assuming that dmrs-TypeEnh is not set, or not expecting that dmrs-TypeEnh is set. The DMRS to which the length-4 FD-OCC applies may be interpreted as Rel. 18 DMRS, and dmrs-TypeEnh is set. <Appendix A> a transmitter configured to transmit a demodulation reference signal (DMRS) configuration and a downlink control information (DCI) format for scheduling a plurality of physical uplink shared channels (PUSCHs) in a plurality of cells, each PUSCH having one PUSCH; and a control unit that determines, based on the configuration and the DCI format, whether a frequency domain (FD)-orthogonal cover code (OCC) of length 4 is applied to the DMRS for the plurality of PUSCHs. <Supplementary information> The transmitting unit may be the transceiver unit 120. The control unit may be the control unit 110.

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

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

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

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

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

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

[0244] The wireless communication system 1 may utilize Multi Input Multi Output (MIMO). For example, one cell may be formed by one antenna / base station 10, or may be formed by multiple antennas / base stations 10. One [virtual] cell (which may be called, for example, a super cell) may be composed of multiple [virtual] cells (which may be called, for example, sub-cells). A super cell may correspond to a cell whose physical range is fixed, and a sub-cell may correspond to a cell whose physical range varies semi-statically / dynamically. In this case, the wireless communication system 1 may be called a cell-free system.

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

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

[0247] Furthermore, the user terminal 20 may perform communication using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) in each CC.

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

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

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

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

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

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

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

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

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

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

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

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

[0260] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be called a search space set. Note that the terms "search space," "search space set," "search space setting," "search space set setting," "CORESET," "CORESET setting," etc. in the present disclosure may be read interchangeably.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0274] The transceiver 120 may form at least one of a transmission beam and a reception beam using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), or the like.

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

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

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

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

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

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

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

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

[0283] The base station 10 may be separated into three elements: a radio unit (RU), a distributed unit (DU), and a central unit (CU). For example, the RU may perform RF processing (digital beamforming, digital-to-analog conversion, analog beamforming, etc.) and lower-level functions of the physical layer (precoding, IFFT, FFT, etc.). The DU may perform higher-level functions of the physical layer (coding to resource element mapping, etc.), MAC layer functions, and RLC layer functions. The CU may perform PDCP layer, Service Data Adaptation Protocol (SDAP) layer, and RRC layer functions.

[0284] In the present disclosure, the base station 10 may include a single device that implements all of the functions of the RU, DU, and CU, or may include multiple devices that each implement some of the functions of the RU, DU, and CU and are connected to each other. In the present disclosure, the base station 10 may be interchangeably read as RU / DU / CU.

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

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

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

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

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

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

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

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

[0293] The transceiver 220 may form at least one of a transmission beam and a reception beam using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), or the like.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0311] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, 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 medium. The memory 1002 may also be referred to as a register, a cache, a main memory, or the like. The memory 1002 may store executable programs (program codes), software modules, and the like for implementing a wireless communication method according to an embodiment of the present disclosure.

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

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

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

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

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

[0317] Note that the devices included in the core network 30 (for example, network nodes that provide NFs) may also be realized by the above-described functional block / hardware configuration.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0332] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

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

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

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

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

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

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

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

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

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

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

[0343] With respect to any information (e.g., variables, constants, parameters) described in the present disclosure, even if not specifically stated in the above embodiments, any first device (e.g., UE / base station) may notify any second device (e.g., base station / UE) of information indicating / identifying (or relating to) the value of the any information.

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

[0345] Note that the physical layer signaling may be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be called an RRC message, such as an RRC connection setup message or an RRC connection reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, a MAC Control Element (CE).

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

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

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

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

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

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

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

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

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

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

[0356] Furthermore, in this disclosure, terms such as "QCL," "QCL assumptions," "QCL relationships," "QCL type information," "QCL properties," "specific QCL type (e.g., Type A, Type D) properties," and "specific QCL type (e.g., Type A, Type D)" may be interchangeable.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. a receiver configured to receive a demodulation reference signal (DMRS) configuration and a downlink control information (DCI) format for scheduling a plurality of physical uplink shared channels (PUSCHs) in a plurality of cells, each PUSCH having one PUSCH; A terminal comprising: a control unit that determines whether a frequency domain (FD)-orthogonal cover code (OCC) of length 4 is applied to the DMRS for the plurality of PUSCHs based on the setting and the DCI format.

2. The terminal according to claim 1, wherein the control unit determines the number of bits of the antenna port field based on an association between a value of the antenna port field in the DCI format and a DMRS port number to which the FD-OCC of length 4 is applied.

3. The terminal of claim 1 , wherein the controller determines that the FD-OCC of length 4 is not applied to the DMRS.

4. The terminal according to claim 1, wherein the control unit controls reporting of capability information indicating support for simultaneous configuration of the DMRS to which the length 4 FD-OCC is applied and the DCI format.

5. receiving a demodulation reference signal (DMRS) configuration; receiving a downlink control information (DCI) format for scheduling a plurality of physical uplink shared channels (PUSCHs) in a plurality of cells, the PUSCHs being one per cell; and determining whether a frequency domain (FD)-orthogonal cover code (OCC) of length 4 is applied to the DMRS for the plurality of PUSCHs based on the setting and the DCI format.

6. a transmitter configured to transmit a demodulation reference signal (DMRS) configuration and a downlink control information (DCI) format for scheduling a plurality of physical uplink shared channels (PUSCHs) in a plurality of cells, each PUSCH having one PUSCH; A base station comprising: a control unit that determines whether a frequency domain (FD)-orthogonal cover code (OCC) of length 4 is applied to the DMRS for the plurality of PUSCHs based on the setting and the DCI format.

Images