CN118020363A - Method and apparatus for transmitting and receiving signal in wireless communication system - Google Patents
Method and apparatus for transmitting and receiving signal in wireless communication system Download PDFInfo
- Publication number
- CN118020363A CN118020363A CN202280065308.7A CN202280065308A CN118020363A CN 118020363 A CN118020363 A CN 118020363A CN 202280065308 A CN202280065308 A CN 202280065308A CN 118020363 A CN118020363 A CN 118020363A
- Authority
- CN
- China
- Prior art keywords
- pucch
- pusch
- band
- cell
- puschs
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims description 119
- 238000004891 communication Methods 0.000 title claims description 81
- 230000005540 biological transmission Effects 0.000 claims abstract description 167
- 230000015654 memory Effects 0.000 claims description 37
- 230000002776 aggregation Effects 0.000 claims description 7
- 238000004220 aggregation Methods 0.000 claims description 7
- 239000010410 layer Substances 0.000 description 22
- 238000012545 processing Methods 0.000 description 22
- 230000011664 signaling Effects 0.000 description 17
- 230000006870 function Effects 0.000 description 15
- 238000012544 monitoring process Methods 0.000 description 15
- 230000008569 process Effects 0.000 description 15
- 230000004044 response Effects 0.000 description 14
- 230000008054 signal transmission Effects 0.000 description 12
- 238000005516 engineering process Methods 0.000 description 11
- 238000010586 diagram Methods 0.000 description 8
- 238000013473 artificial intelligence Methods 0.000 description 5
- 230000001960 triggered effect Effects 0.000 description 5
- 238000013507 mapping Methods 0.000 description 4
- 238000013468 resource allocation Methods 0.000 description 4
- 101100243399 Caenorhabditis elegans pept-2 gene Proteins 0.000 description 3
- 238000001228 spectrum Methods 0.000 description 3
- 101150071746 Pbsn gene Proteins 0.000 description 2
- 230000003190 augmentative effect Effects 0.000 description 2
- 125000004122 cyclic group Chemical group 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- GVVPGTZRZFNKDS-JXMROGBWSA-N geranyl diphosphate Chemical compound CC(C)=CCC\C(C)=C\CO[P@](O)(=O)OP(O)(O)=O GVVPGTZRZFNKDS-JXMROGBWSA-N 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000005259 measurement Methods 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 102100022734 Acyl carrier protein, mitochondrial Human genes 0.000 description 1
- CIWBSHSKHKDKBQ-JLAZNSOCSA-N Ascorbic acid Chemical compound OC[C@H](O)[C@H]1OC(=O)C(O)=C1O CIWBSHSKHKDKBQ-JLAZNSOCSA-N 0.000 description 1
- 101100189913 Caenorhabditis elegans pept-1 gene Proteins 0.000 description 1
- 101000678845 Homo sapiens Acyl carrier protein, mitochondrial Proteins 0.000 description 1
- 230000004913 activation Effects 0.000 description 1
- 230000003044 adaptive effect Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 239000000969 carrier Substances 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 239000000446 fuel Substances 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 238000005286 illumination Methods 0.000 description 1
- 239000002346 layers by function Substances 0.000 description 1
- 239000011159 matrix material Substances 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000010363 phase shift Effects 0.000 description 1
- 238000012913 prioritisation Methods 0.000 description 1
- 239000004984 smart glass Substances 0.000 description 1
- 235000019527 sweetened beverage Nutrition 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
- 238000005406 washing Methods 0.000 description 1
Abstract
A UE according to an embodiment of the present disclosure may receive parameters enabling simultaneous transmission of overlapping PUCCH-PUSCHs having different priorities in the same PUCCH cell group and may perform Uplink (UL) transmission related to PUCCH and one or at least two PUSCHs overlapping PUCCH. The one or at least two PUSCHs may include at least one of a first PUSCH on a first band to which a cell of the PUCCH belongs and a second PUSCH on a second band. Based on the first and second bands being different from each other, the UE may perform UL transmission without multiplexing UCI of the PUCCH onto the second PUSCH.
Description
Technical Field
The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for transmitting or receiving downlink/uplink radio signals in a wireless communication system.
Background
In general, wireless communication systems are evolving to cover a wide range differently to provide communication services such as audio communication services, data communication services, and the like. Wireless communication is a multiple-access system capable of supporting communication with multiple users by sharing the available system resources (e.g., bandwidth, transmit power, etc.). For example, the multiple access system may be any one 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.
Disclosure of Invention
Technical problem
An object of the present disclosure is to provide a method of efficiently performing a wireless signal transmission/reception process and an apparatus thereof.
It will be appreciated by those skilled in the art that the objects achievable with the present disclosure are not limited to those specifically described above, and that the above and other objects achievable with the present disclosure will be more clearly understood from the following detailed description.
Technical proposal
In one aspect of the present disclosure, a method of transmitting a signal by a User Equipment (UE) in a wireless communication system is provided herein. The method may include: receiving parameters related to Physical Uplink Control Channel (PUCCH) -Physical Uplink Shared Channel (PUSCH) simultaneous transmissions; and performing Uplink (UL) transmission related to at least one of a PUCCH and one or more PUSCHs overlapping the PUCCH. The parameter related to the PUCCH-PUSCH simultaneous transmission may be a parameter for enabling simultaneous transmission of overlapping PUCCH-PUSCHs having different priorities within the same PUCCH cell group. The one or more PUSCHs overlapping the PUCCH may include at least one of a first PUSCH on a first band to which a cell of the PUCCH belongs and a second PUSCH on a second band having at least one cell. In a state in which the simultaneous transmission of the overlapping PUCCH-PUSCHs has been enabled, the UE performs the UL transmission based on the first band to which the cell of the PUCCH belongs being different from the second band to which the cell of the second PUSCH belongs without multiplexing Uplink Control Information (UCI) of the PUCCH into the second PUSCH.
The priority of the PUCCH may be different from the priority of the second PUSCH. The cells of the PUCCH and the cells of the second PUSCH may belong to the same PUCCH cell group. The PUCCH and the second PUSCH may be transmitted simultaneously. The simultaneous transmission of the PUCCH and the second PUSCH may be based on inter-band carrier aggregation.
When the UCI in the PUCCH is multiplexed to PUSCH, the PUSCH may be determined as one of PUSCHs on the first band.
Based on the parameters, simultaneous transmission of the PUCCH on the first band and the second PUSCH on the second band may be allowed, but multiplexing of the PUCCH on the first band and the second PUSCH on the second band may not be allowed.
The UCI in the PUCCH may be transmitted through the first PUSCH other than the second PUSCH based on the UE being configured with multiplexing between channels of different priorities and the priority of the PUCCH being different from the priority of the first PUSCH.
The UE may receive at least one of DCI scheduling the first PUSCH and DCI scheduling the second PUSCH through a Physical Downlink Control Channel (PDCCH). The DCI may trigger an aperiodic Channel State Information (CSI) report and include a priority index of the PUSCH.
The UE may first solve the overlap between the PUCCH and the PUSCH having the same priority, solve the overlap between the PUCCH having different priorities, and then solve the overlap between the PUCCH and the PUSCH having different priorities.
In another aspect of the present disclosure, provided herein is a computer-readable recording medium having recorded thereon a program for executing the signal transmission method described above.
In another aspect of the present disclosure, provided herein is a UE configured to perform the signal transmission method described above.
In another aspect of the present disclosure, provided herein is an apparatus for controlling a UE to perform the signal transmission method described above.
In another aspect of the present disclosure, a method of receiving a signal by a Base Station (BS) in a wireless communication system is provided herein. The method may include: transmitting parameters related to PUCCH-PUSCH simultaneous transmission to the UE; and receiving, from the UE, an UL signal related to at least one of a PUCCH and one or more PUSCHs overlapping the PUCCH. The one or more PUSCHs overlapping the PUCCH may include at least one of a first PUSCH on a first band to which a cell of the PUCCH belongs and a second PUSCH on a second band having at least one cell. In a state in which the UE is enabled to perform the simultaneous transmission of the overlapping PUCCH-PUSCHs, the BS receives the UL signal without demultiplexing UCI in the PUCCH from the second PUSCH based on the first band to which the cell of the PUCCH belongs being different from the second band to which the cell of the second PUSCH belongs.
In another aspect of the present disclosure, provided herein is a BS configured to perform the above-described signal reception method.
Advantageous effects
According to the present disclosure, wireless signal transmission and reception can be efficiently performed in a wireless communication system.
Those skilled in the art will appreciate that the effects that can be achieved with the present disclosure are not limited to what has been particularly described hereinabove, and other advantages of the present disclosure will be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings.
Drawings
Fig. 1 illustrates physical channels used in a third generation partnership project (3 GPP) system as an exemplary wireless communication system and a general signal transmission method using the same;
fig. 2 illustrates a radio frame structure;
fig. 3 illustrates a resource grid of time slots;
Fig. 4 illustrates an exemplary mapping of physical channels in a slot;
Fig. 5 illustrates an exemplary acknowledgement/negative acknowledgement (ACK/NACK) transmission procedure;
fig. 6 illustrates an exemplary Physical Uplink Shared Channel (PUSCH) transmission procedure;
Fig. 7 illustrates an example of multiplexing control information in PUSCH;
fig. 8 illustrates an Uplink (UL) signal transmission method according to an embodiment of the present disclosure.
Fig. 9 illustrates various examples of overlapping physical uplink control channels/physical uplink shared channels (PUCCH/PUSCH).
Fig. 10 is a diagram for explaining an operation of solving overlap between PUCCH/PUSCH according to an embodiment of the present disclosure.
Fig. 11 illustrates an implementation example of a method of a User Equipment (UE) transmitting a signal in a wireless communication system according to an embodiment of the present disclosure.
Fig. 12 illustrates an implementation example of a method of a Base Station (BS) receiving a signal in a wireless communication system according to an embodiment of the present disclosure.
Fig. 13 to 16 are diagrams illustrating examples of a wireless device and a communication system 1 suitable for the present disclosure.
Fig. 17 is a diagram illustrating an example of Discontinuous Reception (DRX) operation suitable for use in the present disclosure.
Detailed Description
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 may be implemented as a radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA 2000. TDMA may 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 may 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). The 3 rd generation partnership project (3 GPP) Long Term Evolution (LTE) is part of evolved UMTS (E-UMTS) using E-UTRA, and LTE-Advanced (A) is an evolved version of 3GPP LTE. The 3GPP NR (New radio or New radio Access technology) is an evolved version of 3GPP LTE/LTE-A.
As more and more communication devices require greater communication capacity, enhanced mobile broadband communication relative to conventional Radio Access Technologies (RATs) is required. In addition, large-scale Machine Type Communication (MTC) capable of providing various services by connecting a plurality of devices and objects whenever and wherever is another important issue to be considered for next-generation communication. Communication system designs that consider reliability and delay sensitive services/UEs are also being discussed. Accordingly, the introduction of new radio access technologies that consider enhanced mobile broadband communications (eMBB), large-scale MTC, and ultra-reliable low-delay communications (URLLC) is under discussion. In this disclosure, this technique will be referred to as NR (new radio or new RAT) for simplicity.
For simplicity, the 3GPP NR is mainly described, but the technical concept of the present disclosure is not limited thereto.
In the present disclosure, the term "set)/setting" may be replaced with "configuration/configuration", and both may be used interchangeably. Further, conditional expressions (e.g., "if", "in this case", or "when …") may be replaced with "based on" or "in … cases/states. Furthermore, the operation of the User Equipment (UE)/Base Station (BS) or the software/hardware (SW/HW) configuration may be derived/understood based on the satisfaction of the corresponding conditions. When a procedure on the receiving (or transmitting) side can be derived/understood from a procedure on the transmitting (or receiving) side in signal transmission/reception between wireless communication devices (e.g., BS and UE), description thereof may be omitted. For example, signal determination/generation/encoding/transmission on the transmitting side can be understood as signal monitoring reception/decoding/determination on the receiving side. Further, when it is said that the UE performs (or does not perform) a specific operation, this may also be interpreted as that the BS expects/presumes (or does not expect/presume) the UE to perform the specific operation. When it is said that the BS performs (or does not perform) a specific operation, this may also be interpreted as that the UE expects/presumes (or does not expect/presume) the BS to perform the specific operation. In the following description, for convenience of description, chapters, embodiments, examples, options, methods, schemes, and the like are distinguished from each other and are indexed, which does not mean that each of them necessarily constitutes a separate invention or that each of them can only be implemented separately. Unless clearly contradicted by context, it is to be appreciated/understood that at least some of the chapters, embodiments, examples, options, methods, schemes, etc. may be implemented in combination or may be omitted.
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.
Fig. 1 illustrates a physical channel used in a 3GPP NR system and a general signal transmission method using the same.
When the UE is powered on again from the power-off state or enters a new cell, the UE performs an initial cell search procedure (e.g., establishes synchronization with the BS) in step S101. To this end, the UE receives a Synchronization Signal Block (SSB) from the BS. SSBs include 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 acquires information such as cell Identification (ID). The UE may acquire broadcast information in the cell based on the PBCH. The UE may receive a DL Reference Signal (RS) in an initial cell search procedure to monitor a DL channel state.
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.
The UE may perform a random access procedure to access the BS in steps S103 to S106. For random access, the UE may transmit a preamble to the BS on a Physical Random Access Channel (PRACH) (S103) and receive a response message to the preamble on the PDCCH and the PDSCH corresponding to the PDCCH (S104). In case of contention-based random access, the UE may perform a contention resolution procedure by further transmitting PRACH (S105) and receiving PDCCH and PDSCH corresponding to the PDCCH (S106).
After the foregoing procedure, the UE may receive the PDCCH/PDSCH (S107) and transmit a Physical Uplink Shared Channel (PUSCH)/Physical Uplink Control Channel (PUCCH) (S108) as a general downlink/uplink signal transmission procedure. The control information transmitted from the UE to the BS is referred to as Uplink Control Information (UCI). UCI includes hybrid automatic repeat and request acknowledgement/negative acknowledgement (HARQ-ACK/NACK), scheduling Request (SR), channel State Information (CSI), and the like. CSI includes Channel Quality Indicators (CQIs), precoding Matrix Indicators (PMIs), rank Indicators (RIs), and the like. Although UCI is generally transmitted on the PUCCH, UCI may be transmitted on PUSCH when control information and traffic data need to be transmitted simultaneously. In addition, UCI may be aperiodically transmitted through PUSCH according to a request/command of the network.
Fig. 2 illustrates a radio frame structure. In NR, uplink and downlink transmissions are configured in frames. Each radio frame has a length of 10ms and is divided into two 5ms Half Frames (HF). Each field is divided into five 1ms Subframes (SFs). The subframe is divided into one or more slots, and the number of slots in the subframe depends on a subcarrier spacing (SCS). Each slot includes 12 or 14 Orthogonal Frequency Division Multiplexing (OFDM) symbols according to a Cyclic Prefix (CP). When normal CP is used, each slot includes 14 OFDM symbols. When the extended CP is used, each slot includes 12 OFDM symbols.
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 SCS when using the normal CP.
TABLE 1
| SCS(15*2u) | Nslot symb | Nframe,u slot | Nsubframe,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 |
* N slot symb: number of symbols in a slot
* N frame,u slot: number of slots in a frame
* N subframe,u slot: number of slots in a subframe
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 SCS when the extended CP is used.
TABLE 2
| SCS(15*2u) | Nslot symb | Nframe,u slot | Nsubframe,u slot |
| 60KHz(u＝2) | 12 | 40 | 4 |
The structure of the frame is only an example. The number of subframes, the number of slots, and the number of symbols in a frame may vary.
In an NR system, OFDM parameter sets (e.g., SCS) may be configured differently for a plurality of cells aggregated for one UE. Thus, the (absolute time) duration of a time resource (e.g., SF, slot or TTI) consisting of the same number of symbols, referred to as a Time Unit (TU) for simplicity, may be configured differently among aggregated cells. Here, the symbols may include OFDM symbols (or CP-OFDM symbols) and SC-FDMA symbols (or discrete fourier transform-spread-OFDM (DFT-s-OFDM) symbols).
Fig. 3 shows a resource grid of time slots. A slot includes a plurality of symbols in the time domain. For example, when a normal CP is used, a slot includes 14 symbols. However, when the extended CP is used, the slot includes 12 symbols. The carrier comprises a plurality of subcarriers in the frequency domain. A Resource Block (RB) is defined to a plurality of contiguous subcarriers (e.g., 12 contiguous subcarriers) in the frequency domain. A bandwidth portion (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.). The carrier may include up to N (e.g., five) BWPs. Data communication may be performed through the enabled BWP, and only one BWP may be enabled for one UE. In the resource grid, each element is called a Resource Element (RE), and one complex symbol may be mapped to each RE.
Fig. 4 illustrates an exemplary mapping of physical channels in a slot. The PDCCH may be transmitted in a DL control region and the PDSCH may be transmitted in a DL data region. The PUCCH may be transmitted in the UL control region, and the PUSCH may be transmitted in the UL data region. The Guard Period (GP) provides a time gap for transmission mode to reception mode switching or reception mode to transmission mode switching at the BS and UE. Some symbols at DL-to-UL switching in a subframe may be configured as GP.
Each physical channel will be described in more detail below.
The PDCCH delivers DCI. For example, the PDCCH (i.e., DCI) may carry information on a transport format and resource allocation of a DL shared channel (DL-SCH), resource allocation information of an uplink shared channel (UL-SCH), paging information on a Paging Channel (PCH), system information on the DL-SCH, information on resource allocation of higher layer control messages such as RAR transmitted on the PDSCH, a transmission power control command, information on activation/release of configured scheduling, and the like. The DCI includes a Cyclic Redundancy Check (CRC). The CRC is masked with various Identifiers (IDs), such as a Radio Network Temporary Identifier (RNTI), according to the owner or use of the PDCCH. For example, if the PDCCH is for a specific UE, the CRC is masked by a UE ID (e.g., cell RNTI (C-RNTI)). If the PDCCH is used for a paging message, the CRC is masked by a paging RNTI (P-RNTI). If the PDCCH is used for system information (e.g., a System Information Block (SIB)), the CRC is masked by a system information RNTI (SI-RNTI). When the PDCCH is used for RAR, the CRC is masked by a random access RNTI (RA-RNTI).
The PDCCH includes 1, 2,4, 8 or 16 Control Channel Elements (CCEs) according to its Aggregation Level (AL). CCEs are logical allocation units for providing a specific code rate for PDCCHs according to a radio channel state. The CCE includes 6 Resource Element Groups (REGs), each defined by one OFDM symbol by one (P) RB. The PDCCH is transmitted in a control resource set (CORESET). CORESET is defined as a set of REGs with a given set of parameters (e.g., SCS, CP length, etc.). Multiple CORESET for one UE may overlap each other in the time/frequency domain. CORESET may be configured by system information (e.g., a Master Information Block (MIB)) or UE-specific higher layer signaling (e.g., radio Resource Control (RRC) signaling). Specifically, the number of RBs and the number of symbols (up to 3) in CORESET may be configured through higher layer signaling.
For PDCCH reception/detection, the UE monitors PDCCH candidates. The 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, depending on AL. The monitoring includes (blind) decoding PDCCH candidates. The set of PDCCH candidates decoded by the UE is defined as a PDCCH Search Space (SS). The SS may be a Common Search Space (CSS) or a UE-specific search space (USS). The UE may obtain DCI by monitoring PDCCH candidates in one or more SSs configured by MIB or higher layer signaling. Each CORESET is associated with one or more SSs, and each SS is associated with one CORESET. The SS may be defined based on the following parameters.
-ControlResourceSetId: CORESET associated with SS.
-MonitoringSlotPeriodicityAndOffset: PDCCH monitoring periodicity (in slot units) and PDCCH monitoring offset (in slot units).
-MonitoringSymbolsWithinSlot: the PDCCH in the slot monitors a symbol (e.g., the first symbol of CORESET).
-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).
* Where the UE defines the occasion (e.g., time/frequency resource) where the PDCCH candidate is to be monitored as the PDCCH (monitoring) occasion. One or more PDCCH (monitoring) occasions may be configured in a slot.
Table 3 shows the characteristics of each SS.
TABLE 3
Table 4 shows DCI formats transmitted on PDCCH.
TABLE 4
| DCI format | Usage method |
| 0_0 | Scheduling PUSCH in one cell |
| 0_1 | Scheduling PUSCH in one cell |
| 1_0 | Scheduling PDSCH in one cell |
| 1_1 | Scheduling PDSCH in one cell |
| 2_0 | Informing a group of UEs of a slot format |
| 2_1 | Informing a group of UEs of PRBs and OFDM symbols, wherein a UE may assume that no transmission is intended for the UE |
| 2_2 | Transmission of TPC commands for PUCCH and PUSCH |
| 2_3 | Transmission of a set of TPC commands for SRS transmission by one or more UEs |
DCI format 0_0 may be used to schedule a PUSCH based on a TB (or TB level), and DCI format 0_1 may be used to schedule a PUSCH based on a TB (or TB level) or a PUSCH based on a Code Block Group (CBG) (or CBG level). DCI format 1_0 may be used to schedule a TB (or TB level) -based PDSCH, and DCI format 1_1 may be used to schedule a TB (or TB level) -based PDSCH or a CBG (or CBG level) -based PDSCH (DL grant DCI). DCI format 0_0/0_1 may be referred to as UL grant DCI or UL scheduling information, and DCI format 1_0/1_1 may be referred to as DL grant DCI or DL scheduling information. DCI format 2_0 is used to deliver dynamic slot format information (e.g., dynamic Slot Format Indicator (SFI)) to a UE, and DCI format 2_1 is used to deliver DL preemption information to the UE. DCI format 2_0 and/or DCI format 2_1 may be delivered to a corresponding set of UEs on a set of common PDCCHs, which are PDCCHs for a set of UEs.
DCI format 0_0 and DCI format 1_0 may be referred to as a fallback DCI format, and DCI format 0_1 and DCI format 1_1 may be referred to as a non-fallback DCI format. In the fallback DCI format, the DCI size/field configuration remains the same regardless of the UE configuration. In contrast, the DCI size/field configuration varies in the non-fallback DCI format depending on the UE configuration.
PDSCH conveys DL data (e.g., DL shared channel transport block (DL-SCH TB)) and uses modulation schemes such as Quadrature Phase Shift Keying (QPSK), 16-ary quadrature amplitude modulation (16 QAM), 64QAM, or 256QAM. The TB is encoded into a codeword. PDSCH may deliver up to two codewords. Scrambling and modulation mapping may be performed on a codeword basis, and modulation symbols generated from each codeword may be mapped to one or more layers. Each layer is mapped to resources along with demodulation reference signals (DMRS), and OFDM symbol signals are generated from the mapped layer with the DMRS and transmitted through the corresponding antenna ports.
The PUCCH delivers Uplink Control Information (UCI). UCI includes the following information.
-SR (scheduling request): information for requesting UL-SCH resources.
HARQ (hybrid automatic repeat request) -ACK (acknowledgement): response to DL data packets (e.g., codewords) on PDSCH. The 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 transmitted. In response to the two codewords, a 2-bit HARQ-ACK may be transmitted. The HARQ-ACK response includes a positive ACK (abbreviated ACK), a Negative ACK (NACK), discontinuous Transmission (DTX), or NACK/DTX. The term HARQ-ACK is used interchangeably with HARQ ACK/NACK and ACK/NACK.
CSI (channel state information): feedback information for DL channels. Feedback information related to Multiple Input Multiple Output (MIMO) includes RI and PMI.
Table 5 illustrates an exemplary PUCCH format. Based on the PUCCH transmission duration, the PUCCH format may be divided into short PUCCHs (formats 0 and 2) and long PUCCHs (formats 1, 3, and 4).
TABLE 5
PUCCH format 0 conveys UCI of up to 2 bits and is mapped for transmission in a sequence-based manner. Specifically, the UE transmits a specific UCI to the BS by transmitting one of a plurality of sequences on PUCCH of PUCCH format 0. Only when the UE transmits an affirmative SR, the UE transmits PUCCH of PUCCH format 0 in PUCCH resources for the corresponding SR configuration.
PUCCH format 1 delivers UCI of up to 2 bits in the time domain and spreads modulation symbols of the UCI with an Orthogonal Cover Code (OCC) configured differently according to whether frequency hopping is performed in the time domain. The DMRS is transmitted with symbols that do not transmit modulation symbols (i.e., transmitted in Time Division Multiplexing (TDM)).
PUCCH format 2 conveys UCI of more than 2 bits, and modulation symbols of DCI are transmitted with DMRS in Frequency Division Multiplexing (FDM). DMRS are located in symbols #1, #4, #7, and #10 of a given RB with a density of 1/3. Pseudo Noise (PN) sequences are used for the DMRS sequences. For 2-symbol PUCCH format 2, frequency hopping may be activated.
PUCCH format 3 does not support UE multiplexing in the same PRBS and delivers UCI of more than 2 bits. In other words, PUCCH resources of PUCCH format 3 do not include OCC. The modulation symbols and DMRS are transmitted in TDM.
PUCCH format 4 supports multiplexing of up to 4 UEs in the same PRBS and delivers UCI of more than 2 bits. In other words, PUCCH resources of PUCCH format 3 include OCC. The modulation symbols and DMRS are transmitted in TDM.
At least one of the one or two or more cells configured to the UE may be configured for PUCCH transmission. At least one primary cell may be set as a cell for PUCCH transmission. The at least one PUCCH cell group may be configured to the UE based on the at least one cell configuring the PUCCH transmission, and each PUCCH cell group includes one or two or more cells. The PUCCH cell group may be simply referred to as a PUCCH group. PUCCH transmission may be configured not only in the primary cell but also in the secondary cell (Scell). The primary cell belongs to a primary PUCCH group and the PUCCH-SCell configuring PUCCH transmission belongs to a secondary PUCCH group. For cells belonging to the primary PUCCH group, PUCCH on the primary cell may be used. For cells belonging to the secondary PUCCH group, PUCCH on PUCCH-SCell may be used.
PUSCH delivers UL data (e.g., UL shared channel transport block (UL-SCH TB)) and/or UCI based on CP-OFDM waveform or DFT-s-OFDM waveform. When PUSCH is transmitted in DFT-s-OFDM waveform, UE transmits PUSCH by transform precoding. For example, when transform precoding is not possible (e.g., disabled), the UE can transmit PUSCH in a CP-OFDM waveform, and when transform precoding is possible (e.g., enabled), the UE can transmit PUSCH in a CP-OFDM waveform or DFT-s-OFDM waveform. PUSCH transmissions may be dynamically scheduled by UL grants in DCI, or semi-statically scheduled (configured scheduling or configured grants) by higher layer (e.g., RRC) signaling (and/or layer 1 (L1) signaling such as PDCCH). PUSCH transmission can be performed in a codebook-based or non-codebook-based manner.
Fig. 5 illustrates an exemplary ACK/NACK transmission procedure. Referring to fig. 5, the ue may detect a PDCCH in slot #n. The PDCCH includes DL scheduling information (e.g., DCI format 1_0 or DCI format 1_1). The PDCCH indicates that DL is assigned to a PDSCH offset (DL ASSIGNMENT-to-PDSCH offset) K0 and a PDSCH-to-HARQ-ACK report offset (PDSCH-to-HARQ-ACK reporting offset) K1. For example, DCI format 1_0 and DCI format 1_1 may include the following information.
-Frequency domain resource assignment: indicating RB set assigned to PDSCH
-Time domain resource assignment: indicating K0 and starting position (e.g., OFDM symbol index) and length (e.g., number of OFDM symbols) of PDSCH in a slot
PDSCH to harq_feedback timing indicator: indication K1
HARQ process number (4 bits): HARQ process ID (e.g., PDSCH or TB) indicating data
-PUCCH Resource Indicator (PRI): PUCCH resources to be used for UCI transmission among a plurality of PUCCH resources in the PUCCH resource set are indicated.
After receiving PDSCH in slot# (n+k0) according to scheduling information of slot #n, the UE may transmit UCI on PUCCH in slot# (n+k1). UCI may include a HARQ-ACK response to PDSCH. Fig. 5 is based on the assumption that the SCS of PDSCH is equal to that of PUCCH, and that slot #n1=slot# (n+k0), and should not be construed as limiting the present invention for convenience. When SCS is different, K1 may be indicated/interpreted based on SCS of PUCCH.
In case the PDSCH is configured to carry a maximum of 1 TB, the HARQ-ACK response may be configured in one bit. In the case where PDSCH is configured to carry up to two TBs, HARQ-ACK response may be configured in two bits if spatial bundling is not configured, and may be configured in one bit if spatial bundling is configured. When slot# (n+k1) is designated as the HARQ-ACK transmission timing for the plurality of PDSCH, UCI transmitted in slot# (n+k1) includes HARQ-ACK responses to the plurality of PDSCH.
Whether the UE should perform spatial bundling for the HARQ-ACK response may be configured (e.g., by RRC/higher layer signaling) for each cell group. For example, spatial bundling may be configured for each individual HARQ-ACK response transmitted on PUCCH and/or HARQ-ACK response transmitted on PUSCH.
Spatial bundling may be supported when up to two (or two or more) TBs (or codewords) may be received at a time in the respective serving cell (or schedulable by one DCI) (e.g., when higher layer parameters maxNrofCodeWordsScheduledByDCI indicate 2 TBs). More than four layers may be used for 2-TB transmission and up to four layers may be used for 1-TB transmission. As a result, when spatial bundling is configured for a corresponding cell group, spatial bundling can be performed for a serving cell that can be scheduled more than four layers among the serving cells of the cell group. A UE wanting to send a HARQ-ACK response by spatial bundling may generate the HARQ-ACK response by performing a (bit-wise) logical and operation (logical AND operation) on the a/N bits for the multiple TBs.
For example, assuming that the UE receives DCI scheduling two TBs and receives two TBs on PDSCH based on the DCI, the UE performing spatial bundling may generate a single a/N bit through a logical and operation between a first a/N bit for a first TB and a second a/N bit for a second TB. As a result, the UE reports an ACK bit value to the BS when both the first TB and the second TB are ACKs, and reports a NACK bit value to the BS when at least one of the TBs is a NACK.
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 bit for one TB and the bit value 1. As a result, the UE reports a/N bits for one TB to the BS.
There are multiple parallel DL HARQ processes at the BS/UE for DL transmission. Multiple parallel HARQ processes enable successive DL transmissions while the BS is waiting for HARQ feedback indicating successful or failed reception of the previous DL transmission. Each HARQ process is associated with a HARQ buffer in a 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 MAC PDUs in the buffer, and current redundancy version. Each HARQ process is identified by a HARQ process ID.
Fig. 6 illustrates an exemplary PUSCH transmission procedure. Referring to fig. 6, the ue may detect a PDCCH in slot #n. The PDCCH includes DL scheduling information (e.g., DCI format 1_0 or 1_1). DCI format 1_0 or 1_1 may include the following information.
-Frequency domain resource assignment: indicating the set of RBs assigned to PUSCH.
-Time domain resource assignment: the slot offset K2 and the duration (e.g., number of OFDM symbols) and starting position (e.g., OFDM symbol index) of the PUSCH in one slot are indicated. The start symbol and length of PUSCH may be indicated by the Start and Length Indicator Value (SLIV), or may be indicated separately.
According to the scheduling information in slot #n, the UE may transmit PUSCH in slot # (n+k2). The PUSCH includes the UL-SCH TB.
Fig. 7 illustrates exemplary UCI multiplexing in PUSCH. When multiple PUCCH resources overlap PUSCH resources in a slot and PUCCH-PUSCH simultaneous transmission is not configured in the slot, UCI (UCI piggybacked or PUSCH piggybacked) may be sent on PUSCH as shown. In the case illustrated in fig. 7, HARQ-ACK and CSI are carried in PUSCH resources.
NR operation band
The Frequency Range (FR) of Rel-16 NR is broadly classified as FR1 and FR2. Table 6 shows FR1 and FR2 defined in NR specification TS 38.104.
TABLE 6
| Frequency range assignment | Corresponding frequency range |
| FR1 | 410MHz–7125MHz |
| FR2 | 24250MHz–52600MHz |
In FR1 and FR2, a plurality of NR operation bands are defined. In Rel-17, it is being discussed to further expand the FR2 range by expanding the definition of Rel-16 FR2 (which ranges from 24250MHz to 52600 MHz) as FR2-1 and the definition of 52600MHz to 71000MHz as FR2-2.
Table 7 shows the bands belonging to Rel-16 FR1, and Table 8 shows the bands belonging to Rel-16 FR2.
TABLE 7
/>
TABLE 8
For NR wireless communication, the BS/UE needs to support one of the bands shown in Table 7/8. The actual operating band may vary depending on the specifications and implementation of the BS/UE. Additionally, depending on implementation, one or more carriers/cells may be configured in one band. For carrier aggregation, a UE may be configured with multiple cells. In this case, the plurality of cells configured to the UE may belong to the same band or different bands. For example, among a plurality of cells, a cell in a first cell group may belong to a first band, and a cell in a second cell group may belong to a second band. Carrier aggregation between cells belonging to different bands may be referred to as inter-band Carrier Aggregation (CA). Carrier aggregation between cells belonging to the same band may be referred to as intra-band CA. When multiple UL channels belong to different bands, the UL channels may be located in different cells. The placement of multiple UL channels on different cells may be inter-band CA or intra-band CA, depending on the situation.
NR shared spectrum/unlicensed band (NR-U) operation
A communication node (e.g., BS or UE) operating in the unlicensed band should determine whether other communication nodes are using the channel before transmitting signals.
Definition of terms related to NR-U operations:
-channel: a carrier or a portion of a carrier comprising consecutive RBs, wherein a Channel Access Procedure (CAP) is performed in a shared spectrum.
-Channel Access Procedure (CAP): a process of evaluating the availability of a channel based on sensing to determine whether the channel is used by other communication nodes prior to signal transmission. CAP may be referred to as Listen Before Talk (LBT).
-Channel occupancy: transmissions on channels from BS/UE after CAP.
Channel Occupation Time (COT): the total time the BS/UE and any BS/UE occupied by the shared channel perform a transmission on the channel after the BS/UE's corresponding CAP. In determining the COT, the gap duration may also be counted in the COT if the transmission gap is less than or equal to 25 us. The COT may be shared for transmission between the BS and the corresponding UE.
If a sub-band (SB) in which LBT is separately performed is defined as an LBT-SB, a plurality of LBT-SBs may be included in one broadband cell/BWP. The RB set forming the LBT-SB may be configured through higher layer signaling (e.g., RRC signaling). Accordingly, one cell/BWP may include one or more LBT-SB based on (i) BW of the cell/BWP and (ii) RB set allocation information. Multiple LBT-SBs may be included in a BWP of a cell (or carrier). The LBT-SB may have a band of, for example, 20 MHz. The LBT-SB may include a plurality of 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 LBT-SB. Thus, 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 lower frequency band to higher frequency band.
(1) Type 1 CAP method
The BS in the type 1DL CAP and the UE in the type 1UL CAP may detect whether the channel is idle during the sensing slot duration of the delay duration Td and perform transmission after the counter N is zero. The counter N is adjusted by sensing the channel for an additional sensing time slot duration according to the following procedure:
step 1) sets n=ninit, where Ninit is a random number uniformly distributed between 0 and CWp, and goes to step 4.
Step 2) if N >0 and BS selects the down counter, n=n-1 is set.
Step 3) sensing the channel for an additional sensing time slot duration and if the additional sensing time slot duration is idle, proceeding to step 4; otherwise, go to step 5.
Step 4) if n=0 (Y), stopping; otherwise, turning to step 2,
Step 5) senses the channel until a busy sensing time slot is detected within the additional delay duration Td or all sensing time slots within the additional delay duration Td are detected as idle.
Step 6) if the channel is sensed as idle during all sensing time slot durations of the additional delay duration Td, then go to step 4; otherwise, go to step 5.
The type 1UL CAP may be applied to the following transmission.
PUSCH/SRS transmission scheduled and/or configured by BS
PUCCH transmission scheduled and/or configured by BS
-Transmission related to Random Access Procedure (RAP)
Type 2 CAP is a CAP that is performed without random backoff. Types 2A, 2B, and 2C are defined for DL, and types 2A, 2B, and 2C are defined for UL. In the type 2A UL CAP, the UE may transmit a signal immediately after the channel is sensed as idle during at least the sensing duration tshort_dl (=25 μs). Tshort_dl includes a sensing time duration followed by a duration Tf (=16 μs). In a type 2A UL CAP, tf includes a sensing time slot at the beginning of the duration. In the type 2B UL CAP, the UE may transmit a signal immediately after the channel is sensed as idle for the sensing duration Tf (=16 μs). In a type 2B UL CAP, tf includes the sensing time slot within the last 9us of duration. In type 2C UL CAP, the UE does not sense the channel before performing the transmission.
License for Configuration (CG)
Semi-static Configuration Grants (CG) may be configured for UEs through RRC signaling. Up to 12 active CGs may be configured for the UE in the corresponding BWP of the serving cell.
Each CG may be type 1 or type 2. Type 1 CG may be activated/deactivated independently between serving cells. When multiple types 2 CG are configured, each type 2 CG may be activated by DCI individually. One DCI may deactivate one type 2 CG or multiple types 2 CG.
For CG-based transmissions in NR-us (i.e., shared spectrum channel access), configuration grant uplink control information (CG-UCI) is transmitted on the corresponding CG PUSCH (i.e., PUSCH scheduled by the CG). Multiplexing between the PUCCH carrying CG-UCI and the 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 PUCCH carrying HARQ-ACK overlaps CG PUSCH within a PUCCH group, CG PUSCH transmission is dropped.
UL channels with different priorities
To support data transmission/services such as URLLC where reliability/delay performance is important, service/protection priorities (e.g., low Priority (LP) or High Priority (HP)) may be configured semi-statically (through RRC signaling) or dynamically (through DCI/MAC signaling) for the UE for each physical channel/signal (transmission resource) and control information (e.g., UCI).
Specifically, priority indicators have been introduced in NR rel.16 to some DCI formats (e.g., DCI format 1_1/1_2 for DL and DCI format 0_1/0_2 for UL). When configuring the priority indicator for the corresponding DCI format through higher layer signaling, the UE blindly decodes the DCI format assuming that the priority indicator exists. In case there is no explicit signaling indicating that the priority indicator is to be used for the DCI format, it is assumed that the priority indicator is not included in the DCI format, and the UE blindly decodes 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 DCI is one of various means for indicating/configuring priority, and not the only method.
In the prioritized example described above, lower priority indexes may be configured/indicated for LP and higher priority indexes 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.
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 related UCI transmission. For example, the LP/HP of HARQ-ACK for PDSCH may be indicated by DL grant DCI of the scheduled PDSCH. For example, in the case of (aperiodic) CSI, LP/HP may be indicated by DCI (e.g., UL grant DCI scheduling PUSCH).
In another example, (i) the PUCCH resource set may be configured independently for each priority, and/or (ii) the maximum UCI coding rate for PUCCH transmission may be configured independently for each priority. In another example, (iii) beta offset for encoding UCI on PUSCH may be configured independently for each priority, and/or (iv) HARQ-ACK codebook type may be configured independently for each priority. (i) At least one of (iv) or any combination thereof may be used.
In conventional Rel-16 NR, i) check whether the UE processing timeline associated with PUCCH/PUSCH transmission is met for each priority (e.g., minimum processing time N1 between the reception time of PDSCH (e.g., PDSCH end symbol) and the transmission time of its HARQ-ACK (e.g., HARQ-ACK start symbol), and/or minimum processing time N2 between the reception time of PDCCH (e.g., PDCCH end symbol) and the transmission time of PUSCH/PUCCH associated therewith (e.g., PUSCH/PUCCH start symbol); and ii) UCI/UL multiplexing procedure (where multiple PUCCHs/PUSCHs overlapping in time are combined (multiplexed) into one UL channel) is performed (i.e., UE processing timeline checking and UCI/UL multiplexing procedure are performed for the same priority). If the results for LP and HP PUCCH/PUSCH are multiplexed results, overlapping in time, the transmission of LP PUCCH/PUSCH is discarded and only the transmission of HP PUCCH/PUSCH is performed (see section 9.2.5 of 3GPP TS 38.213V16.2.0).
In Rel-17 NR, UE processing timeline checking and UCI/UL multiplexing procedures may be performed between DL channels (e.g., PDSCH/PDCCH) and UL channels (e.g., PUCCH/PUSCH) with different priorities and the same priority (i.e., for channels between priorities) when multiplexing between LP and HP UL channels for transmission is enabled (e.g., when UCI is multiplexed in PUCCHs with different priorities on a single PUCCH, and/or UCI is multiplexed in PUSCH (or in PUCCH) with different priorities on a PUSCH). Then, the results for LP and HP PUCCH/PUSCH, which are multiplexing results, may be transmitted.
In the conventional Rel-10 LTE-a, an operation in which the UE simultaneously transmits PUCCH and PUSCH at the same time point (e.g., subframe) is introduced. In addition, whether simultaneous pucch+pusch transmission is allowed is defined as the capability of the UE. Thus, the eNB may enable or disable simultaneous pucch+pusch transmission for UEs with corresponding capabilities (if the UE reports the capabilities to the eNB). The UE may be configured to perform UL transmissions according to the corresponding configuration (e.g., if the configuration is "ON", the UE may perform simultaneous pucch+pusch transmissions, whereas if the configuration is "OFF", the UE may perform legacy PUCCH-only or PUSCH-only operations (defined in Rel-8 LTE or Rel-15 NR). Based ON the ON/OFF configuration of simultaneous pucch+pusch transmission defined in Rel-10 LTE-a, table 9 below shows UCI and UL channel transmission operations performed by the UE.
TABLE 9
In Rel-17 NR, when simultaneous pucch+pusch transmissions are enabled, UL multiplexed transmissions between LP and HP channels may also be enabled simultaneously (e.g., between PUCCH and PUSCH on different frequency bands (or different serving cells) with different priorities). In this case, it may be necessary to define UE operations to be performed/applied according to a combination of UL channels (e.g., PUCCH and/or PUSCH) overlapping in time (between different priorities).
In the URLLC scenario, different priorities (e.g., LP and HP) may be configured/indicated for transmission of each UCI type (e.g., HARQ-ACK (a/N), SR, CSI, etc.) and/or each UL channel (e.g., PUCCH, PUSCH, etc.). In these cases, it may be necessary to define specific UE/BS operations (e.g., which type of UCI and/or which UCI priority is to be transmitted on which UL channel) for simultaneous pucch+pusch transmissions.
Accordingly, the present disclosure proposes a method of simultaneously transmitting PUCCH and PUSCH (e.g., PUCCH and PUSCH for configuration/indication at the same time (e.g., in the same slot, the same sub-slot, or the same symbol) in a scenario where different priorities are configured/indicated for UCI types and/or UL channels. When the same priority is configured/indicated for each UCI type and/or UL channel (or there is no separate priority configuration/indication), the proposal described later may be equally applied.
For convenience of description, a specific priority is defined as XP, and a priority different from XP is defined as YP. For example, if xp=lp, yp=hp may be meant. As another example, if xp=hp, then yp=lp may be meant. When two or more priorities are configured/defined, if xp=first priority, it may mean yp=all or part of the remaining priorities other than the first priority, and vice versa.
Hereinafter, when the first signal and the second signal are simultaneously configured/indicated, it may mean that resources for the first signal and resources for the second signal are completely overlapped in the time domain. However, the present disclosure is not limited thereto. For example, when the resources for the first signal and the resources for the second signal at least partially overlap in the time domain, it can be understood that the first signal and the second signal are simultaneously configured/indicated/scheduled. Additionally, the transmission of a specific channel/signal by the UE may be interpreted as the reception of a specific channel/signal by the BS.
In the present disclosure, when a plurality of UL channels overlap in time, it may mean that resources of the UL channels overlap in the same OFDM symbol or that resources of the UL channels are included in the same slot (or sub-slot) duration. In the present disclosure, multiplexing between two UL channels may mean not only an operation of multiplexing and transmitting control information/data carried on the two UL channels on a single UL channel, but also a prioritization operation of discarding transmission of a specific UL channel among the two UL channels and transmitting only the remaining UL channels.
Proposal 1
First, when a plurality of PUCCHs/PUSCHs having the same/different priorities overlap in time, a method of performing UCI/UL (channel) multiplexing according to the following procedure/step may be considered.
1)Alt 1
-Step 1: the UE may perform multiplexing on all PUCCHs having the same or different priorities and overlapping in time.
-Step 2: based on the multiplexing result of step 1, the UE may perform multiplexing on all PUCCHs and PUSCHs having the same or different priorities and overlapping in time.
2)Alt 2
-Step 1: in step 1, the UE may solve the overlap between PUCCHs/PUSCHs having the same priority (e.g., B05 in fig. 10). For example, the UE may first perform multiplexing on PUCCHs having the same priority for each priority and overlapping in time (sub-step 1-1). Based on the multiplexing result in sub-step 1-1, the UE may perform multiplexing again on PUCCH and PUSCH having the same priority for each priority and overlapping in time (sub-step 1-2).
-Step 2: based on the multiplexing result in step 1, the UE may first perform multiplexing on PUCCHs having different priorities and overlapping in time (sub-step 2-1) (B10 in fig. 10). Based on the multiplexing result in sub-step 2-1, the UE can perform multiplexing again on PUCCH and PUSCH having different priorities and overlapping in time (sub-step 2-2) (B15 in fig. 10).
Based on the above explanation, (at least one of) the following three operating parameters may be (individually) set to be enabled or disabled (e.g., at least one configured by higher layer signaling).
1) Inter-p_pucch_mux: for PUCCHs with different priorities, inter-p_pucch_mux is a parameter configuring whether UCI in the PUCCH can be multiplexed on a single PUCCH.
2) Inter-p_pusch_mux: for PUCCHs and PUSCHs having different priorities, inter-p_pusch_mux is a parameter configuring whether UCI in the corresponding PUCCH can be multiplexed on the corresponding PUSCH.
3) Pucch+pusch_tx: for PUCCH and PUSCH on different bands (or cells) with different priorities, pucch+pusch_tx is a parameter configuring whether simultaneous transmission of the corresponding PUCCH and PUSCH is possible. For example, when the UE receives the parameters pucch+pusch_tx configured as follows: pucch+pusch_tx=enabled, based on the first and second cells (belonging to the same PUCCH group) being located in different bands and the PUCCH on the first cell and the PUSCH on the second cell having different priority indexes, the UE may transmit the PUCCH on the first cell and the PUSCH on the second cell simultaneously. The parameters pucch+pusch_tx are used for simultaneous transmission of PUCCH and PUSCH having different priorities, and pucch+pusch_tx=enable may not allow simultaneous transmission of PUCCH and PUSCH having the same priority.
Depending on the multiplexing result (outcome (outcome)) in step 1 and the enable/disable configuration for the above three parameters, the following operations may be considered based on the Alt 2-based application
1) Case 1
A. Achievements of step1 for LP
I. After one or more LP PUCCHs overlapping in time are multiplexed on a specific LP PUCCH (e.g., LP-mux PUCCH) through sub-step 1-1, the LP-mux PUCCH may then overlap in time with the specific LP PUSCH. As a result, the final LP result of step 1 may be an LP PUSCH multiplexed with the LP UCI (e.g., LP UCI-PUSCH).
B. achievements for HP step 1
I. After one or more HP PUCCHs overlapping in time are multiplexed on a specific HP PUCCH (e.g., HP-mux PUCCH) through sub-step 1-1, the HP-mux PUCCH may then overlap in time with the specific HP PUSCH. As a result, the final HP outcome of step 1 may be HP PUSCH multiplexed with HP UCI (e.g., HP UCI-PUSCH).
C. In this case, if the LP effort overlaps in time with the HP effort (on the same cell) or another HP PUSCH (not multiplexed with UCI) (e.g., HP pure PUSCH), the following operations may be considered.
I. When Inter-p_pusch_mux is set to active
Opt 1: the transmission of the entire LP UCI-PUSCH, which is the LP effort, may be discarded.
Opt 2: the LP UCI included in the LP effort may be multiplexed on the HP effort (overlapping in time) or HP pure PUSCH, and the transmission of the LP PUSCH may be dropped.
Ii. when Inter-P_PUSCH_mux is set to disabled
Opt 1: the transmission of the entire LP UCI-PUSCH, which is the LP effort, may be discarded.
D. if the HP effort overlaps (on the same cell) with the LP-pure PUSCH, the transmission of the corresponding LP-pure PUSCH can be discarded.
E. In case 1, the operation may not vary depending on the enable/disable configuration for Inter-p_pucch_mux and pucch+pusch_tx.
2) Case 2
A. Achievements of step1 for LP
As in case 1 above, the LP UCI-PUSCH may be the final LP result of step 1.
B. achievements of step1 for HP
I. After one or more HP PUCCHs overlapping in time are multiplexed on a specific HP PUCCH (e.g., HP-mux PUCCH) through sub-step 1-1, the HP-mux PUCCH may not overlap in time with the HP PUSCH. As a result, the corresponding HP-mux PUCCH may be the final HP result of step 1.
C. in this case, if the HP effort overlaps in time with the LP effort or another LP pure PUSCH (on any cell), the following operations may be considered.
I. When Inter-p_pusch_mux and pucch+pusch_tx are configured as follows: inter-p_pusch_mux=enabled and pucch+pusch_tx=disabled, then the HP UCI included in the HP-mux PUCCH may be multiplexed on the LP effort (overlapping in time) or LP pure PUSCH and then transmitted.
Ii. when Inter-p_pusch_mux and pucch+pusch_tx are configured as follows: inter-p_pusch_mux=disabled and pucch+pusch_tx=disabled:
Opt a: only HP-mux PUCCH may be transmitted and the entire LP effort or transmission of LP pure PUSCH overlapping in time with HP-mux PUCCH may be dropped (this operation may apply when Inter-p_pucch_mux is set to enable or disable both).
Opt B: when LP pure PUSCHs overlap in time, the transmission of the corresponding LP pure PUSCH may be dropped. When the LP achievements overlap in time, the LP UCI and HP-mux PUCCH included in the LP achievements may be multiplexed on a single PUCCH, and the LP PUSCH transmission may be dropped (this operation only applies when Inter-p_pucch_mux is set to enabled).
When Inter-p_pusch_mux and pucch+pusch_tx are configured as follows: with Inter-p_pusch_mux=disabled and pucch+pusch_tx=enabled, the operations in Opt a/B may be applied if the LP PUSCHs overlapping in time are on the same band (or cell) as the HP-mux PUCCH. If the LP PUSCH is on a different band (or cell), simultaneous transmission of the HP-mux PUCCH and the LP PUSCH may be performed.
When Inter-p_pusch_mux and pucch+pusch_tx are configured as follows: inter-p_pusch_mux=enabled and pucch+pusch_tx=enabled, if the LP PUSCHs overlapping in time are on the same band (or cell) as the HP-mux PUCCH, the HP UCI included in the HP-mux PUCCH may be multiplexed on the corresponding LP PUSCH. If the LP PUSCH is on a different band (or cell), simultaneous transmission of the HP-mux PUCCH and the LP PUSCH may be performed.
D. If the LP effort overlaps with the HP pure PUSCH (on the same cell), the operations in Opt 1/2 in case 1 above can be applied.
E. In case 2, the operation in Opt a/B may vary depending on the enable/disable configuration for the Inter-p_pucch_mux.
3) Case 3
A. Achievements for LP step 1
I. After one or more LP PUCCHs overlapping in time are multiplexed on a specific LP PUCCH (e.g., LP-mux PUCCH) through sub-step 1-1, the LP-mux PUCCH may not overlap in time with the LP PUSCH. As a result, the corresponding LP-mux PUCCH may be the final LP result of step 1.
B. achievements of step1 for HP
I. As in case 1 above, HP UCI-PUSCH may be the final HP outcome of step 1.
C. In this case, if the LP effort overlaps in time with the HP effort or another HP pure PUSCH (on any cell), the following operations may be considered.
I. When Inter-p_pusch_mux and pucch+pusch_tx are configured as follows: inter-p_pusch_mux=enabled and pucch+pusch_tx=disabled, the LP UCI included in the LP-mux PUCCH may be multiplexed on the HP effort (overlapping in time) or HP pure PUSCH and then transmitted.
Ii. when Inter-p_pusch_mux and pucch+pusch_tx are configured as follows: when Inter-p_pusch_mux=disabled and pucch+pusch_tx=disabled, only HP achievements or HP pure PUSCHs overlapping in time may be sent and transmissions of LP-mux PUCCH transmissions may be dropped.
When Inter-p_pusch_mux and pucch+pusch_tx are configured as follows: with Inter-p_pusch_mux=disabled and pucch+pusch_tx=enabled, transmissions of LP-mux PUCCH may be dropped if the HP PUSCHs overlapping in time are on the same band (or cell) as the LP-mux PUCCH. If the HP PUSCH is on a different band (or cell), simultaneous transmission of the LP-mux PUCCH and HP PUSCH may be performed.
When Inter-p_pusch_mux and pucch+pusch_tx are configured as follows: inter-p_pusch_mux=enabled and pucch+pusch_tx=enabled, if the HP PUSCHs overlapping in time are on the same band (or cell) as the LP-mux PUCCH, the LP UCI included in the LP-mux PUCCH may be multiplexed on the corresponding HP PUSCH. If the HP PUSCH is on a different band (or cell), simultaneous transmission of the LP-mux PUCCH and HP PUSCH may be performed.
D. If the HP effort overlaps with the LP-pure PUSCH (on the same cell), the transmission of the corresponding LP-pure PUSCH can be discarded.
E. In case 3, no operation may vary depending on the enable/disable configuration for the Inter-p_pucch_mux.
4) Case 4
A. Results of step1 for LP
As in case 3 above, the LP-mux PUCCH may be the final LP result of step 1.
B. achievements of step1 for HP
As in case 2 above, the HP-mux PUCCH may be the final HP result of step 1.
C. Case 4-1
I. When the LP effort overlaps in time with the HP effort, the LP UCI included in the LP effort and the HP UCI included in the HP effort may be multiplexed on a single PUCCH (e.g., hp+lp-mux PUCCH). The corresponding HP+LP-mux PUCCH may be the result of sub-step 2-1 of step2 above.
In this case, if the hp+lp-mux PUCCH overlaps in time (on any cell) with the HP pure PUSCH or the LP pure PUSCH, the following operations may be considered.
I. when Inter-p_pusch_mux and pucch+pusch_tx are configured as follows: the HP UCI and LP UCI included in the hp+lp-mux PUCCH may be multiplexed on the HP pure PUSCH or the LP pure PUSCH (overlapping in time) and then transmitted when Inter-p_pusch_mux=enabled and pucch+pusch_tx=disabled.
Ii. when Inter-p_pusch_mux and pucch+pusch_tx are configured as follows: inter-p_pusch_mux=disabled and pucch+pusch_tx=disabled:
a) Opt a: only PUCCH may be transmitted and transmissions of HP pure PUSCH or LP pure PUSCH overlapping in time with hp+lp-mux may be dropped.
B) Opt B: when LP pure PUSCHs overlap in time, the transmission of the corresponding LP pure PUSCH may be dropped. When HP pure PUSCHs overlap in time, HP UCI included in the hp+lp-mux PUCCH may be multiplexed on the HP pure PUSCH, and transmission of the LP UCI may be discarded.
3. When Inter-p_pusch_mux and pucch+pusch_tx are configured as follows: inter-p_pusch_mux=disabled and pucch+pusch_tx=enabled, the operations in Opt a/B may be applied if the HP PUSCH or LP PUSCH overlapping in time are on the same band (or cell) as the hp+lp-mux PUCCH. If the HP PUSCH or the LP PUSCH are on different bands (or cells), simultaneous transmission of the HP+LP-mux PUCCH and the PUSCH may be performed.
4. When Inter-p_pusch_mux and pucch+pusch_tx are configured as follows: inter-p_pusch_mux=enabled and pucch+pusch_tx=enabled, if the HP PUSCH or LP PUSCH overlapping in time is on the same band (or cell) as the hp+lp-mux PUCCH, HP UCI and LP UCI included in the hp+lp-mux PUCCH may be multiplexed on the corresponding PUSCH. If the HP PUSCH or the LP PUSCH are on different bands (or cells), simultaneous transmission of the HP-mux PUCCH and the PUSCH may be performed.
In case 4-1, when Inter-p_pucch_mux is configured as follows: inter-p_pucch_mux=disabled, the transmission of the LP-mux PUCCH in substep 2-1 of step 2 may be dropped, and the HP-mux PUCCH may be the result (in which case the operations described in case 2 above may be applied).
D. Case 4-2
I. When the LP and HP achievements do not overlap in time, both the HP-mux PUCCH and the LP-mux PUCCH may be achievements of sub-step 2-1 in step 2.
In this case, if the XP-mux PUCCH overlaps in time with YP-pure PUSCH (on any cell), the following operations may be considered.
1. When Inter-p_pusch_mux and pucch+pusch_tx are configured as follows: inter-p_pusch_mux=enabled and pucch+pusch_tx=disabled, XP UCI included in the XP-mux PUCCH may be multiplexed on yppusch (overlapping in time) and then transmitted.
2. When Inter-p_pusch_mux and pucch+pusch_tx are configured as follows: inter-p_pusch_mux=disabled and pucch+pusch_tx=disabled, only HP-mux PUCCH (or HP PUSCH) may be transmitted, and LP PUSCH (or LP-mux PUCCH) overlapping in time therewith may be discarded.
3. When Inter-p_pusch_mux and pucch+pusch_tx are configured as follows: inter-p_pusch_mux=disabled and pucch+pusch_tx=enabled, if the LP PUSCH (or LP-mux PUCCH) overlapping in time (is on the same band (or cell) as the HP-mux PUCCH (or HP PUSCH)), then the transmission of the LP PUSCH (or LP-mux PUCCH) may be dropped. If the LP PUSCH (or LP-mux PUCCH) is on a different band (or cell), simultaneous transmission of the HP-mux PUCCH (or HP PUSCH) and the LP PUSCH (or LP-mux PUCCH) may be performed.
4. When Inter-p_pusch_mux and pucch+pusch_tx are configured as follows: inter-p_pusch_mux=enabled and pucch+pusch_tx=enabled, the XP UCI included in the XP-mux PUCCH may be multiplexed on the corresponding YP PUSCH if the YP PUSCH overlapping in time is on the same band (or cell) as the XP-mux PUCCH. If the YP PUSCH is on a different band (or cell), simultaneous transmission of the XP-mux PUCCH and the YP PUSCH may be performed.
In case 4-2, no operation may vary depending on the enable/disable configuration of the Inter-p_pucch_mux.
For the combination of Inter-p_pucch_mux=enabled and Inter-p_pusch_mux=disabled to be configured, alt 1 may be applied as an exception (while Alt 2 may be applied to the remaining combinations). In the above combination, if step 1 of Alt 2, which multiplexes for the same priority, is applied and then LP UCI is multiplexed on LP PUSCH, it is more likely to be discarded due to overlapping in time with HP PUCCH or HP PUSCH in step 2. However, when Alt 1 is applied, even though the LP PUCCH overlaps the HP PUCCH in step 1, the LP PUCCH is more likely to be multiplexed without being discarded. Alternatively, when the Inter-p_pucch is configured as follows: inter-p_pucch_mux = enabled, it may be specified/enforced that Inter-p_pusch_mux is always configured as follows: inter-p_pusch_mux=enabled.
Proposal 2
Additionally, when pucch+pusch_tx is configured as follows: pucch+pusch_tx=enabled (e.g., when the UE is configured with parameters for simultaneous transmission of XP PUCCH and YP PUSCH on different bands), the following UCI/UL (channel) multiplexing transmission operation method may be considered for PUSCH transmission. For example, the PUSCH transmission may be a scheduled PUSCH (e.g., a PUSCH transmission scheduled by UL grant DCI), but the disclosure is not limited thereto. That is, the PUSCH transmission may be PUSCH transmitted based on a Configuration Grant (CG). As a specific example of a scheduled PUSCH, transmission of aperiodic CSI reports (e.g., aperiodic channel state information (a-CSI)) on a specific PUSCH may be considered triggered. As described above, the UL grant DCI triggering the a-CSI on the PUSCH may include a field indicating a priority index of the corresponding PUSCH. Alternatively, if there is no separate priority index indicated by DCI, the priority of the corresponding PUSCH may be regarded as LP.
1)Alt A
The UE may be configured to multiplex (piggyback) UCI in PUCCH only on PUSCH (which overlaps PUCCH) on the same band (or cell) as PUCCH. As one of conditions that UCI in the XP PUCCH should satisfy for multiplexing (piggybacking) on yppusch, XP PUCCH and YP PUSCH may be required to be located on the same band. For example, the UE may not be allowed to piggyback UCI in the first PUCCH on the first band on a second PUSCH (different from the first band) on a second band (or cell) (which is different from the first band) (which is overlapping in time with the first PUCCH), where the second PUSCH may be, for example, an a-CSI triggered PUSCH or another PUSCH. In this case, if a first PUSCH overlapping in time with a first PUCCH is scheduled on a first band, the UE may piggyback UCI in the first PUCCH on the first PUSCH on the same first band (or cell). If there is no first PUSCH overlapping in time with the first PUCCH on the first band, the UE may simultaneously transmit the first PUCCH on the first band and the second PUSCH on the second band. In this case, it is assumed that the priority index of the first PUCCH is different from the priority index of the second PUSCH. On the other hand, cells belonging to the same PUCCH (cell) group may be sub-grouped into one or two or more sub-groups, which will be described later. Cells belonging to the same subgroup may be on the same band and cells belonging to different subgroups may be on different bands. For example, when the first and second cells configured for CA belong to the same PUCCH cell group, if the first and second cells are on different bands (e.g. inter-band CA in table 7/8), the first and second cells may belong to different subgroups. According to this proposal, inter-band CA is required for PUCCH/PUSCH simultaneous transmission, which provides advantages in terms of reducing complexity of a Radio Frequency (RF) module of the UE and a low peak-to-average power ratio (PAPR). For example, the UE uses a relatively compact and cost-effective RF module compared to the BS, which results in a limited frequency range covered by one RF module of the UE. For example, for bands that are far apart in the frequency domain, different RF modules may be required. Simultaneous transmission based on different RF modules may not cause PAPR problems due to OFDM modulation, but PUCCH/PUSCH transmission based on the same RF module may cause relatively high PAPR. Thus, when PUCCH and PUSCH are on the same band, PUCCH may be piggybacked on PUSCH, thereby reducing UE complexity and PAPR.
Fig. 8 illustrates a UL signal transmission method (e.g., a method related to 1) Alt a of proposal 2) according to an embodiment of the disclosure. In fig. 8, it is assumed that the parameter pucch+pusch_tx=enable is configured to the UE to configure simultaneous transmission of PUCCH and PUSCH on different bands (and different cells) with different priorities is allowed. Referring to fig. 8, PUCCHs and PUSCHs having different priorities may overlap each other (a 05). The UE may check whether the overlapped PUCCH and PUSCH are for inter-band CA (in the same PUCCH group) (a 10) and perform UL transmission. If the cell for overlapping PUCCH and the cell for overlapping PUSCH are on different bands (while the cells belong to the same PUCCH group) (i.e. yes in a 10: inter-band CA), the UE simultaneously transmits PUCCH and PUSCH (a 20). Otherwise (no in a 10), the UE needs to perform an operation to solve the overlap between PUCCH and PUSCH (a 15). As an example of an operation to solve overlap between PUCCH and PUSCH, UCI in PUCCH may be piggybacked on PUSCH. In this case, PUSCH carrying UCI may be transmitted without transmitting PUCCH. On the other hand, if it is determined that PUCCH and PUSCH are simultaneously transmitted, the corresponding PUCCH and PUSCH may be excluded from the overlap resolution operation performed by the UE.
Fig. 9 illustrates various examples of overlapping PUCCH/PUSCH (e.g., various application examples of fig. 8). In fig. 9, it is assumed that the parameter pucch+pusch_tx=enable is configured to the UE to configure simultaneous transmission of PUCCH and PUSCH on different bands (and different cells) with different priorities is allowed. It is also assumed that cell a, cell B and cell C belong to band 1 and cell D belongs to band 2.
Referring to fig. 9 (a), XP PUCCH 802a, YP PUSCH 801a, and YP PUSCH 803a overlap in the time domain. Based on multiplexing between channels of different priorities being configured, the UE multiplexes (e.g., piggybacks) UCI in the XP PUCCH 802a onto the YP PUSCH 801a, which overlaps with the XP PUCCH 802a on the same band (band 1). YP PUSCH 803a in band 2 is transmitted without UCI multiplexing.
Referring to fig. 9 (b), XP PUSCH 802b, YP PUSCH 801b, YP PUSCH 803b, and YP PUSCH 804 overlap in the time domain. Based on multiplexing between different priority channels being configured, the UE determines that one of YP PUSCH 801b and YP PUSCH 804b in band 1 is YP PUSCH multiplexed with UCI in XP PUCCH 802 a. YP PUSCH 803b in band 2 is transmitted without UCI multiplexing.
Fig. 10 is a diagram for explaining an operation of solving overlap between PUCCH/PUSCH according to an embodiment of the present disclosure. Referring to fig. 10, the ue first solves the overlap between PUCCHs/PUSCHs having the same priority (B05). Thereafter, the UE resolves overlap between PUCCHs having different priorities (B10). Then, the UE resolves the overlap between PUCCHs/PUSCHs of different priorities (in the same PUCCH group and the same band) (B15). As a result of performing the overlap-and-parse operation, the UE performs simultaneous transmission of PUCCH/PUSCH having different priorities on different bands, which is finally determined to be transmitted (B20).
2)Alt B
When PUCCH and a-CSI triggered PUSCH overlap in time, UCI in the corresponding PUCCH may be exceptionally piggybacked on the corresponding a-CSI triggered PUSCH, whether the two UL channels are on the same band (or cell) or different bands (or cells). If there is no a-CSI triggered PUSCH overlapping in time with the PUCCH, an operation in Alt a may be performed.
3)Alt C
When PUSCH overlaps with PUCCH on the same band (or cell) in time, one PUSCH is selected among all PUSCHs (on all bands (or cells) in the same PUCCH cell group), and then UCI in PUCCH may be piggybacked on the corresponding PUSCH. On the other hand, when there is no PUSCH overlapping in time with the PUCCH on the same band (or cell) (if there is a PUSCH overlapping in time with the PUCCH on a different band (or cell)), simultaneous transmission of PUCCH and PUSCH transmission may be performed (without UCI piggybacking on PUSCH).
Proposal 3
Additionally, if LP channel resources and HP channel resources overlap in time (assuming Inter-p_pucch_mux=enabled and/or Inter-p_pusch_mux=enabled is configured/indicated) when repeated transmissions (across multiple slots or sub-slots) are configured/indicated for transmissions of at least one of an LP channel (e.g., PUCCH or PUSCH) and an HP channel (e.g., PUCCH or PUSCH) (or when repeated transmissions are not configured/indicated for transmissions of both the LP channel and the HP channel), the following UE operations may be considered. In this case, if one of the LP and HP channels is PUCCH and the other is PUSCH, the two channels may be on the same band (or cell) (within the same PUCCH cell group) (when pucch+pusch_tx=enabled is configured/indicated). Alternatively, when pucch+pusch_tx=disabled is configured/indicated, the two channels may be on any cell (e.g., the same or different cells) (within the same PUCCH cell group).
1) Case 1
A. When the non-repetition based LP PUCCH carrying LP UCI (e.g., HARQ-ACK) and the non-repetition based HP PUCCH carrying HP UCI (e.g., HARQ-ACK) overlap in time (while satisfying the UE processing timeline), the UE may be configured to multiplex and transmit the LP UCI and the HP UCI on one specific PUCCH (e.g., HP PUCCH).
B. when the non-repetition based LP PUCCH and the non-repetition based HP PUSCH carrying LP UCI overlap in time (while satisfying the UE processing timeline), the UE may be configured to multiplex and transmit the LP UCI on the HP PUSCH.
C. When the non-repetition based HP PUCCH and the non-repetition based LP PUSCH carrying HP UCI overlap in time (while satisfying the UE processing timeline above), then the UE may be configured to multiplex and transmit HP UCI on the LP PUSCH.
D. When non-repetition based LP PUCCH and repetition based HP PUSCH (e.g., forming one or more HP PUSCHs among the repeated multiple HP PUSCH resources) carrying the LP UCI overlap in time (while satisfying the UE processing timeline), the UE may be configured to multiplex and transmit the LP UCI on the HP PUSCH (e.g., one particular HP PUSCH among the one or more HP PUSCHs overlapping the LP PUCCH).
E. When the non-repetition based HP PUCCH and the repetition based LP PUSCH (e.g., forming one or more LP PUSCHs of the repeated plurality of LP PUSCH resources) carrying the HP UCI overlap in time (while satisfying the UE processing timeline), the UE may be configured to multiplex and transmit the HP UCI on the LP PUSCH (e.g., one specific LP PUSCH of the one or more LP PUSCHs overlapping the HP PUCCH).
2) Case 2
A. when the repetition-based LP PUCCH carrying the LP UCI and the repetition-based HP PUCCH carrying the HP UCI overlap in time (or the non-repetition-based HP PUCCH is satisfied at the same time as the UE processing timeline), the UE may be configured to transmit only the HP PUCCH (on only the overlapping PUCCH resources or in the slots/sub-slots including the PUCCH resources) and discard the transmission of the LP PUCCH (overlapping with the corresponding HP PUCCH).
B. When the repetition-based HP PUCCH carrying HP UCI and the repetition-based LP PUCCH carrying LP UCI overlap in time (or the non-repetition-based LP PUCCH is satisfied at the same time as the UE processing timeline), the UE may be configured to transmit only the HP PUCCH (on only the overlapping PUCCH resources or in the slots/sub-slots including the PUCCH resources) and discard the transmission of the LP PUCCH (overlapping with the corresponding HP PUCCH).
C. When the repetition-based LP PUCCH and the repetition-based HP PUSCH (or the non-repetition-based HP PUSCH) carrying the LP UCI overlap in time (while satisfying the UE processing timeline), the UE may be configured to transmit only the HP PUSCH (on only the overlapping PUCCH and PUSCH resources, or in the slots/sub-slots containing the PUCCH and PUSCH resources) and discard (overlap with the corresponding HP PUSCH) the transmission of the LP PUCCH.
D. when the repetition-based HP PUCCH and the repetition-based LP PUSCH (or the non-repetition-based LP PUSCH) carrying the HP UCI overlap in time (while satisfying the UE processing timeline), the UE may be configured to transmit only the HP PUCCH (on only the overlapping PUCCH and PUSCH resources, or in slots/sub-slots including the PUCCH and PUSCH resources) and discard the transmission of the LP PUSCH (overlapping the corresponding HP PUCCH).
E. When the repetition-based LP PUSCH and the repetition-based HP PUSCH (or the non-repetition-based HP PUSCH) overlap in time (while satisfying the UE processing timeline), the UE may be configured to transmit only the HP PUSCH (on only overlapping PUSCH resources, or in slots/sub-slots containing PUSCH resources) and discard transmissions of the LP PUSCH (overlapping with the corresponding HP PUSCH).
F. When the repetition-based HP PUSCH and the repetition-based LP PUSCH (or the non-repetition-based LP PUSCH) overlap in time (while satisfying the UE processing timeline), the UE may be configured to transmit only the HP PUSCH (on only overlapping PUSCH resources, or in slots/sub-slots including PUSCH resources) and discard transmissions of the LP PUSCH (overlapping with the corresponding HP PUSCH).
In this document, (frequency) band may mean that a plurality of cells belonging to a single PUCCH cell group are divided into one or more subgroups and cells belonging to the same subgroup are in the same band (i.e. cells belonging to different subgroups are on different bands). Accordingly, information about a subgroup configured in one PUCCH cell group may be provided to the UE, and thus, a band in this document may be replaced with a subgroup.
Fig. 11 illustrates an implementation example of a method by which a UE transmits a signal in a wireless communication system according to an embodiment of the present disclosure. Fig. 11 is an example for better understanding of the above description, and the scope of the present disclosure is not limited to the following description. Redundant description may be omitted and reference may be made to the above description if necessary.
Referring to fig. 11, the ue may receive parameters related to PUCCH-PUSCH simultaneous transmission (C05).
The parameter related to PUCCH-PUSCH simultaneous transmission may be a parameter for enabling simultaneous transmission of overlapping PUCCH-PUSCHs having different priorities within the same PUCCH cell group.
The UE may perform UL transmission related to at least one of the PUCCH and one or more PUSCHs overlapping the PUCCH (C10).
The one or more PUSCHs overlapping the PUCCH may include at least one of a first PUSCH on a first band to which a cell of the PUCCH belongs and a second PUSCH on a second band having at least one cell.
In a state where simultaneous transmission of the overlapping PUCCH-PUSCHs has been enabled, the UE may perform UL transmission without multiplexing UCI in the PUCCH on the second PUSCH based on a first band to which a cell of the PUCCH belongs being different from a second band to which a cell of the second PUSCH belongs.
The priority of the PUCCH may be different from the priority of the second PUSCH. The cell of the PUCCH and the cell of the second PUSCH may belong to the same PUCCH cell group. The PUCCH and the second PUSCH may be transmitted simultaneously. The simultaneous transmission of PUCCH and second PUSCH may be based on inter-band CA.
When UCI in the PUCCH is multiplexed to PUSCH, PUSCH may be determined as one of PUSCHs on the first band.
Based on the parameters, simultaneous transmission of the PUCCH on the first band and the second PUSCH on the second band may be allowed, but multiplexing of the PUCCH on the first band and the second PUSCH on the second band may not be allowed.
Based on the UE being configured with multiplexing between channels having different priorities and the priority of the PUCCH being different from that of the first PUSCH, UCI in the PUCCH may be transmitted through the first PUSCH other than the second PUSCH.
The UE may receive at least one of DCI scheduling a first PUSCH and DCI scheduling a second PUSCH on the PDCCH. The DCI may trigger an a-CSI report and include a priority index of a corresponding PUSCH.
The UE may first solve the overlap between the PUCCH and the PUSCH having the same priority, solve the overlap between the PUCCHs having different priorities, and then solve the overlap between the PUCCH and the PUSCH having different priorities.
Fig. 12 illustrates an implementation example of a method by which a BS receives a signal in a wireless communication system according to an embodiment of the present disclosure. Fig. 12 is an example for better understanding of the above description, and the scope of the present disclosure is not limited to the following description. Redundant description may be omitted and reference may be made to the above description if necessary.
Referring to fig. 12, the bs may transmit parameters related to PUCCH-PUSCH simultaneous transmission to the UE (D05).
The parameters related to PUCCH-PUSCH simultaneous transmission may be parameters for enabling the UE to perform simultaneous transmission of overlapping PUCCH-PUSCHs with different priorities within the same PUCCH cell group.
The BS may receive an UL signal (D10) related to at least one of the PUCCH and one or more PUSCHs overlapping the PUCCH from the UE.
The one or more PUSCHs overlapping the PUCCH may include at least one of a first PUSCH on a first band to which a cell of the PUCCH belongs and a second PUSCH on a second band having at least one cell.
In a state in which the UE is enabled to perform simultaneous transmission of the overlapping PUCCH-PUSCHs, the BS may receive the UL signal without demultiplexing UCI in the PUCCH from the second PUSCH based on a second band to which a cell of the PUCCH belongs, which is different from a first band to which a cell of the second PUSCH belongs.
The priority of the PUCCH may be different from the priority of the second PUSCH. The cell of the PUCCH and the cell of the second PUSCH may belong to the same PUCCH cell group. The PUCCH and the second PUSCH may be received simultaneously. The simultaneous reception of PUCCH and second PUSCH may be based on inter-band CA.
When UCI in the PUCCH is multiplexed to PUSCH, PUSCH may be determined as one of PUSCHs on the first band.
Based on the parameters, simultaneous reception of the PUCCH on the first band and the second PUSCH on the second band may be performed, but multiplexing of the PUCCH on the first band and the second PUSCH on the second band may not be performed.
Based on the BS configuring multiplexing between channels having different priorities to the UE and the priority of the PUCCH is different from that of the first PUSCH, UCI in the PUCCH may be received through the first PUSCH other than the second PUSCH.
The BS may transmit at least one of DCI scheduling the first PUSCH and DCI scheduling the second PUSCH on the PDCCH. The DCI may trigger an a-CSI report and include a priority index of a corresponding PUSCH.
Fig. 13 illustrates a communication system 1 applied to the present disclosure.
Referring to fig. 13, a 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. Wireless devices may include, but are not limited to, robots 100a, vehicles 100b-1 and 100b-2, augmented reality (XR) devices 100c, handheld devices 100d, home appliances 100e, internet of things (IoT) devices 100f, and Artificial Intelligence (AI) devices/servers 400. For example, the vehicles may include vehicles having wireless communication functions, autonomously driven vehicles, and vehicles capable of performing communication between the vehicles. Herein, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., an unmanned aerial vehicle). The XR devices may include Augmented Reality (AR)/Virtual Reality (VR)/Mixed Reality (MR) devices, and may be implemented in the form of head-mounted devices (HMDs), head-up displays (HUDs) installed in vehicles, televisions, smartphones, computers, wearable devices, home appliance devices, digital signage, vehicles, robots, and the like. Handheld devices may include smartphones, smartpads, wearable devices (e.g., smartwatches 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, the BS and network may be implemented as wireless devices, and a particular wireless device 200a may operate as a BS/network node with respect to other wireless devices.
The wireless devices 100a to 100f may connect 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 through 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, the vehicles 100b-1 and 100b-2 may perform direct communications (e.g., vehicle-to-vehicle (V2V)/vehicle-to-anything (V2X) communications). The IoT devices (e.g., sensors) may perform direct communications with other IoT devices (e.g., sensors) or other wireless devices 100 a-100 f.
Wireless communication/connection 150a, 150b, or 150c may be established between wireless devices 100 a-100 f/BS200 or BS200/BS 200. Herein, wireless communication/connection may be established through various RATs (e.g., 5G NR) such as uplink/downlink communication 150a, side link communication 150b (or D2D communication), or inter-BS communication (e.g., relay, integrated Access Backhaul (IAB)). The wireless device and BS/wireless device may transmit/receive radio signals to/from each other through wireless communication/connections 150a and 150 b. For example, wireless communication/connections 150a and 150b may transmit/receive signals over various physical channels. To this end, at least a part of various configuration information configuring a procedure for transmitting/receiving a radio signal, various signal processing procedures (e.g., channel coding/decoding, modulation/demodulation, and resource mapping/demapping), and resource allocation procedures may be performed based on various proposals of the present disclosure.
Fig. 14 illustrates a wireless device suitable for use in the present disclosure.
Referring to fig. 14, the first wireless device 100 and the second wireless device 200 may transmit radio signals through various RATs (e.g., LTE and NR). Herein, { first wireless device 100 and second wireless device 200} may correspond to { wireless device 100x and BS200} and/or { wireless device 100x and wireless device 100x } of fig. 13.
The first wireless device 100 may include one or more processors 102 and one or more memories 104, and additionally 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 descriptions, functions, procedures, proposals, methods and/or operational flowcharts disclosed in this document. For example, the processor 102 may process the information within the memory 104 to generate first information/signals and then transmit radio signals including the first information/signals through the transceiver 106. The processor 102 may receive a radio signal including the second information/signal through the transceiver 106 and then store information obtained by processing the second information/signal 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 code including instructions for performing part or all of the processes controlled by the processor 102 or for performing the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams 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 coupled to the processor 102 and transmit and/or receive radio signals via 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 this disclosure, a wireless device may represent a communication modem/circuit/chip.
The second wireless device 200 may include one or more processors 202 and one or more memories 204, and additionally 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 descriptions, functions, procedures, proposals, methods and/or operational flowcharts disclosed in this document. For example, the processor 202 may process the information within the memory 204 to generate a third information/signal and then transmit a radio signal including the third information/signal through the transceiver 206. The processor 202 may receive a radio signal including the fourth information/signal through the transceiver 206 and then store information obtained by processing the fourth information/signal 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 code including instructions for performing part or all of the processes controlled by the processor 202 or for performing the descriptions, functions, procedures, suggestions, methods, and/or operational flow diagrams 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 can include a transmitter and/or a receiver. The transceiver 206 may be used interchangeably with RF unit. In this disclosure, a wireless device may represent a communication modem/circuit/chip.
Hereinafter, 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 are not limited to, one or more processors 102 and 202. For example, one or more of processors 102 and 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC and SDAP). The 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, procedures, 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 in accordance with the descriptions, functions, procedures, suggestions, methods, and/or operational flowcharts disclosed in this document. The one or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document, and provide the generated signals to the one or more transceivers 106 and 206. The one or more processors 102 and 202 may receive signals (e.g., baseband signals) from the one or more transceivers 106 and 206 and obtain PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document.
One or more of the processors 102 and 202 may be referred to as a controller, microcontroller, microprocessor, or microcomputer. One or more of the processors 102 and 202 may be implemented in 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 the one or more processors 102 and 202. The descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be configured to include modules, procedures or functions. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods and/or operational flowcharts disclosed in this document may be included in the one or more processors 102 and 202 or stored in the one or more memories 104 and 204 to be driven by the one or more processors 102 and 202. The descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in this document may be implemented using firmware or software in the form of codes, commands and/or command sets.
One or more memories 104 and 204 may be coupled to one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, code, instructions, and/or commands. One or more of the 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, a hard drive, registers, a cache memory, a computer-readable storage medium, and/or combinations thereof. The one or more memories 104 and 204 may be located internal and/or external to the one or more processors 102 and 202. The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 by various techniques, such as a wired or wireless connection.
One or more transceivers 106 and 206 may transmit the user data, control information, and/or radio signals/channels mentioned in the methods and/or operational flow diagrams of this document to one or more other devices. One or more transceivers 106 and 206 may receive the user data, control information, and/or radio signals/channels mentioned in the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts 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 transmit and receive radio signals. For example, the one or more processors 102 and 202 may perform control such that the one or more transceivers 106 and 206 may transmit user data, control information, or radio signals to one or more other devices. The one or more processors 102 and 202 may perform control such that the 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 transmit and receive the user data, control information, and/or radio signals/channels mentioned in the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts 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). The one or more transceivers 106 and 206 may convert received radio signals/channels, etc., from RF band signals to baseband signals for processing received user data, control information, radio signals/channels, etc., using the one or more processors 102 and 202. The one or more transceivers 106 and 206 may convert user data, control information, radio signals/channels, etc., processed using the 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.
Fig. 15 illustrates another example of a wireless device applied to the present disclosure. Wireless devices may be implemented in various forms depending on the use case/service (see fig. 13).
Referring to fig. 15, wireless devices 100 and 200 may correspond to wireless devices 100 and 200 of fig. 14 and may be configured by various elements, components, units/portions, 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 one or more processors 102 and 202 and/or one or more memories 104 and 204 of fig. 14. For example, transceiver 114 may include one or more transceivers 106 and 206 and/or one or more antennas 108 and 208 of fig. 14. 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 programs/codes/commands/information stored in the memory unit 130. The control unit 120 may transmit 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.
The additional components 140 may be configured differently depending on the type of wireless device. For example, the additional component 140 may include at least one of a power supply unit/battery, an input/output (I/O) unit, a driving unit, and a computing unit. The wireless device may be implemented as, but is not limited to, a robot (100 a of fig. 13), a vehicle (100 b-1 and 100b-2 of fig. 13), an XR device (100 c of fig. 13), a handheld device (100 d of fig. 13), a home appliance (100 e of fig. 13), an IoT device (100 f of fig. 13), a digital broadcast terminal, a holographic device, a public safety device, an MTC device, a medical device, a financial technology device (or a financial device), a security device, a climate/environment device, an AI server/device (400 of fig. 13), a BS (200 of fig. 13), a network node, etc. The wireless device may be used in a mobile or stationary location depending on the use case/service.
In fig. 15, various elements, components, units/portions and/or modules in wireless devices 100 and 200 may all be connected to each other through wired interfaces, or at least a portion thereof may be connected wirelessly through 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 connected by wire, and the control unit 120 and the first unit (e.g., 130 and 140) may be connected wirelessly through the communication unit 110. The various elements, components, units/portions and/or modules within wireless devices 100 and 200 may also include one or more elements. For example, the control unit 120 may be configured by a set of one or more processors. As an example, the control unit 120 may be configured by a set 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 Random Access Memory (RAM), dynamic RAM (DRAM), read Only Memory (ROM)), flash memory, volatile memory, non-volatile memory, and/or combinations thereof.
Fig. 16 illustrates a vehicle or autonomous driving vehicle applied to the present disclosure. The vehicle or autonomous driving vehicle may be implemented by a mobile robot, a car, a train, a manned/unmanned Aircraft (AV), a ship, or the like.
Referring to fig. 16, the vehicle or autonomous driving vehicle 100 may include an antenna unit 108, a communication unit 110, a control unit 120, a driving 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 part of the communication unit 110. Blocks 110/130/140a through 140d correspond to blocks 110/130/140, respectively, of FIG. 15.
The communication unit 110 may transmit and receive signals (e.g., data and control signals) to and from external devices such as other vehicles, BSs (e.g., gNB and roadside units), and servers. The control unit 120 may perform various operations by controlling elements of the vehicle or the autonomously driven vehicle 100. The control unit 120 may include an Electronic Control Unit (ECU). The driving unit 140a may cause the vehicle or the autonomous driving vehicle 100 to travel on a road. The drive unit 140a may include an engine, a motor, a power system, wheels, brakes, steering devices, and the like. The power supply unit 140b may supply power to the vehicle or the autonomous driving vehicle 100, and includes a wired/wireless charging circuit, a battery, and the like. The sensor unit 140c may acquire vehicle status, surrounding information, user information, and the like. The sensor unit 140c may include an Inertial Measurement Unit (IMU) sensor, a collision sensor, a wheel sensor, a speed sensor, a gradient 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, an illumination sensor, a pedal position sensor, and the like. The autonomous driving unit 140d may implement a technique for maintaining a lane in which the vehicle is traveling, a technique for automatically adjusting a speed (e.g., adaptive cruise control), a technique for autonomously traveling along a determined path, a technique for traveling by automatically setting a path if a destination is set, and the like.
For example, the communication unit 110 may receive map data, traffic information data, and the like 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 such that the vehicle or the autonomous driving vehicle 100 may move along the autonomous driving path according to a driving plan (e.g., speed/direction control). In the middle of autonomous driving, the communication unit 110 may aperiodically/periodically acquire recent traffic information data from an external server and acquire surrounding traffic information data from a neighboring vehicle. In the middle of autonomous driving, the sensor unit 140c may obtain vehicle state and/or ambient information. The autonomous driving unit 140d may update the autonomous driving path and the driving plan based on the newly obtained data/information. The communication unit 110 may transmit information about the vehicle location, the autonomous driving path, and/or the driving plan to an external server. The external server may predict traffic information data using AI technology or the like based on information collected from the vehicle or the autonomous driving vehicle, and provide the predicted traffic information data to the vehicle or the autonomous driving vehicle.
Fig. 17 is a diagram illustrating a DRX operation of a UE according to an embodiment of the present disclosure.
The UE may perform DRX operations in the processes and/or methods described/suggested above. A UE configured with DRX may reduce power consumption by discontinuously receiving DL signals. DRX may be performed in an rrc_idle state, an rrc_inactive state, and an rrc_connected state. The UE performs DRX to discontinuously receive a paging signal in an rrc_idle state and an rrc_inactive state. DRX in the rrc_connected state (rrc_connected DRX) will be described below.
Referring to fig. 17, a 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 a 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 PDCCH monitoring, the UE starts an inactivity timer and remains awake. In contrast, when the UE fails to detect any PDCCH during PDCCH monitoring, the UE transitions to a sleep state after an on duration. Accordingly, when configuring DRX, PDCCH monitoring/reception may be discontinuously performed in the time domain in the procedure and/or method described/suggested above. For example, when configuring DRX, PDCCH reception opportunities (e.g., slots with PDCCH SS) may be discontinuously configured according to the DRX configuration in the present disclosure. In contrast, when DRX is not configured, PDCCH monitoring/reception may be continuously performed in the time domain. For example, when DRX is not configured, PDCCH reception opportunities (e.g., slots with PDCCH SS) may be continuously configured in the present disclosure. Whether DRX is configured or not, PDCCH monitoring may be limited during a time period configured as a measurement gap.
Table 10 describes DRX operation of the UE (in rrc_connected state). Referring to table 6, DRX configuration information is received through higher layer signaling (e.g., RRC signaling), and DRX on/off is controlled through a DRX command from the MAC layer. Once DRX is configured, the UE may discontinuously perform PDCCH monitoring while performing the above-described/proposed procedures and/or methods.
TABLE 10
The MAC-CellGroupConfig includes configuration information required to configure the MAC parameters for the cell group. MAC-CellGroupConfig may also include DRX configuration information. For example, the MAC-CellGroupConfig may include the following information when defining DRX.
Value of drx-onduration timer: the duration of the start period of the DRX cycle is defined.
Value of drx-inactivatetimer: the duration of a time period for which the UE wakes up after detecting a PDCCH occasion indicating a PDCCH of initial UL or DL data is defined.
-Value of drx-HARQ-RTT-TimerDL: the duration of the maximum time period after receiving the DL initial transmission until receiving the DL retransmission is defined.
-Value of drx-HARQ-RTT-TimerDL: a duration of a maximum time period after receiving the UL initial transmission grant until receiving the UL retransmission grant is defined.
-Drx-LongCycleStartOffset: the duration and start time of the DRX cycle are defined.
-Drx-ShortCycle (optional): the duration of the short DRX cycle is defined.
When any one of drx-OnDurationTimer, drx-INACTIVITYTIMER, DRX-HARQ-RTT-TimerDL and drx-HARQ-RTT-TimerDL is operated, the UE performs PDCCH monitoring at each PDCCH occasion, and remains in an awake state.
The above-described embodiments correspond to combinations of elements and features of the present disclosure in a prescribed form. Also, individual elements or features may be considered optional unless explicitly mentioned. Each of the elements or features can be implemented in a form that cannot be combined with other elements or features. Moreover, embodiments of the disclosure can be implemented by combining elements and/or features in part. The sequence of operations explained for each embodiment of the present disclosure can be modified. Some configurations or features of one embodiment can be included in another embodiment or can replace corresponding configurations or features of another embodiment. Also, it is to be expressly understood that the embodiments are configured by combining claims that do not explicitly refer to the relationship in the appended claims or can be included as new claims by modification after filing the application.
Those skilled in the art will appreciate that the present disclosure can be carried out in other specific ways than those herein set forth without departing from the spirit and essential characteristics of the disclosure. The above embodiments are therefore to be construed in all aspects as illustrative and not restrictive. The scope of the present disclosure should be determined by the appended claims and their legal equivalents, rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the appended claims are intended to be embraced therein.
INDUSTRIAL APPLICABILITY
The present disclosure is applicable to a UE, BS, or other device in a wireless mobile communication system.
Claims (15)
1. A method of transmitting a signal by a User Equipment (UE) in a wireless communication system, the method comprising:
receiving parameters related to Physical Uplink Control Channel (PUCCH) -Physical Uplink Shared Channel (PUSCH) simultaneous transmissions; and
Uplink (UL) transmissions related to at least one of a PUCCH and one or more PUSCHs overlapping the PUCCH are performed,
Wherein the parameter related to the PUCCH-PUSCH simultaneous transmission is a parameter for enabling simultaneous transmission of overlapping PUCCH-PUSCHs having different priorities within the same PUCCH cell group,
Wherein the one or more PUSCHs overlapping the PUCCH include at least one of a first PUSCH on a first band to which a cell of the PUCCH belongs and a second PUSCH on a second band having at least one cell, and
Wherein, in a state in which the simultaneous transmission of the overlapping PUCCH-PUSCHs has been enabled, the UE performs the UL transmission based on the first band to which the cell of the PUCCH belongs being different from the second band to which the cell of the second PUSCH belongs without multiplexing Uplink Control Information (UCI) of the PUCCH into the second PUSCH.
2. The method of claim 1, wherein the priority of the PUCCH is different from the priority of the second PUSCH,
Wherein the cell of the PUCCH and the cell of the second PUSCH belong to the same PUCCH cell group, an
Wherein the PUCCH and the second PUSCH are transmitted simultaneously.
3. The method of claim 1, wherein the PUSCH is determined as one of the PUSCHs on the first band based on the UCI in the PUCCH being multiplexed into PUSCH.
4. The method of claim 1, wherein simultaneous transmission of the PUCCH on the first band and the second PUSCH on the second band is allowed based on the parameter, and
Wherein multiplexing of the PUCCH on the first band and the second PUSCH on the second band is not allowed.
5. The method of claim 1, wherein the UCI in the PUCCH is transmitted through the first PUSCH other than the second PUSCH based on the UE being configured with multiplexing between channels of different priorities and the priority of the PUCCH being different from the priority of the first PUSCH.
6. The method of claim 2, wherein the simultaneous transmission of the PUCCH and the second PUSCH is based on inter-band carrier aggregation.
7. The method of claim 1, further comprising:
at least one of Downlink Control Information (DCI) for scheduling the first PUSCH or DCI for scheduling the second PUSCH is received through a Physical Downlink Control Channel (PDCCH).
8. The method of claim 1, wherein Downlink Control Information (DCI) triggers an aperiodic Channel State Information (CSI) report and includes a priority index of the PUSCH.
9. The method of claim 1, wherein the UE first solves an overlap between PUCCHs and PUSCHs having the same priority, solves an overlap between PUCCHs having different priorities, and then solves an overlap between PUCCHs and PUSCHs having different priorities.
10. A computer-readable recording medium having recorded thereon a program for executing the method of claim 1.
11. An apparatus for wireless communication, the apparatus comprising:
A memory storing instructions; and
A processor configured to perform operations by executing the instructions,
Wherein the operations of the processor include:
receiving parameters related to Physical Uplink Control Channel (PUCCH) -Physical Uplink Shared Channel (PUSCH) simultaneous transmissions; and
Uplink (UL) transmissions related to at least one of a PUCCH and one or more PUSCHs overlapping the PUCCH are performed,
Wherein the parameter related to the PUCCH-PUSCH simultaneous transmission is a parameter for enabling simultaneous transmission of overlapping PUCCH-PUSCHs having different priorities within the same PUCCH cell group,
Wherein the one or more PUSCHs overlapping the PUCCH include at least one of a first PUSCH on a first band to which a cell of the PUCCH belongs and a second PUSCH on a second band having at least one cell, and
Wherein, in a state in which simultaneous transmission of overlapping PUCCH-PUSCHs has been enabled, based on the first band to which the cell of the PUCCH belongs being different from the second band to which the cell of the second PUSCH belongs, the processor is configured to perform the UL transmission without multiplexing Uplink Control Information (UCI) of the PUCCH into the second PUSCH.
12. The apparatus of claim 11, further comprising:
A transceiver configured to transmit or receive wireless signals under control of the processor,
Wherein the device is a User Equipment (UE) in a wireless communication system.
13. The device of claim 11, wherein the device is an Application Specific Integrated Circuit (ASIC) or a digital signal processor configured to control a User Equipment (UE).
14. A method of receiving a signal by a Base Station (BS) in a wireless communication system, the method comprising:
transmitting parameters related to Physical Uplink Control Channel (PUCCH) -Physical Uplink Shared Channel (PUSCH) simultaneous transmissions; and
An Uplink (UL) signal related to at least one of a PUCCH and one or more PUSCHs overlapping the PUCCH is received from the UE,
Wherein the parameter related to the PUCCH-PUSCH simultaneous transmission is a parameter for enabling the UE to perform simultaneous transmission of overlapping PUCCH-PUSCHs having different priorities within the same PUCCH cell group,
Wherein the one or more PUSCHs overlapping the PUCCH include at least one of a first PUSCH on a first band to which a cell of the PUCCH belongs and a second PUSCH on a second band having at least one cell, and
Wherein, in a state in which the UE is enabled to perform the simultaneous transmission of the overlapping PUCCH-PUSCHs, the BS receives the UL signal without demultiplexing Uplink Control Information (UCI) in the PUCCH from the second PUSCH based on the first band to which the cell of the PUCCH belongs being different from the second band to which the cell of the second PUSCH belongs.
15. A Base Station (BS) for wireless communication, the BS comprising:
a transceiver; and
A processor configured to control the transceiver to transmit parameters related to a Physical Uplink Control Channel (PUCCH) -Physical Uplink Shared Channel (PUSCH) simultaneous transmission to a User Equipment (UE), and to receive an Uplink (UL) signal related to at least one of a PUCCH and one or more PUSCHs overlapping the PUCCH from the UE,
Wherein the parameter related to the PUCCH-PUSCH simultaneous transmission is a parameter for enabling the UE to perform simultaneous transmission of overlapping PUCCH-PUSCHs having different priorities within the same PUCCH cell group,
Wherein the one or more PUSCHs overlapping the PUCCH include at least one of a first PUSCH on a first band to which the cell of the PUCCH belongs and a second PUSCH on a second band having at least one cell, and
Wherein, in a state in which the UE is enabled to perform the simultaneous transmission of the overlapping PUCCH-PUSCHs, based on the first band to which the cell of the PUCCH belongs being different from the second band to which the cell of the second PUSCH belongs, the processor is configured to receive the UL signal without demultiplexing Uplink Control Information (UCI) in the PUCCH from the second PUSCH.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| KR10-2021-0130228 | 2021-09-30 | ||
| US63/286,079 | 2021-12-05 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN118020363A true CN118020363A (en) | 2024-05-10 |
Family
ID=
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114641960B (en) | Method and apparatus for transmitting or receiving signal in wireless communication system | |
| US11902980B2 (en) | Method and device for transmitting/receiving wireless signal in wireless communication system | |
| CN112740590B (en) | Method and apparatus for transmitting and receiving wireless signal in wireless communication system | |
| CN112534943B (en) | Method and apparatus for transmitting and receiving wireless signal in wireless communication system | |
| CN112740591B (en) | Method and apparatus for transmitting and receiving wireless signal in wireless communication system | |
| CN114642065A (en) | Method and apparatus for transmitting and receiving signal in wireless communication system | |
| CN112740605B (en) | Method and apparatus for transmitting or receiving wireless signal in wireless communication system | |
| CN112534934B (en) | Method for transmitting or receiving signal in wireless communication system supporting unlicensed band and apparatus supporting the same | |
| US11864230B2 (en) | Method and apparatus for transmitting and receiving signal in wireless communication system | |
| US11791949B2 (en) | Method and apparatus for transmitting and receiving signal in wireless communication system | |
| CN114642071A (en) | Method for transmitting and receiving uplink channel in wireless communication system and apparatus therefor | |
| CN113796040B (en) | Method and apparatus for transmitting and receiving signal in wireless communication system | |
| CN115462164A (en) | Method and apparatus for transmitting and receiving signal in wireless communication system | |
| KR102588872B1 (en) | Method and device for transmitting and receiving signals in a wireless communication system | |
| US11909679B2 (en) | Method and device for transmitting/receiving signals in wireless communication system | |
| US20220353943A1 (en) | Method and apparatus for transmitting and receiving radio signal in wireless communication system | |
| CN116963304A (en) | Method and apparatus for transmitting and receiving signal in wireless communication system | |
| KR20240038925A (en) | Method and device for transmitting and receiving wireless signals in a wireless communication system | |
| EP4236155A1 (en) | Method and device for transmitting and receiving signal in wireless communication system | |
| EP4072233A1 (en) | Method and device for signal transmission or reception in wireless communication system | |
| CN118020363A (en) | Method and apparatus for transmitting and receiving signal in wireless communication system | |
| EP4210420B1 (en) | Method of performing a channel access procedure on a shared spectrum, computer readable medium, usre equipment, method of receioving a signal on a shared spectrum and base station | |
| US20220330317A1 (en) | Method and apparatus for transmitting and receiving signal in wireless communication system | |
| CN118020371A (en) | Method and apparatus for transmitting and receiving signal in wireless communication system | |
| CN117716775A (en) | Method and apparatus for transmitting and receiving wireless signal in wireless communication system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication |