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

By encoding and resource mapping of uplink control information of different priority levels in the wireless communication system, the problem of low wireless signal transmission and reception efficiency in the prior art is solved, and multiple on a physical uplink channel are realized. UCI multiplexing and resource optimization improve communication efficiency and capacity.

CN115088368BActive Publication Date: 2025-01-03LG ELECTRONICS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280001684.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2021-10-10
Filing Date
2022-01-07
Publication Date
2025-01-03
Estimated Expiration
2042-01-07

Smart Images

  • Figure CN115088368B_ABST
    Figure CN115088368B_ABST
Patent Text Reader

Abstract

A UE according to an embodiment of the present disclosure is capable of receiving information about a plurality of β offset values ​​for determining the number of REs for UCI to be sent on a PUSCH, receiving DCI for scheduling a first PUSCH, and sending a first HARQ‑ACK on the first PUSCH, and sending a first PUSCH. The plurality of β offset values ​​may include a first β offset value for a case where the priority of the first HARQ‑ACK is the same as the priority of the first PUSCH, and a second β offset value for a case where the priority of the first HARQ‑ACK is different from the priority of the first PUSCH.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for transmitting or receiving a downlink / uplink radio signal in a 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 apparatus 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 a signal by a user equipment (UE) in a wireless communication system may include the following steps: encoding a plurality of UCIs including a first type of uplink control information (UCI) and a second type of UCI; performing resource mapping of coded bits of a plurality of UCIs on a physical uplink channel; and performing uplink transmission based on the resource mapping. Even if the first type of UCI and the second type of UCI have different priorities, the UE may be configured to multiplex the plurality of UCIs on a physical uplink channel. Based on a first type of UCI including a CG-UCI for a configuration grant (CG) operation, a second UCI including a hybrid automatic repeat request-acknowledgement (HARQ-ACK), and a CG-UCI and a HARQ-ACK having different priorities, the UE may perform (i) encoding of each of the CG-UCI and the HARQ-ACK and (ii) resource mapping of each of the CG-UCI and the HARQ-ACK.

[0008] In a state where a second priority higher than the first priority is assigned to a physical uplink channel, the UE may determine the number of resources to be allocated to HARQ-ACK among the remaining resources after determining the number of resources to be allocated to the CG-UCI. For example, based on the CG-UCI being two bits or less, the UE may perform resource mapping on the HARQ-ACK for the remaining resources other than the reserved resources, and perform resource mapping on the CG-UCI by puncturing the reserved resources. For example, based on the CG-UCI being more than two bits, the UE may perform resource mapping on the HARQ-ACK after the resource mapping on the CG-UCI.

[0009] In a state where a second priority higher than the first priority is assigned to a physical uplink channel, the UE may determine the number of resources to be allocated to the CG-UCI among the remaining resources after determining the number of resources to be allocated to the HARQ-ACK. For example, based on the HARQ-ACK being two bits or less, the UE may perform resource mapping on the CG-UCI for the remaining resources other than the reserved resources, and perform resource mapping on the HARQ-ACK by puncturing the reserved resources. For example, based on the HARQ-ACK being more than two bits, the UE may perform resource mapping on the CG-UCI after resource mapping on the HARQ-ACK.

[0010] One physical uplink channel is Configuration Grant - Physical Uplink Shared Channel (CG-PUSCH), and the priority of CG-PUSCH may be different from that of HARQ-ACK.

[0011] Joint coding of CG-UCI and HARQ-ACK with different priorities multiplexed on one physical uplink channel may not be allowed. For example, CG-UCI may be jointly coded with a specific HARQ-ACK having the same priority as CG-UCI, and the result of the joint coding may be separately coded from the HARQ-ACK included in the second type of UCI.

[0012] According to another aspect of the present disclosure, there may be provided a processor-readable recording medium storing a program for executing the above-mentioned signal transmission method.

[0013] According to another aspect of the present disclosure, a UE for executing the above-mentioned signal transmission method may be provided.

[0014] According to another aspect of the present disclosure, a device for controlling a UE that performs the above-mentioned signal transmission method may be provided.

[0015] According to one aspect of the present disclosure, a method for receiving a signal by a base station (BS) in a wireless communication system may include the following steps: receiving coded bits of a plurality of uplink control information (UCI) multiplexed on one physical uplink channel; and obtaining a first type UCI and a second type UCI by decoding the coded bits of the plurality of UCIs. Even if the first type UCI and the second type UCI have different priorities, the BS may configure the UE to multiplex the plurality of UCIs on one physical uplink channel. Based on a first type UCI including a CG-UCI for a configuration grant (CG) operation, a second UCI including a hybrid automatic repeat request-acknowledgement (HARQ-ACK), and a CG-UCI and a HARQ-ACK having different priorities, the BS may (i) determine a resource mapping for each of the CG-UCI and the HARQ-ACK, and (ii) decode each of the CG-UCI and the HARQ-ACK.

[0016] According to another aspect of the present disclosure, a BS for performing the above-mentioned signal transmission method may be provided.

[0017] Beneficial Effects

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

[0019] Those skilled in the art will appreciate that the effects that can be achieved using the present disclosure are not limited to those 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

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

[0021] Figure 1 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 same are shown.

[0022] Figure 2 Shows the radio frame structure.

[0023] Figure 3 A resource grid showing time slots.

[0024] Figure 4 An exemplary mapping of physical channels in time slots is shown.

[0025] Figure 5 An exemplary acknowledgement / negative acknowledgement (ACK / NACK) transmission process is shown.

[0026] Figure 6 An exemplary physical uplink shared channel (PUSCH) transmission process is shown.

[0027] Figure 7 An example of multiplexing control information in the PUSCH is shown.

[0028] Figures 8 to 11 is a diagram illustrating a method of transmitting and receiving a signal according to an embodiment of the present disclosure.

[0029] Figures 12 to 15 is a diagram showing an example of a communication system 1 and a wireless device applicable to the present disclosure.

[0030] Fig.16 is a diagram showing an example of a discontinuous reception (DRX) operation applicable to the present disclosure. DETAILED DESCRIPTION

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

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

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

[0034] 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 the case of...", or "when...") may be replaced with "based on..." or "under the state of...". In addition, the operation or software / hardware (SW / HW) configuration of the user equipment (UE) / base station (BS) may be derived / understood based on satisfying the corresponding conditions. When the processing of the receiving (or transmitting) side in the signal transmission / reception between the wireless communication device (e.g., BS and UE) can be derived / understood from the processing of the transmitting (or receiving) side, its description may be omitted. For example, the signal determination / generation / encoding / transmission of the transmitting side may be understood as the signal monitoring reception / decoding / determination of 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, sections, implementations, examples, options, methods, schemes, etc. are distinguished and indexed from each other, which does not mean that each of them necessarily constitutes an independent invention or that each of them should only be implemented separately. Unless explicitly contradicted with each other, it can be deduced / understood that at least some of the sections, implementations, examples, options, methods, schemes, etc. can be implemented in combination or can be omitted.

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

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

[0037] When the UE is powered on again from a power-off state or enters a new cell, in step S101, 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.

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

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

[0040] After the foregoing process, the UE may receive PDCCH / PDSCH (S107) and send a physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) (S108) 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 the request / command of the network.

[0041] Figure 2The radio frame structure is shown. 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.

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

[0043] [Table 1]

[0044] <![CDATA[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

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

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

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

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

[0049] [Table 2]

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

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

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

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

[0054] Figure 4 An exemplary mapping of physical channels in a time slot is shown. 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 transmit mode to receive mode switch or a receive mode to transmit mode switch at the BS and UE. Some symbols in a subframe at the time of DL to UL switching may be configured as GP.

[0055] The individual physical channels are described in more detail below.

[0056] PDCCH transmits DCI. For example, PDCCH (i.e., DCI) may carry information about the transmission 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 high-level control messages (e.g., RAR sent on PDSCH), transmit power control commands, information about the activation / release of the configured scheduling, etc. DCI includes a cyclic redundancy check (CRC). The CRC is masked using various identifiers (IDs) (e.g., radio network temporary identifier (RNTI)) according to the owner or purpose of the PDCCH. 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 for system information (eg, system information block (SIB)), the CRC is masked by a system information RNTI (SI-RNTI). When the PDCCH is for RAR, the CRC is masked by a random access-RNTI (RA-RNTI).

[0057] 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 to the PDCCH according to the radio channel state. CCE includes 6 resource element groups (REGs), each REG is defined by one OFDM symbol × 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 may overlap with each other in the time / frequency domain. The CORESET may be configured by system information (e.g., Master Information Block (MIB)) or UE-specific high-level signaling (e.g., Radio Resource Control (RRC) signaling). Specifically, the number of RBs and the number of symbols (up to 3) in the CORESET may be configured by high-level signaling.

[0058] For PDCCH reception / detection, the UE monitors PDCCH candidates. PDCCH candidates are CCEs that the UE should monitor to detect PDCCH. Each PDCCH candidate is defined as 1, 2, 4, 8 or 16 CCEs according to AL. Monitoring includes (blind) decoding of the 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 high-level signaling. Each CORESET is associated with one or more SSs, and each SS is associated with a CORESET. The SS can be defined based on the following parameters.

[0059] -controlResourceSetId: CORESET related to SS.

[0060] - monitoringSlotPeriodicityAndOffset: PDCCH monitoring periodicity (in time slots) and PDCCH monitoring offset (in time slots).

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

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

[0063] *The timing (eg, time / frequency resources) 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.

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

[0065] [Table 3]

[0066]

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

[0068] [Table 4]

[0069]

[0070] 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)-based (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-based (or CBG-level) PDSCH (or DL ​​grant DCI). DCI format 0_0 / 0_1 can be called UL grant DCI or UL scheduling information, and DCI format 1_0 / 1_1 can be called DL grant DCI or DL ​​scheduling information. DCI format 2_0 is used to transmit dynamic slot format information (e.g., dynamic slot format indicator (SFI)) to the UE, and DCI format 2_1 is used to transmit DL preemption information to the UE. DCI format 2_0 and / or DCI format 2_1 can be transmitted to a corresponding group of UEs on a group common PDCCH (a PDCCH pointing to a group of UEs).

[0071] 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. Under the fallback DCI format, the DCI size / field configuration remains the same regardless of the UE configuration. In contrast, under the non-fallback DCI format, the DCI size / field configuration varies according to the UE configuration.

[0072] 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 as a codeword. PDSCH can transmit up to two codewords. Scrambling and modulation mapping can be performed based on the codeword, 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 the mapped layer with DMRS and sent through the corresponding antenna port.

[0073] PUCCH transmits uplink control information (UCI). UCI includes the following information.

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

[0075] -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 may be sent. In response to two codewords, a 2-bit HARQ-ACK may be sent. HARQ-ACK responses include positive ACK (abbreviated as ACK), negative ACK (NACK), discontinuous transmission (DTX), or NACK / DTX. The term HARQ-ACK may be used interchangeably with HARQ ACK / NACK and ACK / NACK.

[0076] -CSI (Channel State Information): Feedback information of DL channels. Multiple Input Multiple Output (MIMO) related feedback information includes RI and PMI.

[0077] Table 5 shows an exemplary PUCCH format. The PUCCH format may be divided into short PUCCH (formats 0 and 2) and long PUCCH (formats 1, 3, and 4) based on PUCCH transmission duration.

[0078] [Table 5]

[0079]

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

[0081] PUCCH format 1 transmits up to 2 bits of UCI and the modulation symbol of UCI is spread in the time domain with an orthogonal cover code (OCC) (configured differently depending on whether frequency hopping is performed). DMRS is transmitted in symbols where modulation symbols are not transmitted (ie, transmitted in time division multiplexing (TDM)).

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

[0083] PUCCH format 3 does not support multiplexing of UEs in the same PRBS and transmits 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 sent in TDM.

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

[0085] The PUSCH transmits 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 in 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 may transmit the PUSCH in a CP-OFDM waveform, and when transform precoding is possible (e.g., enabled), the UE may transmit the PUSCH in a CP-OFDM or DFT-s-OFDM waveform. PUSCH transmission may be dynamically scheduled by a UL grant in a DCI, or semi-statically scheduled (configuration scheduling or configuration grant) by higher layer (e.g., RRC) signaling (and / or layer 1 (L1) signaling such as a PDCCH). PUSCH transmission may be performed in a codebook-based or non-codebook-based manner.

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

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

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

[0089] -PDSCH-to-HARQ_feedback timing indicator: indicates K1.

[0090] -HARQ process number (4 bits): indicates the HARQ process ID of the data (eg, PDSCH or TB).

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

[0092] After receiving PDSCH in slot #(n+K0) according to the scheduling information of slot #n, the UE may send UCI on PUCCH in slot #(n+K1). UCI may include a HARQ-ACK response to PDSCH. For convenience, Figure 5 Based on the assumption that the SCS of PDSCH is equal to the SCS of PUCCH and slot #n1=slot #(n+K0), this should not be construed as limiting the present disclosure. When the SCSs are different, K1 may be indicated / interpreted based on the SCS of PUCCH.

[0093] In the case where the PDSCH is configured to carry up to one 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, if spatial bundling is not configured, the HARQ-ACK response may be configured in two bits, and if spatial bundling is configured, the HARQ-ACK response may be configured in one bit. When slot #(n+K1) is designated as the HARQ-ACK transmission timing of multiple PDSCHs, the UCI sent in slot #(n+K1) includes HARQ-ACK responses to multiple PDSCHs.

[0094] Whether the UE should perform spatial bundling for HARQ-ACK responses may be configured for each cell group (e.g., via RRC / high-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.

[0095] Spatial bundling can be supported when up to two (or two or more) TBs (or codewords) can be received at a time (can be or be scheduled by one DCI) in the corresponding serving cell (for example, when the high-level parameter maxNrofCodeWordsScheduledByDCI indicates 2 TBs). More than four layers can be used for 2TB transmission, and up to four layers can be used for 1TB transmission. As a result, when spatial bundling is configured for the corresponding cell group, spatial bundling can be performed for serving cells in the cell group where more than four layers can be scheduled. A UE that wants to send a HARQ-ACK response through spatial bundling can generate a HARQ-ACK response by performing a (bit-by-bit) logical AND operation on the A / N bits of multiple TBs.

[0096] 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 of a first TB and a second A / N bit of 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 TB is NACK, the UE reports a NACK bit value to the BS.

[0097] 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 of the one TB and a bit value 1. As a result, the UE reports the A / N bits of the one TB to the BS.

[0098] There are multiple parallel DL HARQ processes at the BS / UE for DL ​​transmissions. Multiple parallel HARQ processes allow continuous DL transmissions while the BS waits for HARQ feedback indicating the success or failure of reception of the previous DL transmission. Each HARQ process is associated with a HARQ buffer in the medium 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.

[0099] Figure 6 An exemplary PUSCH transmission process is shown. 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.

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

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

[0102] Then, the UE may transmit the PUSCH in slot #(n+K2) according to the scheduling information in slot #n. The PUSCH includes the UL-SCH TB.

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

[0104] For piggybacking of HARQ-ACK in NR Rel.16, when the payload of HARQ-ACK is 2 bits or less, PUSCH data RE (and / or CSI part 2 RE) is 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 TS38.212.

[0105] [Table 6]

[0106]

[0107]

[0108]

[0109]

[0110] In Table 6, the β offset “β offset PUSCH ” is the rate matching weight for UCI on PUSCH and is related to the amount of resources to be used for HARQ-ACK and CSI reporting when sending PUSCH. β offset The set s can be configured via higher layer signaling. offset Collections can be used semi-statically, or beta offset The set may be dynamically indicated by DCI (e.g., UL grant DCI format 0_1 / 0_2). offset In the indication method, the β offset indication field of the DCI includes 2 bits, indicating the four β offsets configured for the UE.offset 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 size of the corresponding payload offset For example, the first β 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.

[0111] NR shared spectrum / unlicensed band (NR-U) operation

[0112] A communication node (eg, a BS or UE) operating in an unlicensed band should determine whether other communication nodes are using a channel before transmitting a signal.

[0113] Definitions of terms related to NR-U operations:

[0114] - Channel: A carrier or a portion of a carrier comprising contiguous RBs in a shared spectrum where a channel access procedure (CAP) is performed.

[0115] - Channel Access Procedure (CAP): A procedure for evaluating the availability of a channel based on sensing to determine whether the channel is used by other communication nodes before signal transmission. CAP may be referred to as Listen Before Talk (LBT).

[0116] - Channel occupancy: Transmissions from BS / UE on the channel after CAP.

[0117] - Channel Occupancy Time (COT): The total time that a BS / UE and any BS / UE sharing the channel occupancy perform transmissions on the channel after the BS / UE corresponding CAP. When determining the COT, if the transmission gap is less than or equal to 25us, the gap duration may also be included in the COT. The transmissions between the BS and the corresponding UE may share the COT.

[0118] If a subband (SB) in which LBT is performed separately is defined as an LBT-SB, multiple LBT-SBs may be included in one broadband cell / BWP. The RB set forming the LBT-SB may be configured by high-layer signaling (e.g., RRC signaling). Therefore, based on (i) the BW of the cell / BWP and (ii) the RB set allocation information, a cell / BWP may include one or more LBT-SBs. Multiple LBT-SBs may be included in the BWP of a cell (or carrier). The LBT-SB may have a frequency band of, for example, 20 MHz. The LBT-SB may include multiple consecutive (P) RBs in the frequency domain and may be referred to as a (P) RB set. Although not shown, a guard band (GB) may be included between the LBT-SBs. Therefore, the BWP may be configured in the form of {LBT-SB#0 (RB set #0)+GB#0+LBT-SB#1 (RB set #1+GB#1)+...+LBT-SB#(K-1) (RB set (#K-1))}. For convenience, LBT-SB / RB may be configured / defined to be increasingly indexed from a lower frequency band to a higher frequency band.

[0119] (1) Type 1 CAP method

[0120] The BS in the Type 1 DL CAP and the UE in the Type 1 UL CAP may detect whether the channel is idle during the sensing slot duration of the deferral duration Td and perform transmission after the counter N is zero. The counter N is adjusted by sensing the channel during the additional sensing slot duration according to the following process:

[0121] Step 1) Set N=Ninit, where Ninit is a random number uniformly distributed between 0 and CWp, and go to step 4.

[0122] Step 2) If N>0 and BS chooses to decrement the counter, then set N=N-1.

[0123] Step 3) Sense the channel during the additional sensing slot duration, and if the additional sensing slot duration is idle, go to step 4; otherwise, go to step 5.

[0124] Step 4) If N=0 (Y), stop; otherwise, go to step 2,

[0125] Step 5) The channel is sensed until a busy sensing slot is detected within the additional deferral duration Td, or all sensing slots of the additional deferral duration Td are detected as idle.

[0126] Step 6) If the channel is sensed as idle during all sensing time slot durations of the additional deferral duration Td, go to step 4; otherwise, go to step 5.

[0127] Type 1 UL CAP is applicable to the following transmissions.

[0128] -PUSCH / SRS transmission scheduled and / or configured by the BS

[0129] - PUCCH transmissions scheduled and / or configured by the BS

[0130] - Transmissions related to the Random Access Procedure (RAP)

[0131] Type 2 CAP is a CAP performed without random backoff. Types 2A, 2B, and 2C are defined for DL, and Types 2A, 2B, and 2C are defined for UL. In a Type 2A UL CAP, the UE may send a signal immediately after the channel is sensed to be idle during at least the sensing duration Tshort_dl (=25us). Tshort_dl includes a sensing slot duration and a duration Tf (=16us) immediately following it. In a Type 2A UL CAP, Tf includes a sensing slot at the beginning of the duration. In a Type 2B UL CAP, the UE may send a signal immediately after the channel is sensed to be idle within the sensing duration Tf (=16us). In a Type 2B UL CAP, Tf includes a sensing slot within the last 9us of the duration. In a Type 2C ULCAP, the UE does not sense the channel before performing a transmission.

[0132] Configuration License (CG)

[0133] A semi-static configuration grant (CG) may be configured for a UE via RRC signaling. A maximum of 12 active CGs may be configured for a UE in the corresponding BWP of the serving cell.

[0134] Each CG can be type 1 or type 2. Type 1 CG can be enabled / disabled independently between serving cells. When multiple type 2 CGs are configured, each type 2 CG can be enabled individually through DCI. One DCI can disable one type 2 CG or multiple type 2 CGs.

[0135] For CG-based transmissions in NR-U (i.e., shared spectrum channel access), the configuration grant uplink control information (CG-UCI) is sent on the corresponding CG PUSCH (i.e., PUSCH scheduled by the CG). Multiplexing between PUCCH carrying CG-UCI and PUCCH carrying HARQ-ACK in NR-U may be configured / allowed by the BS. When multiplexing between PUCCH carrying CG-UCI and PUCCH carrying HARQ-ACK is not configured, and the PUCCH carrying HARQ-ACK overlaps with the CG PUSCH within the PUCCH group, the CG PUSCH transmission is discarded.

[0136] UCI multiplexing on PUSCH for URLLC

[0137] To support data transmission / services where reliability / delay performance is important (e.g., URLLC), service / protection priorities (e.g., low priority (LP) or high priority (HP)) may be configured for the UE semi-statically (via RRC signaling) or dynamically (via DCI signaling or MAC signaling) for each physical channel / signal (transmission resource) (e.g., PUSCH) and control information (e.g., UCI).

[0138] Specifically, priority indicators have been introduced to 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 configured for a corresponding DCI format through high-layer signaling, the UE blindly decodes the DCI format assuming that the priority indicator exists. In the absence of explicit signaling indicating that a priority indicator will be used for a DCI format, the UE blindly decodes the DCI format assuming that a priority indicator is not included in the DCI format. When priority information is not provided for the corresponding DL / UL signal, the UE may assume LP (e.g., priority index = 0) for the DL / UL signal. Those skilled in the art will appreciate that the priority indicator of the DCI is one of various means for indicating / configuring priority, not the only method.

[0139] In the above-mentioned priority ordering example, a lower priority index may be configured / indicated for LP, and a higher priority index may be configured / indicated for HP. Alternatively, 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.

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

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

[0142] In Rel.15 / 16 NR, two parameters (β offset (βoffset) and α factor α (see, for example, Table 6)) are configured / used for UCI multiplexing (e.g., coding / mapping) on ​​PUSCH. βoffset is a parameter that determines the coding rate of UCI (i.e., the number of REs to which UCI (coded bits) is mapped). βoffset can be configured / indicated for each individual UCI type. The α factor is a parameter that limits the maximum number of REs that can be used to map the entire UCI (the upper limit of multiplexed UCI REs). The α factor α can be indicated by the high-level parameter 'scaling' and may also be referred to as the scaling factor α in some cases.

[0143] Table 7 shows the configuration structure / method related to βoffset and α factor in 15 / 16NR.

[0144] [Table 7]

[0145]

[0146] Table 8 is a diagram of the dynamic β described with reference to Table 7. offset Partial excerpt from the relevant NR standard document 3GPP TS38.213 Rel.16.

[0147] [Table 8]

[0148]

[0149] To describe the dynamic β offset , depending on the DCI configuration / format, indicates the dynamic β in the DCI offset The beta_offset indicator field of the value can be 2 bits ("Table 9.3-3" in Table 8) or 1 bit ("Table 9.3-3A" in Table 8). When the beta_offset indicator field of the DCI is two bits, the four beta values ​​configured by higher layer signaling (RRC signaling) are offsetSet (the 1st / 2nd / 3rd / 4th offset index provided by the higher layer in "Table 9.3-3" of Table 8), and when the beta_offset indicator field of the DCI is one bit, two beta values ​​are configured through higher layer signaling (RRC signaling). offset Set (the 1st / 2nd offset index provided by the higher layer in "Table 9.3-3A" of Table 8). Each β offset The set includes seven beta offset value, and these seven β offset The value is given as ( or or )、( or )、( or ). These seven β offset The values ​​are {B_a1, B_a2, B_a3}, {B_c11, B_c12}, {B_c21, B_c22} in Table 7. “(...or...or)” means to select the corresponding β offset For example, assuming that the beta_offset indicator = 01 is indicated to the UE, so the UCI includes HARQ-ACK, and the UE selects the second beta based on the beta_offset indicator = 01. offset (a) When the size of the HARQ-ACK is less than or equal to two bits, the UE selects the 2nd β offset Set selection B_a1(=I offset,0 HARQ-ACK ), (b) When the size of HARQ-ACK is greater than two bits and less than or equal to 11 bits, the UE selects the second β offset Set selection B_a2(=I offset,1 HARQ-ACK ), and (c) when the size of HARQ-ACK is greater than 11 bits, the UE selects the 2nd β offset Set selection B_a3(=I offset,1 HARQ-ACK ). On the other hand, due to the semi-static β offset Instructs the scheme to configure a beta offset Set, so β offset The set is not indicated by the beta_offset indicator of the DCI.

[0150] Therefore, the present disclosure proposes a method of configuring / indicating β considering a combination of multiple UCIs configured / indicated with different priorities (e.g., LP or HP) and a combination of UCIs and PUSCHs configured / indicated with different priorities. offsetMethod for α factor. For the sake of convenience of description, the UCI configured / indicated to have LP / HP is respectively called LP UCI / HP UCI, and the PUSCH indicated / configured to have LP / HP is respectively called LP PUSCH / HP PUSCH. In addition, the case where the UCI multiplexed on the PUSCH only includes the UCI with a specific priority XP (e.g., LP or HP) is defined as the "only XP" case, the case where the UCI multiplexed on the PUSCH includes both the XP UCI and the UCI with a different priority YP (e.g., HP or LP) is defined as the "XP+YP" case, and the case where the UCI multiplexed on the PUSCH includes at least the XP UCI (e.g., "only XP" or "XP+YP") is defined as the "with XP" case.

[0151] [1] β for combinations of UCI and PUSCH with different priorities offset Configuration / instructions

[0152] 1) Semi-static β offset

[0153] A. β (set of values) can be configured for each PUSCH priority (e.g., LP / HP) (combination). For example, for two UCI+PUSCH priority combinations {XP+XP} and {YP+XP} of the XP PUSCH, 7 β values can be configured for each combination offset (if XP = LP, then YP = HP, and if XP = HP, then YP = LP). For example, when it is said that 7 β values can be configured for the combination {YP+XP}, for one UE, this can be understood as (i) configuring 7 β values in the case of XP > YP offset and (ii) configuring 7 β values in the case of XP < YP. Since (i) XP > YP and (ii) XP < YP are incompatible conditions, either (i) or (ii) can be used, and (i) and (ii) are not used together. offset offset offset offset offset offset

[0154] i. And / or, for each of the two UCI cases {only XP, with YP} of the XP PUSCH, 7 β values can be configured for the XP UCI. For example, when only the XP UCI is sent on the XP PUSCH without the YP UCI, 7 β values can be configured offset offset offset offset offset offset

[0155] ii. and / or, for each of the two UCI cases {LP only, with HP} for HP PUSCH, 7 β can be configured for LP UCI offset , and / or for each of the two UCI cases of LP PUSCH {LP only, with HP}, 7 β values ​​may be configured for LPUCI offset For example, 7 β values ​​may be configured for the case where only LP UCI is sent on the HP PUSCH (without HP UCI). offset 7 β values ​​can be configured for the case where HP UCI is sent on HP PUSCH (in addition to LP UCI) offset For example, 7 β values ​​may be configured for the case where only LP UCI (without HP UCI) is sent on LP PUSCH. offset 7 β values ​​can be configured for the case where HP UCI is sent on LPPUSCH (in addition to LP UCI) offset value.

[0156] B. The above β based on each UCI+PUSCH priority combination offset Configuration, UE / BS can be operated to apply the priority combination configuration of UCI and PUSCH actually scheduled / configured / corresponding to β offset value.

[0157] C. For UL-SCH protection, the BS may configure / apply a small β value less than 1.0 (including 0) for / to the UE only for HP PUSCH. offset value, and in the semi-static β offset In the case of , this small β may be configured only for LP CSI (e.g., CSI part 1 and / or part 2, or only CSI part 2). offset value.

[0158] 2) Dynamic β offset

[0159] A. For dynamic β offset Operation, β can be configured for each PUSCH priority (e.g., LP / HP) offset Value (set) (e.g. Figure 8 ), and then a dynamic indication may be performed (e.g., by Figure 8 For example, for each of the two UCI+PUSCH priority combinations {XP+XP} and {YP+XP} of the XP PUSCH (scheduled by the DCI), the four β offset The sets (e.g., with set index = 0, 1, 2, and 3) can be configured by RRC signaling. For example, when it is said that 4 β can be configured for the combination {YP+XP}offset Upon aggregation, this can be understood as (i) configuring 4 β sets for the case of XP > YP offset aggregation and (ii) configuring 4 β sets for the case of XP < YP offset aggregation. Since (i) XP > YP and (ii) XP < YP are incompatible conditions, either (i) or (ii) can be used (e.g., Figure 8 DCI indication / UE selection in operations 810 / 815), and (i) and (ii) are not used together. Each β set offset may include 7 β values (e.g., Table 7 / 8). offset Fig. 9 Shows an example referred to for RRC configuration and DCI indication of β sets for dynamic β offset operations. Referring to offset , the β indicator of DCI Fig. 9 can be one bit or two bits. When the β indicator of DCI (e.g., UL grant DCI scheduling XP PUSCH) is one bit, two β sets corresponding to set indices 0 and 1 can be configured for the UE RRC, while when the β indicator of DCI is two bits, four β sets corresponding to set indices 00, 01, 10, and 11 can be configured for the UE RRC. For the sake of description, assume that the β indicator is 2 bits and dynamically indicates any one of set indices 00, 01, 10, and 11. Each β set offset includes a β value 905 for sending XP HARQ-ACK on XP PUSCH and a β value 910 for sending YP HARQ-ACK on XP PUSCH. In some cases, only CSI part 1 / 2 without XP / YP HARQ-ACK may be sent on XP PUSCH, or CSI part 1 / 2 may be sent on XP PUSCH in addition to XP / YP HARQ-ACK. However, to avoid ambiguity, the description of CSI part 1 / 2 transmission is omitted. YP HARQ-ACK can also be sent on XP PUSCH in addition to XP HARQ-ACK. In this case, the β value 905 and the β value 910 are used together. The β value 910 for sending YP HARQ-ACK on XP PUSCH includes (i) β for the case of XP > YP offset offset offset offset offset offset offset offset offset offset offset offset offset ​​​​​​​​​​​​​Value 910a (i.e., LP HARQ-ACK transmission on HP PUSCH) and (ii) β for the case of XP < YP offset Value 910b (i.e., HP HARQ-ACK transmission on LP PUSCH). Since (i) XP > YP and (ii) XP < YP are incompatible conditions, either (i) β offset Value 910a or (ii) β offset Value 910b can be used, and (i) and (ii) are not used together. For example, even if both (i) β offset Value 910a and (ii) β offset Value 910b are configured for the UE via RRC signaling, the UE selects either (i) β offset Value 910a or (ii) β offset Value 910b to send YP UCI on XP PUSCH ( Figure 8 in operation 815). β offset Value 905 can be used for both (i) and (ii). The UE selects I offset,0 HARQ-ACKx 、I offset,1 HARQ-ACKx and I offset,2 HARQ-ACKx from any of them to send UCI on XP PUSCH ( Figure 8 in operation 815).

[0160] i. And / or, for each of the two UCI cases {only XP, with YP} of XP PUSCH, four β offset sets can be configured for XP UCI. For example, when only XP UCI is sent on XP PUSCH without YP UCI, 4 β offset sets can be configured, and when YP UCI is also sent on XP PUSCH (in addition to XP UCI), four β offset sets can be configured (for each of the cases (i) XP > YP and (ii) XP < YP).

[0161] ii. And / or, for each of the two UCI cases {only LP, with HP} of HP PUSCH, four β offset sets can be configured for LP UCI, and / or for each of the two UCI cases {only LP, with HP} of LP PUSCH, four β offset sets can be configured for LP UCI. For example, 4 β offset4 β sets may be configured for the case where HP UCI is also sent on HP PUSCH (in addition to LP UCI) offset For example, 4 β sets may be configured for the case where only LP UCI (without HP UCI) is sent on LP PUSCH. offset 4 β sets may be configured for the case where HP UCI is also sent on LP PUSCH (in addition to LP UCI) offset gather.

[0162] B. β configured for each of the above two combinations offset The set of set indexes X, that is, {set index X configured in the XP+XP combination and set index X configured in the YP+XP combination} can be mapped to the β of the DCI offset The indicator field indicates a state X (e.g. Figure 8 Operation 810 and Fig. 9 middle).

[0163] C. Applicable as β mapped to DCI offset The priority combination configuration of PUSCH and UCI scheduled by DCI between the two sets of states indicated by the indicator field / the β of the corresponding set offset value.

[0164] D. The above small β can be configured / applied only for the UCI+PUSCH combination {LP+HP} offset Values ​​(e.g., β less than 1 offset In this case, a small β value may also be configured only for LP CSI (e.g., CSI part 1 and / or part 2 or only CSI part 2). offset value.

[0165] E. Semi-static β can be configured for each priority combination of PUSCH and UCI for fallback PUSCH and / or CG PUSCH offset value, and can be applied as the actual UCI+PUSCH priority combination configuration / corresponding β offset value.

[0166] [2] Configuration / indication of alpha factor for combinations of UCI and PUSCH with different priorities

[0167] 1) Semi-static alpha factor

[0168] A. The alpha factor may be configured for each PUSCH priority (e.g., LP / HP) (combination). For example, the alpha factor may be configured for each of the two UCI cases {LP only, with HP}, three UCI cases {LP only, HP only, LP+HP}, two UCI cases {XP only, with YP}, or three UCI cases {XP only, YP only, XP+YP} of XP PUSCH.

[0169] i. Alternatively, an α factor value may be configured for each UCI priority (combination) of the XP PUSCH (e.g., for each of the LP UCI and the HP UCI). In this case, the UE / BS may apply the α factor value configured for the specific priority of the UCI to determine the number of REs to which the UCI with the specific priority is mapped.

[0170] B. Based on the above description, the α factor value configured / corresponding to the priority combination of UCI and PUSCH (and UCI case type) actually scheduled / configured may be applied.

[0171] C. A small alpha factor value less than 0.5 (including 0) may be configured / applied for protecting UL-SCH (eg, on HPPUSCH). A small alpha factor value may be configured only for HP PUSCH and / or LP UCI (eg, "LP only" case).

[0172] 2) Dynamic alpha factor

[0173] A. The alpha factor may be RRC-configured for each PUSCH priority (e.g., LP / HP) (combination) and then dynamically indicated by DCI. For example, for each of the two UCI cases {LP only, with HP}, three UCI cases {LP only, HP only, LP+HP}, two UCI cases {XP only, with YP}, or three UCI cases {XP only, YP only, XP+YP} of XP PUSCH, a set (defined as an "alpha factor set") each having K (e.g., K=4) alpha factor values ​​(e.g., with set index = 0, 1, ..., K-1) may be configured by RRC signaling.

[0174] i. Alternatively, an α factor set may be configured for each UCI priority level of XP PUSCH (e.g., each of LP UCI and HP UCI). In this case, the UE may apply the α factor set configured for a specific priority level of UCI to determine the number of REs to which UCI with a specific priority level is mapped.

[0175] B. The set of alpha factor set indices X configured in each of the above two (or three) UCI ​​cases may be mapped to a state X indicated by a specific field (for the purpose of indicating the alpha factor) in the DCI.

[0176] i. For example, it is possible to configure (i) {two sets with set index X configured for the "LP only" case and set index X configured for the "with HP" case}, (ii) three sets with {set index X configured for the "LP only" case, set index X configured for the "HP only" case, and set index X configured for the "LP+HP" case}, {set index X configured for the "XP only" case and set index X configured for the "with YP" case}, or (iv) three sets with {set index X configured for the "XP only" case, set index X configured for the "YP only" case, and set index X configured for the "XP+YP" case}.

[0177] C. Depending on the priority combination (and UCI case type) of PUSCH and UCI scheduled by DCI, the α factor value of the set configured / corresponding to the priority combination (and UCI case) among the two (or three) sets belonging to the state indicated by the specific field mapped to the DCI can be applied.

[0178] D. A small α factor value less than 0.5 (including 0) may be configured / applied for UL-SCH protection, and even in this case, a small α factor value may be configured only for HP PUSCH and / or only for LP UCI (e.g., only in the “LP only” case).

[0179] E. On the other hand, a separate semi-static alpha factor value may be configured for each combination of PUSCH / UCI priority and UCI case, which is applied when a dynamic alpha factor as described above is not indicated (eg, fallback PUSCH or CG PUSCH as described above).

[0180] [3] Processing operations related to HP HARQ-ACK multiplexing on LP PUSCH

[0181] 1) Problem situation

[0182] A. In the case where HP HARQ-ACK (and / or LP HARQ-ACK and / or LP CSI) is multiplexed on LP PUSCH, (a) based on the β indicated / configured (by DCI) for the HP HARQ-ACK (to be multiplexed on LP PUSCH) offset The number of REs required for mapping HP HARQ-ACK is defined as N h , and (b) the total number of available REs in the PUSCH resources (to which UCI other than DMRS / PTRS can be mapped) is defined as N t (and the α factor is defined as α). Then, if N h >α*N t , or if N hGreater than or less than α*N t A specific value (=M<α*N t )(and if the number of REs used for HP HARQ-ACK mapping is limited to {α*N t}, as is usually the case in this case), the transmission performance of HP HARQ-ACK (e.g., HP UCI reliability) may deteriorate. For example, when the total number of REs available for UCI on LP PUSCH is N t The total number of REs that can be used for (HP) UCI ​​multiplexing is α*N t , the number of REs required for transmission of the HP UCI (eg, HP HARQ-ACK) calculated based on the payload of the HP UCI (eg, HP HARQ-ACK) is N h , and N h >α*N t or N h Greater than or less than α*N t A specific value (=M<α*N t ), since the number of REs used for HP UCI is insufficient, the HP UCI performance may be degraded. A solution to this problem will be described below.

[0183] 2) The proposed method

[0184] A. Option 1

[0185] i. If (as described above) HP HARQ-ACK (and / or LP HARQ-ACK and / or LPCSI) is multiplexed on LP PUSCH N h >α*N t or N h Greater than or less than α*N t t (=M<α*Nt), the UE / BS can preferentially allocate N h REs are used for HPHARQ-ACK mapping, and all remaining {N t -N h {N REs are used for UL-SCH mapping. For example, the UE may discard multiplexing transmission on the LP PUSCH for the remaining UCI (e.g., LP HARQ-ACK and / or LP CSI) except for the HPHARQ-ACK. Alternatively, at least some other UCI (e.g., HP CSI, LP HARQ-ACK and / or LP CSI) and then the UL-SCH may be mapped to the remaining {N REs. t -N h}REs.

[0186] ii. Alternatively, in this case, the UE / BS may determine the number of REs to be allocated for mapping HP UCI, LP UCI, and UL-SCH based on an assumption of a specific α value (e.g., α=1.0). For example, even if the α factor actually configured for the UE is the first value (e.g., the first value<1), the UE / BS may determine the number of REs to be allocated for mapping HP UCI, LP UCI, and UL-SCH based on an assumption of a specific α value (e.g., α=1.0). h >α*N t or N h >M, the UE may be operated (exceptional) assuming that the UE is configured with an α factor of a second value (e.g., second value=1). The UE operation may be defined such that the above operations of performing UCI multiplexing / mapping on the LP PUSCH are limited to N only under the assumption of a specific α factor (e.g., second value=1) instead of the actually configured α factor (e.g., first value<1). h >α*N t or N h >M, or always multiplex HP HARQ-ACK on LP PUSCH.

[0187] B. Option 2

[0188] i. If (as described above) HP HARQ-ACK (and / or LP HARQ-ACK and / or LPCSI) is multiplexed on LP PUSCH N h >α*N t or N h >M, the LP PUSCH transmission may be discarded and all UCI including HP HARQ-ACK (e.g., LP HARQ-ACK and / or LP CSI) may be sent (by multiplexing) on ​​the PUCCH or on a PUSCH other than the LP PUSCH. For example, if HP HARQ-ACK (and / or LP HARQ-ACK and / or LP CSI) is multiplexed on the LP PUSCH, N h >α*N t or N h >M, then the first UCI including at least HP HARQ-ACK may be sent on the first PUCCH, and the LP PUSCH transmission may be discarded. For example, the first UCI may also include HP UCI (e.g., HP CSI) and / or LP HARQ-ACK (according to the corresponding PUCCH resource / format). For example, the first PUCCH may be an HP PUCCH or an LP PUCCH. For example, the first PUCCH may be located first among the HP / LP PUCCH in the time domain.

[0189] C. Option 3

[0190] i. If (as described above) HP HARQ-ACK (and / or LP HARQ-ACK and / or LPCSI) is multiplexed on LP PUSCH N h >α*N t or N h >M, the UE may map only the UCI including the HP HARQ-ACK on the LP PUSCH while discarding the UL-SCH mapping / transmission. For example, in the case where there is other UCI to be sent in addition to the HP HARQ-ACK (e.g., LP HARQ-ACK and / or LP CSI), the UE may first allocate N h REs are used for HP HARQ-ACK mapping. Conversely, in the case where there is no other UCI to be sent besides HPHARQ-ACK, the UE may allocate all N REs. t In the latter case, HP HARQ-ACK can be mapped to more than N REs. h N t RE.

[0191] D. Attention

[0192] i. In the above example, one of Option 1, Option 2, and Option 3 may always be applied regardless of the PUCCH / UCI combination that overlaps with the LPPUSCH in time. Alternatively, in case 1) when LP HARQ-ACK is not included in the PUCCH / UCI that overlaps with the LP PUSCH in time, Option 1 may be applied, and in case 2) (HP HARQ-ACK and) LP HARQ-ACK are included in the PUCCH / UCI that overlaps with the LP PUSCH in time, one of Option 2 and Option 3 may be applied.

[0193] ii. Since the method proposed in "2)" above is related to the α factor (e.g., the determination / lack of the number of UCI REs), it can be used without the above semi-static / dynamic β offset to the extent of conflict, or they may be executed separately.

[0194] iii. Fig.10 2) is a diagram showing an embodiment of the method proposed in step 2. Fig.10 UE can receive the α 1 The UE calculates the number of REs N required for HP HARQ-ACK transmission when it needs to send HP HARQ-ACK on LP PUSCH. h (A10). Unless N h >α1*N t or N h>M, the UE may send UCI (A25) including HP HARQ-ACK on the LP PUSCH based on α1 configured through higher layer signaling. h >α1*N t or N h >M, the UE may send UCI including HP HARQ-ACK (while ignoring α1 configured by higher layer signaling) (A20). For example, HP HARQ-ACK may be transmitted on PUCCH or on LP PUSCH with N h REs are sent (e.g., option 1 / 2 / 3).

[0195] Fig.11 An implementation example of a method of transmitting and receiving a signal according to an embodiment of the present disclosure is shown. Fig.11 It is to help understand the foregoing examples, rather than to limit the scope of the present disclosure. Redundant descriptions can be avoided, and reference can be made to the previous descriptions when necessary.

[0196] Reference Fig.11 , the UE may receive information about a plurality of β offsets (β offset ) value information (B05).

[0197] The UE may receive DCI scheduling the first PUSCH ( B10 ).

[0198] The UE may map the first UCI including the first HARQ-ACK on the first PUSCH based on the multiple β offset values ​​and the β offset indicator included in the DCI (B15).

[0199] The UE may send a first PUSCH (B20).

[0200] Even if the priority of the first HARQ-ACK is different from the priority of the first PUSCH, the UE may be configured to map the first HARQ-ACK on the first PUSCH.

[0201] The plurality of β offset values ​​may include a first β offset value for a case where the priority of the first HARQ-ACK is the same as the priority of the first PUSCH and a second β offset value for a case where the priority of the first HARQ-ACK is different from the priority of the first PUSCH.

[0202] The UE may select a β offset value indicated by a β offset indicator included in the DCI from among the first β offset values ​​or a β offset value indicated by a β offset indicator included in the DCI from among the second β offset values ​​based on the priority of the first HARQ-ACK.

[0203] The N field states that may be indicated by the β offset indicator included in the DCI may be related to the N β offset indexes.

[0204] The first β offset value may include a β offset value for each of the N field states, and the second β offset value may include a β offset value for each of the N field states. For example, a specific one of the N field states may be indicated by the DCI. The UE may determine the number of REs for the first UCI to be mapped on the first PUSCH based on the first β offset value and the second β offset value configured for the indicated specific state.

[0205] The β offset indicator included in the DCI may be 2 bits, and the N field states may be related to the β offset set index {00, 01, 10, 11}. For example, the first β offset value may include the β offset value of each of the four β offset set indexes {00, 01, 10, 11}, and the second β offset value may include the β offset value of each of the four β offset set indexes {00, 01, 10, 11}.

[0206] The second β offset value may include (i) a β offset value for a case where the priority of the first HARQ-ACK is higher than the priority of the first PUSCH and (ii) a β offset value for a case where the priority of the first HARQ-ACK is lower than the priority of the first PUSCH. For example, based on whether the priority of the first PUSCH is the first priority or the second priority higher than the first priority, the UE may select from the second β offset value (i) a β offset value for a case where the priority of the first HARQ-ACK is higher than the priority of the first PUSCH or (ii) a β offset value for a case where the priority of the first HARQ-ACK is lower than the priority of the first PUSCH.

[0207] Mapping of the first UCI on the first PUSCH may include: based on a first α value α configured through higher layer signaling 1 To calculate the total number of available UCI REs on the first PUSCH, “N t "; and calculating the number of REs "M" for mapping the first HARQ-ACK based on the multiple β offset values ​​and the specific β offset value determined based on the β offset indicator included in the DCI. For example, based on the first HARQ-ACK having a second priority higher than the first priority and "M" being greater than "α 1 *N t ”, the UE may map only the UCI including the first HARQ-ACK to a total of “N t "RE. For example, based on the first HARQ-ACK having a second priority higher than the first priority and "M" being greater than "α 1 *N t", assuming that the second α value α is configured through high-level signaling 2 , the UE may map the first HARQ-ACK to a total of “a 2 *N t " specific "M" REs among " REs. Preferably, one of {0.5, 0.65, 0.8, 1.0} can be configured as the first α value through high-layer signaling, and the second α value can be fixed to 1.

[0208] For example, based on the first HARQ-ACK having a second priority higher than the first priority and “M” being greater than “α 1 *N t ", the UE may send the first HARQ-ACK only on the PUCCH while discarding the transmission of the first PUSCH, or multiplex and send the first HARQ-ACK on a second PUSCH other than the first PUSCH.

[0209] Fig.12 A communication system 1 applied to the present disclosure is shown.

[0210] Reference Fig.12 , the communication system 1 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 a head mounted device (HMD), a head up display (HUD) installed in a vehicle, a television, a smart phone, a computer, a wearable device, a home appliance device, a digital sign, a vehicle, a robot, 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.

[0211] 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). An IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., a sensor) or other wireless devices 100a to 100f.

[0212] Wireless communication / connection 150a, 150b or 150c may be established between wireless devices 100a to 100f / BS 200 or BS 200 / BS 200. Herein, wireless communication / connection may 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 may send / receive radio signals to / from each other through wireless communication / connection 150a and 150b. For example, wireless communication / connection 150a and 150b may send / receive signals through various physical channels. To this end, at least a portion of various configuration information for configuring a process for sending / receiving a radio signal, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, and resource mapping / demapping), and a resource allocation process may be performed based on various proposals of the present disclosure.

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

[0214] Reference Fig.13 , 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.12 {wireless device 100x and BS 200} and / or {wireless device 100x and wireless device 100x}.

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

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

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

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

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

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

[0221] Fig.14 Another example of a wireless device applicable to the present disclosure is shown. The wireless device can be used according to the usage / service (refer to Fig.12 ) are implemented in various forms.

[0222] Reference Fig.14 , the wireless devices 100 and 200 may correspond to Fig.13The 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.13 One or more processors 102 and 202 and / or one or more memories 104 and 204. For example, the transceiver 114 may include Fig.13 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.

[0223] 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.12 100a), vehicles ( Fig.12 100b-1 and 100b-2), XR devices ( Fig.12 100c), handheld device ( Fig.12 100d), household appliances ( Fig.12 100e), IoT devices ( Fig.12 100f), digital broadcasting terminal, holographic device, public safety device, MTC device, medical device, fintech device (or financial device), security device, climate / environmental device, AI server / device ( Fig.12 400), BS( Fig.12 200), network nodes, etc. The wireless device can be used in a mobile or fixed location according to the usage example / service.

[0224] exist Fig.14In 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. The various elements, components, units / parts and / or modules 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.

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

[0226] Reference Fig.15 , 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.14 Block 110 / 130 / 140.

[0227] 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 vehicle 100. The control unit 120 may include an electronic control unit (ECU). The drive unit 140a may enable the vehicle or autonomous 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 vehicle 100, and include a wired / wireless charging circuit, a battery, etc. The sensor unit 140c may obtain 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.

[0228] 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 based on information collected from the vehicle or autonomous driving vehicle using AI technology, etc., and provide the predicted traffic information data to the vehicle or autonomous driving vehicle.

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

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

[0231] Reference Fig.16 , 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, the UE starts the inactivity timer and remains awake. On the contrary, when the UE fails to detect any PDCCH during the PDCCH monitoring, 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.

[0232] Table 9 describes the DRX operation of the UE (in the RRC_CONNECTED state). Referring to Table 9, DRX configuration information is received through high-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 executing the above-described / proposed procedures and / or methods.

[0233] [Table 9]

[0234]

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

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

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

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

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

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

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

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

[0243] The above-mentioned embodiments correspond to the combination of elements and features of the present disclosure in a prescribed form. And, unless explicitly mentioned, each element or feature may be regarded as selective. Each element or feature may be implemented in a form that is not combined with other elements or features. In addition, the embodiments of the present disclosure can be implemented by partially combining elements and / or features together. The order of operations described for each embodiment of the present disclosure may be modified. Some configurations or features of an embodiment may be included in another embodiment, or may replace the corresponding configuration or features of another embodiment. And, it is clearly understood that the embodiment is configured by combining claims that do not have a clear reference relationship in the attached claims, or may be included as a new claim by modification after submitting the application.

[0244] Those skilled in the art will appreciate that the present disclosure may be implemented in other specific forms other than those described herein without departing from the spirit and essential characteristics of the present disclosure. Therefore, the above-described embodiments should be interpreted as being illustrative in all respects, rather than 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 scope of the appended claims are intended to be covered therein.

[0245] Industrial Applicability

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

Claims

1. A method for sending uplink control information (UCI) by a user equipment (UE) through a physical uplink shared channel (PUSCH) in a wireless communication system, the method comprising the following steps: Receive about multiple β offset β offset value information, the multiple β offset β offset The value includes i) a first β offset value for UCI multiplexing on PUSCHs of the same priority and ii) a second β offset value for UCI multiplexing on PUSCHs of different priorities; Receiving downlink control information DCI scheduling a first PUSCH; as well as transmitting the first PUSCH multiplexed with the first UCI including the first hybrid automatic repeat request-acknowledgement HARQ-ACK based on the multiple β offset values ​​and the β offset indicator included in the DCI, Wherein, based on (i) the ratio between the amount of resources of the first HARQ-ACK and the total amount of resources of the first UCI exceeds the α value, and (ii) the first UCI also includes a second HARQ-ACK having a lower priority than the first HARQ-ACK, uplink shared channel UL-SCH data is discarded from the first PUSCH transmission for multiplexing of the second HARQ-ACK having the lower priority.

2. The method according to claim 1, wherein: Based on the priority of the first HARQ-ACK, the UE selects the β offset value indicated by the β offset indicator included in the DCI among the first β offset values ​​or selects the β offset value indicated by the β offset indicator included in the DCI among the second β offset values.

3. The method according to claim 1, wherein: The N field states that can be indicated by the beta offset indicator included in the DCI are related to N beta offset set indexes, and The first β offset value includes a β offset value for each of the N field states, and the second β offset value includes a β offset value for each of the N field states.

4. The method according to claim 3, wherein: A specific field state among the N field states is indicated by the DCI.

5. The method according to claim 1, wherein: The beta offset indicator included in the DCI is two bits, and N field states are associated with a beta offset set index {00, 01, 10, 11}, and The first β offset value includes a β offset value for each of four β offset set indexes {00, 01, 10, 11}, and the second β offset value includes a β offset value for each of the four β offset set indexes {00, 01, 10, 11}.

6. The method according to claim 1, wherein: The second β offset value includes (i) a β offset value for a case where the priority of the first HARQ-ACK is higher than the priority of the first PUSCH and (ii) a β offset value for a case where the priority of the first HARQ-ACK is lower than the priority of the first PUSCH.

7. The method according to claim 6, wherein: Based on whether the priority of the first PUSCH is a first priority or a second priority higher than the first priority, the UE selects from the second β offset values ​​(i) the β offset value for the case where the priority of the first HARQ-ACK is higher than the priority of the first PUSCH or (ii) the β offset value for the case where the priority of the first HARQ-ACK is lower than the priority of the first PUSCH.

8. A processor-readable recording medium storing instructions for executing the method according to claim 1.

9. An apparatus for wireless communication, the apparatus comprising: a memory for recording instructions; as well as a processor that performs operations by executing the instructions, The operation of the processor includes: Receive about multiple β offset β offset value information, the multiple β offset β offset The value includes i) a first β offset value for uplink control information UCI multiplexing on a physical uplink shared channel PUSCH of the same priority and ii) a second β offset value for UCI multiplexing on a PUSCH of different priorities; receiving downlink control information DCI scheduling a first PUSCH; and transmitting the first PUSCH multiplexed with the first UCI including the first hybrid automatic repeat request-acknowledgement HARQ-ACK based on the multiple β offset values ​​and the β offset indicator included in the DCI, Wherein, based on (i) the ratio between the amount of resources of the first HARQ-ACK and the total amount of resources of the first UCI exceeds the α value, and (ii) the first UCI also includes a second HARQ-ACK having a lower priority than the first HARQ-ACK, uplink shared channel UL-SCH data is discarded from the first PUSCH transmission for multiplexing of the second HARQ-ACK having the lower priority.

10. The device according to claim 9, further comprising: Transceiver, The device is a user equipment UE.

11. A method for receiving uplink control information UCI by a base station BS through a physical uplink shared channel PUSCH in a wireless communication system, the method comprising the following steps: Sending information about multiple β offsets β to a user equipment UE offset value information, the multiple β offset β offset The value includes i) a first β offset value for UCI multiplexing on PUSCHs of the same priority and ii) a second β offset value for UCI multiplexing on PUSCHs of different priorities; Sending downlink control information DCI for scheduling a first PUSCH to the UE; as well as receiving the first PUSCH multiplexed with the first UCI including the first hybrid automatic repeat request-acknowledgement HARQ-ACK based on the multiple beta offset values ​​and the beta offset indicator included in the DCI, Wherein, based on (i) the ratio between the amount of resources of the first HARQ-ACK and the total amount of resources of the first UCI exceeds the α value, and (ii) the first UCI also includes a second HARQ-ACK having a lower priority than the first HARQ-ACK, uplink shared channel UL-SCH data is discarded from the first PUSCH transmission for multiplexing of the second HARQ-ACK having the lower priority.

12. A base station BS for wireless communication, the BS comprising: Transceiver; as well as The processor is configured to send information about a plurality of β offsets β to a user equipment UE by controlling the transceiver offset value information, the multiple β offset β offset The method comprises: determining a first β offset value including i) a first β offset value for multiplexing uplink control information (UCI) on a physical uplink shared channel (PUSCH) of the same priority and ii) a second β offset value for multiplexing UCI on a PUSCH of different priorities, sending downlink control information (DCI) for scheduling a first PUSCH to the UE, and receiving the first PUSCH multiplexed with a first UCI including a first hybrid automatic repeat request-acknowledgement (HARQ-ACK) based on the multiple β offset values ​​and the β offset indicator included in the DCI, Wherein, based on (i) the ratio between the amount of resources of the first HARQ-ACK and the total amount of resources of the first UCI exceeds the α value, and (ii) the first UCI also includes a second HARQ-ACK having a lower priority than the first HARQ-ACK, uplink shared channel UL-SCH data is discarded from the first PUSCH transmission for multiplexing of the second HARQ-ACK having the lower priority.