WO2020204481A1

WO2020204481A1 - Method for receiving downlink control information, user equipment, storage medium, method for transmitting downlink control information, and base station

Info

Publication number: WO2020204481A1
Application number: PCT/KR2020/004182
Authority: WO
Inventors: 이현호; 김선욱; 배덕현
Original assignee: 엘지전자 주식회사
Priority date: 2019-03-29
Filing date: 2020-03-27
Publication date: 2020-10-08

Abstract

User equipment can monitor, within an active time according to DRX configurations, a PDCCH for transporting DCI. The user equipment can adjust a DCI size to be monitored on the basis of the alignment of the DCI size. The alignment of the DCI size can include adjusting the size for a non-fallback UL DCI format and the size for a non-fallback DL DCI format, and then adjusting the size for a fallback UL DCI format and the size for a fallback DL DCI format. Each of the non-fallback UL DCI format and the fallback UL DCI format is used for scheduling a PUSCH, and each of the non-fallback DL DCI format and the fallback DL DCI format is used for scheduling a physical downlink shared channel (PDSCH).

Description

Method for receiving downlink control information, user equipment and storage medium, and method for transmitting downlink control information and base station

This specification relates to a wireless communication system.

Various devices and technologies such as smart phones and tablet PCs (Personal Computers) that require high data transmission, such as machine-to-machine (M2M) communication, machine type communication (MTC), etc. have appeared and spread. have. Accordingly, the amount of data required to be processed in a cellular network is increasing very rapidly. In order to satisfy such rapidly increasing data processing requirements, carrier aggregation technology, cognitive radio technology, etc. to efficiently use more frequency bands, etc., increase the data capacity transmitted within a limited frequency. Multi-antenna technology, multi-base station cooperation technology, etc. are developing.

As more communication devices require larger communication capacity, there is a need for enhanced mobile broadband (eMBB) communication compared to legacy radio access technology (RAT). In addition, massive machine type communication (mMTC) for providing various services anytime, anywhere by connecting a plurality of devices and objects to each other is one of the major issues to be considered in next-generation communication.

In addition, a discussion on a communication system to be designed in consideration of a service/user equipment (UE) sensitive to reliability and latency is ongoing. The introduction of next generation wireless access technology is being discussed in consideration of eMBB communication, mMTC, ultra-reliable and low latency communication (URLLC), and the like.

With the introduction of new wireless communication technology, not only the number of UEs to which the base station has to provide services in a predetermined resource area increases, but also the amount of data and control information transmitted/received with the UEs that the base station provides service Is increasing. Since the amount of radio resources available for the base station to communicate with the UE(s) is finite, the base station transmits up/downlink data and/or up/downlink control information to/from the UE(s) using finite radio resources. A new scheme for efficient reception/transmission is required. In other words, as the density of the node increases and/or the density of the UE increases, there is a need for a method for efficiently using high density nodes or high density user devices for communication.

In addition, there is a need for a method to efficiently support various services having different requirements in a wireless communication system.

In addition, overcoming delay or latency is an important challenge for applications where performance is sensitive to delay/delay.

The technical problems to be achieved by this specification are not limited to the technical problems mentioned above, and other technical problems that are not mentioned are clearly understood by those of ordinary skill in the technical field related to this specification from the following detailed description. Can be.

In an aspect of the present specification, a method for a user equipment to receive downlink control information (DCI) in a wireless communication system is provided. The method includes: determining a first DCI size based on a size of a non-fallback uplink (UL) DCI format and a size of the non-fallback downlink (DL) DCI format; Based on the determination of the first DCI size based on the size of the non-fallback UL DCI format and the size of the non-fallback DL DCI format, based on the size of the fallback UL DCI format and the size of the fallback DL DCI format 2 determine the DCI size; And receiving at least one DCI based on the first DCI size and the second DCI size during an active time based on a discontinuous reception (DRX) setting. Each of the non-fallback UL DCI format and the fallback UL DCI format may be a DCI format used to schedule a physical uplink shared channel (PUSCH). Each of the non-fallback DL DCI format and the fallback DL DCI format may be a DCI format used to schedule a physical downlink shared channel (PDSCH).

In another aspect of the present specification, a user equipment receiving downlink control information (DCI) in a wireless communication system is provided. The user equipment includes: at least one transceiver; At least one processor; And at least one computer memory operably connectable to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations. The operations include: determining a first DCI size based on a size of a non-fallback uplink (UL) DCI format and a size of the non-fallback downlink (DL) DCI format; Based on the determination of the first DCI size based on the size of the non-fallback UL DCI format and the size of the non-fallback DL DCI format, based on the size of the fallback UL DCI format and the size of the fallback DL DCI format 2 determine the DCI size; And receiving at least one DCI based on the first DCI size and the second DCI size during an active time based on a discontinuous reception (DRX) setting. Each of the non-fallback UL DCI format and the fallback UL DCI format may be a DCI format used to schedule a physical uplink shared channel (PUSCH). Each of the non-fallback DL DCI format and the fallback DL DCI format may be a DCI format used to schedule a physical downlink shared channel (PDSCH).

In another aspect of the present disclosure, an apparatus for user equipment is provided. The device comprises: at least one processor; And at least one computer memory operably connectable to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations. The operations include: determining a first DCI size based on a size of a non-fallback uplink (UL) DCI format and a size of the non-fallback downlink (DL) DCI format; Based on the determination of the first DCI size based on the size of the non-fallback UL DCI format and the size of the non-fallback DL DCI format, based on the size of the fallback UL DCI format and the size of the fallback DL DCI format 2 determine the DCI size; And receiving at least one DCI based on the first DCI size and the second DCI size during an active time based on a discontinuous reception (DRX) setting. Each of the non-fallback UL DCI format and the fallback UL DCI format may be a DCI format used to schedule a physical uplink shared channel (PUSCH). Each of the non-fallback DL DCI format and the fallback DL DCI format may be a DCI format used to schedule a physical downlink shared channel (PDSCH).

In another aspect of the present disclosure, a computer-readable storage medium is provided. The computer-readable storage medium stores at least one computer program including instructions that, when executed by at least one processor, cause the at least one processor to perform operations for a user equipment. The operations include: determining a first DCI size based on a size of a non-fallback uplink (UL) DCI format and a size of the non-fallback downlink (DL) DCI format; Based on the determination of the first DCI size based on the size of the non-fallback UL DCI format and the size of the non-fallback DL DCI format, based on the size of the fallback UL DCI format and the size of the fallback DL DCI format 2 determine the DCI size; And receiving at least one DCI based on the first DCI size and the second DCI size during an active time based on a discontinuous reception (DRX) setting. Each of the non-fallback UL DCI format and the fallback UL DCI format may be a DCI format used to schedule a physical uplink shared channel (PUSCH). Each of the non-fallback DL DCI format and the fallback DL DCI format may be a DCI format used to schedule a physical downlink shared channel (PDSCH).

In another aspect of the present specification, a method for transmitting downlink control information (DCI) by a base station in a wireless communication system is provided. The method includes: adjusting a size of a non-fallback uplink (UL) DCI format and a size of the non-fallback downlink (DL) DCI format to a first DCI size; Based on the adjustment of the size of the non-fallback UL DCI format and the size of the non-fallback DL DCI format to the first DCI size, the size of the fallback UL DCI format and the size of the fallback DL DCI format are determined as the second DCI size. Adjusted to; And transmitting at least one DCI based on the first DCI size and the second DCI size within an active time based on a discontinuous reception (DRX) setting. Each of the non-fallback UL DCI format and the fallback UL DCI format may be a DCI format used to schedule a physical uplink shared channel (PUSCH). Each of the non-fallback DL DCI format and the fallback DL DCI format may be a DCI format used to schedule a physical downlink shared channel (PDSCH).

In another aspect of the present specification, a base station for transmitting downlink control information (DCI) in a wireless communication system is provided. The base station includes: at least one transceiver; At least one processor; And at least one computer memory operably connectable to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations. The operations include: adjusting the size of the non-fallback uplink (UL) DCI format and the size of the non-fallback downlink (DL) DCI format to a first DCI size; Based on the adjustment of the size of the non-fallback UL DCI format and the size of the non-fallback DL DCI format to the first DCI size, the size of the fallback UL DCI format and the size of the fallback DL DCI format are determined as the second DCI size. Adjusted to; And transmitting at least one DCI based on the first DCI size and the second DCI size within an active time based on a discontinuous reception (DRX) setting. Each of the non-fallback UL DCI format and the fallback UL DCI format may be a DCI format used to schedule a physical uplink shared channel (PUSCH). Each of the non-fallback DL DCI format and the fallback DL DCI format may be a DCI format used to schedule a physical downlink shared channel (PDSCH).

In each aspect of the present specification, the base station may provide the DRX configuration to the user equipment.

In each aspect of the present specification, the first DCI size may be one of the size of the non-fallback UL DCI format and the non-fallback DL DCI format. The second DCI size may be one of the fallback UL DCI format and the fallback DL DCI format.

In each aspect of the present specification, the non-fallback UL DCI format may be set to include or not include at least one field having a fixed field size among fields in the fallback UL DCI format.

In each aspect of the present specification, the non-fallback DL DCI format may be set to include or not include at least one field having a fixed field size among fields in the fallback DL DCI format.

In each aspect of the present specification, the size of the non-fallback UL DCI format may be set smaller than the size of the fallback UL DCI format. The size of the non-fallback DL DCI format may be set smaller than the size of the fallback DL DCI format.

In each aspect of the present specification, determining/adjusting the second DCI based on the size of the fallback UL DCI format and the size of the fallback DL DCI format comprises: i) the size of the non-fallback UL DCI format and the ratio -The size of the fallback UL DCI format and the size of the fallback DL DCI format based on determining/determining the first DCI size based on the size of the fallback UL DCI format and ii) not meeting the conditions. It may include determining/adjusting the size of the second DCI based on it. The above conditions may include: i) the total number of different DCI sizes set to be monitored is not more than X+1 for a cell, and ii) a cell radio network temporary identifier (C-RNTI) ), the total number of different DCI sizes set to monitor is not more than X for the cell.

In each aspect of the present specification, receiving the at least one DCI comprises: decoding the DCI of the non-fallback UL DCI format or the DCI of the non-fallback DL DCI format based on the first DCI size. can do. Transmitting the at least one DCI may include: transmitting the DCI of the non-fallback UL DCI format or the DCI of the non-fallback DL DCI format based on the first DCI size.

In each aspect of the present specification, the fallback UL DCI format may be a DCI format DCI format 0_1, and the non-fallback UL DCI format may be a DCI format different from DCI format 0_0 and DCI format 0_1. The fallback DL DCI format may be DCI format 1_1, and the non-fallback DL DCI format may be a DCI format different from DCI format 1_0 and DCI format 1_1.

The above problem solving methods are only some of the examples of the present specification, and various examples reflecting the technical features of the present specification may be derived and understood based on the following detailed description by a person having ordinary knowledge in the art. .

According to the implementation(s) of the present specification, wireless communication signals can be efficiently transmitted/received. Accordingly, the overall throughput of the wireless communication system can be increased.

According to the implementation(s) of the present specification, various services with different requirements can be efficiently supported in a wireless communication system.

According to the implementation(s) of the present specification, a delay/delay occurring during wireless communication between communication devices may be reduced.

The effects according to the present specification are not limited to the above-mentioned effects, and another effect not mentioned will be clearly understood by those of ordinary skill in the art related to the present specification from the following detailed description. .

The accompanying drawings, which are included as part of the detailed description to aid in understanding the implementations of this specification, provide examples of implementations of the specification, and describe implementations of the specification together with the detailed description:

1 shows an example of communication system 1 to which implementations of the present specification are applied;

2 is a block diagram showing examples of communication devices capable of performing a method according to the present specification;

3 shows another example of a wireless device capable of performing implementation(s) of the present specification;

4 illustrates a discontinuous reception (DRX) operation that may be applied to the implementation(s) of the present specification;

Figure 5 is a simplified showing an example of a possible frame structure used in a wireless communication system based on 3rd Generation Partnership Project ^{(3 rd generation partnership project, 3GPP} );

6 illustrates a resource grid of slots;

7 illustrates slot structures that can be used in a 3GPP-based system;

8 shows an example of PDSCH time domain resource allocation by PDCCH and an example of PUSCH time domain resource allocation by PDCCH;

9 illustrates a hybrid automatic repeat request-acknowledgement (HARQ-ACK) transmission/reception process;

10 shows an example of multiplexing uplink control information (UCI) on a PUSCH;

11 shows an example of a process in which a UE with PUCCHs overlapping in a single slot handles collisions between UL channels;

12 illustrates cases of multiplexing UCI multiplexing according to FIG. 11;

13 illustrates a process in which a UE having PUCCH and PUSCH overlapping in a single slot handles collision between UL channels;

14 illustrates UCI multiplexing in consideration of a timeline condition;

15 illustrates transmission of a plurality of HARQ-ACK PUCCHs in a slot;

16 shows an example of a DCI transmission/reception flow according to some implementations of this specification;

17 illustrates a DCI size alignment process according to an example of the present specification;

18 illustrates a DCI size alignment process according to another example of the present specification;

19 and 20 illustrate a DCI size alignment process according to another example of the present specification;

21 and 22 illustrate an operation flow of a UE and a BS based on some implementations of this specification related to DCI parameter selection;

23 illustrates another example of a DCI transmission/reception flow according to some implementations of this specification.

Hereinafter, implementations according to the present specification will be described in detail with reference to the accompanying drawings. The detailed description to be disclosed below with the accompanying drawings is intended to describe an exemplary implementation of the present specification, and is not intended to represent the only implementation form in which the present specification may be practiced. The detailed description below includes specific details to provide a thorough understanding of the present specification. However, one of ordinary skill in the art appreciates that the present specification may be practiced without these specific details.

In some cases, in order to avoid obscuring the concept of the present specification, well-known structures and devices may be omitted or illustrated in a block diagram format centering on core functions of each structure and device. In addition, the same components will be described with the same reference numerals throughout the present specification.

The techniques, devices, and systems described below can be applied to various wireless multiple access systems. Examples of multiple access systems include a code division multiple access (CDMA) system, a frequency division multiple access (FDMA) system, a time division multiple access (TDMA) system, an orthogonal frequency division multiple access (OFDMA) system, and a single carrier frequency (SC-FDMA) system. division multiple access) system, MC-FDMA (multi carrier frequency division multiple access) system, and the like. CDMA may be implemented in a radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA may be implemented in a radio technology such as Global System for Mobile communication (GSM), General Packet Radio Service (GPRS), Enhanced Data Rates for GSM Evolution (EDGE) (ie, GERAN). OFDMA may be implemented in wireless technologies such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (WiFi), IEEE 802.16 (WiMAX), IEEE802-20, and evolved-UTRA (E-UTRA). UTRA is a part of Universal Mobile Telecommunication System (UMTS), and 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is a part of E-UMTS using E-UTRA. 3GPP LTE adopts OFDMA in downlink (DL) and SC-FDMA in uplink (UL). LTE-advanced (LTE-A) is an evolved form of 3GPP LTE.

For convenience of description, the following description will be made on the assumption that the present specification is applied to a 3GPP-based communication system, for example, LTE and NR. However, the technical features of the present specification are not limited thereto. For example, although the following detailed description is described based on a mobile communication system corresponding to a 3GPP LTE/NR system, it can also be applied to any other mobile communication system, except for items specific to 3GPP LTE/NR. Do.

For terms and technologies that are not specifically described among terms and technologies used in the present specification, 3GPP LTE standard documents, for example, 3GPP TS 36.211, 3GPP TS 36.212, 3GPP TS 36.213, 3GPP TS 36.321, 3GPP TS 36.300 and 3GPP TS 36.331 and the like, 3GPP NR standard documents, for example, 3GPP TS 38.211, 3GPP TS 38.212, 3GPP TS 38.213, 3GPP TS 38.214, 3GPP TS 38.300, 3GPP TS 38.331, and the like may be referenced.

In the examples of this specification to be described later, the expression "assumes" by the device may mean that the subject transmitting the channel transmits the channel so as to conform to the "assumption". The subject receiving the channel may mean that the channel is received or decoded in a form conforming to the “assuming” under the premise that the channel is transmitted to conform to the “assuming”.

In the present specification, the UE may be fixed or mobile, and various devices that transmit and/or receive user data and/or various control information by communicating with a base station (BS) belong to this. The UE includes (Terminal Equipment), MS (Mobile Station), MT (Mobile Terminal), UT (User Terminal), SS (Subscribe Station), wireless device, PDA (Personal Digital Assistant), and wireless modem. ), handheld device, etc. In addition, in this specification, a BS generally refers to a fixed station that communicates with a UE and/or other BS, and exchanges various data and control information by communicating with the UE and other BSs. BS may be referred to as other terms such as ABS (Advanced Base Station), NB (Node-B), eNB (evolved-NodeB), BTS (Base Transceiver System), Access Point (Access Point), PS (Processing Server). In particular, the base station of UTRAN is called Node-B, the base station of E-UTRAN is called eNB, and the base station of new radio access technology network is called gNB. Hereinafter, for convenience of description, the base station is collectively referred to as a BS regardless of the type or version of the communication technology.

In this specification, a node refers to a fixed point at which radio signals can be transmitted/received by communicating with the UE. Various types of BSs can be used as nodes regardless of their name. For example, BS, NB, eNB, pico-cell eNB (PeNB), home eNB (HeNB), relay, repeater, and the like may be nodes. Also, the node may not have to be a BS. For example, it may be a radio remote head (RRH) or a radio remote unit (RRU). RRH, RRU, etc. generally have a power level lower than the power level of the BS. RRH or RRU or less, RRH/RRU) is generally connected to the BS by a dedicated line such as an optical cable, so RRH/RRU and BS are generally compared to cooperative communication by BSs connected by wireless lines. By cooperative communication can be performed smoothly. At least one antenna is installed in one node. The antenna may mean a physical antenna, or an antenna port, a virtual antenna, or an antenna group. Nodes are also called points.

In this specification, a cell refers to a certain geographic area in which one or more nodes provide communication services. Therefore, in this specification, communication with a specific cell may mean communication with a BS or a node that provides a communication service to the specific cell. In addition, the downlink/uplink signal of a specific cell means a downlink/uplink signal from/to a BS or a node that provides a communication service to the specific cell. A cell that provides uplink/downlink communication services to a UE is specifically referred to as a serving cell. In addition, the channel state/quality of a specific cell refers to a channel state/quality of a channel or communication link formed between a BS or a node and a UE providing a communication service to the specific cell. In the 3GPP-based communication system, the UE determines the downlink channel state from a specific node, CRS(s) transmitted on a CRS (Cell-specific Reference Signal) resource allocated to the specific node by the antenna port(s) of the specific node, and / Or it can be measured using CSI-RS(s) transmitted on a Channel State Information Reference Signal (CSI-RS) resource.

Meanwhile, the 3GPP-based communication system uses the concept of a cell to manage radio resources, and a cell associated with a radio resource is distinguished from a cell in a geographic area.

The “cell” in the geographic area may be understood as coverage in which a node can provide a service using a carrier, and the “cell” of a radio resource is a bandwidth (a frequency range configured by the carrier). bandwidth, BW). Since downlink coverage, which is a range in which a node can transmit a valid signal, and uplink coverage, which is a range in which a valid signal can be received from a UE, is dependent on the carrier that carries the signal, the node's coverage is used by the node. It is also associated with the coverage of the "cell" of the radio resource to be used. Therefore, the term "cell" can sometimes be used to mean coverage of a service by a node, sometimes a radio resource, and sometimes a range within which a signal using the radio resource can reach a valid strength.

Meanwhile, the 3GPP communication standard uses the concept of a cell to manage radio resources. The term "cell" associated with radio resources is defined as a combination of downlink resources (DL resources) and uplink resources (UL resources), that is, a combination of a DL component carrier (CC) and a UL CC. . The cell may be configured with a DL resource alone or a combination of a DL resource and a UL resource. When carrier aggregation is supported, the linkage between the carrier frequency of the DL resource (or, DL CC) and the carrier frequency of the UL resource (or UL CC) is indicated by system information Can be. For example, a combination of a DL resource and a UL resource may be indicated by a system information block type 2 (SIB2) linkage. Here, the carrier frequency may be the same as or different from the center frequency of each cell or CC. When carrier aggregation (CA) is configured, the UE has only one radio resource control (RRC) connection with the network. One serving cell provides non-access stratum (NAS) mobility information at RRC connection establishment/re-establishment/handover, and one serving cell Provides a security input when re-establishing an RRC connection/handover. Such cells are referred to as primary cells (Pcell). The Pcell is a cell operating on a primary frequency at which the UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure. Depending on the UE capability, secondary cells (Scells) may be configured to form a set of serving cells together with the Pcell. Scell is a cell that can be set after RRC (Radio Resource Control) connection establishment is made, and provides additional radio resources in addition to the resources of a special cell (SpCell). In downlink, a carrier corresponding to a Pcell is called a downlink primary CC (DL PCC), and a carrier corresponding to a Pcell in uplink is called a UL primary CC (DL PCC). A carrier corresponding to the Scell in downlink is referred to as a DL secondary CC (DL SCC), and a carrier corresponding to the Scell in uplink is referred to as a UL secondary CC (UL SCC).

In the case of dual connectivity (DC) operation, the term SpCell refers to a Pcell of a master cell group (MCG) or a Pcell of a secondary cell group (SCG). SpCell supports PUCCH transmission and contention-based random access, and is always activated. The MCG is a group of serving cells associated with a master node (eg, BS) and consists of SpCell (Pcell) and optionally one or more Scells. For a UE configured as DC, the SCG is a subset of serving cells associated with the secondary node, and consists of a PSCell and zero or more Scells. In the case of a UE in the RRC_CONNECTED state that is not set to CA or DC, there is only one serving cell composed of only Pcell. In the case of a UE in the RRC_CONNECTED state set to CA or DC, the term serving cells refers to a set of cells consisting of SpCell(s) and all Scell(s). In DC, two MAC entities, one medium access control (MAC) entity for MCG and one MAC entity for SCG, are configured in the UE.

In a UE in which CA is configured and DC is not configured, a Pcell PUCCH group consisting of a Pcell and zero or more Scells and an Scell PUCCH group consisting of only Scell(s) may be configured. In the case of an Scell, an Scell (hereinafter referred to as a PUCCH cell) through which a PUCCH associated with a corresponding cell is transmitted may be configured. The Scell indicated by the PUCCH Scell belongs to the Scell PUCCH group, and the PUCCH transmission of the related UCI is performed on the PUCCH Scell, and the Scell whose PUCCH Scell is not indicated or the cell indicated as a PUCCH transmission cell is a Pcell belongs to the Pcell PUCCH group, and the PUCCH transmission of related UCI is performed on the Pcell.

In a wireless communication system, a UE receives information from a BS through a downlink (DL), and the UE transmits information to the BS through an uplink (UL). The information transmitted and/or received by the BS and the UE includes data and various control information, and various physical channels exist according to the type/use of the information they transmit and/or receive.

3GPP-based communication standards include downlink physical channels corresponding to resource elements carrying information originating from higher layers, and downlink physical channels corresponding to resource elements used by the physical layer but not carrying information originating from higher layers. Link physical signals are defined. For example, a physical downlink shared channel (PDSCH), a physical broadcast channel (PBCH), a physical downlink control channel (PDCCH), etc. are the downlink physical channels. It is defined, and a reference signal and a synchronization signal are defined as downlink physical signals. A reference signal (RS), also referred to as a pilot, refers to a signal of a predefined special waveform that the BS and the UE know each other. For example, a demodulation reference signal (DMRS), channel state information RS (channel state information RS, CSI-RS), etc. are defined as a downlink reference signal. 3GPP-based communication standards include uplink physical channels corresponding to resource elements carrying information originating from an upper layer, and uplink physical channels corresponding to resource elements used by the physical layer but not carrying information originating from an upper layer. Link physical signals are defined. For example, a physical uplink shared channel (PUSCH), a physical uplink control channel (PUCCH), and a physical random access channel (PRACH) are used as uplink physical channels. It is defined, and a demodulation reference signal (DMRS) for an uplink control/data signal, a sounding reference signal (SRS) used for uplink channel measurement, and the like are defined.

In this specification, PDCCH (Physical Downlink Control CHannel) refers to a set of time-frequency resources (eg, resource elements) carrying Downlink Control Information (DCI), and PDSCH (Physical Downlink Shared CHannel) refers to downlink data. It means a set of time-frequency resources to carry. In addition, PUCCH (Physical Uplink Control CHannel), PUSCH (Physical Uplink Shared CHannel), PRACH (Physical Random Access CHannel) are each (respectively) UCI (Uplink Control Information), uplink data, time-frequency carrying a random access signal It means a collection of resources. Hereinafter, the expression that the user equipment transmits/receives PUCCH/PUSCH/PRACH is used in the same sense as transmitting/receiving uplink control information/uplink data/random access signals on or through PUSCH/PUCCH/PRACH, respectively. do. In addition, the expression that the BS transmits/receives PBCH/PDCCH/PDSCH is used in the same meaning as transmitting broadcast information/downlink data/downlink control information on or through PBCH/PDCCH/PDSCH, respectively.

As more communication devices require a larger communication capacity, there is a need for improved mobile broadband communication compared to the existing radio access technology (RAT). In addition, massive MTC, which provides various services anytime, anywhere by connecting multiple devices and objects, is one of the major issues to be considered in next-generation communication. In addition, a communication system design considering a service/UE sensitive to reliability and latency is being discussed. Introduction of the next-generation RAT in consideration of such advanced mobile broadband communication, massive MTC, and URLLC (Ultra-Reliable and Low Latency Communication) is being discussed. Currently, 3GPP is conducting a study on the next-generation mobile communication system after EPC. In this specification, for convenience, the technology is referred to as a new RAT (NR) or 5G RAT, and a system that uses or supports NR is referred to as an NR system.

1 shows an example of communication system 1 to which implementations of the present specification are applied. Referring to Fig. 1, a communication system 1 applied to the present specification includes a wireless device, a BS, and a network. Here, the wireless device refers to a device that performs communication using wireless access technology (eg, 5G NR (New RAT), LTE (eg, E-UTRA)), and may be referred to as a communication/wireless/5G device. . Although not limited thereto, wireless devices include robots 100a, vehicles 100b-1 and 100b-2, eXtended Reality (XR) devices 100c, hand-held devices 100d, and home appliances 100e. ), an Internet of Thing (IoT) device 100f, and an AI device/server 400. For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, and a vehicle capable of performing inter-vehicle communication. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (eg, a drone). XR devices include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, including HMD (Head-Mounted Device), HUD (Head-Up Display), TV, smartphone, It can be implemented in the form of a computer, wearable device, home appliance, digital signage, vehicle, robot, and the like. Portable devices may include smart phones, smart pads, wearable devices (eg, smart watches, smart glasses), computers (eg, notebook computers, etc.). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors, smart meters, and the like. For example, the BS and the network may be implemented as a wireless device, and a specific wireless device 200a may operate as a BS/network node to another wireless device.

The wireless devices 100a to 100f may be connected to the network 300 through the BS 200. AI (Artificial Intelligence) technology may be applied to the wireless devices 100a to 100f, and the wireless devices 100a to 100f may be connected to the AI server 400 through the network 300. The network 300 may be configured using a 3G network, a 4G (eg, LTE) network, or a 5G (eg, NR) network. The wireless devices 100a to 100f may communicate with each other through the BS 200/network 300, but may perform direct communication (e.g. sidelink communication) without passing through the BS/network. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (e.g. V2V (Vehicle to Vehicle)/V2X (Vehicle to Everything) communication). In addition, the IoT device (eg, sensor) may directly communicate with other IoT devices (eg, sensors) or other wireless devices 100a to 100f.

Wireless communication/

connections

150a and 150b may be achieved between the wireless devices 100a to 100f/BS 200 to the BS 200/wireless devices 100a to 100f. Here, wireless communication/connection may be performed through various wireless access technologies (eg, 5G NR) for uplink/downlink communication 150a and sidelink communication 150b (or D2D communication). Through wireless communication/

connection

150a and 150b, the wireless device and the BS/wireless device may transmit/receive wireless signals to each other. To this end, based on the various proposals of this specification, various configuration information setting procedures for transmission/reception of radio signals, various signal processing procedures (e.g., channel encoding/decoding, modulation/demodulation, resources) Mapping/demapping, etc.), resource allocation process, etc. may be performed.

2 is a block diagram illustrating examples of communication devices capable of performing a method according to the present specification. Referring to FIG. 2, the first wireless device 100 and the second wireless device 200 may transmit and/or receive wireless signals through various wireless access technologies (eg, LTE, NR). Here, {the first wireless device 100, the second wireless device 200} is the {wireless device 100x, BS 200} and/or {wireless device 100x, wireless device 100x) of FIG. 1 } Can be matched.

The first wireless device 100 includes one or more processors 102 and one or more memories 104, and may further include one or more transceivers 106 and/or one or more antennas 108. The processor 102 controls the memory 104 and/or the transceiver 106 and may be configured to implement the functions, procedures, and/or methods described/suggested above. For example, the processor 102 may process information in the memory 104 to generate first information/signal, and then transmit a radio signal including the first information/signal through the transceiver 106. In addition, the processor 102 may store information obtained from signal processing of the second information/signal in the memory 104 after receiving a radio signal including the second information/signal through the transceiver 106. The memory 104 may be connected to the processor 102 and may store various information related to the operation of the processor 102. For example, the memory 104 may store software code including instructions for performing some or all of the processes controlled by the processor 102, or performing the previously described/suggested procedures and/or methods. . Here, the processor 102 and the memory 104 may be part of a communication modem/circuit/chip designed to implement wireless communication technology (eg, LTE, NR). The transceiver 106 may be connected to the processor 102 and may transmit and/or receive radio signals through one or more antennas 108. The transceiver 106 may comprise a transmitter and/or a receiver. The transceiver 106 may be mixed with an RF (Radio Frequency) unit. In this specification, a wireless device may mean a communication modem/circuit/chip.

The second wireless device 200 includes one or more processors 202 and one or more memories 204, and may further include one or more transceivers 206 and/or one or more antennas 208. The processor 202 controls the memory 204 and/or the transceiver 206 and may be configured to implement the functions, procedures, and/or methods described/suggested above. For example, the processor 202 may process information in the memory 204 to generate third information/signal, and then transmit a wireless signal including the third information/signal through the transceiver 206. In addition, the processor 202 may store information obtained from signal processing of the fourth information/signal in the memory 204 after receiving a radio signal including the fourth information/signal through the transceiver 206. The memory 204 may be connected to the processor 202 and may store various information related to the operation of the processor 202. For example, the memory 204 may store software code including instructions for performing some or all of the processes controlled by the processor 202, or performing the procedures and/or methods described/suggested above. . Here, the processor 202 and the memory 204 may be part of a communication modem/circuit/chip designed to implement wireless communication technology (eg, LTE, NR). The transceiver 206 may be connected to the processor 202 and may transmit and/or receive radio signals through one or more antennas 208. The transceiver 206 may include a transmitter and/or a receiver. The transceiver 206 may be mixed with an RF unit. In this specification, a wireless device may mean a communication modem/circuit/chip.

Hereinafter, the hardware elements of the

wireless devices

100 and 200 will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or

more processors

102, 202. For example, the one or

more processors

102, 202 may include one or more layers (e.g., a physical (PHY) layer, a medium access control (MAC) layer, a radio link control (RLC) layer). , A packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, and a functional layer such as a service data adaption protocol (SDAP) may be implemented. One or more processors (102, 202) are one or more protocol data unit (protocol data unit (PDU)) and / or one or more service data unit (service data unit, SDU) according to the functions, procedures, proposals and / or methods disclosed in this document. ) Can be created. One or

more processors

102 and 202 may generate messages, control information, data, or information according to functions, procedures, suggestions and/or methods disclosed herein. At least one processor (102, 202) is PDU, SDU, message, control information, data or signals containing information (e.g., baseband signals) in accordance with the functions, procedures, proposals and/or methods disclosed herein. Can be provided to one or

more transceivers

106 and 206. One or more processors (102, 202) may receive signals (e.g., baseband signals) from one or more transceivers (106, 206), and PDU, SDU according to the functions, procedures, proposals and/or methods disclosed herein. , Messages, control information, data or information can be obtained.

One or more of the

processors

102 and 202 may be referred to as a controller, microcontroller, microprocessor, or microcomputer. One or more of the

processors

102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) May be included in one or

more processors

102 and 202. The functions, procedures, suggestions and/or methods disclosed in this document may be implemented using firmware or software, and firmware or software may be implemented to include modules, procedures, functions, and the like. Firmware or software configured to perform the functions, procedures, proposals and/or methods disclosed herein are included in one or

more processors

102, 202, or stored in one or

more memories

104, 204, and 202). The functions, procedures, proposals and or methods disclosed in this document may be implemented using firmware or software in the form of codes, instructions and/or a set of instructions.

One or

more memories

104 and 204 may be connected to one or

more processors

102 and 202 and may store various types of data, signals, messages, information, programs, codes, instructions and/or instructions. One or

more memories

104 and 204 may be composed of ROM, RAM, EPROM, flash memory, hard drive, register, cache memory, computer readable storage medium, and/or combinations thereof. One or

more memories

104 and 204 may be located inside and/or outside of one or

more processors

102 and 202. In addition, one or

more memories

104, 204 may be connected to one or

more processors

102, 202 through various technologies such as wired or wireless connection.

The one or

more transceivers

106 and 206 may transmit user data, control information, radio signals/channels, and the like mentioned in the methods and/or operation flow charts of this document to one or more other devices. The one or

more transceivers

106 and 206 may receive user data, control information, radio signals/channels, and the like described in the functions, procedures, proposals, methods and/or operational flow charts disclosed herein from one or more other devices. For example, one or

more transceivers

106, 206 may be coupled with one or

more processors

102, 202, and may transmit and/or receive wireless signals. For example, one or

more processors

102, 202 may control one or

more transceivers

106, 206 to transmit user data, control information, or radio signals to one or more other devices. In addition, one or

more processors

102, 202 may control one or

more transceivers

106, 206 to receive user data, control information, or radio signals from one or more other devices. In addition, one or more transceivers (106, 206) may be connected to one or more antennas (108, 208), one or more transceivers (106, 206) through one or more antennas (108, 208) functions and procedures disclosed in this document. It may be configured to transmit and/or receive user data, control information, radio signals/channels, etc. mentioned in the proposal, method and/or operation flow chart. In this document, one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (eg, antenna ports). One or more transceivers (106, 206) in order to process the received user data, control information, radio signal / channel, etc. using one or more processors (102, 202), the received radio signal / channel, etc. in the RF band signal. It can be converted into a baseband signal. One or

more transceivers

106 and 206 may convert user data, control information, radio signals/channels, etc. processed using one or

more processors

102 and 202 from a baseband signal to an RF band signal. To this end, one or more of the

transceivers

106 and 206 may include (analog) oscillators and/or filters.

3 illustrates another example of a wireless device capable of performing implementation(s) of the present specification. Referring to FIG. 3, the

wireless devices

100 and 200 correspond to the

wireless devices

100 and 200 of FIG. 2, and various elements, components, units/units, and/or modules It can be composed of (module). For example, the

wireless devices

100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130, and an additional element 140. The communication unit may include a communication circuit 112 and a transceiver(s) 114. For example, the communication circuit 112 may include one or

more processors

102 and 202 and/or one or

more memories

104 and 204 of FIG. 2. For example, the transceiver(s) 114 may include one or

more transceivers

106, 206 and/or one or

more antennas

108, 208 of FIG. 2. The control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional element 140 and controls all operations of the wireless device. For example, the controller 120 may control the electrical/mechanical operation of the wireless device based on the program/code/command/information stored in the memory unit 130. In addition, the control unit 120 transmits the information stored in the memory unit 130 to an external (eg, other communication device) through the communication unit 110 through a wireless/wired interface, or through the communication unit 110 to the outside (eg, Information received through a wireless/wired interface from another communication device) may be stored in the memory unit 130.

The additional element 140 may be variously configured according to the type of wireless device. For example, the additional element 140 may include at least one of a power unit/battery, an I/O unit, a driving unit, and a computing unit. Although not limited to this, wireless devices include robots (Fig. 1, 100a), vehicles (Fig. 1, 100b-1, 100b-2), XR equipment (Fig. 1, 100c), portable equipment (Fig. 1, 100d), and home appliances. (Fig. 1, 100e), IoT device (Fig. 1, 100f), digital broadcasting UE, hologram device, public safety device, MTC device, medical device, fintech device (or financial device), security device, climate/environment device, It may be implemented in the form of an AI server/device (FIGS. 1, 400), BS (FIGS. 1, 200), and network nodes. The wireless device can be used in a mobile or fixed location depending on the use-example/service.

In FIG. 3, various elements, components, units/units, and/or modules in the

wireless devices

100 and 200 may be entirely interconnected through a wired interface, or at least some may be wirelessly connected through the communication unit 110. For example, in the

wireless devices

100 and 200, the control unit 120 and the communication unit 110 are connected by wire, and the control unit 120 and the first unit (eg, 130, 140) are connected through the communication unit 110. Can be connected wirelessly. In addition, each element, component, unit/unit, and/or module in the

wireless device

100 and 200 may further include one or more elements. For example, the controller 120 may be configured with one or more processor sets. For example, the control unit 120 may be composed of a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphic processing processor, and a memory control processor. As another example, the memory unit 130 includes random access memory (RAM), dynamic RAM (DRAM), read only memory (ROM), flash memory, volatile memory, and non-volatile memory. volatile memory) and/or a combination thereof.

In the present specification, at least one memory (eg, 104 or 204) may store instructions or programs, and the instructions or programs are at least operably connected to the at least one memory when executed. It may cause one processor to perform operations according to some embodiments or implementations of the present specification.

In the present specification, a computer-readable storage medium may store at least one instruction or computer program, and the at least one instruction or computer program is executed by at least one processor. It may cause one processor to perform operations according to some embodiments or implementations of the present specification.

In the present specification, a processing device or apparatus may include at least one processor and at least one computer memory connectable to the at least one processor. The at least one computer memory may store instructions or programs, and when executed, the instructions or programs cause at least one processor operably connected to the at least one memory to It may be possible to perform operations according to embodiments or implementations.

The communication device of the present specification includes at least one processor; And at least one storing instructions that are operably connectable to the at least one processor and, when executed, cause the at least one processor to perform operations according to the example(s) of the present specification to be described later. Contains one computer memory.

4 illustrates a discontinuous reception (DRX) operation that may be applied to the implementation(s) of the present specification.

The UE may perform a DRX operation while performing a process and/or method according to the implementation(s) of the present specification. The UE in which DRX is configured may lower power consumption by discontinuously receiving DL signals. DRX may be performed in the RRC_IDLE state, the RRC_INACTIVE state, and the RRC_CONNECTED state. In the RRC_IDLE state and RRC_INACTIVE state, DRX is used for the UE to receive paging signals discontinuously. Hereinafter, DRX performed in the RRC_CONNECTED state will be described (RRC_CONNECTED DRX).

4 illustrates a DRX cycle for a UE in an RRC_CONNECTED state. Referring to FIG. 4, the DRX cycle is composed of On Duration and Opportunity for DRX. The DRX cycle defines the time interval at which the on duration is periodically repeated. On duration represents a time period during which the UE performs PDCCH monitoring to receive the PDCCH. When DRX is configured, the UE performs PDCCH monitoring during on-duration. If there is a PDCCH successfully detected during PDCCH monitoring, the UE operates an inactivity timer and maintains an awake state. On the other hand, if there is no PDCCH successfully detected during PDCCH monitoring, the UE enters a sleep state after the on duration ends. Accordingly, when DRX is configured, in performing the process and/or method according to the implementation(s) of the present specification, the UE may perform PDCCH monitoring/reception discontinuously in the time domain. For example, when DRX is configured, in this specification, a PDCCH reception time (eg, a slot having a PDCCH search space) may be set discontinuously according to the DRX configuration. On the other hand, when DRX is not configured, in performing the process and/or method according to the implementation(s) of the present specification, the UE may continuously perform PDCCH monitoring/reception in the time domain. For example, when DRX is not set, a PDCCH reception timing (eg, a slot having a PDCCH search space) in the present specification may be continuously set. Meanwhile, regardless of whether or not DRX is set, PDCCH monitoring may be restricted in a time period set as a measurement gap.

The following table illustrates the UE process related to DRX. Referring to the following table, DRX configuration information is received through higher layer (eg, RRC) signaling, and whether DRX ON/OFF is controlled by the DRX command of the MAC layer. When DRX is configured, the UE may perform PDCCH monitoring discontinuously, as illustrated in FIG. 4.

Here, MAC-CellGroupConfig includes configuration information necessary to configure MAC parameters for a cell group. MAC-CellGroupConfig may also include configuration information about DRX. For example, MAC-CellGroupConfig may include information related to DRX as follows.

-Value of drx-OnDurationTimer: Defines the length of the start section of the DRX cycle

-Value of drx-InactivityTimer: Defines the length of the time interval in which the UE is awake after the PDCCH time when the PDCCH indicating initial UL or DL data is detected

-Value of drx-HARQ-RTT-TimerDL: Defines the length of the maximum time interval from receiving the initial DL transmission until the DL retransmission is received.

-Value of drx-HARQ-RTT-TimerDL: After the grant for initial UL transmission is received, the length of the maximum time interval until the grant for UL retransmission is received is defined.

-drx-LongCycleStartOffset: Defines the time length and start point of the DRX cycle

-drx-ShortCycle (optional): Defines the time length of the short DRX cycle.

Here, if any one of drx-OnDurationTimer, drx-InactivityTimer, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerDL is in operation, the UE performs PDCCH monitoring at every PDCCH period while maintaining the awake state. The time during which any one of drx-OnDurationTimer, drx-InactivityTimer, drx-HARQ-RTT-TimerDL, and drx-HARQ-RTT-TimerDL is in operation is referred to as an active time. The UE in which DRX is configured may perform PDCCH monitoring during an active time. The UE in which DRX is configured does not perform PDCCH monitoring during inactivity time.

5 shows an example of a frame structure usable in a 3GPP-based wireless communication system.

The structure of the frame of FIG. 5 is only an example, and the number of subframes, the number of slots, and the number of symbols in the frame may be variously changed. In the NR system, OFDM numerology (eg, subcarrier spacing, SCS) may be set differently between a plurality of cells aggregated to one UE. Accordingly, the same number of symbols may be set differently. The (absolute time) duration of a time resource (eg, a subframe, a slot, or a transmission time interval (TTI)) consisting of may be set differently between aggregated cells, where the symbol is OFDM Symbol (or, cyclic prefix-orthogonal frequency division multiplexing (CP-OFDM) symbol), SC-FDMA symbol (or, discrete Fourier transform-spread-OFDM (discrete Fourier transform-spread-OFDM, DFT-s-OFDM) symbol) In this specification, a symbol, an OFDM-based symbol, an OFDM symbol, a CP-OFDM symbol, and a DFT-s-OFDM symbol may be replaced with each other.

5, in the NR system, uplink and downlink transmissions are organized into frames. Each frame has T _f = (Δf _max *N _f /100) *T _c = 10 ms duration, and is divided into two half-frames, each of which is 5 ms. Here, the basic time unit for NR is T _c = 1/(△f _max *N _f ), △f _max = 480*10 ³ Hz, and N _f =4096. For reference, the basic time unit for LTE is T _s = 1/(△f _ref *N _f,ref ), △f _ref = 15*10 ³ Hz, and N _f,ref =2048. T _c and T _f have a relationship of constant κ = T _c /T _f = 64. Each half-frame consists of five subframes, and the period T _sf of a single subframe is 1 ms. Subframes are further divided into slots, and the number of slots in the subframe depends on the subcarrier spacing. Each slot consists of 14 or 12 OFDM symbols based on a cyclic prefix. In a normal cyclic prefix (CP), each slot is composed of 14 OFDM symbols, and in the case of an extended CP, each slot is composed of 12 OFDM symbols. The numerology depends on the exponentially scalable subcarrier spacing Δf = 2 ^u *15 kHz. The following table shows the number of OFDM symbols per slot ( N ^slot _symb ), the number of slots per ^frame ( N ^{frame, u} _slot ), and the number of slots per subframe according to the subcarrier spacing △f = 2 ^u *15 kHz for the regular CP. It shows ( N ^{subframe, u} _slot ).

The following table shows the number of OFDM symbols per slot, the number of slots per frame, and the number of slots per subframe according to the subcarrier spacing Δf = 2 ^u *15 kHz for the extended CP.

6 illustrates a resource grid of a slot. A slot contains a plurality of (eg, 14 or 12) symbols in the time domain. For each neuron (e.g., subcarrier interval) and carrier, a common resource block (common resource block, CRB) N ^start indicated by higher layer signaling (e.g., radio resource control (RRC) signaling) ^, a, N ^size, _{grid ^u, x} * N _sc ^RB subcarriers and N ^{subframe, u} _symb OFDM symbol of a resource grid (grid), starting from the _grid is defined ^u. Here, N ^size,u _grid,x is the number of resource blocks (RBs) in the resource grid, and the subscript x is DL for downlink and UL for uplink. N ^RB _sc is the number of subcarriers per RB, and in a 3GPP-based wireless communication system, N ^RB _sc is usually 12. There is one resource grid for a given antenna port p , subcarrier spacing configuration u, and transmission direction (DL or UL). The carrier bandwidth N ^size,u _grid for the subcarrier spacing setting u is given to the UE by a higher layer parameter (eg, RRC parameter) from the network. Each element in the resource grid for antenna port p and subcarrier spacing u is referred to as a resource element (RE), and one complex symbol may be mapped to each resource element. Each resource element in the resource grid is uniquely identified by an index k in the frequency domain and an index l indicating a symbol position relative to a reference point in the time domain. In the NR system, the RB is defined by 12 consecutive subcarriers in the frequency domain. In the NR system, RBs may be classified into common resource blocks (CRBs) and physical resource blocks (PRBs). CRBs are numbered from 0 upwards in the frequency domain for the subcarrier spacing setting u . The center of subcarrier 0 of CRB 0 for subcarrier spacing setting u coincides with'point A', which is a common reference point for resource block grids. PRBs are defined within a bandwidth part (BWP) and are numbered from 0 to N ^size _BWP,i -1, where i is the number of the bandwidth part. The relationship between the common resource block n _CRB and the physical resource block n _{PRB in the} bandwidth part i is as follows: n _PRB = n _CRB + N ^size _BWP,i , where N ^size _BWP,i is the bandwidth part relative to CRB 0 This is the starting common resource block. The BWP includes a plurality of consecutive RBs in the frequency domain. The carrier may contain up to N (eg, 5) BWPs. The UE may be configured to have more than one BWP on a given component carrier. Data communication is performed through an activated BWP, and only a predetermined number (eg, one) of BWPs set to the UE may be activated on the corresponding carrier.

7 illustrates slot structures that can be used in a 3GPP-based system. In all 3GPP based systems, e.g., NR systems, each slot is a self-contained structure that may include i) a DL control channel, ii) DL or UL data, and/or iii) a UL control channel. Can have For example, the first N symbols in the slot may be used to transmit the DL control channel (hereinafter, the DL control region), and the last M symbols in the slot may be used to transmit the UL control channel (hereinafter, the UL control region ). N and M are each non-negative integer. A resource region (hereinafter, a data region) between the DL control region and the UL control region may be used for DL data transmission or UL data transmission. The symbols of a single slot may be divided into group(s) of consecutive symbols that can be used as DL, UL, or flexible. Hereinafter, information indicating how each of the symbols of the slot is used is referred to as a slot format. For example, the slot format may define which symbols in the slot are used for UL and which symbols are used for DL.

When a serving cell is to be operated in a TDD mode, the BS may set a pattern for UL and DL allocation for the serving cell through higher layer (eg, RRC) signaling. For example, the following parameters can be used to set the TDD DL-UL pattern:

-Dl-UL-TransmissionPeriodicity providing the period of the DL-UL pattern;

-NrofDownlinkSlots providing the number of consecutive full DL slots at the beginning of each DL-UL pattern, wherein the full slot is a slot having only downlink symbols;

-NrofDownlinkSymbols providing the number of consecutive DL symbols at the beginning of the slot immediately following the last complete DL slot;

-NrofUplinkSlots providing the number of consecutive full UL slots within the end of each DL-UL pattern, wherein the full UL slot is a slot having only uplink symbols; And

-NrofUplinkSymbols providing the number of consecutive UL symbols in the end of the slot immediately preceding the first full UL slot.

Among the symbols in the DL-UL pattern, the remaining symbols that are neither set as DL symbols nor UL symbols are flexible symbols.

The UE that has received the configuration regarding the TDD DL-UL pattern, that is, the TDD UL-DL configuration (eg, tdd-UL-DL-ConfigurationCommon , or tdd-UL-DLConfigurationDedicated ) through higher layer signaling, is slotted based on the configuration. Set the slot format for each slot across the fields.

Meanwhile, various combinations of a DL symbol, a UL symbol, and a flexible symbol for a symbol are possible, but a predetermined number of combinations may be predefined as slot formats, and the predefined slot formats can be identified by slot format indexes, respectively. I can. The following table illustrates some of the predefined slot formats. In the following table, D denotes a DL symbol, U denotes a UL symbol, and F denotes a flexible symbol.

In order to inform which of the predefined slot formats is used in a specific slot, the BS provides a combination of slot formats applicable to the corresponding serving cell for each cell through higher layer (e.g., RRC) signaling for a set of serving cells. A set of these may be set, and the UE may be configured to monitor a group-common PDCCH for a slot format indicator (SFI)(s) through higher layer (eg, RRC) signaling. Hereinafter, the DCI carried by the group-common PDCCH for SFI(s) is referred to as SFI DCI. DCI format 2_0 is used as the SFI DCI. For example, for each serving cell in the set of serving cells, the BS is the (start) position of the slot format combination ID (i.e., SFI-index) for the corresponding serving cell within the SFI DCI, the slot applicable to the serving cell. A set of format combinations, a reference subcarrier interval setting for each slot format in the slot format combination indicated by the SFI-index value in the SFI DCI may be provided to the UE. One or more slot formats are set for each slot format combination in the set of slot format combinations and a slot format combination ID (ie, SFI-index) is assigned. For example, when the BS wants to set a slot format combination with N slot formats, N slots among slot format indexes for slot formats predefined for the slot format combination (eg, see Table 4) Format indexes can be indicated. The BS informs the UE of the total length of the SFI-RNTI, which is the RNTI used for SFI, and the DCI payload scrambled with the SFI-RNTI to configure the UE to monitor the group-common PDCCH for SFIs. When the UE detects the PDCCH based on the SFI-RNTI, the UE may determine the slot format(s) for the corresponding serving cell from the SFI-index for the serving cell among SFI-indexes in the DCI payload within the PDCCH. .

Symbols indicated as flexible by the TDD DL-UL pattern configuration may be indicated as uplink, downlink or flexible by SFI DCI. Symbols indicated as downlink/uplink by TDD DL-UL pattern configuration are not overridden as uplink/downlink or flexible by SFI DCI.

If the TDD DL-UL pattern is not configured, the UE determines whether each slot is uplink or uplink and the symbol allocation within each slot is SFI DCI and/or DCI scheduling or triggering transmission of downlink or uplink signals (e.g., DCI format 1_0, DCI format 1_1, DCI format 1_2, DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 2_3).

A UE with carrier aggregation configured may be configured to use one or more cells. When a UE is configured to have a plurality of serving cells, the UE may be configured to have one or a plurality of cell groups. The UE may be configured to have multiple cell groups associated with different BSs. Alternatively, the UE may be configured to have a plurality of cell groups associated with a single BS. Each cell group of the UE is composed of one or more serving cells, and each cell group includes a single PUCCH cell in which PUCCH resources are configured. The PUCCH cell may be a Pcell or an Scell configured as a PUCCH cell among Scells of a corresponding cell group. Each serving cell of the UE belongs to one of the cell groups of the UE and does not belong to a plurality of cell groups.

The NR frequency bands are defined by two types of frequency ranges, FR1 and FR2, and FR2 is also referred to as a millimeter wave (mmW). The following table exemplifies frequency ranges in which NR can operate.

Hereinafter, physical channels that can be used in a 3GPP-based wireless communication system will be described in more detail.

PDCCH carries DCI. For example, the PDCCH (i.e., DCI) is a transmission format and resource allocation of a downlink shared channel (DL-SCH), resource allocation information for an uplink shared channel (UL-SCH), Located above the physical layer among the protocol stacks of UE/BS such as paging information for a paging channel (PCH), system information on the DL-SCH, and random access response (RAR) transmitted on the PDSCH. It carries resource allocation information for a control message of a layer (hereinafter, upper layer), a transmission power control command, and activation/release of configured scheduling (CS). DCI includes a cyclic redundancy check (CRC), and the CRC is masked/scrambled with various identifiers (e.g., radio network temporary identifier (RNTI)) according to the owner or usage of the PDCCH. For example, if the PDCCH is for a specific UE, the CRC is masked with a UE identifier (eg, cell RNTI (C-RNTI)) If the PDCCH is for paging, the CRC is masked with a paging RNTI (P-RNTI). If the PDCCH relates to system information (eg, system information block (SIB), then the CRC is masked with system information RNTI (system information RNTI, SI-RNTI)). If the PDCCH is for random access response, the CRC is Masked with random access RNTI (RA-RATI).

The PDCCH is transmitted through a control resource set (CORESET). One or more CORESET may be set to the UE. CORESET consists of a set of physical resource blocks (PRBs) with a time period of 1 to 3 OFDM symbols. PRBs constituting the CORESET and the CORESET duration may be provided to the UE through higher layer (eg, RRC) signaling. The set of PDCCH candidates within the set CORESET(s) is monitored according to the corresponding search space sets. In the present specification, monitoring implies decoding (aka, blind decoding) each PDCCH candidate according to monitored DCI formats. The master information block (MIB) on the PBCH provides parameters for monitoring the PDCCH (e.g., setting CORESET #0) to the UE for scheduling the PDSCH carrying the system information block (SIB1). do. The PBCH may also indicate that there is no associated SIB1, and in this case, the UE may be indicated not only a frequency range in which it can be assumed that there is no SSB associated with SSB1, but also another frequency to search for an SSB associated with SIB1. CORESET#0, which is a CORESET for scheduling at least SIB1, may be set through MIB or dedicated RRC signaling.

The set of PDCCH candidates monitored by the UE is defined in terms of PDCCH search space sets. The search space set may be a common search space (CSS) set or a UE-specific search space (USS) set. Each CORESET setting is associated with one or more sets of search spaces, and each set of search spaces is associated with one CORESET setting. The search space set is determined based on the following parameters provided to the UE by the BS.

- controlResourceSetId: an identifier for identifying the CORESET related to the search space set.

-monitoringSlotPeriodicityAndOffset : PDCCH monitoring period and PDCCH monitoring offset to set slots for PDCCH monitoring.

-duration : the number of consecutive slots that the search space lasts at every time (occasion), that is, at every period as given by monitoringSlotPeriodicityAndOffset .

- monitoringSymbolsWithinSlot:, slot within the PDCCH monitoring pattern for the first symbol (s) in the in CORESET slot for the PDCCH monitoring.

-nrofCandidates : The number of PDCCH candidates for each CCE aggregation level.

The UE monitors PDCCH candidates only at PDCCH monitoring occasions. The UE determines the PDCCH monitoring timing from the PDCCH monitoring periodicity, the PDCCH monitoring offset, and the PDCCH monitoring pattern in the slot. The parameter monitoringSymbolsWithinSlot represents, for example, the first symbol(s) for PDCCH monitoring in slots set for PDCCH monitoring (see, for example, parameters monitoringSlotPeriodicityAndOffset and duration ). For example, if monitoringSymbolsWithinSlot is 14-bit, the most significant (left) bit represents the first OFDM symbol in the slot, and the second most significant (left) bit represents the second OFDM symbol in the slot. In this way, monitoringSymbolsWithinSlot can represent the 14 OFDM symbols of the slot with bits each (respectively). For example, the bit(s) set to 1 of the bits in monitoringSymbolsWithinSlot identifies the first symbol(s) of the CORESET in the slot.

The following table exemplifies search space sets, related RNTIs, and usage examples.

The following table exemplifies DCI formats that the PDCCH can carry.

DCI format 0_0 is used to schedule a transport block (TB)-based (or TB-level) PUSCH, and DCI format 0_1 is a TB-based (or TB-level) PUSCH or code block group (CBG) ) Can be used to schedule a base (or CBG-level) PUSCH. DCI format 1_0 is used to schedule TB-based (or TB-level) PDSCH, DCI format 1_1 is used to schedule TB-based (or TB-level) PDSCH or CBG-based (or CBG-level) PDSCH I can. DCI format 0_0 and DCI format 1_0 have a fixed size after the BWP size is initially given by RRC, and DCI format 0_1 and DCI format 1_1 have the size of the DCI field to be changed through various RRC reconfiguration by BS. I can. In the case of CSS, DCI format 0_0 and DCI format 1_0 have a fixed size after the BWP size is initially given by RRC. In the case of USS, DCI format 0_0 and DCI format 1_0 have a fixed size except for the size of the frequency domain resource assignment (FDRA) field, but the size of the FDRA field is the size of the relevant parameter by BS. It can be changed through settings. In DCI format 0_1 and DCI format 1_1, the size of the DCI field may be changed through various RRC reconfiguration by the BS. DCI format 2_0 may be used to deliver dynamic slot format information (eg, SFI DCI) to the UE, and DCI format 2_1 may be used to deliver downlink pre-Emption information to the UE.

For example, each of DCI format 0_0 and DCI format 0_1 includes a frequency domain resource allocation field for scheduling of PUSCH, and each of DCI format 1_0 and DCI format 1_1 includes a frequency domain resource allocation field for scheduling of PDSCH. . The number of bits in the frequency domain resource field of each of DCI format 0_0 and DCI format 0_1 is determined based on N _RB ^UL,BWP, which is the size of an active or initial UL BWP. The number of bits in the frequency domain resource field of each of DCI format 1_0 and DCI format 1_1 is determined based on the size of the active or initial UL BWP, N _RB ^DL,BWP .

Fields defined in DCI formats are mapped to information bits a ₀ to a _A-1 as follows. The first field of the DCI format is mapped to the lowest order information bit a ₀ , and each successive field is mapped to higher order information bits. The most significant bit (MSB) of each field is mapped to the lowest order information bit for that field. For example, the MSB of the first field is mapped to a ₀ . If the number of information bits in the DCI format is less than 12 bits, zeros are appended to the DCI format until the payload size is 12. If necessary, the size of each DCI format is adjusted according to the following DCI size alignment.

If necessary, DCI size alignment is performed to reduce the complexity of blind decoding by the UE. For example, in some scenarios, if necessary, padding or truncation is applied to the DCI formats according to the following steps executed in the following order:

Step 0:

-DCI format 0_0 monitored in CSS is determined, where N _RB ^UL,BWP is the size of the initial UL BWP.

-Determine the DCI format 1_0 monitored in CSS, where N _RB ^DL,BWP is given by:

-The size of CORESET#0 if CORESET#0 is set for that cell; And

-The size of the initial DL BWP if CORESET#0 is not set for that cell.

-If DCI format 0_0 is monitored in CSS and prior to padding (prior to), if the number of information bits in the DCI format 0_0 is less than the payload size of the DCI format 1_0 monitored in CSS for scheduling the same serving cell, The number of zero padding bits is generated for DCI format 0_0 until the payload size is equal to that of the DCI format 1_0.

-If DCI format 0_0 is monitored in CSS, and if the number of information bits in the DCI format 0_0 prior to truncation is greater than the payload size of the DCI format 1_0 monitored in CSS for scheduling the same serving cell, the DCI format 0_0 The bitwidth of the frequency domain resource allocation field in the DCI format 0_0 is reduced by truncating the first few MBSs so that the size becomes the same as the size of the DCI format 1_0.

Step 1:

-Determine the DCI format 0_0 monitored in USS, where N _RB ^UL,BWP is the size of the active UL BWP.

-Determine the DCI format 1_0 monitored in USS, where N _RB ^DL,BWP is the size of the active DL BWP.

-If DCI format 0_0 is monitored in the USS, and if the number of information bits in the DCI format 0_0 prior to padding is less than the size of the DCI format 1_0 monitored in the USS for scheduling the same serving cell, the payload size is the Zeros are attached to the DCI format 0_0 until it is equal to that of DCI format 1_0.

-When DCI format 1_0 is monitored in the USS and if the number of information bits in the DCI format 1_0 prior to padding is less than the payload size of the DCI format 0_0 monitored in the USS for scheduling the same serving cell, the payload size Zeros are attached to the DCI format 1_0 until is equal to that of the DCI format 0_0.

Step 2:

-When the size of DCI format 0_1 is monitored in USS, if the size of DCI format 0_1 is the same as that of DCI format 0_0/1_0 monitored in another USS, zero padding of 1 bit is attached to DCI format 0_1.

-When monitored in USS, if the size of DCI format 1_1 is the same as that of DCI format 0_0/1_0 monitored in other USS, zero padding of 1 bit is attached to DCI format 1_1.

Step 3:

-When both of the following conditions are satisfied, the DCI size alignment process is complete:

-The total number of different DCI sizes is not more than 4 for that cell;

-The total number of different DCI sizes with C-RNTI configured to monitor is not more than 3 for that cell.

Step 4:

-Otherwisewise

-Remove the padding bit (if any) introduced in step 2 above.

-Determine the DCI format 1_0 monitored in USS, where N _RB ^DL,BWP is given by:

-The size of CORESET#0 if CORESET#0 is set for that cell; And

-The size of the initial DL BWP if CORESET#0 is not set for that cell.

-Determine the DCI format 0_0 monitored in USS, where N _RB ^UL,BWP is the size of the initial UL BWP.

-If the number of information bits in the DCI format 0_0 monitored by the USS prior to padding is less than the payload size of the DCI format 1_0 monitored by the USS for scheduling the same serving cell, the payload size is The number of zero padding bits is generated for DCI format 0_0 monitored in USS until equal to that of the DCI format 1_0 monitored in USS.

-If the number of information bits in the DCI format 0_0 monitored by the USS prior to truncation is greater than the payload size of the DCI format 1_0 monitored by the USS for scheduling the same serving cell, the size of the DCI format 0_0 monitored by the USS The bitwidth of the frequency domain resource allocation field in the DCI format 0_0 is reduced by truncating the first few MBSs so that is equal to the size of the DCI format 1_0 monitored in the USS.

Hereinafter, for convenience of description, the DCI size alignment process is referred to as a "first DCI size alignment process".

The UE is not expected to process the configuration resulting in the following after applying the above steps:

-The total number of different DCI sizes set to monitor is more than 4 for that cell; or

-The total number of different DCI sizes with C-RNTI configured to monitor is more than 3 for that cell; or

-The size of DCI format 0_0 in USS is the same as DCI format 0_1 in another USS; or

-The size of DCI format 1_0 in USS is the same as DCI format 1_1 in other USS.

The UE and BS may perform the DCI size alignment process. The BS may set parameters that affect the DCI size, and the UE may determine the DCI size(s) to be monitored by the UE in a corresponding cell based on the parameters. In the parameters affecting the DCI size, for example, frequency domain resource allocation, time domain resource allocation, PDSCH-to-HARQ feedback timing indicator, antenna port, BWP indicator, and/or SRS resource indicators influence the DCI size. I can go crazy. The UE and BS may determine whether to perform a DCI size alignment process for a cell based on the above parameters. The BS may transmit DCI(s) on the corresponding cell based on the DCI size(s) adjusted according to the DCI size alignment process. The UE expects to transmit DCI(s) having the DCI size(s) adjusted according to the DCI size alignment process for the cell on the cell, and may perform DCI monitoring (that is, PDCCH monitoring). In other words, the UE may perform DCI monitoring based on the DCI size(s) adjusted according to the DCI size alignment process for the cell.

PDSCH is a physical layer UL channel for UL data transport. The PDSCH carries downlink data (e.g., a DL-SCH transport block), and modulation methods such as Quadrature Phase Shift Keying (QPSK), 16 Quadrature Amplitude Modulation (QAM), 64 QAM, and 256 QAM are applied. A codeword is generated by encoding a transport block (TB). The PDSCH can carry up to two codewords. Scrambling and modulation mapping are performed for each codeword, and modulation symbols generated from each codeword may be mapped to one or more layers. Each layer is mapped to a radio resource together with a DMRS to generate an OFDM symbol signal, and is transmitted through a corresponding antenna port.

PUCCH means a physical layer UL channel for UCI transmission. PUCCH carries UCI (Uplink Control Information). UCI includes:

-Scheduling request (SR): This is information used to request UL-SCH resources.

-Hybrid automatic repeat request (HARQ)-acknowledgement (ACK): This is a response to a downlink data packet (eg, codeword) on the PDSCH. Indicates whether a downlink data packet has been successfully received by the communication device. HARQ-ACK 1 bit may be transmitted in response to a single codeword, and HARQ-ACK 2 bits may be transmitted in response to two codewords. The HARQ-ACK response includes positive ACK (simply, ACK), negative ACK (NACK), DTX or NACK/DTX. Here, the term HARQ-ACK is mixed with HARQ ACK/NACK, ACK/NACK, or A/N.

-Channel state information (CSI): This is feedback information on a downlink channel. CSI is channel quality information (CQI), rank indicator (rank indicator, RI), precoding matrix indicator (PMI), CSI-RS resource indicator (CSI-RS resource indicator, CRI), SS /PBCH resource block indicator, SSBRI), may include a layer indicator (layer indicator, LI). CSI may be divided into CSI part 1 and CSI part 2 according to the UCI type included in the CSI. For example, CRI, RI, and/or CQI for the first codeword may be included in CSI Part 1, and CQI for LI, PMI, and the second codeword may be included in CSI Part 2.

In this specification, for convenience, PUCCH resources set and/or indicated by the BS to the UE for HARQ-ACK, SR, and CSI transmission are referred to as HARQ-ACK PUCCH resources, SR PUCCH resources, and CSI PUCCH resources, respectively.

The PUCCH format may be classified as follows according to the UCI payload size and/or transmission length (eg, the number of symbols constituting the PUCCH resource). For information on the PUCCH format, refer to Table 8 together.

(0) PUCCH format 0 (PF0, F0)

-Supportable UCI payload size: up to K bits (e.g. K = 2)

-Number of OFDM symbols constituting a single PUCCH: 1 to X symbols (e.g., X = 2)

-Transmission structure: PUCCH format 0 consists of only UCI signals without DMRS, and the UE transmits the UCI state by selecting and transmitting one of a plurality of sequences. For example, the UE transmits a specific UCI to the BS by transmitting one of a plurality of sequences through PUCCH of PUCCH format 0. The UE transmits the PUCCH of PUCCH format 0 in the PUCCH resource for SR configuration corresponding to only when transmitting a positive SR.

-The setting for PUCCH format 0 includes the following parameters for the corresponding PUCCH resource: an index for initial cyclic transition, the number of symbols for PUCCH transmission, and the first symbol for the PUCCH transmission.

(1) PUCCH format 1 (PF1, F1)

-Supportable UCI payload size: up to K bits (e.g. K = 2)

-Number of OFDM symbols constituting a single PUCCH: Y ~ Z symbols (e.g., Y = 4, Z = 14)

-Transmission structure: DMRS and UCI are set/mapped to different OFDM symbols in the form of TDM. That is, the DMRS is transmitted in a symbol in which a modulation symbol is not transmitted. UCI is expressed by multiplying a specific sequence (eg, orthogonal cover code (OCC)) by a modulation (eg, QPSK) symbol. By applying a cyclic shift (CS)/OCC to both UCI and DMRS ( Code division multiplexing (CDM) is supported between multiple PUCCH resources (according to PUCCH format 1) within the same RB. PUCCH format 1 carries UCI with a maximum size of 2 bits, and the modulation symbol is in the time domain. Is spread by an orthogonal cover code (OCC) (which is set differently depending on whether or not frequency hopping).

-The setting for PUCCH format 1 includes the following parameters for the corresponding PUCCH resource: index for initial cyclic transition, number of symbols for PUCCH transmission, first symbol for PUCCH transmission, orthogonal cover code Index for ).

(2) PUCCH format 2 (PF2, F2)

-Supportable UCI payload size: more than K bits (e.g. K = 2)

-Transmission structure: DMRS and UCI are configured/mapped in the form of frequency division multiplex (FDM) within the same symbol. The UE transmits the coded UCI bits by applying only IFFT without DFT. PUCCH format 2 carries UCI of a bit size larger than K bits, and a modulation symbol is transmitted after FDM with DMRS. For example, the DMRS is located at symbol indexes #1, #4, #7, and #10 in a given resource block with a density of 1/3. A pseudo noise (PN) sequence is used for the DMRS sequence. Frequency hopping may be activated for 2-symbol PUCCH format 2.

-The setting for PUCCH format 2 includes the following parameters for the corresponding PUCCH resource: the number of PRBs, the number of symbols for PUCCH transmission, the first symbol for the PUCCH transmission.

(3) PUCCH format 3 (PF3, F3)

-Supportable UCI payload size: more than K bits (e.g. K = 2)

-Transmission structure: DMRS and UCI are set/mapped to different symbols in the form of TDM. The UE transmits by applying DFT to the coded UCI bits. PUCCH format 3 does not support UE multiplexing for the same time-frequency resource (eg, the same PRB).

-The setting for PUCCH format 3 includes the following parameters for the corresponding PUCCH resource: the number of PRBs, the number of symbols for PUCCH transmission, the first symbol for the PUCCH transmission.

(4) PUCCH format 4 (PF4, F4)

-Supportable UCI payload size: more than K bits (e.g. K = 2)

-Transmission structure: DMRS and UCI are set/mapped to different symbols in the form of TDM. PUCCH format 4 can multiplex up to 4 UEs in the same PRB by applying OCC at the front end of the DFT and CS (or interleaved FDM (IFDM) mapping) for DMRS. In other words, the modulation symbols of UCI are transmitted after DMRS and TDM (Time Division Multiplexing).

-The configuration for PUCCH format 4 includes the following parameters for the corresponding PUCCH resource: the number of symbols for PUCCH transmission, length for orthogonal cover code, index for orthogonal cover code, first symbol for the PUCCH transmission.

The following table illustrates PUCCH formats. Depending on the PUCCH transmission length, it may be divided into short PUCCH (formats 0, 2) and long PUCCH (formats 1, 3, 4).

PUCCH resources may be determined for each UCI type (eg, A/N, SR, CSI). PUCCH resources used for UCI transmission may be determined based on UCI (payload) size. For example, the BS configures a plurality of PUCCH resource sets to the UE, and the UE may select a specific PUCCH resource set corresponding to a specific range according to the range of the UCI (payload) size (eg, the number of UCI bits). For example, the UE may select one of the following PUCCH resource sets according to the number of UCI bits (N _UCI ):-PUCCH resource set #0, if the number of UCI bits =< 2

-PUCCH resource set #1, if 2< number of UCI bits =< N ₁

...

-PUCCH resource set #(K-1), if N _K-2 <Number of UCI bits =< N _K-1

Here, K is the number of PUCCH resource sets (K>1), and N _i is the maximum number of UCI bits supported by the PUCCH resource set #i. For example, PUCCH resource set #1 may be composed of resources of PUCCH format 0 to 1, and other PUCCH resource sets may be composed of resources of PUCCH format 2 to 4 (see Table 8).

The setting for each PUCCH resource includes a PUCCH resource index, a starting PRB index, a setting for one of PUCCH formats 0 to PUCCH 4, and the like. In the UE, the code rate for multiplexing HARQ-ACK, SR and CSI report(s) in PUCCH transmission using PUCCH format 2, PUCCH format 3, or PUCCH format 4 is set to the UE by the BS through the upper layer parameter maxCodeRate. . The upper layer parameter maxCodeRate is used to determine how to feed back UCI on PUCCH resources for PUCCH formats 2, 3 or 4.

When the UCI type is SR or CSI, the PUCCH resource to be used for UCI transmission in the PUCCH resource set may be configured to the UE by the network through higher layer signaling (eg, RRC signaling). When the UCI type is HARQ-ACK for the SPS (Semi-Persistent Scheduling) PDSCH, the PUCCH resource to be used for UCI transmission within the PUCCH resource set may be set to the UE by the network through higher layer signaling (e.g., RRC signaling). have. On the other hand, when the UCI type is HARQ-ACK for a PDSCH scheduled by DCI, a PUCCH resource to be used for UCI transmission within a PUCCH resource set may be scheduled based on DCI.

In the case of DCI-based PUCCH resource scheduling, the BS transmits the DCI to the UE through the PDCCH, and the PUCCH to be used for UCI transmission within a specific PUCCH resource set through the ACK/NACK resource indicator (ARI) in the DCI. Resources can be directed. ARI is used to indicate PUCCH resources for ACK/NACK transmission, and may also be referred to as a PUCCH resource indicator (PUCCH resource indicator, PRI). Here, DCI is a DCI used for PDSCH scheduling, and UCI may include HARQ-ACK for PDSCH. Meanwhile, the BS may set a PUCCH resource set consisting of PUCCH resources larger than the number of states that can be represented by the ARI using a (UE-specific) higher layer (eg, RRC) signal. At this time, the ARI indicates a PUCCH resource sub-set within the PUCCH resource set, and which PUCCH resource is to be used in the indicated PUCCH resource sub-set is transmission resource information for the PDCCH (e.g., PDCCH start control channel element (control channel element, CCE) index, etc.) based on an implicit rule.

The UE must have uplink resources available to the UE for UL-SCH data transmission, and must have downlink resources available to the UE for DL-SCH data reception. Uplink resources and downlink resources are assigned to the UE through resource allocation by the BS. Resource allocation may include time domain resource allocation (TDRA) and frequency domain resource allocation (FDRA). In this specification, uplink resource allocation is also referred to as an uplink grant, and downlink resource allocation is also referred to as a downlink allocation. The uplink grant is dynamically received on the PDCCH or in the RAR by the UE, or is set semi-persistently to the UE by RRC signaling from the BS. The downlink assignment is dynamically received on the PDCCH by the UE, or is semi-continuously set to the UE by RRC signaling from the BS.

In the UL, the BS may dynamically allocate uplink resources to the UE through PDCCH(s) addressed to a cell radio network temporary identifier (C-RNTI). The UE monitors the PDCCH(s) to find possible uplink grant(s) for UL transmission. In addition, the BS can allocate uplink resources using a grant set to the UE. Two types of set grants, type 1 and type 2, can be used. In the case of type 1, the BS directly provides a set uplink grant (including a period) through RRC signaling. In the case of type 2, the BS sets the period of the RRC configured uplink grant through RRC signaling, and the configured scheduling RNTI (configured scheduling RNTI, CS-RNTI) through the PDCCH (PDCCH addressed to CS-RNTI) The uplink grant may be signaled and activated or may be deactivated. For example, in the case of type 2, the PDCCH addressed as CS-RNTI indicates that the corresponding uplink grant can be implicitly reused according to a period set by RRC signaling until deactivation.

In the DL, the BS can dynamically allocate downlink resources to the UE through PDCCH(s) addressed with C-RNTI. The UE monitors the PDCCH(s) to find possible downlink assignments. In addition, the BS may allocate downlink resources to the UE using semi-static scheduling (SPS). The BS may set a period of downlink assignments set through RRC signaling, and may signal and activate the set downlink assignment through the PDCCH addressed to CS-RNTI, or deactivate it. For example, the PDCCH addressed to CS-RNTI indicates that the corresponding downlink assignment can be implicitly reused according to a period set by RRC signaling until deactivation.

Hereinafter, resource allocation by PDCCH and resource allocation by RRC will be described in more detail.

* Resource allocation by PDCCH: dynamic grant/allocation

The PDCCH can be used to schedule DL transmission on the PDSCH or UL transmission on the PUSCH. The DCI on the PDCCH for scheduling DL transmission includes a DL resource allocation including at least a modulation and coding format (e.g., a modulation and coding scheme (MCS) index I _MCS ), resource allocation, and HARQ information related to the DL-SCH. I can. The DCI on the PDCCH for scheduling UL transmission may include an uplink scheduling grant that includes at least a modulation and coding format, resource allocation, and HARQ information related to UL-SCH. The size and use of DCI carried by one PDCCH differs according to the DCI format. For example, DCI format 0_0, DCI format 0_1, or DCI format 0_2 may be used for scheduling a PUSCH, and DCI format 1_0, DCI format 1_1, or DCI format 1_2 may be used for scheduling a PDSCH. In particular, DCI format 0_2 and DCI format 1_2 have higher transmission reliability and lower latency than the transmission reliability and latency requirements guaranteed by DCI format 0_0, DCI format 0_1, DCI format 1_0, and DCI format 1_1. It can be used to schedule transmissions with requirements. Some implementations of this specification may be applied to UL data transmission based on DCL format 0_2. Some implementations of this specification may be applied to DL data reception based on DCI format 1_2.

8 illustrates an example of PDSCH time domain resource allocation by PDCCH and an example of PUSCH time domain resource allocation by PDCCH.

The DCI carried by the PDCCH to schedule the PDSCH or PUSCH includes a time domain resource assignment (TDRA) field, and the TDRA field is a row to an allocation table for PDSCH or PUSCH. ) Provide the value m for index m +1. A predefined default PDSCH time domain allocation is applied as the allocation table for the PDSCH, or the PDSCH time domain resource allocation table set by the BS through the RRC signaling pdsch-TimeDomainAllocationList is applied as the allocation table for the PDSCH. A predefined default PUSCH time domain allocation is applied as the allocation table for the PDSCH, or the PUSCH time domain resource allocation table set by the BS through the RRC signaling pusch-TimeDomainAllocationList is applied as the allocation table for the PUSCH. The PDSCH time domain resource allocation table to be applied and/or the PUSCH time domain resource allocation table to be applied may be determined according to a fixed/predefined rule (eg, see 3GPP TS 38.214).

In the PDSCH time domain resource settings, each indexed row is assigned a DL allocation-to-PDSCH slot offset K ₀ , a start and length indicator SLIV (or directly, a start position (eg, start symbol index S ) of the PDSCH in the slot, and an allocation length ( Yes, the number of symbols L )), defines the PDSCH mapping type. In the PUSCH time domain resource settings, each indexed row is a UL grant-to-PUSCH slot offset K ₂ , a start position of a PUSCH in a slot (eg, start symbol index S ) and an allocation length (eg, number of symbols L ), and PUSCH mapping Define the type. K ₀ for PDSCH or K ₂ for PUSCH indicates a difference between a slot with a PDCCH and a slot with a PDSCH or PUSCH corresponding to the PDCCH. SLIV is a joint indication of a start symbol S relative to the start of a slot having a PDSCH or PUSCH and the number L of consecutive symbols counted from the symbol S. In the case of the PDSCH/PUSCH mapping type, there are two types of mapping: one is mapping type A and the other is mapping type B. In the case of PDSCH/PUSCH mapping type A, a demodulation reference signal (DMRS) is located in a third symbol (symbol #2) or a fourth symbol (symbol #3) in a slot according to RRC signaling. In the case of PDSCH/PUSCH mapping type B, the DMRS is located in the first symbol allocated for PDSCH/PUSCH.

The scheduling DCI includes a frequency domain resource assignment (FDRA) field that provides assignment information on resource blocks used for PDSCH or PUSCH. For example, the FDRA field provides the UE with information about a cell for PDSCH or PUSCCH transmission, information about a BWP for PDSCH or PUSCH transmission, and information about resource blocks for PDSCH or PUSCH transmission.

* Resource allocation by RRC

As mentioned above, in the case of uplink, there are two types of transmission without a dynamic grant: an established grant type 1 and an established grant type 2. In the case of an established grant type 1, a UL grant is provided by RRC signaling and is a configured grant. Is saved. In the case of the configured grant type 2, the UL grant is provided by the PDCCH and is stored or cleared as an uplink grant configured based on L1 signaling indicating activation or deactivation of the configured uplink grant. Type 1 and Type 2 may be set by RRC signaling for each serving cell and for each BWP. Multiple settings can be active simultaneously on different serving cells.

When the configured grant type 1 is configured, the UE may receive the following parameters from the BS through RRC signaling:

-CS-RNTI for retransmission, cs-RNTI ;

-Periodicity , which is the set grant type 1 period;

-TimeDomainOffset indicating the offset of the resource for the system frame number (system frame number, SFN) = 0 in the time domain;

-A timeDomainAllocation value m , which provides a row index m + 1 pointing to the allocation table, indicating a combination of the start symbol S , length L , and PUSCH mapping type;

-FrequencyDomainAllocation providing frequency domain resource allocation; And

-McsAndTBS providing I _MCS indicating modulation order, target code rate and transport block size.

When setting the configuration grant type 1 for the serving cell by RRC, the UE stores the UL grant provided by the RRC as a configured uplink grant for the indicated serving cell, and in timeDomainOffset and S ( derived from SLIV ) Initialize or re-initialize so that the configured uplink grant starts in the corresponding symbol and recurs with periodicity . After the uplink grant is configured for the configured grant type 1, the UE may consider that the uplink grant recurs in association with each symbol that satisfies the following: [(SFN * numberOfSlotsPerFrame ( numberOfSymbolsPerSlot ) + ( slot number in the frame * numberOfSymbolsPerSlot ) + symbol number in the slot] = ( timeDomainOffset * numberOfSymbolsPerSlot + S + N * periodicity ) modulo (1024 * numberOfSlotsPerFrame * numberOfSymbolsPerSlot ), for all N >= 0, where numberOfSlotsPerFrame and numberOfSymbolsPerSlot are per frame The number of consecutive slots and consecutive OFDM symbols for each slot are shown respectively (see Tables 2 and 3).

When the configured grant type 2 is configured, the UE may receive the following parameters from the BS through RRC signaling:

- activation, CS-RNTI for the active release, and retransmission of cs-RNTI; And

-A periodicity providing the set grant type 2 period.

The actual uplink grant is provided to the UE by the PDCCH (addressed with CS-RNTI). After the uplink grant is configured for the configured grant type 2, the UE may consider that the uplink grant recurs in association with each symbol that satisfies the following: [(SFN * numberOfSlotsPerFrame * numberOfSymbolsPerSlot ) + (slot number in the frame * numberOfSymbolsPerSlot ) + symbol number in the slot] = [(SFN _{start time} * numberOfSlotsPerFrame * numberOfSymbolsPerSlot + slot _{start time} * numberOfSymbolsPerSlot + symbol _{start time} ) + N * periodicity ] modulo (1024 * numberOfSlotsPerFrame * numberOfSymbolsPerSlot ), for all >= 0, where SFN _{start time} , slot _{start time} , and symbol _{start time} are SFN, slot, and symbol of the first transmission opportunity of PUSCH after the set grant is (re-)initialized, respectively (respectively) And numberOfSlotsPerFrame and numberOfSymbolsPerSlot represent the number of consecutive slots per frame and consecutive OFDM symbols per slot, respectively (refer to Tables 2 and 3).

In the case of downlink, the UE may be configured with semi-persistent scheduling (SPS) for each serving cell and for each BWP by RRC signaling from the BS. In the case of DL SPS, DL allocation is provided to the UE by PDCCH, and is stored or removed based on L1 signaling indicating SPS activation or deactivation. When the SPS is configured, the UE may receive the following parameters from the BS through RRC signaling:

- activation, CS-RNTI for the active release, and retransmission of cs-RNTI;

-NrofHARQ-Processes providing the number of HARQ processes configured for SPS;

- periodicity of providing a downlink period of the assignment set for the SPS.

After downlink assignment is set for SPS, the UE may sequentially consider that the N-th downlink assignment occurs in a slot that satisfies the following: ( numberOfSlotsPerFrame * SFN + slot number in the frame ) = [( numberOfSlotsPerFrame * SFN _{start time} + slot _{start time} ) + N * periodicity * numberOfSlotsPerFrame / 10] modulo (1024 * numberOfSlotsPerFrame ), where SFN _{start time} and slot _{start time} are (re-)initialized The SFN, the slot, and the symbol of the first transmission of the PDSCH after that are respectively indicated, and numberOfSlotsPerFrame and numberOfSymbolsPerSlot indicate the number of consecutive slots per frame and consecutive OFDM symbols for each slot (see Tables 2 and 3).

The cyclic redundancy check (CRC) of the DCI format is scrambled with the CS-RNTI provided by the RRC parameter cs-RNTI , and the new data indicator field for the enabled transport block is set to 0. If there is, the UE confirms that the DL SPS allocated PDCCH or the configured UL grant type 2 PDCCH is valid for scheduling activation or scheduling cancellation. If all fields for the DCI format are set according to Table 9 or Table 10, validity confirmation of the DCI format is achieved. Table 9 exemplifies special fields for validating DL SPS and UL grant type 2 scheduling activation PDCCH, and Table 10 exemplifies special fields for validating DL SPS and UL grant type 2 scheduling release PDCCH.

The actual DL allocation or UL grant for DL SPS or UL grant type 2, and the corresponding modulation and coding scheme are resource allocation fields in the DCI format carried by the corresponding DL SPS or UL grant type 2 scheduling activation PDCCH ( Yes, it is provided by a TDRA field providing a TDRA value m, an FDRA field providing a frequency resource block allocation, and a modulation and coding scheme field). When validity check is achieved, the UE considers the information in the DCI format to be valid activation or valid release of DL SPS or configured UL grant type 2.

9 illustrates a HARQ-ACK transmission/reception process.

Referring to FIG. 9, the UE may detect a PDCCH in slot n. Thereafter, the UE may receive the PDSCH in slot n+K0 according to the scheduling information received through the PDCCH in slot n, and then transmit UCI through the PUCCH in slot n+K1. Here, the UCI includes a HARQ-ACK response for the PDSCH.

The DCI (eg, DCI format 1_0, DCI format 1_1) carried by the PDCCH scheduling the PDSCH may include the following information.

-Frequency domain resource assignment (FDRA): Represents a set of RBs allocated to the PDSCH.

-Time domain resource assignment (TDRA): DL assignment-to-PDSCH slot offset K0, the starting position of the PDSCH in the slot (eg, symbol index S) and length (eg, number of symbols L), PDSCH mapping type Represents. PDSCH mapping type A or PDSCH mapping type B may be indicated by TDRA. In the case of PDSCH mapping type A, the DMRS is located in the third symbol (symbol #2) or the fourth symbol (symbol #3) in the slot. In the case of PDSCH mapping type B, the DMRS is located in the first symbol allocated for the PDSCH.

-PDSCH-to-HARQ_feedback timing indicator: indicates K1.

When the PDSCH is configured to transmit a maximum of 1 TB, the HARQ-ACK response may consist of 1-bit. When the PDSCH is set to transmit up to two transport blocks (TB), the HARQ-ACK response is composed of 2-bits when spatial bundling is not set, and 1-bits when spatial bundling is set. I can. When the HARQ-ACK transmission time point for a plurality of PDSCHs is designated as slot n+K1, the UCI transmitted in slot n+K1 includes HARQ-ACK responses for the plurality of PDSCHs.

In this specification, a HARQ-ACK payload composed of HARQ-ACK bit(s) for one or a plurality of PDSCHs may be referred to as a HARQ-ACK codebook. The HARQ-ACK codebook may be classified into a semi-static HARQ-ACK codebook and a dynamic HARQ-ACK codebook according to a method in which the HARQ-ACK payload is determined.

In the case of a semi-static HARQ-ACK codebook, parameters related to the size of the HARQ-ACK payload to be reported by the UE are semi-statically set by a (UE-specific) upper layer (eg, RRC) signal. For example, the HARQ-ACK payload size of the semi-static HARQ-ACK codebook is, the (maximum) HARQ-ACK payload (size) transmitted through one PUCCH in one slot is all DL carriers set to the UE. (I.e., DL serving cells) and the number of HARQ-ACK bits corresponding to a combination of all DL scheduling slots (or PDSCH transmission slots or PDCCH monitoring slots) in which the HARQ-ACK transmission timing can be indicated (hereinafter, bundling window) Can be determined based on That is, in the semi-static HARQ-ACK codebook scheme, the size of the HARQ-ACK codebook is fixed (to a maximum value) regardless of the actual number of scheduled DL data. For example, the DL grant DCI (PDCCH) includes PDSCH to HARQ-ACK timing information, and the PDSCH-to-HARQ-ACK timing information may have one of a plurality of values (eg, k). For example, if the PDSCH is received in slot #m and the PDSCH to HARQ-ACK timing information in the DL grant DCI (PDCCH) scheduling the PDSCH indicates k, the HARQ-ACK information for the PDSCH is slot # It can be transmitted at (m+k). For example, it can be given as k ∈ {1, 2, 3, 4, 5, 6, 7, 8}. Meanwhile, when HARQ-ACK information is transmitted in slot #n, the HARQ-ACK information may include a maximum possible HARQ-ACK based on the bundling window. That is, HARQ-ACK information of slot #n may include HARQ-ACK corresponding to slot #(n-k). For example, if k ∈ {1, 2, 3, 4, 5, 6, 7, 8}, HARQ-ACK information of slot #n is slot #(n-8)~ regardless of actual DL data reception. Includes HARQ-ACK corresponding to slot # (n-1) (ie, the maximum number of HARQ-ACKs). Here, the HARQ-ACK information may be replaced with the HARQ-ACK codebook and the HARQ-ACK payload. In addition, the slot may be understood/replaced as a candidate opportunity for DL data reception. As an example, the bundling window is determined based on the PDSCH-to-HARQ-ACK timing based on the HARQ-ACK slot, and the PDSCH-to-HARQ-ACK timing set has a pre-defined value (eg, { 1, 2, 3, 4, 5, 6, 7, 8}), and may be set by higher layer (RRC) signaling. Meanwhile, in the case of a dynamic HARQ-ACK codebook, the size of the HARQ-ACK payload to be reported by the UE may be dynamically changed by DCI or the like. In the dynamic HARQ-ACK codebook scheme, the DL scheduling DCI may include counter-DAI (ie, c-DAI) and/or total-DAI (ie, t-DAI). Here, DAI means a downlink assignment index, and is used by the BS to inform the UE of the transmitted or scheduled PDSCH(s) to be included in one HARQ-ACK transmission. In particular, c-DAI is an index indicating the order of PDCCHs carrying DL scheduling DCI (hereinafter, DL scheduling PDCCH), and t-DAI is the total number of DL scheduling PDCCHs up to the current slot in which the PDCCH with t-DAI is located. It is an index to indicate.

In the NR system, a method of implementing a plurality of logical networks on a single physical network is being considered. Here, the logical network must be able to support services having various requirements (eg, eMBB, mMTC, URLLC, etc.). Therefore, the physical layer of the NR is designed to support a flexible transmission structure in consideration of requirements for various services. As an example, the physical layer of the NR may change the OFDM symbol length (OFDM symbol duration) and subcarrier spacing (SCS) (hereinafter, OFDM neurology) as necessary. Also, transmission resources of physical channels may be changed within a certain range (in units of symbols). For example, in the NR, the transmission length/transmission start time of the PUCCH (resource) and the PUSCH (resource) may be flexibly set within a certain range.

Meanwhile, in a wireless communication system including a BS and a UE, when the UE transmits UCI to PUCCH, PUCCH resources may overlap with other PUCCH resources or PUSCH resources in the time axis. For example, from the viewpoint of the same UE (in the same slot) (1) (for different UCI transmission) PUCCH (resource) and PUCCH (resource), or (2) PUCCH (resource) and PUSCH (resource) are time axis Can be nested in Meanwhile, the UE may not support simultaneous PUCCH-PUCCH transmission or simultaneous PUCCH-PUSCH transmission (according to the limitation of UE capability or configuration information received from the BS). In addition, it may not be allowed for the UE to simultaneously transmit multiple UL channels within a certain time range.

In this specification, when a plurality of UL channels to be transmitted by a UE exist within a predetermined time range, methods of handling the plurality of UL channels are described. In addition, in the present specification, methods of handling UCI and/or data that should have been transmitted/received on the plurality of UL channels are described. In the description of examples of this specification, the following terms are used.

-UCI: refers to control information transmitted by the UE by UL. UCI includes various types of control information (ie, UCI type). For example, UCI may include HARQ-ACK (briefly, A/N, AN), SR, and/or CSI.

-UCI multiplexing: This may mean an operation of transmitting different UCI (types) through a common physical layer UL channel (eg, PUCCH, PUSCH). UCI multiplexing may include multiplexing different UCIs (types). For convenience, the multiplexed UCI is referred to as MUX UCI. In addition, UCI multiplexing may include an operation performed in relation to the MUX UCI. For example, UCI multiplexing may include a process of determining UL channel resources to transmit MUX UCI.

-UCI/data multiplexing: This may mean an operation of transmitting UCI and data through a common physical layer UL channel (eg, PUSCH). UCI/data multiplexing may include multiplexing UCI and data. For convenience, the multiplexed UCI is referred to as MUX UCI/Data. In addition, UCI/data multiplexing may include an operation performed in relation to MUX UCI/Data. For example, UCI/data multiplexing may include a process of determining UL channel resources to transmit MUX UCI/Data.

-Slot: It means the basic time unit or time interval for data scheduling. The slot includes a plurality of symbols. Here, the symbol includes an OFDM-based symbol (eg, CP-OFDM symbol, DFT-s-OFDM symbol).

-Superimposed UL channel resource(s): means (at least partially) overlapped UL channel (eg, PUCCH, PUSCH) resource(s) on the time axis within a predetermined time interval (eg, slot). The overlapped UL channel resource(s) may mean UL channel resource(s) before performing UCI multiplexing. In this specification, UL channels (at least partially) overlapping each other on the time axis may be referred to as UL channels colliding in time or in the time domain.

10 shows an example of multiplexing UCI to PUSCH. When PUCCH resource(s) and PUSCH resources overlap in the slot, and simultaneous PUCCH-PUSCH transmission is not configured, UCI may be transmitted through PUSCH as shown. Transmitting UCI through PUSCH is referred to as UCI piggyback or PUSCH piggyback. In particular, FIG. 10 illustrates a case where HARQ-ACK and CSI are carried on PUSCH resources.

When a plurality of UL channels overlap within a predetermined time interval, in order for the BS to properly receive the UL channel(s) transmitted by the UE, a method for the UE to process the plurality of UL channels must be defined. . Hereinafter, methods of handling collisions between UL channels are described.

11 shows an example of a process in which a UE having PUCCHs overlapping in a single slot handles collision between UL channels.

For UCI transmission, the UE may determine a PUCCH resource for each UCI. Each PUCCH resource may be defined by a start symbol and a transmission length. When PUCCH resources for PUCCH transmissions overlap in a single slot, the UE may perform UCI multiplexing based on the PUCCH resource having the fastest start symbol. For example, the UE may determine the PUCCH resource(s) (hereinafter, PUCCH resource(s) B) overlapping (in time) based on the PUCCH resource (hereinafter, PUCCH resource A) with the fastest start symbol in the slot. Yes (S1101). The UE may apply a UCI multiplexing rule to the PUCCH resource A and the PUCCH resource (s) B. For example, based on the UCI A of the PUCCH resource A and the UCI B of the PUCCH resource(s) B, a MUX UCI including all or part of the UCI A and the UCI B is obtained according to a UCI multiplexing rule. I can. The UE may determine a single PUCCH resource (hereinafter, a MUX PUCCH resource) to multiplex the UCI associated with the PUCCH resource A and the PUCCH resource (s) B (S1103). For example, the UE determines a PUCCH resource set (hereinafter, PUCCH resource set X) corresponding to the payload size of the MUX UCI among PUCCH resource sets configured or available to the UE, and the PUCCH resource set X One of the belonging PUCCH resources is determined as the MUX PUCCH resource. For example, the UE belongs to the PUCCH resource set X by using the PUCCH resource indicator field in the last DCI among DCIs having the PDSCH-to-HARQ_feedback timing indicator field indicating the same slot for the PUCCH transmission. One of the PUCCH resources may be determined as the MUX PUCCH resource. The UE may determine the total number of PRBs of the MUX PUCCH resources based on the payload size of the MUX UCI and the maximum code rate for the PUCCH format of the MUX PUCCH resource. If the MUX PUCCH resource overlaps with other PUCCH resources (except for the PUCCH resource A and the PUCCH resource(s) B), the UE is the MUX PUCCH resource (or among the remaining PUCCH resources including the MUX PUCCH resource) The operation described above may be performed again based on the PUCCH resource having the fastest start symbol).

12 illustrates cases of UCI multiplexing according to FIG. 11. Referring to FIG. 12, when a plurality of PUCCH resources overlap in a slot, UCI multiplexing may be performed based on the fastest PUCCH resource A (eg, the fastest start symbol). In FIG. 12, Case 1 and Case 2 illustrate a case where a first PUCCH resource overlaps another PUCCH resource. In this case, the process of FIG. 11 may be performed while the first PUCCH resource is regarded as the fastest PUCCH resource A. On the other hand, Case 3 illustrates a case where the first PUCCH resource does not overlap with other PUCCH resources, and the second PUCCH resource overlaps with other PUCCH resources. In case 3, UCI multiplexing is not performed on the first PUCCH resource. Instead, the process of FIG. 11 may be performed while the second PUCCH resource is regarded as the fastest PUCCH resource A. Case 2 is a case where the MUX PUCCH resource determined to transmit the multiplexed UCI overlaps with other PUCCH resources. In this case, the process of FIG. 11 may be additionally performed while the MUX PUCCH resource (or the fastest (eg, the fastest starting symbol) PUCCH resource among the remaining PUCCHs including the same) is considered as the fastest PUCCH resource A. .

13 illustrates a process in which a UE having PUCCH and PUSCH overlapping in a single slot handles collision between UL channels.

For UCI transmission, the UE may determine a PUCCH resource (S1301). Determining the PUCCH resource for UCI may include determining the MUX PUCCH resource. In other words, determining the PUCCH resource for UCI by the UE may include determining the MUX PUCCH resource based on a plurality of PUCCHs overlapping in the slot.

The UE may perform UCI piggyback on PUSCH resources based on the determined (MUX) PUCCH resource (S1303). For example, when there is a PUSCH resource (where multiplexed UCI transmission is allowed), the UE may apply a UCI multiplexing rule to PUCCH resource(s) overlapping the PUSCH resource (in the time axis). The UE may transmit UCI through PUSCH.

If the PUSCH overlapping the determined PUCCH resource is not in the slot, S1503 is omitted, and UCI may be transmitted through the PUCCH.

Meanwhile, when the determined PUCCH resource overlaps a plurality of PUSCHs on a time axis, the UE may multiplex UCI on one of the plurality of PUSCHs. For example, when the UE intends to transmit the plurality of PUSCHs on each (respective) serving cells, the UE may select a specific serving cell (eg, a serving cell having the smallest serving cell index) among the serving cells. UCI can be multiplexed on the PUSCH. When there are more than one PUSCH in the slot on the specific serving cell, the UE may multiplex the UCI on the fastest PUSCH transmitted in the slot.

14 illustrates UCI multiplexing in consideration of a timeline condition. When the UE performs UCI and/or data multiplexing for PUCCH(s) and/or PUSCH(s) overlapping on the time axis, for UCI and/or data multiplexing due to flexible UL timing settings for PUCCH or PUSCH The UE may run out of processing time. In order to prevent the UE from running out of processing time, in the UCI/data multiplexing process for overlapping PUCCH(s) and/or PUSCH(s) (on the time axis), the following two timeline conditions (hereinafter, multiplexing time Line conditions) are considered.

(1) The last symbol of the PDSCH corresponding to the HARQ-ACK information is received before N1+ time from the start symbol of the fastest channel among the overlapping PUCCH(s) and/or PUSCH(s) (on the time axis). T1 may be determined based on i) the minimum PDSCH processing time N1 defined according to the UE processing capability, ii) d1 predefined as an integer value greater than or equal to 0 depending on the position of the scheduled symbol, the DMRS position in the PUSCH, and BWP switching. have.

For example, T1 can be determined as follows: T1 = (N1 + d1)*(2048+144)*κ*2 ^-u *T _c . N1 is based on u in Tables 11 and 12, respectively, for UE processing capabilities #1 and #2, where μ is the one that results in the largest T1 of ( μ _PDCCH , μ _PDSCH , μ _UL ), where μ _PDCCH is Corresponds to the subcarrier spacing of the PDCCH scheduling the PDSCH, μ _PDSCH corresponds to the subcarrier spacing of the scheduled PDSCH, μ _UL corresponds to the subcarrier spacing of the UL channel to which HARQ-ACK is to be transmitted, κ = T _c / T _f = 64. In the case of N _1,0 in Table 11, if the PDSCH DMRS position l ₁ = 12 of the additional DMRS, then N _1,0 =14, otherwise N _1,0 =13 (see section 7.4.1.1.2 of 3GPP TS 38.211) . For PDSCH mapping type A, if the last symbol of the PDSCH is on the i-th slot of the slot, d1=7-i for i<7, otherwise d1=0. For UE processing capability #1, if the PDSCH is mapping type B, if the number of allocated PDSCH symbols is 7, d1=0, if the number of allocated PDSCH symbols is 4, d1=3, and allocated PDSCH If the number of symbols is 2, d1=3+d, where d is the number of overlapping symbols between the scheduling PDCCH and the scheduled PDSCH. For UE processing capability #2, if the PDSCH is mapping type B, if the number of allocated PDSCH symbols is 7, d1=0, and if the number of allocated PDSCH symbols is 4, d1 is the scheduling PDCCH and the scheduled PDSCH. May be the number of overlapping symbols, and if the number of allocated PDSCH symbols is 2, if the scheduling PDSCH is in the 3-symbol CORESET and the CORESET and the PDSCH have the same start symbol, d1 = 3; otherwise, d1 is the It may be the number of overlapping symbols of the scheduled PDCCH and the scheduled PDSCH. In this specification, T1 may be expressed as T_proc,1.

(2) The last symbol of (e.g., triggering) PDCCH indicating PUCCH or PUSCH transmission is T2 time before the start symbol of the fastest channel among overlapping PUCCH(s) and/or PUSCH(s) (in the time axis) Is received. T2 may be determined based on i) the minimum PUSCH preparation time N2 defined according to the UE PUSCH timing capability, ii) d2, which is predefined as an integer value greater than or equal to 0 according to the position of the scheduled symbol or BWP switching. . d2 can be divided into d _2,1 related to the position of the scheduled symbol and d _2,2 related to the switching of the BWP.

For example, T2 can be determined as follows: T2 = max{(N2 + d _2,1 )*(2048+144)*κ*2 ^-u *T _c , d _2,2 }. N2 is based on u in Tables 13 and 14 for UE timing capabilities #1 and #2, respectively, where μ is the one that results in the largest T2 of ( μ _DL , μ _UL ), where μ _DL is the PUSCH It corresponds to the subcarrier spacing of the PDCCH carrying the scheduling DCI, μ _UL corresponds to the subcarrier spacing of the PUSCH, and κ = T _c /T _f = 64. If the first symbol of PUSCH allocation is composed of only DM-RS, d _2,1 = 0, otherwise, d _2,1 = 1. If the scheduling DCI triggered a switch of the BWP, d _2,2 is equal to the switching time, otherwise d _2,2 =0. The switching time may be differently defined according to the frequency range. For example, the switching time may be set to be 0.5 ms for the frequency range FR1 and 0.25 ms for the frequency range FR2. In this specification, T2 may be expressed as T_proc,2.

The following tables illustrate processing time according to UE processing capability. In particular, Table 11 illustrates the PDSCH processing time for the PDSCH processing capability #1 of the UE, Table 12 illustrates the PDSCH processing time for the PDSCH processing capability #2 of the UE, and Table 13 is the PUSCH timing capability of the UE #1 To illustrate the PUSCH preparation time for, and Table 14 illustrates the PUSCH preparation time for the timing capability #2 of the UE.

When a UE configured to multiplex different UCI types within one PUCCH intends to transmit a plurality of overlapping PUCCHs in a slot or to transmit overlapping PUCCH(s) and PUSCH(s) in a slot, the UE has specific conditions If satisfied, the corresponding UCI types can be multiplexed. The specific conditions may include multiplexing timeline condition(s). For example, PUCCH(s) and PUSCH(s) to which UCI multiplexing is applied in FIGS. 11 to 13 may be UL channels satisfying the multiplexing timeline condition(s). Referring to FIG. 14, the UE may have to transmit a plurality of UL channels (eg, UL channels #1 to #4) in the same slot. Here, UL CH #1 may be a PUSCH scheduled by PDCCH #1. In addition, UL CH #2 may be a PUCCH for transmitting HARQ-ACK for PDSCH. PDSCH is scheduled by PDCCH #2, and resources of UL CH #2 may also be indicated by PDCCH #2.

At this time, when the UL channels overlapping on the time axis (eg, UL channels #1 to #3) satisfy the multiplexing timeline condition, the UE performs UCI multiplexing on the UL channels #1 to #3 overlapping on the time axis. can do. For example, the UE may check whether the first symbol of UL CH #3 satisfies the T1 condition from the last symbol of the PDSCH. In addition, the UE may check whether the first symbol of UL CH #3 from the last symbol of PDCCH #1 satisfies the T2 condition. If the multiplexing timeline condition is satisfied, the UE may perform UCI multiplexing on UL channels #1 to #3. On the other hand, when the fastest UL channel (eg, the UL channel with the fastest start symbol) among the overlapping UL channels does not satisfy the multiplexing timeline condition, multiplexing all corresponding UCI types of the UE may not be allowed.

15 illustrates transmission of a plurality of HARQ-ACK PUCCHs in a slot.

The current NR standard document (eg, 3GPP TS 38.213 V15.2.0) stipulates that the UE does not expect to transmit more than one PUCCH with HARQ-ACK information in a slot. Therefore, according to the current NR standard document, the UE can transmit at most one PUCCH having HARQ-ACK information in one slot. To prevent a situation in which the UE cannot send HARQ-ACK information due to the limitation of the number of HARQ-ACK PUCCHs that can be transmitted by the UE, BS schedules downlink so that HARQ-ACK information can be multiplexed on one PUCCH resource. Should be done. However, when considering a service with strict latency and reliability requirements, such as URLLC service, a scheme in which a plurality of HARQ-ACK feedbacks are concentrated only on one PUCCH in a slot is in terms of PUCCH performance. It may not be desirable. In addition, in order to support a latency-critical service, it may be required that the BS schedules a plurality of consecutive PDSCHs having a short duration within one slot. Even though the UE can transmit the PUCCH in any symbol(s) in the slot by the setting/instruction of the BS, if only one HARQ-ACK PUCCH transmission is allowed in the slot, the BS quickly back-to the PDSCHs. It is inevitable that scheduling with -back and the UE can quickly perform HARQ-ACK feedback. Therefore, for more flexible and efficient resource use and service support, it is preferable to allow a plurality of HARQ-ACK PUCCHs (or PUSCHs) to be transmitted in one slot as illustrated in FIG. 15.

As one of the schemes for reducing downlink signaling overhead among schemes for supporting highly reliable communication services within a short time in packet transmission/reception like URLLC, a DCI field having a configurable size is configured. May be considered. In other words, it is possible to easily perform scheduling for URLLC support or reduce downlink signaling overhead by configuring the DCI field(s) differently according to the needs of the BS. For example, in order to improve the PDCCH reception reliability in the UE, the BS reduces the total payload size of the DCI by removing a specific field among DCI fields that may be included in the DCI or reducing the size of the specific field. Can be reduced. Hereinafter, examples of the present specification that can be applied to scenarios in which DCI field(s) that can be included in DCI or the DCI format in which the corresponding size(s) is configurable are used are described.

<DCI 크기 정렬(DCI size alignment)><DCI size alignment>

In some scenarios the UE does not expect to be set up to monitor more than 4 different DCI sizes for a particular cell. Also in some scenarios the UE does not expect to be configured to monitor more than three different (CRC scrambled with C-RNTI) DCI sizes for a particular cell.

Specific target service and/or QoS and/or block error rate (BLER) requirements and/or reliability requirements and/or latency requirements and/or processing time ) Corresponding to the control channel (or a control channel for scheduling a data channel corresponding thereto) includes DCI information. DCI fields to have a separate DCI size different from the existing DCI size to support the specific target service and/or QoS and/or BLER requirements and/or reliability requirements and/or delay requirements and/or processing time A situation can arise where the sizes are set. In this case, it may not be desirable (or not possible) to separately define the monitoring capability of the UE for the additional DCI size in addition to the monitoring capability for the existing DCI size. It may be necessary to perform DCI size alignment/adjustment when a separate DCI size occurs without changing the monitoring-related UE capability for different DCI sizes. A control channel (or a control channel scheduling the corresponding data channel) corresponding to a specific target service and/or QoS and/or BLER requirements and/or reliability requirements and/or delay requirements and/or processing time is included. In some scenarios in which the field(s) of the DCI to be set is set, DCI size alignment/adjustment to avoid exceeding the monitoring-related UE capability for different DCI sizes may be performed as follows.

For convenience of description, hereinafter, the specific target service and/or QoS and/or BLER requirements and/or reliability requirements and/or delay requirements, and/or control channels corresponding to processing time (or corresponding data DCI (eg, DCI field(s) included in DCI, or DCI in which the size(s) of DCI field(s) included in DCI is settable by BS) included in the control channel for scheduling the channel is "URLLC DCI format". Further, DCI that is not "URLLC DCI format" is referred to as "non-URLLC (non-URLLC) DCI format". "URLLC DCI format" may be referred to as "configurable DCI format", and "non-URLLC DCI format" may be referred to as "non-configurable DCI format". In the non-configurable DCI format, there may be fields whose field size may change according to the configuration, but in the configurable DCI format, the size of the configurable field may be smaller than that in the non-configurable DCI format. In addition, in the non-configurable DCI format, a non-configurable field may be included or not included in the DCI format according to the needs of the BS in the configurable DCI format, and the size may be adjusted. As a non-configurable DCI format (eg, non-URLLC DCI format), there may be, for example, DCI format 0_0, DCI format 1_0, DCI format 0_1, and/or DCI format 1_1. For example, a field size is fixed for DCI format 0_0, DCI format 0_1, DCI format 1_1, and/or DCI format 0_1, but configurable DCI format for certain fields or some fields among the fields constituting the DCI format. It may be allowed to be set by the BS to be included or not included in the corresponding DCI format. As another example, a specific field or some fields among the fields constituting the DCI format cannot be set to have a very small number of bits in DCI format 0_0, DCI format 0_1, DCI format 1_1, and/or DCI format 0_1, but can be set DCI For the format it can be allowed to be set by the BS to have a very small number of bits. “URLLC DCI format” is a newly introduced DCI format, so it may be referred to as “new DCI format” or “non-fallback DCI format”, and DCI format 0_0, DCI format 0_1, DCI format 1_1, and/or DCI format 0_1 It may also be referred to as “legacy DCI format” or “fallback DCI”.

Examples of the present specification described below are, in some scenarios, after the above-described first DCI size alignment process is over, the number of different DCI sizes to be monitored by the UE may be monitored by the UE due to the size of the URLLC DCI format. It can be applied in the case of exceeding the capability regarding the maximum number of different DCI sizes. The following examples may be combined and applied together as long as they are not mutually disposed.

16 illustrates a flow of DCI transmission/reception according to some implementations of this specification.

Based on the DCI size alignment process according to the example(s) of the present specification, the BS may determine the DCI size(s) to be used for DCI transmission (S1601). The BS may transmit DCI(s) (on a cell) based on the determined DCI size(s). Based on the DCI size alignment process according to the example(s) of this specification, the UE may determine the DCI size(s) to be monitored (on the cell). The UE may monitor the DCI(s) (on the cell) based on the determined DCI size(s) (S1603). When the DCI size alignment process is applied, the DCI size actually used by the BS for transmission may be the DCI size obtained by completing the DCI size alignment, and the DCI size actually used by the UE for DCI monitoring, that is, DCI decoding, is DCI. It may be the DCI size obtained by completing the size alignment.

Hereinafter, the non-fallback DCI may correspond to the DCI of the URLLC DCI format (hereinafter, URLLC DCI), and the fallback DCI corresponds to the DCI of the non-URLLC DCI format (hereinafter, non-URLLC DCI). can do. Here, the non-URLLC DCI may mean DCI having a DCI format other than the URLLC DCI format.

Based on the aligned DCI size(s), for example, the DCI(s) (on the cell) based on the DCI size(s) determined based on the DCI size alignment process according to the option(s) described later Can be monitored. For example, the UE receives at least one of non-fallback DCI(s) and fallback DCI(s), and the UE receives DCI size(s) aligned according to option(s) described below. ) Can be decoded. The UE may transmit a UL channel such as PUCCH or PUSCH or receive a DL channel such as PDSCH based on a decoding result. Here, the UL channel and the DL channel may be channels in units of slots or channels in units of mini-slots. Alternatively, the UL channel and the DL channel may be channels for eMBB traffic or channels for URLLC traffic.

Based on the aligned DCI size(s), for example, the DCI(s) (on the cell) based on the DCI size(s) determined based on the DCI size alignment process according to the option(s) to be described later. Can be transmitted. For example, the BS may arrange the size(s) of the non-fallback DCI(s) and/or the size(s) of the fallback DCI(s) according to the option(s) described below. And the BS may transmit non-fallback DCI(s) and/or fallback DCI(s) to the UE based on the aligned DCI size(s). The BS may receive a UL channel such as PUCCH or PUSCH or transmit a DL channel such as PDSCH based on the transmitted DCI(s). For this reason, the UL channel and the DL channel may be channels in units of slots or channels in units of mini-slots. Alternatively, the UL channel and the DL channel may be channels for eMBB traffic or channels for URLLC traffic.

In this specification, the DL DCI format may be a DCI format for scheduling or triggering DL transmission, and the UL DCI format may be a DCI format for scheduling or triggering UL transmission. For example, in the present specification, the DL DCI format may mean a DCI format for scheduling a PDSCH or a DCI format for triggering transmission of a PUCCH, and the UL DCI format may mean a DCI format for scheduling a PUSCH.

* Option 1

17 illustrates a DCI size alignment process according to an example of the present specification. In particular, FIG. 17 illustrates a DCI size alignment process according to Option 1.

The size of the remaining (some or all) DCI formats other than the URLLC DCI format can be adjusted so as not to exceed the capability for the maximum number of different DCI sizes that the UE can monitor. In some implementations of the present specification, the size of the DCI format other than the URLLC DCI format is the size of the DL DCI format of the URLLC DCI format (hereinafter, the URLLC DL DCI format) and the UL DCI format of the URLLC DCI format (hereinafter, the URLLC UL DCI format). Format) can also be adjusted after aligning its size. For example, referring to FIG. 17, the UE or BS may perform DCI size alignment for non-fallback DCI format(s) (S1701) and DCI size alignment for fallback format(s) ( S1703). In some implementations of this specification, the DCI size alignment for the fallback format(s) exceeds the ability for the maximum number of different DCI sizes that the UE can monitor after applying the size alignment for the non-fallback DCI format(s). It can be done if you do. DCI size alignment causes redundant bit(s) for the corresponding format or is accompanied by scheduling restrictions. Since the URLLC DCI format that can be used for URLLC scheduling, which is expected to have a relatively sporadic traffic pattern, will have a lower frequency of use, there may be little adverse effect of such DCI size matching for the URLLC DCI format. Option 1 performs DCI size matching from the URLLC DCI format, which is a DCI format that is expected to be used less frequently, and only if it exceeds the DCI size budget of the UE, it is applied to another DCI format (which is relatively more frequent). DCI size matching may be advantageous in that it is possible to reduce adverse effects of DCI size matching.

When the sizes of the other DCI formats are aligned after the sizes of the URLLC DCI format are aligned, zero bit padding or bit truncation may be applied so that the sizes of the DCI format 1_1 and DCI format 0_1 are aligned. Here, zero-bit padding or bit truncation is applied to a DCI format with a smaller number of bits among DCI format 1_1 and DCI format 0_1 to align the DCI size with the size of a DCI format with a larger number of bits, or It may mean that some of the bit(s) of the DCI format having a larger number of bits among the DCI format 1_1 and the DCI format 0_1 are truncated to align the DCI size with the size of the DCI format with a smaller number of bits.

In some implementations related to option 1, the size of the URLLC DL DCI format and/or the size of the DCI format X and the size of the URLLC DL DCI format having the smallest size among DCI format(s) with a number of bits greater than the size of the URLLC UL DCI format. And/or truncation may be applied to DCI format X so that the size of the URLLC UL DCI format is aligned. Only when such DCI size alignment is applied, a 1-bit flag is included in DCI to distinguish between DCI format X and URLLC DCI format, or search spaces and/or RNTIs having different DCI format X and URLLC DCI format, and /Or CORESETs and/or monitoring times (hereinafter, SSs/RNTIs/CORESETs/MOs) may be set to be monitored. In some implementations of this specification, DCI format X may not include DCI format 0_0 and DCI format 1_0 monitored in CSS (and/or USS).

In some implementations related to option 1, the size of the URLLC DL DCI format and/or the size of the DCI format Y and the size of the URLLC DL DCI format having the largest size of the DCI format(s) with the number of bits less than the size of the URLLC UL DCI format. And/or zero bit padding may be applied to DCI format Y so that the size of the URLLC UL DCI format is aligned. Only when such DCI size alignment is applied, a 1-bit flag is included in DCI to distinguish between DCI format Y and URLLC DCI format, or SSs/RNTIs/CORESETs with different DCI format Y and URLLC DCI formats/ It can be set to be monitored in MOs. In some implementations of this specification, DCI format Y may not include DCI format 0_0 and DCI format 1_0 monitored in CSS (and/or USS).

In some implementations related to option 1, the difference in the size of the URLLC DL DCI format and/or the size of the URLLC UL DCI format and the number of bits of the DCI format X having the smallest size among the DCI format(s) with a larger number of bits is a , If the difference between the size of the URLLC DL format and/or the size of the URLLC UL DCI format and the number of bits of the DCI format Y having the maximum size among the DCI formats with a smaller number of bits is b, comparing a and b, when a <b Truncation may be applied to DCI format X (or a <= b), and zero-bit padding may be applied to DCI format Y when a> b (or a >= b). Alternatively, if a is greater than (or less than) a predetermined value, truncation may be applied to DCI format X, and zero bit padding may be applied to DCI format Y in other cases. Only when such DCI size alignment is applied, i) DCI format X/DCI format Y and ii) URLLC DCI format is included in each DCI with a 1-bit flag, i) DCI format X/DCI format Y And ii) the URLLC DCI format may be set to be monitored in different SSs/RNTIs/CORESETs/MOs.

* Option 2

The URLLC DCI format so that the size of the remaining (some or all) DCI formats other than the URLLC DCI format and the size of the URLLC DCI format are the same so as not to exceed the capability for the maximum number of different DCI sizes that the UE can monitor. Can be resized. In some implementations of this specification, option 2 may be applied after size alignment for the URLLC DL DCI format and the URLLC UL DCI format. For example, aligning the size of the URLLC DL DCI format and the size of the URLLC UL DCI format may be applied only when the DCI format 1_1 and/or the DCI format 0_1 are not set to be monitored.

In some implementations related to option 2, the size of the URLLC DL DCI format and/or the size of the DCI format Z and the size of the URLLC DL DCI format having the smallest size among DCI format(s) with a number of bits greater than the size of the URLLC UL DCI format. And/or zero bit padding may be applied to the URLLC DL DCI format and/or the URLLC UL DCI format so that the size of the URLLC UL DCI format is aligned. Only when such DCI size alignment is applied, a 1-bit flag is included in DCI to distinguish between DCI format Z and URLLC DCI format, or SSs/RNTIs/CORESETs/ which have different DCI format Z and URLLC DCI format. It can be set to be monitored in MOs.

In some implementations related to option 2, the size of the URLLC DL DCI format and/or the size of the DCI format W having the maximum size among the DCI formats with the number of bits less than the size of the URLLC UL DCI format and the size of the URLLC DL DCI format and/or Truncation may be applied to the URLLC DL DCI format and/or the URLLC UL DCI format so that the size of the URLLC UL DCI format is aligned. Only when such DCI size alignment is applied, a 1-bit flag is included in DCI to distinguish between DCI format W and URLLC DCI format, or SSs/RNTIs/CORESETs/ which have different DCI format W and URLLC DCI format. It can be set to be monitored in MOs. For example, this truncation may be applied only when the size of the URLLC DL DCI format and/or the size of the URLLC UL DCI format is larger than the maximum size among other DCI formats.

In some implementations related to option 2, the difference in the number of bits of the DCI format having the smallest size among the size of the URLLC DL DCI format and/or the size of the URLLC UL DCI format and the DCI format(s) with a greater number of bits is a, If the difference between the size of the URLLC DL DCI format and/or the size of the URLLC UL DCI format and the number of bits of the DCI format having the maximum size among DCI formats with a smaller number of bits is b, compare a and b, and if a <b ( Or if a <= b) zero bit padding is applied to the URLLC DL DCI format and/or URLLC UL DCI format, and if a> b (or a >= b) URLLC DL DCI format and/or URLLC UL Truncation can be applied to the DCI format. Alternatively, if a is greater than (or less than) a certain value, zero bit padding is applied to the URLLC DL DCI format and/or the URLLC UL DCI format, and in other cases, truncation is performed on the URLLC DL DCI format and/or the URLLC UL DCI format. Can be applied.

* Option 3

Except for the size of the URLLC DCI format, the maximum number of different DCI sizes that can be monitored by the UE may be separately defined. As an example, in a cell in which the URLLC DCI format is set to be monitored, the UE does not expect to be set to monitor more than three different DCI sizes except for the size of the URLLC DCI format. Additionally or alternatively, the UE does not expect to be configured to monitor more than two different DCI sizes (CRC scrambled with C-RNTI) except for the size of the URLLC DCI format for a particular cell. On the other hand, this rule is not applied in cells where the URLLC DCI format is not set to be monitored, and the UE and BS may follow the maximum number of different DCI sizes defined according to the existing rules in the cell where the URLLC DCI format is not set to be monitored. have.

* Option 4

As another method, after the end of the first DCI size alignment process, if the capacity for different DCI sizes (CRC scrambled with C-RNTI) that the UE can monitor due to the size of the URLLC DCI format is exceeded, the UE And bs:

(4-1) When the size of the DCI format 0_1 and the size of the DCI format 1_1 are different, zero bit padding or bit in DCI format 1_1 or DCI format 0_1 so that the size of the DCI format 1_1 and the size of the DCI format 0_1 are aligned. Truncation (or DCI field reinterpretation for DCI size alignment) can be applied;

(4-2) If the size of DCI format 0_1 and the size of 1_1 are the same, zero padding applied to DCI format 1_1 and DCI format 0_1 is removed, and DCI format 1_0 monitored by USS and DCI format 0_0 monitored by USS The size of the DCI monitored by USS is re-determined based on the size of the initial DL/UL BWP or CORESET#0, and then the size of DCI format 1_0 monitored by USS and the size of DCI format 0_0 monitored by USS are aligned. Zero bit padding or bit truncation can be applied to format 0_0.

18 illustrates a DCI size alignment process according to another example of the present specification. In particular, FIG. 18 illustrates a DCI size alignment process according to option 4. In FIG. 18, the non-fallback DCI format may correspond to the URLLC DCI format.

Referring to FIG. 18, for example, the BS and the UE may perform steps 0 to 3 of the first DCI size alignment process (S1801 to S1804). Then, if the DCI size budget is not satisfied for DCI format(s) other than the non-fallback DCI format (S1805, No), the BS and the UE may perform step 4 of the first DCI alignment process (S1806). ). After performing steps 0 to 3 of the first DCI size alignment process, the DCI size budget is satisfied for DCI format(s) other than the non-fallback DCI format (S1805, Yes), including the non-fallback DCI format. When the DCI size budget for DCI formats is satisfied (S1807, Yes), the BS and the UE may end the DCI size alignment process. After performing steps 0 to 3 of the first DCI size alignment process, the DCI size budget is satisfied for DCI format(s) other than the non-fallback DCI format (S1805, Yes), including the non-fallback DCI format. If the DCI size budget is not satisfied for the DCI formats (S1807, No), and the size of DCI format 0_1 and the size of DCI format 1_1 are not the same (S1808, No), the BS and the UE have the size of the DCI format 0_1 and the The DCI format 1_1 is arranged to have the same size (S1809). After performing steps 0 to 3 of the DCI size alignment process, the DCI size budget is not satisfied for DCI formats other than the non-fallback DCI format (S1807, No), and DCI format 0_1 If the size of and the size of DCI format 1_1 are the same (S1808, Yes), the BS and the UE may perform step 4 of the first size alignment process (S1810). Here, the BS and the UE may determine whether the DCI size budget for the DCI format(s) is satisfied based on whether the following conditions are satisfied:

i) the total number of different DCI sizes set to monitor is not more than X+1 for that cell;

ii) The total number of different DCI sizes with C-RNTI configured to monitor is not more than X for that cell.

In some scenarios, X can be 3.

* Option 5

19 and 20 illustrate a DCI size alignment process according to another example of the present specification. In particular, FIGS. 19 and 20 illustrate a DCI size alignment process according to option 5. 19 and 20, the non-fallback DCI format may correspond to the URLLC DCI format.

As another method, after step 3 of the first DCI size size process is over, if the capacity for different DCI sizes that the UE can monitor (CRC scrambled with C-RNTI) is exceeded due to the size of the URLLC DCI format , UE and BS are:

(5-1) When the size of DCI format 0_1 and DCI format 1_1 are different:

(5-1-1) Zero bit padding or bit truncation (or DCI field reinterpretation for DCI size alignment) is applied to DCI format 1_1 or DCI format 0_1 so that the size of DCI format 1_1 and DCI format 0_1 are aligned. I can. In this case, if the size of DCI format 1_0/0_0 monitored in CSS is the same as the size of one of DCI format 1_1 and DCI format 0_1, the size of DCI format 1_0/0_0 monitored in CSS is not the same. Zero bit padding or bit truncation (and/or DCI field reinterpretation for DCI size alignment) may be applied to the DCI format. In this case, even if zero bit padding or bit truncation (and/or DCI field reinterpretation for DCI size alignment) is applied to the DCI format such as the size of DCI format 1_0/0_0 monitored in CSS, the total DCI size does not decrease. Can be prevented.

(5-1-2) Or DCI monitored by USS so that the size of DCI format 1_0 monitored by USS and DCI format 0_0 monitored by USS is the same as the size of either DCI format 1_1 or DCI format 0_1 Zero bit padding or bit truncation (and/or DCI field reinterpretation for DCI size alignment) may be applied to format 1_0 and DCI format 0_0 or DCI format 1_1 or DCI format 0_1.

Referring to FIG. 19, for example, the BS and the UE may perform steps 0 to 3 of the first DCI size alignment process (S1901 to S1904). If the DCI size budget is satisfied for other DCI format(s) including the non-fallback DCI format after performing steps 0 to 3 of the first DCI size alignment process (S1907, Yes), the BS and the UE are aligned with the DCI size. You can end the process. After performing steps 0 to 3 of the first DCI size alignment process, the DCI size budget is not satisfied for DCI formats including the non-fallback DCI format (S1907, No), and the size of DCI format 0_1 and DCI format 1_1 If the sizes of are not the same (S1908, No), the BS and the UE arrange so that the size of the DCI format 0_1 and the size of the DCI format 1_1 are the same (S1909). After performing steps 0 to 3 of the DCI size alignment process, the DCI size budget is not satisfied for DCI formats including the non-fallback DCI format (S1907, No), and the size of DCI format 0_1 and DCI format 1_1 If is the same (S1908, Yes), the BS and the UE may perform step 4 of the first size alignment process (S1910). Here, the BS and the UE may determine whether the DCI size budget for the DCI format(s) is satisfied based on whether the following conditions are satisfied:

ii) The total number of different DCI sizes set to monitor with C-RNTI is not more than X for that cell.

In some scenarios, X can be 3.

After step 3 of the first DCI size size process is over, due to the size of the URLLC DCI format, if the capacity for different DCI sizes that the UE can monitor (CRC scrambled with C-RNTI) is exceeded, the UE and the BS are :

(5-2) If the size of DCI format 0_1 and DCI format 1_1 are the same, the zero padding applied to DCI format 1_1 DCI format 0_1 is removed, and the size of DCI format 1_0 and DCI format 0_0 monitored by USS DCI format monitored by USS so that the size is re-determined based on the size of the initial DL/UL BWP or CORESET#0, and then the size of DCI format 1_0 monitored by USS and DCI format 0_0 monitored by USS are aligned. Zero bit padding or bit truncation can be applied to 0_0.

Referring to FIG. 20, as another example, the BS and the UE may perform steps 0 to 3 of the first DCI size alignment process (S2001 to S2004). After performing steps 0 to 3 of the first DCI size alignment process, if the DCI size budget is satisfied for other DCI format(s) including the non-fallback DCI format (S2007, Yes), the BS and the UE are aligned with the DCI size. You can end the process. After performing steps 0 to 3 of the first DCI size alignment process, the DCI size budget is not satisfied for DCI formats including the non-fallback DCI format (S2007, No), and the size of DCI format 0_1 and DCI format 1_1 If the size of is not the same (S2008, No), the BS and the UE align the size of the DCI format 0_0/1_0 on the USS and the size of the DCI format 0_1 (or DCI format 1_1) to be the same (S2009). After performing steps 0 to 3 of the DCI size alignment process, the DCI size budget is not satisfied for DCI formats including the non-fallback DCI format (S2007, No), and the size of DCI format 0_1 and DCI format 1_1 If is the same (S2008, Yes), the BS and the UE may perform step 4 of the first size alignment process (S2010). Here, the BS and the UE may determine whether the DCI size budget for the DCI format(s) is satisfied based on whether the following conditions are satisfied:

In some scenarios, X can be 3.

In Options 1 to 5, the DCI format of the URLLC DCI may be a new DCI format different from the DCI format(s) mentioned in the first DCI alignment process or the DCI format(s) illustrated in Table 7. Alternatively, in options 1 to 5, the URLLC DCI has the same DCI format as the DCI format mentioned in the first DCI alignment process or the DCI format illustrated in Table 7, but RNTI and/or search space (for scheduling URLLC traffic) And/or the DCI format mentioned in the first DCI alignment process or the DCI of the DCI format illustrated in Table 7 by setting such as CORESET.

<DCI 파라미터 선택><DCI parameter selection>

If the target service (e.g., URLLC) and/or QoS and/or BLER requirements and/or reliability requirements and/or delay requirements and/or processing times for a specific channel are different, parameter(s) used for scheduling (And/or candidate values of each parameter) may also need to be different. For example, a relatively large value of PDSCH-to-HARQ feedback timing may be required for scheduling eMBB traffic, while a relatively small value of PDSCH-to-HARQ feedback timing may be required for scheduling URLLC traffic.

21 and 22 illustrate the operation flow of the UE and BS based on some implementations of this specification related to DCI parameter selection. In particular, FIG. 21 illustrates an operation flow of a UE based on some implementations related to DCI parameter selection, and FIG. 22 illustrates an operation flow of a BS based on some implementations related to DCI parameter selection.

Referring to Figure 21, the UE may receive a DCI from the BS (S2100). The UE may interpret the field(s) included in the DCI according to some examples to be described later. For example, the UE interprets the DCI based on the search space in which the DCI is transmitted, CORESET, RNTI, and/or value(s) included in field(s) other than the field(s) to be analyzed. Can do it (S2102). In addition, the UE may transmit a UL channel or receive a DL channel based on information obtained according to the interpretation of the field(s) (S2104).

Referring to FIG. 22, the BS may generate a DCI (S2200). In this case, a field value included in the DCI for scheduling the UL/DL channel may be determined according to examples to be described later. For example, it is included in the DCI based on the search space in which the BS intends to transmit the DCI, CORESET, RNTI, and/or the value(s) included in field(s) other than the field(s) to be interpreted. The DCI may be generated by determining the field value(s). Thereafter, the BS may transmit the generated DCI (S2202). And, according to examples to be described later, a field derived based on the search space in which DCI is transmitted, CORESET, RNTI, and/or value(s) included in field(s) other than the field(s) to be analyzed Depending on the value(s), since the scheduling interpretation of the UL/DL channel is different, the base station may receive a UL channel from the UE or transmit a DL channel accordingly (S2204). For example, if an arbitrary field in DCI is called field B and another field is called field A, the value of field B is the search space in which DCI is transmitted, CORESET, RNTI, and/or values contained in field A. It can be derived on the basis of.

Hereinafter, some examples of generating/determining/interpreting field(s) included in DCI are described.

For each state indicated explicitly through a specific field of the DCI, and/or for each search space to which the PDCCH (scheduling DL/UL data) belongs, and/or the PDCCH (scheduling DL/UL data) For each CORESET to which it belongs, and/or for each RNTI, and/or for each CRC masking of a PDCCH, a value and/or a value range and/or a value candidate of a field constituting a specific DCI format (or of a parameter not included in the DCI format) The size of the set (list) and/or field may be differently defined/promised in advance, set through a higher layer signal, or indicated to the UE through a physical layer signal (or MAC CE). The BS can also transmit the PDCCH channel in anticipation of this UE operation.

For example, in the field m of DCI format X, when a PDCCH is detected in search space A, a set of candidate values of {m1, m2, m3, m4} is set, whereas when a PDCCH is detected in search space B, { A set of candidate values of m5, m6, m7, m8} may be set. As another example, field n of DCI format Y may have a field size determined as N1 when a PDCCH CRC scrambled with RNTI g is detected, whereas a field size may be determined as N2 when a PDCCH CRC scrambled with RNTI h is detected. have. As another example, in the field p of DCI format Z, if the value of another field k is 0, the candidate values of {p1, p2, ..., p8} are set, whereas if the value of k is 1, {p9, p10,. A candidate value of .., p16} may be set. As another example, a plurality of values may be set for a specific parameter not included in the DCI format W, and which of the values to be used may be determined according to the value of another field k.

The operation in which a value and/or a value range and/or a candidate set (list) of a value and/or a size of a field constituting the specific DCI format are set differently is a specific target service (eg, URLLC) It may be more usefully applied when a new separate DCI format is not defined for scheduling for QoS and/or BLER requirements and/or reliability requirements and/or delay requirements and/or processing time.

The UE may perform operations according to some implementations of this specification for DCI reception. The UE includes at least one transceiver; At least one processor; And at least one computer operatively connectable to the at least one processor, and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present specification. May include memory. The processing apparatus for the UE includes at least one processor; And at least one computer operatively connectable to the at least one processor, and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present specification. May include memory. The computer-readable storage medium may store at least one computer program including instructions that, when executed by at least one processor, cause the at least one processor to perform operations according to some implementations of the present specification. In some implementations of the present specification, the operations are, for example: first based on the size of the non-fallback uplink (UL) DCI format and the size of the non-fallback downlink (DL) DCI format. Determine the DCI size; A second DCI based on the size of the non-fallback UL DCI format and the size of the non-fallback DL DCI format based on determining the first DCI size, and the size of the fallback UL DCI format and the size of the fallback DL DCI format Determine the size; And receiving at least one DCI based on the first DCI size and the second DCI size during an active time based on a discontinuous reception (DRX) setting. Each of the non-fallback UL DCI format and the fallback UL DCI format may be a DCI format used to schedule a PUSCH. Each of the non-fallback DL DCI format and the fallback DL DCI format may be a DCI format used to schedule a PDSCH. The operations may include receiving the DRX configuration. The first DCI size may be the same as one of the size of the non-fallback UL DCI format and the non-fallback DL DCI format. The second DCI size may be the same as one of the fallback UL DCI format and the fallback DL DCI format. The non-fallback UL DCI format may be set to include or not include at least one field having a fixed field size among fields in the fallback UL DCI format. The non-fallback DL DCI format may be set to include or not include at least one field having a fixed field size among fields in the fallback DL DCI format. The size of the non-fallback UL DCI format may be set smaller than the size of the fallback UL DCI format. The size of the non-fallback DL DCI format may be set smaller than the size of the fallback DL DCI format. Determining the second DCI based on the size of the fallback UL DCI format and the size of the fallback DL DCI format: i) based on the size of the non-fallback UL DCI format and the size of the non-fallback UL DCI format Based on the determination of the first DCI size and ii) based on the condition not satisfied, including determining the second DCI size based on the size of the fallback UL DCI format and the size of the fallback DL DCI format can do. The conditions may include: i) the total number of different DCI sizes configured to be monitored by the UE is greater than X+1 for a cell, and ii) the UE is a cell radio network temporary identifier. identifier, C-RNTI), the total number of different DCI sizes set to be monitored is not more than X for the cell. Receiving the at least one DCI may include monitoring the DCI of the non-fallback UL DCI format or the DCI of the non-fallback DL DCI format during the active time of the UE based on the first DCI size. have. The fallback UL DCI format may be a DCI format DCI format 0_1, and the non-fallback UL DCI format may be a DCI format different from DCI format 0_0 and DCI format 0_1. The fallback DL DCI format may be DCI format 1_1, and the non-fallback DL DCI format may be a DCI format different from DCI format 1_0 and DCI format 1_1.

The BS may perform operations according to some implementations of this specification for DCI transmission. BS includes at least one transceiver; At least one processor; And at least one computer operatively connectable to the at least one processor, and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present specification. May include memory. The processing apparatus for the BS includes at least one processor; And at least one computer operatively connectable to the at least one processor, and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present specification. May include memory. The computer-readable storage medium may store at least one computer program including instructions that, when executed by at least one processor, cause the at least one processor to perform operations according to some implementations of the present specification. The operations in some implementations of the present specification are, for example: the size of the non-fallback uplink (UL) DCI format and the size of the non-fallback downlink (DL) DCI format as a first DCI size. Adjusted to; Based on adjusting the size of the non-fallback UL DCI format and the size of the non-fallback DL DCI format to the first DCI size, a second based on the size of the fallback UL DCI format and the size of the fallback DL DCI format DCI scaled; And transmitting at least one DCI based on the first DCI size and the second DCI size during an active time of the UE based on discontinuous reception (DRX) configuration. Each of the non-fallback UL DCI format and the fallback UL DCI format may be a DCI format used to schedule a PUSCH. Each of the non-fallback DL DCI format and the fallback DL DCI format may be a DCI format used to schedule a PDSCH. The operations may include transmitting the DRX configuration to the UE. The first DCI size may be the same as one of the size of the non-fallback UL DCI format and the non-fallback DL DCI format. The second DCI size may be the same as one of the fallback UL DCI format and the fallback DL DCI format. The non-fallback UL DCI format may be set to include or not include at least one field having a fixed field size among fields in the fallback UL DCI format. The non-fallback DL DCI format may be set to include or not include at least one field having a fixed field size among fields in the fallback DL DCI format. The size of the non-fallback UL DCI format may be set smaller than the size of the fallback UL DCI format. The size of the non-fallback DL DCI format may be set smaller than the size of the fallback DL DCI format. Adjusting the second DCI based on the size of the fallback UL DCI format and the size of the fallback DL DCI format: i) the size of the non-fallback UL DCI format and the size of the non-fallback UL DCI format Based on 1 DCI size adjustment and ii) based on conditions not being satisfied, it may include adjusting the size of the fallback UL DCI format and the size of the fallback DL DCI format to the second DCI size. . The conditions may include: i) the total number of different DCI sizes set to be monitored by the UE is not more than X+1 for a cell, and ii) the UE is a cell radio network temporary identifier (cell radio network The total number of different DCI sizes set to monitor with temporary identifier (C-RNTI) is not more than X for the cell. Transmitting the at least one DCI may include transmitting the DCI of the non-fallback UL DCI format or the DCI of the non-fallback DL DCI format during the active time of the UE based on the first DCI size. have. The fallback UL DCI format may be a DCI format DCI format 0_1, and the non-fallback UL DCI format may be a DCI format different from DCI format 0_0 and DCI format 0_1. The fallback DL DCI format may be DCI format 1_1, and the non-fallback DL DCI format may be a DCI format different from DCI format 1_0 and DCI format 1_1.

Examples of the present specification disclosed as described above are provided to enable those skilled in the art related to the present specification to implement and implement the present specification. Although the above has been described with reference to examples of the present specification, those skilled in the art may variously modify and change the examples of the present specification. Thus, this specification is not intended to be limited to the examples described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Implementations of the present specification may be used in a wireless communication system, a base station or user equipment, and other equipment.

Claims

In a user equipment receiving downlink control information (DCI) in a wireless communication system,

Determining a first DCI size based on a size of a non-fallback uplink (UL) DCI format and a size of the non-fallback downlink (DL) DCI format;

Based on the determination of the first DCI size based on the size of the non-fallback UL DCI format and the size of the non-fallback DL DCI format, based on the size of the fallback UL DCI format and the size of the fallback DL DCI format 2 determine the DCI size; And

Receiving at least one DCI based on the first DCI size and the second DCI size during an active time based on discontinuous reception (DRX) setting,

Each of the non-fallback UL DCI format and the fallback UL DCI format is a DCI format used to schedule a physical uplink shared channel (PUSCH),

Each of the non-fallback DL DCI format and the fallback DL DCI format is a DCI format used to schedule a physical downlink shared channel (PDSCH),

Method for receiving downlink control information.
The method of claim 1,

Comprising receiving the DRX configuration,

Method for receiving downlink control information.
The method of claim 1,

The first DCI size is one of the size of the non-fallback UL DCI format and the non-fallback DL DCI format,

The second DCI size is one of the size of the fallback UL DCI format and the fallback DL DCI format,

Method for receiving downlink control information.
The method of claim 1,

The non-fallback UL DCI format is set to include or not include at least one field having a fixed field size among fields in the fallback UL DCI format,

Method for receiving downlink control information.
The method of claim 1,

The non-fallback DL DCI format is set to include or not include at least one field having a fixed field size among fields in the fallback DL DCI format,

Method for receiving downlink control information.
The method of claim 1,

The size of the non-fallback UL DCI format is smaller than the size of the fallback UL DCI format, the size of the non-fallback DL DCI format is smaller than the size of the fallback DL DCI format,

Method for receiving downlink control information.
The method of claim 1,

Determining the second DCI based on the size of the fallback UL DCI format and the size of the fallback DL DCI format,

i) based on determining the first DCI size based on the size of the non-fallback UL DCI format and the size of the non-fallback UL DCI format, and ii) based on not meeting conditions, the fallback UL DCI And determining the second DCI size based on the size of the format and the size of the fallback DL DCI format, the conditions including:

The total number of different DCI sizes set to monitor is not more than X+1 for the cell,

The total number of different DCI sizes configured to be monitored with a cell radio network temporary identifier (C-RNTI) is not more than X for the cell,

Method for receiving downlink control information.
The method of claim 1,

Receiving the at least one DCI:

Including decoding the DCI of the non-fallback UL DCI format or the DCI of the non-fallback DL DCI format based on the first DCI size,

Method for receiving downlink control information.
The method according to any one of claims 1 to 8,

The fallback UL DCI format is a DCI format DCI format 0_1, the non-fallback UL DCI format is a DCI format different from DCI format 0_0 and DCI format 0_1, and the fallback DL DCI format is DCI format 1_1, and the non- Fallback DL DCI format is a DCI format different from DCI format 1_0 and DCI format 1_1,

Method for receiving downlink control information.
In a user equipment receiving downlink control information (DCI) in a wireless communication system,

At least one transceiver;

At least one processor; And

And at least one computer memory operatively connectable to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations, the operations comprising:

Determining a first DCI size based on a size of a non-fallback uplink (UL) DCI format and a size of the non-fallback downlink (DL) DCI format;

Based on the determination of the first DCI size based on the size of the non-fallback UL DCI format and the size of the non-fallback DL DCI format, based on the size of the fallback UL DCI format and the size of the fallback DL DCI format 2 determine the DCI size; And

Receiving at least one DCI based on the first DCI size and the second DCI size during an active time based on discontinuous reception (DRX) setting,

Each of the non-fallback UL DCI format and the fallback UL DCI format is a DCI format used to schedule a physical uplink shared channel (PUSCH),

Each of the non-fallback DL DCI format and the fallback DL DCI format is a DCI format used to schedule a physical downlink shared channel (PDSCH),

User device.
In the device for user equipment,

At least one processor; And

And at least one computer memory operatively connectable to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations, the operations comprising:

Determining a first DCI size based on a size of a non-fallback uplink (UL) DCI format and a size of the non-fallback downlink (DL) DCI format;

Based on the determination of the first DCI size based on the size of the non-fallback UL DCI format and the size of the non-fallback DL DCI format, based on the size of the fallback UL DCI format and the size of the fallback DL DCI format 2 determine the DCI size; And

Receiving at least one DCI based on the first DCI size and the second DCI size within an active time based on a discontinuous reception (DRX) setting,

Each of the non-fallback UL DCI format and the fallback UL DCI format is a DCI format used to schedule a physical uplink shared channel (PUSCH),

Each of the non-fallback DL DCI format and the fallback DL DCI format is a DCI format used to schedule a physical downlink shared channel (PDSCH),

Device.
A computer-readable storage medium comprising:

The computer-readable storage medium stores at least one computer program including instructions that, when executed by at least one processor, cause the at least one processor to perform operations for a user device, the operations comprising:

Determining a first DCI size based on a size of a non-fallback uplink (UL) DCI format and a size of the non-fallback downlink (DL) DCI format;

Based on the determination of the first DCI size based on the size of the non-fallback UL DCI format and the size of the non-fallback DL DCI format, based on the size of the fallback UL DCI format and the size of the fallback DL DCI format 2 determine the DCI size; And

Receiving at least one DCI based on the first DCI size and the second DCI size during an active time based on discontinuous reception (DRX) setting,

Each of the non-fallback UL DCI format and the fallback UL DCI format is a DCI format used to schedule a physical uplink shared channel (PUSCH),

Each of the non-fallback DL DCI format and the fallback DL DCI format is a DCI format used to schedule a physical downlink shared channel (PDSCH),

Computer readable storage media.
In the base station transmitting downlink control information (DCI) in a wireless communication system,

Adjusting a size of a non-fallback uplink (UL) DCI format and a size of the non-fallback downlink (DL) DCI format to a first DCI size;

Based on the adjustment of the size of the non-fallback UL DCI format and the size of the non-fallback DL DCI format to the first DCI size, the size of the fallback UL DCI format and the size of the fallback DL DCI format are determined as the second DCI size. Adjusted to; And

Including transmitting at least one DCI based on the first DCI size and the second DCI size within an active time based on a discontinuous reception (DRX) setting,

Each of the non-fallback UL DCI format and the fallback UL DCI format is a DCI format used to schedule a physical uplink shared channel (PUSCH),

Each of the non-fallback DL DCI format and the fallback DL DCI format is a DCI format used to schedule a physical downlink shared channel (PDSCH),

Downlink control information transmission method.
In the base station transmitting downlink control information (DCI) in a wireless communication system,

At least one transceiver;

At least one processor; And

And at least one computer memory operatively connectable to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations, the operations comprising:

Adjusting a size of a non-fallback uplink (UL) DCI format and a size of the non-fallback downlink (DL) DCI format to a first DCI size;

Based on the adjustment of the size of the non-fallback UL DCI format and the size of the non-fallback DL DCI format to the first DCI size, the size of the fallback UL DCI format and the size of the fallback DL DCI format are determined as the second DCI size. Adjusted to; And

Including transmitting at least one DCI based on the first DCI size and the second DCI size within an active time based on a discontinuous reception (DRX) setting,

Each of the non-fallback UL DCI format and the fallback UL DCI format is a DCI format used to schedule a physical uplink shared channel (PUSCH),

Each of the non-fallback DL DCI format and the fallback DL DCI format is a DCI format used to schedule a physical downlink shared channel (PDSCH),

Base station.