Terminal, wireless communication method, and base station

WO2026160269A1PCT designated stage Publication Date: 2026-07-30NTT DOCOMO INC
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
NTT DOCOMO INC
Filing Date
2026-01-16
Publication Date
2026-07-30

Smart Images

  • Figure JP2026001335_30072026_PF_FP_ABST
    Figure JP2026001335_30072026_PF_FP_ABST
Patent Text Reader

Abstract

A terminal according to one aspect of the present disclosure comprises: a reception unit that receives an indication of a physical uplink shared channel for carrying a first transport block and a second transport block; and a control unit that, when the first transport block is present and the second transport block is not present, determines whether to transmit a demodulation reference signal (DMRS) for the physical uplink shared channel in one or more specific layers associated with the second transport block among a plurality of layers for the physical uplink shared channel.
Need to check novelty before this filing date? Find Prior Art

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] In 3GPP Rel. 15 / 16, the maximum number of UL layers is four. Future wireless communication systems (e.g., 3GPP Rel. 18 and later) are considering supporting more than four layers in UL transmissions from terminals (user terminals, User Equipment (UE)). However, the behavior of demodulation reference signals (DMRS) transmission when a physical uplink sharing channel (PUSCH) using more than four layers is specified remains unclear. This could lead to reduced resource utilization efficiency.

[0006] Therefore, one of the objectives of this disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately control the DMRS when a PUSCH using more than four layers is instructed.

[0007] A terminal according to one aspect of the present disclosure includes a receiving unit that receives instructions for a physical uplink sharing channel for transporting a first transport block and a second transport block, and a control unit that determines whether, if the first transport block is present and the second transport block is not, a demodulation reference signal (DMRS) for the physical uplink sharing channel is transmitted in one or more specific layers among a plurality of layers for the physical uplink sharing channel that are associated with the second transport block.

[0008] According to one aspect of this disclosure, the DMRS can be appropriately controlled when a PUSCH using more than four layers is instructed.

[0009] Figure 1 shows an example of gNB recognition in the case where the received signal strength of the PUSCH DMRS exceeds a certain value. Figure 2 shows an example of gNB recognition in the case where the received signal strength of the PUSCH DMRS does not exceed a certain value. Figure 3 shows an example of UL skipping in 2TB PUSCH. Figure 4 shows the first part of an example of CW to layer mapping for spatial multiplexing. Figure 5 shows the second part of an example of CW to layer mapping for spatial multiplexing. Figure 6 shows the third part of an example of CW to layer mapping for spatial multiplexing. Figure 7 shows an example of UL skipping according to Embodiment 1. Figure 8 is a diagram showing an example of the schematic configuration of a wireless communication system according to one embodiment. Figure 9 is a diagram showing an example of the configuration of a base station according to one embodiment. Figure 10 is a diagram showing an example of the configuration of a user terminal according to one embodiment. Figure 11 is a diagram showing an example of the hardware configuration of a base station and user terminal according to one embodiment. Figure 12 is a diagram showing an example of a vehicle according to one embodiment.

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

[0011] 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). 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 in 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.

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

[0013] 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. In DMRS configuration type 2, a DMRS is placed in two consecutive REs for every six consecutive REs in the frequency domain.

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

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

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

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

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

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

[0020] In the present disclosure, DMRS [configuration] type 1, DMRS type = 1, DMRS Type 1, that the dmrs-Type set to type2 is not set, may be read interchangeably with each other. In the present disclosure, DMRS [configuration] type 2, DMRS type = 2, DMRS Type 2, that the dmrs-Type set to type2 is set, may be read interchangeably with each other.

[0021] In the present disclosure, new DMRS, extended DMRS, Rel. 18 DMRS, extended DMRS function, extended DMRS [configuration] type, settings / upper layer parameters for the extended DMRS type, enhanced-dmrs-Type_r18, dmrs-TypeEnh, extended DMRS configuration type 1 / 2, DMRS with FD-OCC of length 4, Rel. 18 DMRS type, new DMRS port, Rel. 18 DMRS port, DMRS port to which new FD-OCC is applied, DMRS port outside the port number range of legacy DMRS, extended DMRS port, that the extended DMRS type (dmrs-TypeEnh) is set, that enhanced-dmrs-Type_r18 is set, that extended DMRS configuration type 1 or 2 is set, that the extended DMRS type is set, that the extended DMRS port is indicated, may be read interchangeably with each other.

[0022] In the present disclosure, the extended DMRS [configuration] type 1, DMRS extended type 1, DMRS extended type = 1, DMRS eType 1, the extended DMRS type is set and the dmrs-Type set to type2 is not set, may be read as each other. In the present disclosure, the extended DMRS [configuration] type 2, DMRS extended type 2, DMRS extended type = 2, DMRS eType 2, the extended DMRS type is set and the dmrs-Type set to type2 is set, may be read as each other.

[0023] In the present disclosure, the DMRS maximum length, maxLength, the maximum number of OFDM symbols of the preamble (front loaded) DMRS, may be read as each other. In the present disclosure, the values of maxLength {'len1', 'len2'}, maxLength = {1, 2} [symbols], may be read as each other.

[0024] In the present disclosure, FD-OCC, w f (k'), may be read as each other. In the present disclosure, TD-OCC, w t (l'), the TD-OCC with a length of 2, may be read as each other.

[0025] In the present disclosure, the existing OCC, the existing FD-OCC, the FD-OCC with a length of 2, Rel. 15 FD-OCC, may be read as each other. In the present disclosure, the new OCC, the new FD-OCC, the FD-OCC longer than 2, Rel. 18 FD-OCC, w f (k'), the FD-OCC with a length of 4, may be read as each other.

[0026] In the present disclosure, the [antenna] port, DMRS port, DMRS port number, DMRS port index, antenna port number-1000, may be read as each other.

[0027] In the existing specification, the DMRS setting in the frequency domain is represented by the parameter k (sub-carrier index of the DMRS RE), and the DMRS setting in the time domain is represented by the parameter l (symbol index of the DMRS RE).

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

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

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

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

[0032] 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).

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

[0034] n=0,1,... are indices for each FD-OCC.

[0035] ((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) designation (antenna port table) [for at least one of DMRS configuration type 1 or 2, DMRS maximum length 1 or 2, and rank]. Based on the antenna port table, 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.

[0036] (Control of SRS and PUSCH transmission) In Rel. 15 NR, a terminal (user terminal, User Equipment (UE)) may receive information used for transmitting a measurement reference signal (e.g., a Sounding Reference Signal (SRS)) (SRS configuration information, e.g., parameters in "SRS-Config" of the RRC control element).

[0037] Specifically, the UE may receive at least one of the following: information about one or more SRS resource sets (SRS resource set information, e.g., "SRS-ResourceSet" of the RRC control element) and information about one or more SRS resources (SRS resource information, e.g., "SRS-Resource" of the RRC control element).

[0038] A single SRS resource set may be associated with a predetermined number of SRS resources (a predetermined number of SRS resources may be grouped together). Each SRS resource may be identified by an SRS Resource Indicator (SRI) or an SRS Resource Identifier.

[0039] SRS resource set information may include an SRS resource set ID (SRS-ResourceSetId), a list of SRS resource IDs (SRS-ResourceId) used in the resource set, an SRS resource type, and information on the usage of the SRS.

[0040] Here, the SRS resource type may be one of the following: Periodic SRS (P-SRS), Semi-Persistent SRS (SP-SRS), or Aperiodic CSI (A-SRS). The UE may transmit P-SRS and SP-SRS periodically (or periodically after activation), and A-SRS based on DCI's SRS requests.

[0041] Furthermore, the application (RRC parameter "usage", L1 (Layer-1) parameter "SRS-SetUse") may be, for example, beam management (BM), codebook (CB), noncodebook (NCB), antenna switching (AS), etc. SRS for codebook or noncodebook applications may be used to determine the precoder for SRI-based codebook-based or noncodebook-based uplink shared channel (PUSCH) transmission.

[0042] For example, in the case of codebook-based transmission, the UE may determine the precoder (precoding matrix) for PUSCH transmission based on the SRI, Transmitted Rank Indicator (TRI), and Transmitted Precoding Matrix Indicator (TPMI). In the case of non-codebook-based transmission, the UE may determine the precoder for PUSCH transmission based on the SRI.

[0043] SRS resource information may include SRS resource ID (SRS-ResourceId), number of SRS ports, SRS port number, transmit comb, SRS resource mapping (e.g., time and / or frequency resource location, resource offset, resource period, number of repetitions, number of SRS symbols, SRS bandwidth, etc.), hopping-related information, SRS resource type, sequence ID, SRS spatial relationship information, etc.

[0044] The spatial relation information of the SRS (for example, the "spatialRelationInfo" of the RRC information element) may indicate spatial relation information between a predetermined reference signal and the SRS. The predetermined reference signal may be at least one of a Synchronization Signal / Physical Broadcast Channel (SS / PBCH) block, a Channel State Information Reference Signal (CSI-RS), and an SRS (for example, another SRS). The SS / PBCH block may be called a Synchronization Signal Block (SSB).

[0045] The spatial relationship information of the SRS may include at least one of the following as an index for the predetermined reference signal: an SSB index, a CSI-RS resource ID, and an SRS resource ID.

[0046] In this disclosure, the terms SSB index, SSB resource ID, and SSB Resource Indicator (SSBRI) may be interpreted interchangeably. Similarly, the terms CSI-RS index, CSI-RS resource ID, and CSI-RS Resource Indicator (CRI) may be interpreted interchangeably. Furthermore, the terms SRS index, SRS resource ID, and SRI may be interpreted interchangeably.

[0047] The spatial relationship information of the SRS may include a serving cell index, a BWP index (BWP ID), etc., corresponding to the predetermined reference signal mentioned above.

[0048] If a UE sets spatial relationship information regarding an SRS resource with respect to an SSB or CSI-RS, it may transmit the SRS resource using the same spatial domain filter (spatial domain transmit filter) as the spatial domain filter (spatial domain receive filter) used for receiving the SSB or CSI-RS. In this case, the UE may assume that the UE receive beam for the SSB or CSI-RS and the UE transmit beam for the SRS are the same.

[0049] If a UE sets up spatial relationship information regarding a certain SRS (target SRS) resource and another SRS (reference SRS), it may transmit the target SRS resource using the same spatial domain filter (spatial domain transmit filter) as the spatial domain filter (spatial domain transmit filter) used for transmitting the reference SRS. In other words, in this case, the UE may assume that the UE transmit beam of the reference SRS and the UE transmit beam of the target SRS are the same.

[0050] The UE may determine the spatial relationships of the PUSCH scheduled by the DCI (e.g., DCI format 0_1) based on the value of a predetermined field (e.g., the SRS resource identifier (SRI) field). Specifically, the UE may use spatial relationship information of the SRS resource (e.g., "spatialRelationInfo" of the RRC information element) determined based on the value of the predetermined field (e.g., SRI) for the PUSCH transmission.

[0051] In Rel. 15 / 16 NR, when using codebook-based transmission for PUSCH, the UE may have up to two SRS resources, with the SRS resource set in the codebook configured by the RRC, and one of the up to two SRS resources indicated by the DCI (1-bit SRI field). The transmit beam of PUSCH will be specified by the SRI field.

[0052] The UE may determine the TPMI and layer count (transmission rank) for PUSCH based on the precoding information and layer count field (hereinafter also referred to as the precoding information field). The UE may select a precoder from the uplink codebook for the same number of ports as the number of SRS ports indicated by the higher layer parameter "nrofSRS-Ports" set for the SRS resource specified by the SRI field, based on the TPMI, layer count, etc.

[0053] In Rel. 15 / 16 NR, when using non-codebook-based transmission for PUSCH, the UE may have up to four SRS resources, with the non-codebook SRS resource set by the RRC, and one or more of these up to four SRS resources may be indicated by the DCI (2-bit SRI field).

[0054] The UE may determine the number of layers (transmission rank) for PUSCH based on the above SRI field. For example, the UE may determine that the number of SRS resources specified by the above SRI field is the same as the number of layers for PUSCH. The UE may also calculate the precoder of the above SRS resource.

[0055] If a CSI-RS (which may also be called an associated CSI-RS) associated with the SRS resource (or the SRS resource set to which the SRS resource belongs) is configured at a higher layer, the PUSCH transmit beam may be calculated based on the configured associated CSI-RS (or its measurement). Otherwise, the PUSCH transmit beam may be specified by the SRI.

[0056] Furthermore, the UE may be configured to use either codebook-based or non-codebook-based PUSCH transmission via a higher-layer parameter "txConfig" that indicates the transmission scheme. This parameter may indicate a value of "codebook" or "noncodebook".

[0057] In this disclosure, codebook-based PUSCH (codebook-based PUSCH transmission, codebook-based transmission) may mean PUSCH when the UE is set to “codebook” as the transmission scheme. In this disclosure, non-codebook-based PUSCH (non-codebook-based PUSCH transmission, non-codebook-based transmission) may mean PUSCH when the UE is set to “non-codebook” as the transmission scheme.

[0058] (Transmission with more than 4 antenna ports) Rel. 15 / 16 NR supports uplink (UL) Multi Input Multi Output (MIMO) transmission up to 4 layers. For future wireless communication systems, support for UL transmission with more than 4 layers is being considered to achieve higher spectral efficiency. For example, for Rel. 18 NR, up to 6 ranks of transmission using 6 antenna ports, and up to 6 or 8 ranks of transmission using 8 antenna ports are being considered.

[0059] Furthermore, precoding matrices for UL transmissions using more than four antenna ports are being considered. For example, a codebook for 8-port transmissions (which may also be called an 8 Transmission(TX) UL codebook) is being considered.

[0060] In antenna layouts, Ng is the number of antenna groups. M is the number of antennas (or antenna elements) in the first dimension, and N is the number of antennas (or antenna elements) in the second dimension. The first and second dimensions are, for example, the horizontal and vertical directions. P is the number of polarization planes. When P = 2, it is a cross-polarized antenna.

[0061] An antenna group may also be called a coherent group. A coherent group may contain one or more coherent ports. For example, a partially coherent UE may have multiple coherent groups. Antenna ports within a coherent group may be coherent. Antenna ports between different coherent groups may not be coherent.

[0062] Each coherent group may correspond to a different transmit panel / transmit chain (Tx chain) / SRS resource set / RS resource set / spatial relation info / joint Transmission Configuration Indication state (joint TCI state) / UL TCI state / received TRP. Here, the SRS resource set may specifically correspond to an SRS resource set used in a codebook or non-codebook. Also, each coherent group may correspond to a different receive TRP. Furthermore, a coherent group may also be called a coherent antenna group, port group, antenna set, etc.

[0063] The UE may report supported antenna groups, antenna placement information, and coherence count as UE capability information. The UE may also configure coherence groups (e.g., the number of coherence groups, the number of ports included in each coherence group) through upper-layer signaling.

[0064] The number of panels on which antennas are placed, the orientation of the panels, the coherence of each panel / antenna (fully coherent, partially coherent, noncoherent, etc.), the antenna arrangement in a specific direction (horizontal, vertical, etc.), and the polarization antenna configuration (single polarization, cross polarization, number of polarization planes, etc.) may differ from existing antenna layouts. dG-H and dG-V represent the horizontal and vertical spacing between the centers of adjacent antenna groups, respectively.

[0065] Furthermore, while Rel. 15 / 16 NR supported the transmission of one codeword (CW) per pusher, for Rel. 18 NR, it is being considered that UEs (User Entities) will transmit more than one CW per pusher. For example, support for two CW transmissions for ranks 5-8 and support for two CW (dual CW) transmissions for ranks 2-8 are being considered. One CW corresponds to one transport block (TB). The CW may be obtained by encoding the TB, or the TB may be obtained by decoding the CW.

[0066] Prior to Rel. 17 NR, DL transmissions (e.g., PDSCH transmissions) supported the transmission of two TBs (e.g., TB#1 and TB#2). When two TBs (e.g., TB#2) are supported, the DCI used for scheduling the PDSCH (e.g., DCI format 1_1) may include predetermined fields for TB#1 and predetermined fields for TB#2, respectively. The predetermined fields may be at least one of the following: modulation and coding scheme, new data indicator, or redundancy version.

[0067] In PUSCH transmission, the support (or activation) of dual CW may be communicated from the base station to the UE by a predetermined upper-layer parameter. The predetermined upper-layer parameter may be an upper-layer parameter relating to the maximum number of CWs scheduled by DCI (e.g., maxNrofCodeWordsScheduledByDCI). The predetermined upper-layer parameter (e.g., maxNrofCodeWordsScheduledByDCI) may be included in the PUSCH configuration information (e.g., PUSCH-config).

[0068] For example, if a predetermined higher-layer parameter is set to 2 (e.g., maxNrofCodeWordsScheduledByDCI equals 2), it may mean that a predetermined field for TB#2 is included in the DCI. In other words, if a predetermined higher-layer parameter indicates a predetermined value (e.g., 2) for a PDSCH, it may mean that a field for TB#2 exists (or that two codeword transmission is enabled).

[0069] If a predetermined higher-layer parameter (e.g., maxNrofCodeWordsScheduledByDCI) indicates that two codeword transmissions (e.g., two codeword transmissions) are enabled, then one of the two transport blocks may be disabled in DCI format if certain conditions are met. For example, the predetermined conditions may be that the MCS index (e.g., I) is set for the corresponding transport block. MCS ) and the RV index each reach predetermined values ​​(for example, I MCS It is also possible that = 26 and RV = 1.

[0070] In this way, a predetermined upper-level parameter is set to a predetermined value (for example, maxNrofCodeWordsScheduledByDCI=2), I MCS If there is a TB where =26 and RV=1, the corresponding TB may be disabled to enable dynamic instruction (or switching) between having more than 4 layers and fewer than 4 layers for the PDSCH.

[0071] In this disclosure, 8Tx[PUSCH] transmission, 2TB[PUSCH] transmission, 2CW[PUSCH] transmission, and [PUSCH] transmission using more than four [antenna] ports may be interpreted as mutually exclusive.

[0072] In the two TB / CWs of this disclosure, the first TB, TB1, first CW, and CW0 may be interpreted as interchangeable. In the two TB / CWs of this disclosure, the second TB, TB2, second CW, and CW1 may be interpreted as interchangeable.

[0073] N SRS > In NCB-based 8Tx PUSCH transmission using 4, it is being considered that a method based on existing specifications will be supported. Here, N SRS This is the number of single-port SRS resources configured within the SRS resource set. The method is N SRS =8 and L max Extend the existing SRI instruction table to include =8. Here, L max This is the maximum number of MIMO layers. In the SRI instruction for NCB-based PUSCH, a bitmap instruction and a method based on existing specifications may be selected.

[0074] To configure PUSCH transmission using 8Tx UE, it is being considered to extend the range of maxRank and maxMIMO-Layers to 8, thereby setting the maximum number of MIMO layers in RRC. The maximum rank is set by RRC signaling.

[0075] To support dual CW push transmission for more than 4 ranks with 8Tx UE, it is being considered to indicate a second MCS field (5 bits) for the second CW (CW1) for MCS indication. To support dual CW push transmission for more than 4 ranks with 8Tx UE, it is being considered to indicate a second set of fields for new data indicator (NDI, 1 bit) and redundancy version (RV, 2 bits). In other words, an additional MCS / NDI / RV for the second CW will be supported.

[0076] The maxMIMO-Layers setting in the ServingCell Config (PUSCH-ServingCellConfig) is the maximum number of MIMO layers for an 8Tx PUSCH, and the range of values ​​for the existing parameters maxRank and maxMIMO-Layers is extended from 1 to 8. The maxMIMO-LayersDCI-0-2 setting in the ServingCell Config (PUSCH-ServingCellConfig) is the maximum number of MIMO layers for an 8Tx PUSCH, and the range of values ​​for the existing parameters maxRank and maxMIMO-Layers is extended from 1 to 8.

[0077] maxMIMO-Layers / maxMIMO-LayersDCI-0-2 are parameters for NCB-based PUSCH transmission, are cell-specific parameters, and apply to all BWPs within that cell.

[0078] The maxRank in the PUSCH-Config is a subset of PMIs processed by the maximum transmit rank for PUSCHs scheduled using DCI format 0_1. Its value ranges from 1 to 8. The maxRankDCI-0-2 in the PUSCH-Config is a subset of PMIs processed by the maximum transmit rank for PUSCHs scheduled using DCI format 0_2. Its value ranges from 1 to 8.

[0079] maxRank / maxRankDCI-0-2 are parameters for CB-based push transmission and are BWP-specific parameters.

[0080] (Maximum number of UL MIMO layers) [Specifications for multiplexing and channel coding / General procedures / Rate matching / Rate matching for low density parity check (LDPC) code / Bit selection] The maximum number of layers for a single TB for a UL-shared channel (SCH) is the minimum of X and 4. Here, if the maximum number of MIMO layers (upper layer parameter maxMIMO-Layers) is set in the serving cell's PUSCH serving cell configuration (PUSCH-ServingCellConfig), X is given by that parameter. Otherwise, if the maximum rank (upper layer parameter maxRank) is set in the serving cell's PUSCH configuration (pusch-Config), X is given by the maximum value of maxRank across all BWPs of the serving cell. Otherwise, X is given for the serving cell by the maximum number of layers of PUSCH supported by the UE.

[0081] In other words, even if the maximum number of MIMO layers becomes 8, the maximum number of MIMO layers used to transmit one TB remains 4. Therefore, when performing UL transmission using more than 4 MIMO layers, the UE will transmit two TBs.

[0082] (UL Skipping) [MAC Protocol Specification / MAC Procedure / UL-SCH Transfer / Multiplexing and Assembly / Logical Channel Prioritization / Resource Placement] A MAC entity performs the following steps x:

[0083] ◆Procedure 1: If the MAC entity is configured with enhancedSkipUplinkTxDynamic with a value of true, and the grant instructed to the HARQ entity is destined for C-RNTI, or if the MAC entity is configured with enhancedSkipUplinkTxConfigured with a value of true, and the grant instructed to the HARQ entity is a configured UL grant, then the MAC entity performs the following steps: —◆There is no UCI to be multiplexed onto this PUSCH transmission, —◆There is no aperiodic CSI requested for this PUSCH transmission, —◆The MAC PDU contains zero MAC service data units (SDUs), —◆The MAC PDU contains only periodic buffer status reports (BSRs) and there is no data available for any logical channel group (LCG), or the MAC PDU contains only padding BSRs, --◆That MAC entity does not generate a MAC PDU for the HARQ entity.

[0084] ◆Step 2: In cases other than Step 1, if the MAC entity is configured with SkipUplinkTxDynamic with the value true, and the grant directed to the HARQ entity is destined for C-RNTI, or the grant directed to the HARQ entity is a configured UL grant, the MAC entity performs the following steps: —◆There is no aperiodic CSI requested for this PUSCH transmission, —◆The MAC PDU contains zero MAC SDUs, —◆The MAC PDU contains only periodic BSRs and there is no data available for any LCG, or the MAC PDU contains only padding BSRs, —◆The MAC entity does not generate a MAC PDU for the HARQ entity.

[0085] Thus, a UE configured with UL skipping (enhancedSkipUplinkTxDynamic / enhancedSkipUplinkTxConfigured / skipUplinkTxDynamic with the value true) by RRC can, based on autonomous determination, stop generating the MAC PDU (skip UL transmission) if a configuration grant or dynamic grant exists but UL data does not exist.

[0086] The gNB needs to distinguish between the following two actions: ◆Action 1: The UE autonomously performed UL skipping, and as a result, the PUSCH was not received by the gNB. In this case, the gNB does nothing. ◆Action 2: The UE sent a PUSCH, but for channel conditions or other reasons, the PUSCH was not properly received by the gNB. In this case, the gNB sends a DCI to prompt a HARQ retransmission.

[0087] In existing specifications (prior to Rel. 18), the maximum number of MIMO layers transmitted by a UE is 4, so a UE transmits one TB in a PUSCH. A gNB can determine that UL skipping has occurred based on the received strength of the PUSCH DMRS based on the UL grant, for example, as follows: ◆ If the received strength of the PUSCH DMRS in the gNB exceeds a certain value (is above a certain value), the gNB determines that the PUSCH is receivable (or has been transmitted), as shown in the example in Figure 1, and performs decoding of the PUSCH. If decoding fails, the gNB issues a HARQ retransmission instruction via DCI. ◆ If the received strength of the PUSCH DMRS in the gNB is below a certain value (is less than a certain value), the gNB determines that the PUSCH is not receivable (or has not been transmitted), as shown in the example in Figure 2, and does not perform decoding of the PUSCH.

[0088] In Rel. 18, as mentioned above, the maximum number of MIMO layers transmitted by the UE is eight, and in transmissions using more than four layers, the UE transmits two TBs. When the UE is instructed to transmit using more than four layers, the following two cases are possible:

[0089] ◆Case 1: The UE performed UL skipping on both TBs [of the two TBs]. In this case, the UE does not transmit a PUSCH DMRS in order to abort the PUSCH. The gNB can determine that it will not decode the PUSCH based solely on the received PUSCH DMRS strength.

[0090] ◆Case 2: The UE performs UL skipping on one of the two TBs and transmits the other TB. In this case, since the UE transmits PUSCH and therefore transmits PUSCH DMRS, the gNB cannot determine whether to decode PUSCH based solely on the received PUSCH DMRS strength. As shown in the example in Figure 3, suppose the UE, instructed to perform an 8-layer PUSCH, performs UL skipping from layers 5 to 8 and transmits PUSCH and PUSCH DMRS using layers 1 to 4. In this case, since PUSCH DMRS is transmitted, the gNB cannot determine whether to decode PUSCH based solely on the received PUSCH DMRS strength.

[0091] In the existing specifications, the association between DMRS port numbers and the PUSCH MIMO layer is defined as shown in Table M-1, which is displayed in Figures 4 through 6. UE / gNB associates the DMRS port number with the PUSCH MIMO layer based on this table.

[0092] The complex modulation symbols for each of the multiple codewords (TBs) to be transmitted are mapped to up to four layers according to Table M-1. In this table, the complex modulation symbol d for the codeword q ∈ {0,1} (q) (0),...,d (q) (M symb (q) -1) is 0, 1, ..., Msymb layer For -1, the modulation symbol x(i) = [x (0) (i), ..., x (v-1) (i)] T It is mapped to. Here, v is the number of layers, and M symb layer λ is the number of modulation symbols per layer. Layers may also be represented by λ = 0, 1, ..., v-1.

[0093] However, when 2TB PUSCH is set / instructed, the operation of the UE for gNB to determine whether 2TB has been transmitted has not been sufficiently considered.

[0094] Even when a UE performs UL skipping on one of two TBs, it is not prohibited for the UE to send PUSCH DMRS on all DMRS ports. If a UE performs UL skipping on one TB and sends PUSCH DMRS on all DMRS ports, the gNB may not recognize the UL skipping on that TB and may send unnecessary HARQ retransmission instructions using DCI. Thus, if the operation regarding UL skipping is not sufficiently considered, it may lead to a decrease in resource utilization efficiency.

[0095] Therefore, the inventors conceived of an operation related to DMRS transmission when 2TB PUSCH is set / instructed.

[0096] (Various Modifications, etc.) Hereinafter, embodiments relating to this disclosure will be described in detail with reference to the drawings. Each wireless communication method according to each embodiment may be applied individually or in combination.

[0097] 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".

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

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

[0100] 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).

[0101] 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).

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

[0103] In this disclosure, "having the ability to..." may be interpreted as "supporting / reporting the ability to..."

[0104] In this disclosure, ceil(x), ceiling function, and ceiling function may be interpreted as interchangeable. In this disclosure, floor(x), floor function, and floor function may be interpreted as interchangeable. In this disclosure, sqrt(x), square root (root) may be interpreted as interchangeable. In this disclosure, x mod y, mod(x,y), mod function, and modulo operation may be interpreted as interchangeable. In this disclosure, Σ i=M N f(i), the summation of f(i) over i=M, M+1, ..., N, and f(M)+f(M+1)+...+f(N) can be rephrased as one another. C(x,y) represents the number of combinations of choosing y items from x items (combinatorial coefficient), and is also called the binomial coefficient.

[0105] In this disclosure, a bThe notation a_b and a with a subscript b may be interchangeable. In this disclosure, a c The notation a^c and a with a c superscripted to the right may be interpreted as interchangeable. In this disclosure, a b c The notation a_b^c, where a has a b attached to the lower right and c attached to the upper right, may be interpreted as being interchangeable. In this disclosure, x ~ x may be represented by placing a ~ above x, or it may be called x tilde. In this disclosure, x - This can also be represented by placing a hyphen (-) above x, or it may be called an x-bar.

[0106] In this disclosure, the terms constant value, fixed value, set value, and threshold may be interpreted interchangeably.

[0107] In this disclosure, UE, MAC entities, and upper layers may be interpreted as interchangeable. In this disclosure, UE, physical (PHY) layers, and lower layers may be interpreted as interchangeable. In this disclosure, HARQ buffers, HARQ processes, and HARQ entities may be interpreted as interchangeable.

[0108] In this disclosure, with respect to notices between MAC entities and the physical layer, transmit, provide, indicate, and instruct may be interpreted as mutually exclusive. In this disclosure, with respect to notices between MAC entities and the physical layer, receive, be provided, be indicated, and be instructed may be interpreted as mutually exclusive.

[0109] In this disclosure, skipping, stop, cancellation, and drop may be interpreted as interchangeable.

[0110] (Wireless communication method) If conditions A and B are met, the UE may decide whether to transmit a DMRS [and the PUSCH] for the PUSCH on one or more specific layers (one or more second layers) associated with TB2 (CW1) among the multiple layers for the PUSCH. The number (rank) of layers for the PUSCH may be greater than 4. The one or more layers associated with TB2 do not have to include layers 0 and 1. The one or more layers associated with TB2 may be layers 2 to 4 for a layer count (rank) of 5, layers 3 to 5 for a layer count (rank) of 6, layers 3 to 6 for a layer count (rank) of 7, and layers 4 to 7 for a layer count (rank) of 8.

[0111] If conditions A and B are met, the UE may decide whether to transmit a DMRS [and the PUSCH] for the PUSCH in one or more layers (one or more first layers) associated with TB1(CW0) among the multiple layers for the PUSCH.

[0112] If conditions A and B are met, the UE may decide whether to transmit DMRS [and the PUSCH] for the PUSCH at multiple layers (all layers) for that PUSCH.

[0113] In this disclosure, condition A [is satisfied] and receiving instructions / settings for a PUSCH (2TB PUSCH) to transport two TBs (TB1 and TB2) may be interpreted as mutually exclusive.

[0114] Condition A may be the AND result of two or more of the following conditions Ax: ◆Condition A1: UL skipping is set. ◆Condition A2: A value greater than 4 is set as the maximum number of PUSCH layers. ◆Condition A3: A value greater than 4 (2TB PUSCH) is indicated as the rank or number of layers of PUSCH. ◆Condition A4: The UE reports capability information corresponding to Embodiment 1 or Embodiment 2.

[0115] The maximum number of PUSCH layers may be the maximum number of PUSCH layers (MIMO layers for PUSCH), and may be at least one of the maximum rank (maxRank [in PUSCH-Config, the maximum number of CB-based PUSCH layers) and the maximum number of MIMO layers (maxMIMO-Layers [in PUSCH-ServingCellConfig, the maximum number of NCB-based PUSCH layers). The number of PUSCH layers may be at least one of the rank for [CB-based] PUSCH and the number of [MIMO] layers for [NCB-based] PUSCH. In this disclosure, the [MIMO] layers and layer index [used for transmitting PUSCH] may be interpreted as interchangeable. In this disclosure, the number of [MIMO] layers and rank may be interpreted as interchangeable. In this disclosure, the number of [MIMO] layers and rank may be interpreted as interchangeable.

[0116] In this disclosure, UL skipping having a value of true, a MAC entity / UE having UL skipping having a value of true, a MAC entity / UE receiving a UL skipping setting having a value of true, and UL skipping setting having a value of true may be interpreted as mutually exclusive. In this disclosure, UL skipping setting, RRC IE for UL skipping, enhancedSkipUplinkTxDynamic / enhancedSkipUplinkTxConfigured / skipUplinkTxDynamic may be interpreted as mutually exclusive.

[0117] In this disclosure, the terms "instruction / setting of the rank or number of layers of PUSCH", "instruction / setting of PUSCH", "DCI, [UL] grant for scheduling / activation of PUSCH", "dynamic grant", and "configured grant" may be interpreted as interchangeable.

[0118] In this disclosure, the following conditions may be interpreted interchangeably: condition B [is satisfied], the UE / MAC entity does not generate a MAC PDU for one of the two indicated TBs [associated with the HARQ buffer], the UE / MAC entity generates a MAC PDU for only one of the two indicated TBs [associated with the HARQ buffer], there is no UL data for one of the two indicated TBs, there is UL data for only one of the two indicated TBs, and the size of the data [to be transmitted] is less than or equal to the size of one TB. One of the two indicated TBs may be TB2.

[0119] Condition B may be the AND result of one or more of the following conditions Bx: ◆Condition B1: The grant directed to the UE / HARQ entity was addressed to C-RNTI. ◆Condition B2: The grant directed to the UE / HARQ entity is a configured UL grant. ◆Condition B3: There are no UCIs to be multiplexed onto this PUSCH transmission. ◆Condition B4: There are no aperiodic CSIs requested for this PUSCH transmission. ◆Condition B5: The MAC PDU [corresponding to one of the two directed TBs] contains zero MAC SDUs. ◆Condition B6: The MAC PDU [corresponding to one of the two specified TBs] contains only periodic BSRs and there is no available data [corresponding to one of the two specified TBs] for any LCG, or the MAC PDU [corresponding to one of the two specified TBs] contains only padding BSRs.

[0120] In this disclosure, the UL data, TB, CW, HARQ buffer, and MAC PDU [to be transmitted] may be interpreted as other terms. The TB / CW may be associated with the HARQ buffer. The HARQ buffer may be associated with the MAC PDU. The MAC PDU may be associated with one or more MAC SDUs.

[0121] <Embodiment 1> gNB can determine whether PUSCH DMRS has been received for each MIMO layer by at least one of the following two values ​​x: ◆Value 1: Received power for each DMRS port. ◆Value 2: Correlation between the received signal for each DMRS port and the [PUSCH DMRS] replica [received signal].

[0122] To implement this determination method, if the UE performs UL skipping on one of the two designated TBs (e.g., TB2) (if conditions A and B are met), it may stop PUSCH DMRS transmission on the DMRS port corresponding to the MIMO layer associated with that TB.

[0123] If conditions A and B are met, the UE may decide not to transmit DMRS [and its PUSCH] for one or more specific layers associated with TB2.

[0124] According to this embodiment, if a UE is instructed to perform a UL transmission using more than four layers and to perform UL skipping on one of the two TBs, the gNB can recognize that UL skipping has been performed based on the reception status of PUSCH DMRS. This allows the gNB to avoid issuing unnecessary HARQ retransmission instructions.

[0125] Embodiment 1 may be based on at least one of the following embodiments 1-x.

[0126] <<Embodiment 1-1>> If condition A is met and the UE / MAC entity does not generate a MAC PDU for the HARQ buffer associated with one of the two indicated TBs, the UE / MAC entity may stop transmitting PUSCH DMRS on all DMRS ports corresponding to all MIMO layers associated with that one TB, and PUSCH on all MIMO layers associated with that one TB.

[0127] As shown in the example in Figure 7, when the UE performs UL skipping on TB2 (CW1), it may stop PUSCH DMRS transmission on the DMRS port corresponding to the MIMO layer associated with TB2.

[0128] For value 1, with basic DMRS type 1, DMRS maximum length 2, and rank 8, CW0 [based on TB1] is mapped to DMRS ports 0, 1, 2, and 3, and CW1 [based on TB2] is mapped to DMRS ports 4, 5, 6, and 7. For example, since DMRS ports 3 and 4 are mapped to different physical resources (time / frequency resources), the gNB can separately determine whether the received power of DMRS port 3 (CW0) exceeds the threshold and whether the received power of DMRS port 4 (CW1) exceeds the threshold. This allows the gNB to separately determine whether a PUSCH DMRS [corresponding to CW0] is being transmitted on DMRS port 3 and whether a PUSCH DMRS [corresponding to CW1] is being transmitted on DMRS port 4.

[0129] Regarding value 2, in the case of basic DMRS type 1, DMRS maximum length 2, and rank 7, CW0 is mapped to DMRS ports 0, 1, and 2, and CW1 is mapped to DMRS ports 3, 4, 5, and 6. For example, DMRS ports 2 and 3 are mapped to the same physical resources (time and frequency resources) and are CDM'd using different FD-OCCs. The DMRS sequence of DMRS port 2 is multiplied by FD-OCC[+1 +1], and the DMRS sequence of DMRS port 2 is multiplied by [+1 -1]. gNB can determine whether the correlation with DMRS port 2 (CW0) exceeds a threshold by calculating the correlation between the received signal replica obtained by multiplying the DMRS sequence of DMRS port 2 by FD-OCC[+1 +1] and the received signal. The gNB can determine whether the correlation with DMRS port 3 (CW1) exceeds a threshold by calculating the correlation between the received signal replica obtained by multiplying the DMRS sequence of DMRS port 3 by FD-OCC[+1 -1] and the received signal. This allows the gNB to separately determine whether a PUSCH DMRS [corresponding to CW0] is being transmitted on DMRS port 3 and whether a PUSCH DMRS [corresponding to CW1] is being transmitted on DMRS port 4.

[0130] <<Embodiment 1-2>> If condition A is met, and the MAC entity does not generate a MAC PDU for the HARQ buffer associated with one of the two indicated TBs, the MAC entity may send a notification to the physical layer (lower layer). The physical layer may receive a notification from the MAC entity (upper layer) indicating that it will not generate a MAC PDU for the HARQ buffer associated with that one TB.

[0131] <<Embodiment 1-3>> The UE may report that it supports the functionality of Embodiment 1-1 by UE capability signaling. The UE capability signaling may include one of the following IEs: ◆FeatureSetUplink ◆FeatureSetUplinkPerCC ◆MIMO-ParametersPerBand

[0132] The IE (e.g., FeatureSetUplinkPerCC) that includes the UE capability signaling may also include the capability to indicate support for PUSCH transmissions using more than four layers (codebookParameter8TxPUSCH-r18 or nonCodebook-8TxPUSCH-r18).

[0133] <<Embodiment 1-4>> The UE may enable the functionality of Embodiment 1-1 by an RRC IE [from the gNB]. The RRC IE may be one of the following IEs: ◆PUSCH-Config ◆PUSCH-ServingCellConfig

[0134] <Embodiment 2> For a 2TB PUSCH transmission, it may be assumed that UL skipping is not performed on only one of the two TBs (TB1 and TB2) (for example, TB2) (when conditions A and B are met) (the UE does not have to perform UL skipping on only one TB).

[0135] According to this embodiment, the UE can appropriately determine whether to transmit PUSCH [and PUSCH DMRS], and the gNB can appropriately determine whether that PUSCH [and PUSCH DMRS] is transmitted. For example, even if a 2TB PUSCH is set / instructed and there is no UL data for 1TB of that 2TB, the UE can appropriately transmit that PUSCH [and PUSCH DMRS], and the gNB can appropriately receive / decode that PUSCH [and PUSCH DMRS].

[0136] If conditions A and B are met, the UE may decide whether to transmit DMRS for the PUSCH [and the PUSCH] at multiple layers for that PUSCH.

[0137] Embodiment 2 may be based on at least one of the following Embodiment 2-x.

[0138] <<Embodiment 2-1>> Even if condition A is met and the UE / MAC entity does not generate a MAC PDU for the HARQ buffer associated with one of the two indicated TBs, the UE / MAC entity [always] generates MAC PDUs for all indicated UL grants. The two generated MAC PDUs (MAC PDU1 and MAC PDU2) may be based on one of the following: ◆ MAC PDU1 is based on TB1. MAC PDU2 includes a 0-bit MAC SDU (data payload). MAC PDU2 may also include a header corresponding to the 0-bit MAC SDU. ◆ MAC PDU1 is based on TB1. MAC PDU2 includes dummy data / signals. ◆ MAC PDU1 is based on TB1. MAC PDU2 is based on part or all of TB1. ◆TB1 is split into first data and second data. MAC PDU1 is based on first data. MAC PDU2 is based on second data.

[0139] gNB may send HARQ-ACK information / retransmission request / DCI / corresponding to MAC PDU2, or it may not send HARQ-ACK information / retransmission request / DCI / corresponding to MAC PDU2. UE may receive HARQ-ACK information / retransmission request / DCI / corresponding to MAC PDU2, or it may not receive HARQ-ACK information / retransmission request / DCI / corresponding to MAC PDU2 (it may be assumed that HARQ-ACK information / retransmission request / DCI / corresponding to MAC PDU2 is not sent). HARQ-ACK information may be ACK or NACK. gNB may send HARQ-ACK information / retransmission request / DCI / corresponding to MAC PDU1. UE may receive HARQ-ACK information / retransmission request / DCI / corresponding to MAC PDU1.

[0140] If conditions A and B are met, the UE may decide to transmit DMRS [and its PUSCH] for one or more specific layers associated with TB2. If conditions A and B are met, the UE may decide to transmit DMRS [and its PUSCH] for multiple layers for a PUSCH.

[0141] <<Embodiment 2-2>> If condition A is met and the UE / MAC entity does not generate a MAC PDU for the HARQ buffer associated with one of the two indicated TBs, the UE / MAC entity may transmit / generate one of the following specific data for that one TB: ◆ A MAC PDU containing a 0-bit MAC SDU (data payload). The MAC PDU may include a header corresponding to the 0-bit MAC SDU. ◆ Dummy data / signals in place of the MAC PDU. ◆ A MAC PDU containing part or all of the other TB (TB1) of the two TBs.

[0142] gNB may send HARQ-ACK information / retransmission request / DCI / corresponding to specific data, or it may not send HARQ-ACK information / retransmission request / DCI / corresponding to specific data. UE may receive HARQ-ACK information / retransmission request / DCI / corresponding to specific data, or it may not receive HARQ-ACK information / retransmission request / DCI / corresponding to specific data (it may be assumed that HARQ-ACK information / retransmission request / DCI / corresponding to specific data is not sent). HARQ-ACK information may be ACK or NACK. gNB may send HARQ-ACK information / retransmission request / DCI / corresponding to TB1. UE may receive HARQ-ACK information / retransmission request / DCI / corresponding to TB1.

[0143] If conditions A and B are met, the UE may decide to transmit DMRS [and its PUSCH] for one or more specific layers associated with TB2. If conditions A and B are met, the UE may decide to transmit DMRS [and its PUSCH] for multiple layers for a PUSCH.

[0144] <<Embodiment 2-3>> If condition A is met, and the UE / MAC entity does not generate a MAC PDU for the HARQ buffer associated with one of the two instructed TBs, then the UE / MAC entity also does not generate a MAC PDU for the other TB that is instructed to be spatially multiplexed with that one TB.

[0145] In Embodiment 2-3, if conditions A and B are met, the UE may decide not to transmit DMRS [and its PUSCH] for one or more specific layers associated with TB2. If conditions A and B are met, the UE may decide not to transmit DMRS [and its PUSCH] for multiple layers for a PUSCH.

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

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

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

[0149] 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).

[0150] In the embodiments described above, the UE may receive at least one piece of information (QCL information) from the NW from among several of the following QCL rules / QCL types: ◆ QCL type A (Doppler shift, Doppler spread, mean delay, and delay spread) ◆ QCL type B (Doppler shift and Doppler spread) ◆ QCL type C (Doppler shift and mean delay) ◆ QCL type D (spatial reception parameters)

[0151] 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

[0152] 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)

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

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

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

[0156] 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).

[0157] <<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 designated / 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.

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

[0159] 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), a capability per feature set (FS) or feature set per component-carrier (FSPC), or a capability per functionality / model.

[0160] 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)).

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

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

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

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

[0165] (Note) The following inventions are added with respect to one embodiment of the present disclosure. <Note 1> A terminal having: a receiving unit that receives instructions for a physical uplink sharing channel for transporting a first transport block and a second transport block; and a control unit that determines whether, if the first transport block is present and the second transport block is absent, to transmit a demodulation reference signal (DMRS) for the physical uplink sharing channel on one or more specific layers among a plurality of layers for the physical uplink sharing channel that are associated with the second transport block. <Note 2> The terminal according to Note 1, wherein, if the first transport block is present and the second transport block is absent, the control unit determines whether to transmit the first transport block and the first DMRS on one or more first layers among the plurality of layers that correspond to the first transport block, and whether to not transmit the second transport block and the second DMRS on one or more specific layers. <Note 3> If the first transport block is present and the second transport block is absent, the control unit decides to transmit the physical uplink sharing channel and the DMRS in the multiple layers, as described in Note 1 or Note 2. <Note 4> If the first transport block is present and the second transport block is absent, the control unit decides to skip the transmission of the physical uplink sharing channel, as described in any of Notes 1 to 3. <Supplement> The terminal in Notes 1 to 4 may be a user terminal 20. The receiving / transmitting unit in Notes 1 to 4 may be a transmitting / receiving unit 220. The control unit in Notes 1 to 4 may be a control unit 210.<Note A> A base station comprising: a transmitting unit that transmits instructions for a physical uplink sharing channel for transporting a first transport block and a second transport block; and a control unit that, when the first transport block is present and the second transport block is absent, determines whether a demodulation reference signal (DMRS) for the physical uplink sharing channel is transmitted in one or more specific layers associated with the second transport block among a plurality of layers for the physical uplink sharing channel. <Supplement> The base station in Note A may be a base station 10. The receiving / transmitting unit in Note A may be a transmitting / receiving unit 120. The control unit in Note A may be a control unit 110.

[0166] (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.

[0167] Figure 8 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).

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

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

[0170] 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))).

[0171] 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 and number 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.

[0172] 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).

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

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

[0175] Multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with Common Public Radio Interface (CPRI), X2 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.

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

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

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

[0179] 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).

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

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

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

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

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

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

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

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

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

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

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

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

[0192] 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).

[0193] (Base Station) Figure 9 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0210] (User Terminal) Figure 10 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0228] (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.

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

[0230] 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 11 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.

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

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

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

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

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

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

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

[0238] 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).

[0239] 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).

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

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

[0242] (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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0260] 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".

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

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

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

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

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

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

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

[0268] 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).

[0269] 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 notifying the specified information or by notifying other information).

[0270] 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).

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

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

[0273] 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0290] Figure 12 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.

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

[0292] 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).

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

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

[0295] 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.).

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

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

[0298] 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).

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

[0300] 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).

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

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

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

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

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

[0306] 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).

[0307] 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."

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

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

[0310] 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).

[0311] Furthermore, “judgment (decision)” may be considered as “judgment (decision)” of resolving, selecting, choosing, establishing, comparing, etc. In other words, “judgment (decision)” may be considered as “judgment (decision)” of some action. In this disclosure, “judgment (decision)” may be interpreted as mutually interchangeable with the actions described above.

[0312] Furthermore, in this disclosure, “determine / determining” may be interpreted as “assume / assuming,” “expect / expecting,” or “consider / considering.” In addition, in this disclosure, “not expecting to do…” may be interpreted as “expecting not to do….”

[0313] In this disclosure, "expect" may be interpreted as "be expected." For example, "expect(s) ..." (where "..." may be expressed as, for example, a that clause or an infinitive) may be interpreted as "be expected ...." Similarly, "does not expect ..." may be interpreted as "be not expected ...." Furthermore, "An apparatus A is not expected ..." may be interpreted as "An apparatus B other than apparatus A does not expect ..." (for example, if apparatus A is a UE, apparatus B may be a base station).

[0314] The term "maximum transmit power" as used in this disclosure may mean the maximum transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0315] As used in this disclosure, the terms “connected,” “coupled,” and any variations thereof mean any direct or indirect connection or coupling between two or more elements, and may include one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be replaced with “access.”

[0316] In this 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, in some non-exclusive and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

[0317] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0318] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

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

[0320] 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").

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

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

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

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

[0325] This application is based on Japanese Patent Application No. 2025-009755, filed on January 23, 2025. All of its contents are included herein.

Claims

1. A terminal having a receiving unit that receives instructions for a physical uplink sharing channel for transporting a first transport block and a second transport block, and a control unit that determines whether, if the first transport block is present and the second transport block is absent, a demodulation reference signal (DMRS) for the physical uplink sharing channel is transmitted in one or more specific layers associated with the second transport block among a plurality of layers for the physical uplink sharing channel.

2. The terminal according to claim 1, wherein, if there is a first transport block and there is no second transport block, the control unit determines to transmit the first transport block and the first DMRS on one or more first layers corresponding to the first transport block, and not to transmit the second transport block and the second DMRS on one or more specific layers.

3. The terminal according to claim 1, wherein if there is a first transport block and there is no second transport block, the control unit decides to transmit the physical uplink sharing channel and the DMRS in the plurality of layers.

4. The terminal according to claim 1, wherein if there is a first transport block and there is no second transport block, the control unit decides to skip transmission on the physical uplink sharing channel.

5. A wireless communication method for a terminal, comprising the steps of: receiving instructions for a physical uplink sharing channel for transporting a first transport block and a second transport block; and determining whether, if the first transport block is present and the second transport block is absent, a demodulation reference signal (DMRS) for the physical uplink sharing channel is transmitted in one or more specific layers among a plurality of layers for the physical uplink sharing channel that are associated with the second transport block.

6. A base station comprising: a transmitting unit that transmits instructions for a physical uplink sharing channel for transporting a first transport block and a second transport block; and a control unit that determines, when the first transport block is present and the second transport block is absent, whether a demodulation reference signal (DMRS) for the physical uplink sharing channel is being transmitted in one or more specific layers among a plurality of layers for the physical uplink sharing channel that are associated with the second transport block.