Methods and apparatus for transmitting and receiving signals in a wireless communication system

Abstract

User equipment (UE) operations related to at least one of the embodiments of the present disclosure may include: multiplexing a plurality of UCIs on a single physical uplink shared channel (PUSCH); and transmitting a single PUSCH in which the plurality of UCIs are multiplexed. Based on the UE being configured to multiplex UCIs with different priorities on the same PUSCH, a priority of a first UCI included in the plurality of UCIs is Priority‑H higher than Priority‑L, and the first UCI with Priority‑H includes 2 parts of channel state information (CSI), the UE may discard all hybrid automatic repeat request acknowledgment (HARQ‑ACK) information of a second UCI with Priority‑L lower than Priority‑H, and map the first part of the CSI and the second part of the CSI to the single PUSCH.

Description

Technical Field

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for transmitting / receiving uplink / downlink wireless signals in the wireless communication system. Background Art

[0002] In general, wireless communication systems are developing to cover a wide range in various ways to provide communication services such as audio communication services, data communication services, etc. Wireless communication is a multiple access system that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, etc.). For example, the multiple access system can be any of a code division multiple access (CDMA) system, a frequency division multiple access (FDMA) system, a time division multiple access (TDMA) system, an orthogonal frequency division multiple access (OFDMA) system, and a single carrier frequency division multiple access (SC-FDMA) system. Summary of the invention

[0003] Technical issues

[0004] An object of the present disclosure is to provide a method and an apparatus thereof for efficiently performing a wireless signal transmission / reception process.

[0005] Those skilled in the art will understand that the objectives that can be achieved using the present disclosure are not limited to those specifically described above, and the above and other objectives that can be achieved by the present disclosure will be more clearly understood from the following detailed description.

[0006] Technical Solution

[0007] According to one aspect of the present disclosure, a method for transmitting uplink control information (UCI) by a user equipment (UE) in a wireless communication system may include: multiplexing a plurality of UCIs on a single physical uplink shared channel (PUSCH); and transmitting a single PUSCH in which the plurality of UCIs are multiplexed. Based on i) the UE being configured to multiplex UCIs with different priorities on the same PUSCH, ii) the priority of a first UCI included in the plurality of UCIs is Priority-H higher than Priority-L, and iii) the first UCI with Priority-H includes 2 parts of channel state information (CSI), the UE may discard all hybrid automatic repeat request acknowledgment (HARQ-ACK) information of a second UCI with Priority-L lower than Priority-H, and map the first part of the CSI and the second part of the CSI to a single PUSCH.

[0008] In a state where the first UCI with Priority-H does not include any HARQ-ACK information, the UE may perform resource element (RE) reservation for potential HARQ-ACK associated with Priority-H on a single PUSCH.

[0009] In a state where the first UCI with Priority-H does not include any HARQ-ACK information, the UE may perform multiplexing assuming that potential HARQ-ACK related to Priority-H is UCI type 1.

[0010] The UE may perform multiplexing assuming that the first part of the CSI and the second part of the CSI are UCI type 2 and UCI type 3, respectively.

[0011] Based on the HARQ-ACK information not exceeding 2 bits in the first UCI with Priority-H, the UE may perform RE reservation for potential HARQ-ACK associated with Priority-H on a single PUSCH regardless of whether there is actual HARQ-ACK associated with Priority-H.

[0012] The UE may map the first part of the CSI to REs on a single PUSCH excluding specific REs reserved by RE reservation among available REs of the single PUSCH, and after mapping the first part, sequentially map the second part of the CSI and data to the remaining REs including the specific REs on the single PUSCH.

[0013] Based on the existence of actual 1-bit or 2-bit HARQ-ACK associated with Priority-H, after mapping the second part and the data, the UE may puncture specific REs reserved by RE reservation and map 1-bit or 2-bit HARQ-ACK associated with Priority-H.

[0014] The single PUSCH may be a PUSCH with Priority-H.

[0015] The first part of the CSI with Priority-H and the second part of the CSI may be related to aperiodic CSI reporting.

[0016] According to one aspect of the present disclosure, a processor-readable recording medium may be provided, which records instructions for executing the above UCI transmission method.

[0017] According to one aspect of the present disclosure, a UE for performing the above UCI transmission method may be provided.

[0018] According to one aspect of the present disclosure, a device for controlling a UE to perform the above UCI transmission method may be provided.

[0019] According to one aspect of the present disclosure, a method for receiving UCI by a BS in a wireless communication system may include: receiving a single PUSCH from a UE; and obtaining a plurality of UCIs multiplexed on the received single PUSCH. Based on i) the BS configuring the UE to multiplex UCIs with different priorities on the same PUSCH, ii) the priority of a first UCI included in the plurality of UCIs is Priority-H higher than Priority-L, and iii) the first UCI with Priority-H includes 2 parts of CSI, the BS may perform demultiplexing on a single PUSCH for a first part of CSI and a second part of CSI, assuming that all HARQ-ACK information of a second UCI with Priority-L lower than Priority-H is discarded.

[0020] According to one aspect of the present disclosure, a BS for performing the above signal reception method may be provided.

[0021] Beneficial Effects

[0022] According to the present disclosure, wireless signal transmission and reception can be efficiently performed in a wireless communication system.

[0023] Those skilled in the art will appreciate that the effects that can be achieved using the present disclosure are not limited to the contents specifically described above, and other advantages of the present disclosure will be more clearly understood from the following detailed description in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The accompanying drawings, which are included to provide a further understanding of the present disclosure and are incorporated in and constitute a part of this application, illustrate embodiments of the present disclosure and together with the description serve to explain the principles of the present disclosure. In the drawings:

[0025] Figure 1 illustrates physical channels used in a 3rd Generation Partnership Project (3GPP) system as an exemplary wireless communication system and a general signal transmission method using the physical channels;

[0026] Figure 2 illustrates the radio frame structure;

[0027] Figure 3 A resource grid of illustrated time slots;

[0028] Figure 4 illustrates an exemplary mapping of physical channels in time slots;

[0029] Figure 5illustrates an exemplary physical downlink shared channel (PDSCH) transmission and reception process;

[0030] Figure 6 illustrates an exemplary physical uplink shared channel (PUSCH) transmission and reception process;

[0031] Figure 7 An example of multiplexing control information in a PUSCH is shown;

[0032] Figure 8 illustrates various scenarios where signals with different priorities overlap each other;

[0033] Fig. 9 , Fig.10 and Fig.11 is a diagram illustrating uplink control information (UCI) multiplexing according to an embodiment of the present disclosure;

[0034] Fig.12 and Fig.13 illustrating a signal transmission and reception method according to an embodiment of the present disclosure;

[0035] Figures 14 to 17 illustrates an example of a communication system 1 and a wireless device applied to the present disclosure; and

[0036] Fig.18 An exemplary discontinuous reception (DRX) operation suitable for use with the present disclosure is illustrated. DETAILED DESCRIPTION

[0037] Embodiments of the present disclosure are applicable to various wireless access technologies such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), and single carrier frequency division multiple access (SC-FDMA). CDMA can be implemented as a radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented as a radio technology such as Global System for Mobile Communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rates for GSM Evolution (EDGE). OFDMA can be implemented as a radio technology such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wireless Fidelity (Wi-Fi)), IEEE 802.16 (Worldwide Interoperability for Microwave Access (WiMAX)), IEEE 802.20, and Evolved UTRA (E-UTRA). UTRA is part of Universal Mobile Telecommunications System (UMTS). 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is a part of Evolved UMTS (E-UMTS) using E-UTRA, and LTE-Advanced (A) is an evolved version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A.

[0038] As more and more communication devices require greater communication capacity, enhanced mobile broadband communications relative to traditional radio access technologies (RATs) are needed. In addition, large-scale machine-type communications (MTC), which can provide various services anytime and anywhere by connecting multiple devices and objects, is another important issue to be considered for next-generation communications. Discussions are also underway to design communication systems that take into account services / UEs that are sensitive to reliability and latency. Therefore, discussions are underway to introduce new radio access technologies that take into account enhanced mobile broadband communications (eMBB), massive MTC, and ultra-reliable low-latency communications (URLLC). In this disclosure, for simplicity, this technology will be referred to as NR (new radio or new RAT).

[0039] For the sake of brevity, 3GPP NR is mainly described, but the technical concept of the present disclosure is not limited thereto.

[0040] In the present disclosure, the term "set / setting" may be replaced with "configure / configuration", and the two may be used interchangeably. In addition, conditional expressions (e.g., "if", "in this case", or "when...") may be replaced with "based on" or "in a situation / state...". In addition, the operation or software / hardware (SW / HW) configuration of a user equipment (UE) / base station (BS) may be derived / understood based on the satisfaction of the corresponding condition. When the process on the receiving (or transmitting) side may be derived / understood from the process on the transmitting (or receiving) side in the signal transmission / reception between wireless communication devices (e.g., BS and UE), its description may be omitted. For example, signal determination / generation / encoding / transmission on the transmitting side may be understood as signal monitoring reception / decoding / determination on the receiving side. In addition, when it is said that the UE performs (or does not perform) a specific operation, this may also be interpreted as the BS expecting / assuming (or not expecting / assuming) that the UE performs a specific operation. When it is said that the BS performs (or does not perform) a specific operation, this may also be interpreted as the UE expecting / assuming (or not expecting / assuming) that the BS performs a specific operation. In the following description, for the convenience of description, chapters, embodiments, examples, options, methods, schemes, etc. are distinguished from each other and marked with indexes, which does not mean that each of them necessarily constitutes an independent invention or each of them can only be implemented separately. Unless explicitly contradicted, it can be concluded / understood that at least some of the chapters, embodiments, examples, options, methods, schemes, etc. can be implemented in combination or can be omitted.

[0041] In a wireless communication system, a user equipment (UE) receives information from a base station (BS) through a downlink (DL) and transmits information to the BS through an uplink (UL). The information transmitted and received by the BS and the UE includes data and various control information, and includes various physical channels according to the type / purpose of the information transmitted and received by the UE and the BS.

[0042] Figure 1 Illustration of physical channels used in a 3GPP NR system and a general signal transmission method using the same.

[0043] When the UE is powered on again from a power-off state or enters a new cell, in step S11, the UE performs an initial cell search process (e.g., establishes synchronization with the BS). To this end, the UE receives a synchronization signal block (SSB) from the BS. The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). The UE establishes synchronization with the BS based on the PSS / SSS and obtains information such as a cell identity (ID). The UE can obtain broadcast information in the cell based on the PBCH. The UE can receive a DL reference signal (RS) during the initial cell search process to monitor the DL channel status.

[0044] After the initial cell search, the UE may acquire more specific system information by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) based on information of the PDCCH in step S12.

[0045] The UE may perform a random access procedure to access the BS in steps S13 to S16. For random access, the UE may send a preamble to the BS on a physical random access channel (PRACH) (S13) and receive a response message to the preamble on a PDCCH and a PDSCH corresponding to the PDCCH (S14). In the case of contention-based random access, the UE may perform a contention resolution procedure by further sending a PRACH (S15) and receiving a PDCCH and a PDSCH corresponding to the PDCCH (S16).

[0046] After the aforementioned process, the UE may receive PDCCH / PDSCH (S17) and send a physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) (S18) as a general downlink / uplink signal transmission process. The control information sent from the UE to the BS is called uplink control information (UCI). UCI includes hybrid automatic repeat and request confirmation / negative determination (HARQ-ACK / NACK), scheduling request (SR), channel state information (CSI), etc. CSI includes channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), etc. Although UCI is usually sent on PUCCH, UCI may be sent on PUSCH when control information and service data need to be sent simultaneously. In addition, UCI may be sent aperiodically via PUSCH according to a request / command of the network.

[0047] Figure 2 Figure 1. Radio frame structure. In NR, uplink transmission and downlink transmission are configured in frames. Each radio frame has a length of 10ms and is divided into two 5ms half frames (HF). Each half frame is divided into five 1ms subframes (SF). A subframe is divided into one or more time slots, and the number of time slots in a subframe depends on the subcarrier spacing (SCS). Depending on the cyclic prefix (CP), each time slot includes 12 or 14 orthogonal frequency division multiplexing (OFDM) symbols. When a normal CP is used, each time slot includes 14 OFDM symbols. When an extended CP is used, each time slot includes 12 OFDM symbols.

[0048] Table 1 exemplarily shows that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to the SCS when a normal CP is used.

[0049] [Table 1]

[0050] SCS(15*2^u) <![CDATA[N slot symb ]]> <![CDATA[N frame,u slot ]]> <![CDATA[N subframe,u slot ]]> 15KHz(u=0) 14 10 1 30KHz(u=1) 14 20 2 60KHz(u=2) 14 40 4 120KHz(u=3) 14 80 8 240KHz(u=4) 14 160 16

[0051] *N slot symb : The number of symbols in a time slot

[0052] *N frame,u slot : Number of time slots in a frame

[0053] *N subframe,u slot : Number of time slots in a subframe

[0054] Table 2 shows that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to the SCS when the extended CP is used.

[0055] [Table 2]

[0056] SCS(15*2^u) <![CDATA[N slot symb ]]> <![CDATA[N frame,u slot ]]> <![CDATA[N subframe,u slot ]]> 60KHz(u=2) 12 40 4

[0057] The structure of the frame is only an example. The number of subframes, the number of time slots, and the number of symbols in a frame may vary.

[0058] In the NR system, OFDM parameter sets (e.g., SCS) may be configured differently for multiple cells aggregated for one UE. Therefore, the (absolute time) duration of a time resource (e.g., SF, time slot, or TTI) (referred to as a time unit (TU) for simplicity) consisting of the same number of symbols may be configured differently between aggregated cells. Here, the symbol may include an OFDM symbol (or CP-OFDM symbol) and an SC-FDMA symbol (or a discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbol).

[0059] Figure 3 A resource grid showing a time slot. A time slot includes multiple symbols in the time domain. For example, when a normal CP is used, a time slot includes 14 symbols. However, when an extended CP is used, a time slot includes 12 symbols. A carrier includes multiple subcarriers in the frequency domain. A resource block (RB) is defined as a plurality of consecutive subcarriers (e.g., 12 consecutive subcarriers) in the frequency domain. A bandwidth part (BWP) may be defined as a plurality of consecutive physical RBs (PRBs) in the frequency domain and corresponds to a single parameter set (e.g., SCS, CP length, etc.). A carrier may include up to N (e.g., five) BWPs. Data communication may be performed via enabled BWPs, and only one BWP may be enabled for a UE. In a resource grid, each element is referred to as a resource element (RE), and a complex symbol may be mapped to each RE.

[0060] Figure 4An exemplary mapping of physical channels in a time slot is illustrated. PDCCH may be sent in the DL control region, and PDSCH may be sent in the DL data region. PUCCH may be sent in the UL control region, and PUSCH may be sent in the UL data region. A guard period (GP) provides a time gap for a transmission mode to reception mode switch or a reception mode to transmission mode switch at a BS and a UE. Some symbols in a subframe at the time of a DL to UL switch may be configured as a GP.

[0061] Each physical channel is described in more detail below.

[0062] PDCCH delivers DCI. For example, PDCCH (i.e., DCI) can carry information about the transport format and resource allocation of the DL shared channel (DL-SCH), resource allocation information of the uplink shared channel (UL-SCH), paging information about the paging channel (PCH), system information about DL-SCH, information about resource allocation of higher-layer control messages (such as RAR sent on PDSCH), transmit power control commands, information about activation / release of configured scheduling, etc. DCI includes a cyclic redundancy check (CRC). Depending on the owner or purpose of the PDCCH, the CRC is masked with various identifiers (IDs) (e.g., radio network temporary identifiers (RNTI)). For example, if the PDCCH is used for a specific UE, the CRC is masked by the UE ID (e.g., cell RNTI (C-RNTI)). If the PDCCH is used for a paging message, the CRC is masked by the paging RNTI (P-RNTI). If the PDCCH is used for system information (e.g., system information block (SIB)), the CRC is masked by the system information RNTI (SI-RNTI). When the PDCCH is used for RAR, the CRC is masked by a random access RNTI (RA-RNTI).

[0063] The PDCCH includes 1, 2, 4, 8 or 16 control channel elements (CCEs) depending on its aggregation level (AL). CCE is a logical allocation unit for providing a specific code rate for the PDCCH according to the radio channel state. CCE includes 6 resource element groups (REGs), each REG is defined by one OFDM symbol multiplied by one (P)RB. The PDCCH is transmitted in a control resource set (CORESET). A CORESET is defined as a set of REGs with a given parameter set (e.g., SCS, CP length, etc.). Multiple CORESETs for one UE can overlap with each other in the time / frequency domain. The CORESET can be configured by system information (e.g., master information block (MIB)) or UE-specific higher layer signaling (e.g., radio resource control (RRC) signaling). Specifically, the number of RBs and the number of symbols (up to 3) in the CORESET can be configured by higher layer signaling.

[0064] For PDCCH reception / detection, the UE monitors PDCCH candidates. PDCCH candidates are CCEs that the UE should monitor to detect PDCCH. Depending on the AL, each PDCCH candidate is defined as 1, 2, 4, 8 or 16 CCEs. Monitoring includes (blind) decoding of PDCCH candidates. The set of PDCCH candidates decoded by the UE is defined as the PDCCH search space (SS). The SS can be a common search space (CSS) or a UE-specific search space (USS). The UE can obtain DCI by monitoring PDCCH candidates in one or more SSs configured by MIB or higher layer signaling. Each CORESET is associated with one or more SSs, and each SS is associated with one CORESET. The SS can be defined based on the following parameters.

[0065] -controlResourceSetId: CORESET associated with SS.

[0066] - monitoringSlotPeriodicityAndOffset: PDCCH monitoring periodicity (in time slot units) and PDCCH monitoring offset (in time slot units).

[0067] - monitoringSymbolsWithinSlot: PDCCH monitoring symbols in a slot (eg, the first symbol of a CORESET).

[0068] -nrofCandidates: The number of PDCCH candidates for each AL={1,2,4,8,16} (one of 0, 1, 2, 3, 4, 5, 6 and 8).

[0069] * The timing (eg, time / frequency resource) at which the UE is to monitor a PDCCH candidate is defined as a PDCCH (monitoring) timing. One or more PDCCH (monitoring) timings may be configured in a time slot.

[0070] Table 3 shows the characteristics of each SS.

[0071] [Table 3]

[0072]

[0073] Table 4 shows the DCI format transmitted on the PDCCH.

[0074] [Table 4]

[0075]

[0076] DCI format 0_0 can be used to schedule TB-based (or TB-level) PUSCH, and DCI format 0_1 ​​can be used to schedule TB-based (or TB-level) PUSCH or code block group (CBG) (or CBG level) PUSCH. DCI format 1_0 can be used to schedule TB-based (or TB-level) PDSCH, and DCI format 1_1 can be used to schedule TB-based (or TB-level) PDSCH or CBG (or CBG level) based PDSCH (DL grant DCI). DCI format 0_0 / 0_1 can be referred to as UL grant DCI or UL scheduling information, and DCI format 1_0 / 1_1 can be referred to as DL grant DCI or DL ​​scheduling information. DCI format 2_0 is used to deliver dynamic slot format information (e.g., dynamic slot format indicator (SFI)) to the UE, and DCI format 2_1 is used to deliver DL preemption information to the UE. DCI format 2_0 and / or DCI format 2_1 may be delivered to a corresponding group of UEs on a group-common PDCCH, which is a PDCCH for a group of UEs.

[0077] DCI format 0_0 and DCI format 1_0 may be referred to as fallback DCI formats, while DCI format 0_1 ​​and DCI format 1_1 may be referred to as non-fallback DCI formats. In the fallback DCI format, the DCI size / field configuration remains the same regardless of the UE configuration. In contrast, the DCI size / field configuration varies in the non-fallback DCI format depending on the UE configuration.

[0078] PDSCH transmits DL data (e.g., DL shared channel transport block (DL-SCH TB)) and uses a modulation scheme such as quadrature phase shift keying (QPSK), hexadecimal quadrature amplitude modulation (16QAM), 64QAM or 256QAM. TB is encoded into codewords. PDSCH can deliver up to two codewords. Scrambling and modulation mapping can be performed on the basis of codewords, and the modulation symbols generated from each codeword can be mapped to one or more layers. Each layer is mapped to a resource together with a demodulation reference signal (DMRS), and an OFDM symbol signal is generated from a mapped layer with DMRS and sent through a corresponding antenna port.

[0079] PUCCH delivers uplink control information (UCI). UCI includes the following information.

[0080] -SR (Scheduling Request): Information used to request UL-SCH resources.

[0081] -HARQ (Hybrid Automatic Repeat Request) -ACK (Acknowledgement): A response to a DL data packet (e.g., a codeword) on the PDSCH. HARQ-ACK indicates whether the DL data packet has been successfully received. In response to a single codeword, a 1-bit HARQ-ACK can be sent. In response to two codewords, a 2-bit HARQ-ACK can be sent. The HARQ-ACK response includes a positive ACK (abbreviated as ACK), a negative ACK (NACK), a discontinuous transmission (DTX), or NACK / DTX. The term HARQ-ACK is used interchangeably with HARQ ACK / NACK and ACK / NACK.

[0082] -CSI (Channel State Information): Feedback information for DL ​​channels. Feedback information related to Multiple Input Multiple Output (MIMO) includes RI and PMI.

[0083] Table 5 illustrates an exemplary PUCCH format. Based on PUCCH transmission duration, the PUCCH format may be divided into short PUCCH (formats 0 and 2) and long PUCCH (formats 1, 3, and 4).

[0084] [Table 5]

[0085]

[0086] PUCCH format 0 conveys up to 2 bits of UCI and is mapped in a sequence-based manner for transmission. Specifically, the UE sends a specific UCI to the BS by sending one of multiple sequences on the PUCCH of PUCCH format 0. The UE sends the PUCCH of PUCCH format 0 in the PUCCH resources for the corresponding SR configuration only when the UE sends a positive SR.

[0087] PUCCH format 1 transmits up to 2 bits of UCI in the time domain, and spreads the modulation symbol of UCI in the time domain using an orthogonal cover code (OCC) (which is configured differently depending on whether frequency hopping is performed). DMRS is transmitted with a symbol in which no modulation symbol is transmitted (ie, transmitted in time division multiplexing (TDM)).

[0088] PUCCH format 2 conveys more than 2 bits of UCI, and the modulation symbols of DCI are sent with DMRS in frequency division multiplexing (FDM). DMRS are located in symbols #1, #4, #7, and #10 of a given RB with a density of 1 / 3. Pseudo-noise (PN) sequences are used for DMRS sequences. For 2-symbol PUCCH format 2, frequency hopping can be activated.

[0089] PUCCH format 3 does not support UE multiplexing in the same PRBS and conveys UCI of more than 2 bits. In other words, the PUCCH resources of PUCCH format 3 do not include OCC. The modulation symbols and DMRS are transmitted in TDM.

[0090] PUCCH format 4 supports multiplexing of up to 4 UEs in the same PRBS and delivers more than 2 bits of UCI. In other words, the PUCCH resources of PUCCH format 3 include OCC. The modulation symbols and DMRS are transmitted in TDM.

[0091] The PUSCH delivers UL data (e.g., UL shared channel transport block (UL-SCH TB)) and / or UCI based on a CP-OFDM waveform or a DFT-s-OFDM waveform. When the PUSCH is transmitted with a DFT-s-OFDM waveform, the UE transmits the PUSCH by transform precoding. For example, when transform precoding is not possible (e.g., disabled), the UE can transmit the PUSCH with a CP-OFDM waveform, and when transform precoding is possible (e.g., enabled), the UE can transmit the PUSCH with a CP-OFDM waveform or a DFT-s-OFDM waveform. PUSCH transmission can be dynamically scheduled by a UL grant in a DCI, or semi-statically scheduled (configured scheduling or configured grant) by higher layer (e.g., RRC) signaling (and / or layer 1 (L1) signaling such as PDCCH). PUSCH transmission can be performed in a codebook-based or non-codebook-based manner.

[0092] Figure 5 An exemplary ACK / NACK transmission process is shown. Figure 5 , the UE can detect the PDCCH in time slot #n. The PDCCH includes DL scheduling information (e.g., DCI format 1_0 or DCI format 1_1). The PDCCH indicates the DL assignment-to-PDSCH offset K0 and the PDSCH-to-HARQ-ACK reporting offset K1. For example, DCI format 1_0 and DCI format 1_1 may include the following information.

[0093] - Frequency domain resource assignment: indicates the RB set assigned to PDSCH

[0094] -Time domain resource assignment: Indicates K0 and the starting position (e.g., OFDM symbol index) and length (e.g., number of OFDM symbols) of the PDSCH in the time slot

[0095] -PDSCH-to-HARQ_feedback timing indicator: indicates K1

[0096] -HARQ process number (4 bits): Indicates the HARQ process ID of the data (e.g., PDSCH or TB)

[0097] - PUCCH resource indicator (PRI): indicates a PUCCH resource to be used for UCI transmission among a plurality of PUCCH resources in a PUCCH resource set.

[0098] After receiving the PDSCH in slot #(n+K0) according to the scheduling information of slot #n, the UE may transmit UCI on the PUCCH in slot #(n+K1). The UCI may include a HARQ-ACK response to the PDSCH. Figure 5 Based on the assumption that the SCS of PDSCH is equal to the SCS of PUCCH, and slot #n1 = slot #(n+K0), for the sake of convenience, it should not be understood as limiting the present invention. When the SCS is different, K1 can be indicated / interpreted based on the SCS of PUCCH.

[0099] In the case where the PDSCH is configured to carry a maximum of 1 TB, the HARQ-ACK response may be configured in one bit. In the case where the PDSCH is configured to carry up to two TBs, the HARQ-ACK response may be configured in two bits if spatial bundling is not configured, and may be configured in one bit if spatial bundling is configured. When slot #(n+K1) is designated as the HARQ-ACK transmission timing for multiple PDSCHs, the UCI sent in slot #(n+K1) includes HARQ-ACK responses for multiple PDSCHs.

[0100] Whether the UE should perform spatial bundling for HARQ-ACK responses may be configured for each cell group (e.g., via RRC / higher layer signaling). For example, spatial bundling may be configured for each individual HARQ-ACK response sent on the PUCCH and / or a HARQ-ACK response sent on the PUSCH.

[0101] Spatial bundling may be supported when up to two (or two or more) TBs (or codewords) may be received at one time (or schedulable by one DCI) in the corresponding serving cell (e.g., when the higher layer parameter maxNrofCodeWordsScheduledByDCI indicates 2 TBs). More than four layers may be used for 2-TB transmission, and up to four layers may be used for 1-TB transmission. As a result, when spatial bundling is configured for the corresponding cell group, spatial bundling may be performed for serving cells that may schedule more than four layers among the serving cells of the cell group. A UE that desires to send a HARQ-ACK response via spatial bundling may generate a HARQ-ACK response by performing a (bitwise) logical AND operation on A / N bits for multiple TBs.

[0102] For example, assuming that a UE receives a DCI that schedules two TBs and receives the two TBs on a PDSCH based on the DCI, the UE that performs spatial bundling can generate a single A / N bit by a logical AND operation between a first A / N bit for a first TB and a second A / N bit for a second TB. As a result, when both the first TB and the second TB are ACK, the UE reports an ACK bit value to the BS, and when at least one of the TBs is NACK, the UE reports a NACK bit value to the BS.

[0103] For example, when only one TB is actually scheduled in a serving cell configured to receive two TBs, the UE may generate a single A / N bit by performing a logical AND operation on the A / N bits for one TB and a bit value 1. As a result, the UE reports the A / N bits for one TB to the BS.

[0104] There are multiple parallel DL HARQ processes for DL ​​transmission at the BS / UE. Multiple parallel HARQ processes enable continuous DL transmission while the BS is waiting for HARQ feedback indicating successful or failed reception of the previous DL transmission. Each HARQ process is associated with a HARQ buffer in the media access control (MAC) layer. Each DL HARQ process manages state variables such as the number of MAC physical data unit (PDU) transmissions, HARQ feedback for the MAC PDUs in the buffer, and the current redundancy version. Each HARQ process is identified by a HARQ process ID.

[0105] Figure 6 An exemplary PUSCH transmission process is shown in FIG. Figure 6 , the UE may detect the PDCCH in slot #n. The PDCCH includes DL scheduling information (eg, DCI format 1_0 or 1_1). The DCI format 1_0 or 1_1 may include the following information.

[0106] - Frequency domain resource assignment: indicates the RB set assigned to the PUSCH.

[0107] -Time domain resource assignment: Indicates the slot offset K2 and the duration (e.g., number of OFDM symbols) and starting position (e.g., OFDM symbol index) of the PUSCH in one slot. The starting symbol and length of the PUSCH can be indicated by the start and length indicator value (SLIV) or separately.

[0108] Then, according to the scheduling information in time slot #n, the UE can send PUSCH in time slot #(n+K2). PUSCH includes UL-SCH TB.

[0109] Figure 7 Figure 1 shows an exemplary UCI multiplexing in PUSCH. When multiple PUCCH resources overlap with PUSCH resources in a slot and simultaneous PUCCH-PUSCH transmission is not configured in the slot, UCI can be sent on PUSCH (UCI piggybacking or PUSCH piggybacking) as shown. Figure 7 In the illustrated case, HARQ-ACK and CSI are carried in PUSCH resources.

[0110] For HARQ-ACK piggybacking to PUSCH in NR Rel.16, when the payload of HARQ-ACK is 2 bits or less, PUSCH data REs (and / or CSI part 2REs) are punctured, and when the payload of HARQ-ACK is greater than 2 bits, rate matching is performed. Table 6 describes HARQ-ACK rate matching for UCI in TS 38.212.

[0111] [Table 6]

[0112]

[0113]

[0114]

[0115]

[0116] In Table 6, the beta offset "β offset PUSCH " is related to the amount of resources to be used for HARQ-ACK and CSI reporting during PUSCH transmission. offset The set s can be configured by higher layer signaling. A specific set can be used semi-statically, or β offsetThe set may be indicated dynamically via DCI (e.g., DCI format 0_1 / 0_2). offset In the indication scheme, the beta offset indication field of the DCI includes four beta offsets configured for the UE. offset Two bits from one of the sets. Each β offset The set includes three beta offset value, two β values ​​for CSI part 1 offset values ​​and two β values ​​for CSI part 2 offset value, and select a specific β according to the corresponding payload size offset For example, the first beta offset HARQ-ACK The value may be used to send M HARQ-ACKs on the PUSCH, and the second β offset HARQ-ACK The value may be used to send N HARQ-ACKs on the PUSCH.

[0117] The meanings of the terms used in this article are summarized below. To help understand these terms, please refer to Figure 5 / 6 and its description.

[0118] - K0 (DL assignment to PDSCH offset): the slot interval between the DCI transmission slot and the PDSCH transmission slot (scheduled by the corresponding DCI).

[0119] - SLIV (Start and Length Indicator Value): Information on the start symbol and symbol duration (or end symbol) of a PDSCH (PDSCH opportunity).

[0120] - Mapping type: Information indicating whether the position of the DMRS symbol of the PDSCH is determined based on a symbol index within a slot duration or within a PDSCH duration.

[0121] - TDRA (Time Domain Resource Allocation) table: includes multiple {K0, SLIV, mapping type} combinations (configured by RRC) (one combination is mapped to each of the multiple rows in the table). A specific row is indicated by DCI.

[0122] - K1 (PDSCH-to-HARQ_Feedback timing indicator): the time slot interval between the PDSCH transmission time slot and the HARQ-ACK transmission time slot (for corresponding PDSCH reception).

[0123] Multiplexing between UL channels with different priorities (and / or different TTI lengths)

[0124] In order to support data transmission / services for which reliability / delay performance is important (such as URLLC), the service / protection priority (e.g., low priority (LP) or high priority (HP)) can be semi-statically configured for the UE (via RRC signaling, etc.) or dynamically indicated to the UE (via DCI / MAC signaling).

[0125] Specifically, a priority indicator has been introduced into some DCI formats in NR Rel.16 (e.g., DCI formats 1_1 / 1_2 for DL ​​and DCI formats 0_1 / 0_2 for UL). When a priority indicator is to be provided for a corresponding DCI format through higher layer signaling, the UE performs blind decoding on the DCI format assuming that the priority indicator exists. In the absence of explicit signaling through higher layer signaling indicating that a priority indicator is to be used for a DCI format, the UE performs blind decoding assuming that the priority indicator field is not included in the DCI format. When priority information is not provided for the corresponding DL / UL signal, the UE may assume that the DL / UL signal has a LP (e.g., priority index = 0). Those skilled in the art will appreciate that the priority indicator of the DCI is only one of various means for indicating / configuring priority, and not the only method.

[0126] In the above-mentioned prioritization example, a lower priority index may be configured / indicated for LP and a higher priority index may be configured / indicated for HP, or a lower bit value (e.g., bit '0') may be configured / indicated for LP and a higher bit value (e.g., bit '1') may be configured / indicated for HP.

[0127] For example, a priority (e.g., LP or HP) may be configured / indicated for each PUCCH / PUSCH resource configured / indicated for each UCI type (e.g., HARQ-ACK, SR, and / or CSI) or corresponding UCI transmission. For example, LP / HP may be indicated for HARQ-ACK of PDSCH by a DL grant DCI that schedules PDSCH. For example, LP / HP may be indicated for (non-periodic) CSI by a DCI (e.g., a UL grant DCI that schedules PUSCH).

[0128] In another example, (i) a PUCCH resource set may be independently configured for each priority, and / or (ii) a maximum UCI coding rate for PUCCH transmission may be independently configured for each priority. In another example, (iii) a beta offset β for encoding UCI on PUSCH (e.g., for HARQ-ACK and CSI part 1 / 2, see Table 6) may be independently configured for each priority. offset, and / or (iv) the HARQ-ACK codebook type may be independently configured for each priority. At least one or a combination of (i) to (iv) may be used.

[0129] In addition, in order to support low-latency based URLLC transmission, a TTI length based on a sub-slot duration shorter than a TTI based on a slot duration in a conventional NR may be configured (especially for UCI / PUCCH / PUSCH transmission configured / indicated as having HP), and the UE / BS may be operated to quickly perform UL transmission in the sub-slot. For example, the sub-slot duration may be set to 7 symbols (e.g., 2 sub-slots are configured in one slot) or 2 symbols (e.g., 7 sub-slots are configured in one slot), which should not be interpreted as a limitation.

[0130] In conventional Rel-16, with respect to PUCCH / PUSCH transmission with each priority, (a) it is determined whether the UE processing timeline (e.g., i) the minimum processing time N1 between the reception time of (the end symbol of) PDSCH and the transmission time of (the start symbol of) the corresponding HARQ-ACK and / or ii) the minimum processing time N2 between the reception time of (the end symbol of) PDCCH and the transmission time of (the start symbol of) the corresponding PUSCH / PUCCH) is met, and (b) a UCI multiplexing process (in which a plurality of PUCCH / PUSCHs overlapping with each other in time are combined (multiplexed) into one UL channel) is performed. When the resultant LP PUCCH and the resultant HP PUCCH corresponding to the result of UCI multiplexing overlap with each other in time, only the HP PUCCH may be transmitted, and the LP transmission may be discarded. For example, when the time resources of the LP PUCCH with multiplexed LP UCI overlap with the time resources of the HP PUCCH with multiplexed HP UCI, the LP PUCCH is dropped and only the HP PUCCH is transmitted as defined in Rel.16.

[0131] In contrast, in Rel-17, LP and HP multiplexing may be configured, instead of priority-based discarding in the case of LP and HP overlap. Therefore, LP and HP multiplexing rules may be needed. The same or different TTI lengths may be configured for LP and HP. For example, a first TTI may be configured for LP, and a second TTI may be configured for HP. The first TTI may be longer than the second TTI, or vice versa.

[0132] Although the overlap between the time resources of the LP PUCCH and the time resources of the HP PUCCH is regarded as a specific example of the overlap between the LP and the HP, the present disclosure may be applied to various overlaps between UL / DL channels without being limited to the above example.

[0133] Under the assumption of LP PUCCH and HP PUCCH, for convenience, it is necessary to define UE operation according to the UCI type of the HP PUCCH overlapping with the LP PUCCH and / or the PUCCH format type of LP / HP and the overlap between one LP PUCCH and multiple PUCCHs (or multiple subslots configured for HP).

[0134] Examples of the present disclosure propose that different TTI lengths be configured for LP and HP (e.g., Figure 8 A UE operation method for UL multiplexing transmission in a situation (as illustrated) when one LP PUCCH temporally overlaps with one or more (multiple) (TDM) HP PUCCHs (eg, when the LP time resources and the HP time resources at least partially overlap with each other).

[0135] For the convenience of description, it is assumed below that the TTI length for LP transmission is set to the traditional time slot duration, and the TTI length for HP transmission is set to the sub-time slot duration. However, the proposal of the present disclosure can be applied even based on the same principle to the case where the same TTI length is configured for LP and HP (not limited to this assumption). In addition, although it is assumed below that the LP PUCCH is a PUCCH carrying HARQ-ACK and the HP PUCCH is a PUCCH carrying HARQ-ACK and / or SR, the proposal of the present disclosure can be applied even based on the same principle to the case where the LP / HP PUCCH is a PUCCH carrying any UCI type (e.g., HARQ-ACK, SR, or CSI) (not limited to the above assumption).

[0136] In addition, when it is said that the LP PUCCH overlaps with the HP PUCCH in time, this may imply that the corresponding LP PUCCH resource overlaps with the corresponding HP PUCCH resource in the same symbol, or the corresponding LP PUCCH resource overlaps with the HP subslot period including the HP PUCCH resource. For convenience, PUCCH formats 0 / 1 / 2 / 3 / 4 are referred to as PF0 / 1 / 2 / 3 / 4.

[0137] Figure 8 is a diagram illustrating the overlap between LP and HP.

[0138] exist Figure 8 , (a) may illustrate the overlap between one LP PUCCH and two HP PUCCHs, (b) / (c)) / (f) may illustrate the overlap between one LP PUCCH and one HP PUCCH, and (d) / (e) / (g) / (h) may illustrate no overlap between the LPPUCCH and the HP PUCCH.

[0139] exist Figure 8 Among them, (a) / (b) / (d) / (f) / (g) can illustrate the case where LP PUCCH is not limited to one HP subslot (for example, LP PUCCH spans multiple HP subslots), and (c) / (e) / (h) can illustrate the case where LP PUCCH is limited to one HP subslot.

[0140] [Proposal 1]

[0141] 1) Case 1

[0142] A. In some cases, one LP HARQ-ACK PUCCH may overlap with one or more (multiple) HP HARQ-ACK PUCCHs. The following exemplary specific scheduling may cause overlap: (a) the UE receives a first PDCCH carrying a first DCI from the BS, wherein i) the first DCI schedules a first PDSCH, ii) the first DCI has no priority indication information or has a priority indication indicating LP (e.g., 0), and iii) the first PUCCH resource for the first PDSCH is based on the first DCI (e.g., Figure 5 (b) the UE receives a second PDCCH carrying a second DCI from the BS, wherein iv) the second DCI schedules a second PDSCH, v) the second DCI includes priority indication information, and the priority indication indicates HP (e.g., 1), and vi) a second PUCCH resource for the second PDSCH is based on the second DCI (e.g., Figure 5 The first PUCCH resource and the second PUCCH resource may at least partially overlap with each other (in the time domain). However, the overlap between the LP HARQ-ACK PUCCH and the HP HARQ-ACK PUCCH may not necessarily be related to dynamic scheduling, and at least one of the LP HARQ-ACK PUCCH or the HP HARQ-ACK PUCCH may be related to a configured grant (e.g., SPS). In addition, the overlap between the LPHARQ-ACK PUCCH and the HP HARQ-ACK PUCCH may not necessarily be related to HARQ-ACK for the PDSCH, and at least one of the LP HARQ-ACK PUCCH or the HP HARQ-ACK PUCCH may be related to the reception of the PDCCH (e.g., SPS release). When one LP HARQ-ACK PUCCH overlaps with one or more (multiple) HPHARQ-ACK PUCCHs in the various examples above, the following operations may be performed.

[0143] i. The LP PUCCH may be multiplexed with a specific one of the HP PUCCHs (referred to as "HP PUCCH#1"), and the HARQ-ACK of the LP PUCCH may be multiplexed and transmitted on a specific HP PUCCH (referred to as "HP PUCCH#2") in the HP subslot including "HP PUCCH#1".

[0144] ii. Option 1

[0145] 1. HP PUCCH#1 can be determined as the first (or last) HP PUCCH overlapping with the LP PUCCH or the first (or last) HP PUCCH (overlapping with the LPPUCCH and) meeting the UE processing timeline (between DL channels (e.g., PDSCH / PDCCH) and UL channels (e.g., PUCCH / PUSCH) with the same priority (e.g., regarding the same priority) and between DL channels and UL channels with different priorities (e.g., regarding inter-priority)).

[0146] And / or HP PUCCH#1 may be determined as the HP PUCCH that (overlaps with the LP PUCCH and) carries most HP HARQ-ACK bits, and / or is configured with a PUCCH format (e.g., PF2 / 3 / 4 instead of PF0 / 1) that carries a UCI payload with a larger size.

[0147] iii. Option 2

[0148] 1. HP PUCCH#1 can be determined as the first (or last) HP PUCCH among the HP PUCCHs overlapping with the LP PUCCH that carries HP HARQ-ACK corresponding to the PDSCH scheduled by the DCI (i.e., dynamic HP HARQ-ACK), or the first (or last) HP PUCCH (among the HP PUCCHs overlapping with the LP PUCCH) that carries dynamic HP HARQ-ACK and meets the UE processing timeline (with respect to the same priority and between priorities).

[0149] In case there is no HP PUCCH satisfying the above conditions among the HP PUCCHs overlapped with the LP PUCCH, Option 1 may be applied.

[0150] iv. HP PUCCH#2 may be determined as a PUCCH resource different from HP PUCCH#1 (or the same PUCCH resource as HP PUCCH#1) according to the payload size of HP HARQ-ACK and / or LP HARQ-ACK.

[0151] 2) Case 2

[0152] A. When one LP HARQ-ACK PUCCH overlaps with one or more (multiple) HP SR PUCCHs, the following operations may be performed.

[0153] i.Alt 1

[0154] 1. The LP PUCCH can be multiplexed with a specific one of the HP PUCCHs (referred to as "HP PUCCH#1"), and the HARQ-ACK of the LP PUCCH can be multiplexed and transmitted on a specific HP PUCCH (referred to as "HP PUCCH#2") in the HP subslot including "HP PUCCH#1" (together with the SR of HP PUCCH#1).

[0155] LP PUCCH may include at least PUCCH formats 2 / 3 / 4.

[0156] 2. HP PUCCH#1 may be determined as the first (or last) HP PUCCH overlapping with the LP PUCCH or the first (or last) HP PUCCH (overlapping with the LPPUCCH and) satisfying the UE processing timeline (with respect to the same priority and between priorities).

[0157] In this case, in the presence of an HP HARQ-ACK PUCCH overlapping with an LP PUCCH (or an HP subslot including an HP HARQ-ACK PUCCH and overlapping with an LP PUCCH), the UE / BS may apply operation of case 1 with priority (over operation of case 2).

[0158] 3. HP PUCCH#2 can be determined as belonging to a specific HP PUCCH resource set (corresponding to / configured with the payload size of LP HARQ-ACK or the total UCI payload size calculated by adding the payload size of LP HARQ-ACK and the payload size of HP SR corresponding to HP PUCCH#1) / one of the multiple resources configured in the specific HP PUCCH resource set (for example, based on the following method).

[0159] - Option 1: HP PUCCH #2 may be determined as a PUCCH resource corresponding to a PUCCH resource indicator (PRI) indicated by the last DCI (scheduling LP PDSCH transmission) among resources of the HP PUCCH set.

[0160] - Option 2: HP PUCCH #2 may be determined as a PUCCH resource configured for a specific (eg, lowest) PRI value / state / index among the resources of the HP PUCCH set.

[0161] - Option 3: HP PUCCH#2 may be determined as the PUCCH resource (the resource configured for a specific (e.g., lowest) value / state / index among the resources) with the most UCI REs or the maximum supportable payload size among the resources of the HP PUCCH set (according to the number of UCI REs and the maximum UCI coding rate).

[0162] ii.Alt 2

[0163] 1. All HP PUCCHs may be multiplexed with LP PUCCHs (referred to as "LP PUCCH #1"), and SRs corresponding to HP PUCCHs may be multiplexed and transmitted on a specific LPPUCCH (referred to as "LP PUCCH #2") (together with HARQ-ACK of LP PUCCH #1).

[0164] -LP PUCCH may include at least PUCCH formats 2 / 3 / 4.

[0165] - In this case, in the presence of a HP HARQ-ACK PUCCH overlapping with a LP PUCCH (or a HP subslot including a HP HARQ-ACK PUCCH and overlapping with a LP PUCCH), the UE / BS may apply the operation of Case 1 with priority (over the operation of Case 2).

[0166] 2. LP PUCCH #2 may be determined as the same PUCCH resource as LP PUCCH #1 (or a different resource from LP PUCCH #1) according to the payload size of LP HARQ-ACK and / or HP SR.

[0167] In the case of a portion of the total UCI payload configured on LP PUCCH#2 corresponding to the HP SR, a bitmap can be configured that indicates positive or negative for each of multiple SRs (configuration / index) (rather than the traditional form of indicating only a specific one (positive) SR (configuration / index) among multiple HP SRs corresponding to the HP PUCCH).

[0168] Alternatively, a bitmap indicating, for each opportunity of the HP SR PUCCH, whether the SR information is positive or negative in the opportunity may be configured.

[0169] 3. LP PUCCH#2 can be determined as belonging to an LP PUCCH resource set (corresponding to / configured with a payload size of LP HARQ-ACK or a total UCI payload size calculated by adding the payload size of LP HARQ-ACK and the payload size of HP SR corresponding to HP PUCCH) / one of multiple resources configured in the HP PUCCH resource set (for example, based on the following method).

[0170] - Option 1: LP PUCCH #2 may be determined as a PUCCH resource corresponding to the PRI indicated by the last DCI (scheduling LP PDSCH transmission) among resources of the LP PUCCH set.

[0171] - Option 2: When DCI scheduling LP PDSCH has not been received (e.g., all received LP PDSCHs are SPS PDSCHs sent without scheduling DCI), LP PUCCH #2 can be determined as a specific SPS PUCCH resource configured for LP (corresponding to / configured for LP UCI size or a total UCI payload size calculated by adding the payload sizes of LP UCI and HP UCI).

[0172] 3) Case 3

[0173] A. When one LP PUCCH (eg, LP PUCCH carrying (LP) HARQ-ACK) overlaps with one or more (multiple) HP PUCCHs (eg, HARQ-ACK and / or SR PUCCHs) (including Case 1 and Case 2), the following operations may be performed.

[0174] i. The LP PUCCH can be multiplexed with a specific one of the HP PUCCHs (referred to as "HP PUCCH#1"), and the UCI of the LP PUCCH (e.g., HARQ-ACK and / or SR) can be multiplexed and transmitted on a specific HP PUCCH (referred to as "HP PUCCH#2") in the HP subslot including "HP PUCCH#1" (together with the UCI of HPPUCCH#1 (e.g., HARQ-ACK and / or SR)).

[0175] ii. Option 0

[0176] 1. In case there is a specific HP PUCCH configured / indicated for the first (or last) HP subslot (overlapping with the LP PUCCH and) that temporally overlaps with the LP PUCCH resource, HP PUCCH #1 may be determined as the specific HP PUCCH.

[0177] - In case there is no HP PUCCH (overlapping with LP PUCCH) in the first (or last) HP subslot overlapping with LP PUCCH, the transmission of LP PUCCH and corresponding LP UCI (eg, HARQ-ACK) may be dropped.

[0178] iii. Option 1

[0179] 1. HP PUCCH#1 may be determined as the first (or last) HP PUCCH overlapping with LP PUCCH or the first (or last) HP PUCCH (overlapping with LPPUCCH and) satisfying the UE processing timeline (with respect to the same priority and between priorities).

[0180] - In the event that there is no HP PUCCH satisfying the above conditions among the HP PUCCHs overlapped with the LP PUCCH, transmission of the LP PUCCH and the corresponding LP UCI (eg, HARQ-ACK) may be dropped.

[0181] 2. When repeated transmission is configured / indicated for at least one of the HP PUCCHs, PUCCH#1 may be determined as the first (or last) HP PUCCH (overlapping with the LP PUCCH) for which repetition is not configured / indicated.

[0182] - In the case that there is no HP PUCCH satisfying the above conditions among the HP PUCCHs overlapping with the LP PUCCH, HP PUCCH #1 may be determined as the first (or last) HP PUCCH overlapping with the LP PUCCH.

[0183] - Alternatively, in the case where there is no HP PUCCH satisfying the above conditions among the HP PUCCHs overlapping with the LP PUCCH, transmission of the LP PUCCH and the corresponding LP UCI (eg, HARQ-ACK) may be dropped.

[0184] iv. Option 2

[0185] 1. HP PUCCH#1 can be determined as the first (or last) HP PUCCH that carries HP HARQ-ACK among the HP PUCCHs overlapping with the LP PUCCH, or the first (or last) HP PUCCH that carries HP HARQ-ACK (among the HP PUCCHs overlapping with the LP PUCCH) and meets the UE processing timeline (with respect to the same priority and between priorities).

[0186] - In case there is no HP PUCCH satisfying the above conditions among the HP PUCCHs overlapped with the LP PUCCH, Option 1 may be applied.

[0187] 2. When repeated transmission is configured / indicated for at least one of the HP PUCCHs, HP PUCCH#1 may be determined as the first (or last) HP PUCCH carrying HP HARQ-ACK among the HP PUCCHs (overlapping with the LP PUCCH) for which repetition is not configured / indicated.

[0188] - In the case that there is no HP PUCCH satisfying the above conditions among the HP PUCCHs overlapping with the LP PUCCH, HP PUCCH#1 may be determined as the first (or last) HP PUCCH among the HP PUCCHs (overlapping with the LP PUCCH) for which repetition is not configured / indicated.

[0189] - Alternatively, in the case where there is no HP PUCCH satisfying the above condition among the HP PUCCHs overlapping with the LP PUCCH, HP PUCCH #1 may be determined as the first (or last) HP PUCCH overlapping with the LP PUCCH.

[0190] - Alternatively, in the case where there is no HP PUCCH satisfying the above conditions among the HP PUCCHs overlapping with the LP PUCCH, transmission of the LP PUCCH and the corresponding LP UCI (eg, HARQ-ACK) may be dropped.

[0191] v. Option 3

[0192] 1. HP PUCCH#1 can be determined as the first (or last) HP PUCCH among the HP PUCCHs overlapping with the LP PUCCH that carries HP HARQ-ACK (i.e., dynamic HP HARQ-ACK) corresponding to the reception of a PDSCH scheduled by DCI (or reception of DCI), or the first (or last) HP PUCCH (among the HP PUCCHs overlapping with the LP PUCCH) that carries dynamic HP HARQ-ACK and meets the UE processing timeline (with respect to the same priority and between priorities).

[0193] - In case there is no HP PUCCH satisfying the above conditions among the HP PUCCHs overlapped with the LP PUCCH, Option 1 may be applied.

[0194] 2. When repeated transmission is configured / indicated for at least one of the HP PUCCHs, HP PUCCH#1 can be determined as the first (or last) HP PUCCH carrying HP HARQ-ACK (i.e., dynamic HP HARQ-ACK) corresponding to the reception of PDSCH scheduled by DCI (or reception of DCI) among the HP PUCCHs that are not configured / indicated for repetition (overlapping with LP PUCCH).

[0195] - In the case that there is no HP PUCCH satisfying the above conditions among the HP PUCCHs overlapping with the LP PUCCH, HP PUCCH#1 may be determined as the first (or last) HP PUCCH (overlapping with the LP PUCCH) for which repetition is not configured / indicated.

[0196] - Alternatively, in the case where there is no HP PUCCH satisfying the above condition among the HP PUCCHs overlapping with the LP PUCCH, HP PUCCH #1 may be determined as the first (or last) HP PUCCH overlapping with the LP PUCCH.

[0197] - Alternatively, in the case where there is no HP PUCCH satisfying the above conditions among the HP PUCCHs overlapping with the LP PUCCH, transmission of the LP PUCCH and the corresponding LP UCI (eg, HARQ-ACK) may be dropped.

[0198] vi. HP PUCCH#2 may be determined as a PUCCH resource different from HP PUCCH#1 (or the same PUCCH resource as HP PUCCH#1) according to the payload size of HP UCI (e.g., HARQ-ACK and / or SR) and / or LP UCI (e.g., HARQ-ACK).

[0199] [Proposal 2]

[0200] UL multiplexing transmission operations are proposed for each of the following cases: (a) the case where one LP PUSCH overlaps with multiple (TDM) HP PUCCHs (e.g., HP HARQ-ACK) in time, (b) the case where one HP PUSCH overlaps with multiple (TDM) LP PUCCHs (e.g., LP HARQ-ACK) in time, (c) the case where one LP PUCCH (LP PUCCH carrying (LP) HARQ-ACK) overlaps with multiple (TDM) HP PUSCHs in time, and the case where one HP PUCCH (e.g., HARQ-ACK) overlaps with multiple (TDM) LP PUSCHs in time.

[0201] When it is said that the LP PUCCH overlaps with the HP PUSCH in time, this may imply that the corresponding LP PUCCH resources overlap with the corresponding HP PUSCH resources in the same symbol or that the LP PUCCH resources overlap (at least partially) with the HP time slot / sub-time slot including the HP PUSCH resources. In addition, when it is said that the LP PUSCH overlaps with the HP PUCCH, this may imply that the corresponding LPPUSCH resources overlap with the corresponding HP PUCCH resources in the same symbol or that the LP PUSCH resources overlap (at least partially) with the HP time slot / sub-time slot including the HP PUCCH resources.

[0202] 1) Case 0

[0203] A. When simultaneous transmission of PUCCH and PUSCH existing in different frequency resources (e.g., frequency bands or cells) and configured / indicated to have different priorities is enabled, and the cell carrying the (HARQ-ACK) PUCCH is changed by a specific pattern configured semi-statically or a dynamic indication of the DCI, the UE may not expect a situation in which one LP PUSCH is configured / indicated to temporally overlap with multiple (TDM) HP PUCCHs (e.g., HP PUCCHs including HARQ-ACK) in the same band (or cell) (e.g., this situation is considered to be an error situation), or when this situation occurs, the UE may discard the LP PUSCH transmission.

[0204] i. Therefore, even if one LP PUSCH temporally overlaps with multiple (TDM) HP PUCCHs (e.g., HP PUCCH carrying HARQ-ACK), the UE can perform LP PUSCH transmission (without discarding it) when only one HP PUCCH (among multiple HP PUCCHs) is configured / indicated for the same frequency band as the LP PUSCH (this case is not considered an error case).

[0205] 2) Case 1

[0206] A. When one HP PUSCH overlaps with multiple LP PUCCHs (eg, LPPUCCHs carrying (LP) HARQ-ACK) in time, the UE may operate as follows.

[0207] i. The LP UCI of a specific one LP PUCCH (referred to as "LPPUCCH#1") among multiple LP PUCCHs may be multiplexed on the HP PUSCH, while the remaining LP PUCCH transmissions except for the LP PUCCH#1 may be dropped.

[0208] ii. Option 1

[0209] 1. LP PUCCH#1 may be determined as the first (or last) LP PUCCH overlapping with HP PUSCH or the first (or last) LP PUCCH (overlapping with HPPUSCH and) satisfying the UE processing timeline (with respect to the same priority and between priorities).

[0210] - In the case that there is no LP PUCCH satisfying the above conditions among the LP PUCCHs overlapped with the HP PUSCH, transmission of the LP PUCCH and the corresponding LP UCI (eg, HARQ-ACK) may be dropped.

[0211] iii. Option 2

[0212] 1. LP PUCCH #1 may be determined as an LP PUCCH of LP UCI (eg, HARQ-ACK) having a maximum (or minimum) payload size among LP PUCCHs overlapped with HP PUSCH.

[0213] - When there are multiple LPPUCCHs of LP UCI (eg, HARQ-ACK) having the largest (or smallest) payload size, LP PUCCH #1 may be determined as the temporally first (or last) LP PUCCH among the multiple LP PUCCHs.

[0214] iv. When i) an HP (or LP) PUSCH overlaps with ii) one or more LP PUCCHs (e.g., LP PUCCH carrying (LP)HARQ-ACK) and iii) a specific PUCCH including (multiplexed) HP UCI (e.g., HARQ-ACK) and LP UCI (e.g., HARQ-ACK), the UE may multiplex iii) the HP UCI and LPUCI of the specific PUCCH on i) the HP (or LP) PUSCH and discard ii) the remaining LP PUCCH transmissions except the transmission.

[0215] 3) Case 2

[0216] A. When one LP PUCCH (eg, LP PUCCH carrying (eg, (LP)HARQ-ACK)) temporally overlaps with multiple HP PUSCHs, the UE may operate as follows.

[0217] i. The LP UCI of the LPPUSCH may be multiplexed on a specific one of the HP PUSCHs (referred to as "HP PUSCH#1").

[0218] ii. Option 1

[0219] HP PUSCH#1 may be determined as the first (or last) HP PUSCH overlapping with the LP PUCCH or the first (or last) HP PUSCH (overlapping with the LPPUCCH and) satisfying the UE processing timeline (with respect to the same priority and between priorities).

[0220] - In the event that there is no HP PUSCH satisfying the above conditions among the HP PUSCHs overlapped with the LP PUCCH, transmission of the LP PUCCH and the corresponding LP UCI (eg, HARQ-ACK) may be dropped.

[0221] iii. Option 2

[0222] 1. HP PUSCH #1 may be determined as the first (or last) HP PUSCH that is not indicated as carrying an aperiodic CSI report among the HP PUSCHs overlapping with the LP PUCCH.

[0223] - When aperiodic CSI reporting is indicated on all HP PUSCHs, Option 1 may be applied.

[0224] iv. Option 3

[0225] 1. HP PUSCH#1 may be determined as the HP PUSCH having the maximum (or minimum) beta offset parameter value βoffset indicated (by DCI) to calculate the number of LP HARQ-ACK mapped REs (on the HP PUSCH) among the HP PUSCHs overlapping with the LP PUCCH.

[0226] - When there are multiple HP PUSCHs having a maximum (or minimum) beta offset parameter value βoffset indicated for LP HARQ-ACK, HP PUSCH #1 may be determined as the temporally first (or last) HPPUSCH among the multiple HP PUSCHs.

[0227] v. Option 4

[0228] 1. HP PUSCH #1 may be determined as the first (or last) HP PUSCH among the HP PUSCHs overlapping with the LP PUCCH that has a non-zero value as the β offset indicated (by DCI) for the LP HARQ-ACK (on the HP PUSCH).

[0229] - When the value of βoffset indicated for LP HARQ-ACK is zero for all HP PUSCHs, the UE may drop the LP PUCCH and the corresponding LP HARQ-ACK transmission.

[0230] 2. (In a further generalization,) when a PUCCH including LP HARQ-ACK overlaps in time with one or more HP (or LP) PUSCHs in one or more (multiple) carriers / cells, it can be specified that the UE (when selecting a PUSCH for UCI multiplexing) first selects a PUSCH from the HP (or LP) PUSCHs having a non-zero value as the β offset indicated (by the DCI) for the LP HARQ-ACK.

[0231] vi. Option 5

[0232] 1. HP PUSCH#1 may be determined as the HP PUSCH having the maximum (or minimum) value indicated (by DCI) as the size of the LP HARQ-ACK payload (or as the number of LP HARQ-ACK bits) to be multiplexed on the HP PUSCH among the HP PUSCHs overlapping with the LP PUCCH.

[0233] -When there are multiple HP PUSCHs having a maximum (or minimum) value indicated (by DCI) as the LP HARQ-ACK payload size (or as the number of LP HARQ-ACK bits), HP PUSCH#1 can be determined as the first (or last) HP PUSCH in time among them.

[0234] vii. Option 6

[0235] 1. HP PUSCH #1 may be determined as the first (or last) HP PUSCH among the HP PUSCHs overlapping with the LP PUCCH having a non-zero value indicated (by the DCI) as the LP HARQ-ACK payload size (or as the number of LP HARQ-ACK bits) to be multiplexed on the HP PUSCH.

[0236] - When the value indicated as the LP HARQ-ACK payload size (or as the number of LP HARQ-ACK bits) is zero for all HP PUSCHs, the UE may drop the LP PUCCH and the corresponding LP HARQ-ACK transmissions.

[0237] 2. (In further generalization,) when a PUCCH including LP HARQ-ACK overlaps with multiple HP (or LP) PUSCHs in one or more (multiple) carriers / cells, it can be specified that the UE (when selecting a PUSCH for UCI multiplexing) first selects (via DCI) a PUSCH from among the HP (or LP) PUSCHs that has a non-zero value as the LP HARQ-ACK payload size (or as the number of LPHARQ-ACK bits).

[0238] viii. Option 7

[0239] 1. (Options 2 / 4 / 6 are summarized as) HP PUSCH#1 may be determined as the first (or last) HP PUSCH among the HP PUSCHs overlapping with the LP PUCCH that does not result in discarding of LP HARQ-ACK mapping / transmission.

[0240] - When LP HARQ-ACK mapping / transmission should be dropped for all HP PUSCHs, the UE may drop the LP PUCCH and the corresponding LP HARQ-ACK transmission.

[0241] 2. (In further generalization) when a PUCCH including LP HARQ-ACK temporally overlaps with one or more HP (or LP) PUSCHs in one or more (multiple) carriers / cells, it can be specified that the UE (when selecting a PUSCH for UCI multiplexing) first selects a PUSCH from the HP (or LP) PUSCH that does not result in discarded LP HARQ-ACK mapping / transmission.

[0242] 4) Case 3

[0243] A. When one HP PUCCH (eg, HP PUCCH carrying (HP) HARQ-ACK) temporally overlaps with multiple LPPUSCHs, the UE may operate as follows.

[0244] i. The HP UCI of the HP PUCCH may be multiplexed on a specific one LP PUSCH (referred to as "LP PUSCH #1") among a plurality of LP PUSCHs.

[0245] ii. Option 1

[0246] 1. LP PUSCH#1 may be determined as the first (or last) LP PUSCH overlapping with the HP PUCCH or the first (or last) LPPUSCH (overlapping with the HP PUCCH and) satisfying the UE processing timeline (with respect to the same priority and between priorities).

[0247] - In the case that there is no LP PUSCH satisfying the above conditions among the LP PUSCHs overlapped with the HP PUCCH, the transmission of the LP PUSCH may be dropped.

[0248] iii. Option 2

[0249] 1. LP PUSCH #1 may be determined as the first (or last) LPPUSCH that is not indicated as carrying an aperiodic CSI report (and / or on which a periodic or semi-persistent CSI report is not multiplexed) among the LP PUSCHs overlapping with the HP PUCCH.

[0250] - Option 1 may be applied when aperiodic CSI reporting is indicated for all LP PUSCHs (and / or periodic or semi-persistent CSI reporting is multiplexed for all LP PUSCHs).

[0251] iv. Option 3

[0252] 1. LP PUSCH#1 may be determined as the LP PUSCH having the maximum (or minimum) beta offset parameter value βoffset indicated (by DCI) to calculate the number of HP HARQ-ACK mapped REs (on the LP PUSCH) among the LP PUSCHs overlapping with the HP PUCCH.

[0253] - When there are multiple LP PUSCHs having a maximum (or minimum) beta offset parameter value βoffset indicated for HP HARQ-ACK, LP PUSCH#1 may be determined as the temporally first (or last) LP PUSCH among the multiple LP PUSCHs.

[0254] 5) Case 4

[0255] A. In case an operation of multiplexing and transmitting UCI of a PUCCH on a PUSCH having a priority different from that of a PUCCH is enabled, the UE may exceptionally perform the following operations in the following cases.

[0256] B. Scenario 4-1A

[0257] i. When a HP CG PUSCH based on a configured grant (CG) (and / or a HP DG PUSCH scheduled by a DCI that does not include UL DAI information (e.g., total DAI or payload size information for HP HARQ-ACK and / or LP HARQ-ACK)) overlaps in time with a specific PUCCH that includes (multiplexed) HP UCI (e.g., HARQ-ACK) and LP UCI (e.g., HARQ-ACK) (and the HP CG PUSCH is selected for UCI multiplexing on the PUSCH), the UE may operate as follows.

[0258] 1. Option 1

[0259] - The UE may send only specific PUCCH while dropping the HP CG PUSCH transmission.

[0260] 2. Option 2

[0261] - The UE may multiplex only HP UCI (between HP UCI and LPUCI included in a specific PUCCH) on the HP CG PUSCH while dropping LP UCI transmission.

[0262] ii. Note: When the HP DG PUSCH based on dynamic (DG) DCI (and scheduled by DCI including UL DAI information (e.g., total DAI or payload size information for HP HARQ-ACK and / or LP HARQ-ACK)) overlaps in time with a specific PUCCH including (multiplexed) HP UCI (e.g., HARQ-ACK) and LP UCI (e.g., HARQ-ACK) (and the HP DG PUSCH is selected for UCI multiplexing on PUSCH), the UE can multiplex both the HP UCI and LP UCI included in the specific PUCCH on the HP DG PUSCH.

[0263] C. Scenario 4-1B

[0264] i. When the HP CG PUSCH based on the configured grant (CG) (and / or the HP DG PUSCH scheduled by DCI that does not include UL DAI information (e.g., total DAI or payload size information for HP HARQ-ACK and / or LP HARQ-ACK)) overlaps in time with the HP PUCCH (e.g., HP PUCCH carrying (HP) HARQ-ACK) and the LP PUCCH (e.g., LP PUCCH carrying (LP) HARQ-ACK) (and the HP CG PUSCH is selected for UCI multiplexing on PUSCH), the UE may operate as follows.

[0265] 1. Option 1

[0266] -The UE may multiplex the HP UCI of only the HP PUCCH on the HP CG PUSCH while dropping the LP PUCCH transmission.

[0267] ii. Note: When the HP DG PUSCH based on dynamic (DG) DCI (and indicated by DCI scheduling including UL DAI information (e.g., total DAI or payload size information for HP HARQ-ACK and / or LP HARQ-ACK)) overlaps in time with the HP PUCCH (e.g., HP PUCCH carrying (HP) HARQ-ACK) and the LP PUCCH (e.g., LP PUCCH carrying (LP) HARQ-ACK) (and the HP DG PUSCH is selected for UCI multiplexing on PUSCH), the UE can multiplex both the HP UCI and LP UCI of the HP PUCCH on the HP DGPUSCH.

[0268] D. Situation 4-1C

[0269] i. When the CG-based HP CG PUSCH (and / or HP DG PUSCH scheduled by DCI that does not include UL DAI information (e.g., total DAI or payload size information for HP HARQ-ACK and / or LP HARQ-ACK)) overlaps in time with the LPPUCCH (e.g., LP PUCCH carrying (LP) HARQ-ACK) (and the HP CG PUSCH is selected for UCI multiplexing on PUSCH), the UE may operate as follows.

[0270] 1. Option 1

[0271] - The UE may send only HP CG PUCCH (without UCI multiplexing on PUSCH) while dropping LP PUCCH transmission.

[0272] ii. NOTE: When the HP DG PUSCH based on DG DCI (and scheduled by DCI including UL DAI information (e.g., total DAI or payload size information for HP HARQ-ACK and / or LPHARQ-ACK)) overlaps in time with the LP PUCCH (e.g., LP PUCCH carrying (LP) HARQ-ACK) (and the HP DG PUSCH is selected for UCI multiplexing on PUSCH), the UE may multiplex the LP UCI of the LP PUCCH on the HP DG PUSCH.

[0273] E. Ambiguity regarding HP UL-SCH-related or HP UCI-related rate matching / RE mapping, which may be caused by misalignment of the payload size of LP HARQ-ACK (between UE and BS), may be prevented through the operations of Case 4-1A, Case 4-1B, and Case 4-1C.

[0274] F. Scenario 4-2A

[0275] i. When the CG-based LP CG PUSCH (and / or the LP DG PUSCH scheduled by DCI that does not include UL DAI information (e.g., total DAI or payload size information for LP HARQ-ACK and / or HP HARQ-ACK)) temporally overlaps with a specific PUCCH that includes (multiplexed) HP UCI (e.g., HARQ-ACK) and LP UCI (e.g., HARQ-ACK) (and the LP CG PUSCH is selected for UCI multiplexing on PUSCH), the UE may operate as follows.

[0276] 1. Option 1

[0277] -The UE may send only specific PUCCH while dropping LP CG PUCCH transmission.

[0278] ii. Note: When the DG-based LP DG PUSCH (indicated by DCI scheduling including UL DAI information (e.g., total DAI or payload size information for LP HARQ-ACK and / or HP HARQ-ACK)) temporally overlaps with a specific PUCCH including (multiplexed) HP UCI (e.g., HARQ-ACK) and LP UCI (e.g., HARQ-ACK) (and the LPDG PUSCH is selected for UCI multiplexing on the PUSCH), the UE can multiplex the HP UCI and LP UCI included in the specific PUCCH on the LP DG PUSCH.

[0279] G. Scenario 4-2B

[0280] i. When the CG-based LP CG PUSCH (and / or the LP DG PUSCH scheduled by the DCI that does not include UL DAI information (e.g., total DAI or payload size information for LP HARQ-ACK and / or HP HARQ-ACK)) temporally overlaps with the HP PUCCH (e.g., HP PUCCH carrying (HP) HARQ-ACK) and the LP PUCCH (e.g., LP PUCCH carrying (LP) HARQ-ACK) (and the LP CG PUSCH is selected for UCI multiplexing on the PUSCH), the UE may operate as follows.

[0281] 1. Option 1

[0282] -The UE may drop LP CG PUSCH transmission.

[0283] ii. Note: When the CG-based LP CG PUSCH (and / or the LP DG PUSCH scheduled by DCI that does not include UL DAI information (e.g., total DAI or payload size information for LPHARQ-ACK and / or HP HARQ-ACK)) temporally overlaps with the HP PUCCH (e.g., HP PUCCH carrying (HP) HARQ-ACK) and the LP PUCCH (e.g., LP PUCCH carrying (LP) HARQ-ACK) (and the LP CG PUSCH is selected for UCI multiplexing on PUSCH), the UE can multiplex both the HP UCI of the HP PUCCH and the LP UCI of the LP PUCCH on the LP DG PUSCH.

[0284] H. Situation 4-2C

[0285] i. When the CG-based LP CG PUSCH (and / or the LP DG PUSCH scheduled by DCI that does not include UL DAI information (e.g., total DAI or payload size information for LP HARQ-ACK and / or HP HARQ-ACK)) overlaps in time with the HPPUCCH (e.g., HP PUCCH carrying (HP) HARQ-ACK) (and the LP CG PUSCH is selected for UCI multiplexing on PUSCH), the UE may operate as follows.

[0286] 1. Option 1

[0287] -The UE may drop LP CG PUSCH transmission.

[0288] ii. Note: When the DG-based LP DG PUSCH (indicated by DCI scheduling including UL DAI information (e.g., total DAI or payload size information for LP HARQ-ACK and / or HP HARQ-ACK)) overlaps in time with the HP PUCCH (e.g., HP PUCCH carrying (HP) HARQ-ACK) (and LP CG PUSCH is selected for UCI multiplexing on PUSCH), the UE can multiplex the HP UCI of the HP PUCCH on the LP DG PUSCH.

[0289] I. Scenario 4-3A

[0290] i. When the LP fallback PUSCH scheduled by a specific (e.g., fallback) DCI (e.g., DCI format 0_0) (and / or the LP DG PUSCH scheduled by a DCI that does not include UL DAI information indication) overlaps in time with a specific PUCCH including (multiplexed) HP UCI (e.g., HARQ-ACK) and LP UCI (e.g., HARQ-ACK) (and the LP fallback PUSCH is selected for UCI multiplexing on the PUSCH), the UE may operate as follows.

[0291] 1. Option 1

[0292] - The UE may transmit only specific PUCCH while dropping LP fallback PUSCH transmission.

[0293] ii. Note: When an LP (or HP) non-fallback PUSCH scheduled by another (e.g., non-fallback) DCI (e.g., DCI format 0_1 ​​or 0_2) (and scheduled by a DCI indicated by UL DAI information) overlaps in time with a specific PUCCH including (multiplexed) HP UCI (e.g., HARQ-ACK) and LP UCI (e.g., HARQ-ACK) (and the LP (or HP) non-fallback PUSCH is selected for UCI multiplexing on the PUSCH), the UE can multiplex both the HP UCI and the LP UCI included in the specific PUCCH on the LP (or HP) non-fallback PUSCH.

[0294] J. Situation 4-3B

[0295] i. When the LP fallback PUSCH scheduled by a specific (e.g., fallback) DCI (e.g., DCI format 0_0) (and / or the LP DG PUSCH scheduled by a DCI that does not include UL DAI information indication) overlaps in time with the HP PUCCH (e.g., HP PUCCH carrying (HP) HARQ-ACK) (and / or the LP PUCCH (e.g., LP PUCCH carrying (LP) HARQ-ACK)) (and the LP fallback PUSCH is selected for UCI multiplexing on the PUSCH), the UE may operate as follows.

[0296] 1. Option 1

[0297] - The UE may discard LP fallback PUSCH transmission.

[0298] ii. Note: When an LP (or HP) non-fallback PUSCH scheduled by another (e.g., non-fallback) DCI (e.g., DCI format 0_1 ​​or 0_2) (and scheduled by a DCI indicated by including UL DAI information) overlaps in time with an HP PUCCH (e.g., HP PUCCH carrying (HP) HARQ-ACK) (and / or an LP PUCCH (e.g., LP PUCCH carrying (LP) HARQ-ACK)) (and the LP fallback PUSCH is selected for UCI multiplexing on the PUSCH), the UE may multiplex the HP UCI of the HP PUCCH (and / or the LP UCI of the LP PUCCH) on the LP (or HP) non-fallback PUSCH.

[0299] K. Ambiguity regarding HP UCI-related rate matching / RE mapping that may be caused by misalignment of LP HARQ-ACK payload size (between UE and BS) may be prevented through the operations of Case 4-2A, Case 4-2B, Case 4-2C, Case 4-3A, and Case 4-3B.

[0300] [Proposal 3]

[0301] 1) Case A

[0302] A. When one LP HARQ-ACK PUCCH (e.g., PUCCH format 0 / 1) overlaps with at least one HP SR PUCCH (e.g., PUCCH format 0 / 1), the UE may operate based on at least one of the following “ii.Alt A”, “iii.Alt B” and / or “iv.Alt C” according to an embodiment of the present disclosure.

[0303] i. Background

[0304] 1. In the case where one HP (positive) SR (eg, 1 HP PUCCH) overlaps with one LP HARQ-ACK (eg, 1 LP PUCCH), for example, for each PUCCH format, the following operations may be considered.

[0305] 2. Combination A: single HP SR PF0 + single LP HARQ-ACK PF0

[0306] - HARQ-ACK is sent in the resources of a single HARQ-ACK PF0 or a single SR PF0.

[0307] (i) In case of HARQ-ACK PF0, the corresponding resource (PRB) may include an additional PF0 resource to which a specific PRB offset is applied. In case of SR PF0, an additional PF0 resource to which a specific PRB offset is applied may be included in the corresponding resource (PRB index).

[0308] 3. Combination B: single HP SR PF0 + single LP HARQ-ACK PF1

[0309] -HARQ-ACK can be sent in the resources of a single HARQ-ACK PF1 or in the resources of a single SR PF0.

[0310] (i) In case of a single HARQ-ACK PF1, the corresponding resources (PRB) may include additional PF1 resources to which a specific PRB offset is applied. In case of a single SR PF0, additional PF0 resources to which a specific PRB offset is applied may be included in the corresponding resources (PRB index).

[0311] - Alternatively, only SR may be sent in a single SR PF0, while HARQ-ACK may be dropped.

[0312] 4. Combination C: single HP SR PF1 + single LP HARQ-ACK PF0

[0313] -HARQ-ACK can be sent in the resources of a single HARQ-ACK PF0 or in the resources of a single SR PF1.

[0314] (i) In the case of HARQ-ACK PF0, the corresponding resources (PRBs) may include additional PF0 resources to which a specific PRB offset is applied.

[0315] 5. Combination D: single HP SR PF1 + single LP HARQ-ACK PF1

[0316] -HARQ-ACK can be sent in the resources of a single SR PF1.

[0317] ii.Alt A

[0318] 1. When (all or) some of the (a) and (b) PF combinations based on (a) one or more HP SR PUCCHs (PF0 / 1) and (b) LP HARQ-ACK PUCCH (PF0 / 1) correspond to combinations that enable HARQ-ACK to be sent on SR PUCCH, the UE may multiplex and send LP HARQ-ACK on a specific one (e.g., the first or last) HP SR PUCCH among some of the corresponding HP SR PUCCHs (or on all corresponding HP SR PUCCHs).

[0319] 2. When neither (a) nor (b) PF combinations based on (a) one or more HP SR PUCCHs (PF0 / 1) and (b) LP HARQ-ACK PUCCHs (PF0 / 1) corresponds to a combination that enables HARQ-ACK to be sent on the SR PUCCH, the UE may send only HP SR on each HP SR PUCCH while dropping LP HARQ-ACK (PUCCH) transmission.

[0320] iii.Alt B

[0321] 1. When all (a) and (b) PF combinations based on (a) one or more HP SR PUCCHs (PF0 / 1) and (b) LP HARQ-ACK PUCCH (PF0 / 1) correspond to combinations that enable HARQ-ACK to be sent on the SR PUCCH, the UE may multiplex and send LP HARQ-ACK on a specific (e.g., the first or last) HP SR PUCCH among all HP SR PUCCHs (or on all HP SR PUCCHs).

[0322] 2. When (either or) some of the (a) and (b) PF combinations based on (a) one or more HP SR PUCCHs (PF0 / 1) and (b) LP HARQ-ACK PUCCHs (PF0 / 1) do not correspond to a combination that enables HARQ-ACK to be sent on the SR PUCCH, the UE may send only HP SR on each HP SR PUCCH while dropping the LP HARQ-ACK (PUCCH) transmission.

[0323] iv.Alt C

[0324] 1. When the (a) and (b) PF combinations based on (a) a specific (e.g., the first or last) HPSR PUCCH (PF0 / 1) among one or more HP SR PUCCHs (PF0 / 1) and (b) LP HARQ-ACK PUCCH (PF0 / 1) correspond to a combination that enables HARQ-ACK to be sent on the SR PUCCH, the UE may multiplex and send LP HARQ-ACK on the HP SR PUCCH.

[0325] 2. When the (a) and (b) PF combinations based on (a) a specific (e.g., the first or last) HPSR PUCCH (PF0 / 1) among one or more HP SR PUCCHs (PF0 / 1) and (b) LP HARQ-ACK PUCCH (PF0 / 1) do not correspond to a combination that enables HARQ-ACK to be sent on the SR PUCCH, the UE may send only HP SR on each HP SR PUCCH while discarding LP HARQ-ACK (PUCCH) transmission.

[0326] [Proposal 4]

[0327] A method of multiplexing UCI on PUSCH in NR Rel-15 / 16 (referred to as "Rel-15 / 16 UCI on PUSCH" for convenience) is summarized in Table 7 below.

[0328] [Table 7]

[0329]

[0330]

[0331]

[0332] Case H-0) When the UCI combination requiring multiplexed transmission on PUSCH (e.g., HP PUSCH) is {HP HARQ-ACK, LP HARQ-ACK, HP CSI part 1, HP CSI part 2}, the UE / BS can operate based on Alt 1) or Alt 2).

[0333] -Alt 1) In the case where HP CSI part 2 transmission is discarded, the RE number allocation and RE mapping methods corresponding to UCI type 1, UCI type 2 and UCI type 3 in "Rel-15 / 16UCI on PUSCH" in Table 7 can be applied to HPHARQ-ACK, LP HARQ-ACK and HP CSI part 1, respectively, and the RE number allocation and RE mapping methods corresponding to UCI type 1, UCI type 2 and UCI type 3 in "Rel-15 / 16UCI on PUSCH" in Table 7 can be applied to HP HARQ-ACK, HP CSI part 1 and LP HARQ-ACK, respectively.

[0334] -Alt 2) Alternatively, in the case where LP HARQ-ACK transmission is discarded, the RE number allocation and RE mapping methods corresponding to UCI type 1, UCI type 2 and UCI type 3 in "Rel-15 / 16UCI on PUSCH" of Table 7 can be applied to HP HARQ-ACK, HP CSI part 1 and HP CSI part 2, respectively.

[0335] In a more specific example, the BS may configure (through RRC) or indicate (through DCI) a method to be applied to or applied to the UE between Alt 1 and Alt 2, and the UE may perform UCI multiplexing on the HP PUSCH based on the configured method.

[0336] Case H-1) When the UCI combination for multiplexing transmission on PUSCH (e.g., HP PUSCH) is {LP HARQ-ACK, HP CSI part 1, HP CSI part 2} (and the operation of multiplexing and transmitting HP UCI and LP UCI on the same (HP)PUSCH is configured), the UE may (sequentially) reserve the REs of the earliest non-DMRS symbol after the first DMRS symbol in the (HP)PUSCH resource as a reserved RE set corresponding to 2-bit HP HARQ-ACK, even though the HP HARQ-ACK to be actually transmitted does not exist (in this case, the number of reserved REs is determined based on the beta offset 'βoffset' configured for HP HARQ-ACK transmission on HP PUSCH). In this state, the UE may operate based on Alt 1) or Alt 2).

[0337] -Alt 1) In the case where HP CSI part 2 transmission is dropped, the RE number allocation and RE mapping method corresponding to UCI type 2 and UCI type 3 in "Rel-15 / 16UCI on PUSCH" of Table 7 may be applied to LP HARQ-ACK and HP CSI part 1 (or HP CSI part 1 and LP HARQ-ACK), respectively.

[0338] -Alt 2) Alternatively, in the case where LP HARQ-ACK transmission is discarded, RE number allocation and RE mapping methods corresponding to UCI type 2 and UCI type 3 in "Rel-15 / 16 UCI on PUSCH" of Table 7 may be applied to HPCSI part 1 and HP CSI part 2, respectively.

[0339] For example, the above method may be applied to UCI multiplexing on any HP PUSCH or only to HP CG PUSCH or HP DG PUSCH scheduled by DCI indicated by no UL DAI information (total DAI or payload size information for HP HARQ-ACK and / or LP HARQ-ACK). For the HP DG PUSCH scheduled by DCI indicated by UL DAI information (total DAI or payload size information for HP HARQ-ACK and / or LPHARQ-ACK), Alt 1) the RE number allocation and RE mapping methods corresponding to UCI type 1, UCI type 2 and UCI type 3 in "Rel-15 / 16UCI on PUSCH" of Table 7 can be applied to LP HARQ-ACK, HP CSI part 1 and HP CSI part 2, respectively, or Alt 2) the RE number allocation and RE mapping methods corresponding to UCI type 1, UCI type 2 and UCI type 3 in "Rel-15 / 16UCI on PUSCH" of Table 7 can be applied to HP CSI part 1, HP CSI part 2 and LP HARQ-ACK, respectively.

[0340] Case H-2) When the UCI combination requiring multiplexing transmission on (HP)PUSCH is {LP HARQ-ACK, HP single-part CSI} (and the operation of multiplexing and transmitting HP UCI and LP UCI on the same (HP)PUSCH is configured), the UE may (sequentially) reserve the REs of the earliest non-DMRS symbol after the first DMRS symbol in the HP PUSCH resource as a reserved RE set corresponding to 2-bit HP HARQ-ACK, even though the HP HARQ-ACK to be actually transmitted does not exist (in this case, the number of reserved REs is determined based on the beta offset 'βoffset' configured for HP HARQ-ACK transmission on HP PUSCH). In this state, the UE may operate based on Alt 1) or Alt 2).

[0341] -Alt 1) RE number allocation and RE mapping methods corresponding to UCI type 2 and UCI type 3 in "Rel-15 / 16 UCI on PUSCH" of Table 7 may be applied to LP HARQ-ACK and HP CSI, respectively.

[0342] -Alt 2) Alternatively, RE number allocation and RE mapping methods corresponding to UCI type 2 and UCI type 3 in "Rel-15 / 16 UCI on PUSCH" of Table 7 may be applied to HP CSI and LP HARQ-ACK, respectively.

[0343] For example, the above method can be applied to UCI multiplexing on any HP PUSCH or only to HP CG PUSCH or HP DG PUSCH scheduled by DCI indicated by not including UL DAI information (total DAI or payload size information for HP HARQ-ACK and / or LP HARQ-ACK). For HP DG PUSCH scheduled by DCI indicated by including UL DAI information (total DAI or payload size information for HP HARQ-ACK and / or LPHARQ-ACK), Alt 1) RE number allocation and RE mapping methods corresponding to UCI type 1 and UCI type 2 in "Rel-15 / 16UCI on PUSCH" of Table 7 can be applied to LP HARQ-ACK and HP CSI, respectively, or Alt 2) RE number allocation and RE mapping methods corresponding to UCI type 1 and UCI type 2 in "Rel-15 / 16UCI on PUSCH" of Table 7 can be applied to HP CSI and LPHARQ-ACK, respectively.

[0344] Case H-3) When the UCI that needs to be multiplexed and transmitted on the HP PUSCH is only {LP HARQ-ACK} (and the operation of multiplexing and transmitting HP UCI on the same (HP) PUSCH is configured), although the HP HARQ-ACK to be actually transmitted does not exist, the UE may (sequentially) reserve the REs of the earliest non-DMRS symbol after the first DMRS symbol in the HP PUSCH resource as the reserved RE set corresponding to the 2-bit HP HARQ-ACK (in this case, the number of reserved REs is determined based on the beta offset 'βoffset' configured for the HP HARQ-ACK transmission on the HPPUSCH). In this state, the UE may apply the RE number allocation and RE mapping method corresponding to UCI type 2 in "Rel-15 / 16UCI on PUSCH" of Table 7 to LP HARQ-ACK.

[0345] For example, the above method can be applied to UCI multiplexing on any HP PUSCH or only to HP CG PUSCH or HP DG PUSCH scheduled by DCI indicated by not including UL DAI information (total DAI or payload size information for HP HARQ-ACK and / or LP HARQ-ACK). For HP DG PUSCH scheduled by DCI indicated by including UL DAI information (total DAI or payload size information for HP HARQ-ACK and / or LPHARQ-ACK), the RE number allocation and RE mapping method corresponding to UCI type 1 in "Rel-15 / 16UCI on PUSCH" of Table 7 can be applied to LP HARQ-ACK.

[0346] Table 8 lists at least some of the above examples of multiplexing UCIs with different priorities on the HP PUSCH (eg, case Hx).

[0347] [Table 8]

[0348]

[0349] Referring to Table 8, when multiplexing of UCI with different priorities is configured for PUSCH transmission, RE reservation associated with potential HP HARQ-ACK may be performed on HP PUSCH even if HP HARQ-ACK does not actually exist. For example, for both the case where there are 2 bits or less of actual HP HARQ-ACK (e.g., case H-0) and the case where there is no HP HARQ-ACK (e.g., case H-1), RE reservation associated with (actual / potential) 1-bit or 2-bit HP HARQ-ACK or 0-bit HP HARQ-ACK may be performed on HP PUSCH, and in terms of RE number allocation and RE mapping method, UCI type 2 / 3 associated with (actual / potential) HPHARQ-ACK other than UCI type 1 may be applied to the remaining UCI.

[0350] For example, even when there is no HP HARQ-ACK to be reported by the UE (i.e., 0 bits), RE reservation associated with potential HP HARQ-ACK may be performed only when the priority of PUSCH is HP. When the priority of PUSCH is LP and the UE determines that the HP HARQ-ACK to be reported is 0 bits, RE reservation associated with potential HP HARQ-ACK may not be performed for LP PUSCH.

[0351] When RE reservation related to HARQ-ACK is performed for HP PUSCH, there is a technical effect that HP data (e.g., UL-SCH) (and / or HP CSI part 1 and / or HP CSI part 2) mapped to HP PUSCH is protected. In a specific example, assume that although a specific HP DCI scheduling a specific HP PDSCH is sent, the UE fails to receive it. As a result of missing the specific HP DCI scheduling a specific HP PDSCH, the UE may misunderstand that the total payload size of the HP HARQ-ACK to be reported for the specific HP PDSCH is 0 bits. When the UE performs resource mapping for the HP PUSCH in this misunderstood state, the BS may expect the UE to report an N-bit (e.g., 1 or 2 bits) HP HARQ-ACK for the specific HP PDSCH and decode the HP PUSCH. When a specific RE is configured as a reserved RE associated with HP HARQ-ACK on HP PUSCH, regardless of the UE incorrectly determining the payload size of the HP HARQ-ACK as 0 bits, the UE / BS operates based on Table 7 above (e.g., the UE maps CSI part 2 and data (e.g., HP UL-SCH) after mapping CSI part 1 by avoiding the reserved specific REs). Assuming that the reserved REs have been punctured (e.g., based on the operation of Table 7) for HP HARQ-ACK, the BS decodes CSI part 2 and data (e.g., HP UL-SCH) in the remaining REs. In addition, the BS can recognize that the UE has failed to correctly receive the PDSCH scheduling based on the failure to detect the ACK in the reserved specific REs, and perform retransmission (if necessary).

[0352] Compared to this embodiment, a description will be given of a problem when reserved REs related to HP HARQ-ACK are configured in HP PUSCH based only on the UE's determination that there is actually a 1-bit or 2-bit HP HARQ-ACK. If the UE mistakenly recognizes that the payload size of the HP HARQ-ACK is 0 bits, the UE maps CSI part 1 / 2 and data (e.g., HP UL-SCH) without reserving specific REs. However, since the BS decodes the HP PUSCH under the assumption of 1 or 2-bit A / N mapping to specific REs, the reception performance of the HP PUSCH including CSI part 1 / 2 and HP UL-SCH data is degraded.

[0353] Although this PUSCH reception performance degradation is acceptable for LP PUSCH (carrying LP CSI part 1 / LP CSI part 2 / LP UL-SCH), it is preferably not allowed for HP PUSCH (carrying HPCSI part 1 / HP CSI part 2 / HP UL-SCH) which requires relatively high importance and reliability. Therefore, RE reservation can be performed for LP PUSCH only based on the UE's determination that there is a valid 1 or 2-bit HP HARQ-ACK on the LP PUSCH to improve the efficiency of resource usage, but the UE performs RE reservation associated with potential 1 or 2-bit HP HARQ-ACK regardless of the determination that there is no actual HP HARQ-ACK on the HP PUSCH to protect HP and improve reliability.

[0354] When HP HARQ-ACK is present and its size exceeds 2 bits, rate matching for PUSCH taking into account the HP HARQ-ACK payload size is performed instead of performing RE reservation for HP HARQ-ACK. Therefore, HP PUSCH performance degradation does not matter.

[0355] In an example of allowing LP PUSCH performance degradation caused by not performing reservation for potential HP HARQ-ACK, when the UE determines that the HP HARQ-ACK is 0 bits and multiplexes {LP HARQ-ACK, LP CSI part 1, LP CSI part 2} on the LP PUSCH, the UE does not perform RE reservation for the potential HP HARQ-ACK. When the UE misses the HP DCI and thus skips reporting 2 bits or less of HP HARQ-ACK, the reception performance of the LP PUSCH may be more or less degraded. However, such reception performance may be allowed for LPs with relatively low importance and low protection level (for efficiency of resource usage).

[0356] In the above description, HP CSI part 1 and HP CSI part 2 may correspond to aperiodic CSI. For example, aperiodic HP CSI reporting may be triggered by DCI, and HP CSI part 1 and HP CSI part 2 may be transmitted on the HP PUSCH scheduled by DCI.

[0357] Although CSI part 1 and CSI part 2 may be transmitted on PUSCHs having the same priority, transmitting CSI part 1 and CSI part 2 on PUSCHs having different priorities may not be permitted. For example, (non-periodic) HP CSI part 1 / 2 may be transmitted only on HP PUSCH and not on LP PUSCH, and (periodic) LP CSI part 1 / 2 may be dropped when (periodic) LP CSI part 1 / 2 overlaps with HP PUSCH.

[0358] Those skilled in the art will appreciate that although Alt 1 and Alt 2 are optional in the same case Hx, they are optional in different cases Hx and cases Hy (e.g., Fig. 9 ) do not conflict (they are compatible).

[0359] Fig. 9 is a diagram illustrating multiplexing of UCIs with different priorities on an HP PUSCH according to an embodiment of the present disclosure. Fig. 9 ] The operation of the UE / BS to which at least Case H-0 and Case H-1 are applied is illustrated in FIG.

[0360] refer to Fig. 9 , the UE / BS determines the UCI to be multiplexed on the HP PUSCH (905), and determines whether these UCIs have the same priority (910). In the case of the same priority, the UE / BS can operate in the same manner as in the legacy NR Rel.16 (935). In the case of different priorities, the UE needs to determine whether the BS has configured to multiplex UCIs with different priorities on the PUSCH (915). When the UE is not configured to multiplex UCIs with different priorities on the PUSCH, the UE can operate in the same manner as in the legacy NR Rel.16 (935).

[0361] For convenience, it is assumed that the UE is configured to multiplex UCI with different priorities on PUSCH (915, yes). When HPHARQ-ACK is greater than 2 bits (917, no), rate matching is performed for HP PUSCH in consideration of the payload size of HP HARQ-ACK. When HP HARQ-ACK is 0, 1 or 2 bits (917, yes), RE reservation is performed for HP HARQ-ACK on HP PUSCH (920).

[0362] When HP UCI includes HP CSI part 1 / 2 (925, yes), HP CSI part 1 and HP CSI part 2 are respectively regarded as UCI type 2 and UCI type 3 in Table 7 and mapped on PUSCH. In case LP HARQ-ACK exists, LP HARQ-ACK is discarded (940).

[0363] When the HP UCI does not include the HP CSI part 1 / 2 (925, No) and the LP HARQ-ACK is mappable, the LP HARQ-ACK may be transmitted on the HP PUSCH (930).

[0364] Case L-0) When the UCI combination requiring multiplexed transmission on LP PUSCH is {HP HARQ-ACK, LP HARQ-ACK, LP CSI part 1, LP CSI part 2}, the RE number allocation and RE mapping method corresponding to UCI type 1, UCI type 2 and UCI type 3 in "Rel-15 / 16UCI on PUSCH" in Table 7 can be applied to HP HARQ-ACK, LPHARQ-ACK, LP CSI part 1, respectively, however the transmission of LP CSI part 2 can be discarded.

[0365] Fig.10 is a diagram illustrating multiplexing of UCIs with different priorities on an LP PUSCH according to an embodiment of the present disclosure. Fig.10 The diagram in FIG. 4 illustrates UE / BS operations to which at least case L-0 is applied.

[0366] refer to Fig.10 , the UE / BS determines the UCI to be multiplexed on the LP PUSCH (A05), and determines whether the UCI has the same priority (A07). In the case of the same priority, the UE / BS can operate in the same manner as in the legacy NR Rel.16 (A15). In the case of different priorities, the UE needs to determine whether the BS has configured to multiplex UCI with different priorities on the PUSCH (A10). When the UE is not configured to multiplex UCI with different priorities on the PUSCH, the UE can operate in the same manner as in the legacy NR Rel.16 (A15).

[0367] For convenience, it is assumed that the UE is configured to multiplex UCI with different priorities on PUSCH (A10, yes). When HPHARQ-ACK is greater than 2 bits (A17, no), rate matching is performed for HP PUSCH taking into account the payload size of HP HARQ-ACK. When HP HARQ-ACK is (equal to or greater than 1 bit and) equal to or less than 2 bits, RE reservation is performed for HP HARQ-ACK on LP PUSCH (A25). When HP HARQ-ACK is 0 bits, RE reservation is not performed for potential HP HARQ-ACK on LP PUSCH (A35).

[0368] In case L-0, on LP-PUSCH, HP HARQ-ACK may be considered as UCI type 1, and LPHARQ-ACK may be considered as UCI type 2 (A30).

[0369] Case L-1) When the UCI combination requiring multiplexed transmission on LP PUSCH is {LP HARQ-ACK, LP CSI part 1, LP CSI part 2}, (and when the operation of multiplexing and sending HP UCI and LP UCI on the same (LP)PUSCH is configured) although the actual HP HARQ-ACK to be sent does not exist, the UE may (sequentially) reserve REs in the earliest non-DMRS symbol after the first DMRS symbol in the LP PUSCH resource as a reserved RE set corresponding to 2-bit HP HARQ-ACK (in this case, the number of reserved REs may be determined based on the beta offset 'βoffset' configured for sending HP HARQ-ACK on LP PUSCH). In this case, the UE may apply the RE number allocation and RE mapping method corresponding to UCI type 2 and UCI type 3 in "Rel-15 / 16UCI on PUSCH" of Table 7 to LP HARQ-ACK and LP CSI part 1, respectively, while discarding the transmission of LP CSI part 2.

[0370] Case L-2) When the UCI combination requiring multiplexing transmission on LP PUSCH is {LP HARQ-ACK, LP single-part CSI}, (and when the operation of multiplexing and sending HP UCI and LP UCI on the same (LP)PUSCH is configured) although the actual HP HARQ-ACK to be sent does not exist, the UE may (sequentially) reserve REs in the earliest non-DMRS symbol after the first DMRS symbol in the LP PUSCH resource as a reserved RE set corresponding to 2-bit HP HARQ-ACK (in this case, the number of reserved REs may be determined based on the beta offset 'βoffset' configured for sending HP HARQ-ACK on LP PUSCH). In this case, the UE may apply the RE number allocation and RE mapping method corresponding to UCI type 2 and UCI type 3 in "Rel-15 / 16UCI on PUSCH" of Table 7 to LP HARQ-ACK and LP CSI, respectively.

[0371] Case L-3) When the UCI that requires multiplexing transmission on the LP PUSCH is only {LP HARQ-ACK}, (and when the operation of multiplexing and sending HP UCI and LP UCI on the same (LP)PUSCH is configured) although the actual HPHARQ-ACK to be sent does not exist, the UE may (sequentially) reserve REs in the earliest non-DMRS symbol after the first DMRS symbol in the LP PUSCH resource as a reserved RE set corresponding to 2-bit HP HARQ-ACK (in this case, the number of reserved REs may be determined based on the beta offset 'βoffset' configured for sending HP HARQ-ACK on the LP PUSCH). In this case, the UE may apply the RE number allocation and RE mapping method corresponding to UCI type 2 in "Rel-15 / 16UCI on PUSCH" of Table 7 to LP HARQ-ACK.

[0372] Table 9 summarizes at least some of the above examples of multiplexing UCI with different priorities on the LP PUSCH (eg, case Lx).

[0373] [Table 9]

[0374]

[0375] Table 8 and Table 9 do not conflict with each other, and the UE / BS can support both parts of Table 8 and parts of Table 9. Fig.11 , depending on whether PUSCH B05 determined for UCI is HP or LP (B10), the UE / BS may implement the portion of Table 8 as Fig. 9The UE / BS may operate as in the implementation of part of Table 9 (B15) or Fig.10 Do the same as in (B20).

[0376] When the UCI combination requiring multiplexed transmission on LP PUSCH is {HP HARQ-ACK, HP single part CSI, LPHARQ-ACK}, the UE can apply the RE number allocation and RE mapping methods corresponding to UCI type 1, UCI type 2 and UCI type 3 in "Rel-15 / 16UCI on PUSCH" in Table 7 to HP HARQ-ACK, HP single part CSI and LPHARQ-ACK, respectively.

[0377] In this case, when the HP PUSCH includes UL-SCH transmission, and the number of remaining REs (e.g., N) after mapping the HP HARQ-ACK and the HP single partial CSI among all UCI REs available for UCI mapping on the HP PUSCH is less than a specific number of REs (e.g., X) (corresponding to the minimum number of REs required for LP HARQ-ACK mapping), even if N is less than X, the UE may 1) discard the transmission of the entire LP HARQ-ACK or 2) map the coded bits of the entire payload of the LP HARQ-ACK to N REs for transmission. In this document, X may be determined (e.g., as a minimum integer equal to or greater than {A x B x C / D}) based on a combination of the following: the payload size (e.g., A) of the LP HARQ-ACK (including CRC), the β configured for the LPHARQ-ACK, offset value (e.g., B), the total number of REs available for data mapping on the HP PUSCH (e.g., C), and the TB size of the UL-SCH.

[0378] In another method, the UE may 3) send only some specific HARQ-ACK bits (eg, with bit indices) (based on the β for LP HARQ-ACK) to the UE. offset The packets satisfying (eg, being equal to or lower than) a specific coding rate (eg, {D / (B x C)}) and being mappable to N REs as much as possible) are mapped to N REs in the total LP HARQ-ACK payload for transmission.

[0379] Or in this case, when the HP PUSCH does not include UL-SCH transmission, and mapping the LP HARQ-ACK to the remaining (N) REs after mapping the HP HARQ-ACK and the HP single part CSI among all UCI REs available for UCI mapping on the HP PUSCH results in a coding rate (e.g., M) of the LP HARQ-ACK being higher than a certain level (e.g., Y), 1) the UE may discard transmission of the entire LP HARQ-ACK (in this case, N REs may be additionally used to map the HP single part CSI), or 2) even if M is greater than Y, the UE may map the coded bits of the entire payload of the LP HARQ-ACK to N REs for transmission. The coding rate (e.g., R) indicated by the DCI scheduling the HP PUSCH and the β configured for the LP HARQ-ACK may be determined based on the coding rate (e.g., R) indicated by the DCI scheduling the HP PUSCH and the β configured for the LP HARQ-ACK. offset The combination of values ​​(e.g., B) determines Y (e.g., {R / B}).

[0380] In another method, the UE may 3) send only some specific HARQ-ACK bits (eg, with bit indices) (based on the β for LP HARQ-ACK) to the UE. offset The LP HARQ-ACK payload that satisfies (eg, is equal to or lower than) a specific coding rate (eg, {R / B}) and can be mapped to N REs as much as possible) is mapped to N REs in the total LP HARQ-ACK payload for transmission.

[0381] When the UCI combination requiring multiplexed transmission on HP PUSCH is {HP CSI part 1, HP CSI part 2, LPHARQ-ACK}, the UE can apply the RE number allocation and RE mapping methods corresponding to UCI type 1, UCI type 2 and UCI type 3 in "Rel-15 / 16UCI on PUSCH" of Table 7 to HP CSI part 1, HP CSI part 2 and LP HARQ-ACK, respectively.

[0382] In this case, when the HP PUSCH includes UL-SCH transmission, and the number of remaining REs (e.g., N) after mapping HP CSI part 1 and HP CSI part 2 among all UCI REs available for UCI mapping on the HP PUSCH is less than a specific number of REs (e.g., X) (corresponding to the minimum number of REs required for LP HARQ-ACK mapping), even if N is less than X, the UE may 1) discard the transmission of the entire LP HARQ-ACK or 2) map the coded bits of the entire payload of the LP HARQ-ACK to N REs for transmission. In this document, X may be determined (e.g., as a minimum integer equal to or greater than {A x B x C / D}) based on a combination of the following: the payload size of the LP HARQ-ACK (including CRC) (e.g., A), the βoffset value configured for the LPHARQ-ACK (e.g., B), the total number of REs available for data mapping on the HP-PUSCH (e.g., C), and the TB size of the UL-SCH (e.g., D).

[0383] In another method, the UE may 3) map only some specific HARQ-ACK bits (e.g., with bit indices) that satisfy (e.g., are equal to or lower than) a specific coding rate (e.g., {D / (B x C)}) based on the βoffset for LP HARQ-ACK and are mappable to N REs as much as possible to N REs in the total LP HARQ-ACK payload for transmission.

[0384] Alternatively, in this case, when the HP PUSCH does not include UL-SCH transmission, and mapping the LP HARQ-ACK to the remaining (N) REs after mapping the HP CSI part 1 and the HP CSI part 2 among all UCI REs available for UCI mapping on the HP PUSCH results in a coding rate (e.g., M) of the LP HARQ-ACK being higher than a certain level (e.g., Y), 1) the UE may discard transmission of the entire LP HARQ-ACK (in this case, N REs may be additionally used to map the HP CSI part 2), or 2) even if M is greater than Y, the UE may map the coded bits of the entire payload of the LP HARQ-ACK to the N REs for transmission. Y may be determined (e.g., as {R / B}) based on a combination of a coding rate (e.g., R) indicated by the DCI that schedules the HP PUSCH and a βoffset value (e.g., B) configured for the LP HARQ-ACK.

[0385] In another method, the UE may 3) map only some specific HARQ-ACK bits (e.g., with bit indices) that satisfy (e.g., are equal to or lower than) a specific coding rate (e.g., {R / B}) based on the βoffset used for LP HARQ-ACK and are mappable to N REs as much as possible to N REs in the total LP HARQ-ACK payload for transmission.

[0386] When the UCI combination requiring multiplexed transmission on LP PUSCH is {HP HARQ-ACK, LP HARQ-ACK, LP CSI part 1, LP CSI part 2}, the UE may apply the RE number allocation and RE mapping methods corresponding to UCI type 1, UCI type 2, and UCI type 3 in "Rel-15 / 16UCI on PUSCH" of Table 7 to HP HARQ-ACK, LP HARQ-ACK, and LP CSI part 1, respectively, while discarding the LP CSI part 2 transmission.

[0387] In this case, when the LP PUSCH includes UL-SCH transmission, and the number of remaining REs after mapping HP HARQ-ACK and LP HARQ-ACK among all UCI REs available for UCI mapping on the LP PUSCH (e.g., N) is less than a specific number of REs (e.g., X) (corresponding to the minimum number of REs required for LP CSI part 1 mapping), even if N is less than X, the UE may 1) discard the transmission of the entire LP CSI part 1 or 2) map the coded bits of the entire payload of the LP CSI part 1 to N REs. Herein, X may be determined (e.g., as a minimum integer equal to or greater than {A x B xC / D}) based on a combination of the payload size (e.g., A) of the LP CSI part 1 (including CRC), the β offset value configured for the LP CSI part 1 (e.g., B), the total number of REs available for data mapping on the LP-PUSCH (e.g., C), and the TB size (e.g., D) of the UL-SCH.

[0388] In another method, the UE may 3) map only some specific CSI bits (e.g., with bit indices) that satisfy (e.g., are equal to or lower than) a specific coding rate (e.g., {D / (B x C)}) based on the βoffset value configured for LP CSI part 1 and are mappable to N REs as much as possible to N REs in the total LP CSI part 1 payload for transmission.

[0389] Alternatively, in this case, when the LP PUSCH does not include UL-SCH transmission, and mapping the LP CSI part 1 to the remaining (N) REs after mapping the HP HARQ-ACK and the LP HARQ-ACK among all UCI REs available for UCI mapping on the LP PUSCH results in a coding rate (e.g., M) of the HP CSI part 1 being higher than a certain level (e.g., Y), 1) the UE may discard transmission of the entire LP CSI part 1 (in this case, N REs may be additionally used for mapping the LP HARQ-ACK), or 2) the UE may map the coded bits of the entire payload of the LP CSI part 1 to N REs for transmission even if M is greater than Y. Y may be determined (e.g., as {R / B}) based on a combination of the coding rate (e.g., R) indicated by the DCI scheduling the LP PUSCH and a β offset value (e.g., B) configured for the LP CSI part 1.

[0390] In another method, the UE may 3) map only some specific CSI bits (e.g., with bit indices) that satisfy (e.g., are equal to or lower than) a specific coding rate (e.g., {R / B}) based on the βoffset configured for LP CSI part 1 (and are mappable to N REs as much as possible) to N REs in the total LP CSI part 1 payload for transmission.

[0391] When the UCI combination requiring multiplexed transmission on LP PUSCH is {HP HARQ-ACK, LP HARQ-ACK, LP single part CSI}, the UE can apply the RE number allocation and RE mapping methods corresponding to UCI type 1, UCI type 2 and UCI type 3 in "Rel-15 / 16UCI on PUSCH" in Table 7 to HP HARQ-ACK, LP HARQ-ACK and LP single part CSI, respectively.

[0392] In this case, when the LP PUSCH includes UL-SCH transmission, and the number of remaining REs after mapping HP HARQ-ACK and LP HARQ-ACK among all UCI REs available for UCI mapping on the LP PUSCH (e.g., N) is less than a specific number of REs (e.g., X) (corresponding to the minimum number of REs required for LP single-part CSI mapping), even if N is less than X, the UE may 1) discard the transmission of the entire LP single-part CSI, or 2) map the coded bits of the entire payload of the LP single-part CSI to N REs for transmission. Herein, X may be determined (e.g., as a minimum integer equal to or greater than {A x B x C / D}) based on a combination of the following: a payload size (e.g., A) of the LP single-part CSI (including CRC), a βoffset value (e.g., B) configured for the LP single-part CSI, a total number of REs available for data mapping on the LP-PUSCH (e.g., C), and a TB size (e.g., D) of the UL-SCH.

[0393] In another method, the UE may 3) map only some specific CSI bits (e.g., with bit indices) that satisfy (e.g., are equal to or lower than) a specific coding rate (e.g., {D / (BxC)}) based on a βoffset value configured for the LP single-part CSI (or LP CSI part 1) and are mappable to N REs as much as possible to N REs in the total LP single-part CSI payload for transmission.

[0394] Alternatively, in this case, when the LP PUSCH does not include UL-SCH transmission, and mapping the LP single-part CSI to the remaining (N) REs after mapping the HP HARQ-ACK and the LP HARQ-ACK among all UCI REs available for UCI mapping on the LP PUSCH results in a coding rate (e.g., M) of the LP single-part CSI being higher than a certain level (e.g., Y), 1) the UE may discard transmitting the entire LP single-part CSI (in this case, N REs may be additionally used to map the LP HARQ-ACK), or 2) the UE may map the coded bits of the entire payload of the LP single-part CSI to N REs for transmission even if M is greater than Y. Y may be determined (e.g., as {R / B}) based on a combination of the coding rate (e.g., R) indicated by the DCI scheduling the LP PUSCH and a β offset value (e.g., B) configured for the LP single-part CSI (or LP CSI part 1).

[0395] In another method, the UE may 3) map only some specific CSI bits (e.g., with bit indices) that satisfy (e.g., are equal to or lower than) a specific coding rate (e.g., {R / B}) based on the β offset configured for the LP single-part CSI (or LP CSI part 1) and are mappable to N REs as much as possible to N REs in the total LP single-part CSI payload for transmission.

[0396] [Proposal 5-1]

[0397] In the case where simultaneous transmission of PUCCH and PUSCH located in different frequency resources (e.g., frequency bands (or cells)) and configured / indicated to have different priorities is enabled, the following operations may be considered. In the following description, XP may represent a specific priority, and YP may represent a priority different from XP. For example, when XP=HP, YP=LP. In another example, when XP=LP, YP=HP.

[0398] 1) When the PUCCH on which the HP UCI and the LP UCI are multiplexed and the HP PUCCH or the LP PUCCH are located in different bands (or cells) and temporally overlap with each other, the following operations may be performed.

[0399] A. Alt 1: Because the priority of at least one UCI multiplexed on the PUCCH is different from that of the PUSCH, the UE may operate to transmit the PUCCH and the PUSCH simultaneously.

[0400] i. Regarding PUCCH and PUSCH located in different bands (or cells) and overlapping each other in time, when the priority of all UCI on PUCCH is the same as that of PUSCH, simultaneous transmission of PUCCH and PUSCH is not allowed. In this case, the UE can multiplex and transmit the UCI of PUCCH on PUSCH.

[0401] B.Alt 2: Because the priority of at least one UCI multiplexed on PUCCH is equal to the priority of PUSCH, simultaneous transmission of PUCCH and PUSCH is not allowed. In this case, the UE can multiplex and transmit the HPUCI and LP UCI of PUCCH on PUSCH.

[0402] i. That is, with respect to PUCCH and PUSCH located in different bands (or cells) and temporally overlapping each other, the UE may operate to simultaneously transmit PUCCH and PUSCH only when the priority of all UCIs on the PUCCH is different from that of the PUSCH.

[0403] 2) When the XP PUCCH carrying the XP UCI and at least one (inter-band) YP PUSCH are located in different frequency resources (bands (or cells)) and overlap with each other in time (e.g., over at least some time resources), and the XP PUCCH and at least one (intra-band) YP PUSCH are located in the same band (or cell) and overlap with each other in time, the UE may operate as follows.

[0404] A. Case 1: When multiplexing is configured / indicated as an operation of XP PUCCH and YP PUSCH with different priorities (eg, multiplexing XP UCI on YP PUSCH) is enabled, the following operations may be performed.

[0405] i. Option 1: A YP PUSCH may be selected by applying a specific rule to all intra-band YP PUSCHs and inter-band YP PUSCHs, and the XP UCI of the XP PUCCH may be multiplexed and transmitted on the selected YP PUSCH.

[0406] ii. Option 2: A YP PUSCH may be selected by applying a specific rule only to the in-band YP PUSCH, and the XP UCI of the XP PUCCH may be multiplexed and transmitted on the selected YP PUSCH.

[0407] B. Case 2: When multiplexing is configured / indicated as XP PUCCH and YP PUSCH with different priorities (eg, multiplexing XP UCI on YP PUSCH) is disabled, the following operations may be performed.

[0408] i. When XP is a higher priority than YP, only XP PUCCH may be sent, and the transmission of intra-band YP PUSCH and inter-band YP PUSCH may be discarded. When XP is a lower priority than YP, only intra-band YP PUSCH and inter-band YP PUSCH may be sent, and the transmission of XP PUCCH may be discarded.

[0409] C. Note: When XP PUCCH temporally overlaps with at least one intra-band YP PUSCH, simultaneous transmission between XP PUCCH and each YP PUSCH may not be allowed (in this case, Case 1 or Case 2 may be applied), and when XP PUCCH temporally overlaps only with inter-band YP PUSCH, XP PUCCH and inter-band YP PUSCH may be sent simultaneously.

[0410] [Proposal 5-2]

[0411] When the HP(SPS)PUCCH carrying the HP(SPS) HARQ-ACK for receiving the SPSPDSCH overlaps in time with the LP PUCCH carrying the LP HARQ-ACK in a situation where multiplexing transmission of PUCCHs with different priorities is enabled (e.g., the HP PUCCH time resources and the LP PUCCH time resources at least partially overlap with each other), the following UE operations may be considered.

[0412] 1) When the HP SPS PUCCH is configured in the form of an sps-PUCCH-AN-List including multiple PUCCH resources (based on PF0 / 1 / 2 / 3 / 4) corresponding to multiple different UCI payload sizes, the UE may operate as follows.

[0413] A. The UE may multiplex and send HP SPS HARQ-ACK and LP HARQ-ACK (corresponding to the total payload size of two UCIs) on the HP SPS PUCCH.

[0414] B. When the HP SPS HARQ-ACK payload size (N H bits) and the payload size of LP HARQ-ACK (N L bits) is greater than the maximum UCI payload size (N T bits), the UE can operate as follows.

[0415] i. Option 1

[0416] 1. The UE can receive the HP SPS PUCCH (corresponding to the payload size N of the HP SPS HARQ-ACK payload) H bits), while discarding the LP HARQ-ACK transmission.

[0417] ii. Option 2

[0418] 1. The UE can send HARQ-ACK bits in the HP SPS PUCCH (corresponding to the maximum UCI payload size, N T bits) and transmits a specific T -N H} bits (eg, the first {N T -N H} bits) and N corresponding to the HP SPS HARQ-ACK H bits, while discarding the transmission of the remaining LP HARQ-ACK bits.

[0419] iii. Option 3

[0420] 1.UE can use the maximum UCI payload size N T bits are multiplexed and transmitted on the HP SPS PUCCH corresponding to the LP HARQ-ACK bits and the HP SPS PUCCH bits as a specific {N T +N H} bits.

[0421] 2) When the HP SPS PUCCH is configured in the form of n1PUCCH-AN including a PUCCH resource (based on PF0 / 1) corresponding to a 1 / 2-bit UCI payload size, the following operation may be considered.

[0422] A. Option 1

[0423] i. The UE may send only HP SPS HARQ-ACK on the HP SPS PUCCH while dropping the LP HARQ-ACK transmission.

[0424] B. Option 2

[0425] i. When HP SPS HARQ-ACK is one bit, the UE may multiplex and transmit a specific one bit (e.g., the first bit corresponding to the MSB) among the LPHARQ-ACK bits and one HP SPS HARQ-ACK bit on the HP SPS PUCCH while discarding the transmission of the remaining LP HARQ-ACK bits.

[0426] ii. When the HP SPS HARQ-ACK is two bits, the UE may send only the HP SPS HARQ-ACK on the HP SPS PUCCH while dropping the transmission of the LP HARQ-ACK.

[0427] Regarding Option 1 and Option 2, the same option (eg, Option 1) may be applied to the following Case 1 and Case 2, or different options may be applied to Case 1 and Case 2 (eg, Option 1 is applied to Case 1, and Option 2 is applied to Case 2).

[0428] Case 1: HP SPS HARQ-ACK is one or more bits (and two or less bits), LP HARQ-ACK is one or more bits, and the total payload size of two UCIs is greater than two bits.

[0429] Case 2: HP SPS HARQ-ACK is one bit, LP HARQ-ACK is one bit, and thus the total payload size of two UCIs is two bits.

[0430] When the HP(SPS)PUCCH carrying HP(SPS)HARQ-ACK and the HP(SR)PUCCH carrying HP SR (or the HP PUCCH in which HP(SPS)HARQ-ACK and HP SR are multiplexed) overlap in time (e.g., at least partially overlap in time resources) with the LP PUCCH carrying LP HARQ-ACK in a scenario where multiplexed transmission of PUCCHs with different priorities is enabled, the following UE operations may be considered.

[0431] 1) When the HP SPS PUCCH is configured in the form of an sps-PUCCH-AN-List including multiple PUCCH resources (based on PF0 / 1 / 2 / 3 / 4) corresponding to multiple different UCI payload sizes (and when the HP SPS HARQ-ACK is one or more bits, the LP HARQ-ACK is one or more bits, and the total payload size of the two UCIs is greater than two bits), the UE can operate as follows.

[0432] A. The UE may multiplex and transmit HP UCI (where HP SPS HARQ-ACK and HP SR are combined) and LP HARQ-ACK on the HP SPS PUCCH (corresponding to the total payload size of two UCIs).

[0433] B. When the HP UCI payload size (N H bits) and the payload size of LP HARQ-ACK (N L bits) is greater than the maximum UCI payload size (N T bits), the UE can operate as follows.

[0434] i. Option 1

[0435] 1. The UE may send only HP UCI on the HP SPS PUCCH (corresponding to a payload size of NH bits of HP UCI payload) while dropping the LP HARQ-ACK transmission.

[0436] ii. Option 2

[0437] 1. The UE can send HARQ-ACK bits in the HP SPS PUCCH (corresponding to the maximum UCI payload size, N Tbits) and transmits a specific T -N H} bits (eg, the first {N T -N H} bits) and N corresponding to the HP UCI H bits, while discarding the transmission of the remaining LP HARQ-ACK bits.

[0438] iii. Option 3

[0439] 1.UE can use the maximum UCI payload size N T bits corresponding to the HP SPS PUCCH multiplexed and sent as the sum of the LP HARQ-ACK bits and the HP UCI bits {N T +N H} bits.

[0440] In the same situation above, when HP SPS HARQ-ACK is one bit, LP HARQ-ACK is one bit, and thus the total payload size of two UCIs is 2 bits, option 1 may be applied.

[0441] 2) When the HP SPS PUCCH is configured in the form of n1PUCCH-AN including (PF0 / 1-based) PUCCH resources corresponding to a 1 / 2-bit UCI payload size (and when the HP SPS HARQ-ACK is one or more bits (and two or less bits), the LP HARQ-ACK is one or more bits, and thus the total payload size of the two UCIs is greater than two bits), the following operations may be considered.

[0442] A. Option 1

[0443] i. The UE may send only HP UCI (e.g., only HP SPS HARQ-ACK and HP SR) on the HP SPS PUCCH (when the HP SPS PUCCH is PF0) or on the HP SR PUCCH (when the HP SPS PUCCH is PF1 and the HP SR PUCCH is PF1), while dropping the LP HARQ-ACK transmission.

[0444] B. Option 2

[0445] i. When HP SPS HARQ-ACK is one bit, the UE may multiplex and transmit a specific one bit (e.g., the first bit corresponding to the MSB) among the LP HARQ-ACK bits and one HP SPS HARQ-ACK bit (and HP SR) on the HP SPS PUCCH or the HP SR PUCCH, while discarding the transmission of the remaining LP HARQ-ACK bits.

[0446] ii. When HP SPS HARQ-ACK is two bits, the UE can send only HP SPS HARQ-ACK (and HP SR) on the HP SPS PUCCH (when HP SPSPUCCH is PF0) or on the HP SR PUCCH (when HP SPS PUCCH is PF1 and HP SR PUCCH is PF1), while discarding the LP HARQ-ACK transmission.

[0447] In the same situation above, when HP SPS HARQ-ACK is one bit, LP HARQ-ACK is one bit, and thus the total payload size of two UCIs is 2 bits, option 1 may be applied.

[0448] Fig.12 is a flowchart illustrating a method of transmitting a signal by a UE according to an embodiment of the present disclosure. Fig.12 are examples of possible UE operations according to at least some of the above embodiments, and the scope of the present disclosure is not limited to Fig.12 . Descriptions that are repeated with the previous description will be avoided, and when necessary, reference can be made to the previous description.

[0449] refer to Fig.12 , the UE may receive at least one layer 1 (L1) signaling (e.g., physical layer signaling) and / or at least one layer 3 (L3) signaling (e.g., RRC signaling) (C01). The at least one L1 signaling and / or the at least one L3 signaling may be related to scheduling that results in multiplexing UCI (e.g., LP / HP UCI) on the PUSCH. For example, there may be various examples that result in multiplexing UCI on the PUSCH. The various examples may include the previously referenced Figures 4 to 8 The PUSCH transmission described (e.g., PUSCH based on dynamic scheduling DCI and / or PUSCH based on configured grant). The UCI multiplexed on PUSCH may include at least part of Table 8 / 9, and the case where UCI of PUCCH is multiplexed on PUSCH due to PUCCH-PUSCH overlap may also be considered.

[0450] For example, in some cases, multiple UCIs including {LP HARQ-ACK, HP CSI part 1, HP CSI part 2} may be multiplexed on the HP PUSCH based on L1 (and / or L3) scheduling (C01). In addition, for example, in some cases, multiple UCIs including {LP HARQ-ACK, HP HARQ-ACK, HP CSI part 1, HP CSI part 2} may be multiplexed on the HP PUSCH based on L1 (and / or L3) scheduling (C01). More specifically, in a non-limiting example, the L1 (and / or L3) scheduling (C01) may include a UL grant format DCI (e.g., DCI format 0_1 / 0_2, etc.) that triggers aperiodic CSI reporting. For example, i) the L1 (and / or L3) scheduling (C01) received by the UE from the BS may include an HP DCI with a priority indication field set to HP (e.g., 1), ii) the CSI request field of the HP DCI may trigger aperiodic CSI reporting for the UE, and iii) the HP DCI may include information about HPPUSCH resources. When HP HARQ-ACK is included in the UCI to be multiplexed, the HP HARQ-ACK may be, but is not limited to, an HARQ-ACK associated with an HP PDSCH scheduled by a DL grant HP DCI. The HP HARQ-ACK may be an HARQ-ACK for an HP SPS PDSCH or an HP PDCCH. The LP HARQ-ACK may be, but is not limited to, an HARQ-ACK associated with an LPPDSCH scheduled by a DL grant LP DCI. The LP HARQ-ACK may be an HARQ-ACK for an LP SPS PDSCH or an LP PDCCH. The DL grant LP DCI may be a DCI that schedules a PDSCH without priority indication information or with the priority indication set to LP (e.g., 0). It may happen that the LP PUCCH resources indicated by the DL grant LP DCI or the LP PUSCH carrying the LP HARQ-ACK for the LP PUCCH (in the time domain) overlap at least partially with the HP PUSCH resources. LP HARQ-ACK is not limited to dynamic scheduling. For example, LP HARQ-ACK may be associated with SPS PDSCH. Such UCI multiplexing on HP PUSCH is an exemplary scheduling to help understand the present disclosure. The interpretation of the scope of the present disclosure is not necessarily limited to UCI multiplexing on HP PUSCH, and not all corresponding examples need to be interpreted as necessary characteristics.

[0451] The UE can multiplex multiple UCIs on a single PUSCH (C05).

[0452] The UE may transmit a single PUSCH on which multiple UCIs are multiplexed (C10).

[0453] Based on i) the UE is configured to multiplex UCIs with different priorities on the same PUSCH, ii) the priority of the first UCI included in the multiple UCIs is Priority-H (e.g., HP) higher than Priority-L (e.g., LP), and iii) 2-part CSI is included in the first UCI with Priority-H, the UE can discard all HARQ-ACK information of the second UCI with Priority-L lower than Priority-H, and map the first part of the CSI and the second part of the CSI on a single PUSCH.

[0454] In a state where the first UCI with Priority-H does not include any HARQ-ACK information, the UE may perform RE reservation for potential HARQ-ACK related to Priority-H on a single PUSCH.

[0455] In a state where the first UCI with Priority-H does not include any HARQ-ACK information, assuming that potential HARQ-ACK related to Priority-H is UCI type 1, the UE may perform multiplexing.

[0456] Assuming that the first part of the CSI and the second part of the CSI are UCI type 2 and UCI type 3, respectively, the UE may perform multiplexing.

[0457] Based on the HARQ-ACK information not exceeding 2 bits in the first UCI with Priority-H, the UE may perform RE reservation for potential HARQ-ACK associated with Priority-H on a single PUSCH, regardless of whether HARQ-ACK associated with Priority-H actually exists.

[0458] The UE may map the first part of the CSI to REs excluding specific REs reserved by RE reservation among available REs on a single PUSCH, and after mapping of the first part, the second part of the CSI and data are sequentially mapped to the remaining REs including the specific REs on the single PUSCH.

[0459] Based on the existence of actual 1-bit or 2-bit HARQ-ACK associated with Priority-H, after mapping of the second part and data, the UE can puncture specific REs reserved by RE reservation and map 1-bit or 2-bit HARQ-ACK associated with Priority-H.

[0460] The single PUSCH may be a PUSCH with Priority-H.

[0461] The first part and the second part of the CSI with Priority-H may be related to aperiodic CSI reporting.

[0462] Fig.13 is a flowchart illustrating a method of receiving a signal by a BS according to an embodiment of the present disclosure. Fig.13 are implementation examples of possible BS operations according to at least some of the above-described embodiments, and the scope of the present disclosure is not limited to Fig.13 . Descriptions that are repeated with the previous description will be avoided, and when necessary, reference can be made to the previous description.

[0463] The BS may send at least one L1 signaling (e.g., physical layer signaling) and / or at least one L3 signaling (e.g., RRC signaling) (D01). The at least one L1 signaling and / or at least one L3 signaling may be related to scheduling that causes UCI (e.g., LP / HP UCI) to be multiplexed on the PUSCH. For example, there may be various examples that cause UCI to be multiplexed on the PUSCH. The various examples may include the aforementioned Figures 4 to 8 The PUSCH transmission described (e.g., PUSCH based on dynamic scheduling DCI and / or PUSCH based on configured grant). The UCI multiplexed on PUSCH may include at least part of Table 8 / 9, and the case where UCI of PUCCH is multiplexed on PUSCH due to PUCCH-PUSCH overlap may be considered.

[0464] For example, in some cases, multiple UCIs including {LP HARQ-ACK, HP CSI part 1, HP CSI part 2} may be multiplexed on the HP PUSCH based on L1 (and / or L3) scheduling (D01). In addition, for example, in some cases, multiple UCIs including {LP HARQ-ACK, HP HARQ-ACK, HP CSI part 1, HP CSI part 2} may be multiplexed on the HP PUSCH based on L1 (and / or L3) scheduling (D01). More specifically, in a non-limiting example, the L1 (and / or L3) scheduling (D01) may include a UL grant format DCI (e.g., DCI format 0_1 / 0_2, etc.) that triggers aperiodic CSI reporting. For example, i) the L1 (and / or L3) scheduling (D01) received by the UE from the BS may include an HP DCI with a priority indication field set to HP (e.g., 1), ii) the CSI request field of the HP DCI may trigger aperiodic CSI reporting for the UE, and iii) the HP DCI may include information about HPPUSCH resources. When HP HARQ-ACK is included in the UCI to be multiplexed, the HP HARQ-ACK may be, but is not limited to, an HARQ-ACK associated with an HP PDSCH scheduled by a DL grant HP DCI. The HP HARQ-ACK may be an HARQ-ACK for an HP SPS PDSCH or an HP PDCCH. The LP HARQ-ACK may be, but is not limited to, an HARQ-ACK associated with an LPPDSCH scheduled by a DL grant LP DCI. The LP HARQ-ACK may be an HARQ-ACK for an LP SPS PDSCH or an LP PDCCH. The DL grant LP DCI may be a DCI that schedules a PDSCH without priority indication information or with the priority indication set to LP (e.g., 0). It may happen that the LP PUCCH resources indicated by the DL grant LP DCI or the LP PUSCH carrying the LP HARQ-ACK for the LP PUCCH (in the time domain) overlap at least partially with the HP PUSCH resources. LPHARQ-ACK is not limited to dynamic scheduling. For example, LP HARQ-ACK may be associated with SPS PDSCH. This UCI multiplexing on the HP PUSCH is an exemplary scheduling to help understand the present disclosure. The interpretation of the scope of the present disclosure is not necessarily limited to UCI multiplexing on the HP PUSCH, and not all corresponding examples need to be interpreted as necessary characteristics.

[0465] The BS may receive a single PUSCH from the UE (D05).

[0466] The BS can obtain a plurality of UCIs multiplexed on a received single PUSCH (D10).

[0467] Based on i) the BS configures the UE to multiplex UCIs with different priorities on the same PUSCH, ii) the priority of the first UCI included in the multiple UCIs is Priority-H higher than Priority-L, and iii) 2 parts of CSI are included in the first UCI with Priority-H, assuming that all HARQ-ACK information of the second UCI with Priority-L lower than Priority-H has been discarded, the BS can perform demultiplexing on the first part of the CSI and the second part of the CSI.

[0468] In a state where the first UCI with Priority-H does not include any HARQ-ACK information, the UE may perform RE reservation for potential HARQ-ACK related to Priority-H on a single PUSCH.

[0469] In a state where the first UCI with Priority-H does not include any HARQ-ACK information, the BS may perform demultiplexing assuming that UCI type 1 has been allocated to potential HARQ-ACK related to Priority-H.

[0470] Assuming that the first part of the CSI and the second part of the CSI are UCI type 2 and UCI type 3, respectively, the BS may perform demultiplexing.

[0471] Based on the HARQ-ACK information not exceeding 2 bits in the first UCI with Priority-H, the BS may assume that RE reservation is performed for potential HARQ-ACK associated with Priority-H on a single PUSCH, regardless of whether HARQ-ACK associated with Priority-H actually exists.

[0472] The BS may assume that the first part of the CSI is mapped to REs excluding specific REs reserved by RE reservation among available REs on a single PUSCH, and after mapping of the first part, the second part of the CSI and data are sequentially mapped to the remaining REs including the specific REs on the single PUSCH.

[0473] Based on the existence of actual 1-bit or 2-bit HARQ-ACK associated with Priority-H, after mapping of the second part and data, the BS can assume that the UE punctures specific REs reserved by RE reservation and maps 1-bit or 2-bit HARQ-ACK associated with Priority-H.

[0474] The single PUSCH may be a PUSCH with Priority-H.

[0475] The first part and the second part of the CSI with Priority-H may be related to aperiodic CSI reporting.

[0476] Fig.14 A communication system 1 applied to the present disclosure is shown.

[0477] refer to Fig.14 , the communication system 1 applied to the present disclosure includes a wireless device, a base station (BS), and a network. Herein, a wireless device refers to a device that performs communication using a radio access technology (RAT) (e.g., 5G new RAT (NR) or long term evolution (LTE)), and may be referred to as a communication / radio / 5G device. The wireless device may include (but is not limited to) a robot 100a, vehicles 100b-1 and 100b-2, an extended reality (XR) device 100c, a handheld device 100d, a home appliance 100e, an Internet of Things (IoT) device 100f, and an artificial intelligence (AI) device / server 400. For example, a vehicle may include a vehicle with a wireless communication function, an autonomous driving vehicle, and a vehicle capable of performing communication between vehicles. Herein, a vehicle may include an unmanned aerial vehicle (UAV) (e.g., a drone). XR devices may include augmented reality (AR) / virtual reality (VR) / mixed reality (MR) devices, and may be implemented in the form of head mounted devices (HMDs), head up displays (HUDs) installed in vehicles, televisions, smart phones, computers, wearable devices, home appliance devices, digital signage, vehicles, robots, etc. Handheld devices may include smart phones, smart boards, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., notebooks). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters. For example, a BS and a network may be implemented as wireless devices, and a specific wireless device 200a may operate as a BS / network node relative to other wireless devices.

[0478] The wireless devices 100a to 100f may be connected to the network 300 via the BS 200. AI technology may be applied to the wireless devices 100a to 100f, and the wireless devices 100a to 100f may be connected to the AI ​​server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although the wireless devices 100a to 100f may communicate with each other via the BS 200 / network 300, the wireless devices 100a to 100f may perform direct communication (e.g., side link communication) with each other without passing through the BS / network. For example, vehicles 100b-1 and 100b-2 may perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). IoT devices (e.g., sensors) may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0479] Wireless communication / connection 150a, 150b or 150c can be established between wireless devices 100a to 100f / BS200 or BS200 / BS200. Herein, wireless communication / connection can be established through various RATs (e.g., 5G NR) such as uplink / downlink communication 150a, sidelink communication 150b (or D2D communication) or inter-BS communication (e.g., relay, integrated access backhaul (IAB)). The wireless device and the BS / wireless device can send / receive radio signals to / from each other through wireless communication / connection 150a and 150b. For example, wireless communication / connection 150a and 150b can send / receive signals through various physical channels. To this end, at least a portion of various configuration information for configuring processes for sending / receiving radio signals, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation and resource mapping / demapping) and resource allocation processes can be performed based on various proposals of the present disclosure.

[0480] Fig.15 A wireless device suitable for use with the present disclosure is shown.

[0481] refer to Fig.15 , the first wireless device 100 and the second wireless device 200 may transmit radio signals via various RATs (e.g., LTE and NR). Herein, {the first wireless device 100 and the second wireless device 200} may correspond to Fig.14 {wireless device 100x and BS200} and / or {wireless device 100x and wireless device 100x}.

[0482] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and further include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may control the memory 104 and / or the transceiver 106, and may be configured to implement the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. For example, the processor 102 may process the information in the memory 104 to generate first information / signals, and then transmit a radio signal including the first information / signals through the transceiver 106. The processor 102 may receive a radio signal including second information / signals through the transceiver 106, and then store information obtained by processing the second information / signals in the memory 104. The memory 104 may be connected to the processor 102, and may store various information related to the operation of the processor 102. For example, the memory 104 may store software codes including commands for executing part or all of the processes controlled by the processor 102 or for executing the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. Herein, the processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver 106 may be connected to the processor 102 and transmit and / or receive radio signals through one or more antennas 108. Each transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be used interchangeably with a radio frequency (RF) unit. In the present disclosure, a wireless device may represent a communication modem / circuit / chip.

[0483] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and further include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may control the memory 204 and / or the transceiver 206, and may be configured to implement the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. For example, the processor 202 may process the information in the memory 204 to generate third information / signals, and then transmit a radio signal including the third information / signals through the transceiver 206. The processor 202 may receive a radio signal including fourth information / signals through the transceiver 206, and then store information obtained by processing the fourth information / signals in the memory 204. The memory 204 may be connected to the processor 202, and may store various information related to the operation of the processor 202. For example, the memory 204 may store software codes including commands for executing part or all of the processes controlled by the processor 202 or for executing the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. Herein, the processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver 206 may be connected to the processor 202 and transmit and / or receive radio signals through one or more antennas 208. Each transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be used interchangeably with an RF unit. In the present disclosure, a wireless device may represent a communication modem / circuit / chip.

[0484] In the following, the hardware elements of the wireless devices 100 and 200 will be described in more detail. One or more protocol layers may be implemented by (but not limited to) one or more processors 102 and 202. For example, one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP). One or more processors 102 and 202 may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs) according to the descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document. One or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document. One or more processors 102 and 202 may generate a signal (e.g., a baseband signal) including a PDU, SDU, message, control information, data, or information according to the description, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document, and provide the generated signal to one or more transceivers 106 and 206. One or more processors 102 and 202 may receive a signal (e.g., a baseband signal) from one or more transceivers 106 and 206 and obtain the PDU, SDU, message, control information, data, or information according to the description, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document.

[0485] One or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs) may be included in one or more processors 102 and 202. The descriptions, functions, processes, proposals, methods, and / or operational flow charts disclosed in this document may be implemented using firmware or software, and the firmware or software may be configured to include modules, processes, or functions. Firmware or software configured to execute the descriptions, functions, processes, proposals, methods, and / or operational flow charts disclosed in this document may be included in one or more processors 102 and 202 or stored in one or more memories 104 and 204 to be driven by one or more processors 102 and 202. The descriptions, functions, processes, proposals, methods and / or operational flow charts disclosed in this document may be implemented in the form of codes, commands and / or command sets using firmware or software.

[0486] One or more memories 104 and 204 may be connected to one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, codes, instructions and / or commands. One or more memories 104 and 204 may be configured by read-only memory (ROM), random access memory (RAM), electrically erasable programmable read-only memory (EPROM), flash memory, hard disk drive, register, cache memory, computer-readable storage medium and / or a combination thereof. One or more memories 104 and 204 may be located inside and / or outside of one or more processors 102 and 202. One or more memories 104 and 204 may be connected to one or more processors 102 and 202 by various technologies such as wired or wireless connections.

[0487] One or more transceivers 106 and 206 may send user data, control information and / or radio signals / channels mentioned in the method and / or operation flow chart of this document to one or more other devices. One or more transceivers 106 and 206 may receive user data, control information and / or radio signals / channels mentioned in the description, function, process, proposal, method and / or operation flow chart disclosed in this document from one or more other devices. For example, one or more transceivers 106 and 206 may be connected to one or more processors 102 and 202 and send and receive radio signals. For example, one or more processors 102 and 202 may perform control so that one or more transceivers 106 and 206 may send user data, control information or radio signals to one or more other devices. One or more processors 102 and 202 may perform control so that one or more transceivers 106 and 206 may receive user data, control information or radio signals from one or more other devices. One or more transceivers 106 and 206 may be connected to one or more antennas 108 and 208, and one or more transceivers 106 and 206 may be configured to send and receive user data, control information and / or radio signals / channels mentioned in the description, functions, processes, proposals, methods and / or operation flow charts disclosed in this document through one or more antennas 108 and 208. In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106 and 206 may convert received radio signals / channels, etc. from RF band signals to baseband signals so as to process received user data, control information, radio signals / channels, etc. using one or more processors 102 and 202. One or more transceivers 106 and 206 may convert user data, control information, radio signals / channels, etc. processed using one or more processors 102 and 202 from baseband signals to RF band signals. To this end, one or more of the transceivers 106 and 206 may include (analog) oscillators and / or filters.

[0488] Fig.16 Another example of a wireless device applicable to the present disclosure is shown. The wireless device can be configured based on the usage / service (refer to Fig.14 ) are implemented in various forms.

[0489] refer to Fig.16 , the wireless devices 100 and 200 may correspond to Fig.15The wireless devices 100 and 200 of the present invention may be configured by various elements, components, units / parts and / or modules. For example, each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130 and an additional component 140. The communication unit may include a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 may include Fig.15 The one or more processors 102 and 202 and / or the one or more memories 104 and 204 of the present invention. For example, the transceiver 114 may include Fig.15 The control unit 120 is electrically connected to the communication unit 110, the memory 130, and the additional components 140, and controls the overall operation of the wireless device. For example, the control unit 120 may control the electrical / mechanical operation of the wireless device based on the program / code / command / information stored in the memory unit 130. The control unit 120 may send information stored in the memory unit 130 to the outside (e.g., other communication devices) via the communication unit 110 through a wireless / wired interface, or store information received from the outside (e.g., other communication devices) via the communication unit 110 in the memory unit 130 through a wireless / wired interface.

[0490] The additional components 140 may be configured differently depending on the type of wireless device. For example, the additional components 140 may include at least one of a power supply unit / battery, an input / output (I / O) unit, a drive unit, and a computing unit. The wireless device may be configured in the form of (but not limited to) a robot ( Fig.14 100a), vehicles ( Fig.14 100b-1 and 100b-2), XR devices ( Fig.14 100c), handheld devices ( Fig.14 100d), household appliances ( Fig.14 100e), IoT devices ( Fig.14 100f), digital broadcasting terminals, holographic equipment, public safety equipment, MTC equipment, medical equipment, fintech equipment (or financial equipment), security equipment, climate / environmental equipment, AI servers / equipment ( Fig.14 400), BS( Fig.14 200), network nodes, etc. The wireless device can be used in a mobile or fixed location depending on the usage example / service.

[0491] exist Fig.16In the wireless devices 100 and 200, various elements, components, units / parts and / or modules in the wireless devices 100 and 200 may all be connected to each other through a wired interface, or at least a part thereof may be wirelessly connected through the communication unit 110. For example, in each of the wireless devices 100 and 200, the control unit 120 and the communication unit 110 may be wired, and the control unit 120 and the first unit (e.g., 130 and 140) may be wirelessly connected through the communication unit 110. Each element, component, unit / part and / or module within the wireless devices 100 and 200 may also include one or more elements. For example, the control unit 120 may be configured by a collection of one or more processors. As an example, the control unit 120 may be configured by a collection of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing unit, and a memory control processor. As another example, the memory 130 may be configured by a random access memory (RAM), a dynamic RAM (DRAM), a read-only memory (ROM)), a flash memory, a volatile memory, a non-volatile memory, and / or a combination thereof.

[0492] Fig.17 A vehicle or an autonomous vehicle applied to the present disclosure is shown. The vehicle or the autonomous vehicle can be implemented by a mobile robot, a car, a train, a manned / unmanned aerial vehicle (AV), a ship, etc.

[0493] refer to Fig.17 , the vehicle or autonomous driving vehicle 100 may include an antenna unit 108, a communication unit 110, a control unit 120, a drive unit 140a, a power supply unit 140b, a sensor unit 140c, and an autonomous driving unit 140d. The antenna unit 108 may be configured as a part of the communication unit 110. Blocks 110 / 130 / 140a to 140d correspond to Fig.16 Block 110 / 130 / 140.

[0494] The communication unit 110 may send and receive signals (e.g., data and control signals) to and from external devices such as other vehicles, BSs (e.g., gNBs and roadside units), and servers. The control unit 120 may perform various operations by controlling elements of the vehicle or autonomous driving vehicle 100. The control unit 120 may include an electronic control unit (ECU). The drive unit 140a may enable the vehicle or autonomous driving vehicle 100 to travel on a road. The drive unit 140a may include an engine, a motor, a power system, wheels, brakes, a steering device, etc. The power supply unit 140b may supply power to the vehicle or autonomous driving vehicle 100, and include a wired / wireless charging circuit, a battery, etc. The sensor unit 140c may acquire vehicle status, surrounding environment information, user information, etc. The sensor unit 140c may include an inertial measurement unit (IMU) sensor, a collision sensor, a wheel sensor, a speed sensor, a slope sensor, a weight sensor, a heading sensor, a position module, a vehicle forward / backward sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a depth sensor, an ultrasonic sensor, a lighting sensor, a pedal position sensor, etc. The autonomous driving unit 140d may implement a technology for maintaining a lane in which the vehicle is traveling, a technology for automatically adjusting a speed (e.g., adaptive cruise control), a technology for autonomously traveling along a determined path, a technology for traveling by automatically setting a path if a destination is set, and the like.

[0495] For example, the communication unit 110 may receive map data, traffic information data, etc. from an external server. The autonomous driving unit 140d may generate an autonomous driving path and a driving plan from the obtained data. The control unit 120 may control the drive unit 140a so that the vehicle or the autonomous driving vehicle 100 may move along the autonomous driving path according to the driving plan (e.g., speed / direction control). In the middle of autonomous driving, the communication unit 110 may aperiodically / periodically obtain the latest traffic information data from the external server and obtain surrounding traffic information data from neighboring vehicles. In the middle of autonomous driving, the sensor unit 140c may obtain vehicle status and / or surrounding environment information. The autonomous driving unit 140d may update the autonomous driving path and driving plan based on the newly obtained data / information. The communication unit 110 may transmit information about the vehicle position, autonomous driving path, and / or driving plan to an external server. The external server may predict traffic information data using AI technology, etc. based on information collected from the vehicle or autonomous driving vehicle, and provide the predicted traffic information data to the vehicle or autonomous driving vehicle.

[0496] Fig.18 is a diagram illustrating a DRX operation of a UE according to an embodiment of the present disclosure.

[0497] The UE may perform DRX operation in the process and / or method described / proposed above. A UE configured with DRX may reduce power consumption by discontinuously receiving DL signals. DRX may be performed in the RRC_IDLE state, the RRC_INACTIVE state, and the RRC_CONNECTED state. The UE performs DRX in the RRC_IDLE state and the RRC_INACTIVE state to discontinuously receive paging signals. DRX in the RRC_CONNECTED state (RRC_CONNECTED DRX) will be described below.

[0498] refer to Fig.18 , the DRX cycle includes an on-duration and a DRX opportunity. The DRX cycle defines the time interval between periodic repetitions of the on-duration. The on-duration is the time period during which the UE monitors the PDCCH. When the UE is configured with DRX, the UE performs PDCCH monitoring during the on-duration. When the UE successfully detects the PDCCH during the PDCCH monitoring period, the UE starts the inactivity timer and remains awake. On the contrary, when the UE fails to detect any PDCCH during the PDCCH monitoring period, the UE transitions to a sleep state after the on-duration. Therefore, when DRX is configured, PDCCH monitoring / reception may be performed discontinuously in the time domain in the process and / or method described / proposed above. For example, when DRX is configured, the PDCCH reception timing (e.g., a time slot with a PDCCH SS) may be configured discontinuously according to the DRX configuration in the present disclosure. On the contrary, when DRX is not configured, PDCCH monitoring / reception may be performed continuously in the time domain. For example, when DRX is not configured, the PDCCH reception timing (e.g., a time slot with a PDCCH SS) may be configured continuously in the present disclosure. Regardless of whether DRX is configured, PDCCH monitoring may be restricted during time periods configured as measurement gaps.

[0499] Table 10 describes the DRX operation of the UE (in the RRC_CONNECTED state). Referring to Table 10, DRX configuration information is received through higher layer signaling (e.g., RRC signaling), and DRX on / off is controlled by a DRX command from the MAC layer. Once DRX is configured, the UE may perform PDCCH monitoring discontinuously while performing the above / proposed procedures and / or methods.

[0500] [Table 10]

[0501]

[0502] MAC-CellGroupConfig includes the configuration information required to configure MAC parameters for the cell group. MAC-CellGroupConfig may also include DRX configuration information. For example, when defining DRX, MAC-CellGroupConfig may include the following information.

[0503] -drx-OnDurationTimer value: defines the duration of the start period of the DRX cycle.

[0504] - Value of drx-InactivityTimer: defines the duration of the time period that the UE wakes up after detecting a PDCCH opportunity indicating a PDCCH for initial UL or DL ​​data.

[0505] - Value of drx-HARQ-RTT-TimerDL: defines the duration of the maximum time period after receiving a DL initial transmission until a DL retransmission is received.

[0506] - Value of drx-HARQ-RTT-TimerDL: defines the duration of the maximum time period after receiving a UL initial transmission grant until receiving a UL retransmission grant.

[0507] -drx-LongCycleStartOffset: defines the duration and start time of the DRX cycle.

[0508] -drx-ShortCycle (optional): defines the duration of the short DRX cycle.

[0509] When any of drx-OnDurationTimer, drx-InactivityTimer, drx-HARQ-RTT-TimerDL and drx-HARQ-RTT-TimerDL is running, the UE performs PDCCH monitoring at each PDCCH opportunity and remains in the awake state.

[0510] The above-mentioned embodiments correspond to the combination of elements and features of the present disclosure in a prescribed form. And, unless each element or feature is explicitly mentioned, each element or feature can be considered to be selective. Each of the elements or features can be implemented in a form that cannot be combined with other elements or features. In addition, by partially combining elements and / or features together, it is possible to implement the embodiments of the present disclosure. The operation sequence explained for each embodiment of the present disclosure can be modified. Some configurations or features of an embodiment can be included in another embodiment, or can replace the corresponding configuration or features of another embodiment. And, it is obviously understandable that the embodiment is configured by combining claims that do not have an explicit reference relationship in the attached claims, or can be included as a new claim obtained by modification after submitting an application.

[0511] Those skilled in the art will appreciate that the present disclosure can be performed in other specific ways different from the ways set forth herein without departing from the spirit and essential characteristics of the present disclosure. Therefore, the above embodiments are interpreted in all respects as illustrative and not restrictive. The scope of the present disclosure should be determined by the appended claims and their legal equivalents, rather than by the above description, and all changes falling within the meaning and equivalent range of the appended claims should be included therein.

[0512] Industrial Applicability

[0513] The present disclosure is applicable to UE, BS or other devices in a wireless mobile communication system.

Claims

1. A method performed by a user equipment (UE), the method comprising: multiplexing a plurality of uplink control information (UCI) with different priorities on a physical uplink shared channel (PUSCH), the plurality of UCIs including a first UCI with a first priority index and a second UCI with a second priority index lower than the first priority index, based on the UE being configured to multiplex a plurality of uplink control information (UCI) with different priorities on a physical uplink shared channel (PUSCH); as well as transmitting the PUSCH in which the plurality of UCIs are multiplexed, In the multiplexing of the first UCI and the second UCI on the PUSCH, based on the association of the PUSCH with the second priority index, the first UCI includes first hybrid automatic repeat request acknowledgement (HARQ-ACK) information, and the second UCI includes second HARQ-ACK information: The first HARQ-ACK information of the first UCI is allocated a first amount of resources as a first UCI type for the HARQ-ACK, and The second HARQ-ACK information of the second UCI is allocated a second amount of resources as a second UCI type for channel state information (CSI) part 1, and the second amount of resources is determined based on the deduction of the first amount of resources.

2. The method according to claim 1, wherein: Based on the PUSCH being associated with the first priority index and the first UCI not including any HARQ-ACK information, the UE performs resource element (RE) reservation on the PUSCH for potential HARQ-ACK related to the first priority index.

3. The method according to claim 1, wherein: Based on the PUSCH being associated with the first priority index and the first UCI not including any HARQ-ACK information, the UE performs the multiplexing assuming that a potential HARQ-ACK related to the first priority index is of the first UCI type.

4. The method according to claim 1, wherein: Based on the PUSCH associated with the second priority index, and the first UCI includes the first HARQ-ACK information, and the second UCI includes the second HARQ-ACK information and CSI part 1 information: The CSI part 1 information of the second UCI is multiplexed on the PUSCH based on a third UCI type associated with CSI part 2.

5. The method according to claim 1, wherein: The first UCI type and the second UCI type are related to a resource allocation order.

6. The method according to claim 5, wherein: The resource allocation order is related to the New Radio Access Technology (NR) Release 15 of the 3rd Generation Partnership Project (3GPP).

7. The method according to claim 1, wherein: The two parts of CSI including the CSI part 1 and the CSI part 2 are related to the aperiodic CSI report.

8. The method according to claim 1, wherein: The second priority index is an integer of 0 and the first priority index is an integer of 1.

9. An apparatus for controlling a user equipment (UE), the apparatus comprising: a memory configured to store instructions; as well as a processor configured to perform operations by executing the instructions, The operations include: multiplexing a plurality of uplink control information (UCI) with different priorities on a physical uplink shared channel (PUSCH), the plurality of UCIs including a first UCI with a first priority index and a second UCI with a second priority index lower than the first priority index, based on the UE being configured to multiplex a plurality of UCIs with different priorities on a physical uplink shared channel (PUSCH); and transmitting the PUSCH in which the plurality of UCIs are multiplexed, In the multiplexing of the first UCI and the second UCI on the PUSCH, based on the association of the PUSCH with the second priority index, the first UCI includes first hybrid automatic repeat request acknowledgement (HARQ-ACK) information, and the second UCI includes second HARQ-ACK information: The first HARQ-ACK information of the first UCI is allocated a first amount of resources as a first UCI type for the HARQ-ACK, and The second HARQ-ACK information of the second UCI is allocated a second amount of resources as a second UCI type for channel state information (CSI) part 1, and the second amount of resources is determined based on the deduction of the first amount of resources.

10. A user equipment (UE), comprising: Transceiver; as well as a processor configured to, by controlling the transceiver, multiplex a plurality of uplink control information (UCI) having different priorities on a physical uplink shared channel (PUSCH), the plurality of UCIs including a first UCI having a first priority index and a second UCI having a second priority index lower than the first priority index, and transmit the PUSCH in which the plurality of UCIs are multiplexed, based on the UE being configured to multiplex a plurality of UCIs having different priorities on the PUSCH, In the multiplexing of the first UCI and the second UCI on the PUSCH, based on the association of the PUSCH with the second priority index, the first UCI includes first hybrid automatic repeat request acknowledgement (HARQ-ACK) information, and the second UCI includes second HARQ-ACK information: The first HARQ-ACK information of the first UCI is allocated a first amount of resources as a first UCI type for the HARQ-ACK, and The second HARQ-ACK information of the second UCI is allocated a second amount of resources as a second UCI type for channel state information (CSI) part 1, and the second amount of resources is determined based on the deduction of the first amount of resources.

11. A method performed by a base station (BS), the method comprising: receiving a physical uplink shared channel (PUSCH) from a user equipment (UE); as well as Based on the BS having configured the UE to multiplex a plurality of uplink control information (UCI) with different priorities on the PUSCH, obtaining a plurality of UCIs with different priorities, the plurality of UCIs including a first UCI with a first priority index and a second UCI with a second priority index lower than the first priority index; as well as In obtaining the first UCI and the second UCI from the PUSCH, based on the association of the PUSCH with the second priority index, the first UCI includes first hybrid automatic repeat request acknowledgment (HARQ-ACK) information, and the second UCI includes second HARQ-ACK information: The first HARQ-ACK information of the first UCI is obtained based on a first amount of resources allocated for a first UCI type of the HARQ-ACK, and The second HARQ-ACK information of the second UCI is obtained based on a second amount of resources allocated for a second UCI type of a channel state information (CSI) part 1, and the second amount of resources is determined based on a deduction of the first amount of resources.

12. A base station (BS), comprising: Transceiver; as well as a processor configured to receive a physical uplink shared channel (PUSCH) from a user equipment (UE) by controlling the transceiver, and obtain a plurality of uplink control information (UCI) with different priorities based on that the BS has configured the UE to multiplex a plurality of UCIs with different priorities on the PUSCH, the plurality of UCIs including a first UCI with a first priority index and a second UCI with a second priority index lower than the first priority index; In obtaining the first UCI and the second UCI from the PUSCH, based on the association of the PUSCH with the second priority index, the first UCI includes first hybrid automatic repeat request acknowledgment (HARQ-ACK) information, and the second UCI includes second HARQ-ACK information: The first HARQ-ACK information of the first UCI is obtained based on a first amount of resources allocated for a first UCI type of the HARQ-ACK, and The second HARQ-ACK information of the second UCI is obtained based on a second amount of resources allocated for a second UCI type of a channel state information (CSI) part 1, and the second amount of resources is determined based on a deduction of the first amount of resources.

Images