WO2021010705A1 - Procédé pour émettre et recevoir des informations harq-ack dans un système de communication sans fil et dispositif associé - Google Patents

Procédé pour émettre et recevoir des informations harq-ack dans un système de communication sans fil et dispositif associé Download PDF

Info

Publication number
WO2021010705A1
WO2021010705A1 PCT/KR2020/009190 KR2020009190W WO2021010705A1 WO 2021010705 A1 WO2021010705 A1 WO 2021010705A1 KR 2020009190 W KR2020009190 W KR 2020009190W WO 2021010705 A1 WO2021010705 A1 WO 2021010705A1
Authority
WO
WIPO (PCT)
Prior art keywords
harq
dci
index
information
ack
Prior art date
Application number
PCT/KR2020/009190
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 WO2021010705A1 publication Critical patent/WO2021010705A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • 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
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA

Definitions

  • the present specification relates to a wireless communication system, and more particularly, to a method of transmitting and receiving HARQ-ACK information based on multiple Transmission Reception Points (TRPs) and an apparatus supporting the same.
  • TRPs Transmission Reception Points
  • Mobile communication systems have been developed to provide voice services while ensuring user activity.
  • the mobile communication system has expanded to not only voice but also data services, and nowadays, the explosive increase in traffic causes a shortage of resources and users request higher speed services, so a more advanced mobile communication system is required. .
  • next-generation mobile communication system The requirements of the next-generation mobile communication system are largely explosive data traffic acceptance, dramatic increase in transmission rate per user, largely increased number of connected devices, very low end-to-end latency, and support for high energy efficiency. You should be able to. To this end, dual connectivity, Massive Multiple Input Multiple Output (MIMO), In-band Full Duplex, Non-Orthogonal Multiple Access (NOMA), and Super Wideband Various technologies such as wideband) support and device networking are being studied.
  • MIMO Massive Multiple Input Multiple Output
  • NOMA Non-Orthogonal Multiple Access
  • Super Wideband Various technologies such as wideband support and device networking are being studied.
  • This specification proposes a method for transmitting and receiving HARQ-ACK information by a terminal supported by a plurality of Transmission Reception Points (TRPs) in a wireless communication system.
  • TRPs Transmission Reception Points
  • this specification proposes a method of configuring a HARQ-ACK codebook in consideration of multiple TRP operations.
  • the present specification proposes a method of classifying multiple TRPs based on an index of a control resource set group (or pool) associated with a control resource set in which a downlink control channel is received.
  • this specification proposes a method of determining a resource of an uplink channel for transmitting HARQ-ACK information.
  • a preamble for random access is provided. Transmitting; Receiving a response message for random access corresponding to the preamble, a radio remote control (RRC) connection is established based on the preamble and the response message; Receiving a plurality of downlink control information (DCI) through a physical downlink control channel (PDCCH), each control resource set associated with the PDCCH to which each DCI is received is a different control resource Corresponds to a group of sets; Receiving a physical downlink shared channel (PDSCH) scheduled by each DCI in slot n; And transmitting HARQ-ACK information corresponding to the PDSCH in slot n+k through a physical uplink control channel (PUCCH), wherein k is the number of slots, and the resource of the PUCCH is It is determined based on a specific DCI among the plurality
  • RRC radio remote control
  • each DCI includes (i) a field related to the number of slots k and (ii) a PUCCH resource indication field, and the resource of the PUCCH is the specific DCI. It may be determined based on the PUCCH resource indication field.
  • the HARQ-ACK information includes (i) first HARQ-ACK information corresponding to a PDSCH associated with a first control resource set corresponding to a first control resource set group, and (ii) Second HARQ-ACK information corresponding to the PDSCH associated with the second control resource set corresponding to the second control resource set group may be concatenated and configured as one.
  • the order of the plurality of DCIs is determined in an ascending order of the cell index for a monitoring opportunity related to a PDCCH of the same index, and then related to the PDCCH.
  • the order may be determined in ascending order of the index of monitoring opportunities.
  • the order may be determined in an ascending order of the index of each control resource set group for the monitoring opportunity and the same cell index related to the PDCCH of the same index.
  • the specific DCI may be a last DCI among the plurality of DCIs.
  • the second control resource set based on the index of the first control resource set group being 0 and the index of the second control resource set group being 1, the second control resource set The DCI received through the PDCCH associated with the second control resource set corresponding to the group may be determined as the specific DCI.
  • the first control resource set group is included in a first serving cell
  • the second resource set group is included in a second serving cell
  • the first serving The first HARQ-ACK information associated with a cell and the second HARQ-ACK information associated with the second serving cell may be respectively generated and then concatenated.
  • the method further includes receiving configuration information, wherein the configuration information is configured as one by concatenating the first HARQ-ACK information and the second HARQ-ACK information It may include information indicating whether or not.
  • the HARQ-ACK information includes (i) first HARQ-ACK information corresponding to a PDSCH associated with a first control resource set corresponding to a first control resource set group, and (ii) The second HARQ-ACK information corresponding to the PDSCH associated with the second control resource set corresponding to the second control resource set group may be individually configured.
  • the first HARQ-ACK information and the second HARQ-ACK information may be transmitted by time division multiplexing (TDM) in one slot, respectively.
  • TDM time division multiplexing
  • the HARQ-ACK information and a physical uplink shared channel based on a value of a downlink assignment indicator (DAI) field of a specific DCI of DCI format 0_1 among the plurality of DCIs Multiplexing (multiplexing) of (physical uplink shared channel, PUSCH) may be indicated.
  • DCI downlink assignment indicator
  • the HARQ-ACK information may be transmitted through at least one of a first transmission/reception point or a second transmission/reception point.
  • the terminal comprises: one or more transceivers; One or more processors; And one or more memories that store instructions for operations executed by the one or more processors, and are connected to the one or more processors, wherein the operations are preambles for random access.
  • HARQ-ACK Hybrid Automatic Repeat and ReQuest-Acknowledgement
  • a radio remote control (RRC) connection is established based on the preamble and the response message;
  • RRC radio remote control
  • a preamble for random access is provided.
  • a radio remote control (RRC) connection is established based on the preamble and the response message; Transmitting a plurality of downlink control information (DCI) through a physical downlink control channel (PDCCH) to a user equipment (UE), associated with a PDCCH through which each DCI is transmitted Each control resource set corresponds to a different control resource set group; Transmitting a physical downlink shared channel (PDSCH) scheduled by each DCI in slot n; And receiving HARQ-ACK information corresponding to the PDSCH in slot n+k through a physical uplink control channel (PUCCH), wherein k is the number of slots, and the resource of the PUCCH is It is determined based on a specific DCI among the plurality of DCIs, and the specific DCI is based on i) an index of a monitoring occasion related to the PDCCH, (ii) a cell index, and (iii) an index of each control resource
  • the base station comprises: one or more transceivers;
  • One or more processors And one or more memories that store instructions for operations executed by the one or more processors, and are connected to the one or more processors, wherein the operations are preambles for random access.
  • the one or more processors allow the device to perform random access. Transmitting a preamble for, and receiving a response message for random access corresponding to the preamble, a radio remote control (RRC) connection is established based on the preamble and the response message, and a physical downlink control channel ( Receives a plurality of downlink control information (DCI) through a physical downlink control channel (PDCCH), and receives a physical downlink shared channel (PDSCH) scheduled by each DCI in slot n And, the HARQ-ACK information corresponding to the PDSCH is controlled to be transmitted in slot n+k through a physical uplink control channel (PUCCH), but each control resource set associated with the PDCCH in which each DCI is received is Corresponding to different control resource set groups, k is the number of slots, the resource of the PUCCH is determined based on a specific DCI among the plurality
  • RRC radio remote control
  • the one or more commands include a user equipment (UE) transmitting a preamble for random access and receiving a response message for random access corresponding to the preamble, based on the preamble and the response message.
  • UE user equipment
  • RRC radio remote control
  • PDSCH physical downlink control channel
  • PUCCH physical uplink control channel
  • each control resource set associated with a PDCCH in which each DCI is received corresponds to a different control resource set group
  • k is the number of slots
  • the resource of the PUCCH is the plurality of It is determined based on a specific DCI among DCI, and the specific DCI is determined based on i) an index of a monitoring occasion related to the PDCCH, (ii) a cell index, and (iii) an index of each control resource set group.
  • HARQ-ACK information may be transmitted and received for a plurality of TRPs.
  • HARQ-ACK information may be transmitted and received in consideration of HARQ-ACK timing.
  • a HARQ-ACK codebook may be configured in consideration of multiple TRP operations.
  • a resource of an uplink channel for transmitting HARQ-ACK information may be determined, and HARQ-ACK information may be transmitted and received based on the determined resource.
  • the index of the control resource set group associated with the control resource set may be determined as a specific value.
  • FIG. 1 shows an example of an overall system structure of an NR to which the method proposed in the present specification can be applied.
  • FIG. 2 shows a relationship between an uplink frame and a downlink frame in a wireless communication system to which the method proposed in the present specification can be applied.
  • FIG 3 shows an example of a frame structure in an NR system.
  • FIG. 4 shows an example of a resource grid supported by a wireless communication system to which the method proposed in the present specification can be applied.
  • FIG. 5 shows examples of an antenna port and a resource grid for each neurology to which the method proposed in the present specification can be applied.
  • FIG. 6 illustrates physical channels and general signal transmission used in a 3GPP system.
  • FIG. 7 is a diagram illustrating an example of a downlink transmission/reception operation.
  • FIG. 8 is a diagram illustrating an example of an uplink transmission/reception operation.
  • FIG. 9 is a flowchart showing an example of a CSI-related procedure.
  • FIG. 10 is a diagram showing an example of HARQ-ACK timing (K1).
  • FIG. 11 shows an example of a transmission/reception method for improving reliability using transmission in a plurality of TRPs.
  • FIG. 12 shows an example of a method of generating a HARQ-ACK codebook for multi-TRP (eg, TRP1, TRP2).
  • FIG. 13 is an example of a summary diagram showing conditions related to generation of a compressed quasi-static HARQ-ACK codebook and various cases of operations corresponding to the condition.
  • FIG. 14 shows an example of a signaling procedure for performing data transmission/reception between a network side and a terminal (UE) in the context of multiple TRPs to which the method and/or embodiments proposed in the present specification can be applied .
  • FIG. 15 shows an example of an operation flowchart of a terminal transmitting HARQ-ACK information to which the method and/or embodiment proposed in the present specification can be applied.
  • 16 shows an example of an operation flowchart of a base station receiving HARQ-ACK information to which the method and/or embodiment proposed in the present specification can be applied.
  • FIG. 17 illustrates a communication system 1 applied to the present invention.
  • 19 illustrates a signal processing circuit for a transmission signal.
  • 21 illustrates a portable device applied to the present invention.
  • downlink refers to communication from a base station to a terminal
  • uplink refers to communication from a terminal to a base station
  • the transmitter may be part of the base station, and the receiver may be part of the terminal.
  • the transmitter may be part of the terminal, and the receiver may be part of the base station.
  • the base station may be referred to as a first communication device, and the terminal may be referred to as a second communication device.
  • Base station is a fixed station, Node B, evolved-NodeB (eNB), Next Generation NodeB (gNB), base transceiver system (BTS), access point (AP), network (5G).
  • BS Base station
  • eNB evolved-NodeB
  • gNB Next Generation NodeB
  • BTS base transceiver system
  • AP access point
  • 5G network
  • the terminal may be fixed or mobile, and UE (User Equipment), MS (Mobile Station), UT (user terminal), MSS (Mobile Subscriber Station), SS (Subscriber Station), AMS (Advanced Mobile) Station), WT (Wireless terminal), MTC (Machine-Type Communication) device, M2M (Machine-to-Machine) device, D2D (Device-to-Device) device, vehicle, robot, AI module , Drone (Unmanned Aerial Vehicle, UAV), AR (Augmented Reality) device, VR (Virtual Reality) device.
  • UE User Equipment
  • MS Mobile Station
  • UT user terminal
  • MSS Mobile Subscriber Station
  • SS Subscriber Station
  • AMS Advanced Mobile
  • WT Wireless terminal
  • MTC Machine-Type Communication
  • M2M Machine-to-Machine
  • D2D Device-to-Device
  • vehicle robot
  • AI module Drone (Unmanned Aerial Vehicle, UAV), AR (Augmented Reality) device
  • CDMA may be implemented with a radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000.
  • TDMA may be implemented with radio technologies such as Global System for Mobile communications (GSM)/General Packet Radio Service (GPRS)/Enhanced Data Rates for GSM Evolution (EDGE).
  • GSM Global System for Mobile communications
  • GPRS General Packet Radio Service
  • EDGE Enhanced Data Rates for GSM Evolution
  • OFDMA may be implemented with a wireless technology such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (Evolved UTRA).
  • Wi-Fi IEEE 802.11
  • WiMAX IEEE 802.16
  • IEEE 802-20 and E-UTRA
  • Evolved UTRA Evolved UTRA
  • 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is a part of Evolved UMTS (E-UMTS) using E-UTRA
  • LTE-A Advanced
  • LTE-A pro is an evolved version of 3GPP LTE
  • 3GPP New Radio or New Radio Access Technology (NR) is an evolved version of 3GPP LTE/LTE-A/LTE-A pro.
  • LTE refers to technology after 3GPP TS 36.xxx Release 8.
  • LTE technology after 3GPP TS 36.xxx Release 10 is referred to as LTE-A
  • LTE technology after 3GPP TS 36.xxx Release 13 is referred to as LTE-A pro
  • 3GPP NR refers to the technology after TS 38.xxx Release 15.
  • LTE/NR may be referred to as a 3GPP system.
  • "xxx" means standard document detail number.
  • LTE/NR may be collectively referred to as a 3GPP system.
  • RRC Radio Resource Control
  • RRC Radio Resource Control
  • NR is an expression showing an example of a 5G radio access technology (RAT).
  • RAT radio access technology
  • the three main requirements areas for 5G are (1) Enhanced Mobile Broadband (eMBB) area, (2) Massive Machine Type Communication (mMTC) area, and (3) ultra-reliability and It includes a low-latency communication (Ultra-reliable and Low Latency Communications, URLLC) area.
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • URLLC Low Latency Communications
  • KPI key performance indicator
  • eMBB goes far beyond basic mobile Internet access, covering rich interactive work, media and entertainment applications in the cloud or augmented reality.
  • Data is one of the key drivers of 5G, and it may not be possible to see dedicated voice services for the first time in the 5G era.
  • voice is expected to be processed as an application program simply using the data connection provided by the communication system.
  • the main reasons for the increased traffic volume are an increase in content size and an increase in the number of applications requiring high data rates.
  • Streaming services (audio and video), interactive video and mobile Internet connections will become more widely used as more devices connect to the Internet. Many of these applications require always-on connectivity to push real-time information and notifications to the user.
  • Cloud storage and applications are increasing rapidly in mobile communication platforms, which can be applied to both work and entertainment.
  • cloud storage is a special use case that drives the growth of the uplink data rate.
  • 5G is also used for remote work in the cloud, and requires much lower end-to-end delays to maintain a good user experience when tactile interfaces are used.
  • Entertainment For example, cloud gaming and video streaming is another key factor that is increasing the demand for mobile broadband capabilities. Entertainment is essential on smartphones and tablets anywhere, including high mobility environments such as trains, cars and airplanes.
  • Another use case is augmented reality and information retrieval for entertainment.
  • augmented reality requires very low latency and an instantaneous amount of data.
  • one of the most anticipated 5G use cases relates to the ability to seamlessly connect embedded sensors in all fields, i.e. mMTC.
  • mMTC massive machine type computer
  • Industrial IoT is one of the areas where 5G plays a major role in enabling smart cities, asset tracking, smart utilities, agriculture and security infrastructure.
  • URLLC includes new services that will transform the industry with ultra-reliable/low-latency links such as self-driving vehicles and remote control of critical infrastructure.
  • the level of reliability and delay is essential for smart grid control, industrial automation, robotics, drone control and coordination.
  • 5G can complement fiber-to-the-home (FTTH) and cable-based broadband (or DOCSIS) as a means of providing streams rated at hundreds of megabits per second to gigabits per second. This high speed is required to deliver TVs in 4K or higher (6K, 8K and higher) resolutions as well as virtual and augmented reality.
  • Virtual Reality (VR) and Augmented Reality (AR) applications involve almost immersive sports events. Certain application programs may require special network settings. In the case of VR games, for example, game companies may need to integrate core servers with network operators' edge network servers to minimize latency.
  • Automotive is expected to be an important new driving force in 5G, with many use cases for mobile communication to vehicles. For example, entertainment for passengers demands simultaneous high capacity and high mobility mobile broadband. The reason is that future users will continue to expect high-quality connections, regardless of their location and speed.
  • Another application example in the automotive field is an augmented reality dashboard. It identifies an object in the dark on top of what the driver is looking through the front window, and displays information that tells the driver about the distance and movement of the object overlaid.
  • wireless modules enable communication between vehicles, exchange of information between the vehicle and supporting infrastructure, and exchange of information between the vehicle and other connected devices (eg, devices carried by pedestrians).
  • the safety system allows the driver to lower the risk of accidents by guiding alternative courses of action to make driving safer.
  • the next step will be a remote controlled or self-driven vehicle. It is very reliable and requires very fast communication between different self-driving vehicles and between the vehicle and the infrastructure. In the future, self-driving vehicles will perform all driving activities, and drivers will be forced to focus only on traffic anomalies that the vehicle itself cannot identify.
  • the technical requirements of self-driving vehicles call for ultra-low latency and ultra-fast reliability to increase traffic safety to levels unachievable by humans.
  • Smart cities and smart homes referred to as smart society, will be embedded with high-density wireless sensor networks.
  • a distributed network of intelligent sensors will identify the conditions for cost and energy-efficient maintenance of a city or home.
  • a similar setup can be done for each household.
  • Temperature sensors, window and heating controllers, burglar alarms and appliances are all wirelessly connected. Many of these sensors are typically low data rates, low power and low cost. However, for example, real-time HD video may be required in certain types of devices for surveillance.
  • the smart grid interconnects these sensors using digital information and communication technologies to collect information and act accordingly. This information can include the behavior of suppliers and consumers, allowing smart grids to improve efficiency, reliability, economics, sustainability of production and the distribution of fuels such as electricity in an automated way.
  • the smart grid can also be viewed as another low-latency sensor network.
  • the health sector has many applications that can benefit from mobile communications.
  • the communication system can support telemedicine providing clinical care from remote locations. This can help reduce barriers to distance and improve access to medical services that are not consistently available in remote rural areas. It is also used to save lives in critical care and emergencies.
  • a wireless sensor network based on mobile communication may provide remote monitoring and sensors for parameters such as heart rate and blood pressure.
  • Wireless and mobile communications are becoming increasingly important in industrial applications. Wiring is expensive to install and maintain. Thus, the possibility of replacing cables with reconfigurable wireless links is an attractive opportunity for many industries. However, achieving this requires that the wireless connection operates with a delay, reliability and capacity similar to that of the cable, and its management is simplified. Low latency and very low error probability are new requirements that need to be connected to 5G.
  • Logistics and freight tracking are important use cases for mobile communications that enable tracking of inventory and packages from anywhere using location-based information systems. Logistics and freight tracking use cases typically require low data rates, but require a wide range and reliable location information.
  • a new RAT system including NR uses an OFDM transmission scheme or a similar transmission scheme.
  • the new RAT system may follow OFDM parameters different from those of LTE.
  • the new RAT system follows the numerology of the existing LTE/LTE-A as it is, but can have a larger system bandwidth (eg, 100 MHz).
  • one cell may support a plurality of neurology. That is, terminals operating in different neurology can coexist within one cell.
  • Numerology corresponds to one subcarrier spacing in the frequency domain.
  • different numerology can be defined.
  • eLTE eNB is an evolution of eNB that supports connectivity to EPC and NGC.
  • gNB A node that supports NR as well as connection with NGC.
  • New RAN A radio access network that supports NR or E-UTRA or interacts with NGC.
  • Network slice is a network defined by an operator to provide an optimized solution for specific market scenarios that require specific requirements with end-to-end coverage.
  • Network function is a logical node within a network infrastructure with well-defined external interfaces and well-defined functional behaviors.
  • NG-C Control plane interface used for the NG2 reference point between the new RAN and NGC.
  • NG-U User plane interface used for the NG3 reference point between the new RAN and NGC.
  • Non-standalone NR A deployment configuration in which gNB requires LTE eNB as an anchor for control plane connection to EPC or eLTE eNB as an anchor for control plane connection to NGC.
  • Non-standalone E-UTRA Deployment configuration in which eLTE eNB requires gNB as an anchor for control plane connection to NGC.
  • User plane gateway The endpoint of the NG-U interface.
  • FIG. 1 shows an example of an overall system structure of an NR to which the method proposed in the present specification can be applied.
  • the NG-RAN is composed of gNBs that provide a control plane (RRC) protocol termination for an NG-RA user plane (new AS sublayer/PDCP/RLC/MAC/PHY) and a user equipment (UE). do.
  • RRC control plane
  • UE user equipment
  • the gNBs are interconnected through an X n interface.
  • the gNB is also connected to the NGC through the NG interface.
  • the gNB is connected to an Access and Mobility Management Function (AMF) through an N2 interface and a User Plane Function (UPF) through an N3 interface.
  • AMF Access and Mobility Management Function
  • UPF User Plane Function
  • the neurology may be defined by subcarrier spacing and CP (Cyclic Prefix) overhead.
  • the plurality of subcarrier intervals is an integer N (or, It can be derived by scaling with ). Further, even if it is assumed that a very low subcarrier spacing is not used at a very high carrier frequency, the neurology to be used can be selected independently of the frequency band.
  • OFDM Orthogonal Frequency Division Multiplexing
  • a number of OFDM neurology supported in the NR system may be defined as shown in Table 1.
  • NR supports multiple numerology (or subcarrier spacing (SCS)) to support various 5G services. For example, when the SCS is 15 kHz, it supports a wide area in traditional cellular bands, and when the SCS is 30 kHz/60 kHz, it is dense-urban, lower latency. And a wider carrier bandwidth (wider carrier bandwidth) is supported, and when the SCS is 60 kHz or higher, a bandwidth greater than 24.25 GHz is supported to overcome phase noise.
  • SCS subcarrier spacing
  • the NR frequency band is defined as a frequency range of two types (FR1, FR2).
  • FR1 and FR2 may be configured as shown in Table 2 below. Further, FR2 may mean a millimeter wave (mmW).
  • mmW millimeter wave
  • Downlink and uplink transmission It is composed of a radio frame having a section of.
  • each radio frame It consists of 10 subframes having a section of.
  • FIG. 2 shows a relationship between an uplink frame and a downlink frame in a wireless communication system to which the method proposed in the present specification can be applied.
  • the slots are within a subframe Are numbered in increasing order of, within the radio frame Are numbered in increasing order.
  • One slot is Consisting of consecutive OFDM symbols of, Is determined according to the used neurology and slot configuration. Slot in subframe Start of OFDM symbol in the same subframe It is aligned in time with the beginning of.
  • Table 3 shows the number of OFDM symbols per slot in a normal CP ( ), the number of slots per radio frame ( ), the number of slots per subframe ( ), and Table 4 shows the number of OFDM symbols per slot, the number of slots per radio frame, and the number of slots per subframe in an extended CP.
  • 3 shows an example of a frame structure in an NR system. 3 is merely for convenience of description and does not limit the scope of the present invention.
  • 1 subframe may include 4 slots.
  • a mini-slot may be composed of 2, 4 or 7 symbols, or may be composed of more or fewer symbols.
  • an antenna port In relation to the physical resource in the NR system, an antenna port, a resource grid, a resource element, a resource block, a carrier part, etc. Can be considered.
  • the antenna port is defined such that a channel carrying a symbol on the antenna port can be inferred from a channel carrying another symbol on the same antenna port.
  • the two antenna ports are QC/QCL (quasi co-located or quasi co-location) relationship.
  • the wide range characteristic includes one or more of delay spread, Doppler spread, frequency shift, average received power, and received timing.
  • FIG. 4 shows an example of a resource grid supported by a wireless communication system to which the method proposed in the present specification can be applied.
  • the resource grid on the frequency domain It is composed of subcarriers, and one subframe Although it is exemplarily described as consisting of OFDM symbols, it is not limited thereto.
  • the transmitted signal is One or more resource grids composed of subcarriers and Is described by the OFDM symbols. From here, to be. remind Denotes a maximum transmission bandwidth, which may vary between uplink and downlink as well as neurology.
  • the neurology And one resource grid may be configured for each antenna port p.
  • FIG. 5 shows examples of an antenna port and a resource grid for each neurology to which the method proposed in the present specification can be applied.
  • each element of the resource grid for the antenna port p is referred to as a resource element, and an index pair Is uniquely identified by From here, Is the index in the frequency domain, Refers to the position of a symbol within a subframe.
  • an index pair Is used. From here, to be.
  • antenna port p Is a complex value Corresponds to. If there is no risk of confusion or if a specific antenna port or neurology is not specified, the indices p and Can be dropped, resulting in a complex value or Can be
  • the physical resource block (physical resource block) in the frequency domain It is defined as consecutive subcarriers.
  • Point A serves as a common reference point of the resource block grid and can be obtained as follows.
  • -OffsetToPointA for the PCell downlink indicates the frequency offset between the lowest subcarrier of the lowest resource block and point A of the lowest resource block that overlaps the SS/PBCH block used by the UE for initial cell selection, and the 15 kHz subcarrier spacing for FR1 and It is expressed in resource block units assuming a 60 kHz subcarrier spacing for FR2;
  • -absoluteFrequencyPointA represents the frequency-position of point A expressed as in the absolute radio-frequency channel number (ARFCN).
  • Common resource blocks set the subcarrier interval Numbered from 0 to the top in the frequency domain for.
  • Subcarrier spacing setting The center of subcarrier 0 of the common resource block 0 for is coincided with'point A'.
  • the resource element (k,l) for may be given as in Equation 1 below.
  • Is It can be defined relative to point A so that it corresponds to a subcarrier centered on point A.
  • Physical resource blocks are from 0 in the bandwidth part (BWP) Numbered to, Is the number of the BWP.
  • Physical resource block in BWP i And common resource block The relationship between may be given by Equation 2 below.
  • the NR system can support up to 400 MHz per component carrier (CC). If the terminal operating in such a wideband CC always operates with the RF for the entire CC turned on, the terminal battery consumption may increase. Or, when considering several use cases (e.g., eMBB, URLLC, Mmtc, V2X, etc.) operating within one wideband CC, different numerology (e.g., sub-carrier spacing) for each frequency band within the CC may be supported. Or, the capability for the maximum bandwidth may be different for each terminal. In consideration of this, the base station can instruct the terminal to operate only in a portion of the bandwidth rather than the entire bandwidth of the wideband CC, and the portion of the bandwidth is defined as a bandwidth part (BWP) for convenience.
  • the BWP may be composed of continuous resource blocks (RBs) on the frequency axis, and may correspond to one numerology (e.g., sub-carrier spacing, CP length, slot/mini-slot duration).
  • the base station can set a number of BWPs even within one CC configured to the terminal. For example, in the PDCCH monitoring slot, a BWP occupying a relatively small frequency domain may be set, and a PDSCH indicated by the PDCCH may be scheduled on a larger BWP. Alternatively, if UEs are concentrated in a specific BWP, some UEs can be set to different BWPs for load balancing. Alternatively, in consideration of frequency domain inter-cell interference cancellation between neighboring cells, some spectrum of the total bandwidth may be excluded and both BWPs may be set within the same slot.
  • the base station can configure at least one DL/UL BWP to the terminal associated with the wideband CC, and at a specific time point at least one of the configured DL/UL BWP(s) (L1 signaling or MAC It can be activated by CE or RRC signaling, etc.) and switching to other configured DL/UL BWP can be indicated (by L1 signaling or MAC CE or RRC signaling, etc.) It can also be switched.
  • the activated DL/UL BWP is defined as the active DL/UL BWP.
  • the DL/UL BWP assumed by the terminal is the initial active DL Defined as /UL BWP.
  • a terminal receives information from a base station through a downlink (DL), and the terminal transmits information to the base station through an uplink (UL).
  • the information transmitted and received by the base station and the terminal includes data and various control information, and various physical channels exist according to the type/use of information transmitted and received by them.
  • the terminal When the terminal is powered on or newly enters a cell, the terminal performs an initial cell search operation such as synchronizing with the base station (S601). To this end, the UE receives a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS) from the base station to synchronize with the base station and obtain information such as cell ID. Thereafter, the terminal may receive a physical broadcast channel (PBCH) from the base station to obtain intra-cell broadcast information. Meanwhile, the UE may receive a downlink reference signal (DL RS) in the initial cell search step to check a downlink channel state.
  • PSS Primary Synchronization Signal
  • SSS Secondary Synchronization Signal
  • PBCH physical broadcast channel
  • DL RS downlink reference signal
  • the UE After completing the initial cell search, the UE acquires more detailed system information by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) according to the information carried on the PDCCH. It can be done (S602).
  • a physical downlink control channel (PDCCH)
  • a physical downlink shared channel (PDSCH)
  • the terminal may perform a random access procedure (RACH) for the base station (S603 to S606).
  • RACH random access procedure
  • the UE transmits a specific sequence as a preamble through a physical random access channel (PRACH) (S603 and S605), and a response message to the preamble through a PDCCH and a corresponding PDSCH (RAR (Random Access Response) message)
  • PRACH physical random access channel
  • RAR Random Access Response
  • a contention resolution procedure may be additionally performed (S606).
  • the UE receives PDCCH/PDSCH (S607) and Physical Uplink Shared Channel (PUSCH)/Physical Uplink Control Channel as a general uplink/downlink signal transmission procedure.
  • Control Channel; PUCCH) transmission (S608) may be performed.
  • the terminal may receive downlink control information (DCI) through the PDCCH.
  • DCI includes control information such as resource allocation information for the terminal, and different formats may be applied according to the purpose of use.
  • DCI format 0_0 and DCI format 0_1 are used for scheduling PUSCH in one cell
  • DCI format 1_0 and DCI format 1_1 are used for scheduling PDSCH in one cell.
  • the information included in DCI format 0_0 is CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI and transmitted.
  • DCI format 0_1 is used to reserve a PUSCH in one cell.
  • the information included in DCI format 0_1 is transmitted after being CRC scrambled by C-RNTI or CS-RNTI or SP-CSI-RNTI or MCS-C-RNTI.
  • DCI format 1_0 is used for PDSCH scheduling in one DL cell.
  • DCI format 1_0 The information included in DCI format 1_0 is transmitted after being CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI.
  • DCI format 1_1 is used for PDSCH scheduling in one cell.
  • Information included in DCI format 1_1 is transmitted after being CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI.
  • DCI format 2_1 is used to inform the PRB(s) and OFDM symbol(s) which may be assumed to be not intended for transmission by the UE.
  • Information such as preemption indication 1, preemption indication 2,..., preemption indication N included in DCI format 2_1 is CRC scrambled and transmitted by INT-RNTI.
  • control information transmitted by the terminal to the base station through the uplink or received from the base station by the terminal is a downlink/uplink ACK/NACK signal, a channel quality indicator (CQI), a precoding matrix index (PMI), a rank indicator (RI). ), etc.
  • the terminal may transmit control information such as CQI/PMI/RI described above through PUSCH and/or PUCCH.
  • PUCCH Physical uplink control channel
  • PUCCH supports a plurality of formats, and PUCCH formats can be classified by symbol duration, payload size, and multiplexing.
  • Table 5 below is a table showing an example of a PUCCH format.
  • the PUCCH formats in Table 5 can be largely classified into (1) short PUCCH and (2) long PUCCH.
  • PUCCH formats 0 and 2 may be included in the short PUCCH, and PUCCH formats 1, 3, and 4 may be included in the long PUCCH.
  • the terminal uses one or two serving cells in different symbols in one slot. PUCCHs are transmitted. When two PUCCHs are transmitted in one slot, at least one of the two PUCCHs has a structure of a short PUCCH. That is, in one slot, (1) short PUCCH and short PUCCH can be transmitted, and (2) long PUCCH and short PUCCH can be transmitted, but (3) long PUCCH and long PUCCH cannot be transmitted.
  • FIG. 7 is a diagram illustrating an example of a downlink transmission/reception operation.
  • the base station schedules downlink transmission such as a frequency/time resource, a transport layer, a downlink precoder, and MCS (S701).
  • the base station may determine a beam for PDSCH transmission to the terminal through the beam management operations described above.
  • the terminal receives downlink control information (DCI: Downlink Control Information) for downlink scheduling (ie, including scheduling information of the PDSCH) from the base station on the PDCCH (S702).
  • DCI Downlink Control Information
  • DCI format 1_0 or 1_1 can be used for downlink scheduling, and in particular, DCI format 1_1 includes the following information: DCI format identifier (Identifier for DCI formats), bandwidth part indicator (Bandwidth part indicator), frequency domain Resource allocation (Frequency domain resource assignment), time domain resource assignment (Time domain resource assignment), PRB bundling size indicator (PRB bundling size indicator), rate matching indicator (Rate matching indicator), ZP CSI-RS trigger (ZP CSI-RS trigger), antenna port(s) (Antenna port(s)), Transmission configuration indication (TCI), SRS request, Demodulation Reference Signal (DMRS) sequence initialization (DMRS sequence initialization)
  • DCI format identifier Identifier for DCI formats
  • bandwidth part indicator Bandwidth part indicator
  • frequency domain Resource allocation Frequency domain resource assignment
  • time domain resource assignment time domain resource assignment
  • PRB bundling size indicator PRB bundling size indicator
  • rate matching indicator Rate matching indicator
  • ZP CSI-RS trigger ZP CSI-RS
  • the number of DMRS ports may be scheduled according to each state indicated in the antenna port(s) field, and also single-user (SU)/multi-user (MU) transmission Scheduling is possible.
  • the TCI field is composed of 3 bits, and the QCL for the DMRS is dynamically indicated by indicating a maximum of 8 TCI states according to the value of the TCI field.
  • the terminal receives downlink data from the base station on the PDSCH (S703).
  • the UE detects a PDCCH including DCI format 1_0 or 1_1, the PDSCH is decoded according to an indication by the corresponding DCI.
  • the UE when the UE receives the PDSCH scheduled according to DCI format 1_1, the UE may set the DMRS configuration type according to the higher layer parameter'dmrs-Type', and the DMRS type is used to receive the PDSCH.
  • the terminal may set the maximum number of front-loaded DMRS symbols for the PDSCH by the higher layer parameter'maxLength'.
  • DMRS configuration type 1 when a single codeword is scheduled by the terminal and an antenna port mapped with an index of ⁇ 2, 9, 10, 11 or 30 ⁇ is designated, or the terminal schedules two codewords If so, the UE assumes that all remaining orthogonal antenna ports are not associated with PDSCH transmission to another UE.
  • DMRS configuration type 2 when a single codeword is scheduled in the terminal and an antenna port mapped with an index of ⁇ 2, 10 or 23 ⁇ is specified, or when two codewords are scheduled in the terminal, the terminal It is assumed that the remaining orthogonal antenna ports are not associated with PDSCH transmission to another terminal.
  • a precoding unit precoding granularity
  • P′ may correspond to one of ⁇ 2, 4, broadband ⁇ . If P'is determined to be broadband, the terminal does not expect to be scheduled with non-contiguous PRBs, and the terminal can assume that the same precoding is applied to the allocated resources.
  • P'is determined to be one of ⁇ 2, 4 ⁇ a precoding resource block group (PRG) is divided into P'consecutive PRBs. The actual number of consecutive PRBs in each PRG may be one or more. The UE may assume that the same precoding is applied to consecutive downlink PRBs in the PRG.
  • PRG precoding resource block group
  • the UE In order for the UE to determine the modulation order, target code rate, and transport block size in the PDSCH, the UE first reads the 5-bit MCS field in DCI, and the modulation order and target code Determine the rate. Then, the redundancy version field in the DCI is read, and the redundancy version is determined. Then, the UE determines the transport block size using the number of layers and the total number of allocated PRBs before rate matching.
  • a transport block may be composed of one or more code block groups (CBGs), and one CBG may be composed of one or more code blocks (CBs).
  • CBGs code block groups
  • CBs code blocks
  • ACK/NACK transmission and retransmission in units of CB/CBG may also be possible.
  • the UE may receive information on CB/CBG from the base station through DCI (e.g. DCI format 0_1, DCI format 1_1, etc.).
  • the UE may receive information on a data transmission unit (e.g. TB / CB / CBG) from the base station.
  • the base station schedules uplink transmission such as a frequency/time resource, a transport layer, an uplink precoder, and MCS (S801).
  • the base station may determine a beam for PUSCH transmission by the terminal through the beam management operations described above.
  • the UE receives a DCI for uplink scheduling (ie, including scheduling information of PUSCH) from the base station on the PDCCH (S802).
  • DCI format 0_0 or 0_1 may be used for uplink scheduling, and in particular, DCI format 0_1 includes the following information: DCI format identifier (Identifier for DCI formats), UL/SUL (Supplementary uplink) indicator (UL/ SUL indicator), bandwidth part indicator, frequency domain resource assignment, time domain resource assignment, frequency hopping flag, modulation and coding scheme (MCS) : Modulation and coding scheme), SRS resource indicator (SRI), precoding information and number of layers, antenna port(s) (Antenna port(s)), SRS request (SRS request), DMRS sequence initialization, UL-SCH (Uplink Shared Channel) indicator (UL-SCH indicator)
  • SRS resources set in the SRS resource set associated with the upper layer parameter'usage' may be indicated by the SRS resource indicator field.
  • SRS resource indicator field may indicate SRS resource indicator field.
  • patialRelationInfo' can be set for each SRS resource, and its value can be one of ⁇ CRI, SSB, SRI ⁇ .
  • the terminal transmits uplink data to the base station on the PUSCH (S803).
  • the UE detects a PDCCH including DCI format 0_0 or 0_1, it transmits a corresponding PUSCH according to an indication by the corresponding DCI.
  • codebook-based transmission For PUSCH transmission, two transmission methods are supported: codebook-based transmission and non-codebook-based transmission.
  • codebook-based transmission when the upper layer parameter'txConfig' is set to'codebook', the terminal is set to codebook-based transmission. On the other hand, when the upper layer parameter'txConfig' is set to'nonCodebook', the terminal is set to non-codebook based transmission. If the upper layer parameter'txConfig' is not set, the UE does not expect to be scheduled according to DCI format 0_1. When PUSCH is scheduled according to DCI format 0_0, PUSCH transmission is based on a single antenna port. In the case of codebook-based transmission, the PUSCH may be scheduled in DCI format 0_0, DCI format 0_1, or semi-statically.
  • the UE transmits PUSCH based on SRI, Transmit Precoding Matrix Indicator (TPMI) and transmission rank from DCI, as given by the SRS resource indicator field and the Precoding information and number of layers field. Determine the precoder.
  • the TPMI is used to indicate the precoder to be applied across the antenna port, and corresponds to the SRS resource selected by the SRI when multiple SRS resources are configured.
  • the TPMI is used to indicate a precoder to be applied across the antenna port, and corresponds to the single SRS resource.
  • a transmission precoder is selected from an uplink codebook having the same number of antenna ports as the upper layer parameter'nrofSRS-Ports'.
  • the terminal is configured with at least one SRS resource.
  • the SRI indicated in slot n is associated with the most recent transmission of the SRS resource identified by the SRI, where the SRS resource precedes the PDCCH carrying the SRI (ie, slot n).
  • the PUSCH may be scheduled in DCI format 0_0, DCI format 0_1, or semi-statically.
  • the UE can determine the PUSCH precoder and transmission rank based on the wideband SRI, where the SRI is given by the SRS resource indicator in the DCI or by the upper layer parameter'srs-ResourceIndicator'. Is given.
  • the UE uses one or multiple SRS resources for SRS transmission, where the number of SRS resources may be set for simultaneous transmission within the same RB based on UE capability. Only one SRS port is configured for each SRS resource. Only one SRS resource may be set to the upper layer parameter'usage' set to'nonCodebook'.
  • the maximum number of SRS resources that can be configured for non-codebook-based uplink transmission is 4.
  • the SRI indicated in slot n is associated with the most recent transmission of the SRS resource identified by the SRI, where the SRS transmission precedes the PDCCH carrying the SRI (ie, slot n).
  • the antenna port is defined so that a channel carrying a symbol on an antenna port can be inferred from a channel carrying another symbol on the same antenna port.
  • the two antenna ports are QC/QCL (quasi co-located or quasi co-location). ) It can be said that it is in a relationship.
  • the channel characteristics are delay spread, Doppler spread, frequency/Doppler shift, average received power, and received timing/average delay) and Spatial RX parameter.
  • the Spatial Rx parameter means a spatial (receiving) channel characteristic parameter such as angle of arrival.
  • the UE may be configured as a list of up to M TCI-State configurations in the higher layer parameter PDSCH-Config in order to decode the PDSCH according to the detected PDCCH having DCI intended for the UE and a given serving cell.
  • the M depends on the UE capability.
  • Each TCI-State includes a parameter for setting a quasi co-location relationship between one or two DL reference signals and the DM-RS port of the PDSCH.
  • the Quasi co-location relationship is set with the higher layer parameter qcl-Type1 for the first DL RS and qcl-Type2 for the second DL RS (if set).
  • the QCL type is not the same regardless of whether the reference is the same DL RS or different DL RSs.
  • the quasi co-location type corresponding to each DL RS is given by the higher layer parameter qcl-Type of QCL-Info, and can take one of the following values:
  • the corresponding NZP CSI-RS antenna ports may indicate/set that a specific TRS and a specific SSB and a QCL are provided in a QCL-Type A perspective and a QCL-Type D perspective. have.
  • the UE receiving this indication/configuration receives the corresponding NZP CSI-RS using the Doppler and delay values measured in the QCL-TypeA TRS, and applies the reception beam used for QCL-TypeD SSB reception to the corresponding NZP CSI-RS reception. can do.
  • the UE may receive an activation command by MAC CE signaling used to map up to 8 TCI states to the codepoint of the DCI field'Transmission Configuration Indication'.
  • the UE is a list of up to M candidates (candidate) transmission configuration indication (Transmission Configuration Indication, TCI) states for at least QCL (Quasi Co-location) indication purposes You can receive RRC settings.
  • M may be 64.
  • Each TCI state can be set as one RS set.
  • Each ID of a DL RS for spatial QCL purpose (QCL Type D) in at least an RS set may refer to one of DL RS types such as SSB, P-CSI RS, SP-CSI RS, and A-CSI RS.
  • initialization/update of the ID of the DL RS(s) in the RS set used for spatial QCL purposes may be performed through at least explicit signaling.
  • the TCI-State IE is associated with one or two DL reference signals (RS) corresponding quasi co-location (QCL) types.
  • the TCI-State IE may include parameters such as bwp-Id/referencesignal/QCL type.
  • the bwp-Id parameter indicates the DL BWP where the RS is located, the cell parameter indicates the carrier where the RS is located, and the reference signal parameter is a reference antenna port (s) that is a source of quasi co-location for the target antenna port(s). ) Or a reference signal including it.
  • the target antenna port(s) may be CSI-RS, PDCCH DMRS, or PDSCH DMRS.
  • a corresponding TCI state ID may be indicated in NZP CSI-RS resource configuration information.
  • a TCI state ID may be indicated in each CORESET setting.
  • the TCI state ID may be indicated through DCI.
  • the channel state information-reference signal (CSI-RS) is time and/or frequency tracking, CSI calculation, and L1 (layer 1)-RSRP (reference signal received). power) is used for computation and mobility.
  • CSI computation is related to CSI acquisition (acquisition)
  • L1-RSRP computation is related to beam management (BM).
  • Channel state information collectively refers to information that can indicate the quality of a radio channel (or link) formed between a terminal and an antenna port.
  • FIG. 9 is a flowchart showing an example of a CSI-related procedure.
  • a terminal eg, user equipment, UE transmits configuration information related to CSI to a base station through radio resource control (RRC) signaling (eg: general Node B, gNB) (S910).
  • RRC radio resource control
  • the configuration information related to the CSI is CSI-IM (interference management) resource related information, CSI measurement configuration related information, CSI resource configuration related information, CSI-RS resource related information Alternatively, it may include at least one of information related to CSI report configuration.
  • CSI-IM interference management
  • the CSI-IM resource related information may include CSI-IM resource information, CSI-IM resource set information, and the like.
  • the CSI-IM resource set is identified by a CSI-IM resource set ID (identifier), and one resource set includes at least one CSI-IM resource.
  • Each CSI-IM resource is identified by a CSI-IM resource ID.
  • CSI resource configuration related information may be expressed as CSI-ResourceConfig IE.
  • CSI resource configuration related information defines a group including at least one of a non zero power (NZP) CSI-RS resource set, a CSI-IM resource set, or a CSI-SSB resource set. That is, the CSI resource configuration related information includes a CSI-RS resource set list, and the CSI-RS resource set list is at least one of the NZP CSI-RS resource set list, CSI-IM resource set list, or CSI-SSB resource set list It can contain one.
  • the CSI-RS resource set is identified by the CSI-RS resource set ID, and one resource set includes at least one CSI-RS resource. Each CSI-RS resource is identified by a CSI-RS resource ID.
  • Table 6 shows an example of the NZP CSI-RS resource set IE.
  • parameters indicating the use of CSI-RS for each NZP CSI-RS resource set eg, BM related'repetition' parameter, tracking related'trs-Info' parameter
  • BM related'repetition' parameter e.g., BM related'repetition' parameter, tracking related'trs-Info' parameter
  • the repetition parameter corresponding to the higher layer parameter corresponds to the'CSI-RS-ResourceRep' of the L1 parameter.
  • the CSI report configuration related information includes a reportConfigType parameter indicating a time domain behavior and a reportQuantity parameter indicating a CSI related quantity for reporting.
  • the time domain behavior may be periodic, aperiodic, or semi-persistent.
  • CSI report configuration related information may be expressed as CSI-ReportConfig IE, and Table 7 below shows an example of CSI-ReportConfig IE.
  • the UE measures CSI based on the configuration information related to the CSI (S920).
  • the CSI measurement may include (1) a CSI-RS reception process of the terminal (S921), and (2) a process of calculating CSI through the received CSI-RS (S922), and a detailed description thereof Will be described later.
  • RE (resource element) mapping of CSI-RS resources is set in the time and frequency domains by the higher layer parameter CSI-RS-ResourceMapping.
  • Table 8 shows an example of CSI-RS-ResourceMapping IE.
  • density (D) represents the density of CSI-RS resources measured in RE/port/PRB (physical resource block), and nrofPorts represents the number of antenna ports.
  • the terminal reports the measured CSI to the base station (S930).
  • the UE may omit the report.
  • the terminal may report to the base station.
  • the aperiodic TRS is triggered or the repetition is set.
  • the NR system supports more flexible and dynamic CSI measurement and reporting.
  • the CSI measurement may include a procedure for acquiring CSI by receiving a CSI-RS and computing the received CSI-RS.
  • aperiodic/semi-persistent/periodic CM channel measurement
  • IM interference measurement
  • CSI-IM a 4 port NZP CSI-RS RE pattern is used.
  • NR's CSI-IM-based IMR has a design similar to that of LTE's CSI-IM, and is set independently from ZP CSI-RS resources for PDSCH rate matching. And, in the NZP CSI-RS-based IMR, each port emulates an interference layer with a (preferred channel and) precoded NZP CSI-RS. This is for intra-cell interference measurement in the multi-user case, and mainly targets MU interference.
  • the base station transmits the precoded NZP CSI-RS to the terminal on each port of the configured NZP CSI-RS-based IMR.
  • the UE measures interference by assuming a channel / interference layer for each port in the resource set.
  • a number of resources are set in a set, and the base station or network indicates a subset of NZP CSI-RS resources for channel / interference measurement through DCI.
  • Each CSI resource setting'CSI-ResourceConfig' is (given by the higher layer parameter csi-RS-ResourceSetList) Contains the configuration for the CSI resource set.
  • CSI resource setting corresponds to CSI-RS-resourcesetlist.
  • S represents the number of the set CSI-RS resource set.
  • the configuration for the CSI resource set includes each CSI resource set including CSI-RS resources (consisting of NZP CSI-RS or CSI-IM) and SS/PBCH block (SSB) resources used for L1-RSRP computation. .
  • Each CSI resource setting is located in the DL BWP (bandwidth part) identified by the higher layer parameter bwp-id. And, all CSI resource settings linked to the CSI reporting setting have the same DL BWP.
  • the time domain behavior of the CSI-RS resource within the CSI resource setting included in the CSI-ResourceConfig IE is indicated by the higher layer parameter resourceType, and may be set to aperiodic, periodic or semi-persistent.
  • the number of set CSI-RS resource sets (S) is limited to '1'.
  • the set periodicity and slot offset are given in the numerology of the associated DL BWP, as given by the bwp-id.
  • the same time domain behavior is configured for CSI-ResourceConfig.
  • the same time domain behavior is configured for CSI-ResourceConfig.
  • CM channel measurement
  • IM interference measurement
  • a channel measurement resource may be an NZP CSI-RS for CSI acquisition
  • an interference measurement resource may be a CSI-IM and an NZP CSI-RS for IM.
  • CSI-IM (or ZP CSI-RS for IM) is mainly used for inter-cell interference measurement.
  • NZP CSI-RS for IM is mainly used for intra-cell interference measurement from multi-users.
  • the UE may assume that CSI-RS resource(s) for channel measurement and CSI-IM / NZP CSI-RS resource(s) for interference measurement configured for one CSI reporting are'QCL-TypeD' for each resource. .
  • resource setting can mean a list of resource sets.
  • each trigger state set using the higher layer parameter CSI-AperiodicTriggerState is one or more CSI-ReportConfig and each CSI-ReportConfig is linked to a periodic, semi-persistent or aperiodic resource setting.
  • One reporting setting can be connected with up to three resource settings.
  • the resource setting (given by higher layer parameter resourcesForChannelMeasurement) is for channel measurement for L1-RSRP computation.
  • the first resource setting (given by higher layer parameter resourcesForChannelMeasurement) is for channel measurement, and the second resource (given by csi-IM-ResourcesForInterference or nzp-CSI-RS -ResourcesForInterference)
  • the setting is for interference measurement performed on CSI-IM or NZP CSI-RS.
  • the first resource setting (given by resourcesForChannelMeasurement) is for channel measurement
  • the second resource setting (given by csi-IM-ResourcesForInterference) is for CSI-IM-based interference measurement
  • the third resource setting (given by nzp-CSI-RS-ResourcesForInterference) is for NZP CSI-RS based interference measurement.
  • each CSI-ReportConfig is linked to a periodic or semi-persistent resource setting.
  • the resource setting is for channel measurement for L1-RSRP computation.
  • the first resource setting (given by resourcesForChannelMeasurement) is for channel measurement
  • the second resource setting (given by higher layer parameter csi-IM-ResourcesForInterference) is performed on CSI-IM. It is used for interference measurement.
  • each CSI-RS resource for channel measurement is associated with each CSI-IM resource and resource according to the order of CSI-RS resources and CSI-IM resources within the corresponding resource set. .
  • the number of CSI-RS resources for channel measurement is the same as the number of CSI-IM resources.
  • the UE when interference measurement is performed in the NZP CSI-RS, the UE does not expect to be set as one or more NZP CSI-RS resources in the associated resource set within the resource setting for channel measurement.
  • the UE in which the higher layer parameter nzp-CSI-RS-ResourcesForInterference is configured does not expect 18 or more NZP CSI-RS ports to be configured in the NZP CSI-RS resource set.
  • the UE assumes the following.
  • Each NZP CSI-RS port configured for interference measurement corresponds to an interfering transport layer.
  • time and frequency resources that can be used by the UE are controlled by the base station.
  • Channel state information is a channel quality indicator (CQI), a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), an SS/PBCH block resource indicator (SSBRI), a layer It may include at least one of indicator (LI), rank indicator (RI), or L1-RSRP.
  • CQI channel quality indicator
  • PMI precoding matrix indicator
  • CRI CSI-RS resource indicator
  • SSBRI SS/PBCH block resource indicator
  • LI indicator
  • RI rank indicator
  • L1-RSRP L1-RSRP
  • the terminal CSI-ReportConfig reporting setting It is set by a higher layer with a CSI-ResourceConfig resource setting and a list of one or two trigger states (provided by aperiodicTriggerStateList and semiPersistentOnPUSCH-TriggerStateList).
  • aperiodicTriggerStateList each trigger state includes a channel and an associated CSI-ReportConfigs list indicating selectively interference resource set IDs.
  • each trigger state contains one associated CSI-ReportConfig.
  • time domain behavior of CSI reporting supports periodic, semi-persistent, and aperiodic.
  • Periodic CSI reporting period (periodicity) and slot offset (slot offset) may be set to RRC, refer to CSI-ReportConfig IE.
  • SP Semi-periodic
  • period and slot offset are set to RRC, and CSI reporting is activated/deactivated by separate MAC CE/DCI.
  • SP CSI on PUSCH the periodicity of SP CSI reporting is set to RRC, but the slot offset is not set to RRC, and SP CSI reporting is activated/deactivated by DCI (format 0_1).
  • DCI format 0_1
  • SP-CSI C-RNTI a separate RNTI
  • the initial CSI reporting timing follows a PUSCH time domain allocation value indicated by DCI, and the subsequent CSI reporting timing follows a period set by RRC.
  • DCI format 0_1 includes a CSI request field, and may activate/deactivation a specific configured SP-CSI trigger state.
  • SP CSI reporting has the same or similar activation/deactivation as a mechanism with data transmission on the SPS PUSCH.
  • aperiodic CSI reporting is performed on PUSCH and is triggered by DCI.
  • information related to the trigger of aperiodic CSI reporting may be transmitted/instructed/configured through MAC-CE.
  • AP CSI-RS timing is set by RRC, and timing for AP CSI reporting is dynamically controlled by DCI.
  • a method of dividing and reporting CSI in a plurality of reporting instances that were applied to PUCCH-based CSI reporting in LTE (eg, transmission in the order of RI, WB PMI/CQI, and SB PMI/CQI) is not applied. Instead, the NR limits the setting of a specific CSI report in the short/long PUCCH, and a CSI omission rule is defined.
  • the PUSCH symbol/slot location is dynamically indicated by DCI.
  • candidate slot offsets are set by RRC.
  • a slot offset (Y) is set for each reporting setting.
  • slot offset K2 is set separately.
  • Two CSI latency classes are defined in terms of CSI computation complexity.
  • low latency CSI it is a WB CSI including a maximum of 4 ports Type-I codebook or a maximum of 4-ports non-PMI feedback CSI.
  • High latency CSI refers to CSI other than low latency CSI.
  • Z, Z' is defined in the unit of OFDM symbols.
  • Z represents the minimum CSI processing time until CSI reporting is performed after receiving the Aperiodic CSI triggering DCI.
  • Z' represents the minimum CSI processing time until CSI reporting is performed after receiving the CSI-RS for channel/interference.
  • the UE reports the number of CSIs that can be simultaneously calculated.
  • HARQ in NR may have the following characteristics.
  • 1) HARQ-ACK feedback of 1 bit per TB (transport block) may be supported.
  • the operation of one DL HARQ process is supported for some UEs, while the operation of one or more DL HARQ processes is supported for a given UE.
  • the UE may support a set of minimum HARQ processing time.
  • the minimum HARQ processing time means the minimum time required by the UE from the reception of DL data from the base station to the corresponding HARQ-ACK transmission timing.
  • two terminal processing times (N1 and K1) may be defined according to (1) symbol granularity and (2) slot granularity.
  • N1 represents the number of OFDM symbols required for terminal processing from the end of PDSCH reception to the earliest possible start of corresponding HARQ-ACK transmission.
  • the N1 may be defined as shown in Tables 9 and 10 below according to OFDM numerology (ie, subcarrier spacing) and DMRS pattern.
  • K1 may represent the number of slots from the slot of the PDSCH to the slot of the corresponding HARQ-ACK transmission.
  • 10 is a diagram showing an example of HARQ-ACK timing (K1).
  • K0 represents the number of slots from a slot with a DL grant PDCCH to a slot with a corresponding PDSCH transmission
  • K2 represents the number of slots from a slot with a UL grant PDCCH to a slot with a corresponding PUSCH transmission.
  • Show. That is, KO, K1, K2 can be briefly summarized as shown in Table 11 below.
  • the slot timing between A and B is indicated by the field of DCI from the set of values.
  • NR supports different minimum HARQ processing times between terminals.
  • the HARQ processing time includes a delay between a DL data reception timing and a corresponding HARQ-ACK transmission timing, and a delay between a UL grant reception timing and a corresponding UL data transmission timing.
  • the terminal transmits its minimum HARQ processing time capability to the base station.
  • Asynchronous and adaptive DL HARQ is supported at least in enhanced mobile broadband (eMBB) and ultra-reliable low latency (URLLC).
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable low latency
  • HARQ ACK / NACK feedback for multiple DL transmissions in the time domain may be transmitted in one UL data / control domain.
  • the timing between DL data reception and the corresponding acknowledgment is indicated by a field in the DCI from a set of values, the set of values being set by the upper layer. The timing is defined for at least
  • CoMP Coordinated Multi Point
  • the technique of CoMP is by cooperatively transmitting the terminal by exchanging (eg, using X2 interface) or utilizing channel information (eg, RI/CQI/PMI/LI, etc.) received from the terminal by a plurality of base stations, It refers to a method of effectively controlling interference.
  • it can be classified into joint transmission (JT), coordinated scheduling (CS), coordinated beamforming (CB), dynamic point selection (DPS), dynamic point blacking (DPB), and the like.
  • Non-coherent joint transmission may mean cooperative transmission that does not consider interference (ie, does not have interference).
  • the NCJT may be a method in which the base station(s) transmit data to one terminal through multiple TRPs using the same time resource and frequency resource.
  • multiple TRPs of the base station(s) may be configured to transmit data to the terminal through different layers using different demodulation reference signal (DMRS) ports.
  • DMRS demodulation reference signal
  • the NCJT may correspond to a transmission scheme in which transmission of the MIMO layer(s) is performed from two or more TRPs without adaptive precoding between TRPs.
  • NCJT is a fully overlapped NCJT (fully overlapped NCJT) scheme in which time resources and frequency resources used for transmission by each base station (or TRP) are completely overlapped and time resources used by each base station (or TRP) for transmission and/or
  • the frequency resources may be partially overlapped in a partially overlapped NCJT (partially overlapped NCJT) method.
  • data of a first base station (eg, TRP 1) and data of a second base station (eg, TRP 2) are both transmitted in some time resources and/or frequency resources, and the remaining time resources and / Or only data of either the first base station or the second base station may be transmitted in the frequency resource.
  • the TRP delivers data scheduling information to the NCJT receiving terminal as DCI (Downlink Control Information).
  • DCI Downlink Control Information
  • the M-TRP (multiple TRP) transmission method is i) DCI with different TRPs. It can be divided into M-DCI (multiple DCI) based M-TRP transmission and ii) S-DCI (single DCI) based M-TRP transmission method in which one TRP transmits DCI.
  • the single DCI based MTRP method in which one representative TRP transmits data transmitted by itself and scheduling information for data transmitted by another TRP to one DCI, MTRP cooperatively transmits one common PDSCH and participates in cooperative transmission.
  • layers ie, different DMRS ports
  • MTRP transmits one PDSCH
  • each TRP transmits only some layers of multiple layers constituting one PDSCH. For example, when layer 4 data is transmitted, TRP 1 transmits layer 2 and TRP 2 transmits layer 2 to the UE.
  • DMRS port information may be indicated using a new DMRS table.
  • the MTRP transmits different DCIs and PDSCHs, respectively (the UE receives N DCIs and N PDSCHs from N TRPs), and the corresponding PDSCHs are transmitted by overlapping each other on frequency and time resources (some or all).
  • Corresponding PDSCHs are scrambling through different scrambling IDs, and corresponding DCIs may be transmitted through Coresets belonging to different Coreset groups.
  • whether a single DCI based MTRP scheme or a multiple DCI based MTRP scheme may be indicated to the UE through separate signaling.
  • PDSCH rate matching for CRS may be different according to whether a single DCI based MTRP scheme or a multiple DCI based MTRP scheme.
  • the base station described in the present specification may be a generic term for an object that transmits and receives data to and from a terminal.
  • the base station described herein may be a concept including one or more transmission points (TPs), one or more transmission and reception points (TRPs), and the like.
  • TPs transmission points
  • TRPs transmission and reception points
  • multiple TPs and/or multiple TRPs described herein may be included in one base station or included in multiple base stations.
  • the TP and/or TRP may include a panel of a base station, a transmission and reception unit, and the like.
  • TRP means an antenna array with one or more antenna elements available in a network located at a specific geographic location in a specific area. I can. In this specification, for convenience of explanation, it is described based on “TRP", but TRP is a base station, a transmission point (TP), a cell (eg, a macro cell / small cell / pico cell, etc.), an antenna array, or a panel. Can be understood/applied by being replaced with (panel).
  • the CORESET group ID described in this specification refers to an index / identification information (eg ID) / indicator, etc. for distinguishing CORESET set/associated (or, for each TRP/panel) for each TRP/panel. can do.
  • the CORESET group may be an index for identifying CORESET / identification information (e.g. ID) / a group / union of CORESET identified by the CORESET group ID.
  • the CORESET group ID may be specific index information defined in CORSET configuration.
  • the CORESET group may be set/indicated/defined by an index defined in the CORESET configuration for each CORESET.
  • the CORESET group ID may be set/indicated through higher layer signaling (e.g. RRC siganling) / L2 signaling (e.g. MAC-CE) / L1 signaling (e.g. DCI).
  • the upper layer parameter ControlResourceSet IE (information element) is used to set a time/frequency control resource set (CORESET).
  • the control resource set may be related to detection and reception of downlink control information.
  • the ControlResourceSet IE may include a CORESET related ID (eg, controlResourceSetID), an index of a CORESET pool for CORESET (eg, CORESETPoolIndex), a time/frequency resource setting of CORESET, and TCI information related to CORESET.
  • the index of the CORESET pool (eg, CORESETPoolIndex) may be set to 0 or 1.
  • it may be set/instructed to perform PDCCH detection for each TRP/panel in a corresponding CORESET group unit.
  • And/or uplink control information eg CSI, HARQ-A/N, SR
  • uplink physical channel resources eg PUCCH/PRACH/SRS resources
  • HARQ A/N process/retransmission
  • PDSCH/PUSCH, etc. scheduled for each TRP/panel in a corresponding CORESET group unit may be managed.
  • the M-TRP transmission method in which a plurality of (e.g., M) TRPs transmit data to one terminal (user equipment, UE) is a method for greatly increasing the transmission rate, eMBB M-TRP (or M-TRP eMMB) transmission And URLLC M-TRP (or M-TRP URLLC) transmission, which is a method for increasing the reception success rate and reducing latency.
  • the URLLC M-TRP may mean that the M-TRP transmits the same TB (Transport Block) using different resources (eg, layer/time resource/frequency resource, etc.).
  • the UE configured with the URLLC M-TRP transmission scheme may be instructed by several TCI state(s) by DCI, and data received using the QCL reference signal (RS) of each TCI state may be assumed to be the same TB.
  • RS QCL reference signal
  • eMBB M-TRP may mean that the M-TRP transmits different TBs using different resources (eg, layer/time resource/frequency resource, etc.).
  • the UE configured with the eMBB M-TRP transmission scheme may be instructed by several TCI state(s) by DCI, and data received using the QCL RS of each TCI state may be assumed to be different TBs.
  • each TCI code point in the DCI may correspond to 1 or 2 TCI states.
  • each TCI state may correspond to one CDM group for at least DMRS type 1.
  • the UE may determine/determine whether the corresponding M-TRP transmission is URLLC transmission or eMBB transmission by separately using the RNTI set for MTRP-URLLC and the RNTI set for MTRP-eMBB. That is, if the CRC masking of the DCI received by the UE is performed using an RNTI set for MTRP-URLLC, this corresponds to URLLC transmission, and if the CRC masking of DCI is performed using an RNTI set for MTRP-URLLC May correspond to eMBB transmission.
  • Table 12 shows various schemes that can be considered for URLLC M-TRP transmission. Referring to Table 12, there are various schemes of SDM/FDM/TDM schemes.
  • 11 is an example of a transmission/reception method for improving reliability supported by a plurality of TRPs, and the following two methods may be considered.
  • FIG. 11A shows a case in which layer groups transmitting the same codeword (CW)/transport block (TB) correspond to different TRPs. That is, the same CW may be transmitted through different layers/layer groups.
  • the layer group may mean a kind of layer set consisting of one or more layers.
  • the number of layers increases, the amount of transmission resources increases, and there is an advantage in that robust channel coding with a low code rate can be used for TB.
  • channels are different from a plurality of TRPs, it is possible to expect an improvement in the reliability of a received signal based on a diversity gain.
  • FIG. 11B shows an example in which different CWs are transmitted through layer groups corresponding to different TRPs. That is, different CWs may be transmitted through different layers/layer groups.
  • TBs corresponding to the first CW (CW #1) and the second CW (CW #2) are the same. Therefore, it can be seen as an example of repeated transmission of the same TB.
  • the code rate corresponding to the TB may be high compared to (a) of FIG.
  • it has the advantage of being able to adjust a code rate by indicating different redundancy version (RV) values for encoding bits generated from the same TB according to a channel environment, or to adjust a modulation order of each CW.
  • RV redundancy version
  • the same TB is repeatedly transmitted through different layer groups and each layer group is transmitted by different TRP/panels, thereby increasing the data reception probability.
  • Layer(s) belonging to different layer groups are transmitted through DMRS ports belonging to different DMRS CDM groups, respectively.
  • the above-described multiple TRP-related content includes not only a spatial division multiplexing (SDM) method using different layers, but also a frequency division multiplexing (FDM) method based on different frequency domain resources (eg, RB/PRB (set)), and Of course, it can be extended and applied to a time division multiplexing (TDM) method based on / or different time domain resources (eg, slot, symbol, sub-symbol).
  • SDM spatial division multiplexing
  • FDM frequency division multiplexing
  • TDM time division multiplexing
  • proposal 1 proposes a method of configuring a HARQ-ACK codebook for multi-TRP transmission and a method of determining a resource for transmitting HARQ-ACK information.
  • Proposal 2 proposes a method of determining a specific index allocated to CORESET when a specific index corresponding to CORESET (eg, CORESET group ID, CORESETPoolIndex, etc.) is not set.
  • Proposal 3 proposes a method of extending the compressed quasi-static HARQ-ACK codebook generation method to multi-TRP.
  • Proposal 4 proposes a method for transmitting a HARQ-ACK codebook to a PUSCH in consideration of multi-TRP transmission (a method for multiplexing a HARQ-ACK codebook and a PUSCH).
  • each TRP may be classified based on the index of the CORESET pool (eg, CORESETPoolIndex) (or CORESET group ID) set in the CORESET.
  • CORESETPoolIndex or CORESET group ID
  • the methods described herein are described based on one or more TP/TRPs of the base station(s), but the methods may be applied in the same or similar manner to transmission based on one or more panels of the base station(s). Of course.
  • the NR standard supports two types, namely, a Type-1 HARQ-ACK codebook and a Type-2 HARQ-ACK codebook.
  • a Type-1 HARQ-ACK codebook and a Type-2 HARQ-ACK codebook.
  • Each codebook method is summarized below.
  • a Type-1 HARQ-ACK codebook one or more candidate PDSCHs capable of transmitting HARQ-ACK information to PUCCH/PUSCH to be transmitted in a specific slot (eg, n-th slot (slot #n)) are received (candidate PDSCH reception)) defines a HARQ-ACK codebook (ie, a set of HARQ information bits). Even when actual PDSCH transmission is not performed, bit(s) for corresponding PDSCH reception may be defined in the HARQ-ACK codebook. When the UE recognizes that PDSCH transmission is not performed (including a case in which PDSCH detection fails), it is defined to transmit NACK.
  • HARQ-ACK information in 1 bit or 2 bits according to the value of "maxNrofCodeWordsScheduledByDCI", which is an upper layer parameter indicating the maximum number of codewords (CW) for a single opportunity for a candidate PDSCH reception Can be configured.
  • “harq-ACK-SpatialBundlingPUCCH” is set to the terminal, HARQ-ACK information may be configured with 1 bit.
  • the UE when there is an occasion of receiving a candidate PDSCH in response to a PDCCH having DCI format 1_1, and "maxNrofCodeWordsScheduledByDCI" instructs reception of 2 transport blocks, the UE receives a PDSCH including one transport block Then, i) if "harq-ACK-SpatialBundlingPUCCH” is not set, the UE generates HARQ-ACK information associated with the first transport block and NACK for the second transport block, and ii) if "harq-ACK-SpatialBundlingPUCCH" is set, HARQ-Ack information can be generated as an ACK for the second transport block.
  • HARQ-ACK information is included in the same PUCCH/PUSCH based on counter downlink assignment indicator (DAI) (C-DAI) and total DAI (T-DAI) values indicated in the actually transmitted PDCCH.
  • DAI counter downlink assignment indicator
  • T-DAI total DAI
  • a codebook is configured based on PDCCH information transmitted to an actual terminal.
  • the UE fails to detect a specific PDCCH, it transmits a NACK to a bit for a corresponding PDCCH among bits defined in the codebook. At this time, whether the PDCCH detection has failed may be recognized by the UE through the C-DAI and T-DAI values.
  • the value of the C-DAI field in the DCI foramt is the cumulative number of ⁇ serving cell, PDCCH monitoring occasion ⁇ -pair(s) of PDSCH reception or SPS PDSCH release associated with the DCI format that exists up to the current serving cell and the current PDCCH monitoring opportunity ( accumulative number).
  • the serving cell index follows in ascending order, followed by the PDCCH monitoring opportunity in ascending order.
  • the value of T-DAI in the DCI format represents the total number of ⁇ serving cell, PDCCH monitoring occasion ⁇ -pair(s) of PDSCH reception or SPS PDSCH release associated with the DCI format that exists up to the current PDCCH monitoring opportunity. .
  • a joint (joint) HARQ-ACK codebook and (ii) a separated (individual) HARQ-ACK codebook scheme may be considered.
  • the joint (joint) HARQ-ACK codebook may refer to a method of configuring each HARQ-ACK information for different TRPs into one codebook. This method can increase resource utilization because it can reduce the TDM PUCCH resource in the intra/inter slot.
  • CORESETPoolIndex some kind of index that can mean different TRPs can be set for each CORESET, and the terminal corresponds to different TRPs when different indexes are set for different CORESETs.
  • the terminal indicates that each of the first CORESET and the second CORESET corresponds to a different TRP (i.e., multiple TRP operation) Can be assumed.
  • HARQ-ACK information for each PDSCH scheduled by different PDCCHs received through CORESET corresponding to different TRPs is the same uplink resource corresponding to a specific TRP. It may be transmitted through a specific TRP (eg, PUCCH, PUSCH, etc.).
  • the separated (individual) HARQ-ACK codebook may refer to a method of configuring HARQ-ACK information for different TRPs into different codebooks. This method can prevent a problem in which all HARQ-ACK information (ie, ACK/NACK information) is lost due to a failure in joint HARQ-ACK codebook transmission in an environment with a blockage probability.
  • CORESETPoolIndex some kind of index that can mean different TRPs can be set for each CORESET, and the terminal corresponds to different TRPs when different indexes are set for different CORESETs.
  • the terminal indicates that each of the first CORESET and the second CORESET corresponds to a different TRP (i.e., multiple TRP operation) Can be assumed.
  • HARQ-ACK information for each PDSCH scheduled by different PDCCHs received through CORESET corresponding to different TRPs is different from each other corresponding to different TRPs. It may be transmitted to each TRP through link resources (eg, PUCCH, PUSCH, etc.).
  • link resources eg, PUCCH, PUSCH, etc.
  • 12 shows an example of a method of generating a HARQ-ACK codebook for multi-TRP (eg, TRP1, TRP2).
  • 12(a) shows a joint HARQ-ACK codebook method
  • FIG. 12(b) shows a separated HARQ-ACK codebook method.
  • a semi-static codebook or a Type-1 HARQ-ACK codebook
  • the HARQ-ACK codebook configuration as described above may be considered.
  • HARQ-ACK information for PDSCH1 from TRP1 and PDSCH2 from TRP2 is configured as one codebook and specified using the same (ie one) PUCCH. It can be transmitted by TRP (eg, TRP1).
  • TRP eg, TRP1
  • HARQ-ACK information for PDSCH1 is configured as one codebook and transmitted to TRP1 using one PUCCH
  • HARQ-ACK information for PDSCH2 is It can be configured as another codebook and transmitted to TRP2 using another PUCCH.
  • the joint HARQ-ACK codebook may have a size that is more than twice as large as that of the existing HARQ-ACK codebook.
  • this ie, a codebook having an increased size compared to the existing HARQ-Ack codebook
  • HARQ-ACK information corresponding to each bit in the extended codebook may be defined as a specific rule.
  • a reference payload size may be based on the size of the extended codebook.
  • the codebook may be defined to be twice the size of the existing HARQ-ACK codebook.
  • the two codebooks are concatenated.
  • a joint HARQ-ACK codebook of twice the size can be configured.
  • the base station may dynamically configure a specific codebook scheme (ie, a joint HARQ-ACK codebook or a separate HARQ-ACK codebook) to the terminal or semi-statically.
  • a specific codebook scheme ie, a joint HARQ-ACK codebook or a separate HARQ-ACK codebook
  • a method of defining a new field in DCI may be considered. Joint HARQ-ACK codebook operation or separated HARQ-ACK codebook operation may be indicated/configured to the terminal through the field.
  • a 1-bit field can be defined in DCI.
  • the terminal may perform a separated HARQ-ACK codebook method, and when 1 is indicated/set, the terminal may perform a joint HARQ-ACK codebook method.
  • the terminal may perform a joint HARQ-ACK codebook method, and when 1 is indicated/set, the terminal may perform a separated HARQ-ACK codebook method.
  • the field within the DCI for setting/instructing the specific codebook scheme may be included in all DCIs for scheduling a PDSCH to the UE, or may be included only in a specific DCI.
  • the method of using the 1-bit field (ie, 0 or 1) described above is an example for convenience of description and does not limit the technical scope of the present invention. Therefore, even when setting/instructing a joint HARQ-ACK codebook and a separated HARQ-ACK codebook using an N-bit field (here, N is a natural number), that is, two or more states in the methods described below Of course, it can be extended and applied.
  • the terminal can configure a codebook that is distinguished from each other according to a specific rule.
  • a specific index value within a certain range may be set in each CORESET, and scheduled by PDCCH(s) detected in CORESET having the same index (eg CORESET group ID, HARQ codebook group ID).
  • Each codebook can be configured for each ACK/NACK(s) of PDSCH(s).
  • HARQ-ACK information of a PDSCH scheduled by a PDCCH detected in a CORESET having the same CORESETPoolIndex may be configured as a HARQ-ACK codebook for each CORESETPoolIndex.
  • the terminal When the terminal is configured/instructed to a joint HARQ-ACK codebook scheme (eg, a 1-bit field is set to 1), the terminal may configure HARQ-ACK information into one codebook.
  • configuring as one codebook means configuring HARQ-ACK information for PDSCH(s) transmitted in different TRPs as one codebook and using the same (ie one) PUCCH resource to the base station (eg PDSCH(s) It may mean transmitting (to one of the transmitted TRPs).
  • different TRPs may be classified based on different CORESETPoolIndex, and when CORESETs having different CORESETPoolIndex values are set, the UE may recognize that the multiple TRP operation is performed.
  • different TRPs may be represented as a situation in which different indices (e.g. CORESET group ID, CORESETPoolIndex, HARQ codebook group ID) are mapped to CORESET.
  • the PDCCH scheduling the PDSCH can be configured as one HARQ-ACK codebook for different types of indexes (eg CORESET group ID, CORESETPoolIndex, HARQ codebook group ID) set in the transmitted CORESET. have.
  • a specific codebook scheme (eg, a joint HARQ-ACK codebook operation or a separated HARQ-ACK codebook operation) may be set/instructed implicitly using a field in the existing DCI.
  • a specific codebook scheme eg, a joint HARQ-ACK codebook operation or a separated HARQ-ACK codebook operation
  • a method of using a PUCCH resource indicator (PRI) field in DCI may be considered.
  • the PRI field can be used for indicating an uplink resource for feedback of HARQ-ACK information. This is because it can be interpreted as an implicit indication to use the same resource when the same PRI value is indicated to the terminal in different TRPs. It can be seen that it is suitable for the proposed method.
  • a joint HARQ-ACK codebook is configured for each PDSCH, and if the PRI is different, an index set in CORESET (eg CORESET group ID, CORESETPoolIndex, HARQ codebook group ID) separated HARQ-ACK codebook can be configured.
  • CORESET eg CORESET group ID, CORESETPoolIndex, HARQ codebook group ID
  • the UE may recognize that the same PUCCH resource is indicated in different TRPs, and this is a joint HARQ-ACK using the same PUCCH resource. It can be interpreted to mean to send a codebook.
  • Example 2-1 when the terminal fails to receive a specific PDCCH among a plurality of PDCCHs, the base station instructs the joint HARQ-ACK codebook, but it is interpreted that the terminal has instructed the separated HARQ-ACK codebook.
  • PUCCH transmission can be performed.
  • Example 2-2 the same method as in Example 2-2 below may be considered.
  • the PRI field in the DCI is used, but by setting a range of values indicated through the PRI field, the PRI value(s) indicated to the terminal through different PDCCHs are included within a specific range.
  • a joint HARQ-ACK codebook may be configured, and a separated HARQ-ACK codebook may be configured when exceeding the specific range (ie, when the value is outside the specific range).
  • a specific range of the PRI value that can indicate the joint HARQ-ACK codebook is set such as 000 to 011.
  • the terminal may recognize that the joint HARQ-ACK codebook is indicated, whereas 100, 101, 110, 111 not included in the range.
  • the separated HARQ-ACK codebook is indicated.
  • the PRI value is within a specific range by receiving PDCCH #1.
  • a joint HARQ-ACK codebook can be configured.
  • the specific range of the PRI value that can indicate the joint HARQ-ACK codebook is defined as a fixed rule between the base station and the terminal, or information on the specific range (ie, a specific value) is transmitted through higher layer signaling. It can be set/delivered to the terminal.
  • a separated ACK/NACK codebook or a joint ACK/NACK codebook configuration may be set/instructed using a reserved value of the DCI field for DMRS port indication.
  • a separated ACK/NACK codebook or a joint ACK/NACK codebook configuration can be set/indicated by indicating a specific combination using a plurality of previously defined DCI fields. For example, the above operation may be performed using a specific combination of a DCI field for DMRS port indication and a DCI field for TB information indication (i.e., MCS, NDI, RV).
  • different DCIs may be transmitted to the terminal in different TRPs performing multi-TRP transmission (eg, the above-described multiple DCI based MTRP scheme). It is assumed that one of the joint HARQ-ACK codebook or the separated HARQ-ACK codebook is indicated/configured based on the method described in the embodiments of proposal 1.
  • a resource through which a PUCCH including HARQ-ACK information is transmitted may be determined as follows.
  • the order may be defined according to the time when the DCI was transmitted/ the index (eg CORESET group ID, CORESETPoolIndex, HARQ codebook group ID) set in the CORESET to which the DCI was transmitted.At this time, based on a specific order, for example, in time order It is transmitted in the latest slot, and when the slots are the same, it can be defined to use the DCI with the lowest (or largest) index set in CORESET and the PUCCH resource indicated by a specific DCI.
  • the index eg CORESET group ID, CORESETPoolIndex, HARQ codebook group ID
  • the UE When the UE calculates the PUCCH resource, it first determines the PUCCH resource set.As described above, in the case of the joint HARQ-ACK codebook, two compared to the existing HARQ-ACK codebook in consideration of different PDSCH transmissions overlapping in the time domain. A size larger than twice may be considered, and the final PUCCH resource may be finally determined through the PRI value indicated through the corresponding DCI.
  • a resource through which a PUCCH including HARQ-ACK information is transmitted may be determined as follows.
  • the time at which the DCI is transmitted/ the index set in the CORESET in which the DCI is transmitted e.g. CORESET group ID, CORESETPoolIndex, HARQ codebook group ID), etc. may be a reference.
  • PUCCH resources indicated by the DCI transmitted in the latest slot in time order are used, and at this time, the last DCI to determine the PUCCH resource may be determined for each index set in CORESET.
  • the PUCCH resource set is first determined. In this case, the size of the payload that does not take into account the transmission of different PDSCHs overlapping in the time domain may be considered, and finally, through the corresponding DCI. The final PUCCH resource may be determined through the indicated PRI value.
  • the index set in CORESET e.g., CORESETPoolIndex
  • the index set in CORESET e.g., CORESETPoolIndex
  • Transmission for a specific resource eg, a resource indicated/indicated through DCI detected in a CORESET corresponding to a smaller or larger index
  • One of a joint HARQ-ACK codebook or a separated HARQ-ACK codebook may be indicated/determined according to whether PUCCH resources indicated by different PDCCHs scheduling each PDSCH are identical.
  • the same PUCCH resources may mean that parameters for PUCCH transmission such as time/frequency resources and/or PUCCH format for PUCCH transmission are the same.
  • the same time/frequency resource may mean that one of a time resource, a frequency resource, or a time and frequency resource is the same.
  • the UE may calculate (or determine) a PUCCH resource indicated by each PDCCH after assuming a joint HARQ-ACK codebook. Thereafter, when PUCCH resources indicated by different PDCCHs scheduling each PDSCH are the same, the UE may configure HARQ-ACK information for PDSCHs scheduled by different PDCCHs as a joint HARQ-ACK codebook. have.
  • the UE sets the HARQ-ACK information for the PDSCHs scheduled by the different PDCCHs in the CORESET index (eg CORESET group).
  • ID HARQ codebook group ID
  • the PUCCH resource for transmitting each codebook may be recalculated (or determined) (by the terminal) on the assumption of a separated HARQ-ACK codebook.
  • the payload size when determining the PUCCH resource set, the payload size may be based on the size of the aforementioned'extended codebook'.
  • PUCCH resources when PUCCH resources are calculated again by assuming a separated HARQ-ACK codebook because PUCCH resources indicated from different PDCCHs are different, it may be based on the existing codebook size, that is, the existing codebook size before the expansion.
  • a method of semi-fixedly setting a joint HARQ-ACK codebook or a separated HARQ-ACK codebook according to a backhaul situation between TRPs may be considered.
  • a specific scheme among the joint HARQ-ACK codebook or the separated HARQ-ACK codebook may be configured in the terminal through a higher layer parameter (eg, a layer 1 (L1) parameter).
  • a specific HARQ-ACK codebook scheme may be configured/instructed based on a'PhysicalCellGroupConfig' field used to configure a cell-group specific L1 parameter.
  • a parameter eg, ackNackFeedbackMode
  • a joint HARQ-ACK codebook or a separated HARQ-ACK codebook may be indicated through the parameter.
  • the parameter may be set when there are a plurality of different CORESETPoolindexes in the ControlResourceSet.
  • the terminal configured in the joint HARQ-ACK codebook mode may consider a codebook having a size larger than that of the existing HARQ-ACK codebook in consideration of transmission of different PDSCHs overlapping in the time domain, and can be extended.
  • HARQ-ACK information corresponding to each bit in the codebook can be defined as a specific rule.
  • the codebook when the joint HARQ-ACK codebook is indicated/configured, the codebook may be defined to be twice the size of the existing HARQ-ACK codebook.
  • the double-sized joint HARQ-ACK codebook may be configured by configuring different codebooks in the order of an index (eg, CORESETPoolIndex) set in CORESET, and then concatenating the two codebooks.
  • an index eg, CORESETPoolIndex
  • a reference payload size may be based on the size of the extended codebook.
  • each HARQ-ACK codebook when a semi-fixedly separated HARQ-ACK codebook is set, PUCCH resources indicated by different DCIs received from CORESET corresponding to different indexes (eg, CORESETPoolIndex) are TDM (time domain multiplexing) within the same slot, or / And when transmitted in different slots, a separated HARQ-ACK codebook operation constituting each codebook for different indices may be performed. That is, each HARQ-ACK codebook can be configured for each CORESETPoolIndex.
  • each separated HARQ-ACK codebook corresponding to a different index It can be transmitted at the same time through other PUCCH resources.
  • PUCCH resources indicated by different DCIs received from CORESET corresponding to different indexes are TDM within the same slot or/and within the same slot
  • all HARQ-ACK information corresponding to different indices may be transmitted to the base station at one time through a specific PUCCH resource.
  • a specific index e.g., the lowest index or the lowest DCI corresponding to a specific cell (eg, a cell corresponding to the lowest cell ID or the highest cell ID) using the PUCCH resource indicated by the DCI received through the CORESET corresponding to the high (highest) index
  • a specific index e.g., the lowest index or the lowest DCI corresponding to a specific cell (eg, a cell corresponding to the lowest cell ID or the highest cell ID) using the PUCCH resource indicated by the DCI received through the CORESET corresponding to the high (highest) index
  • PUCCH resources may be determined according to a PUCCH resource indicator (PRI) field value indicated through a specific DCI.
  • the specific DCI may be the last DCI among received DCIs.
  • the terminal receives a different DCI from a CORESET corresponding to a different index (e.g. CORESETPoolIndex), i) the DCI is transmitted, ii) the index set in the CORESET to which the DCI is transmitted (eg CORESET group ID, CORESETPoolIndex ) And iii) the order of the DCI may be defined based on the cell index (or ID).
  • the time when the DCI is transmitted may mean an index of a monitoring opportunity related to a channel (eg, PDCCH) through which the DCI is transmitted.
  • PUCCH resources may be determined according to the PRI field value of a specific DCI determined based on the order of the DCI. For example, the order of the DCI is transmitted from the latest slot in chronological order within one cell, and if the slots in which the DCI is transmitted are the same (or if the DCI monitoring opportunity is the same), the DCI with the largest index set in CORESET It can be defined to use the PUCCH resource indicated by.
  • PUCCH resources for transmitting HARQ-ACK information through the PRI field of the last DCI among the received DCIs Can be determined.
  • the received DCIs are indexed in ascending order of the serving cell index for the same PDCCH monitoring occasion, and then may be indexed according to the index of the PDCCH monitoring opportunity.
  • DCIs in one serving cell within the same PDCCH monitoring opportunity may be indexed based on a specific index of CORESET (eg, CORESETPoolIndex).
  • the DCI received from CORESET may be indexed before the DCI received from CORESET where the value of CORESETPoolIndex is 1.
  • the last DCI may be determined according to the index order.
  • received at the second CORESET HARQ-ACK information can be transmitted using PUCCH resources indicated by the PRI field value of DCI.
  • the DCI PDSCHs scheduled by A may be transmitted to the base station through different PUCCH resources indicated through the corresponding DCI.
  • a specific index is set for each CORESET, and different HARQ-ACK codebooks are configured for each index.
  • a specific index set for each CORESET may mean a CORESET group ID (or index) associated with CORESET or an index of a CORESET pool.
  • HARQ-ACK information for a PDSCH scheduled by PDCCHs transmitted/received through a CORESET(s) in which index 1 is set is configured as one codebook, and transmitted through a CORESET(s) in which index 2 is set.
  • HARQ-ACK information for a PDSCH scheduled by PDCCHs may be configured as another codebook.
  • the method of using the index 1/2 described above is only an example for convenience of description, and does not limit the technical scope of the present invention. Therefore, in the methods described below, it can be extended and applied even when setting/instructing a joint HARQ-ACK codebook or a separated HARQ-ACK codebook using N or more indexes that can be set (or mapped) for CORESET. Yes, of course.
  • the above-described method should be applicable even when a number of cells (eg, Cell #1/Cell #2) are defined.
  • a number of cells eg, Cell #1/Cell #2
  • a single TRP or multi-TRP configuration is different for each cell.
  • only single TRP transmission may be considered in Cell #1
  • multi-TRP transmission may be considered in Cell #2.
  • different specific indexes may be set for each CORESET defined in Cell #2 to form a separated HARQ-ACK codebook, but in the case of Cell #1, since a single TRP is assumed, a separate specific index is provided for each CORESET. May not be set.
  • CORESET in a specific cell (eg Cell #1), CORESET can be identified through a specific index, but in another cell (eg, Cell #2), a specific index is not mapped to CORESET, so there is no standard for classifying CORESET. This can happen.
  • the HARQ-ACK codebook is configured from the viewpoint of the terminal, ambiguity occurs from the viewpoint of multiple cells.
  • a specific index (eg CORESET group ID, CORESETPoolIndex, HARQ codebook group ID) is mapped to a CORESET in a specific cell among a plurality of cells set to the terminal, and a CORESET is mapped to another specific cell. If the index does not exist, the terminal assumes that a specific index (eg, the lowest index or the highest index) among the indexes mapped to the CORESET defined in another cell is mapped for the CORESET where the mapped index does not exist. Can be defined/set.
  • Scell #1 Index 0-CORESET #0/ #1/ #2, Index 1-CORESET #3/ #4
  • Scell #2 CORESET #0/ #1/ #2/ #3/ #4 without index
  • Scell #4 Index 0-CORESET #0/ #1/ #2, Index 1-CORESET #3/ #4
  • Pcell, Scell #2, and Scell #3 represent that separate indexes are not mapped to CORESET assuming single TRP transmission.
  • Scell #1 and Scell #4 have a specific index mapped to each CORESET assuming multi-TRP transmission (e.g., index 0 is set for CORESET #0 to CORESET #2, and CORESET #3 and CORESET #4) , Index 1 is set).
  • index 0 is set for CORESET #0 to CORESET #2, and CORESET #3 and CORESET #4
  • Index 1 is set.
  • ambiguity may occur when configuring the HARQ-ACK codebook from the viewpoint of the UE.
  • the UE may assume that a specific index among the indexes mapped to CORESET defined in another cell is mapped to a CORESET in which the mapped index does not exist.
  • the UE may assume that index 0 (or index 1) is mapped to CORESET defined in Pcell, Scell #2, and Scell #3.
  • the UE may generate and transmit HARQ-ACK information for CORESET with a specific index of 0 or for CORESET with no index set and HARQ-ACK information for CORESET with an index of 1 corresponding to CORESET, respectively.
  • the terminal may generate a codebook corresponding to index 0 for Pcell/ Scell #1/ Scell #2/ Scell #3/ Scell #4, and Scell #1/ Scell # For 4, a codebook corresponding to index 1 can be generated.
  • the codebook may be configured according to an order based on a cell index (eg, Cell ID) and a PDSCH reception point.
  • the PDSCH reception point may mean a PDSCH monitoring opportunity. For example, it is possible to generate a codebook according to the order of the cell index first, and then according to the order of the PDSCH reception points (or according to the order of the PDSCH reception points, and then generate the codebook according to the order of the cell index. ).
  • the codebook corresponding to index 0 is PDSCH #1 on Pcell, PDSCH #1 on Scell #1, PDSCH #1 on Scell #2, PDSCH #1 on Scell #3, PDSCH #1 on Scell #4, PDSCH #2 on Pcell, PDSCH #2 on Scell #1, PDSCH #2 on Scell #2, PDSCH #2 on Scell #3, PDSCH #2 on Scell #4 in the order of HARQ-ACK information.
  • a codebook for can be constructed.
  • the codebook corresponding to index 1 is a codebook for HARQ-ACK information in the order of PDSCH #1 on Scell #1, PDSCH #1 on Scell #4, PDSCH #2 on Scell #1, and PDSCH #2 on Scell #4. This can be configured.
  • a general semi-static HARQ-ACK codebook (or Type-1 HARQ-ACK codebook) may be generated as follows.
  • the total number of possible PDSCH reception points (or candidates) for the serving cell c is denoted by M_c, and the total of M_c is denoted by M_A,c when all serving cells supporting the terminal are considered. Since the UE configures and feeds back HARQ-ACK information for all serving cells as one codebook, the UE may configure HARQ-ACK information for M_A,c PDSCH reception points as one codebook.
  • HARQ-ACK information for the corresponding reception point Is defined to transmit.
  • Type-1 HARQ-ACK codebook even when PDSCH transmission is not actually performed, bits must be transmitted for HARQ-ACK information for all available PDSCHs, thus increasing feedback overhead.
  • the total number of possible PDSCH reception points for Serving cell c is denoted by M_c
  • the total of M_c is denoted by M_A,c when all serving cells supporting the UE are considered.
  • the UE considers HARQ-ACK information for all M_A,c PDSCH reception points when configuring the HARQ-ACK codebook, but when receiving DCI format 1_0 having a counter DAI field value of 1 in PCell, M_A, Instead of feeding back HARQ-ACK information for all c reception points, only HARQ-ACK information for PDSCH reception scheduled by the DCI (i.e., DCI format 1_0 with a counter DAI field value of 1 in the PCell) can be fed back. .
  • the above-described method will be referred to as a'compressed quasi-static HARQ-ACK codebook generation method'. However, the use of these terms does not limit the technical scope of the present invention.
  • the above-described compressed quasi-static HARQ-ACK codebook generation method assumes a single TRP. Even in a multi-TRP situation, when generating a semi-static HARQ-ACK codebook (or Type-1 HARQ-ACK codebook), the payload is overloaded. In order to reduce the head, the compressed quasi-static HARQ-ACK codebook generation method may be used. Hereinafter, a detailed method for extending the compressed quasi-static HARQ-ACK codebook generation method to multi-TRP will be described.
  • a HARQ-ACK codebook can be independently configured according to a specific index (eg CORESET group ID, HARQ codebook group ID, CORESETPoolIndex) set (or mapped) to CORESET.
  • a specific index eg CORESET group ID, HARQ codebook group ID, CORESETPoolIndex
  • the terminal receives/detects DCI format 1_0 in which the counter DAI field value is 1 in the PCell, the terminal only applies to the HARQ-ACK codebook corresponding to a specific index set (or mapped) to the CORESET in which the corresponding DCI is detected.
  • a codebook can be configured according to a compressed quasi-static HARQ-ACK codebook generation method.
  • Proposal 3-1, Proposal 3-2, Proposal 4, Proposal 4-1, Proposal 4-2, etc. the same situation as the second example can be assumed. It is assumed that Pcell and Scell #1 to Scell #4 are set, and there are 5 CORESETs (ie, CORESET #0 to CORESET #4) for each cell.
  • CORESETPoolIndex a specific index set in CORESET (eg, CORESETPoolIndex) is described as being set to index 0 or index 1, but the method of using a specific number of indexes (eg, index 0 / 1) is an example for convenience of explanation.
  • Scell #1 Index 0-CORESET #0/ #1/ #2, Index 1-CORESET #3/ #4
  • Scell #4 Index 0-CORESET #0/ #1/ #2, Index 1-CORESET #3/ #4
  • Pcell, Scell #2 and Scell #3 represent an example in which the same index (eg, index 0) is mapped to all CORESETs assuming single TRP transmission.
  • Scell #1 and Scell #4 assume multi-TRP transmission and have different specific indexes for each CORESET (e.g., index 0 is set for CORESET #0 to CORESET #2, and indexes for CORESET #3 and CORESET #4) 1 shows an example in which setting) is mapped.
  • the UE when configuring the separated HARQ-ACK codebook, the UE can generate a codebook corresponding to index 0 for Pcell/ Scell #1/ Scell #2/ Scell #3/ Scell #4, and Scell #1 / For Scell #4, a codebook corresponding to index 1 can be generated. Each codebook may be transmitted through different PUCCH/PUSCH resources.
  • the terminal receives a DCI corresponding to'DCI format 1_0 in which the counter DAI field value is 1 in PCell' in the CORESET corresponding to a specific index, semi-static HARQ-ACK compressed only to the index mapped to the CORESET that succeeded in detecting the DCI Codebook generation method can be applied. That is, the UE may generate a codebook that transmits only HARQ-ACK information corresponding to the PDSCH scheduled by the DCI.
  • the terminal is index 0 (or index 1)
  • the compressed quasi-static HARQ-ACK codebook generation method can be applied only when generating a codebook corresponding to. That is, the UE may generate a codebook that transmits only HARQ-ACK information corresponding to the PDSCH scheduled by the DCI. For example, when a fall back DCI is received from a CORESET corresponding to index 0, HARQ-ACK for a PDSCH scheduled by a DCI detected from a CORESET corresponding to index 1 may not be transmitted.
  • the specific index may be defined as a fixed rule between the base station and the terminal, or information on the specific index may be configured/instructed to the terminal through signaling (eg, RRC, MAC-CE, DCI, etc.).
  • index 0 is set/instructed as the specific index.
  • the proposed operation is performed, and when the DCI is received in the CORESET corresponding to index 1
  • the suggested operation may not be performed. That is, even when the terminal receives a DCI that satisfies'DCI format 1_0 with a counter DAI field value of 1 in PCell' in CORESET corresponding to index 1, the terminal uses the above-described compressed semi-static HARQ-ACK codebook generation method.
  • Each HARQ-ACK codebook for the PDSCH scheduled by the detected DCI may be generated and transmitted through PUCCH resources indicated by the DCIs detected in each CORESET.
  • the proposed method for applying the above-described compressed quasi-static HARQ-ACK codebook generation method may be determined whether to operate based on DCI format 1_0 transmitted through the PCell.
  • whether to perform single TRP transmission or multi-TRP transmission may vary depending on the serving cell, and thus, the PCell may be configured/instructed to perform single TRP transmission.
  • a CORESET corresponding to a specific index may not be defined in the PCell.
  • index 0 is set for all CORESETs defined in the PCell. In this case, for index 1, there may be a problem that DCI format 1_0 is not received through the PCell.
  • a terminal receiving'DCI format 1_0 with counter DAI field value of 1'through a specific Scell among SCell(s) may configure a codebook according to a compressed quasi-static HARQ-ACK codebook generation method.
  • a specific Scell is predefined as a fixed rule (eg, Scell having the lowest/highest CC ID value) between the base station and the terminal, or the base station performs higher layer signaling (e.g., RRC, MAC It is possible to set a specific value to the terminal through -CE)/ DCI.
  • a fixed rule eg, Scell having the lowest/highest CC ID value
  • the base station performs higher layer signaling (e.g., RRC, MAC It is possible to set a specific value to the terminal through -CE)/ DCI.
  • the UE may configure the codebook according to the compressed semi-static HARQ-ACK codebook generation method.
  • the terminal when receiving DCI format 1_0 with counter DAI field value of 1 through SCell #1, which is the lowest SCell, the terminal is compressed semi-static HARQ-ACK when configuring the HARQ-ACK codebook corresponding to index 1.
  • a codebook can be configured according to a codebook generation method.
  • HARQ-ACK information for different TRPs may be configured as one HARQ-ACK codebook.
  • HARQ-ACK information corresponding to different indices may be configured as one HARQ-ACK codebook. I can.
  • the terminal detects DCI format 1_0 (DCI format 1_0 with counter DAI field value of 1 on the PCell) with a counter DAI field value of 1 in the PCell through a specific CORESET among CORESETs with different indexes set, the terminal A compressed semi-static HARQ-ACK codebook generation method is applied to the number of (sub-) codebooks corresponding to the number of indexes corresponding to the CORESET set to itself, and the joint HARQ-ACK codebook is connected by concatenating the (sub-) codebooks according to the index order. Configurable.
  • Proposal 3-2 will be described based on the second example described above.
  • the UE can generate a (sub-) codebook corresponding to index 0 for Pcell/ Scell #1/ Scell #2/ Scell #3/ Scell #4, and Scell #1/ For Scell #4, a (sub-) codebook corresponding to index 1 can be generated.
  • two (sub-) codebooks may be concatenated to form a joint HARQ-ACK codebook and then transmitted through one PUCCH/PUSCH resource.
  • the terminal when the terminal receives a DCI corresponding to'DCI format 1_0 in which the counter DAI field value is 1 in PCell' in the CORESET corresponding to a specific index, as an example, when index 0 (or index 1) is mapped to CORESET, The terminal applies a compressed quasi-static HARQ-ACK codebook generation method to the (sub-) codebook corresponding to index 0 (or index 1), and corresponds to each index for a different index set in the PCell among the remaining different indexes. After applying the compressed quasi-static HARQ-ACK codebook generation method to the (sub-) codebook, one joint HARQ-ACK codebook may be configured by concatenating different (sub-) codebooks.
  • the above proposal is that when a PCell detects DCI format 1_0 with a counter DAI field value of 1 in a CORESET corresponding to a specific index when a plurality of different indices are set in a plurality of CORESETs set in the terminal, the PCell is defined. It can be viewed as a method of applying a compressed quasi-static HARQ-ACK codebook generation method to the (sub-) codebook for all indexes having a mapping relationship with CORESETs.
  • the compressed quasi-static HARQ-ACK codebook generation method may be applied only to a process of generating a (sub-) codebook corresponding to an index set in CORESET in which a DCI format 1_0 with a counter DAI field value of 1 is detected in the PCell.
  • the (sub- ) A compressed semi-static HARQ-ACK codebook generation method is applied only to the codebook, and index 1 (or index 0) for the (sub-) codebook corresponding to the remaining different indexes (index 1 (or index 0) in the above example)
  • index 1 (or index 0) for the (sub-) codebook corresponding to the remaining different indexes (index 1 (or index 0) in the above example)
  • one joint HARQ-ACK codebook may be configured by concatenating different (sub-) codebooks.
  • the operation may be set to be applied only when indicated through a CORESET corresponding to a specific index.
  • the specific index may be defined as a fixed rule between the base station and the terminal, or information on the specific index may be set/instructed to the terminal through signaling or the like. For example, when a DCI corresponding to DCI format 1_0 with a counter DAI field value of 1 is received from a PCell in a CORESET corresponding to index 0, the proposed operation is performed, and the DCI is received at a CORESET corresponding to index 1. In this case, the suggested operation may not be performed.
  • the HARQ-ACK codebook can be generated by considering all possible PDSCH reception points of M_A,c for all serving cells. Alternatively, in CORESET corresponding to index 1, the terminal may not expect to receive the DCI.
  • an operation is proposed based on the PCell, but this operation can be extended to the SCell.
  • the terminal detects DCI format 1_0 with a counter DAI field value of 1 in a PCell in a certain SCell, the corresponding (sub-)codebook for all indexes having a mapping relationship with the CORESETs defined in the corresponding SCell
  • a compressed quasi-static HARQ-ACK codebook generation method can be applied to a PDSCH reception point (occasion) corresponding to the SCell.
  • Scell #1 and Scell #4 among Pcell/ Scell #1/ Scell #2/ Scell #3/ Scell #4 operate in multi-TRP.
  • DCI format 1_0 with counter DAI field value of 1 is received from PCell through CORESET corresponding to index 0 or index 1 in Scell #1 (or Scell #4)
  • a compressed quasi-static HARQ-ACK codebook generation method can be applied to the (sub-)codebook for index 0 and index 1 having a mapping relationship with the generated CORESETs.
  • a UE reports HARQ-ACK information in a PUCCH only for a SPS PDSCH release indicated by DCI format 1_0 with counter DAI field value of 1 on the PCell within the M_A,c occasions for candidate PDSCH receptions as in Subclause 9.1.2.1 , where the value of counter DAI in DCI format 1_0 is according to Table 9.1.3-1
  • a UE reports HARQ-ACK information in a PUCCH only for a PDSCH reception scheduled by DCI format 1_0 with counter DAI field value of 1 on the PCell within the M_A,c occasions for candidate PDSCH receptions as in Subclause 9.1.2.1, where the value of counter DAI in DCI format 1_0 is according to Table 9.1.3-1
  • a UE reports HARQ-ACK information in a PUCCH only for SPS PDSCH reception within the M_A,c occasions for candidate PDSCH receptions as in Subclause 9.1.2.1, where the value of counter DAI in DCI format 1_0 is according to Table 9.1 .3-1
  • condition 1 When condition 1 is satisfied-Operation 1) the UE determines a HARQ-ACK codebook only for the SPS PDSCH release according to corresponding M_A,c occasion(s) on respective serving cell(s).
  • condition 2 When condition 2 is satisfied-operation 2) the UE determines a HARQ-ACK codebook only for the PDSCH reception according to corresponding M_A,c occasion(s) on respective serving cell(s).
  • condition 3 When condition 3 is satisfied-Operation 3) the UE determines a HARQ-ACK codebook only for the SPS PDSCH reception according to corresponding M_A,c occasion(s) on respective serving cell(s).
  • 13 is an example of a summary diagram showing conditions related to generation of a compressed quasi-static HARQ-ACK codebook and various cases (eg, Cases 1 to 9) for operations corresponding to the conditions. 13 shows examples of proposals in consideration of multiple TRP transmission based on multiple DCI for operations 1 to 3 according to conditions 1 to 3 above.
  • a specific index set for CORESET may mean a CORESET group ID, a CORESET pool index, or a HARQ codebook group ID.
  • "Different TRP" may mean a case in which specific indexes (e.g., CORESET group ID, CORESET Pool Index, HARQ codebook group ID) set in CORESET are different from each other. Unless otherwise stated, this interpretation is equally applicable to the following proposals.
  • Cases 1 to 9 various cases (eg, Cases 1 to 9) will be described in detail for the operations 1 to 3 according to the conditions 1 to 3 above.
  • the "when the CORESETs set in the PCell can correspond to all TRPs" may mean a case in which the indexes corresponding to the CORESETs set in the PCell can include all indices set in a serving cell other than the PCell. .
  • it may mean that an index corresponding to CORESETs set in a PCell is set to 0 and 1, and an index corresponding to CORESETs set in a serving cell other than a Pcell is set to at least one of 0 or 1. Unless otherwise stated, this interpretation is equally applicable to the following proposals.
  • operation 1 or for the final HARQ-ACK codebook connecting each HARQ-ACK codebook corresponding to different TRPs Operation 2 can be performed.
  • the "CORESET in which a specific index is set” may mean a CORESET in which any one of a plurality of indexes is set.
  • the specific index may be defined as a fixed rule. For example, it may mean defining an index that is a criterion for selecting CORESET as a specific index (eg, index 0 or index 1 ).
  • a specific index may be set/indicated through higher layer signaling (eg, RRC signaling, MAC-CE, etc.)/DCI.
  • the "CORESET with a specific index set” may mean a CORESET corresponding to the set specific index. Unless otherwise stated, this interpretation is equally applicable to the following proposals.
  • the "When CORESETs set in the PCell can correspond/relate only to specific TRPs" means that the indexes corresponding to the CORESETs set in the PCell may include only some of all the indices set in serving cells other than the PCell. It can mean if there is. For example, an index corresponding to CORESETs set in a Pcell is set to 0, and an index corresponding to CORESETs set in a serving cell other than a PCell is set to 0 and 1. Unless otherwise stated, this interpretation is equally applicable to the following proposals.
  • operation 1 or for the final HARQ-ACK codebook connecting each HARQ-ACK codebook corresponding to different TRPs Operation 2 can be performed.
  • operation 1 or operation 2 can be performed only for the HARQ-ACK codebook corresponding/related to the index set in the corresponding CORESET.
  • operation 1 or operation 2 may be performed according to whether condition 1 or condition 2 is satisfied for each HARQ-ACK codebook corresponding to/related to different indexes. For example, when a DCI that satisfies condition 1 or condition 2 is received in CORESET in which index 0 is set, operation 1 or operation 2 may be performed only for a HARQ-ACK codebook corresponding to/related to index 0. Independently, when a DCI that satisfies condition 1 or condition 2 is received in CORESET in which index 1 is set, operation 1 or operation 2 may be performed only for the HARQ-ACK codebook corresponding/related to index 1.
  • operation 1 or operation 2 can be performed only for the HARQ-ACK codebook corresponding/related to the index set in the corresponding CORESET.
  • operation 1 or operation 2 may be performed according to whether condition 1 or condition 2 is satisfied for each HARQ-ACK codebook corresponding to/related to different indexes. For example, when a DCI that satisfies condition 1 or condition 2 is received in CORESET in which index 0 is set, operation 1 or operation 2 may be performed only for a HARQ-ACK codebook corresponding to/related to index 0. Independently, when a DCI that satisfies condition 1 or condition 2 is received in CORESET in which index 1 is set, operation 1 or operation 2 may be performed only for the HARQ-ACK codebook corresponding/related to index 1.
  • Case 4-1) In addition to the case of case 4, in the case of a TRP corresponding/related to CORESET(s) not set in the PCell
  • the PCell may be replaced with a specific SCell among SCells configured in the terminal.
  • the SCell having the lowest or largest id among the SCells configured for the terminal may be applied.
  • the replacement of a PCell with a specific SCell according to the above proposal may be limited to a special case.
  • a special case may be a case in which a CORESET with an index corresponding to/not related to the corresponding CORESETs exists for the CORESETs set in the PCell (e.g. when there is a TRP in which a CORESET/CORESET group is set only for SCells).
  • condition 1 and condition 2 can be modified as shown in Table 14.
  • the CORESETs set in the PCell to perform operation 1 or operation 2 are defined to correspond to all TRPs.
  • the base station may set the CORESETs to the terminal so that the indexes corresponding to the CORESETs set in the PCell include all indexes set in the serving cell other than the PCell. case 5) i) Joint HARQ-ACK codebook is set/instructed, ii) condition 3 is satisfied, and iii) M_A,c includes all time points corresponding to different TRPs,
  • condition 3 it is determined whether condition 3 is satisfied, and operation 3 may be performed according to whether the condition is satisfied.
  • operation 3 is performed for each HARQ-ACK codebook according to whether the condition is satisfied.
  • operation 3 may be performed for each HARQ-ACK codebook corresponding to different TRPs according to whether condition 3 is satisfied.
  • operation 1 or operation 2 can be performed only for the HARQ-ACK codebook corresponding to the specific index. In this case, operation 1 or operation 2 may be performed according to whether condition 1 or condition 2 is satisfied for each HARQ-ACK codebook corresponding to a different index.
  • the "when the CORESETs set in the PCell can correspond to all TRPs" may mean a case in which the indexes corresponding to the CORESETs set in the PCell can include all the indices set in serving cells other than the PCell. have. Unless otherwise stated, this interpretation is equally applicable to the following proposals.
  • the "When CORESETs set in the PCell can correspond/relate only to specific TRPs" means that the indexes corresponding to the CORESETs set in the PCell may include only some of all the indices set in serving cells other than the PCell. It can mean if there is. Unless otherwise stated, this interpretation is equally applicable to the following proposals.
  • operation 1 or operation 2 may be performed only for the HARQ-ACK codebook corresponding to the index set in the corresponding CORESET.
  • operation 1 or operation 2 may be performed according to whether condition 1 or condition 2 is satisfied for each HARQ-ACK codebook corresponding to a different index. For example, when a DCI that satisfies condition 1 or condition 2 is received in CORESET in which index 0 is set, operation 1 or operation 2 may be performed only for a HARQ-ACK codebook corresponding to/related to index 0.
  • operation 1 or operation 2 may be performed only for the HARQ-ACK codebook corresponding/related to index 1.
  • the PCell may be replaced with a specific SCell among SCells configured in the terminal.
  • the SCell having the lowest/largest id among the SCells configured for the terminal may be applied.
  • the replacement of a PCell with a specific SCell according to the above proposal may be limited to a special case.
  • a special case may be a case in which a CORESET with an index corresponding to/not related to the corresponding CORESETs exists for the CORESETs set in the PCell (e.g. when there is a TRP in which the CORESET/CORESET group is set only for SCells).
  • the CORESETs set in the PCell to perform operation 1 or operation 2 are defined to correspond to all TRPs. I can. That is, the base station may set the CORESETs to the terminal so that the indexes corresponding to the CORESETs set in the PCell include all indexes set in the serving cell other than the PCell. Case 9) i) If the Separated HARQ-ACK codebook is set/instructed, ii) condition 3 is satisfied, and iii) M_A,c includes only a time point corresponding to a specific TRP,
  • operation 3 is performed for each HARQ-ACK codebook according to whether the condition is satisfied.
  • operation 3 may be performed for each HARQ-ACK codebook corresponding to different TRPs according to whether condition 3 is satisfied.
  • the current 5G NR standard defines operations as shown in Table 16.
  • the base station may indicate to the terminal whether to transmit the HARQ-ACK codebook through the PUSCH.
  • the base station can use the value of the V ⁇ UL_TDAI field (eg 1st DAI field) set/indicated in DCI format 0_1 scheduling PUSCH, and when the corresponding value is indicated as 1, the terminal reads the HARQ-ACK codebook in Can be transmitted via
  • the UE can transmit the HARQ-ACK codebook through the corresponding PUSCH only when the compressed quasi-static HARQ-ACK codebook generation method is indicated.
  • This operation may be referred to as'a method for transmitting a HARQ-ACK codebook through a PUSCH' for convenience in describing the following proposed technique.
  • the method for transmitting the HARQ-ACK codebook to PUSCH assumes a single TRP, so that the operation can be supported even in a multi-TRP situation. A new action must be defined. In the following description, an operation for extending the operation to multi-TRP is proposed.
  • the HARQ-ACK codebook can be independently configured according to a specific index (e.g. CORESET group ID, CORESETPoolIndex, HARQ codebook group ID) set in CORESET.
  • a method for transmitting a HARQ-ACK codebook indicating whether to multiplex HARQ-ACK information to PUSCH transmission as a PUSCH may be defined to operate between CORESETs with the same index.
  • Proposal 4-1 will be described based on the second example described above.
  • Pcell, Scell #2 and Scell #3 represent an example in which the same index (eg, index 0) is mapped to all CORESETs assuming single TRP transmission.
  • Scell #1 and Scell #4 assume multi-TRP transmission and have different specific indexes for each CORESET (e.g., index 0 is set for CORESET #0 to CORESET #2, and indexes for CORESET #3 and CORESET #4) 1 shows an example in which setting) is mapped.
  • the UE when configuring the separated HARQ-ACK codebook, the UE can generate a codebook corresponding to index 0 for Pcell/ Scell #1/ Scell #2/ Scell #3/ Scell #4, and Scell #1 / For Scell #4, a codebook corresponding to index 1 can be generated.
  • Each codebook may be transmitted through different PUCCH/PUSCH resources.
  • the V ⁇ UL_TDAI value defined in DCI format 0_1, which is a reference in the scheme for transmitting the HARQ-ACK codebook to the PUSCH can be applied only to the codebook corresponding to the index mapped to the CORESET in which the DCI is detected. For example, if the DCI format 0_1 is detected in a CORESET set with index 0 (or index 1) and the value of V ⁇ UL_TDAI is 1, a HARQ-ACK codebook corresponding to index 0 (or index 1) is generated, and then HARQ- The ACK codebook can be multiplexed to the PUSCH according to a scheme for transmitting the ACK codebook to the PUSCH.
  • the HARQ-ACK codebook corresponding to index 1 (or index 0) is transmitted through the PUSCH according to the V ⁇ UL_TDAI value indicated in DCI format 0_1 transmitted through the CORESET in which index 1 (or index 0) is set, or the PUCCH resource and If there is no overlapping PUSCH resource, it may be transmitted through a PUCCH resource indicated by DCI.
  • HARQ-ACK information corresponding to different indexes is provided even when different specific indexes (eg CORESET group ID, CORESETPoolIndex, HARQ codebook group ID) are set for different CORESETs. It can be configured with one HARQ-ACK codebook.
  • a DCI field eg 1st DAI field in DCI format 0_1 for indicating this to the UE It can be extended by the number of different indexes mapped to the CORESET set to
  • Proposal 4-2 will be described based on the second example described above.
  • Pcell, Scell #2 and Scell #3 represent an example in which the same index (eg, index 0) is mapped to all CORESETs assuming single TRP transmission.
  • Scell #1 and Scell #4 assume multi-TRP transmission and have different specific indexes for each CORESET (e.g., index 0 is set for CORESET #0 to CORESET #2, and indexes for CORESET #3 and CORESET #4) 1 shows an example in which setting) is mapped.
  • the terminal may generate a (sub-)codebook corresponding to index 0 for Pcell/ Scell #1/ Scell #2/ Scell #3/ Scell #4 when configuring the joint HARQ-ACK codebook, and , For Scell #1/ Scell #4, a (sub-)codebook corresponding to index 1 can be generated.
  • the terminal may configure a joint HARQ-ACK codebook by concatenating the two (sub-)codebooks, and then transmit it through one PUCCH/PUSCH resource.
  • the corresponding in DCI format 0_1 to indicate whether the (sub-)codebook corresponding to each index in the joint HARQ-ACK codebook is multiplexed to PUSCH and transmitted.
  • the DCI field can be extended to 2 bits (or as many as the number of indexes set in CORESET). For example, 1 bit may be used to indicate whether the (sub-)codebook corresponding to index 0 is multiplexed, and another 1 bit may be used to indicate whether the (sub-)codebook corresponding to index 1 is multiplexed. In this case, the (sub-)codebook for which multiplexing is not indicated may not be transmitted to the base station (dropping).
  • a previously defined DCI field is used as it is, but it is possible to indicate whether or not the entire joint HARQ-ACK codebook is to be multiplexed to the PUSCH. For example, if the V ⁇ UL_TDAI value of DCI format 0_1 is 1, the entire joint HARQ-ACK codebook can be multiplexed to the PUSCH, and in the opposite case (i.e., if the V ⁇ UL_TDAI value is 0) the joint HARQ-ACK codebook The whole may not be multiplexed to the PUSCH.
  • a method of using or extending a DCI field defined in an existing DCI format has been described, but in order to perform the proposal, a new DCI field is defined in the DCI format, or existing DCI fields (eg, DMRS It is also possible to perform the proposed operation when a combination of specific values is indicated for the port indication field, TB information field, etc.).
  • the'index' is in the CORESET setting separately from the index set to distinguish CORESET (e.g., CORESET ID). It may mean an index that can be interpreted as some kind of index that can be included, for example, CORESET group ID, CORESETPoolIndex, HARQ codebook group ID, and the like.
  • the method of connecting according to This example may be an example of configuring the joint ACK/NACK codebook, and is not limited to the only method of configuring the joint ACK/NACK codebook.
  • M-TRP or M-cell, hereinafter, all TRPs can be replaced by cells, or a case in which multiple CORESETs (/CORESET groups) are set from one TRP can also be assumed to be M-TRP
  • signaling when the UE receives multiple DCI ie, when each TRP transmits DCI to the UE. 14 is only an example for convenience of description and does not limit the technical scope of the present invention.
  • TRP refers to a panel, an antenna array, and a cell (eg, macro cell / small cell / pico cell, etc.).
  • TP transmission point
  • base station base station
  • gNB base station
  • the TRP may be classified according to information (eg, index, ID) on the CORESET group (or CORESET pool).
  • information eg, index, ID
  • CORESET groups or CORESET pools
  • Such setting of the CORESET group (or CORESET pool) may be performed through higher layer signaling (eg, RRC signaling, etc.).
  • the network side may be one base station including a plurality of TRPs, and may be one cell including a plurality of TRPs.
  • an ideal/non-ideal backhaul may be set between TRP 1 and TRP 2 constituting the network side.
  • the following description is described based on a plurality of TRPs, but this can be extended and applied equally to transmission through a plurality of panels.
  • the operation in which the terminal receives a signal from TRP1/TRP2 can also be interpreted/described as an operation in which the terminal receives a signal (via/using TRP1/2) from the network side (or may be an operation).
  • the operation in which the terminal transmits a signal to TRP1/TRP2 is an operation in which the terminal transmits a signal to the network side (via/using TRP1/TRP2) can be interpreted/explained (or can be an operation), and vice versa Can also be interpreted/explained.
  • the UE may receive configuration information related to transmission/reception based on multiple TRP through/using TRP 1 (and/or TRP 2) from the network side (S1405). That is, the network side may transmit configuration information related to multiple TRP-based transmission and reception to the UE through/using TRP 1 (and/or TRP 2) (S1405).
  • the configuration information may include information related to the configuration of the network side (i.e. TRP configuration) / resource information related to transmission and reception based on multiple TRP (resource allocation).
  • the configuration information may be delivered through higher layer signaling (eg, RRC signaling, MAC-CE, etc.).
  • the setting information is predefined or set, the corresponding step may be omitted.
  • the setting information may include CORESET related setting information (eg, ControlResourceSet IE) as described in the above-described methods (eg, proposal 1 / proposal 2 / proposal 3 / proposal 4).
  • the CORESET-related setting information may include a CORESET-related ID (eg, controlResourceSetID), an index of a CORESET pool for CORESET (eg, CORESETPoolIndex), a time/frequency resource setting of CORESET, and TCI information related to CORESET.
  • the index of the CORESET pool (eg, CORESETPoolIndex) may mean a specific index (e.g. CORESET group index, HARQ codebook index) mapped/set to each CORESET.
  • the configuration information may include configuration related to the joint HARQ-ACK codebook or separated HARQ-ACK codebook described in the above-described method (eg, proposal 1 / proposal 2 / proposal 3 / proposal 4, etc.) .
  • the configuration information may include a parameter (eg, ackNackFeedbackMode) for setting the HARQ-ACK codebook scheme, and a joint HARQ-ACK codebook or a separated HARQ-ACK codebook may be indicated through the parameter.
  • the configuration information is information related to the generation of a compressed quasi-static HARQ-ACK codebook / HARQ-ACK information, as described in the above-described method (eg, proposal 1 / proposal 2 / proposal 3 / proposal 4, etc.) And information indicating whether or not the PUSCH is multiplexed.
  • the configuration information may include configuration related to PDCCH / PDSCH / PUCCH / PUSCH, etc., as described in the above-described methods (eg, proposal 1 / proposal 2 / proposal 3 / proposal 4, etc.).
  • an operation in which the UE (100/200 of FIGS. 17 to 21) of the above-described step S1405 receives configuration information related to the multiple TRP-based transmission/reception from the network side (100/200 of FIGS. 17 to 21) May be implemented by the apparatus of FIGS. 17 to 21, which will be described below.
  • one or more processors 102 may control one or more transceivers 106 and/or one or more memories 104 to receive configuration information related to transmission and reception based on the multiple TRP, and one or more transceivers 106 May receive configuration information related to the multiple TRP-based transmission and reception from the network side.
  • configuration information related to the multiple TRP-based transmission and reception of the network side (100/200 of FIGS. 17 to 21) of the above-described step S1405 to the UE (100/200 of FIGS. 17 to 21) The operation of transmitting may be implemented by the apparatus of FIGS. 17 to 21 to be described below.
  • one or more processors 102 may control one or more transceivers 106 and/or one or more memories 104 to transmit configuration information related to transmission and reception based on the multiple TRP, and one or more transceivers 106 May transmit configuration information related to transmission/reception based on the multiple TRP from the network side.
  • the UE may receive DCI 1 and Data 1 scheduled by the corresponding DCI 1 through/using TRP 1 from the network side (S1410-1).
  • the UE may receive DCI 2 from the network side through/using TRP 2 and Data 2 scheduled by the corresponding DCI 2 (S1410-2). That is, the network side may transmit DCI 1 and Data 1 scheduled by the corresponding DCI 1 to the UE through/using TRP 1 (S1410-1).
  • the network side may transmit DCI 2 and Data 2 scheduled by the corresponding DCI 2 through/using TRP 2 to the UE (s1410-2).
  • DCI e.g. DCI 1, DCI 2
  • Data e.g. Data 1, Data 2
  • control channels e.g. PDCCH, etc.
  • data channels e.g. PDSCH, etc.
  • steps S1410-1 and S1410-2 may be performed simultaneously, or one may be performed earlier than the other.
  • the DCI 1 and/or the DCI 2 are transmitted and received through a PDCCH, and the Data 1 and/or Alternatively, it may include scheduling information on the PDSCH for transmission and reception of the Data 2.
  • the DCI 1 and / or the DCI 2 is a specific index (eg, CORESETPoolIndex) is mapped / set CORESET as described in the above-described method (e.g., proposal 1 / proposal 2 / proposal 3 / proposal 4, etc.) Can be detected/received at
  • the DCI 1 and/or the DCI 2 may include information on at least one operation of the above-described methods (eg, proposal 1 / proposal 2 / proposal 3 / proposal 4, etc.).
  • the DCI 1 and / or the DCI 2 is a joint HARQ-ACK codebook or separated HARQ-ACK codebook Can be used to indicate.
  • the DCI 1 and/or the DCI 2 may include an explicit field indicating either a joint HARQ-ACK codebook or a separated HARQ-ACK codebook.
  • any of a joint HARQ-ACK codebook or a separated HARQ-ACK codebook One may be indicated.
  • the DCI 1 and/or the DCI 2 may be'DCI format 1_0 with counter DAI field value of 1 on the PCell' as described above.
  • the UE (100/200 of FIGS. 17 to 21) of the above-described step S1410-1 / S1410-2 is the DCI 1 and/or the DCI from the network side (100/200 of FIGS. 17 to 21). 2 and/or the operation of receiving Data 1 and/or Data 2 may be implemented by the apparatus of FIGS. 17 to 21 to be described below.
  • one or more processors 102 may include one or more transceivers 106 and/or one or more memories 104 to receive the DCI1 and/or the DCI 2 and/or the Data 1 and/or the Data2. Control, and one or more transceivers 106 may receive the DCI1 and/or the DCI 2 and/or the Data 1 and/or the Data2 from the network side.
  • the Network side (100/200 of FIGS. 17 to 21) of the above-described steps S1410-1 / S1410-2 is the DCI1 and/or the DCI 2 to the UE (100/200 of FIGS. 17 to 21). And/or the operation of transmitting the Data 1 and/or the Data 2 may be implemented by the devices of FIGS. 17 to 21 to be described below.
  • one or more processors 102 may include one or more transceivers 106 and/or one or more memories 104 to transmit the DCI1 and/or the DCI 2 and/or the Data 1 and/or the Data2. Control, and one or more transceivers 106 may transmit the DCI1 and/or the DCI 2 and/or the Data 1 and/or the Data2 to the UE.
  • the UE may decode Data 1 and Data 2 received from TRP 1 and TRP 2 (S1415). For example, the UE may perform channel estimation and/or decoding of data based on the above-described method (eg, proposal 1 / proposal 2 / proposal 3 / proposal 4, etc.).
  • step S1415 the operation of decoding the Data 1 and Data 2 by the UE (100/200 of FIGS. 17 to 21) in step S1415 described above may be implemented by the apparatus of FIGS. 17 to 21 to be described below.
  • one or more processors 102 may control one or more memories 104 to perform an operation of decoding Data 1 and Data 2.
  • the UE may receive DCI 3 for scheduling PUSCH from the network side.
  • the DCI 3 may be DCI format 0_1, and may include a 1-bit or n-bit (n> 1) DAI field.
  • the DCI and / or HARQ for the Data 1 and / or Data 2 through one or more PUCCH (s) -ACK information may be transmitted to the network side through/using TRP 1 and/or TRP 2 (S1420-1, S1420-2).
  • the network side is based on the above-described proposed method (eg, proposal 1 / proposal 2 / proposal 3 / proposal 4, etc.), the DCI and / or HARQ-ACK information for the Data 1 and / or Data 2 (eg ACK information, NACK information, etc.) may be received from the UE through/using TRP 1 and/or TRP 2 (S1420-1, S1420-2).
  • the DCI and / or HARQ-ACK information for the Data 1 and / or Data 2 eg ACK information, NACK information, etc.
  • TRP 1 and/or TRP 2 S1420-1, S1420-2
  • HARQ-ACK information for Data 1 and/or Data 2 may be combined or separated into one.
  • the UE is configured to transmit only HARQ-ACK information to the representative TRP (e.g. TRP 1), and transmission of HARQ-ACK information to another TRP (e.g. TRP 2) may be omitted.
  • the HARQ-ACK information may be composed of a joint HARQ-ACK codebook or a separated HARQ-ACK codebook described in the above-described method (eg, proposal 1 / proposal 2 / proposal 3 / proposal 4, etc.).
  • the first HARQ-ACK information associated with the TRP1 and the second HARQ-ACK information associated with the TRP2 are concatenated to one HARQ- It can be composed of ACK information.
  • one HARQ-ACK information configured by concatenating the first HARQ-ACK information and the second HARQ-ACK information may be transmitted to a specific TRP through the same uplink resource (eg, PUCCH, PUSCH, etc.).
  • the first HARQ-ACK information related to the TRP1 and the second HARQ-ACK information related to the TRP2 are each TDM (Time division multiplexing) and transmitted.
  • each HARQ-ACK information may be transmitted to each TRP through different uplink resources (eg, PUCCH, PUSCH, etc.).
  • the HARQ-ACK information may be transmitted through PUCCH and/or PUSCH.
  • the PUCCH resource through which HARQ-ACK information is transmitted may be determined based on the method described in the above-described method (eg, proposal 1/ proposal 2/ proposal 3/ proposal 4, etc.).
  • PUCCH resources may be determined according to a PUCCH resource indicator (PRI) field value indicated through a specific DCI.
  • PRI PUCCH resource indicator
  • the terminal receives different DCIs from CORESETs corresponding to different CORESETPoolIndexes (e.g., the first DCI and the second DCI), i) the time when the DCI was transmitted, ii) the CORESETPoolIndex set in the CORESET where the DCI was transmitted, and iii)
  • the order of DCI may be determined based on the cell index (or ID).
  • the time when the DCI is transmitted may mean an index of a monitoring opportunity related to a channel (eg, PDCCH) through which the DCI is transmitted.
  • PUCCH resources may be determined according to the PRI field value of a specific DCI (eg, last DCI) determined based on the order of the DCI.
  • the HARQ-ACK information is set as a compressed semi-static HARQ-ACK codebook in consideration of the number of possible PDSCH reception points for the DCI (eg DCI1 / DCI2) / all serving cells supporting the terminal / serving cells. Can be.
  • the UE (100/200 of FIGS. 17 to 21) of the above-described steps S1420-1 / S1420-2 is the Network side (100/200 of FIGS. 17 to 21) through one or more PUCCHs.
  • the operation of transmitting HARQ-ACK information for Data 2 may be implemented by the apparatus of FIGS. 17 to 21 to be described below.
  • one or more processors 102 may use one or more transceivers 106 and/or one or more memories 104 to transmit HARQ-ACK information for Data 1 and/or Data 2 through one or more PUCCHs.
  • Control, and at least one transceiver 106 may transmit HARQ-ACK information for Data 1 and/or Data 2 to the network side.
  • the Network side (100/200 of FIGS. 17 to 21) of steps S1420-1 / S1420-2 described above is the Data 1 through one or more PUCCHs from the UE (100/200 of FIGS. 17 to 21).
  • the operation of receiving HARQ-ACK information for Data 2 may be implemented by the apparatuses of FIGS. 17 to 21 to be described below.
  • one or more processors 102 may control one or more transceivers 106 and/or one or more memories 104 to receive HARQ-ACK information for Data 1 and/or Data 2.
  • One or more transceivers 106 may receive HARQ-ACK information for Data 1 and/or Data 2 from the UE.
  • a multi-DCI-based M-TRP operation has been mainly described, but in some cases, it may be applied to a single DCI-based M-TRP operation.
  • HARQ-ACK Hybrid Automatic Repeat and ReQuest-Acknowledgement
  • UE user equipment
  • An example of a transfer operation flow chart is shown.
  • the terminal may be supported by a plurality of TRPs, and an ideal/non-ideal backhaul may be set between a plurality of TRPs.
  • 15 is merely for convenience of description and does not limit the scope of the present invention.
  • some step(s) shown in FIG. 15 may be omitted depending on circumstances and/or settings.
  • TRP refers to a panel, an antenna array, and a cell (eg, macro cell / small cell / pico cell, etc.).
  • TP transmission point
  • base station base station
  • gNB base station
  • the TRP may be classified according to information (eg, index, ID) on the CORESET group (or CORESET pool).
  • information eg, index, ID
  • CORESET groups or CORESET pools
  • Such setting of the CORESET group (or CORESET pool) may be performed through higher layer signaling (eg, RRC signaling, etc.).
  • the UE may transmit a preamble for random access (S1510).
  • the preamble may correspond to'Msg1' or'MsgA' in the random access procedure of the NR standard.
  • one or more processors 102 may control one or more transceivers 106 and/or one or more memories 104 to transmit the preamble, and one or more transceivers 106 may transmit the preamble.
  • the terminal may receive a response message for random access corresponding to the preamble (S1520).
  • a radio remote control (RRC) connection may be established based on the preamble and the response message.
  • step S1520 the operation of receiving a response message for random access by the terminal (100/200 of FIGS. 17 to 21) in step S1520 described above may be implemented by the apparatus of FIGS. 17 to 21 to be described below.
  • one or more processors 102 may control one or more transceivers 106 and/or one or more memories 104 to receive the response message, and one or more transceivers 106 may receive the response message. I can.
  • steps S1510 and S1520 may correspond to the random access procedure described in FIG. 6 described above.
  • the terminal may perform the operations described below in a state in which the RRC connection is established.
  • the terminal may receive configuration information.
  • the configuration information may be received through higher layer signaling (eg, RRC or MAC CE).
  • the operation of receiving the setting information may be performed before the operation of receiving a plurality of DCIs (eg, the first DCI and the second DCI) in step S1530.
  • the setting information may include CORESET related setting information (eg, ControlResourceSet IE) as described in the above-described methods (eg, proposal 1 / proposal 2 / proposal 3 / proposal 4).
  • the CORESET-related setting information may include a CORESET-related ID (eg, controlResourceSetID), an index of a CORESET pool for CORESET (eg, CORESETPoolIndex), a time/frequency resource setting of CORESET, and TCI information related to CORESET.
  • CORESET related setting information eg, ControlResourceSet IE
  • the CORESET-related setting information may include a CORESET-related ID (eg, controlResourceSetID), an index of a CORESET pool for CORESET (eg, CORESETPoolIndex), a time/frequency resource setting of CORESET, and TCI information related to CORESET.
  • the configuration information may include information related to a feedback mode of the HARQ-ACK information (eg, ackNackFeedbackMode). That is, the configuration information may include information indicating whether the first HARQ-ACK information and the second HARQ-ACK information are concatenated and configured as one.
  • the information related to the feedback mode may indicate either a joint mode or a separate mode, and a HARQ-ACK codebook may be configured based on the indicated mode.
  • a joint HARQ-ACK codebook when a joint mode is indicated, a joint HARQ-ACK codebook is configured, and when an individual mode is indicated, a Separated HARQ-ACK codebook Can be configured.
  • the configuration information is information related to the generation of a compressed quasi-static HARQ-ACK codebook / HARQ-ACK information, as described in the above-described method (eg, proposal 1 / proposal 2 / proposal 3 / proposal 4, etc.) And information indicating whether or not the PUSCH is multiplexed.
  • the UE may receive a plurality of downlink control information (DCI) (S1530).
  • DCI downlink control information
  • the plurality of DCIs may be received through a physical downlink control channel (PDCCH).
  • PDCH physical downlink control channel
  • each control resource set associated with a PDCCH through which each DCI is received may correspond to a different control resource set group.
  • the control resource set group may include one or more control resource sets (ie, CORESET) corresponding to the same CORESETPoolIndex, It may be a concept corresponding to the CORESET pool. Therefore, receiving each DCI based on different control resource set groups may mean receiving each DCI through CORESET corresponding to different CORESETPoolIndex. That is, the CORESETPoolIndex corresponding to the CORESET to which each DCI is received may be set differently.
  • Each DCI may include (i) a field related to the number k of slots associated with the HARQ-ACK timing and (ii) a PUCCH resource indication field (eg, a PRI field).
  • each DCI may further include a DMRS port related field and a transport block related field.
  • At least one of the plurality of DCIs may correspond to DCI format 1_0 in which the counter DAI field value is 1 in the PCell.
  • At least one of the plurality of DCIs may correspond to DCI format 0_1 including a V ⁇ UL_TDAI field (e.g. 1st DAI field).
  • Multiplexing of the HARQ-ACK information and a physical uplink shared channel (PUSCH) is indicated based on a value of a downlink assignment indicator (DAI) field of a specific DCI of DCI format 0_1 among the plurality of DCIs Can be. That is, whether to transmit the HARQ-ACK codebook by multiplexing it through the PUSCH can be indicated.
  • DAI downlink assignment indicator
  • the operation in which the terminal (100/200 of FIGS. 17 to 21) in step S1530 described above receives a plurality of DCIs may be implemented by the apparatus of FIGS. 17 to 21 to be described below.
  • one or more processors 102 may control one or more transceivers 106 and/or one or more memories 104 to receive the plurality of DCIs, and one or more transceivers 106 may control the plurality of DCIs. Can receive.
  • the UE may receive a physical downlink shared channel (PDSCH) scheduled by each DCI (S1540).
  • the PDSCH may be received in slot n.
  • the terminal may receive a first PDSCH scheduled by a first DCI and a second PDSCH scheduled by a second DCI.
  • the first DCI and the first PDSCH may be received through a first transmission/reception point
  • the second DCI and the second PDSCH may be received through a second transmission/reception point.
  • step S1540 the operation of receiving the PDSCH by the terminal (100/200 of FIGS. 17 to 21) in step S1540 described above may be implemented by the apparatus of FIGS. 17 to 21 to be described below.
  • one or more processors 102 may control one or more transceivers 106 and/or one or more memories 104 to receive the PDSCH, and one or more transceivers 106 may receive the PDSCH. .
  • the terminal may transmit HARQ-ACK information (S1550).
  • the HARQ-ACK information may be information corresponding to the received PDSCH.
  • the HARQ-ACK information may be transmitted in slot n+k through a physical uplink control channel (PUCCH).
  • PUCCH physical uplink control channel
  • k represents the number of slots.
  • the HARQ-ACK information may be transmitted through at least one of a first transmission and reception point or a second transmission and reception point.
  • the resource of the PUCCH through which the HARQ-ACK information is transmitted may be determined based on the method described in the above-described method (eg, proposal 1 / proposal 2 / proposal 3 / proposal 4, etc.).
  • the plurality of DCIs is (i) a physical downlink control channel (PDCCH) related monitoring opportunity ( Monitoring occasion) index, (ii) cell index, and (iii) index associated with each control resource set group (eg, CORESETPoolIndex) can be indexed based on (the order can be determined).
  • the PDCCH-related monitoring opportunity may mean a time point at which DCI is received/transmitted.
  • the index associated with the control resource set group may mean a CORESETPoolIndex set in a CORESET to which DCI is transmitted.
  • PUCCH resources may be determined according to a specific DCI determined based on the indexing (or order) of the plurality of DCIs.
  • the same PDCCH related monitoring opportunity may be indexed in an ascending order of the cell index, and then indexed in an ascending order of the PDCCH related monitoring opportunity index.
  • DCIs in one serving cell within the same PDCCH monitoring opportunity may be indexed based on an index (eg, CORESETPoolIndex) associated with a control resource set group. Based on the fact that the index associated with the first control resource set group is 0 and the index associated with the second control resource set group is 1, the first DCI may be indexed before the second DCI.
  • an index eg, CORESETPoolIndex
  • the resource of the PUCCH may be determined based on a last DCI among a plurality of received DCIs. That is, it may be determined based on the PUCCH resource indication field of the last DCI.
  • the last DCI may be determined based on i) an index of a monitoring occasion related to the PDCCH, (ii) a cell index, and (iii) an index of each control resource set group.
  • the order may be determined in an ascending order of the cell index, and thereafter, the order may be determined in an ascending order of the index of monitoring opportunities related to the PDCCH.
  • the order may be determined in an ascending order of the index of each control resource set group.
  • the last DCI may be determined based on the order.
  • the second The DCI received through the PDCCH associated with the second control resource set corresponding to the control resource set group may be determined as the last DCI.
  • the PUCCH resource set may be determined based on the payload size of the extended codebook (ie, considering the case of overlapping transmission in the time domain).
  • PUCCH resources for Separated HARQ-ACK codebook transmission i) DCI is transmitted It may be determined based on the time point and iii) the cell index (or ID).
  • the HARQ-ACK information may be configured based on the method described in the above-described method (eg, proposal 1/ proposal 2/ proposal 3/ proposal 4, etc.).
  • the HARQ-ACK information corresponds to (i) first HARQ-ACK information corresponding to a PDSCH associated with a first control resource set corresponding to a first control resource set group and (ii) corresponding to a second control resource set group.
  • the second HARQ-ACK information corresponding to the PDSCH associated with the second control resource set may be concatenated to be configured as one (ie, one HARQ-ACK information).
  • second HARQ-ACK information associated with the second serving cell may be generated and then concatenated to be configured as one.
  • one HARQ-ACK information configured by concatenating the first HARQ-ACK information and the second HARQ-ACK information may be transmitted to a specific transmission/reception point through the same uplink resource (eg, PUCCH, PUSCH, etc.).
  • the HARQ-ACK information includes (i) first HARQ-ACK information corresponding to a PDSCH associated with a first control resource set corresponding to a first control resource set group and (ii) corresponding to a second control resource set group.
  • Each of the second HARQ-ACK information corresponding to the PDSCH associated with the second control resource set may be individually configured.
  • the first HARQ-ACK information and the second HARQ-ACK information may be transmitted by time division multiplexing (TDM) in one slot, respectively.
  • TDM time division multiplexing
  • each HARQ-ACK information may be transmitted to each transmission/reception point through different uplink resources (eg, PUCCH, PUSCH, etc.).
  • the terminal CORESET in which the corresponding DCI is detected may be configured according to the compressed semi-static HARQ-ACK codebook generation method only for the HARQ-ACK codebook corresponding to a specific index set (or mapped) to.
  • the HARQ-ACK codebook may be multiplexed and transmitted through the PUSCH.
  • the operation of transmitting the HARQ-ACK information by the terminal (100/200 of FIGS. 17 to 21) in step S1550 described above may be implemented by the apparatus of FIGS. 17 to 21 to be described below.
  • one or more processors 102 may control one or more transceivers 106 and/or one or more memories 104 to transmit the HARQ-ACK information, and one or more transceivers 106 may control the HARQ-ACK information.
  • Information can be transmitted.
  • 16 shows an example of an operation flowchart for receiving HARQ-ACK information of a base station (BS) to which the methods proposed in the present specification (eg, proposal 1/ proposal 2/ proposal 3/ proposal 4, etc.) can be applied .
  • BS base station
  • the methods proposed in the present specification eg, proposal 1/ proposal 2/ proposal 3/ proposal 4, etc.
  • 16 is merely for convenience of description and does not limit the scope of the present invention.
  • some step(s) shown in FIG. 16 may be omitted depending on circumstances and/or settings.
  • the base station may be a generic term for an object that transmits and receives data to and from the terminal.
  • the base station may be a concept including one or more transmission points (TP), one or more transmission and reception points (TRP).
  • the TP and/or TRP may include a panel of a base station, a transmission and reception unit, and the like.
  • the TRP may be classified according to information (eg, index, ID) on the CORESET group (or CORESET pool).
  • information eg, index, ID
  • the CORESET group or CORESET pool
  • Such setting of the CORESET group (or CORESET pool) may be performed through higher layer signaling (eg, RRC signaling, etc.).
  • the base station may receive a preamble for random access (S1610).
  • the preamble may correspond to'Msg1' or'MsgA' in the random access procedure of the NR standard.
  • step S1610 the operation of receiving the preamble for random access by the base station (100/200 in FIGS. 17 to 21) of step S1610 described above will be implemented by the apparatus of FIGS. 17 to 21 to be described below.
  • one or more processors 102 may control one or more transceivers 106 and/or one or more memories 104 to receive the preamble, and one or more transceivers 106 may receive the preamble. .
  • the base station may transmit a response message for random access corresponding to the preamble (S1620).
  • a radio remote control (RRC) connection may be established based on the preamble and the response message.
  • step S1620 the operation of receiving a response message for random access by the terminal (100/200 of FIGS. 17 to 21) of step S1620 described above may be implemented by the apparatus of FIGS. 17 to 21 to be described below.
  • one or more processors 102 may control one or more transceivers 106 and/or one or more memories 104 to transmit the response message, and one or more transceivers 106 may transmit the response message. have.
  • steps S1610 and S1620 may correspond to the random access procedure described in FIG. 6 described above.
  • the terminal may perform the operations described below in a state in which the RRC connection is established.
  • the base station may transmit configuration information to the terminal.
  • the configuration information may be transmitted through higher layer signaling (eg, RRC or MAC CE). Further, the operation of transmitting the setting information may be performed before the operation of transmitting a plurality of DCIs in step S1630.
  • the setting information may include CORESET related setting information (eg, ControlResourceSet IE) as described in the above-described methods (eg, proposal 1 / proposal 2 / proposal 3 / proposal 4).
  • the CORESET-related setting information may include a CORESET-related ID (eg, controlResourceSetID), an index of a CORESET pool for CORESET (eg, CORESETPoolIndex), a time/frequency resource setting of CORESET, and TCI information related to CORESET.
  • CORESET related setting information eg, ControlResourceSet IE
  • the CORESET-related setting information may include a CORESET-related ID (eg, controlResourceSetID), an index of a CORESET pool for CORESET (eg, CORESETPoolIndex), a time/frequency resource setting of CORESET, and TCI information related to CORESET.
  • the configuration information may include information related to a feedback mode of the HARQ-ACK information (eg, ackNackFeedbackMode). That is, the configuration information may include information indicating whether the first HARQ-ACK information and the second HARQ-ACK information are concatenated and configured as one.
  • the information related to the feedback mode may indicate either a joint mode or a separate mode, and a HARQ-ACK codebook may be configured based on the indicated mode.
  • a joint HARQ-ACK codebook when a joint mode is indicated, a joint HARQ-ACK codebook is configured, and when an individual mode is indicated, a Separated HARQ-ACK codebook Can be configured.
  • the configuration information is information related to the generation of a compressed quasi-static HARQ-ACK codebook / HARQ-ACK information, as described in the above-described method (eg, proposal 1 / proposal 2 / proposal 3 / proposal 4, etc.) And information indicating whether or not the PUSCH is multiplexed.
  • the base station may transmit a plurality of downlink control information (DCI) to a user equipment (UE) (S1610).
  • DCI downlink control information
  • UE user equipment
  • the plurality of DCIs may be received through a physical downlink control channel (PDCCH).
  • PDCCH physical downlink control channel
  • each control resource set associated with a PDCCH through which each DCI is received may correspond to a different control resource set group.
  • the control resource set group may include one or more control resource sets (ie, CORESET) corresponding to the same CORESETPoolIndex, It may be a concept corresponding to the CORESET pool. Therefore, receiving each DCI based on different control resource set groups may mean receiving each DCI through CORESET corresponding to different CORESETPoolIndex. That is, the CORESETPoolIndex corresponding to the CORESET to which each DCI is received may be set differently.
  • Each DCI may include (i) a field related to the number k of slots associated with the HARQ-ACK timing and (ii) a PUCCH resource indication field (eg, a PRI field).
  • each DCI may further include a DMRS port related field and a transport block related field.
  • step S1630 the operation of transmitting a plurality of DCIs by the base station (100/200 of FIGS. 17 to 21) of step S1630 described above may be implemented by the apparatus of FIGS. 17 to 21 to be described below.
  • one or more processors 102 may control one or more transceivers 106 and/or one or more memories 104 to transmit the plurality of DCIs, and one or more transceivers 106 may control the plurality of DCIs. Can be transmitted to the terminal.
  • the base station may transmit a physical downlink shared channel (PDSCH) scheduled by each DCI to the terminal (S1640).
  • PDSCH physical downlink shared channel
  • the PDSCH may be transmitted in slot n.
  • the base station may transmit a first PDSCH scheduled by a first DCI and a second PDSCH scheduled by a second DCI.
  • the first DCI and the first PDSCH may be transmitted through a first transmission/reception point
  • the second DCI and the second PDSCH may be transmitted through a second transmission/reception point.
  • step S1640 the operation of transmitting the PDSCH by the base station (100/200 of FIGS. 17 to 21) in step S1640 described above may be implemented by the apparatus of FIGS. 17 to 21 to be described below.
  • one or more processors 102 may control one or more transceivers 106 and/or one or more memories 104 to transmit the PDSCH, and one or more transceivers 106 may transmit the PDSCH to the terminal. have.
  • the base station may receive HARQ-ACK information from the terminal (S1650).
  • the HARQ-ACK information may be information corresponding to the PDSCH.
  • the HARQ-ACK information may be received in slot n+k through a physical uplink control channel (PUCCH).
  • PUCCH physical uplink control channel
  • k represents the number of slots.
  • the HARQ-ACK information may be received through at least one of a first transmission and reception point or a second transmission and reception point.
  • the resource of the PUCCH through which the HARQ-ACK information is transmitted may be determined based on the method described in the above-described method (eg, proposal 1 / proposal 2 / proposal 3 / proposal 4, etc.).
  • the plurality of DCIs are (i) physical downlink control channel (PDCCH) related monitoring Indexing may be performed based on an index of a monitoring occasion, (ii) a cell index, and (iii) an index associated with each control resource set group (eg, CORESETPoolIndex) (an order may be determined).
  • PUCCH resources may be determined according to a specific DCI determined based on the indexing (or order) of the plurality of DCIs.
  • the same PDCCH related monitoring opportunity may be indexed in an ascending order of the cell index, and then indexed in an ascending order of the PDCCH related monitoring opportunity index.
  • DCIs in one serving cell within the same PDCCH monitoring opportunity may be indexed based on an index (eg, CORESETPoolIndex) associated with a control resource set group. Based on the fact that the index associated with the first control resource set group is 0 and the index associated with the second control resource set group is 1, the first DCI may be indexed before the second DCI.
  • an index eg, CORESETPoolIndex
  • the resource of the PUCCH may be determined based on a last DCI among a plurality of received DCIs. That is, it may be determined based on the PUCCH resource indication field of the last DCI.
  • the last DCI may be determined based on i) an index of a monitoring occasion related to the PDCCH, (ii) a cell index, and (iii) an index of each control resource set group.
  • the order may be determined in an ascending order of the cell index, and thereafter, the order may be determined in an ascending order of the index of monitoring opportunities related to the PDCCH.
  • the order may be determined in an ascending order of the index of each control resource set group.
  • the last DCI may be determined based on the order.
  • PUCCH resources for Separated HARQ-ACK codebook transmission i) DCI is transmitted It may be determined based on the time point and iii) the cell index (or ID).
  • the HARQ-ACK information may be configured based on the method described in the above-described method (eg, proposal 1/ proposal 2/ proposal 3/ proposal 4, etc.).
  • the HARQ-ACK information corresponds to (i) first HARQ-ACK information corresponding to a PDSCH associated with a first control resource set corresponding to a first control resource set group and (ii) corresponding to a second control resource set group.
  • the second HARQ-ACK information corresponding to the PDSCH associated with the second control resource set may be concatenated to be configured as one (ie, one HARQ-ACK information).
  • second HARQ-ACK information associated with the second serving cell may be generated and then concatenated to be configured as one.
  • the HARQ-ACK information includes (i) first HARQ-ACK information corresponding to a PDSCH associated with a first control resource set corresponding to a first control resource set group and (ii) corresponding to a second control resource set group.
  • Each of the second HARQ-ACK information corresponding to the PDSCH associated with the second control resource set may be individually configured.
  • the first HARQ-ACK information and the second HARQ-ACK information may be transmitted by time division multiplexing (TDM) in one slot, respectively.
  • TDM time division multiplexing
  • the operation of receiving HARQ-ACK information by the base station (100/200 of FIGS. 17 to 21) of step S1650 described above may be implemented by the apparatus of FIGS. 17 to 21 to be described below.
  • one or more processors 102 may control one or more transceivers 106 and/or one or more memories 104 to receive the HARQ-ACK information, and one or more transceivers 106 may control the HARQ-ACK information.
  • Information can be received from the terminal.
  • the network side (e.g. TRP 1 / TRP 2) may correspond to a first radio device, a UE may correspond to a second radio device, and the opposite case may be considered in some cases.
  • a first radio device eg TRP 1
  • a second device eg TRP 2
  • the opposite case may be considered in some cases.
  • Network side/UE signaling and operation are performed by one or more processors (eg 102, 202) of FIGS. 17 to 21
  • Network side/UE signaling and operation eg proposal 1/ 2/ 3/ 4/ FIG. 14/ FIG. 15/ FIG. 16, etc.
  • FIGS. 17 to 21 Network side/UE signaling and operation (eg proposal 1/ 2/ 3/ 4/ FIG. 14/ FIG. 15/ FIG. 16, etc.) described above can be processed by at least one processor of FIGS. 17 to 21 (eg It may be stored in one or more memories (eg 104, 204) in the form of an instruction/program (eg instruction, executable code) for driving the 102 and 202.
  • instruction/program eg instruction, executable code
  • the one or more processors may be configured by the above-described method and operation (eg proposal 1/2 / 3/ 4/ FIG. 14/ FIG. 15/ FIG. 16, etc.).
  • the one or more processors may control the device to transmit a preamble for random access and to receive a response message for random access corresponding to the preamble.
  • a radio remote control (RRC) connection may be established based on the preamble and the response message.
  • RRC radio remote control
  • the one or more processors receive a plurality of downlink control information (DCI) through the device through a physical downlink control channel (PDCCH), and each A physical downlink shared channel (PDSCH) scheduled by DCI is received in slot n, and HARQ-ACK information corresponding to the PDSCH is received through a physical uplink control channel (PUCCH). It can be controlled to transmit in slot n+k (k is the number of slots).
  • DCI downlink control information
  • PDCCH physical downlink control channel
  • PUCCH physical uplink control channel
  • the resource of the PUCCH may be determined based on a specific DCI among the plurality of DCIs, and the specific DCI is i) an index of a monitoring occasion related to the PDCCH, (ii) a cell index and (iii) each It may be determined based on the index of the control resource set group.
  • the one or more instructions executable by one or more processors May include a command instructing to perform the above-described proposed method and operation (eg, proposal 1/ 2/ 3/ 4/ FIG. 14/ FIG. 15/ FIG. 16, etc.).
  • the one or more instructions executable by one or more processors of the computer-readable medium include a user equipment (UE) transmitting a preamble for random access and corresponding to the preamble. It may include a command instructing to receive a response message for random access.
  • a radio remote control (RRC) connection may be established based on the preamble and the response message.
  • RRC radio remote control
  • the one or more commands receive a plurality of downlink control information (DCI) through a physical downlink control channel (PDCCH), and each DCI A physical downlink shared channel (PDSCH) scheduled by is received in slot n, and HARQ-ACK information corresponding to the PDSCH is received through a physical uplink control channel (PUCCH). It may include a command instructing to transmit at n+k (k is the number of slots).
  • each control resource set associated with the PDCCH through which each DCI is received may correspond to a different control resource set group.
  • the resource of the PUCCH may be determined based on a specific DCI among the plurality of DCIs. The specific DCI may be determined based on i) an index of a monitoring occasion related to the PDCCH, (ii) a cell index, and (iii) an index of each control resource set group.
  • FIG. 17 illustrates a communication system 1 applied to the present invention.
  • a communication system 1 applied to the present invention includes a wireless device, a base station, and a network.
  • the wireless device refers to a device that performs communication using a wireless access technology (eg, 5G NR (New RAT), LTE (Long Term Evolution)), 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 base station and the network may be implemented as a wireless device, and the specific wireless device 200a may operate as a base station/network node to another wireless device.
  • the wireless devices 100a to 100f may be connected to the network 300 through the base station 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 base station 200 / network 300, but may perform direct communication (e.g. sidelink communication) without going through the base station / 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, 150b, and 150c may be established between the wireless devices 100a to 100f / base station 200 and the base station 200 / base station 200.
  • the wireless communication/connection includes various wireless access such as uplink/downlink communication 150a, sidelink communication 150b (or D2D communication), base station communication 150c (eg relay, Integrated Access Backhaul). This can be achieved through technology (eg 5G NR)
  • wireless communication/connections 150a, 150b, 150c the wireless device and the base station/wireless device, and the base station and the base station can transmit/receive radio signals to each other.
  • the wireless communication/connection 150a, 150b, 150c can transmit/receive signals through various physical channels.
  • the first wireless device 100 and the second wireless device 200 may transmit and receive wireless signals through various wireless access technologies (eg, LTE and NR).
  • ⁇ the first wireless device 100, the second wireless device 200 ⁇ is the ⁇ wireless device 100x, the base station 200 ⁇ and/or ⁇ wireless device 100x, wireless device 100x) of FIG. ⁇ 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 descriptions, functions, procedures, suggestions, methods, and/or operational flowcharts disclosed herein.
  • 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 perform some or all of the processes controlled by the processor 102, or instructions for performing the descriptions, functions, procedures, suggestions, methods, and/or operational flow charts disclosed in this document. It can store software code including
  • 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 coupled with the processor 102 and may transmit and/or receive radio signals through one or more antennas 108.
  • the transceiver 106 may include a transmitter and/or a receiver.
  • the transceiver 106 may be mixed with an RF (Radio Frequency) unit.
  • the 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 descriptions, functions, procedures, suggestions, methods, and/or operational flowcharts disclosed herein.
  • 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 perform some or all of the processes controlled by the processor 202, or instructions for performing the descriptions, functions, procedures, suggestions, methods and/or operational flow charts disclosed in this document. It can store software code including
  • 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 used interchangeably with an RF unit.
  • the wireless device may mean a communication modem/circuit/chip.
  • one or more protocol layers may be implemented by one or more processors 102, 202.
  • one or more processors 102, 202 may implement one or more layers (eg, functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP).
  • One or more processors 102, 202 may be configured to generate one or more Protocol Data Units (PDUs) and/or one or more Service Data Units (SDUs) according to the description, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. Can be generated.
  • PDUs Protocol Data Units
  • SDUs Service Data Units
  • One or more processors 102, 202 may generate messages, control information, data, or information according to the description, function, procedure, suggestion, method, and/or operational flow chart disclosed herein.
  • At least one processor (102, 202) generates a signal (e.g., a baseband signal) including PDU, SDU, message, control information, data or information according to the functions, procedures, proposals and/or methods disclosed herein. , It may be provided to one or more transceivers (106, 206).
  • One or more processors 102, 202 may receive signals (e.g., baseband signals) from one or more transceivers 106, 206, and the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed herein PDUs, SDUs, messages, control information, data, or information may be obtained according to the parameters.
  • signals e.g., baseband signals
  • 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
  • the description, functions, procedures, suggestions, methods, and/or operational flow charts disclosed in this document may be implemented using firmware or software, and firmware or software may be implemented to include modules, procedures, functions, and the like.
  • the description, functions, procedures, proposals, methods and/or operational flow charts disclosed in this document are included in one or more processors 102, 202, or stored in one or more memories 104, 204, and are It may be driven by the above processors 102 and 202.
  • the descriptions, functions, procedures, proposals, methods and/or operational flowcharts 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.
  • One or more transceivers (106, 206) may receive user data, control information, radio signals/channels, etc. mentioned in the description, functions, procedures, suggestions, methods and/or operation flow charts disclosed in this document from one or more other devices.
  • one or more transceivers 106 and 206 may be connected to one or more processors 102 and 202, and may transmit and 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 with one or more antennas (108, 208), and one or more transceivers (106, 206) through one or more antennas (108, 208), the description and functionality disclosed in this document. It may be set to transmit and receive user data, control information, radio signals/channels, etc. mentioned in procedures, proposals, methods and/or operation flowcharts.
  • 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.
  • 19 illustrates a signal processing circuit for a transmission signal.
  • the signal processing circuit 1000 may include a scrambler 1010, a modulator 1020, a layer mapper 1030, a precoder 1040, a resource mapper 1050, and a signal generator 1060.
  • the operations/functions of FIG. 19 may be performed in the processors 102 and 202 and/or the transceivers 106 and 206 of FIG. 18.
  • the hardware elements of FIG. 19 may be implemented in the processors 102 and 202 and/or the transceivers 106 and 206 of FIG. 18.
  • blocks 1010 to 1060 may be implemented in the processors 102 and 202 of FIG. 18.
  • blocks 1010 to 1050 may be implemented in the processors 102 and 202 of FIG. 18, and block 1060 may be implemented in the transceivers 106 and 206 of FIG. 18.
  • the codeword may be converted into a wireless signal through the signal processing circuit 1000 of FIG. 19.
  • the codeword is an encoded bit sequence of an information block.
  • the information block may include a transport block (eg, a UL-SCH transport block, a DL-SCH transport block).
  • the radio signal may be transmitted through various physical channels (eg, PUSCH, PDSCH).
  • the codeword may be converted into a scrambled bit sequence by the scrambler 1010.
  • the scramble sequence used for scramble is generated based on an initialization value, and the initialization value may include ID information of a wireless device.
  • the scrambled bit sequence may be modulated by the modulator 1020 into a modulation symbol sequence.
  • the modulation scheme may include pi/2-Binary Phase Shift Keying (pi/2-BPSK), m-Phase Shift Keying (m-PSK), m-Quadrature Amplitude Modulation (m-QAM), and the like.
  • the complex modulation symbol sequence may be mapped to one or more transport layers by the layer mapper 1030.
  • the modulation symbols of each transport layer may be mapped to the corresponding antenna port(s) by the precoder 1040 (precoding).
  • the output z of the precoder 1040 can be obtained by multiplying the output y of the layer mapper 1030 by the N*M precoding matrix W.
  • N is the number of antenna ports
  • M is the number of transmission layers.
  • the precoder 1040 may perform precoding after performing transform precoding (eg, DFT transform) on complex modulation symbols. Also, the precoder 1040 may perform precoding without performing transform precoding.
  • the resource mapper 1050 may map modulation symbols of each antenna port to a time-frequency resource.
  • the time-frequency resource may include a plurality of symbols (eg, CP-OFDMA symbols, DFT-s-OFDMA symbols) in the time domain, and may include a plurality of subcarriers in the frequency domain.
  • CP Cyclic Prefix
  • DAC Digital-to-Analog Converter
  • the signal processing process for the received signal in the wireless device may be configured as the reverse of the signal processing process 1010 to 1060 of FIG. 19.
  • a wireless device eg, 100 and 200 in FIG. 18
  • the received radio signal may be converted into a baseband signal through a signal restorer.
  • the signal restorer may include a frequency downlink converter, an analog-to-digital converter (ADC), a CP canceller, and a Fast Fourier Transform (FFT) module.
  • ADC analog-to-digital converter
  • FFT Fast Fourier Transform
  • the baseband signal may be reconstructed into a codeword through a resource de-mapper process, a postcoding process, a demodulation process, and a de-scramble process.
  • a signal processing circuit for a received signal may include a signal restorer, a resource demapper, a postcoder, a demodulator, a descrambler, and a decoder.
  • the wireless device 20 shows another example of a wireless device applied to the present invention.
  • the wireless device may be implemented in various forms according to use-examples/services (see FIG. 17).
  • the wireless devices 100 and 200 correspond to the wireless devices 100 and 200 of FIG. 18, and various elements, components, units/units, and/or modules ) Can be composed of.
  • 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.
  • communication circuitry 112 may include one or more processors 102 and 202 and/or one or more memories 104 and 204 of FIG. 18.
  • the transceiver(s) 114 may include one or more transceivers 106,206 and/or one or more antennas 108,208 of FIG. 17.
  • 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 (Figs. 17, 100a), vehicles (Figs. 17, 100b-1, 100b-2), XR devices (Figs. 17, 100c), portable devices (Figs. (Figs. 17, 100e), IoT devices (Figs. 17, 100f), digital broadcasting terminals, hologram devices, public safety devices, MTC devices, medical devices, fintech devices (or financial devices), security devices, climate/environment devices, It may be implemented in the form of an AI server/device (FIGS. 17 and 400), a base station (FIGS. 17 and 200), and a network node.
  • 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 connected to each other through a wired interface, or at least part of them 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.
  • Portable devices may include smart phones, smart pads, wearable devices (eg, smart watches, smart glasses), and portable computers (eg, notebook computers).
  • the portable device may be referred to as a mobile station (MS), a user terminal (UT), a mobile subscriber station (MSS), a subscriber station (SS), an advanced mobile station (AMS), or a wireless terminal (WT).
  • MS mobile station
  • UT user terminal
  • MSS mobile subscriber station
  • SS subscriber station
  • AMS advanced mobile station
  • WT wireless terminal
  • the portable device 100 includes an antenna unit 108, a communication unit 110, a control unit 120, a memory unit 130, a power supply unit 140a, an interface unit 140b, and an input/output unit 140c. ) Can be included.
  • the antenna unit 108 may be configured as a part of the communication unit 110.
  • Blocks 110 to 130/140a to 140c correspond to blocks 110 to 130/140 of FIG. 20, respectively.
  • the communication unit 110 may transmit and receive signals (eg, data, control signals, etc.) with other wireless devices and base stations.
  • the controller 120 may perform various operations by controlling components of the portable device 100.
  • the controller 120 may include an application processor (AP).
  • the memory unit 130 may store data/parameters/programs/codes/commands required for driving the portable device 100. Also, the memory unit 130 may store input/output data/information, and the like.
  • the power supply unit 140a supplies power to the portable device 100 and may include a wired/wireless charging circuit, a battery, and the like.
  • the interface unit 140b may support connection between the portable device 100 and other external devices.
  • the interface unit 140b may include various ports (eg, audio input/output ports, video input/output ports) for connection with external devices.
  • the input/output unit 140c may receive or output image information/signal, audio information/signal, data, and/or information input from a user.
  • the input/output unit 140c may include a camera, a microphone, a user input unit, a display unit 140d, a speaker, and/or a haptic module.
  • the input/output unit 140c acquires information/signals (eg, touch, text, voice, image, video) input from the user, and the obtained information/signals are stored in the memory unit 130. Can be saved.
  • the communication unit 110 may convert information/signals stored in the memory into wireless signals, and may directly transmit the converted wireless signals to other wireless devices or to a base station.
  • the communication unit 110 may restore the received radio signal to the original information/signal. After the restored information/signal is stored in the memory unit 130, it may be output in various forms (eg, text, voice, image, video, heptic) through the input/output unit 140c.
  • an embodiment of the present invention may be implemented by various means, for example, hardware, firmware, software, or a combination thereof.
  • an embodiment of the present invention provides one or more ASICs (application specific integrated circuits), DSPs (digital signal processors), DSPDs (digital signal processing devices), PLDs (programmable logic devices), and FPGAs ( field programmable gate arrays), processors, controllers, microcontrollers, microprocessors, etc.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGAs field programmable gate arrays
  • processors controllers, microcontrollers, microprocessors, etc.
  • an embodiment of the present invention may be implemented in the form of a module, procedure, or function that performs the functions or operations described above.
  • the software code may be stored in a memory and driven by a processor.
  • the memory may be located inside or outside the processor, and may exchange data with the processor through various known means.
  • the method of transmitting/receiving HARQ-ACK information in the wireless communication system of the present invention has been described centering on an example applied to a 3GPP LTE/LTE-A system and a 5G system (New RAT system). It is possible.

Landscapes

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

Abstract

La présente invention concerne un procédé d'émission et de réception d'informations HARQ-ACK dans un système de communication sans fil et un dispositif associé. Spécifiquement, un procédé pour un UE pour rapporter des informations HARQ-ACK dans un système de communication sans fil comprend les étapes consistant à : transmettre un préambule pour un accès aléatoire ; recevoir un message de réponse pour l'accès aléatoire correspondant au préambule, une connexion de commande à distance radio (RRC) est établie sur la base du préambule et du message de réponse ; recevoir une pluralité d'éléments d'informations de commande de liaison descendante (DCI) par l'intermédiaire d'un canal physique de contrôle descendant (PDCCH), des ensembles de ressources de commande associés au PDCCH, à travers lesquels les éléments de DCI sont reçus, correspondent à différents groupes d'ensembles de ressources de commande ; recevoir, dans une fente n, un canal physique partagé descendant (PDSCH) ordonnancée au moyen de chaque élément de DCI ; et transmettre les informations HARQ-ACK, correspondant au PDSCH, dans une fente n+k à travers un canal physique de contrôle de liaison montante (PUCCH), k étant le nombre de fentes, la ressource du PUCCH étant déterminée sur la base de DCI spécifiques parmi la pluralité d'éléments de DCI, et les DCI spécifiques étant déterminées sur la base i) d'un indice d'une occasion de surveillance concernant le PDCCH, (ii) d'un indice de cellule, et (iii) de l'indice de chaque groupe d'ensembles de ressources de commande.
PCT/KR2020/009190 2019-07-12 2020-07-13 Procédé pour émettre et recevoir des informations harq-ack dans un système de communication sans fil et dispositif associé WO2021010705A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
KR10-2019-0084659 2019-07-12
KR20190084659 2019-07-12
KR20190123435 2019-10-04
KR10-2019-0123435 2019-10-04

Publications (1)

Publication Number Publication Date
WO2021010705A1 true WO2021010705A1 (fr) 2021-01-21

Family

ID=74210939

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2020/009190 WO2021010705A1 (fr) 2019-07-12 2020-07-13 Procédé pour émettre et recevoir des informations harq-ack dans un système de communication sans fil et dispositif associé

Country Status (1)

Country Link
WO (1) WO2021010705A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115118404A (zh) * 2021-03-22 2022-09-27 北京紫光展锐通信技术有限公司 Harq-ack的反馈方法及相关产品
WO2022240132A1 (fr) * 2021-05-10 2022-11-17 엘지전자 주식회사 Procédé, équipement utilisateur, dispositif de traitement et support de stockage pour transmettre des informations de harq-ack, et procédé et station de base pour recevoir des informations de harq-ack
WO2023003439A1 (fr) * 2021-07-23 2023-01-26 Samsung Electronics Co., Ltd. Procédé de communication, appareil de communication, dispositif électronique et support de stockage lisible par ordinateur
WO2023195779A1 (fr) * 2022-04-07 2023-10-12 엘지전자 주식회사 Procédé de transmission/réception de liaison montante dans un système de communication sans fil, et dispositif associé
WO2023211067A1 (fr) * 2022-04-27 2023-11-02 삼성전자 주식회사 Procédé et dispositif permettant une transmission simultanée de liaison montante avec un panneau multiple dans un système de communication sans fil
WO2024088397A1 (fr) * 2022-10-28 2024-05-02 上海朗帛通信技术有限公司 Procédé et dispositif pour nœud utilisé dans des communications sans fil

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150163797A1 (en) * 2012-01-06 2015-06-11 Samsung Electronics Co., Ltd. Method for transmitting harq-ack information based on transmission diversity
KR101884353B1 (ko) * 2011-12-20 2018-08-01 엘지전자 주식회사 무선 통신 시스템에서 랜덤 접속 과정의 수행 방법 및 장치
KR20190038991A (ko) * 2017-10-02 2019-04-10 주식회사 케이티 차세대 무선망을 위한 harq ack/nack 피드백 정보를 송수신하는 방법 및 장치

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101884353B1 (ko) * 2011-12-20 2018-08-01 엘지전자 주식회사 무선 통신 시스템에서 랜덤 접속 과정의 수행 방법 및 장치
US20150163797A1 (en) * 2012-01-06 2015-06-11 Samsung Electronics Co., Ltd. Method for transmitting harq-ack information based on transmission diversity
KR20190038991A (ko) * 2017-10-02 2019-04-10 주식회사 케이티 차세대 무선망을 위한 harq ack/nack 피드백 정보를 송수신하는 방법 및 장치

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
NTT DOCOMO, INC.: "On HARQ-ACK feedback", 3GPP DRAFT; R1-1807067, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Busan, Korea; 20180521 - 20180525, R1-1807067, 12 May 2018 (2018-05-12), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051462888 *
OPPO: "Remaining details on HARQ-ACK transmission", 3GPP DRAFT; R1-1806838, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Busan, Korea; 20180521 - 20180525, R1-1806838, 11 May 2018 (2018-05-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051461990 *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115118404A (zh) * 2021-03-22 2022-09-27 北京紫光展锐通信技术有限公司 Harq-ack的反馈方法及相关产品
WO2022240132A1 (fr) * 2021-05-10 2022-11-17 엘지전자 주식회사 Procédé, équipement utilisateur, dispositif de traitement et support de stockage pour transmettre des informations de harq-ack, et procédé et station de base pour recevoir des informations de harq-ack
WO2023003439A1 (fr) * 2021-07-23 2023-01-26 Samsung Electronics Co., Ltd. Procédé de communication, appareil de communication, dispositif électronique et support de stockage lisible par ordinateur
WO2023195779A1 (fr) * 2022-04-07 2023-10-12 엘지전자 주식회사 Procédé de transmission/réception de liaison montante dans un système de communication sans fil, et dispositif associé
WO2023211067A1 (fr) * 2022-04-27 2023-11-02 삼성전자 주식회사 Procédé et dispositif permettant une transmission simultanée de liaison montante avec un panneau multiple dans un système de communication sans fil
WO2024088397A1 (fr) * 2022-10-28 2024-05-02 上海朗帛通信技术有限公司 Procédé et dispositif pour nœud utilisé dans des communications sans fil

Similar Documents

Publication Publication Date Title
WO2021010707A1 (fr) Procédé permettant de transmettre et de recevoir des informations harq-ack dans un système de communication sans fil et dispositif associé
WO2021010710A1 (fr) Procédé et dispositif de transmission/réception d'informations de harq-ack dans un système de communication sans fil
WO2020222606A1 (fr) Procédé d'émission et de réception de signal de référence de suivi de phase dans un système de communication sans fil, et appareil associé
WO2020167018A1 (fr) Procédé de transmission et de réception de données dans un système de communication sans fil et appareil associé
WO2021029748A1 (fr) Procédé de transmission/réception de données de liaison descendante dans un système de communication sans fil, et dispositif associé
WO2021029755A1 (fr) Procédé permettant d'effectuer une procédure de reprise après défaillance de faisceau dans un système de communication sans fil, et dispositif associé
WO2021040353A1 (fr) Procédé permettant de transmettre ou de recevoir un canal de liaison montante dans un système de communication sans fil, et dispositif associé
WO2021029738A1 (fr) Procédé de transmission/réception d'un canal de liaison montante dans un système de communication sans fil, et appareil associé
WO2020209597A1 (fr) Appareil et procédé de rapport d'informations d'état de canal dans un système de communication sans fil
WO2020162728A1 (fr) Procédé et dispositif d'émission et de réception d'un canal physique partagé de liaison montante dans un système de communication sans fil
WO2020222567A1 (fr) Procédé permettant de transmettre et de recevoir un canal de liaison montante dans un système de communication sans fil, et dispositif associé
WO2021029749A1 (fr) Procédé de transmission et de réception de canal physique partagé de liaison descendante dans un système de communication sans fil, et dispositif s'y rapportant
WO2020263049A1 (fr) Procédé d'exécution de procédure de récupération de défaillance de faisceau dans un système de communication sans fil et dispositif associé
WO2021066635A1 (fr) Procédé de transmission et de réception de canal physique partagé de liaison descendante dans un système de communication sans fil, et dispositif s'y rapportant
WO2020122687A1 (fr) Procédé d'émission et de réception de données dans un système de communication sans fil et appareil associé
WO2020122686A1 (fr) Procédé de transmission et de réception de données dans un système de communication sans fil et dispositif associé
WO2021020847A1 (fr) Procédé et dispositif pour la transmission et la réception de canal physique partagé de liaison montante dans un système de communication sans fil
WO2021066631A1 (fr) Procédé de transmission/réception de pdsch dans un système de communication sans fil et dispositif associé
WO2021066630A1 (fr) Procédé d'émission et de réception de signal de référence de suivi de phase dans un système de communication sans fil, et appareil associé
WO2021034086A1 (fr) Procédé pour transmettre/recevoir des informations de commande de liaison descendante dans un système de communication sans fil, et dispositif associé
WO2020222605A1 (fr) Procédé d'émission et de réception de canal de données dans un système de communication sans fil, et appareil associé
WO2020197357A1 (fr) Procédé d'émission et de réception de signal de référence de sondage dans un système de communications sans fil, et dispositif correspondant
WO2021066622A1 (fr) Procédé d'émission et de réception de signal de référence de suivi de phase dans un système de communication sans fil, et appareil associé
WO2021029752A1 (fr) Procédé de transmission et de réception de données de liaison descendante dans un système de communications sans fil, et dispositif associé
WO2020197286A1 (fr) Procédé d'émission/réception de données dans un système de communication sans fil et dispositif associé

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: 20839709

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: 20839709

Country of ref document: EP

Kind code of ref document: A1