Terminal, radio communication method, and base station

Abstract

To appropriately control UL transmission when more than four layers are indicated.SOLUTION: A terminal according to an aspect of the present disclosure has: a receiving section that receives indication of a physical uplink shared channel (PUSCH) for carrying a plurality of transport blocks; and a control section that, when the plurality of transport blocks are transmitted on the PUSCH, controls transmitting, on the PUSCH, a specific medium access control (MAC) subheader including a specific field set to a specific value and the plurality of transport blocks.SELECTED DRAWING: Figure 10

Description

[Technical Field]

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

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

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

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

[0005] In 3GPP Rel. 15 / 16, the maximum number of layers in the uplink (UL) is four. Support for more than four layers in UL transmission from a terminal (user terminal, User Equipment (UE)) is being considered for future wireless communication systems (e.g., 3GPP Rel. 18 and later). However, there has been insufficient consideration of the operation when UL transmission (Physical Uplink Shared Channel, PUSCH) using more than four layers is instructed. Such insufficient consideration may result in increased implementation complexity and reduced resource utilization efficiency.

[0006] Therefore, one object of the present disclosure is to provide a terminal, a wireless communication method, and a base station that appropriately control UL transmission when more than four layers are specified. [Means for solving the problem]

[0007] A terminal according to one embodiment of the present disclosure includes a receiving unit that receives an indication of a physical uplink shared channel (PUSCH) for carrying a plurality of transport blocks, and a control unit that controls, when the plurality of transport blocks are transmitted on the PUSCH, transmission of a specific medium access control (MAC) subheader including a specific field set to a specific value and the plurality of transport blocks on the PUSCH. [Effects of the Invention]

[0008] According to one aspect of the present disclosure, UL transmission can be appropriately controlled when more than four layers are indicated. [Brief explanation of the drawings]

[0009] [Figure 1] Figure 1 shows an example of gNB recognition in the case where the received strength of PUSCH DMRS exceeds a certain value. [Figure 2] Figure 2 shows an example of gNB recognition in the case where the received strength of the PUSCH DMRS does not exceed a certain value. [Figure 3] FIG. 3 shows an example of UL skipping in a 2TB PUSCH. [Figure 4] FIG. 4 shows a first part of an example of a CW-to-layer mapping for spatial multiplexing. [Figure 5] FIG. 5 shows a second part of an example of CW-to-layer mapping for spatial multiplexing. [Figure 6] FIG. 6 shows a third part of an example of CW-to-layer mapping for spatial multiplexing. [Figure 7] FIG. 7 shows an example of UL skipping. [Figure 8] 8A-8C show an example of a MAC subheader for the UL-SCH. [Figure 9] 9A-9C show another example of a MAC subheader for the UL-SCH. [Figure 10] 10A to 10C show an example of a MAC subheader for a UL-SCH according to embodiment 1-1. [Figure 11] 11A to 11C show another example of a MAC subheader for a UL-SCH according to embodiment 1-1. [Figure 12] FIG. 12 shows an example of a table L showing LCID values ​​for the UL-SCH. [Figure 13] FIG. 13 shows an example of a table Lb showing eLCID values ​​for UL-SCH. [Figure 14] FIG. 14 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 15] FIG. 15 is a diagram illustrating an example of the configuration of a base station according to an embodiment. [Figure 16] FIG. 16 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. [Figure 17] FIG. 17 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. [Figure 18] FIG. 18 is a diagram illustrating an example of a vehicle according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

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

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

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

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

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

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

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

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

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

[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, legacy DMRS configuration type is configured, legacy DMRS configuration type 1 or 2 is configured, extended DMRS type (dmrs-TypeEnh) is not configured, and legacy DMRS port is indicated may be read interchangeably.

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

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

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

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

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

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

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

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

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

[0029] The basic Type 1 single-symbol DMRS uses ports 1000 to 1003. The basic Type 1 double-symbol DMRS uses ports 1000 to 1007. The extended Type 1 single-symbol DMRS uses ports 1000 to 1003 and 1008 to 1011. The extended Type 1 double-symbol DMRS uses ports 1000 to 1015.

[0030] Basic Type 1 single-symbol DMRS uses ports 0 to 3. Basic Type 1 double-symbol DMRS uses ports 0 to 7. Extended Type 1 single-symbol DMRS uses ports 0 to 3 and 8 to 11. Extended Type 1 double-symbol DMRS uses ports 0 to 15.

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

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

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

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

[0035] ((Notification of PUSCH DMRS port)) One or more DMRS ports used for PUSCH transmission are notified to the UE by the antenna port field in the DCI based on a table (antenna port table) for indicating antenna ports (DMRS ports) [for at least one of DMRS configuration type 1 or 2, DMRS 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 the number of REs based on the notified information.

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

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

[0038] An SRS resource set may be associated with (or group together) a predetermined number of SRS resources, each of which may be identified by an SRS Resource Indicator (SRI) or SRS Resource Identifier (ID).

[0039] The 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 SRS usage.

[0040] Here, the SRS resource type may indicate any one of periodic SRS (P-SRS), semi-persistent SRS (SP-SRS), and aperiodic SRS (A-SRS). Note that the UE may transmit P-SRS and SP-SRS periodically (or periodically after activation) and transmit A-SRS based on an SRS request in the DCI.

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

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

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

[0044] The spatial relationship information of the SRS (e.g., the RRC information element "spatialRelationInfo") may indicate spatial relationship 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 (e.g., another SRS). The SS / PBCH block may be referred to as a Synchronization Signal Block (SSB).

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

[0046] In the present disclosure, the SSB index, SSB resource ID, and SSB resource indicator (SSBRI) may be interchangeable. Also, the CSI-RS index, CSI-RS resource ID, and CSI-RS resource indicator (CRI) may be interchangeable. Also, the SRS index, SRS resource ID, and SRI may be interchangeable.

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

[0048] When the UE is configured with spatial relationship information regarding the SSB or CSI-RS and the SRS for a certain SRS resource, the UE may transmit the SRS resource using the same spatial domain filter (spatial domain transmit filter) as the spatial domain filter for receiving the SSB or CSI-RS (spatial domain receive filter). 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] When spatial relationship information regarding a certain SRS (target SRS) resource is configured between another SRS (reference SRS) and the SRS (target SRS), the UE 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) for transmitting the reference SRS. That is, 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 relationship of the PUSCH scheduled by the DCI (e.g., DCI format 0_1) based on the value of a predetermined field (e.g., an SRS resource identifier (SRI) field). Specifically, the UE may use spatial relationship information of the SRS resource (e.g., the RRC information element "spatialRelationInfo") determined based on the value of the predetermined field (e.g., the SRI) for PUSCH transmission.

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

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

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

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

[0055] If a CSI-RS (which may be referred to as an associated CSI-RS) associated with the SRS resource (or an SRS resource set to which the SRS resource belongs) is configured by a higher layer, the transmit beam for the PUSCH may be calculated based on (measurements of) the configured associated CSI-RS. Otherwise, the transmit beam for the PUSCH may be specified by the SRI.

[0056] The UE may be configured to use codebook-based PUSCH transmission or non-codebook-based PUSCH transmission by a higher layer parameter "txConfig" indicating a transmission scheme. The parameter may indicate a value of "codebook" or "non-codebook."

[0057] In this disclosure, codebook-based PUSCH (codebook-based PUSCH transmission, codebook-based transmission) may refer to a PUSCH when a UE is configured with "codebook" as the transmission scheme. In this disclosure, non-codebook-based PUSCH (non-codebook-based PUSCH transmission, non-codebook-based transmission) may refer to a PUSCH when a UE is configured with "non-codebook" as the transmission scheme.

[0058] (Transmitting on more than 4 antenna ports) Rel.15 / 16 NR supports uplink (UL) multi-input multi-output (MIMO) transmission with up to four layers. To achieve higher spectral efficiency for future wireless communication systems, support for UL transmission with more than four layers is being considered. For example, for Rel.18 NR, maximum 6-rank transmission using six antenna ports and maximum 6- or 8-rank transmission using eight antenna ports are being considered.

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

[0060] In the antenna layout, 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 becomes a cross-polarized antenna.

[0061] An antenna group may be referred to as a coherent group. A coherent group may include 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 / SRS resource set / RS resource set / spatial relation information / 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 for codebook or non-codebook. Also, each coherent group may correspond to a different received TRP. Also, the coherent group may be called a coherent antenna group, a port group, an antenna set, etc.

[0063] The UE may report supported antenna groups, antenna configuration information, and the number of coherent antennas as UE capability information. The UE may also be configured with coherent groups (e.g., the number of coherent groups and the number of ports included in each coherent group) via higher layer signaling.

[0064] The number of panels on which the antennas are arranged, the orientation of the panels, the coherency of each panel / antenna (fully coherent, partially coherent, non-coherent, etc.), the antenna arrangement in a particular 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 spacings between the centers of adjacent antenna groups, respectively.

[0065] Furthermore, while Rel. 15 / 16 NR supported transmission of one codeword (CW) in one PUSCH, for Rel. 18 NR, UE transmission of more than one CW in one PUSCH is being considered. 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. The TB may also be obtained by decoding the CW.

[0066] In Rel. 17 NR and earlier, transmission of two TBs (e.g., TB#1 and TB#2) is supported in DL transmission (e.g., PDSCH transmission). When two TBs (e.g., TB#2) are supported, a predetermined field for TB#1 and a predetermined field for TB#2 may be included in the DCI (e.g., DCI format 1_1) used for scheduling the PDSCH. The predetermined field may be, for example, at least one of a modulation and coding scheme, a new data indicator, and a redundancy version.

[0067] The support (or enablement) of dual CWs in PUSCH transmission may be notified to the UE by a predetermined higher layer parameter. The predetermined higher layer parameter may be a higher layer parameter related to the maximum number of CWs scheduled by DCI (e.g., maxNrofCodeWordsScheduledByDCI). The predetermined higher layer parameter (e.g., maxNrofCodeWordsScheduledByDCI) may be included in 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), this 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 PDSCH, this may mean that a field for TB#2 is present (or that two codeword transmission is enabled).

[0069] If a predetermined higher layer parameter (e.g., maxNrOfCodeWordsScheduledByDCI) indicates that two codeword transmission is enabled, one of the two transport blocks may be disabled by the DCI format if a predetermined condition is met. For example, the predetermined condition may be a MCS index (e.g., I MCS ) and the RV index are respectively set to predetermined values ​​(for example, I MCS = 26 and RV = 1).

[0070] In this way, a predetermined upper layer parameter is set to a predetermined value (e.g., maxNrofCodeWordsScheduledByDCI=2), and I MCS If there is a TB with RV=26 and RV=1, the corresponding TB may be disabled to realize dynamic indication (or switching) between the case where there are more than four layers and the case where there are less than four layers for the PDSCH.

[0071] In the present disclosure, 8Tx [PUSCH] transmission, 2TB [PUSCH] transmission, 2CW [PUSCH] transmission, and [PUSCH] transmission using more than four [antenna] ports may be read as interchangeable.

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

[0073] N SRS It is being considered that a method based on existing specifications will be supported for NCB-based 8Tx PUSCH transmission using >4, where N SRS is the number of single-port SRS resources configured in the SRS resource set. SRS =8 and L max Extend the existing SRI indication table to include L = 8, where L max is the maximum number of MIMO layers. In the SRI indication for the NCB-based PUSCH, a selection may be made between a bitmap indication and a method based on existing specifications.

[0074] To configure PUSCH transmission by an 8Tx UE, it is considered that the maximum number of MIMO layers will be RRC configured by extending the range of maxRank and maxMIMO-Layers up to 8. The maximum rank will be configured by RRC signaling.

[0075] To support dual CW PUSCH transmission for ranks greater than four by an 8Tx UE, a second MCS field (5 bits) is considered to be indicated for the second CW (CW1) for MCS indication. To support dual CW PUSCH transmission for ranks greater than four by an 8Tx UE, a second set of new data indicator (NDI, 1 bit) and redundancy version (RV, 2 bits) fields is considered to be indicated. That is, additional MCS / NDI / RV for the second CW are supported.

[0076] The maxMIMO-Layers in the serving cell PUSCH configuration (PUSCH-ServingCellConfig) is the maximum number of MIMO layers for 8Tx PUSCH, and the value ranges of the existing parameters maxRank and maxMIMO-Layers are extended from 1 to 8. The maxMIMO-LayersDCI-0-2 in the serving cell PUSCH configuration (PUSCH-ServingCellConfig) is the maximum number of MIMO layers for 8Tx PUSCH, and the value ranges of the existing parameters maxRank and maxMIMO-Layers are extended from 1 to 8.

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

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

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

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

[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, and when UL transmission is performed using more than four MIMO layers, the UE will transmit two TBs.

[0082] (UL Skipping) [MAC Protocol Specification / MAC Procedure / UL-SCH Transmission / Multiplexing and Assembly / Logical Channel Prioritization / Resource Allocation] The MAC entity performs the following procedure x:

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

[0084] ◆ Step 2: Otherwise from step 1, if the MAC entity is configured with SkipUplinkTxDynamic with value true and the grant indicated to the HARQ entity is addressed to a C-RNTI or is a configured UL grant, the MAC entity performs the following steps: There is no aperiodic CSI requested for this PUSCH transmission, and The MAC PDU contains zero MAC SDUs, and - If the MAC PDU contains only periodic BSRs and no data is available for any LCG, or if the MAC PDU contains only padding BSRs, --The MAC entity does not generate MAC PDUs for the HARQ entity.

[0085] In this way, a UE that has been configured by RRC for UL skipping (enhancedSkipUplinkTxDynamic / enhancedSkipUplinkTxConfigured / skipUplinkTxDynamic with value true) can, based on its own autonomous decision, stop generating MAC PDUs (skip UL transmission) if a configured or dynamic grant is present but no UL data is present.

[0086] The gNB must distinguish between two operations: ◆ Action 1: As a result of the UE autonomously performing UL skipping, the PUSCH is not received by the gNB. In this case, the gNB does not do anything in particular. ◆ Operation 2: The UE transmits a PUSCH, but the PUSCH is not correctly received by the gNB due to channel conditions, etc. In this case, the gNB transmits a DCI to prompt HARQ retransmission.

[0087] In existing specifications (prior to Rel. 18), the maximum number of MIMO layers transmitted by a UE is four, so the UE transmits one TB in the PUSCH. The gNB can determine that UL skipping has occurred from the received strength of the PUSCH DMRS based on the UL grant, for example, as follows: When the received strength of the PUSCH DMRS at the gNB exceeds a certain value (is equal to or greater than a certain value), the gNB determines that the PUSCH can be received (or that the PUSCH is being transmitted), and performs decoding of the PUSCH, as in the example of Figure 1. If decoding fails, the gNB issues a HARQ retransmission command via DCI. ◆If the received strength of the PUSCH DMRS at the gNB is equal to or less than a certain value (is less than a certain value), the gNB determines that the PUSCH cannot be received (or that the PUSCH is not being transmitted), as in the example of 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 a UE is 8, and in a transmission using more than four layers, the UE transmits two TBs. When a UE is instructed to transmit using more than four layers, the following two cases are possible:

[0089] ◆Case 1: The UE performs UL skipping for both TBs [of two TBs]. In this case, the UE discontinues the PUSCH and does not transmit the PUSCH DMRS. The gNB can decide not to decode the PUSCH based solely on the PUSCH DMRS received strength.

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

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

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

[0093] However, when 2TB PUSCH is configured / instructed, the UE's behavior for the gNB to determine whether 2TB has been transmitted has not been fully considered.

[0094] In this regard, the following determination method A is considered.

[0095] ◆Judgment method A The gNB can determine whether it has received the PUSCH DMRS for each MIMO layer based on at least one of the following two values ​​x: -◆Value 1: Received power per DMRS port. -◆Value 2: Correlation between the received signal for each DMRS port and the [PUSCH DMRS] replica [received signal].

[0096] To achieve this determination method A, when the UE performs UL skipping on one of the two specified TBs (e.g., TB2), the UE may stop PUSCH DMRS transmission on the DMRS port corresponding to the MIMO layer associated with that one TB.

[0097] If a UE is instructed / configured to transmit two TBs and the UE / MAC entity does not generate a MAC PDU for a HARQ buffer associated with one of the two instructed TBs, the UE / MAC entity may stop transmitting PUSCH DMRS on all DMRS ports corresponding to all MIMO layers associated with that TB and PUSCH corresponding to all MIMO layers associated with that TB.

[0098] As in the example of FIG. 7, when the UE performs UL skipping in TB2 (CW1), the UE may stop PUSCH DMRS transmission in the DMRS port corresponding to the MIMO layer associated with TB2.

[0099] For value 1, in the case of basic DMRS type 1, DMRS max 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, because DMRS port 3 and DMRS port 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 a threshold and whether the received power of DMRS port 4 (CW1) exceeds a 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.

[0100] For 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 port 2 and DMRS port 3 are mapped to the same physical resources (time and frequency resources) and are CDM-modulated using different FD-OCCs. The DMRS sequence for DMRS port 2 is multiplied by FD-OCC [+1 +1], and the DMRS sequence for DMRS port 2 is multiplied by [+1 -1]. The gNB can determine whether the correlation for DMRS port 2 (CW0) exceeds a threshold by calculating the correlation between the received signal and the received signal replica obtained by multiplying the DMRS sequence for DMRS port 2 by FD-OCC [+1 +1]. The gNB can determine whether the correlation for DMRS Port 3 (CW1) exceeds a threshold by calculating the correlation between the received signal and a received signal replica obtained by multiplying the DMRS sequence for DMRS Port 3 by FD-OCC[+1 -1]. 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.

[0101] (MAC PDU(UL-SCH)) [MAC Protocol Specification / PDU and Format and Parameters / PDU] The MAC sublayer provides data transfer services on the following UL logical channels: Common control channel (CCCH): This channel is used for transmitting control information between the UE and the network. This channel is used for UEs that do not have an RRC connection with the network. Dedicated control channel (DCCH): This channel is a point-to-point bidirectional channel that transmits dedicated control information between the UE and the network. This channel is used for UEs that have an RRC connection with the network. Dedicated traffic channel (DTCH): This channel is a point-to-point channel dedicated to one UE for the transfer of user information. This channel can exist in both the UL and DL.

[0102] CCCH and DCCH are control channels. DTCH is a traffic channel. The logical channels CCCH, DCCH and DTCH are mapped to the transport channel UL-SCH.

[0103] A MAC PDU is a bit string that is byte-aligned in length (i.e., has a length that is a multiple of 8 bits). The bit string is represented by a table with the most significant bit being the leftmost bit of the first row of the table and the least significant bit being the rightmost bit of the last row of the table. More generally, the bit string is read from left to right, and then the rows are read in order. The bit order of each parameter field in the MAC PDU is such that the leftmost bit represents the first most significant bit and the rightmost bit represents the last least significant bit.

[0104] A MAC SDU is a string of bits that is byte-aligned in length (i.e., has a length that is a multiple of 8 bits) and is included in the MAC PDU bit-first.

[0105] The MAC CE is a bit string that is byte-aligned in length (ie, has a length that is a multiple of 8 bits).

[0106] The MAC subheaders are bit strings whose length is byte-aligned (i.e., whose length is a multiple of 8 bits). Each MAC subheader immediately precedes the corresponding MAC SDU, MAC CE, or padding.

[0107] A MAC PDU consists of one or more MAC sub-PDUs, each of which consists of one of the following: ◆MAC subheader only (including padding). ◆MAC subheader and MAC SDU. ◆MAC subheader and MAC CE. ◆MAC subheader and padding.

[0108] The MAC SDU is of variable length.

[0109] Each MAC subheader corresponds to a MAC SDU or a MAC CE or padding.

[0110] The MAC subheader, excluding the fixed size MAC CE, padding, and MAC SDUs including the UL CCCH, consists of the header field R / F / LCID / (eLCID) / L. The MAC subheader for the fixed size MAC CE and padding consists of the header field R / LCID / (eLCID). The MAC subheader for the MAC SDUs including the UL CCCH consists of the header field (LX) / R / LCID.

[0111] Figure 8A shows an example of a MAC subheader including an LCID field and an 8-bit L field. Figure 8B shows an example of a MAC subheader including an LCID field, an 8-bit eLCID field, and an 8-bit L field. Figure 8C shows an example of a MAC subheader including an LCID field, a 16-bit eLCID field, and an 8-bit L field. Figure 9A shows an example of a MAC subheader including an LCID field and a 16-bit L field. Figure 9B shows an example of a MAC subheader including an LCID field, an 8-bit eLCID field, and a 16-bit L field. Figure 9C shows an example of a MAC subheader including an LCID field, a 16-bit eLCID field, and a 16-bit L field.

[0112] (MAC Subheader for UL-SCH) [MAC Protocol Specifications / PDUs, Formats and Parameters / Formats and Parameters] The MAC subheader may include at least one of the following fields: LCID: The Logical Channel ID (LCID) field identifies the logical channel instance of the corresponding MAC SDU (following this MAC subheader) for the UL-SCH, or the type of MAC CE (following this MAC subheader) and padding. The LCID field is 6 bits long. If the LCID field is set to 34, there is one additional octet containing the eLCID field in this MAC subheader, and that one additional octet follows the octet containing the LCID field. If the LCID field is set to 33, there are two additional octets containing the eLCID field in this MAC subheader, and that two additional octets follow the octet containing the LCID field. ◆ eLCID: For UL-SCH, the extended logical channel ID (eLCID) field identifies the logical channel instance of the corresponding MAC SDU or the type of the corresponding MAC CE. ◆L: The Length (L) field indicates the length in bytes of the corresponding MAC SDU or the corresponding variable-size MAC CE. There is one L field per MAC subheader, excluding subheaders corresponding to fixed-size MAC CEs, padding, and MAC SDUs containing UL CCCH. The size of the L field is indicated by the F field. ◆F: The Format (F) field indicates the length of the L field. There is one F field per MAC subheader, excluding subheaders corresponding to fixed size MAC CE, padding, and MAC SDUs including UL CCCH. The size of the F field is 1 bit. A value of 0 indicates an 8-bit L field. A value of 1 indicates a 16-bit L field. ◆R: Reserved bit, set to 0.

[0113] (Issues) However, in the UE / gNB, the implementation of the above-described determination method A may be complicated. Thus, if sufficient consideration is not given to the operation related to PUSCH transmission when 2TB PUSCH is configured / instructed, it may lead to an increase in implementation complexity and a decrease in resource utilization efficiency.

[0114] Therefore, the present inventors came up with an idea of ​​an operation related to PUSCH transmission when 2TB PUSCH is configured / instructed.

[0115] (Various reading changes, etc.) Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. Wireless communication methods according to the embodiments may be applied independently or in combination.

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

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

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

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

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

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

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

[0123] In the present disclosure, ceil(x), ceiling function, and ceiling function may be interchangeable. In the present disclosure, floor(x), floor function, and floor function may be interchangeable. In the present disclosure, sqrt(x), square root, and square root may be interchangeable. In the present disclosure, x mod y, mod(x,y), mod function, and modulo operation may be interchangeable. In the present disclosure, Σ i=M N f(i), the summation of f(i) over i = M, M+1,...,N, and f(M) + f(M+1) +... + f(N) may be interpreted interchangeably. C(x,y) represents the number of combinations of x to y (combinatorial coefficient), and is also called the binomial coefficient.

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

[0125] In the present disclosure, the terms constant value, fixed value, set value, and threshold value may be interpreted as interchangeable.

[0126] In this disclosure, the terms UE, MAC entity (of the UE), and upper layer (of the UE) may be interchangeable. In this disclosure, the terms UE, physical (PHY) layer (of the UE), and lower layer (of the UE) may be interchangeable. In this disclosure, the terms HARQ buffer (of the UE), HARQ process, and HARQ entity (of the UE) may be interchangeable.

[0127] In this disclosure, with respect to notification between the MAC entity and the physical layer, the terms transmit, provide, indicate, and instruct may be read interchangeably. In this disclosure, with respect to notification between the MAC entity and the physical layer, the terms receive, be provided, be indicated, and be instructed may be read interchangeably.

[0128] In the present disclosure, skipping, stop, cancellation, and drop may be read interchangeably.

[0129] In this disclosure, the terms UL transmission, logical channel, UL-SCH, one or more MAC PDUs, one or more TBs, and PUSCH may be interchangeable. In this disclosure, the terms UE transmitting one or more TBs on a PUSCH, UE transmitting a PUSCH using one or more TBs, and UE transmitting a PUSCH carrying one or more TBs may be interchangeable.

[0130] In this disclosure, LCID [value / index] and LCID field [codepoint] may be read interchangeably.

[0131] (Wireless communication method) In the present disclosure, condition A [being satisfied] and receiving an indication / configuration of a PUSCH (multi-TB PUSCH) for carrying multiple TBs (TB1, TB2, . . . ) may be read as interchangeable.

[0132] The condition A may be one of the following conditions Ax, or may be an AND result of two or more conditions. ◆Condition A1: A value greater than 4 is set as the maximum number of PUSCH layers. ◆Condition A2: A value greater than 4 is specified as the rank or number of layers of the PUSCH.

[0133] 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 the [CB-based] PUSCH and the number of [MIMO] layers for the [NCB-based] PUSCH. In the present disclosure, the terms "MIMO layer" and "layer index" used for transmitting PUSCH may be interchangeable. In the present disclosure, the terms "number of [MIMO] layers" and "rank" may be interchangeable. In the present disclosure, the terms "number of [MIMO] layers" and "rank" may be interchangeable.

[0134] In the present disclosure, the terms "indicating / setting the rank or number of layers of a PUSCH," "indicating / setting the PUSCH," "DCI for scheduling / activation of a PUSCH," "[UL] grant," "dynamic grant," and "configured grant" may be interchangeable.

[0135] In the present disclosure, UL skipping configured [having a value true], a MAC entity / UE configured for UL skipping [having a value true], a MAC entity / UE receiving a UL skipping configuration [having a value true], and a UL skipping configuration [having a value true] may be interchangeable. In the present disclosure, the UL skipping configuration, the RRC IE for UL skipping, enhancedSkipUplinkTxDynamic / enhancedSkipUplinkTxConfigured / skipUplinkTxDynamic may be interchangeable.

[0136] In the present disclosure, condition B [is met], the UE / MAC entity does not generate MAC PDUs for one or more TBs [associated with HARQ buffers] of the specified TBs, the UE / MAC entity generates N-1 MAC PDUs for only N-1 TBs [associated with HARQ buffers] of the specified N TBs, there is no [UL data corresponding to] one or more TBs of the specified TBs, there is [UL data corresponding to] only N-1 TBs of the specified N TBs, and the size of the data [to be transmitted] for the specified N TBs is less than or equal to the size of N-1 TBs may be read as interchangeable.

[0137] In the present disclosure, the following may be interpreted interchangeably: condition B is not met; the UE / MAC entity generates multiple MAC PDUs corresponding to the indicated multiple TBs; there is [UL data corresponding to] the indicated multiple TBs; and the size of the data [to be transmitted] for the indicated N TBs is less than or equal to the size of N-1 TBs.

[0138] The condition B may be an AND result of one or more conditions among the following multiple conditions Bx. ◆Condition B1: The grant instructed to the UE / HARQ entity was addressed to the C-RNTI. ◆Condition B2: The grant indicated to the UE / HARQ entity is a configured UL grant. ◆Condition B3: There is no UCI to be multiplexed onto this PUSCH transmission. ◆ Condition B4: There is no aperiodic CSI requested for this PUSCH transmission. ◆Condition B5: The MAC PDU [corresponding to one of the two indicated TBs] contains zero MAC SDUs. ◆Condition B6: The MAC PDU [corresponding to one of the two indicated TBs] contains only periodic BSRs and no data is available for any LCG [corresponding to one of the two indicated TBs], or the MAC PDU [corresponding to one of the two indicated TBs] contains only padding BSRs. ◆Condition B7: UL skipping is set. ◆Condition B8: The UE reports capability information corresponding to any of the following embodiments:

[0139] In this disclosure, UL data (to be transmitted), TB, CW, HARQ buffer, and MAC PDU may be interchangeable. TB / CW may be associated with a HARQ buffer. A HARQ buffer may be associated with a MAC PDU. One MAC PDU may correspond to one TB.

[0140] In the present disclosure, the following states / actions may be interchangeable. ◆The UE transmits one TB. The UE is instructed / configured to transmit one TB, or the UE is instructed / configured to transmit two TBs and performs UL skipping for one of the two TBs. ◆Condition A is not met, or condition A and condition B are met.

[0141] In the present disclosure, the following states / actions may be interchangeable. The UE transmits multiple TBs. ◆Multiple TBs are sent. ◆The UE is instructed / configured to transmit N TBs and does not perform UL skipping of TBs less than N (1 to N-1 TBs). Condition A is met and condition B is not met.

[0142] The UE may receive an indication of a PUSCH (UL transmission) to carry multiple TBs. When multiple TBs are transmitted on the PUSCH, the UE may control transmission on the PUSCH of a specific MAC subheader including a specific field set to a specific value, the multiple TBs, and multiple MAC PDUs including the specific MAC subheader.

[0143] <Embodiment 1> When performing UL transmission using multiple TBs (when multiple TBs are transmitted on the PUSCH), the UE may notify / report that multiple TBs are being transmitted or the number of TBs to be transmitted. A subheader of the MAC layer (MAC subheader) may be used for the notification / report. The notification / report may be performed by a specific MAC subheader including a specific field set to a specific value.

[0144] According to this embodiment, the UE can properly notify / report the number of TBs transmitted by UL transmission (PUSCH), and the gNB can properly recognize the number of TBs transmitted by that UL transmission.

[0145] This embodiment may be based on at least one of the following embodiments 1-x.

[0146] <<Embodiment 1-1>> The UE may signal / report the number of TBs transmitted by a UL transmission using a specific field in one or more MAC subheaders of the UL transmission, which may be an R (reserved bit) field.

[0147] When the UE transmits one TB, each MAC subheader in the MAC PDU corresponding to each transmitted TB may include an R field (set to value 0), similar to the existing MAC subheader consisting of the header fields R / F / LCID / (eLCID) / L described above.

[0148] When transmitting two TBs, the UE may change one or more R fields in one or more specific MAC subheaders included in two MAC PDUs corresponding to the two TBs to new fields, which may be, for example, T fields.

[0149] FIG. 10A shows an example of a MAC subheader including an LCID field and an 8-bit L field when transmitting two TBs. FIG. 10B shows an example of a MAC subheader including an LCID field, an 8-bit eLCID field, and an 8-bit L field when transmitting two TBs. FIG. 10C shows an example of a MAC subheader including an LCID field, a 16-bit eLCID field, and an 8-bit L field when transmitting two TBs. FIG. 11A shows an example of a MAC subheader including an LCID field and a 16-bit L field when transmitting two TBs. FIG. 11B shows an example of a MAC subheader including an LCID field, an 8-bit eLCID field, and a 16-bit L field when transmitting two TBs. FIG. 11C shows an example of a MAC subheader including an LCID field, a 16-bit eLCID field, and a 16-bit L field when transmitting two TBs.

[0150] When the UE transmits two TBs, it may change one or more R fields in one or more specific MAC subheaders in one or more specific MAC PDUs among the two MAC PDUs corresponding to the two TBs to T fields.

[0151] The one or more specific MAC subheaders may be the first MAC subheader in the MAC PDU corresponding to the first TB of the two TBs to be transmitted, or all MAC subheaders in the MAC PDU corresponding to the first TB of the two TBs to be transmitted, or all MAC subheaders in the two MAC PDUs corresponding respectively to the two TBs to be transmitted.

[0152] If the UE is transmitting two TBs, it may set the value of the T field to a value of 1. For example, if the UE is transmitting one TB, it may set the R field in one or more specific MAC subheaders to 0. For example, if the UE is transmitting two TBs, it may set the T field in one or more specific MAC subheaders to 1.

[0153] When the UE transmits two TBs, it may set specific fields in one or more MAC subheaders to specific values.

[0154] When the gNB receives a PUSCH, it can recognize the number of transmitted TBs from the MAC subheader in the PUSCH and transmit appropriate HARQ-ACK information for one or more transmitted TBs. For example, if a UE transmits one TB, it may receive HARQ-ACK information corresponding to that one TB. For example, if a UE transmits two TBs, it may receive HARQ-ACK information corresponding to those two TBs. If a UE is instructed / configured to transmit two TBs and transmits only one of the two TBs, it may receive HARQ-ACK information corresponding to only that one TB.

[0155] <<Embodiment 1-2>> The UE may use the LCID [field] in one or more specific MAC subheaders in the UL transmission to indicate / report the number of TBs transmitted by that UL transmission.

[0156] When transmitting multiple TBs, the UE may set the LCID in one or more specific MAC subheaders included in multiple MAC PDUs corresponding to the multiple TBs to specific values ​​(specific codepoints, specific indexes). The specific values ​​may be one or more of multiple reserved values ​​(codepoints / indexes = 37 to 42) for the LCID codepoint / index in existing specifications. The specific values ​​may be one or more of values ​​35 to 46. Multiple specific values ​​may be defined. The multiple specific values ​​may correspond to multiple values ​​of the number N of TBs to be transmitted, respectively.

[0157] 12 shows an example of Table L showing LCID values ​​for the UL-SCH. In this example, a specific LCID value of 37 indicates that a DTCH using two TBs (two MAC PDUs) is to be transmitted. In this example, a specific LCID value of 38 indicates that a DTCH using three TBs (three MAC PDUs) is to be transmitted. In this example, a specific LCID value of 39 indicates that a DTCH using four TBs (four MAC PDUs) is to be transmitted.

[0158] For example, when transmitting two TBs, the UE may set one or more LCIDs in one or more specific MAC subheaders in one or more specific MAC PDUs of two MAC PDUs corresponding to the two TBs to specific values. The specific MAC PDU may include one or more first MAC sub-PDUs and one second MAC sub-PDU. The first MAC sub-PDU may include a first MAC subheader corresponding to a UL-SCH corresponding to one of the two TBs to be transmitted and a MAC SDU corresponding to the UL-SCH. The second MAC sub-PDU may include a specific MAC subheader corresponding to a specific MAC CE and the specific MAC CE. The first MAC subheader may include an LCID indicating an identifier of a logical channel (DTCH). The specific MAC subheader may include an LCID indicating a specific value.

[0159] The one or more specific MAC PDUs may be a MAC PDU corresponding to the first of the two TBs to be transmitted, or may be two MAC PDUs corresponding respectively to the two TBs to be transmitted.

[0160] The specific value may indicate that the number of TBs to be transmitted is greater than 1, or may indicate that a specific MAC CE notifies / reports the number of TBs to be transmitted. The specific MAC CE may indicate the number of TBs to be transmitted or may include a field indicating the number of TBs to be transmitted.

[0161] <<Embodiments 1-3>> The UE may use the eLCID [field] in one or more specific MAC subheaders in the UL transmission to indicate / report the number of TBs transmitted by that UL transmission.

[0162] When transmitting multiple TBs, the UE may set eLCID in one or more specific MAC subheaders included in multiple MAC PDUs corresponding to the multiple TBs to specific values ​​(specific codepoints, specific indexes). The specific values ​​may be one or more of multiple reserved values ​​(codepoints = 0 to 218, indexes = 64 to 282) for the eLCID codepoint / index in existing specifications. The specific values ​​may be one or more of values ​​from 35 to 46. Multiple specific values ​​may be defined. The multiple specific values ​​may correspond to multiple values ​​of the number N of TBs to be transmitted, respectively.

[0163] 13 shows an example of table Lb indicating values ​​of eLCID for UL-SCH. In this example, a specific code point 216 (specific index 280) of eLCID indicates that a DTCH using two TBs (two MAC PDUs) is to be transmitted. In this example, a specific code point 217 (specific index 281) of eLCID indicates that a DTCH using three TBs (three MAC PDUs) is to be transmitted. In this example, a specific code point 218 (specific index 282) of eLCID indicates that a DTCH using four TBs (four MAC PDUs) is to be transmitted.

[0164] For example, when transmitting two TBs, the UE may set one or more eLCIDs in one or more specific MAC subheaders in one or more specific MAC PDUs among two MAC PDUs corresponding to the two TBs to specific values. The specific MAC PDU may include one or more first MAC sub-PDUs and one second MAC sub-PDU. The first MAC sub-PDU may include a first MAC subheader corresponding to a UL-SCH corresponding to one of the two TBs to be transmitted and a MAC SDU corresponding to the UL-SCH. The second MAC sub-PDU may include a specific MAC subheader corresponding to a specific MAC CE and the specific MAC CE. The first MAC subheader may include an eLCID indicating an identifier of a logical channel. The specific MAC subheader may include an eLCID indicating a specific value.

[0165] The one or more specific MAC PDUs may be a MAC PDU corresponding to the first of the two TBs to be transmitted, or may be two MAC PDUs corresponding respectively to the two TBs to be transmitted.

[0166] The specific value may indicate that the number of TBs to be transmitted is greater than 1, or may indicate that a specific MAC CE notifies / reports the number of TBs to be transmitted. The specific MAC CE may indicate the number of TBs to be transmitted or may include a field indicating the number of TBs to be transmitted.

[0167] <Embodiment 2> The UE may report that it supports the features of embodiment 1 through UE capability signaling. The UE capability signaling may be included in any of the following IEs: ◆FeatureSetUplink ◆FeatureSetUplinkPerCC ◆MIMO-ParametersPerBand

[0168] The IE (e.g., FeatureSetUplinkPerCC) including the UE capability signaling may include the capability (codebookParameter8TxPUSCH-r18 or nonCodebook-8TxPUSCH-r18) to support PUSCH transmission using more than 4 layers.

[0169] According to this embodiment, the UE can appropriately report / notify the support of the functions of Embodiment 1, and the gNB can appropriately recognize the support of the functions of Embodiment 1.

[0170] <Embodiment 3> The activation of the functions of Embodiment 1 in the UE may be set by the RRC IE [from the gNB]. The RRC IE may be included in any of the following multiple IEs. ◆PUSCH-Config ◆PUSCH-ServingCellConfig

[0171] According to this embodiment, the gNB can appropriately set / enable the functions of Embodiment 1, and the UE can be appropriately set / enabled with the functions of Embodiment 1.

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

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

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

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

[0176] In the above embodiment, the UE may receive information (QCL information) of at least one of the following several QCL rules / QCL types from the NW: ◆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)

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

[0178] In the above embodiments, the information from the NW may be set / instructed by the following methods. ◆ Common to multiple UEs or UE-specific ◆ Cell-specific or common to multiple cells ◆ Per UE / Per CC / Per BWP / Per band / Per cell / Per cell group (CG) [[ID=二十]]

[0179] [[ID=二十一]] [[ID=二十二]]<<Notification of information from UE>> [[ID=二十三]] [[ID=二十四]]The notification of any information from the UE to the NW (or equivalently, the transmission / reporting of any information from the UE to the BS) in the above embodiments may be performed using physical layer signaling (e.g., UCI), upper layer signaling (e.g., RRC signaling, MAC CE, RRC message, LPP message), specific signals / channels (e.g., UCI, PUCCH, PUSCH, PRACH, reference signal), or a combination thereof. [[ID=二十五]] [[ID=二十六]]

[0180] [[ID=二十七]] [[ID=二十八]]When the above notification is performed by MAC CE, the MAC CE may be identified by including a new LCID not defined in the existing standard in the MAC sub-header. The MAC CE may be an extension of the existing MAC CE. For example, the MAC CE may introduce a new octet to the existing MAC CE. [[ID=二十九]] [[ID=三十]]

[0181] [[ID=三十一]] [[ID=三十二]]When the above notification is performed by UCI, the above notification may be transmitted using PUCCH or PUSCH. [[ID=三十三]] [[ID=三十四]]

[0182] [[ID=三十五]] In addition, notification of any information from the UE in the above embodiments may be periodic, semi-persistent (triggered by the UE or the gNB), or aperiodic (triggered by the UE or the gNB).

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

[0184] The specific UE capabilities may indicate at least one of the following: ◆Supporting the above specific processing / action / control / assuming / information, ◆ Capabilities of each embodiment. * Capabilities of each option in each embodiment, or capabilities of a combination of multiple options in each embodiment. ◆The capabilities of each option in each embodiment, or the capabilities of a combination of multiple options in each embodiment. ◆Support LP-WUS [related functions]. Support new priority information.

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

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

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

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

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

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

[0191] (Addendum) The following inventions are added regarding one embodiment of the present disclosure. <Appendix 1> a receiver for receiving an indication of a Physical Uplink Shared Channel (PUSCH) for carrying a plurality of transport blocks; a control unit that controls, when the plurality of transport blocks are transmitted on the PUSCH, the transmission of a specific medium access control (MAC) subheader including a specific field set to a specific value and the plurality of transport blocks on the PUSCH. <Appendix 2> When one transport block is transmitted on the PUSCH, the specific field is set to 0; 2. The terminal of claim 1, wherein the specific field is set to 1 when two transport blocks are transmitted on the PUSCH. <Appendix 3> 3. The terminal according to claim 1, wherein, when the plurality of transport blocks are transmitted on the PUSCH, the MAC subheader corresponds to a MAC control element (CE). <Appendix 4> 4. The terminal according to claim 1, wherein, when the plurality of transport blocks are transmitted on the PUSCH, the specific value corresponds to the number of the plurality of transport blocks. <Appendix A> a transmitter for transmitting an indication of a Physical Uplink Shared Channel (PUSCH) for carrying a plurality of transport blocks; a control unit that controls reception of a specific medium access control (MAC) subheader including a specific field set to a specific value and the multiple transport blocks on the PUSCH when the multiple transport blocks are transmitted on the PUSCH. <Supplementary information> The terminal in Supplementary Notes 1 to 4 may be a user terminal 20. The receiver / transmitter in Supplementary Notes 1 to 4 may be a transceiver 220. The controller in Supplementary Notes 1 to 4 may be a controller 210. The base station in Supplementary Notes A may be a base station 10. The receiver / transmitter in Supplementary Notes A may be a transceiver 120. The controller in Supplementary Notes A may be a controller 110.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0262] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), or other suitable storage medium. The memory 1002 may also be referred to as a register, a cache, a main memory, or the like. The memory 1002 may store executable programs (program codes), software modules, and the like for implementing a wireless communication method according to an embodiment of the present disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. a receiver for receiving an indication of a Physical Uplink Shared Channel (PUSCH) for carrying a plurality of transport blocks; A terminal having a control unit that controls the transmission of a specific medium access control (MAC) subheader including a specific field set to a specific value and the multiple transport blocks on the PUSH when the multiple transport blocks are transmitted on the PUSH.

2. When one transport block is transmitted on the PUSCH, the specific field is set to 0; The terminal of claim 1 , wherein the specific field is set to 1 when two transport blocks are transmitted on the PUSCH.

3. The terminal of claim 1 , wherein when the plurality of transport blocks are transmitted on the PUSCH, the MAC subheader corresponds to a MAC control element (CE).

4. The terminal according to claim 1 , wherein, when the plurality of transport blocks are transmitted on the PUSCH, the specific value corresponds to the number of the plurality of transport blocks.

5. receiving an indication of a Physical Uplink Shared Channel (PUSCH) for carrying a plurality of transport blocks; When the plurality of transport blocks are transmitted on the PUSCH, a specific medium access control (MAC) subheader including a specific field set to a specific value and the plurality of transport blocks are controlled to be transmitted on the PUSCH.

6. a transmitter configured to transmit an indication of a Physical Uplink Shared Channel (PUSCH) for carrying a plurality of transport blocks; a control unit that controls reception of a specific medium access control (MAC) subheader including a specific field set to a specific value and the multiple transport blocks on the PUSCH when the multiple transport blocks are transmitted on the PUSCH.

Images