CN118020371A - 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
- CN118020371A CN118020371A CN202280065325.0A CN202280065325A CN118020371A CN 118020371 A CN118020371 A CN 118020371A CN 202280065325 A CN202280065325 A CN 202280065325A CN 118020371 A CN118020371 A CN 118020371A
- Authority
- CN
- China
- Prior art keywords
- pdsch
- field
- dci
- mcs
- pdschs
- 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 111
- 238000004891 communication Methods 0.000 title claims description 75
- 230000015654 memory Effects 0.000 claims description 38
- 230000011664 signaling Effects 0.000 claims description 24
- 238000013507 mapping Methods 0.000 claims description 22
- 238000013468 resource allocation Methods 0.000 claims description 8
- 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 claims description 4
- 230000005540 biological transmission Effects 0.000 description 52
- 239000010410 layer Substances 0.000 description 40
- 238000012544 monitoring process Methods 0.000 description 17
- 230000008569 process Effects 0.000 description 16
- 230000006870 function Effects 0.000 description 15
- 230000004044 response Effects 0.000 description 14
- 238000005516 engineering process Methods 0.000 description 11
- 230000008054 signal transmission Effects 0.000 description 11
- 238000012545 processing Methods 0.000 description 9
- 208000037918 transfusion-transmitted disease Diseases 0.000 description 8
- 238000010586 diagram Methods 0.000 description 6
- 238000013473 artificial intelligence Methods 0.000 description 5
- 230000000694 effects Effects 0.000 description 3
- 101150071746 Pbsn gene Proteins 0.000 description 2
- 230000003190 augmentative effect Effects 0.000 description 2
- 230000008901 benefit Effects 0.000 description 2
- 230000015556 catabolic process Effects 0.000 description 2
- 125000004122 cyclic group Chemical group 0.000 description 2
- 238000006731 degradation reaction Methods 0.000 description 2
- 238000001514 detection method Methods 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
- 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
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000000712 assembly Effects 0.000 description 1
- 238000000429 assembly 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
- 239000004984 smart glass Substances 0.000 description 1
- 230000000153 supplemental effect Effects 0.000 description 1
- 230000001502 supplementing effect Effects 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
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
According to an embodiment of the present disclosure, a terminal may receive N PDSCHs scheduled by a single DCI, and the terminal may determine that all first TBs for all N PDSCHs are disabled based on a first MCS field of DCI indicating a specific MCS for a first TB of the N PDSCHs and a first RV field of DCI indicating only a specific RV for all first TBs of the N PDSCHs.
Description
Technical Field
The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for transmitting/receiving uplink/downlink wireless signals in 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, provided herein is a method of receiving a signal by a User Equipment (UE) in a wireless communication system. The method may include: receiving Downlink Control Information (DCI) for scheduling N Physical Downlink Shared Channels (PDSCH) through a single Physical Downlink Control Channel (PDCCH); and receiving the N PDSCHs based on the DCI. The DCI may include (i) a first Modulation and Coding Scheme (MCS) field for a first Transport Block (TB) of the N PDSCHs, and (ii) a first Redundancy Version (RV) field including N bits, each bit indicating an RV for each of the first TBs of the N PDSCHs. Based on the first MCS field of the first TB for the N PDSCHs being set to a specific MCS and all N bits included in the first RV field of the first TB for the N PDSCHs being set to only a specific RV, the UE may determine that all the first TBs are disabled for all the N PDSCHs.
The index of the specific MCS may be 26 and the index of the specific RV may be 2.
Based on the first MCS field of the first TBs for the N PDSCHs being set to the specific MCS and only a portion of the N bits included in the first RV field being set to the specific RV, the UE may determine that all the first TBs are enabled for all the N PDSCHs.
The maximum number of TBs that can be received on one PDSCH may be set to 2. The DCI may further include (iii) a second MCS field for a second TB of the N PDSCH, and (iv) a second RV field including N bits, each bit indicating an RV for each of the second TBs of the N PDSCH.
Based on the second MCS field of the second TB for the N PDSCHs being set to the specific MCS and all the N bits included in the second RV field of the second TB for the N PDSCHs being set to only a specific RV, the UE may determine that all the second TBs are disabled for all the N PDSCHs.
Based on the second MCS field of the second TB for the N PDSCHs being set to the specific MCS and all the N bits included in the second RV field of the second TB for the N PDSCHs being set to only the specific RV, the UE may determine that all the first TBs are disabled for all the N PDSCHs.
Each of the N bits included in the first RV field may indicate RV0 or RV2 for a first TB of an associated PDSCH.
The UE may receive configuration information related to the multi-PDSCH scheduling through higher layer signaling. The higher layer signaling may include TDRA tables, the TDRA tables including multiple combinations of { K0, SLIV, mapping types }. In each combination of { K0, SLIV, mapping type }, the 'K0' may represent a slot offset from a slot of the related DCI to a slot of the related PDSCH, the 'SLIV' may represent a start symbol of the related PDSCH and a symbol duration of the related PDSCH, and the 'mapping type' may be information for determining a position of a DMRS symbol of the related PDSCH. The DCI may indicate one row of the TDRA table.
The DCI may further include a first NDI field including N bits.
Each of the N bits of the first NDI field may be associated with each of the first TBs of the N PDSCH.
In another aspect of the present disclosure, provided herein is a computer-readable recording medium having recorded thereon a program for executing the method of claim 1.
In another aspect of the present disclosure, provided herein is a UE configured to perform the above-described signal reception method.
In another aspect of the present disclosure, provided herein is an apparatus configured to control a UE performing the above-described signal transmission method.
In another aspect of the present disclosure, provided herein is a method of transmitting a signal by a Base Station (BS) in a wireless communication system. The method may include: transmitting DCI for scheduling N PDSCHs through a single PDCCH; and transmitting the N PDSCHs based on the DCI. The DCI may include (i) a first MCS field for a first TB of the N PDSCHs, and (ii) a first RV field including N bits, each bit indicating an RV for each of the first TBs of the N PDSCHs. By setting the first MCS field of the first TB for the N PDSCHs to a specific MCS and setting all the N bits included in the first RV field of the first TB for the N PDSCHs to only a specific RV, the BS may inform a User Equipment (UE) to disable all the first TBs for all the N PDSCHs.
In another aspect of the present disclosure, provided herein is a BS configured to perform the above-described signal transmission 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. 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 to 10 are diagrams for explaining Downlink Control Information (DCI) scheduling a plurality of Physical Downlink Shared Channels (PDSCH) (multi-PDSCH scheduling DCI) according to an embodiment of the present disclosure.
Fig. 11 to 13 are flowcharts illustrating a signal transmission and reception method according to an embodiment of the present disclosure.
Fig. 14 to 17 illustrate a communication system 1 and a wireless device suitable for use in the present disclosure; and
Fig. 18 illustrates Discontinuous Reception (DRX) operation suitable for use with 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 Transmission Time Interval (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 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. A Transport Block (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 system information (SIB 1) broadcast in the cell includes cell-specific PDSCH configuration information PDSCH-ConfigCommon. PDSCH-ConfigCommon includes a list (or look-up table) PDSCH-TimeDomainAllocationList of parameters related to the time domain resource allocation of PDSCH. PDSCH-TimeDomainAllocationList may include up to 16 entries (or rows), each with a jointly encoded { K0, PDSCH mapping type, PDSCH starting Symbol and Length (SLIV) }. In addition to PDSCH-TimeDomainAllocationList configured by PDSCH-ConfigCommon, PDSCH-TimeDomainAllocationList may also be provided by UE-specific PDSCH-configured PDSCH-Config. The UE-specific configured pdsch-TimeDomainAllocationList may have the same structure as the UE-commonly configured pdsch-TimeDomainAllocationList. For K0 and SLIV of pdsch-TimeDomainAllocationList, the following description includes the description with reference to FIG. 5.
The PUCCH delivers Uplink Control Information (UCI). The 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), a Discontinuous Transmission (DTX), or a 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.
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 PDSCH reception and 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 DL assignment to PDSCH offset (DL ASSIGNMENT-to-PDSCH offset), K0, and PDSCH-to-HARQ-ACK reporting 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: k0 and a starting position (e.g., OFDM symbol index) and length (e.g., number of OFDM symbols) of the PDSCH in the slot are indicated. As described above, the row index of the pdsch-TimeDomainAllocationList, either UE-common or UE-specific provided, may be indicated by the TDRA field.
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 referred to by a Start and Length Indicator Value (SLIV).
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.
In the nrrel.15/16 system, depending on how the HARQ-ACK bits (payloads) are configured, three HARQ-ACK codebook types are defined: type 1, type 2, and type 3. In a type-1 codebook, HARQ-ACK payloads are configured according to a combination of a set of candidate HARQ-ACK timings (K1) and a set of candidate PDSCH opportunities (SLIV) configured for a respective cell based on the cell (e.g., a semi-static fixed length codebook based on RRC signaling). In a type-2 codebook, the codebook size may be dynamically changed according to the number of PDSCH actually scheduled or the corresponding number of resource allocations (e.g., DAI). In the type-3 codebook, the HARQ-ACK payload is configured by mapping HARQ-ACK bits to corresponding HARQ Process Numbers (HPNs) based on HPNs, according to the maximum number of HARQ processes (configured for the corresponding cell based on the cell) (e.g., one-time a/N reporting).
Multi-PDSCH scheduling/transmission/reception based on single DCI
3GPP (e.g., rel-15 and Rel-16) has recently been dedicated to standardization of 5G systems called New RATs (NR). NR systems seek to support multiple logical networks in a single physical system. For this purpose, the NR system is designed to support services (e.g., eMBB, mctc, and URLLC) having various requirements by performing/modifying analog/hybrid beamforming operations, etc., taking into consideration various OFDM parameter sets (e.g., OFDM symbol duration, subcarrier spacing (SCS), and CP length), a wide operating frequency range (up to about 50 GHz), and characteristics of a high frequency band.
In Rel-17, the need for developing higher NR (i.e., high Frequency (HF) NR) systems operating in the high frequency band (e.g., 60 to 70GHz or more) than conventional Rel-15/16 based systems is considered. The introduction and application of new OFDM parameter sets based on SCS (e.g., 240KHz, 480KHz or 960 KHz) that are larger than those defined in 3gpp TS 38.211 (e.g., parameter sets such as 15KHz, 30KHz, 60KHz and 120 KHz) of conventional NR may be considered in view of higher frequencies and wider bandwidths than conventional NR, and radio channel characteristics such as greater phase noise and/or greater doppler shift caused by high frequency bands.
When a larger SCS is used in an HF NR system, the OFDM symbol duration and slot duration are shortened as much as possible (e.g., when the SCS is increased N times in the frequency domain, the symbol duration and/or slot duration is reduced to 1/N in the time domain). Thus, a cell plan that reduces cell coverage as much as possible may be considered. However, in other cases (e.g., when the (target) cell coverage is maintained to correspond to a legacy NR level or when the SCS of the system is increased from a legacy NR SCS to a large SCS for HF NR, but the (target) cell coverage is not reduced, inversely proportional to the SCS increase), there may be a need for supplementing the coverage for physical channel/signal transmission (e.g., an extended/supplemental coverage scheme in processing the physical channel/signal such that the DL physical channel/signal may reach UEs at the edge/boundary of the target cell coverage or UL physical channel/signal transmitted from UEs located at the edge/boundary of the target cell coverage reaches the BS). In addition, since the use of a large SCS of CP length is reduced as much as possible, it is necessary to consider the effects of delay spread and/or phase noise of a radio channel, and/or beam switching time.
The term "beam" may be replaced by a (beamformed) signal/channel/resource transmitted over a corresponding beam. For example, the index of a beam may be generically represented as an index of the signal/channel/resource corresponding to the beam. Alternatively, the term "beam" is replaced with a signal/channel/resource associated with the beam and the beam is identified accordingly. When a different Tx beam is configured for each RO, the BS may identify the Tx beam used by the UE by an RO index or an SSB index associated with the RO.
Further, when OFDM symbols and slot durations are reduced due to the use of a large SCS as described above, a transmission/reception operation (e.g., PDCCH monitoring) to be performed by the UE in one symbol/slot duration requires fast processing, and the introduction of a multi-TTI scheduling scheme, which simultaneously schedules multiple multiplexed PDSCH (e.g., at least part of PDSCH is time division multiplexed) through one DCI, may be considered in consideration of UE processing burden (associated with a PDCCH monitoring period). For example, a frequency band available for multiple PDSCH scheduled by one DL DCI may include 120kHz, 480kHz, and/or 960kHz, but the frequency band is not limited thereto.
The meaning of the terms used herein is summarized as follows. To aid in understanding the terminology, fig. 5/6 and the description thereof may be referred to.
-K0 (DL assigned to PDSCH offset): the slot spacing between a DCI transmission slot and a PDSCH transmission slot (scheduled by the corresponding DCI).
-SLIV (start and length indicator values): information about the starting symbol and symbol duration (or ending symbol) of PDSCH (PDSCH occasion).
-Mapping type: information indicating whether the position of DMRS symbols of PDSCH is determined based on symbol index within the slot duration or based on symbol index within the PDSCH duration.
-TDRA (time domain resource assignment) table: including a plurality of K0, SLIV, map type combinations (configured by RRC) (at least one combination is mapped to each of a plurality of rows in the table). The specific row is indicated by DCI.
-K1 (PDSCH-to-harq_feedback timing indicator): the slot spacing between PDSCH transmission slots and HARQ-ACK transmission slots (for corresponding PDSCH reception).
To schedule multiple PDSCH in one DCI, each row of the TDRA table (e.g., higher layer parameters PDSCH-TimeDomainResourceAllocationListForMultiPDSCH) for a UE may include one or more combinations of K0, SLIV, map types. For example, referring to fig. 8, three combinations of { K0, SLIV, map types } may be configured for row K of the TDRA table, and two combinations of { K0, SLIV, map types } may be configured for row k+1. If the row index indicated by TDRA field in dci=k, a total of three PDSCH (pdsch#1, pdsch#2, and pdsch#3) may be scheduled to the UE. In row K of TDRA table, three combinations of { K0, SLIV, mapping type } may be associated with three PDSCH (pdsch#1, pdsch#2, and pdsch#3), respectively.
Hereinafter, configuration and signaling/application of multi-TTI (scheduling) DCI field information for simultaneously scheduling a plurality of PDSCH (each carrying one or more individual TBs) will be described.
(1) Configuration of New Data Indicator (NDI) fields/information
1) Option 1
A. When the maximum number of TBs that can be transmitted on one PDSCH is set to 2 (e.g., when higher layer parameters maxNrofCodeWordsScheduledByDCI are configured such that transmission of (up to) two TBs on one PDSCH is allowed), 1) a specific 1-bit (e.g., TB-specific) NDI field may be configured/indicated for each TB (of each PDSCH) for PDSCH scheduled by the multi-TTI DCI, or 2) a common 1-bit (e.g., TB common) NDI field applied to two (transportable) TBs may be configured/indicated for each PDSCH for the corresponding PDSCH. As a specific example, the following may be configured by RRC: 1) For PDSCH scheduled by multiple TTIs, whether a specific 1-bit (e.g., TB-specific) NDI field may be configured/indicated for each TB (of each PDSCH); or 2) for the respective PDSCH, a common 1-bit (e.g., TB common) NDI field that applies to two (transportable) TBs may be configured/indicated for each PDSCH.
B. For example, referring to fig. 8, for PDSCH scheduled by one DCI, a 1-bit NDI may be configured/indicated separately for each TB (of each PDSCH). When the maximum number of TBs that can be transmitted on one PDSCH is set to 2 (e.g., when higher layer parameters maxNrofCodeWordsScheduledByDCI are configured such that transmission of (up to) two TBs on one PDSCH is allowed), the following fields may be provided for TB 2: a second Modulation and Coding Scheme (MCS) field, a second NDI field, and a second Redundancy Version (RV) field. The first NDI field may include a total of N NDI bits. The size 'N' of the first NDI field may be determined based on the row in TDRA table having the most combinations of { K0, SLIV, mapping type }. In other words, if TDRA tables are configured such that up to N PDSCH can be simultaneously scheduled by one DCI, the first NDI field may include N NDI bits to cover up to N PDSCH. Of the total N NDI bits of the first NDI field, the nth NDI bit, denoted as B n-1, may be NDI for TB1 of pdsch#n (e.g., B n-1 indicates whether TB1 is a new transmission TB or a retransmission TB). Similarly, of the total N NDI bits of the second NDI field, the nth NDI bit, denoted as B n-1, may be NDI for TB2 of pdsch#n (e.g., B n-1 indicates whether TB2 is a new transmission TB or a retransmission TB).
2) Option 2
A. When the maximum number of TBs that can be transmitted on one PDSCH is set to 2 (e.g., when higher layer parameters maxNrofCodeWordsScheduledByDCI are configured such that transmission of (up to) two TBs on one PDSCH is allowed), if fewer than K PDSCH are scheduled by the multi TTIDCI, a TB-specific NDI field may be configured/indicated for each TB for the corresponding PDSCH. If more than K PDSCH are scheduled by the multiple TTIDCI, the following can be configured by RRC: 1) Whether to configure/indicate a TB-specific NDI field for each TB (of each PDSCH) of the corresponding PDSCH; or 2) whether the TB common NDI field is configured/indicated for each PDSCH of the corresponding PDSCH.
B. Regarding the value of K, for example, k=1 or k=n/2. Alternatively, the K value may be configured by RRC.
3) Annotating
A. In all options, the number of PDSCH may mean the number of valid PDSCH actually transmitted, excluding invalid PDSCH that is not transmitted due to overlapping in time with a particular UL symbol (e.g., semi-statically configured UL symbol), or the total number of PDSCH indicated by the multiple TTIDCI, regardless of actual transmission.
B. When the above options are applied, an increase in the number of NDI fields/bits configured in the multiple TTIDCI may be minimized, thereby reducing DCI overhead.
(2) Configuration of RV field/information
1) Option 1
A. When the maximum number of TBs that can be transmitted on one PDSCH is set to 2, if fewer than K PDSCHs are scheduled by TTIDCI more, one 2-bit RV field may be configured/indicated for each PDSCH (that is, two TBs transmitted on one PDSCH may be scheduled based on the same 2-bit RV value). If more than K PDSCH are scheduled by the multiple TTIDCI, one 1-bit RV field may be configured/indicated for each PDSCH (that is, two TBs transmitted on one PDSCH may be scheduled based on the same 1-bit RV value).
B. Regarding the value of K, for example, k=1 or k=n/2. Alternatively, the K value may be configured by RRC.
2) Option 2
A. When the maximum number of TBs that can be transmitted on one PDSCH is set to 2, the following can be configured by RRC: 1) For PDSCH scheduled by multiple TTIDCI, whether a specific (e.g., TB-specific) RV field is configured/indicated for each TB (per PDSCH) (i.e., two RV fields are configured/indicated for each PDSCH); or 2) whether a common (e.g., TB common) RV field is configured/indicated for each PDSCH (i.e., whether two TBs transmitted on one PDSCH are scheduled based on the same RV value) for the corresponding PDSCH.
3) Option 3
A. When the maximum number of TBs that can be transmitted on one PDSCH is set to 2, if fewer than K PDSCHs are scheduled by the multiple TTIDCI, a TB-specific RV field may be configured/indicated for each TB. If more than K PDSCH are scheduled by the multiple TTIDCI, the following can be configured by RRC: 1) For the corresponding PDSCHS, whether a TB-specific RV field is configured/indicated for each TB (of each PDSCH); or 2) for a corresponding PDSCHS, whether a TB common RV field is configured/indicated for each PDSCH.
B. regarding the value of K, for example, k=1 or k=n/2. Alternatively, the K value may be configured by RRC.
4) Option 4
A. When the maximum number of TBs that can be transmitted on one PDSCH is set to 2, if the maximum number of N PDSCHs can be scheduled by a single multi TTIDCI, the total number of NDI bits and RV bits configured/indicated by the corresponding DCI may be configured to be always less than or equal to o_max. When M (<=n) PDSCH is actually scheduled by the multiple TTIDCI, 1) if Mx2 (NDI for 1 bit per TB) +mx4 (RV for 2 bits per TB) <=o_max, 2 bits RV may be configured/indicated for each TB (per PDSCH) for M PDSCH. 2) If mx2+mx4> o_max, a 1-bit RV may be configured/indicated for each TB (of each PDSCH) for the M PDSCHs. Alternatively, a 2-bit TB common RV may be configured/indicated for each PDSCH, or a 1-bit TB common RV may be configured/indicated for each PDSCH.
B. Regarding the above o_max, o_max may be a multiple of N, for example, o_max=3n. Alternatively, the o_max value may be configured by RRC.
5) Annotating
A. In all options, the number of PDSCH may mean the number of valid PDSCH actually transmitted, excluding invalid PDSCH that is not transmitted due to overlapping in time with a particular UL symbol (e.g., semi-statically configured UL symbol), or the total number of PDSCH indicated by the multiple TTIDCI, regardless of actual transmission.
B. When the above options are applied, an increase in the number of RV fields/bits configured in the multiple TTIDCI may be minimized, thereby reducing DCI overhead.
(2-A) TB disable operation
1) Problem conditions
A. In the case of single TTI scheduling (where only one PDSCH (e.g., single TTIDCI) is scheduled by one DCI), when the maximum number of TBs that can be transmitted on one PDSCH is set to 2 (e.g., when higher layer parameters maxNrofCodeWordsScheduledByDCI are configured such that transmission of two TBs on one PDSCH is allowed), if a combination of a specific MCS index (e.g., 26) and a specific RV index (i.e., RV ID) (e.g., 1) is indicated by DCI, an operation of disabling transmission/reception of specific TB transmission/reception is defined.
B. When multiple PDSCH are scheduled by one more TTIDCI (to reduce DCI overhead), a structure of configuring/indicating 1-bit RV field/information per TB by DCI may be considered. In addition to RV index 1 (which is not often used), a corresponding 1-bit RV field may indicate one of two specific RV indexes including RV index 0 (e.g., RV index 0 and X, where X may be 2 or 3). For example, referring to fig. 8, a specific 1-bit RV may be configured/indicated for each TB (of each PDSCH) for a PDSCH scheduled by one DCI. When the maximum number of TBs that can be transmitted on one PDSCH is set to 2 (e.g., when higher layer parameters maxNrofCodeWordsScheduledByDCI are configured such that transmission of two TBs on one PDSCH (up to) is allowed), the following fields may be provided for TB 2: a second MCS field, a second NDI field, and a second RV field. The first RV field may include a total of N bits. The size 'N' of the first RV field may be determined based on the row in TDRA table having the most { K0, SLIV, mapping type } combination. In other words, if TDRA tables are configured such that up to N PDSCH can be simultaneously scheduled by one DCI, the first RV field may include N RV bits to cover up to N PDSCH. Of the total N RV bits of the 1 st RV field, the nth bit, denoted as B n-1, may be the RV of TB1 for pdsch#n (e.g., B n-1 indicates whether the RV index is TB 0 or RV 2). Similarly, the nth bit, denoted as B n-1, of the N total RV bits of the second RV field, may be the RV of TB2 for pdsch#n (e.g., B n-1 indicates whether the RV index of TB2 is RV0 or RV 2). C. Thus, when the maximum number of TBs that can be transmitted on one PDSCH is set to 2 (e.g., when 2 TBs of transmissions are scheduled by one PDSCH), if multiple PDSCH are scheduled simultaneously by multiple TTIDCI, then consideration must be given to how to instruct/define the TB disable operation.
2) Proposed method
A. Option 1
I. when multiple PDSCH are scheduled by multiple TTIDCI, if a combination of a specific MCS index (e.g., 26) and RV index (e.g., x=2 or 3) is indicated by the corresponding DCI, a TB disable operation to be performed may be defined.
On the other hand, when only one PDSCH is scheduled by the multiple TTIDCI, a 2-bit RV field/information may be configured/indicated for each TB (as in the current single TTIDCI). In this case, if a combination of a specific MCS index (e.g., 26) and RV index 1 is indicated by corresponding DCI, a TB disable operation may be performed.
B. Option 2
I. When multiple PDSCH are scheduled by multiple TTIDCI, if a specific MCS index (e.g., 26) is indicated by DCI, and if RV indexes (associated with specific TBs) for all scheduled PDSCH are indicated as Z (here, Z is X or 0), it may be defined to perform TB disable operation for all corresponding PDSCH. For example, referring to fig. 9, three PDSCH are scheduled by DCI. When a specific MCS index (e.g., MCS 26) is indicated by the first MCS field for TB1, if RV index Z (e.g., RV 2) is indicated by the first RV field for TB1 for all three TBs, TB1 may be disabled for all three PDSCH. In fig. 9, it is assumed that the maximum number of TBs that can be transmitted on one PDSCH is set to 2 (e.g., it is assumed that higher layer parameters maxNrofCodeWordsScheduledByDCI are configured such that transmission of (up to) two TBs on one PDSCH is allowed). In fig. 9, even when RV index Z (e.g., RV 2) is indicated for all three TBs 2 of the three PDSCH by the second RV field for TB2, if the second MCS field for TB2 does not indicate a specific MCS index (e.g., MCS 26), TB2 may be enabled for all three PDSCH. Meanwhile, the RV bits for which RV index Z is indicated for TB disable may be RV bits associated with the (actually) "scheduled" PDSCH. For example, referring to fig. 10, assume the following: the maximum number of TBs that can be transmitted on one PDSCH is set to 2 (e.g., higher layer parameters maxNrofCodeWordsScheduledByDCI are configured such that transmission of (up to) two TBs on one PDSCH is allowed). In addition, it is also assumed that TDRA tables are configured such that, until after N PDSCHs can be scheduled by DCI, DCI received on PDCCH actually schedules three PDSCHs. When a particular MCS index (e.g., MCS 26) is indicated by the second MCS field for TB2, and when RV index Z (e.g., RV 2) is indicated by the second RV field for TB2 for all three TBs, TB2 may be disabled for all three PDSCH. Referring to fig. 10, when three RV bits of the second RV field: when B0, B1, and B2 indicate RV index Z (e.g., RV 2), TB2 may be disabled for all scheduled PDSCHs based on the particular MCS index indicated by the second MCS field (e.g., MCS 26), regardless of the remaining N-3 RV bits (e.g., RV bits for the N-3 PDSCHs that are not actually scheduled).
Even when an MCS index (e.g., 26) is indicated by the multiple TTIDCI, if an RV index (associated with a specific TB) is indicated as a value other than Z for at least one scheduled PDSCH, each of the plurality of PDSCH/TBs may be transmitted/received by directly applying the MCS index and the RV index indicated by the corresponding DCI (without performing the above TB disable operation). For example, referring to fig. 10, when a specific MCS index (e.g., MCS 26) is indicated by a first MCS field of TB1 for three PDSCHs scheduled by one DCI, TB1 may be enabled for all three PDSCHs when RV index Z (e.g., RV 2) is indicated by the first RV field for TB1 only for some of the three RV bits of the three PDSCHs and when RV index Z (e.g., RV 2) is not indicated for the remaining RV bits. Specifically, in fig. 10, TB1 on pdsch#1 may be transmitted based on MCS26 and RV2, TB1 on pdsch#2 may be transmitted based on MCS26 and RV0, and TB1 on pdsch#3 may be transmitted based on MCS26 and RV 2.
An advantage of uniformly enabling/disabling TB1 (or TB 2) for all scheduled PDSCH is that the complexity of UE implementation/operation is simplified. Even if TB1 (or TB 2) is enabled/disabled uniformly for all scheduled PDSCH, system inefficiency/performance degradation may not be significant. The reason is that for FR2-2 bands (where multi PDSCH scheduling is performed), since a large SCS such as 480K/960K is used, the duration spanned by multiple PDSCHs simultaneously scheduled by a single DCI is short, and as a result, the reception success/failure result for a specific TB index with a high probability is expected to be the same throughout multiple PDSCHs (at the time of previous transmission). In other words, since the result of receiving a specific TB index for all the multiple PDSCH will be the same in probability, even if TB1 (or TB 2) is uniformly enabled/disabled for all scheduled PDSCH, UE implementation/operation complexity can be reduced without significant performance degradation.
C. option 3
I. When multiple PDSCH are scheduled by multiple TTIDCI and a specific MCS index (e.g., 26) is indicated by DCI, one of two specific RV indexes including RV index 1 (e.g., RV index 1 and RV index Y, where Y may be 0, 2, or 3) may be indicated by a 1-bit RV field for each TB.
On the other hand, when multiple PDSCH are scheduled by the multiple TTIDCI and MCS indexes other than a specific MCS index (e.g., 26) are indicated, one of RV index 0 and RV index X may be indicated by a 1-bit RV field for each TB.
D. Option 4
I. If the number of PDSCHs scheduled by the multiple TTIDCI is less than the maximum number of PDSCHs configured (or scheduled) by the corresponding DCI, whether to perform/apply the TB disable operation may be indicated by a specific bit (e.g., remaining bits not used in a field configuration such as MCS/NDI/RV) in the corresponding DCI.
On the other hand, if the number of PDSCH scheduled by the multiple TTIDCI is equal to the maximum number of PDSCH configured (or scheduled) by the corresponding DCI, the TB disable operation may not be allowed.
(3) Configuration of MCS field/information
1) Option 1
A. when the maximum number of TBs that can be transmitted on one PDSCH is set to 2, if PDSCH scheduled by more TTIDCI is less than K, then up to two TBs can be transmitted for each PDSCH (in this case, two MCS fields are configured/indicated for PDSCH scheduled by DCI, that is, MCS fields are configured/indicated for two TBs (indexes) that can be transmitted on the corresponding PDSCH.) if more than K PDSCH is scheduled by more TTIDCI, only one TB can be transmitted for each PDSCH (in this case, only one MCS field is configured/indicated for PDSCH scheduled by DCI, that is, one MCS field is configured/indicated for one TB (index) that can be transmitted on the corresponding PDSCH)
B. regarding the value of K, for example, k=1 or k=n/2. Alternatively, the K value may be configured by RRC.
2) Option 2
A. When the maximum number of TBs that can be transmitted on one PDSCH is set to 2, if scheduled by more TTIDCI by fewer than K PDSCHs, two MCS fields may be configured/indicated for the corresponding PDSCH (that is, a specific (e.g., TB-specific) MCS field applied to each of two TBs (indexes) that can be transmitted on the corresponding PDSCH is configured/indicated). On the other hand, if more than K PDSCHs are scheduled by the multi-TTI DCI, only one MCS field may be configured/indicated for the corresponding PDSCH (that is, only one common (e.g., TB common) MCS field applied to two TBs (indexes) that can be transmitted on each corresponding PDSCH is configured/indicated).
B. Regarding the value of K, for example, k=1 or k=n/2. Alternatively, the K value may be configured by RRC. For example, referring to fig. 8, 9, or 10, when the maximum number of TBs that can be transmitted on one PDSCH is set to 2 through the higher layer parameter maxNrofCodeWordsScheduledByDCI and scheduling of up to N PDSCH in one DCI is configured through the higher layer parameter PDSCH-TimeDomainResourceAllocationListForMultiPDSCH, if M PDSCH (where M is an integer greater than or equal to 1 and less than or equal to N) are scheduled by the DCI, the first MCS field may be commonly applied to TB1 of the M scheduled PDSCH and the second MCS field may be commonly applied to TB2 of the M scheduled PDSCH.
3) Option 3
A. When the maximum number of TBs that can be transmitted on one PDSCH is set to 2, the following may be configured by RRC: 1) For PDSCH scheduled by multiple TTIDCI, whether to configure/indicate two TB-specific MCS fields; or 2) whether only one TB-common MCS field is configured/indicated for the corresponding PDSCH.
4) Option 4
A. When the maximum number of TBs that can be transmitted on one PDSCH is set to 2, if fewer than K PDSCHs are scheduled by TTIDCI more, the TB-specific MCS field is configured/indicated for the corresponding PDSCH. If more than K PDSCH are scheduled by the multiple TTIDCI searches, the following may be configured by RRC: 1) For the corresponding PDSCH, two TB-specific MCS fields are configured/indicated; or 2) whether only one TB-common MCS field is configured/indicated for the corresponding PDSCH.
B. regarding the value of K, for example, k=1 or k=n/2. Alternatively, the K value may be configured by RRC.
5) Option 5
A. When the maximum number of TBs that can be transmitted on one PDSCH is set to 2, for the first TB index of PDSCH scheduled by multiple TTIDCI, an M-bit (e.g., full) MCS field (having the same size as the current single TTIDCI) may be configured/indicated. For the second TB index, an L-bit (e.g., delta) MCS field (having a size less than M bits) may be configured/indicated. In this case, an offset with respect to an MCS index (e.g., a first MCS index) indicated by an M-bit MCS field (applied to the first TB index) may be indicated by a corresponding L-bit MCS field. The MCS index determined by adding the corresponding offset to the first MCS index may be applied to the second TB index.
6) Option 6
A. When the maximum number of TBs that can be transmitted on one PDSCH is set to 2, if fewer than K PDSCHs are scheduled by TTIDCI more, a full MCS field may be configured/indicated for each of the first and second TB indices of the PDSCHs. If more than K PDSCHs are scheduled by the multiple TTIDCI, the full MCS field may be configured/indicated for a first TB index for the corresponding PDSCH and the delta MCS field may be configured/indicated for a second TB index.
B. regarding the value of K, for example, k=1 or k=n/2. Alternatively, the K value may be configured by RRC.
7) Option 7
A. When the maximum number of TBs that can be transmitted on one PDSCH is set to 2, the following may be configured by RRC: 1) Whether to configure/indicate a full MCS field for a second TB index of a PDSCH scheduled by multiple TTIDCI; or 2) whether to configure/indicate the delta MCS field for the second TB index of the corresponding PDSCH.
8) Option 8
A. when the maximum number of TBs that can be transmitted on one PDSCH is set to 2, if less than K PDSCHs are scheduled by TTIDCI more, the full MCS field may be configured/indicated for each of the first and second TB indexes of the PDSCH. On the other hand, if more than K PDSCH are scheduled by the multiple TTIDCI, the following may be configured by RRC: 1) Whether to configure/indicate a full MCS field for a second TB index of a corresponding PDSCH; or 2) whether to configure/indicate the delta MCS field for the second TB index of the corresponding PDSCH.
B. regarding the value of K, for example, k=1 or k=n/2. Alternatively, the K value may be configured by RRC.
9) Annotating
A. In all options, the number of PDSCH may mean the number of valid PDSCH actually transmitted, excluding invalid PDSCH that is not transmitted due to overlapping in time with a particular UL symbol (e.g., semi-statically configured UL symbol), or the total number of PDSCH indicated by the multiple TTIDCI, regardless of actual transmission.
B. When the above options are applied, an increase in the number of MCS fields/bits configured in the multiple TTIDCI may be minimized, thereby reducing DCI overhead.
The differences between the various DCI field configuration methods/options described above are for ease of explanation. Two or more configuration methods/options may be combined, or each method/option may be implemented independently
Fig. 11 is a diagram for explaining multi-TTI/PDSCH scheduling according to an embodiment of the present disclosure. Fig. 11 is exemplary, and the present disclosure is not limited thereto.
Referring to fig. 11, the ue may receive information from the BS through higher layer signaling (V320). For example, configuration information related to multi TTIPDSCH scheduling, configuration information related to multi TTIPDSCH HARQ-ACK feedback, etc. may be received through higher layer signaling. For example, higher layer parameters (or tables) related to values indicated by the status of at least one of fields (1) through (8) in the DCI may be configured.
The UE may receive DCI (single PDCCH signal) (V330). The UE may perform blind detection for DCI scheduling the multi TTIPDSCH based on information through higher layer signaling.
The BS may transmit a plurality of scheduled PDSCH through one DCI transmission (V335). The UE may receive TTIPDSCH more based on the DCI. For example, the multiple TTIPDSCH may be received based on a state of at least one field from among fields (1) to (8) in the DCI.
The UE may generate/determine HARQ-ACKs (V337) for the received PDSCH (all or at least part of the PDSCH). The HARQ-ACK may be generated based on a particular codebook. The UE may refer to this information for HARQ-ACK generation/determination through higher layer signaling and/or DCI.
The UE may transmit HARQ-ACK for PDSCH (V338). HARQ-ACK transmission resources (time resources, timing, etc.) may be determined based on the DCI.
Fig. 12 illustrates a method of receiving a signal by a UE thereof in a wireless communication system according to an embodiment of the present disclosure. Fig. 12 is exemplary, and the present disclosure is not limited thereto.
Referring to fig. 12, a ue may receive DCI (a 05) for scheduling N PDSCHs through a single PDCCH.
The UE may receive N PDSCH (a 10) based on the DCI.
The DCI may include (i) a first MCS field for a first TB of N PDSCH and (ii) a first RV field including N bits, each bit indicating an RV for each of the first TBs of N PDSCH. Based on the first MCS field of the first TB for the N PDSCH being set to a specific MCS and N bits included in the first RV field for the first TB of the N PDSCH being all set to a specific RV, the UE may determine to disable all the first TBs for all the N PDSCH.
The index of the specific MCS may be 26 and the index of the specific RV may be 2.
Based on the first MCS field of the first TBs for the N PDSCHs being set to a specific MCS and only a part of N bits included in the first RV field being set to a specific RV, the UE may determine to enable all the first TBs for all the N PDSCHs.
The maximum number of TBs that can be received through one PDSCH may be set to 2. The DCI may further include (iii) a second MCS field for a second TB of the N PDSCH, and (iv) a second RV field including N bits, each bit indicating an RV for each of the second TBs of the N PDSCH.
Based on the second MCS field of the second TB for the N PDSCH being set to a specific MCS and all N bits included in the second RV field of the second TB for the N PDSCH being set to only a specific RV, the UE may determine to disable all the second TBs for all the N PDSCH.
Based on the first MCS field being set to a specific MCS and N bits among all bits of the first RV field being all set to only a specific RV, the UE may determine that all first TBs are disabled for all N PDSCH.
Each of the N bits included in the first RV field may indicate RV0 or RV2 for the first TB of the related PDSCH.
The UE may receive configuration information related to multi-PDSCH scheduling through higher layer signaling (e.g., V320 in fig. 11). Higher layer signaling may include TDRA tables, which TDRA tables include multiple combinations of { K0, SLIV, mapping types }. In each combination of { K0, SLIV, mapping type }, the 'K0' may represent a slot offset from a slot of the related DCI to a slot of the related PDSCH, the 'SLIV' may represent a start symbol of the related PDSCH and a symbol duration of the related PDSCH, and the 'mapping type' may be information for determining a position of a DMRS symbol of the related PDSCH. The DCI may indicate one row of TDRA tables.
The DCI may further include a first NDI field including N bits.
Fig. 13 illustrates a method of signaling a signal through a BS thereof in a wireless communication system according to an embodiment of the present disclosure. Fig. 13 is exemplary, and the present disclosure is not limited thereto.
Referring to fig. 13, the bs may generate DCI (B05) for scheduling N PDSCH.
The BS may transmit DCI (B10) through a single PDCCH.
The BS may transmit N PDSCH (B15) scheduled by DCI.
The DCI may include (i) a first MCS field for a first TB of N PDSCH and (ii) a first RV field including N bits, each bit indicating an RV for each of the first TBs of N PDSCH. The BS may inform the UE to disable all first TBs for all N PDSCH by setting a first MCS field of the first TB for N PDSCH to a specific MCS and setting all N bits included in a first RV field of the first TB for N PDSCH to only a specific RV.
The index of the specific MCS may be 26 and the index of the specific RV may be 2.
When the first MCS field of the first TB for the N PDSCHs is set to a specific MCS and when only a part of the N bits included in the first RV field is set to a specific RV, all the first TBs may be enabled for all the N PDSCHs.
The maximum number of TBs that can be received through one PDSCH may be set to 2. The DCI may further include (iii) a second MCS field for a second TB of the N PDSCH, and (iv) a second RV field including N bits, each bit indicating an RV for each of the second TBs of the N PDSCH.
By setting the second MCS field of the second TB for the N PDSCHs to a specific MCS and setting all N bits included in the second RV field of the second TB for the N PDSCHs to only a specific RV, the BS may inform the UE that all the second TBs are disabled for all the N PDSCHs.
By setting the first MCS field to a specific MCS and setting all N bits among all bits of the first RV field to only a specific RV, the BS may inform the UE that all first TBs are disabled for all N PDSCH.
Each of the N bits included in the first RV field may indicate RV0 or RV2 of the first TB of the associated PDSCH.
The BS may transmit configuration information related to the multi-PDSCH scheduling through higher layer signaling (e.g., V320 in fig. 11). Higher layer signaling may include TDRA tables, which TDRA tables include multiple combinations of { K0, SLIV, mapping types }. In each combination of { K0, SLIV, mapping type }, the 'K0' may represent a slot offset from a slot of the related DCI to a slot of the related PDSCH, the 'SLIV' may represent a start symbol of the related PDSCH and a symbol duration of the related PDSCH, and the 'mapping type' may be information for determining a position of a DMRS symbol of the related PDSCH. The DCI may indicate one row of TDRA tables.
The DCI may further include a first NDI field including N bits.
For convenience of description, the present disclosure has focused on DL grant DCI based multi-PDSCH scheduling. However, it should be understood by those skilled in the art that the multi-TTI scheduling method according to the present disclosure is not limited to DL, and is applicable to multi-PUSCH scheduling based on UL grant DCI. For example, the multi-TTI scheduling DCI may refer to at least one of a multi-PDSCH scheduling DCI (which schedules a plurality of PUSCHs multiplexed in a time domain) and a multi-PUSCH scheduling DCI (which schedules a plurality of PUSCHs multiplexed in a time domain).
Fig. 14 illustrates a communication system 1 applied to the present disclosure.
Referring to fig. 14, a communication system 1 applied to the present disclosure includes a wireless device, a Base Station (BS), and a network. Herein, a wireless device refers to a device that performs communication using a Radio Access Technology (RAT) (e.g., 5G New RAT (NR) or Long Term Evolution (LTE)) and may be referred to as a communication/radio/5G device. 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. 15 illustrates a wireless device suitable for use in the present disclosure.
Referring to fig. 15, 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. 14.
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. 16 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. 14).
Referring to fig. 16, wireless devices 100 and 200 may correspond to wireless devices 100 and 200 of fig. 15 and may be configured by various elements, assemblies, 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. 15. For example, transceiver 114 may include one or more transceivers 106 and 206 and/or one or more antennas 108 and 208 of fig. 15. The control unit 120 is electrically connected to the communication unit 110, the memory 130, and the additional components 140, and controls the overall operation of the wireless device. For example, the control unit 120 may control the electrical/mechanical operation of the wireless device based on 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. 14), a vehicle (100 b-1 and 100b-2 of fig. 14), an XR device (100 c of fig. 14), a handheld device (100 d of fig. 14), a home appliance (100 e of fig. 14), an IoT device (100 f of fig. 14), 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. 14), a BS (200 of fig. 14), a network node, etc. The wireless device may be used in a mobile or stationary location depending on the use case/service.
In fig. 16, 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. 17 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. 17, 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. 16.
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. 18 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. 18, 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 6 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, as shown in fig. 5.
TABLE 6
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 receiving a signal by a User Equipment (UE) in a wireless communication system, the method comprising:
Receiving Downlink Control Information (DCI) for scheduling N Physical Downlink Shared Channels (PDSCH) through a single Physical Downlink Control Channel (PDCCH); and
The N PDSCH is received based on the DCI,
Wherein the DCI includes (i) a first Modulation and Coding Scheme (MCS) field for a first Transport Block (TB) of the N PDSCHs, and (ii) a first Redundancy Version (RV) field including N bits, each bit indicating an RV for each of the first TB of the N PDSCHs, and
Wherein the UE determines that all the first TBs are disabled for all the N PDSCHs based on the first MCS field of the first TB for the N PDSCHs being set to a specific MCS and all the N bits included in the first RV field of the first TB for the N PDSCHs being set to only a specific RV.
2. The method of claim 1, wherein the index of the particular MCS is 26, and
Wherein the index of the specific RV is 2.
3. The method of claim 1, wherein the UE determines that all of the first TBs are enabled for all of the N PDSCHs based on the first MCS field of the first TB for the N PDSCHs being set to the particular MCS and only a portion of the N bits included in the first RV field being set to only the particular RV.
4. The method of claim 1, wherein a maximum number of TBs receivable on one PDSCH is set to 2, and
Wherein the DCI further includes (iii) a second MCS field for a second TB of the N PDSCH, and (iv) a second RV field including N bits, each bit indicating an RV for each of the second TBs of the N PDSCH.
5. The method of claim 4, wherein the UE determines that all of the second TBs are disabled for all of the N PDSCHs based on the second MCS field of the second TB for the N PDSCHs being set to the particular MCS and all of the N bits included in the second RV field of the second TB for the N PDSCHs being set to only a particular RV.
6. The method of claim 1, wherein the UE determines that all of the first TBs are disabled for all of the N PDSCHs based on the first MCS field being set to the particular MCS and the N bits of all of the bits of the first RV field being all set to only the particular RV.
7. The method of claim 1, wherein each of the N bits included in the first RV field indicates RV0 or RV2 for a first TB of a related PDSCH.
8. The method of claim 1, further comprising:
configuration information related to multi-PDSCH scheduling is received through higher layer signaling.
9. The method of claim 8, wherein the higher layer signaling comprises a Time Domain Resource Allocation (TDRA) table, the Time Domain Resource Allocation (TDRA) table comprising a plurality of combinations of { K0, SLIV, map types },
Wherein, in each combination of { K0, SLIV, mapping type }:
'K0' represents a slot offset from a slot of the related DCI to a slot of the related PDSCH;
'SLIV' denotes a start symbol of the related PDSCH and a symbol duration of the related PDSCH; and
The 'mapping type' is information for determining the position of demodulation reference signal (DMRS) symbols of the related PDSCH, and
Wherein the DCI indicates one row of the TDRA table.
10. The method of claim 1, wherein the DCI further comprises a first New Data Indicator (NDI) field comprising N bits, and
Wherein each of the N bits of the first NDI field is associated with each of the first TBs of the N PDSCH.
11. A computer-readable recording medium having recorded thereon a program for executing the method of claim 1.
12. An apparatus of wireless communication, the apparatus comprising:
a memory configured to store instructions; and
A processor configured to perform operations by executing the instructions,
Wherein the operations performed by the processor include:
Receiving Downlink Control Information (DCI) for scheduling N Physical Downlink Shared Channels (PDSCH) through a single Physical Downlink Control Channel (PDCCH); and
The N PDSCH is received based on the DCI,
Wherein the DCI includes (i) a first Modulation and Coding Scheme (MCS) field for a first Transport Block (TB) of the N PDSCHs, and (ii) a first Redundancy Version (RV) field including N bits, each bit indicating an RV for each of the first TB of the N PDSCHs, and
Wherein, based on the first MCS field of the first TB for the N PDSCH being set to a specific MCS and all of the N bits included in the first RV field of the first TB for the N PDSCH being set to a specific RV only, the processor is configured to determine that all of the first TBs are disabled for all of the N PDSCH.
13. The apparatus of claim 12, further comprising:
a transceiver configured to transmit or receive radio signals under control of the processor,
Wherein the device is a third generation partnership project (3 GPP) based User Equipment (UE).
14. A method of transmitting a signal by a Base Station (BS) in a wireless communication system, the method comprising:
Transmitting Downlink Control Information (DCI) for scheduling N Physical Downlink Shared Channels (PDSCH) through a single Physical Downlink Control Channel (PDCCH); and
The N PDSCH is transmitted based on the DCI,
Wherein the DCI includes (i) a first Modulation and Coding Scheme (MCS) field for a first Transport Block (TB) of the N PDSCHs, and (ii) a first Redundancy Version (RV) field including N bits, each bit indicating an RV for each of the first TB of the N PDSCHs, and
Wherein the BS informs a User Equipment (UE) that all the first TBs are disabled for all the N PDSCHs by setting the first MCS field of the first TB for the N PDSCHs to a specific MCS and setting all the N bits included in the first RV field of the first TB for the N PDSCHs to only a specific RV.
15. A Base Station (BS) for wireless communication, the BS comprising:
a memory configured to store instructions; and
A processor configured to perform operations by executing the instructions,
Wherein the operations performed by the processor include:
Transmitting Downlink Control Information (DCI) for scheduling N Physical Downlink Shared Channels (PDSCH) through a single Physical Downlink Control Channel (PDCCH); and
The N PDSCH is transmitted based on the DCI,
Wherein the DCI includes (i) a first Modulation and Coding Scheme (MCS) field for a first Transport Block (TB) of the N PDSCHs, and (ii) a first Redundancy Version (RV) field including N bits, each bit indicating an RV for each of the first TB of the N PDSCHs, and
Wherein by setting the first MCS field of the first TB for the N PDSCH to a specific MCS and setting all the N bits included in the first RV field of the first TB for the N PDSCH to only a specific RV, the processor is configured to inform a User Equipment (UE) that all the first TBs are disabled for all the N PDSCH.
Applications Claiming Priority (4)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| KR10-2021-0130204 | 2021-09-30 | ||
| KR20210133945 | 2021-10-08 | ||
| KR10-2021-0133945 | 2021-10-08 | ||
| PCT/KR2022/014618 WO2023055104A1 (en) | 2021-09-30 | 2022-09-29 | Method and device for transmitting and receiving signal in wireless communication system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN118020371A true CN118020371A (en) | 2024-05-10 |
Family
ID=90949052
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202280065325.0A Pending CN118020371A (en) | 2021-09-30 | 2022-09-29 | Method and apparatus for transmitting and receiving signal in wireless communication system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN118020371A (en) |
-
2022
- 2022-09-29 CN CN202280065325.0A patent/CN118020371A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112740590B (en) | Method and apparatus for transmitting and receiving wireless signal in wireless communication system | |
| CN112753184B (en) | Method for transmitting or receiving signal in wireless communication system supporting unlicensed band and apparatus supporting the same | |
| CN112740591B (en) | Method and apparatus for transmitting and receiving wireless signal in wireless communication system | |
| CN113796140B (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 | |
| US20220191899A1 (en) | Method for transmitting or receiving signals for multiple transport block scheduling, and apparatus therefor | |
| US11831445B2 (en) | Method and device for transmitting and receiving signal in wireless communication system | |
| CN112534943A (en) | Method and apparatus for transmitting and receiving wireless signal in wireless communication system | |
| US11864230B2 (en) | Method and apparatus for transmitting and receiving signal in wireless communication system | |
| CN114902602A (en) | Method and apparatus for transmitting and receiving signal in wireless communication system | |
| US20220232610A1 (en) | Method and apparatus for transmitting/receiving wireless signal in wireless communication system | |
| CN116114328A (en) | Method and apparatus for transmitting and receiving wireless signal in wireless communication system | |
| CN113796040B (en) | Method and apparatus for transmitting and receiving signal in wireless communication system | |
| US20220353943A1 (en) | Method and apparatus for transmitting and receiving radio signal in wireless communication system | |
| EP4050958A1 (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 | |
| CN115428573A (en) | Method and apparatus for transmitting and receiving wireless signal in wireless communication system | |
| EP4236558A1 (en) | Method and device 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 | |
| CN118020371A (en) | Method and apparatus for transmitting and receiving signal in wireless communication system | |
| US12003335B2 (en) | Method and device for transmitting and receiving signal in wireless communication system | |
| EP4236155A1 (en) | Method and device for transmitting and receiving signal in wireless communication system | |
| US20220330317A1 (en) | Method and apparatus for transmitting and receiving signal in wireless communication system | |
| EP4270845A1 (en) | Method and apparatus for transmitting and receiving signal in wireless communication system | |
| EP4072233A1 (en) | Method and device for signal transmission or reception in wireless communication system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination |