WO2020204481A1 - Procédés de réception d'informations de commande de liaison descendante, équipement utilisateur, support d'informations, procédé de transmission d'informations de commande de liaison descendante, et station de base - Google Patents

Procédés de réception d'informations de commande de liaison descendante, équipement utilisateur, support d'informations, procédé de transmission d'informations de commande de liaison descendante, et station de base Download PDF

Info

Publication number
WO2020204481A1
WO2020204481A1 PCT/KR2020/004182 KR2020004182W WO2020204481A1 WO 2020204481 A1 WO2020204481 A1 WO 2020204481A1 KR 2020004182 W KR2020004182 W KR 2020004182W WO 2020204481 A1 WO2020204481 A1 WO 2020204481A1
Authority
WO
WIPO (PCT)
Prior art keywords
dci format
dci
size
fallback
format
Prior art date
Application number
PCT/KR2020/004182
Other languages
English (en)
Korean (ko)
Inventor
이현호
김선욱
배덕현
Original Assignee
엘지전자 주식회사
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 엘지전자 주식회사 filed Critical 엘지전자 주식회사
Publication of WO2020204481A1 publication Critical patent/WO2020204481A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/04—Error control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling

Definitions

  • This specification relates to a wireless communication system.
  • eMBB enhanced mobile broadband
  • RAT legacy radio access technology
  • massive machine type communication 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.
  • 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.
  • a method for a user equipment to receive downlink control information (DCI) in a wireless communication system 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.
  • DRX discontinuous reception
  • 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).
  • PUSCH physical uplink shared channel
  • PDSCH physical downlink shared channel
  • a user equipment receiving downlink control information (DCI) in a wireless communication system 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.
  • DCI downlink control information
  • 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.
  • DRX discontinuous reception
  • 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).
  • PUSCH physical uplink shared channel
  • PDSCH physical downlink shared channel
  • an apparatus for user equipment 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.
  • DRX discontinuous reception
  • 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).
  • PUSCH physical uplink shared channel
  • PDSCH physical downlink shared channel
  • a 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.
  • DRX discontinuous reception
  • 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).
  • PUSCH physical uplink shared channel
  • PDSCH physical downlink shared channel
  • a method for transmitting downlink control information (DCI) by a base station in a wireless communication system 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.
  • DCI downlink control information
  • 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).
  • a base station for transmitting downlink control information (DCI) in a wireless communication system.
  • 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.
  • DCI downlink control information
  • 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.
  • DRX discontinuous reception
  • 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).
  • PUSCH physical uplink shared channel
  • PDSCH physical downlink shared channel
  • the base station may provide the DRX configuration to the user equipment.
  • 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.
  • 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/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.
  • C-RNTI cell radio network temporary identifier
  • 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.
  • 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.
  • wireless communication signals can be efficiently transmitted/received. Accordingly, the overall throughput of the wireless communication system can be increased.
  • a delay/delay occurring during wireless communication between communication devices may be reduced.
  • FIG. 1 shows an example of communication system 1 to which implementations of the present specification are applied;
  • FIG. 2 is a block diagram showing examples of communication devices capable of performing a method according to the present specification
  • FIG. 3 shows another example of a wireless device capable of performing implementation(s) of the present specification
  • DRX discontinuous reception
  • 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 );
  • FIG. 7 illustrates slot structures that can be used in a 3GPP-based system
  • HARQ-ACK hybrid automatic repeat request-acknowledgement
  • FIG. 11 shows an example of a process in which a UE with PUCCHs overlapping in a single slot handles collisions between UL channels
  • FIG. 12 illustrates cases of multiplexing UCI multiplexing according to FIG. 11;
  • FIG. 13 illustrates a process in which a UE having PUCCH and PUSCH overlapping in a single slot handles collision between UL channels
  • 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
  • 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.
  • CDMA code division multiple access
  • FDMA frequency division multiple access
  • TDMA time division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single carrier frequency
  • division multiple access 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.
  • UTRA Universal Terrestrial Radio Access
  • 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).
  • IEEE Institute of Electrical and Electronics Engineers
  • WiFi WiFi
  • WiMAX IEEE 802.16
  • E-UTRA evolved-UTRA
  • UTRA is a part of Universal Mobile Telecommunication System (UMTS)
  • 3GPP 3rd Generation Partnership Project
  • LTE Long Term Evolution
  • 3GPP LTE adopts OFDMA in downlink (DL) and SC-FDMA in uplink (UL).
  • LTE-advanced (LTE-A) is an evolved form of 3GPP LTE.
  • 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.
  • 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”.
  • 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.
  • 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).
  • the base station of UTRAN is called Node-B
  • the base station of E-UTRAN is called eNB
  • the base station of new radio access technology network is called gNB.
  • the base station is collectively referred to as a BS regardless of the type or version of the communication technology.
  • 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.
  • BS, NB, eNB, pico-cell eNB (PeNB), home eNB (HeNB), relay, repeater, and the like may be nodes.
  • the node may not have to be a BS.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • CRS Cell-specific Reference Signal
  • 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.
  • 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.
  • DL resources downlink resources
  • UL resources uplink resources
  • the cell may be configured with a DL resource alone or a combination of a DL resource and a UL resource.
  • 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.
  • a combination of a DL resource and a UL resource may be indicated by a system information block type 2 (SIB2) linkage.
  • SIB2 system information block type 2
  • the carrier frequency may be the same as or different from the center frequency of each cell or CC.
  • CA carrier aggregation
  • the UE has only one radio resource control (RRC) connection with the network.
  • RRC radio resource control
  • 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.
  • NAS non-access stratum
  • Pcell primary cells
  • 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.
  • secondary cells 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).
  • a carrier corresponding to a Pcell is called a downlink primary CC (DL PCC)
  • 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)
  • a carrier corresponding to the Scell in uplink is referred to as a UL secondary CC (UL SCC).
  • the term SpCell refers to a Pcell of a master cell group (MCG) or a Pcell of a secondary cell group (SCG).
  • MCG master cell group
  • SCG secondary cell group
  • PUCCH PUCCH transmission and contention-based random access
  • 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.
  • the SCG is a subset of serving cells associated with the secondary node, and consists of a PSCell and zero or more Scells.
  • serving cells 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.
  • MAC medium access control
  • 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.
  • 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.
  • 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.
  • a physical downlink shared channel (PDSCH), a physical broadcast channel (PBCH), a physical downlink control channel (PDCCH), etc. are the downlink physical channels.
  • PBCH physical broadcast channel
  • PDCCH physical downlink control channel
  • 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.
  • a demodulation reference signal (DMRS), channel state information RS (channel state information RS, CSI-RS), etc.
  • 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.
  • PUSCH physical uplink shared channel
  • PUCCH physical uplink control channel
  • PRACH physical random access channel
  • DMRS demodulation reference signal
  • SRS sounding reference signal
  • PDCCH Physical Downlink Control CHannel
  • PDSCH Physical Downlink Shared CHannel
  • DCI Downlink Control Information
  • PUCCH Physical Uplink Control CHannel
  • PUSCH Physical Uplink Shared CHannel
  • PRACH Physical Random Access CHannel
  • UCI Uplink Control Information
  • uplink data time-frequency carrying a random access signal It means a collection of resources.
  • 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.
  • 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.
  • next-generation communication 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).
  • 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.
  • 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.
  • 3GPP is conducting a study on the next-generation mobile communication system after EPC.
  • the technology is referred to as a new RAT (NR) or 5G RAT
  • NR new RAT
  • 5G RAT a system that uses or supports NR
  • a communication system 1 applied to the present specification includes a wireless device, a BS, and a network.
  • 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.
  • 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.
  • the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, and a vehicle capable of performing inter-vehicle communication.
  • the vehicle may include an Unmanned Aerial Vehicle (UAV) (eg, a drone).
  • UAV Unmanned Aerial Vehicle
  • 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.
  • 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
  • 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.
  • the vehicles 100b-1 and 100b-2 may perform direct communication (e.g.
  • V2V Vehicle to Vehicle
  • V2X Vehicle to Everything
  • the IoT device eg, sensor
  • the IoT device 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.
  • 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).
  • 5G NR wireless access technologies
  • the wireless device and the BS/wireless device may transmit/receive wireless signals to each other.
  • 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.
  • 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).
  • ⁇ 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • a wireless device may mean a communication modem/circuit/chip.
  • one or more protocol layers may be implemented by one or more processors 102, 202.
  • 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).
  • PHY physical
  • MAC medium access control
  • RLC radio link control
  • 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.
  • PDCP packet data convergence protocol
  • RRC radio resource control
  • SDAP service data adaption protocol
  • 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.
  • 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.
  • signals e.g., baseband signals
  • transceivers 106, 206
  • PDU Packet Data Unit
  • 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.
  • ASICs Application Specific Integrated Circuits
  • DSPs Digital Signal Processors
  • DSPDs Digital Signal Processing Devices
  • PLDs Programmable Logic Devices
  • FPGAs Field Programmable Gate Arrays
  • 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.
  • 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.
  • one or more transceivers 106, 206 may be coupled with one or more processors 102, 202, and may transmit and/or receive wireless signals.
  • 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.
  • 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.
  • 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.
  • 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.
  • one or more of the transceivers 106 and 206 may include (analog) oscillators and/or filters.
  • 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).
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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
  • 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.
  • 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.
  • 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.
  • the control unit 120 and the first unit eg, 130, 140
  • each element, component, unit/unit, and/or module in the wireless device 100 and 200 may further include one or more elements.
  • the controller 120 may be configured with one or more processor sets.
  • 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.
  • 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.
  • At least one memory 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.
  • 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.
  • 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.
  • DRX discontinuous reception
  • 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.
  • RRC_IDLE state and RRC_INACTIVE state DRX is used for the UE to receive paging signals discontinuously.
  • RRC_CONNECTED DRX DRX performed in the RRC_CONNECTED state will be described (RRC_CONNECTED DRX).
  • 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.
  • 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.
  • the UE may perform PDCCH monitoring/reception discontinuously in the time domain.
  • a PDCCH reception time eg, a slot having a PDCCH search space
  • the UE may continuously perform PDCCH monitoring/reception in the time domain.
  • a PDCCH reception timing (eg, a slot having a PDCCH search space) in the present specification may be continuously 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.
  • 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.
  • RRC Radio Resource Control
  • the UE may perform PDCCH monitoring discontinuously, as illustrated in FIG. 4.
  • MAC-CellGroupConfig includes configuration information necessary to configure MAC parameters for a cell group.
  • MAC-CellGroupConfig may also include configuration information about DRX.
  • MAC-CellGroupConfig may include information related to DRX as follows.
  • -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.
  • 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.
  • FIG. 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.
  • OFDM numerology eg, subcarrier spacing, SCS
  • SCS subcarrier spacing
  • 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)
  • CP-OFDM cyclic prefix-orthogonal frequency division multiplexing
  • SC-FDMA symbol or, discrete Fourier transform-spread-OFDM (discrete Fourier transform-spread-OFDM, DFT-s-OFDM) symbol
  • 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.
  • uplink and downlink transmissions are organized into frames.
  • 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.
  • a slot contains a plurality of (eg, 14 or 12) symbols in the time domain.
  • a common resource block (common resource block, CRB) N start indicated by higher layer signaling (e.g., radio resource control (RRC) signaling)
  • RRC radio resource control
  • 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.
  • N size,u grid,x is the number of resource blocks (RBs) in the resource grid
  • 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.
  • 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.
  • RRC parameter resource element
  • 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.
  • RE 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.
  • the RB is defined by 12 consecutive subcarriers in the frequency domain.
  • 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 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.
  • 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.
  • a DL control channel ii) DL or UL data
  • a UL control channel iii) DL or UL data
  • a UL control channel iii) DL or UL data
  • a UL control channel UL control channel.
  • 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.
  • information indicating how each of the symbols of the slot is used is referred to as a slot format.
  • the slot format may define which symbols in the slot are used for UL and which symbols are used for DL.
  • the BS may set a pattern for UL and DL allocation for the serving cell through higher layer (eg, RRC) signaling.
  • RRC higher layer
  • -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;
  • 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.
  • the TDD UL-DL configuration eg, tdd-UL-DL-ConfigurationCommon , or tdd-UL-DLConfigurationDedicated
  • 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.
  • D denotes a DL symbol
  • U denotes a UL symbol
  • F denotes a flexible symbol.
  • the BS 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.
  • SFI DCI slot format indicator
  • DCI format 2_0 is used as the SFI DCI.
  • 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.
  • 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.
  • 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.
  • 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).
  • 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 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.
  • the UE 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).
  • mmW millimeter wave
  • the following table exemplifies frequency ranges in which NR can operate.
  • the PDCCH carries DCI.
  • the PDCCH i.e., DCI
  • the PDCCH 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.
  • PCH paging information for a paging channel
  • RAR random access response
  • 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).
  • CS configured scheduling
  • 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).
  • C-RNTI radio network temporary identifier
  • 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).
  • SIB system information block
  • RA-RATI random access RNTI
  • the PDCCH is transmitted through a control resource set (CORESET).
  • 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.
  • PRBs physical resource blocks
  • RRC higher layer
  • 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.
  • -duration the number of consecutive slots that the search space lasts at every time (occasion), that is, at every period as given by monitoringSlotPeriodicityAndOffset .
  • 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
  • DCI format 0_1 is a TB-based (or TB-level) PUSCH or code block group (CBG) )
  • CBG code block group
  • 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
  • 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.
  • DCI format 0_0 and DCI format 1_0 have a fixed size after the BWP size is initially given by RRC.
  • 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.
  • FDRA frequency domain resource assignment
  • 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
  • DCI format 2_1 may be used to deliver downlink pre-Emption information to the UE.
  • each of DCI format 0_0 and DCI format 0_1 includes a frequency domain resource allocation field for scheduling of PUSCH
  • 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 0 to a A-1 as follows.
  • the first field of the DCI format is mapped to the lowest order information bit a 0 , 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 0 . 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.
  • 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
  • N RB UL,BWP is the size of the initial UL BWP.
  • N RB DL,BWP is given by:
  • 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.
  • 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.
  • N RB UL,BWP is the size of the active UL BWP.
  • N RB DL,BWP is the size of the active DL BWP.
  • 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.
  • the payload size Zeros are attached to the DCI format 1_0 until is equal to that of the DCI format 0_0.
  • DCI format 0_1 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.
  • DCI format 1_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.
  • the total number of different DCI sizes with C-RNTI configured to monitor is not more than 3 for that cell.
  • N RB DL,BWP is given by:
  • N RB UL,BWP is the size of the initial UL BWP.
  • 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.
  • the size of the DCI format 0_0 monitored by the USS 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.
  • 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;
  • the total number of different DCI sizes with C-RNTI configured to monitor is more than 3 for that cell;
  • 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.
  • 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.
  • DCI monitoring that is, PDCCH monitoring
  • the 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:
  • SR -Scheduling request
  • HARQ-ACK-acknowledgement 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
  • 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.
  • the term HARQ-ACK is mixed with HARQ ACK/NACK, ACK/NACK, or A/N.
  • CSI Channel quality information
  • rank indicator rank indicator
  • PMI precoding matrix indicator
  • CSI-RS resource indicator CRI
  • SS /PBCH resource block indicator SSBRI
  • CSI 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.
  • 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.
  • 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.
  • 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.
  • OCC orthogonal cover code
  • CS cyclic shift
  • CS Code division multiplexing
  • 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 ).
  • 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.
  • 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.
  • 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.
  • 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.
  • IFDM interleaved FDM
  • 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).
  • K is the number of PUCCH resource sets (K>1)
  • N i is the maximum number of UCI bits supported by the PUCCH resource set #i.
  • PUCCH resource set #1 may be composed of resources of PUCCH format 0 to 1
  • 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.
  • 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.
  • 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).
  • 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).
  • a PUCCH resource to be used for UCI transmission within a PUCCH resource set may be scheduled based on DCI.
  • 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).
  • DCI is a DCI used for PDSCH scheduling, and UCI may include HARQ-ACK for PDSCH.
  • 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.
  • 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).
  • uplink resource allocation is also referred to as an uplink grant
  • 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.
  • the BS may dynamically allocate uplink resources to the UE through PDCCH(s) addressed to a cell radio network temporary identifier (C-RNTI).
  • C-RNTI cell radio network temporary identifier
  • the UE monitors the PDCCH(s) to find possible uplink grant(s) for UL transmission.
  • 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.
  • 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.
  • 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.
  • 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.
  • the BS may allocate downlink resources to the UE using semi-static scheduling (SPS).
  • SPS semi-static scheduling
  • 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.
  • 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.
  • 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.
  • MCS modulation and coding scheme
  • 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.
  • DCI format 0_0, DCI format 0_1, or DCI format 0_2 may be used for scheduling a PUSCH
  • DCI format 1_0, DCI format 1_1, or DCI format 1_2 may be used for scheduling a PDSCH.
  • 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.
  • FIG. 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.
  • TDRA time domain resource assignment
  • 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).
  • each indexed row is assigned a DL allocation-to-PDSCH slot offset K 0 , 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.
  • each indexed row is a UL grant-to-PUSCH slot offset K 2 , 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 0 for PDSCH or K 2 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.
  • mapping type A there are two types of mapping: one is mapping type A and the other is mapping type B.
  • a demodulation reference signal is located in a third symbol (symbol #2) or a fourth symbol (symbol #3) in a slot according to RRC signaling.
  • 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.
  • FDRA frequency domain resource assignment
  • 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.
  • an established grant type 1 there are two types of transmission without a dynamic grant: an established grant type 1 and an established grant type 2.
  • a UL grant is provided by RRC signaling and is a configured grant. Is saved.
  • 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.
  • the UE may receive the following parameters from the BS through RRC signaling:
  • 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;
  • the UE 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 .
  • the UE may receive the following parameters from the BS through RRC signaling:
  • the actual uplink grant is provided to the UE by the PDCCH (addressed with CS-RNTI).
  • the UE may be configured with semi-persistent scheduling (SPS) for each serving cell and for each BWP by RRC signaling from the BS.
  • SPS semi-persistent scheduling
  • DL allocation is provided to the UE by PDCCH, and is stored or removed based on L1 signaling indicating SPS activation or deactivation.
  • the UE may receive the following parameters from the BS through RRC signaling:
  • 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
  • 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).
  • TDRA field providing a TDRA value m
  • an FDRA field providing a frequency resource block allocation
  • 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.
  • 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.
  • 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.
  • FDRA -Frequency domain resource assignment
  • TDRA Time domain resource assignment
  • PDSCH mapping type A or PDSCH mapping type B may be indicated by TDRA.
  • the DMRS is located in the third symbol (symbol #2) or the fourth symbol (symbol #3) in the slot.
  • the DMRS is located in the first symbol allocated for the PDSCH.
  • -PDSCH-to-HARQ_feedback timing indicator indicates K1.
  • the HARQ-ACK response may consist of 1-bit.
  • 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.
  • 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.
  • 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.
  • 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.
  • a (UE-specific) upper layer eg, RRC
  • 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.
  • the size of the HARQ-ACK codebook is fixed (to a maximum value) regardless of the actual number of scheduled DL data.
  • the DL grant DCI includes PDSCH to HARQ-ACK timing information
  • the PDSCH-to-HARQ-ACK timing information may have one of a plurality of values (eg, 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 ⁇ .
  • 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).
  • 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).
  • the HARQ-ACK information may be replaced with the HARQ-ACK codebook and the HARQ-ACK payload.
  • the slot may be understood/replaced as a candidate opportunity for DL data reception.
  • 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.
  • RRC higher layer
  • the size of the HARQ-ACK payload to be reported by the UE may be dynamically changed by DCI or the like.
  • the DL scheduling DCI may include counter-DAI (ie, c-DAI) and/or total-DAI (ie, t-DAI).
  • 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.
  • 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.
  • the physical layer of the NR is designed to support a flexible transmission structure in consideration of requirements for various services.
  • the physical layer of the NR may change the OFDM symbol length (OFDM symbol duration) and subcarrier spacing (SCS) (hereinafter, OFDM neurology) as necessary.
  • 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.
  • PUCCH resources may overlap with other PUCCH resources or PUSCH resources in the time axis.
  • PUCCH resources may overlap with other PUCCH resources or PUSCH resources in the time axis.
  • PUCCH (resource) and PUCCH (resource) are time axis
  • 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).
  • UCI refers to control information transmitted by the UE by UL.
  • UCI includes various types of control information (ie, UCI type).
  • 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).
  • the multiplexed UCI is referred to as MUX UCI.
  • UCI multiplexing may include an operation performed in relation to the MUX UCI.
  • 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.
  • the multiplexed UCI is referred to as MUX UCI/Data.
  • UCI/data multiplexing may include an operation performed in relation to MUX UCI/Data.
  • UCI/data multiplexing may include a process of determining UL channel resources to transmit MUX UCI/Data.
  • the slot includes a plurality of symbols.
  • 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.
  • 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.
  • FIG. 10 shows an example of multiplexing UCI to PUSCH.
  • UCI may be transmitted through PUSCH as shown. Transmitting UCI through PUSCH is referred to as UCI piggyback or PUSCH piggyback.
  • FIG. 10 illustrates a case where HARQ-ACK and CSI are carried on PUSCH resources.
  • a method for the UE to process the plurality of UL channels must be defined.
  • methods of handling collisions between UL channels are described.
  • FIG. 11 shows an example of a process in which a UE having PUCCHs overlapping in a single slot handles collision between UL channels.
  • the UE may determine a PUCCH resource for each UCI.
  • Each PUCCH resource may be defined by a start symbol and a transmission length.
  • 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.
  • a MUX UCI including all or part of the UCI A and the UCI B is obtained according to a UCI multiplexing rule.
  • 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).
  • 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
  • PUCCH resource set X One of the belonging PUCCH resources is determined as the MUX PUCCH resource.
  • 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).
  • UCI multiplexing 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).
  • 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.
  • 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.
  • 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.
  • 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. .
  • FIG. 13 illustrates a process in which a UE having PUCCH and PUSCH overlapping in a single slot handles collision between UL channels.
  • 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.
  • 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.
  • a specific serving cell eg, a serving cell having the smallest serving cell index
  • FIG. 14 illustrates UCI multiplexing in consideration of a timeline condition.
  • 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.
  • the following two timeline conditions hereinafter, multiplexing time Line conditions
  • 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.
  • T1 may be expressed as T_proc,1.
  • T2 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.
  • 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.
  • 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
  • Table 13 is the PUSCH timing capability of the UE #1 To illustrate the PUSCH preparation time for
  • Table 14 illustrates the PUSCH preparation time for the timing capability #2 of the UE.
  • 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).
  • 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).
  • the UE may have to transmit a plurality of UL channels (eg, UL channels #1 to #4) in the same slot.
  • UL CH #1 may be a PUSCH scheduled by PDCCH #1.
  • 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.
  • 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.
  • the fastest UL channel eg, the UL channel with the fastest start symbol
  • the current NR standard document 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.
  • BS schedules downlink so that HARQ-ACK information can be multiplexed on one PUCCH resource. Should be done.
  • 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.
  • 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.
  • HARQ-ACK PUCCHs or PUSCHs
  • a DCI field having a configurable size is configured. May be considered.
  • 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.
  • 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.
  • 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.
  • the control channel or a control channel for scheduling a data channel corresponding thereto
  • DCI information corresponds 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.
  • DCI size alignment/adjustment 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.
  • DCI size alignment/adjustment to avoid exceeding the monitoring-related UE capability for different DCI sizes may be performed as follows.
  • 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”.
  • 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
  • URLLC DCI format may be referred to as “configurable DCI format”
  • non-URLLC DCI format may be referred to as “non-configurable DCI format”.
  • the size of the configurable field may be smaller than that 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.
  • non-configurable 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.
  • 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.
  • 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
  • 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.
  • 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).
  • 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).
  • the DCI size actually used by the BS for transmission may be the DCI size obtained by completing the DCI size alignment
  • 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.
  • 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).
  • the non-URLLC DCI may mean DCI having a DCI format other than the URLLC DCI format.
  • 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.
  • 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.
  • 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.
  • the UL channel and the DL channel may be channels in units of slots or channels in units of mini-slots.
  • the UL channel and the DL channel may be channels for eMBB traffic or channels for URLLC traffic.
  • the DCI(s) (on the cell) 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.
  • 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.
  • a UL channel such as PUCCH or PUSCH
  • a DL channel such as PDSCH based on the transmitted DCI(s).
  • the UL channel and the DL channel may be channels in units of slots or channels in units of mini-slots.
  • the UL channel and the DL channel may be channels for eMBB traffic or channels for URLLC traffic.
  • the DL DCI format may be a DCI format for scheduling or triggering DL transmission
  • the UL DCI format may be a DCI format for scheduling or triggering UL transmission
  • the DL DCI format may mean a DCI format for scheduling a PDSCH or a DCI format for triggering transmission of a PUCCH
  • the UL DCI format may mean a DCI format for scheduling a PUSCH.
  • FIG. 17 illustrates a DCI size alignment process according to an example of the present specification.
  • 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.
  • 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.
  • 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).
  • 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.
  • 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.
  • 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.
  • 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.
  • DCI format X may not include DCI format 0_0 and DCI format 1_0 monitored in CSS (and/or USS).
  • 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
  • DCI format X 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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
  • 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
  • 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.
  • 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.
  • 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.
  • FIG. 18 illustrates a DCI size alignment process according to another example of the present specification.
  • FIG. 18 illustrates a DCI size alignment process according to option 4.
  • the non-fallback DCI format may correspond to the URLLC DCI format.
  • 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.
  • 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).
  • the BS and the UE may perform step 4 of the first size alignment process (S1810).
  • 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:
  • the total number of different DCI sizes with C-RNTI configured to monitor is not more than X for that cell.
  • X can be 3.
  • FIGS. 19 and 20 illustrate a DCI size alignment process according to another example of the present specification.
  • FIGS. 19 and 20 illustrate a DCI size alignment process according to option 5.
  • the non-fallback DCI format may correspond to the URLLC DCI format.
  • 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:
  • 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.
  • 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 may be applied to format 1_0 and DCI format 0_0 or DCI format 1_1 or DCI format 0_1.
  • 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.
  • 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).
  • the BS and the UE may perform step 4 of the first size alignment process (S1910).
  • 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:
  • the total number of different DCI sizes set to monitor with C-RNTI is not more than X for that cell.
  • X can be 3.
  • 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 :
  • 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.
  • 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).
  • the BS and the UE may perform step 4 of the first size alignment process (S2010).
  • 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:
  • the total number of different DCI sizes set to monitor with C-RNTI is not more than X for that cell.
  • X can be 3.
  • 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.
  • 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.
  • parameter(s) used for scheduling 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.
  • FIG. 21 and 22 illustrate the operation flow of the UE and BS based on some implementations of this specification related to DCI parameter selection.
  • FIG. 21 illustrates an operation flow of a UE based on some implementations related to DCI parameter selection
  • FIG. 22 illustrates an operation flow of a BS based on some implementations related to DCI parameter selection.
  • 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).
  • 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).
  • the BS may generate a DCI (S2200).
  • 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).
  • the base station may receive a UL channel from the UE or transmit a DL channel accordingly (S2204).
  • 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.
  • the PDCCH 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • a specific target service eg, URLLC
  • 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.
  • 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.
  • 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.
  • DRX discontinuous reception
  • 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.
  • 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.
  • 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.
  • 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.
  • DRX discontinuous reception
  • 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.
  • Implementations of the present specification may be used in a wireless communication system, a base station or user equipment, and other equipment.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention porte sur un équipement utilisateur pouvant surveiller, dans une période d'activation selon des configurations DRX, un PDCCH destiné à transporter des DCI. L'équipement utilisateur peut régler une taille DCI à surveiller sur la base de l'alignement de la taille DCI. L'alignement de la taille DCI peut consister à régler la taille d'un format DCI UL sans repli ainsi que la taille d'un format DCI DL sans repli, puis à régler la taille d'un format DCI UL de repli et la taille d'un format DCI DL de repli. Le format DCI UL sans repli et le format DCI UL de repli sont utilisés pour programmer un PUSCH, et le format DCI DL sans repli et le format DCI DL de repli sont utilisés pour planifier un canal partagé de liaison descendante physique (PDSCH).
PCT/KR2020/004182 2019-03-29 2020-03-27 Procédés de réception d'informations de commande de liaison descendante, équipement utilisateur, support d'informations, procédé de transmission d'informations de commande de liaison descendante, et station de base WO2020204481A1 (fr)

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
KR10-2019-0037422 2019-03-29
KR20190037422 2019-03-29
KR10-2019-0051788 2019-05-02
KR20190051788 2019-05-02
KR20190100009 2019-08-15
KR10-2019-0100009 2019-08-15

Publications (1)

Publication Number Publication Date
WO2020204481A1 true WO2020204481A1 (fr) 2020-10-08

Family

ID=72666931

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2020/004182 WO2020204481A1 (fr) 2019-03-29 2020-03-27 Procédés de réception d'informations de commande de liaison descendante, équipement utilisateur, support d'informations, procédé de transmission d'informations de commande de liaison descendante, et station de base

Country Status (1)

Country Link
WO (1) WO2020204481A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114765480A (zh) * 2021-01-14 2022-07-19 ***通信有限公司研究院 Dci大小确定方法、装置、终端及存储介质

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013055193A2 (fr) * 2011-10-13 2013-04-18 엘지전자 주식회사 Procédé et dispositif de réception d'informations de commande dans un système de communication sans fil

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013055193A2 (fr) * 2011-10-13 2013-04-18 엘지전자 주식회사 Procédé et dispositif de réception d'informations de commande dans un système de communication sans fil

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"On PDCCH enhancements for eURLLC", R1-1902493, 3GPP TSG RAN WG1 #96, 16 February 2019 (2019-02-16), Athens, Greece, XP051600189 *
ERICSSON: "PDCCH enhancements for NR URLLC", R1-1901593, 3GPP TSG RAN WG1 #96, 16 February 2019 (2019-02-16), Athens, Greece, XP051599290 *
PANASONIC: "PDCCH enhancements for NR URLLC", R1-1902399, 3GPP TSG RAN WG1 #96, 15 February 2019 (2019-02-15), Athens, Greece, XP051600095 *
VIVO: "PDCCH enhancements for URLLC", R1-1901692, 3GPP TSG RAN WG1 #96, 16 February 2019 (2019-02-16), Athens, Greece, XP051599388 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114765480A (zh) * 2021-01-14 2022-07-19 ***通信有限公司研究院 Dci大小确定方法、装置、终端及存储介质

Similar Documents

Publication Publication Date Title
WO2020204526A1 (fr) Procédé de transmission de livre de codes harq-ack, équipement utilisateur, dispositif et support de stockage, procédé de réception de livre de codes harq-ack et station de base
WO2020197333A1 (fr) Procédé, équipement utilisateur, dispositif et support de stockage permettant d'exécuter une transmission de liaison montante, et procédé et station de base permettant d'exécuter une réception de liaison montante
WO2020226391A1 (fr) Procédé, équipement utilisateur, dispositif et support de stockage pour la transmission de pusch, et procédé et station de base pour la réception de pusch
WO2020197338A1 (fr) Procédé, équipement utilisateur, dispositif et support d'informations pour réaliser une transmission de liaison montante et procédé et station de base pour réaliser une réception de liaison montante
WO2020204486A1 (fr) Procédé de transmission d'informations de commande de liaison descendante et station de base, procédé de réception d'informations de commande de liaison descendante, équipement d'utilisateur et support de stockage
WO2021100982A1 (fr) Procédé de transmission de livre de codes harq-ack, équipement utilisateur, dispositif et support d'enregistrement, et procédé et station de base de réception de livre de codes harq-ack
WO2021091350A1 (fr) Procédé, équipement d'utilisateur, appareil et support de stockage lisible par ordinateur pour la transmission de pusch et procédé et station de base pour la réception de pusch
WO2020145773A1 (fr) Procédé, équipement utilisateur, dispositif et support de stockage pour transmettre une liaison montante, et procédé et station de base pour recevoir une liaison montante
WO2020167065A1 (fr) Procédé, équipement utilisateur et support de stockage pour une transmission de liaison montante, et procédé et station de base pour une réception de liaison montante
WO2020167014A1 (fr) Procédé, équipement d'utilisateur, dispositif et support d'informations pour réaliser une émission de liaison montante et procédé et station de base pour réaliser une réception de liaison montante
WO2021158067A1 (fr) Procédé, dispositif utilisateur et support de stockage pour transmettre un canal de liaison montante, et procédé et station de base pour recevoir un canal de liaison montante
WO2020204528A1 (fr) Procédé, équipement utilisateur, dispositif et support d'enregistrement pour réaliser une transmission de liaison montante et procédé et station de base pour réaliser une réception de liaison montante
WO2022031110A1 (fr) Procédé, équipement utilisateur, dispositif de traitement, support de stockage et programme informatique permettant de transmettre un canal de liaison montante, et procédé et station de base permettant de recevoir un canal de liaison montante
WO2021029708A1 (fr) Procédé, dispositif de transmission, et support d'enregistrement permettant de transmettre un bloc de transport dans une bande sans licence
WO2021194301A1 (fr) Procédé de transmission de harq-ack, équipement utilisateur et support de stockage, et procédé de réception de harq-ack et station de base
WO2020145772A1 (fr) Procédé et équipement utilisateur pour effectuer une transmission de liaison montante, et procédé pour effectuer une réception de liaison montante
WO2022086268A1 (fr) Procédé, équipement utilisateur, dispositif de traitement, support de stockage et programme informatique permettant la transmission d'un rapport d'informations d'état de canal, et procédé et station de base permettant la réception d'un rapport d'informations d'état de canal
WO2020197358A1 (fr) Procédé, équipement utilisateur, dispositif et support d'informations pour réaliser une transmission de liaison montante et procédé et station de base pour réaliser une réception de liaison montante
WO2020204541A1 (fr) Procédé, équipement utilisateur, dispositif et support de stockage permettant de réaliser une émission en liaison montante, et procédé et station de base permettant de réaliser une réception en liaison montante
WO2022031102A1 (fr) Procédé de transmission de canal de liaison montante, dispositif utilisateur, dispositif de traitement, support de stockage, programme informatique, procédé de réception de canal de liaison montante, et station de base
WO2021066596A1 (fr) Procédé de surveillance d'instructions d'annulation de liaison montante, équipement utilisateur, appareil, support d'enregistrement lisible par ordinateur, procédé de transmission d'instructions d'annulation de liaison montante, et station de base
WO2022086263A1 (fr) Procédé, équipement d'utilisateur, dispositif de traitement, support de stockage et programme informatique pour la réception d'un canal de liaison descendante, et procédé et station de base pour la transmission d'un canal de liaison descendante
WO2022031101A1 (fr) Procédé, équipement utilisateur, dispositif de traitement, support de stockage et programme informatique permettant de transmettre un canal de liaison montante, et procédé et station de base permettant de recevoir un canal de liaison montante
WO2021066311A1 (fr) Procédé de réception de pdcch, équipement utilisateur, dispositif et support de stockage, ainsi que procédé de transmission de pdcch et station de base
WO2020204533A1 (fr) Procédé, équipement d'utilisateur, dispositif et support de stockage permettant de réaliser une transmission de liaison montante et procédé et station de base pour réaliser une réception de liaison montante

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20782118

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20782118

Country of ref document: EP

Kind code of ref document: A1