WO2022010132A1 - 집성된 캐리어들을 사용한 신호의 송수신 방법 및 장치 - Google Patents
집성된 캐리어들을 사용한 신호의 송수신 방법 및 장치 Download PDFInfo
- Publication number
- WO2022010132A1 WO2022010132A1 PCT/KR2021/007756 KR2021007756W WO2022010132A1 WO 2022010132 A1 WO2022010132 A1 WO 2022010132A1 KR 2021007756 W KR2021007756 W KR 2021007756W WO 2022010132 A1 WO2022010132 A1 WO 2022010132A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- search space
- cell
- space set
- dci
- dci format
- 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.)
- Ceased
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B17/00—Monitoring; Testing
- H04B17/30—Monitoring; Testing of propagation channels
- H04B17/309—Measuring or estimating channel quality parameters
- H04B17/318—Received signal strength
- H04B17/328—Reference signal received power [RSRP]; Reference signal received quality [RSRQ]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
- H04W72/232—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B17/00—Monitoring; Testing
- H04B17/20—Monitoring; Testing of receivers
- H04B17/24—Monitoring; Testing of receivers with feedback of measurements to the transmitter
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B17/00—Monitoring; Testing
- H04B17/30—Monitoring; Testing of propagation channels
- H04B17/373—Predicting channel quality or other radio frequency [RF] parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04J—MULTIPLEX COMMUNICATION
- H04J11/00—Orthogonal multiplex systems, e.g. using WALSH codes
- H04J11/0069—Cell search, i.e. determining cell identity [cell-ID]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
- H04L1/0036—Systems modifying transmission characteristics according to link quality, e.g. power backoff arrangements specific to the receiver
- H04L1/0038—Blind format detection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
- H04L1/0045—Arrangements at the receiver end
- H04L1/0046—Code rate detection or code type detection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
- H04L1/0072—Error control for data other than payload data, e.g. control data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/0078—Avoidance of errors by organising the transmitted data in a format specifically designed to deal with errors, e.g. location
- H04L1/0079—Formats for control data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1829—Arrangements specially adapted for the receiver end
- H04L1/1854—Scheduling and prioritising arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/0001—Arrangements for dividing the transmission path
- H04L5/0003—Two-dimensional division
- H04L5/0005—Time-frequency
- H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A) or DMT
- H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A) or DMT the frequencies being arranged in component carriers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0044—Allocation of payload; Allocation of data channels, e.g. PDSCH or PUSCH
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/0091—Signalling for the administration of the divided path, e.g. signalling of configuration information
- H04L5/0094—Indication of how sub-channels of the path are allocated
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/0091—Signalling for the administration of the divided path, e.g. signalling of configuration information
- H04L5/0096—Indication of changes in allocation
- H04L5/0098—Signalling of the activation or deactivation of component carriers, subcarriers or frequency bands
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
- H04W72/044—Wireless resource allocation based on the type of the allocated resource
- H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/12—Wireless traffic scheduling
- H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
- H04W72/1273—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of downlink data flows
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
- H04W72/231—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the layers above the physical layer, e.g. RRC or MAC-CE signalling
Definitions
- the present invention relates to a technology for transmitting and receiving a signal in a communication system, and more particularly, to a technology for transmitting and receiving a signal using aggregated carriers.
- the NR communication system may support a frequency band of 6 GHz or higher as well as a frequency band of 6 GHz or less, and may support various communication services and scenarios compared to the LTE communication system. For example, by constructing an NR communication system, usage scenarios such as enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communication (URLLC), and massive Machine Type Communication (mMTC) may be supported.
- eMBB enhanced Mobile BroadBand
- URLLC Ultra Reliable Low Latency Communication
- mMTC massive Machine Type Communication
- the communication system may support a carrier aggregation technology, and communication between the base station and the terminal may be performed using aggregated carriers. In this case, methods for efficiently performing downlink communication and/or uplink communication using aggregated carriers are needed.
- An object of the present invention for solving the above problems is to provide a method and apparatus for transmitting and receiving a signal using aggregated carriers in a communication system.
- a method of operating a terminal for achieving the above object includes the steps of receiving configuration information of a plurality of cells from a base station, configured in a first cell among the plurality of cells, and Receiving configuration information of a first search space set for scheduling from the base station, setting information of a second search space set for scheduling of the first cell set in a second cell among the plurality of cells from the base station receiving, performing a first monitoring operation on the first search space set and a second monitoring operation on the second search space set, thereby searching for one of the first search space set and the second search space set Receiving a DCI from the base station in a spatial set, and receiving a data channel from the base station based on the DCI in the first cell, wherein the first search space set and the second search space set include: It is a USS set.
- the first monitoring operation may include a blind decoding operation for PDCCH candidate(s) included in the first search space set
- the second monitoring operation may include PDCCH candidate(s) included in the second search space set.
- ) may include a blind decoding operation, and both the first monitoring operation and the second monitoring operation may be performed within a reference time.
- An upper limit value of the number of times of PDCCH blind decoding for scheduling of the first cell may be applied for each reference time, and the reference time may be applied to the first cell and the second cell according to subcarrier intervals applied to the first cell and the second cell. It may be determined as one slot of any one of the second cells.
- the data channel may be a PDSCH including unicast data.
- the method of operating the terminal may further include receiving, from the base station, configuration information of a third search space set configured in the first cell and for scheduling of the first cell, and monitoring operations are performed in the first cell. This may be performed on a search space set, the second search space set, and the third search space set, and the third search space set may be a CSS set.
- the first DCI format monitored in the first search space set so that the size of the first DCI format monitored in the first search space set and the size of the first DCI format monitored in the second search space set are aligned
- zero padding may be applied to the first DCI format monitored in the second search space set, and the DCI may be the first DCI format.
- the monitoring operation of the first DCI format may be configured by an RRC message from the base station, and the first DCI format may be DCI format 1_1 or DCI format 1_2.
- Whether one or more fields exist in the DCI may be determined according to a search space set or cell in which the DCI is received.
- the one or more fields may include a CIF.
- the first cell may be a primary cell
- the second cell may be a secondary cell
- the method of operating a base station according to a second embodiment of the present invention for achieving the above object includes transmitting configuration information of a plurality of cells to a terminal, configured in a first cell among the plurality of cells, and transmitting configuration information of a first search space set for scheduling to the terminal; setting information of a second search space set for scheduling of the first cell set in a second cell among the plurality of cells to the terminal transmitting; transmitting DCI to the terminal in one of the first search space set and the second search space set; and transmitting a data channel to the terminal based on the DCI in the first cell, wherein the first search space set and the second search space set are USS sets.
- the data channel may be a PDSCH including unicast data.
- the method of operating the base station may further include transmitting configuration information of a third search space set configured in the first cell for scheduling of the first cell to the terminal, wherein the DCI is the first cell.
- the search space set may be transmitted in one of the search space set, the second search space set, and the third search space set, and the third search space set may be a CSS set.
- the first DCI format to be monitored in the first search space set so that the size of the first DCI format to be monitored in the first search space set and the size of the first DCI format to be monitored in the second search space set are aligned
- zero padding may be applied to the first DCI format to be monitored in the second search space set, and the DCI may be the first DCI format.
- the monitoring operation of the first DCI format may be configured by an RRC message from the base station, and the first DCI format may be DCI format 1_1 or DCI format 1_2.
- Whether one or more fields exist in the DCI may be determined according to a search space set or cell in which the DCI is transmitted, and the one or more fields may include a CIF.
- the first cell may be a primary cell
- the second cell may be a secondary cell
- a terminal for achieving the above object includes a processor, a memory in electronic communication with the processor, and instructions stored in the memory, and when the instructions are executed by the processor, In the above commands, the terminal receives configuration information of a plurality of cells from the base station, is configured in a first cell among the plurality of cells, and transmits configuration information of a first search space set for scheduling of the first cell from the base station receiving, from the base station, configuration information of a second search space set configured in a second cell among the plurality of cells for scheduling of the first cell, and performing a first monitoring operation for the first search space set; Receive a DCI from the base station in one of the first search space set and the second search space set by performing a second monitoring operation on the second search space set, and in the first cell and cause to receive a data channel from the base station based on the DCI, wherein the first search space set and the second search space set are USS sets.
- Both the first monitoring operation and the second monitoring operation may be performed within a reference time period, and the reference time is determined according to a subcarrier interval applied to the first cell and the second cell. It may be determined as one slot of any one of the cells.
- the instructions may be operable to further cause the terminal to receive, from the base station, configuration information of a third search space set configured in the first cell and for scheduling of the first cell, wherein monitoring operations include The first search space set, the second search space set, and the third search space set are performed, and the third search space set may be CSS.
- the base station may set search space sets in a plurality of cells, transmit control information in one search space set among the search space sets, and transmit data based on the control information.
- the terminal may acquire control information by monitoring the search space sets set by the base station, and may receive data based on the control information. According to the above-described operation, downlink communication using aggregated carriers can be efficiently performed. Accordingly, the performance of the communication system can be improved.
- FIG. 1 is a conceptual diagram illustrating a communication system.
- FIG. 2 is a block diagram illustrating communication nodes constituting a communication system.
- FIG. 3 is a conceptual diagram illustrating a carrier aggregation method and a method of disposing the aggregated carriers.
- FIG. 4 is a conceptual diagram illustrating a mapping method of a search space set in cross-carrier scheduling according to (Method 100).
- FIG. 5 is a conceptual diagram illustrating a method of switching a bandwidth portion in cross-carrier scheduling according to (Method 100).
- FIG. 6 is a conceptual diagram illustrating a first application method of a PDSCH default QCL by a plurality of serving cells.
- FIG. 7 is a conceptual diagram illustrating a second application method of a PDSCH default QCL by a plurality of serving cells.
- FIG. 8 is a conceptual diagram illustrating a PDSCH scheduling method by a plurality of serving cells.
- first, second, etc. may be used to describe various elements, but the elements should not be limited by the terms. The above terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, a first component may be referred to as a second component, and similarly, a second component may also be referred to as a first component. and/or includes a combination of a plurality of related listed items or any of a plurality of related listed items.
- the communication system may be a 4G communication system (eg, a long-term evolution (LTE) communication system, an LTE-A communication system), a 5G communication system (eg, a new radio (NR) communication system), and the like.
- the 4G communication system may support communication in a frequency band of 6 GHz or less
- the 5G communication system may support communication in a frequency band of 6 GHz or more as well as a frequency band of 6 GHz or less.
- the communication system to which the embodiments according to the present invention are applied is not limited to the contents described below, and the embodiments according to the present invention can be applied to various communication systems.
- the communication system may be used in the same meaning as the communication network (network), and "LTE” may indicate “4G communication system”, “LTE communication system” or “LTE-A communication system”, and “NR” may indicate “5G communication system” or “NR communication system”.
- FIG. 1 is a conceptual diagram illustrating a first embodiment of a communication system.
- the communication system 100 is a plurality of communication nodes (110-1, 110-2, 110-3, 120-1, 120-2, 130-1, 130-2, 130-3, 130-4, 130-5, 130-6).
- the communication system 100 is a core network (core network) (eg, S-GW (serving-gateway), P-GW (packet data network (PDN)-gateway), MME (mobility management entity)) may include more.
- core network eg, S-GW (serving-gateway), P-GW (packet data network (PDN)-gateway), MME (mobility management entity)
- the core network is an access and mobility management function (AMF), a user plane function (UPF), a session management function (SMF), etc.
- AMF access and mobility management function
- UPF user plane function
- SMF session management function
- SMS session management function
- the plurality of communication nodes 110 to 130 may support a communication protocol (eg, an LTE communication protocol, an LTE-A communication protocol, an NR communication protocol, etc.) defined in a 3rd generation partnership project (3GPP) standard.
- a plurality of communication nodes 110 to 130 are CDMA (code division multiple access) technology, WCDMA (wideband CDMA) technology, TDMA (time division multiple access) technology, FDMA (frequency division multiple access) technology, OFDM (orthogonal frequency division) technology multiplexing) technology, Filtered OFDM technology, CP (cyclic prefix)-OFDM technology, DFT-s-OFDM (discrete Fourier transform-spread-OFDM) technology, OFDMA (orthogonal frequency division multiple access) technology, SC (single carrier)-FDMA Technology, Non-orthogonal Multiple Access (NOMA) technology, GFDM (generalized frequency division multiplexing) technology, FBMC (filter bank multi-carrier) technology, UFMC (universal filtered multi
- FIG. 2 is a block diagram showing a first embodiment of a communication node constituting a communication system.
- the communication node 200 may include at least one processor 210 , a memory 220 , and a transceiver 230 connected to a network to perform communication.
- the communication node 200 may further include an input interface device 240 , an output interface device 250 , a storage device 260 , and the like.
- Each of the components included in the communication node 200 may be connected by a bus 270 to communicate with each other.
- the processor 210 may execute a program command stored in at least one of the memory 220 and the storage device 260 .
- the processor 210 may refer to a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor on which methods according to embodiments of the present invention are performed.
- Each of the memory 220 and the storage device 260 may be configured as at least one of a volatile storage medium and a non-volatile storage medium.
- the memory 220 may be configured as at least one of a read only memory (ROM) and a random access memory (RAM).
- the communication system 100 includes a plurality of base stations 110 - 1 , 110 - 2 , 110 - 3 , 120 - 1 and 120 - 2 , and a plurality of terminals 130 - 1, 130-2, 130-3, 130-4, 130-5, 130-6).
- Each of the first base station 110-1, the second base station 110-2, and the third base station 110-3 may form a macro cell.
- Each of the fourth base station 120-1 and the fifth base station 120-2 may form a small cell.
- the fourth base station 120-1, the third terminal 130-3, and the fourth terminal 130-4 may belong to the cell coverage of the first base station 110-1.
- the second terminal 130-2, the fourth terminal 130-4, and the fifth terminal 130-5 may belong to the cell coverage of the second base station 110-2.
- the fifth base station 120-2, the fourth terminal 130-4, the fifth terminal 130-5, and the sixth terminal 130-6 may belong to the cell coverage of the third base station 110-3.
- the first terminal 130-1 may belong to the cell coverage of the fourth base station 120-1.
- the sixth terminal 130-6 may belong to the cell coverage of the fifth base station 120-2.
- each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 is a NodeB (NB), an evolved NodeB (eNB), gNB, an advanced base station (ABS), HR - BS (high reliability-base station), BTS (base transceiver station), radio base station (radio base station), radio transceiver (radio transceiver), access point (access point), access node (node), RAS (radio access station) ), MMR-BS (mobile multihop relay-base station), RS (relay station), ARS (advanced relay station), HR-RS (high reliability-relay station), HNB (home NodeB), HeNB (home eNodeB), It may be referred to as a road side unit (RSU), a radio remote head (RRH), a transmission point (TP), a transmission and reception point (TRP), and the like.
- RSU road side unit
- RRH radio remote head
- TP transmission point
- TRP transmission and
- Each of the plurality of terminals 130-1, 130-2, 130-3, 130-4, 130-5, 130-6 includes a user equipment (UE), a terminal equipment (TE), an advanced mobile station (AMS), HR-MS (high reliability-mobile station), terminal, access terminal, mobile terminal, station, subscriber station, mobile station, portable It may be referred to as a portable subscriber station, a node, a device, an on board unit (OBU), and the like.
- UE user equipment
- TE terminal equipment
- AMS advanced mobile station
- HR-MS high reliability-mobile station
- OBU on board unit
- each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 may operate in different frequency bands or may operate in the same frequency band.
- Each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 may be connected to each other through an ideal backhaul link or a non-ideal backhaul link.
- information can be exchanged with each other through an ideal backhaul link or a non-ideal backhaul link.
- Each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 may be connected to the core network through an ideal backhaul link or a non-ideal backhaul link.
- Each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 transmits a signal received from the core network to the corresponding terminals 130-1, 130-2, 130-3, 130 -4, 130-5, 130-6), and the signal received from the corresponding terminal (130-1, 130-2, 130-3, 130-4, 130-5, 130-6), is transmitted to the core network can be sent to
- each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 transmits MIMO (eg, single user (SU)-MIMO, multi user (MU)- MIMO, massive MIMO, etc.), coordinated multipoint (CoMP) transmission, carrier aggregation (CA) transmission, transmission in an unlicensed band, direct communication between terminals (device to device communication, D2D) (or , Proximity Services (ProSe)), Internet of Things (IoT) communication, dual connectivity (DC), and the like may be supported.
- MIMO eg, single user (SU)-MIMO, multi user (MU)- MIMO, massive MIMO, etc.
- CoMP coordinated multipoint
- CA carrier aggregation
- CA carrier aggregation
- D2D direct communication between terminals
- D2D device to device communication
- ProSe Proximity Services
- IoT Internet of Things
- DC dual connectivity
- the second base station 110 - 2 may transmit a signal to the fourth terminal 130 - 4 based on the SU-MIMO method, and the fourth terminal 130 - 4 uses the SU-MIMO method.
- a signal may be received from the second base station 110 - 2 .
- the second base station 110-2 may transmit a signal to the fourth terminal 130-4 and the fifth terminal 130-5 based on the MU-MIMO scheme, and the fourth terminal 130-4. and each of the fifth terminals 130 - 5 may receive a signal from the second base station 110 - 2 by the MU-MIMO method.
- Each of the first base station 110-1, the second base station 110-2, and the third base station 110-3 may transmit a signal to the fourth terminal 130-4 based on the CoMP scheme, and the fourth The terminal 130-4 may receive signals from the first base station 110-1, the second base station 110-2, and the third base station 110-3 by the CoMP method.
- a plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) each of the terminals (130-1, 130-2, 130-3, 130-4) belonging to its own cell coverage , 130-5, 130-6) and the CA method can transmit and receive signals.
- Each of the first base station 110-1, the second base station 110-2, and the third base station 110-3 controls D2D between the fourth terminal 130-4 and the fifth terminal 130-5. and each of the fourth terminal 130-4 and the fifth terminal 130-5 may perform D2D under the control of the second base station 110-2 and the third base station 110-3, respectively. .
- the signal may be transmitted using a plurality of carriers (eg, aggregated carriers).
- a plurality of carriers eg, aggregated carriers.
- the following embodiments may be applied to an NR communication system.
- the following embodiments may be applied not only to the NR communication system but also to other communication systems (eg, an LTE communication system, a fifth generation (5G) communication system, a sixth generation (6G) communication system, etc.).
- the numerology may include a subcarrier interval and a CP length (or CP type).
- Table 1 may be a first embodiment of a method for configuring a pneumatology for a CP-OFDM based communication system. Adjacent subcarrier intervals may have a relationship of a power of two to each other, and the CP length may be scaled at the same rate as the OFDM symbol length.
- the pneumatologies of Table 1 may be supported.
- neurology(s) not listed in Table 1 may be further supported.
- CP type(s) not listed in Table 1 eg, extended CP
- Elements constituting a frame structure in the time domain may include a subframe, a slot, a mini-slot, a symbol, and the like.
- a subframe may be used as a unit of transmission, measurement, etc., and the length of the subframe may have a fixed value (eg, 1 ms) regardless of the subcarrier interval.
- a slot may include consecutive symbols (eg, 14 OFDM symbols).
- the length of the slot may be variable, different from the length of the subframe. For example, the length of the slot may be inversely proportional to the subcarrier spacing.
- the slot may be used in units of transmission, measurement, scheduling, resource configuration, timing (eg, scheduling timing, hybrid automatic repeat request (HARQ) timing, channel state information (CSI) measurement and reporting timing, etc.).
- the length of the actual time resource used for transmission, measurement, scheduling, resource setting, etc. may not match the length of the slot.
- the mini-slot may include consecutive symbol(s), and the length of the mini-slot may be shorter than the length of the slot.
- the mini-slot may be used in units of transmission, measurement, scheduling, resource configuration, timing, and the like.
- a mini-slot (eg, a mini-slot length, a mini-slot boundary, etc.) may be predefined in a technical specification.
- a mini-slot (eg, a mini-slot length, a mini-slot boundary, etc.) may be configured (or indicated) in the terminal. When a specific condition is satisfied, it may be configured (or indicated) in the terminal that the mini-slot is used.
- the base station may schedule a data channel (eg, a physical downlink shared channel (PDSCH), a physical uplink shared channel (PUSCH), a physical sidelink shared channel (PSSCH)) using some or all of the symbols constituting the slot.
- a data channel eg, a physical downlink shared channel (PDSCH), a physical uplink shared channel (PUSCH), a physical sidelink shared channel (PSSCH)
- PDSCH physical downlink shared channel
- PUSCH physical uplink shared channel
- PSSCH physical sidelink shared channel
- Elements constituting the frame structure in the frequency domain may include a resource block (RB), subcarriers, and the like.
- One RB may include consecutive subcarriers (eg, 12 subcarriers).
- the number of subcarriers constituting one RB may be constant irrespective of the pneumatology. In this case, the bandwidth occupied by one RB may be proportional to the subcarrier spacing of the Numerology.
- the RB may be used as a transmission and resource allocation unit such as a data channel and a control channel.
- Resource allocation of the data channel may be performed in units of RBs or RB groups (eg, resource block group (RBG)).
- One RBG may include one or more consecutive RBs.
- Resource allocation of the control channel may be performed in units of control channel elements (CCEs). In the frequency domain, one CCE may include one or more RBs.
- a slot is at least one of a downlink (downlink, DL) section, a flexible section (or, an unknown section), and an uplink (uplink, UL) section It may be composed of a combination of sections.
- Each of the downlink section, the flexible section, and the uplink section may consist of one or more consecutive symbols.
- the flexible section may be located between the downlink section and the uplink section, between the first downlink section and the second downlink section, between the first uplink section and the second uplink section, and the like. When the flexible section is inserted between the downlink section and the uplink section, the flexible section can be used as a guard section.
- a slot may include one or more flexible sections. Alternatively, the slot may not include a flexible section.
- the terminal may perform a predefined operation in the flexible section.
- the terminal may perform a semi-static or periodically set operation by the base station in the flexible section.
- the operation periodically set by the base station is a PDCCH (physical downlink control channel) monitoring operation, SS/PBCH (synchronization signal/physical broadcast channel) block reception and measurement operation, CSI-RS (channel state information-reference signal) Reception and measurement operation, reception operation of downlink semi-persistent scheduling (SPS) PDSCH, sounding reference signal (SRS) transmission operation, physical random access channel (PRACH) transmission operation, PUCCH transmission operation configured periodically, configuration grant ) may include a PUSCH transmission operation according to the
- the flexible symbol may be overridden by a downlink symbol or an uplink symbol. When the flexible symbol is overridden by the downlink or uplink symbol, the terminal may perform a new operation instead of the existing operation on the corresponding flexible symbol (eg, an
- the slot format may be semi-statically configured by higher layer signaling (eg, radio resource control (RRC) signaling).
- RRC radio resource control
- Information indicating the semi-static slot format may be included in system information, and the semi-static slot format may be cell-specifically configured.
- the semi-static slot format may be additionally configured for each UE through UE-specific higher layer signaling (eg, RRC signaling).
- a flexible symbol of a cell-specifically configured slot format may be overridden by a downlink symbol or an uplink symbol by UE-specific higher layer signaling.
- the slot format may be dynamically indicated by physical layer signaling (eg, a slot format indicator (SFI) included in downlink control information (DCI)).
- SFI slot format indicator
- DCI downlink control information
- a semi-statically set slot format may be overridden by a dynamically indicated slot format.
- a semi-statically configured flexible symbol may be overridden by a downlink symbol or an uplink symbol by SFI.
- the base station and the terminal may perform a downlink operation, an uplink operation, a sidelink operation, and the like in a bandwidth part.
- the bandwidth portion may be defined as a set of contiguous RBs (eg, physical resource blocks (PRBs)) in a frequency domain having a specific numerology. RBs constituting one bandwidth portion may be continuous in the frequency domain.
- PRBs physical resource blocks
- One neurology may be used for signal transmission (eg, transmission of a control channel or a data channel) in one bandwidth portion.
- “signal” when used in a broad sense may mean any physical signal and channel.
- the terminal performing the initial access procedure may obtain configuration information of the initial bandwidth portion from the base station through system information.
- a terminal operating in an RRC connected state may obtain configuration information of a bandwidth portion from a base station through terminal-specific higher layer signaling.
- the configuration information of the bandwidth part may include a numerology (eg, subcarrier spacing and/or CP length) applied to the bandwidth part.
- the configuration information of the bandwidth part further includes information indicating the location of the start RB (eg, start PRB) of the bandwidth part and information indicating the number of RBs (eg, PRB) constituting the bandwidth part can do.
- At least one bandwidth portion among the bandwidth portion(s) configured in the terminal may be activated.
- each of one uplink bandwidth part and one downlink bandwidth part may be activated in one carrier.
- TDD time division duplex
- a pair of an uplink bandwidth portion and a downlink bandwidth portion may be activated.
- the base station may set a plurality of bandwidth portions to the terminal within one carrier, and may switch the active bandwidth portion of the terminal.
- RB may mean a common RB (CRB).
- RB may mean PRB or virtual RB (VRB).
- a CRB may mean an RB constituting a set (eg, a common RB grid) of RBs that are continuous based on a reference frequency (eg, point A). Carriers, bandwidth portions, etc. may be deployed on a common RB grid. That is, a carrier, a bandwidth portion, and the like may be composed of CRB(s).
- An RB or CRB constituting a bandwidth portion may be referred to as a PRB, and a CRB index within the bandwidth portion may be appropriately converted into a PRB index.
- the RB may mean an interlace RB (IRB).
- the minimum resource unit constituting the PDCCH may be a resource element group (REG).
- the REG may consist of one PRB (eg, 12 subcarriers) in the frequency domain and one OFDM symbol in the time domain. Accordingly, one REG may include 12 resource elements (REs).
- a demodulation reference signal (DM-RS) for decoding the PDCCH may be mapped to 3 REs among 12 REs constituting the REG, and control information (eg, modulated DCI) is transmitted to the remaining 9 REs. can be mapped to
- DM-RS demodulation reference signal
- One PDCCH candidate may consist of one CCE or aggregated CCEs.
- One CCE may consist of a plurality of REGs.
- the NR communication system may support CCE aggregation levels 1, 2, 4, 8, 16, etc., and one CCE may consist of 6 REGs.
- a control resource set may be a resource region in which the UE performs blind decoding of the PDCCH.
- CORESET may consist of a plurality of REGs.
- CORESET may consist of one or more PRBs in the frequency domain and one or more symbols (eg, OFDM symbols) in the time domain. Symbols constituting one CORESET may be continuous in the time domain. PRBs constituting one CORESET may be continuous or discontinuous in the frequency domain.
- One DCI (eg, one PDCCH) may be transmitted in one CORESET.
- a plurality of CORESETs may be configured from a cell viewpoint or a terminal viewpoint, and the plurality of CORESETs may overlap each other in time-frequency resources.
- the CORESET may be set in the terminal by the PBCH (eg, system information transmitted through the PBCH, a master information block (MIB)). ID (identifier) of CORESET set by PBCH may be 0. That is, the CORESET set by the PBCH may be referred to as CORESET #0.
- the UE operating in the RRC idle state may perform a monitoring operation in CORESET #0 to receive the first PDCCH in the initial access procedure. Not only the UE operating in the RRC idle state but also the UE operating in the RRC connected state may perform a monitoring operation in CORESET #0.
- CORESET may be set in the terminal by other system information (eg, system information block type 1 (SIB1)) in addition to the system information transmitted through the PBCH.
- SIB1 system information block type 1
- the UE may receive SIB1 including configuration information of CORESET.
- CORESET may be set in the UE by UE-specific higher layer signaling (eg, RRC signaling).
- One or more CORESETs for each downlink bandwidth portion may be configured for the UE.
- the UE may monitor the PDCCH candidate(s) for the CORESET set in the corresponding bandwidth part in the downlink active bandwidth part.
- the UE may monitor the PDCCH candidate(s) for a CORESET (eg, CORESET #0) set in a downlink bandwidth part other than the corresponding bandwidth part in the downlink active bandwidth part.
- the initial downlink active bandwidth part may include CORESET #0, and may be combined with CORESET #0.
- CORESET having a quasi co-location (QCL) relationship with the SS/PBCH block in a primary cell (PCell), a secondary cell (SCell), and/or a primary secondary cell (PSCell) #0 may be configured for the terminal.
- CORESET #0 may not be set for the UE.
- the search space may be a set of PDCCH candidate(s) or a set of resource regions occupied by PDCCH candidate(s).
- the UE may perform blind decoding on each of the PDCCH candidates within a predefined search space.
- the UE may determine whether the PDCCH has been transmitted to the UE by performing a cyclic redundancy check (CRC) on the blind decoding result.
- CRC cyclic redundancy check
- the UE may receive the PDCCH.
- the UE may periodically monitor the search space, and may monitor the search space at one or more time locations (eg, PDCCH monitoring occasion (MO), CORESET) within one period.
- time locations eg, PDCCH monitoring occasion (MO), CORESET
- the PDCCH candidate may be composed of CCE(s) selected by a predefined hash function within a CORESET or search space occurrence.
- the search space may be defined/configured for each CCE aggregation level. In this case, the sum of search spaces for all CCE aggregation levels may be referred to as a search space set.
- search space may mean “search space set”
- search space set may mean “search space”.
- the search space set may be logically associated with or correspond to one CORESET.
- One CORESET may be logically combined with or correspond to one or more search space sets.
- a search space set for transmitting a common DCI or a group common DCI may be referred to as a common search space set (hereinafter, referred to as a “CSS set”).
- Common DCI or group common DCI may include resource allocation information of PDSCH for transmission of system information, paging information, power control command, SFI, preemption indicator, and the like.
- the common DCI may correspond to DCI formats 0_0, 1_0, etc.
- a cyclic redundancy check (CRC) of the common DCI transmitted to the terminal is a system information-radio network temporary identifier (SI-RNTI), P-RNTI It may be scrambled by (paging-RNTI), random access-RNTI (RA-RNTI), temporary cell-RNTI (TC-RNTI), or the like.
- SI-RNTI system information-radio network temporary identifier
- P-RNTI P-RNTI It may be scrambled by (paging-RNTI), random access-RNTI (RA-RNTI), temporary cell-RNTI (TC-RNTI), or the like.
- the CRC of the group common DCI transmitted to the terminal may be scrambled by SFI-RNTI (slot format indicator-RNTI), etc.
- the CSS set may include Type 0, Type
- the search space set for transmitting the UE-specific DCI may be referred to as a UE-specific search space set (hereinafter, referred to as a “USS set”).
- the UE-specific DCI may include scheduling and resource allocation information such as PDSCH, PUSCH, and PSSCH.
- the terminal-specific DCI may correspond to DCI formats 0_1, 0_2, 1_1, 1_2, 3_0, 3_1, etc., and the CRC of the terminal-specific DCI transmitted to the terminal is C-RNTI, CS-RNTI (configured Scheduling-RNTI), modulation and coding scheme-C-RNTI (MCS-C-RNTI), or the like may be scrambled.
- UE-specific DCI may be transmitted even in the CSS set.
- the UE-specific DCI may be transmitted according to a DCI format corresponding to the common DCI.
- the UE may monitor the PDCCH (eg, DCI formats 0_0, 0_1) in which CRC is scrambled with C-RNTI, CS-RNTI, MCS-C-RNTI, etc. in the CSS set.
- the UE may monitor a fallback DCI (or a fallback DCI format) in the CSS set.
- the payload size of the fallback DCI format may be fixed. Even when RRC reconfiguration for a corresponding serving cell and/or bandwidth portion is performed, the size of the fallback DCI (eg, the payload size of the fallback DCI format) may not be changed. Even while the RRC reconfiguration procedure is being performed, the fallback DCI may be used for scheduling.
- the fallback DCI may include DCI formats 0_0, 1_0, and the like.
- the UE may monitor non-fallback DCI (or non-fallback DCI format) in the USS set.
- the payload size of the non-fallback DCI format may be changed by RRC reconfiguration for a corresponding serving cell and/or a bandwidth portion.
- the non-fallback DCI may include DCI formats 0_1, 1_1, 0_2, 1_2, 3_0, 3_1, and the like.
- the UE may monitor the fallback DCI (or the fallback DCI format) in the USS set.
- the UE may receive configuration information indicating monitoring of only one DCI format among the fallback DCI and the non-fallback DCI in each USS set from the flag station.
- the fallback DCI may correspond to a common DCI format and may also correspond to a UE-specific DCI format transmitted according to the common DCI format.
- the non-fallback DCI may correspond to a UE-specific DCI format (eg, a UE-specific DCI format transmitted according to a DCI format rather than a common DCI format).
- the non-fallback DCI monitoring operation may be configured in the terminal through a signaling procedure (eg, RRC signaling procedure) from the base station.
- the type 0 CSS set may be used for receiving DCI scheduling PDSCH including SIB1, and may be configured through PBCH or cell-specific RRC signaling.
- the ID of the type 0 CSS set may be assigned or set to 0.
- Type 0 CSS set can be logically combined with CORESET #0.
- the UE may assume that the PDCCH DM-RS has a QCL relationship with some signal (eg, SS/PBCH block, CSI-RS, PDSCH DM-RS, PDCCH DM-RS, etc.).
- some signal eg, SS/PBCH block, CSI-RS, PDSCH DM-RS, PDCCH DM-RS, etc.
- the PDCCH and the PDCCH DM-RS may have a QCL relationship with each other. Therefore, the UE can obtain information about the large-scale propagation characteristics of the radio channel experienced by the PDCCH and the PDCCH DM-RS through the above-described QCL assumption, and use the obtained large-scale propagation characteristics to estimate the channel and form the receive beam. etc. can be used.
- the spatial reception parameter may correspond to characteristics such as a reception beam, a reception channel spatial correlation, and a transmission/reception beam pair.
- the spatial reception parameter may be referred to as “spatial QCL”.
- the PDCCH may be used to mean including the PDCCH DM-RS, and saying that the PDCCH has a QCL relationship with a certain signal may include the meaning that the DM-RS of the PDCCH has a QCL relationship with a certain signal.
- a signal having a QCL relationship with the PDCCH or a resource thereof may be referred to as a QCL source, a QCL source signal, a QCL source resource, or the like.
- PDCCHs transmitted in the same CORESET, a search space set corresponding to the same CORESET, and/or PDCCH monitoring occasions corresponding to the same CORESET may have the same QCL relationship. That is, the unit of aggregation in which the UE assumes the same QCL may be a CORESET, and the QCL assumption may be independent for each CORESET.
- the QCL, QCL source, etc. of a certain CORESET may mean QCL, QCL source, etc. of the PDCCH received through the corresponding CORESET, respectively.
- different QCL assumptions may be applied to search space sets corresponding to one CORESET. For example, a search space set for monitoring RA-RNTI (eg, Type 1 CSS set) and other search space sets may have different QCL relationships.
- the QCL relationship or QCL assumption (eg, QCL source, QCL type, etc.) of CORESET may be determined by a predefined method.
- the UE selects an SS/PBCH block and/or CSI-RS in which a PDCCH DM-RS received through a certain CORESET or a certain search space set during initial access or random access procedure and a predefined QCL type It can be assumed to have a QCL relationship with
- the QCL type may mean a set of one or more QCL parameter(s).
- the QCL relationship or QCL assumption (eg, QCL source, QCL type, etc.) of CORESET is signaling (eg, RRC signaling, medium access control (MAC) control element (CE) signaling, and DCI from the base station to the terminal. signaling, one or a combination of two or more). That is, the base station may set a transmission configuration information (TCI) state for CORESET in the terminal.
- TCI state is an ID of a signal (eg, QCL source of PDCCH DM-RS, QCL source resource) having a QCL relationship with a DM-RS (eg, PDCCH DM-RS) of a physical channel to which TCI is applied. and/or at least one QCL type thereof.
- the TCI state may include one or more ⁇ ID and/or QCL type ⁇ .
- the base station may set one or more TCI state candidates for each CORESET through RRC signaling to the terminal, and one TCI state used for CORESET monitoring of the terminal from among the one or more TCI state candidates MAC signaling (or DCI signaling) ) to indicate or set.
- the MAC signaling procedure (or DCI signaling procedure) may be omitted.
- the UE may perform PDCCH monitoring and reception operations for the corresponding CORESET based on the TCI state setting information received from the base station.
- a high frequency band and a low frequency band may be different from each other.
- a low frequency band eg, a band below 6 GHz
- path loss of a signal due to a channel is relatively small
- a signal may be transmitted/received using a beam having a wide beamwidth.
- the entire coverage of a cell (or sector) may be covered even with a single beam.
- beamforming by a large-scale antenna may be used to extend the signal reach.
- beamforming may be applied to a common signal and a control channel as well as a data channel.
- a communication node eg, a base station
- the signal can be transmitted and received multiple times.
- An operation of repeatedly transmitting a signal on a plurality of time resources using a plurality of beams may be referred to as a beam sweeping operation.
- a system for transmitting a signal using a plurality of beams having such a narrow beam width may be referred to as a multi-beam system.
- the multi-beam system may operate based on beam management.
- the UE may measure beam quality with respect to a received signal (eg, SS/PBCH block, CSI-RS, etc.), and may report the measurement result of the beam quality to the base station. For example, the UE calculates beam quality measurements such as reference signal received power (RSRP) and signal-to-interference-plus-noise ratio (SINR) for each beam (eg, each signal, each resource). and the optimal beam(s) and corresponding measurement value(s) may be reported to the base station.
- the base station may determine a transmission beam for the terminal based on measurement information of beam quality received from the terminal.
- the base station based on the measurement information of the beam quality received from the terminal, the terminal's physical signal and channel (eg, PDCCH, PDSCH, CSI-RS, PUCCH, PUSCH, SRS, PRACH, etc.) for reception of TCI state can be set in the terminal.
- the terminal's physical signal and channel eg, PDCCH, PDSCH, CSI-RS, PUCCH, PUSCH, SRS, PRACH, etc.
- a carrier aggregation method may be applied to the terminal. That is, the terminal may receive configuration information of a plurality of carriers from the base station, may aggregate the plurality of carriers, and may communicate with the base station using the aggregated carriers.
- a carrier may be interpreted to mean a cell or a serving cell, and each of the cell and the serving cell may be interpreted to mean a carrier.
- Aggregated carriers may be adjacent to each other in the frequency domain.
- the aggregated carriers may not be contiguous in the frequency domain.
- the plurality of carriers may belong to the same frequency band or different frequency bands.
- One or more downlink bandwidth parts and one or more uplink bandwidth parts may be configured in each of the carriers, and a sidelink bandwidth part may be additionally configured in a specific carrier.
- the terminal may perform communication (eg, a transmission operation, a reception operation, a measurement operation) in the active bandwidth portion of the activated carrier(s).
- a terminal to which the carrier aggregation method is applied may have one PCell and one or more SCell(s).
- the PCell may be referred to as a first cell and the SCell may be referred to as a second cell.
- the PCell may be referred to as a second cell and the SCell may be referred to as a first cell.
- the UE may determine the PCell in an initial cell search procedure, a cell (re)selection procedure, a handover procedure, and the like.
- the SCell may be configured in a terminal (eg, a terminal in an RRC connected state) through a signaling message (eg, an RRC signaling message) transmitted from a base station. SCell can be activated or deactivated.
- Activation and/or deactivation of the SCell may be controlled through a signaling message (eg, DCI, medium access control (MAC) control element (CE), RRC signaling, etc.) transmitted from the base station.
- PCell and SCell may be configured specifically for a UE.
- the same serving cell may operate as a PCell for a first terminal and may operate as an SCell for a second terminal.
- a plurality of terminals may use different serving cells as PCells.
- a serving cell may be configured with a downlink carrier and/or an uplink carrier.
- the serving cell may include a plurality of uplink carriers and/or a plurality of downlink carriers.
- the serving cell may include a supplementary uplink carrier.
- the serving cell may include a secondary downlink carrier.
- DCI (or PDCCH) for scheduling the data channel may be transmitted on the same carrier as the carrier through which the corresponding data channel is transmitted. This scheme may be referred to as a self-scheduling scheme. Alternatively, the DCI (or PDCCH) for scheduling the data channel may be transmitted on a carrier different from the carrier through which the corresponding data channel is transmitted. This scheme may be referred to as a cross-carrier scheduling scheme.
- the cross-carrier scheduling scheme may be used for the purpose of offloading a control channel, controlling interference between control channels, and the like.
- the data channel may be a data channel including unicast data or UE-specific data (eg, a downlink-shared channel (DL-SCH), an uplink-shared channel (UL-SCH)).
- the DCI for scheduling the data channel may mean a DCI (or DCI format) having a CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI.
- One of the self-scheduling scheme and the cross-carrier scheduling scheme may be applied to each carrier or each serving cell.
- a carrier through which the scheduling DCI is transmitted may be referred to as a scheduling cell, and a carrier through which a data channel is transmitted may be referred to as a scheduled cell.
- the scheduling cell may be the same as the scheduled cell.
- the scheduling cell may be different from the scheduled cell.
- the UE may perform the PDCCH monitoring operation corresponding to the scheduled cell in the scheduling cell.
- An association relationship between the scheduling cell and the scheduled cell may be established in the terminal through a higher layer signaling (eg, RRC signaling) procedure.
- HARQ-ACK (acknowledgement) information which is a reception response of the PDSCH, may be transmitted through the PUCCH.
- the terminal may transmit the PUCCH including the HARQ-ACK information to the base station through the PCell.
- the UE adds configuration information of a cell capable of transmitting PUCCH including HARQ-ACK information in addition to the PCell (hereinafter referred to as "PUCCH cell") from the base station can be received with
- one PCell and one SCell may be configured as a PUCCH cell in the UE.
- the UE may receive configuration information of the PUCCH cell group coupled to each PUCCH cell from the base station.
- HARQ-ACK information for a PDSCH transmitted through a serving cell belonging to a PUCCH cell group may be transmitted through a corresponding PUCCH cell.
- a communication service provider may wish to simultaneously provide services of heterogeneous communication systems (eg, an NR communication system and an LTE communication system) using the same frequency band.
- the carrier of the NR communication system hereinafter referred to as "NR carrier”
- the carrier of the LTE communication system hereinafter referred to as "LTE carrier”
- NR carrier the carrier of the NR communication system
- LTE carrier the carrier of the LTE communication system
- the NR carrier and LTE carriers may dynamically share spectrum according to traffic conditions. That is, the NR signal of the NR carrier and the LTE signal of the LTE carrier may be dynamically multiplexed and transmitted in time, frequency, and/or spatial resources within the same frequency domain.
- the base station when the traffic of the LTE communication system is high, the base station (or the base station of the NR communication system) may transmit a small amount of signals in the NR carrier overlapping the LTE carrier. When the traffic of the LTE communication system is small, the base station (or the base station of the NR communication system) may transmit a signal using many physical resources in the NR carrier overlapping the LTE carrier.
- FIG. 3 is a conceptual diagram illustrating a carrier aggregation method and a method of disposing the aggregated carriers.
- a base station may configure a plurality of cells (eg, PCell and SCell) and transmit configuration information of the plurality of cells to the terminal.
- PCell and SCell may be aggregated in a terminal.
- the PCell may be an FDD cell
- SCell may be a TDD cell.
- the downlink carrier of the PCell may overlap with a carrier (eg, an LTE carrier) of another communication system.
- a part of the downlink physical resource of the PCell may be used for LTE signal transmission.
- a part of the downlink physical resource of the PCell may be occupied in advance for LTE signal transmission.
- the size of the resource region that can be used for NR signal transmission in the downlink carrier of the PCell may be limited.
- CORESET may be set in a limited resource area of the PCell, and the above-described restriction may cause a decrease in the PDCCH transmission capacity of the PCell. If the PDCCH transmission capacity is small, the base station may not be able to schedule the data channel even though transmission available resources (eg, uplink resources of the PCell) of the data channel (eg, PUSCH) are sufficient. Accordingly, spectral efficiency may decrease, and transmission delay time may increase.
- a cross-carrier scheduling scheme may be applied to the PCell.
- an SCell may be configured and/or activated in the terminal, and cross-carrier scheduling from the SCell to the PCell may be used.
- the base station may transmit a DCI (or PDCCH) for scheduling a data channel (eg, PDSCH, PUSCH) of the PCell to the UE through a cell other than the PCell (eg, SCell).
- a DCI for the PCell eg, data channel scheduling of the PCell
- the UE performs a PDSCH reception operation or a PUSCH transmission operation on the PCell based on the scheduling information of the DCI.
- DCI received from a specific CORESET of the SCell, a specific search space set, a specific monitoring occasion, etc. may be regarded as DCI for the PCell, and this operation may be configured (or instructed) by the UE.
- the DCI received from the SCell includes a carrier indicator field (CIF) corresponding to the PCell
- the UE may regard the DCI as a DCI for the PCell.
- CIF carrier indicator field
- the data channel of the PCell may be a data channel including unicast data or UE-specific data (eg, DL-SCH, UL-SCH).
- the data channel of the PCell may be a data channel allocated from the scheduling DCI for the PCell regardless of whether UE-specific data is included.
- Scheduling DCI for PCell may mean DCI (or DCI format) having CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI.
- the scheduling DCI for the PCell may include DCI formats 0_1, 1_1, 0_2, 1_2, and the like.
- the scheduling DCI for the PCell may be a DCI transmitted through the USS set. That is, the search space set of the SCell in which the UE performs PDCCH monitoring for the PCell may include at least the USS set.
- the PCell may be an FDD cell or a TDD cell.
- the SCell may be an FDD cell or a TDD cell.
- duplex schemes in the PCell and the SCell may be the same or different from each other.
- the PCell may be an FDD cell
- the SCell may be a TDD cell.
- the numerologies eg, subcarrier spacing and/or CP type
- the subcarrier spacing of the activated bandwidth portion of the PCell may be 15 kHz
- the subcarrier spacing of the activated bandwidth portion of the SCell may be 30 kHz.
- the UE may monitor the scheduling DCI for the PCell in the USS set of the SCell.
- the non-fallback DCI format for the PCell in the USS set of the SCell may be monitored, and this operation may be configured in the UE.
- the UE may perform monitoring in the USS set of the SCell according to the above-described configuration.
- the payload size of the non-fallback DCI format for the PCell may be changed by RRC reconfiguration of the PCell (eg, change of a configuration parameter for an active bandwidth portion of the PCell, etc.).
- the UE may not receive the non-fallback DCI format for the PCell in the SCell while performing the RRC reconfiguration procedure of the PCell due to ambiguity of the DCI size.
- “DCI size”, “DCI format size”, “DCI payload size” and “DCI format payload size” may have the same meaning.
- Beam failure may occur when "the link performance of the SCell is degraded" or "the CORESET beam of the SCell is invalid". When beam failure occurs, it may be difficult for the UE to receive DCI for PCell in the SCell.
- the UE for scheduling of the PCell (eg, reception of scheduling information), the UE not only monitors the non-fallback DCI format in the USS set of the SCell, but also “other search space sets and/or A monitoring operation for "other DCI formats" may be additionally performed. This operation may be referred to as (method 100). (Method 100) will be described in the examples below.
- the terminal may additionally perform the monitoring operation of the fallback DCI for the PCell in the CSS set of the PCell.
- the UE may monitor the fallback DCI in the CSS set of the PCell and monitor the non-fallback DCI in the USS set of the SCell. Both the monitoring operation in the PCell and the monitoring operation in the SCell may be performed within a reference time.
- the UE may additionally perform the monitoring operation of the fallback DCI for the PCell in the CSS set of the PCell and/or the USS set of the SCell.
- the UE may monitor the fallback DCI in the CSS set of the PCell and/or the USS set of the SCell, and obtain a non-fallback DCI in the USS set of the SCell. can be monitored.
- some monitoring operations eg, monitoring operation of fallback DCI in CSS set of PCell, monitoring operation of fallback DCI in USS set of SCell
- the second embodiment may include the first embodiment.
- the UE may additionally perform the monitoring operation of the fallback DCI for the PCell in the CSS set of the PCell, the USS set of the PCell, and/or the USS set of the SCell, and select the PCell from the USS set of the PCell.
- a non-fallback DCI monitoring operation may be additionally performed.
- the UE may perform a monitoring operation of the fallback DCI in the CSS set of the PCell, the USS set of the PCell, and/or the USS set of the SCell, and the USS set of the SCell and/or Alternatively, the non-fallback DCI monitoring operation may be performed in the USS set of the PCell.
- some monitoring operation may or may not be performed according to the definition in the base station setting and/or technical standard.
- the UE may not perform the monitoring operation of the fallback DCI in the USS set of the SCell, and may perform the monitoring operation of the fallback DCI in the CSS set of the PCell and/or the USS set of the PCell. and may perform a non-fallback DCI monitoring operation in the USS set of the SCell and/or the USS set of the PCell.
- the UE may not perform the monitoring operation of the fallback DCI in the USS set of the SCell and may not perform the monitoring of the fallback DCI in the USS set of the PCell.
- the monitoring operation of the fallback DCI may be performed in the CSS set of , and the monitoring operation of the non-fallback DCI may be performed in the USS set of the SCell and/or the USS set of the PCell.
- the third embodiment may include the first embodiment or the second embodiment.
- the UE may additionally perform the monitoring operation of the fallback DCI for the PCell in the CSS set of the SCell.
- the UE may perform a monitoring operation of the fallback DCI in the CSS set of the SCell, and may perform the monitoring operation of the non-fallback DCI in the USS set of the SCell.
- the CSS set of the SCell may be a specific type of CSS set (eg, type 3 CSS set).
- the fourth embodiment may be implemented in combination with the above-described embodiment(s). For example, the fourth embodiment may be combined with the first embodiment.
- the UE may perform the monitoring operation of the fallback DCI in the CSS set of the PCell and/or the CSS set of the SCell, and the monitoring operation of the non-fallback DCI in the USS set of the SCell. can do.
- the UE may perform a PDCCH monitoring operation in both the PCell and the SCell. That is, the self-scheduling scheme (eg, the self-scheduling scheme from the PCell) and the cross-carrier scheduling scheme (eg, the cross-carrier scheduling scheme from the SCell) are simultaneously applied to one serving cell (eg, PCell) can
- the monitoring operation in the PCell and the monitoring operation in the SCell may all (or together) be performed within the same reference time.
- both the fallback DCI and the non-fallback DCI may be monitored.
- the corresponding serving cell (eg, PCell) ) for scheduling can be performed.
- the fallback DCI may be selectively transmitted in the CSS set and the USS set.
- the UE monitors non-fallback DCI in a plurality of serving cells (eg, PCell and SCell) in order to receive scheduling information for a certain serving cell (eg, PCell). can do. According to this, even when the link quality of any serving cell for which DCI is monitored is deteriorated, scheduling by non-fallback DCI may be performed through another serving cell.
- cross-carrier scheduling from SCell to PCell will be mainly considered, but this may only be an example for a specific scenario (eg, dynamic spectrum sharing scenario).
- the PCell and/or SCell may be interpreted as any serving cell configured in the UE.
- a PCell that is a scheduled cell may be interpreted as a first serving cell
- an SCell that is a scheduling cell may be interpreted as a second serving cell.
- Each of the first serving cell and the second serving cell may be a PCell, an SCell, or a PSCell.
- the PSCell may be effective when dual connectivity technology is applied to the terminal.
- Embodiments may be used for cross-carrier scheduling within a primary cell group or a secondary cell group.
- the PCell may correspond to the PSCell.
- two serving cells will be mainly considered, but embodiments may be extended to three or more cells.
- the embodiments can be easily extended to a case in which the UE monitors scheduling DCI for a certain serving cell in three or more serving cells.
- one serving cell among three or more serving cells may be a cell to which scheduling DCI is applied.
- one serving cell among three or more serving cells may be a PCell, and the remaining two or more serving cells may be an SCell.
- the payload size of each DCI (or DCI format) monitored by the UE may be determined based on a serving cell to which DCI is applied or a (active) bandwidth portion.
- the size of DCI may be determined by a setting value of configuration parameter(s) associated with fields of DCI among configuration parameters related to a serving cell or (active) bandwidth portion to which DCI is applied.
- the size of the DCI may be determined based on a scheduled cell (or an active bandwidth portion of the scheduled cell).
- the size of the DCI for the PCell may be determined by the setting value of the setting parameter(s) related to the PCell or the active bandwidth portion of the PCell.
- the number of maximum payload sizes of DCI (or DCI format) that the UE can monitor may be limited.
- the UE may perform PDCCH monitoring for up to X different DCI sizes for each serving cell.
- X may be a natural number.
- the UE may perform PDCCH monitoring for up to Y different DCI sizes.
- Y may be a natural number less than or equal to X.
- the upper limit values of the number of DCI sizes, X and Y may be predefined in a technical standard or set in the terminal from the base station.
- X may be 4 and Y may be 3.
- the UE determines different DCI sizes until the total number of DCI sizes does not exceed X or Y A sorting procedure can be performed.
- the UE may perform PDCCH monitoring for up to X different DCI sizes for each serving cell for each reference time.
- X may be a natural number.
- the UE may perform PDCCH monitoring for up to Y different DCI sizes for each reference time.
- Y may be a natural number less than or equal to X.
- X and Y which are upper limits of the number of DCI sizes, may be predefined in a technical standard or set in the terminal from the base station.
- X may be 4 and Y may be 3. If the total number of different sizes of DCI format(s) configured to be monitored for a certain reference time in each serving cell exceeds X or Y, the terminal determines that the total number of DCI sizes for the reference time is X or Y A procedure of aligning different DCI sizes may be performed until it does not exceed. That is, the DCI size alignment procedure may be performed for each reference time.
- the method described above may be referred to as (Method 110).
- the above-described reference time may be one slot.
- the reference time may be a time unit smaller than one slot (eg, Z1 symbol(s)).
- the reference time may be Z2 consecutive slots.
- Z2 may be a natural number.
- Z1 and/or Z2 may be predefined in a technical standard or may be set in the terminal from the base station.
- the value of Z1 and/or Z2 (or the range of Z1 and/or Z2 values) applied to the reference time is the operating frequency band (eg, the frequency band to which the carrier belongs), the number used in the carrier, or the bandwidth portion It may be determined based on roller paper (eg, subcarrier spacing and/or CP type).
- the slot used as the reference time may be a slot according to the number of cells to be scheduled (or (active) bandwidth portion corresponding to the scheduled cell).
- the slot used as the reference time may be a slot according to the number of scheduling cells (or (active) bandwidth portion corresponding to one scheduling cell) among a plurality of scheduling cells.
- the aforementioned one scheduling cell may be a cell in which a bandwidth portion (eg, an active bandwidth portion) having the smallest (or largest) subcarrier spacing among the plurality of scheduling cells is located.
- the bandwidth portion of the cells for scheduling may be switched, and accordingly, one cell, which is a criterion for determining neurology, may be dynamically changed.
- the UE can count the number of DCI sizes in a section corresponding to each slot of the PCell in a certain section, and in another section, corresponding to each slot of the SCell The number of DCI sizes may be counted in the interval.
- the aforementioned (active) bandwidth portion may be a downlink bandwidth portion or an uplink bandwidth portion.
- the above-described (active) bandwidth portion may be a bandwidth portion having a subcarrier interval that is not larger (or smaller) among the downlink bandwidth portion and the uplink bandwidth portion.
- the UE When the UE performs PDCCH monitoring in a plurality of scheduling cells (eg, PCell and SCell) for scheduling of a scheduled cell (eg, PCell) according to the above-described embodiments, in the scheduling cells A method of determining the size of the DCI format to be monitored will be described below.
- the UE may determine the size of DCI format(s) to be monitored in one or more scheduling cells (eg, PCell and SCell) for the PCell.
- the UE may count the total number of DCI sizes to be monitored in the one or more scheduling cells.
- the UE may count the total number of DCI sizes to be monitored in the one or more scheduling cells for each reference time.
- the UE may perform a procedure for reducing the number of DCI sizes by aligning DCI sizes. This operation is performed for each reference time of each scheduled cell (or scheduling cell(s) corresponding to the scheduled cell) or each scheduled cell (or scheduling cell(s) corresponding to the scheduled cell). can be performed.
- the above-described procedure may consist of a plurality of steps. “Aligning DCI sizes” may mean “aligning DCI sizes to be the same”.
- the UE may determine the sizes of an uplink fallback DCI format (eg, DCI format 0_0) and a downlink fallback DCI format (eg, DCI format 1_0) in the CSS set.
- the UE aligns the size of one DCI format (eg, uplink fallback DCI format) to the size of another DCI format (eg, downlink fallback DCI format)
- the sizes of uplink and downlink fallback DCI formats may be identical to each other.
- the matched size in the CSS set may be referred to as the first size.
- the CSS set may be the CSS set of the PCell and/or the CSS set of the SCell.
- the size of the fallback DCI format monitored by the CSS set of the PCell may be the same as the size of the fallback DCI format monitored by the CSS set of the SCell. . That is, the sizes of the fallback DCI formats that the UE monitors in the CSS set for the PCell may all be the same.
- a bit stream (eg, a zero bit stream) predetermined in the DCI format of one cell so that the fallback DCI formats have the same size. , zero padding) may be inserted.
- the fallback DCI format may be monitored only in one search space set among the CSS set of the PCell and the CSS set of the SCell at each reference time (eg, each slot), and this operation may be configured in the terminal.
- the size of the fallback DCI format monitored by the CSS set of the PCell and the size of the same fallback DCI format monitored by the CSS set of the SCell may generally be different from each other.
- the size of the fallback DCI format monitored by the CSS set of the PCell may be the same as the size of the same fallback DCI format monitored by the CSS set of the SCell.
- the UE may determine the sizes of the uplink fallback DCI format (eg, DCI format 0_0) and the downlink fallback DCI format (eg, DCI format 1_0) of the USS set.
- the UE aligns the size of one DCI format with the size of another DCI format to match the size of the uplink fallback DCI format and the size of the downlink fallback DCI format in the USS set. have.
- the matched size in the USS set may be referred to as a second size.
- the USS set may be the USS set of the PCell and/or the USS set of the SCell.
- the size of the fallback DCI format monitored by the USS set of the PCell may be the same as the size of the same fallback DCI format monitored by the USS set of the SCell. That is, the sizes of the fallback DCI formats that the UE monitors in the USS set for the PCell may all be the same.
- a predetermined bit string eg, zero bit string, zero padding
- the fallback DCI format may be monitored in only one search space set among the USS set of the PCell and the USS set of the SCell within each reference time (eg, each slot), and this operation may be configured in the UE.
- the size of the fallback DCI format monitored by the USS set of the PCell may be generally different from the size of the same fallback DCI format monitored by the USS set of the SCell.
- the size of the fallback DCI format monitored by the USS set of the PCell may be different from the size of the same fallback DCI format monitored by the USS set of the SCell.
- the UE may determine the sizes of the uplink non-fallback DCI format (eg, DCI format 0_1) and the downlink non-fallback DCI format (eg, DCI format 1_1) of the USS set.
- the size of the uplink non-fallback DCI format and/or the downlink non-fallback DCI format in the USS set may coincide with the second size.
- a size of the corresponding non-fallback DCI format may be differentiated from the second size by adding a predetermined bit string (eg, one bit having a zero value, or a zero bit string having one or more bits) to the payload.
- a predetermined bit string eg, one bit having a zero value, or a zero bit string having one or more bits
- the cell to which the USS set monitoring the non-fallback DCI format belongs and the cell of the USS set monitoring the fallback DCI format match are additionally satisfied (eg, the USS monitoring the non-fallback DCI format)
- the USS monitoring the non-fallback DCI format are PCells
- a predetermined bit string may be added to the payload of the non-fallback DCI format, and the size of the non-fallback DCI format is the size of the fallback DCI format.
- the cell to which the USS set monitoring the non-fallback DCI format belongs does not match the cell of the USS set monitoring the fallback DCI format (eg, the cell to which the USS set monitoring the non-fallback DCI format belongs is the SCell and , when the cell to which the USS set monitoring the fallback DCI format belongs is a PCell), the above-described method may not be applied. Accordingly, the size of the non-fallback DCI format may coincide with the size of the fallback DCI format.
- the above-described bit string padding method is the USS set of the PCell It can be applied only to the non-fallback DCI format monitored in .
- the bitstream padding method may be applied to both the non-fallback DCI format monitored by the USS set of the PCell and the non-fallback DCI format monitored by the USS set of the SCell.
- the size of the non-fallback DCI format monitored in the USS set of the PCell may match the size of the non-fallback DCI format monitored in the USS set of the SCell.
- the size of the uplink non-fallback DCI format of the USS set determined in step 3 may be referred to as a size 3-1, and the size of the downlink non-fallback DCI format of the USS set determined in step 3 is 3 It can be referred to as two sizes.
- the 3-1 size may be the same as the 3-2 size. Alternatively, the 3-1 size may be different from the 3-2 size.
- the UE may determine the sizes of the uplink non-fallback DCI format (eg, DCI format 0_2) and the downlink non-fallback DCI format (eg, DCI format 1_2) of the USS set.
- the size of the uplink non-fallback DCI format and/or the downlink non-fallback DCI format in the USS set may coincide with the second size.
- the UE uses the uplink non-fallback DCI format and/or the downlink non-fallback DCI format of the USS set.
- a size of the corresponding non-fallback DCI format may be differentiated from the second size by adding a predetermined bit string (eg, one bit having a zero value, or a zero bit string having one or more bits) to the payload.
- a method of allowing the size of the non-fallback DCI format to be distinguished from the second size may be applied according to the above-described predetermined condition.
- the base station determines that the size of the non-fallback DCI format of the USS set (eg, DCI format 0_2, 1_2, 0_1, or 1_1) is the second size.
- configuration parameters related to the size of the DCI format may be determined as appropriate values to be different from the size 2, and the determined configuration parameters may be transmitted to the terminal.
- the UE may not expect that the size of the non-fallback DCI format is the same as the second size in the USS set.
- a method for allowing the size of the non-fallback DCI format to be distinguished from the second size in the USS set may be applied according to the above-described predetermined condition.
- the size of the uplink non-fallback DCI format of the USS set determined in step 4 may be referred to as a size 4-1, and the size of the downlink non-fallback DCI format of the USS set determined in step 4 is 4 It can be referred to as two sizes.
- the 4-1 size may be the same as the 4-2 size. Alternatively, the 4-1 size may be different from the 4-2 size.
- Payload size of the non-fallback DCI format that the UE monitors in the USS set of a plurality of serving cells may be determined to have different sizes. For example, whether or not specific field(s) of the DCI format are included may be different for each serving cell in which the DCI format is transmitted. That is, when the PCell is scheduled by the same DCI format, the DCI format transmitted in the PCell (eg, USS set of PCell) may include specific field(s) and the SCell (eg, USS of SCell) The DCI format transmitted in the set) may not include the specific field(s) described above.
- the PCell eg, USS set of PCell
- SCell eg, USS of SCell
- the DCI format transmitted from the PCell may not include specific field(s)
- the DCI format transmitted from the SCell eg, the USS set of the SCell
- the DCI format transmitted from the SCell may be described above. It may include specific field(s).
- the specific field(s) described above may be field(s) related to a scheduling cell. That is, the presence or absence of specific field(s) in DCI, the size of DCI, the interpretation method of the terminal, and/or related operations are determined by "the type of cell in which the DCI is transmitted" and/or "the cell in which the DCI is transmitted and scheduled. It may be determined based on a relationship between cells (eg, whether the scheduling cell matches the scheduled cell).
- the specific field may be CIF.
- the DCI format transmitted in the PCell eg, USS set of PCell
- the SCell eg, USS set of SCell
- the same DCI format transmitted may include CIF.
- the payload size of the DCI format monitored by the PCell may be different from the payload size of the same DCI format monitored by the SCell.
- the difference between the payload sizes of the DCI format may be the number of bits of the CIF (eg, up to 3 bits).
- each of the non-fallback DCI formats (eg, DCI formats 0_1, 1_1, 0_2, 1_2) monitored in the USS set may have a plurality (eg, up to two) sizes.
- the bit string insertion for differentiation from the second size may be applied to the DCI format having the same payload size as the second size.
- the DCI size that the UE needs to monitor The total number may be increased. This may cause PDCCH configuration constraints and/or PDCCH capacity reduction.
- DCI format (eg, non-fallback) monitored in the same type of search space set (eg, USS set) for the same cell (eg, the same scheduled cell)
- the DCI format has different payload sizes for a plurality of serving cells (eg, a plurality of scheduling cells)
- the DCI format has one DCI size. It can be considered to have, and the number of DCI sizes can be counted according to the considered sizes.
- a method of aligning the payload size in one serving cell to the payload size in another serving cell in the above-described case may be considered.
- the UE aligns the payload size of the DCI format monitored by the PCell (eg, USS set of PCell) and the payload size of the DCI format monitored by the SCell (eg, USS set of SCell) with each other can do it.
- a predetermined bit string eg, a zero bit string
- a predetermined bit of a length appropriate for the payload of the DCI format (eg, the same length as the CIF of the SCell)
- a column eg, a zero bit string
- the size of the corresponding DCI format may be aligned with the size of the DCI format monitored in the SCell (eg, a USS set of the SCell).
- the predetermined bit string is inserted in the last part of the payload of the DCI format (eg, becomes least significant bit (LSB)(s) of the payload) or inserted in the first part of the payload (eg, For example, it may be the most significant bit(s) of the payload (MSB).
- the position at which the predetermined bit stream is inserted into the DCI format may be the same as the position of the CIF of the same DCI format monitored by the SCell (eg, the USS set of the SCell).
- the field configuration and the size of the fields of DCI formats for a plurality of scheduling cells may be the same.
- the DCI format is CIF (or corresponding to CIF) field or bit string).
- the length of the CIF and/or the location in the payload may be the same for a PCell (eg, USS set of PCell) and SCell (eg, USS set of SCell).
- a serving cell corresponding to each field value (eg, codepoint) of the CIF may also be the same between the PCell and the SCell.
- the CIF of the DCI format transmitted from the PCell may always indicate the PCell, which is the same cell, as the scheduled cell.
- the UE can expect that the CIF value of the DCI format transmitted from the PCell (eg, the USS set of the PCell) always corresponds to the ID of the PCell.
- the UE may regard the serving cell scheduled by the DCI format as the PCell regardless of the serving cell indicated by the CIF value of the DCI format transmitted from the PCell (eg, the USS set of the PCell).
- the UE may compare the total number of sizes of DCI formats determined in the above steps with an upper limit value (eg, X and/or Y) of DCI sizes.
- DCI formats may be DCI formats for C-RNTI (or CS-RNTI, MCS-C-RNTI), in which case an upper limit value Y may be applied.
- the DCI size determination procedure may be terminated.
- the UE may assume the DCI size determined according to the above-described procedure, and may perform blind decoding and reception operations for DCI formats.
- the UE may additionally perform a DCI size alignment procedure and may change the payload size of some DCI format(s).
- the additional DCI size alignment procedure may include a sixth step, a seventh step, an eighth step, etc. to be described later.
- the PDCCH monitoring capability of the UE may be defined based on a scheduled cell (eg, PCell). For example, the UE considers the sum of all DCI sizes in all scheduling cells corresponding to the scheduled cell (eg, PCell) as the total number of DCI sizes for the scheduled cell (eg, PCell). and compare the counted total number to an upper bound on the number of DCI magnitudes (eg, X and/or Y). In this case, the upper limit value may be defined as a single value corresponding to a scheduled cell. Alternatively, the PDCCH monitoring capability of the UE may be defined for each of a plurality of scheduled cells or cell groups.
- the UE may count the total number of DCI sizes for each of the PCell and SCell, which are cells to be scheduled, and may compare the total number of DCI sizes with the upper limit value.
- the upper limit value may be defined as a value corresponding to each scheduled cell or cell group.
- An upper limit value for each cell or cell group to be scheduled may be predefined in a technical standard.
- the upper limit value for each cell or cell group to be scheduled may be set from the base station to the terminal.
- the UE may perform a DCI size alignment procedure. In this case, the DCI size alignment procedure may be performed for the corresponding cell.
- step 6 the UE determines the size (eg, second size) of the uplink fallback DCI format (eg, DCI format 0_0) of the USS set in the uplink fallback DCI format (eg, DCI) of the CSS set. It is possible to align the size (eg, the first size) of the format 0_0), and the size (eg, the second size) of the downlink fallback DCI format (eg, DCI format 1_0) of the USS set is CSS It may be aligned to the size (eg, first size) of the downlink fallback DCI format (eg, DCI format 1_0) of the set. Even when the sixth step is completed, if the total number of DCI sizes exceeds the upper limit value, the seventh step may be performed.
- the UE may align the sizes of non-fallback DCI formats (eg, DCI formats 0_2 and 1_2) of the USS set with each other.
- the above-described procedure may include a procedure for aligning sizes between an uplink non-fallback DCI format (eg, DCI format 0_2) and a downlink non-fallback DCI format (eg, DCI format 1_2).
- the seventh step may include a procedure for aligning the different payload sizes. Even when the seventh step is completed, if the total number of DCI sizes exceeds the upper limit value, the eighth step may be performed.
- the UE may align the sizes of non-fallback DCI formats (eg, DCI formats 0_1 and 1_1) of the USS set with each other.
- the above-described procedure may include a procedure for aligning sizes between an uplink non-fallback DCI format (eg, DCI format 0_1) and a downlink non-fallback DCI format (eg, DCI format 1_1).
- the eighth step may include a procedure for aligning the different payload sizes.
- the terminal may not perform step(s) irrelevant to the DCI format configured to be monitored by the base station. For example, when monitoring of DCI formats 0_2 and 1_2 is not configured in the terminal, the terminal may omit the fourth and seventh steps. The order of some step(s) may be changed. New step(s) may also be added to the steps described above. For example, when monitoring other DCI formats other than the above-described DCI formats is configured in the terminal, the terminal determines the payload size of the corresponding DCI format (eg, other DCI format) and / or an alignment step is added.
- the terminal determines the payload size of the corresponding DCI format (eg, other DCI format) and / or an alignment step is added.
- a serving cell includes a plurality of uplink carriers (eg, one uplink carrier and one supplementary uplink carrier), and a certain DCI format has a different size for a plurality of uplink carriers
- the UE sets the size of the DCI format in one carrier to that of the DCI format in another carrier so that the corresponding DCI format (eg, any DCI format) has the same size for a plurality of uplink carriers.
- An alignment procedure may be additionally performed.
- the alignment of the DCI size may be applied within one scheduling cell.
- the alignment of the DCI size may be applied between a plurality of scheduling cells. Aligning the sizes of monitored DCI formats in one serving cell may help reduce PDCCH reception complexity. For example, "the DCI size is the same in PDCCH candidates belonging to different search space sets (eg, overlapping search space sets) within the same cell, and the corresponding PDCCH candidates are mapped to the same set of CCE(s) and the same scrambling is applied to the corresponding PDCCH candidates", the UE may perform blind decoding only once to monitor the corresponding PDCCH candidates.
- the number of times of performing PDCCH blind decoding may be counted only once, and PDCCH monitoring complexity may be reduced.
- aligning the sizes of DCI formats monitored in different serving cells may not help reduce PDCCH reception complexity.
- PDCCH candidates monitored by different serving cells cannot have the same set of CCE(s). Therefore, even when the DCI size is the same, it may be difficult to detect the DCI through one blind decoding. In this case, the number of times of performing the PDCCH blind decoding may be counted, respectively.
- the UE when DCI formats are monitored in the same serving cell, the UE may perform an operation of aligning (eg, matching) the sizes of corresponding DCI formats to each other, and DCI formats are different in serving cells. In the case of monitoring, the UE may not perform an operation of aligning (eg, matching) the sizes of corresponding DCI formats to each other.
- the fallback DCI format of the CSS set eg, DCI formats 0_0 and 1_0
- the fallback DCI format of the USS set eg For example, DCI formats 0_0 and 1_0
- the terminal may omit the fifth step.
- the fallback DCI format of the CSS set eg, DCI formats 0_0 and 1_0
- the fallback DCI format of the USS set e.g. DCI formats 0_0 and 1_0
- the UE may perform step 5 with respect to the fallback DCI format (eg, DCI formats 0_0 and 1_0) in the USS set of the PCell, and the fallback DCI format (eg, DCI format) in the USS set of the SCell.
- the fifth step may be omitted.
- the UE may perform step 5 for fallback DCI formats in the USS set of the PCell and the USS set of the SCell.
- the first method may be a method of increasing the upper limit of the number of DCI sizes.
- the upper limit of the number of DCI sizes for a scheduled cell eg, PCell
- K may be a natural number.
- the upper limit value for the total number of DCI sizes for a plurality of scheduling cells may increase by K.
- each of the upper limit values for the total number of DCI sizes for each scheduling cell may increase by K1 and K2.
- K1 may be different from K2.
- K1 may coincide with K2.
- the second method may be a method of increasing the upper limit of the number of PDCCH blind decoding that the UE can perform within a reference time and/or the number of receivable CCEs.
- the upper limit of the total number of times of performing PDCCH blind decoding for a plurality of scheduled cells and/or the number of receivable CCEs may increase.
- the upper limit of the number of times of performing PDCCH blind decoding and/or the number of receivable CCEs for each scheduling cell may be predefined or set in the terminal from the base station.
- An upper limit value for at least one scheduling cell may increase.
- the increment of the upper limit value for "K value (or K1, K2 value)" or “the number of times of performing PDCCH blind decoding and/or the number of receivable CCEs" may be defined as the capability of the terminal, and the terminal itself Supported K value(s) (or K1, K2 value(s)), the number of times PDCCH blind decoding is performed, and/or the increment(s) of the upper limit value for the number of receivable CCEs may be reported to the base station. .
- the above-described method may be applied only to some terminals having the capability.
- the third method may be a method of partially changing the counting criteria for the number of times PDCCH blind decoding is performed and/or the number of CCEs.
- the CCE may be a receivable CCE. For example, when PDCCH candidates monitored by different serving cells (eg, a fallback DCI format in the CSS set of the PCell and/or a non-fallback DCI format in the USS set of the SCell) are not processed through a single PDCCH blind decoding Even in this case, if a predetermined condition is satisfied, the UE may count a plurality of PDCCH blind decodings as one PDCCH blind decoding.
- the above-described predetermined condition may include at least one of "a condition in which DCI formats have the same size" and "a condition in which the same scrambling is applied to DCI formats".
- the predetermined condition may not include “a condition in which PDCCH candidates are mapped to the same set of CCEs”.
- the third method may be defined based on the capability of the terminal and may be applied only to some terminals.
- the UE may monitor the fallback DCI format for the PCell in the USS set of the SCell. Meanwhile, the UE may monitor the fallback DCI format for the SCell in the USS set of the SCell. If the fallback DCI format for the PCell and the fallback DCI for the SCell are simultaneously monitored in the USS set of the SCell, it may be difficult for the UE to distinguish whether the received fallback DCI format is for the PCell or the SCell. In order to solve the above-mentioned problem, the CIF may be included in the fallback DCI format.
- the UE may perform a reception operation or a transmission operation of a data channel (eg, PDSCH, PUSCH) scheduled by the corresponding fallback DCI format in a serving cell indicated by the CIF of the received fallback DCI format.
- a data channel eg, PDSCH, PUSCH
- only the fallback DCI format for one serving cell can be monitored in one serving cell (or a specific search space set of the serving cell, a specific search space set type of the serving cell), and this operation is performed to the terminal. can be set.
- monitoring "fallback DCI format for SCell” or "fallback DCI format for PCell" in the SCell is to monitor the terminal. can be set.
- the CIF corresponding to the SCell or PCell may be configured in the UE through higher layer signaling (eg, RRC signaling).
- RRC signaling e.g., RRC signaling
- the group common DCI (or group common PDCCH) for the PCell may be transmitted through the CSS set (eg, Type 3 CSS set) of the PCell.
- the PDCCH capacity of the PCell may be insufficient. Therefore, PDCCH transmission may be offloaded from PCell to SCell, and a cross-carrier indication method for group common DCI (eg, SCell ⁇ PCell) may be considered to support this operation.
- DCI eg, group common DCI
- the CSS set eg, type 3 CSS set
- the UE operates the PCell based on the control information can be performed.
- the above-described operation of the PCell includes an operation according to a slot format instruction, a preemption operation, a power control operation, an uplink transmission cancellation operation, an operation according to a wake-up instruction, an SCell dormancy operation, etc.
- the group common DCI may include DCI formats 2_0, 2_1, 2_2, 2_3, 2_4, 2_5, 2_6, and the like.
- the UE may monitor and receive a DCI including a transmit power control (TPC) command for PUCCH power control of the PCell in the SCell (eg, the type 3 CSS set of the SCell).
- TPC transmit power control
- the UE may monitor and receive DCI including control information indicating a wake-up operation of the PCell in the SCell (eg, the type 3 CSS set of the SCell).
- N BD The maximum number of times (hereinafter, referred to as “N BD ”) and processing (eg, channel estimation) of PDCCH blind decoding (BD) for each reference time for a serving cell (eg, a scheduled cell) is possible
- N CCEs The maximum number of CCEs (hereinafter, referred to as “N CCEs ”) may be defined.
- the reference time may be each slot, each PDCCH monitoring span, or P consecutive slots.
- P may be a natural number.
- One or more PDCCH monitoring spans may be deployed in one slot. There may be slots in which PDCCH monitoring spans are not allocated.
- a slot or PDCCH monitoring span means a slot or PDCCH monitoring span of a scheduling cell (or a bandwidth portion of the scheduling cell (eg, active bandwidth portion, one configured bandwidth portion)) can do.
- Each of N BD and N CCE is the scheduling cell (or, the bandwidth portion of the scheduling cell (eg, active bandwidth portion, configured any one bandwidth portion)) by the numerology (eg, subcarrier interval) can be decided.
- the UE may perform PDCCH monitoring in a plurality of scheduling cells for PDSCH/PUSCH scheduling for one scheduled cell.
- the numerologies eg, subcarrier spacing and/or CP type
- the UE may monitor the search space of the PCell and the SCell for scheduling for the PCell.
- the numerology of the PCell (or the active bandwidth portion of the PCell) may be referred to as the first numerology (or the first subcarrier interval)
- the numerology of the SCell or the active bandwidth portion of the SCell
- is It may be referred to as a second numerology (or second subcarrier spacing).
- BD and CCE counting for the PCell may be performed based on the reference neurology or one scheduling cell (or active bandwidth part) corresponding to the reference neurology.
- Parameters for BD and CCE counting for PCell eg, time units such as slots, PDCCH monitoring spans, N BD , N CCE, etc.
- the reference pneumatology may be a pneumatology having a smaller (or larger) subcarrier spacing among the first pneumology and the second pneumatology.
- the base station may set one of the first neurology and the second neurology as the reference neurology, and may inform the terminal of information on the reference neurology.
- the terminal may check the reference neurology based on the information received from the base station.
- the reference numerology may be a numerology having the smallest (or largest) subcarrier spacing among numerologies corresponding to all bandwidth portions configured for scheduling cells.
- the reference numerology may be a numerology having the smallest (or largest) subcarrier spacing among numerologies corresponding to all bandwidth portions configured in one cell among scheduling cells.
- the terminal may receive information on the reference number from the base station, and the reference number may coincide with one of the numbers used in bandwidth portions set in cells to be scheduled.
- the reference numerology may not match the numerology used in the bandwidth portion activated in the scheduling cells.
- the reference numerology may mean a reference subcarrier interval. According to the above-described method, an integer number of slot(s) may be included in each reference time for each scheduled cell.
- the UE determines the search space set (eg, PDCCH candidates belonging to the search space set) set within the reference time until the total number of PDCCH candidates and the total number of CCEs do not exceed N BD and N CCE for each reference time described above. It can be mapped sequentially.
- the UE may perform a blind decoding operation only on a PDCCH candidate belonging to a mapped search space set, and may omit a blind decoding operation on a PDCCH candidate belonging to an unmapped search space set.
- the UE may map the USS set(s) after preferentially mapping the CSS set(s).
- the terminal may not expect that the CSS set is not mapped. For example, all PDCCH candidates belonging to the CSS set may always be monitored by the UE.
- the search space set (eg, USS set) may be sequentially mapped based on the ID of the search space set (eg, in order of decreasing search space set ID).
- N BD and N CCE are for the PCell in the plurality of scheduling cells. It may mean an upper limit value of the summed number of PDCCH candidates for a search space set monitored for scheduling and an upper limit value of the summed number of CCEs, respectively.
- the terminal sets the search space set within the reference time until the total number of PDCCH candidates and the total number of CCEs for the plurality of scheduled cells for each reference time does not exceed N BD and N CCE (eg, search PDCCH candidates belonging to the spatial set) may be sequentially mapped.
- the search space set configured in the terminal for PCell scheduling may be monitored in one scheduling cell among a plurality of scheduling cells by configuration from the base station. For example, whether cross-carrier scheduling is applied in each set of search spaces monitored for PCell scheduling may be configured in the terminal. If cross-carrier scheduling is not set to be applied to the search space set monitored for PCell scheduling, the search space set may be monitored in the PCell, and the corresponding CORESET in the PCell (eg, CORESET combined by CORESET ID) may be mapped onto On the other hand, when cross-carrier scheduling is set to be applied to a search space set monitored for PCell scheduling, the search space set may be monitored in a scheduling cell other than the PCell (eg, SCell), and another scheduling cell ( For example, in SCell), it may be mapped onto a corresponding CORESET (eg, CORESET combined by CORESET ID). In this case, all search space sets to which cross-carrier scheduling is applied may be monitored in the same cell (eg, one SCell).
- the mapping order of the aforementioned search space set may be determined regardless of whether cross-carrier scheduling is applied in the search space set (eg, a monitored scheduling cell). For example, even when there are a plurality of scheduling cells, a search space set (eg, USS set) having a lower (or higher) ID may be preferentially mapped as in the above-described method.
- the mapping order (or whether to map) of the aforementioned search space set may be determined by whether cross-carrier scheduling is applied in the search space set (eg, a monitored scheduling cell).
- the mapping order (or whether to map) of the search space set (eg, USS set) may be determined by the ID of the search space set and the ID of a cell in which the search space set is monitored.
- FIG. 4 is a conceptual diagram illustrating a mapping method of a search space set in cross-carrier scheduling according to (Method 100).
- a base station may configure a plurality of cells (eg, a first CC and a second CC), and may transmit configuration information of the plurality of cells to the terminal.
- the base station may configure a search space set in each of the plurality of cells, and may transmit configuration information of the search space set to the terminal.
- the first carrier eg, the first CC
- the second carrier eg, the second CC
- the UE may monitor DCI for scheduling the PDSCH or PUSCH of the first carrier in the first carrier and the second carrier.
- the first carrier may be a PCell
- the second carrier may be an SCell.
- different numerologies may be used for the PCell and the SCell.
- the subcarrier spacing (e.g., 15 kHz) applied to the PCell (or bandwidth portion of the PCell) may be less than the subcarrier spacing (e.g. 30 kHz) applied to the SCell (or bandwidth portion of the SCell).
- one slot in the PCell may include a plurality of slots (eg, two slots) in the SCell.
- the first slot of the PCell may include a first slot and a second slot of the SCell.
- PCell's pneumatic or subcarrier spacing (eg, 15 kHz) can be used as the reference pneumologic or reference subcarrier spacing.
- each slot, each span, etc. of the PCell may be regarded as a reference time for PDCCH mapping.
- a monitoring operation in a plurality of cells (eg, search space sets in the plurality of cells) may be completed within a reference time.
- the UE may map the PDCCH candidates of the search space set for PCell scheduling to the PCell and the SCell for a duration corresponding to each slot of the PCell. In this case, the above-described method may be used.
- the UE may first map a first search space set (eg, a first SS set) that is a CSS set among search space sets for scheduling of a PCell set in a corresponding slot.
- the UE may sequentially map the USS sets (eg, the second SS set and the third SS set) among the search space sets for PCell scheduling set in the corresponding slot.
- the mapping order may be determined based on the search space set ID of the USS set.
- the UE preferentially maps the second search space set (eg, the second SS set) of the SCell, which is a USS set having a smaller ID.
- the second search space set may include a plurality of (eg, two) PDCCH monitoring occasions (eg, CORESETs) within a corresponding reference time.
- a plurality of PDCCH monitoring occasions may all be mapped. Alternatively, all of the plurality of PDCCH monitoring occasions may not be mapped.
- the mapping order may be determined based on the search space set ID of the USS set and the ID of a cell (eg, a scheduling cell) to which the USS set is mapped.
- the UE may preferentially map a search space set mapped to a PCell (eg, a cell such as a scheduled cell) over a search space set mapped to an SCell (eg, a cell for cross-carrier scheduling).
- the UE may map a search space set mapped to the SCell (eg, a cell for cross-carrier scheduling) in preference to a search space set mapped to a PCell (eg, the same cell to be scheduled). .
- one of the above two mapping rules may be configured from the base station to the terminal.
- the UE may map the search space set(s) in the order of lower (or higher) search space set IDs with respect to the search space set(s) mapped to the same cell.
- the UE may first map the first search space set, which is the CSS set, and preferentially map the third search space set, which is the USS set, in the PCell under the condition that N BD and N CCE are not exceeded. and the second search space set that is the USS set in the SCell may be mapped to the following.
- the search space sets may be set to exist only in one cell among a plurality of scheduled cells for each reference time.
- the search space sets may be configured only in the PCell at a first reference time (eg, in a first slot) and only in the SCell at a second reference time (eg, in a second slot).
- the UE may map the search space sets by the method described above in one cell (eg, a scheduling cell) to which the search space sets are mapped for each reference time.
- the above-described method can be applied to all search space sets configured for scheduling of the PCell.
- the above-described method may be applied only to some of the search space sets (eg, USS sets) configured for scheduling of the PCell.
- the CSS set mapped to the PCell and the USS set mapped to the SCell may be set together within the same reference time.
- the terminal may receive information instructing to switch (or change) the bandwidth portion from the base station.
- the terminal may switch the bandwidth portion from the current bandwidth portion (hereinafter, referred to as “first bandwidth portion”) to another bandwidth portion (hereinafter referred to as “second bandwidth portion”).
- a time point at which the terminal performs a transmission/reception operation in the second bandwidth portion may be a specific time point of a specific slot (eg, the first symbol of a specific slot).
- the terminal may receive information indicating a specific slot in which the transmission/reception operation starts in the second bandwidth portion from the base station.
- a specific slot may be indicated by DCI, and the UE may regard a slot in which PDSCH or PUSCH is scheduled (or the first slot among slots in which PDSCH or PUSCH is scheduled) as a specific slot. That is, the specific slot may be a slot scheduled by DCI.
- the start time of the transmission/reception operation in the switched second bandwidth portion may be a specific time point (eg, the first symbol) of the first slot.
- the start time of the transmission/reception operation in the switched second bandwidth portion may be a specific time point (eg, the first symbol) of the first slot or the second slot.
- the bandwidth partial switching of the SCell may occur within the first slot of the PCell, which is a reference time for search space set mapping.
- the terminal may perform transmission/reception operation for the first bandwidth portion in the first slot of the SCell belonging to the first slot of the PCell, and may perform the transmission/reception operation for the second bandwidth portion in the second slot of the SCell belonging to the first slot of the PCell.
- a transmission/reception operation may be performed.
- the discovery space set setting for the first bandwidth part may be applied to the first slot of the SCell
- the discovery space set setting for the second bandwidth part may be applied to the second slot of the SCell.
- the search space set setting may be changed within the reference time.
- each reference time does not include the complete slot(s) of the SCell.
- a certain slot may not be completely included in one reference time. That is, in the SCell, a certain slot may be included in a plurality of reference times.
- the slot boundary of the PCell and the slot boundary of the SCell may not be aligned. That is, the time in the PCell may deviate from the time in the SCell.
- FIG. 5 is a conceptual diagram illustrating a method of switching a bandwidth portion in cross-carrier scheduling according to (Method 100).
- the base station may configure a plurality of cells (eg, a first CC and a second CC), and may transmit configuration information of the plurality of cells to the terminal.
- the base station may configure a search space set in each of the plurality of cells, and may transmit configuration information of the search space set to the terminal.
- the first carrier eg, the first CC
- the second carrier eg, the second CC
- the UE may monitor DCI for scheduling the PDSCH or PUSCH of the first carrier in the first carrier and the second carrier.
- the first carrier may be a PCell
- the second carrier may be an SCell. In this case, bandwidth partial switching may be applied in the SCell.
- the terminal may perform bandwidth partial switching from the first bandwidth portion (eg, first BWP) to the second bandwidth portion (eg, second BWP) according to the bandwidth partial switching instruction or setting, and the second bandwidth In this part, the transmission/reception operation may be performed from the fourth slot.
- first bandwidth portion eg, first BWP
- second bandwidth portion eg, second BWP
- the slot boundary of the PCell and the slot boundary of the SCell may not be aligned with each other from the time when the bandwidth partial switching of the SCell is completed.
- the slot of the SCell may not be completely included in each slot of the PCell (eg, a reference time for search space set mapping).
- the fourth slot of the SCell may be included in both the second slot and the third slot of the PCell. That is, a part of the fourth slot of the SCell may be included in the second slot of the PCell, and the remainder of the fourth slot of the SCell may be included in the third slot of the PCell.
- Each of the second slot and the third slot of the PCell may be considered a reference time.
- the mapping method of the search space set by the above-described method may be difficult to perform.
- the mapping method of the search space set may be transformed into a complex form and performed.
- the application time of bandwidth partial switching for the scheduling cell is limited can be Specifically, the timing at which the switching to the second bandwidth part in the scheduling cell is completed (or the timing when the transmission/reception operation of the second bandwidth part starts) is determined by some slots (eg, reference A slot having a start time aligned with the boundary of the view) or a specific time of some slot (eg, the first symbol) may be limited.
- some slots eg, reference A slot having a start time aligned with the boundary of the view
- a specific time of some slot eg, the first symbol
- a time point at which switching to the second bandwidth portion is completed in each scheduled cell is the reference number (or a cell or bandwidth corresponding to the reference number). Part) may be limited to a slot having a start time aligned with a slot boundary by a slot or a specific time point (eg, the first symbol) of the corresponding slot. According to the above-described method, switching of the bandwidth portion may not occur within the reference time, and no change in the search space set setting or the change in the numerology applied to transmission of the search space set may occur within the reference time. have. Accordingly, the above-described method of mapping the search space set can be easily performed.
- the above-described method of limiting the application timing of partial bandwidth switching may be equally applied to the activation timing or inactivity timing of a scheduled cell. That is, the activation time of the scheduling cell (or the time of starting the transmission/reception operation in the activated scheduling cell) is a starting time aligned with the boundary between some slots (eg, the reference time point) among the slots of the corresponding scheduling cell.
- a slot having a starting point aligned with a slot boundary by a reference numerology (or a cell or bandwidth portion corresponding to the reference numerology), or a specific timing of some slots (eg, the first symbol) ) may be limited.
- Activation or deactivation of the scheduled cell may be configured in the UE through higher layer signaling (eg, RRC signaling, MAC CE signaling). Alternatively, activation or deactivation of the scheduled cell may be instructed to the UE through DCI.
- DCI may include information indicating activation or deactivation of a scheduling cell.
- the DCI may include information indicating bandwidth partial switching of a scheduling cell.
- the above-described activation and deactivation operations may refer to transition operations to a dormancy or non-dormancy (or active) state.
- the DCI may include information instructing to switch from the first bandwidth portion to the second bandwidth portion in a cell scheduled by the UE, the first bandwidth portion may be a dormant bandwidth portion, and the second bandwidth portion may be a non-dormant (or active) bandwidth portion.
- the first bandwidth portion may be a non-dormant (or active) bandwidth portion, and the second bandwidth portion may be a dormant bandwidth portion.
- the transition to an activated or deactivated state (or a dormant or non-dormant state) of a scheduled cell within a reference time may not occur, and the above-described method of mapping the search space set can be easily performed. have.
- the method of limiting the application time of the bandwidth partial switching described above may be equally applied to the application time of the search space set group (SSSG) switching of the terminal in the scheduling cell.
- the terminal may switch the SSSG it monitors according to a setting or instruction from the base station.
- SSSG switching may be performed based on a slot boundary.
- the SSSG switching time eg, the time when the UE starts monitoring the changed SSSG (eg, slot)
- the slots eg, the boundary of the reference time
- a slot having a start time aligned with a slot having a start time aligned with a slot boundary by a reference numerology (or a cell or bandwidth portion corresponding to the reference numerology), or a specific timing of some slots (e.g. For example, it may be limited to the first symbol).
- SSSG switching may be indicated to the UE through DCI (eg, DCI for scheduling PDSCH, DCI for scheduling PUSCH, group common DCI (eg, DCI format 2_0), etc.).
- DCI eg, DCI for scheduling PDSCH, DCI for scheduling PUSCH, group common DCI (eg, DCI format 2_0), etc.
- the SSSG may not be switched within the reference time, and the above-described method of mapping the search space set may be easily performed.
- the UE can improve PDSCH reception performance by assuming that the PDSCH DM-RS is QCL with another reference signal or SS/PBCH block.
- the terminal may determine "TCI state information configured or indicated by the base station" or "QCL source and QCL type for PDSCH based on a predetermined rule".
- the QCL applied to the PDSCH may vary according to a scheduling offset value.
- the scheduling offset may mean a distance or a symbol offset between a DCI reception time (eg, the last symbol of DCI) and a PDSCH reception time (eg, a PDSCH start symbol).
- the scheduling offset is greater than or equal to a reference value (threshold)
- the QCL of the PDSCH may follow the TCI state indicated through the scheduling DCI or the TCI state (or QCL) of the CORESET in which the scheduling DCI is transmitted.
- the scheduling offset is smaller than the reference value, the QCL of the PDSCH may follow the default QCL.
- the TCI state information(s) configured for the PDSCH includes a reception beam-related QCL parameter (eg, QCL type D)
- a QCL application operation according to a scheduling offset may be performed. Otherwise, the QCL of the PDSCH may be determined regardless of the scheduling offset.
- the reference value for QCL application may be defined as the capability of the terminal, and the terminal may report the reference value(s) supported by the terminal to the base station. Alternatively, the reference value may be set in the terminal from the base station.
- the reference value may mean a time required for the UE to decode the PDCCH plus a beam switching time, and may be defined as the number of symbols.
- the UE may assume a default QCL (eg, a default beam) for a time interval (eg, symbols) corresponding to a reference value from the next symbol of the monitored CORESET, and based on the above-mentioned assumption, a downlink signal (eg, PDSCH) may be received.
- a default QCL eg, a default beam
- a time interval eg, symbols
- a downlink signal eg, PDSCH
- a time interval in which a default QCL for the PDSCH is assumed may be referred to as a “default beam interval”. If DCI scheduling the PDSCH is detected within the default beam interval, the UE may apply a default QCL (eg, a default beam) to the entire PDSCH interval, and may receive the PDSCH based on the default QCL.
- a default QCL eg, a default beam
- the UE may monitor the scheduling DCI for the PCell in a plurality of serving cells (eg, PCell and SCell).
- the default beam interval may be determined by CORESETs (eg, time resources of CORESETs) belonging to a plurality of serving cells.
- CORESET may mean a CORESET, a PDCCH candidate, a search space set, a PDCCH monitoring occasion, etc. that the UE monitors for PDSCH reception.
- FIG. 6 is a conceptual diagram illustrating a first application method of a PDSCH default QCL by a plurality of serving cells
- FIG. 7 is a conceptual diagram illustrating a second application method of a PDSCH default QCL by a plurality of serving cells.
- the base station may configure a plurality of cells (eg, a first CC and a second CC), and may transmit configuration information of the plurality of cells to the terminal.
- the base station may configure a search space set in each of the plurality of cells, and may transmit configuration information of the search space set to the terminal.
- the first and second carriers may be aggregated in the terminal.
- the first carrier may be a PCell
- the second carrier may be an SCell.
- the UE may perform PDCCH monitoring in the PCell and the SCell for scheduling of the PCell.
- the UE selects a default QCL in a default beam interval determined by each CORESET of the PCell and a default beam interval determined by each CORESET of the SCell (eg, the union of default beam intervals).
- the UE may assume the default QCL in the first default beam interval determined by the first CORESET belonging to the PCell and the second default beam interval determined by the second CORESET belonging to the SCell, and the downlink of the PCell based on the default QCL A link signal (eg, PDSCH) may be received.
- each default beam interval may be determined by the reference value of the scheduling offset of the PDSCH by the above-described method.
- the length of the default beam interval may be determined by the capability report of the UE and the numerology of the serving cell (eg, cell to which CORESET belongs). Therefore, for the same UE, the length of the default beam interval may be the same or different for each serving cell to which CORESET belongs.
- the length of the first default beam section may be referred to as T1
- the length of the second default beam section may be referred to as T2. That is, the reference value of the scheduling offset for the first CORESET may be T1, and the reference value of the scheduling offset for the second CORESET may be T2.
- T1 and T2 may generally be different from each other.
- T1 may be the same as T2.
- T1 and T2 may have the same value.
- T1 and T2 may have different values.
- T1 and T2 may have the same value irrespective of the number of scheduling cells, and may be determined based on the number of one cell (or a bandwidth portion of the cell) among scheduling cells.
- the numerology may include a subcarrier spacing and/or a CP type.
- the default beam interval (eg, the first default beam interval) determined by CORESET of the PCell is the default beam interval determined by CORESET of the SCell (eg, the second default beam) section) may overlap.
- the default QCL by CORESET eg, self-scheduling
- one serving cell eg, PCell
- the UE may apply the same default QCL to the first and second default beam sections.
- the UE may apply the default QCL by the CORESET (eg, the first CORESET) of the PCell to the first and second default beam intervals.
- the UE may apply the default QCL by the SCell CORESET (eg, the second CORESET) to the first and second default beam intervals.
- the UE is irrespective of the default QCL by the CORESET (eg, the first CORESET) of the PCell and the default QCL by the CORESET (eg, the second CORESET) of the SCell in the first and second default beam intervals
- An independently determined default QCL may be applied.
- the UE may use one default QCL (eg, a common default QCL) for PDSCH reception for a plurality of serving cells. That is, one default QCL may be applied to one scheduled cell (ie, PCell) regardless of whether the default beam intervals overlap.
- a default QCL may be individually applied to each of the default beam intervals for a plurality of scheduling cells.
- the UE may apply a default QCL by CORESET (eg, first CORESET) of the PCell in the first default beam interval, and the SCell in the second default beam interval
- the default QCL by the CORESET eg, the second CORESET
- one default QCL may be applied in a section in which the first default beam section and the second default beam section overlap.
- One default QCL may be one of a default QCL by CORESET (eg, first CORESET) of the PCell and a default QCL by CORESET (eg, second CORESET) of the SCell.
- one default QCL may be a default QCL independently determined regardless of default QCLs.
- the default QCL may be used for only one scheduling cell.
- the scheduling offset of the PDSCH may be allowed for the scheduling offset of the PDSCH to have a value smaller than the reference value.
- the UE can expect that the scheduling offset of the PDSCH is always equal to or greater than the reference value.
- the default QCL of the aforementioned PDSCH may be determined as a QCL applied to a specific control channel.
- the default QCL of the PDSCH may be a QCL applied to a specific control channel determined based on a time point to which the default beam section belongs (eg, a slot to which the default beam section belongs).
- the UE considers the TCI state or QCL of a specific CORESET (eg, CORESET having the smallest ID) included in the most recent slot including at least one CORESET as the default QCL of the PDSCH.
- the most recent slot may be the most recent slot including at least one CORESET among slots preceding the slot to which the default beam period belongs.
- the most recent slot may be the most recent slot including at least one CORESET from among the slot to which the default beam period belongs and the slots preceding the corresponding slot.
- the default QCL of the PDSCH may follow one of the TCI state(s) configured or activated for the PDSCH.
- the default QCL of the PDSCH may follow one TCI state (eg, the TCI state having the lowest ID) among the activated TCI state(s) for the PDSCH.
- the default QCL of the PDSCH may be determined by a combination of the TCI state (or QCL) of the control channel and the TCI state for the PDSCH. For example, if there is slot(s) including at least one CORESET within the time window, the terminal has a specific CORESET (eg, having the smallest ID) included in the most recent slot among the corresponding slot(s).
- the TCI state or QCL of CORESET may be considered as the default QCL of the PDSCH.
- the default QCL of the PDSCH is one of the TCI state(s) (eg, activated TCI state(s)) for the PDSCH (eg, The TCI state having the lowest ID or the TCI state set for the corresponding purpose by the base station) may be followed.
- the position of the time window may be determined based on the slot to which the CORESET monitored for the corresponding PDSCH scheduling belongs (or the slot to which the default beam period belongs).
- the time window may be defined as L slot(s) before the slot to which the CORESET monitored for the corresponding PDSCH scheduling belongs (or the slot to which the default beam period belongs). L may be a natural number.
- the time window includes a slot to which the CORESET monitored for the corresponding PDSCH scheduling belongs (or a slot to which a default beam interval belongs) and (M-1) number of slot(s) before the corresponding slot (eg, a total of M slots) )) can be defined as M may be a natural number.
- L and/or M may be predefined in the standard.
- the base station may set L and/or M to the terminal.
- the L slots or M slots may be physically contiguous slots.
- the UE may generate a HARQ-ACK codebook including HARQ-ACK information of the PDSCH, and may report the HARQ-ACK codebook to the base station.
- the HARQ-ACK codebook is a HARQ-ACK codebook having a semi-static size (hereinafter referred to as "Type 1 HARQ-ACK codebook") and a HARQ-ACK codebook having a dynamic size (hereinafter, "Type 2 HARQ-ACK codebook"). ) can be classified as
- the HARQ-ACK codebook (or payload) may consist of a bit string, and each bit of the bit string may correspond to one piece of downlink HARQ-ACK information.
- the size of the HARQ-ACK codebook may be 1 or more.
- a Type 2 HARQ-ACK codebook may be generated for a set of PDCCH monitoring occasion(s). Each bit of the type 2 HARQ-ACK codebook may correspond to each PDCCH monitoring occasion for which the terminal receives DCI (or the terminal considers that the base station transmits DCI). PDCCH monitoring occasions may be indexed in ascending order of the cell ID (eg, physical layer cell ID) of the serving cell, and then indexed in ascending order of the start time (eg, start symbol) of the search space set. have. HARQ-ACK information corresponding in the order of the index of the PDCCH monitoring occasion may constitute the payload of the type 2 HARQ-ACK codebook.
- the cell ID eg, physical layer cell ID
- start time eg, start symbol
- each serving cell may be a scheduled cell, and the cell ID of each serving cell may be the cell ID of each scheduled cell.
- one PDCCH monitoring occasion may be assumed for each serving cell (eg, a scheduled cell).
- the UE may monitor the scheduling DCI for the PCell in a plurality of serving cells (eg, PCell and SCell).
- a plurality of serving cells eg, PCell and SCell.
- FIG. 8 is a conceptual diagram illustrating a PDSCH scheduling method by a plurality of serving cells.
- the base station may configure a plurality of cells (eg, a first CC and a second CC), and may transmit configuration information of the plurality of cells to the terminal.
- the base station may configure a search space set in each of the plurality of cells, and may transmit configuration information of the search space set to the terminal.
- the first and second carriers may be aggregated in the terminal.
- the first carrier may be a PCell
- the second carrier may be an SCell.
- the UE may perform PDCCH monitoring in the PCell and the SCell for scheduling of the PCell.
- the PDCCH monitoring occasions configured in the plurality of serving cells may overlap in time and may be started at the same time point.
- the PDCCH monitoring occasion eg, first PDCCH MO (monitoring occasion)
- the PDCCH monitoring occasion eg, the second PDCCH MO
- the UE may receive the DCI for the PCell in the first PDCCH monitoring occasion (eg, the first PDCCH MO), and may receive the first PDSCH based on the received DCI.
- the UE may receive DCI for the PCell in the second PDCCH monitoring occasion (eg, the second PDCCH MO), and may receive the second PDSCH based on the received DCI.
- the UE may receive scheduling information of the PDSCH in each of a plurality of PDCCH monitoring occasions having the same starting time in different serving cells for one scheduled cell (eg, PCell).
- HARQ- of PDSCHs (eg, first PDSCH and second PDSCH) from a plurality of PDCCH monitoring occasions having the same starting time in different serving cells for one scheduled cell (eg, PCell)
- ACK information may be multiplexed in the same HARQ-ACK codebook (eg, type 2 HARQ-ACK codebook), and the HARQ-ACK codebook is transmitted to the base station through the same uplink channel (eg, PUCCH, PUSCH).
- the PDCCH monitoring occasion(s) corresponding to the same type 2 HARQ-ACK codebook is the cell ID of the scheduling cell, the cell ID of the scheduled cell, and/or the start time of the search space set. (eg, start symbol).
- the PDCCH monitoring occasion may be indexed in ascending order of the cell ID of the scheduling cell (or scheduled cell), and will be indexed in ascending order of the cell ID of the next scheduled cell (or scheduling cell). and finally indexed in ascending order of the start time of the search space set.
- the PDCCH monitoring occasion(s) corresponding to the same type 2 HARQ-ACK codebook is a cell ID of a serving cell (eg, a scheduled cell), a start time of a search space set (eg, a start symbol), And/or it may be indexed according to a transmission time of the PDSCH (eg, a start time, a start symbol).
- the PDCCH monitoring occasion may be indexed in ascending order of the cell ID of the serving cell (eg, the scheduled cell), then may be indexed in ascending order of the start time of the search space set, and finally the PDSCH may be indexed in an ascending order of transmission time (eg, start time) of .
- the above-described indexing order of the PDCCH monitoring occasion may be merely an example, and the indexing of the PDCCH monitoring occasion may be performed in another order.
- the above-described indexing in ascending order may be merely an example, and indexing of the PDCCH monitoring occasion may also be performed in descending order or the like.
- PDSCHs eg, first PDSCH and second PDSCH scheduled from a plurality of PDCCH monitoring occasions having the same start time in different serving cells
- DAI downlink association index
- C-DAI counter DAI
- T-DAI total DAI
- the UE can expect that up to one PDSCH is scheduled from PDCCH monitoring occasions having the same start time in different serving cells for one scheduled cell (eg, PCell). For example, the UE may not expect a plurality of PDSCHs to be scheduled from PDCCH monitoring occasions having the same start time.
- the base station may transmit the scheduling DCI for the PCell only in one of the first PDCCH monitoring occasion and the second PDCCH monitoring occasion. The UE may assume the above-described operation of the base station, and may perform the PDCCH monitoring operation for the PCell according to the assumption.
- the terminal may receive only one PDSCH of the first and second PDSCHs, and may report a type 2 HARQ-ACK codebook including HARQ-ACK information for the received PDSCH to the base station.
- the index of the PDCCH monitoring occasion may be determined by the cell ID of the serving cell (eg, scheduled cell) and/or the start time (eg, start symbol) of the search space set as described above. .
- Cross-carrier scheduling from SCell to PCell can be dynamically activated or deactivated.
- self scheduling eg, self-scheduling from PCell
- cross-carrier scheduling eg, For example, cross-carrier scheduling from SCell
- the above-described scheduling method may be dynamically activated or deactivated. For example, whether to apply the embodiments of (Method 100) may be dynamically indicated to the terminal.
- the cell in which the UE monitors the CSS set for PCell scheduling may be fixed to the PCell, and the cell in which the UE monitors the USS set may be dynamically switched to the PCell or the SCell.
- the above-described operation may be performed through switching of the bandwidth portion.
- the above-described operation may be performed through bandwidth partial switching of the SCell, which is a cell for cross-carrier scheduling of the PCell. This operation may be referred to as (method 200). Below (Method 200) will be described in detail.
- the terminal may receive configuration information of a plurality of bandwidth portions of the SCell. That is, in the SCell, a plurality of bandwidth portions may be configured in the terminal.
- the plurality of bandwidth portions may include first and second bandwidth portions.
- the first bandwidth portion may be configured to perform cross-carrier scheduling for the PCell. That is, monitoring the scheduling DCI for the PCell in the search space set of the first bandwidth portion may be configured in the UE.
- the second bandwidth portion may not be configured to perform cross-carrier scheduling for the PCell. That is, not monitoring the scheduling DCI for the PCell in the search space set of the second bandwidth portion may be configured in the UE. According to this, whether cross-carrier scheduling is applied may be set in units of a bandwidth portion of a scheduling cell.
- Each of the first and second bandwidth portions in the SCell may be dynamically activated or deactivated. Dynamic bandwidth portion switching from the first bandwidth portion to the second bandwidth portion may be performed. Alternatively, dynamic bandwidth portion switching from the second bandwidth portion to the first bandwidth portion may be performed. In an embodiment, without loss of generality, only dynamic bandwidth portion switching from the second bandwidth portion to the first bandwidth portion may be considered.
- Cross-carrier scheduling from SCell to PCell may be deactivated by switching from the first bandwidth portion to the second bandwidth portion.
- Cross-carrier scheduling from SCell to PCell may be activated by switching from the second bandwidth portion to the first bandwidth portion.
- switching between the first bandwidth portion and the second bandwidth portion may be indicated to the UE by DCI (eg, non-fallback DCI) or DCI format (eg, non-fallback DCI format).
- the non-fallback DCI format may include DCI formats 0_1, 1_1, 0_2, 1_2, and the like.
- the first or second bandwidth portion may be activated and the remaining bandwidth portion may be deactivated according to the bandwidth portion indicator of the non-fallback DCI format.
- the non-fallback DCI format may be transmitted through the SCell. Alternatively, the non-fallback DCI format may be transmitted through a PCell or other serving cell.
- the non-fallback DCI format may be DCI or scheduling DCI for any serving cell.
- the non-fallback DCI format may be limited to a scheduling DCI for a specific serving cell (eg, PCell).
- switching between the first bandwidth portion and the second bandwidth portion may be indicated to the UE by a group common DCI or a group common DCI format (eg, DCI format 2_X, X is an integer greater than or equal to 0).
- DCI format 2_6 For example, switching between the first bandwidth portion and the second bandwidth portion may be triggered by DCI format 2_6.
- the above-described method may be performed for a plurality of serving cells (eg, a plurality of scheduling cells for the same scheduled cell).
- the PCell may be cross-carrier scheduled by a plurality of SCells, and activation or deactivation of cross-carrier scheduling of the plurality of SCells may be indicated through one DCI format.
- a timer may be set in the terminal for switching the bandwidth portion of the SCell.
- the terminal may perform bandwidth partial switching from the first bandwidth portion to the second bandwidth portion.
- the terminal may perform partial bandwidth switching from the second bandwidth portion to the first bandwidth portion.
- the bandwidth portion activated by the timer may be a fallback bandwidth portion, and the fallback bandwidth portion may be configured in the terminal. The timer may be started or restarted when the first or second bandwidth portion is activated.
- the methods according to the present invention may be implemented in the form of program instructions that can be executed by various computer means and recorded in a computer-readable medium.
- the computer-readable medium may include program instructions, data files, data structures, etc. alone or in combination.
- the program instructions recorded on the computer-readable medium may be specially designed and configured for the present invention, or may be known and available to those skilled in the art of computer software.
- Examples of computer-readable media include hardware devices specially configured to store and execute program instructions, such as ROM, RAM, flash memory, and the like.
- Examples of program instructions include not only machine language codes such as those generated by a compiler, but also high-level language codes that can be executed by a computer using an interpreter or the like.
- the hardware device described above may be configured to operate as at least one software module to perform the operations of the present invention, and vice versa.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- Electromagnetism (AREA)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
- Radar Systems Or Details Thereof (AREA)
- Reduction Or Emphasis Of Bandwidth Of Signals (AREA)
Abstract
Description
Claims (20)
- 통신 시스템에서 단말의 동작 방법으로서,복수의 셀들의 설정 정보를 기지국으로부터 수신하는 단계;상기 복수의 셀들 중에서 제1 셀에 설정되고 상기 제1 셀의 스케줄링을 위한 제1 탐색 공간 집합의 설정 정보를 상기 기지국으로부터 수신하는 단계;상기 복수의 셀들 중에서 제2 셀에 설정되고 상기 제1 셀의 스케줄링을 위한 제2 탐색 공간 집합의 설정 정보를 상기 기지국으로부터 수신하는 단계;상기 제1 탐색 공간 집합에 대한 제1 모니터링 동작과 상기 제2 탐색 공간 집합에 대한 제2 모니터링 동작을 수행함으로써, 상기 제1 탐색 공간 집합 및 상기 제2 탐색 공간 집합 중 하나의 탐색 공간 집합에서 DCI(downlink control information)를 상기 기지국으로부터 수신하는 단계; 및상기 제1 셀에서 상기 DCI에 기초하여 데이터 채널을 상기 기지국으로부터 수신하는 단계를 포함하며,상기 제1 탐색 공간 집합 및 상기 제2 탐색 공간 집합은 USS(UE-specific search space) 집합인, 단말의 동작 방법.
- 청구항 1에 있어서,상기 제1 모니터링 동작은 상기 제1 탐색 공간 집합에 포함된 PDCCH(physical downlink control channel) 후보(들)에 대한 블라인드 복호 동작을 포함하고, 상기 제2 모니터링 동작은 상기 제2 탐색 공간 집합에 포함된 PDCCH 후보(들)에 대한 블라인드 복호 동작을 포함하며, 상기 제1 모니터링 동작과 상기 제2 모니터링 동작은 기준 시간 내에서 모두 수행되는, 단말의 동작 방법.
- 청구항 2에 있어서,상기 기준 시간마다 상기 제1 셀의 스케줄링을 위한 PDCCH 블라인드 복호 횟수의 상한 값이 적용되며, 상기 기준 시간은 상기 제1 셀 및 상기 제2 셀에 적용되는 부반송파 간격에 따라 상기 제1 셀 및 상기 제2 셀 중 어느 하나의 셀의 1개 슬롯으로 결정되는, 단말의 동작 방법.
- 청구항 1에 있어서,상기 데이터 채널은 유니캐스트 데이터를 포함하는 PDSCH(physical downlink shared channel)인, 단말의 동작 방법.
- 청구항 1에 있어서,상기 단말의 동작 방법은,상기 제1 셀에 설정되고 상기 제1 셀의 스케줄링을 위한 제3 탐색 공간 집합의 설정 정보를 상기 기지국으로부터 수신하는 단계를 더 포함하며,모니터링 동작들은 상기 제1 탐색 공간 집합, 상기 제2 탐색 공간 집합, 및 상기 제3 탐색 공간 집합에 대해 수행되고, 상기 제3 탐색 공간 집합은 CSS(common search space) 집합인, 단말의 동작 방법.
- 청구항 1에 있어서,상기 제1 탐색 공간 집합에서 모니터링되는 제1 DCI 포맷의 크기와 상기 제2 탐색 공간 집합에서 모니터링되는 상기 제1 DCI 포맷의 크기가 정렬되도록, 상기 제1 탐색 공간 집합에서 모니터링되는 상기 제1 DCI 포맷 또는 상기 제2 탐색 공간 집합에서 모니터링되는 상기 제1 DCI 포맷에 제로 패딩이 적용되고, 상기 DCI는 상기 제1 DCI 포맷인, 단말의 동작 방법.
- 청구항 6에 있어서,상기 제1 DCI 포맷의 모니터링 동작은 상기 기지국으로부터의 RRC(radio resource control) 메시지에 의해 설정되고, 상기 제1 DCI 포맷은 DCI 포맷 1_1 또는 DCI 포맷 1_2인, 단말의 동작 방법.
- 청구항 1에 있어서,상기 DCI 내에서 하나 이상의 필드들의 존재 여부는 상기 DCI가 수신된 탐색 공간 집합 또는 셀에 따라 결정되는, 단말의 동작 방법.
- 청구항 8에 있어서,상기 하나 이상의 필드들은 CIF(carrier indicator field)를 포함하는, 단말의 동작 방법.
- 청구항 1에 있어서,상기 제1 셀은 프라이머리 셀이고, 상기 제2 셀은 세컨더리 셀인, 단말의 동작 방법.
- 통신 시스템에서 기지국의 동작 방법으로서,복수의 셀들의 설정 정보를 단말에 전송하는 단계;상기 복수의 셀들 중에서 제1 셀에 설정되고 상기 제1 셀의 스케줄링을 위한 제1 탐색 공간 집합의 설정 정보를 상기 단말에 전송하는 단계;상기 복수의 셀들 중에서 제2 셀에 설정되고 상기 제1 셀의 스케줄링을 위한 제2 탐색 공간 집합의 설정 정보를 상기 단말에 전송하는 단계;상기 제1 탐색 공간 집합 및 상기 제2 탐색 공간 집합 중 하나의 탐색 공간 집합에서 DCI(downlink control information)를 상기 단말에 전송하는 단계; 및상기 제1 셀에서 상기 DCI에 기초하여 데이터 채널을 상기 단말에 전송하는 단계를 포함하며,상기 제1 탐색 공간 집합 및 상기 제2 탐색 공간 집합은 USS(UE-specific search space) 집합인, 기지국의 동작 방법.
- 청구항 11에 있어서,상기 데이터 채널은 유니캐스트 데이터를 포함하는 PDSCH(physical downlink shared channel)인, 기지국의 동작 방법.
- 청구항 11에 있어서,상기 기지국의 동작 방법은,상기 제1 셀에 설정되고 상기 제1 셀의 스케줄링을 위한 제3 탐색 공간 집합의 설정 정보를 상기 단말에 전송하는 단계를 더 포함하며,상기 DCI는 상기 제1 탐색 공간 집합, 상기 제2 탐색 공간 집합, 및 상기 제3 탐색 공간 집합 중 하나의 탐색 공간 집합에서 전송되고, 상기 제3 탐색 공간 집합은 CSS(common search space) 집합인, 기지국의 동작 방법.
- 청구항 11에 있어서,상기 제1 탐색 공간 집합에서 모니터링 대상인 제1 DCI 포맷의 크기와 상기 제2 탐색 공간 집합에서 모니터링 대상인 상기 제1 DCI 포맷의 크기가 정렬되도록, 상기 제1 탐색 공간 집합에서 모니터링 대상인 상기 제1 DCI 포맷 또는 상기 제2 탐색 공간 집합에서 모니터링 대상인 상기 제1 DCI 포맷에 제로 패딩이 적용되고, 상기 DCI는 상기 제1 DCI 포맷인, 기지국의 동작 방법.
- 청구항 14에 있어서,상기 제1 DCI 포맷의 모니터링 동작은 상기 기지국으로부터의 RRC(radio resource control) 메시지에 의해 설정되고, 상기 제1 DCI 포맷은 DCI 포맷 1_1 또는 DCI 포맷 1_2인, 기지국의 동작 방법.
- 청구항 11에 있어서,상기 DCI 내에서 하나 이상의 필드들의 존재 여부는 상기 DCI가 전송된 탐색 공간 집합 또는 셀에 따라 결정되고, 상기 하나 이상의 필드들은 CIF(carrier indicator field)를 포함하는, 기지국의 동작 방법.
- 청구항 11에 있어서,상기 제1 셀은 프라이머리 셀이고, 상기 제2 셀은 세컨더리 셀인, 기지국의 동작 방법.
- 단말로서,프로세서(processor);상기 프로세서와 전자적(electronic)으로 통신하는 메모리(memory); 및상기 메모리에 저장되는 명령들(instructions)을 포함하며,상기 명령들이 상기 프로세서에 의해 실행되는 경우, 상기 명령들은 상기 단말이,복수의 셀들의 설정 정보를 기지국으로부터 수신하고;상기 복수의 셀들 중에서 제1 셀에 설정되고 상기 제1 셀의 스케줄링을 위한 제1 탐색 공간 집합의 설정 정보를 상기 기지국으로부터 수신하고;상기 복수의 셀들 중에서 제2 셀에 설정되고 상기 제1 셀의 스케줄링을 위한 제2 탐색 공간 집합의 설정 정보를 상기 기지국으로부터 수신하고;상기 제1 탐색 공간 집합에 대한 제1 모니터링 동작과 상기 제2 탐색 공간 집합에 대한 제2 모니터링 동작을 수행함으로써, 상기 제1 탐색 공간 집합 및 상기 제2 탐색 공간 집합 중 하나의 탐색 공간 집합에서 DCI(downlink control information)를 상기 기지국으로부터 수신하고; 그리고상기 제1 셀에서 상기 DCI에 기초하여 데이터 채널을 상기 기지국으로부터 수신하는 것을 야기하도록 동작하고,상기 제1 탐색 공간 집합 및 상기 제2 탐색 공간 집합은 USS(UE-specific search space) 집합인, 단말.
- 청구항 18에 있어서,상기 제1 모니터링 동작과 상기 제2 모니터링 동작은 기준 시간 내에서 모두 수행되고, 상기 기준 시간은 상기 제1 셀 및 상기 제2 셀에 적용되는 부반송파 간격에 따라 상기 제1 셀 및 상기 제2 셀 중 어느 하나의 셀의 1개 슬롯으로 결정되는, 단말.
- 청구항 18에 있어서,상기 명령들은 상기 단말이,상기 제1 셀에 설정되고 상기 제1 셀의 스케줄링을 위한 제3 탐색 공간 집합의 설정 정보를 상기 기지국으로부터 수신하는 것을 더 야기하도록 동작하고,모니터링 동작들은 상기 제1 탐색 공간 집합, 상기 제2 탐색 공간 집합, 및 상기 제3 탐색 공간 집합에 대해 수행되고, 상기 제3 탐색 공간 집합은 CSS(common search space)인, 단말.
Priority Applications (5)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202180049493.6A CN115804219A (zh) | 2020-07-10 | 2021-06-21 | 使用聚合载波进行信号发送/接收的方法和装置 |
| EP21838308.1A EP4181445A4 (en) | 2020-07-10 | 2021-06-21 | Method and device for signal transmission/reception using aggregated carriers |
| CA3187870A CA3187870A1 (en) | 2020-07-10 | 2021-06-21 | Method and device for signal transmission/reception using aggregated carriers |
| US18/012,814 US20230254857A1 (en) | 2020-07-10 | 2021-06-21 | Method and device for signal transmission/reception using aggregated carriers |
| AU2021304710A AU2021304710A1 (en) | 2020-07-10 | 2021-06-21 | Method and device for signal transmission/reception using aggregated carriers |
Applications Claiming Priority (6)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| KR20200085608 | 2020-07-10 | ||
| KR10-2020-0085608 | 2020-07-10 | ||
| KR10-2021-0007093 | 2021-01-18 | ||
| KR20210007093 | 2021-01-18 | ||
| KR20210017911 | 2021-02-08 | ||
| KR10-2021-0017911 | 2021-02-08 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2022010132A1 true WO2022010132A1 (ko) | 2022-01-13 |
Family
ID=79553297
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/KR2021/007756 Ceased WO2022010132A1 (ko) | 2020-07-10 | 2021-06-21 | 집성된 캐리어들을 사용한 신호의 송수신 방법 및 장치 |
Country Status (7)
| Country | Link |
|---|---|
| US (1) | US20230254857A1 (ko) |
| EP (1) | EP4181445A4 (ko) |
| KR (1) | KR20220007514A (ko) |
| CN (1) | CN115804219A (ko) |
| AU (1) | AU2021304710A1 (ko) |
| CA (1) | CA3187870A1 (ko) |
| WO (1) | WO2022010132A1 (ko) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20240032062A1 (en) * | 2022-07-25 | 2024-01-25 | Samsung Electronics Co., Ltd. | Dci size alignment for a scheduled cell with multiple scheduling cells |
| WO2024065851A1 (zh) * | 2022-09-30 | 2024-04-04 | 北京小米移动软件有限公司 | 盲检控制、确定方法及装置、通信装置和存储介质 |
| WO2024094192A1 (zh) * | 2022-11-04 | 2024-05-10 | 华为技术有限公司 | 一种下行控制信息的传输方法及通信装置 |
| US12574860B2 (en) | 2022-04-29 | 2026-03-10 | Electronics And Telecommunications Research Institute | Method and apparatus for coherent transmission and reception of reference signal |
Families Citing this family (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022030909A1 (ko) * | 2020-08-05 | 2022-02-10 | 엘지전자 주식회사 | 무선 통신 시스템에서 상향링크 또는 하향링크 송수신 방법 및 장치 |
| EP4195816A4 (en) * | 2020-08-06 | 2024-04-10 | Ntt Docomo, Inc. | TERMINAL DEVICE, BASE STATION DEVICE AND RECEIVING METHOD |
| AU2021322743B2 (en) * | 2020-08-06 | 2025-01-23 | Telefonaktiebolaget Lm Ericsson (Publ) | Cell monitoring in cross-carrier scheduling |
| EP4193540A1 (en) * | 2020-08-07 | 2023-06-14 | Telefonaktiebolaget LM Ericsson (publ) | Control channel handling for enhanced cross-carrier scheduling |
| JP2023546489A (ja) | 2020-10-23 | 2023-11-02 | テレフオンアクチーボラゲット エルエム エリクソン(パブル) | 拡張クロスキャリアスケジューリングのための物理ダウンリンク制御チャネルの制限処理 |
| CN116803168A (zh) * | 2021-01-15 | 2023-09-22 | 苹果公司 | 针对lte和nr dss的调度限制增强 |
| KR20220113025A (ko) * | 2021-02-05 | 2022-08-12 | 삼성전자주식회사 | 무선 통신 시스템에서 스케줄링을 수행하기 위한 방법 및 장치 |
| CN115190595A (zh) * | 2021-04-02 | 2022-10-14 | 索尼集团公司 | 电子设备、通信方法、存储介质和计算机程序产品 |
| US12273898B2 (en) * | 2021-04-05 | 2025-04-08 | Apple Inc. | Enhanced dynamic spectrum sharing (DSS) in cell groups |
| EP4409793A4 (en) * | 2021-10-01 | 2025-06-25 | Lenovo (Beijing) Limited | Method and apparatus for group-wide DCI payload sizing |
| WO2023077392A1 (en) * | 2021-11-05 | 2023-05-11 | Zte Corporation | Methods and systems for determining control message format in wireless networks |
| US20230337255A1 (en) * | 2022-04-15 | 2023-10-19 | Acer Incorporated | Device and Method for Handling Search Space Set Group and Transmission Configuration Indicator State |
| US20230354331A1 (en) * | 2022-04-29 | 2023-11-02 | Samsung Electronics Co., Ltd. | Pdcch for multi-cell scheduling |
| US12550161B2 (en) * | 2022-04-29 | 2026-02-10 | Apple Inc. | Methods for DCI configurations and procedures with multi-cell scheduling DCI |
| US20240040429A1 (en) * | 2022-07-21 | 2024-02-01 | Samsung Electronics Co., Ltd. | Method and apparatus for dci size for multi-cell scheduling |
| US20240275518A1 (en) * | 2023-02-14 | 2024-08-15 | Qualcomm Incorporated | Techniques for downlink control information size alignment and monitoring for inactive cells |
| KR20240150249A (ko) * | 2023-04-07 | 2024-10-15 | 삼성전자주식회사 | 통신 시스템에서 하향링크 제어 정보 길이 정렬 방법 및 장치 |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20190129011A (ko) * | 2018-05-09 | 2019-11-19 | 엘지전자 주식회사 | 무선 통신 시스템에서 단말의 제어 채널 모니터링 방법 및 상기 방법을 이용하는 단말 |
Family Cites Families (25)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9231743B2 (en) * | 2009-04-24 | 2016-01-05 | Lg Electronics Inc. | Method and apparatus for transmitting and receiving control signal for merging carriers in transmission |
| CA2793084C (en) * | 2010-03-19 | 2016-06-14 | Sharp Kabushiki Kaisha | Mobile communication system, base station apparatus, mobile station apparatus, and communication method |
| US10116422B2 (en) * | 2012-11-02 | 2018-10-30 | Qualcomm Incorporated | Managing cross-carrier scheduling in carrier aggregation with EPDCCH in LTE |
| US9420576B2 (en) * | 2013-04-23 | 2016-08-16 | Qualcomm Incorporated | PDSCH transmission schemes with compact downlink control information (DCI) format in new carrier type (NCT) in LTE |
| US9900844B2 (en) * | 2014-01-13 | 2018-02-20 | Samsung Electronics Co., Ltd. | Uplink transmissions for dual connectivity |
| US10674519B2 (en) * | 2015-01-12 | 2020-06-02 | Lg Electronics Inc. | Method for monitoring downlink control information wireless communication system, and device therefor |
| WO2017052199A1 (en) * | 2015-09-25 | 2017-03-30 | Lg Electronics Inc. | Method and user equipment for receiving downlink control information, and method and base station for transmitting downlink control information |
| US10856323B2 (en) * | 2016-05-10 | 2020-12-01 | Lg Electronics Inc. | Method for receiving data in wireless communication system, and apparatus therefor |
| US10601551B2 (en) * | 2017-05-04 | 2020-03-24 | Sharp Kabushiki Kaisha | Hybrid automatic repeat request for uplink ultra-reliable and low-latency communications |
| WO2019033056A1 (en) * | 2017-08-10 | 2019-02-14 | Babaei Alireza | Harq retransmission and control channel monitoring |
| CN111066371B (zh) * | 2017-09-11 | 2021-04-13 | Lg电子株式会社 | 在无线通信系统中发送下行链路控制信息的方法和设备 |
| US10512072B2 (en) * | 2017-09-11 | 2019-12-17 | Lg Electronics Inc. | Method and apparatus for transmitting downlink control information in wireless communication system |
| JP7140489B2 (ja) * | 2017-11-01 | 2022-09-21 | シャープ株式会社 | 端末装置、基地局装置、および、通信方法 |
| BR112020016028A2 (pt) * | 2018-02-15 | 2020-12-08 | Sharp Kabushiki Kaisha | Equipamentos de usuário, estações base e métodos |
| BR112020018519A2 (pt) * | 2018-03-14 | 2020-12-29 | Ntt Docomo, Inc. | Terminal de usuário e método de radiocomunicação |
| CA3043813A1 (en) * | 2018-05-18 | 2019-11-18 | Comcast Cable Communications, Llc | Cross-carrier scheduling with multiple active bandwidth parts |
| WO2020032693A1 (ko) * | 2018-08-10 | 2020-02-13 | 엘지전자 주식회사 | 무선 통신 시스템에서 스케줄링 정보의 모니터링 방법 및 상기 방법을 이용하는 장치 |
| KR102700669B1 (ko) * | 2018-08-16 | 2024-08-30 | 삼성전자주식회사 | 무선통신 시스템에서 데이터를 송수신하는 방법 및 장치 |
| WO2020053942A1 (ja) * | 2018-09-10 | 2020-03-19 | 株式会社Nttドコモ | ユーザ端末及び無線通信方法 |
| US11374723B2 (en) * | 2019-03-28 | 2022-06-28 | Beijing Xiaomi Mobile Software Co., Ltd. | Cross-carrier scheduling activation for a dormant cell |
| EP3847774B1 (en) * | 2019-07-03 | 2023-11-22 | Ofinno, LLC | Hybrid automatic repeat request acknowledgement codebook determination |
| US11864186B2 (en) * | 2019-08-05 | 2024-01-02 | Ofinno, Llc | Cross carrier scheduling |
| CN111132344B (zh) * | 2019-12-27 | 2023-01-17 | 北京紫光展锐通信技术有限公司 | 跨载波调度方法、装置及存储介质 |
| CN111901869B (zh) * | 2020-02-12 | 2025-02-07 | 中兴通讯股份有限公司 | 一种调度主小区的配置方法、装置、设备及储存介质 |
| WO2021174084A1 (en) * | 2020-02-28 | 2021-09-02 | Comcast Cable Communications, Llc | Scheduling wireless communications |
-
2021
- 2021-06-21 AU AU2021304710A patent/AU2021304710A1/en active Pending
- 2021-06-21 CA CA3187870A patent/CA3187870A1/en active Pending
- 2021-06-21 CN CN202180049493.6A patent/CN115804219A/zh active Pending
- 2021-06-21 WO PCT/KR2021/007756 patent/WO2022010132A1/ko not_active Ceased
- 2021-06-21 KR KR1020210080171A patent/KR20220007514A/ko active Pending
- 2021-06-21 US US18/012,814 patent/US20230254857A1/en active Pending
- 2021-06-21 EP EP21838308.1A patent/EP4181445A4/en active Pending
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20190129011A (ko) * | 2018-05-09 | 2019-11-19 | 엘지전자 주식회사 | 무선 통신 시스템에서 단말의 제어 채널 모니터링 방법 및 상기 방법을 이용하는 단말 |
Non-Patent Citations (5)
| Title |
|---|
| NOKIA, NOKIA SHANGHAI BELL: "Remaining details on search space", 3GPP DRAFT; R1-1806142_SEARCHSPACE_NOK, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Busan, South Korea; 20180521 - 20180525, 11 May 2018 (2018-05-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051461722 * |
| NTT DOCOMO, INC.: "Offline summary for PDCCH structure and search space", 3GPP DRAFT; R1-1813933, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Spokane, USA; 20181112 - 20181116, 13 November 2018 (2018-11-13), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051480137 * |
| QUALCOMM INCORPORATED: "Maintenance for physical downlink control channel", 3GPP DRAFT; R1-1809426_MAINTENANCE FOR PHYSICAL DOWNLINK CONTROL CHANNEL, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Gothenburg, Sweden; 20180820 - 20180824, 11 August 2018 (2018-08-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051516789 * |
| See also references of EP4181445A4 * |
| ZTE, SANECHIPS: "Search space design and related issues", 3GPP DRAFT; R1-1805263 SEARCH SPACE DESIGN AND RELATED ISSUES, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Sanya, China; 20180416 - 20180420, 15 April 2018 (2018-04-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051427505 * |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US12574860B2 (en) | 2022-04-29 | 2026-03-10 | Electronics And Telecommunications Research Institute | Method and apparatus for coherent transmission and reception of reference signal |
| US20240032062A1 (en) * | 2022-07-25 | 2024-01-25 | Samsung Electronics Co., Ltd. | Dci size alignment for a scheduled cell with multiple scheduling cells |
| US12581506B2 (en) * | 2022-07-25 | 2026-03-17 | Samsung Electronics Co., Ltd. | DCI size alignment for a scheduled cell with multiple scheduling cells |
| WO2024065851A1 (zh) * | 2022-09-30 | 2024-04-04 | 北京小米移动软件有限公司 | 盲检控制、确定方法及装置、通信装置和存储介质 |
| WO2024094192A1 (zh) * | 2022-11-04 | 2024-05-10 | 华为技术有限公司 | 一种下行控制信息的传输方法及通信装置 |
Also Published As
| Publication number | Publication date |
|---|---|
| CA3187870A1 (en) | 2022-01-13 |
| AU2021304710A1 (en) | 2023-02-02 |
| EP4181445A1 (en) | 2023-05-17 |
| US20230254857A1 (en) | 2023-08-10 |
| EP4181445A4 (en) | 2024-08-14 |
| CN115804219A (zh) | 2023-03-14 |
| KR20220007514A (ko) | 2022-01-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2022010132A1 (ko) | 집성된 캐리어들을 사용한 신호의 송수신 방법 및 장치 | |
| WO2023128676A1 (ko) | 민감한 트래픽을 위한 제어 채널의 송수신 방법 및 장치 | |
| WO2019216599A1 (ko) | 고신뢰 및 저지연 통신을 위한 신호의 송수신 방법 | |
| WO2014073865A1 (en) | Method and apparatus for transmitting and receiving data in a wireless communication system | |
| WO2019066318A1 (ko) | 통신 시스템에서 프리엠션의 지시 방법 | |
| WO2018030854A1 (ko) | 무선 통신 시스템에서 단말이 다른 단말에게 데이터를 전송하는 방법 | |
| WO2016021958A1 (ko) | 상향링크 신호 전송 방법 및 사용자기기와, 상향링크 신호 수신 방법 및 기지국 | |
| WO2016018046A1 (ko) | 무선 통신 시스템에서 무선 신호 송수신 방법 및 장치 | |
| WO2022071688A1 (ko) | 단말의 저전력 동작을 위한 적응적 제어 채널 모니터링 방법 및 이를 위한 장치 | |
| WO2016018056A1 (ko) | 하향링크 제어 정보 수신 방법 및 사용자기기와, 하향링크 제어 정보 전송 방법 및 기지국 | |
| WO2016093618A1 (ko) | 반송파 집성을 지원하는 무선 통신 시스템에서 단말의 채널 상태 정보 보고 방법 및 이를 위한 장치 | |
| WO2014116074A1 (ko) | 무선 통신 시스템에서 단말이 하향링크 제어 정보를 수신하는 방법 및 이를 위한 장치 | |
| WO2013109109A1 (ko) | 제어 정보 송수신 방법 및 이를 위한 장치 | |
| WO2018128439A1 (ko) | 통신 시스템에서 제어 채널의 송수신 방법 및 장치 | |
| WO2014007593A1 (ko) | 제어 신호 송수신 방법 및 이를 위한 장치 | |
| WO2019194574A1 (en) | Method and apparatus for supporting relay operation for urllc in wireless communication system | |
| WO2017119791A2 (ko) | 무선 통신 시스템에서 무선 신호 송수신 방법 및 장치 | |
| WO2017179921A1 (ko) | 무선통신 시스템에서 변경된 tdd 상향링크-하향링크 설정에 따라 동작하는 방법 및 이를 위한 장치 | |
| WO2025206670A1 (ko) | 저전력 통신을 위한 랜덤 액세스 방법 및 장치 | |
| WO2025234763A1 (ko) | Sbfd 서브밴드에서 랜덤 액세스 절차를 위한 방법 및 장치 | |
| WO2016043513A1 (ko) | 무선 통신 시스템에서 무선 신호 송수신 방법 및 장치 | |
| WO2024232634A1 (ko) | 단일 trp와 다중 trp 간의 스위칭의 방법 및 장치 | |
| WO2024155102A1 (ko) | 동기 신호 블록 전송을 고려한 부분대역 전이중 통신을 지원하기 위한 방법 및 장치 | |
| WO2023249438A1 (ko) | 비면허 대역에서 사이드링크 통신을 위한 방법 및 장치 | |
| WO2014193104A1 (ko) | 저전력 송신 파워를 갖는 소규모 셀로부터 epdcch를 수신하는 방법 및 단말 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 21838308 Country of ref document: EP Kind code of ref document: A1 |
|
| ENP | Entry into the national phase |
Ref document number: 3187870 Country of ref document: CA |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 202317000358 Country of ref document: IN |
|
| ENP | Entry into the national phase |
Ref document number: 2021304710 Country of ref document: AU Date of ref document: 20210621 Kind code of ref document: A |
|
| ENP | Entry into the national phase |
Ref document number: 2021838308 Country of ref document: EP Effective date: 20230210 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
