Terminal, wireless communication method, base station and system

Abstract

A terminal according to an aspect of the present disclosure comprises: a receiving unit that, when receiving information indicating that a plurality of code words are scheduled by one piece of downlink control information with respect to a physical uplink shared channel, receives the downlink control information including information related to the number of scheduled code words; and a control unit that, on the basis of the information related to the number of code words, performs a control related to a field corresponding to a particular code word included in the downlink control information. According to an aspect of the present disclosure, a PUSCH transmission for a plurality of CWs can be appropriately performed.

Description

[Technical Field]

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

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

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

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

[0005] For future wireless communication systems (e.g., Rel. 18 NR), it has been considered that a user terminal (User Equipment (UE)) will transmit multiple code words (CWs) using an uplink shared channel (Physical Uplink Shared Channel (PUSCH)). However, the details of this operation have not been fully explored. For example, how to support Code Block Group (CBG)-based transmission when multiple CWs are transmitted on a PUSCH has not been fully explored. If PUSCH transmission for multiple CWs is not performed appropriately, there is a risk that throughput will decrease and communication quality will deteriorate.

[0006] Therefore, the present disclosure provides a terminal and a wireless communication method that appropriately perform PUSCH transmission for multiple CWs. 、 base station and systems One of the aims is to provide [Means for solving the problem]

[0007] A terminal according to one embodiment of the present disclosure receives a physical uplink shared channel (PUSCH) send a receiver for receiving higher layer signaling indicating that up to two transport blocks (TBs) are scheduled by one downlink control information (DCI); and the DCI; The higher layer signaling configures that up to two TBs are scheduled by the DCI; PUSCH Sending record If the number of TBs is greater than 4, then a maximum of two TBs are scheduled by the DCI. Sending record and a control unit that determines that one TB is scheduled by the DCI when the number of ears is four or less. [Effects of the Invention]

[0008] According to one aspect of the present disclosure, PUSCH transmission for multiple CWs can be performed appropriately. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram illustrating an example of the association between precoder types and TPMI indices. [Figure 2] 2A-2C are diagrams illustrating an example of PUSCH transmission using multiple panels. [Figure 3] 3A to 3C are diagrams showing examples of methods 1 to 3 of simultaneous UL transmission using multiple panels. [Figure 4] 4A and 4B are diagrams showing an example of the bit configuration of the CBGTI field in the first embodiment. [Figure 5] 5A and 5B are diagrams illustrating an example of bit values ​​of the DCI field in the second embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of the configuration of a base station according to an embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0010] (Repeated transmission) Rel. 15 supports repeated transmission in data transmission. For example, a base station (network (NW), gNB) may repeat transmission of DL data (e.g., downlink shared channel (PDSCH)) a predetermined number of times. Alternatively, a UE may repeat transmission of UL data (e.g., uplink shared channel (PUSCH)) a predetermined number of times.

[0011] The UE may be scheduled for a predetermined number of repeated PUSCH transmissions by a single DCI, which may also be referred to as a repetition factor K or aggregation factor K.

[0012] The n-th repetition may also be referred to as the n-th transmission occasion, etc., and may be identified by a repetition index k (0≦k≦K−1). The repetitive transmission may be applied to a PUSCH that is dynamically scheduled in DCI (e.g., a dynamic grant-based PUSCH) or a configured grant-based PUSCH.

[0013] The UE semi-statically receives information indicating the repetition factor K (e.g., aggregationFactorUL or aggregationFactorDL) through higher layer signaling. Here, the higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, etc., or a combination thereof.

[0014] The MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. The broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), etc.

[0015] The UE controls reception processing (e.g., at least one of reception, demapping, demodulation, and decoding) of the PDSCH or transmission processing (e.g., at least one of transmission, mapping, modulation, and coding) of the PUSCH for K consecutive slots based on at least one of the following field values ​​(or information indicated by the field value) in the DCI: Allocation of time domain resources (e.g., starting symbol, number of symbols in each slot, etc.), Allocation of frequency domain resources (e.g., a predetermined number of resource blocks (RBs) and a predetermined number of resource block groups (RBGs)), Modulation and Coding Scheme (MCS) index, Configuration of the PUSCH demodulation reference signal (DMRS: Demodulation Reference Signal), PUSCH spatial relation info or Transmission Configuration Indication (TCI) state (TCI-state).

[0016] The same symbol allocation may be applied to K consecutive slots. The UE may determine the symbol allocation for each slot based on the start symbol S and the number of symbols L (e.g., Start and Length Indicator (SLIV)) determined based on the value m of a predetermined field in the DCI (e.g., the Time Domain Resource Allocation (TDRA) field). The UE may also determine the first slot based on K2 information determined based on the value m of a predetermined field in the DCI (e.g., the TDRA field).

[0017] On the other hand, among the K consecutive slots, the redundancy versions (RVs) applied to TBs based on the same data may be the same or at least partially different. For example, the RV applied to the TB in the n-th slot (transmission opportunity, repetition) may be determined based on the value of a predetermined field (e.g., RV field) in the DCI.

[0018] In Rel. 15, the PUSCH can be repeatedly transmitted across multiple slots (in slot units). In Rel. 16 and later, repeated transmission of the PUSCH in units shorter than slots (for example, in subslot units, minislot units, or units of a predetermined number of symbols) is supported.

[0019] The UE may determine symbol allocation for PUSCH transmission (e.g., PUSCH with k=0) in a predetermined slot based on the start symbol S and the number of symbols L determined based on the value m of a predetermined field (e.g., the TDRA field) in the DCI of the PUSCH. Note that the UE may determine the predetermined slot based on Ks information determined based on the value m of a predetermined field (e.g., the TDRA field) of the DCI.

[0020] The UE may dynamically receive information indicating the repetition factor K (e.g., number of repetitions) via downlink control information. The repetition factor may be determined based on the value m of a predetermined field (e.g., the TDRA field) in the DCI. For example, a table may be supported that defines the correspondence between the bit value notified by the DCI, the repetition factor K, the start symbol S, and the number of symbols L.

[0021] Slot-based repetitive transmission may be referred to as repetition transmission type A (eg, PUSCH repetition Type A), and sub-slot-based repetitive transmission may be referred to as repetition transmission type B (eg, PUSCH repetition Type B).

[0022] The UE may be configured to apply at least one of repetitive transmission type A and repetitive transmission type B. For example, the base station may notify the UE of the repetitive transmission type applied by the UE by higher layer signaling (e.g., PUSCHRepTypeIndicator).

[0023] For each DCI format that schedules the PUSCH, either the repetitive transmission type A or the repetitive transmission type B may be configured in the UE.

[0024] For example, for a first DCI format (e.g., DCI format 0_1), if higher layer signaling (e.g., PUSCHRepTypeIndicator-AorDCIFormat0_1) is set to repetitive transmission type B (e.g., PUSCH-RepTypeB), the UE applies repetitive transmission type B for PUSCH repetitive transmissions scheduled in the first DCI format. Otherwise (e.g., if PUSCH-RepTypeB is not set or if PUSCH-RepTypA is set), the UE applies repetitive transmission type A for PUSCH repetitive transmissions scheduled in the first DCI format.

[0025] (PUSCH precoder) In NR, it is being considered that a UE will support at least one of codebook (CB)-based transmission and non-codebook (NCB)-based transmission.

[0026] For example, it is being considered that a UE uses at least a sounding reference signal (SRS) resource indicator (SRI) to determine a precoder (precoding matrix) for CB-based and / or NCB-based Physical Uplink Shared Channel (PUSCH) transmission.

[0027] In the case of CB-based transmission, the UE may determine a precoder for PUSCH transmission based on the SRI, a Transmitted Rank Indicator (TRI), a Transmitted Precoding Matrix Indicator (TPMI), etc. In the case of NCB-based transmission, the UE may determine a precoder for PUSCH transmission based on the SRI.

[0028] The SRI, TRI, TPMI, etc. may be notified to the UE using Downlink Control Information (DCI). The SRI may be specified by the SRS Resource Indicator field (SRI field) of the DCI, or may be specified by the parameter "srs-ResourceIndicator" included in the RRC information element "ConfiguredGrantConfig" of the configured grant PUSCH. The TRI and TPMI may be specified by the "Precoding information and number of layers" field of the DCI.

[0029] The UE may report UE capability information related to a precoder type, and the base station may configure the precoder type based on the UE capability information through higher layer signaling. The UE capability information may be information on the precoder type used by the UE in PUSCH transmission (which may be represented by the RRC parameter "pusch-TransCoherence").

[0030] In the present disclosure, higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, and the like, or a combination thereof.

[0031] The MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. The broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), etc.

[0032] The UE may determine a precoder to be used for PUSCH transmission based on precoder type information (which may be represented by the RRC parameter "codebookSubset") included in PUSCH configuration information ("PUSCH-Config" information element of RRC signaling) notified by higher layer signaling. The UE may be configured with a subset of the PMI specified by the TPMI by the codebookSubset.

[0033] The precoder type may be specified by any one of full coherent, partial coherent, and non-coherent, or a combination of at least two of these (for example, it may be expressed by parameters such as "fully and partial and non-coherent" or "partial and non-coherent").

[0034] Fully coherent may mean that all antenna ports used for transmission are synchronized (may also be expressed as being able to match the phase, being able to control the phase for each coherent antenna port, being able to apply a precoder appropriately for each coherent antenna port, etc.). Partially coherent may mean that some of the antenna ports used for transmission are synchronized, but those some ports cannot be synchronized with other ports. Non-coherent may mean that each antenna port used for transmission cannot be synchronized.

[0035] Note that a UE that supports a fully coherent precoder type may be assumed to support partially coherent and non-coherent precoder types, and a UE that supports a partially coherent precoder type may be assumed to support a non-coherent precoder type.

[0036] The precoder type may be interpreted as coherency, PUSCH transmission coherence, coherent type, coherence type, codebook type, codebook subset, codebook subset type, or the like.

[0037] The UE may determine, from multiple precoders (which may also be called precoding matrices, codebooks, etc.) for CB-based transmission, a precoding matrix corresponding to a TPMI index obtained from the DCI (e.g., DCI format 0_1, etc.) that schedules the UL transmission.

[0038] Figure 1 shows an example of the association between precoder types and TPMI indices. Figure 1 corresponds to a table of precoding matrix W for single-layer (rank 1) transmission using four antenna ports in DFT-s-OFDM (Discrete Fourier Transform spread OFDM, in which transform precoding is effective).

[0039] In FIG. 1, when the precoder type (codebookSubset) is fullyAndPartialAndNonCoherent, the UE is notified of a TPMI of one of 0 to 27 for single layer transmission. When the precoder type is partialAndNonCoherent, the UE is configured with a TPMI of one of 0 to 11 for single layer transmission. When the precoder type is noncoherent, the UE is configured with a TPMI of one of 0 to 3 for single layer transmission.

[0040] As shown in Figure 1, a precoding matrix in which only one element in each column is not zero may be called a non-coherent codebook. A precoding matrix in which a predetermined number (not all) of elements in each column are not zero may be called a partially coherent codebook. A precoding matrix in which all elements in each column are not zero may be called a fully coherent codebook.

[0041] Non-coherent and partially coherent codebooks may be referred to as antenna selection precoders, and fully coherent codebooks may be referred to as non-antenna selection precoders.

[0042] In the present disclosure, a partially coherent codebook may correspond to a codebook (precoding matrix) corresponding to a TPMI specified by DCI for codebook-based transmission by a UE configured with a partially coherent codebook subset (e.g., RRC parameter "codebookSubset"="partialAndNonCoherent"), excluding a codebook corresponding to a TPMI specified by a UE configured with a non-coherent codebook subset (e.g., RRC parameter "codebookSubset"="nonCoherent") (i.e., in the case of single-layer transmission with four antenna ports, codebooks with TPMI=4 to 11).

[0043] In the present disclosure, a fully coherent codebook may refer to a codebook (precoding matrix) corresponding to a TPMI specified by DCI for codebook-based transmission by a UE configured with a fully coherent codebook subset (e.g., RRC parameter "codebookSubset"="fullyAndPartialAndNonCoherent"), excluding a codebook corresponding to a TPMI specified by a UE configured with a partially coherent codebook subset (e.g., RRC parameter "codebookSubset"="partialAndNonCoherent") (i.e., in the case of single-layer transmission with four antenna ports, codebooks with TPMI=12 to 27).

[0044] (Spatial relations for SRS, PUSCH) The 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)).

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

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

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

[0048] Here, the SRS resource type may indicate any one of periodic SRS (P-SRS), semi-persistent SRS (SP-SRS), and aperiodic SRS (A-SRS, AP-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.

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

[0050] For example, the UE may determine a precoder 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.

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

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

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

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

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

[0056] In NR, transmission of uplink signals may be controlled based on the presence or absence of beam correspondence (BC). BC may be, for example, the ability of a node (e.g., a base station or a UE) to determine the beam to be used for transmitting a signal (transmit beam, Tx beam) based on the beam to be used for receiving the signal (receive beam, Rx beam).

[0057] In addition, BC may also be called transmit / receive beam correspondence (Tx / Rx beam correspondence), beam reciprocity, beam calibration, calibrated / non-calibrated, reciprocity calibrated / non-calibrated, correspondence, agreement, etc.

[0058] For example, without BC, the UE may transmit an uplink signal (e.g., PUSCH, PUCCH, SRS, etc.) using the same beam (spatial domain transmit filter) as the SRS (or SRS resource) instructed by the base station based on measurement results of one or more SRSs (or SRS resources).

[0059] On the other hand, when BC is present, the UE may transmit an uplink signal (e.g., PUSCH, PUCCH, SRS, etc.) using a beam (spatial domain transmit filter) that is the same as or corresponds to the beam (spatial domain receive filter) used to receive a specified SSB or CSI-RS (or CSI-RS resource).

[0060] When the UE is configured with spatial relationship information regarding the SSB or CSI-RS and the SRS for a certain SRS resource (e.g., with BC), 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.

[0061] When the UE is configured with spatial relationship information between another SRS (reference SRS) and the SRS (target SRS) for a resource of the SRS (target SRS) (e.g., without BC), 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. In other words, in this case, the UE may assume that the UE transmit beam of the reference SRS and the UE transmit beam of the target SRS are the same.

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

[0063] When codebook-based transmission is used for PUSCH, two SRS resources may be configured for the UE by RRC, and one of the two SRS resources may be indicated by DCI (a 1-bit predetermined field). When non-codebook-based transmission is used for PUSCH, four SRS resources may be configured for the UE by RRC, and one of the four SRS resources may be indicated by DCI (a 2-bit predetermined field). To use a spatial relationship other than the two or four spatial relationships configured by RRC, RRC reconfiguration is required.

[0064] In addition, the DL-RS can be configured for the spatial relationship of the SRS resources used for the PUSCH. For example, for SP-SRS, the UE can be configured by RRC with the spatial relationship of multiple (e.g., up to 16) SRS resources, and one of the multiple SRS resources can be indicated by the MAC CE.

[0065] (UL TCI condition) In Rel.16 NR, the use of UL TCI status as a UL beam indication method is being considered. The notification of the UL TCI status is similar to the notification of the UE's DL beam (DL TCI status). Note that the DL TCI status may be interchangeably read as the TCI status for PDCCH / PDSCH.

[0066] The channel / signal (which may be referred to as a target channel / RS) to which the UL TCI state is set (specified) may be, for example, at least one of a PUSCH (DMRS of PUSCH), a PUCCH (DMRS of PUCCH), a random access channel (Physical Random Access Channel (PRACH)), an SRS, etc.

[0067] Furthermore, the RS (source RS) that has a QCL relationship with the channel / signal may be, for example, a DL RS (e.g., SSB, CSI-RS, TRS, etc.) or a UL RS (e.g., SRS, SRS for beam management, etc.).

[0068] In the UL TCI state, an RS that has a QCL relationship with the channel / signal may be associated with a panel ID for receiving or transmitting the RS, and the association may be explicitly configured (or specified) or implicitly determined by higher layer signaling (e.g., RRC signaling, MAC CE, etc.).

[0069] The correspondence between the RS and the panel ID may be set by being included in the UL TCI state information, or may be set by being included in at least one of the resource setting information, spatial relationship information, etc. of the RS.

[0070] The QCL type indicated by the UL TCI state may be the existing QCL type AD or may be another QCL type, and may include a predetermined spatial relationship, associated antenna ports (port index), etc.

[0071] When a UE is assigned an associated panel ID for an UL transmission (e.g., specified by DCI), the UE may perform the UL transmission using the panel corresponding to the panel ID. The panel ID may be associated with a UL TCI state, and when a UL TCI state is assigned (or activated) for a given UL channel / signal, the UE may identify the panel to use for the UL channel / signal transmission according to the panel ID associated with the UL TCI state.

[0072] (Multiple panel submission) <Transmission method> In Rel. 15 and Rel. 16 UEs, only one beam and panel are used for UL transmission at a time (Figure 2A). From Rel. 17 onwards, simultaneous UL transmission using multiple beams and panels for one or more TRPs is being considered to improve UL throughput and reliability. The following describes simultaneous transmission of PUSCH, but a similar process can also be used for PUCCH.

[0073] For simultaneous UL transmission using multiple beams and multiple panels, reception by one TRP with multiple panels (Fig. 2B) or reception by two TRPs with an ideal backhaul (Fig. 2C) is considered. A single PDCCH is considered for scheduling multiple PUSCHs (e.g., simultaneous transmission of PUSCH#1 and PUSCH#2). Panel-specific transmission is considered to be supported, and a panel ID is introduced.

[0074] The base station may use the UL TCI or Panel ID to configure or indicate panel-specific transmission for UL transmission. The UL TCI (UL TCI state) may be based on signaling similar to the DL beam indication supported in Rel. 15. The Panel ID may be implicitly or explicitly applied to transmission of at least one of the target RS resource or target RS resource set, PUCCH, SRS, and PRACH. If the Panel ID is explicitly signaled, the Panel ID may be configured in at least one of the target RS, target channel, and reference RS (e.g., DL RS resource configuration or spatial relationship information).

[0075] The multi-panel UL transmission method or candidate multi-panel UL transmission method may be at least one of the following methods 1 to 3 (multi-panel UL transmission methods 1 to 3). Only one of methods 1 to 3 may be supported. Multiple methods including at least one of methods 1 to 3 may be supported, and one of the multiple methods may be configured in the UE.

[0076] 《Method 1》 Coherent multi-panel UL transmission

[0077] Multiple panels may be synchronized with each other. All layers are mapped to all panels. Multiple analog beams may be directed. The SRS Resource Indicator (SRI) field may be extended. This scheme may use up to 4 layers for the UL.

[0078] In the example of FIG. 3A, the UE maps one codeword (CW) or one transport block (TB) to L layers (PUSCH(1, 2, ..., L)) and transmits the L layers from each of two panels. Panel #1 and Panel #2 are coherent. Scheme 1 can obtain diversity gain. The total number of layers in the two panels is 2L. If the maximum total number of layers is 4, the maximum number of layers in one panel is 2.

[0079] 《Method 2》 Non-coherent multi-panel UL transmission of one codeword (CW) or transport block (TB)

[0080] Multiple panels may not be synchronized. Different layers are mapped to one CW or TB for different panels and PUSCHs from multiple panels. A layer corresponding to one CW or TB may be mapped to multiple panels. This scheme may use up to four layers or up to eight layers for the UL. If up to eight layers are supported, this scheme may support one CW or TB using up to eight layers.

[0081] In the example of FIG. 3B, the UE maps 1 CW or 1 TB to k layers (PUSCH(1, 2, ..., k)) and Lk layers (PUSCH(k+1, k+2, ..., L)), transmits the k layers from panel #1, and transmits the Lk layers from panel #2. Scheme 2 can obtain gains through multiplexing and diversity. The total number of layers in the two panels is L.

[0082] 《Method 3》 Two CW or TB non-coherent multi-panel UL transmitters

[0083] Multiple panels may not be synchronized. Different layers are mapped to different panels and two CWs or TBs for PUSCHs from multiple panels. A layer corresponding to one CW or TB may be mapped to one panel. Layers corresponding to multiple CWs or TBs may be mapped to different panels. This scheme may use up to four layers or up to eight layers for the UL. When up to eight layers are supported, this scheme may support up to four layers per CW or TB.

[0084] In the example of FIG. 3C, the UE maps CW#1 or TB#1 among 2 CWs or 2 TBs to k layers (PUSCH(1, 2, …, k)), maps CW#2 or TB#2 to L - k layers (PUSCH(k + 1, k + 2, …, L)), transmits the k layers from panel #1, and transmits the L - k layers from panel #2. Method 3 can obtain gains by multiplexing and diversity. The total number of layers in the two panels is L.

[0085] <DCI Extension> When applying the above-described Methods 1 to 3, an existing DCI may be extended. For example, at least one of the following Options 1 to 6 may be applied.

[0086] [Option 1] For Method 1, multiple PUSCHs may be indicated (scheduled) by a single PDCCH (DCI). The SRI field may be extended to indicate multiple PUSCHs. Multiple SRI fields in the DCI may be used to indicate multiple PUSCHs from multiple panels. For example, a DCI that schedules two PUSCHs may include two SRI fields.

[0087] The extension of the SRI field for Method 2 may be different from the extension of the SRI field for Method 1 in the following points. <00,00337>

[0088] Among the L layers, for layers 1, 2, …, k, the UE may use the SRI (SRS#i) first indicated by the SRI field in the DCI as a spatial filter for UL transmission from panel 1. Among the remaining layers k + 1, k + 2, …, L of the L layers, the UE may use the SRI (SRS#j) second indicated by the SRI field in the DCI as a spatial filter for UL transmission from panel 2. k may follow a predefined rule or may be explicitly indicated by the DCI.

[0089] In addition to the extension of the SRI field for Scheme 2 to support two CWs or TBs for different TRPs, at least one of the following fields in the DCI may be extended to indicate multiple PUSCHs: modulation and coding scheme (MCS) field, precoding information and number of layers field, Transmission Power Control (TPC) command for scheduled PUSCH field, Frequency Domain Resource Assignment (FDRA) field, and Time Domain Resource Assignment (TDRA) field. Different TRPs may have different path losses or SINRs.

[0090] [Option 2] Information regarding the repetition transmission type of the PUSCH may be notified to or configured in the UE by higher layer signaling. For example, if repetition transmission type B (e.g., PUSCH-RepTypeB) is not configured by higher layer signaling, the UE may apply repetition transmission type A. The repetition transmission type may be configured for each DCI format (or PUSCH type). The PUSCH type may include a dynamic grant-based PUSCH and a configuration grant-based PUSCH.

[0091] Information regarding the repetition factor, information regarding the PUSCH allocation, information regarding the spatial relationship (or precoder) to be used for PUSCH transmission, and information regarding the redundancy version to be used for PUSCH transmission may be notified to the UE by DCI or a combination of DCI and higher layer parameters.

[0092] For information on the repetition factor (e.g., K) and information on PUSCH allocation (e.g., start symbol S and PUSCH length L), multiple candidates may be defined in a table, and a specific candidate may be selected by DCI. In the following description, an example will be given in which the PUSCH repetition factor (K) is 4, but the applicable repetition factor is not limited to 4.

[0093] As for information regarding spatial relationships (hereinafter also referred to as spatial relationship information), multiple candidates may be set by higher layer signaling, and one or more pieces of spatial relationship information may be activated by at least one of DCI and MAC CE.

[0094] [Option 3] The following describes the number of bits in the TPC command field included in one DCI that schedules PUSCH transmissions across multiple TRPs, and the association between the TPC command field and a TPC-related index (e.g., a closed-loop index). A UE may control multiple PUSCH transmissions based at least on the index.

[0095] The number of bits of the TPC command field included in one DCI scheduling PUSCH transmission across multiple TRPs may be extended to a specific number (e.g., 2M) compared to the number of bits in Rel. 15 / 16. In the present disclosure, M may be the number of TRPs or the number of SRIs that may be indicated for PUSCH transmission across multiple TRPs.

[0096] For example, for codebook-based transmission, when the SRI for PUSCH transmission for two TRPs is indicated by the DCI, the TPC command field may be extended to 4 bits.

[0097] The correspondence between the extended TPC command field and a specific index (e.g., closed-loop index) related to the TPC may follow at least one of the following correspondence 1 and correspondence 2. Although the closed-loop index will be described below, the closed-loop index in the present disclosure may be replaced with any specific index related to the TPC.

[0098] [[Mapping 1]] If the extended TPC command field is divided into a specific number of bits (e.g., 2, 4, etc.), the xth (x being any integer) smallest (or largest) specific number of bits may be associated with the xth SRI / SRI combination indicated by the DCI.

[0099] [[Mapping 2]] If the extended TPC command field is divided into a specific number (e.g., two) of bits, the x-th smallest (or largest) specific number of bits may be associated with the SRI corresponding to the x-th smallest (or largest) closed-loop index indicated by the DCI.

[0100] [Option 4] When PUSCHs are repeatedly transmitted across multiple TRPs, the same number of antenna ports may be configured / instructed for different TRPs (different PUSCHs). In other words, the same number of antenna ports may be configured / instructed in common for multiple TRPs (multiple PUSCHs). In this case, the UE may assume that the same number of antenna ports is configured / instructed in common for multiple TRPs (multiple PUSCHs). In this case, the UE may determine the TPMI for PUSCH transmission according to at least one of Indication Method 1-1 or Indication Method 1-2 described below.

[0101] [[Instruction method 1-1]] The precoding information and number of layers field included in the scheduling DCI may have the same number of bits as specified in Rel.15 / 16. In this case, one precoding information and number of layers field included in one DCI may be indicated to the UE. In other words, the UE may determine a TPMI based on one precoding information and number of layers field included in one DCI. Then, the UE may apply the precoding information and number of layers field / TPMI to PUSCH transmissions of different TRPs.

[0102] [[Instruction method 1-2]] The number of bits of the precoding information and layer number fields included in the scheduling DCI may be expanded to a specific number compared to Rel. 15 / 16. The specific number may be represented as X×M.

[0103] The above X may be determined based on the size of the precoding information and the number of layers field included in the DCI for UL transmission for one TRP. For example, the above X may be determined based on at least one of the number of antenna ports and a number set by a specific upper layer parameter (e.g., at least one of ul-FullPowerTransmission, maxRank, codebookSubset, and transformPrecoder).

[0104] Alternatively, X may be a fixed value. The UE may assume that X has a fixed size regardless of the number of antenna ports configured by a higher layer. The UE may also assume that X has a fixed size regardless of the value of the Number of Antenna Ports field (the number of antenna ports indicated by the Number of Antenna Ports field).

[0105] Furthermore, when PUSCHs are repeatedly transmitted across multiple TRPs, different or the same number of antenna ports may be configured / instructed for different TRPs (different PUSCHs). In other words, the number of antenna ports may be configured / instructed separately for multiple TRPs (multiple PUSCHs). In this case, the UE may assume that the number of antenna ports is configured / instructed independently for each of the multiple TRPs (multiple PUSCHs). In this case, the UE may determine the TPMI for PUSCH transmission according to Indication Method 2 described below.

[0106] [[Instruction method 2]] The precoding information and layer number fields included in the scheduling DCI may have a bit number that is expanded to a specific number compared to Rel. 15 / 16. The specific number is X1 + X2 + ... + X M It may be expressed as:

[0107] Above X i (i is an integer from 1 to M) may be determined based on the size of the precoding information and layer number field included in the DCI for UL transmission of the i-th TRP. For example, the above X i may be determined based on at least one of the number of antenna ports and the number set by a specific upper layer parameter (e.g., at least one of ul-FullPowerTransmission, maxRank, codebookSubset, and transformPrecoder). i may be set to a fixed value.

[0108] The above M may be the number of TRPs or the number of spatial relationship information (SRI) that can be indicated for PUSCH transmission across multiple TRPs.

[0109] [Option 5] The UE may determine the SRI to apply to the PUSCH based on at least one of the SRI field of the DCI that schedules the PUSCH and the CORESET pool index of the control resource set (CORESET) for the DCI (e.g., where the DCI is detected).

[0110] The UE may determine the SRI to apply to each PUSCH based on multiple SRI fields included in the DCI scheduling the multiple PUSCHs.

[0111] The UE may determine the SRI to apply to each PUSCH based on one SRI field included in the DCI that schedules multiple PUSCHs.

[0112] The UE may determine the transmit power of the PUSCH based on the SRI field of the DCI that schedules the PUSCH. For example, the UE may determine transmit power control (TPC)-related parameters of the PUSCH based on the SRI field of the DCI that schedules the PUSCH.

[0113] [Option 6] The UE may decide to perform either repeated transmission for a single TRP or repeated transmission for multiple TRPs based on a specific field included in the DCI.

[0114] For example, when a field included in the DCI indicates that one of the first SRI field or the second SRI field is to be applied among multiple (e.g., two) SRI fields (a first SRI field and a second SRI field), the UE may determine that repeated transmission of multiple PUSCHs is to be performed at the applied SRI. In other words, when a field included in the DCI indicates that one SRI field is to be applied among multiple SRI fields, the UE may determine to perform repeated transmission of PUSCHs in a single TRP.

[0115] Furthermore, for example, when a field included in DCI indicates that both a first SRI field and a second SRI field among multiple (e.g., two) SRI fields (a first SRI field and a second SRI field) are to be applied, the UE may determine that repeated transmission of multiple PUSCHs is to be performed in multiple SRIs (e.g., multiple TRPs). In other words, when a field included in DCI indicates that multiple SRI fields are to be applied, the UE may determine to perform repeated transmission of PUSCHs in multiple TRPs.

[0116] (CBG-based transmission) Incidentally, Rel.15 / 16 NR specifies transmission in units of transport blocks (TBs) (TB-based transmission) and transmission in units of code block groups (CBGs) (CBG-based transmission). Note that transmission in the present disclosure may be interpreted as retransmission.

[0117] A CBG may be a group of one or more Code Blocks (CBs). A CB may correspond to a portion (segment) into which a TB is divided when the TB size exceeds a threshold (e.g., 6144 bits). In other words, one TB may be composed of one or more CBs.

[0118] In the present disclosure, CBG may be interchangeably read as CB, and TB may be interchangeably read as Code Word (CW).

[0119] The UE may receive UE-specific PUSCH parameter configuration information (e.g., RRC PUSCH-ServingCellConfig information element) that is common across the BWP of the serving cell. If the PUSCH-ServingCellConfig information element includes a parameter (PUSCH-CodeBlockGroupTransmission) for enabling and configuring CBG-based transmission, the UE performs CBG-based PUSCH transmission in the serving cell.

[0120] The PUSCH-CodeBlockGroupTransmission may include a parameter (maxCodeBlockGroupsPerTransportBlock) indicating the maximum number of CBGs per TB. The maximum number of CBGs per TB for the PUSCH may be set to 2, 4, 6, 8, or the like.

[0121] In Rel. 15 / 16 NR, one CW may be transmitted using one PUSCH.

[0122] When CBG-based transmission is configured, DCI format 0_1 ​​includes a field for information indicating the CBG to be transmitted / retransmitted (CBG Transmission Information (CBGTI)). The number of bits of this CBGTI field may be determined by the number of bits for the maximum number of CBGs per TB configured for the PUSCH.

[0123] If the New Data Indicator (NDI) field of the scheduling DCI indicates the first transmission of a TB, the UE may expect the CBGTI field of that DCI to indicate the full CBG of that TB, and the UE may include the full CBG of that TB.

[0124] If the NDI field of the scheduling DCI indicates that a TB should be retransmitted, the UE may include only the CBG indicated by the CBGTI field of that DCI.

[0125] A bit value of '0' in the CBGTI field indicates that the corresponding CBG is not transmitted, and a bit value of '1' in the CBGTI field indicates that the corresponding CBG is transmitted. The bit order of the CBGTI field may be an order in which the most significant bit (MSB) is mapped in order from CBG#0.

[0126] The UE may receive UE-specific PDSCH parameter configuration information (e.g., RRC PDSCH-ServingCellConfig information element) that is common across the BWP of the serving cell. If the PDSCH-ServingCellConfig includes parameters for enabling and configuring CBG-based transmission (PDSCH-CodeBlockGroupTransmission), the UE performs CBG-based PDSCH reception in the serving cell.

[0127] The PDSCH-CodeBlockGroupTransmission may include a parameter (maxCodeBlockGroupsPerTransportBlock) indicating the maximum number of CBGs per TB. The maximum number of CBGs per TB for the PDSCH may be set to 2, 4, 6, 8, etc. Note that when multiple CWs are used for the PDSCH (maxNrofCodeWordsScheduledByDCI), the maximum number of CBGs may be 4. The use of multiple CWs for the PDSCH may be determined by a parameter (maxNrofCodeWordsScheduledByDCI) in the PDSCH configuration information (RRC PDSCH-Config information element) that indicates the maximum number of CWs scheduled by one DCI.

[0128] In Rel. 15 / 16 NR, one or two CWs may be transmitted using one PDSCH.

[0129] When CBG-based transmission is configured, DCI format 1_1 includes a field for information indicating the CBG to be transmitted / retransmitted (CBGTI). The number of bits in this CBGTI field may be determined by the maximum number of CBGs per TB configured for the PDSCH and maxNrofCodeWordsScheduledByDCI.

[0130] Specifically, the size of the CBGTI field in DCI format 1_1 is N TB It may be N bits, where N TB is the value indicated by maxNrofCodeWordsScheduledByDCI, where N is the maximum number of CBGs per TB set by maxCodeBlockGroupsPerTransportBlock. TB If =2, the CBGTI field is mapped such that the first set of N bits starting from the MSB corresponds to the first TB, the second set corresponds to the second TB (if scheduled), etc. The first M bits of each set of N bits are mapped one-to-one to the M CBGs of the corresponding TB, in order, with the MSB mapped to CBG#0.

[0131] The number of CBGs M for TB reception may be determined by M = min(N, C), where C may be the number of CBs for the TB. min(N, C) is a function that returns the smallest value of N and C. M may be different for the first TB and the second TB.

[0132] If the New Data Indicator (NDI) field of the scheduling DCI indicates that a TB is being transmitted for the first time, the UE may assume that the entire CBG for that TB is present.

[0133] If the NDI field of the scheduling DCI indicates that a TB should be retransmitted, the UE may include only the CBG indicated by the CBGTI field of that DCI.

[0134] A bit value of '0' in the CBGTI field indicates that the corresponding CBG is not transmitted, and a bit value of '1' in the CBGTI field indicates that the corresponding CBG is transmitted.

[0135] In addition, DCI format 1_1 may further include CBG Flushing Out Information (CBGFI). The CBGFI may indicate whether a retransmitted CBG can be combined with the same CBG previously received. The UE may be configured to determine whether the CBGFI is valid by an RRC parameter (codeBlockGroupFlushIndicator) that is a parameter for enabling and configuring CBG-based transmission.

[0136] As described above, in dynamic grant-based DL transmission or UL transmission, retransmission may be controlled for each TB or for each CBG. When retransmission is controlled for each CBG, retransmission of successfully decoded CBGs can be omitted, thereby reducing overhead compared to TB-based retransmission.

[0137] (Problem) As described above, DCI extensions and the like for the examples of Schemes 1 to 3 have been studied. However, the details of the operation of transmitting multiple CWs on a PUSCH have not been fully studied. For example, how to support CBG-based transmission when transmitting multiple CWs on a PUSCH has not been fully studied. If PUSCH transmission for multiple CWs is not performed appropriately, there is a risk that throughput will decrease and communication quality will deteriorate. Therefore, the present inventors have conceived a method for a UE to appropriately perform PUSCH transmission for multiple CWs.

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

[0139] In the present disclosure, "A / B" may be read as "at least one of A and B."

[0140] In the present disclosure, terms such as activate, deactivate, indicate, select, configure, update, determine, and notify may be read interchangeably.

[0141] In the present disclosure, CW, TB, beam, panel, PUSCH, PDSCH, UE panel, RS port group, DMRS port group, SRS port group, RS resource group, DMRS resource group, SRS resource group, beam group, TCI state group, spatial relationship group, SRS resource indicator (SRI) group, antenna port group, antenna group, CORESET group, and CORESET pool may be read as interchangeable.

[0142] The panel may be associated with at least one of a panel ID, a UL TCI state, a UL beam, a DL beam, a DL RS resource, and spatial relationship information.

[0143] In the present disclosure, spatial relationship, spatial configuration, spatial relationship information, spatialRelationInfo, SRI, SRS resource, precoder, UL TCI, TCI state, Unified TCI, QCL, etc. may be read interchangeably.

[0144] In the present disclosure, the terms index, ID, indicator, and resource ID may be read interchangeably.

[0145] In the present disclosure, single DCI (sDCI), single PDCCH, multi-TRP (MTRP) system based on single DCI, sDCI-based MTRP, scheduling multiple PUSCHs (corresponding to different SRIs) using one DCI, sDCI-based MTRP transmission, and activating two TCI states on at least one TCI codepoint may be read interchangeably.

[0146] In the present disclosure, multi-DCI (mDCI), multi-PDCCH, multi-TRP system based on multi-DCI, mDCI-based MTRP, mDCI-based MTRP transmission, use of multi-DCI for MTRP, scheduling of multiple PUSCHs (corresponding to different SRIs) using two DCIs, and setting two CORESET pool indices or CORESET pool index=1 (or a value greater than or equal to 1) may be read interchangeably.

[0147] In this disclosure, the terms repetition (one repetition), occasion, and channel may be interchangeable. In this disclosure, the terms UL data, TB, CW, and UCI may be interchangeable.

[0148] The transmission scheme and new transmission scheme of the present disclosure may mean at least one of the above-mentioned schemes 1 to 3. At least one of the above-mentioned schemes 1 to 3 may be applied to PUSCH transmission in the following embodiments. Note that application of at least one of the above-mentioned schemes 1 to 3 regarding the PUSCH may be set by, for example, a higher layer parameter.

[0149] In the present disclosure, two CWs transmitted using a PUSCH may have different contents or may have the same contents. A PUSCH transmitting two CWs may be regarded as one PUSCH transmitted simultaneously or repeatedly.

[0150] The DCI in the following embodiments may be limited to a specific DCI format among DCI formats for scheduling a PUSCH (for example, DCI formats 0_0, 0_1, and 0_2), or may correspond to multiple DCI formats. Note that when multiple DCI formats are applicable, common control (the same control and the same processing) may be performed for all DCI formats, or different control may be performed for each DCI format.

[0151] In the following embodiments, "plurality" and "two" may be read interchangeably.

[0152] The number of layers for PUSCH transmission in the following embodiments is not limited to being greater than 4. For example, PUSCH transmission of two CWs in the present disclosure may be performed with a number of layers equal to or less than 4 (for example, 2). With regard to the above-described methods 1-3, the number of layers L may be greater than 4 or equal to or less than 4. Furthermore, the maximum number of layers is not limited to 4 or more, and may be less than 4.

[0153] Furthermore, PUSCH transmission in the following embodiments may or may not be premised on the use of multiple panels (may be applied regardless of the panels).

[0154] (Wireless communication method) First Embodiment The first embodiment relates to the number of CWs, the number of CBGs, the CBGTI field, etc. for the PUSCH.

[0155] [Number of CWs] For PUSCH, whether one or multiple (e.g., two) CWs are scheduled by one DCI (single DCI) may be configured in the UE by higher layer signaling (e.g., RRC parameters, MAC CE). This higher layer signaling configuration may be a configuration per BWP / serving cell. This configuration may correspond to information explicitly indicating the number of CWs, or may correspond to information indicating enabling / disabling scheduling of a certain number of CWs (e.g., 2).

[0156] The UE may determine the number of CWs scheduled by the DCI (which may also be referred to as the number of configured CWs) based on this configuration.

[0157] The number of CWs to be set may be a fixed number of scheduled CWs. For example, if the number of CWs to be scheduled by DCI is set by RRC to be two, the UE may expect that two CWs will always be scheduled by DCI for the PUSCH. In this case, even if the scheduled PUSCH corresponds to one MIMO layer (single layer), the fixed number of CWs to be set may be used to transmit the PUSCH.

[0158] The number of CWs to be configured may be the maximum number of scheduled CWs. For example, if the number of CWs scheduled by DCI is configured by RRC to be two, the UE may expect one or two CWs to be dynamically scheduled by DCI for the PUSCH (in other words, the number of scheduled CWs may vary within a range of values ​​up to the maximum number). In this case, if the scheduled PUSCH corresponds to X or more MIMO layers, the UE may use two CWs; otherwise, it may use one CW.

[0159] The value of X may be determined in advance by a specification, or may be notified to the UE from the base station using higher layer signaling (e.g., RRC parameters, MAC CE), physical layer signaling (e.g., DCI), or a combination thereof, or may be determined based on the UE capabilities.

[0160] [Maximum CBG per TB] Regardless of whether one or two CWs are (or can be) scheduled by one DCI, the parameter indicating the maximum number of CBGs per TB (maxCodeBlockGroupsPerTransportBlock) may take the values ​​2, 4, 6 and 8 (same as Rel. 16).

[0161] Furthermore, when one CW is scheduled by one DCI, the possible values ​​of the parameter indicating the maximum number of CBGs per TB (maxCodeBlockGroupsPerTransportBlock) are 2, 4, 6, and 8, the same as in Rel. 16, and when one CW is scheduled by two DCIs, the possible values ​​of the parameter indicating the maximum number of CBGs per TB (maxCodeBlockGroupsPerTransportBlock) may be smaller than in the case where one CW is scheduled (for example, it may be limited to 2 and 4).

[0162] Furthermore, a parameter indicating the maximum number of CBGs per TB (maxCodeBlockGroupsPerTransportBlock) may be set separately from the parameter indicating the maximum number of CBGs per TB (maxCodeBlockGroupsPerTransportBlockForTwoCodeWords, for example). The parameter indicating the maximum number of CBGs per TB for two TBs may indicate the maximum number of CBGs per TB common to the two TBs, or may indicate the maximum number of CBGs per TB individual to the two TBs. For example, the maximum number of CBGs for a first TB may be a first maximum number of CBGs, and the maximum number of CBGs for a second TB may be a second maximum number of CBGs different from the first maximum number of CBGs. Note that, when the maximum number of CBGs is individual to each TB, the first maximum number of CBGs for one TB may be set by a higher layer parameter, and the second maximum number of CBGs for the other TB may be determined based on the first maximum number of CBGs. Note that the first maximum number of CBGs may always be specified / set to be larger / smaller / the same as the second maximum number of CBGs.

[0163] [CBGTI field] In Rel. 16, the CBGTI field was included only in DCI format 0_1 ​​as a DCI format for PUSCH. In the present disclosure, the CBGTI field may be included in DCI format 0_1 / 0_2 as a DCI format for PUSCH. Unless otherwise specified, the value indicated by the CBGTI field and the control (processing) related to the CGBTI field may be as described above (similar to the existing NR specifications).

[0164] When CBG-based transmission is configured, DCI format 0_1 / 0_2 may include a field for information indicating the CBG to be transmitted / retransmitted (CBGTI). The number of bits of this CBGTI field may be determined by the maximum number of CBGs per TB configured for the PUSCH and the number of CWs scheduled by one DCI.

[0165] Specifically, the size of the CBGTI field in DCI format 0_1 / 0_2 is N TB It may be N bits, where N TB is the number of CWs scheduled by one DCI, and N is the maximum number of CBGs per TB set by maxCodeBlockGroupsPerTransportBlock. TB If =2, the CBGTI field is mapped such that the first set of N bits starting from the MSB corresponds to the first TB, the second set corresponds to the second TB (if scheduled), etc. The first M bits of each set of N bits are mapped one-to-one to the M CBGs of the corresponding TB, in order, with the MSB mapped to CBG#0.

[0166] The number of CBGs M for TB transmission may be determined by M=min(N, C), where C may be the number of CBs (of the above TBs) in the PUSCH. min(N, C) is a function that returns the minimum value of N and C. M may be different for the first TB and the second TB.

[0167] The size of the CBGTI field may be calculated as the number of CWs multiplied by the number of CBGs (per TB).

[0168] For example, as described above, regardless of whether one or two CWs are scheduled (or can be scheduled) by one DCI, if the possible values ​​of the parameter indicating the maximum number of CBGs per TB (maxCodeBlockGroupsPerTransportBlock) are 2, 4, 6, and 8, the size of the CBGTI field can be any of 2, 4, 6, 8, 12, and 16.

[0169] As described above, when one CW is scheduled by two DCIs, if the possible values ​​of the parameter indicating the maximum number of CBGs per TB (maxCodeBlockGroupsPerTransportBlock) are 2 and 4, the size of the CBGTI field can be any of 2, 4, 6, and 8.

[0170] As described above, when the maximum number of CBGs per individual TB is set for the two TBs, the size of the CBGTI field may correspond to N1 + N2. Here, N1 is the maximum number of CBGs for the first TB, and N2 may be the maximum number of CBGs for the second TB.

[0171] Figures 4A and 4B are diagrams showing an example of the bit configuration of the CBGTI field in the first embodiment. In this example, the case where 2 < M < N and M is the same for each TB is shown, but the bit configuration of the CBGTI field is not limited to this. Note that this example only shows the bit configuration of the field of interest among the DCI fields, and it is naturally understood that the DCI may include other fields as well (the same applies to Figures 5A and 5B described later).

[0172] Figure 4A shows the bit configuration when the size of the CBGTI field is N TB · N bits, and Figure 4B shows the bit configuration when the size of the CBGTI field is N1 + N2 bits.

[0173] Note that the "number of CWs scheduled by one DCI" in the first embodiment may be read as the number of CWs that can be scheduled by one DCI, or may be read as the maximum number of CWs scheduled by a DCI set by a higher layer parameter. The maximum number of CWs may be determined, for example, by a parameter (maxNrofCodeWordsScheduledByDCI) indicating the maximum number of CWs scheduled by one DCI in the PUSCH configuration information (RRC's PUSCH-Config information element).

[0174] [Modification Example] The first embodiment may be read for PDSCH. In this case, in the above description, PUSCH can be read as PDSCH, transmission and reception can be read as each other, and DCI format 0_x (x is an integer) can be read as DCI format 1_x.

[0175] For example, even if two CWs are enabled for a PDSCH, the parameter indicating the maximum number of CBGs per TB (maxCodeBlockGroupsPerTransportBlock) may take the values ​​2, 4, 6, and 8. In this case, the size of the CBGTI field of DCI format 1_1 / 1_2 may be any of 2, 4, 6, 8, 12, and 16.

[0176] According to the first embodiment described above, the UE can appropriately support CBG-based transmission even in the case of PUSCH transmission for two CWs.

[0177] <Second embodiment> The second embodiment relates to fields of one DCI when the UE is notified by higher layer signaling that two CWs are scheduled by the DCI.

[0178] In a second embodiment, the DCI may include multiple NDI fields, each corresponding to an NDI for a different CW. For example, a first NDI field may indicate an NDI for a first CW, and a second NDI field may indicate an NDI for a second CW.

[0179] In the second embodiment, the DCI may include one field (which may be called an NDI field or may be called by another name) corresponding to multiple NDIs. For example, this field may indicate an NDI for a first CW and an NDI for a second CW. The correspondence between the value of the field and the NDI for each CW may be determined in advance by a specification, or may be notified from the base station to the UE using higher layer signaling (e.g., RRC parameters, MAC CE), physical layer signaling (e.g., DCI), or a combination thereof, or may be determined based on UE capabilities.

[0180] In the second embodiment, the DCI may include a plurality of RV fields corresponding to the RVs of respective different CWs. For example, the first RV field may indicate the RV for the first CW, and the second RV field may indicate the RV for the second CW.

[0181] In the second embodiment, the DCI may include one field (which may be called an RV field or may be called by another name) corresponding to a plurality of RVs. For example, this field may indicate the RV for the first CW and the RV for the second CW. The correspondence between the value of the field and the RV for each CW may be determined in advance by a specification, or may be notified from the base station to the UE using higher layer signaling (e.g., RRC parameters, MAC CE), physical layer signaling (e.g., DCI), or a combination thereof, or may be determined based on the UE capabilities.

[0182] The field related to NDI / RV in the second embodiment may have the same number of bits as the existing NDI / RV field, or may have a different number of bits.

[0183] Note that in the second embodiment, like the <DCI extension> described above, fields such as SRI / TPMI / TPC / MCS / RV / NDI / TDRA / FDRA / precoding information and the number of layers may be extended (e.g., a plurality may be included for the first CW and the second CW).

[0184] [Dynamic indication of the number of CWs] As described in the first embodiment, when the number of the CWs to be set is the maximum number of CWs to be scheduled, for the PUSCH, one or two CWs may be dynamically scheduled by the DCI.

[0185] Regarding this dynamic indication of the number of CWs, information regarding the number of CWs to be scheduled (e.g., "only one CW is scheduled (or one CW is disabled)" or "two CWs are scheduled") may be explicitly or implicitly indicated to the UE by a field of the DCI. For example, the number of CWs to be scheduled may be explicitly notified by a new field of the DCI (which may be called, for example, a CW number field).

[0186] The number of CWs to be scheduled may also be signaled by other fields of the DCI (e.g., fields for SRI / TPMI / TPC / MCS / RV / NDI / TDRA / FDRA / precoding information and number of layers). For example, the number of CWs to be scheduled may be signaled by a specific codepoint in one field, or the number of CWs to be scheduled may be signaled by setting one or more fields to specific values, respectively.

[0187] For example, if the number of MIMO layers to be scheduled is 1, the UE may determine that only one CW is scheduled.

[0188] Which field in the DCI is used to indicate the number of CWs (e.g., whether the DCI includes a CW number field) may be determined in advance by a specification, may be notified to the UE by higher layer signaling (e.g., RRC parameters, MAC CE), or may be determined based on the UE capabilities.

[0189] Note that when it is instructed that the number of scheduled CWs is 1, the field corresponding to the second CW (e.g., for the extended DCI of <DCI Extension> described above, the SRI / TPMI / TPC / MCS / RV / NDI / TDRA / FDRA field corresponding to the second CW) may be set to a specific value (e.g., 0) or a specific bit sequence (e.g., all '0'), may be ignored by the UE, may be used for other purposes (e.g., to improve the decoding (error correction) performance of DCI as virtual cyclic redundancy check (Virtual CRC) bits), or may not be included in the DCI.

[0190] In other words, the UE may perform control regarding the fields of the scheduling DCI based on the number of scheduled CWs. For example, the UE may assume a specific value (e.g., 0), perform a specific process (e.g., discard), or determine that it does not exist for the field corresponding to the second CW of the scheduling DCI based on the number of scheduled CWs.

[0191] FIGS. 5A and 5B are diagrams showing an example of bit values of the DCI field in the second embodiment. In this example, the bit values of the CW number field, the field corresponding to the first CW (e.g., the SRI field for the first CW, etc.), and the field corresponding to the second CW (e.g., the SRI field for the second CW, etc.) are shown. X indicates that it may be any bit value (0 / 1).

[0192] FIG. 5A shows an example of bit values when the CW number field indicates 1 (e.g., meaning CW number = 2). In this case, the fields corresponding to each CW indicate valid values (values used for the transmission of the corresponding CW).

[0193] Figure 5B shows an example of bit values ​​when the Number of CWs field indicates 0 (e.g., meaning Number of CWs = 1). In this case, the field corresponding to the first CW indicates a valid value, but the field corresponding to the second CW is set to all 0s.

[0194] According to the second embodiment described above, the UE can appropriately determine the configuration of the DCI field for scheduling PUSCH transmission for two CWs.

[0195] <Third embodiment> The third embodiment relates to TPC commands when the UE is informed by higher layer signaling that two CWs are scheduled by one DCI.

[0196] The TPC command field for the scheduled PUSCH may be extended to indicate TPC commands for multiple PUSCHs.

[0197] [[Option 1]] Multiple TPC command fields in the DCI may be used for panel or beam specific power control, in other words, each TPC command field may apply to power control of PUSCH transmissions for different CWs.

[0198] [[Option 2]] One TPC command field may be maintained. RRC signaling and / or MAC CE may be used to map one TPC index to multiple sets of TPC parameters for multiple PUSCHs. A new table for TPC command mapping may be defined in the specification. In this table, an index may correspond to multiple sets of TPC parameters (or TPC commands) for multiple PUSCHs.

[0199] If TPC commands for each CW are available, the accumulated values ​​of the TPC commands may be accumulated separately for each CW or may be accumulated collectively across all CWs (without distinguishing between CWs). For example, the UE may determine the PUSCH transmit power for a first CW based on the accumulated values ​​of the TPC commands for the first CW and may determine the PUSCH transmit power for a second CW based on the accumulated values ​​of the TPC commands for the second CW.

[0200] If TPC commands per CW are not available, the cumulative value of the TPC commands may be accumulated collectively over the CW.

[0201] According to the third embodiment described above, the UE can appropriately control the PUSCH transmission power for each CW even when transmitting PUSCHs for two CWs.

[0202] <Supplementary information> It should be noted that at least one of the above-described embodiments may be applied only to UEs that have reported or support a particular UE capability.

[0203] The specific UE capabilities may indicate at least one of the following: Whether to support multiple (e.g., two) CWs for PUSCH scheduled by one DCI (single DCI); ·Whether to support method 1 / 2 / 3 for UL (PUSCH) transmission.

[0204] Furthermore, the above-mentioned specific UE capabilities may be capabilities that are applied across all frequencies (commonly regardless of frequency), capabilities for each frequency (e.g., cell, band, BWP), capabilities for each frequency range (e.g., FR1, FR2, FR3, FR4, FR5), or capabilities for each subcarrier spacing.

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

[0206] Furthermore, at least one of the above-described embodiments may be applied when specific information related to the above-described embodiments is configured in the UE by higher layer signaling (if not configured, for example, the operation of Rel. 15 / 16 is applied). For example, the specific information may be information indicating that the CW number field is enabled, any RRC parameter for a specific release (e.g., Rel. 18), etc.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0233] (base station) 7 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0250] In addition, the transceiver 120 may transmit, to the user terminal 20, information indicating that multiple codewords (CWs) are scheduled by one piece of downlink control information (DCI) for the physical uplink shared channel (PUSCH) (for example, an upper layer parameter indicating a fixed number or a maximum number of CWs to be scheduled).

[0251] The transceiver 120 may receive the physical uplink shared channel for the plurality of codewords transmitted by the user terminal 20 based on the information.

[0252] Furthermore, when transmitting information indicating that multiple codewords (CWs) are scheduled by one piece of downlink control information (DCI) for the physical uplink shared channel (PUSCH) (for example, an upper layer parameter indicating a fixed number or a maximum number of CWs to be scheduled) to the user terminal 20, the transceiver unit 120 may transmit the downlink control information including information regarding the number of codewords to be scheduled.

[0253] Based on the information on the number of codewords (for example, when the number of CWs=1 is indicated), the control unit 110 may assume that control regarding a field corresponding to a specific codeword (for example, a second CW) included in the downlink control information is performed by the user terminal 20. Furthermore, the transceiver unit 120 may receive the physical uplink shared channel transmitted from the user terminal 20 after such control has been performed.

[0254] (user terminal) 8 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0271] The transceiver 220 may receive information indicating that multiple codewords (CWs) are scheduled by one downlink control information (DCI) for the physical uplink shared channel (PUSCH) (e.g., a higher layer parameter indicating a fixed or maximum number of CWs to be scheduled).

[0272] The controller 210 may control transmission of the physical uplink shared channel for the plurality of codewords based on the information.

[0273] The information may indicate a fixed number of codewords to be scheduled. In this case, the control unit 210 may determine that the number of codewords to be scheduled by the downlink control information is the fixed number.

[0274] The information may indicate a maximum number of scheduled codewords. In this case, the controller 210 may determine that the number of codewords scheduled by the downlink control information may vary within a range of values ​​up to the maximum number.

[0275] The control unit 210 may calculate the size of the Code Block Group Transmission Information (CBGTI) field of the downlink control information based on the number of codewords scheduled by the downlink control information and the number of CBGs per codeword.

[0276] Furthermore, when the transceiver 220 receives information indicating that multiple codewords (CWs) are scheduled by one downlink control information (DCI) for the physical uplink shared channel (PUSCH) (e.g., a higher layer parameter indicating a fixed number or a maximum number of CWs to be scheduled), the transceiver 220 may receive the downlink control information including information regarding the number of codewords to be scheduled (e.g., a CW count field).

[0277] Based on information regarding the number of codewords (e.g., when the number of CWs=1 is indicated), the control unit 210 may perform control regarding a field corresponding to a specific codeword (e.g., the second CW) included in the downlink control information.

[0278] The control unit 210 may determine that the field corresponding to the specific codeword is a specific value (for example, 0) based on the information about the number of codewords.

[0279] The control unit 210 may discard the field corresponding to the specific codeword based on the information about the number of codewords.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0326] 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," "antenna port group," "layer," "number of layers," "rank," "resource," "resource set," "resource group," "beam," "beam width," "beam angle," "antenna," "antenna element," "panel," etc. may be used interchangeably.

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

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

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

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

[0331] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, or the mobile object itself. 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). 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.

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

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

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

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

[0336] Each aspect / embodiment described in the present disclosure may be related to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), 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-Wide Band (UWB), Bluetooth (registered trademark), or other appropriate wireless communication methods, or to next-generation systems that are based on and extend these systems. Furthermore, the present invention may be applied to a combination of multiple systems (for example, a combination of LTE or LTE-A and 5G).

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

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

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

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

[0341] Also, "decision" may be considered to be "deciding" resolving, selecting, choosing, establishing, comparing, etc. In other words, "decision" may be considered to be "deciding" on some action.

[0342] Furthermore, "judgment (decision)" may be interpreted as "assuming," "expecting," "considering," or the like.

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

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

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

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

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

[0348] 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 invention according to the present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the invention as defined by the description of the claims. Therefore, the description of the present disclosure is intended to be illustrative and explanatory and does not impose any limiting meaning on the invention according to the present disclosure.

Claims

1. a receiving unit for receiving higher layer signaling indicating that up to two transport blocks (TBs) are scheduled by one downlink control information (DCI) for a physical uplink shared channel (PUSCH) transmission; and the DCI; A terminal having a control unit that determines that up to two TBs are scheduled by the DCI when the higher layer signaling sets that up to two TBs are scheduled by the DCI, and that up to two TBs are scheduled by the DCI when the number of layers of the PUSH transmission is greater than four, and that one TB is scheduled by the DCI when the number of layers of the PUSH transmission is four or less.

2. receiving higher layer signaling indicating that up to two transport blocks (TBs) are scheduled by one downlink control information (DCI) for a physical uplink shared channel (PUSCH) transmission; and the DCI; A wireless communication method for a terminal, comprising: a step of determining that up to two TBs are scheduled by the DCI by the higher layer signaling, and that up to two TBs are scheduled by the DCI if the number of layers of the PUSCH transmission is greater than four, and that one TB is scheduled by the DCI if the number of layers of the PUSCH transmission is four or less.

3. a transmitter configured to transmit, to a terminal, higher layer signaling indicating that up to two transport blocks (TBs) are scheduled by one downlink control information (DCI) for a physical uplink shared channel (PUSCH) transmission; and the DCI; A base station having a control unit that sets, by the higher layer signaling, that up to two TBs are scheduled by the DCI, and controls to schedule up to two TBs by the DCI if the number of layers of the PUSCH transmission is greater than four, and to schedule one TB by the DCI if the number of layers of the PUSCH transmission is four or less.

4. A system having a terminal and a base station, The terminal a receiving unit for receiving higher layer signaling indicating that up to two transport blocks (TBs) are scheduled by one downlink control information (DCI) for a physical uplink shared channel (PUSCH) transmission; and the DCI; A control unit that determines that up to two TBs are scheduled by the DCI when the higher layer signaling sets that up to two TBs are scheduled by the DCI, and that up to two TBs are scheduled by the DCI when the number of layers of the PUSCH transmission is greater than four, and that one TB is scheduled by the DCI when the number of layers of the PUSCH transmission is four or less, The base station A system comprising a transmitter that transmits the higher layer signaling and the DCI.

Images