Terminal, wireless communication method, and base station

The terminal and base station configuration dynamically controls grant-based transmission in next-generation wireless systems by utilizing specific fields in downlink control information, addressing the inefficiencies in higher rank transmissions and enhancing communication throughput and resource utilization.

WO2024236713A1PCT designated stage expired Publication Date: 2024-11-21NTT DOCOMO INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2023/018175
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-15
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

In next-generation wireless communication systems, particularly in 5G and beyond, the control of grant-based transmission with ranks greater than 4 is not adequately addressed, leading to potential suppression of communication throughput and efficiency in using radio resources.

Method used

A terminal and base station configuration that dynamically controls grant-based transmission by using specific fields in downlink control information to determine valid activation or release of uplink shared channels, ensuring appropriate configuration even with higher ranks, thereby optimizing resource allocation.

Benefits of technology

This approach effectively manages grant-based transmission for ranks greater than 4, enhancing communication throughput and radio resource efficiency by ensuring proper configuration and activation/release of uplink shared channels.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2023018175_21112024_PF_FP_ABST
    Figure JP2023018175_21112024_PF_FP_ABST
Patent Text Reader

Abstract

A terminal according to one aspect of the present disclosure comprises: a reception unit that, when a dynamic grant-based uplink shared channel for two transport blocks (TB) is configured, receives downlink control information (DCI) for the dynamic grant-based uplink shared channel; and a control unit that, on the basis of a set of specific fields included in the DCI, determines whether the DCI is a valid activation DCI or a release DCI for the configured grant-based uplink shared channel for one or two TBs. In one aspect of the present disclosure, it is possible to appropriately control configured grant-based transmission when using transmission having a rank greater than four.
Need to check novelty before this filing date? Find Prior Art

Description

Terminal, wireless communication method and base station

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

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

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

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

[0005] Rel. 15 NR supports uplink (UL) multi-input multi-output (MIMO) transmission with up to four layers. For future NRs, support for UL transmission with a number of layers greater than four is being considered to achieve higher spectral efficiency. For example, for Rel. 18 NR, maximum 6-rank transmission using 6 antenna ports and maximum 6- or 8-rank transmission using 8 antenna ports are being considered.

[0006] However, sufficient consideration has not been given to grant-based transmission with a rank greater than 4. Unless appropriate control is performed, there is a risk that the increase in communication throughput will be suppressed and the utilization efficiency of radio resources will decrease.

[0007] Therefore, one of the objects of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately control configured grant-based transmission when transmission with a rank greater than 4 is used.

[0008] A terminal according to one aspect of the present disclosure includes: a receiving unit that receives downlink control information (DCI) for a dynamic grant-based uplink shared channel of two transport blocks (TBs) when the dynamic grant-based uplink shared channel is configured; and a control unit that determines, based on a set of specific fields included in the DCI, whether the DCI is a valid activation or release DCI for the configured grant-based uplink shared channel of one or two TBs.

[0009] According to one aspect of the present disclosure, configured grant-based transmission can be appropriately controlled when transmission of rank greater than 4 is used.

[0010] Figures 1A-1D are diagrams showing an example of special fields for verifying DCI for activation / deactivation of Type 2CG in Rel. 17 NR. Figures 2A and 2B are diagrams showing an example of special fields for verifying DCI for activation of Type 2CG in a second embodiment. Figure 3 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. Figure 4 is a diagram showing an example of a configuration of a base station according to an embodiment. Figure 5 is a diagram showing an example of a configuration of a user terminal according to an embodiment. Figure 6 is a diagram showing an example of hardware configurations of a base station and a user terminal according to an embodiment. Figure 7 is a diagram showing an example of a vehicle according to an embodiment.

[0011] (Dynamic grant-based transmission and configured grant-based transmission) For UL transmission in NR, there are dynamic grant-based transmission and configured grant-based transmission.

[0012] Dynamic grant-based transmission is UL transmission using an uplink shared channel (e.g., a Physical Uplink Shared Channel (PUSCH)), in which resource allocation is dynamically indicated to a terminal (user terminal, User Equipment (UE)) by Downlink Control Information (DCI) (UL grant).

[0013] The configured grant-based transmission is a UL transmission using an uplink shared channel (e.g., PUSCH) in which resource allocation is semi-statically instructed to the UE by higher layer signaling.

[0014] Dynamic grant-based transmission may also be referred to as dynamic grant-based PUSCH (DG PUSCH), UL Transmission with dynamic grant, PUSCH with dynamic grant, UL Transmission with UL grant, UL grant-based transmission, UL transmission scheduled by dynamic grant (transmission resource configured), etc.

[0015] The configured grant-based transmission may also be referred to as configured grant-based PUSCH (CG PUSCH), UL Transmission with configured grant, PUSCH with configured grant, UL Transmission without UL grant, UL grant-free transmission, UL transmission scheduled by configured grant (transmission resource is configured), UL Semi-Persistent Scheduling (SPS) transmission, etc.

[0016] In the present disclosure, the terms configured grant (CG) and SPS may be read interchangeably.

[0017] Each of the DG and CG may be referred to as an actual UL grant, i.e., the actual UL grant may be higher layer signaling (e.g., Radio Resource Control (RRC) signaling), physical layer signaling (e.g., DCI for activation, which will be described later), or a combination thereof.

[0018] There are several types of configured grant-based transmission (Type 1, Type 2, etc.).

[0019] In configured grant type 1 transmission (type 1CG), configuration information for CG (parameters used for CG transmission, which may also be called CG parameters) is configured in the UE using only higher layer signaling.

[0020] In configured grant type 2 transmission (type 2CG), some of the CG parameters are configured in the UE by higher layer signaling, and other parts of the CG parameters may be notified to the UE by physical layer signaling (e.g., DCI for activation, which will be described later).

[0021] If a type 1 CG is configured, the UE may determine that one or more CGs are triggered. The UE may perform PUSCH transmission without a dynamic grant using the configured resources for CG PUSCH transmission (which may also be referred to as CG resources, transmission occasions, etc.). Note that even if CG PUSCH transmission is configured, the UE may skip CG PUSCH transmission if there is no data in the transmission buffer.

[0022] When a type 2 CG is configured and an activation signal is notified, the UE may determine that one or more CGs are triggered (or activated). The activation signal (e.g., activation DCI) may be a DCI (PDCCH) having a cyclic redundancy check (CRC) scrambled by a predetermined identifier (e.g., Configured Scheduling Radio Network Temporary Identifier (CS-RNTI)). Note that a signal for deactivating a CG (e.g., deactivation DCI) may be the same as or similar to the activation DCI. Note that deactivation may be interchangeable with release.

[0023] The UE may determine whether to transmit a PUSCH using a CG resource configured by a higher layer based on the activation signal. The UE may release (may be called "release," "deactivate," etc.) the resource (PUSCH) corresponding to the CG based on the deactivation signal or expiration of a predetermined timer (elapse of a predetermined time).

[0024] The UE may perform PUSCH transmission without a dynamic grant using an activated resource for CG PUSCH transmission (which may also be referred to as a CG resource, a transmission occasion, etc.). Note that even when CG PUSCH transmission is activated (is in an active state), the UE may skip CG PUSCH transmission if there is no data in the transmission buffer.

[0025] The UE verifies whether one or more fields included in the detected DCI have special values ​​(special value(s)) to determine whether the DCI is for activation / deactivation of a type 2 CG. An example of the relationship between the one or more fields and the special values ​​is shown in Figures 1A-1D.

[0026] 1A-1D are diagrams illustrating examples of special fields for verifying a DCI for activation / deactivation of a Type 2 CG in Rel. 17 NR. Figures 1A and 1B correspond to a DCI for activation, and Figures 1C and 1D correspond to a DCI for deactivation. Also, Figures 1A and 1C correspond to a case where a UE is provided with one CG Type 2 configuration in an active Bandwidth Part (BWP), and Figures 1B and 1D correspond to a case where a UE is provided with multiple CG Type 2 configurations in an active BWP.

[0027] FIG. 1A indicates that DCI format 0_0 / 0_1 / 0_2 may correspond to an activation DCI if the Hybrid Automatic Repeat reQuest (HARQ) Process Number (HPN) field (if present) is set to all '0's and the Redundancy Version (RV) field (if present) is set to all '0's.

[0028] Figure 1C indicates that DCI format 0_0 / 0_1 / 0_2 may correspond to a deactivation DCI if the HPN field (if present) is set to all '0's, the RV field (if present) is set to all '0's, the Modulation and Coding Scheme (MCS) field is set to all '1's, and the frequency domain resource allocation field is set to all '0's or '1's.

[0029] 1B and 1D imply that if a UE is provided with multiple CG type 2 configurations, the HPN field is not used to verify the DCI for activation / deactivation, since the HPN field is used to indicate which of the multiple CG type 2 configurations to activate / deactivate.

[0030] Note that other conditions than those shown in Figures 1A-1D may also be used to verify the activation / deactivation DCI, for example, the activation / deactivation DCI has the New Data Indicator (NDI) field set to 0 for the Transport Block (TB) being activated.

[0031] That is, in Rel. 17, the DCI for activation for type 2 CG indicates the MCS, but does not indicate the NDI and RV because the corresponding fields have special values ​​as described above.

[0032] The above-mentioned CG parameters may be configured in the UE using CG configuration information of a higher layer (e.g., a ConfiguredGrantConfig information element of the RRC layer). The CG parameters may include, for example, information specifying CG resources. The CG parameters may include, for example, information regarding a CG index, a time offset, a periodicity, etc.

[0033] Here, the period and the time offset may be expressed in units of symbols, slots, subframes, frames, etc. The period may be represented, for example, by a predetermined number of symbols. The time offset may be represented, for example, by an offset relative to the timing of a predetermined index (such as slot number 0 and / or system frame number 0).

[0034] Some of the CG parameters may be configured by the CG configuration information, and the rest may be configured by the PUSCH configuration information (e.g., the RRC information element PUSCH-Config). For example, the maximum rank for the CG PUSCH may be indicated by a parameter provided by the PUSCH configuration information (e.g., the RRC parameters maxRank, maxRankDCI-0-2-r16, etc.).

[0035] For type 1 CG, information normally specified by DCI for DG PUSCH is configured by CG configuration information. For example, information corresponding to the precoding information and layer number field, measurement reference signal (SRS) Resource Indicator (SRI) field, MCS field, and antenna port field of DCI is notified to the UE by the precodingAndNumberOfLayers field, srs-ResourceIndicator field, mcsAndTBS field, and antennaPort field included in the CG configuration information, respectively.

[0036] For example, the UE may determine a Transmitted Precoding Matrix Indicator (TPMI) and the number of layers (transmission rank) for the CG PUSCH based on precodingAndNumberOfLayers.

[0037] Furthermore, repetition transmission may be configured for the CG. If repetition for the CG is supported, repetition-related parameters may be configured by the CG configuration information. The repetition-related parameters may include, for example, an RRC parameter repK indicating the number of repeated transmissions of a transport block (TB), an RRC parameter repK-RV indicating an RV sequence to be used for repeated transmission, and an RRC parameter sequenceOffsetForRV indicating an RV offset of the start RV of the first repetition for the second resource set.

[0038] The number of repeated transmissions may be any integer, for example, 1, 2, 4, 8, etc. If the number of repeated transmissions is n (>0), the UE may transmit one TB using n transmission opportunities. A CG PUSCH with a number of repeated transmissions greater than 1 may be referred to as a repeated CG PUSCH.

[0039] Furthermore, a single DCI (SDCI)-based Time Division Multiplexing (TDM) Multi Transmission / Reception Point (MTRP) PUSCH may be configured for the CG. If the SDCI-based TDM MTRP PUSCH for the CG is supported, parameters related to the second TRP (or the second SRS resource set) may be configured by the CG configuration information. For example, information corresponding to the precoding information, number of layers, and SRI fields for the second SRS resource set of the DCI may be notified to the UE by the precodingAndNumberOfLayers2 field and srs-ResourceIndicator2 field included in the CG configuration information, respectively.

[0040] <CG PUSCH Retransmission> In Rel. 15 NR, retransmission of Type 1 CG / Type 2 CG PUSCH was scheduled by the DG and could not be performed on the CG PUSCH, but in Rel. 16 and later, retransmission on the CG PUSCH (retransmission on CG resources) is supported.

[0041] The UE may receive information regarding retransmission of the CG PUSCH through a specific DCI format (eg, DCI format 0_1), and may control retransmission of data / control information in the CG PUSCH based on the information.

[0042] The information regarding the retransmission may be a Downlink Feedback Information (DFI) flag field.

[0043] The DFI flag field may have a bit length of 0 or 1. When the UE is configured to monitor DCI format 0_1 ​​with CRC scrambled by CS-RNTI and performs shared spectrum channel access in a cell, the bit length of the DFI flag field may be 1. In other cases, the bit length of the DFI flag field may be 0.

[0044] When the DFI flag field has a bit length of 1 bit, a value of 0 in the DFI flag field may indicate activation / release of a type 2 CG, and a value of 1 in the DFI flag field may indicate CG-DFI.

[0045] When CG-DFI is indicated to a UE, the remaining bits constituting DCI format 0_1 ​​may be determined. Specifically, when CG-DFI is indicated to a UE, the remaining bits constituting DCI format 0_1 ​​may include a HARQ-ACKnowledgement (HARQ-ACK) bitmap field, a Transmission Power Control (TPC) command for scheduled PUSCH field, etc. The TPC command field may have a bit length of 2 bits.

[0046] The HARQ-ACK bitmap field may have a bit length of 16 bits. The HARQ-ACK bitmap may correspond to the HPNs in ascending order from the most significant bit (MSB) to the least significant bit (LSB). Note that in the present disclosure, the MSB and LSB may be interchanged. When the value of the HARQ-ACK bitmap field is 1, an ACK may be indicated for the PUSCH / UCI of the corresponding HPN. When the value of the HARQ-ACK bitmap field is 0, a negative ACK (NACK) may be indicated for the PUSCH / UCI of the corresponding HPN.

[0047] The UE may transmit UCI in the CG PUSCH. This UCI may be called CG-based UCI or CG-specific UCI (CG-UCI). CG-UCI may be transmitted when the CG retransmission timer field (cg-RetransmissionTimer-r16) is configured by the CG configuration information.

[0048] If the UE receives a CG-DFI before the CG retransmission timer expires, the UE may terminate the TB repetition (retransmission) for HPNs for which the HARQ-ACK bitmap field indicates ACK, and may perform retransmission using the CG PUSCH for HPNs for which the HARQ-ACK bitmap field indicates NACK.

[0049] If the UE does not receive the CG-DFI before the CG retransmission timer expires, the UE may retransmit the CG PUSCH transmission (initial transmission) at the previous CG opportunity using the CG PUSCH at the CG opportunity after the CG retransmission timer expires.

[0050] The CG-UCI may include a specific field, which may be at least one of an HPN field, an RV field, an NDI field, and a Channel Occupancy Time (COT) shared information field. The specific field indicates information such as an HPN for each CG opportunity (for data to be transmitted on a CG PUSCH in the CG opportunity).

[0051] The HPN field may have a bit length of 4 bits, the RV field may have a bit length of 2 bits, and the NDI field may have a bit length of 1 bit.

[0052] The COT sharing information field may have a bit length of Ceil(log2(C)) bits when a specific upper layer parameter (e.g., ULtoDL-CO-SharingED-Threshold-r16) and other upper layer parameters (e.g., cg-COT-SharingList-r16) are set and the number of set combinations in the other upper layer parameters (e.g., cg-COT-SharingList-r16) is C.

[0053] Furthermore, the COT sharing information field may have a bit length of 1 bit when a specific upper layer parameter (e.g., ULtoDL-CO-SharingED-Threshold-r16) is not set and another upper layer parameter (e.g., cg-COT-SharingList-r16) is set. In cases other than the above two cases, the COT sharing information field may have a bit length of 0 bit.

[0054] In addition, when a field related to CG-UCI multiplexing (cg-UCI-Multiplexing-r16) is set by the CG configuration information, the UE may jointly encode the CG-UCI and HARQ-ACK when the CG PUSCH and the uplink control channel (Physical Uplink Control Channel (PUCCH)) overlap.

[0055] CG PUSH retransmission control based on CG-DFI / CG-UCI may be used in an NR system that uses unlicensed spectrum (shared spectrum).

[0056] (Transmission of More Than Four Antenna Ports) Rel. 15 / 16 NR supports uplink (UL) multi-input multi-output (MIMO) transmission with up to four layers. For future wireless communication systems, support for UL transmission with more than four layers is being considered to achieve higher spectral efficiency. For example, for Rel. 18 NR, maximum six-rank transmission using six antenna ports and maximum six- or eight-rank transmission using eight antenna ports are being considered.

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

[0058] Furthermore, while Rel. 15 / 16 NR supported the transmission of one codeword (CW) in one PUSCH, Rel. 18 NR is considering allowing a UE to transmit more than one CW in one PUSCH. For example, support for two CW transmissions for ranks 5-8 and support for two CW (dual CW) transmissions for ranks 2-8 are being considered. One CW corresponds to one transport block (TB).

[0059] The support (or enablement) of dual CWs in PUSCH transmission may be notified to the UE by a predetermined higher layer parameter. The predetermined higher layer parameter may be a higher layer parameter (e.g., maxNrofCodeWordsScheduledByDCI) related to the maximum number of CWs scheduled by DCI. The predetermined higher layer parameter (e.g., maxNrofCodeWordsScheduledByDCI) may be included in PUSCH configuration information (e.g., PUSCH-config).

[0060] For example, if 2 is set by a predetermined upper layer parameter (for example, maxNrofCodeWordsScheduledByDCI equals 2), this may mean that a field for TB#2 is included in the DCI.

[0061] Incidentally, DCI formats for PUSCH scheduling up to Rel. 17 NR (e.g., DCI formats 0_1 / 0_2) included fields for one CW (e.g., MCS field, NDI field, RV field, etc.).

[0062] In NR Rel. 18 and later, for dual CWs, it is being considered to include fields for two CWs (e.g., an MCS field, an NDI field, and an RV field for the second CW) in the DCI format for PUSCH scheduling.

[0063] When the maximum rank (e.g., RRC parameters maxRank, maxRankDCI-0-2-r16, etc.) > 4 is configured by the PUSCH configuration information (e.g., RRC information element PUSCH-Config), the rank may be dynamically indicated by the DCI. For example, the DCI may indicate the rank value or whether the rank is 4 or less.

[0064] If the rank is 4 or less, the fields (e.g., MCS field, NDI field, RV field) for the CW to be disabled (e.g., the second CW) may not be used for actual indication. Also, one of the two CWs may be disabled when a specific condition is met. The specific condition may be determined by the MCS index (e.g., I) for the corresponding CW. MCS ) and RV index (e.g., rvid) are specified values ​​(e.g., I MCS = 26 and rvid = 1).

[0065] Note that when a maximum rank > 4 is set, the field for the second CW described above may be included only when a rank > 4 is indicated, and may not be included or may be ignored when a rank ≦ 4 is indicated.

[0066] For dual CWs, the field for the second CW may be indicated using an existing field. For example, one or more (or all) bits of the antenna port field may be used to indicate at least one of the TRI (rank), MCS, RV, and NDI for the second CW. Note that if the antenna port field is 4 or 5 bits, for example, bits 1 to 4 may be used for PUSCH transmissions with ranks greater than 4.

[0067] However, sufficient consideration has not been given to CG PUSCHs with a rank greater than 4. For example, for a UE supporting 8 transmissions (e.g., an 8Tx UE), for CG PUSCH transmissions with a rank greater than 4 (e.g., CG PUSCH transmission with rank>4), issues arise such as whether enabling / disabling (or activation / deactivation) of the second CW (or second TB) is supported, and if supported, how to control it (e.g., how to control it when the number of TBs that can be used (activated) differs between the DG PUSCH and the CG PUSCH).

[0068] If appropriate control is not performed for the CG PUSCH, there is a risk that an increase in communication throughput may be suppressed or that the utilization efficiency of radio resources may decrease.

[0069] Therefore, the present inventors have conceived a method for appropriately performing CG PUSCH transmission when PUSCH transmission with a rank greater than 4 is used.

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

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

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

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

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

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

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

[0077] In the present disclosure, TPMI and TPMI index may be interchangeable. In the present disclosure, TX (transmission), port, antenna port, etc. may be interchangeable. A port / antenna port may refer to a port / antenna port for UL (e.g., SRS / PUSCH) transmission. In the present disclosure, an SRS resource set and a resource set may be interchangeable. A coherent group and an SRS resource set may be interchangeable.

[0078] In this disclosure, 8TX is mainly described, but the same applies to 5TX, 6TX, 7TX, 8 or more TX, 4 or less TX, etc. In the following embodiments, "4" may be read as "n (n is any integer)."

[0079] In the present disclosure, the rank, transmission rank, number of layers, and number of antenna ports may be interchangeable. Furthermore, the application of one CW / TB, the number of layers being four or less, four or less layers, etc. may be interchangeable. The application of two CW / TBs, the number of layers being more than four, more than four layers, 2TB PUSCH, dual CW PUSCH, etc. may be interchangeable.

[0080] In addition, in the present disclosure, a UE that supports PUSCH transmission with more than four layers may support 2TB spatial multiplexing. Note that in the present disclosure, spatial multiplexing may be interpreted interchangeably as transmission of two TB / CWs multiplexed in the spatial domain in the PUSCH.

[0081] In the present disclosure, activating ( / deactivating) CG transmission (CG PUSCH) may be interpreted as activating ( / deactivating) at least one of a CG setting, a transmission based on a CG setting, a transmission using resources corresponding to a CG setting, and the like.

[0082] In the present disclosure, activating one or two TBs for a certain CG PUSCH configuration may be interpreted as transmitting CG PUSCH for one or two TBs based on the CG PUSCH configuration.

[0083] In the following embodiments, the CG PUSCH may be replaced with at least one of the CG PUSCH, the repeated CG PUSCH, and the SDCI-based MTRP CG PUSCH. Note that different or the same content of the embodiments may be applied to these CG PUSCHs.

[0084] (Wireless Communication Method) First Embodiment The first embodiment relates to a case where the number of TBs that can be used (enabled) for a DG PUSCH and at least one CG PUSCH is different.

[0085] When a 2TB PUSCH is configured for a DG PUSCH, the number of layers of a specific CG PUSCH may be limited to 4 or less. The specific CG PUSCH may be either or both of a Type 1 CG PUSCH and a Type 2 CG PUSCH.

[0086] Note that the specific CG PUSCH may be a CG PUSCH corresponding to a specific configured grant setting index (for example, RRC information element ConfiguredGrantConfigIndex), or may be a CG PUSCH configured in a specific BWP / cell.

[0087] Furthermore, when a 2TB PUSCH is configured for a DG PUSCH, a CG PUSCH that can have a layer number greater than four may correspond to either or both of a Type 1 CG PUSCH and a Type 2 CG PUSCH, may correspond to a CG PUSCH corresponding to a specific configured grant setting index, or may correspond to a CG PUSCH configured in a specific BWP / cell.

[0088] Note that configuring a 2TB PUSCH for a DG PUSCH may be interpreted as configuring a 2TB PUSCH in PUSCH configuration information (for example, the RRC information element PUSCH-Config).

[0089] When a 2TB PUSCH is configured for a DG PUSCH, the UE may determine that a 2TB PUSCH is configured for a CG PUSCH other than the specific CG PUSCH (for example, the other of the type 1 CG PUSCH and the type 2 CG PUSCH).

[0090] Furthermore, regardless of whether a 2TB PUSCH is configured for a DG PUSCH, the UE may be configured in CG configuration information (e.g., the RRC information element ConfiguredGrantConfig) that a 1TB PUSCH or a 2TB PUSCH is configured for a certain type of CG PUSCH.

[0091] According to the first embodiment described above, the UE can appropriately determine the rank of the CG PUSCH. For example, even when PUSCH / CG PUSCHs with ranks greater than 4 are supported, by limiting the rank of a specific CG PUSCH to 4 or less, it is expected that the UE load associated with transmitting the specific CG PUSCH can be reduced.

[0092] Second Embodiment The second embodiment relates to a DCI for activation / release of a Type 2 CG PUSCH in the case where a 2TB PUSCH is configured for at least a DG PUSCH.

[0093] In the second embodiment, a 2TB PUSCH may or may not be applied to the type 2 CG PUSCH. Whether a 2TB PUSCH is applied to the activated type 2 CG PUSCH may be configured by higher layer signaling or may be determined based on DCI for activation.

[0094] In the second embodiment, it is assumed that a 2TB PUSCH is configured for the DG PUSCH, and the UE controls the 2TB PUSCH according to a specific DCI format, where the specific format may include at least one of DCI format 0_1, DCI format 0_2, DCI format 0_3, and DCI format 0_0.

[0095] DCI formats 0_0, 0_1, and 0_2 are DCI formats defined in the existing NR standard, but may be interchangeably read as DCI formats for scheduling the PUSCH of one cell. DCI format 0_3 may be interchangeably read as DCI formats for scheduling the PUSCH of multiple cells.

[0096] In a second embodiment, when the UE detects (receives) the specific DCI format for controlling the 2TB PUSCH, the UE may determine whether the specific DCI format is a valid DCI for activation / release based on a set of specific DCI fields (one or more fields) of the specific DCI format. For example, the UE may determine that the specific DCI format is a valid DCI for activation / release when all of the set of specific DCI fields have specific values. Note that the specific value may be different for each corresponding field.

[0097] The set of specific DCI fields may include at least one of the following DCI fields: an NDI field for the first TB, an NDI field for the second TB, an RV field for the first TB, an RV field for the second TB, an MCS field for the first TB, and an MCS field for the second TB.

[0098] The set of specific DCI fields may include fields other than the above DCI fields (for example, an HPN field, similar to the existing DCI for activation / release).

[0099] Furthermore, the set of specific DCI fields may be different between the activation DCI and the release DCI. For example, the set of specific DCI fields for the activation DCI may include the NDI field and the RV field for the 1 / 2 TB and may not include the MCS field, and the set of specific DCI fields for the release DCI may include the NDI field, the RV field, and the MCS field for the 1 / 2 TB.

[0100] The TB activated / released by one activation / release DCI in the second embodiment may be in accordance with at least one of the following: - Always the first TB; - Either the first TB or the second TB; - Either the first TB, the second TB, or both TBs; - Always both TBs.

[0101] Indicating activation / release of the i-th TB (i=1 or 2) may be achieved by the above DCI field for the i-th TB having a specific value, or may be determined based on a specific rule.

[0102] The specific rule is that the DCI includes a field indicating that one TB is disabled (e.g., an MCS index (e.g., I MCS ) and RV index (e.g., rvid) are specified values ​​(e.g., I MCS In this case, the UE can determine that the DCI indicating that one TB is not deactivated does not correspond to the DCI indicating the activation / release of the other TB.

[0103] The specific rule may be configured by higher layer signaling. For example, a rule that the indication of activation / release of the second TB is determined by the DCI field for the first TB having a specific value may be configured in the UE by higher layer signaling, or the specified value may be configured in the UE by higher layer signaling.

[0104] In addition, the UE may determine the activation / release of the Type 2 CG PUSCH having 1 TB / 2 TB based on the NDI field / RV field for the enabled TB in the specific DCI format having the CRC scrambled by the CS-RNTI. In addition, in the present disclosure, the CS-RNTI may be read as a specific RNTI or the like.

[0105] 2A and 2B are diagrams showing examples of special fields for validation of DCI for activation of Type 2 CG in the second embodiment, where Fig. 2A corresponds to the case where the UE is provided with one CG Type 2 configuration in the active BWP, and Fig. 2B corresponds to the case where the UE is provided with multiple CG Type 2 configurations in the active BWP.

[0106] In this example, the specific DCI format is DCI format 0_1. Therefore, DCI formats 0_0 and 0_2 are the same as those in Figures 1A and 1B, but are shown for comparison purposes.

[0107] Figure 2A means that DCI format 0_1, in which the HPN field (if present) is set to all '0' and the RV field (if present) is set to all '0' for enabled TBs, can correspond to the DCI for activation.

[0108] FIG. 2B indicates that DCI format 0_1, in which the RV field (if present) is set to all '0' for the enabled TB, may correspond to the activation DCI.

[0109] For example, DCI format 0_1 ​​in which the HPN field (if present) is set to all '0's, the RV field (if present) is set to all '0's or all '0's for enabled TBs, the MCS field is set to all '1's, and the frequency domain resource allocation field is set to all '0's or '1's may correspond to a release DCI.

[0110] In the present disclosure, setting a certain field to all '0's or all '1's may be interpreted as setting the field to a predetermined specific bit string.

[0111] According to the second embodiment described above, the UE can appropriately determine the DCI for activation / release of the 1 TB / 2 TB type 2 CG PUSCH.

[0112] Third Embodiment The third embodiment relates to a specific DCI for activation / release in a type 2 CG PUSCH supporting a 2TB PUSCH when one or more TBs have already been activated.

[0113] In the third embodiment, when two TBs are activated for a certain CG PUSCH configuration, the operation of releasing one of these two TBs may or may not be supported.

[0114] In other words, the above operation is not supported, the UE may expect that the DCI for releasing a Type 2 CG PUSCH is a DCI that releases all activated TBs for a certain CG PUSCH configuration.

[0115] If two TBs are activated for a certain CG PUSCH configuration, the UE may detect and ignore a DCI indicating the release of only one of these two TBs (without determining that it is a valid DCI for release).

[0116] Also, in the third embodiment, when only one of two TBs for a certain CG PUSCH configuration is activated, an operation to activate both of these two TBs (or an operation to activate the other of these two TBs) may or may not be supported.

[0117] In other words, the above operation is not supported, the UE may expect that the DCI for activation of Type 2 CG PUSCH is a DCI that can activate at least one TB only for CG PUSCH configurations in which all TBs are not activated (and may determine that it is a valid DCI for activation of at least one TB).

[0118] When one or more TBs are activated for a certain CG PUSCH configuration, the UE may detect a new activation DCI for the CG PUSCH configuration but may ignore it (it may not determine that the DCI is a valid activation DCI).

[0119] According to the third embodiment described above, it is possible to eliminate the discrepancy between the UE and the base station regarding the activation / release operation of the Type 2 CG PUSCH.

[0120] <Supplementary Information> [Notification of Information to UE] In the above-described embodiments, any information may be notified to the UE (from a network (NW) (e.g., a base station (BS))) (in other words, reception of any information from the BS by the UE) using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.

[0121] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new Logical Channel ID (LCID) in the MAC subheader, which is not defined in existing standards.

[0122] When the notification is made by DCI, the notification may be made by a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used to scramble Cyclic Redundancy Check (CRC) bits assigned to the DCI, the format of the DCI, etc.

[0123] Furthermore, notification of any information to the UE in the above embodiments may be performed periodically, semi-persistently, or aperiodically.

[0124] [Notification of Information from UE] In the above-described embodiments, notification of any information from the UE (to the NW) (in other words, transmission / report of any information from the UE to the BS) may be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PUCCH, PUSCH, PRACH, reference signal), or a combination thereof.

[0125] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new LCID, which is not defined in existing standards, in the MAC subheader.

[0126] If the notification is made by UCI, the notification may be transmitted using PUCCH or PUSCH.

[0127] Furthermore, any information in the above-described embodiments may be notified from the UE periodically, semi-persistently, or aperiodically.

[0128] [Application of Each Embodiment] At least one of the above-described embodiments may be applied when a specific condition is met. The specific condition may be defined in a standard or may be notified to a UE / BS using higher layer signaling / physical layer signaling.

[0129] At least one of the above-described embodiments may be applied only to UEs that have reported or support a particular UE capability.

[0130] The specific UE capability may indicate at least one of the following: - Supporting specific processing / operation / control / information for at least one of the above embodiments; - Supporting the case where the number of TBs available (enabled) for the DG PUSCH and at least one CG PUSCH is different; - Supporting CG PUSCH when a 2TB PUSCH is configured for at least the DG PUSCH; - Supporting 2TB CG PUSCH; - Supporting interpretation of the NDI / RV fields for enabled TBs as activation / release of Type 2 CG PUSCH; - Supporting TB-by-TB activation (of CG PUSCH); - Supporting TB-by-TB release (of CG PUSCH).

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

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

[0133] Furthermore, at least one of the above-described embodiments may be applied when the UE configures / activates / triggers specific information related to the above-described embodiment (or performs the operations of the above-described embodiment) through higher layer signaling / physical layer signaling. For example, the specific information may be information indicating that 2TB CG PUSCH is enabled, any RRC parameter for a specific release (e.g., Rel. 18 / 19), etc.

[0134] If the UE does not support at least one of the specific UE capabilities or is not configured with the specific information, the UE may apply, for example, the behavior of Rel. 15 / 16 / 17.

[0135] (Supplementary Notes) The following inventions are supplemented with respect to one embodiment of the present disclosure. [Supplementary Note 1] A terminal comprising: a receiver that receives downlink control information (DCI) for a dynamic grant-based uplink shared channel when the dynamic grant-based uplink shared channel of two transport blocks (TBs) is configured; and a controller that determines, based on a set of specific fields included in the DCI, whether the DCI is a valid activation or release DCI for the configured grant-based uplink shared channel of one or two TBs. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein, when the DCI has a cyclic redundancy check (CRC) scrambled by a specific Radio Network Temporary Identifier (RNTI), the controller determines, based on a redundancy version field for an enabled TB, whether the DCI is a valid activation or release DCI for the configured grant-based uplink shared channel. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein, when the DCI includes a field indicating that one of two TBs is disabled, the controller determines that the DCI is a valid activation or release DCI for the configured grant-based uplink shared channel of the other of the two TBs. [Supplementary Note 4] The terminal according to any of Supplementary Note 1 to Supplementary Note 3, wherein, when two TBs are activated for the configuration of a certain configured grant-based uplink shared channel and a DCI indicating the release of only one of the two TBs is detected, the controller does not determine that the DCI is a valid release DCI.

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

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

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

[0139] In EN-DC, the LTE (E-UTRA) base station (eNB) is the master node (Master Node (MN)), and the NR base station (gNB) is the secondary node (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.

[0140] 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 SN are NR base stations (gNBs) (NR-NR Dual Connectivity (NN-DC))).

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

[0142] 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 (CCs) and dual connectivity (DC).

[0143] 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 higher than 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 correspond to a higher frequency band than FR2.

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

[0145] The multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with the Common Public Radio Interface (CPRI), an X2 interface, etc.) or wirelessly (e.g., 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.

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

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

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

[0149] An Orthogonal Frequency Division Multiplexing (OFDM)-based radio access scheme may be used in the wireless 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).

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

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

[0152] 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)), or the like may be used as an uplink channel.

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

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

[0155] 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 a UL grant, a UL DCI, etc. Note that the PDSCH may be replaced with DL data, and the PUSCH may be replaced with UL data.

[0156] A control resource set (CORESET) and a search space may be used to detect the PDCCH. The CORESET corresponds to resources for searching 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 the CORESET associated with a certain search space based on the search space configuration.

[0157] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be referred to as a search space set. Note that the terms "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," "CORESET configuration," and the like in the present disclosure may be read interchangeably.

[0158] The PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), delivery confirmation 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.

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

[0160] 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, as the DL-RS, 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.

[0161] 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 an SS (PSS, SSS) and a PBCH (and a 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 a reference signal.

[0162] Furthermore, in the wireless communication system 1, a sounding reference signal (SRS), a demodulation reference signal (DMRS), or the like 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).

[0163] (Base Station) Fig. 4 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.

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

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

[0166] 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, control information, sequences, etc. to be transmitted as signals, 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.

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

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

[0169] 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 relates, such as an array antenna.

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

[0171] The transceiver 120 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

[0172] The transmitter / receiver unit 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.

[0173] The transmitter / receiver unit 120 (transmission processing unit 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.

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

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

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

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

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

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

[0180] In addition, when a dynamic grant-based uplink shared channel of two transport blocks (TBs) is configured in a user terminal 20, the transceiver unit 120 may transmit downlink control information (DCI) for the dynamic grant-based uplink shared channel to the user terminal 20.

[0181] The control unit 110 may control a specific set of fields to be included in the DCI to allow the user terminal 20 to determine whether the DCI is a valid activation or release DCI for a grant-based uplink shared channel configured for one or two TBs.

[0182] (User Terminal) Fig. 5 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.

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

[0184] 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, etc., which are described based on common understanding in the technical field to which the present disclosure relates.

[0185] The control unit 210 may control signal generation, mapping, etc. The control unit 210 may 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.

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

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

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

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

[0190] The transceiver unit 220 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

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

[0192] The transmitter / receiver unit 220 (transmission processing unit 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.

[0193] 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 if not, it may not be necessary to perform DFT processing as the transmission processing.

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

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

[0196] The transceiver unit 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, and acquire user data, etc.

[0197] The transceiver 220 (measurement unit 223) may perform measurements on the received signal. For example, the measurement unit 223 may perform RRM measurements, CSI measurements, 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.

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

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

[0200] In addition, when a dynamic grant-based uplink shared channel (DG PUSCH) of two transport blocks (TBs) is configured, the transceiver unit 220 may receive downlink control information (DCI) for the dynamic grant-based uplink shared channel.

[0201] The control unit 210 may determine whether the DCI is a valid activation or release DCI for a configured grant-based uplink shared channel (CG PUSCH) of one or two TBs based on a set of specific fields included in the DCI.

[0202] The control unit 210 may determine whether the DCI is a valid activation or release DCI for the configured grant-based uplink shared channel based on a redundancy version field for an enabled TB when the DCI has a Cyclic Redundancy Check (CRC) scrambled by a specific Radio Network Temporary Identifier (RNTI).

[0203] The control unit 210 may determine that, when the DCI includes a field indicating that one of the two TBs is disabled, the DCI is a valid activation or release DCI for the configured grant-based uplink shared channel of the other of the two TBs.

[0204] When two TBs are activated for a configuration of a certain grant-based uplink shared channel and a DCI indicating the release of only one of the two TBs is detected, the control unit 210 does not need to determine that the DCI is a valid DCI for release.

[0205] (Hardware Configuration) Note that 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 be realized by combining software with the single device or the multiple devices.

[0206] 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 described above, the implementation method of each is not particularly limited.

[0207] For example, a base station, a user terminal, or the like 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. 6 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, and the like.

[0208] In the present disclosure, the terms apparatus, circuit, device, section, unit, etc. may be used 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.

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

[0210] Each function in the base station 10 and the user terminal 20 is realized, for example, by loading specified 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.

[0211] 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), transceiver unit 120 (220), etc. may be realized by the processor 1001.

[0212] 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 implemented by a control program stored in the memory 1002 and running on the processor 1001, and the other functional blocks may be implemented in a similar manner.

[0213] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EEPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. The memory 1002 may also be referred to as a register, cache, main memory, etc. The memory 1002 may store executable programs (program codes), software modules, etc. for implementing a wireless communication method according to an embodiment of the present disclosure.

[0214] Storage 1003 is a computer-readable recording medium and may be composed of 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, a stick, a key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be referred to as an auxiliary storage device.

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

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

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

[0218] 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 this hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0219] (Modifications) Note that terms described 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.

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

[0221] 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, Subcarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame structure, specific filtering performed by a transceiver in the frequency domain, and specific windowing performed by a transceiver in the time domain.

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

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

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

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

[0226] 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. Note that the definition of TTI is not limited to this.

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

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

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

[0230] 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 greater than or equal to 1 ms.

[0231] 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 be determined based on numerology.

[0232] 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, each of which may be composed of one or more resource blocks.

[0233] In addition, one or more RBs may be referred to as a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

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

[0235] A Bandwidth Part (BWP), which may also be referred to as a partial 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 BWP and numbered within the BWP.

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

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

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

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

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

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

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

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

[0244] The notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the 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.

[0245] Note that the physical layer signaling may be referred to as 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 referred to as 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).

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

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

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

[0249] 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), these wired and / or wireless technologies are included within the definition of transmission media.

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

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

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

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

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

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

[0256] Furthermore, in the present disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) property," and "specific QCL type (e.g., Type A, Type D)" may be interchangeable.

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

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

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

[0260] 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 partitioned 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 terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication service within that coverage.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0279] 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 an uplink channel and a downlink channel may be read as a sidelink channel.

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

[0281] 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), a Serving-Gateway (S-GW), etc.), or a combination thereof.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A terminal having a receiving unit that receives downlink control information (DCI) for a dynamic grant-based uplink shared channel of two transport blocks (TBs) when the dynamic grant-based uplink shared channel is configured; and a control unit that determines whether the DCI is a valid activation or release DCI for a configured grant-based uplink shared channel of one or two TBs based on a set of specific fields included in the DCI.

2. The terminal of claim 1, wherein the control unit determines whether the DCI is a valid activation or release DCI for the configured grant-based uplink shared channel based on a redundancy version field for an enabled TB when the DCI has a Cyclic Redundancy Check (CRC) scrambled by a specific Radio Network Temporary Identifier (RNTI).

3. The terminal of claim 1, wherein the control unit determines that, when the DCI includes a field indicating that one of the two TBs is disabled, the DCI is a valid activation or release DCI for the configured grant-based uplink shared channel of the other of the two TBs.

4. The terminal of claim 1, wherein when two TBs are activated for a configuration of a certain grant-based uplink shared channel and a DCI indicating the release of only one of the two TBs is detected, the control unit does not determine that the DCI is a valid DCI for release.

5. A wireless communication method for a terminal, comprising: when a dynamic grant-based uplink shared channel of two transport blocks (TBs) is configured, a step of receiving downlink control information (DCI) for the dynamic grant-based uplink shared channel; and a step of determining whether the DCI is a valid activation or release DCI for the configured grant-based uplink shared channel of one or two TBs based on a set of specific fields included in the DCI.

6. A base station having: a transmitter that transmits downlink control information (DCI) for a dynamic grant-based uplink shared channel of two transport blocks (TBs) to a terminal when the dynamic grant-based uplink shared channel is configured in the terminal; and a controller that controls a set of specific fields to be included in the DCI so that the terminal can determine whether the DCI is a valid activation or release DCI for a configured grant-based uplink shared channel of one or two TBs.