Terminal, wireless communication method, base station and system

Abstract

A terminal according to one embodiment of the present disclosure comprises: a reception unit for receiving first configuration information relating to a physical uplink control channel (PUCCH), second configuration information relating to a physical uplink shared channel (PUSCH), and third configuration information relating to an uplink simultaneous transmission using a plurality of panels; and a control unit for controlling selection relating to the resources of the PUSCH and transmission of at least one of the PUSCH and the PUCCH on the basis of the first configuration information, the second configuration information, and the third configuration information. According to one embodiment of the present disclosure, it is possible to appropriately control UL transmissions, even when the UL transmissions are carried out using a plurality of panels.

Description

Terminal, wireless communication method and base station

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

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

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

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

[0005] In future wireless communication systems, a UE will be able to use one of multiple panels (or multiple beams) for uplink (UL) transmission. Furthermore, in Rel. 18 and beyond, support for simultaneous UL transmission (e.g., simultaneous multi-panel UL transmission (SiMPUL)) using multiple panels to one or more Transmission / Reception Points (TRPs) is being considered to improve UL throughput / reliability.

[0006] However, there has been insufficient consideration on how to control UL transmission using multiple panels (e.g., simultaneous UL transmission). If UL transmission using multiple panels is not performed appropriately, there is a risk of degradation of system performance, such as a decrease in throughput.

[0007] Therefore, one of the objectives of the present 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.

[0008] A terminal according to one aspect of the present disclosure includes a receiving unit that receives first setting information related to a physical uplink control channel (PUCCH), second setting information related to a physical uplink shared channel (PUSCH), and third setting information related to simultaneous uplink transmission using multiple panels, and a control unit that controls selection of resources for the PUSCH and transmission of at least one of the PUSCH and the PUCCH based on the first setting information, the second setting information, and the third setting information.

[0009] According to one aspect of the present disclosure, even when UL transmission is performed using multiple panels, UL transmission can be appropriately controlled.

[0010] FIG. 1 is a diagram showing an example of the association between precoder types and TPMI indexes. FIGS. 2A to 2C are diagrams showing an example of PUSCH transmission using multiple panels. FIGS. 3A and 3B are diagrams showing an example of UL transmission control based on priority. FIG. 4 is a diagram showing another example of UL transmission control based on priority. FIG. 5 is a diagram showing an example of a method for simultaneous transmission of PUSCH and PUCCH using multiple panels. FIG. 6 is a diagram showing an example of a PUSCH / PUCCH transmission method according to option 3-1. FIG. 7 is a diagram showing an example of a PUSCH / PUCCH transmission method according to option 3-2. FIG. 8 is a diagram showing an example of a PUSCH / PUCCH transmission method according to option 3-3. FIG. 9 is a diagram showing an example of a PUSCH / PUCCH transmission method according to option 4-1. FIG. 10 is a diagram showing an example of a PUSCH / PUCCH transmission method according to options 4-2, 4-3, and 4-4. Fig. 11 is a diagram showing an example of a PUSCH / PUCCH transmission method according to option 4-5. Fig. 12 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. Fig. 13 is a diagram showing an example of a configuration of a base station according to an embodiment. Fig. 14 is a diagram showing an example of a configuration of a user terminal according to an embodiment. Fig. 15 is a diagram showing an example of the hardware configuration of a base station and a user terminal according to an embodiment. Fig. 16 is a diagram showing an example of a vehicle according to an embodiment.

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

[0012] For example, it is being considered that the UE determines a precoder (precoding matrix) for CB-based and / or NCB-based Physical Uplink Shared Channel (PUSCH) transmission using at least a Sounding Reference Signal (SRS) resource indicator (SRI).

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

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

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

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

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

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

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

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

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

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

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

[0024] Fig. 1 is a diagram showing an example of association between precoder types and TPMI indexes. Fig. 1 corresponds to a table of precoding matrices W for single-layer (rank 1) transmission using four antenna ports in DFT-s-OFDM (Discrete Fourier Transform spread OFDM, transform precoding is effective).

[0025] In Fig. 1, when the precoder type (codebookSubset) is fully, partial, and noncoherent (fullyAndPartialAndNonCoherent), the UE is notified of a TPMI of any one of 0 to 27 for single layer transmission. Also, when the precoder type is partial and noncoherent (partialAndNonCoherent), the UE is configured with a TPMI of any one of 0 to 11 for single layer transmission. When the precoder type is noncoherent, the UE is configured with a TPMI of any one of 0 to 3 for single layer transmission.

[0026] As shown in Fig. 1, a precoding matrix in which only one element in each column is non-zero may be called a non-coherent codebook. A precoding matrix in which a predetermined number (not all) of elements in each column are non-zero 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] The non-coherent codebook and the partially coherent codebook may be referred to as an antenna selection precoder, and the fully coherent codebook may be referred to as a non-antenna selection precoder.

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

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

[0030] (Spatial Relationship for SRS, PUSCH) The UE may receive information (SRS configuration information, e.g., parameters in the RRC control element "SRS-Config") used for transmitting measurement reference signals (e.g., Sounding Reference Signals (SRS)).

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

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

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

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

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

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

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

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

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

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

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

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

[0043] BC may also be referred to as transmit / receive beam correspondence (Tx / Rx beam correspondence), beam reciprocity, beam calibration, calibrated / non-calibrated, reciprocity calibrated / non-calibrated, correspondence, agreement, etc.

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

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

[0046] When the UE is configured with spatial relationship information regarding the SRS and an SSB or CSI-RS for a certain SRS resource (e.g., with BC), the UE may transmit the SRS resource using the same spatial domain filter (spatial domain transmit filter) as the spatial domain filter for receiving the SSB or CSI-RS (spatial domain receive filter). In this case, the UE may assume that the UE receive beam for the SSB or CSI-RS and the UE transmit beam for the SRS are the same.

[0047] When the UE is configured with spatial relationship information between another SRS (reference SRS) and the target SRS for a certain SRS (target SRS) resource (e.g., without BC), the UE may transmit the target SRS resource using the same spatial domain filter (spatial domain transmit filter) as the spatial domain filter for transmitting the reference SRS. That is, 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.

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

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

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

[0051] (Multiple Panel Transmission) In Rel. 15 and Rel. 16 UEs, only one beam and panel are used for UL transmission at a time (Fig. 2A). In Rel. 17, simultaneous UL transmission of multiple beams and panels for one or more TRPs is being considered to improve UL throughput and reliability.

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

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

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

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

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

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

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

[0059] The QCL type indicated by the UL TCI status may be an existing QCL type A-D, or may be another QCL type, and may include a predetermined spatial relationship, associated antenna ports (port index), etc.

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

[0061] (Traffic Type) In future wireless communication systems (e.g., NR), traffic types (also referred to as services, service types, communication types, use cases, etc.) such as further advances in mobile broadband (e.g., enhanced Mobile Broadband (eMBB)), machine-type communications that realize multiple simultaneous connections (e.g., massive Machine Type Communications (mMTC), Internet of Things (IoT)), and highly reliable and low-latency communications (e.g., Ultra-Reliable and Low-Latency Communications (URLLC)) are expected. For example, URLLC requires smaller delays and higher reliability than eMBB.

[0062] At the physical layer, traffic types may be identified based on at least one of the following: logical channels with different priorities, a Modulation and Coding Scheme (MCS) table (MCS index table), a Channel Quality Indication (CQI) table, a DCI format, a Radio Network Temporary Identifier (RNTI) used to scramble (mask) the Cyclic Redundancy Check (CRC) bits included (added) in the DCI (DCI format), a Radio Resource Control (RRC) parameter, a specific RNTI (e.g., RNTI for URLLC, MCS-C-RNTI, etc.), a search space, and a predetermined field in the DCI (e.g., a newly added field or reuse of an existing field).

[0063] Specifically, the traffic type of HARQ-ACK for the PDSCH may be determined based on at least one of the following: - An MCS index table used to determine at least one of the modulation order, target code rate, and transport block size (TBS) of the PDSCH (e.g., whether or not to use MCS index table 3) - An RNTI used for CRC scrambling of DCI used for scheduling the PDSCH (e.g., whether CRC scrambling is performed using C-RNTI or MCS-C-RNTI)

[0064] The traffic type of the SR may also be determined based on a higher layer parameter used as the SR's identifier (SR-ID), which may indicate whether the traffic type of the SR is eMBB or URLLC.

[0065] Furthermore, the traffic type of the CSI may be determined based on configuration information (CSIreportSetting) related to CSI reporting, a DCI type used for triggering, or a DCI transmission parameter, etc. The configuration information, DCI type, etc. may indicate whether the traffic type of the CSI is eMBB or URLLC. The configuration information may also be an upper layer parameter.

[0066] Furthermore, the traffic type of the PUSCH may be determined based on at least one of the following: - An MCS index table used to determine at least one of the modulation order, target coding rate, and TBS of the PUSCH (for example, whether or not to use MCS index table 3) - An RNTI used for CRC scrambling of DCI used for scheduling the PUSCH (for example, whether CRC scrambling is performed using C-RNTI or MCS-C-RNTI)

[0067] The traffic type may be associated with communication requirements (requirements such as delay, error rate, etc.), data type (voice, data, etc.), and the like.

[0068] The difference between the requirements of URLLC and eMBB may be that the latency of URLLC is less than that of eMBB, or that the requirements of URLLC include reliability requirements.

[0069] For example, the user (U) plane latency requirement for eMBB may include a downlink U-plane latency of 4 ms and an uplink U-plane latency of 4 ms, while the U-plane latency requirement for URLLC may include a downlink U-plane latency of 0.5 ms and an uplink U-plane latency of 0.5 ms, and the reliability requirement for URLLC may include a 32-byte error rate of 10-5 at a U-plane latency of 1 ms.

[0070] Furthermore, enhanced Ultra Reliable and Low Latency Communications (eURLLC) is being studied to improve the reliability of traffic, mainly for unicast data. Hereinafter, when there is no need to distinguish between URLLC and eURLLC, they will simply be referred to as URLLC.

[0071] (Priority Setting) In NR Rel. 16 and later, it is being considered to set multiple levels (e.g., two levels) of priority for a given signal or channel. For example, it is expected that different priorities will be set for signals or channels corresponding to different traffic types (also referred to as services, service types, communication types, use cases, etc.) to control communications (e.g., transmission control in the event of a collision). This makes it possible to control communications by setting different priorities for the same signal or channel depending on the service type, etc.

[0072] Priority may be set for at least one of a signal (e.g., UCI such as HARQ-ACK, reference signal, etc.), a channel (PDSCH, PUSCH, PUCCH, etc.), a reference signal (e.g., channel state information (CSI), sounding reference signal (SRS), etc.), a scheduling request (SR), and a HARQ-ACK codebook. Priority may also be set for each of the PUCCH used to transmit an SR, the PUCCH used to transmit an HARQ-ACK, and the PUCCH used to transmit CSI.

[0073] The priority may be defined as a first priority (e.g., high) and a second priority (e.g., low) that is lower than the first priority. Alternatively, three or more types of priority may be set.

[0074] For example, priorities may be set for the HARQ-ACK for a dynamically scheduled PDSCH, the HARQ-ACK for a semi-persistent PDSCH (SPS PDSCH), and the HARQ-ACK for SPS PDSCH release. Alternatively, priorities may be set for the HARQ-ACK codebooks corresponding to these HARQ-ACKs. When setting a priority for a PDSCH, the priority of the PDSCH may be read as the priority of the HARQ-ACK for the PDSCH.

[0075] In addition, priorities may be set for dynamic grant-based PUSCH, configuration grant-based PUSCH, etc.

[0076] Priority information may be notified from the base station to the UE using at least one of higher layer signaling and DCI. For example, the priority of a scheduling request may be configured by a higher layer parameter (e.g., schedulingRequestPriority). The priority of a HARQ-ACK for a PDSCH (e.g., a dynamic PDSCH) scheduled by a DCI may be signaled by the DCI. The priority of a HARQ-ACK for an SPS PDSCH may be configured by a higher layer parameter (e.g., HARQ-ACK-Codebook-indicator-forSPS) or may be signaled by a DCI indicating activation of the SPS PDSCH. A predetermined priority (e.g., low) may be set for P-CSI / SP-CSI transmitted by the PUCCH. On the other hand, the priority of A-CSI / SP-CSI transmitted by the PUSCH may be signaled by a DCI (e.g., a trigger DCI or an activation DCI).

[0077] The priority of the dynamic grant-based PUSCH may be signaled in the DCI that schedules the PUSCH. The priority of the configured grant-based PUSCH may be configured by a higher layer parameter (e.g., priority). A predetermined priority (e.g., low) may be set for the P-SRS / SP-SRS and the A-SRS triggered by the DCI (e.g., DCI format 0_1 / DCI format 2_3).

[0078] (Priority for CSI Reporting) In Rel. 15 / 16 NR, a CSI report (which may also be referred to as a CSI report, CSI feedback, etc.) may be associated with a priority value. For example, the priority value may be expressed as a function Pri ｉＣＳＩ (y, k, c, s). The priority may be interchangeably read as CSI reporting priority, CSI priority, and the like.

[0079] For example, Pri ｉＣＳＩ (y, k, c, s) may be calculated using the following equation (1).

[0080] (Formula 1) PriｉＣＳＩ (y,k,c,s)=2・N ｃｅｌｌｓ ・M ｓ ・y+N ｃｅｌｌｓ ・M ｓ ・k+M ｓ ・c+s

[0081] Here, y may be a value based on the type of CSI report (A-CSI report, SP-CSI report, or P-CSI report) and the channel transmitting the CSI report (Physical Uplink Shared Channel (PUSCH) or Physical Uplink Control Channel (PUCCH)).

[0082] For example, y may be 0 for an A-CSI report transmitted via a PUSCH, y may be 1 for an SP-CSI report transmitted via a PUSCH, y may be 2 for an SP-CSI report transmitted via a PUCCH, and y may be 3 for a P-CSI report transmitted via a PUCCH.

[0083] k may be a value based on whether the CSI report includes L1-RSRP / SINR (e.g., k=0 if the CSI report includes L1-RSRP / SINR, and k=1 if not). c may be a serving cell index. s may be a report configuration ID (reportConfigID). Note that L1-RSRP / L1-SINR may be configured in different CSI reports.

[0084] Also, N ｃｅｌｌｓ is the value of the maximum number of serving cells to be configured (upper layer parameter maxNrofServingCells), M ｓ may be the value of the maximum number of configured CSI reporting configurations (higher layer parameter maxNrofCSI-ReportConfigurations).

[0085] Pri associated with the first CSI report ｉＣＳＩ The value of (y, k, c, s) is the Pri associated with the second CSI report. ｉＣＳＩ If it is less than the value of (y, k, c, s), it may mean that the first CSI report has a higher priority than the second CSI report.

[0086] According to Equation 1, for the same reporting amount in the same serving cell, the priority is given in the following order: A-CSI on PUSCH > SP-CSI on PUSCH > SP-CSI on PUCCH > P-CSI on PUCCH.

[0087] Two CSI reports may be said to collide if the time occupancy of two physical channels scheduled to carry them overlaps in at least one OFDM symbol and are transmitted on the same carrier.

[0088] Also, in Rel. 15 / 16 NR, if a UE is configured to transmit two conflicting CSI reports and the CSI report types are different (in other words, the above y values ​​of these CSI reports are different), the higher Pri ｉＣＳＩ The CSI report with (y, k, c, s) is not transmitted, and the lower Pri ｉＣＳＩ A CSI report having (y, k, c, s) may be transmitted.

[0089] In Rel. 15 / 16 NR, if a UE is configured to transmit two conflicting CSI reports, and the CSI report types are the same or different and both are CSI on PUCCH, both CSI reports are multiplexed or Pri ｉＣＳＩ One CSI report may be dropped based on (y, k, c, s).

[0090] (UL Transmission Overlap) The UE may control UL transmission based on priority when multiple UL signals / UL channels overlap (or collide).

[0091] The overlap of multiple UL signals / UL channels may refer to the case where the time resources (or the time resources and the frequency resources) of multiple UL signals / UL channels overlap, or the case where the transmission timings of multiple UL signals / UL channels overlap. The time resource may be interpreted as the time domain. The time resource may be in units of a symbol, a slot, a subslot, or a subframe.

[0092] Overlapping UL signals / UL channels at the same UE (e.g., intra-UE) may mean overlapping UL signals / UL channels at least in the same time resource (e.g., symbol), and colliding UL signals / UL channels at different UEs (e.g., inter-UE) may mean overlapping UL signals / UL channels in the same time resource (e.g., symbol) and frequency resource (e.g., RB).

[0093] For example, when multiple UL signals / UL channels with the same priority overlap, the UE controls the multiple UL signals / UL channels to be multiplexed into one UL channel for transmission (see FIG. 3A).

[0094] 3A shows a case where a HARQ-ACK (or a PUCCH for transmitting the HARQ-ACK) to which the first priority (high) is set overlaps with an UL data / UL-SCH (or a PUSCH for transmitting the UL data / UL-SCH) to which the first priority (high) is set. In this case, the UE multiplexes (or maps) the HARQ-ACK onto the PUSCH and transmits both the UL data and the HARQ-ACK.

[0095] When multiple UL signals / UL channels with different priorities overlap, the UE may control the UL transmission with higher priority (e.g., prioritize the UL transmission with higher priority) and not perform (e.g., drop) the UL transmission with lower priority (see Figure 3B).

[0096] 3B shows a case where UL data / HARQ-ACK (or UL channel for transmitting UL data / HARQ-ACK) set to a first priority (high) overlaps with UL data / HARQ-ACK (or UL channel for transmitting UL data / HARQ-ACK) set to a second priority (low). In this case, the UE drops the UL data / HARQ-ACK with a low priority and controls the transmission of the UL data / HARQ-ACK with a high priority. Note that the UE may change (e.g., postpone or shift) the transmission timing of the UL transmission with a low priority.

[0097] If more than two (or three or more) UL signals / UL channels overlap in the time domain, the transmission may be controlled in two steps (see FIG. 4).

[0098] In step 1, one UL channel is selected for multiplexing UL signals transmitted in UL transmissions with the same priority. In Fig. 4, an SR (or a PUCCH for SR transmission) having a first priority (high) and a HARQ-ACK (or a PUCCH for HARQ-ACK transmission) may be multiplexed onto a predetermined UL channel (here, the PUCCH for HARQ-ACK transmission). Similarly, an HARQ-ACK (or a PUCCH for HARQ-ACK transmission) having a second priority (low) and data (or a PUSCH for data / UL-SCH transmission) may be multiplexed onto a predetermined UL channel (here, the PUSCH).

[0099] In step 2, among UL transmissions with different priorities, a higher priority UL transmission may be preferentially transmitted and a lower priority UL transmission may be dropped. In Fig. 4, a PUCCH for transmitting an SR and HARQ-ACK having a first priority (high) may be preferentially transmitted, and a PUSCH for transmitting an HARQ-ACK and data having a second priority (low) may be dropped.

[0100] In this way, the UE can resolve collisions between multiple UL transmissions with the same priority in step 1, and between multiple UL transmissions with different priorities in step 2.

[0101] (PUCCH and PUSCH Collision Handling) Hereinafter, specific processes (collision handling) for overlapping various UL channels / signals defined up to Rel. 16 will be described.

[0102] The UE may transmit the PUCCH using a PUCCH resource (e.g., a PUCCH for SR) if the PUCCH resource does not overlap in time with the PUSCH transmission after multiplexing (mapping) UCI ​​(e.g., HARQ-ACK).

[0103] The UE may multiplex (map / piggyback) HARQ-ACK information / CSI report onto the PUSCH if the PUCCH resource overlaps with the PUSCH transmission in time, and in this case, the UE does not need to transmit SR.

[0104] The UE may not transmit a PUSCH that overlaps in time with a PUCCH within a slot.

[0105] When multiple PUCCHs overlap, the UE selects one PUCCH after multiplexing UCI, and if the PUCCH overlaps with a PUSCH in time, collision handling between the PUCCH and the PUSCH is performed.

[0106] (Simultaneous multi-panel UL transmission (SiMPUL)) In future wireless communication systems (e.g., Rel. 18 and later), support for simultaneous UL transmission using multiple panels (e.g., simultaneous multi-panel UL transmission (SiMPUL)) to one or more transmission / reception points (TRPs) is being considered to improve UL throughput / reliability.

[0107] In simultaneous UL transmission using multiple panels, the UE may transmit a physical uplink control channel (PUCCH) and a physical uplink shared channel (PUSCH).

[0108] In Rel. 17, when multiple (e.g., two) PUCCH / PUSCH transmissions with different priorities overlap (in the time domain), the UE first de-overlaps the PUCCH / PUSCH transmission with the smaller (lower) priority index.

[0109] In this case, if multiplexing / mapping of UCIs with different priorities is supported, first, the UE eliminates overlapping of PUCCH / PUSCH transmissions with larger (higher) priority indexes.

[0110] Second, the UE de-duplicates PUCCH transmissions of different priority indices.

[0111] Third, the UE eliminates overlaps between PUCCH and PUSCH transmissions of different priority indices.

[0112] Also, if multiplexing / mapping of UCIs with different priorities is not supported, the UE will cancel the PUCCH / PUSCH with a lower priority index according to a specific rule.

[0113] In the present disclosure, the priority index may correspond to a traffic type. In the present disclosure, the PUCCH / PUSCH may be associated with a priority index, and the association may be configured / instructed to the UE.

[0114] However, when simultaneous transmission using multiple panels for PUSCH and PUCCH (e.g., PUCCH / UCI with different priorities) is supported, the UE's behavior regarding overlapping PUSCH / PUCCH transmissions is unclear, which may result in reduced system performance, such as reduced throughput.

[0115] Therefore, the present inventors have conceived a method for appropriately controlling UL transmission even when UL transmission is performed using multiple panels.

[0116] Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. Wireless communication methods according to the embodiments may be applied independently or in combination.

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

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

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

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

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

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

[0123] In the present disclosure, the terms index, identifier (ID), indicator, resource ID, etc. may be interchangeable. In the present disclosure, the terms sequence, list, set, group, cluster, subset, etc. may be interchangeable.

[0124] In the present disclosure, the terms panel, UE panel, panel group, antenna group, UE capability value, UE capability value set, specific (pool) index included in PUSCH configuration, specific (pool) index included in PUCCH configuration, specific (pool) index included in SRS configuration, beam, beam group, precoder, Uplink (UL) transmitting entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relation, SRS Resource Indicator (SRI), Control Resource Set (CONTROLLER RESEARCH SET ... Signal (DMRS) port), antenna port group (e.g., DMRS port group), group (e.g., spatial relationship group, Code Division Multiplexing (CDM) group, reference signal group, CORESET group, Physical Uplink Control Channel (PUCCH) group, PUCCH resource group), resource (e.g., reference signal resource, SRS resource), resource set (e.g., reference signal resource set), CORESET pool, downlink Transmission Configuration Indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, Quasi-Co-Location (QCL), QCL assumption, etc.The UE capability value set may include, for example, the maximum number of supported SRS ports.

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

[0126] In the present disclosure, the terms drop, abort, cancel, puncture, rate match, postpone, etc. may be read interchangeably.

[0127] In each embodiment of the present disclosure, the following may be interpreted interchangeably: multi-DCI using multi-TRP is configured; no CORESET pool index (RRC parameter "coresetPoolIndex") is provided; and in the active BWP of the serving cell, one or more first CORESETs are provided with a CORESET pool index (RRC parameter "coresetPoolIndex") of a first value (e.g., 0), and one or more second CORESETs are provided with a CORESET pool index (RRC parameter "coresetPoolIndex") of a second value (e.g., 1).

[0128] (Wireless Communication Method) PUCCH resources for UCI (eg, SR / HARQ-ACK / CSI) and panels may be associated based on a specific method.

[0129] The association may be configured in the UE using higher layer signaling (e.g., RRC / MAC CE), may be instructed to the UE using DCI, or may be notified to the UE by combining RRC / MAC CE / DCI. Such information notified to the UE may be called configuration information, instruction information, etc.

[0130] The panels may be associated with PUCCH resources or with spatial relationship information / TCI status of the PUCCH resources.

[0131] The PUSCH transmission and the panel may be associated in a particular manner.

[0132] The association may be configured in the UE using higher layer signaling (e.g., RRC / MAC CE), may be instructed to the UE using DCI, or may be notified to the UE by combining RRC / MAC CE / DCI. Such information notified to the UE may be called configuration information, instruction information, etc.

[0133] The panel may be associated with a PUSCH transmission (resource), or with a TCI state / SRI / SRS resource of a PUSCH transmission, or with CSI in the PUSCH (aperiodic (AP) / semi-persistent (SP) CSI).

[0134] The UCI (eg, SR / HARQ-ACK / CSI report) and the panel may be associated based on a specific method.

[0135] The association may be configured in the UE using higher layer signaling (e.g., RRC / MAC CE), may be indicated to the UE using DCI, or may be notified to the UE using a combination of RRC / MAC CE / DCI.

[0136] A panel may be associated with a PUCCH resource for a CSI report / SR / HARQ-ACK, or may be associated with at least one of a CSI reporting configuration, an SR configuration, and a PDCCH / PDSCH corresponding to the HARQ-ACK information. For CSI in a PUSCH, a panel may be associated with a PUSCH transmission of the CSI report.

[0137] Each embodiment / aspect / option / choice in the present disclosure may be applied to the use of at least one of a single DCI using multiple TRPs and multiple DCIs using multiple TRPs.

[0138] Furthermore, each embodiment / aspect / option / choice of the present disclosure may not be applicable to cases where multiple DCIs using multiple TRPs are applied.

[0139] In the following embodiments and drawings of the present disclosure, a case where PUSCH / PUCCH overlap in the time domain will be described, but this overlap may mean that PUSCH / PUCCH resources completely overlap, that at least some PUSCH / PUCCH resources overlap, or that the time resource of one PUSCH / PUCCH resource is completely included in the time resource of another PUSCH / PUCCH resource. Also, in the present disclosure, overlap in the time domain may simply be described as "overlapping."

[0140] In the following embodiments of the present disclosure, an example in which the number of panels is two will be described, but the number of panels may be three or more. In other words, the number of panels, which is two, may be interpreted as three or more.

[0141] In the present disclosure, simultaneous UL transmission using multiple panels of PUSCH and PUCCH is supported / configured / enabled may mean that the UE transmits PUCCH using one panel / beam and PUSCH using another panel / beam (Figure 5).

[0142] In the present disclosure, if a specific timeline condition is met, the UE may multiplex / map UCI in the PUCCH to the PUSCH. The specific timeline condition may be a timeline condition defined in existing specifications (Rel. 15 / 16 / 17) or a new timeline for multiplexing / mapping UCI in the PUCCH to the PUSCH associated with a different panel.

[0143] <First Embodiment> (Analysis 1) In Rel. 16 / 17, for multiple DCIs using multiple TRPs, if the HARQ-ACK feedback mode is not set to separate (e.g., when the RRC parameter ackNackFeedbackMode=separate is not set), the UE does not expect / assume that the PUSCH / PUCCH scheduled / triggered by a DCI whose CORESET pool index value corresponds to 0 and the PUSCH / PUCCH scheduled / triggered by a DCI whose CORESET pool index value corresponds to 1 overlap in the time domain (this may be referred to as Limitation 1).

[0144] However, if simultaneous transmission using multiple panels for multiple (eg, two) PUSCH / PUCCHs is supported, it is unclear whether such overlapping is allowed.

[0145] In the first embodiment, the allowance / support of overlapping of PUSCH and PUCCH will be described below.

[0146] Simultaneous transmission using multiple panels for multiple (e.g., two) PUSCHs / PUCCHs may be supported / configured / enabled. The UE may support simultaneous transmission using multiple panels for multiple (e.g., two) PUSCHs / PUCCHs. The UE may be configured / enabled for simultaneous transmission using multiple panels for multiple (e.g., two) PUSCHs / PUCCHs.

[0147] This configuration / activation may be performed using higher layer signaling (RRC / MAC CE) / DCI.

[0148] Restriction 1 above may only apply if the relevant configuration / activation is not performed for the UE.

[0149] A configuration related to multiple DCIs using multiple TRPs may be configured for the UE. A specific HARQ-ACK feedback mode may be configured for the UE (e.g., the HARQ-ACK feedback mode may be set to separate (e.g., the RRC parameter ackNackFeedbackMode=separate is notified)).

[0150] The UE may make assumptions / expectations / decisions regarding PUSCH / PUCCH overlap based on whether the PUSCH / PUCCH are associated with the same panel or different panels.

[0151] For example, when one PUSCH / PUCCH and another PUSCH / PUCCH are associated with the same panel, the UE may not expect / assume that the PUSCH / PUCCH scheduled / triggered by a DCI corresponding to a CORESET pool index of a first value (e.g., 0) overlaps (in the time domain) with the PUSCH / PUCCH scheduled / triggered by a DCI corresponding to a CORESET pool index of a second value (e.g., 1).

[0152] For example, when one PUSCH / PUCCH and another PUSCH / PUCCH are associated with different panels, the UE may follow at least one of the following options 1-1 to 1-3.

[0153] The UE may not expect / assume that a PUSCH / PUCCH scheduled / triggered by a DCI corresponding to a CORESET pool index of a first value (e.g., 0) overlaps (in the time domain) with a PUSCH / PUCCH scheduled / triggered by a DCI corresponding to a CORESET pool index of a second value (e.g., 1) (option 1-1).

[0154] The UE may expect / assume that a PUSCH / PUCCH scheduled / triggered by a DCI corresponding to a CORESET pool index of a first value (e.g., 0) overlaps (in the time domain) with a PUSCH / PUCCH scheduled / triggered by a DCI corresponding to a CORESET pool index of a second value (e.g., 1) (option 1-2). In this case, the UE may transmit the PUSCH / PUCCH corresponding to the CORESET pool index of the first value simultaneously (overlapping in the time domain) with the PUSCH / PUCCH corresponding to the CORESET pool index of the second value.

[0155] The UE may be configured to apply either of the above options 1-1 and 1-2 using higher layer signaling (RRC / MAC CE) (option 1-3).

[0156] Note that each embodiment of the present disclosure including this embodiment may be applied not only to overlapping of PUSCH and PUCCH, but also to overlapping of PUSCH and PUSCH, and overlapping of PUCCH and PUCCH.

[0157] According to the first embodiment described above, even when simultaneous transmission using multiple panels is supported, it is possible to appropriately control operations related to overlapping of PUSCH / PUCCH.

[0158] Second Embodiment (Analysis 2) In Rel. 16 / 17, when a PUSCH without UL data (UL-SCH) overlaps (in the time domain) with a PUCCH that includes a positive SR, the PUSCH is dropped (this may be referred to as Restriction 2).

[0159] However, when simultaneous transmission using multiple panels for multiple (e.g., two) PUSCHs / PUCCHs is supported, it is unclear how UEs should behave with respect to overlap between a PUSCH that does not contain UL data and a PUCCH that contains a positive SR.

[0160] In the second embodiment, the overlapping in simultaneous transmission using multiple panels will be described below.

[0161] Simultaneous transmission using multiple panels for multiple (e.g., two) PUSCHs / PUCCHs may be supported / configured / enabled. The UE may support simultaneous transmission using multiple panels for multiple (e.g., two) PUSCHs / PUCCHs. The UE may be configured / enabled for simultaneous transmission using multiple panels for multiple (e.g., two) PUSCHs / PUCCHs.

[0162] This configuration / activation may be performed using higher layer signaling (RRC / MAC CE) / DCI.

[0163] Restriction 2 above may only apply if the relevant configuration / activation is not performed for the UE.

[0164] A PUSCH without UL data (UL-SCH) and a PUCCH including a positive SR may be configured to overlap (in the time domain).

[0165] The UE may determine whether to transmit the PUSCH / PUCCH based on whether the PUSCH / PUCCH is associated with the same panel or a different panel.

[0166] For example, if the PUSCH and the PUCCH are associated with the same panel, the UE may drop the transmission of the PUSCH.

[0167] For example, if the PUSCH and the PUCCH are associated with different panels, the UE may follow at least one of the following options 2-1 to 2-3.

[0168] The UE may not transmit the PUSCH (option 2-1). The UE may decide not to transmit the PUSCH.

[0169] The UE may transmit PUSCH using one panel and PUCCH using another panel (option 2-2).

[0170] The UE may be configured to apply either option 2-1 or 2-2 using higher layer signaling (RRC / MAC CE) (option 2-3).

[0171] According to the second embodiment described above, even when simultaneous transmission using multiple panels is supported, it is possible to appropriately control operations related to overlap between a PUSCH that does not include UL data and a PUCCH that includes a positive SR.

[0172] <Third Embodiment> (Analysis 3) In Rel. 16 / 17, when a PUCCH including UCI and a PUSCH including AP / SP-CSI overlap (in the time domain), a UE multiplexes / maps only the HARQ-ACK included in the UCI onto the PUSCH and drops the PUCCH (this may be referred to as Restriction 3).

[0173] However, when simultaneous transmission using multiple panels for multiple (e.g., two) PUSCHs / PUCCHs is supported, it is unclear how UEs should behave regarding overlap between the PUCCH containing the UCI and the PUSCH containing the AP / SP-CSI.

[0174] In the third embodiment, the overlapping in simultaneous transmission using multiple panels will be described below.

[0175] Simultaneous transmission using multiple panels for multiple (e.g., two) PUSCHs / PUCCHs may be supported / configured / enabled. The UE may support simultaneous transmission using multiple panels for multiple (e.g., two) PUSCHs / PUCCHs. The UE may be configured / enabled for simultaneous transmission using multiple panels for multiple (e.g., two) PUSCHs / PUCCHs.

[0176] This configuration / activation may be performed using higher layer signaling (RRC / MAC CE) / DCI.

[0177] Restriction 3 above may only apply if the relevant configuration / activation is not performed for the UE.

[0178] A PUSCH containing CSI (e.g., AP / SP-CSI) and a PUCCH containing UCI (HARQ-ACK / SR / CSI) may be configured to overlap (in the time domain).

[0179] The UE may determine whether to transmit PUSCH / PUCCH (UCI) based on whether the PUSCH / PUCCH is associated with the same panel or a different panel.

[0180] For example, if the PUSH and the PUCCH are associated with the same panel, the UE may multiplex / map the HARQ-ACK to the PUSH (if the UCI of the PUCCH includes the HARQ-ACK) and not transmit (or drop) the PUCCH.

[0181] For example, if the PUSCH and the PUCCH are associated with different panels, the UE may follow at least one of the following options 3-1 to 3-4.

[0182] The UE may multiplex / map the HARQ-ACK onto the PUSCH (if the UCI of the PUCCH includes the HARQ-ACK) and not transmit the PUCCH (option 3-1).

[0183] The UE may multiplex / map the HARQ-ACK to the PUSCH (if the UCI of the PUCCH includes the HARQ-ACK) and map the UCI excluding the HARQ-ACK to the PUCCH. The UE may transmit the PUSCH using one panel and the PUCCH using another panel (option 3-2).

[0184] The UE may not multiplex / map the HARQ-ACK to the PUSCH (even if the HARQ-ACK is included in the UCI of the PUCCH). The UE may transmit the PUSCH using one panel and the PUCCH using another panel (option 3-3).

[0185] The UE may be configured to apply any of the above options 3-1 to 3-3 using higher layer signaling (RRC / MAC CE) (option 3-4).

[0186] 6 is a diagram illustrating an example of a PUSCH / PUCCH transmission method according to option 3-1. In the example shown in FIG. 6, a PUCCH including UCI (HARQ-ACK / SR / CSI) and a PUSCH including CSI (AP / SP-CSI) overlap.

[0187] In the example shown in Fig. 6, the UE multiplexes / maps / piggybacks the HARQ-ACK included in the UCI of the PUCCH onto the PUSCH using a certain panel, and then transmits the PUSCH. The UE drops the PUCCH.

[0188] 7 is a diagram illustrating an example of a PUSCH / PUCCH transmission method according to option 3-2. In the example shown in FIG. 7, a PUCCH including UCI (HARQ-ACK / SR / CSI) and a PUSCH including CSI (AP / SP-CSI) overlap.

[0189] In the example shown in Fig. 7, the UE uses one panel to multiplex / map / piggyback the HARQ-ACK included in the UCI of the PUCCH onto the PUSCH and transmits the PUSCH, and then uses another panel to transmit UCI other than the HARQ-ACK via the PUCCH.

[0190] 8 is a diagram showing an example of a PUSCH / PUCCH transmission method according to option 3-3. In the example shown in FIG. 8, a PUCCH including UCI (HARQ-ACK / SR / CSI) and a PUSCH including CSI (AP / SP-CSI) overlap.

[0191] In the example shown in Figure 8, the UE uses one panel to transmit the PUSCH without multiplexing / mapping / piggybacking the HARQ-ACK included in the UCI of the PUCCH onto the PUSCH, and uses another panel to transmit the UCI including the HARQ-ACK via the PUCCH.

[0192] In this embodiment, when the PUSCH and the PUCCH are associated with the same panel, the UE may determine to transmit the PUSCH / PUCCH according to existing operations (defined up to Rel. 15 / 16 / 17). When the PUSCH and the PUCCH are associated with different panels, the UE may determine to transmit the PUSCH in one panel and the PUCCH in another panel.

[0193] According to the third embodiment described above, even when simultaneous transmission using multiple panels is supported, it is possible to appropriately control operations related to overlapping of a PUCCH including UCI (HARQ-ACK / SR / CSI) and a PUSCH including CSI (AP / SP-CSI).

[0194] <Fourth Embodiment> (Analysis 4) In Rel. 16 / 17, when a PUCCH including UCI and a PUSCH without AP / SP-CSI (PUSCH without AP / SP CSI) overlap (in the time domain), a UE multiplexes / maps only the HARQ-ACK and CSI included in the UCI onto the PUSCH, and drops the PUCCH (this may be referred to as Restriction 4).

[0195] However, when simultaneous transmission using multiple panels for multiple (e.g., two) PUSCHs / PUCCHs is supported, it is unclear how UEs should behave regarding overlap between a PUCCH containing the UCI and a PUSCH that does not contain AP / SP-CSI.

[0196] In the fourth embodiment, the overlapping in simultaneous transmission using multiple panels will be described below.

[0197] Simultaneous transmission using multiple panels for multiple (e.g., two) PUSCHs / PUCCHs may be supported / configured / enabled. The UE may support simultaneous transmission using multiple panels for multiple (e.g., two) PUSCHs / PUCCHs. The UE may be configured / enabled for simultaneous transmission using multiple panels for multiple (e.g., two) PUSCHs / PUCCHs.

[0198] This configuration / activation may be performed using higher layer signaling (RRC / MAC CE) / DCI.

[0199] Restriction 4 above may only apply if the relevant configuration / activation is not performed for the UE.

[0200] A PUSCH that does not include CSI (e.g., AP / SP-CSI) and a PUCCH that includes UCI (HARQ-ACK / SR / CSI) may be configured to overlap (in the time domain).

[0201] The UE may determine whether to transmit PUSCH / PUCCH (UCI) based on whether the PUSCH / PUCCH is associated with the same panel or a different panel.

[0202] For example, if the PUSCH and the PUCCH are associated with the same panel, the UE may multiplex / map at least one of the HARQ-ACK and CSI to the PUSCH (if the UCI of the PUCCH includes HARQ-ACK / CSI) and not transmit (or drop) the PUCCH.

[0203] For example, if the PUSCH and the PUCCH are associated with different panels, the UE may follow at least one of the following options 4-1 to 4-6.

[0204] The UE may multiplex / map the HARQ-ACK / CSI onto the PUSCH (if the UCI of the PUCCH includes the HARQ-ACK / CSI) and not transmit the PUCCH (option 4-1).

[0205] The UE may multiplex / map the HARQ-ACK / CSI to the PUSCH (if the UCI of the PUCCH includes the HARQ-ACK / CSI) and map the UCI excluding the HARQ-ACK / CSI to the PUCCH. The UE may transmit the PUSCH using one panel and the PUCCH using another panel (option 4-2).

[0206] The UE may multiplex / map the HARQ-ACK to the PUSCH (if the UCI of the PUCCH includes the HARQ-ACK) and map the UCI excluding the HARQ-ACK to the PUCCH. The UE may transmit the PUSCH using one panel and the PUCCH using another panel (option 4-3).

[0207] The UE may multiplex / map the CSI to the PUSCH (if the CSI is included in the UCI of the PUCCH) and map the UCI excluding the CSI to the PUCCH. The UE may transmit the PUSCH using one panel and the PUCCH using another panel (option 4-4).

[0208] The UE may not multiplex / map the HARQ-ACK / CSI to the PUSCH (even if the HARQ-ACK / CSI is included in the UCI of the PUCCH).The UE may transmit the PUSCH using one panel and the PUCCH using another panel (options 4-5).

[0209] The UE may be configured to apply any of the above options 4-1 to 4-5 using higher layer signaling (RRC / MAC CE) (option 4-6).

[0210] 9 is a diagram illustrating an example of a PUSCH / PUCCH transmission method according to option 4-1. In the example illustrated in FIG. 9, a PUCCH including UCI (HARQ-ACK / SR / CSI) and a PUSCH not including CSI (AP / SP-CSI) overlap.

[0211] In the example shown in Fig. 9, the UE multiplexes / maps / piggybacks the HARQ-ACK and CSI included in the UCI of the PUCCH onto the PUSCH using a certain panel, and then transmits the PUSCH. The UE drops the PUCCH.

[0212] 10 is a diagram illustrating an example of a PUSCH / PUCCH transmission method according to options 4-2, 4-3, and 4-4. In the example illustrated in FIG. 10, a PUCCH including UCI (HARQ-ACK / SR / CSI) and a PUSCH not including CSI (AP / SP-CSI) overlap.

[0213] In the example shown in Fig. 10, the UE uses a certain panel to multiplex / map / piggyback at least one of HARQ-ACK and CSI included in UCI of the PUCCH onto the PUSCH and transmits the PUSCH, and uses another panel to transmit UCI other than the HARQ-ACK and CSI via the PUCCH.

[0214] 11 is a diagram illustrating an example of a PUSCH / PUCCH transmission method according to option 4-5. In the example illustrated in FIG. 11, a PUCCH including UCI (HARQ-ACK / SR / CSI) and a PUSCH not including CSI (AP / SP-CSI) overlap.

[0215] In the example shown in Figure 11, the UE uses one panel to transmit the PUSCH without multiplexing / mapping / piggybacking the HARQ-ACK / CSI included in the UCI of the PUCCH onto the PUSCH, and uses another panel to transmit the UCI including the HARQ-ACK / CSI via the PUCCH.

[0216] In this embodiment, when the PUSCH and the PUCCH are associated with the same panel, the UE may determine to transmit the PUSCH / PUCCH according to existing operations (defined up to Rel. 15 / 16 / 17). When the PUSCH and the PUCCH are associated with different panels, the UE may determine to transmit the PUSCH in one panel and the PUCCH in another panel.

[0217] According to the fourth embodiment described above, even when simultaneous transmission using multiple panels is supported, it is possible to appropriately control operations related to overlapping of a PUCCH including UCI (HARQ-ACK / SR / CSI) and a PUSCH not including CSI (AP / SP-CSI).

[0218] Fifth Embodiment (Analysis 5) In Rel. 16 / 17, for two CSIs overlapping in the time domain, if the two CSIs have different priority-related values ​​(e.g., y) (except for the case where y for one CSI is 2 and y for the other CSI is 3), the CSI report with the lower priority is dropped (this may be referred to as Restriction 5).

[0219] y may be a value based on at least one of the type of CSI report (A-CSI report, SP-CSI report, or P-CSI report) and the channel on which the CSI report is transmitted.

[0220] For example, the y of the PUSH of AP-CSI may be a first value (e.g., 0), the y of the PUSH of SP-CSI may be a second value (e.g., 1), the y of the PUCCH of SP-CSI may be a third value (e.g., 2), and the y of the PUCCH of P-CSI may be a fourth value (e.g., 3).

[0221] The above restriction 5 may be applied to at least one of overlapping of CSI in a PUSCH and CSI in a PUCCH, and overlapping of CSI in a PUSCH and CSI in a PUSCH.

[0222] However, when simultaneous transmission using multiple panels for multiple (e.g., two) PUSCH / PUCCHs is supported, it is unclear how UEs should behave with respect to overlapping of multiple (e.g., two) CSIs.

[0223] In the fifth embodiment, the above overlap in simultaneous transmission using multiple panels will be described below.

[0224] Simultaneous transmission using multiple panels for multiple (e.g., two) PUSCHs / PUCCHs may be supported / configured / enabled. The UE may support simultaneous transmission using multiple panels for multiple (e.g., two) PUSCHs / PUCCHs. The UE may be configured / enabled for simultaneous transmission using multiple panels for multiple (e.g., two) PUSCHs / PUCCHs.

[0225] This configuration / activation may be performed using higher layer signaling (RRC / MAC CE) / DCI.

[0226] Restriction 4 above may only apply if the relevant configuration / activation is not performed for the UE.

[0227] Multiple (e.g., two) CSI reports may be configured to overlap (in the time domain), with the multiple CSI reports having different priority-related values ​​(e.g., a function that gives the priority value (e.g., Pr ｉｉＣＳＩ (y, k, c, s)).

[0228] This embodiment may be applied to cases other than the case where the first CSI report and the second CSI report overlap, and the first CSI report corresponds to a specific first value of y (e.g., 2), and the second CSI report corresponds to a specific second value of y (e.g., 3).

[0229] The value of y may be based on at least one of the type of CSI report (A-CSI report, SP-CSI report, or P-CSI report) and the channel on which the CSI report is transmitted.

[0230] For example, the y of the PUSH of AP-CSI may be a first value (e.g., 0), the y of the PUSH of SP-CSI may be a second value (e.g., 1), the y of the PUCCH of SP-CSI may be a third value (e.g., 2), and the y of the PUCCH of P-CSI may be a fourth value (e.g., 3).

[0231] The UE may determine transmission of the multiple CSIs based on whether the multiple CSIs are associated with the same panel or different panels.

[0232] For example, if the multiple CSIs are associated with the same panel, the UE may not transmit a CSI report with a lower priority.

[0233] The priority is a function that gives the priority value (e.g., Pr ｉｉＣＳＩ (y, k, c, s)). A higher priority may be determined based on a lower (or higher) Pr ｉｉＣＳＩ It may correspond to the values ​​of (y, k, c, s).

[0234] For example, if the multiple CSIs are associated with different panels, the UE may follow at least one of the following options 5-1 to 5-3.

[0235] The UE may not transmit low priority CSI reports (option 5-1).

[0236] The UE may transmit some CSI reports using one panel and other CSI reports using another panel (option 5-2).

[0237] The UE may be configured to apply either of the above options 5-1 and 5-2 using higher layer signaling (RRC / MAC CE) (option 5-3).

[0238] According to the fifth embodiment described above, even when simultaneous transmission using multiple panels is supported, it is possible to appropriately control operations related to overlapping of multiple CSIs corresponding to different priorities.

[0239] Sixth Embodiment (Analysis 6) In Rel. 16 / 17, when a PUCCH (including UCI) overlaps with multiple PUSCHs, some of the PUSCHs are scheduled by DCI, and some of the PUSCHs are configured grant (CG) PUSCHs, the UE multiplexes / maps the UCI onto the PUSCHs scheduled by the DCI (Limitation 6-A).

[0240] In addition, in Rel. 16 / 17, when a PUCCH (including UCI) overlaps with multiple PUSCHs and AP-CSI is not multiplexed / mapped to any of the multiple PUSCHs, the UE multiplexes / maps the UCI to the PUSCH of the serving cell with the smallest serving cell index (ServCellIndex). In this case, if there are multiple PUSCHs for the serving cell with the smallest serving cell index, the UE multiplexes / maps the UCI to the earliest PUSCH (Restriction 6-B).

[0241] Also, in Rel. 16 / 17, the UE does not assume / expect one or more PUSCHs containing AP-CSI to overlap with the PUCCH (restriction 6-C).

[0242] However, when simultaneous transmission using multiple panels for multiple (eg, two) PUSCHs / PUCCHs is supported, the UE behavior regarding the selection / decision of the PUSCH as described above is unclear.

[0243] In the sixth embodiment, the selection / determination of the PUSCH in simultaneous transmission using multiple panels will be described below.

[0244] Simultaneous transmission using multiple panels for multiple (e.g., two) PUSCHs / PUCCHs may be supported / configured / enabled. The UE may support simultaneous transmission using multiple panels for multiple (e.g., two) PUSCHs / PUCCHs. The UE may be configured / enabled for simultaneous transmission using multiple panels for multiple (e.g., two) PUSCHs / PUCCHs.

[0245] This configuration / activation may be performed using higher layer signaling (RRC / MAC CE) / DCI.

[0246] The above restrictions 6-A / 6-B / 6-C may only be applied if the relevant configuration / activation is not performed for the UE.

[0247] A PUCCH and multiple PUSCHs may be configured to overlap each other (in the time domain), and the multiple PUSCHs may be PUSCHs that satisfy the conditions for multiplexing / mapping of UCI.

[0248] The UE may determine whether to transmit a PUSCH / PUCCH (UCI) based on whether the PUCCH / multiple PUSCHs are associated with the same panel or different panels.

[0249] For example, if the PUCCH (including UCI) and the multiple PUSCHs are associated with the same panel, the UE may select / determine a specific PUSCH from the multiple PUSCHs based on a specific rule. The specific rule may be a PUSCH within the restrictions defined in Rel. 16 / 17. The UE may multiplex / map UCI to the selected / determined PUSCH.

[0250] For example, if the multiple PUSCHs are associated with the same panel, and the PUCCH (including UCI) and the multiple PUSCHs are associated with different panels, the UE may select / determine a specific PUSCH from the multiple PUSCHs based on a specific rule. The specific rule may be a PUSCH within the restrictions specified in Rel. 16 / 17. The UE may multiplex / map UCI to the selected / determined PUSCH.

[0251] For example, if the multiple PUSCHs are associated with different panels, the UE may select / determine a specific PUSCH from the multiple PUSCHs based on a specific rule, and may multiplex / map UCI to the selected / determined PUSCH.

[0252] The particular rule may be at least one of the following options 6-1 to 6-5.

[0253] (Option 6-1) First, the UE may make a selection / decision (first selection / decision) based on the panel ID for multiple PUSCHs.

[0254] For example, the UE may select / determine a PUSCH corresponding to an ID (panel ID) for a particular panel, or a PUSCH associated with the same panel as a PUCCH corresponding to a particular priority.

[0255] The ID for that particular panel may be a lower (or higher) panel ID.

[0256] The PUCCH corresponding to the particular priority may be a PUCCH corresponding to a higher (or lower) priority.

[0257] In the present disclosure, higher, larger, lower, smaller, highest, maximum, lowest, and minimum may be read interchangeably.

[0258] For the PUSCH based on the first selection / decision, if there are multiple PUSCHs (i.e., if there are PUSCHs associated with the same panel), the UE may apply the rules in Rel. 16 / 17 to the PUSCH (e.g., first, make a selection / decision based on the PUSCH type, second, make a selection / decision based on the serving cell index, and third, make a selection / decision regarding the time resource of the PUSCH).

[0259] (Option 6-2) First, the UE may perform a selection / decision (first selection / decision) based on the type of PUSCH for multiple PUSCHs.

[0260] For example, for multiple PUSCHs, a priority may be applied based on whether the PUSCH is a PUSCH scheduled by DCI or a configured grant PUSCH. For example, the priority of the PUSCH scheduled by DCI may be specified to be higher (or lower) than the priority of the configured grant PUSCH. The UE may select / decide the PUSCH based on the priority.

[0261] Next, if there are multiple PUSHs based on the first selection / decision, the UE may make a selection / decision (second selection / decision) based on the panel ID for the PUSHs based on the first selection / decision.

[0262] For example, if there are multiple PUSHs based on the first selection / determination, the UE may select / determine from the selected / determined PUSHs a PUSH corresponding to an ID (panel ID) for a specific panel, or a PUSH associated with the same panel as a PUCH corresponding to a specific priority.

[0263] The ID for that particular panel may be a lower (or higher) panel ID.

[0264] The PUCCH corresponding to the particular priority may be a PUCCH corresponding to a higher (or lower) priority.

[0265] Furthermore, if there are multiple PUSHs based on the second selection / decision (i.e., if there are PUSHs associated with the same panel), the UE may make a selection / decision (third selection / decision) based on the serving cell index (ServCellIndex) corresponding to the PUSH.

[0266] For example, when there are multiple PUSCHs based on the second selection / determination, the UE may select / determine a PUSCH corresponding to a specific serving cell index (ServCellIndex) from the selected / determined PUSCHs. For example, the priority of a PUSCH with a smaller serving cell index (ServCellIndex) may be specified to be higher (or lower) than a PUSCH with a larger serving cell index (ServCellIndex). The UE may select / determine a PUSCH based on the priority.

[0267] Furthermore, when there are multiple PUSCHs based on the third selection / determination, the UE may select / determine the earliest (or latest) PUSCH from among the multiple PUSCHs (fourth selection / determination). For example, the priority of an earlier PUSCH may be specified to be higher (or lower) than the priority of a later PUSCH.

[0268] (Option 6-3) First, the UE may perform a selection / decision (first selection / decision) based on the type of PUSCH for multiple PUSCHs.

[0269] For example, for multiple PUSCHs, a priority may be applied based on whether the PUSCH is a PUSCH scheduled by DCI or a configured grant PUSCH. For example, the priority of the PUSCH scheduled by DCI may be specified to be higher (or lower) than the priority of the configured grant PUSCH. The UE may select / decide the PUSCH based on the priority.

[0270] Next, if there are multiple PUSHs based on the first selection / decision, the UE may make a selection / decision (second selection / decision) based on the serving cell index (ServCellIndex) corresponding to the PUSH.

[0271] For example, when there are multiple PUSCHs based on the first selection / determination, the UE may select / determine a PUSCH corresponding to a specific serving cell index (ServCellIndex) from the selected / determined PUSCHs. For example, the priority of a PUSCH with a smaller serving cell index (ServCellIndex) may be specified to be higher (or lower) than a PUSCH with a larger serving cell index (ServCellIndex). The UE may select / determine a PUSCH based on the priority.

[0272] Furthermore, if there are multiple PUSHs based on the second selection / decision (i.e., if there are multiple PUSHs corresponding to the same serving cell index), the UE may make a selection / decision (third selection / decision) based on the panel ID for the PUSH based on the second selection / decision.

[0273] For example, if there are multiple PUSHs based on the second selection / determination, the UE may select / determine from the selected / determined PUSHs a PUSH corresponding to an ID (panel ID) for a specific panel, or a PUSH associated with the same panel as a PUCH corresponding to a specific priority.

[0274] The ID for that particular panel may be a lower (or higher) panel ID.

[0275] The PUCCH corresponding to the particular priority may be a PUCCH corresponding to a higher (or lower) priority.

[0276] Furthermore, when there are multiple PUSCHs based on the third selection / determination, the UE may select / determine the earliest (or latest) PUSCH from among the multiple PUSCHs (fourth selection / determination). For example, the priority of an earlier PUSCH may be specified to be higher (or lower) than the priority of a later PUSCH.

[0277] (Option 6-4) First, the UE may perform a selection / decision (first selection / decision) based on the type of PUSCH for multiple PUSCHs.

[0278] For example, for multiple PUSCHs, a priority may be applied based on whether the PUSCH is a PUSCH scheduled by DCI or a configured grant PUSCH. For example, the priority of the PUSCH scheduled by DCI may be specified to be higher (or lower) than the priority of the configured grant PUSCH. The UE may select / decide the PUSCH based on the priority.

[0279] Next, if there are multiple PUSHs based on the first selection / decision, the UE may make a selection / decision (second selection / decision) based on the serving cell index (ServCellIndex) corresponding to the PUSH.

[0280] For example, when there are multiple PUSCHs based on the first selection / determination, the UE may select / determine a PUSCH corresponding to a specific serving cell index (ServCellIndex) from the selected / determined PUSCHs. For example, the priority of a PUSCH with a smaller serving cell index (ServCellIndex) may be specified to be higher (or lower) than a PUSCH with a larger serving cell index (ServCellIndex). The UE may select / determine a PUSCH based on the priority.

[0281] Furthermore, when there are multiple PUSCHs based on the second selection / determination, the UE may select / determine the earliest (or latest) PUSCH from among the multiple PUSCHs (third selection / determination). For example, the priority of an earlier PUSCH may be specified to be higher (or lower) than the priority of a later PUSCH.

[0282] Furthermore, if there are multiple PUSHs based on the third selection / decision (i.e., if there are overlapping PUSHs in the same time domain after the first to third selections / decisions), the UE may make a selection / decision (fourth selection / decision) based on the panel ID for the PUSH based on the third selection / decision.

[0283] For example, if there are multiple PUSHs based on the third selection / determination, the UE may select / determine from the selected / determined PUSHs a PUSH corresponding to an ID (panel ID) for a specific panel, or a PUSH associated with the same panel as a PUCH corresponding to a specific priority.

[0284] The ID for that particular panel may be a lower (or higher) panel ID.

[0285] The PUCCH corresponding to the particular priority may be a PUCCH corresponding to a higher (or lower) priority.

[0286] (Option 6-5) The UE may select / determine the PUSCH corresponding to each panel by applying the rules in the above-mentioned Rel. 16 / 17 (e.g., first, select / determine based on the type of PUSCH, second, select / determine based on the serving cell index, and third, select / determine based on the time resource of the PUSCH).

[0287] The UE may multiplex / map UCI to multiple PUSCHs using multiple panels.

[0288] According to the sixth embodiment described above, even when simultaneous UL transmission using multiple panels is performed, it is possible to appropriately select / determine a PUSCH to which UCI is multiplexed / mapped from multiple PUSCHs.

[0289] <Modification> With regard to the setting method for the above options 1-3 / 2-3 / 3-4 / 4-6 / 5-3, each option may be set based on different (independent) setting information (signaling).

[0290] Regarding the configuration methods for the above options 1-3 / 2-3 / 3-4 / 4-6 / 5-3, at least two of the options (or all of the options) may be configured based on common (joint) configuration information (signaling).

[0291] In each embodiment of the present disclosure, "associated with different panels" and "associated with the same panel" may be read interchangeably.

[0292] <Other Embodiments> A higher layer parameter (RRC IE) / UE capability corresponding to a function (feature) in at least one of the above embodiments may be defined. The UE capability may indicate support of this function.

[0293] A UE configured with higher layer parameters corresponding to the function (enabling the function) may perform the function. It may also be specified that "a UE not configured with higher layer parameters corresponding to the function shall not perform the function (for example, in accordance with Rel. 15 / 16 / 17)."

[0294] A UE that reports a UE capability indicating that it supports the feature may perform the feature. It may also be specified that a UE that does not report a UE capability indicating that it supports the feature shall not perform the feature (e.g., in accordance with Rel. 15 / 16 / 17).

[0295] If the UE reports a UE capability indicating that it supports the function and the corresponding higher layer parameters are configured, the UE may perform the function. It may also be specified that "if the UE does not report a UE capability indicating that it supports the function or if the corresponding higher layer parameters are not configured, the UE shall not perform the function (e.g., in accordance with Rel. 15 / 16 / 17)."

[0296] The UE capability may indicate whether the UE supports this feature.

[0297] The function may be the application of simultaneous UL transmission using multiple panels.

[0298] UE capability may be defined as whether or not it supports simultaneous transmission of PUCCH in one panel and PUSCH in another panel.

[0299] The UE capability may be defined as whether it supports multiplexing / mapping of UCI in a PUSCH associated with the same panel as the PUCCH in cases where the PUCCH containing UCI overlaps with the PUSCH.

[0300] The UE capability may be defined as whether or not it supports multiplexing / mapping of UCI in a PUSCH associated with a different panel than the PUCCH in the case where the PUCCH containing UCI overlaps with the PUSCH.

[0301] The UE capability may be defined as whether or not it supports multiplexing / mapping of HARQ-ACK in a PUSCH associated with the same panel as the PUCCH in cases where a PUCCH containing UCI overlaps with a PUSCH containing CSI (AP / SP-CSI).

[0302] The UE capability may be defined as whether or not it supports multiplexing / mapping of HARQ-ACK in a PUSCH associated with a different panel than the PUCCH in the case where the PUCCH containing UCI overlaps with the PUSCH containing CSI (AP / SP-CSI).

[0303] UE capability may be defined as whether or not it supports multiplexing / mapping of HARQ-ACK / CSI in a PUSCH associated with the same panel as the PUCCH in cases where a PUCCH containing UCI overlaps with a PUSCH not containing CSI (AP / SP-CSI).

[0304] The UE capability may be defined as whether or not it supports multiplexing / mapping of HARQ-ACK / CSI in a PUSCH associated with a different panel than the PUCCH in the case where a PUCCH containing UCI overlaps with a PUSCH not containing CSI (AP / SP-CSI).

[0305] The UE capability may be defined as whether or not it supports simultaneous transmission of multiple (two) pieces of CSI in the case where the multiple (two) pieces of CSI overlap and are associated with different panels.

[0306] UE capability may be defined as whether it supports at least one of the methods described in the first to sixth embodiments above.

[0307] According to the above and other embodiments, the UE can achieve the above functions while maintaining compatibility with existing specifications.

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

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

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

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

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

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

[0314] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of carrier aggregation (CA) using multiple component carriers (CCs) and dual connectivity (DC).

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

[0316] Furthermore, the user terminal 20 may perform communication using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0351] The transceiver 120 may transmit first configuration information related to multiple pieces of channel state information (CSI) and second configuration information related to simultaneous transmission of a physical uplink control channel (PUCCH) using multiple panels. The controller 110 may use the first configuration information and the second configuration information to indicate PUCCH resources to which the multiple pieces of CSI in the same time domain are mapped (second embodiment).

[0352] The transceiver 120 may transmit first setting information related to a physical uplink control channel (PUCCH), second setting information related to a physical uplink shared channel (PUSCH), and third setting information related to simultaneous uplink transmission using multiple panels. The controller 110 may use the first setting information, the second setting information, and the third setting information to issue an instruction related to simultaneous transmission of the PUSCH and the PUCCH in the same time domain (first, second, third, and fifth embodiments).

[0353] The transceiver 120 may transmit first setting information related to a physical uplink control channel (PUCCH), second setting information related to a physical uplink shared channel (PUSCH), and third setting information related to simultaneous uplink transmission using multiple panels. The control unit 110 may use the first setting information, the second setting information, and the third setting information to instruct selection of resources for the PUSCH and transmission of at least one of the PUSCH and the PUCCH (fourth and sixth embodiments).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0371] The transceiver 220 may generate first configuration information related to a physical uplink control channel (PUCCH), second configuration information related to a physical uplink shared channel (PUSCH), and third configuration information related to simultaneous uplink transmission using multiple panels. The controller 210 may control assumptions regarding transmission of the PUSCH and the PUCCH in the same time domain and transmission of at least one of the PUSCH and the PUCCH based on the first configuration information, the second configuration information, and the third configuration information (first, second, third, and fifth embodiments).

[0372] When a PUCCH including a positive scheduling request (SR) is configured using the first configuration information and a PUSCH not including uplink data is configured using the second configuration information, the control unit 210 may control the transmission of at least one of the PUSCH and the PUCCH based on whether the PUSCH and the PUCCH are associated with the same panel (second embodiment).

[0373] When a PUCCH including at least one of a hybrid automatic repeat request acknowledgement (HARQ-ACK), a scheduling request, and first channel state information (CSI) is configured using the first configuration information, and a PUSCH including second CSI is configured using the second configuration information, the control unit 210 may control the transmission of at least one of the PUSCH and the PUCCH based on whether the PUSCH and the PUCCH are associated with the same panel (third embodiment).

[0374] When multiple pieces of channel state information (CSI) are set to the same time domain, the control unit 210 may control the transmission of at least one of the PUSCH and the PUCCH based on the priority values ​​of the multiple CSI and whether the PUSCH and the PUCCH are associated with the same panel (fifth embodiment).

[0375] The transceiver 220 may receive first setting information related to a physical uplink control channel (PUCCH), second setting information related to a physical uplink shared channel (PUSCH), and third setting information related to simultaneous uplink transmission using multiple panels. The controller 210 may control selection of resources for the PUSCH and transmission of at least one of the PUSCH and the PUCCH based on the first setting information, the second setting information, and the third setting information (fourth and sixth embodiments).

[0376] When a PUCCH including at least one of a hybrid automatic repeat request acknowledgement (HARQ-ACK), a scheduling request, and first CSI is configured using the first configuration information, and a PUSCH not including CSI is configured using the second configuration information, the control unit 210 may control the transmission of at least one of the PUSCH and the PUCCH based on whether the PUSCH and the PUCCH are associated with the same panel (fourth embodiment).

[0377] When the PUSCH and the PUCCH are associated with different panels, the controller 210 may determine whether to map the HARQ-ACK and the first CSI to the PUSCH (fourth embodiment).

[0378] When the PUSH is a plurality of PUSHs, the control unit 210 may determine a PUSH to which uplink control information is mapped from the plurality of PUSHs based on an ID related to a panel associated with each of the plurality of PUSHs, the type of each of the plurality of PUSHs, a serving cell index associated with each of the plurality of PUSHs, and the time resource of each of the plurality of PUSHs (sixth embodiment).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0419] Note that the physical layer signaling may be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be referred to as an RRC message, such as an RRC Connection Setup message or an RRC Connection Reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, a MAC Control Element (CE).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0461] Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The invention according to the present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the invention as defined by the description of the claims. Therefore, the description of the present disclosure is intended to be illustrative and explanatory and does not impose any limiting meaning on the invention according to the present disclosure.

Claims

1. A method and apparatus for transmitting a plurality of physical uplink shared channels (PUSCHs) using multiple panels, comprising: a receiving unit for receiving higher layer signaling for enabling simultaneous transmission using multiple panels for multiple physical uplink shared channels (PUSCHs); A control unit that multiplexes uplink control information (UCI) into a PUSCH associated with the same CORESET as a physical uplink control channel (PUCCH) corresponding to a specific priority when the multiple PUSCHs are associated with different control resource sets (COntrol REsource SET (CORESET)).

2. The terminal of claim 1, wherein the PUCCH corresponds to a higher priority.

3. The terminal of claim 1, wherein the PUCCH corresponds to a lower priority.

4. A method for transmitting a plurality of physical uplink shared channels (PUSCHs) using a plurality of panels, comprising: receiving higher layer signaling for enabling simultaneous transmission using multiple panels for multiple physical uplink shared channels (PUSCHs); and when the plurality of PUSCHs are associated with different control resource sets (COntrol REsource SETs (CORESETs)), multiplexing uplink control information (UCI) into a PUSCH associated with the same CORESET as a physical uplink control channel (PUCCH) corresponding to a specific priority.

5. A transmitter that transmits higher layer signaling to enable simultaneous transmission using multiple panels for multiple physical uplink shared channels (PUSCHs), and a control unit that instructs a PUSCH associated with the same CORESET as a physical uplink control channel (PUCCH) corresponding to a specific priority to multiplex uplink control information (UCI) when the multiple PUSCHs are associated with different control resource sets (COntrol REsource SET (CORESET)).

6. A system having a terminal and a base station, The terminal includes a receiver for receiving higher layer signaling for enabling simultaneous transmission using multiple panels for multiple physical uplink shared channels (PUSCHs); A control unit that multiplexes uplink control information (UCI) onto a PUSCH associated with the same CORESET as a physical uplink control channel (PUCCH) corresponding to a specific priority when the plurality of PUSCHs are associated with different control resource sets (COntrol REsource SET (CORESET)), The base station includes a transmitter that transmits the higher layer signaling; A control unit that instructs the UCI to be multiplexed onto the PUSCH.