Terminal, wireless communication method, and base station

Abstract

A terminal according to one aspect of the present disclosure comprises: a reception unit that receives a configuration of a demodulation reference signal (DMRS), and receives a downlink control information (DCI) format for scheduling a plurality of physical uplink shared channels (PUSCHs) in a plurality of cells having one PUSCH for each cell; and a control unit that determines, on the basis of 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.

Description

Terminal, wireless communication method, and base station

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

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

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

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

[0005] Multiple port reference signals (for example, demodulation reference signals (DMRS)) are used for purposes such as orthogonalizing layers.

[0006] In future wireless communication systems, there are plans to increase the number of DMRS ports beyond existing specifications. However, the configuration and application of DMRS in this case have not been adequately considered. If DMRS is not properly configured and applied, communication throughput and communication quality may deteriorate.

[0007] Therefore, one of the objectives of this disclosure is to provide terminals, wireless communication methods, and base stations to which appropriate DMRS is applied.

[0008] A terminal according to one aspect of the present disclosure includes a receiving unit that receives a demodulation reference signal (DMRS) setting and a downlink control information (DCI) format for scheduling a plurality of PUSCHs in a plurality of cells, each having one physical uplink sharing channel (PUSCH) per cell, and a control unit that determines, based on 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 plurality of PUSCHs.

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

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

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

[0012] The front-loaded demodulation reference signal (DMRS) is the first (first symbol or near the first symbol) DMRS for faster demodulation (reduction of data demodulation time) (Figure 1). For high-speed mobile terminals (user terminals, User Equipment (UE)) or high modulation and coding scheme (MCS) / rank, {0, 1, 2, 3} additional DMRS can be configured by the RRC IE. Additional DMRS are effective for scenarios such as high Doppler frequencies and high MCS. The frequency positions of the additional DMRS are the same as those of the front-loaded DMRS.

[0013] For the frequency domain, either (PDSCH / PUSCH) DMRS setting type 1 or 2 is set. ◆DMRS setting 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 setting 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 a higher rank.

[0014] Single-symbol DMRS or double-symbol DMRS can be configured. ◆Single-symbol DMRS is commonly used (it is a mandatory feature in Rel. 15). In single-symbol DMRS, the number of additional DMRS (symbols) is {0, 1, 2, 3}. Single-symbol DMRS supports both cases where frequency hopping is enabled and disabled. If the maximum number (maxLength) in the uplink DMRS configuration (DMRS-UplinkConfig) is not set, single-symbol DMRS is used. In DMRS configuration type 1, DMRS is placed in one RE for every two consecutive REs in the frequency domain. In DMRS configuration type 2, DMRS is placed in two consecutive REs for every six consecutive REs in the frequency domain. ◆Double-symbol DMRS is used for more DMRS ports (especially for Multi-User Multi-Input Multi-Output (MU-MIMO)). In double-symbol DMRS, the number of additional DMRS (symbols) is {0,1}. Double-symbol DMRS supports the case where frequency hopping is disabled. If the maximum number (maxLength) in the uplink DMRS configuration (DMRS-UplinkConfig) is 2 (len2), whether it is single-symbol DMRS or double-symbol DMRS is determined by DCI or configured grant. A DMRS is placed in one RE for 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, a DMRS is placed in two consecutive REs for every six consecutive REs in the frequency domain. Figure 2B shows an example of DMRS configuration type 2 for double-symbol DMRS.

[0015] For additional DMRS [in the time domain], the additional DMRS position is set by the higher-level 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, single symbol DMRS, mapping type A, dmrs-AdditionalPosition = pos1, l d In the case where = 10, the DMRS position is l0, 9. For example, single symbol DMRS, mapping type A, dmrs-AdditionalPosition = pos3, l d In the case of =12, the DMRS positions are l0, 5, 8, 11. For example, in the case of single symbol DMRS, mapping type B, dmrs-AdditionalPosition=pos0, the DMRS position is l0. For example, 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, double symbol DMRS, mapping type A, dmrs-AdditionalPosition=pos1,l d In the case where = 10, 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, double symbol DMRS, mapping type B, dmrs-AdditionalPosition = pos1, l d In the case where the value is 10, the DMRS positions are l0 and l7.

[0016] Multiple DMRS ports mapped to the same resource element (Resource Element (RE), a resource of time and frequency) are called a DMRS code division multiplexing (CDM) group.

[0017] For the basic DMRS in Rel. 15, enhanced DMRS is introduced in Rel. 18. The enhanced DMRS is set by the upper layer parameter dmrs-TypeEnh.

[0018] There are several parameters for the DMRS port. ◆ OCC type: A Walsh matrix is used for the OCC of the PDSCH. A cyclic shift is used for the OCC of the PUSCH. ◆ FD-OCC: As two FD-OCCs for the basic DMRS, w f (k’), k’ = 0, 1 are used from w f (1). As four FD-OCCs for the enhanced DMRS, w f (k’), k’ = 0, 1, 2, 3 are used. ◆ TD-OCC: As two TD-OCCs for the double-symbol DMRS, w t (l’), l’ = 0, 1 are used.

[0019] Several configurations are available for DMRS, as follows: ◆Configuration 1: Basic DMRS, Configuration Type 1, Single Symbol DMRS Up to four DMRS ports are available using two CDM groups' FDM and two FD-OCCs (length 2) within each CDM group. ◆Configuration 2: Basic DMRS, Configuration Type 1, Double Symbol DMRS Up to eight DMRS ports are available using two CDM groups' FDM and two FD-OCCs (length 2) and two TD-OCCs (length 2) within each CDM group. ◆Configuration 3: Basic DMRS, Configuration Type 2, Single Symbol DMRS Up to six DMRS ports are available using three CDM groups' FDM and two FD-OCCs (length 2) within each CDM group. ◆Setting 4: Basic DMRS, Setting Type 2, Double Symbol DMRS Up to 12 DMRS ports are available through FDM in three CDM groups and a CDM using two FD-OCCs (length 2) and two TD-OCCs (length 2) within each CDM group. ◆Setting 5: Extended DMRS, Setting Type 1, Single Symbol DMRS Up to 8 DMRS ports are available through FDM in two CDM groups and a CDM using four FD-OCCs (length 4) within each CDM group. ◆Setting 6: Extended DMRS, Setting Type 1, Double Symbol DMRS Up to 16 DMRS ports are available through FDM in two CDM groups and a CDM using four FD-OCCs (length 4) and two TD-OCCs (length 2) within each CDM group. ◆Setting 7: Extended DMRS, Setting Type 2, Single Symbol DMRS Up to 12 DMRS ports are available through FDM in three CDM groups and CDM using four FD-OCCs (length 4) within each CDM group. ◆Setting 8: Extended DMRS, Setting Type 2, Double Symbol DMRS Up to 24 DMRS ports are available through FDM in three CDM groups and CDM using four FD-OCCs (length 4) and two TD-OCCs (length 2) within each CDM group.

[0020] In this 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 applies, DMRS port within the port number range of legacy DMRS, legacy DMRS port, legacy DMRS configuration type being configured, legacy DMRS configuration type 1 or 2 being configured, extended DMRS type (dmrs-TypeEnh) not being configured, and legacy DMRS port being indicated may be interpreted as one another.

[0021] In this disclosure, the statements "DMRS [Setting] Type 1", "DMRS Type = 1", "DMRS Type 1", and "dmrs-Type set to type2 is not set" may be interpreted interchangeably. In this disclosure, the statements "DMRS [Setting] Type 2", "DMRS Type = 2", "DMRS Type 2", and "dmrs-Type set to type2 is set" may be interpreted interchangeably.

[0022] In this disclosure, the following terms may be interpreted interchangeably: new DMRS, enhanced DMRS, Rel. 18 DMRS, enhanced DMRS function, enhanced DMRS [configuration] type, configuration / upper layer parameters for enhanced DMRS type, enhanced-dmrs-Type_r18, dmrs-TypeEnh, enhanced 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 applies, DMRS port outside the port number range of existing DMRS, enhanced DMRS port, setting of enhanced DMRS type (dmrs-TypeEnh), setting of enhanced-dmrs-Type_r18, setting of enhanced DMRS configuration type 1 or 2, setting of enhanced DMRS type, and indicating an enhanced DMRS port.

[0023] In this disclosure, Extended DMRS [configuration] type 1, DMRS extended type 1, DMRS extended type = 1, DMRS eType 1, Extended DMRS type is configured and dmrs-Type set to type 2 is not configured may be interpreted as mutually exclusive. In this disclosure, Extended DMRS [configuration] type 2, DMRS extended type 2, DMRS extended type = 2, DMRS eType 2, Extended DMRS type is configured and dmrs-Type set to type 2 is configured may be interpreted as mutually exclusive.

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

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

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

[0027] In this disclosure, the terms [Antenna] port, DMRS port, DMRS port number, DMRS port index, and antenna port number-1000 may be interpreted as interchangeable.

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

[0029] The table showing parameters for DMRS configuration type 1 or 2 of PUSCH or PDSCH (DMRS parameter table, association) is PDSCH DMRS port p or PUSCH DMRS port p ~ And, CDM group λ, Δ related to frequency offset, FD-OCC W f (k'), TD-OCC W t (l') indicates an association with at least one of the following.

[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 through 3. Basic type 1 double symbol DMRS uses ports 0 through 7. Extended type 1 single symbol DMRS uses ports 0 through 3 and 8 through 11. Extended type 1 double symbol DMRS uses ports 0 through 15.

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

[0033] v is the number of layers. j=0, 1, ..., v-1 are the layer indices. 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 represented using a pseudo-random (pseudo-noise) sequence c(n).

[0034] w f (k') (FD-OCC) and w t (l') (TD-OCC) is the orthogonal cover code as 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,... are indices for each FD-OCC.

[0036] ((Notification of PDSCH DMRS Ports)) One or more DMRS ports used for PDSCH transmission are notified to the UE by the DCI [antenna port field in DCI] based on a table (antenna port table, association) for specifying antenna ports (DMRS ports) [for DMRS setting type 1 or 2 and DMRS maximum length 1 or 2]. Based on an 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 REs based on the notified information.

[0037] For the DCI format used to schedule PDSCH, the following multiple Antenna Port tables are defined, showing 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 Max 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 Max Length (maxLength) = 2 is set. ◆Table AD-3, Table AD-3A: Cases 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: Cases 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: Cases 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: Cases where DMRS type (dmrs-Type) = 1, extended DMRS type (dmrs-TypeEnh) is set, and DMRS maximum length (maxLength) = 2. ◆Table AD-9, Table AD-9A: Cases where DMRS type (dmrs-Type) = 2, extended DMRS type (dmrs-TypeEnh) is set, and DMRS maximum length (maxLength) = 1.◆Table AD-10, Table AD-10A: Cases 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 set for the antenna port field of DCI format 1_1 receives an activation command that maps at least one code point in the DCI field 'Transmission Configuration Indication' to two TCI states, or if a UE that has dl-OrJointTCI-StateList set has two indicative TCI states, then that UE uses table AD-1 / 2 / 3 / 4 / 7 / 8 / 9 / 10; otherwise, that UE uses table AD-1A / 2A / 3A / 4A / 7A / 8A / 9A / 10A.

[0039] ((Notification of PUSCH DMRS Ports)) One or more DMRS ports used for PUSCH transmission are notified to the UE by the DCI [antenna port field] based on a table for antenna port (DMRS port) identification (antenna port table) [for at least one of DMRS setting type 1 or 2, DMRS maximum length 1 or 2, and rank]. Based on an 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 REs based on the notified information.

[0040] For the DCI format used to schedule PUSCH, the following several Antenna Port tables are defined, showing 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 set, the conversion precoder is enabled except that π / 2 BPSK modulation is used, and the DMRS type (dmrs-Type) = 1 and the DMRS maximum length (maxLength) = 1. ◆Table AU-6A: Case where the conversion precoder is enabled, both dmrs-UplinkTransformPrecoding and tp-pi2BPSK are set, π / 2 BPSK modulation is used, and the DMRS type (dmrs-Type) = 1 and the DMRS maximum length (maxLength) = 1. ◆Table AU-7: Case where both dmrs-UplinkTransformPrecoding and tp-pi2BPSK are set, the conversion precoder is enabled except that π / 2 BPSK modulation is used, the DMRS type (dmrs-Type) = 1, and the DMRS maximum length (maxLength) = 2. ◆Table AU-7A: Case where the conversion precoder is enabled, both dmrs-UplinkTransformPrecoding and tp-pi2BPSK are set, π / 2 BPSK modulation is used, the DMRS type (dmrs-Type) = 1, and the DMRS maximum length (maxLength) = 2.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0055] (Data Physical Layer Procedure) ((DMRS Reception Procedure)) In the specification of the data physical layer procedure, the following procedure 1-x is specified for the DMRS reception procedure.

[0056] ◆Procedure 1-1: 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. 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 4_2, etc.

[0057] ◆Procedure 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 by DCI format 4_2 with a PDCCH having a CRC scrambled by multicast G-RNTI or G-CS-RNTI, the UE may set the upper layer parameter dmrs-Type / dmrs-TypeEnh, and the set DMRS setting type is used for receiving the PDSCH.

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

[0059] (UE DMRS Transmission Procedure) In the specification for the physical layer procedure for data, the following procedure 4-x is specified for the UE DMRS transmission procedure.

[0060] ◆Procedure 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 specification for multiplexing and channel coding, the following procedure 2-x is specified for DCI Format 1_3.

[0062] ◆Procedure 2-1: DCI format 1_3 is used for scheduling one PDSCH within a single cell, or for scheduling multiple PDSCHs within multiple cells, each having one PDSCH.

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

[0064] ―◆Procedure 2-2-1: Antenna port [field]. Its number of bits is determined by the following:

[0065] --◆Procedure 2-2-1-1: If antennaPortsDCI-1-3=type1a is set by the higher 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 For}, max(M A (r)) bits. Here, N cell DL,2 r is the number of cells in the scheduled cell set set, set by the higher layer parameter scheduledCellListDCI-1-3 (list of scheduled cells), where r is mapped to those cells in ascending order of serving cell index, and r=1 corresponds to the cell with the smallest serving cell index, M A (r) is defined as described below.

[0066] --◆Step 2-2-1-2: If antennaPortsDCI-1-3=type2 is set by the higher 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 , and so on. ---◆Each block corresponds to antenna port information for one cell, and multiple blocks are arranged in ascending order of serving cell index, with block number 1 corresponding to antenna port information for the cell having the smallest serving cell index. Each block is defined as described below.

[0067] --◆Procedure 2-2-1-3: The aforementioned M in the case of antennaPortsDCI-1-3=type1a A (r), or in the case of antennaPortsDCI-1-3=type2, each of the aforementioned blocks is defined as follows: ---◆As defined by tables AD-1 / 2 / 3 / 4 and tables AD-1A / 2A / 3A / 4A, M A (r) Or each block is 4, 5, or 6 bits. 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. Antenna ports {p0,...,p 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} is equal to. Here, x A x is the bit width of the "antenna port" [field] derived according to dmrs-DownlinkForPDSCH-MappingTypeA, andB This is the bit width of the "antenna port" [field] derived according to dmrs-DownlinkForPDSCH-MappingTypeB. The PDSCH mapping type is x A and x B If it corresponds to the smaller value, then in the most significant bit (MSB) of this field, |x A -x B The zeros in the | symbol are padded.

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

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

[0071] ((DCI Format 4_2)) In the specifications for multiplexing and channel coding, the following procedure 3-x is specified for DCI Format 4_2.

[0072] ◆Procedure 3-1: DCI format 4_2 is used for scheduling PDSCHs for multicast within DL cells.

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

[0074] ―◆Procedure 3-2-1: Antenna port [field]. Its number of bits is determined by the following:

[0075] --◆Procedure 3-2-1-1: As defined by Table AD-1 / 2 / 3 / 4, the antenna port [field] is 4, 5, or 6 bits. 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. Antenna port {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 to have both dmrs-DownlinkForPDSCH-MappingTypeA and dmrs-DownlinkForPDSCH-MappingTypeB, the bit width of this [Antenna Port] field is max{x A ,x B} is equal to. Here, x A x is the bit width of the "antenna port" [field] derived according to dmrs-DownlinkForPDSCH-MappingTypeA, and B This is the bit width of the "antenna port" [field] derived according to dmrs-DownlinkForPDSCH-MappingTypeB. The PDSCH mapping type is x A and x B If it corresponds to the smaller value, then in the most significant bit (MSB) of this field, |x A -x B The zeros in the | symbol are padded.

[0077] ((DCI Format 0_1)) In the specifications for multiplexing and channel coding, the following procedure 5-x is specified for DCI Format 0_1.

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

[0079] ◆Procedure 5-2: The following information is transmitted using DCI format 0_1, which has a CRC that has been scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI.

[0080] ―◆Procedure 5-2-1: Antenna port [field]. Its number of bits is determined by the following:

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

[0082] ---◆Procedure 5-2-1-3-2: When the conversion precoder is enabled, and both dmrs-UplinkTransformPrecoding and tp-pi2BPSK are set, and π / 2 BPSK modulation is used, and dmrs-Type=1 and maxLength=1, the antenna port [field] is 2 bits, as defined in table AU-6A. Here, n SCID This is a scrambling identifier (identity) for the antenna port as defined in the physical channel and modulation specifications.

[0083] ---◆Procedure 5-2-1-3-3: When the conversion precoder is enabled, and dmrs-Type=1, and maxLength=2, unless both dmrs-UplinkTransformPrecoding and tp-pi2BPSK are set and π / 2 BPSK modulation is used, the antenna port [field] is 4 bits, as defined in table AU-7.

[0084] ---◆Procedure 5-2-1-3-4: When the conversion precoder is enabled, and both dmrs-UplinkTransformPrecoding and tp-pi2BPSK are set, and π / 2 BPSK modulation is used, and dmrs-Type=1 and maxLength=2, the antenna port [field] is 4 bits, as defined in table AU-7A. Here, n SCID This is a scrambling identifier (identity) for the antenna port as defined in the physical channel and modulation specifications.

[0085] ---◆Procedure 5-2-1-3-5: If the conversion 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 the table AU-8 / 9 / 10 / 10A / 11 according to the rank value.

[0086] ---◆Procedure 5-2-1-3-6: If the conversion 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 the table AU-12 / 13 / 14 / 14A / 15 / 15A / 15B / 15C / 15D according to the rank value.

[0087] ---◆Procedure 5-2-1-3-7: If the conversion 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 the table AU-16 / 17 / 18 / 18A / 19 / 19A / 19B according to the rank value.

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

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

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

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

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

[0093] ―◆Procedure 5-2-2: Here, the values ​​1, 2, and 3 for 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] --◆Procedure 5-2-2-1: If txConfig=nonCodebook, 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", 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 layer number 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} is equal to. Here, x A x is the bit width of the "antenna port" [field] derived according to dmrs-UplinkForPUSCH-MappingTypeA, and B This is the bit width of the "antenna port" [field] derived according to dmrs-UplinkForPUSCH-MappingTypeB. The mapping type of the PDSCH is x A and x B If it corresponds to the smaller value, then in the most significant bit (MSB) of this field, |x A -x B The zeros in the | symbol are padded.

[0099] ―◆Procedure 5-2-4: If a conversion precoder field exists, and the bit width of the antenna port field for the case where the conversion precoder is enabled is not equal to the bit width of the antenna port field for the case where the conversion precoder is disabled, then several MSBs with a value set to '0' are inserted into the antenna port field of the case with the smaller bit width until the bit widths of the antenna port fields for the two cases become equal.

[0100] ((DCI Format 0_2)) In the specifications for multiplexing and channel coding, the following procedure 6-x is specified for DCI Format 0_2.

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

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

[0103] ―◆Procedure 6-2-1: Antenna port [field]. Its number of bits is determined by the following:

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

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

[0106] ―◆Procedures 6-2-2 to 6-2-4: Same as procedures 5-2-2 to 5-2-4.

[0107] ((DCI Format 0_3)) In the specifications for multiplexing and channel coding, the following procedure 7-x is specified for DCI Format 0_3.

[0108] ◆Procedure 7-1: DCI format 0_3 is used for scheduling one PUSCH within a single cell, or for scheduling multiple PUSCHs within multiple cells, each having one PUSCH.

[0109] ◆Procedure 7-2: The following information is transmitted using DCI format 0_3, which has a CRC that has been scrambled by C-RNTI or MCS-C-RNTI.

[0110] ―◆Procedure 7-2-1: Antenna port [field]. Its number of bits is determined by the following:

[0111] --◆Procedure 7-2-1-1: If antennaPortsDCI0-3=type1a is set by the higher 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 For}, max(M A (r)) bits, where [N cell UL,2 is the number of cells in the scheduled cell set set, set by the higher layer parameter scheduledCellListDCI-0-3 (list of scheduled cells), where r is mapped to those cells in ascending order of serving cell index, and r=1 corresponds to the cell with the minimum serving cell index, M A (r) is defined as described below.

[0112] --◆Procedure 7-2-1-2: If antennaPortsDCI0-3=type2 is set by the higher 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 , and so on. ---◆Each block corresponds to antenna port information for one cell, and multiple blocks are arranged in ascending order of serving cell index, with block number 1 corresponding to antenna port information for the cell having the smallest serving cell index. Each block is defined as described below.

[0113] --◆Procedure 7-2-1-3: The aforementioned M in the case of antennaPortsDCI0-3=type1a A(r), or in the case of antennaPortsDCI0-3=type2, each of the aforementioned blocks is defined as follows:

[0114] ---◆Procedure 7-2-1-3-1: If the conversion precoder is enabled, and dmrs-Type=1, and maxLength=1, then unless both dmrs-UplinkTransformPrecoding and tp-pi2BPSK are set and π / 2 BPSK modulation is used, M A (r) Or each block is 2 bits, as defined in Table AU-6.

[0115] ---◆Procedure 7-2-1-3-2: If the conversion precoder is enabled, and both dmrs-UplinkTransformPrecoding and tp-pi2BPSK are set, 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. Here, n SCID This is a scrambling identifier (identity) for the antenna port as defined in the physical channel and modulation specifications.

[0116] ---◆Procedure 7-2-1-3-3: If the conversion precoder is enabled, and dmrs-Type=1, and maxLength=2, then unless both dmrs-UplinkTransformPrecoding and tp-pi2BPSK are set and π / 2 BPSK modulation is used, M A (r) Or each block is 4 bits, as defined in Table AU-7.

[0117] ---◆Procedure 7-2-1-3-4: If the conversion precoder is enabled, and both dmrs-UplinkTransformPrecoding and tp-pi2BPSK are set, 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. Here, n SCID This is a scrambling identifier (identity) for the antenna port as defined in the physical channel and modulation specifications.

[0118] ---◆Procedure 7-2-1-3-5: If the conversion 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, and according to the precoding information and layer number fields when the upper layer parameter txConfig=codebook, M A (r) Or each block is 3 bits, as defined in the table AU-8 / 9 / 10 / 10A / 11 according to the rank value.

[0119] ---◆Procedure 7-2-1-3-6: If the conversion 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, and according to the precoding information and layer number fields when the upper layer parameter txConfig=codebook, M A (r) Or each block is 4 bits, as defined in the table AU-12 / 13 / 14 / 14A / 15 / 15A / 15B / 15C / 15D according to the rank value.

[0120] ---◆Procedure 7-2-1-3-7: If the conversion 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, and according to the precoding information and layer number fields when the upper layer parameter txConfig=codebook, M A(r) Or each block is 4 bits, as defined in the table AU-16 / 17 / 18 / 18A / 19 / 19A / 19B according to the rank value.

[0121] ---◆Procedure 7-2-1-3-8: If the conversion 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, and according to the precoding information and layer number fields when the upper layer parameter txConfig=codebook, M A (r) Or each block is 5 bits, as defined in the table AU-20 / 21 / 22 / 22A / 23 / 23A / 23B / 23C / 23D according to the rank value.

[0122] ―◆Procedure 7-2-2: Here, the values ​​1, 2, and 3 for 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] ―◆Procedure 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} is equal to. Here, x A x is the bit width of the "antenna port" [field] derived according to dmrs-UplinkForPUSCH-MappingTypeA, and B This is the bit width of the "antenna port" [field] derived according to dmrs-UplinkForPUSCH-MappingTypeB. The mapping type of the PDSCH is x A and x B If it corresponds to the smaller value, then in the most significant bit (MSB) of this field, |x A -xB The zeros in the | symbol are padded.

[0124] In the specifications for the physical layer procedure for data, DCI format 0_3 can schedule multi-carrier pushes using the Rel. 18 DMRS port. However, in the specifications for multiplexing and channel coding, DCI format 0_3 does not support the Rel. 18 DMRS port.

[0125] (Multicast) As shown in the example in Figure 7, after the random access (RA) procedure, the UE may receive a common frequency resource (CFR) [multicast] setting and a PUCCH setting [by a UE individual RRC message]. The CFR setting may include at least one of the CFR location and bandwidth, a PDCCH setting, a PDSCH setting, and an SPS setting. The UE may then receive multicast traffic [scheduled using DCI format 4_1 / 4_2 with a CRC scrambled by G-RNTI / G-CS-RNTI]. The UE may send a HARQ-ACK for that 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] Within the PDSCH settings (PDSCH-Config) in the DL BWP individual settings (BWP-DownlinkDedicated), DMRS-DownlinkConfig is set. 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 for Rel. 18 DMRS to be set for DCI format 1_1, but not for DCI format 1_2.

[0128] While PDSCH-Config allows for the configuration of PDSCH settings for DCI format 1_3 (pdsch-ConfigDCI-1_3-r18), it does not have a DMRS-DownlinkConfig setting specific to DCI format 1_3. This means that DCI format 1_3 reuses the DMRS-DownlinkConfig in PDSCH-Config for DCI format 1_1. In other words, a single RRC parameter enables the Rel. 18 DMRS port for PDSCH scheduled by DCI format 1_1 / 1_3.

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

[0130] In other words, the following RRC parameters for PDSCH can enable the Rel. 18 DMRS port for PDSCH scheduled by the corresponding DCI format: ◆ For DCI formats 1_1 / 1_3, dmrs-DownlinkForPDSCH-MappingTypeA or dmrs-DownlinkForPDSCH-MappingTypeB (DMRS-DownlinkConfig) in PDSCH-Config within BWP-DownlinkDedicated. ◆ For DCI format 1_2, dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2-r16 or dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2-r16 (DMRS-DownlinkConfig) in PDSCH-Config within BWP-DownlinkDedicated. ◆For DCI format 4_2, dmrs-DownlinkForPDSCH-MappingTypeA or dmrs-DownlinkForPDSCH-MappingTypeB (DMRS-DownlinkConfig) within pdsch-ConfigMulticast-r17 (PDSCH-Config) within CFR-ConfigMulticast-r17 within BWP-DownlinkDedicated.

[0131] Similarly, the following RRC parameters for PUSCH can enable the Rel. 18 DMRS port for PUSCH, which is scheduled according to the corresponding DCI format: ◆ For DCI formats 0_1 / 0_3, dmrs-UplinkForPUSCH-MappingTypeA or dmrs-UplinkForPUSCH-MappingTypeB (DMRS-UplinkConfig) in PUSCH-Config within BWP-UplinkDedicated. ◆ For DCI format 0_2, dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2-r16 or dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2-r16 (DMRS-UplinkConfig) in PUSCH-Config within BWP-UplinkDedicated.

[0132] (UE Capability) The UE may report a complexity UE capability regarding the maximum number of DMRS types to be set for PDSCH across all DL DCI formats per cell. A component of this UE capability may include the maximum number of DMRS types to be set 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 to be set for PDSCH across all DL DCI formats per cell is defined as the total number of different DMRS types reported.

[0133] (Issue) The joint functionality between DCI Format 1_3 / 4_2 / 0_3 and Rel. 18 DMRS has not been sufficiently considered and is not adequately defined in the specification.

[0134] When Rel. 18 DMRS is enabled or configured, an increase in UE complexity is possible in terms of extended DMRS channel estimation for processing four new FD-OCC patterns. For example, estimation of associated parameters 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 leads to higher implementation complexity and higher UE processing capacity. Since the Rel. 18 DMRS function is enabled through upper-layer signaling, the corresponding processing resources are prepared based on its configuration. Similarly, PDCCH processing in a single Rel. 18 DCI (e.g., counting of CCE limits) is performed based on the activation / configuration of the function. Therefore, whether it is dynamic scheduling in DCI format 1_1 or dynamic scheduling in DCI format 1_3, Rel. 18 DMRS and Rel. When both functions of Rel. 18 Single DCI are configured by RRC, the corresponding processing resources are affected by both functions. Simultaneous configuration of both Rel. 18 DMRS and Rel. 18 Single DCI may result in additional preparation / processing for the UE implementation.

[0135] To address this issue, a new UE capability is being considered to support the 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 for the new capability is FeatureSet.

[0136] Thus, if the functionality using Rel. 18 DMRS is not sufficiently considered / defined, there is a risk that the UE may not be able to properly receive PDSCH [DMRS].

[0137] Therefore, the inventors investigated scheduling methods for PDSCH [DMRS] and conceived the following embodiments.

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

[0139] (Various substitutions) In this disclosure, words enclosed in parentheses () may indicate an explanation of the preceding word (e.g., an explanation of spelling), a paraphrase, a specific example, or supplementary explanation. Also, in this disclosure, words enclosed in square brackets [] may be interpreted as part of the overall meaning of the text, or they may be interpreted as being excluded (ignored). Note that parentheses () and square brackets [] may be used for purposes / meanings other than those described above.

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

[0141] In this disclosure, terms such as notice, activate, deactivate, indicate (or specify), select, configure, update, and determine may be interpreted interchangeably. In this disclosure, terms such as support, control, controllable, operate, and capable of operating may be interpreted interchangeably.

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

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

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

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

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

[0147] In the present disclosure, A b , A_b, Ab, the notation with b attached to the lower right of A, may be read as each other. In the present disclosure, A c , A^c, the notation with c attached to the upper right of A, may be read as each other. In the present disclosure, A b c , A_b^c, the notation with b attached to the lower right of A and c attached to the upper right of A, may be read as each other. In the present disclosure, x ~ may be represented by attaching ~ above x or may be called x tilde. In the present disclosure, x - may be represented by attaching - above x or may be called x bar. In the present disclosure, x ＾This can also be represented by placing a caret (^) above x, or it may be called an x-hat.

[0148] In this disclosure, FR may be at least one of FR1, FR2, FR2-1, FR2-2, FR3, subterahertz, and terahertz. In this disclosure, the frequency range corresponding to FR1 may be 410–7125 MHz. In this disclosure, FR2 may include FR2-1 and FR2-2, 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] In this disclosure, the following abbreviations may be used: ◆FDM: frequency division multiplexing ◆TDM: time division multiplexing ◆CDM: code division multiplexing

[0150] In this disclosure, the terms "indicate," "report," and "select" may be interpreted as interchangeable.

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

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

[0153] Based on the settings and the DCI format, the UE may determine 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 plurality of PDSCHs.

[0154] <Embodiment 1> The above-described specifications for multiplexing and channel coding may be updated to support DCI format 1_3 being able to schedule a PDSCH using a Rel. 18 DMRS port (FD-OCC of length 4).

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

[0156] --◆Procedure 2-2-1-3A: The aforementioned M in the case of antennaPortsDCI-1-3=type1a A (r), or in the case of antennaPortsDCI-1-3=type2, each of the aforementioned blocks is defined as follows: ---◆As defined by tables AD-1 / 2 / 3 / 4 / 7 / 8 / 9 / 10 and tables AD-1A / 2A / 3A / 4A / 7A / 8A / 9A / 10A, M A (r) Or each block is 4, 5, 6, 7, or 8 bits. 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. Antenna ports {p0,...,p v-1} is determined according to the order of the 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] Figures 8 and 9 show an example of an antenna port table (AD-7) for PDSCH when the extended DMRS type (dmrs-TypeEnh) is configured.

[0158] In Embodiment 1, a new UE capability to support the simultaneous configuration of Rel. 18 DMRS and Rel. 18 Single DCI [for the aforementioned DCI Format 1_3] does not need to be introduced (and may not be required).

[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 is required for the simultaneous configuration of Rel. 18 DMRS and Rel. 18 single DCI [for DCI format 1_3].

[0160] <<Variations>> In Embodiment 1, simultaneous configuration of both Rel. 18 DMRS and Rel. 18 Single DCI may increase the complexity / processing capacity of the UE, and a new UE capability to support the simultaneous configuration of Rel. 18 DMRS and Rel. 18 Single DCI [for DCI Format 1_3], or a new UE capability for a combination of Rel. 18 DMRS and Rel. 18 Single DCI [for DCI Format 1_3], may be introduced (and may be required).

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

[0162] <Embodiment 2> The specification of the data physical layer procedure described above may be updated to exclude the fact that DCI format 1_3 can schedule a PDSCH using a Rel. 18 DMRS port (FD-OCC of length 4).

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

[0164] ◆Procedure 1-1A: 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 (in the case where the upper layer parameter dmrs-TypeEnh is set). When the UE receives a PDSCH scheduled by a PDCCH having DCI format 1_3, it ignores dmrs-TypeEnh. 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 4_2, etc.

[0165] ◆Procedure 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 by DCI format 4_2 with a PDCCH having a CRC scrambled by multicast G-RNTI or G-CS-RNTI, the UE may set the upper layer parameter dmrs-Type / dmrs-TypeEnh, and the set DMRS setting type is used for receiving the PDSCH.

[0166] In Embodiment 2, the simultaneous configuration of both Rel. 18 DMRS and Rel. 18 Single DCI may increase the complexity / processing capacity of the UE, and new UE capabilities may be introduced (or may be required) to support the simultaneous configuration of Rel. 18 DMRS and Rel. 18 Single DCI [for the aforementioned] [DCI format 1_3].

[0167] In Embodiment 2, DCI format 1_3 does not support Rel. 18 DMRS, and a new UE capability may be required for the simultaneous configuration of Rel. 18 DMRS and Rel. 18 Single DCI [for DCI format 1_3].

[0168] <<Premium>>

[0169] In step 1-1A, "ignore dmrs-TypeEnh" may be replaced with "assume that dmrs-TypeEnh is not set" or "do not expect that dmrs-TypeEnh will be set."

[0170] <<Variation>> In Embodiment 2, a new UE capability to support the simultaneous configuration of Rel. 18 DMRS and Rel. 18 Single DCI [for DCI Format 1_3] [as described above] does not need to be introduced (or is not required).

[0171] <Embodiment 3> The above-described specifications for multiplexing and channel coding may be updated to support DCI format 4_2 being able to schedule a PDSCH using a Rel. 18 DMRS port (FD-OCC of length 4).

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

[0173] --◆Procedure 3-2-1-1A: As defined by Table AD-1 / 2 / 3 / 4 / 7 / 8 / 9 / 10, the antenna port [field] is 4, 5, 6, 7, or 8 bits. 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. Antenna port {p0,...,p v-1} is determined according to the order of the DMRS ports given by table AD-1 / 2 / 3 / 4 / 7 / 8 / 9 / 10.

[0174] In Embodiment 3, a new UE capability to support the simultaneous configuration of Rel. 18 DMRS and Rel. 18 Single DCI for DCI format 4_2 does not need to be introduced (or is not 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 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 is required for the simultaneous configuration of Rel. 18 DMRS and Rel. 18 single DCI [for DCI format 4_2].

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

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

[0178] <Embodiment 4> The specification of the data physical layer procedure described above may be updated to exclude the fact that DCI format 4_2 can schedule a PDSCH using a Rel. 18 DMRS port (FD-OCC of length 4).

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

[0180] ◆Procedure 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 (in the case where the upper layer parameter dmrs-TypeEnh is set). When the UE receives a PDSCH scheduled by DCI format 1_3 with a PDCCH having CRC scrambled by C-RNTI, MCS-C-RNTI, or CS-RNTI, or a PDSCH scheduled by DCI format 4_2 with a PDCCH having CRC scrambled by G-RNTI for multicast or G-CS-RNTI, it ignores dmrs-TypeEnh. The DMRS reception procedure for a PDSCH scheduled by a PDCCH having DCI format 1_1 is similarly applicable to a PDSCH scheduled by a PDCCH having DCI format 4_2, etc.

[0181] ◆Procedure 1-2B: When receiving a PDSCH scheduled in DCI format 1_1 by a PDCCH having a CRC scrambled by C-RNTI, MCS-C-RNTI, or CS-RNTI, the UE may set the upper layer parameter dmrs-Type / dmrs-TypeEnh, and the set DMRS setting type is used for receiving the PDSCH.

[0182] In Embodiment 4, the simultaneous configuration of both Rel. 18 DMRS and Rel. 18 Single DCI may increase the complexity / processing capacity of the UE, and new UE capabilities may be introduced (or may be required) to support the 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 a new UE capability may be required for the simultaneous configuration of Rel. 18 DMRS and Rel. 18 Single DCI [for DCI format 4_2 as described above].

[0184] <<Premium>>

[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, a new UE capability to support the simultaneous configuration of Rel. 18 DMRS and Rel. 18 Single DCI [for DCI Format 4_2] does not need to be introduced (or is not required).

[0187] <Embodiment 5> The above-described specifications for multiplexing and channel coding may be updated to support the scheduling of a PUSCH using the Rel. 18 DMRS port (FD-OCC of length 4) in DCI format 0_3.

[0188] In the aforementioned specifications for multiplexing and channel coding, the following procedures 7-2-1-3-5A to 7-2-1-3-12A may be specified instead of procedures 7-2-1-3-5 to 7-2-1-3-8.

[0189] ---◆Procedure 7-2-1-3-5A: If the conversion 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, and according to the precoding information and layer number fields when the upper layer parameter txConfig=codebook, M A (r) Or each block is 3 bits, as defined in the table AU-8 / 9 / 10 / 10A / 11 according to the rank value.

[0190] ---◆Procedure 7-2-1-3-6A: If the conversion 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, and according to the precoding information and layer number fields when the upper layer parameter txConfig=codebook, M A (r) Or each block is 4 bits, as defined in the table AU-12 / 13 / 14 / 14A / 15 / 15A / 15B / 15C / 15D according to the rank value.

[0191] ---◆Procedure 7-2-1-3-7A: If the conversion 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, and according to the precoding information and layer number fields when the upper layer parameter txConfig=codebook, M A (r) Or each block is 4 bits, as defined in the table AU-16 / 17 / 18 / 18A / 19 / 19A / 19B according to the rank value.

[0192] ---◆Procedure 7-2-1-3-8A: If the conversion 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, and according to the precoding information and layer number fields when the upper layer parameter txConfig=codebook, M A (r) Or each block is 5 bits, as defined in the table AU-20 / 21 / 22 / 22A / 23 / 23A / 23B / 23C / 23D according to the rank value.

[0193] ---◆Procedure 7-2-1-3-9A: If the conversion 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, and according to the precoding information and layer number fields when the upper layer parameter txConfig=codebook, M A (r) Or each block is 4 bits, as defined in the table AU-38 / 39 / 40 / 40A / 41 / 42 / 43 / 44 / 45 according to the rank value.

[0194] ---◆Procedure 7-2-1-3-10A: If the conversion 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, and according to the precoding information and layer number fields when the upper layer parameter txConfig=codebook, M A(r) Or each block is 5 bits, as defined in the table AU-46 / 47 / 48 / 48A / 49 / 50 / 51 / 52 / 53 according to the rank value.

[0195] ---◆Procedure 7-2-1-3-11A: If the conversion 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, and according to the precoding information and layer number fields when the upper layer parameter txConfig=codebook, M A (r) Or each block is 5 bits, as defined in the table AU-54 / 55 / 56 / 56A / 57 / 58 / 59 / 60 / 61 according to the rank value.

[0196] ---◆Procedure 7-2-1-3-12A: If the conversion 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, and according to the precoding information and layer number fields when the upper layer parameter txConfig=codebook, M A (r) Or each block is 6 bits, as defined in the table AU-62 / 63 / 64 / 64A / 65 / 66 / 67 / 68 / 69 according to the rank value.

[0197] Figure 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 to support the simultaneous configuration of Rel. 18 DMRS and Rel. 18 Single DCI for DCI format 0_3 does not need to be introduced (or is not 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 is required for the simultaneous configuration of Rel. 18 DMRS and Rel. 18 single DCI [for DCI format 0_3].

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

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

[0202] <<Variations>> A new UE capability may be reported by the UE indicating the maximum number of new DMRS types (extended DMRS types) that can be set for a single DCI format 0_3.

[0203] <<Premium>>

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

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

[0207] ---◆Procedure 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 the table AU-54 / 55 / 56 / 56A / 57 / 58 / 59 / 60 / 61 according to the rank value.

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

[0209] <Embodiment 6> The specification of the data physical layer procedure described above may be updated to exclude the fact that DCI format 0_3 can schedule a PUSCH using a Rel. 18 DMRS port (FD-OCC of length 4).

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

[0211] ◆Procedure 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 (in the case where dmrs-TypeEnh is set). When the UE transmits a PUSCH scheduled by a PDCCH having DCI format 0_3, it ignores dmrs-TypeEnh.

[0212] In Embodiment 6, the simultaneous configuration of both Rel. 18 DMRS and Rel. 18 Single DCI may increase the complexity / processing capacity of the UE, and new UE capabilities may be introduced (or may be required) to support the 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 may be required for the simultaneous configuration of Rel. 18 DMRS and Rel. 18 single DCI [for DCI format 0_3 as described above].

[0214] <<Premium>>

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

[0216] <<Variations>> In Embodiment 6, a new UE capability to support the simultaneous configuration of Rel. 18 DMRS and Rel. 18 Single DCI [for DCI Format 0_3] does not need to be introduced (or is not required).

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

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

[0219] If the above notification is made by DCI, the notification may be made by a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used to scramble the Cyclic Redundancy Check (CRC) bits assigned to the DCI, or the format of the DCI. 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-described embodiment may be periodic, semi-persistent (triggered by the UE or gNB), or aperiodic (triggered by the UE or gNB).

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

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

[0223] In the embodiments described above, information from the network may be set / instructed by the following methods: ◆ Common to multiple UEs, or individual to a UE ◆ 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>> Notification of any information from the UE to the NW in the embodiments described above (in other words, transmission / reporting of any information from the UE to the BS) may be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MAC CE, RRC messages, LPP messages), specific signals / channels (e.g., UCI, PUCCH, PUSCH, PRACH, reference signals), or a combination thereof.

[0225] When the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new LCID not specified in existing standards in the MAC subheader. The MAC CE may be an extension of an existing MAC CE. For example, the MAC CE may introduce a new octet into an existing MAC CE.

[0226] If the above notice is made by the UCI, the notice may be transmitted using PUCCH or PUSCH.

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

[0228] <<Regarding the application of each embodiment>> In UE / BS, specific (one or more) processes / operations / controls / assumptions / information for at least one of the embodiments described above may be applied (or used) if any or more of the following conditions are met: ◆ A higher-layer parameter indicating the specific process / operation / control / assumption / information is set; ◆ The specific process / operation / control / assumption / information is determined based on the relevant higher-layer parameter; ◆ The specific process / operation / control / assumption / information is instructed / specified / activated / triggered by MAC CE / DCI / UCI / Resource / Channel / RS; ◆ A specific UE capability indicating (or related to) the specific process / operation / control / assumption / information is reported or supported; ◆ The application of the specific process / operation / control / assumption / information is determined based on specific conditions.

[0229] The above-mentioned specific UE capabilities may represent at least one of the following: ◆ Supporting the above-mentioned specific processing / operation / control / assumption / information; ◆ The capability of each embodiment; ◆ The capability of each option in each embodiment, or the capability of a combination of multiple options in each embodiment; ◆ The capability of each choice in each embodiment, or the capability of a combination of multiple choices in each embodiment.

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

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

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

[0233] Information regarding 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 set 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 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 conditions described / defined in the specification. ◆ The information is determined by a combination of several of the above methods. For example, the information is determined by the setting / indication of higher layer parameters / MAC CE / DCIs and reported by UE capabilities.

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

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

[0236] (Note) The following inventions are added with respect to embodiments (3 / 4) of the present disclosure. <Note 1> A terminal having: a receiving unit that receives a demodulation reference signal (DMRS) setting and a downlink control information (DCI) format for scheduling physical downlink shared channels (PDSCHs) for multicast within a downlink cell; and a control unit that determines, based on 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 plurality of PDSCHs. <Note 2> The terminal according to Note 1, wherein the control unit determines the number of bits in the antenna port field based on the association between the value of the antenna port field in the DCI format and the DMRS port number to which the FD-OCC of length 4 is applied. <Note 3> The terminal according to Note 1 or Note 2, wherein the control unit determines that the FD-OCC of length 4 is not applied to the DMRS. <Note 4> The control unit is a terminal as described in any of Notes 1 to 3, which controls the reporting of capability information indicating support for simultaneous setting of a DMRS to which the length 4 FD-OCC is applied and the DCI format. <Supplement> The receiving unit may be a transmitting / receiving unit 220. The control unit may be a control unit 210. The DCI format may be DCI format 4_2. The association may be tables AD-7 / 8 / 9 / 10. The decision that the length 4 FD-OCC is not applied to the DMRS may be rephrased as ignoring dmrs-TypeEnh, assuming that dmrs-TypeEnh is not set, or not expecting dmrs-TypeEnh to be set. The DMRS to which the length 4 FD-OCC is applied may be rephrased as Rel. 18 DMRS, with dmrs-TypeEnh set.<Note A> A base station comprising: a transmitting unit that transmits a demodulation reference signal (DMRS) setting and a downlink control information (DCI) format for scheduling physical downlink shared channels (PDSCHs) for multicast within a downlink cell; and a control unit that determines, based on 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 plurality of PDSCHs. <Supplement> The transmitting unit may be a transceiver unit 120. The control unit may be a control unit 110.

[0237] (Note) The following inventions are added with respect to embodiments (5 / 6) of the present disclosure. <Note 1> A terminal having: a receiving unit that receives a demodulation reference signal (DMRS) setting and a downlink control information (DCI) format for scheduling a plurality of PUSCHs in a plurality of cells having one physical uplink shared channel (PUSCH) per cell; and a control unit that determines, based on the setting and the DCI format, whether a 4-length frequency domain (FD)-orthogonal cover code (OCC) is applied to the DMRS for the plurality of PUSCHs. <Note 2> The terminal according to Note 1, wherein the control unit determines the number of bits in the antenna port field based on the association between the value of the antenna port field in the DCI format and the DMRS port number to which the 4-length FD-OCC is applied. <Note 3> The terminal according to Note 1 or Note 2, wherein the control unit determines that the 4-length FD-OCC is not applied to the DMRS. <Note 4> The control unit is a terminal as described in any of Notes 1 to 3, which controls the reporting of capability information indicating support for simultaneous configuration of a DMRS to which the FD-OCC of length 4 is applied and the DCI format. <Supplement> The receiving unit may be a transmitting / receiving unit 220. The control unit may be a control unit 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 is M A(r) may be read as, or each block in the antenna port field. The decision that the FD-OCC of length 4 is not applied to the DMRS may be read as ignoring dmrs-TypeEnh, assuming that dmrs-TypeEnh is not set, or not expecting that dmrs-TypeEnh is set. The DMRS to which the FD-OCC of length 4 is applied may be read as Rel. 18 DMRS, where dmrs-TypeEnh is set. <Note A> A base station having: a transmitting unit that transmits a demodulation reference signal (DMRS) setting and a downlink control information (DCI) format for scheduling a plurality of PUSCHs in a plurality of cells having one physical uplink sharing channel (PUSCH) per cell; and a control unit that determines, based on 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 plurality of PUSCHs. <Note> The transmitting unit may be a transmitting / receiving unit 120. The control unit may be a control unit 110.

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

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

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

[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 where both MN and SN are NR base stations (gNB) (NR-NR Dual Connectivity (NN-DC))).

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

[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 by multiple antennas / base stations 10. One [virtual] cell (which may be called a supercell, for example) may be composed of multiple [virtual] cells (which may be called subcells, for example). A supercell may correspond to a cell with a fixed physical range, and a subcell may correspond to a cell whose physical range fluctuates quasi-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 the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). A macrocell C1 may be included in FR1, and a small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and FR2 may be a frequency band above 24 GHz. Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may be in a frequency band higher than FR2.

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

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

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

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

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

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

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

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

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

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

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

[0258] Furthermore, the DCI that schedules PDSCH may be called DL assignment, DL DCI, etc., and the DCI that schedules PUSCH may be called UL grant, UL DCI, etc. Furthermore, PDSCH may be read as DL data, and PUSCH may be read as UL data.

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

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

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

[0262] In this disclosure, downlinks, uplinks, etc., may be expressed without the prefix "link." Also, the prefix "physical" may be omitted from the names of various channels.

[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, the DL-RS may include 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.

[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 SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS / PBCH block, SS Block (SSB), etc. Note that SS, SSB, etc. may also be called reference signals.

[0265] Furthermore, in the wireless communication system 1, the uplink reference signal (UL-RS) may include a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. The DMRS may also be called a user-specific reference signal (UE-specific Reference Signal).

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

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

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

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

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

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

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

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

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

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

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

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

[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 130.

[0279] The transmitting / receiving unit 120 (receiving 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 (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.

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

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

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

[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 implement RF processing (digital beamforming, digital-to-analog conversion, analog beamforming, etc.) and lower-level physical layer functions (precoding, IFFT, FFT, etc.). The DU may implement higher-level physical layer functions (coding to resource element mapping, etc.), MAC layer functions, and RLC layer functions. The CU may implement PDCP layer, Service Data Adaptation Protocol (SDAP) layer, and RRC layer functions.

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

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

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

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

[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 transmitting / receiving unit 220 and the transmitting / receiving antenna 230. The control unit 210 may generate data to be transmitted as signals, control information, sequences, etc., and transfer them to the transmitting / receiving unit 220.

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

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

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

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

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

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

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

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

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

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

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

[0301] The measurement unit 223 may derive channel measurements for CSI calculation based on channel measurement resources. 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 interference measurement resources. Interference measurement resources may be at least one of the following: NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, etc. CSI-IM may also be called CSI-Interference Management (IM), and may be interpreted interchangeably with Zero Power (ZP) CSI-RS. In this disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc., may be interpreted interchangeably.

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

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

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

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

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

[0307] For example, although only one processor 1001 is shown in the diagram, there may be multiple processors. Furthermore, the processing may be performed by one processor, or it may be performed by two or more processors simultaneously, sequentially, or by other means. Note that the processor 1001 may be implemented using 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 the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations and control communication via the communication device 1004, or control at least one of reading and writing data in the memory 1002 and storage 1003.

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

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

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

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

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

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

[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 different buses may be configured for 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), and a field programmable gate array (FPGA), and some or all of each functional block may be implemented using such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0317] Furthermore, devices included in the core network 30 (for example, network nodes that provide NF) may also be implemented using the functional block / hardware configuration described above.

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

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

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

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

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

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

[0324] For example, one subframe may be called a TTI, multiple consecutive subframes may be called a TTI, and one slot or one mini-slot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe in existing LTE (1 ms), a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing a TTI may be called a slot, mini-slot, 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, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

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

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

[0328] A TTI with a time length of 1 ms may be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc.

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

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

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

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

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

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

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

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

[0337] The structures of wireless frames, subframes, slots, minislots, and symbols described above are merely examples. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless 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, and the number of symbols, symbol length, and cyclic prefix (CP) length within the TTI can be varied in various ways.

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

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

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

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

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

[0343] Any information described in this disclosure (e.g., variables, constants, parameters) may be communicated from any first device (e.g., UE / base station) to any second device (e.g., base station / UE) that indicates / specifies (or relates to) the value of such any information, even if not specifically stated in the embodiments described above.

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

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

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

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

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

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

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

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

[0352] In this disclosure, "antenna port" may be interpreted interchangeably with "antenna port for any signal / channel" (e.g., a Demodulation Reference Signal (DMRS) port). In this disclosure, "resource" may be interpreted interchangeably with "resource for any signal / channel" (e.g., a reference signal resource, an SRS resource, etc.). Resources may include time / frequency / code / spatial / power resources. Furthermore, a spatial domain transmit filter may include at least one of a spatial domain transmit filter and a spatial domain receive filter.

[0353] The above group may include, for example, at least one of the following: 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, or a panel group.

[0354] Furthermore, in this disclosure, terms such as beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, Codeword (CW), Transport Block (TB), and RS may be interpreted interchangeably.

[0355] Furthermore, in this disclosure, 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 interpreted interchangeably.

[0356] Furthermore, in this disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) properties," and "specific QCL type (e.g., Type A, Type D)" may be interpreted interchangeably.

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

[0358] Furthermore, the spatial relationship information Identifier (ID) (TCI state ID) and spatial relationship information (TCI state) may be interpreted as mutually exclusive. "Spatial relationship information (TCI state)" may be interpreted as mutually exclusive as "a set of spatial relationship information (TCI state)," "one or more pieces of spatial relationship information," etc. TCI state and TCI may be interpreted as mutually exclusive. Spatial relationship information and spatial relationship may be interpreted as mutually exclusive.

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

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

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

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

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

[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. At least one of the base station and the mobile station may also be a device mounted on a moving object, the moving object itself, etc.

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

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

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

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

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

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

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

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

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

[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 sends and receives data (information) via the communication port 63 to the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axle 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and various sensors 50-58 provided in the vehicle 40.

[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 external devices. For example, it can send and receive various types of information to and from external devices via wireless communication. The communication module 60 may be located either inside or outside the electronic control unit 49. The external device may be, for example, the base station 10 or the user terminal 20 described above. Alternatively, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 (it may function as at least one of the base station 10 and the user terminal 20).

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

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

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

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

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

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

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

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

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

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

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

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

[0388] Also, "judgment (decision)" may be regarded as "resolving", "selecting", "choosing", "establishing", "comparing", etc. That is, "judgment (decision)" may be regarded as performing some action. In the present disclosure, "judgment (decision)" may be mutually read as the above-described actions.

[0389] Also, in the present disclosure, "judgment (decision) (determine / determining)" may be mutually read as "assume / assuming", "expect / expecting", "consider / considering", etc. In the present disclosure, "not assume that..." may be mutually read as "assume that not...".

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

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

[0392] As used in the present disclosure, the terms "connected" and "coupled", or any variations thereof, mean 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 "accessed".

[0393] In the present disclosure, when two elements are connected, they can be considered to be "connected" or "coupled" to each other using one or more wires, cables, printed electrical connections, etc., and also using electromagnetic energy having wavelengths in the radio frequency region, microwave region, optical (both visible and invisible) region, etc., as some non-limiting and non-exhaustive examples.

[0394] In the present disclosure, the term "A and B are different" may mean that "A and B are different from each other". Note that the term may also mean that "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] In the present disclosure, when the terms "include", "including" and their variations are used, these terms are intended to be inclusive, similar to the term "comprising". Further, the term "or" used in the present disclosure is intended not to be an exclusive disjunction.

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

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

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

[0399] In this disclosure, phrases 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. Furthermore, A, B, etc., may be replaced with appropriate expressions such as nouns, gerunds, or regular sentences depending on the context. The time difference between A and B may be approximately zero (immediately after or immediately before). Additionally, a time offset may be applied to the time when A occurs. For example, "A" may be interpreted as "before / after the time offset when A occurs". The time offset (e.g., one or more symbols / slots) may be predetermined or determined by the UE based on notified information.

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

[0401] Although the invention described herein has been explained in detail above, it will be clear to those skilled in the art that the invention described herein is not limited to the embodiments described herein. The descriptions herein are illustrative and not intended to be restrictive in any way to the invention described herein.

[0402] This application is based on Japanese Patent Application No. 2024-208469, filed on November 29, 2024. All of its contents are included herein.

Claims

1. A terminal having: a receiving unit that receives a demodulation reference signal (DMRS) setting and a downlink control information (DCI) format for scheduling multiple PUSCHs in multiple cells, each having one physical uplink shared channel (PUSCH) per cell; and a control unit that determines, based on 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.

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

3. The terminal according to claim 1, wherein the control unit 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 the reporting of capability information indicating support for simultaneous configuration of a DMRS to which the length 4 FD-OCC is applied and the DCI format.

5. A wireless communication method for a terminal, comprising the steps of: receiving a demodulation reference signal (DMRS) setting; receiving a downlink control information (DCI) format for scheduling multiple PUSCHs in a plurality of cells, each having one physical uplink shared channel (PUSCH) per cell; and determining, based on 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 plurality of PUSCHs.

6. A base station having: a transmitting unit that transmits a demodulation reference signal (DMRS) setting and a downlink control information (DCI) format for scheduling multiple PUSCHs in multiple cells, each having one physical uplink shared channel (PUSCH) per cell; and a control unit that determines, based on 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.

Images