EP4216644A1 - Procédé et dispositif de transmission d'informations de commande pour une communication coopérative de réseau d'un système de communication sans fil - Google Patents

Procédé et dispositif de transmission d'informations de commande pour une communication coopérative de réseau d'un système de communication sans fil Download PDF

Info

Publication number
EP4216644A1
EP4216644A1 EP21883358.0A EP21883358A EP4216644A1 EP 4216644 A1 EP4216644 A1 EP 4216644A1 EP 21883358 A EP21883358 A EP 21883358A EP 4216644 A1 EP4216644 A1 EP 4216644A1
Authority
EP
European Patent Office
Prior art keywords
pucch
information
resource
transmission
dci
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP21883358.0A
Other languages
German (de)
English (en)
Other versions
EP4216644A4 (fr
Inventor
Euichang Jung
Suha Yoon
Jinhyun PARK
Youngrok JANG
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Samsung Electronics Co Ltd
Original Assignee
Samsung Electronics Co Ltd
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 Samsung Electronics Co Ltd filed Critical Samsung Electronics Co Ltd
Publication of EP4216644A1 publication Critical patent/EP4216644A1/fr
Publication of EP4216644A4 publication Critical patent/EP4216644A4/fr
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—TPC
    • H04W52/30—TPC using constraints in the total amount of available transmission power
    • H04W52/32—TPC of broadcast or control channels
    • H04W52/325—Power control of control or pilot channels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • 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/022—Site diversity; Macro-diversity
    • H04B7/024—Co-operative use of antennas of several sites, e.g. in co-ordinated multipoint or co-operative multiple-input multiple-output [MIMO] systems
    • 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
    • H04B7/0697—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using spatial multiplexing
    • 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/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • 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/1607—Details of the supervisory signal
    • H04L1/1671—Details of the supervisory signal the supervisory signal being transmitted together with control information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0014—Three-dimensional division
    • H04L5/0023—Time-frequency-space
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—TPC
    • H04W52/06—TPC algorithms
    • H04W52/08—Closed loop power control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—TPC
    • H04W52/06—TPC algorithms
    • H04W52/14—Separate analysis of uplink or downlink
    • H04W52/146—Uplink power control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—TPC
    • H04W52/54—Signalisation aspects of the TPC commands, e.g. frame structure
    • H04W52/58—Format of the TPC bits
    • 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
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—TPC
    • H04W52/38—TPC being performed in particular situations
    • H04W52/40—TPC being performed in particular situations during macro-diversity or soft handoff

Definitions

  • the disclosure relates to a wireless communication system, and more specifically, to a method and apparatus for a terminal to transmit control information to multiple transmission points/panels/beams for cooperative communication between multiple transmission points/panels/beams.
  • the 5G or pre-5G communication system is also called a ⁇ Beyond 4G Network' or a 'Post Long-Term Evolution (LTE) System.
  • the 5G communication system is considered to be implemented in higher frequency (millimeter (mm) Wave) bands, e.g., 60 gigahertz (GHz) bands, so as to accomplish higher data rates.
  • the beamforming, massive multiple-input multiple-output (MIMO), Full Dimensional MIMO (FD-MIMO), array antenna, an analog beam forming, large scale antenna techniques are discussed in 5G communication systems.
  • MIMO massive multiple-input multiple-output
  • FD-MIMO Full Dimensional MIMO
  • array antenna an analog beam forming, large scale antenna techniques.
  • system network improvement is under way based on advanced small cells, cloud Radio Access Networks (RANs), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, moving network, cooperative communication, Coordinated Multi-Points (CoMP), reception-end interference cancellation and the like.
  • RANs cloud Radio Access Networks
  • D2D device-to-device
  • CoMP Coordinated Multi-Points
  • Hybrid frequency shift keying (FSK) and quadrature amplitude modulation (QAM) Modulation (FQAM) and sliding window superposition coding (SWSC) as an advanced coding modulation (ACM), and filter bank multi carrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) as an advanced access technology have been developed.
  • the Internet which is a human centered connectivity network where humans generate and consume information
  • IoT Internet of Things
  • IoE Internet of Everything
  • sensing technology “wired/wireless communication and network infrastructure,” “service interface technology,” and “Security technology”
  • M2M Machine-to-Machine
  • MTC Machine Type Communication
  • IoT Internet technology services
  • IoT may be applied to a variety of fields including smart home, smart building, smart city, smart car or connected cars, smart grid, health care, smart appliances and advanced medical services through convergence and combination between existing Information Technology (IT) and various industrial applications.
  • IT Information Technology
  • 5G communication systems to IoT networks.
  • technologies such as a sensor network, Machine Type Communication (MTC), and Machine-to-Machine (M2M) communication may be implemented by beamforming, MIMO, and array antennas.
  • MTC Machine Type Communication
  • M2M Machine-to-Machine
  • Application of a cloud Radio Access Network (RAN) as the above-described Big Data processing technology may also be considered to be as an example of convergence between the 5G technology and the IoT technology.
  • RAN Radio Access Network
  • a method for a terminal to transmit control information to a plurality of transmission points/panels/beams and an apparatus are required for network coordination in a wireless communication system.
  • the disclosure provides a method for a terminal to transmit control information to multiple transmission points/panels/nodes/beams for network coordination communication in a wireless communication system.
  • the disclosure provides a method for configuring parameters related to power control and determining transmission power of PUCCH so that a terminal can control the transmission power of the PUCCH for each transmission point/panel/beam/node.
  • the disclosure provides a method for repeatedly transmitting PDCCHs for each transmission point/panel/beam/node.
  • the method includes receiving configuration information related to a physical uplink control channel (PUCCH) power control through a radio resource control (RRC) signaling; identifying first information for the PUCCH power control associated with a first node, and second information for the PUCCH power control associated with a second node, based on the configuration information; receiving downlink control information (DCI), which is associated with a transmit power control (TPC) command and includes a first bit field corresponding to the first information and a second bit field corresponding to the second information; determining transmission power of the PUCCH based on the first information, the second information, and the DCI; and transmitting the PUCCH based on the determined transmission power.
  • PUCCH physical uplink control channel
  • RRC radio resource control
  • the method according to an embodiment of the disclosure may further include receiving activation information for activating the configuration information for a PUCCH resource through medium access control-control element (MAC-CE) signaling, and an identifier of the PUCCH resource and a plurality of configuration information identifiers corresponding to the PUCCH resource may be indicated based on the activation information.
  • MAC-CE medium access control-control element
  • the configuration information may include the first information associated with the first node and the second information associated with the second node, each of the first information and the second information may include an identifier of each information and a closed loop index, and a first closed loop index included in the first information and a second closed loop index included in the second information may be configured to different values.
  • transmitting the PUCCH based on the determined transmission power may include transmitting the PUCCH in a first resource through the first node using the transmission power determined based on the first information and the DCI; transmitting the PUCCH in a second resource through the second node using the transmission power determined based on the second information and the DCI; and locating the first resource and the second resource in different slots or non-overlapping time intervals within one slot.
  • the method according to an embodiment of the disclosure may further include receiving information on a number of repetition transmissions of the PUCCH, and the PUCCH may be repeatedly transmitted in a non-overlapping time resource as many times as the number of repetition transmissions, and the transmission power determined based on the first information and the DCI may be applied to odd-numbered PUCCH transmission, and the transmission power determined based on the second information and the DCI is applied to even-numbered PUCCH transmission.
  • the method includes transmitting configuration information related to power control of a physical uplink control channel (PUCCH) through a radio resource control (RRC) signaling; configuring first information for the PUCCH power control associated with a first node and second information for the PUCCH power control associated with a second node, based on the configuration information; transmitting downlink control information (DCI), which is associated with a transmit power control (TPC) command and includes a first bit field corresponding to the first information and a second bit field corresponding to the second information; and receiving the PUCCH to which transmission power determined based on the first information, the second information, and the DCI is applied.
  • DCI downlink control information
  • TPC transmit power control
  • a terminal transmits control information for each transmission point/panel/beam/node, so that reliability can be improved as compared to transmission of control information to a single transmission/point/panel/node/beam.
  • a terminal may transmit PUCCH by controlling transmission power for each transmission point/panel/beam/node.
  • Each block of the flowcharts and/or block diagrams, and combinations of blocks in the flowcharts and/or block diagrams, can be implemented by computer program instructions.
  • These computer program instructions may be provided to a processor of a general-purpose computer, special purpose computer, or other programmable data processing apparatus, such that the instructions that are executed via the processor of the computer or other programmable data processing apparatus implement the functions/acts specified in the flowcharts and/or block diagrams.
  • These computer program instructions may also be stored in a non-transitory computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the non-transitory computer-readable memory produce articles of manufacture embedding instructions that implement the function/act specified in the flowcharts and/or block diagrams.
  • the computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions that are executed on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowcharts and/or block diagrams.
  • the respective block diagrams may illustrate parts of modules, segments, or codes including at least one or more executable instructions for performing specific logic function(s).
  • the functions of the blocks may be performed in a different order in several modifications. For example, two successive blocks may be performed substantially at the same time, or they may be performed in reverse order according to their functions.
  • the term "module” means, but is not limited to, a software or hardware component, such as a field programmable gate array (FPGA) or application specific integrated circuit (ASIC), which performs certain tasks.
  • a module may advantageously be configured to reside on the addressable storage medium and configured to be executed on one or more processors.
  • a module may include components, such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables.
  • the functionalities of the components and modules may be combined into fewer components and modules or further separated into more components and modules.
  • the components and modules may be implemented such that they execute one or more central processing units (CPUs) in a device or a secure multimedia card.
  • CPUs central processing units
  • BS base station
  • eNB evolved Node B
  • UE user equipment
  • MS mobile station
  • cellular phone a smartphone
  • computer a multimedia system with a communication function
  • the present disclosure is a communication technique that converges a 5G (5th generation) communication system with IoT (Internet of Things) technology to support a higher data transmission rate after the 4G (4th generation) system and its system.
  • the disclosure provides a technology for a terminal to receive broadcast information from a base station in a wireless communication system.
  • the disclosure is applicable to intelligent services (e.g., smart homes, smart buildings, smart cities, smart cars or connected car, health care, digital education, retail, and security and safety-related services) based on the 5G communication technology and the IoT-related technology.
  • HSPA high speed packet access
  • LTE long speed packet access
  • E-UTRA evolved universal terrestrial radio access
  • LTE-A LTE-Advanced
  • HRPD high rate packet data
  • UMB ultra mobile broadband
  • IEEE Institute of Electrical and Electronics Engineers
  • an LTE system uses orthogonal frequency division multiplexing (OFDM) in the downlink and single carrier frequency division multiple access (SC-FDMA) in the uplink.
  • OFDM orthogonal frequency division multiplexing
  • SC-FDMA single carrier frequency division multiple access
  • uplink (UL) denotes a radio transmission path from a terminal (or UE or MS) to a base station (gNB)
  • downlink (DL) denotes a radio transmission path from the base station to the terminal.
  • Such multiple access schemes are characterized by allocating the time-frequency resources for transmitting user-specific data and control information without overlapping each other, i.e., maintaining orthogonality, in order to distinguish among user-specific data and control information.
  • the 5G communication system should meet various requirements of services demanded by users and service providers.
  • the services to be supported by 5G systems may be categorized into three categories: enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable and low-latency communications (URLLC).
  • eMBB enhanced mobile broadband
  • mMTC massive machine type communications
  • URLLC ultra-reliable and low-latency communications
  • eMBB is intended to provide exceptionally high data rate in comparison with those supported by the legacy LTE, LTE-A, and LTE-A Pro.
  • the eMBB should increase the peak data rate up to 20 Gbps in DL and 10 Gbps in UL per base station.
  • eMBB should improve the user-perceived data rate.
  • signal transmission/reception technologies including a MIMO technique should be improved.
  • the data rate requirements for 5G communication systems may be met by use of a frequency bandwidth broader than 20 MHz in the frequency band of 3 to 6 GHz or above 6 GHz instead of the current LTE band of 2 GHz.
  • mMTC is intended to support application services for IoT.
  • massive access resources should be secured for terminals within a cell, terminal coverage and battery life span should be improved, and device manufacturing cost should be reduced.
  • the IoT services should be designed to support a large number of terminals (e.g., 1,000,000 terminals/km2) within a cell in consideration of the nature of the IoT terminals that are attached to various sensors and devices for providing a communication function.
  • the mMTC terminals will likely be located in coverage holes such as a basement of a building, which requires broader coverage in comparison with other services being supported in the 5G communication system.
  • the mMTC terminals that are characterized by their low prices and battery replacement difficulty should be designed to have very long battery lifetime.
  • URLLC is targeted for mission-critical cellular-based communication services such as remote robots and machinery control, industrial automation, unmanned aerial vehicles, remote health care, and emergency alert services that require ultra-low latency and ultra-high reliability. Accordingly, a URLLC service requires an ultra-low latency and ultra-high reliability. For example, a URLLC service should meet the requirements of air-interface latency lower than 0.5 ms and a packet error rate less than or equal to 10-5. In order to support the URLLC services, the 5G system should support transmit time intervals (TTI) shorter than those of other services and assign broad resources in the frequency band.
  • TTI time intervals
  • the 5G system should support a short TTI for the URLLC, which is shorter than that for other services, and allocate broad resources in a frequency band to secure reliability of the communication link.
  • the services may categorized into mMTC, URLLC, and eMBB, the disclosure is not limited by such categorization.
  • the above-described services to be supported by 5G systems should be provided within one framework in a mixed manner.
  • the services may be provided and controlled in a systematic manner instead of a service-specific manner.
  • the disclosure relates to a method and apparatus for reporting channel state information to increase power saving efficiency of a terminal in a wireless communication system.
  • the power saving effect can be further improved by optimizing a method for reporting channel state information accordingly.
  • FIG. 1 is a diagram illustrating a basic structure of a time-frequency domain in a mobile communication system, according to an embodiment of the disclosure.
  • a horizontal axis represents a time domain
  • a vertical axis represents a frequency domain
  • a basic unit of resources in the time-frequency domain is a resource element (RE) 1-01, which may be defined as one orthogonal frequency division multiplexing (OFDM) symbol 1-02 on the time axis and one subcarrier 1-03 on the frequency axis.
  • OFDM orthogonal frequency division multiplexing
  • N sc RB e.g., twelve
  • consecutive REs may constitute one resource block (RB) 1-04.
  • RB resource block
  • a plurality of OFDM symbols may constitute one subframe 1-10.
  • FIG. 2 illustrates a diagram for explaining a frame, subframe and slot structure of a next generation mobile communication system according to an embodiment of the disclosure.
  • one frame 2-00 may composed of one or more subframes 2-01, and one subframe may be composed of one or more slots 2-02.
  • one frame 2-00 may be defined as 10 ms.
  • One subframe 2-01 may be defined as 1 ms, and thus one frame 2-00 may be composed of a total of 10 subframes 2-01.
  • One slot 2-02 or 2-03 may be defined as 14 OFDM symbols (i.e., the number of symbols per slot ( N symb slot ) is 14).
  • One subframe 2-01 may consist of one or a plurality of slots 2-02 or 2-03, and the number of slots 2-02 or 2-03 per one subframe 2-01 may vary depending on a setting value ⁇ 2-04 or 2-05 for a subcarrier spacing.
  • N slot subframe , ⁇ and N slot frame , ⁇ according to each subcarrier spacing setting ⁇ may be defined as Table 1 below. [Table 1] ⁇ N symb slot N slot frame , ⁇ N slot subframe 0 14 10 1 1 14 20 2 2 14 40 4 3 14 80 8 4 14 160 16 5 14 320 32
  • one component carrier (CC) or serving cell may be configured with up to 250 or more RBs. Therefore, when the terminal always receives the entire serving cell bandwidth, such as in LTE, power consumption of the terminal may be extreme, and to solve this problem, the base station configures one or more bandwidth parts (BWP) for the terminal. Thus, it is possible to support a terminal to change a reception area within a cell.
  • the base station may set 'initial BWP', which is the bandwidth of CORESET #0 (or common search space, CSS), to the terminal through the MIB.
  • the base station may configure an initial BWP (first BWP) of the terminal through RRC signaling and notify at least one or more pieces of BWP configuration information that may be indicated through future downlink control information (DCI).
  • the base station may indicate which band the terminal will use by notifying the BWP ID through DCI. If the terminal does not receive DCI from the currently allocated BWP for more than a specific time, the terminal returns to 'default BWP' and attempts DCI reception.
  • FIG. 3 illustrates an example of bandwidth part configuration in a wireless communication system, according to an embodiment of the disclosure.
  • FIG 3 illustrates an example that a UE bandwidth 3-00 is configured as two bandwidth parts, that is, a bandwidth part #1 (BWP#1) 3-05 and a bandwidth part #2 (BWP#2) 3-10.
  • a base station may configure one or a plurality of bandwidth parts to a UE and configure the following information as [Table 2] for each bandwidth part.
  • the above example is not considered as limitation, and in addition to the above configuration information, various parameters related to the bandwidth part may be configured in the UE.
  • the above information may be delivered by the base station to the UE through higher layer signaling, for example, radio resource control (RRC) signaling.
  • RRC radio resource control
  • the configured one or at least one among the plurality of configured bandwidth parts may be activated. Whether to activate the configured bandwidth part may be semi-statically delivered from the base station to the UE through RRC signaling or dynamically delivered through MAC CE (control element) or downlink control information (DCI).
  • MAC CE control element
  • DCI downlink control information
  • the UE before RRC connection may receive configuration of an initial bandwidth part (initial BWP) for initial access from the base station through a master information block (MIB).
  • MIB master information block
  • the UE may receive configuration information about a search space and a control resource set (CORESET) through which a physical downlink control channel (PDCCH) (or downlink control information (DCI)) for receiving system information (which may correspond to remaining system information (RMSI) or system information block 1 (SIB1)) required for initial access can be transmitted.
  • PDCH physical downlink control channel
  • DCI downlink control information
  • SIB1 system information block 1
  • the base station may notify, to the UE through the MIB, configuration information such as frequency allocation information, time allocation information, and numerology for the control resource set #0.
  • the base station may notify, to the UE through the MIB, configuration information about a monitoring period and occurrence for the control resource set #0, that is, configuration information about the search space #0.
  • the UE may regard, as an initial bandwidth part for initial access, a frequency range configured with the control resource set #0 acquired from the MIB. In this case, the identity (ID) of the initial bandwidth part may be regarded as 0.
  • the configuration of the bandwidth part supported by the next generation mobile communication system may be used for various purposes.
  • the base station may configure a frequency location (configuration information 2) of the bandwidth part to the UE, so that the UE can transmit and receive data at a specific frequency location within the system bandwidth.
  • the base station may configure a plurality of bandwidth parts to the UE for the purpose of supporting different numerologies. For example, in order to support both data transmission and reception using a subcarrier spacing of 15 kHz and a subcarrier spacing of 30 kHz to a certain UE, two bandwidth parts may be configured with the subcarrier spacings of 15 kHz and 30 kHz, respectively. Different bandwidth parts may be subjected to frequency division multiplexing (FDMA), and in order to transmit/receive data at a specific subcarrier spacing, a bandwidth part configured with the corresponding subcarrier spacing may be activated.
  • FDMA frequency division multiplexing
  • the base station may configure bandwidth parts having bandwidths of different sizes to the UE. For example, if the UE supports a very large bandwidth, for example, a bandwidth of 100 MHz, and always transmits and receives data using that bandwidth, very large power consumption may occur. In particular, monitoring an unnecessary downlink control channel with a large bandwidth of 100 MHz in a situation that there is no traffic may be very inefficient in terms of power consumption.
  • the base station may configure a bandwidth part of a relatively small bandwidth, for example, a bandwidth part of 20 MHz, to the UE. In the absence of traffic, the UE may perform a monitoring operation in the 20 MHz bandwidth part, and when data occurs, the UE may transmit/receive data in the 100 MHz bandwidth part under the instruction of the base station.
  • terminals before RRC connection may receive configuration information on the initial bandwidth part through a master information block (MIB) in an initial access step. More specifically, the terminal may receive a control region (Control Resource Set, CORESET) for a downlink control channel in which a DCI scheduling a System Information Block (SIB) can be transmitted from the MIB of a Physical Broadcast Channel (PBCH).
  • the bandwidth of the control region set as the MIB may be regarded as an initial bandwidth part, and the terminal may receive the PDSCH through which the SIB is transmitted through the set initial bandwidth part.
  • the initial bandwidth part may be used for other system information (Other System Information, OSI), paging, and random access in addition to the purpose of receiving the SIB.
  • OSI System Information
  • SS synchronization signal
  • PBCH next-generation mobile communication system
  • the SS/PBCH block may refer to a physical layer channel block composed of a primary SS (PSS), a secondary SS (SSS), and a PBCH. Specifically, it is as follows.
  • the UE may detect the PSS and the SSS in the initial access stage and decode the PBCH.
  • the UE may acquire the MIB from the PBCH, and a control resource set #0 (which may correspond to a control resource set having a control resource set index of 0) may be configured therefrom.
  • the UE may perform monitoring on the control resource set #0, assuming that a selected SS/PBCH block and a demodulation reference signal (DMRS) transmitted in the control resource set #0 are in quasi co-location (QCL).
  • DMRS demodulation reference signal
  • the UE may receive system information via downlink control information transmitted in the control resource set #0. From the received system information, the UE may acquire configuration information related to a random access channel (RACH) required for the initial access.
  • RACH random access channel
  • the UE may transmit a physical RACH (PRACH) to the base station in consideration of the selected SS/PBCH index, and the base station that receives the PRACH may acquire information on the SS/PBCH block index selected by the UE.
  • PRACH physical RACH
  • the base station can know that the UE has selected a certain block from among the SS/PBCH blocks and is monitoring the control resource set #0 related thereto.
  • DCI downlink control information
  • 5G or NR system next-generation mobile communication system
  • Scheduling information for uplink data (or physical uplink shared channel (PUSCH)) or downlink data (or physical downlink shared channel (PDSCH)) in a next-generation mobile communication system (5G or NR system) may be transmitted from the base station to the terminal through DCI.
  • the UE may monitor the DCI format for fallback and the DCI format for non-fallback with respect to PUSCH or PDSCH.
  • the fallback DCI format may be composed of a fixed field predefined between the base station and the terminal, and the DCI format for non-fallback may include a configurable field.
  • DCI may be transmitted through a physical downlink control channel (PDCCH) through channel coding and modulation processes.
  • a Cyclic Redundancy Check (CRC) may be attached to the DCI message payload, and the CRC may be scrambled with a Radio Network Temporary Identifier (RNTI) corresponding to the identity of the terminal.
  • RNTI Radio Network Temporary Identifier
  • different RNTIs may be used for scrambling the CRC attached to the payload of the DCI message. That is, the RNTI may be included in the CRC calculation process and transmitted without being explicitly transmitted.
  • the UE may check the CRC using the allocated RNTI. If the CRC check result is correct, the terminal can know that the corresponding message has been transmitted to the terminal.
  • DCI scheduling a PDSCH for system information may be scrambled with SI-RNTI.
  • SI system information
  • a DCI scheduling a PDSCH for a Random Access Response (RAR) message may be scrambled with RA-RNTI.
  • RAR Random Access Response
  • a DCI scheduling a PDSCH for a paging message may be scrambled with a P-RNTI.
  • DCI notifying SFI Slot Format Indicator
  • DCI notifying TPC Transmit Power Control
  • DCI scheduling UE-specific PDSCH or PUSCH may be scrambled with C-RNTI (Cell RNTI).
  • a DCI format 0_0 may be used as a fallback DCI for scheduling the PUSCH, and in this case the CRC may be scrambled with the C-RNTI.
  • the DCI format 0_0 in which the CRC is scrambled with the C-RNTI may include, for example, information in Table 3 below.
  • a DCI format 0_1 may be used as a non-fallback DCI for scheduling the PUSCH, and in this case the CRC may be scrambled with the C-RNTI.
  • the DCI format 0_1 in which the CRC is scrambled with the C-RNTI may include, for example, information in Table 4 below.
  • a DCI format 1_0 may be used as a fallback DCI for scheduling the PDSCH, and in this case the CRC may be scrambled with the C-RNTI.
  • the DCI format 1_0 in which the CRC is scrambled with the C-RNTI may include, for example, information in Table 5 below.
  • DCI format 1_0 may be used as a DCI for scheduling a PDSCH for a RAR message, and in this case, the CRC may be scrambled with RA-RNTI.
  • DCI format 1_0 in which the CRC is scrambled with the C-RNTI may include information as shown in [Table 6] below. [Table 6] - Frequency domain resource assignment - bits - Time domain resource assignment - 4 bits - VRB-to-PRB mapping - 1 bit - Modulation and coding scheme - 5 bits - TB scaling - 2 bits - Reserved bits - 16 bits
  • a DCI format 1_1 may be used as a non-fallback DCI for scheduling the PDSCH, and in this case the CRC may be scrambled with the C-RNTI.
  • the DCI format 1_1 in which the CRC is scrambled with the C-RNTI may include, for example, information in Table 7 below. [Table 7] - Carrier indicator - 0 or 3 bits - Identifier for DCI formats - [1] bits - Bandwidth part indicator - 0, 1 or 2 bits - Frequency domain resource assignment • For resource allocation type 0, bits • For resource allocation type 1, bits • For resource allocation type 1, bits - Time domain resource assignment - 1, 2, 3, or 4 bits - VRB-to-PRB mapping - 0 or 1 bit, only for resource allocation type 1.
  • FIG. 4 illustrates a view of an example of configuring a control region of a downlink control channel in a next generation wireless communication system according to an embodiment of the disclosure. That is, FIG. 4 illustrates an example of a control resource set (CORESET) in which a downlink control channel is transmitted in 5G wireless communication systems.
  • CORESET control resource set
  • FIG. 4 illustrates an example in which a UE bandwidth part 4-10 is configured in the frequency axis and two control resource sets (control resource set #1 4-01 and control resource set #2 4-02) are configured within 1 slot 4-20 in the time axis.
  • the control resource sets 4-01 and 4-02 may be configured in specific frequency resources 4-03 within a total UE BWP 4-10 in the frequency axis.
  • the control resource set 4-01 and 4-02 may be configured as one or a plurality of OFDM symbols in the time axis, which may be defined as a control resource set duration 4-04.
  • control resource set #1 4-01 may be configured as a control resource set duration of 2 symbols
  • control resource set #2 4-02 may be configured as a control resource set duration of 1 symbol.
  • the control resource sets in the next generation mobile communication system may be configured through higher-layer signaling (for example, system information, a master information block (MIB), or radio resource control (RRC) signaling) in the UE by the BS.
  • Configuring the control resource set in the UE may mean providing information such as a control resource set identity, a frequency location of the control resource set, and a symbol length of the control resource set. For example, the following information as [Table 8] may be included.
  • tci-StatesPDCCH (referred to as a transmission configuration indication (TCI) state) configuration information may include information on one or a plurality of synchronization signal (SS)/physical broadcast channel (PBCH) block indexes or channel state information reference signal (CSI-RS) indexes having the Quasi Co-Located (QCL) relationship with a DMRS transmitted in the corresponding CORESET.
  • TCI transmission configuration indication
  • SS synchronization signal
  • PBCH physical broadcast channel
  • CSI-RS channel state information reference signal
  • one or more different antenna ports may be substituted, but in the future description of the present disclosure, for convenience, different antenna ports are collectively referred to) may be associated with each other by the QCL settings shown in [Table 9] below.
  • the QCL configuration may link two different antenna ports in a relationship between a (QCL) target antenna port and a (QCL) reference antenna port, and the terminal may apply or assume all or some of the statistical characteristics of the channel measured at the reference antenna port (e.g., the channel's large scale parameters, such as Doppler shift, Doppler spread, average delay, delay spread, average gain, spatial Rx (or Tx) parameters, or reception spatial filter coefficients or transmission spatial filter coefficients of the terminal) to receiving target antenna ports.
  • the target antenna port means an antenna port for transmitting a channel or signal configured by higher layer configuration including the QCL configuration or an antenna port for transmitting a channel or signal to which a TCI state indicating the QCL configuration is applied.
  • the reference antenna port means an antenna port that transmits a channel or signal indicated (specified) by the referenceSignal parameter in the QCL configuration.
  • statistical characteristics of channels limited by the QCL configuration may be classified as follows according to the QCL type.
  • QCL-TypeA is a QCL type used when all measurable statistical characteristics in the frequency and time axes can be referenced, because the bandwidth and transmission period of the target antenna port are sufficient compared to the reference antenna port (i.e., the number of samples and transmission band/time of the target antenna port are more than the number of samples and transmission band/time of the reference antenna port in both the frequency axis and the time axis).
  • QCL-TypeB is a QCL type used when the bandwidth of a target antenna port is sufficient to measure measurable statistical characteristics in the frequency axis, that is, Doppler shift and Doppler spreads.
  • QCL-TypeC is a QCL type used when the bandwidth and transmission period of the target antenna port are insufficient to measure second-order statistics, that is, Doppler spread and delay spread, and only first-order statistics, that is, Doppler shift and average delay, can be referred.
  • QCL-TypeD is a QCL type that is set when the spatial reception filter values used when receiving the reference antenna port can be used when receiving the target antenna port.
  • the base station can set or indicate a maximum of two QCL configurations to one target antenna port through the following TCI state setting.
  • the first QCL configuration may be set to one of QCL-TypeA, QCL-TypeB, and QCL-TypeC.
  • the configurable QCL type is specified according to the type of target antenna port and reference antenna port, and will be described in detail below.
  • the second QCL configuration may be set to QCL-TypeD and may be omitted in some cases.
  • [Table 9-1] shows valid TCI state configurations when the target antenna port is a CSI-RS for tracking (TRS).
  • the TRS is an NZP CSI-RS for which a repetition parameter is not configured and trs-Info is configured as true among CSI-RSs.
  • the third configuration in [Table 9-1] may be used for an aperiodic TRS.
  • Valid TCI state configurations when the target antenna port is a CSI-RS for tracking (TRS) Valid TCI state Configuration DL RS 1 qcl-Type 1 DL RS 2 (if configured) qcl-Type 2 (if configured) 1 SSB QCL-TypeC SSB QCL-TypeD 2 SSB QCL-TypeC CSI-RS (BM) QCL-TypeD 3 TRS (periodic) QCL-TypeA TRS (same as DL RS 1) QCL-TypeD
  • the CSI-RS for CSI is an NZP CSI-RS for which a parameter (for example, a repetition parameter) indicating repetition is not configured and trs-Info is not configured as true among the CSI-RSs.
  • [Table 9-3] shows valid TCI state configurations when the target antenna port is a CSI-RS for beam management (BM) (that is, the same meaning as a CSI-RS for L1 RSRP reporting).
  • the CSI-RS for BM is an NZP CSI-RS for which a repetition parameter is configured to have a value of on or off and trs-Info is not configured as true.
  • BM beam management
  • Valid TCI state configurations when the target antenna port is a CSI-RS for BM (for L1 RSRP reporting).
  • [Table 9-4] shows valid TCI state configurations when the target antenna port is a PDCCH DMRS.
  • Valid TCI state configurations when the target antenna port is a PDCCH DMRS Valid TCI state Configuration DL RS 1 qcl-Type 1 DL RS 2 (if configured) qcl-Type 2 (if configured) 1 TRS QCL-TypeA TRS (same as DL RS 1)
  • QCL-TypeD 2 TRS QCL-TypeA CSI-RS (BM)
  • QCL-TypeA CSI-RS (same as DL RS 1)
  • [Table 9-5] shows valid TCI state configurations when the target antenna port is a PDSCH DMRS.
  • Valid TCI state configurations when the target antenna port is a PDSCH DMRS Valid TCI state Configuration DL RS 1 qcl-Type 1 DL RS 2 (if configured) qcl-Type 2 (if configured) 1 TRS QCL-TypeA TRS QCL-TypeD 2 TRS QCL-TypeA CSI-RS (BM) QCL-TypeD 3 CSI-RS (CSI) QCL-TypeA CSI-RS (CSI) QCL-TypeD
  • the target antenna port and the reference antenna port for each step are configured and operated as "SSB” -> "TRS” -> "CSI-RS for CSI, CSI-RS for BM, PDCCH DMRS, or PDSCH DMRS".
  • the target antenna port and the reference antenna port for each step are configured and operated as "SSB” -> "TRS” -> "CSI-RS for CSI, CSI-RS for BM, PDCCH DMRS, or PDSCH DMRS".
  • FIG. 5 illustrates a view for explaining the structure of a downlink control channel of a mobile communication system according to an embodiment of the disclosure. That is, FIG. 5 is a diagram illustrating an example of a base unit of time and frequency resources constituting a downlink control channel that can be used in a 5G system.
  • the basic unit of time and frequency resources constituting the control channel may be referred to as a resource element group (REG) 5-03, and the REG 5-03 may be defined as one OFDM symbol 5-01 on the time axis and one physical resource block (PRB) 5-02, that is, twelve subcarriers, on the frequency axis.
  • the base station may compose a downlink control channel allocation unit by concatenating the REGs 5-03.
  • one CCE 5-04 may be composed of a plurality of REGs 5-03.
  • the REG 5-03 may be composed of twelve REs
  • one CCE 5-04 may be composed of six REGs 5-03
  • one CCE 5-04 may be composed of seventy-two REs.
  • a downlink control resource set it may be composed of a plurality of CCEs 5-04, and a specific downlink control channel may be transmitted through mapping with one or a plurality of CCEs 5-04 depending on an aggregation level (AL) in the control resource set.
  • the CCEs 5-04 in the control resource set are distinguished by means of numbers, and the numbers of the CCEs 5-04 may be assigned according to a logical mapping scheme.
  • the basic unit of the downlink control channel shown in FIG. 5 may include both REs to which DCI is mapped and a region to which a DMRS 5-05, which is a reference signal for decoding them, is mapped.
  • three DMRSs 5-05 may be transmitted within one REG 5-03.
  • the UE needs to detect a signal without knowing information about the downlink control channel.
  • a search space indicating a set of CCEs is defined.
  • the search space is a set of downlink control channel candidates consisting of CCEs that the UE should attempt to decode on a given aggregation level. Because there are various aggregation levels that make one bundle with 1, 2, 4, 8, or 16 CCEs, the UE may have a plurality of search spaces.
  • a search space set may be defined as a set of search spaces in all the configured aggregation levels.
  • the search spaces may be classified into a common search space and a UE-specific search space.
  • a certain group of UEs or all UEs may search the common search space of the PDCCH to receive cell-common control information such as dynamic scheduling for system information or a paging message.
  • UE may receive PDSCH scheduling assignment information for SIB transmission including cell operator information by searching the common search space of the PDCCH. Because a certain group of UEs or all UEs should receive the PDCCH, the common search space may be defined as a set of promised CCEs. The UE may receive the scheduling assignment information for the UE-specific PDSCH or PUSCH by searching the UE-specific search space of the PDCCH.
  • the UE-specific search space may be defined UE-specifically as a function of the UE identity and various system parameters.
  • parameters for the search space for the PDCCH may be configured from the base station to the UE through higher layer signaling (e.g., SIB, MIB, RRC signaling).
  • the base station may configured, to the UE, the number of PDCCH candidates in each aggregation level L, a monitoring period for the search space, a monitoring occasion in units of symbols in a slot for the search space, a search space type (a common search space or a UE-specific search space), a combination of a DCI format to be monitored in the corresponding search space and an RNTI, a control resource set index to be monitored in the search space, and the like.
  • the configuration may be include the following information in Table 10.
  • the base station may configure one or a plurality of search space sets to the UE based on configuration information.
  • the base station may configure a search space set 1 and a search space set 2 to the UE, configure a DCI format A scrambled with X-RNTI in the search space set 1 to be monitored in the common search space, and configured a DCI format B scrambled with Y-RNTI in the search space set 2 to be monitored in the UE-specific search space.
  • one or a plurality of search space sets may exist in the common search space or the UE-specific search space.
  • a search space set #1 and a search space set #2 may be configured as the common search space
  • a search space set #3 and a search space set #4 may be configured as the UE-specific search space.
  • the common search space may be classified into a search space set of a specific type according to a purpose.
  • RNTIs to be monitored may be different for each type of the search space set.
  • the common search space type, purpose, and RNTI to be monitored may be classified as follows.
  • PCell PDCCH transmission for scheduling data C-RNTI, MCS-C-RNTI, CS-RNTI
  • the following combination of a DCI format and an RNTI may be monitored.
  • the following examples are not considered as a limitation.
  • the following combination of a DCI format and an RNTI may be monitored.
  • the following examples are not considered as a limitation.
  • the specified RNTIs may follow the following definitions and purposes.
  • the aforementioned specified DCI formats may follow the definition of Table 11 below.
  • Table 11 DCI format Usage 0_0 Scheduling of PUSCH in one cell 0_1 Scheduling of PUSCH in one cell 1_0 Scheduling of PDSCH in one cell 1_1 Scheduling of PDSCH in one cell 2_0 Notifying a group of UEs of the slot format 2_1 Notifying a group of UEs of the PRB(s) and OFDM symbol(s) where UE may assume no transmission is intended for the UE 2_2 Transmission of TPC commands for PUCCH and PUSCH 2_3 Transmission of a group of TPC commands for SRS transmissions by one or more UEs
  • a plurality of search space sets may be configured with different parameters (e.g., parameters in Table 10), so the set of search space monitored by the UE at every time point may vary. For example, if a search space set #1 is configured with a X-slot period, a search space set #2 is configured with a Y-slot period, and X and Y are different, the UE may monitor both the search space set #1 and the search space set #2 in a specific slot, and monitor one of the search space set #1 and the search space set #2 in a specific slot.
  • parameters in Table 10 e.g., parameters in Table 10
  • the following conditions may be considered in a method for determining a search space set to be monitored by the UE.
  • the number of PDCCH candidates that can be monitored per slot does not exceed M ⁇ .
  • the M ⁇ may be defined as the maximum number of PDCCH candidates per slot in a cell configured with a subcarrier spacing of 15 ⁇ 2 ⁇ kHz, and may be defined as shown in Table 12 below. [Table 12] ⁇ Maximum number of monitored PDCCH candidates per slot and per serving cell M ⁇ 0 44 1 36 2 22 3 20
  • the number of CCEs constituting the entire search space per slot does not exceed C ⁇ .
  • the C ⁇ may be defined as the maximum number of CCEs per slot in a cell configured with a subcarrier spacing of 15 ⁇ 2 ⁇ kHz, and may be defined as shown in Table 13 below. [Table 13] ⁇ Maximum number of non-overlapped CCEs per slot and per serving cell C ⁇ 0 56 1 56 2 48 3 32
  • condition A a situation satisfying both conditions 1 and 2 at a specific time point is defined as "condition A”. Accordingly, not satisfying condition A may mean that at least one of conditions 1 and 2 is not satisfied.
  • Condition A may not be satisfied at a specific time point according to a configuration of search space sets by the BS. If condition A is not satisfied at a specific time point, the UE may select and monitor only some of the search space sets configured to satisfy condition A at the corresponding time point, and the BS may transmit the PDCCH through the selected search space sets.
  • the following method may be applied as a method of selecting some of all the configured search space sets.
  • condition A for the PDCCH is not satisfied at a specific time point (slot)
  • the UE or the BS may select a search space set of which a search space type is configured as a common-search space among search space sets existing at the corresponding time point in preference to a search space set of which a search space type is configured as a UE-specific search space.
  • search space sets configured as the common-search space are all selected (that is, if condition A is satisfied even after all search spaces configured as the common-search space are selected), the UE (or BS) may select search space sets configured as the UE-specific search space. At this time, if the number of search space sets of configured as the UE-specific search space is plural, a search space set having a lower search space set index may have a higher priority. UE-specific search space sets may be selected within a range in which condition A is satisfied in consideration of the priority.
  • FD-RA frequency domain resource allocation
  • FIG. 6 illustrates an example of frequency axis resource allocation of a physical downlink shared channel (PDSCH) in a wireless communication system according to an embodiment of the disclosure.
  • PDSCH physical downlink shared channel
  • FIG. 6 illustrates three frequency axis resource allocation methods of type 0 6-00, type 1 6-05, and dynamic switch 6-10 which can be configured through a higher layer in the wireless communication system (for example, 5G system or NR system) according to an embodiment of the disclosure.
  • the wireless communication system for example, 5G system or NR system
  • NRBG is the number of resource block groups (RBGs) determined as shown in [Table 14] below according to a BWP size allocated by a BWP indicator and a higher-layer parameter rbg-Size, and data is transmitted in an RBG indicated as 1 by the bitmap.
  • RBG resource block groups
  • some pieces of DCI for allocating the PDSCH to the corresponding UE includes frequency axis resource allocation information of ⁇ log 2 ( N RB DL , BWP N RB DL , BWP + 1 / 2 ⁇ bits. A condition therefor is described later again.
  • the BS may configure a starting VRB 6-20 and a length 6-25 of frequency axis resources allocated successively therefrom.
  • some pieces of DCI for allocating the PDSCH to the corresponding UE includes frequency axis resource allocation information of bits of a larger value 6-35 among payload 6-15 for configuring resource type 0 and payload 6-20 and 6-25 for configuring resource type 1.
  • a condition therefor is described later again.
  • one bit may be added to the first part (MSB) of the frequency axis resource allocation information within the DCI, and the use of resource type 0 may be indicated when the corresponding bit is "0" and the use of resource type 1 may be indicated when the corresponding bit is "1".
  • the BS may configure a table for time domain resource allocation information for a downlink data channel (physical downlink shared channel (PDSCH)) and an uplink data channel (physical uplink shared channel (PUSCH)) in the UE through higher-layer signaling (for example, RRC signaling).
  • PDSCH physical downlink shared channel
  • PUSCH physical uplink shared channel
  • the time domain resource allocation information may include PDCCH-to-PDSCH slot timing (corresponding to a time interval in units of slots between a time point at which a PDCCH is received and a time point at which a PDSCH scheduled by the received PDCCH is transmitted, and indicated by K0) or PDCCH-to-PUSCH slot timing (corresponding to a time interval in units of slots between a time point at which a PDCCH is received and a time point at which a PUSCH scheduled by the received PDCCH is transmitted, and indicated by K2), a location and a length of a start symbol in which a PDSCH or a PUSCH is scheduled within the slot, a mapping type of a PDSCH or a PUSCH, and the like.
  • PDCCH-to-PDSCH slot timing corresponding to a time interval in units of slots between a time point at which a PDCCH is received and a time point at which a PUSCH scheduled by the received PDCCH is transmitted, and indicated by K2
  • the BS may inform the UE of one of the entries in the table for the time domain resource allocation information through L1 signaling (for example, DCI) (for example, indicated through a ⁇ time domain resource allocation field within DCI).
  • the UE may acquire time domain resource allocation information for a PDSCH or a PUSCH on the basis of the DCI received from the BS.
  • FIG. 7 illustrates an example of allocation of time axis resources of a PDSCH in a wireless communication system according to an embodiment of the disclosure.
  • the BS may indicate a time axis location of PDSCH resources according to subcarrier spacing (SCS) ( ⁇ PDSCH , ⁇ PDCCH ) of a data channel and a control channel configured using a higher layer, a scheduling offset (K 0 ) value, and an OFDM symbol start location 7-00 and length 7-05 within one slot dynamically indicated through DCI.
  • SCS subcarrier spacing
  • K 0 scheduling offset
  • FIG. 8 illustrates an example of allocation of time-axis resources according to subcarrier spacing of a data channel and a control channel in a wireless communication system according to an embodiment of the disclosure.
  • ⁇ PDSCH ⁇ PDCCH
  • slot numbers for the data and the control are the same as each other, and thus the BS and the UE may generate a scheduling offset according to a predetermined slot offset K0.
  • the terminal transmits uplink control information (UCI) to the base station through physical uplink control channel (PUCCH).
  • the control information may include at least one of HARQ-ACK indicating success or failure of demodulation/decoding for a transport block (TB) received by the UE through the PDSCH, scheduling request (SR) for requesting resource allocation from the UE to the PUSCH base station for uplink data transmission, and channel state information (CSI), which is information for reporting the channel state of the terminal.
  • HARQ-ACK indicating success or failure of demodulation/decoding for a transport block (TB) received by the UE through the PDSCH
  • SR scheduling request
  • CSI channel state information
  • the PUCCH resource may be largely divided into a long PUCCH and a short PUCCH according to the length of the allocated symbol.
  • the long PUCCH has a length of 4 symbols or more in a slot
  • the short PUCCH has a length of 2 symbols or less in a slot.
  • the long PUCCH may be used for the purpose of improving uplink cell coverage, and thus may be transmitted in a DFT-S-OFDM scheme, which is a single carrier transmission rather than an OFDM transmission.
  • the long PUCCH supports transmission formats such as PUCCH format 1, PUCCH format 3, and PUCCH format 4 depending on the number of supportable control information bits and whether terminal multiplexing through Pre-DFT OCC support at the front end of the IFFT is supported.
  • the PUCCH format 1 is a DFT-S-OFDM-based long PUCCH format capable of supporting up to 2 bits of control information, and uses as much frequency resources as 1RB.
  • the control information may be constituted with each of or a combination of HARQ-ACK and SR.
  • PUCCH format 1 an OFDM symbol including a demodulation reference signal (DMRS) that is a demodulation reference signal (or a reference signal) and an OFDM symbol including UCI are repeatedly constituted.
  • DMRS demodulation reference signal
  • the first start symbol of 8 symbols is sequentially constituted with DMRS symbol, UCI symbol, DMRS symbol, UCI symbol, DMRS symbol, UCI symbol, DMRS symbol, UCI symbol.
  • the DMRS symbol is spread using an orthogonal code (or orthogonal sequence or spreading code, w_i(m)) on the time axis to a sequence corresponding to the length of 1RB on the frequency axis within one OFDM symbol, and is transmitted after performing IFFT.
  • the UCI symbol is generated as follows.
  • the UE has a structure to generate d(0) by BPSK modulating 1-bit control information and QPSK modulating 2-bit control information, multiply the generated d(0) by a sequence corresponding to the length of 1 RB on the frequency axis to scramble, spread the scrambled sequence using an orthogonal code (or an orthogonal sequence or spreading code, w i(m) ) on the time axis, and transmit the same after performing the IFFT.
  • an orthogonal code or an orthogonal sequence or spreading code, w i(m)
  • the UE generates the sequence, based on the group hopping or sequence hopping configuration and the configured ID configured as a higher signal from the base station, and generates a sequence corresponding to a length of 1 RB by cyclic shifting the generated sequence with an initial cyclic shift (CS) value configured as a higher signal.
  • CS cyclic shift
  • i means the index of the spreading code itself
  • m means the index of the elements of the spreading code.
  • the numbers in [ ] in Table 16-1 mean, for example, ⁇ ( m ).
  • the PUCCH format 3 is a DFT-S-OFDM-based long PUCCH format capable of supporting more than 2 bits of control information, and the number of RBs used can be configured through an higher layer.
  • the control information may be constituted with each of or a combination of HARQ-ACK, SR, and CSI.
  • the location of the DMRS symbol is presented according to whether frequency hopping in the slot and whether additional DMRS symbols are configured as illustrated in [Table 17] below.
  • the first start symbol of the 8 symbols starts with 0, and the DMRS is transmitted in the first symbol and the fifth symbol.
  • the above table is applied in the same way to the DMRS symbol location of the PUCCH format 4.
  • the PUCCH format 4 is a DFT-S-OFDM-based long PUCCH format capable of supporting more than 2 bits of control information, and uses as much frequency resources as 1RB.
  • the control information may be constituted with each of or a combination of HARQ-ACK, SR, and CSI.
  • the difference between the PUCCH format 4 and the PUCCH format 3 is that in the case of the PUCCH format 4, the PUCCH format 4 of a plurality of terminals can be multiplexed within one RB. It is possible to multiplex PUCCH format 4 of a plurality of terminals through application of Pre-DFT OCC to control information in the front of the IFFT.
  • the number of transmittable control information symbols of one terminal decreases according to the number of multiplexed terminals.
  • the number of multiplexable terminals that is, the number of different OCCs that can be used, may be 2 or 4, and the number of OCCs and the OCC index to be applied may be configured through a higher layer.
  • the short PUCCH may be transmitted in both a downlink centric slot and an uplink centric slot.
  • the short PUCCH may be transmitted at the last symbol of the slot or an OFDM symbol at the end (e.g., the last OFDM symbol, the second OFDM symbol from the end, or the last 2 OFDM symbols).
  • the short PUCCH may be transmitted using one OFDM symbol or two OFDM symbols.
  • the short PUCCH may be used to shorten a delay time compared to the long PUCCH in a situation where uplink cell coverage is good, and is transmitted in a CP-OFDM scheme.
  • the short PUCCH supports transmission formats such as PUCCH format 0 and PUCCH format 2 according to the number of supportable control information bits.
  • the PUCCH format 0 is a short PUCCH format capable of supporting up to 2 bits of control information, and uses frequency resources of 1 RB.
  • the control information may be constituted with each of or a combination of HARQ-ACK and SR.
  • the PUCCH format 0 does not transmit DMRS, but has a structure of transmitting only sequences mapped to 12 subcarriers in the frequency axis within one OFDM symbol.
  • the terminal generates a sequence, based on the group hopping or sequence hopping configuration and configured ID configured as a higher signal from the base station, cyclic shifts the generated sequence to the final cyclic shift (CS) value obtained by adding another CS value according to whether it is ACK or NACK to the indicated initial CS value, maps it to 12 subcarriers, and transmits the same.
  • CS cyclic shift
  • HARQ-ACK is 1 bit
  • 6 is added to the initial CS value to generate the final CS
  • 0 is added to the initial CS to generate the final CS.
  • the CS value 0 for NACK and 6 for ACK are defined in the standard, and the terminal always generates PUCCH format 0 according to the value to transmit 1-bit HARQ-ACK.
  • 1 Bit HARQ-ACK NACK ACK Final CS (Initial CS + O) mod 12 initial CS (Initial CS + 6) mod 12
  • HARQ-ACK is 2 bits
  • 0 is added to the initial CS value if (NACK, NACK) as in the following Table 19, and 3 is added to the initial CS value if (NACK, ACK), and if (ACK, ACK)), 6 is added to the initial CS value, and 9 is added to the initial CS value if (ACK, NACK).
  • the CS value 0 for (NACK, NACK), the CS value 3 for (NACK, ACK), the CS value 6 for (ACK, ACK), and the CS value 9 for (ACK, NACK) are defined in the standard.
  • the terminal always transmits a 2-bit HARQ-ACK by generating PUCCH format 0 according to the above values.
  • the PUCCH format 2 is a short PUCCH format that supports more than 2 bits of control information, and the number of RBs used can be configured through a higher layer.
  • the control information may be constituted with each of or a combination of HARQ-ACK, SR, and CSI.
  • the location of the subcarrier through which the DMRS is transmitted within one OFDM symbol is fixed to the subcarrier having indexes of #1, #4, #7, and #10, when the index of the first subcarrier is #0, as shown in FIG. 414.
  • the control information is mapped to the remaining subcarriers through a modulation process after channel coding except for the subcarrier where the DMRS is located.
  • values that may be configured for each of the above-described PUCCH formats and their ranges may be arranged as illustrated in Table 20 below. In the case that the value does not need to be configured in the Table 20, it is indicated as N.A.
  • multi-slot repetition may be supported for PUCCH formats 1, 3, and 4, PUCCH repetition can be configured for each PUCCH format.
  • the terminal repeatedly transmits the PUCCH including UCI as many as the number of slots configured through nrofSlots, which is higher layer signaling.
  • the PUCCH transmission in each slot may be performed using the same number of consecutive symbols, and the corresponding consecutive symbols may be configured through a nrofSymbols in the PUCCH-format 1, the PUCCH-format 3, or the PUCCH-format 4, which is higher layer signaling.
  • the PUCCH transmission in each slot may be performed using the same start symbol, and the corresponding start symbol may be configured through a startingSymbolIndex in the PUCCH-format 1, the PUCCH-format 3, or the PUCCH-format 4, which is higher layer signaling.
  • the terminal For the repetitive PUCCH transmission, if the terminal has been configured to perform frequency hopping in PUCCH transmission in different slots, the terminal performs frequency hopping in units of slots. In addition, if the terminal has been configured to perform frequency hopping in the PUCCH transmission in different slots, the terminal starts the PUCCH transmission from the first PRB index configured through startingPRB, which is higher layer signaling, in the even-numbered slot, and in the odd-numbered slot, the terminal starts the PUCCH transmission from the second PRB index configured through secondHopPRB, which is higher layer signaling.
  • the terminal is configured to perform frequency hopping in PUCCH transmission in different slots, the index of the slot in which the terminal is instructed to transmit the first PUCCH is 0, and during the configured total number of repetitive PUCCH transmissions, the value of the number of repetitive PUCCH transmissions is increased in each slot regardless of the PUCCH transmission performed. If the terminal is configured to perform frequency hopping in PUCCH transmission in different slots, the terminal does not expect that frequency hopping in the slot is configured when transmitting PUCCH. If the terminal is not configured to perform frequency hopping in PUCCH transmission in different slots but is configured for frequency hopping in a slot, the first and second PRB indexes are applied equally in the slot.
  • the base station may configure PUCCH resources for each BWP through a higher layer for a specific terminal.
  • the configuration may be as in Table 21.
  • one or a plurality of PUCCH resource sets in the PUCCH resource setting for a specific BWP may be configured, and a maximum payload value for UCI transmission may be configured in some of the PUCCH resource sets.
  • Each PUCCH resource set may belong to one or more PUCCH resources, and each of the PUCCH resources may belong to one of the above-described PUCCH formats.
  • the maximum payload value of the first PUCCH resource set may be fixed to 2 bits, and thus the corresponding value may not be separately configured through a higher layer.
  • the index of the corresponding PUCCH resource set may be configured in ascending order according to the maximum payload value, and the maximum payload value may not be configured in the last PUCCH resource set.
  • the higher layer configuration for the PUCCH resource set may be as illustrated in Table 22 below.
  • the resourceList parameter of the table may include IDs of PUCCH resources belonging to the PUCCH resource set.
  • a PUCCH resource set as illustrated in Table 23, which is constituted with a plurality of cell-specific PUCCH resources in the initial BWP, may be used.
  • the PUCCH resource to be used for initial access in this PUCCH resource set may be indicated through SIB 1.
  • the maximum payload of each PUCCH resource included in the PUCCH resource set may be 2 bits in case of PUCCH format 0 or 1, and may be determined by symbol length, number of PRBs, and maximum code rate in case of the remaining formats.
  • the symbol length and number of PRBs may be configured for each PUCCH resource, and the maximum code rate may be configured for each PUCCH format.
  • a PUCCH resource for an SR corresponding to schedulingRequestID may be configured through a higher layer as shown in Table 24.
  • the PUCCH resource may be a resource belonging to PUCCH format 0 or PUCCH format 1.
  • a transmission period and an offset are configured through the periodicityAndOffset parameter of Table 24.
  • the corresponding PUCCH resource is transmitted, otherwise the corresponding PUCCH resource may not be transmitted.
  • a PUCCH resource for transmitting a periodic or semi-persistent CSI report through PUCCH may be configured in the pucch-CSI-ResourceList parameter as shown in [Table 25] as higher signaling.
  • the parameter includes a list of PUCCH resources for each BWP for the cell or CC to which the corresponding CSI report is to be transmitted.
  • the PUCCH resource may be a resource belonging to PUCCH format 2 or PUCCH format 3 or PUCCH format 4.
  • a transmission period and an offset are configured through reportSlotConfig of Table 25.
  • a resource set of PUCCH resources to be transmitted is first selected according to the payload of the UCI including the corresponding HARQ-ACK. That is, a PUCCH resource set having a minimum payload not smaller than the UCI payload is selected.
  • the PUCCH resource in the PUCCH resource set can be selected through the PUCCH resource indicator (PRI) in the DCI scheduling the TB corresponding to the corresponding HARQ-ACK, and the PRI may be the PUCCH resource indicator specified in Table 5 or Table 6.
  • the relationship between the PRI configured as higher signaling and the PUCCH resource selected from the PUCCH resource set may be as shown in Table 26.
  • the PUCCH resource may be selected by the following equation 1.
  • r PUCCH ⁇ n CCE , p ⁇ ⁇ R PUCCH / 8 ⁇ N CCE , p ⁇ + ⁇ PRI ⁇ ⁇ R PUCCH 8 ⁇ if ⁇ PRI ⁇ R PUCCH mod 8 ⁇ n CCE , p ⁇ ⁇ R PUCCH / 8 ⁇ N CCE , p ⁇ + ⁇ PRI ⁇ ⁇ R PUCCH 8 ⁇ + R PUCCH mod 8 if ⁇ PRI ⁇ R PUCCH mod 8
  • the time point at which the corresponding PUCCH resource is transmitted is after the K 1 slot from the TB transmission corresponding to the corresponding HARQ-ACK.
  • the K 1 value candidate is configured as a higher layer, and more specifically, is configured in the dl-DataToUL-ACK parameter in the PUCCH-Config specified in [Table 21].
  • the K 1 value of one of these candidates may be selected by the PDSCH-to-HARQ feedback timing indicator in the DCI scheduling the TB, and this value may be a value specified in Table 5 or Table 6.
  • the unit of the K 1 value may be a slot unit or a sub slot unit.
  • a sub slot is a unit of a length smaller than that of a slot, and one or a plurality of symbols may constitute one sub slot.
  • the terminal can transmit UCI through one or two PUCCH resources in one slot or sub slot, and when UCI is transmitted through two PUCCH resources in one slot/sub slot, i) each PUCCH resource does not overlap in units of symbols, and ii) at least one PUCCH resource may be a short PUCCH. Meanwhile, the terminal may not expect to transmit a plurality of PUCCH resources for HARQ-ACK transmission within one slot.
  • the PUCCH transmission procedure in the case that two or more PUCCH resources overlap.
  • one of the overlapping PUCCH resources may selected or a new PUCCH resource may be selected according to the condition that the transmitted PUCCH resource should not overlap in symbol units.
  • the UCI payload transmitted through the overlapping PUCCH resource may be multiplexed and transmitted or some may be dropped.
  • Case 1 is divided into Case 1-1) a case where two or more PUCCH resources for HARQ-ACK transmission are overlapped, and Case 1-2) the remaining cases.
  • FIG. 9 is a view illustrating a case of overlapping a plurality of PUCCH resources for HARQ-ACK transmission for PDSCH in the case that multi-slot repetition is not configured according to an embodiment of the disclosure.
  • the corresponding PUCCH resources may be considered to be overlapped with each other. That is, in the case that the uplink slots corresponding to the K 1 values 9-50 and 9-51 indicated by a plurality of PDCCHs are the same, the PUCCH resources corresponding to the corresponding PDCCHs may be considered as overlapping each other.
  • SR on PUCCH format 0+HARQ-ACK on PUCCH format 1 SR is dropped and only HARQ-ACK is transmitted
  • the multiplexing of these UCIs may follow the higher layer configuration.
  • whether to multiplex between HARQ-ACK and CSI and whether to multiplex between multiple CSIs may be independently performed.
  • whether HARQ-ACK and CSI are multiplexed may be configured through simultaneous HARQ-ACK-CSI parameters for each PUCCH format 2, 3, or 4, and the corresponding parameters may all be configured to the same value for the PUCCH format. In the case that it is configured not to perform multiplexing through the above parameter, only HARQ-ACK is transmitted and the overlapping CSI may be dropped.
  • whether to multiplex a plurality of CSIs may be configured through a multi-CSI-PUCCH-ResourceList parameter in PUCCH-Config. That is, in the case that the multi-CSI-PUCCH-ResourceList parameter is configured, inter-CSI multiplexing may be performed. Otherwise, only a PUCCH corresponding to a CSI having a higher priority may be transmitted according to the inter-CSI priority.
  • the selection method of the PUCCH resource to transmit the corresponding UCI resource and the multiplexing method may differ according to the information of the overlapped UCI and the format of the PUCCH resource, which can be summarized as shown in Table 28 below.
  • the terminal selects one of the resources in the list with the lowest index capable of transmitting all the multiplexed UCI payloads, and then transmits UCI payload. In the case that there is no resource capable of transmitting all of the multiplexed UCI payloads in the list, the terminal selects the resource with the largest index and then transmits HARQ-ACK and CSI reports as many as the number of transmittable to the resource.
  • the focus has dealt with the case where two PUCCH resources are overlapped, but the method may be similarly applied even the case where three or more PUCCH resources overlap.
  • the multiplexing method between HARQ-ACK and CSI can be followed.
  • UCI with a higher priority is transmitted according to the priority in the order of HARQ-ACK>SR>CSI, and UCI with a lower priority may be dropped.
  • a plurality of CSI PUCCH resources is configured not to perform multiplexing when overlapping, PUCCH corresponding to the high priority CSI is transmitted, and PUCCH corresponding to other CSI may be dropped.
  • Case 2 which is the case where multi-slot repetition is configured, is divided into cases where two or more PUCCH resources for HARQ-ACK transmission are located in the same start slot Case 2-1) and the other cases Case 2-2). Each case is illustrated in FIG. 10 .
  • FIG. 10 is a view illustrating a case in which a PUCCH resource overlaps in the case of the configuration of multi-slot repetition according to an embodiment of the disclosure.
  • Case 2-2 corresponds to a case in which a symbol unit overlap occurs between PUCCH for HARQ-ACK transmission and PUCCH for SR or CSI transmission, or between PUCCHs for multiple SR or CSI transmission. That is, in the case that PUCCH #1 is repeatedly transmitted over a plurality of slots 10-50 and 10-51 and PUCCH #2 is also repeatedly transmitted over a plurality of slots 10-60 and 10-61, it corresponds to the case where more than one symbol overlap in one slot 10-70 occurs between PUCCH #1 and PUCCH #2.
  • the PUCCH corresponding to the high priority CSI may be transmitted, and the PUCCH corresponding to another CSI may be dropped in the corresponding slot.
  • PUCCH transmission or drop according to the above-described priority is performed only in the slot where the overlap per symbol has occurred, and is not performed in other slots. That is, the PUCCH in which multi-slot repetition is configured may be dropped in the slot where the symbol unit overlap occurs, but may be transmitted as configured in the remaining slots.
  • the terminal transmits PUCCH in the first slot of the repeated transmission of N PUCCH repeat > 1 , transmits the PUSCH in the second slot.
  • the terminal transmits PUCCH and does not transmit PUSCH in slots in which PUCCH and PUSCH overlap.
  • mini-slot has a shorter length on the time axis than a slot, and one mini-slot may be constituted with fewer than 14 symbols. For example, 2 or 7 symbols may constitute one mini-slot.
  • units such as the HARQ-ACK feedback timing K1 value and the number of repetitive transmissions may be replaced by mini-slot units in the existing slot.
  • Mini-slot configuration may be applied to all PUCCH transmissions or may be limited to PUCCH transmission for a specific service. For example, slot unit transmission may be applied to PUCCH for eMBB service, whereas mini-slot unit transmission may be applied to PUCCH for URLLC service.
  • the terminal does not have a terminal-specific configuration for PUCCH resource configuration (dedicated PUCCH resource configuration)
  • the PUCCH resource set is provided through the higher signaling, pucch-ResourceCommon
  • the beam configuration for PUCCH transmission follows the beam configuration used in PUSCH transmission scheduled through the random access response (RAR) UL grant.
  • the terminal has a terminal-specific configuration for PUCCH resource configuration (dedicated PUCCH resource configuration)
  • the beam configuration for PUCCH transmission is provided through pucch-spatialRelationInfoId, which is the higher signaling illustrated in Table 29.
  • the terminal If the terminal has been configured with one pucch-spatialRelationInfoId, beam configuration for PUCCH transmission of the terminal is provided through one pucch-spatialRelationInfoId. If the terminal is configured with a plurality of pucch-spatialRelationInfoIDs, the terminal is instructed to activate one of the plurality of pucch-spatialRelationInfoIDs through a MAC control element (CE). The terminal may receive up to eight pucch-spatialRelationInfoIDs through higher signaling, and may receive an indication that only one pucch-spatialRelationInfoID is activated among them.
  • CE MAC control element
  • the terminal applies pucch-spatialRelationInfoID activation through MAC CE from a slot that first appears after 3 N slot subframe , ⁇ slot from a slot in which HARQ-ACK transmission for a PDSCH that transmits MAC CE including activation information for pucch-spatialRelationInfoID.
  • ⁇ is a neurology applied to PUCCH transmission
  • N slot subframe ⁇ is the number of slots per subframe in a given neurology.
  • the higher layer configuration for pucch-spatialRelationInfo may be as shown in Table 29 below.
  • the pucch-spatialRelationInfo may be interchangeable with PUCCH beam information.
  • one referenceSignal configuration may exist in a specific pucch-spatialRelationInfo configuration, and the referenceSignal is ssb-Index indicating a specific SS/PBCH, csi-RS-Index indicating a specific CSI-RS, or srs indicating a specific SRS.
  • the terminal may configure the beam used when receiving the SS/PBCH corresponding to the ssb-Index among SS/PBCHs in the same serving cell as a beam for PUCCH transmission, or if servingCellId is provided, the terminal may configure the beam used when receiving an SS/PBCH corresponding to an ssb-Index among SS/PBCHs in a cell indicated by servingCellId as a beam for pucch transmission.
  • the terminal may configure the beam used when receiving a CSI-RS corresponding to csi-RS-Index among CSI-RSs in the same serving cell as a beam for PUCCH transmission, or if servingCellId is provided, the terminal may configure the beam used when receiving a CSI-RS corresponding to csi-RS-Index among CSI-RSs in a cell indicated by servingCellId as a beam for pucch transmission.
  • the terminal may configure the transmission beam used when transmitting the SRS corresponding to the resource index provided as an higher signaling resource in the same serving cell and/or in the activated uplink BWP as a beam for PUCCH transmission, or if the servingCellID and/or uplinkBWP are/is provided, the terminal may configure the transmission beam used when transmitting the SRS corresponding to the resource index provided through the higher signaling resource in the cell indicated by the servingCellID and/or uplinkBWP and/or in the uplink BWP as a beam for PUCCH transmission.
  • pucch-PathlossReferenceRS-Id configuration may exist in a specific pucch-spatialRelationInfo configuration.
  • PUCCH-PathlossReferenceRS of Table 30 may be mapped with pucch-PathlossReferenceRS-Id of [Table 29], and up to 4 may be configured through pathlossReferenceRSs in the higher signaling PUCCH-PowerControl of Table 30. If the PUCCH-PathlossReferenceRS is connected to the SS/PBCH through the referenceSignal of Table 30, ssb-Index is configured, and if PUCCH-PathlossReferenceRS is connected to CSI-RS, csi-RS-Index is configured.
  • a transition time may be required to satisfy the transmit power requirement condition of the ON state.
  • a transition time may be required to satisfy the transmit power requirement of the OFF state.
  • a switching time may be required even when the transmit power change or transmit RB change or hopping occurs in the transmit ON state.
  • FIG. 11 is a view illustrates a switching time required for switching between a transmit OFF state and a transmit ON state.
  • the switching time may be defined for frequency range 1 (FR1) and frequency range 2 (FR2), respectively (11-05, 11-10).
  • FIGS. 12a ad 12b are views illustrating a switching time required for transmission power change, transmission RB change, or hopping in frequency range 1 (FR1) in a transmission ON state.
  • the switching time for the case where a transmission channel is changed, a transmission power change, a transmission RB change, or hopping is accompanied may be defined as 12-05 and 12-10.
  • the switching time between the SRS channel and other channels may be differently defined.
  • different switching times may be defined according to the length of the transmission channel before and after the change/hopping (12-15, 12-20, 12-25).
  • the transition time can be defined within the long subslot (12-15). In the case of transmission power change or transmission RB change or hopping between short subslot transmissions is involved, the transition times can be defined within short subslots (12-20, 12-25). In the case that the numerology is less than 60 kHz in FR1, blank symbol does not need to be configured between short subslots (12-20), whereas in the case that the numerology is 60 kHz in FR1, blank symbol between short subslots needs to be configured (12-25).
  • the long subslot may indicate large PUSCH transmission or long PUCCH transmission in which the number of transmission symbols is greater than 2, and the short subslot may indicate PUSCH transmission or short PUCCH transmission in which the number of transmission symbols is 2 or less.
  • FIGS. 13a and 13b are views illustrating a switching time required for transmission power change, transmission RB change, or hopping in frequency range 2 (FR2) in a transmission ON state.
  • a switching time for the case where a transmission channel is changed, a transmission power change or a transmission RB change or hopping is accompanied may be defined as follows (13-05).
  • different switching times may be defined according to the length of the transmission channel before and after the change/hopping (13-10, 13-15, 13-20).
  • the switching time may be defined between the long subslot (13-10).
  • the switching time may be defined between short subslots (13-15, 13-20), and in the case that the numerology is less than 120 kHz in FR2, blank symbols between short subslots do not need to be configured (13-15), whereas in the case that the numerology is 120 kHz in FR2, blank symbols between short subslots need to be configured (13-20).
  • the long subslot may indicate PUSCH transmission or long PUCCH transmission in which the number of transmission symbols is greater than 2, and the short subslot may indicate PUSCH transmission or short PUCCH transmission in which the number of transmission symbols is 2 or less.
  • the terminal may perform a procedure of reporting the UE capability supported by the terminal to the corresponding base station while connected to the serving base station.
  • this may be referred to as UE capability (report).
  • the base station may deliver a message enquiring a UE capability report (e.g., UE capability enquire message) to the terminal in the connected state.
  • the base station may include a UE capability report request for each radio access technology (RAT) type.
  • the UE capability report request for each RAT type may include frequency band information requesting the UE capability of the terminal.
  • the RAT type may include, for example, nr, eutra-nr, eutra, and the like.
  • the base station may indicate at least one of nr, eutra-nr, and eutra, and make a request for reporting the UE capability of the UE therefor.
  • the UE may indicate at least one of nr, eutra-nr, and eutra for the RAT type which can be supported by the terminal, and report the UE capability therefor to the base station.
  • the terminal supporting NR-based wireless communication may insert the RAT type indicating nr into a message reporting the UE capability (for example, UE capability information message) and report the UE capability.
  • a message reporting the UE capability for example, UE capability information message
  • the terminal supporting (NG) E-UTRA NR dual connectivity (EN-DC) (covering E-UTRA connected to EPC or 5GC) or NR E-UTRA dual connectivity (NE-DC) may insert the RAT type indicating eutra-nr into a message reporting the UE capability (for example, UE capability information message) and report the UE capability.
  • NG terminal supporting
  • NE-DC NR E-UTRA dual connectivity
  • the UE capability enquiry message may request a plurality of RAT types through one RRC message container.
  • the base station may include the UE capability enquiry message including a UE capability report request for each RAT type multiple times and transmit the message to the terminal.
  • the terminal that receives the RRC message including a plurality of UE capability enquiry messages may constitute the UE capability information corresponding to each UE capability report request and report (transmit) the message multiple times to the base station.
  • a UE capability enquiry for multi-radio dual connectivity including NR, LTE, and E-UTRA NR dual connectivity (EN-DC) can be made.
  • the UE capability enquiry message is generally sent initially after the terminal establishes connection, but the UE capability can be requested under any conditions when the base station is required.
  • the terminal receiving the UE capability report request from the base station may constitute the UE capability according to the RAT type and band information requested from the base station.
  • a method for the terminal to constitute the UE capability may include the following methods.
  • the terminal may constitute a band combination (BC) for EN-DC and NR standalone (SA).
  • BC band combination
  • SA NR standalone
  • the terminal may constitute a BC candidate list for EN-DC and NR SA based on the bands requesting the UE capability report through the list information (e.g., FreqBandList) included in the UE capability enquiry message received from the base station.
  • the priorities of the bands may have priorities in the order described in FreqBandList.
  • the terminal may remove the BC for NR SA BCs from the BC candidate list constituted in Operation 1. This operation may be also performed only in the case that the LTE base station (eNB) requests "eutra" capability.
  • the terminal may remove fallback BCs from the BC candidate list constituted in the above operation.
  • the fallback BC may mean the BC in which a band corresponding to at least one secondary cell (SCell) is removed from any super set BC.
  • SCell secondary cell
  • the fallback BC may be omitted because super set BC can already cover fallback BC.
  • Operation 3 also applies to multi-RAT dual connectivity (MR-DC). For example, this operation can also be applied to LTE bands. BCs remaining after this stage may be referred as a "final candidate BC list".
  • the terminal may select BCs to be reported by selecting BCs suitable for the requested RAT type from the "final candidate BC list".
  • the terminal may constitute a list including the BCs selected by the terminal (e.g., supportedBandCombinationList) in an order.
  • the terminal may constitute the BC and UE capability to be reported in accordance with the preset order of Rat-Type. (e.g., nr->eutra-nr->eutra).
  • the terminal may constitute featureSetCombination for each BC included in the constituted supportedBandCombinationList, and may constitute a list including each featureSetCombination (e.g., featureSetCombinations).
  • the featureSetCombination may mean a set of feature sets for each band within the selected BC, and the feature set may mean a set of capabilities supported by the terminal in carriers within a specific band.
  • the terminal may compare each BC and feature set combination for each BC with respect to the supportedBandCombinationList.
  • a specific BC e.g., BC #X
  • BC #Y includes BC to be compared, e.g., all the bands of BC #Y.
  • BC #Y may be defined as a fallback BC of BC #X.
  • a new BC list from which all the fallback BCs are removed is constituted, and a list of "candidate feature set combinations" for each of these BCs may be constituted.
  • the "candidate feature set combination" may include both the feature set combinations for NR and EUTRA-NR BC, and may be constituted based on the feature set combination of UE-NR-Capabilities and UE-MRDC-Capabilities containers.
  • featureSetCombinations may be included in both containers of UE-MRDC-Capabilities and UE-NR-Capabilities.
  • the NR feature set may be included only in UE-NR-Capabilities.
  • the terminal may transmit a UE capability information message including UE capability to the base station.
  • the base station then performs scheduling and transmission/reception management to the terminal based on the UE capability received from the terminal.
  • FIG. 14 is a view illustrating a structure of a base station and a terminal radio protocol when performing single cell, carrier aggregation, and dual connectivity according to an embodiment of the disclosure.
  • a wireless protocol of a wireless communication system includes an NR service data adaptation protocol (SDAP) 1425 or 1470, an NR packet data convergence protocol (PDCP) 1430 or1465, an NR radio link control (RLC) 1435 or 1460, and an NR medium access control (MAC) 1440 or 1455 in each of the UE and the NR gNB.
  • SDAP NR service data adaptation protocol
  • PDCP NR packet data convergence protocol
  • RLC radio link control
  • MAC medium access control
  • Main functions of the NR SDAP 1425 or 1470 may include some of the following functions.
  • the UE may receive a configuration as to whether to use a header of the SDAP layer device or a function of the SDAP layer device for each PDCP layer device, each bearer, or each logical channel through an RRC message. If the SDAP header is configured, a 1-bit indicator of NAS reflective QoS of the SDAP header and a 1 bit-indicator of AS reflective QoS may indicate that the UE updates or reconfigures information on mapping of QoS flow and a data bearer in uplink and downlink.
  • the SDAP header may include QoS flow ID information indicating the QoS.
  • the QoS information may be used as data-processing-priority or scheduling information to support a seamless service.
  • Main functions of the NR PDCP 1430 or 1465 may include some of the following functions
  • the reordering function of the NR PDCP layer device is a function of sequentially reordering PDCP PDUs received from a lower layer on the basis of a PDCP sequence number (SN), and may include a function of sequentially transferring the reordered data to a higher layer, or may include a function of directly transmitting data regardless of the sequence, a function of recording PDCP PDUs lost due to the reordering, a function of reporting statuses of the lost PDCP PDUs to a transmitting side, and a function of making a request for retransmitting the lost PDCP PDUs.
  • SN PDCP sequence number
  • Main functions of the NR RLC 1435 or 1460 may include some of the following functions.
  • the sequential delivery function (in-sequence delivery) of the NR RLC layer device is a function of sequentially transmitting RLC SDUs received from a lower layer to the higher layer, and when one original RLC SDU is divided into a plurality of RLC SDUs and then received, the sequential delivery function (In-sequence delivery) of the NR RLC layer device may include a function of reassembling and transmitting the RLC SDUs, a function of reordering the received RLC PDUs on the basis of an RLC sequence number (SN) or a PDCP SN, a function of recording RLC PDUs lost due to the reordering, a function of reporting statuses of the lost RLC PDUs to a transmitting side, and a function of making a request for retransmitting the lost RLC PDUs.
  • SN RLC sequence number
  • PDCP SN a function of recording RLC PDUs lost due to the reordering
  • the sequential delivery function (In-sequence delivery) of the NR RLC layer device may include may include a function of, if a predetermined timer expires even though there are lost RLC SDUs, sequentially transferring all RLC SDUs received up to now to the higher layer.
  • the NR RLC device may process the RLC PDUs sequentially in the order of reception thereof (according to an arrival order regardless of a serial number or a sequence number) and may transfer the RLC PDUs to the PDCP device regardless of the sequence thereof (out-of-sequence delivery).
  • the NR RLC device may receive segments that are stored in the buffer or are to be received in the future, reconfigure the segments to be one RLC PDU, process the RLC PDU, and then transmit the same to the PDCP device.
  • the NR RLC layer device may not include a concatenation function, and the function may be performed by the NR MAC layer, or may be replaced with a multiplexing function of the NR MAC layer.
  • the non-sequential function (Out-of-sequence delivery) of the NR RLC layer device is a function of transferring RLC SDUs received from a lower layer directly to a higher layer regardless of the sequence of the RLC SDUs, and may include, when one original RLC SDU is divided into a plurality of RLC SDUs and then received, a function of reassembling and transmitting the RLC PDUs and a function of storing RLC SNs or PDCP SNs of the received RLC PDUs, reordering the RLC PDUs, and recording lost RLC PDUs.
  • the NR MAC 1440 or 1455 may be connected to a plurality of NR RLC layer devices configured in one UE and main functions of the NR MAC may include some of the following functions.
  • the NR PHY layer 1445 or 1450 perform an operation for channel-coding and modulating higher-layer data to generate an OFDM symbol and transmitting the OFDM symbol through a radio channel or demodulating and channel-decoding the OFDM symbol received through the radio channel and transmitting the demodulated and channel-decoded OFDM symbol to the higher layer.
  • the detailed structure of the radio protocol structure may vary according to a carrier (or cell) operation method.
  • a carrier or cell
  • the base station and the terminal use a protocol structure having a single structure for each layer, such as S00.
  • the base station and the terminal have a single structure up to RLC like S10, but use the protocol structure for multiplexing the PHY layer through the MAC layer.
  • CA carrier aggregation
  • the base station and the terminal have a single structure up to the RLC like S20, but use a protocol structure for multiplexing the PHY layer through the MAC layer.
  • PUCCH transmission is focused on transmission toward a single cell and/or a single transmission point and/or a single panel and/or a single beam and/or a single transmission direction.
  • a cell, a transmission point, a panel, a beam, and/or a transmission direction, etc. that can be distinguished through higher layer/L1 parameters such as TCI state or spatial relation information, or indicators such as cell ID, TRP ID, panel ID are described in a unified manner as a transmission reception point (TRP). Therefore, TRP may be appropriately replaced by one of the above terms.
  • one PUCCH resource used for PUCCH transmission is one, and since only one PUCCH-spatialRelationInfo can be activated for one PUCCH resource, the terminal may maintain the indicated transmission beam when transmitting the PUCCH.
  • the terminal may maintain the indicated transmission beam when transmitting the PUCCH.
  • the PUCCH is repeatedly transmitted over several slots or several mini-slots, a transmission beam according to one indicated PUCCH-spatialRelationInfo needs to be maintained throughout the repeated transmission.
  • the PUCCH may be repeatedly transmitted for each TRP.
  • the terminal must support configuration for PUCCH transmission to a plurality of TRPs.
  • a plurality of beam directions may be indicated for transmission to a plurality of TRPs for one PUCCH, or each of a plurality of PUCCHs including the same UCI may be transmitted to a different TRP, and different beam directions for these PUCCHs needs to be indicated.
  • transmission delay time of uplink control information is minimized and high reliability is achieved.
  • a detailed PUCCH resource configuration method is described in detail in the following embodiments.
  • the base station is a subject that performs resource allocation of the terminal, and may be at least one of a gNode B, gNB, eNode B, Node B, a base station (BS), a radio access unit, a base station controller, or a node on a network.
  • the terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function.
  • UE user equipment
  • MS mobile station
  • a cellular phone a smart phone
  • computer or a multimedia system capable of performing a communication function.
  • an embodiment of the disclosure will be described below using an NR or LTE/LTE-A system as an example, but an embodiment of the disclosure may be applied to other communication systems having a similar technical background or channel type.
  • the embodiments of the disclosure may be applied to other communication systems through some modifications without significantly departing from the scope of the disclosure, as determined by a person having skilled technical knowledge.
  • the content of the disclosure is applicable to FDD and TDD systems.
  • higher signaling is a signal transmission method that is transmitted from the base station to the terminal using a downlink data channel of the physical layer or from the terminal to the base station using an uplink data channel of the physical layer, which may be referred to as RRC signaling, PDCP signaling, or a medium access control element (MAC CE).
  • RRC signaling a downlink data channel of the physical layer or from the terminal to the base station using an uplink data channel of the physical layer
  • MAC CE medium access control element
  • the terminal in determining whether to apply the cooperative communication, may use various methods such as the PDCCH(s) for allocating the PDSCH to which the cooperative communication is applied having a specific format, or the PDCCH(s) for allocating the PDSCH to which the cooperative communication is applied having a specific indicator indicating whether cooperative communication is applied, or the PDCCH(s) for allocating the PDSCH to which cooperative communication is applied being scrambled with a specific RNTI, or assuming the application of cooperative communication in a specific section indicated by an higher layer, etc.
  • an NC-JT case a case in which the terminal receives the PDSCH to which the cooperative communication is applied based on conditions similar to the above.
  • determining the priority between A and B may be mentioned in various ways, such as selecting one having a higher priority according to a predetermined priority rule to perform an operation corresponding thereto, or omitting or dropping an operation having a lower priority.
  • the 5G wireless communication system can support not only a service requiring a high transmission rate, but also a service having a very short transmission delay and a service requiring a high connection density.
  • the coordinated transmission between each cell, TRP, and/or beam is one of the element technologies capable of satisfying various service requirements by increasing the strength of a signal received by the terminal or efficiently controlling interference between cells, TRPs, and/or beams.
  • Joint transmission is a representative transmission technology for the above described cooperative communication, and supports one terminal through different cells, TRPs and/or beams through the joint transmission technology to increase the strength of the signal received by the terminal. Meanwhile, since the characteristics of each cell, TRP, and/or the channel between the beam and the terminal may be greatly different, different precoding, MCS, resource allocation, etc. need to be applied to each cell, TRP, and/or the link between the beam and the terminal.
  • NC-JT non-coherent joint transmission
  • the configuring of individual DL transmission information for each cell, TRP, and/or beam is a major factor that increases the payload required for DL DCI transmission, which may adversely affect the DCI reception performance. Therefore, it is necessary to carefully design a tradeoff between the amount of DCI information and the PDCCH reception performance for JT support.
  • FIG. 15 is a view illustrating an example of an antenna port structure and resource allocation for cooperative communication in a wireless communication system according to an embodiment.
  • radio resource allocation for each TRP according to a joint transmission (JT) scheme and conditions are illustrated.
  • 1500 is an example of coherent joint transmission (C-JT) supporting coherent precoding between cells, TRPs, and/or beams.
  • C-JT coherent joint transmission
  • TRP A 1505 and TRP B 1510 may transmit single data (PDSCH) to the terminal 1515, and a plurality of TRPs may perform joint precoding.
  • PDSCH single data
  • the same DMRS ports e.g., DMRS ports A and B in both TRPs
  • the terminal may receive one DCI information for receiving one PDSCH demodulated based on the DMRS transmitted through the DMRS ports A and B.
  • 1520 is an example of non-coherent joint transmission (NC-JT) supporting non-coherent precoding between each cell, TRP and/or beam.
  • NC-JT non-coherent joint transmission
  • a PDSCH is transmitted to the terminal 1535 for each cell, TRP, and/or beam, and individual precoding may be applied to each PDSCH.
  • Each cell, TRP, and/or beam may transmit a different PDSCH to improve throughput compared to single cell, TRP, and/or beam transmission, or each cell, TRP, and/or beam may repeatedly transmit the same PDSCH to improve reliability compared to single cell, TRP, and/or beam transmission.
  • radio resource allocations may be considered in the case that all the frequency and time resources used for PDSCH transmission by a plurality of TRPs are the same (1540), the case that the frequency and time resources used by a plurality of TRPs do not overlap at all (1545), and the case that some of the frequency and time resources used by a plurality of TRPs overlap (1550).
  • the disclosure provides a repetitive transmission instruction and configuration method for improving NC-JT transmission reliability.
  • DCIs of various types, structures, and relationships may be considered.
  • FIG. 16 is a view illustrating an example of downlink control information (DCI) structure for cooperative communication in a wireless communication system according to an embodiment of the disclosure.
  • DCI downlink control information
  • Case #1 (1600) is an example in which control information for PDSCHs transmitted in (N-1) additional TRPs is transmitted in the same form as control information for PDSCHs transmitted in a serving TRP (same DCI format), in a situation in which different (N-1) PDSCHs are transmitted in (N-1) additional TRPs (TRP #1 to TRP #(N-1)) in addition to serving TRP (TRP #0) used for single PDSCH transmission. That is, the terminal may acquire control information on PDSCHs transmitted in different TRPs (TRP #0 to TRP #(N-1)) through DCI (DCI #0 DCWN-1)) having the same DCI format and the same payload. Meanwhile, in this embodiment and an embodiment to be described later, the control information transmitted in the serving TRP may be classified into first DCI and the DCI transmitted in another TRP (cooperative TRP), which may be referred to as second DCI.
  • second DCI cooperative TRP
  • Case #2 (1605) is an example in which control information for PDSCH transmitted in (N-1) additional TRPs is transmitted in a different form (different DCI format or different DCI payload) from control information for PDSCH transmitted in serving TRP, in a situation in which different (N-1) PDSCHs are transmitted in (N-1) additional TRPs (TRP #1 to TRP #(N-1)) in addition to serving TRP (TRP #0) used for single PDSCH transmission.
  • DCI #0 which is control information for the PDSCH transmitted from the serving TRP (TRP #0)
  • all information elements of DCI format 1_0 to DCI format 1_1 are included, but the secondary DCI (hereinafter, sDCI)) (sDCI #0 to sDCI #(N-2)), which is control information for PDSCHs transmitted in cooperative TRP (TRP #1 to TRP #(N-1)) may include only some of the information elements of DCI format 1_0 to DCI format 1_1.
  • the payload may be small compared to normal DCI (nDCI) including control information related to PDSCH transmitted in the serving TRP, or may include reserved bits as many as the number of bits less than nDCI.
  • nDCI normal DCI
  • the degree of freedom for controlling (allocation) of each PDSCH may be limited according to the contents of the information element included in the sDCI, or since the reception performance of sDCI is superior to that of nDCI, the probability of occurrence of a coverage difference for each DCI may be lowered.
  • Case #3 (1610) is an example in which control information for PDSCHs transmitted in (N-1) additional TRPs is transmitted in a different form (different DCI format or different DCI payload) from control information for PDSCHs transmitted in serving TRP, in a situation in which different (N-1) PDSCHs are transmitted in (N-1) additional TRPs (TRP #1 to TRP #(N-1)) other than serving TRP (TRP #0) used when transmitting a single PDSCH.
  • TRP #1 to TRP #(N-1) serving TRP
  • DCI #0 which is control information for the PDSCH transmitted in the serving TRP (TRP #0)
  • all information elements of DCI format 1_0 to DCI format 1_1 are included
  • control information for PDSCHs transmitted in cooperative TRP TRP #1 to TRP #(N-1)
  • only some of the information elements of DCI format 1_0 to DCI format 1_1 may be included in one 'secondary' DCI (sDCI).
  • the sDCI may include at least one of HARQ-related information such as frequency domain resource assignment, time domain resource assignment, and MCS of cooperative TRPs.
  • HARQ-related information such as frequency domain resource assignment, time domain resource assignment, and MCS of cooperative TRPs.
  • information not included in the sDCI such as a bandwidth part (BWP) indicator or a carrier indicator
  • DCI DCI #0, normal DCI, nDCI
  • the freedom degree for controlling (allocation) of each PDSCH may be limited according to the contents of the information element included in the sDCI.
  • Case #4 (1615) is an example in which control information for PDSCHs transmitted in (N-1) additional TRPs is transmitted through a long DCI (IDCI) such as control information for PDSCHs transmitted in a serving TRP, in a situation in which different (N-1) PDSCHs are transmitted in (N-1) additional TRPs (TRP #1 to TRP #(N-1)) in addition to serving TRP (TRP #0) used for single PDSCH transmission. That is, the terminal may obtain control information on PDSCHs transmitted in different TRPs (TRP #0 to TRP #(N-1)) through a single DCI.
  • IDCI long DCI
  • the complexity of DCI blind decoding of the terminal may not increase, but the degree of freedom of PDSCH control (allocation) may be low, such as the number of cooperative TRPs being limited according to the long DCI payload limitation.
  • sDCI may refer to various auxiliary DCIs such as secondary DCI, or normal DCI (DCI format 1_0 to 1_1 described above) including PDSCH control information transmitted in the cooperative TRP.
  • first DCI and the second DCI may be used to classify the DCI according to the form or characteristic of the DCI or the TRP for transmitting the DCI.
  • DCI transmitted through serving TRP may be expressed as a first DCI
  • DCI transmitted through cooperative TRP may be expressed as a second DCI.
  • case #1, case #2, and case #3 in which one or more DCI (PDCCH) is used for NC-JT support are classified into multiple PDCCH-based NC-JTs
  • Case #4 in which a single DCI (PDCCH) is used for NC-JT support can be classified as a single PDCCH-based NC-JT.
  • cooperation TRP may be replaced with various terms such as “cooperation panel” or “cooperation beam” when applied in practice.
  • the case where NC-JT is applied may be interpreted in various ways according to the situation such as “the case where a terminal receives one or more PDSCHs at the same time in one BWP", “the case where a terminal receives a PDSCH based on two or more transmission configuration indicator (TCI) indications at the same time in one BWP", “the case where a PDSCH received by a terminal is associated with one or more DMRS port groups", etc., but it is used as an expression for convenience of description.
  • TCI transmission configuration indicator
  • the radio protocol structure for NC-JT may be used in various ways according to the TRP deployment scenario. For example, in the case that there is no or small backhaul delay between cooperative TRPs, it is possible to use a structure based on MAC layer multiplexing similar to 1410 of FIG. 14 (CA-like method). On the other hand, in the case that the backhaul delay between cooperative TRPs is so large that the backhaul delay cannot be ignored (e.g., the case that 2 ms or more is required for information exchange such as CSI, scheduling, HARQ-ACK, etc. between cooperative TRPs), similar to 1420 of FIG. 14 , it is possible to secure characteristics robust to delay by using an independent structure for each TRP from the RLC layer (DC-like method).
  • DC-like method DC-like method
  • the CORESET or search space for each TRP may be configured as at least one of the following cases.
  • the above-described index for each CORESET may be named as CORESETPoolIndex, and for CORESETs for which the same CORESETPoolIndex value is configured, the terminal may determine or consider that the PDCCH is transmitted from the same TRP. In the case of a CORESET in which the CORESETPoolIndex value is not configured, the terminal may determine or consider that the default value of CORESETPoolIndex is configured, and the default value may be 0.
  • the second embodiment describes a method of delivering HARQ-ACK information for NC-JT transmission.
  • FIGS. 17a , 17b , 17c , and 17d are views illustrating a method of delivering HARQ-ACK information for NC-JT transmission according to various DCI configuration and PUCCH configuration.
  • FIG. 17a (Option #1: HARQ-ACK for single-PDCCH NC-JT) 17-00 illustrates an example in which HARQ-ACK information for one or more PDSCHs 17-05 scheduled by a TRP is transmitted through one PUCCH resource 17-10 in the case of single-PDCCH-based NC-JT.
  • the PUCCH resource may be indicated through the PRI value and K 1 value in the DCI described above.
  • FIG. 17b (Option #2) to FIG. 17d (Option #4) 17-20, 17-40, 17-60 illustrate the case of multi-PDCCH-based NC-JT.
  • each option may be classified according to the number of PUCCH resources to transmit HARQ-ACK information corresponding to the PDSCH of each TRP and the location of the PUCCH resource on the time axis.
  • FIG. 17b illustrates an example in which the terminal transmits HARQ-ACK information corresponding to the PDSCHs 17-25 and 17-26 of each TRP through one PUCCH resource 17-30.
  • all HARQ-ACK information for each TRP may be generated based on a single HARQ-ACK codebook, or HARQ-ACK information for each TRP may be generated based on a separate HARQ-ACK codebook.
  • HARQ-ACK information for each TRP is concatenated and may be transmitted in one PUCCH resource 17-30.
  • the TRP may be classified into at least one of a set of CORESETs having the same higher layer index, a set of CORESETs belonging to the same TCI state or beam or beam group, and a set of search spaces belonging to the same TCI state or beam or beam group.
  • FIG. 17c (Option #3: inter-slot time-division multiplexed (TDMed) separate HARQ-ACK) 17-40 illustrates an example in which the terminal transmits HARQ-ACK information corresponding to the PDSCH 17-45 and 17-46 of each TRP through PUCCH resources 17-50 and 17-51 of different slots 17-52 and 17-53.
  • TDMed inter-slot time-division multiplexed
  • the slot including the PUCCH resource for each TRP may be determined by the K 1 value described above.
  • the terminal considers that all corresponding PDCCHs are transmitted in the same TRP, and all HARQ-ACK information corresponding to them may be transmitted.
  • HARQ-ACK information concatenated in one PUCCH resource located in the same slot may be transmitted to the TRP.
  • FIG. 17d (Option #4: intra-slot TDMed separate HARQ-ACK) 17-60 illustrates an example of transmitting HARQ-ACK information corresponding to the PDSCHs 17-65 and 17-66 of each TRP through different PUCH resources 17-70 and 17-71 in different symbols in the same slot 17-75.
  • the slot including the PUCCH resource for each TRP may be determined by the K 1 value described above, and in the case that the K 1 value indicated by the plurality of PDCCHs indicates the same slot, the terminal may perform PUCCH resource selection and transmission symbol determination through at least one of the following methods.
  • a PUCCH resource group for HARQ-ACK transmission for each TRP may be configured.
  • the PUCCH resource for HARQ-ACK transmission for each TRP may be selected within the PUCCH resource group for the corresponding TRP.
  • Time division multiplexing (TDM) may be expected between PUCCH resources selected from different PUCCH resource groups, that is, it may be expected that the selected PUCCH resource does not overlap on a symbol basis (within the same slot).
  • the terminal may generate an individual HARQ-ACK codebook for each TRP and then transmit the same in a PUCCH resource selected for each TRP.
  • the PUCCH resource for each TRP may be selected according to the PRI. That is, the PUCCH resource selection process in Rel-15 described above may be independently performed for each TRP.
  • the PRIs used to determine the PUCCH resource for each TRP have to be different. For example, the terminal may not expect that the PRI used to determine the PUCCH resource for each TRP is indicated with the same value.
  • TDM may be expected between PUCCH resources indicated by the PRI for each TRP. That is, it may be expected that the selected PUCCH resources do not overlap on a symbol basis (within the same slot).
  • an individual HARQ-ACK codebook for each TRP may be generated in the PUCCH resource selected for each TRP and then transmitted.
  • the K 1 value may be defined in units of subslots.
  • the terminal may generate a HARQ-ACK codebook for PDSCH/PDCCHs instructed to report HARQ-ACK in the same subslot, and then transmit the same through the PUCCH resource indicated by the PRI.
  • the process of generating the HARQ-ACK codebook and selecting a PUCCH resource may be irrelevant to whether TRP is classified for CORESET and/or search space.
  • one of the options may be configured through a higher layer or may be implicitly selected according to a situation.
  • one of Option 2 joint HARQ-ACK
  • Option 3 or 4 separate HARQ-ACK
  • Option 1 for the former and Option 2 or 3 or 4 for the latter may be selected.
  • an option to be used may be determined according to the selection of a PUCCH resource.
  • PUCCH resources of the same slot are selected in different TRPs
  • HARQ-ACK may be transmitted according to Option 4
  • HARQ-ACK may be transmitted according to Option 2.
  • HARQ-ACK may be transmitted according to Option 3.
  • the configuration for the options may be dependent on the UE capability.
  • the base station may receive the UE capability according to the above-described procedure, and the option may be configured based on this.
  • Option 4 configuration is allowed only for a terminal having a capability supporting intra-slot TDMed separate HARQ-ACK, and a terminal not equipped with the corresponding capability may not expect configuration according to Option 4.
  • FIG. 17e is a flowchart illustrating an example of a method for a terminal to transmit HARQ-ACK information for NC-JT transmission to a base station.
  • the terminal may transmit the capability for the described options to the base station through UE capability report message (e.g., an UECapabilityInformation message), and the base station may explicitly configure which option is applied to the terminal, based on the capability information transmitted by the terminal, or a specific option may be implicitly applied.
  • UE capability report message e.g., an UECapabilityInformation message
  • the terminal may receive PUCCH configuration information from the base station through higher signaling, in step S1780.
  • the PUCCH configuration information may include at least one information of Table 21, Table 22, Table 29, and Table 30, and at least one of PUCCH group configuration information, information for configuring a relationship between a PRI and a PUCCH resource as shown in Table 26, and information for configuring a candidate for a K 1 value as shown in Table 21 may be included.
  • the terminal may receive the DCI for scheduling downlink data from the base station on the PDCCH (this can be mixed with PDCCH reception) in step S1781.
  • step S1782 at least one of HARQ-ACK payload to be transmitted according to the method described above, a PDSCH-to-HARQ feedback timing indicator included in the DCI, and a PRI is identified based on the applied option, and a PUCCH resource to transmit HARQ-ACK may be determined.
  • the terminal may transmit HARQ-ACK information in the determined PUCCH resource in step S1783.
  • FIG. 17f is a flowchart illustrating an example of a method for a base station to receive HARQ-ACK information for NC-JT transmission from a terminal.
  • the base station may receive the UE capability report message (e.g., an UECapabilityInformation message) including capability information on whether the described option transmitted by the terminal is supported, and may explicitly configure which option is applied to the terminal based on the capability information transmitted by the terminal or implicitly apply a specific option.
  • the UE capability report message e.g., an UECapabilityInformation message
  • the base station may transmit PUCCH configuration information to the terminal through higher signaling in step S1785.
  • the PUCCH configuration information may include at least one information of Table 21, Table 22, Table 29, and Table 30, and at least one of PUCCH group configuration information, information for configuring a relationship between a PRI and a PUCCH resource in Table 26, and information for configuring a candidate for a K1 value in Table 21 may be included.
  • the base station transmits the DCI for scheduling downlink data to the terminal on the PDCCH (this may be mixed with PDCCH transmission), and the terminal may identify at least one of a HARQ-ACK payload to be transmitted according to the above-described method, a PDSCH-to-HARQ feedback timing indicator included in the DCI, and a PRI, based on an option applied to the terminal, and may determine a PUCCH resource to transmit HARQ-ACK.
  • the terminal transmits HARQ-ACK information from the determined PUCCH resource, and the base station may receive HARQ-ACK information from the PUCCH resource determined in the same way in step S1787.
  • PUCCH resources may be configured in at least one of the following methods. Meanwhile, transmission of PUCCH resources may mean transmission of PUCCH or transmission of UCI through PUCCH.
  • one purpose of performing repetitive PUCCH transmission to a plurality of TRPs may be overcome with blockage, and using short PUCCH may overcome blockage with less delay compared to using long PUCCH. Therefore, a short PUCCH may be used for repetitive PUCCH transmission to a plurality of TRPs.
  • a change in beam and transmission power may occur between repetitive transmissions.
  • a guard time or offset between short PUCCH transmissions may be required to satisfy the above-described transient time. Therefore, when performing repetitive short PUCCH transmission to a plurality of TRPs, repetitive transmission reflecting the offset may be required.
  • repetitive transmission of the short PUCCH may be performed in a sub-slot unit.
  • FIG. 18a is a view illustrating repetitive short PUCCH transmission in sub-slot units.
  • the length of the sub-slot may be equal to or longer than the length of short PUCCH repetitively transmitted, and the length of the sub-slot may vary depending on time.
  • FIG. 18a illustrates an example in which all sub-slots have the same length as 2 (18-05), but is not limited thereto.
  • the offset between the short PUCCHs may be configured through PUCCH resource scheduling of the base station, such as configuring the start symbol location in the sub-slot of the short PUCCH and the length configuration of the short PUCCH.
  • PUCCH resource scheduling such as configuring the start symbol location in the sub-slot of the short PUCCH and the length configuration of the short PUCCH.
  • a method of configuring the offset between repetitive short PUCCH transmissions may be necessary.
  • the offset may be configured in a sub-slot unit or a symbol unit.
  • FIG. 18a illustrates an example in which the offset is configured as 1 symbol (18-10). 1 symbol is only an example and is not limited thereto.
  • the offset may be configured between repetitive transmissions of each short PUCCH. Alternatively, in the case in which the transmission power change does not occur during repetitive short PUCCH transmission, an offset is not required, and thus an offset may be configured only between repetitive transmissions in which transmission power change occurs.
  • the above-described ⁇ between repetitive transmissions in which transmission power change occurs' may be replaced with an expression such as ⁇ between repetitive transmissions in which beam change occurs' and ⁇ between repetitive transmissions in which spatialRelationInfo is different'.
  • repetitive PUCCH transmission may not occur for each adjacent sub-slot, but may be repeated for each sub-slot of a predetermined period.
  • FIG. 18a illustrates an example in which the above-described repetitive transmission period is configured to 2 sub-slot (18-15), but the period of 2 sub-slots is only an example and is not limited thereto.
  • a preset offset may be reflected in the repetitive transmission period (18-15).
  • repetitive short PUCCH transmission may be performed in a slot or sub-slot.
  • FIG. 18b is a view illustrating repetitive short PUCCH transmission in a slot or sub-slot.
  • the above-described repetitive short PUCCH transmission may be performed within one slot or sub-slot (18-20), or may be performed over a plurality of slots or sub-slots (18-30).
  • an offset between repetitive transmissions may be configured (18-25).
  • the offset may be configured in units of symbols.
  • the offset may be configured between repetitive transmissions of each short PUCCH.
  • an offset is not required, and thus an offset may be configured only between repetitive transmissions in which transmission power change occurs.
  • the 'between repetitive transmissions in which transmission power change occurs' may be replaced with an expression such as 'between repetitive transmissions in which beam change occurs' and 'between repetitive transmissions in which spatialRelationInfo is different' .
  • an offset may be configured or applied only when transmitting a short PUCCH repeatedly, and an offset may not be applied when transmitting repeatedly a long PUCCH. This may be because whether a guard time between transmissions in which the transmission power change occurs is required is different depending on the length of the transmitted PUCCH.
  • an offset between repetitive transmissions may be configured (18-35).
  • the offset can be applied only between repetitive transmissions within one slot or sub-slot.
  • an offset between repetitive transmissions between different slots or sub-slots may be given through configuring a start symbol of the short PUCCH (18-40). That is, the start symbol configuring of the short PUCCH may be applied to repetitive transmission of the first short PUCCH of every slot or sub-slot.
  • the offset may be applied between repetitive transmissions between different slots or sub-slots.
  • the start symbol configured for the short PUCCH may be applied only to the first short PUCCH transmission among all the repetitive short PUCCH transmissions.
  • the above-described offset may be configured between repetitive transmissions of each short PUCCH.
  • an offset is not required, and thus an offset may be configured only between repetitive transmissions in which transmission power change occurs.
  • the 'between repetitive transmissions in which transmission power change occurs' may be replaced with an expression such as 'between repetitive transmissions in which beam change occurs' and 'between repetitive transmissions in which spatialRelationInfo is different'.
  • whether an offset is configured and/or applied may vary according to the length of the repeatedly transmitted PUCCH. For example, an offset may be configured or applied only when transmitting a short PUCCH repeatedly, and an offset may not be applied when transmitting a long PUCCH repeatedly. The reason may be that whether a guard time between transmissions in which the transmission power change occurs is required is different depending on the length of the transmitted PUCCH.
  • FIG. 18c is another view illustrating the repetitive PUCCH transmission in a slot or sub-slot in a wireless communication system according to an embodiment of the disclosure.
  • some PUCCHs among all repetitive transmissions may span a boundary of a slot or sub-slot (18-50).
  • a treatment method for this case at least one of the following methods may be included.
  • Method 1 A symbol crossing a slot or sub-slot boundary in the repetitive PUCCH transmission may be dropped.
  • the configured number of repetitive transmissions and the actual number of repetitive transmissions are the same.
  • a symbol over a slot or sub-slot boundary in the repetitive PUCCH transmission may be regarded as a new repetitive transmission.
  • the actual number of the repetitive transmissions may be greater than the configured number of repetitive transmissions.
  • Method 3 The repetitive transmission over a slot or sub-slot boundary in the repetitive PUCCH transmission is dropped.
  • the actual number of repetitive transmissions may be smaller than the configured number of repetitive transmissions.
  • the repetitive PUCCH transmission that is, the repetitive transmission over a slot or sub-slot boundary is shifted to the next slot or sub-slot.
  • the shifted location may be the first symbol of the next slot or sub-slot, or a location configured as the PUCCH start symbol.
  • Method 5 It is scheduled so that the repetitive PUCCH transmission, that is, the repetitive transmission over a slot or sub-slot boundary is not occurred. In this case, the terminal may not expect repetitive transmission across the slot or sub-slot boundary.
  • one or more DL symbols exist in a slot or sub-slot, and the methods may be similarly applied even in the case that the repetitive PUCCH transmission overlaps the DL symbols.
  • the lengths of repetitive PUCCH transmissions may not be the same.
  • the case in which soft combining between PUCCHs having different lengths is not performed may be occurred. Therefore, at least one of the following constraint condition or PUCCH encoding may need to be changed.
  • the number of TRPs may be smaller than the number of repetitive transmissions.
  • a mapping rule for which TRP each repetitive transmission is transmitted is required.
  • a transmission pattern for each TRP may be periodically configured.
  • FIG. 19 is a view illustrating an example of a mapping rule between repetitive PUCCH transmission and TRP according to an embodiment of the disclosure.
  • FIG. 19 illustrates a transmission pattern for each TRP in the case that the total number of repetitive transmissions is N and the number of receptions TRPs is K.
  • Each TRP is allocated with L consecutive repeated transmissions in a round-robin manner.
  • the L value may be configured to one of 1, 2, . . . , ⁇ N / K ⁇ , ⁇ N K + 1 ⁇ (19-10, 19-20). If the L value is small, TRP switching becomes more frequent, so there is an advantage in that the probability of early termination increases, but there is a disadvantage that more overhead for TRP switching is required.
  • a transmission pattern for each TRP for all repetitive transmissions may be indicated. For example, in the case that two receiving TRPs are designated for 4 repetitive transmissions and they are named TRP #1 and TRP #2, the pattern for repetitive transmission may be indicated as ⁇ TRP #1, TRP #1, TRP #1, TRP #2 ⁇ .
  • the UCI may be transmitted to different TRPs on each of the plurality of PUCCH resources by including the same UCI on a plurality of PUCCH resources.
  • different beams may be configured for each of the plurality of PUCCH resources, and in the case that the repetitive transmission is configured for PUCCH resources, the entire repetitive transmission may be transmitted to the same TRP.
  • the terminal should determine whether a specific UCI is transmitted on a plurality of PUCCH resources or is transmitted on a single PUCCH resource as in the prior art, and for this, at least one of the following methods may be used.
  • a constraint condition for the PUCCH set may be configured. For example, in the case that repetitive transmission for PUCCH resources in the PUCCH set is not configured, all PUCCH resources in the PUCCH set may be transmitted in the same slot or sub-slot, at this time, the overlap on the time axis between the PUCCH resources in the PUCCH set may not be allowed. As another example, a maximum value of the maximum number of PUCCH resources in the PUCCH set may be limited. As an example, the maximum value of the number of PUCCH resources may be 2.
  • Independent UE capability may be required for each option related to PUCCH transmission to a plurality of TRPs described above.
  • some of the terminals may not support repetitive short PUCCH transmission.
  • the terminal reports whether to support short PUCCH repetition transmission to the base station through the capability report, and the base station may configure short PUCCH repetition only to the terminal supporting short PUCCH repetition transmission after receiving the UE capability report.
  • the terminal may report a minimum offset value between repetitions that can be supported during repetitive short PUCCH transmission to the base station through the capability report in a symbol, slot, sub-slot, or absolute time unit.
  • the base station may schedule the PUCCH with reference to the minimum supportable offset of the terminal after receiving the UE capability report.
  • the minimum offset may be reported with regard to not only an offset between repetitive short PUCCH transmissions, but also an offset between short PUCCH-long PUCCH repetitive transmissions, and an offset between long PUCCH-long PUCCH repetitive transmissions.
  • the minimum offset may not be an offset applied to all repetitive PUCCH transmissions.
  • the minimum offset may be a value applied only between repetitive PUCCH transmissions accompanied by a beam/transmission power change.
  • the above description is described only for the case of repetitive transmission of the same PUCCH of the embodiment 3-1, but it is similarly applicable to the case of transmissions of a plurality of PUCCH resources of the embodiment 3-2.
  • the maximum number of repetitive PUCCH transmissions in a slot or sub-slot may also be different for each terminal. Accordingly, the terminal may report the maximum number of repetitive PUCCH transmissions to the base station through the capability report. Meanwhile, the length of the sub-slot supported by the terminal may also differ for each terminal, and the length of the repeatedly transmitted sub-slot may be reported to the base station through the capability report. In addition, it is possible to report the combination of the above capabilities to the base station. For example, the maximum number of repetitive PUCCH transmissions in a slot for each length of a sub-slot may be reported to the base station through capability reporting. For the convenience of description, the above description is described only for the case of repetitive transmission of the same PUCCH of the embodiment 3-1, but it is similarly applicable to the transmissions of a plurality of PUCCH resources of the embodiment 3-2.
  • FIGS. 20 and 21 are views illustrating an example of application of a transmission power control (TPC) command according to a resource allocation method for repetitive PUCCH transmission scheduled in a PDCCH and a mapping rule between TRPs according to various embodiments of the disclosure.
  • the terminal may increase or reduce the power for PUCCH transmission by identifying the resources configured for the PUCCH and TPC command information indicated by the PDCCH, described above.
  • TRP may be expressed by being replaced with terms such as cell, transmission point, panel, node, TP, beam and/or transmission direction.
  • the TRP may be classified according to an index configured in CORESET (e.g., CORESETPoolIndex).
  • CORESETPoolIndex an index configured in CORESET
  • the terminal may determine or consider that the PDCCH is transmitted from the same TRP for CORESETs in which the same CORESETPoolIndex value is configured.
  • different beam directions may be indicated for each PUCCH for PUCCH transmission to a plurality of TRPs.
  • FIG. 20 is a view illustrating a resource allocation method for repetitive transmission of an inter-slot-based PUCCH and an application method of power adjustment according to a mapping rule between TRPs according to an embodiment of the disclosure.
  • the base station may allocate resources of PDSCH#1 and PDSCH#2 using DCI formats 1_0, 1_1, and 1_2 of PDCCH#1.
  • the base station may indicate a field for allocating PDSCH resources transmitted by the base station using at least one of the DCI formats 1_0, 1_1, and 1_2.
  • the base station may include information indicating a PUCCH resource for transmitting HARQ-ACK/NACK information indicating whether the terminal has successfully received the PDSCH (e.g., PUCCH resource indicator (PRI))) and information instructing to adjust the power of the PUCCH resource (e.g., a TPC command) in at least one of the DCI formats 1_0, 1_1, and 1_2, and may transmit it to the terminal.
  • a PUCCH resource for transmitting HARQ-ACK/NACK information indicating whether the terminal has successfully received the PDSCH
  • information instructing to adjust the power of the PUCCH resource e.g., a TPC command
  • a case in which one PUCCH resource is configured in one slot may be referred to as inter-slot repetition.
  • FIG. 21 is a view illustrating a resource allocation method for repetitive transmission of an intra-slot-based PUCCH and an application method of power adjustment according to a mapping rule between TRPs according to an embodiment of the disclosure.
  • the base station may allocate resources of PDSCH#1, PDSCH#2, PDSCH#3, and PDSCH#4 using DCI formats 1_0, 1_1, and 1_2 of PDCCH#2.
  • the base station may indicate a field for allocating PDSCH resources transmitted by the base station using at least one of the DCI formats 1_0, 1_1, and 1_2.
  • the base station may include information indicating a PUCCH resource for transmitting HARQ-ACK/NACK information indicating whether the terminal has successfully received the PDSCH (e.g., PRI), and information instructing to adjust the power of the PUCCH resource (e.g., TPC command) in at least one of the DCI formats 1_0, 1_1, and 1_2 and may transmit it to the terminal.
  • a case in which a plurality of PUCCH resources is configured in one slot as illustrated in FIG. 21 may be referred to as intra-slot repetition.
  • one or a plurality of PUCCH resources may be configured in one slot using a higher layer parameter, and a period thereof may be configured.
  • the HARQ ACK/NACK information transmitted by the terminal may be transmitted through the same encoding for each repetitive PUCCH resource (e.g., PUCCH#1-1 to #1-4, PUCCH#2-1 to #2-4) configured by the base station.
  • each repetitive PUCCH resource e.g., PUCCH#1-1 to #1-4, PUCCH#2-1 to #2-4
  • the basic uplink beamforming direction for PUCCH transmission of the terminal configured by the base station may be determined by various parameters and index values (e.g., PUCCH-PathlossReferenceRS, referenceSignal p0-PUCCH-Id, etc.) in each higher layer parameter PUCCH-SpatialRelationInfo.
  • Various parameters and indexes e.g., PUCCH-PathlossReferenceRS, reference Signal p0-PUCCH-Id, etc.
  • the higher layer parameter PUCCH-SpatialRelationInfo may be used to configure a spatial setting for PUCCH transmission and a parameter for PUCCH power control.
  • the base station may configure the various parameters and index values (e.g., PUCCH-SpatialRelationInfoID, PUCCH-PathlossReferenceRS-ID, reference Signal, p0-PUCCH-Id, closedLoopIndex, etc. in Table 31) to one set or individually, in one PUCCH-SpatialRelationInfo in the higher layer.
  • the terminal may determine that information corresponding to the beamforming direction configured by the base station for PUCCH transmission is the same.
  • the terminal may transmit PUCCH#0-1 to PUCCH#0-4 by applying the same beamforming direction based on the parameter and index in the configured PUCCH-SpatialRelationInfo.
  • the base station may configure the various parameters and index values (e.g., PUCCH-SpatialRelationInfoID, PUCCH-PathlossReferenceRS-ID, reference Signal, p0-PUCCH-Id, closedLoopIndex, etc. in Table 31) to one set or individually in one PUCCH-SpatialRelationInfo in the higher layer.
  • parameters and index values e.g., PUCCH-SpatialRelationInfoID, PUCCH-PathlossReferenceRS-ID, reference Signal, p0-PUCCH-Id, closedLoopIndex, etc. in Table 31
  • the terminal is configured to one set instead of a plurality of sets for each parameter, and if repetitive PUCCH resources allocated to correspond to one or repetitive PDSCH resources are repeated within one slot or within one subslot, the one set of the various parameters and indexes in the configured one PUCCH-SpatialRelationInfo may be applied during the designated slot or subslot.
  • the terminal may apply one set of the various parameters and indexes in the configured one PUCCH-SpatialRelationInfo during the designated slot or subslot.
  • the terminal may apply one set of the various parameters and indexes in the configured one PUCCH-SpatialRelationInfo during the designated slot or subslot.
  • the base station may configure the higher layer parameter or index value in a partially changed form, and configure two or more beamforming directions in PUCCH resources that are repeated as one set.
  • a method for this a method according to RRC configuration and a method according to MAC CE message configuration may be possible.
  • a method for configuring two or more beamforming directions for repetitive PUCCH transmission and controlling transmission power of PUCCH is proposed.
  • the configuration of two or more beamforming directions may mean that the terminal may transmit PUCCHs in different TRPs, respectively.
  • the base station may configure the parameter or index value constituted in the configured one higher layer parameter (e.g., PUCCH-SpatialRelationInfo-r17) to one value.
  • the base station may configure one parameter pucch-SpatialRelationInfoId in the higher layer parameter (e.g., PUCCH-SpatialRelationInfo-r17), and may configure closedLoopIndex corresponding to each pucch-PathlossReferenceRS-Id and p0-PUCCH-Id to i0 or i1.
  • the pucch-SpatialRelationInfoId configuration value may be configured to 1, the pucch-PathlossReferenceRS-Id configuration value may be configured to 1, the P0-PUCCH-Id configuration value may be configured to 2, and the closedLoopIndex configuration value may be configured to i0.
  • a pucch-SpatialRelationInfoId configuration value may be configured to 2
  • a pucch-PathlossReferenceRS-Id configuration value may be configured to 2
  • a P0-PUCCH-Id configuration value may be configured to 1
  • a closedLoopIndex configuration value may be configured to i1.
  • the terminal may identify whether the closedLoopIndex configuration value is configured to i0 (0) or il (1), based on the 1-bit value (e.g., 0 or 1) of the closedLoopIndex field of the DCI in the PDCCH where the command to perform group common PUCCH-based power control is possible.
  • the 1-bit value e.g., 0 or 1
  • the base station may configure at least two parameters or index values constituted in the configured one higher layer parameter (e.g., PUCCH-SpatialRelationInfo-r17).
  • the higher layer parameter PUCCH-SpatialRelationInfo-r17 may be used to configure spatial setting for PUCCH transmission and parameters for PUCCH power control.
  • an higher layer parameter (e.g., PUCCH-SpatialRelationInfo-r17) may be configured as shown in Table 32 below.
  • pucch-SpatialRelationInfoId1 and pucch-SpatialRelationInfoId2 may be configured in the higher layer parameter PUCCH-SpatialRelationInfo-r17, respectively.
  • PUCCH-SpatialRelationInfo-r17 parameters and index values corresponding to each pucch-SpatialRelationInfoId1 (e.g., pucch-PathlossReferenceRS-Id1, p0-PUCCH-Id1, ClosedLoopIndex1, etc.) and parameters and index values corresponding to pucch-SpatialRelationInfoId2 (e.g., pucch-PathlossReferenceRS-Id2, p0-PUCCH-Id2, and ClosedLoopIndex2, etc.) may be configured.
  • the terminal may determine information related to the beamforming direction according to the number of repetitive PUCCHs.
  • a parameter e.g., nrofSlots
  • the terminal may determine that pucch-SpatialRelationInfoId1 is configured for a resource for the first transmitted PUCCH, and pucch-SpatialRelationInfoId2 is configured for a resource for the second transmitted PUCCH.
  • the terminal may transmit the first PUCCH based on the parameter and index value corresponding to pucch-SpatialRelationInfoId1, and transmit the second PUCCH based on the parameter and index value corresponding to pucch-SpatialRelationInfoId2.
  • a mapping relationship between a PUCCH resource repeatedly transmitted and a beamforming direction may be indicated through a higher layer parameter (e.g., SpatialMapping).
  • a higher layer parameter e.g., SpatialMapping
  • the terminal may determine that pucch-SpatialRelationInfoId1 is configured for resources for the first and third transmitted PUCCHs, and pucch-SpatialRelationInfoId2 is configured for resources for the second and fourth transmitted PUCCHs.
  • pucch-SpatialRelationInfoId1 is configured for resources for the first and third transmitted PUCCHs
  • pucch-SpatialRelationInfoId2 is configured for resources for the second and fourth transmitted PUCCHs.
  • the terminal may determine that pucch-SpatialRelationInfoId1 is configured for resources for the first and second transmitted PUCCHs, and pucch-SpatialRelationInfoId2 is configured for resources for the third and fourth transmitted PUCCHs.
  • the configuration shown in Table 33 may be considered for the PUCCH operation that is repeated in one set with different beamforming directions.
  • the base station may further configure using spatialRelationInfoToAddModListExt in addition to the basic configuration of the configured spatialRelationInfoToAddModList, or may further configure by replacing the basic configuration of spatialRelationInfoToAddModList with spatialRelationInfoToAddModList2.
  • the mapping relationship between the transmitted PUCCH resource and the beamforming direction may be determined based on the SpatialMapping parameter of Table 33. For example, if the higher layer parameter SpatialMapping is configured to cyclicMapping, the terminal may determine that the information related to a plurality of beamforming directions configured in SpatialRelationInfoToAddMod-List and SpatialRelationInfoToAddModListExt is configured to be applied to PUCCH resources that are repeatedly transmitted by crossing each other (e.g., 20-30 in FIG. 20 ).
  • the terminal may determine that the information related to a plurality of beamforming directions configured in SpatialRelationInfoToAddModList and SpatialRelationInfoToAddModListExt is configured to be applied to PUCCH resources that are sequentially and repeatedly transmitted to each other (e.g., 20-60 in FIG. 20 ).
  • the terminal may determine that SpatialRelationInfoToAddModList is configured for resources for the first and third transmitted PUCCHs, and SpatialRelationInfoToAddModListExt is configured for resources for the second and fourth transmitted PUCCHs.
  • the terminal may determine that SpatialRelationInfoToAddModList is configured for resources for the first and second transmitted PUCCHs, and SpatialRelationInfoToAddModListExt is configured for resources for the third and fourth transmitted PUCCHs.
  • the base station may basically configure using MAC CE message in addition to the PUCCH-SpatialRelationInfo-r16 or PUCCH-SpatialRelationInfo-r17 configuration.
  • MAC CE message of FIG. 22 is basically configured first in the higher layer (RRC) according to the above described methods A-1, A-2-1, and A-2-2 and is then additionally updated in the MAC layer is illustrated.
  • FIG. 22 is a view illustrating a format of an Enhanced PUCCH Spatial Relation Activation/Deactivation MAC CE message according to an embodiment of the disclosure.
  • a Serving Cell ID may mean an ID of a serving cell to which the terminal is accessed
  • a BWP ID may mean a frequency-side resource index corresponding to the BWP ID among the BWPs corresponding to the Serving Cell ID
  • a PUCCH resource ID may indicate a PUCCH resource corresponding to a specific PUCCH resource ID among the PUCCH resources configured in the BWP ID.
  • the base station may constitute MAC CE to map or reconfigure Spatial Relation Info ID 1 and Spatial Relation Info ID 2 indicating pucch-SpatialRelationInfoId configured in the RRC to one PUCCH resource ID and may transmit it to the terminal.
  • Spatial Relation Info ID1 and Spatial Relation Info ID2 may be applied to PUCCH transmission alternately or sequentially according to the mapping method configured in RRC, that is, the cyclicMapping and sequentialMapping.
  • FIG. 22 is designed as a structure for additionally configuring and changing N number of PUCCH resource ID(s) at the same time, but if additional configuration and change of spatial relation info ID among PUCCH resource ID(s) is unnecessary, the Oct resource of the corresponding MAC CE may be omitted.
  • Table 34 below shows the power adjustment equation for PUCCH transmission.
  • g(i) is a parameter for performing closed-loop power control, and may vary depending on whether the terminal performs accumulation-based power control or absolute value-based power control. Whether the terminal performs accumulation-based power control or absolute value-based power control may be transmitted to the terminal through higher layer signaling (dedicated RRC signaling). For example, when the accumulation-enabled parameter is configured to 'on', the terminal may perform accumulation-based power control, and when the accumulation-enabled parameter is configured to 'off', the terminal may perform absolute value-based power control.
  • higher layer signaling dedicated RRC signaling
  • P 0 PUCCH, f, c means a value of P 0 PUCCH at the frequency f of the serving-cell c, is a parameter composed of P 0_ NOMINAL_PUCCH + P 0_ UE _ PUCCH , and is a value notified by the base station to the terminal through higher layer signaling (RRC signaling).
  • RRC signaling higher layer signaling
  • q u in P 0 PUCCH denotes an index of P 0 PUCCH , and may have different indexes depending on a beam used for PUCCH transmission or a service type of the corresponding PUCCH (i.e., eMBB usage or URLLC usage).
  • PL which is the path loss value calculated by the terminal, may be calculated through the received power of the downlink RS transmitted by the base station. Since there is no cell-specific reference signal (CRS) in the NR, the PL may be measured by the terminal through the RS resource indicated by the base station through q u .
  • q u may be a resource index of a channel state information-reference signal (CSI-RS) or a resource index of a synchronization signal block (SSB) resource.
  • CSI-RS channel state information-reference signal
  • SSB synchronization signal block
  • bit width of the field including the TPC command (a value indicating the degree of increase or reduction of power using a value of ⁇ PUCCH, b , f , c ) information is maintained to 2 bits (TPC command for scheduled PUCCH) in DCI format 1_0, 1_1, or 1_2 as in a general method may be considered.
  • TPC command for scheduled PUCCH a value indicating the degree of increase or reduction of power using a value of ⁇ PUCCH, b , f , c ) information
  • TPC command for scheduled PUCCH in DCI format 1_0, 1_1, or 1_2 as in a general method
  • the terminal may equally apply the power reduction to all repetitive PUCCH resources scheduled in the DCI.
  • the reduction amount may be determined by configuring the value of Accumulated ⁇ PUCCH, b , f , c in the equation for determining the PUCCH transmission power described in Table 34 above to -1 (dB).
  • the terminal may apply to maintain the same power for all repetitive PUCCH resources scheduled in DCI.
  • the reduction amount may be determined by configuring the value of Accumulated ⁇ PUCCH, b , f , c in the equation for determining the PUCCH transmission power to 0 (dB).
  • the terminal may apply the same power increase to all repetitive PUCCH resources scheduled in the DCI.
  • the increase amount may be determined by configuring the value of Accumulated ⁇ PUCCH, b , f , c in the equation for determining the PUCCH transmission power to 1/3 (dB).
  • the terminal may apply the power reduction recursively repeatedly to all PUCCH resources scheduled in the DCI.
  • the reduction amount may be determined by configuring the value of Accumulated ⁇ PUCCH, b , f , c in the equation for determining the PUCCH transmission power to -1 (dB) to reflect the reduction or increase as many times as the number of repetitive transmissions.
  • the terminal may apply the power increase recursively repeatedly to all PUCCH resources scheduled in the DCI.
  • the increase amount may be determined by configuring the value of Accumulated ⁇ PUCCH, b , f , c in the equation for determining the PUCCH transmission power to 1/3 (dB) to reflect the reduction or increase as many times as the number of repetitive transmission.
  • the DCI for the TPC command is 2 bits, and if one Spatialrelationinfo for configuring the beamforming direction to the repetitive PUCCH resource as in various embodiments of method A-1/A-2-1/A-2-2/A-2-3 is configured, a method of selectively performing power adjustment for the PUCCH transmission for a plurality of PUCCH resources may be required.
  • the value of the TPC command field in the DCI received by the terminal is 00, according to the total number of repetitive transmissions of the configured PUCCH resource, the power may be reduced or increased for at least a part of the total number. For example, if the total number of repetitions is 2, power adjustment may be applied only to the initial transmission or the last transmission. For example, if the total number of repetitions is 4, the power adjustment can be applied only to the initial 1 or 2 transmissions or 3 or 4 transmissions.
  • the bit width of the field including the TPC command (a value indicating the degree of increase/reduction in power using a value of ⁇ PUCCH, b , f , c ) information in DCI format 1_0, 1_1, or 1_2 may be assigned to 3 bits (TPC command for scheduled PUCCH).
  • TPC command for scheduled PUCCH.
  • the first 1 bit e.g., LSB or MSB
  • the first bit if the first 1 bit is 0, it may be interpreted as information indicating to correspond to the first configured PUCCH resource, and if the first bit is 1, it may be interpreted as information indicating to correspond to the second configured PUCCH resource.
  • the remaining 2 bits can be applied in the same manner as in the embodiment of method B-1.
  • the first 1 bit (e.g., LSB or MSB) of the 3 bits is 0, it may be interpreted as information indicating to correspond to the first and second configured PUCCH resources, and if the first 1 bit is 1, it may be interpreted as information indicating to correspond to the third and fourth configured PUCCH resources.
  • the remaining 2 bits may be applied in the same manner as in the embodiment of method B-1.
  • the first bit e.g., LSB or MSB
  • the first bit may be interpreted as information indicating that the first configured PUCCH resource corresponds to all PUCCH resources included in the allocated slot or subslot
  • the first bit if the first bit is 1, it may be interpreted as information indicating to correspond to the PUCCH resource allocated after the slot or subslot.
  • the remaining 2 bits may be applied in the same way as in the embodiment of method B-1.
  • the bit width of the field including the TPC command (a value indicating the degree of increase or reduction of power by using a value of ⁇ PUCCH, b , f , c ) information in DCI format 1_0, 1_1, or 1_2 may be assigned to 4 bits (TPC command for scheduled PUCCH).
  • TPC command for scheduled PUCCH.
  • the first 2 bits (e.g., 2 LSB or 2 MSB) among the 4 bits may be indicated to be mapped to the order of PUCCH resources repeatedly transmitted.
  • the terminal may determine that the first transmitted PUCCH resource is indicated if the 2 bits are 00, the second transmitted PUCCH resource is indicated if the 2 bits are 01, the third transmitted PUCCH resource is indicated if the 2 bits are 10, and the fourth transmitted PUCCH resource is indicated if the 2 bits are 11.
  • the terminal may sequentially interpretate by associating two sets from the order in which PUCCH resources is first transmitted to one bit information.
  • the remaining 2 bits may be applied in the same manner as in the embodiment of method B-1.
  • the first 2 bits (e.g., 2 LSB or 2 MSB) of 4 bits
  • 00 may be interpretated as information indicating to correspond to all PUCCH resources included in a slot or subslot to which the first configured PUCCH resource is allocated
  • 01 may be interpretated as information indicating to correspond to a PUCCH resource allocated immediately after the slot or subslot
  • 10 may be interpretated as information indicating to correspond to a PUCCH resource allocated immediately after the slot or subslot indicated in 01
  • 11 may be interpretated as information indicating to correspond to a PUCCH resource allocated immediately after the slot or subslot indicated in 10.
  • the remaining 2 bits can be applied in the same way as in the embodiment of method B-1.
  • the same method as in the above described method B-1, B-2-1 or B-2-2 may be applied to the method of configuring the bit width of a field including TPC command (a value indicating the degree of increase or decrease of power by using a value of ⁇ PUCCH, b , f , c ) information in DCI format 2_2.
  • the terminal may identify 1 bit corresponding to the Closed loop indicator and determine the direction of beamforming by expanding the ⁇ Method A-2-1> described above.
  • the terminal may identify whether closedLoopIndex is configured to i0 (0) or i1 (1), based on the 1-bit value (e.g., 0 or 1) of the Closed loop indicator field included in DCI (e.g., DCI format 2_2).
  • FIGS. 20 and 21 illustrate an inter-slot repetition scenario and an intra-slot repetition scenario.
  • Method B-3-1, Method B-3-2, and Method B-3-3 proposed below may mean that two or more beamforming directions for repetitive PUCCH transmission are configured to the terminal based on methods A-2-1, A-2-2, and A-2-3 described above and the like.
  • the bit width of the field including the TPC command (a value indicating the degree of increase or decrease of power by using a value of ⁇ PUCCH, b , f , c ) information in DCI format 1_0, 1_1, or 1_2 may be assigned to 2 bits (TPC command for scheduled PUCCH).
  • TPC command for scheduled PUCCH.
  • the terminal may equally apply power reduction to all PUCCH resources with different spatialrelationinfo scheduled in the PDCCH while repeating.
  • the reduction amount may be determined by configuring the value of accumulated ⁇ PUCCH, b , f , c in the equation for determining the PUCCH transmission power described in Table 34 above to -1 (dB).
  • the terminal may apply to maintain the same power for all PUCCH resources with different spatialrelationinfo scheduled in the DCI while repeating.
  • the reduction amount may be determined by configuring the value of Accumulated ⁇ PUCCH, b , f , c in the equation for determining the PUCCH transmission power to 0 (dB).
  • the terminal may apply the same power increase to all PUCCH resources with different spatialrelationinfo scheduled in DCI while repeating.
  • the increase amount may be determined by configuring the value of Accumulated ⁇ PUCCH, b , f , c in the equation for determining the PUCCH transmission power to 1/3 (dB).
  • the terminal may repeatedly recursively apply power reduction to all PUCCH resources with different spatialrelationinfo scheduled in DCI while repeating.
  • the reduction amount may be configured by configuring the value of Accumulated ⁇ PUCCH, b , f , c in the equation for determining the PUCCH transmission power may be configured to -1 (dB) to reflect the reduction or increase by the number of repetitive transmission.
  • the terminal may recursively repeatedly apply the power increase to all repetitive PUCCH resources scheduled in the DCI.
  • the increase amount can be configured to reflect the reduction or increase by the number of times of repetitive transmission by configuring the value of Accumulated ⁇ PUCCH, b , f , c in the equation for determining the PUCCH transmission power to 1/3 (dB).
  • the bit width of the field including the TPC command (a value indicating the degree of increase or reduction of power by using a value of ⁇ PUCCH, b , f , c ) information in DCI format 1_0, 1_1, or 1_2 may be assigned to 3 bits (TPC command for scheduled PUCCH).
  • TPC command for scheduled PUCCH.
  • the first 1-bit field (e.g., LSB or MSB) of the 3 bits is 0, it may be interfered as information indicating to correspond to a first PUCCH resource allocated to be transmitted first (corresponding to both a case in which in a higher layer, the SpatialMapping scheme is configured to cyclicMapping and a case in which the SpatialMapping scheme is configured to sequentialMapping) or the PUCCH resource corresponding to SpatialrelationinfoId1 described in method A-2-1/A-2-2/A-2-3 above.
  • the first 1-bit field (e.g., LSB or MSB) of the 3 bits is 1, it is interpreted as information indicating to correspond to a second PUCCH resource allocated to be transmitted second (a case in which the SpatialMapping scheme is configured to cyclicMapping in the higher layer) or information indicating to correspond to the PUCCH resource corresponding to SpatialrelationinfoId2 described in method A-2-1/A-2-2/A-2-3 above. It may be understood that the PUCCH resources repeatedly transmitted from the third thereafter are applied in conjunction according to the above-described SpatialMapping configuration scheme. The remaining 2 bits of the TPC field may be equally applied as in the embodiment of Method B-1.
  • the closed loop indicator (1 bit) described in ⁇ Method A-2-1> is configured in the first 1-bit field (e.g., LSB or MSB) among the 3 bits, and the terminal identifies 1 bit corresponding to the closed loop indicator and determine the beamforming direction by expanding the ⁇ Method A-2-1> described above.
  • the first 1-bit field e.g., LSB or MSB
  • the terminal may identify whether closedLoopIndex is configured with i0 (0) or i1(1) based on the 1-bit value (e.g., 0 or 1) of the closed loop indicator field included in DCI (e.g., DCI format 2_2) and determine the beamforming direction through the identification.
  • DCI e.g., DCI format 2_2
  • the bit width of the field including the TPC command (a value indicating the degree of increase or reduction of power by using a value of ⁇ PUCCH, b , f , c ) information in DCI format 1_0, 1_1, or 1_2 may be assigned to 4 bits (TPC command for scheduled PUCCH).
  • TPC command for scheduled PUCCH.
  • the first 1-bit field (e.g., LSB or MSB) among the 4 bits may include information for the first PUCCH resource allocated to be transmitted first (corresponding to both a case in which the SpatialMapping scheme is configured to cyclicMapping in a higher layer and a case in which the SpatialMapping scheme is configured to sequentialMapping) or for a PUCCH resource (e.g., PUCCH#1-1, PUCCH#1-3 PUCCH#2-1, PUCCH #2-2) corresponding to the SpatialrelationinfoId1 described in method A-2-1/A-2-2/A-2-3 above.
  • a PUCCH resource e.g., PUCCH#1-1, PUCCH#1-3 PUCCH#2-1, PUCCH #2-2
  • the terminal determines that the TPC operation of the last two bits of the TPC field is not applied, and in the case in which if the first bit of the TPC field is 1, the terminal may determine that the TPC operation of the last two bits of the TPC field is applied.
  • the terminal determines that the TPC operation of the last two bits of the TPC field is not applied, and in the case in which if the first bit of the TPC field is 1, the terminal may determine that the TPC operation of the last two bits of the TPC field is applied.
  • the second 1 bit in the TPC field consisting of 4 bits may include information for the second PUCCH resource allocated to be transmitted second (a case in which the SpatialMapping scheme is configured to cyclicMapping in the higher layer) or for a PUCCH resource (e.g., PUCCH#1-2, PUCCH#1-4, PUCCH#2-3, PUCCH#2-4) corresponding to Spatialrelationinfo-Id2 described in the above method A-2-1/A-2-2/A-2-3.
  • a PUCCH resource e.g., PUCCH#1-2, PUCCH#1-4, PUCCH#2-3, PUCCH#2-4
  • the terminal determines that the TPC operation of the last two bits field of the TPC field is not applied, and in the case that the second 1 bit of the TPC field received by the terminal is 1, the terminal determines that the TPC operation of the last two bits field of the TPC field is applied.
  • the first 2 bits of the 4 bits field are mapped to each PUCCH resource, but in various embodiments, at least one of 00 and 11 in the first 2 bits of the TPC field is mapped to PUCCH#1-1 to #1-4 resources of 20-30 of FIG. 20 , 01 may be mapped to PUCCH#1-1, #1-3 resources, and 10 may be mapped to PUCCH#1-2, #1-4 resources.
  • the last 2 bits of the TPC can be applied in the same way as in the embodiment of method B-1.
  • FIG. 23 illustrates an example of a signaling procedure between a terminal 23-00 and a base station 23-05 in a wireless communication system according to an embodiment of the disclosure. It is assumed that the terminal and base station in FIG. 23 can operate according to the above-described proposed method and/or embodiment (e.g., method A-1/A-2-1/A-2-2/A-2-3/ method B-1B-2-1B-2-2B-2-3B-3-1B-3-2B-3-3, etc.).
  • the base station may be a generic term for an object that transmits/receives data to and from a terminal.
  • the base station may be a concept including one or more TRPs (or cell, transmission point, panel, node, TP, beam and/or transmission direction).
  • the base station may be a concept including TRP-1(TRP#1) and TRP-2(TRP#2) described in FIG. 20 and FIG. 21 .
  • the TRP-1(TRP#1) may correspond to a first node
  • the TRP-2(TRP#2) may correspond to a second node.
  • the first and second nodes may be concepts included in the base station, and may be controlled by the base station.
  • the terminal may receive configuration information related to physical uplink control channel (PUCCH) power control (S2310). That is, the base station may transmit configuration information related to the PUCCH power control to the terminal.
  • the configuration information may be transmitted through radio resource control (RRC) signaling.
  • RRC radio resource control
  • the configuration information may correspond to at least one of the above-described PUCCH-SpatialRelationInfo, PUCCH-SpatialRelationInfo-r16, PUCCH-SpatialRelationInfo-r17, spatialRelationInfoToAddModList, spatialRelationInfoToAddModListExt, and spatialRelationInfoToAddModList2.
  • the configuration information may include first information associated with the first node and second information associated with the second node.
  • each of the first information and the second information may include an identifier (e.g., pucch-SpatialRelationInfoId) of each information and a closed loop index (closedloopindex).
  • the first closed-loop index included in the first information and the second closed-loop index included in the second information may be configured to different values.
  • the terminal may identify the first information for PUCCH power control associated with the first node and the second information for PUCCH power control associated with the second node on a basis of the configuration information (S2320).
  • the first information for PUCCH power control associated with the first node may include pucch-SpatialRelationInfoId1 and corresponding pucch-PathlossReferenceRS-Id1, p0-PUCCH-Id1, and ClosedLoopIndex1.
  • the second information for PUCCH power control associated with the second node may include pucch-SpatialRelationInfoId2 and corresponding pucch-PathlossReferenceRS-Id2, p0-PUCCH-Id2 and ClosedLoopIndex2.
  • the terminal may identify that two or more beamforming directions are configured based on the first information and the second information.
  • the terminal may receive downlink control information (DCI) (S2330). That is, the base station may transmit the DCI to the terminal.
  • DCI downlink control information
  • the DCI may include a first bit field corresponding to the first information and a second bit field corresponding to the second information, which are associated with a transmit power control (TPC) command.
  • TPC transmit power control
  • the terminal may determine the transmission power of the PUCCH based on the first information, the second information, and the DCI (S2340).
  • the transmission power of the PUCCH associated with the first node may be determined based on the first information and the DCI
  • the transmission power of the PUCCH associated with the second node may be determined based on the second information and the DCI.
  • the terminal may transmit the PUCCH based on the determined transmission power (S2350). That is, the base station may receive the PUCCH to which the determined transmission power is applied from the terminal.
  • the terminal may transmit the PUCCH in a first resource through the first node using the transmission power determined based on the first information and the DCI.
  • the terminal may transmit the PUCCH in a second resource through the second node using the transmission power determined based on the second information and the DCI.
  • the first resource and the second resource may be located in different slots or in non-overlapping time intervals in one slot.
  • the terminal may receive information on the number of repetitive transmissions of the PUCCH.
  • the terminal may repeatedly transmit the PUCCH in non-overlapping time resources by the number of repetitive transmissions.
  • the transmission power determined based on the first information and the DCI and ii) the transmission power determined based on the second information and the DCI may be applied to the PUCCH resources that are repeatedly transmitted according to a cyclic mapping (cyclicmapping) scheme or a sequential mapping (sequenticalMapping) scheme.
  • the transmission power determined based on the first information and the DCI may be applied to the odd-numbered PUCCH transmission, and the transmission power determined based on the second information and the DCI may be applied to the even-numbered PUCCH transmission.
  • the transmission power determined based on the first information and the DCI may be applied to (the number of repetitive transmissions/2) PUCCHs transmitted first in the time axis, and the transmission power determined based on the second information and the DCI may be applied to the remaining PUCCHs.
  • the terminal may receive activation information for activating the configuration information for the PUCCH resource through medium access control-control element (MAC-CE) signaling. That is, the base station may transmit the activation information to the terminal. Based on the activation information, the identifier (e.g., PUCCH resource ID) of the PUCCH resource and a plurality of configuration information identifiers (e.g., Spatial Relation Info ID 1 and Spatial Relation Info ID 2) corresponding to the PUCCH resource may be indicated.
  • MAC-CE medium access control-control element
  • FIG. 24 is a view illustrating a structure of a terminal in a wireless communication system according to an embodiment of the disclosure.
  • the terminal may include a transceiver 24-00, a memory 24-05, and a processor 24-10.
  • the transceiver 24-00 and processor 24-10 of the terminal may operate according to the above-described communication method of the terminal.
  • the components of the terminal are not limited to the above-described example.
  • the terminal may include more or fewer components than the above-described components.
  • the transceiver 24-00, the memory 24-05, and the processor 24-10 may be implemented in the form of a single chip.
  • the transceiver 24-00 may transmit and receive signals to and from the base station.
  • the signal may include control information and data.
  • the transceiver 24-00 may include an RF transmitter that up-converts and amplifies a frequency of a transmitted signal, an RF receiver that amplifies a received signal with low noise and down-converts a frequency, and the like.
  • this is only an embodiment of the transceiver 24-00, and components of the transceiver 24-00 are not limited to the RF transmitter and the RF receiver.
  • the transceiver 24-00 may receive a signal through a wireless channel, output a signal to the processor 24-10, and transmit a signal output from the processor 24-10 through the wireless channel.
  • the memory 24-05 may store programs and data necessary for the operation of the terminal. In addition, the memory 24-05 may store control information or data included in signals transmitted and received by the terminal.
  • the memory 24-05 may be composed of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media. Also, there may be a plurality of memories 24-05.
  • the processor 24-10 may control a series of processes so that the terminal can operate according to the above-described embodiment.
  • the processor 24-10 may control the components of the terminal to receive a DCI composed of two layers and simultaneously receive a plurality of PDSCHs.
  • There may be a plurality of processors 24-10, and the processor 24-10 may perform a component control operation of the terminal by executing a program stored in the memory 24-05.
  • FIG. 25 is a view illustrating a structure of a base station in a wireless communication system according to an embodiment of the disclosure.
  • the base station may include a transceiver 25-00, a memory 25-05, and a processor 25-10.
  • the transceiver 25-00 and processor 25-10 of the base station may operate according to the above-described communication method of the base station.
  • the components of the base station are not limited to the above-described example.
  • the base station may include more or fewer components than the above-described components.
  • the transceiver 25-00, the memory 25-05, and the processor 25-10 may be implemented in the form of a single chip.
  • the transceiver 25-00 may transmit and receive signals to and from the terminal.
  • the signal may include control information and data.
  • the transceiver 25-00 may include an RF transmitter that up-converts and amplifies a frequency of a transmitted signal, an RF receiver that amplifies a received signal with low noise and down-converts a frequency, and the like.
  • this is only an embodiment of the transceiver 25-00, and components of the transceiver 25-00 are not limited to the RF transmitter and the RF receiver.
  • the transceiver 25-00 may receive a signal through a wireless channel, output a signal to the processor 25-10, and transmit a signal output from the processor 25-10 through the wireless channel.
  • the memory 25-05 may store programs and data required for operation of the base station. In addition, the memory 25-05 may store control information or data included in signals transmitted and received by the base station.
  • the memory 25-05 may be formed of a storage medium such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media. Also, there may be a plurality of memories 25-05.
  • the processor 25-10 may control a series of processes so that the base station can operate according to the above-described embodiment.
  • the processor 25-10 may control each component of the base station to constitute and transmit DCIs of two layers including allocation information for a plurality of PDSCHs.
  • There may be a plurality of processors 25-10, and the processors 25-10 may perform component control operations of the base station by executing a program stored in the memory 25-05.
  • a computer-readable storage medium for storing one or more programs (software modules) may be provided.
  • the one or more programs stored in the computer-readable storage medium may be configured for execution by one or more processors within the electronic device.
  • the at least one program may include instructions that cause the electronic device to perform the methods according to various embodiments of the disclosure as defined by the appended claims and/or disclosed herein.
  • the programs may be stored in non-volatile memories including a random access memory and a flash memory, a read only memory (ROM), an electrically erasable programmable read only memory (EEPROM), a magnetic disc storage device, a compact disc-ROM (CD-ROM), digital versatile discs (DVDs), or other type optical storage devices, or a magnetic cassette.
  • ROM read only memory
  • EEPROM electrically erasable programmable read only memory
  • CD-ROM compact disc-ROM
  • DVDs digital versatile discs
  • any combination of some or all of them may form a memory in which the program is stored.
  • a plurality of such memories may be included in the electronic device.
  • the programs may be stored in an attachable storage device which may access the electronic device through communication networks such as the Internet, Intranet, Local Area Network (LAN), Wide LAN (WLAN), and Storage Area Network (SAN) or a combination thereof.
  • a storage device may access the electronic device via an external port.
  • a separate storage device on the communication network may access a portable electronic device.
  • an element included in the disclosure is expressed in the singular or the plural according to presented detailed embodiments.
  • the singular form or plural form is selected appropriately to the presented situation for the convenience of description, and the disclosure is not limited by elements expressed in the singular or the plural. Therefore, either an element expressed in the plural may also include a single element or an element expressed in the singular may also include multiple elements.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)
EP21883358.0A 2020-10-22 2021-10-22 Procédé et dispositif de transmission d'informations de commande pour une communication coopérative de réseau d'un système de communication sans fil Pending EP4216644A4 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR20200137834 2020-10-22
PCT/KR2021/014965 WO2022086291A1 (fr) 2020-10-22 2021-10-22 Procédé et dispositif de transmission d'informations de commande pour une communication coopérative de réseau d'un système de communication sans fil

Publications (2)

Publication Number Publication Date
EP4216644A1 true EP4216644A1 (fr) 2023-07-26
EP4216644A4 EP4216644A4 (fr) 2024-03-27

Family

ID=81290002

Family Applications (1)

Application Number Title Priority Date Filing Date
EP21883358.0A Pending EP4216644A4 (fr) 2020-10-22 2021-10-22 Procédé et dispositif de transmission d'informations de commande pour une communication coopérative de réseau d'un système de communication sans fil

Country Status (5)

Country Link
US (1) US20230224824A1 (fr)
EP (1) EP4216644A4 (fr)
KR (1) KR20220053510A (fr)
CN (1) CN116530044A (fr)
WO (1) WO2022086291A1 (fr)

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10631191B2 (en) * 2015-03-24 2020-04-21 Ofinno, Llc Uplink transmission power control of a wireless device in a wireless network
US10952231B2 (en) * 2018-05-10 2021-03-16 Asustek Computer Inc. Method and apparatus for beam indication for uplink transmission in a wireless communication system
WO2020030974A2 (fr) * 2018-08-09 2020-02-13 Lenovo (Singapore) Pte.Ltd. Attribution de puissance de transmission en liaison montante

Also Published As

Publication number Publication date
CN116530044A (zh) 2023-08-01
KR20220053510A (ko) 2022-04-29
US20230224824A1 (en) 2023-07-13
WO2022086291A1 (fr) 2022-04-28
EP4216644A4 (fr) 2024-03-27

Similar Documents

Publication Publication Date Title
US11804929B2 (en) Apparatus and method for transmission of uplink control information in network cooperative communication
EP4016910A1 (fr) Procédé et appareil de répétition d'une transmission en liaison montante pour communication coopérative en réseau
EP4093130A1 (fr) Procédé et dispositif de transmission répétitive d'informations de commande de liaison montante pour une communication collaborative de réseau
EP4050811A1 (fr) Procédé et appareil pour la configuration d'un faisceau par défaut pour la communication coopérative en réseau
US20220386156A1 (en) Method and device for measuring interference signal in wireless communication system
US20210250944A1 (en) Method and apparatus for transmitting control information for network cooperative communication
US20220124740A1 (en) Method and apparatus for reporting channel state information for network cooperative communication
US20220209904A1 (en) Method and apparatus for determining processing time of ue in wireless communication system
US20220240160A1 (en) Method and apparatus of explicit linkage between repetitive transmission and reception for downlink control information in wireless communication system
US20220312337A1 (en) Method and device for controlling uplink transmission power for network coordination communication system
US20230318761A1 (en) Method and device for transmitting/receiving control information in wireless cooperative communication system
US20230016937A1 (en) Method and apparatus for data transmission and reception in network cooperative communication
EP4080805A1 (fr) Procédé et appareil de transmission ou de réception de signal de référence dans un système de communication sans fil
KR20230120712A (ko) 무선통신시스템에서 harq-ack 전송 방법 및 장치
CN116349173A (zh) 无线通信系统中重复发送/接收下行链路控制信息的方法和设备
EP4216644A1 (fr) Procédé et dispositif de transmission d'informations de commande pour une communication coopérative de réseau d'un système de communication sans fil
CN113519194A (zh) 网络协作通信中用于发送上行链路控制信息的装置和方法
US20220408468A1 (en) Method and apparatus for transmitting data in network cooperative communications
US20220239418A1 (en) Method and apparatus for transmitting/receiving harq-ack feedback for network cooperative communication
KR20210064008A (ko) 네트워크 협력통신을 위한 디폴트 빔 설정 방법 및 장치
CN116724511A (zh) 用于网络协作通信的harq-ack反馈发送或接收的方法和设备
KR20230106084A (ko) 무선 통신 시스템에서 복수 개의 송수신 빔 활성화 및 지시 방법 방법 및 장치
KR20220144706A (ko) 네트워크 협력 통신에서 하향링크 제어정보 반복 전송 방법 및 장치
KR20230121377A (ko) 무선 통신 시스템에서 상향링크 전송 방법 및 장치
CN116803174A (zh) 在无线通信系统中对下行链路控制信息的重复发射和接收进行配置的方法和装置

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20230420

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
A4 Supplementary search report drawn up and despatched

Effective date: 20240223

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 52/40 20090101ALI20240219BHEP

Ipc: H04W 52/58 20090101ALI20240219BHEP

Ipc: H04W 52/32 20090101ALI20240219BHEP

Ipc: H04W 52/14 20090101ALI20240219BHEP

Ipc: H04W 52/08 20090101ALI20240219BHEP

Ipc: H04L 1/1607 20230101ALI20240219BHEP

Ipc: H04L 1/08 20060101ALI20240219BHEP

Ipc: H04B 7/024 20170101ALI20240219BHEP

Ipc: H04B 7/06 20060101ALI20240219BHEP

Ipc: H04L 1/18 20230101ALI20240219BHEP

Ipc: H04L 5/00 20060101ALI20240219BHEP

Ipc: H04W 72/12 20230101AFI20240219BHEP