Terminal, wireless communication method, and base station

Abstract

The present invention provides a terminal, method, and base station that appropriately control UL transmission even when using multiple panels for UL transmission. [Solution] In a mobile communication system, a user terminal includes, when the application or switching between a first transmission mode and a second transmission mode is supported, a receiving unit that receives information about the transmission mode, and a control unit that determines the size of the effective bits for each transmission mode in a predetermined field of downlink control information (DCI) that schedules UL transmission, based on parameters corresponding to a sounding reference signal (SRS) resource set associated with the transmission mode.

Description

Technical Field

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

Background Art

[0002] In a Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) was specified for the purpose of further high data rates, low latency, etc. (Non-Patent Document 1). Also, for the purpose of further large capacity and sophistication of LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9), LTE-Advanced (3GPP Rel. 10-14) was specified.

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

Prior Art Documents

Non-Patent Documents

[0004]

Non-Patent Document 1

Summary of the Invention

[0005] In future wireless communication systems, the UE (Unified Element) may use one of multiple panels (or multiple beams) for uplink (UL) transmission. Furthermore, in Rel. 18 and later, support for Simultaneous Transmission across Multiple Panels (STxMP), which utilizes multiple panels to one or more transmission / reception points (TRPs), is being considered to improve UL throughput and reliability.

[0006] However, how to control UL transmission using multiple panels (e.g., simultaneous UL transmission) has not been adequately considered. If UL transmission using multiple panels is not handled properly, system performance may deteriorate, such as a decrease in throughput.

[0007] Therefore, one of the objectives of this disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately control UL transmission even when UL transmission is performed using multiple panels. [Means for solving the problem]

[0008] A terminal according to one aspect of the present disclosure includes, when the application or switching between a first transmission mode and a second transmission mode is supported, a receiving unit that receives information about a transmission mode, and a control unit that determines the size of the effective bits for each transmission mode in a predetermined field of downlink control information (DCI) that schedules UL transmission, based on parameters corresponding to a sounding reference signal (SRS) resource set associated with the transmission mode. [Effects of the Invention]

[0009] According to one aspect of this disclosure, UL transmission can be appropriately controlled even when using multiple panels for UL transmission. [Brief explanation of the drawing]

[0010] [Figure 1] Figure 1 shows an example of the association between precoder type and TPMI index. [Figure 2] Figures 2A and 2B show an example of single-panel UL transmission. [Figure 3] Figures 3A-3C show examples of methods 1-3 for simultaneous UL transmission using a multi-panel setup. [Figure 4] Figures 4A-4C show an example of a PUSCH transmission method. [Figure 5] Figures 5A-5C show other examples of PUSCH's transmission method. [Figure 6] Figure 6 shows an example of simultaneous UL transmission using a multi-panel setup. [Figure 7] Figures 7A and 7B show an example of the SRI field of DCI according to the first embodiment. [Figure 8] Figures 8A and 8B show other examples of the SRI field of DCI according to the first embodiment. [Figure 9] Figures 9A and 9B show an example of the SRI field of DCI according to the second embodiment. [Figure 10] Figures 10A and 10B show other examples of the SRI field of DCI according to the second embodiment. [Figure 11] Figures 11A and 11B show an example of the SRI field of DCI according to the third embodiment. [Figure 12] Figures 12A and 12B show other examples of the SRI field of DCI according to the third embodiment. [Figure 13] Figure 13 shows an example of a predetermined field (e.g., SRI field / TPMI field) of DCI according to the fourth embodiment. [Figure 14] FIG. 14 is a diagram showing an example of a predetermined field (for example, SRI field / TPMI field) of DCI according to the fourth embodiment. [Figure 15] FIGS. 15A and 15B are diagrams showing an example of BWP switching according to the fifth embodiment. [Figure 16] FIGS. 16A and 16B are diagrams showing another example of BWP switching according to the fifth embodiment. [Figure 17] FIG. 17 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 18] FIG. 18 is a diagram showing an example of a configuration of a base station according to an embodiment. [Figure 19] FIG. 19 is a diagram showing an example of a configuration of a user terminal according to an embodiment. [Figure 20] FIG. 20 is a diagram showing an example of a hardware configuration of a base station and a user terminal according to an embodiment. [Figure 21] FIG. 21 is a diagram showing an example of a vehicle according to an embodiment.

MODE FOR CARRYING OUT THE INVENTION

[0011] (PUSCH Precoder) In NR, it is considered that a UE supports at least one of codebook (Codebook (CB)) - based transmission and non - codebook (Non - Codebook (NCB)) - based transmission.

[0012] For example, it is considered that a UE determines a precoder (precoding matrix) for at least one of CB - based and NCB - based Physical Uplink Shared Channel (PUSCH) transmission using at least a Measurement Reference Signal (Sounding Reference Signal (SRS)) Resource Indicator (SRS Resource Indicator (SRI)).

[0013] For CB-based transmissions, the UE may determine the precoder for PUSCH transmission based on the SRI, Transmitted Rank Indicator (TRI), and Transmitted Precoding Matrix Indicator (TPMI). For NCB-based transmissions, the UE may determine the precoder for PUSCH transmission based on the SRI.

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

[0015] The UE may report UE capability information regarding the precoder type, and the base station may set the precoder type based on this UE capability information via upper-layer signaling. This UE capability information may also be information about the precoder type used by the UE in PUSCH transmission (which may be represented by the RRC parameter "pusch-TransCoherence").

[0016] In this disclosure, the upper-layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, or a combination thereof.

[0017] MAC signaling may use, for example, MAC Control Elements (MAC CEs) or MAC Protocol Data Units (PDUs). Broadcast information may also be, for example, Master Information Blocks (MIBs) or System Information Blocks (SIBs).

[0018] The UE may determine which precoder to use for PUSCH transmission based on precoder type information (which may be represented by the RRC parameter "codebookSubset") contained in the PUSCH configuration information (the "PUSCH-Config" information element of the RRC signaling) notified by upper-layer signaling. The UE may set a subset of the PMI specified by TPMI using codebookSubset.

[0019] The precoder type may be specified by fully coherent, partially coherent, and non-coherent, or by a combination of at least two of these (for example, they may be represented by parameters such as "fullyAndPartialAndNonCoherent" or "partialAndNonCoherent").

[0020] Fully coherent may mean that all antenna ports used for transmission are synchronized (this may also be expressed as being able to align phases, using the same precoder, etc.). Partially coherent may mean that some of the antenna ports used for transmission are synchronized, but those ports are not synchronized with the others. Non-coherent may mean that the individual antenna ports used for transmission are not synchronized.

[0021] Furthermore, a UE that supports fully coherent precoder types may be assumed to support partially coherent and noncoherent precoder types. A UE that supports partially coherent precoder types may be assumed to support noncoherent precoder types.

[0022] The precoder type may be reinterpreted as coherency, push-transmit coherence, coherent type, coherence type, codebook type, codebook subset, codebook subset type, etc.

[0023] The UE may determine a precoding matrix from multiple precoders (which may also be called precoding matrices, codebooks, etc.) for CB-based transmissions that corresponds to the TPMI index obtained from the DCI (e.g., DCI format 0_1; hereafter the same) for scheduling UL transmissions.

[0024] Figure 1 shows an example of the association between precoder type and TPMI index. Figure 1 corresponds to the table of precoding matrices W for single-layer (rank 1) transmission using 4 antenna ports with DFT-s-OFDM (Discrete Fourier Transform spread OFDM, where transform precoding is enabled).

[0025] In Figure 1, if the precoder type (codebookSubset) is fullyAndPartialAndNonCoherent, the UE is notified of one of the TPMIs from 0 to 27 for single-layer transmissions. If the precoder type is partialAndNonCoherent, the UE is set to one of the TPMIs from 0 to 11 for single-layer transmissions. If the precoder type is nonCoherent, the UE is set to one of the TPMIs from 0 to 3 for single-layer transmissions.

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

[0027] Non-coherent codebooks and partially coherent codebooks may also be called antenna selection precoders. Fully coherent codebooks may also be called non-antenna selection precoders.

[0028] In this disclosure, a partially coherent codebook may refer to a subset of codebooks (precoding matrices) corresponding to TPMIs specified by DCI for codebook-based transmission, obtained by a UE with a partially coherent codebook subset (e.g., RRC parameter "codebookSubset" = "partialAndNonCoherent") set, excluding the codebooks corresponding to TPMIs specified by a UE with a noncoherent codebook subset (e.g., RRC parameter "codebookSubset" = "nonCoherent") set (i.e., for single-layer transmission with 4 antenna ports, the codebooks for TPMIs 4 through 11).

[0029] In this disclosure, a fully coherent codebook may refer to a subset of fully coherent codebooks (e.g., RRC parameter "codebookSubset" = "fullyAndPartialAndNonCoherent") set to a UE that corresponds to a TPMI specified by DCI for codebook-based transmission, excluding the codebooks corresponding to TPMIs specified by a UE that has a partially coherent codebook subset (e.g., RRC parameter "codebookSubset" = "partialAndNonCoherent") set to a UE (i.e., for single-layer transmission with 4 antenna ports, the codebooks for TPMIs 12 to 27).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0050] Furthermore, the UE may be configured to use either codebook-based or non-codebook-based push transmission via a higher-layer parameter "txConfig" that indicates the transmission scheme. This parameter may represent the values ​​"codebook" or "noncodebook".

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

[0052] Incidentally, future wireless communication systems (e.g., Rel.18 NR and later) are expected to support simultaneous UL transmission using multiple beams / panels / TRPs (e.g., simultaneous multi-panel UL transmission (STxMP)) directed towards one or more transmission / reception points (TRPs).

[0053] For example, Rel.18 is considering simultaneous UL transmission using up to 2 TRPs / 2 panels. Furthermore, considering both single-DCI-based and multi-DCI-based multi-TRP operation, it is envisioned that the total number of layers across all panels will be a maximum of 4, and the total number of codewords across all panels will be a maximum of 2. Of course, the number of TRPs, panels, layers, and codewords are not limited to these figures.

[0054] (TPMI and transmission rank) In Rel.16, it is considered that for codebook-based PUSCH transmissions, the Transmitted Precoding Matrix Indicator (TPMI) and transmit rank are specified by specific fields (e.g., precoding information and layer number field) included in the downlink control information (e.g., DCI format 0_1). In this disclosure, rank may be interpreted as layer.

[0055] The precoder used by the UE for codebook-based push transmission may be selected from uplink codebooks having the same number of antenna ports as the value set by the higher-layer parameter (e.g., nrofSRS-Ports) configured for the SRS resource.

[0056] The size (number of bits) of the particular field is variable, depending on the number of antenna ports for PUSCH (e.g., the number of ports indicated by nrofSRS-Ports above) and several higher-layer parameters.

[0057] The relevant field may be 0 bits if a higher-layer parameter (e.g., txConfig) set for the UE is set to nonCodebook.

[0058] Furthermore, this particular field may be 0 bits if a higher-layer parameter (e.g., txConfig) set for the UE is set in the codebook for a single antenna port.

[0059] Furthermore, the specific field may have a bit length of 2 to 6 bits for each of the four antenna ports, based on at least one of the following: a higher-layer parameter set for the UE (e.g., txConfig) is set in the codebook, and the presence or absence of a transform precoder (enabled or disabled).

[0060] Furthermore, the specific field may have a bit length of 1 to 4 bits for two antenna ports, based on at least one of the following: a higher-layer parameter set for the UE (e.g., txConfig) is set in the codebook, and the presence or absence of a transform precoder (enabled or disabled).

[0061] The other higher-layer parameter may be at least one of the following: a parameter for specifying the UL's full-power transmission mode (e.g., ul-FullPowerTransmission, ul-FullPowerTransmission-r16), a parameter indicating the maximum transmission rank of the UL (e.g., maxRank), a parameter indicating a subset of a certain precoding matrix indicator (PMI) (e.g., codebookSubset), or a parameter for specifying a transform precoder (e.g., transformPrecoder).

[0062] (Single panel transmission) The single-panel UL transmission method or candidate single-panel UL transmission method may be at least one of the following transmission methods A and B (single-panel UL transmission methods A and B). In this disclosure, panel / UE panel may be interpreted as a set of UE capability values ​​reported for each UE capability (e.g., UE capability value set). Also in this disclosure, different panels, different spatial relationships, different joint TCI states, different TPC parameters, different antenna ports, etc., may be interpreted as one another.

[0063] <Transmission Method A: Single Panel Single TRP UL Transmission> In Rel.15 and Rel.16, the UE uses a transmission method in which it transmits ULs to one TRP at one time point in time from only one beam and panel (Figure 2A).

[0064] <Transmission Method B: Single Panel Multi-TRP UL Transmission> Rel.17 explores the possibility of performing UL transmissions from only one beam and panel at a single point in time, and then repeatedly transmitting to multiple TRPs (Figure 2B). In the example in Figure 2B, the UE transmits a PUSCH from panel #1 to TRP #1 (switching beam and panel), and then transmits a PUSCH from panel #2 to TRP #2. The two TRPs are connected via an ideal backhaul.

[0065] (Multi-panel transmission) In Rel.18 and later, support for simultaneous UL transmission using multiple panels (e.g., simultaneous multi-panel UL transmission (STxMP)) to one or more TRPs is being considered to improve UL throughput and reliability. Furthermore, multi-panel UL transmission schemes are being considered for specific UL channels (e.g., PUSCH / PUCCH).

[0066] For multi-panel UL transmissions, for example, up to X panels (e.g., X=2) and up to Y panels (e.g., Y=2) may be supported. If UL precoding instructions for PUSCH are supported in multi-panel UL transmissions, existing system codebooks (e.g., Rel.16 or earlier) may be supported for simultaneous multi-panel transmissions. When considering single-DCI and multi-DCI based multi-TRP operations, the number of layers may be up to x (e.g., x=4) across all panels, and the number of codewords (CW) may be up to y (e.g., y=2) across all panels.

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

[0068] <Transmission Method 1: Coherent Multi-Panel UL Transmission> Multiple panels may be synchronized with each other. All layers are mapped to all panels. Multiple analog beams are indicated. The SRS Resource Indicator (SRI) field may be extended. This scheme may use up to four layers for the UL.

[0069] In the example in Figure 3A, the UE maps one codeword (CW) or one transport block (TB) to L layers (PUSCH(1,2,…,L)) and transmits L layers from each of the two panels. Panels #1 and #2 are coherent. Transmission method 1 can gain gain through diversity. The total number of layers across the two panels is 2L. If the maximum total number of layers is 4, then the maximum number of layers on a single panel is 2.

[0070] <Transmission Method 2: Non-coherent multi-panel UL transmission of a single codeword (CW) or transport block (TB)> Multiple panels do not need to be synchronized. Different layers are mapped to different panels and to a single CW or TB for a PUSCH from multiple panels. A layer corresponding to a single CW or TB may be mapped to multiple panels. This transmission scheme may use up to 4 or up to 8 layers for UL. If it supports up to 8 layers, this transmission scheme may support a single CW or TB using up to 8 layers.

[0071] In the example shown in Figure 3B, the UE maps 1 CW or 1 TB to k layers (PUSCH(1,2,…,k)) and Lk layers (PUSCH(k+1,k+2,…,L)), transmitting k layers from panel #1 and Lk layers from panel #2. Transmission method 2 can obtain gain through multiplexing and diversity. The total number of layers in the two panels is L.

[0072] <Transmission Method 3: Non-coherent multi-panel UL transmission using two CW or TB signals> Multiple panels do not need to be synchronized. Different layers are mapped to different panels and to two CW or TB signals for a PUSCH from multiple panels. A layer corresponding to one CW or TB signal may be mapped to one panel. Layers corresponding to multiple CW or TB signals may be mapped to different panels. This transmission scheme may use up to 4 or 8 layers for a UL signal. If supporting up to 8 layers, this transmission scheme may support up to 4 layers per CW or TB signal.

[0073] In the example shown in Figure 3C, the UE maps CW#1 or TB#1 of the 2CW or 2TB signals to k layers (PUSCH(1,2,…,k)) and CW#2 or TB#2 to Lk layers (PUSCH(k+1,k+2,…,L)), transmitting k layers from panel #1 and Lk layers from panel #2. Transmission method 3 can obtain gain through multiplexing and diversity. The total number of layers in the two panels is L.

[0074] In each of the above transmission methods, the base station may set or instruct a panel-specific transmission for UL transmission using UL TCI or panel ID. UL TCI (UL TCI state) may be based on signaling similar to DL beam instruction supported in Rel.15. Panel ID may be implicitly or explicitly applied to at least one transmission of target RS resource or target RS resource set, PUCCH, SRS, and PRACH. If panel ID is explicitly communicated, panel ID may be set in at least one of target RS, target channel, and reference RS (e.g., DL RS resource configuration or spatial relation information).

[0075] (Simultaneous multi-panel transmission) In the one or more transmission methods / modes described above, multi-panel UL transmission (e.g., Simultaneous Transmission across Multiple Panels (STxMP)) is being considered for PUSCH scheduling based on one DCI (Single DCI) and PUSCH scheduling based on multiple DCIs (Multi-DCI).

[0076] <Single DCI-based STxMP> In simultaneous multi-panel transmission (STxMP) in a single DCI-based multi-TRP system, the following methods may be applied to UL transmission (e.g., PUSCH). • Space Division Multiplexing (SDM) method: Different layers / DMRS ports of a single PUSCH are precoded separately and transmitted simultaneously from different UE beams / panels (see Figures 4A and 4B). • Spatial Division Multiplexing Repetition (SDM) scheme: Two PUSCH transmission opportunities with different redundant versions (Redundancy Versions (RVs)) of the same TB are transmitted simultaneously from two different UE beams / panels on the same time and frequency resources (see Figure 4C). • Frequency Division Multiplexing (FDM)-A scheme: Different portions of the frequency domain resources for a single push transmission occasion (e.g., one push transmission occasion) are transmitted from different UE beams / panels (see Figure 5A). • FDM-B method: Two Push transmission opportunities with the same TB and the same / different RV are transmitted from different UE beams / panels on non-overlapping frequency-domain resources and the same time-domain resources (see Figure 5B). • SFN-based transmission method: All identical layer / DMRS ports on a single pusher transmit simultaneously from two different UE beams / panels (see Figure 5C).

[0077] In this disclosure, repeated transmission and transmission may be interpreted interchangeably. Transmitting multiple TBs may mean transmitting the same TB multiple times, or transmitting different TBs.

[0078] [Space division multiplexing (SDM)] The UE may assume that PUSCH repetitions with Space Division Multiplexing (SDM) applied are scheduled to use the same time and frequency resources. That is, if the UE uses multiple coherent panels, it may transmit SDM-applied PUSCH repetitions using the same time and frequency resources.

[0079] Figure 4A shows an example of repeated transmission with SDM applied in a single CW. In Figure 4A, the time and frequency resources of Layer #1-2 and Layer #3-4 corresponding to PUSCH / PUCCH are the same.

[0080] Figure 4B shows an example of repeated transmission with SDM applied to two CW modes. In Figure 4B, the time and frequency resources for CW#1 and CW#2 corresponding to PUSCH / PUCCH are the same.

[0081] Figure 4C shows an example of repetitive transmission with SDM applied. In Figure 4C, the time and frequency resources of repetitions #1 and #2 of PUSCH / PUCCH are the same.

[0082] Furthermore, a push transmission using SDM (for example, a push repetition transmission) may have a configuration in which at least a portion of the time and frequency resources overlap.

[0083] [Frequency division multiplexing (FDM)] A UE may assume that frequency division multiplexing (FDM) applied push / pucch repetitions are scheduled on the same time resources but different frequency resources. That is, if a UE uses multiple coherent panels, it may transmit FDM-applied push / pucch repetitions on the same time resources but different frequency resources.

[0084] Figure 5A shows a first example of repeated transmission using FDM (FDM-A). Figure 5A shows an example where one PUSCH / PUCCH repeated transmission is performed per TB / UCI.

[0085] Figure 5B shows a second example of repeated transmission using FDM (FDM-B). Figure 5B shows an example where two PUSCH / PUCCH repeated transmissions are performed for one TB / UCI.

[0086] Figure 5C shows an example of repeated transmission using a single frequency network (SFN). Figure 5C shows an example where one PUSCH / PUCCH is transmitted using a different beam / panel for each TB / UCI.

[0087] As shown in Figures 4A and 4B, when performing simultaneous multi-panel transmission (STxMP SDM scheme) based on spatial division multiplexing for non-coded book PUSCH transmission, different layer / DMRS ports of a single PUSCH can be precoded separately and transmitted simultaneously from different UP panels.

[0088] For simultaneous multi-panel transmissions based on the spatial division multiplexing scheme of non-code book-based PUSCH, the following two options are conceivable as SRI indications:

[0089] 《Option 1》 One SRI combination (e.g., one SRI combination) is specified. The SRI combination may be specified from SRS resources in a non-code book across two panels (e.g., NCB SRS resources across two panels).

[0090] 《Option 2》 Multiple (e.g., two) SRS combinations (e.g., two SRI combinations) are specified. Each SRI combination may be specified from SRS resources in a non-code book of one panel (e.g., NCB SRS resources of one panel).

[0091] An SRI combination may include one or more SRS resources (e.g., SRS resources for a non-code book). For example, one SRI combination (or SRI field) may indicate a corresponding SRI / SRS resource for each panel. An SRI combination may be interpreted as an SRI set or SRI group.

[0092] <Multi-DCI based STxMP> In Rel.18 and later, it is expected that simultaneous transmission of UL channels / UL signals (e.g., PUSCH+PUSCH) will be supported in STxMP in multi-DCI-based multi-TRP systems (see Figure 6). As an example, it is expected that simultaneous transmission of PUSCH signals (e.g., PUSCH+PUSCH) will be supported.

[0093] In this case, the UE can simultaneously send two independent PUSCHs associated with different TRPs in the same active BWP. The total number of layers corresponding to these two PUSCHs may be specified as a maximum of X (or less than or equal to X), where X may be, for example, 4, or any other value. The maximum number of layers for each of the two PUSCHs may be X / 2 (for example, 2), or any other value.

[0094] For multi-DCI based STxMP, in the scheduling of PUSCH simultaneous transmissions (e.g., STxMP PUSCH+PUSCH Transmission), SRS resource sets and CORESET pool indices may be associated based on predetermined rules. For example, a first SRS resource set may be associated with a first CORESET pool index (e.g., 0), and other SRS resource sets may be associated with a second CORESET pool index (e.g., 1).

[0095] A PUSCH may be associated with an SRS resource set that has the same CORESER pool index value. For example, a PUSCH may be associated with an SRS resource set that is associated with the CORESER pool index of the CORESET corresponding to the PDCCH that schedules the PUSCH.

[0096] The interpretation method for SRI / TPMI fields in DCI may differ between dynamic grant-based PUSCH (e.g., DG-PUSCH) and setting grant-based PUSCH (e.g., Type 2 CG-PUSCH).

[0097] For DG-PUSCH, the indicated SRI / TPMI field may correspond to an SRS resource set associated with the same value as the CORESET pool index of the CORESET that received the DCI scheduling the PUSCH (e.g., scheduling DCI format0_1 / 0_2). For type 2 CG-PUSCH, the indicated SRI / TPMI field may correspond to an SRS resource set associated with the same value as the CORESER pool index of the CORESET that received the activation DCI.

[0098] In the case of a Type 1 CG-PUSCH, one SRS resource set index may be set in the RRC parameter associated with the configuration grant (e.g., ConfiguredGrantConfig), and a predetermined RRC parameter (e.g., srs-ResourceIndicator / precodingAndNumberOfLayers) may correspond to that SRS resource set.

[0099] For multi-DCI based STxMP (e.g., PUSCH+PUSCH), asymmetric panels may be considered, allowing for separate configuration of SRS resource count / SRS ports (or number of SRS ports) / maximum rank (e.g., maxrank) / codebook subset / full power mode for the two panels / TRPs. Asymmetric panels may mean that the two panels have different capabilities regarding the number of SRS ports / maximum rank / codebook subset, etc.

[0100] For example, when two SRS resource sets are configured for a multi-DCI based STxMP (e.g., PUSCH+PUSCH), predetermined parameters corresponding to the two configured SRS resource sets may be set separately. These predetermined parameters may be at least one of the following: the number of SRS resources, the maximum number of max ranks / SSB indices (e.g., maxRank / Lmax), the codebook subset (e.g., codebook subset), and the full power mode (e.g., fullpower mode).

[0101] Incidentally, the size of the predetermined fields included in DCI is determined based on the number of SRS resources in the SRS resource set, the maximum rank, and the codebook subset (or the number of codebook subsets). The predetermined fields may be, for example, SRI fields / TPMI fields.

[0102] For example, for a CB's SRI field, the size of the SRI field is determined based on the number of SRS resources in the SRS resource set. Alternatively, for an NCB's SRI field, the size of the SRI field is determined based on the number of SRS resources in the SRS resource set and the maximum rank. Alternatively, for a CB's TPMI field, the size of the TPMI field is determined based on the number of antenna ports and codebook subset, the maximum rank, and the full power mode.

[0103] Thus, it is assumed that different numbers or values ​​of SRS resources / antenna ports / maximum rank / full power mode / codebook subset settings will be supported for two panels / TRP / SRS resource sets / CORESET pool index / PDCCH / DCI / CORESET. In such cases, the question arises as to how to determine / control the size of certain fields in the DCI (e.g., SRI field / TPMI field) for PUSCH scheduled by different CORESET pool indexes (or different PDCCH / DCI). If the size of certain fields included in the DCI cannot be properly determined / controlled, UL transmission may not be performed properly, potentially degrading communication quality.

[0104] Therefore, the inventors focused on the case where different numbers or values ​​of SRS resources / antenna ports / maximum rank / full power mode / codebook subsets are supported for two panels / TRP / SRS resource sets / CORESET pool index / PDCCH / DCI / CORESET, and considered appropriate UL transmission control in such cases, conceiving one aspect of this embodiment.

[0105] Alternatively, the inventors focused on cases where switching between single TRP / single TRP transmission and simultaneous UL transmission using a multi-panel (e.g., STxMP) is supported, and considered appropriate UL transmission control in such cases, conceiving one embodiment of this design.

[0106] Alternatively, the inventors focused on the UE operation during bandwidth portion (BWP) switching in cases where simultaneous UL transmission using multiple panels (e.g., STxMP) is supported, and investigated appropriate UL transmission control in such cases, conceiving one aspect of this embodiment.

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

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

[0109] In this disclosure, terms such as notice, activate, deactivate, indicate, select, configure, update, and determine may be interpreted interchangeably. In this disclosure, terms such as support, control, controllable, operate, and operable may be interpreted interchangeably.

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

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

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

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

[0114] In this disclosure, multi-TRP, multi-TRP system, multi-TRP transmission, multi-PDSCH, channel using multi-TRP, channel using multiple TCI state / spatial relationships, multi-TRP being enabled by RRC / DCI, multiple TCI state / spatial relationships being enabled by RRC / DCI, and at least one of single-DCI-based multi-TRP and multi-DCI-based multi-TRP may be interpreted as mutually exclusive. In this disclosure, multi-DCI-based multi-TRP and setting a CORESET pool index value of 1 for a CORESET may be interpreted as mutually exclusive. In this disclosure, single-DCI-based multi-TRP and mapping at least one code point of a TCI field to two TCI states may be interpreted as mutually exclusive.

[0115] In this disclosure, the following can be interpreted interchangeably: single TRP, single DCI, single PDCCH, multi-TRP based on single DCI, single TRP system, single TRP transmission, single PDSCH, channel using single TRP, channel using one TCI state / spatial relationship, multi-TRP not being activated by RRC / DCI, multiple TCI state / spatial relationships not being activated by RRC / DCI, no CORESET pool index value of 1 is set for any CORESET, and no code point in the TCI field is mapped to two TCI states, and two TCI states are activated on at least one TCI code point.

[0116] In this disclosure, "switch," "decide," and "select" may be interpreted as interchangeable.

[0117] In this disclosure, panels, TRPs, SRS resource sets, and CORESET pool indexes may be interpreted interchangeably. In this disclosure, the first / second SRS resource set may refer to an SRS resource set with a lower / higher index (or ID).

[0118] In the following embodiments, we will describe the case where two SRS resource sets are configured as an example, but the number of configurable SRS resource sets is not limited to two, and may be three or more. In the following description, two SRS resource sets may be read as X SRS resource sets (for example, X is 2 or more).

[0119] (Wireless communication method) <First Embodiment> In the first embodiment, an example of a method for determining / controlling a predetermined field included in DCI (e.g., an SRI field for CB) will be described.

[0120] The first embodiment may be suitably applied to cases where different numbers of SRS resources are configured for two SRS resource sets associated with two CORESET pool indexes in a multi-DCI based UL simultaneous transmission (e.g., M-DCI STxMP PUSCH+PUSCH). The SRS resource sets may be SRS resource sets for codebooks (CB SRS resource sets).

[0121] For example, this may apply to a case where the number of SRS resources is set separately (e.g., different numbers of SRS resources) for a first SRS resource set associated with a first CORESET pool index and a second SRS resource set associated with a second CORESET pool index. Of course, the first embodiment may also apply to cases other than those described above.

[0122] For the SRI field included in DCI, at least one of the following options 1-1 to 1-2 may be applied.

[0123] [Option 1-1] The size of the SRI field may be determined based on the CORESET from which the DCI is monitored. For example, the size of the SRI field included in a DCI may be determined based on the number of SRS resources in the SRS resource set associated with the CORESER pool index of the CORESET from which the DCI is monitored.

[0124] For example, the UE may determine the size of the SRI field included in the first DCI based on the number of SRS resources included in the first SRS resource set associated with the CORESER pool index (e.g., #x) of the CORESET that monitors the first DCI (see Figure 7A). Alternatively, the UE may determine the size of the SRI field included in the second DCI based on the number of SRS resources included in the second SRS resource set associated with the CORESER pool index (e.g., #y) of the CORESET that monitors the second DCI.

[0125] This example illustrates a case where the size of the SRI field in the first DCI (or the number of SRS resources included in the first SRS resource set) differs from the size of the SRI field in the second DCI (or the number of SRS resources included in the second SRS resource set).

[0126] This allows for the appropriate determination of the size of the SRI field included in each DCI, even when the number of SRS resources is set separately for each SRS resource set.

[0127] DCI size alignment may be performed between the DCI corresponding to the first CORESER pool index #x and the DCI corresponding to the second CORESER pool index #y. In this case, the DCI sizes may be aligned by assuming that the size of one DCI (e.g., the DCI corresponding to the first CORESER pool index #x) is smaller than the size of the other DCI (e.g., the DCI corresponding to the second CORESER pool index #y).

[0128] For example, zeros (e.g., padding bits) may be added to one DCI (e.g., the DCI corresponding to the first CORESER pool index #x) until its size is equal to the size of the other DCI (e.g., the DCI corresponding to the second CORESER pool index #y) (see Figure 7B).

[0129] The cases may be x=0 and y=1, or x=1 and y=0.

[0130] [Options 1-2] The size of the SRI field may be determined independently of (or regardless of) the CORESET from which the DCI is monitored. For example, the size of the SRI field included in the DCI may be determined based on the maximum of a first size #x and a second size #y (or the larger of the first size #x and the second size #y is applied).

[0131] The first size #x may be the size of the valid bits in the SRI field, which is determined based on the number of SRS resources in the SRS resource set associated with the first CORESET pool index #x. The second size #y may be the size of the valid bits in the SRI field, which is determined based on the number of SRS resources in the SRS resource set associated with the second CORESET pool index #y.

[0132] Let's consider the case where the first size #x is smaller than the second size #y (for example, the number of SRS resources in the SRS resource set associated with the first CORESET pool index #x is less than the number of SRS resources in the SRS resource set associated with the second CORESET pool index #y).

[0133] In this case, when interpreting the SRI field of the first DCI of the first CORESET pool index #x, only the most significant bit (e.g., MSB) of the first size #x may be valid or used (see Figure 8A). Alternatively, when interpreting the SRI field of the first DCI of the first CORESET pool index #x, only the least significant bit (e.g., LSB) of the first size #x may be valid or used (see Figure 8B). Similarly, the SRI field of the second DCI associated with the second CORESET pool index #y may be interpreted in the case where the second size #y is smaller than the first size #x.

[0134] The UE may ignore invalid / unused bits. Alternatively, invalid / unused bits may be set to a predetermined value (e.g., all 0 or all 1). The UE may assume / expect / determine that invalid / unused bits are set to a predetermined value (e.g., all 0 or all 1).

[0135] In this way, by determining and controlling which bits of the SRI field are active / used based on the number of corresponding SRS resources, the size of the SRI fields of the first DCI and the second DCI can be set to be the same, even if the number of SRS resources is set separately for each SRS resource set. This eliminates the need for size alignment (e.g., adding padding bits) caused by differences in SRI field size.

[0136] <Second Embodiment> In the second embodiment, an example of a method for determining / controlling a predetermined field included in DCI (e.g., an SRI field for NCB) is described.

[0137] The second embodiment may be suitably applied to cases where different numbers of SRS resources / maximum ranks are set for two SRS resource sets associated with two CORESET pool indexes in a multi-DCI based UL simultaneous transmission (e.g., M-DCI STxMP PUSCH+PUSCH). The SRS resource sets may be SRS resource sets for non-code books (NCB SRS resource sets).

[0138] For example, this may apply to a case where the number of SRS resources / maximum rank are set separately (e.g., different number of SRS resources / different maximum ranks) for a first SRS resource set associated with a first CORESET pool index and a second SRS resource set associated with a second CORESET pool index. Of course, the second embodiment may apply to cases other than those described above.

[0139] For the SRI field included in DCI, at least one of the following options 2-1 to 2-2 may be applied.

[0140] [Option 2-1] The size of the SRI field may be determined based on the CORESET from which the DCI is monitored. For example, the size of the SRI field included in the DCI may be determined based on at least one of the number of SRS resources and the maximum rank associated with the CORESER pool index of the CORESET from which the DCI is monitored.

[0141] For example, the UE may determine the size of the SRI field included in the first DCI based on at least one of the following: the number of SRS resources included in the first SRS resource set, associated with the CORESER pool index (e.g., #x) of the CORESET monitoring the first DCI, and the maximum rank (see Figure 9A). The UE may also determine the size of the SRI field included in the second DCI based on at least one of the following: the number of SRS resources included in the second SRS resource set, associated with the CORESER pool index (e.g., #y) of the CORESET monitoring the second DCI, and the maximum rank.

[0142] This example illustrates a case where the size of the SRI field in the first DCI (or the number of first SRS resources included in the first SRS resource set / the first maximum rank) differs from the size of the SRI field in the second DCI (or the number of second SRS resources included in the second SRS resource set / the second maximum rank).

[0143] This allows for the proper determination of the size of the SRI field included in each DCI, even when the number of SRS resources and the maximum rank are set separately for each SRS resource set in the CORESER pool index.

[0144] DCI size alignment may be performed between the DCI corresponding to the first CORESER pool index #x and the DCI corresponding to the second CORESER pool index #y. In this case, the DCI sizes may be aligned by assuming that the size of one DCI (e.g., the DCI corresponding to the first CORESER pool index #x) is smaller than the size of the other DCI (e.g., the DCI corresponding to the second CORESER pool index #y).

[0145] For example, zeros (e.g., padding bits) may be added to one DCI (e.g., the DCI corresponding to the first CORESER pool index #x) until its size is equal to the size of the other DCI (e.g., the DCI corresponding to the second CORESER pool index #y) (see Figure 9B).

[0146] The cases may be x=0 and y=1, or x=1 and y=0.

[0147] [Option 2-2] The size of the SRI field may be determined independently of (or regardless of) the CORESET from which the DCI is monitored. For example, the size of the SRI field included in the DCI may be determined based on the maximum of a first size #x and a second size #y (or the larger of the first size #x and the second size #y is applied).

[0148] The first size #x may be the size of the valid bits in the SRI field, which is determined based on at least one of the number of SRS resources and the maximum rank associated with the first CORESET pool index #x. The second size #y may be the size of the valid bits in the SRI field, which is determined based on at least one of the number of SRS resources and the maximum rank associated with the second CORESET pool index #y.

[0149] Let's consider the case where the first size #x is smaller than the second size #y (for example, the number of SRS resources / maximum rank associated with the first CORESET pool index #x is less than the number of SRS resources / maximum rank associated with the second CORESET pool index #y).

[0150] In this case, when interpreting the SRI field of the first DCI associated with the first CORESET pool index #x, only the most significant bit (e.g., MSB) of the first size #x may be valid or used (see Figure 10A). Alternatively, when interpreting the SRI field of the first DCI associated with the first CORESET pool index #x, only the least significant bit (e.g., LSB) of the first size #x may be valid or used (see Figure 10B). Similarly, the SRI field of the second DCI associated with the second CORESET pool index #y may be interpreted in the same way for the case where the second size #y is smaller than the first size #x.

[0151] The UE may ignore invalid / unused bits. Alternatively, invalid / unused bits may be set to a predetermined value (e.g., all 0 or all 1). The UE may assume / expect / determine that invalid / unused bits are set to a predetermined value (e.g., all 0 or all 1).

[0152] In this way, by determining and controlling which bits of the SRI field are active / used based on the corresponding number of SRS resources / maximum rank, the size of the SRI fields of the first DCI and the second DCI can be set to be the same, even if the number of SRS resources / maximum rank are set separately. This eliminates the need for size alignment (e.g., adding padding bits) due to differences in SRI field size.

[0153] <Third Embodiment> In the third embodiment, an example of a method for determining / controlling a predetermined field included in DCI (e.g., the TPMI field for CB) is described.

[0154] The third embodiment may be suitably applied to cases in multi-DCI based UL simultaneous transmission (e.g., M-DCI STxMP PUSCH+PUSCH) where two SRS resource sets associated with two CORESET pool indices are configured with different numbers or contents of antenna ports / SRS ports / codebook subsets / full power modes. The SRS resource sets may be SRS resource sets for codebooks (CB SRS resource sets). Numbers or contents may be interpreted as numbers or values.

[0155] For example, this may apply to a case where the number or content of antenna ports / SRS ports / codebook subsets / full power modes are set separately for a first SRS resource set associated with a first CORESET pool index and a second SRS resource set associated with a second CORESET pool index. Of course, the third embodiment may apply to cases other than those described above.

[0156] For the TPMI field included in DCI, at least one of the following options 3-1 to 3-2 may be applied.

[0157] [Option 3-1] The size of the TPMI field may be determined based on the CORESET from which the DCI is monitored. For example, the size of the TPMI field included in a DCI may be determined based on predetermined parameters associated with the CORESER pool index of the CORESET from which the DCI is monitored. These predetermined parameters may be, for example, the number or content of antenna ports / SRS ports / codebook subsets / full power modes.

[0158] For example, the UE may determine the size of the TPMI field included in the first DCI based on the number or content of antenna ports / SRS ports / codebook subsets / full power modes associated with the CORESER pool index (e.g., #x) of the CORESET monitoring the first DCI (see Figure 11A). The UE may also determine the size of the TPMI field included in the second DCI based on the number or content of antenna ports / SRS ports / codebook subsets / full power modes associated with the CORESER pool index (e.g., #y) of the CORESET monitoring the second DCI.

[0159] This example shows a case where the size of the TPMI field in the first DCI (or the antenna port / SRS port / codebook subset / full power mode corresponding to the first CORESET pool index #x or the first SRS resource set) differs from the size of the TPMI field in the second DCI (or the antenna port / SRS port / codebook subset / full power mode corresponding to the second CORESET pool index #y or the second SRS resource set).

[0160] This allows for the proper determination of the size of the TPMI field included in each DCI, even if the number or content of antenna ports / SRS ports / codebook subsets / full power modes are configured separately for each CORESET pool index / SRS resource set.

[0161] DCI size alignment may be performed between the DCI corresponding to the first CORESER pool index #x and the DCI corresponding to the second CORESER pool index #y. In this case, the DCI sizes may be aligned by assuming that the size of one DCI (e.g., the DCI corresponding to the first CORESER pool index #x) is smaller than the size of the other DCI (e.g., the DCI corresponding to the second CORESER pool index #y).

[0162] For example, zeros (e.g., padding bits) may be added to one DCI (e.g., the DCI corresponding to the first CORESER pool index #x) until its size is equal to the size of the other DCI (e.g., the DCI corresponding to the second CORESER pool index #y) (see Figure 11B).

[0163] The cases may be x=0 and y=1, or x=1 and y=0.

[0164] [Option 3-2] The size of the TPMI field may be determined independently of (or regardless of) the CORESET from which the DCI is monitored. For example, the size of the TPMI field included in the DCI may be determined based on the maximum of a first size #x and a second size #y (or the larger of the first size #x and the second size #y is applied).

[0165] The first size #x may be the size of the valid bits in the TPMI field, determined based on a predetermined parameter associated with the first CORESET pool index #x (e.g., the number or content of antenna ports / SRS ports / codebook subsets / full power modes). The second size #y may be the size of the valid bits in the TPMI field, determined based on a predetermined parameter associated with the second CORESET pool index #y (e.g., the number or content of antenna ports / SRS ports / codebook subsets / full power modes).

[0166] Consider the case where the first size #x is smaller than the second size #y. In this case, when interpreting the TPMI field of the first DCI for the first CORESET pool index #x, only the most significant bit (e.g., MSB) of the first size #x may be valid or used (see Figure 12A). Alternatively, when interpreting the TPMI field of the first DCI for the first CORESET pool index #x, only the least significant bit (e.g., LSB) of the first size #x may be valid or used (see Figure 12B). The same interpretation may apply to the case where the second size #y is smaller than the first size #x, where the TPMI field of the second DCI associated with the second CORESET pool index #y may be interpreted in the same way.

[0167] The UE may ignore invalid / unused bits. Alternatively, invalid / unused bits may be set to a predetermined value (e.g., all 0 or all 1). The UE may assume / expect / determine that invalid / unused bits are set to a predetermined value (e.g., all 0 or all 1).

[0168] In this way, by determining and controlling which bits of the TPMI field are active / used based on the number or content of the corresponding antenna ports / SRS ports / codebook subsets / full power modes, the TPMI field sizes of the first DCI and the second DCI can be set to be the same, even if the number or content of the antenna ports / SRS ports / codebook subsets / full power modes are set separately. This eliminates the need for size alignment (e.g., adding padding bits) due to differences in TPMI field sizes.

[0169] <Fourth Embodiment> In the fourth embodiment, an example of a method for determining / controlling predetermined fields (e.g., SRI field / TPMI field) included in DCI when dynamic switching between a first transmission mode (e.g., single TRP / single panel transmission) and a second transmission mode (e.g., simultaneous transmission using multiple panels (e.g., STxMP)) is supported is described.

[0170] In simultaneous multi-panel transmission of a pusher in a single DCI-based multi-TRP system, a spatial division multiplexing scheme (SDM scheme) may be applied (STxMP SDM Tx). For example, different layer / DMRS ports of a single pusher may be precoded separately and transmitted simultaneously from different UE panels.

[0171] Dynamic switching between a first transmission mode (e.g., single panel) and a second transmission mode (e.g., simultaneous transmission using a spatial division multiplexing scheme with multiple panels (e.g., STxMP SDM)) may be supported. The term "transmission mode" may be interpreted as "transmission mode," "transmission type," "transmission method," or "transmission technique."

[0172] In this case, different numbers or types of SRS resources / antenna ports / maximum rank / codebook subset / full power modes may be set for single TRP transmissions using TRP#1 (e.g., sTRP Tx with TRP#1), single TRP transmissions using TRP#2 (e.g., sTRP Tx with TRP#2), simultaneous multi-panel transmissions using spatial multiplexing with TRP#1 (e.g., STxMP SDM Tx with TRP#1), and simultaneous multi-panel transmissions using spatial multiplexing with TRP#2 (e.g., STxMP SDM Tx with TRP#2).

[0173] Alternatively, different numbers or types of SRS resources / antenna ports / maximum rank / codebook subset / full power modes may be configured for single TRP transmission associated with a predetermined SRS resource set / spatial multiplexing simultaneous multi-panel transmission associated with a predetermined SRS resource set.

[0174] A single TRP transmission associated with a predetermined SRS resource set may be, for example, a single TRP transmission associated with a first SRS resource set (e.g., sTRP Tx associated with first SRS resource set) or a single TRP transmission associated with a second SRS resource set (e.g., sTRP Tx associated with second SRS resource set).

[0175] A spatially multiplexed simultaneous multi-panel transmission associated with a predetermined SRS resource set may be, for example, a spatially multiplexed simultaneous multi-panel transmission associated with a first SRS resource set (e.g., STxMP SDM Tx associated with the first SRS resource set) or a spatially multiplexed simultaneous multi-panel transmission associated with a second SRS resource set (e.g., STxMP SDM Tx associated with the second SRS resource set).

[0176] Thus, if different parameter settings (e.g., number of SRS resources / number of antenna ports / maximum rank / codebook subset / full power mode) are supported for single TRP / single panel transmission and simultaneous transmission using multiple panels, the bit size in a given field (e.g., size of valid bits) may also be set separately. For example, the size of valid bits in a given field (e.g., SRI field / TPMI field) may differ when single TRP transmission associated with a first SRS resource set / single TRP transmission associated with a second SRS resource set / simultaneous multi-panel transmission using spatial multiplexing is indicated.

[0177] The size of the valid bits in a given field of the DCI (e.g., SRI field / TPMI field) may be determined based on the transmission mode (e.g., single-panel transmission / simultaneous multi-panel transmission) / SRS resource set and a given parameter corresponding to that transmission mode / SRS resource set. The given parameter may be, for example, the number of SRS resources / number of antenna ports / maximum rank / codebook subset / full power mode. The transmission mode (e.g., single-panel transmission / simultaneous multi-panel transmission) may be interpreted as the transmission mode corresponding to a given SRS resource set (e.g., first SRS resource set / second SRS resource set).

[0178] For example, the size of the valid bits in a predetermined field may be determined based on whether a single TRP transmission associated with a first SRS resource set / a single TRP transmission associated with a second SRS resource set / a simultaneous multi-panel transmission using spatial multiplexing is instructed (or which transmission mode is instructed / which SRS resource set is instructed). Furthermore, the size of the valid bits in the SRI field / TPMI field may be determined based on predetermined parameters set for a single TRP transmission associated with a first SRS resource set / a single TRP transmission associated with a second SRS resource set / a simultaneous multi-panel transmission using spatial multiplexing associated with a first SRS resource set / a simultaneous multi-panel transmission using spatial multiplexing associated with a third SRS resource set (or predetermined parameters corresponding to each SRS resource set).

[0179] Information regarding the applicable transmission mode / corresponding SRS resource set may be instructed / configured to the UE using DCI / MAC CE / RRC.

[0180] The size N of a given field included in the DCI (for example, at least one of the TPMI field / SRI field) may be determined based on the maximum value of the size #x of the first significant bit, the size #y of the second significant bit, and the size #z of the third significant bit (or the larger of the size #x of the first significant bit, the size #y of the second significant bit, and the size #z of the third significant bit is applied).

[0181] The size #x of the first valid bit may correspond to the size of the valid bits in a predetermined field when a single TRP transmission associated with the first SRS resource set is instructed. The size #y of the second valid bit may correspond to the size of the valid bits in a predetermined field when a single TRP transmission associated with the second SRS resource set is instructed. The size #z of the third valid bit may correspond to the size of the valid bits in a predetermined field when a simultaneous multi-panel transmission using spatial multiplexing is instructed. The size N of the predetermined field may be set to the largest of sizes #x, #y, and #z.

[0182] A single TRP associated with a first SRS resource set, a single TRP associated with a second SRS resource set, or simultaneous multi-panel transmission in spatial multiplexing is instructed, and cases may occur where size #x, size #y, or size #z is less than N. In this case, only the most significant bit (MSB) or least significant bit (LSB) of a given field (e.g., for size #x, size #y, or size #z) may be valid or utilized.

[0183] For example, the UE may assume / determine that the size of the valid bits in a given field is size #x when a single TRP transmission associated with a first SRS resource set is configured / instructed. Alternatively, the UE may assume / determine that the size of the valid bits in a given field is size #y when a single TRP transmission associated with a second SRS resource set is configured / instructed. Alternatively, the UE may assume / determine that the size of the valid bits in a given field is size #z when a simultaneous multi-panel transmission using spatial multiplexing is configured / instructed.

[0184] The UE may ignore invalid / unused bits. Alternatively, invalid / unused bits may be set to a predetermined value (e.g., all 0 or all 1). The UE may assume / expect / determine that invalid / unused bits are set to a predetermined value (e.g., all 0 or all 1).

[0185] For example, consider the case where size #x > size #y ≥ size #z. In this case, the size N of a given field may be set to be equal to size #x. When the UE is instructed by DCI / MAC CE to perform a single TRP transmission associated with the first SRS resource set, only the most significant bit (e.g., MSB) of size #x for a given field (e.g., TPMI field / SRI field) may be valid or used (see Figure 13).

[0186] Furthermore, if the UE is instructed by DCI / MAC CE to perform a single TRP transmission associated with a second SRS resource set, only the most significant bit (e.g., MSB) of size #y for a given field (e.g., TPMI field / SRI field) may be enabled or used. Also, if the UE is instructed by DCI / MAC CE to perform a spatially multiplexed simultaneous multi-panel transmission (e.g., STxMP SDM Tx), only the most significant bit (e.g., MSB) of size #z for a given field (e.g., TPMI field / SRI field) may be enabled or used.

[0187] Alternatively, if the UE is instructed by DCI / MAC CE to perform a single TRP transmission associated with a first SRS resource set, only the least significant bit (e.g., LSB) of a given field (e.g., TPMI field / SRI field) of size #x may be valid or used (see Figure 14).

[0188] Furthermore, if the UE is instructed by DCI / MAC CE to perform a single TRP transmission associated with a second SRS resource set, only the least significant bit (e.g., LSB) of size #y for a given field (e.g., TPMI field / SRI field) may be valid or used. Also, if the UE is instructed by DCI / MAC CE to perform a spatially multiplexed simultaneous multi-panel transmission (e.g., STxMP SDM Tx), only the least significant bit (e.g., LSB) of size #z for a given field (e.g., TPMI field / SRI field) may be valid or used.

[0189] Simultaneous multi-panel transmission using spatial multiplexing (e.g., STxMP SDM Tx) may be distinguished into STxMP SDM transmission in the order TRP#1-TRP#2 and STxMP SDM transmission in the order TRP#2-TRP#1.

[0190] A TRP#1-TRP#2 sequence of STxMP SDM transmission may mean that the first L1 layer / DMRS port is associated with the first SRS resource set, and the remaining layer / DMRS ports are associated with the second SRS resource set. A TRP#2-TRP#1 sequence of STxMP SDM transmission may mean that the first L1 layer / DMRS port is associated with the second SRS resource set, and the remaining layer / DMRS ports are associated with the first SRS resource set.

[0191] Furthermore, when different SRS resource sets are associated with simultaneous multi-panel transmissions using spatial multiplexing (e.g., STxMP SDM Tx), the size of the effective bits #z1 corresponding to the simultaneous multi-panel transmission associated with the first SRS resource set and the size of the effective bits #z2 corresponding to the simultaneous multi-panel transmission associated with the second SRS resource set may be supported.

[0192] The transmit type instruction / SRS resource set instruction may be instructed from the base station to the UE by the DCI / MAC CE. For example, a single TRP transmit associated with a first SRS resource set (e.g., sTRP TX associated with first SRS resource set) may be instructed by the SRS resource set instruction field in the DCI (e.g., '00'). A single TRP transmit associated with a second SRS resource set (e.g., sTRP TX associated with second SRS resource set) may be instructed by the SRS resource set instruction field in the DCI (e.g., '01').

[0193] Simultaneous multi-panel transmissions using spatial multiplexing (e.g., STxMP SDM Tx) may be indicated by the DCI's SRS resource set instruction field (e.g., '10' or '11'). If STxMP SDM Tx is distinguished into STxMP SDM transmissions in the TRP#1-TRP#2 order and STxMP SDM transmissions in the TRP#2-TRP#1 order, either one may be indicated by the DCI. For example, an STxMP SDM transmission in the TRP#1-TRP#2 order (e.g., STxMP SDM Tx with TRP#1-TRP#2 order) may be indicated by the DCI's SRS resource set instruction field (e.g., '10'). An STxMP SDM transmission in the TRP#2-TRP#1 order (e.g., STxMP SDM Tx with TRP#2-TRP#1 order) may be indicated by the DCI's SRS resource set instruction field (e.g., '11').

[0194] The fourth embodiment may apply not only when dynamic switching is supported between single DCI-based spatial division multiplexing UL simultaneous transmission (e.g., STxMP SDM) and single panel (e.g., single panel). For example, it may apply when dynamic switching is supported between multi-DCI-based spatial division multiplexing UL simultaneous transmission (e.g., STxMP SDM) and single panel (e.g., single panel). When multi-DCI-based spatial division multiplexing UL simultaneous transmission is instructed / configured, this may be interpreted as when multiple (e.g., two) SRS resource sets / CORESET pool indexes are configured. When a single TRP is configured, this may be interpreted as when one SRS resource set / CORESET pool index is configured.

[0195] <Fifth Embodiment> In the fifth embodiment, an example of a method for controlling UL transmission (e.g., PUSCH transmission) when switching of the bandwidth portion (e.g., BWP) is performed will be described.

[0196] The fifth embodiment may be preferably applied when, in BWP switching, the application of different transmission modes (single TRP transmission / single panel transmission and simultaneous multi-panel transmission using multiple panels (STxMP)) is supported in the BWP before and after the switch. Of course, the application of the fifth embodiment is not limited to this.

[0197] For multi-DCI-based simultaneous UL transmissions (e.g., PUSCH+PUSCH), a PUSCH may be associated with a predetermined SRS resource set. This predetermined SRS resource set may be an SRS resource set associated with the CORESET pool index of the DCI that schedules the PUSCH.

[0198] If BWP switching is supported, there may be cases where the bandwidth part indicator field of the DCI received in BWP#a points to another BWP#b. In this case, if two SRS resource set / CORESET pool indices are set in the pointed-to BWP#b, the question arises as to which SRS resource set the PUSCH (e.g., the PUSCH scheduled in that DCI) is associated.

[0199] In the fifth embodiment, when a BWP switch occurs, PUSCH may determine the corresponding SRS resource set / CORESET pool index based on predetermined rules.

[0200] Case 5-1 Regarding BWP switching, if a different BWP#b is indicated by the DCI bandwidth portion indication field detected in BWP#a, and multi-DCI based simultaneous transmission (e.g., M-DCI STxMP PUSCH+PUSCH) is configured in the indicated BWP#b, then at least one of the following options 5-1 to 5-2 may be applied. Note that if multi-DCI based simultaneous transmission (e.g., M-DCI STxMP PUSCH+PUSCH) is configured in the indicated BWP#b, this can be interpreted as two SRS resource sets / CORESET pool indices being configured in the indicated BWP#b.

[0201] [Option 5-1] If a single TRP is configured in BWP#a (or the BWP where DCI is detected) (see Figure 15A), at least one of the following options 5-1-1 to 5-1-2 may be applied. Note that "a single TRP is configured in BWP#a (or the BWP where DCI is detected)" may be interpreted as "one SRS resource set / CORESET pool index is configured in BWP#a (or the BWP where DCI is detected)."

[0202] 《Option 5-1-1》 A scheduled PUSCH may be associated with a specific SRS resource set in BWP#b. This PUSCH may be scheduled by a DCI (or a DCI detected in BWP#a) that signals a BWP switch. The specific SRS resource set may be the first SRS resource set or an SRS resource set with a lower index. For example, the UE may assume / determine that the scheduled PUSCH is associated with the first SRS resource set in BWP#b.

[0203] By default, the UE may assume / determine that a scheduled PUSCH is associated with a specific SRS resource set in BWP#b (e.g., the first SRS resource set). However, if other instructions / conditions exist, the SRS resource set corresponding to the PUSCH may be determined based on those instructions / conditions.

[0204] 《Option 5-1-2》 When BWP switching is applied, information regarding the SRS resource set associated with the scheduled PUSCH may be set by higher-layer parameters, etc.

[0205] [Option 5-2] If multi-DCI-based simultaneous transmission (e.g., M-DCI STxMP PUSCH+PUSCH) is configured in BWP#a (or the BWP in which DCI is detected) (see Figure 15B), then at least one of the following options 5-2-1 to 5-2-3 may be applied. Note that "multi-DCI-based simultaneous transmission (e.g., M-DCI STxMP PUSCH+PUSCH) is configured in BWP#a (or the BWP in which DCI is detected)" may be interpreted as "two SRS resource sets / CORESET pool indexes are configured in BWP#a (or the BWP in which DCI is detected)."

[0206] 《Option 5-2-1》 A scheduled PUSCH may be associated with a specific SRS resource set in BWP#b. This specific SRS resource set may be the first SRS resource set or an SRS resource set with a smaller index. For example, the UE may assume / determine that a scheduled PUSCH is associated with the first SRS resource set in BWP#b.

[0207] By default, the UE may assume / determine that a scheduled PUSCH is associated with a specific SRS resource set in BWP#b (e.g., the first SRS resource set). However, if other instructions / conditions exist, the SRS resource set corresponding to the PUSCH may be determined based on those instructions / conditions.

[0208] 《Option 5-2-2》 A scheduled PUSCH may be associated with an SRS resource set that is associated with a CORESET pool index corresponding to the DCI that schedules the PUSCH. The association between the SRS resource set and the CORESET pool index may be determined based on predetermined rules.

[0209] For example, the association between an SRS resource set and a CORESET pool index may follow the settings of the specified BWP#b (Rule 1). Alternatively, the association between an SRS resource set and a CORESET pool index may follow the settings of BWP#a (or the BWP where DCI was detected) (Rule 2). Alternatively, the association between an SRS resource set and a CORESET pool index in BWP#a and BWP#b may be set to be the same (Rule 3). In Rule 3, the UE may expect / assume / determine that the association between an SRS resource set and a CORESET pool index in BWP#a and BWP#b is set to be the same.

[0210] 《Option 5-2-3》 When BWP switching is applied, information regarding the SRS resource set associated with the scheduled PUSCH may be set by higher-layer parameters, etc.

[0211] [Variations] If the bandwidth portion indication field of the DCI detected in BWP#a points to BWP#b, the SRS resource set / CORESET pool index may be set to the same value between BWP#a and BWP#b. The UE may determine the SRI field by expecting / assuming / judging that the SRS resource set / CORESET pool index is set to the same value between BWP#a and BWP#b, if the bandwidth portion indication field of the DCI detected in BWP#a points to BWP#b.

[0212] Case 5-2 Regarding BWP switching, if the bandwidth portion indication field of the DCI detected in BWP#a indicates a different BWP#b from BWP#a, and a single TRP is set in the indicated BWP#b, then at least one of the following options 5-3 to 5-4 may be applied. Note that "a single TRP is set in BWP#b" may be interpreted as "one SRS resource set / CORESET pool index is set in BWP#b."

[0213] [Option 5-3] If a single TRP is configured in BWP#a (or the BWP where DCI is detected) (see Figure 16A), the same behavior as in existing systems (e.g., Rel. 17 and earlier) may apply. Note that "a single TRP is configured in BWP#a (or the BWP where DCI is detected)" may be interpreted as "one SRS resource set / CORESET pool index is configured in BWP#a (or the BWP where DCI is detected)."

[0214] [Option 5-4] If multi-DCI-based simultaneous transmission (e.g., M-DCI STxMP PUSCH+PUSCH) is configured in BWP#a (or the BWP in which DCI is detected) (see Figure 16B), then at least one of the following options 5-4-1 to 5-4-2 may be applied. Note that "multi-DCI-based simultaneous transmission (e.g., M-DCI STxMP PUSCH+PUSCH) is configured in BWP#a (or the BWP in which DCI is detected)" may be interpreted as "two SRS resource sets / CORESET pool indexes are configured in BWP#a (or the BWP in which DCI is detected)."

[0215] 《Option 5-4-1》 A specific SRI field in BWP#a may indicate the SRS resource set in BWP#b. This specific SRI field may be the first SRI field or an SRI field with a smaller index. For example, the UE may assume / determine that the first SRI field in BWP#a indicates the SRS resource set in BWP#b.

[0216] The UE may, by default, assume / determine that the SRS resource set in BWP#b is indicated by the first SRI field in BWP#a. On the other hand, if there are other indications / conditions, the SRS resource set may be determined based on those indications / conditions.

[0217] 《Option 5-4-2》 When BWP switching is applied, information regarding the SRS resource set associated with the scheduled PUSCH may be set by higher-layer parameters, etc.

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

[0219] If the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new Logical Channel ID (LCID) not defined in existing standards in the MAC subheader.

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

[0221] Furthermore, the notification of any information to the UE in the above-described embodiment may be periodic, semi-persistent, or aperiodic.

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

[0223] If the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new LCID, not specified in existing standards, in the MAC subheader.

[0224] If the above notice is issued by the UCI, the notice may be sent using PUCCH or PUSCH.

[0225] Furthermore, the notification of any information from the UE in the above-described embodiments may be periodic, semi-persistent, or aperiodic.

[0226] [Regarding the application of each embodiment] At least one of the embodiments described above may be applied if certain conditions are met. These conditions may be specified in a standard or notified to the UE / BS using upper-layer signaling / physical layer signaling.

[0227] At least one of the embodiments described above may apply only to a UE that has reported or supports a particular UE capability.

[0228] The specific UE capability may represent at least one of the following: • Support for specific processing / operation / control / information (e.g., simultaneous multi-panel transmission using multiple panels (STxMP)) for at least one of the above embodiments. • Supports multi-DCI based STxMP, • Support for separately setting the size of a given field (e.g., SRI field / TPMI field) in a multi-DCI based STxMP. • Supports simultaneous multi-panel spatial multiplexing (STxMP SDM). • Supports switching between single TRP transmission / single panel transmission and simultaneous multi-panel transmission (STxMP) using multiple panels. • Support for applying different transmission modes (single TRP transmission / single panel transmission and simultaneous multi-panel transmission using multiple panels (STxMP)) during BWP switching.

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

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

[0231] Furthermore, at least one of the embodiments described above may be applied when the UE is configured / activated / triggered by upper layer signaling / physical layer signaling to perform certain information (or the actions of the embodiments described above) related to the embodiments described above. For example, such certain information may be information indicating the activation of simultaneous multi-panel transmission (STxMP) using multiple panels, or arbitrary RRC parameters for a particular release (e.g., Rel.18 / 19).

[0232] If the UE does not support at least one of the above-mentioned specific UE capabilities or does not have the above-mentioned specific information configured, the behavior of, for example, Rel.15 / 16 may be applied.

[0233] (Note) The following invention is added with respect to one embodiment of this disclosure. [Note 1-1] A terminal comprising: a receiving unit that receives at least one of a first downlink control information (DCI) and a second DCI associated with two control resource set pool indices, respectively; and a control unit that, when different parameter settings are supported for two sounding reference signal (SRS) resource sets associated with the two control resource set pool indices, determines the size of predetermined fields of the first DCI and the second DCI based on parameters corresponding to one control resource set pool indices or parameters corresponding to two control resource set pool indices, respectively. [Appendix 1-2] The terminal described in Appendix 1-1 determines the size of a predetermined field of the first DCI based on a first parameter corresponding to an SRS resource set associated with a control resource set pool index of a control resource set that monitors the first DCI. [Appendix 1-3] The terminal described in Appendix 1-1 or Appendix 1-2 determines the size of a predetermined field of the first DCI based on a first parameter corresponding to an SRS resource set associated with the control resource set pool index of a control resource set that monitors the first DCI, and a second parameter corresponding to an SRS resource set associated with the control resource set pool index of a control resource set that monitors the second DCI. [Appendix 1-4] The terminal according to any one of the appendices 1-1 to 1-3, wherein the control unit determines that the size of a predetermined field of the first DCI is the same as the size of the second effective bit if the size of a first effective bit determined based on a first parameter corresponding to an SRS resource set associated with the control resource set pool index of a control resource set that monitors the first DCI is smaller than the size of a second effective bit determined based on a second parameter corresponding to an SRS resource set associated with the control resource set pool index of a control resource set that monitors the second DCI.

[0234] [Note 2-1] A terminal having, when the application or switching between a first transmission mode and a second transmission mode is supported, a receiving unit that receives information about the transmission mode, and a control unit that determines the size of the effective bits for each transmission mode in a predetermined field of downlink control information (DCI) that schedules UL transmission, based on parameters corresponding to a sounding reference signal (SRS) resource set associated with the transmission mode. [Note 2-2] The terminal as described in Appendix 2-1, wherein the control unit determines that the largest size among the sizes of the effective bits of each transmission mode is the size of the predetermined field. [Appendix 2-3] The terminal described in Appendix 2-1 or Appendix 2-2 controls the UL transmission based on the interpretation of some bits in the predetermined field that correspond to the effective bits when the size of the effective bits in a certain transmission mode is smaller than the size of the predetermined field. [Appendix 2-4] The information regarding the aforementioned transmission method is provided to the terminal specified in any of the appendices 2-1 to 2-3, as instructed by the DCI that schedules the UL transmission.

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

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

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

[0238] In EN-DC, the LTE (E-UTRA) base station (eNB) is the Master Node (MN), and the NR base station (gNB) is the Secondary Node (SN). In NE-DC, the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN.

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

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

[0241] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of Carrier Aggregation (CA) using multiple Component Carriers (CC) and Dual Connectivity (DC).

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

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

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

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

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

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

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

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

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

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

[0252] The PDSCH is to transmit user data, upper layer control information, System Information Block (SIB), etc. The PUSCH may transmit user data, upper layer control information, etc. Also, the PBCH may transmit the Master Information Block (MIB).

[0253] The PDCCH may transmit lower layer control information. The lower layer control information may include, for example, downlink control information (Downlink Control Information (DCI)) including scheduling information for at least one of the PDSCH and the PUSCH.

[0254] Note that the DCI for scheduling the PDSCH may be called DL assignment, DL DCI, etc., and the DCI for scheduling the PUSCH may be called UL grant, UL DCI, etc. Note that the PDSCH may be read as DL data, and the PUSCH may be read as UL data.

[0255] For the detection of the PDCCH, a control resource set (COntrol REsource SET (CORESET)) and a search space may be used. The CORESET corresponds to the resource for searching for the DCI. The search space corresponds to the search area and search method for PDCCH candidates (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 setting.

[0256] 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 "search space", "search space set", "search space configuration", "search space set configuration", "CORESET", "CORESET configuration", etc. in the present disclosure may be read interchangeably with each other.

[0257] Uplink control information (UCI) including at least one of channel state information (CSI), delivery confirmation information (which may also be referred to as, for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR) may be transmitted by PUCCH. A random access preamble for connection establishment with a cell may be transmitted by PRACH.

[0258] Note that in the present disclosure, downlink, uplink, etc. may be expressed without adding "link". Also, the beginning of various channels may be expressed without adding "Physical".

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

[0260] The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS / PBCH block, SS Block (SSB), etc. SS, SSB, etc., may also be called reference signals.

[0261] Furthermore, in the wireless communication system 1, the Uplink Reference Signal (UL-RS) may transmit the Sounding Reference Signal (SRS), Demodulation Reference Signal (DMRS), etc. The DMRS may also be called the User-Specific Reference Signal (UE-specific Reference Signal).

[0262] (base station) Figure 18 shows an example of the configuration of a base station according to one 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 one or more of the control unit 110, transceiver unit 120, transceiver antenna 130, and transmission line interface 140 may be provided.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0276] The transmission / reception unit 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.

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

[0278] Note that the transmission unit and reception unit of the base station 10 in the present disclosure may be configured by at least one of the transmission / reception unit 120, the transmission / reception antenna 130, and the transmission path interface 140.

[0279] The transmitting / receiving unit 120 may transmit at least one of a first downlink control information (DCI) and a second DCI, each associated with two control resource set pool indices. The control unit 110 may control the size of predetermined fields of the first DCI and the second DCI based on the parameters corresponding to the SRS resource set associated with one control resource set pool index, or the parameters corresponding to the SRS resource sets associated with two control resource set pool indices, if different parameter settings are supported for the two sounding reference signal (SRS) resource sets associated with the two control resource set pool indices.

[0280] The transmitting / receiving unit 120 may transmit information about the transmission mode if the application or switching between the first and second transmission modes is supported. The control unit 110 may control the size of the valid bits for each transmission mode in a predetermined field of the downlink control information (DCI) that schedules the UL transmission, based on parameters corresponding to the sounding reference signal (SRS) resource set associated with the transmission mode.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0297] The measurement unit 223 may derive channel measurements for CSI calculation based on channel measurement resources. Channel measurement resources may be, for example, Non Zero Power (NZP) CSI-RS resources. The measurement unit 223 may also derive interference measurements for CSI calculation based on interference measurement resources. Interference measurement resources may be at least one of the following: an NZP CSI-RS resource for interference measurement, a CSI-Interference Measurement (IM) resource, etc. CSI-IM may also be called CSI-Interference Management (IM), and may be interpreted interchangeably with Zero Power (ZP) CSI-RS. In this disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc., may be interpreted interchangeably.

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

[0299] The transmitting / receiving unit 220 may receive at least one of a first downlink control information (DCI) and a second DCI associated with two control resource set pool indices, respectively. The control unit 210 may determine the size of predetermined fields of the first DCI and the second DCI based on the parameters corresponding to the SRS resource set associated with one control resource set pool index, or the parameters corresponding to the SRS resource sets associated with two control resource set pool indices, if different parameter settings are supported for two sounding reference signal (SRS) resource sets associated with two control resource set pool indices, respectively.

[0300] The control unit 210 may determine the size of a predetermined field of the first DCI based on a first parameter corresponding to an SRS resource set associated with the control resource set pool index of the control resource set that monitors the first DCI. Alternatively, the control unit 210 may determine the size of a predetermined field of the first DCI based on a first parameter corresponding to an SRS resource set associated with the control resource set pool index of the control resource set that monitors the first DCI, and a second parameter corresponding to an SRS resource set associated with the control resource set pool index of the control resource set that monitors the second DCI. Alternatively, the control unit 210 may determine that the size of a predetermined field of the first DCI is the same as the size of the second significant bit if the size of the first significant bit, determined based on a first parameter corresponding to an SRS resource set associated with the control resource set pool index of the control resource set monitoring the first DCI, is smaller than the size of the second significant bit, determined based on a second parameter corresponding to an SRS resource set associated with the control resource set pool index of the control resource set monitoring the second DCI.

[0301] The transmitting / receiving unit 220 may receive information regarding the transmission mode if the application or switching between the first and second transmission modes is supported. The control unit 210 may determine the size of the valid bits for each transmission mode in a predetermined field of the downlink control information (DCI) that schedules the UL transmission, based on parameters corresponding to the sounding reference signal (SRS) resource set associated with the transmission mode.

[0302] The control unit 210 may determine that the largest size of the valid bits for each transmission mode is equal to the size of a predetermined field. Alternatively, if the size of the valid bits for a given transmission mode is smaller than the size of a predetermined field, the control unit 210 may control the UL transmission based on the interpretation of some of the bits in the predetermined field that correspond to the valid bits. Information regarding the transmission mode may be indicated in the DCI that schedules the UL transmission.

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

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

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

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

[0307] For example, although only one processor 1001 is shown in the diagram, there may be multiple processors. Furthermore, processing may be performed by one processor, or by two or more processors simultaneously, sequentially, or by other means. Note that processor 1001 may be implemented using one or more chips.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0321] A slot may include multiple mini-slots. Each mini-slot may consist of one or more symbols in the time domain. Mini-slots may also be called sub-slots. Mini-slots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may be called a PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may be called a PDSCH (PUSCH) mapping type B.

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

[0323] For example, one subframe may be called TTI, multiple consecutive subframes may be called TTI, or one slot or one mini-slot may be called TTI. In other words, at least one of the subframe and TTI may be a subframe (1ms) in existing LTE, a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. Note that the unit representing TTI may be called a slot, mini-slot, etc., instead of a subframe.

[0324] Here, TTI refers to, for example, the smallest unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

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

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

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

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

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

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

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

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

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

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

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

[0336] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative examples. For instance, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots within a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0351] The above group may include, for example, at least one of the following: a spatial relationship group, a code division multiplexing (CDM) group, a reference signal (RS) group, a control resource set (CORESET) group, a PUCCH group, an antenna port group (e.g., a DMRS port group), a layer group, a resource group, a beam group, an antenna group, or a panel group.

[0352] Furthermore, in this disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, Codeword (CW), Transport Block (TB), RS, etc., may be interpreted as being interchangeable.

[0353] Furthermore, in this disclosure, TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, joint TCI state, etc., may be interpreted interchangeably.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0386] Furthermore, "judgment (decision)" may be considered as "judging (deciding)" something like resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment (decision)" may be considered as "judging (deciding)" something about an action. In this disclosure, "judgment (decision)" may be interpreted interchangeably with the actions described above.

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

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

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

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

[0391] In this disclosure, when two elements are connected, they can be considered to be “connected” or “coupled” to each other using one or more wires, cables, printed electrical connections, etc., and, in some non-exclusive and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, or optical domain (both visible and invisible).

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

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

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

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

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

[0397] In this disclosure, phrases such as "when A, B", "if A, then B", "B upon A", "B in response to A", "B based on A", "B during / while A", "B before A", "B at (the same time as) / on A", "B after A", "B since A", and "B until A" may be interchangeable. Furthermore, A, B, etc., may be replaced with appropriate expressions such as nouns, gerunds, or regular sentences depending on the context. The time difference between A and B may be approximately 0 (immediately after or immediately before). Additionally, a time offset may be applied to the time when A occurs. For example, "A" may be interpreted as "before / after the time offset when A occurs". The time offset (e.g., one or more symbols / slots) may be predetermined or determined by the UE based on the information provided.

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

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

Claims

1. When the application or switching between the first and second transmission modes is supported, a receiving unit receives information regarding the transmission mode, A terminal having a control unit that determines the size of the effective bits for each transmission mode in a predetermined field of downlink control information (DCI) that schedules UL transmission, based on parameters corresponding to a sounding reference signal (SRS) resource set associated with the aforementioned transmission mode.

2. The terminal according to claim 1, wherein the control unit determines that the largest size among the sizes of the effective bits of each transmission mode is the size of the predetermined field.

3. The terminal according to claim 1, wherein the control unit controls the UL transmission based on the interpretation of some bits in the predetermined field that correspond to the effective bits when the size of the effective bits of a certain transmission mode is smaller than the size of the predetermined field.

4. The terminal according to claim 1, wherein the information relating to the transmission method is instructed by the DCI that schedules the UL transmission.

5. If the application or switching between the first and second transmission modes is supported, the process includes receiving information regarding the transmission mode. A wireless communication method for a terminal, comprising the steps of determining the size of the effective bits for each transmission mode in a predetermined field of downlink control information (DCI) that schedules UL transmission, based on parameters corresponding to a sounding reference signal (SRS) resource set associated with the aforementioned transmission mode.

6. When the application or switching between the first and second transmission modes is supported, a transmission unit transmits information regarding the transmission mode. A base station having a control unit that controls the size of the effective bits for each transmission mode in a predetermined field of downlink control information (DCI) that schedules UL transmission, based on parameters corresponding to a sounding reference signal (SRS) resource set associated with the aforementioned transmission mode.

Images