WO2021054726A1 - Procédé et appareil de répétition d'une transmission en liaison montante pour communication coopérative en réseau - Google Patents

Procédé et appareil de répétition d'une transmission en liaison montante pour communication coopérative en réseau Download PDF

Info

Publication number
WO2021054726A1
WO2021054726A1 PCT/KR2020/012516 KR2020012516W WO2021054726A1 WO 2021054726 A1 WO2021054726 A1 WO 2021054726A1 KR 2020012516 W KR2020012516 W KR 2020012516W WO 2021054726 A1 WO2021054726 A1 WO 2021054726A1
Authority
WO
WIPO (PCT)
Prior art keywords
pucch
information
transmission
resource
terminal
Prior art date
Application number
PCT/KR2020/012516
Other languages
English (en)
Korean (ko)
Inventor
장영록
노훈동
박진현
지형주
Original Assignee
삼성전자 주식회사
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 삼성전자 주식회사 filed Critical 삼성전자 주식회사
Priority to EP20864484.9A priority Critical patent/EP4016910A4/fr
Priority to US17/761,584 priority patent/US20220353698A1/en
Publication of WO2021054726A1 publication Critical patent/WO2021054726A1/fr

Links

Images

Classifications

    • 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/0032—Distributed allocation, i.e. involving a plurality of allocating devices, each making partial allocation
    • H04L5/0035—Resource allocation in a cooperative multipoint environment
    • 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/1867—Arrangements specially adapted for the transmitter end
    • H04L1/189—Transmission or retransmission of more than one copy of a message
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/24—Cell structures
    • H04W16/28—Cell structures using beam steering
    • 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
    • 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
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/046—Wireless resource allocation based on the type of the allocated resource the resource being in the space domain, e.g. beams
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/232—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • 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/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1854—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • 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/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1896—ARQ related signaling
    • 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
    • H04L2001/0092—Error control systems characterised by the topology of the transmission link
    • H04L2001/0093—Point-to-multipoint
    • 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/0048—Allocation of pilot signals, i.e. of signals known to the receiver

Definitions

  • the present disclosure relates to a wireless communication system, and more specifically, to a method and apparatus for a terminal to perform repetitive transmission through uplink for multiple transmission points or panels or beams for cooperative communication between multiple transmission points or panels or beams. For.
  • a 5G communication system or a pre-5G communication system is called a Beyond 4G Network communication system or an LTE system and a Post LTE system.
  • the 5G communication system is being considered for implementation in the ultra-high frequency (mmWave) band (eg, such as the 60 Giga (60 GHz) band).
  • mmWave ultra-high frequency
  • 5G communication systems include beamforming, massive MIMO, and Full Dimensional MIMO (FD-MIMO).
  • ACM advanced coding modulation
  • FQAM Hybrid FSK and QAM Modulation
  • SWSC Soliding Window Superposition Coding
  • FBMC Filter Bank Multi Carrier
  • NOMA non orthogonal multiple access
  • SCMA sparse code multiple access
  • IoT Internet of Things
  • M2M Machine Type Communication
  • MTC Machine Type Communication
  • a 5G communication system to an IoT network.
  • technologies such as sensor network, machine to machine (M2M), and machine type communication (MTC) are implemented by techniques such as beamforming, MIMO, and array antenna.
  • M2M machine to machine
  • MTC machine type communication
  • cloud RAN cloud radio access network
  • the present disclosure provides a method and apparatus for a terminal to perform uplink repetitive transmission for a plurality of transmission points or panels or beams for network coordination in a wireless communication system.
  • the present invention for solving the above problem is a method of transmitting uplink control information of a terminal in a communication system, the method comprising: receiving, from a base station, repetition configuration information of a physical uplink control channel (PUCCH); And repeatedly transmitting the uplink control information on the PUCCH according to the PUCCH repetition configuration information, wherein the PUCCH repetition configuration information includes a plurality of spatial relation information.
  • PUCCH physical uplink control channel
  • the PUCCH repetition setting information may include an identifier of a reference signal related to a path loss corresponding to each spatial relationship information
  • the plurality of spatial relationship information includes a spatial relationship information identifier and the spatial relationship information
  • a method of receiving uplink control information of a base station of a communication system comprising: transmitting physical uplink control channel (PUCCH) repetition configuration information to a terminal; And repeatedly receiving the uplink control information on the PUCCH according to the PUCCH repetition configuration information, wherein the PUCCH repetition configuration information includes a plurality of spatial relation information.
  • PUCCH physical uplink control channel
  • a terminal for transmitting uplink control information of a communication system comprising: a transceiver; And a control unit configured to receive physical uplink control channel (PUCCH) repetition configuration information from the base station, and control to repeatedly transmit the uplink control information on the PUCCH according to the PUCCH repetition configuration information, wherein the PUCCH repetition configuration information It is characterized by including a plurality of spatial relation information (spatial relation information).
  • PUCCH physical uplink control channel
  • a terminal for transmitting uplink control information of a communication system comprising: a transceiver; And a control unit configured to receive physical uplink control channel (PUCCH) repetition configuration information from the base station, and control to repeatedly transmit the uplink control information on the PUCCH according to the PUCCH repetition configuration information, wherein the PUCCH repetition configuration information It is characterized by including a plurality of spatial relation information (spatial relation information).
  • PUCCH physical uplink control channel
  • the terminal may transmit control information and data with high reliability by performing repeated uplink transmission to each transmission point, panel, or beam.
  • FIG. 1 is a diagram illustrating a basic structure of a time-frequency domain of a mobile communication system according to an embodiment of the present disclosure.
  • FIG. 2 is a diagram illustrating a frame, subframe, and slot structure of a mobile communication system according to an embodiment of the present disclosure.
  • BWP bandwidth part
  • FIG. 4 is a diagram illustrating an example of setting a control region of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure.
  • FIG. 5 is a diagram illustrating a structure of a downlink control channel of a mobile communication system according to an embodiment of the present disclosure.
  • FIG. 6 is a diagram illustrating 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 present disclosure.
  • PDSCH physical downlink shared channel
  • FIG. 7 is a diagram illustrating an example of time axis resource allocation of a PDSCH in a wireless communication system according to an embodiment of the present disclosure.
  • FIG. 8 is a diagram illustrating an example of time axis resource allocation according to subcarrier intervals of a data channel and a control channel in a wireless communication system according to an embodiment of the present disclosure.
  • FIG. 9 is a diagram illustrating an example in which multiple PUCCH resources for HARQ-ACK transmission for a PDSCH overlap when multi-slot repetition is not configured according to an embodiment of the present disclosure.
  • FIG. 10 is a diagram illustrating an example of overlapping PUCCH resources when multi-slot repetition is configured according to an embodiment of the present disclosure.
  • FIG. 11 is a diagram 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 present disclosure.
  • FIG. 12 is a diagram illustrating an example of an antenna port configuration and resource allocation for cooperative communication according to some embodiments in a wireless communication system according to an embodiment of the present disclosure.
  • DCI downlink control information
  • FIG. 14 is a diagram illustrating a method of transmitting HARQ-ACK information when a single PDCCH is used for NC-JT transmission.
  • 15 is a diagram illustrating a method of transmitting joint HARQ-ACK information when multi-PDCCH is used for NC-JT transmission.
  • 16 is a diagram illustrating a method of transmitting inter-slot time division multiplexed HARQ-ACK information when multi-PDCCH is used for NC-JT transmission.
  • 17 is a diagram illustrating a method of transmitting intra-slot time division multiplexed HARQ-ACK information when multi-PDCCH is used for NC-JT transmission.
  • 18 is a diagram illustrating an example of a method for a terminal to transmit HARQ-ACK information for NC-JT transmission to a base station.
  • 19 is a diagram illustrating an example of a method for a base station to receive HARQ-ACK information for NC-JT transmission from a terminal.
  • 20 is a diagram illustrating an example of a method for repeatedly transmitting a PUCCH through a plurality of TRPs by a terminal.
  • 21 is a diagram illustrating an example of a method for a base station to receive a PUCCH repeatedly transmitted by a terminal through a plurality of TRPs.
  • 22 is a diagram illustrating an example of a method of activating a plurality of PUCCH-spatialRelationInfo to MAC CE according to some embodiments.
  • 23A is a diagram illustrating an example of a method of repeatedly transmitting PUSCH based on DCI format 0_0 of a terminal according to some embodiments.
  • 23B is a diagram illustrating another example of a method of repeatedly transmitting PUSCH based on DCI format 0_0 according to some embodiments.
  • 24A is a diagram illustrating an example of a method of repeatedly transmitting a codebook-based PUSCH by a terminal according to some embodiments.
  • 24B is a diagram illustrating another example of a method of repeatedly transmitting a codebook-based PUSCH by a terminal according to some embodiments.
  • FIG. 25A is a diagram illustrating an example of a non-codebook-based PUSCH repetitive transmission method of a terminal when one SRS resource set is set.
  • 25B is a diagram illustrating an example of a non-codebook-based PUSCH repetitive transmission method of a terminal when two SRS resource sets are configured.
  • 26 is a diagram illustrating a terminal structure in a wireless communication system according to an embodiment of the present disclosure.
  • FIG. 27 is a diagram illustrating a structure of a base station in a wireless communication system according to an embodiment of the present disclosure.
  • each block of the flowchart diagrams and combinations of the flowchart diagrams may be executed by computer program instructions. Since these computer program instructions can be mounted on the processor of a general purpose computer, special purpose computer or other programmable data processing equipment, the instructions executed by the processor of the computer or other programmable data processing equipment are described in the flowchart block(s). It creates a means to perform functions. These computer program instructions can also be stored in computer-usable or computer-readable memory that can be directed to a computer or other programmable data processing equipment to implement a function in a particular way, so that the computer-usable or computer-readable memory It may also be possible to produce an article of manufacture containing instruction means for performing the functions described in the flowchart block(s).
  • each block may represent a module, segment, or part of code that contains one or more executable instructions for executing the specified logical function(s).
  • the functions mentioned in the blocks may occur out of order. For example, two blocks shown in succession may in fact be executed substantially simultaneously, or the blocks may sometimes be executed in the reverse order depending on the corresponding function.
  • the term' ⁇ unit' used in this embodiment refers to software or hardware components such as field programmable gate array (FPGA) or application specific integrated circuit (ASIC), and' ⁇ unit' performs certain roles. do.
  • The' ⁇ unit' may be configured to be in an addressable storage medium, or may be configured to reproduce one or more processors. Therefore, according to some embodiments,' ⁇ unit' refers to components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, and programs. Includes procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables.
  • components and functions provided in the' ⁇ units' may be combined into a smaller number of elements and' ⁇ units', or may be further separated into additional elements and' ⁇ units'.
  • components and' ⁇ units' may be implemented to play one or more CPUs in a device or a security multimedia card.
  • the' ⁇ unit' may include one or more processors.
  • the base station is a subject that performs resource allocation of the terminal, and may be at least one of a gNode B, an eNode B, a 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.
  • the present disclosure describes a technique for a terminal to receive broadcast information from a base station in a wireless communication system.
  • the present disclosure relates to 5G (5 th generation) communication system to support higher data rates than after 4G (4 th generation) system, a communication method and a system for fusing and IoT (Internet of Things, things, Internet) technology.
  • This disclosure is based on 5G communication technology and IoT-related technology, and intelligent services (for example, smart home, smart building, smart city, smart car or connected car, healthcare, digital education, retail, security and safety related services, etc. ) Can be applied.
  • a term referring to broadcast information a term referring to control information, a term related to communication coverage, a term referring to a state change (e.g., event), and network entities
  • a term referring to, a term referring to messages, a term referring to a component of a device, and the like are exemplified for convenience of description. Accordingly, the present invention is not limited to the terms described below, and other terms having equivalent technical meanings may be used.
  • LTE 3rd generation partnership project long term evolution
  • the wireless communication system deviated from the initial voice-oriented service, for example, 3GPP HSPA (High Speed Packet Access), LTE (Long Term Evolution or E-UTRA (Evolved Universal Terrestrial Radio Access)), LTE-Advanced. (LTE-A), LTE-Pro, 3GPP2's High Rate Packet Data (HRPD), UMB (Ultra Mobile Broadband), and IEEE's 802.16e. It is evolving into a communication system.
  • 3GPP HSPA High Speed Packet Access
  • LTE-A LTE-Advanced.
  • LTE-Pro LTE-Pro
  • HRPD High Rate Packet Data
  • UMB UserMB
  • an LTE system employs an OFDM (Orthogonal Frequency Division Multiplexing, which can be mixed with CP-OFDM (Cyclic Prefix-OFDM)) in downlink (DL), and uplink (Uplink, UL) employs a single carrier frequency division multiple access (SC-FDMA, which can be mixed with discrete Fourier transform spread OFDM (DFT-s-OFDM)) scheme.
  • OFDM Orthogonal Frequency Division Multiplexing
  • SC-FDMA single carrier frequency division multiple access
  • DFT-s-OFDM discrete Fourier transform spread OFDM
  • Uplink refers to a radio link through which a terminal (UE (User Equipment) or MS (Mobile Station)) transmits data or control signals to a base station (eNode B or base station (BS)), and downlink refers to a base station It means a wireless link that transmits data or control signals.
  • UE User Equipment
  • MS Mobile Station
  • BS base station
  • each user's data or control information is distinguished by assigning and operating time-frequency resources to carry data or control information for each user so that they do not overlap with each other, that is, orthogonality is established. do.
  • Enhanced Mobile BroadBand eMBB
  • massive Machine Type Communication mMTC
  • Ultra Reliability Low Latency Communciation URLLC
  • eMBB aims to provide a data transmission speed that is more improved than the data transmission speed supported by the existing LTE, LTE-A, or LTE-Pro.
  • eMBB in a 5G communication system, eMBB must be able to provide a maximum transmission rate of 20 Gbps in downlink and 10 Gbps in uplink from the viewpoint of one base station. At the same time, an increased user perceived data rate must be provided.
  • MIMO multi-input multi-output
  • the data transmission speed required by the 5G communication system can be satisfied.
  • mMTC is being considered to support application services such as Internet of Things (IoT) in 5G communication systems.
  • IoT Internet of Things
  • mMTC may require large-scale terminal access support within a cell, improved terminal coverage, improved battery time, and reduced terminal cost.
  • the IoT is attached to various sensors and various devices to provide communication functions, so it must be able to support a large number of terminals (for example, 1,000,000 terminals/km 2) within a cell.
  • the terminal supporting mMTC is highly likely to be located in a shaded area not covered by the cell, such as the basement of a building due to the nature of the service, it may require wider coverage compared to other services provided by the 5G communication system.
  • a terminal supporting mMTC must be configured as a low-cost terminal, and since it is difficult to frequently exchange the battery of the terminal, a very long battery life time may be required.
  • a service supporting URLLC must satisfy an air interface latency of less than 0.5 milliseconds, and at the same time have a requirement of a packet error rate of 10 -5 or less. Therefore, for a service supporting URLLC, a 5G system must provide a smaller Transmit Time Interval (TTI) than other services, and at the same time, a design requirement to allocate a wide resource in a frequency band is required.
  • TTI Transmit Time Interval
  • Services considered in the 5G communication system described above should be provided by fusion with each other based on one framework. That is, for efficient resource management and control, it is preferable that each service is integrated into one system, controlled, and transmitted rather than independently operated.
  • an embodiment of the present invention will be described below using an LTE, LTE-A, LTE Pro, or NR system as an example, but the embodiment of the present invention may be applied to other communication systems having a similar technical background or channel type. In addition, the embodiments of the present invention may be applied to other communication systems through some modifications without significantly departing from the scope of the present invention, as determined by a person having skilled technical knowledge.
  • FIG. 1 is a diagram illustrating a basic structure of a time-frequency domain of a mobile communication system according to an embodiment of the present disclosure.
  • the horizontal axis represents the time domain and the vertical axis represents the frequency domain.
  • the basic unit of a resource in the time and frequency domain is a resource element (RE, 101), defined as 1 Orthogonal Frequency Division Multiplexing (OFDM) symbol 102 on the time axis and 1 subcarrier 103 on the frequency axis. Can be.
  • OFDM Orthogonal Frequency Division Multiplexing
  • consecutive REs may constitute one resource block (RB, 104).
  • a plurality of OFDM symbols may constitute one subframe (110).
  • FIG. 2 is a diagram illustrating a frame, subframe, and slot structure of a next-generation mobile communication system according to an embodiment of the present disclosure.
  • one component carrier (CC) or serving cell may be configured with a maximum of 250 or more RBs. Therefore, when the terminal always receives the entire serving cell bandwidth like LTE, the power consumption of the terminal can be extreme, and to solve this, the base station sets one or more bandwidth parts (BWP) to the terminal. Thus, it is possible to support the UE to change the reception area within the cell.
  • the base station may set an initial bandwidth (initial BWP), which is a bandwidth of CORESET #0 (or common search space, CSS), to the terminal through the MIB.
  • the base station may set an initial BWP (first BWP) of the terminal through RRC signaling, and may notify at least one or more BWP configuration information that may be indicated through downlink control information (DCI) in the future. Thereafter, the base station can indicate which band the terminal will use by notifying the BWP ID through DCI. If the terminal does not receive DCI in the currently allocated BWP for more than a certain time, the terminal returns to the default BWP and attempts DCI reception.
  • first BWP initial BWP
  • DCI downlink control information
  • FIG. 3 illustrates an example of a partial configuration of a bandwidth in a wireless communication system according to an embodiment of the present disclosure.
  • FIG. 3 shows an example in which the terminal bandwidth 300 is set to two bandwidth portions, that is, a bandwidth portion #1 (305) and a bandwidth portion #2 (310).
  • the base station may set one or a plurality of bandwidth portions to the terminal, and may set information as shown in Table 2 below for each bandwidth portion.
  • various parameters related to the bandwidth portion may be set to the terminal.
  • the above-described information can be delivered from the base station to the terminal through higher layer signaling, for example, RRC signaling.
  • At least one bandwidth portion among the set one or a plurality of bandwidth portions may be activated. Whether or not to activate the configured bandwidth portion may be transmitted from the base station to the terminal in a semi-static manner through RRC signaling, or may be dynamically transmitted through a MAC control element (CE) or DCI.
  • CE MAC control element
  • a terminal before radio resource control (RRC) connection may receive an initial bandwidth part (Initial BWP) for initial access from a base station through a master information block (MIB). More specifically, in order to receive system information (which may correspond to Remaining System Information (RMSI) or System Information Block 1 (SIB1)) required for initial access through the MIB in the initial access step, the PDCCH may be transmitted. It is possible to receive setting information about the existing control area (Control Resource Set, CORESET) and search space.
  • the control region and the search space set as the MIB may be regarded as identifiers (Identity, ID) 0, respectively.
  • the base station may notify the terminal of configuration information such as frequency allocation information, time allocation information, and numerology for control region #0 through the MIB.
  • the base station may notify the terminal of the setting information for the monitoring period and occasion for the control area #0, that is, the setting information for the search space #0 through the MIB.
  • the UE may consider the frequency domain set to control region #0 acquired from the MIB as an initial bandwidth part for initial access.
  • the identifier (ID) of the initial bandwidth part may be regarded as 0.
  • the UE can receive the PDSCH through which the SIB is transmitted, and the initial bandwidth part is not only for receiving the SIB, but also other system information (OSI), paging, and random access. Access) can also be used.
  • OSI system information
  • the setting of the bandwidth part supported by the above-described next-generation mobile communication system can be used for various purposes.
  • the bandwidth supported by the terminal when the bandwidth supported by the terminal is smaller than the system bandwidth, the bandwidth supported by the terminal may be supported through the setting of the bandwidth portion.
  • the bandwidth portion For example, in Table 2, the frequency position of the bandwidth portion (configuration information 2) is set to the terminal, so that the terminal can transmit and receive data at a specific frequency position within the system bandwidth.
  • the base station may set a plurality of bandwidth portions to the terminal. 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 an arbitrary terminal, two bandwidth portions may be set to use subcarrier spacings of 15 kHz and 30 kHz, respectively. Different bandwidth portions may be FDM (Frequency Division Multiplexing), and when data is to be transmitted/received at a specific subcarrier interval, a bandwidth portion set at the corresponding subcarrier interval may be activated.
  • FDM Frequency Division Multiplexing
  • the base station may set a bandwidth portion having a different size of bandwidth to the terminal. For example, if the terminal supports a very large bandwidth, such as 100 MHz, and always transmits/receives data through the corresponding bandwidth, it may cause very large power consumption. In particular, it is very inefficient in terms of power consumption for the UE to monitor an unnecessary downlink control channel for a large bandwidth of 100 MHz in a situation where there is no traffic. Therefore, for the purpose of reducing power consumption of the terminal, the base station may set a bandwidth portion of a relatively small bandwidth to the terminal, for example, a bandwidth portion of 20 MHz. In a situation where there is no traffic, the UE can perform a monitoring operation in the 20 MHz bandwidth portion, and when data is generated, it can transmit and receive data using the 100 MHz bandwidth portion according to the instruction of the base station.
  • Synchronization Signal (SS)/PBCH block of a next-generation mobile communication system will be described.
  • the SS/PBCH block may mean a physical layer channel block composed of a Primary SS (PSS), a Secondary SS (SSS), and a PBCH. More specifically, the SS/PBCH block may be defined as follows.
  • -PSS As a signal that is a reference for downlink time/frequency synchronization, some information of the cell ID may be provided.
  • -SSS It is a reference for downlink time/frequency synchronization, and the remaining cell ID information not provided by the PSS can be provided. Additionally, it may serve as a reference signal for demodulation of the PBCH.
  • the essential system information may include search space-related control information indicating radio resource mapping information of the control channel, scheduling control information for a separate data channel transmitting system information, and the like.
  • the SS/PBCH block may be formed of a combination of PSS, SSS and PBCH.
  • One or more SS/PBCH blocks may be transmitted within 5 ms time, and each transmitted SS/PBCH block may be distinguished by an index.
  • the UE may detect the PSS and SSS in the initial access phase and may decode the PBCH.
  • the UE may obtain the MIB from the PBCH, and may receive the control region #0 set through the MIB.
  • the UE may perform monitoring on the control region #0 assuming that the selected SS/PBCH block and the DMRS (Demodulation RS (Reference Signal)) transmitted in the control region #0 are Quasi Co Location (QCL).
  • the system information can be received by the downlink control information transmitted in area # 0.
  • the terminal can obtain the RACH (Random Access Channel) related configuration information required for initial access from the received system information.
  • RACH Random Access Channel
  • the PRACH Physical RACH
  • the base station receiving the PRACH can obtain information on the SS/PBCH block index selected by the terminal.
  • a block is selected, and the control region #0 corresponding to (or associated with) the SS/PBCH block selected by the UE is monitored.
  • DCI downlink control information
  • Uplink data (or physical uplink shared channel (PUSCH)) or downlink data (or physical downlink data channel (Physical Downlink Shared Channel, PDSCH)) in a next-generation mobile communication system (5G or NR system) Scheduling information for may be delivered from the base station to the terminal through DCI.
  • the UE may monitor a DCI format for fallback and a DCI format for non-fallback with respect to the PUSCH or PDSCH.
  • the fallback DCI format may consist of a fixed field that is 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.
  • a Cyclic Redundancy Check (CRC) may be attached to the DCI message payload, and the CRC may be scrambling with a Radio Network Temporary Identifier (RNTI) corresponding to the identity of the UE.
  • RNTI Radio Network Temporary Identifier
  • Different RNTIs according to the purpose of the DCI message, for example, UE-specific data transmission, a power control command, or a random access response, may be used for scrambling of the CRC attached to the payload of the DCI message. That is, the RNTI is not explicitly transmitted, but may be included in the CRC calculation process and transmitted.
  • the UE can 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.
  • DCI scheduling a PDSCH for a Random Access Response (RAR) message may be scrambled with RA-RNTI.
  • DCI scheduling a PDSCH for a paging message may be scrambled with a P-RNTI.
  • the DCI notifying the SFI Slot Format Indicator
  • DCI notifying TPC Transmit Power Control
  • the DCI scheduling the UE-specific PDSCH or PUSCH may be scrambled with a Cell RNTI (C-RNTI).
  • C-RNTI Cell RNTI
  • DCI format 0_0 may be used as a fallback DCI for scheduling PUSCH, and in this case, CRC may be scrambled with C-RNTI.
  • CRC may be scrambled with C-RNTI.
  • the DCI format 0_0 in which CRC is scrambled with C-RNTI may include information as shown in Table 3 below.
  • DCI format 0_1 may be used as a non-fallback DCI for scheduling PUSCH, and in this case, CRC may be scrambled with C-RNTI.
  • CRC may be scrambled with C-RNTI.
  • the DCI format 0_1 in which CRC is scrambled with C-RNTI may include information as shown in Table 4 below.
  • -CBG transmission information (code block group transmission information)-0, 2, 4, 6, or 8 bits
  • phase tracking reference signal-demodulation reference signal relationship (phase tracking reference signal-demodulation reference signal relationship)-0 or 2 bits.
  • DCI format 1_0 may be used as a fallback DCI for scheduling a PDSCH, and in this case, the CRC may be scrambled with C-RNTI.
  • the DCI format 1_0 in which CRC is scrambled with C-RNTI may include information as shown in Table 5 below.
  • 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 C-RNTI.
  • the DCI format 1_1 in which CRC is scrambled with C-RNTI may include information as shown in Table 6 below.
  • -ZP CSI-RS trigger zero power channel status information reference signal trigger
  • TCI Transmission configuration indication
  • FIG. 4 is a diagram for explaining setting of a control region of a downlink control channel in a next generation mobile communication system according to an embodiment of the present disclosure. That is, FIG. 4 is a diagram illustrating an embodiment of a control region (Control Resource Set, CORESET) in which a downlink control channel is transmitted according to an embodiment of the present disclosure.
  • CORESET Control Resource Set
  • control region #1 401, control region #2 402 within one slot 420 as a frequency axis and a UE bandwidth part 410 as a frequency axis.
  • the control regions 401 and 402 may be set in a specific frequency resource 403 within the entire terminal bandwidth part 410 on the frequency axis.
  • the control regions 401 and 402 may be set as one or a plurality of OFDM symbols on the time axis, which may be defined as a control region length (Control Resource Set Duration, 404).
  • control region #1 401 may be set to a control region length of 2 symbols
  • control region #2 402 may be set to control region length of 1 symbol.
  • the base station provides higher layer signaling to the terminal (e.g., system information, MIB (Master Information Block), RRC (signaling, which is higher signaling, higher layer signaling, higher layer signaling). , L3 signaling, etc.).
  • Setting the control region to the terminal means providing information such as the control region identifier (Identity), the frequency position of the control region, and the symbol length of the control region.
  • the setting of the control region may include information as shown in Table 7 below.
  • ControlResourceSet :: SEQUENCE ⁇
  • ControlResourceSetId ControlResourceSetId
  • tci-StatesPDCCH SEQUENCE(SIZE (1..maxNrofTCI-StatesPDCCH)) OF TCI-StateId OPTIONAL,
  • TCI state configuration information is one or more SS (Synchronization Signal)/PBCH (Physical It may include information on a Broadcast Channel) block index or a Channel State Information Reference Signal (CSI-RS) index. It may also include information on what kind of relationship the QCL relationship is.
  • SS Synchronization Signal
  • PBCH Physical It may include information on a Broadcast Channel block index or a Channel State Information Reference Signal (CSI-RS) index. It may also include information on what kind of relationship the QCL relationship is.
  • CSI-RS Channel State Information Reference Signal
  • the setting of the TCI state may include information as shown in Table 8 below.
  • a cell index and/or a BWP index and a QCL type of a reference RS may be set together with an index of a reference RS having a QCL relationship, that is, an SS/PBCH block index or a CSI-RS index.
  • the QCL type indicates a channel characteristic that is assumed to be shared between the reference RS and the control region DMRS, and examples of possible QCL types are as follows.
  • the TCI state can be similarly set not only for the control region DMRS but also for other target RSs such as PDSCH DMRS and CSI-RS.
  • 5 is a diagram illustrating a structure of a downlink control channel of a next-generation mobile communication system according to an embodiment of the present disclosure. 5 shows an example of a basic unit of time and frequency resources constituting a downlink control channel.
  • a basic unit of time and frequency resources constituting a control channel may be defined as a Resource Element Group (REG) 503.
  • the REG 503 may be defined as 1 OFDM symbol 501 on the time axis and 1 Physical Resource Block (PRB) 502 on the frequency axis, that is, 12 subcarriers.
  • the base station may configure a downlink control channel allocation unit by concatenating the REG 503.
  • one CCE 504 may be composed of a plurality of REGs 503.
  • the REG 503 shown in FIG. 5 may be composed of 12 REs, and if 1 CCE 504 is composed of 6 REGs 503, 1 CCE 504 will be composed of 72 REs. I can.
  • the corresponding region may be composed of a plurality of CCEs 504, and a specific downlink control channel is configured with one or more CCEs 504 according to an aggregation level (AL) within the control region. It can be mapped and transmitted.
  • the CCEs 504 in the control area are classified by numbers, and in this case, the numbers of the CCEs 504 may be assigned according to a logical mapping method.
  • the basic unit of the downlink control channel shown in FIG. 5, that is, the REG 503 may include both REs to which DCI is mapped and a region to which the DMRS 505, which is a reference signal for decoding them, is mapped. As shown in FIG. 5, three DMRSs 505 may be transmitted within 1 REG 503.
  • the UE needs to detect a signal without knowing the information on the downlink control channel, and a search space indicating a set of CCEs may be defined for blind decoding.
  • the search space is a set of downlink control channel candidates (Candidates) consisting of CCEs to which the UE should attempt decoding on a given aggregation level. Since there are various aggregation levels that make one bundle with 1, 2, 4, 8, and 16 CCEs, the terminal may have a plurality of search spaces.
  • the search space set may be defined as a set of search spaces at all set aggregation levels.
  • the search space may be classified into a common search space and a UE-specific search space.
  • terminals of a certain group or all terminals may examine a common search space of a PDCCH in order to receive cell-common control information such as dynamic scheduling for system information or a paging message.
  • the UE may receive PDSCH scheduling allocation information for transmission of SIB including cell operator information, etc. by examining the common search space of the PDCCH.
  • the common search space may be defined as a set of predetermined CCEs.
  • the UE may receive scheduling allocation information for UE-specific PDSCH or PUSCH by examining the UE-specific search space of the PDCCH.
  • the terminal-specific search space may be defined terminal-specifically as a function of the identity of the terminal and various system parameters.
  • the parameter for the search space for the PDCCH may be set from the base station to the terminal by higher layer signaling (eg, SIB, MIB, RRC signaling).
  • the base station is the number of PDCCH candidates at each aggregation level L, the monitoring period for the search space, the monitoring time (occasion) of the symbol unit in the slot for the search space, and the search space type (common search space or terminal-specific search Space), the combination of the DCI format and RNTI to be monitored in the search space, the control region index to monitor the search space, etc. can be set to the terminal.
  • the above-described setting may include information shown in Table 9 below.
  • SearchSpaceId 0 identifies the SearchSpace configured via PBCH (MIB) or ServingCellConfigCommon.
  • ControlResourceSetId ControlResourceSetId
  • monitoringSlotPeriodicityAndOffset CHOICE ⁇
  • the base station may set one or a plurality of search space sets to the terminal.
  • the base station may set search space set 1 and search space set 2 to the terminal, and set to monitor DCI format A scrambled with X-RNTI in search space set 1 in a common search space.
  • DCI format B scrambled with Y-RNTI in search space set 2 can be set to be monitored in a UE-specific search space.
  • one or a plurality of search space sets may exist in a common search space or a terminal-specific search space.
  • search space set #1 and search space set #2 may be set as a common search space
  • search space set #3 and search space set #4 may be set as terminal-specific search spaces.
  • a combination of the following DCI format and RNTI may be monitored.
  • DCI format a combination of the following DCI format and RNTI.
  • RNTI a combination of the following DCI format and RNTI.
  • the specified RNTIs can follow the definitions and uses as follows.
  • C-RNTI Cell RNTI
  • TC-RNTI Temporal Cell RNTI
  • CS-RNTI Configured Scheduling RNTI
  • RA-RNTI Random Access RNTI
  • P-RNTI Paging RNTI
  • SI-RNTI System Information RNTI
  • INT-RNTI Used to inform whether or not the PDSCH is pucturing
  • TPC-PUSCH-RNTI Transmit Power Control for PUSCH RNTI
  • TPC-PUCCH-RNTI Transmit Power Control for PUCCH RNTI
  • TPC-SRS-RNTI Transmit Power Control for SRS RNTI
  • the DCI formats described above may be defined as shown in Table 10 below.
  • a plurality of search space sets may be set with different parameters (eg, parameters in Table 8). Accordingly, the set of search space sets monitored by the terminal may vary at each time point. For example, if search space set #1 is set to X-slot period, search space set #2 is set to Y-slot period, and X and Y are different, the terminal searches for search space set #1 in a specific slot. Both space set #2 can be monitored, and one of search space set #1 and search space set #2 can be monitored in a specific slot.
  • FD-RA frequency domain resource allocation
  • FIG. 6 is a diagram illustrating an example of PDSCH frequency axis resource allocation in a wireless communication system according to an embodiment of the present disclosure.
  • resource allocation type 0 600
  • type 1 (605)
  • dynamic switch 610 that can be set through an upper layer in the NR.
  • N RBG some downlink control information (DCI) for allocating a PDSCH to the corresponding terminal is N RBG number. It has a bitmap composed of bits.
  • N RBG means the number of resource block groups (RBGs) determined as shown in Table 11 below according to the BWP size allocated by the BWP indicator and the upper layer parameter rbg-Size, and 1 by bitmap. Data is transmitted to the RBG indicated by.
  • the terminal is configured to use only resource allocation type 1 through higher layer signaling (605), some DCIs that allocate PDSCH to the corresponding terminal It has frequency axis resource allocation information consisting of three bits.
  • the base station may set a starting VRB (620) and a length 625 of a frequency axis resource continuously allocated therefrom.
  • some DCIs that allocate PDSCH to the terminal are payload 615 for setting resource allocation type 0
  • frequency axis resource allocation information consisting of bits of a larger value 635 among payloads 620 and 625 for setting resource allocation type 1.
  • one bit may be added to the first part (MSB) of the frequency axis resource allocation information within the DCI, and if the corresponding bit is 0, it indicates that the resource allocation type 0 is used, and if it is 1, the resource allocation type 1 is used. Can be indicated.
  • TD-RA time domain resource allocation
  • the base station may set a table for time domain resource allocation information for the PDSCH and PUSCH to the UE as higher layer signaling (eg, RRC signaling).
  • the time domain resource allocation information includes PDCCH-to-PDSCH slot timing (corresponds to the time interval in units of slots between the time when the PDCCH is received and the time when the PDSCH scheduled by the received PDCCH is transmitted, expressed as K 0 ), PDCCH-to-PUSCH slot timing (corresponds to the time interval in units of slots between the time when the PDCCH is received and the time when the PUSCH scheduled by the received PDCCH is transmitted , denoted as K 2 ), the PDSCH within the slot, or Information on the location and length of the start symbol in which the PUSCH is scheduled, the PDSCH or the PUSCH mapping type, and the like may be included. For example, information shown in Table 12 or Table 13 below may be notified from the base station to the terminal.
  • PDSCH-TimeDomainResourceAllocationList SEQUENCE (SIZE(1..maxNrofDL-Allocations)) OF PDSCH-TimeDomainResourceAllocation
  • PUSCH-TimeDomainResourceAllocationList SEQUENCE (SIZE(1..maxNrofUL-Allocations)) OF PUSCH-TimeDomainResourceAllocation
  • the base station may notify the terminal of one of the entries in the table for time domain resource allocation information described above to the terminal through L1 signaling (for example, DCI) (for example, to be indicated by the'time domain resource allocation' field in the DCI. Can).
  • L1 signaling for example, DCI
  • the terminal may obtain time domain resource allocation information for the PDSCH or PUSCH based on the DCI received from the base station.
  • FIG. 7 is a diagram illustrating an example of time axis resource allocation of a PDSCH in a wireless communication system according to an embodiment of the present disclosure.
  • a base station includes subcarrier spacing (SCS) of a data channel and a control channel set using an upper layer ( ), the scheduling offset (K 0 ) value, and the time axis of the PDSCH resource in the slot 710 according to the OFDM symbol start position 700 and the length 705 in one slot dynamically indicated through DCI Position can be indicated.
  • SCS subcarrier spacing
  • K 0 scheduling offset
  • FIG. 8 is a diagram illustrating an example of time axis resource allocation according to subcarrier intervals of a data channel and a control channel in a wireless communication system according to an embodiment of the present disclosure.
  • the base station and the terminal when the subcarrier spacing of the data channel and the control channel is the same (800, ), since the slot number for data and control are the same, the base station and the terminal generate a scheduling offset according to a predetermined slot offset K 0. On the other hand, if the subcarrier spacing of the data channel and the control channel is different (805, ), since the slot number for data and control is different, the base station and the terminal have a scheduling offset according to a predetermined slot offset K 0 based on the subcarrier interval of the PDCCH. Occurs.
  • the terminal may perform a procedure of reporting the capability supported by the terminal to the corresponding base station while being connected to the serving base station. In the following description, this is referred to as UE capability report.
  • the base station may deliver a UE capability inquiry message for requesting a capability report to the UE in the connected state.
  • the message may include a UE capability request for each radio access technology (RAT) type of the base station.
  • the request for each RAT type may include information on a combination of supported frequency bands.
  • UE capability for each RAT type may be requested through one RRC message container transmitted by the base station, or the base station may send a UE capability inquiry message including a UE capability request for each RAT type. It can be included multiple times and delivered to the terminal.
  • the terminal transmits uplink control information (UCI) to the base station through the PUCCH.
  • the control information includes HARQ-ACK indicating success or failure of demodulation/decoding for a transport block (TB) received by the UE through the PDSCH, and scheduling request (SR) for requesting resource allocation from the UE to the PUSCH base station for uplink data transmission.
  • CSI channel state information
  • the PUCCH resource can be largely divided into long PUCCH and short PUCCH according to the length of the allocated symbol.
  • a long PUCCH has a length of 4 symbols or more in a slot
  • a short PUCCH has a length of 2 symbols or less in a slot.
  • PUCCH format 1 is a DFT-S-OFDM-based long PUCCH format capable of supporting up to 2 bits of control information, and uses frequency resources as much as 1 RB.
  • the control information may be composed of a combination of HARQ-ACK and SR or each.
  • PUCCH format 1 an OFDM symbol including a DMRS, which is a demodulation reference signal (or a reference signal), and an OFDM symbol including UCI are repeatedly configured.
  • the first start symbol of 8 symbols is sequentially composed of a DMRS symbol, a UCI symbol, a DMRS symbol, a UCI symbol, a DMRS symbol, a UCI symbol, a DMRS symbol, and a 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 1 RB on the frequency axis within one OFDM symbol, and IFFT is performed. Will be sent after.
  • the UCI symbol is generated as follows.
  • the terminal generates d(0) by modulating 1-bit control information in BPSK and 2-bit control information in QPSK, multiplying the generated d(0) by a sequence corresponding to the length of 1 RB on the frequency axis to scramble, and scramble.
  • the sequence is spread using an orthogonal code (or an orthogonal sequence or spreading code, w i(m) ) on the time axis, IFFT is performed, and then transmitted.
  • the UE generates the sequence based on the group hopping or sequence hopping set and set ID set as a higher signal from the base station, and cyclic shifts the generated sequence with an initial CS (cyclic shift) value set as a higher signal to a length of 1 RB. Create a sequence corresponding to.
  • w i(m ) is given the length of the spreading code (N SF) It is determined as shown in Table 14 below.
  • i means the index of the spreading code itself, and m means the index of the elements of the spreading code.
  • 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 set through an upper layer.
  • the control information may consist of a combination of HARQ-ACK, SR, and CSI, or each.
  • the DMRS symbol position is shown in Table 15 below according to whether frequency hopping in the slot and whether additional DMRS symbols are set.
  • 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 table is applied in the same manner to the DMRS symbol position of PUCCH format 4.
  • PUCCH format 4 is a DFT-S-OFDM-based long PUCCH format capable of supporting more than 2 bits of control information, and uses frequency resources as much as 1 RB.
  • the control information may consist of a combination of HARQ-ACK, SR, and CSI, or each.
  • the difference between PUCCH format 4 and PUCCH format 3 is that in case of PUCCH format 4, PUCCH format 4 of several 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. However, 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 set through a higher layer.
  • Short PUCCH can be transmitted in both a downlink centric slot and an uplink centric slot, and generally, the last symbol of the slot or an OFDM symbol at the rear (for example, the last OFDM symbol or It is transmitted in the second OFDM symbol from the last, or the last 2 OFDM symbols). Of course, it is also possible to transmit a short PUCCH at any position in the slot. In addition, the short PUCCH may be transmitted using one OFDM symbol or two OFDM symbols. Short PUCCH can be used to shorten a delay time compared to long PUCCH in a situation where uplink cell coverage is good, and is transmitted in a CP-OFDM scheme.
  • Short PUCCH supports transport formats such as PUCCH format 0 and PUCCH format 2 according to the number of supportable control information bits.
  • 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 composed of a combination of HARQ-ACK and SR or each.
  • PUCCH format 0 does not transmit DMRS, but transmits only sequences mapped to 12 subcarriers along the frequency axis within one OFDM symbol.
  • the terminal generates a sequence based on the group hopping or sequence hopping configuration and set ID set as a higher signal from the base station, and the final CS value obtained by adding different CS values according to whether ACK or NACK to the indicated initial cyclic shift (CS) value.
  • the generated sequence is cyclic shifted, mapped to 12 subcarriers, and transmitted.
  • HARQ-ACK is 2 bits, as in Table 17 below, 0 is added to the initial CS value if (NACK, NACK), if (NACK, ACK), 3 is added to the initial CS value, and if (ACK, ACK) 6 is added to the initial CS value, and if (ACK, NACK), 9 is added to the initial CS value.
  • the CS value 0 for (NACK, NACK), 3 for the CS value for (NACK, ACK), 6 for the CS value for (ACK, ACK), and 9 for the CS value for (ACK, NACK) are defined in the standard.
  • the UE always transmits a 2-bit HARQ-ACK by generating PUCCH format 0 according to the value.
  • PUCCH format 2 is a short PUCCH format supporting control information of more than 2 bits, and the number of RBs used can be set through an upper layer.
  • the control information may consist of a combination of HARQ-ACK, SR, and CSI, or each.
  • PUCCH format 2 the position of the subcarrier in which the DMRS is transmitted within one OFDM symbol is in the subcarrier having the indexes of #1, #4, #7, and #10 when the index of the first subcarrier is #0. It is fixed.
  • the control information is mapped to the remaining subcarriers except for the subcarrier in which the DMRS is located through a modulation process after channel coding.
  • multi-slot repetition may be supported for PUCCH formats 1, 3, and 4, and PUCCH repetition may be set for each PUCCH format.
  • the UE repeatedly transmits PUCCH including UCI as many as the number of slots set through nrofSlots, which is higher layer signaling.
  • PUCCH transmission in each slot is performed using the same number of consecutive symbols, and the number of corresponding consecutive symbols is nrofSymbols in the higher layer signaling PUCCH-format1 or PUCCH-format3 or PUCCH-format4. It can be set through.
  • PUCCH transmission in each slot is performed using the same start symbol, and the corresponding start symbol may be set through startingSymbolIndex in PUCCH-format1 or PUCCH-format3 or PUCCH-format4, which is higher layer signaling.
  • the UE For repeated PUCCH transmission, if the UE is configured to perform frequency hopping in PUCCH transmission in different slots, the UE performs frequency hopping in units of slots. In addition, if the UE is configured to perform frequency hopping in PUCCH transmission in different slots, the UE starts PUCCH transmission from the first PRB index set through startingPRB, which is higher layer signaling, in the even-numbered slot, and is odd. In the second slot, PUCCH transmission starts from the second PRB index set through secondHopPRB, which is higher layer signaling.
  • the index of the slot in which the UE is instructed to transmit the first PUCCH is 0, and during the set total number of repeated PUCCH transmissions, each slot The value of the number of repetitive PUCCH transmissions increases regardless of whether PUCCH transmission is performed in If the UE is configured to perform frequency hopping in PUCCH transmission in different slots, the UE does not expect that frequency hopping in the slot is configured when transmitting PUCCH.
  • the first and second PRB indexes are applied equally in the slot.
  • the base station can configure PUCCH resources for each BWP through an upper layer for a specific terminal.
  • the setting may be as shown in Table 19 below.
  • resourceSetToAddModList SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceSets)) OF PUCCH-ResourceSet OPTIONAL, - Need N
  • resourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceSets)) OF PUCCH-ResourceSetId OPTIONAL, - Need N
  • resourceToAddModList SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-Resource OPTIONAL, - Need N
  • resourceToReleaseList SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-ResourceId OPTIONAL, - Need N
  • schedulingRequestResourceToAddModList SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceConfig
  • schedulingRequestResourceToReleaseList SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceId
  • multi-CSI-PUCCH-ResourceList SEQUENCE (SIZE (1..2)) OF PUCCH-ResourceId OPTIONAL, - Need M
  • spatialRelationInfoToAddModList SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos)) OF PUCCH-SpatialRelationInfo
  • spatialRelationInfoToReleaseList SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos)) OF PUCCH-SpatialRelationInfoId
  • one or a plurality of PUCCH resource sets in the PUCCH resource setting for a specific BWP may be set, and a maximum payload value for UCI transmission may be set in some of the PUCCH resource sets.
  • One or a plurality of PUCCH resources may belong to each PUCCH resource set, 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 set through an upper layer or the like.
  • the index of the corresponding PUCCH resource set may be set in ascending order according to the maximum payload value, and the maximum payload value may not be set in the last PUCCH resource set.
  • the upper layer configuration for the PUCCH resource set may be as shown in Table 20 below.
  • PUCCH-ResourceSet :: SEQUENCE ⁇
  • resourceList SEQUENCE (SIZE (1..maxNrofPUCCH-ResourcesPerSet)) OF PUCCH-ResourceId,
  • the resourceList parameter of the table may include IDs of PUCCH resources belonging to the PUCCH resource set.
  • a PUCCH resource set as shown in Table 21, which is composed of a plurality of cell-specific PUCCH resources in the initial BWP, may be used.
  • PUCCH resources to be used for initial access in this PUCCH resource set may be indicated through SIB1.
  • the maximum payload of each PUCCH resource included in the PUCCH resource set may be 2 bits in the case of PUCCH format 0 or 1, and may be determined by the symbol length, the number of PRBs, and the maximum code rate in the case of the remaining formats.
  • the above-described symbol length and number of PRBs may be set for each PUCCH resource, and the maximum code rate may be set for each PUCCH format.
  • a PUCCH resource for an SR corresponding to schedulingRequestID may be configured through a higher layer as shown in Table 22 below.
  • the PUCCH resource may be a resource belonging to PUCCH format 0 or PUCCH format 1.
  • SchedulingRequestResourceConfig :: SEQUENCE ⁇
  • a transmission period and an offset are set through the periodicityAndOffset parameter of Table 22.
  • 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 a PUCCH may be set in the pucch-CSI-ResourceList parameter as shown in Table 23 below 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.
  • pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource
  • pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource
  • reportSlotOffsetList SEQUENCE (SIZE (1.. maxNrofUL-Allocations)) OF INTEGER(0..32),
  • reportSlotOffsetList SEQUENCE (SIZE (1..maxNrofUL-Allocations)) OF INTEGER(0..32)
  • the PUCCH resource is configured with a transmission period and an offset through reportSlotConfig of Table 23.
  • a resource set of PUCCH resources to be transmitted is first selected according to the payload of UCI including the corresponding HARQ-ACK. That is, a PUCCH resource set having a minimum payload that is not smaller than the UCI payload is selected.
  • the PUCCH resource in the PUCCH resource set may be selected through the PUCCH resource indicator (PRI) in the DCI scheduling the TB corresponding to the corresponding HARQ-ACK, and the PRI is the PUCCH specified in Table 5 or Table 6. May be a resource indicator.
  • 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 24 below.
  • the PUCCH resource may be selected by the following equation.
  • r PUCCH is the index of the selected PUCCH resource in the PUCCH resource set
  • R PUCCH is the number of PUCCH resources belonging to the PUCCH resource set
  • ⁇ PRI is the PRI value
  • N CCE is the total number of CCEs of the CORESET p to which the receiving DCI belongs.
  • n CCE,p indicates the first CCE index for the received DCI.
  • the time point at which the corresponding PUCCH resource is transmitted is after the K1 slot from the TB transmission corresponding to the corresponding HARQ-ACK.
  • the K1 value candidate is set as an upper layer, and more specifically, is set in the dl-DataToUL-ACK parameter in the PUCCH-Config specified in Table 19.
  • the K1 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 above.
  • the unit of the K1 value may be a slot unit or a subslot unit.
  • a subslot is a unit of a length smaller than that of a slot, and one or a plurality of symbols may constitute one subslot.
  • the UE can transmit UCI through one or two PUCCH resources in one slot or subslot, and when UCI is transmitted through two PUCCH resources in one slot/subslot i) Each PUCCH resource does not overlap in units of symbols, ii) At least one PUCCH resource may be a short PUCCH. Meanwhile, the UE may not expect to transmit a plurality of PUCCH resources for HARQ-ACK transmission within one slot.
  • a PUCCH transmission procedure when two or more PUCCH resources overlap.
  • one of the overlapping PUCCH resources may be selected or a new PUCCH resource may be selected according to the above-described condition, that is, the condition that the transmitted PUCCH resources do not overlap in symbol units.
  • all UCI payloads transmitted through overlapping PUCCH resources may be multiplexed and transmitted, or some may be dropped.
  • FIG. 9 A case corresponding to Case 1-1) is illustrated in FIG. 9.
  • FIG. 9 is a diagram illustrating an example in which a plurality of PUCCH resources for HARQ-ACK transmission for a PDSCH overlap when multi-slot repetition is not configured according to an embodiment of the present disclosure.
  • the corresponding PUCCH resources may be considered to overlap with each other. That is, when the uplink slots corresponding to the K1 values 950 and 951 indicated by the plurality of PDCCHs are the same, it can be considered that PUCCH resources corresponding to the corresponding PDCCHs overlap with each other.
  • HARQ-ACK information for the PDSCH 921 through the selected PUCCH resource 931 and HARQ-ACK information for the other PUCCH 930 overlapping with the PUCCH resource 931 are all predefined HARQ-ACK codebooks It is transmitted after being encoded by.
  • a PUCCH resource for HARQ-ACK transmission and a PUCCH resource for SR and/or CSI transmission overlap, or a plurality of PUCCH resources for SR and/or CSI transmission overlap are multiplexed.
  • whether or not HARQ-ACK and CSI are multiplexed may be set through simultaneousHARQ-ACK-CSI parameters for PUCCH formats 2, 3, and 4, and the corresponding parameters may all be set to the same value for the PUCCH format. If multiplexing is not set to be performed through the above parameter, only HARQ-ACK is transmitted and overlapping CSI may be dropped.
  • whether or not multiplexing between a plurality of CSIs can be set through a multi-CSI-PUCCH-ResourceList parameter in PUCCH-Config. That is, when the multi-CSI-PUCCH-ResourceList parameter is set, inter-CSI multiplexing may be performed. Otherwise, only a PUCCH corresponding to a CSI having a higher priority according to the inter-CSI priority may be transmitted.
  • a method of selecting a PUCCH resource to transmit a corresponding UCI resource and a multiplexing method may differ according to the information of overlapped UCI and the format of the PUCCH resource, which can be summarized as shown in Table 26 below. .
  • SR format 0/1) HARQ-ACK CSI (format 2, 3, 4) format 1 format 0, 2, 3, 4 SR (format 0/1) - option 1 option 2 option 3 HARQ-ACK format 1 option 1 option 4 option 4 option 5 (grant-based) option 6 (SPS) format 0, 2, 3, 4 option 2 option 4 option 4 option 5 (grant-based) option 6 (SPS) CSI (format 2, 3, 4) option 3 option 5 (grant-based) option 6 (SPS) option 5 (grant-based) option 6 (SPS) option 7
  • the UE makes different PUCCH resource selection according to the SR value of the HARQ-ACK PUCCH resource and the overlapped SR PUCCH resource. That is, if the SR value is positive, the SR PUCCH resource is selected. If the SR value is negative, the HARQ-ACK PUCCH resource is selected. HARQ-ACK information is transmitted to the selected PUCCH resource.
  • UE transmits by multiplexing HARQ-ACK information and SR information on PUCCH resources for HARQ-ACK transmission.
  • UE transmits by multiplexing SR information and CSI on PUCCH resources for CSI transmission.
  • the UE transmits CSI HARQ-ACK information and CSI information are multiplexed and transmitted on PUCCH resources for.
  • the UE selects one of the resources in the list with the lowest index capable of transmitting all the multiplexed UCI payloads, and then UCI Send the payload. If there is no resource capable of transmitting all of the multiplexed UCI payloads in the list, the UE selects the resource with the largest index and then transmits HARQ-ACKs and CSI reports as many as possible to the corresponding resource.
  • 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.
  • multiplexing is set not to be performed when multiple CSI PUCCH resources overlap, a PUCCH corresponding to a high-priority CSI is transmitted, and a PUCCH corresponding to another CSI may be dropped.
  • Case 2 that is, when multi-slot repetition is configured, is divided into Case 2-1) a case where two or more PUCCH resources for HARQ-ACK transmission are located in the same start slot and Case 2-2) the remaining cases. Each case is shown in FIG. 10.
  • FIG. 10 is a diagram illustrating an example in which PUCCH resources overlap when multi-slot repetition is configured according to an embodiment of the present disclosure.
  • Case 2-2 corresponds to a case in which 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, when PUCCH #1 is repeatedly transmitted over multiple slots (1050, 1051) and PUCCH #2 is also repeatedly transmitted over multiple slots (1060, 1061), PUCCH #1 and PUCCH #2 are in one slot (1070). This is the case where more than one symbol overlap occurs.
  • a PUCCH corresponding to a CSI having a higher priority is transmitted, and a PUCCH corresponding to another CSI may be dropped in a corresponding slot.
  • PUCCH transmission or drop according to the above-described priority is performed only in a slot in which symbol unit overlap has occurred, and not in other slots. That is, the PUCCH in which multi-slot repetition is set may be dropped in a slot in which symbol unit overlap occurs, but may be transmitted as set in the remaining slots.
  • 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 upper signaling, pucch-ResourceCommon, in this case, the beam configuration for PUCCH transmission is Random Access Resoponse (RAR)
  • RAR Random Access Resoponse
  • the beam configuration for PUCCH transmission is provided through pucch-spatialRelationInfoId, which is a higher level signaling shown in Table 219.
  • the terminal If the UE has been configured with one pucch-spatialRelationInfoId, beam configuration for PUCCH transmission of the UE is provided through one pucch-spatialRelationInfoId. If the terminal has been configured with a plurality of pucch-spatialRelationInfoIDs, the terminal is instructed to activate one of the plurality of pucch-spatialRelationInfoIDs through a MAC CE (control element) from the base station. The terminal may receive up to eight pucch-spatialRelationInfoIDs through higher-level signaling, and may receive an indication that only one pucch-spatialRelationInfoID is activated among them.
  • MAC CE control element
  • pucch-spatialRelationInfoID activation through MAC CE is applied.
  • ⁇ above is the neurology applied to PUCCH transmission, Denotes the number of slots per subframe in a given neurology.
  • the upper layer configuration for pucch-spatialRelationInfo may be as shown in Table 27 below. pucch-spatialRelationInfo can be mixed with PUCCH beam information.
  • PUCCH-SpatialRelationInfo :: SEQUENCE ⁇
  • one referenceSignal setting may exist in a specific pucch-spatialRelationInfo setting, and the referenceSignal is ssb-Index indicating a specific SS/PBCH, csi-RS-Index indicating a specific CSI-RS, or It may be srs indicating a specific SRS.
  • the UE sets the beam used when receiving the SS/PBCH corresponding to the ssb-Index among SS/PBCHs in the same serving cell as the beam for PUCCH transmission, or if servingCellId is provided.
  • a beam used when receiving an SS/PBCH corresponding to an ssb-Index among SS/PBCHs in a cell indicated by servingCellId may be set as a beam for PUCCH transmission.
  • the UE sets a 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, a beam used when receiving a CSI-RS corresponding to csi-RS-Index among CSI-RSs in a cell indicated by servingCellId may be set as a beam for PUCCH transmission.
  • the UE sets the transmission beam used to transmit the SRS corresponding to the resource index provided as a higher signaling resource in the same serving cell and/or in the activated uplink BWP as a beam for PUCCH transmission.
  • the transmission beam used when transmitting the SRS corresponding to the resource index provided through the higher signaling resource in the cell indicated by servingCellID and/or uplinkBWP and/or in the uplink BWP is used for PUCCH transmission. It can be set as a beam for.
  • One pucch-PathlossReferenceRS-Id configuration may exist in a specific pucch-spatialRelationInfo configuration.
  • PUCCH-PathlossReferenceRS of Table 28 can be mapped with pucch-PathlossReferenceRS-Id of Table 27, and up to 4 can be set through pathlossReferenceRSs in the upper signaling PUCCH-PowerControl of Table 28. If the PUCCH-PathlossReferenceRS is connected to the SS/PBCH through the referenceSignal of Table 28, the ssb-Index is set, and if it is connected to the CSI-RS, the csi-RS-Index is set.
  • pathlossReferenceRSs SEQUENCE (SIZE (1..maxNrofPUCCH-PathlossReferenceRSs)) OF PUCCH-PathlossReferenceRS OPTIONAL, - Need M
  • the base station may configure at least one SRS configuration for each uplink BWP in order to transmit configuration information for SRS transmission to the terminal, and may also configure at least one SRS resource set for each SRS configuration.
  • the base station and the terminal may exchange higher-level signaling information as follows in order to transmit information on the SRS resource set.
  • a time axis transmission setting of the SRS resource referenced in the SRS resource set may be set to one of'periodic','semi-persistent', and'aperiodic'. If it is set to'periodic' or'semi-persistent', associated CSI-RS information may be provided according to the usage of the SRS resource set. If set to'aperiodic', an aperiodic SRS resource trigger list and slot offset information may be provided, and associated CSI-RS information may be provided according to the usage of the SRS resource set.
  • the usage destination of the SRS resource referenced in the SRS resource set it may be set to one of'beamManagement','codebook','nonCodebook', and'antennaSwitching'.
  • the UE can understand that the SRS resource included in the set of SRS resource indexes referenced in the SRS resource set follows the information set in the SRS resource set.
  • the base station and the terminal may transmit and receive higher layer signaling information to deliver individual configuration information for the SRS resource.
  • the individual configuration information for the SRS resource may include time-frequency axis mapping information within the slot of the SRS resource, and this may include information on frequency hopping within or between slots of the SRS resource.
  • the individual configuration information for the SRS resource may include the time axis transmission configuration of the SRS resource, and may be set to one of'periodic','semi-persistent', and'aperiodic'. This may be limited to have the same time axis transmission configuration as the SRS resource set including the SRS resource.
  • an SRS resource transmission period and a slot offset may additionally be included in the time axis transmission setting.
  • the base station may activate, deactivate, or trigger SRS transmission to the terminal through higher layer signaling including RRC signaling or MAC CE signaling, or L1 signaling (eg, DCI). For example, the base station may activate or deactivate periodic SRS transmission through higher layer signaling to the terminal.
  • the base station may instruct to activate the SRS resource set in which the resourceType is set to periodic through higher layer signaling, and the terminal may transmit the SRS resource referenced in the activated SRS resource set.
  • the time-frequency axis resource mapping in the slot of the transmitted SRS resource follows the resource mapping information set in the SRS resource, and the slot mapping including the transmission period and the slot offset follows the periodicityAndOffset set in the SRS resource.
  • the spatial domain transmission filter applied to the transmitted SRS resource may refer to spatial relation info set in the SRS resource, or may refer to associated CSI-RS information set in the SRS resource set including the SRS resource.
  • the terminal may transmit the SRS resource in the uplink BWP activated for the periodic SRS resource activated through higher layer signaling.
  • the base station may activate or deactivate semi-persistent SRS transmission through higher layer signaling to the terminal.
  • the base station may instruct to activate the SRS resource set through MAC CE signaling, and the terminal may transmit the SRS resource referenced in the activated SRS resource set.
  • the SRS resource set activated through MAC CE signaling may be limited to an SRS resource set in which the resourceType is set to semi-persistent.
  • the time-frequency axis resource mapping in the slot of the transmitted SRS resource follows the resource mapping information set in the SRS resource, and the slot mapping including the transmission period and the slot offset follows the periodicityAndOffset set in the SRS resource.
  • the spatial domain transmission filter applied to the transmitted SRS resource may refer to spatial relation info set in the SRS resource, or may refer to associated CSI-RS information set in the SRS resource set including the SRS resource. If spatial relation info is set in the SRS resource, the spatial domain transmission filter may be determined by referring to configuration information about spatial relation info delivered through MAC CE signaling that does not follow this and activates semi-persistent SRS transmission.
  • the terminal may transmit the SRS resource in the uplink BWP activated for the semi-persistent SRS resource activated through higher layer signaling.
  • the base station may trigger aperiodic SRS transmission to the terminal through DCI.
  • the base station may indicate one of the aperiodic SRS resource triggers (aperiodicSRS-ResourceTrigger) through the SRS request field of the DCI.
  • the UE may understand that the SRS resource set including the aperiodic SRS resource trigger indicated through DCI in the aperiodic SRS resource trigger list among the configuration information of the SRS resource set is triggered.
  • the terminal may transmit the SRS resource referenced in the triggered SRS resource set.
  • the time-frequency axis resource mapping in the slot of the transmitted SRS resource follows the resource mapping information set in the SRS resource.
  • slot mapping of the transmitted SRS resource may be determined through a slot offset between the PDCCH including the DCI and the SRS resource, which refers to the value(s) included in the slot offset set set in the SRS resource set.
  • the slot offset between the PDCCH including the DCI and the SRS resource may apply a value indicated in the time domain resource assignment field of the DCI among the offset value(s) included in the slot offset set set in the SRS resource set.
  • the spatial domain transmission filter applied to the transmitted SRS resource may refer to spatial relation info set in the SRS resource or may refer to associated CSI-RS information set in the SRS resource set including the SRS resource.
  • the terminal may transmit the SRS resource in the uplink BWP activated for the aperiodic SRS resource triggered through DCI.
  • the base station triggers aperiodic SRS transmission to the terminal through DCI, in order for the terminal to transmit the SRS by applying configuration information on the SRS resource, between the PDCCH including the DCI triggering the aperiodic SRS transmission and the transmitted SRS
  • a minimum time interval of may be required.
  • the time interval for SRS transmission of the UE is defined as the number of symbols between the first symbol to which the SRS resource transmitted first is mapped among the SRS resource (s) transmitted from the last symbol of the PDCCH including the DCI that triggers the aperiodic SRS transmission. can do.
  • the minimum time interval may be determined with reference to a PUSCH preparation procedure time required for the UE to prepare for PUSCH transmission.
  • the minimum time interval may have a different value according to the usage destination of the SRS resource set including the transmitted SRS resource.
  • the minimum time interval may be determined as an N 2 symbol defined in consideration of the terminal processing capability according to the capability of the UE with reference to the PUSCH preparation process time of the UE.
  • the minimum time interval is set as N 2 symbols, and the usage destination of the SRS resource set is'nonCodebook. 'Or'beamManagement', the minimum time interval can be set to N 2 +14 symbols.
  • the terminal transmits an aperiodic SRS when the time interval for aperiodic SRS transmission is greater than or equal to the minimum time interval, and ignores the DCI that triggers the aperiodic SRS when the time interval for aperiodic SRS transmission is less than the minimum time interval. I can.
  • the spatialRelationInfo configuration information of Table 29 refers to one reference signal and applies the beam information of the reference signal to the beam used for the corresponding SRS transmission.
  • the setting of spatialRelationInfo may include information as shown in Table 30 below.
  • the base station may set an SS/PBCH block index, a CSI-RS index, or an SRS index as an index of a reference signal to be referenced in order to use beam information of a specific reference signal.
  • the higher signaling referenceSignal is configuration information indicating which reference signal beam information is to be referred to for the corresponding SRS transmission
  • ssb-Index is the index of the SS/PBCH block
  • csi-RS-Index is the index of the CSI-RS
  • srs is the index of the SRS.
  • the terminal may apply the reception beam used when receiving the SS/PBCH block corresponding to the ssb-Index as the transmission beam of the corresponding SRS transmission. If the value of the higher signaling referenceSignal is set to'csi-RS-Index', the terminal may apply the reception beam used when receiving the CSI-RS corresponding to csi-RS-Index as the transmission beam of the corresponding SRS transmission. . If the value of the higher signaling referenceSignal is set to'srs', the UE may apply the transmission beam used when transmitting the SRS corresponding to srs as the transmission beam of the corresponding SRS transmission.
  • PUSCH transmission may be dynamically scheduled by a UL grant in DCI, or may operate according to a configured grant Type 1 or Type 2.
  • the dynamic scheduling indication for PUSCH transmission is possible in DCI format 0_0 or 0_1.
  • the configured grant Type 1 PUSCH transmission may be semi-statically configured through reception of configuredGrantConfig including rrc-ConfiguredUplinkGrant of Table 31 through higher signaling without receiving DCI scheduling UL transmission.
  • the configured grant Type 2 PUSCH transmission may be semi-persistently scheduled by the UL grant in the DCI after reception of the configuredGrantConfig that does not include the rrc-ConfiguredUplinkGrant of Table 31 through higher signaling.
  • parameters applied to PUSCH transmission are shown in Table 31 except for dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and scaling of UCI-OnPUSCH, which are provided as upper signaling, pusch-Config in Table 32.
  • configuredGrantConfig It is applied through the higher signaling configuredGrantConfig. If the UE has been provided with transformPrecoder in configuredGrantConfig, which is the upper signaling of Table 31, the UE applies tp-pi2BPSK in pusch-Config of Table 32 to PUSCH transmission operated by the configured grant.
  • sym32x14 sym40x14, sym64x14, sym80x14, sym128x14, sym160x14, sym256x14, sym320x14, sym512x14,
  • sym40x12 sym64x12, sym80x12, sym128x12, sym160x12, sym256x12, sym320x12, sym512x12, sym640x12,
  • pathlossReferenceIndex INTEGER (0..maxNrofPUSCH-PathlossReferenceRSs-1),
  • PUSCH transmission may follow a codebook-based transmission method and a non-codebook-based transmission method, respectively, depending on whether the value of txConfig in the pusch-Config of Table 32, which is the higher signaling, is'codebook' or'nonCodebook'.
  • PUSCH transmission may be dynamically scheduled through DCI format 0_0 or 0_1, and may be semi-statically configured by a set grant. If the UE is instructed to schedule PUSCH transmission through DCI format 0_0, the UE uses the pucch-spatialRelationInfoID corresponding to the UE-specific PUCCH resource corresponding to the minimum ID in the uplink BWP activated in the serving cell. Beam configuration for transmission is performed, and in this case, PUSCH transmission is based on a single antenna port. The UE does not expect scheduling for PUSCH transmission through DCI format 0_0 within a BWP in which PUCCH resources including pucch-spatialRelationInfo are not configured. If the UE has not configured the txConfig in the pusch-Config of Table 32, the UE does not expect to be scheduled in DCI format 0_1.
  • frequencyHoppingOffsetLists SEQUENCE (SIZE (1..4)) OF INTEGER (1.. maxNrofPhysicalResourceBlocks-1)
  • codebookSubset ENUMERATED ⁇ fullyAndPartialAndNonCoherent, partialAndNonCoherent,nonCoherent ⁇
  • Codebook-based PUSCH transmission may be dynamically scheduled through DCI format 0_0 or 0_1, and may operate semi-statically by a set grant. If the codebook-based PUSCH is dynamically scheduled according to DCI format 0_1 or is semi-statically set by a set grant, the UE has an SRS Resource Indicator (SRI), a Transmission Precoding Matrix Indicator (TPMI), and a transmission rank (PUSCH). A precoder for PUSCH transmission is determined based on the number of transport layers).
  • SRI SRS Resource Indicator
  • TPMI Transmission Precoding Matrix Indicator
  • PUSCH transmission rank
  • a precoder for PUSCH transmission is determined based on the number of transport layers).
  • TPMI is used to indicate a precoder applied to PUSCH transmission. If the terminal has been configured with one SRS resource, the TPMI is used to indicate the precoder to be applied in the configured one SRS resource. If the terminal has been configured with a plurality of SRS resources, the TPMI is used to indicate a precoder to be applied in the SRS resource indicated through the SRI.
  • the precoder to be used for PUSCH transmission is selected from an uplink codebook having the same number of antenna ports as the nrofSRS-Ports value in the upper signaling SRS-Config.
  • the UE determines a codebook subset based on TPMI and codebookSubset in pusch-Config, which is a higher level signaling.
  • the codebookSubset in the upper signaling pusch-Config may be set to one of'fullyAndPartialAndNonCoherent','partialAndNonCoherent', or'nonCoherent' based on the UE capability that the UE reports to the base station.
  • the terminal does not expect that the value of the higher signaling codebookSubset is set to'fullyAndPartialAndNonCoherent'.
  • the terminal does not expect the value of the higher signaling codebookSubset to be set to'fullyAndPartialAndNonCoherent' or'partialAndNonCoherent'.
  • the UE may receive one SRS resource set in which the value of usage in the SRS-ResourceSet, which is the higher signaling, is set to'codebook', and one SRS resource in the corresponding SRS resource set may be indicated through SRI. If multiple SRS resources are set in the SRS resource set in which the upper signaling SRS-ResourceSet is set to'codebook', the UE has the same value for all SRS resources with the value of nrofSRS-Ports in the SRS-Resource, which is the higher signaling. I expect it to be set.
  • the terminal transmits one or more SRS resources included in the SRS resource set in which the usage value is set to'codebook' according to higher signaling, and the base station selects one of the SRS resources transmitted by the terminal and selects the corresponding SRS. Instructs the UE to perform PUSCH transmission using the transmission beam information of the resource.
  • the SRI is used as information for selecting an index of one SRS resource and is included in the DCI.
  • the base station includes information indicating a TPMI and a transmission rank to be used by the UE for PUSCH transmission in the DCI. The UE performs PUSCH transmission by using the SRS resource indicated by the SRI, applying the transmission rank indicated based on the transmission beam of the SRS resource and the precoder indicated by the TPMI.
  • Non-codebook-based PUSCH transmission may be dynamically scheduled through DCI format 0_0 or 0_1, and may operate semi-statically by a set grant.
  • the terminal may be scheduled for non-codebook-based PUSCH transmission through DCI format 0_1.
  • the UE may be configured with one connected NZP CSI-RS resource (non-zero power CSI-RS).
  • the UE may calculate a precoder for SRS transmission through measurement of the NZP CSI-RS resource connected to the SRS resource set. If the difference between the last received symbol of the aperiodic NZP CSI-RS resource connected to the SRS resource set and the first symbol of the aperiodic SRS transmission in the terminal is less than 42 symbols, the terminal information on the precoder for SRS transmission Do not expect to be updated.
  • the connected NZP CSI-RS is indicated by SRS request, which is a field in DCI format 0_1 or 1_1.
  • SRS request which is a field in DCI format 0_1 or 1_1.
  • the connected NZP CSI-RS resource is an aperiodic NZP CSI-RS resource
  • there is a connected NZP CSI-RS when the value of the field SRS request in DCI format 0_1 or 1_1 is not '00' It will point to ham.
  • the DCI should not indicate cross carrier or cross BWP scheduling.
  • the corresponding NZP CSI-RS is located in a slot in which the PDCCH including the SRS request field is transmitted. At this time, the TCI states set in the scheduled subcarrier are not set to QCL-TypeD.
  • the connected NZP CSI-RS may be indicated through the associatedCSI-RS in the SRS-ResourceSet, which is higher signaling.
  • the UE does not expect that spatialRelationInfo, which is an upper level signaling for SRS resources, and associatedCSI-RS in SRS-ResourceSet, which is an upper level signaling, are configured together.
  • the UE may determine a precoder and a transmission rank to be applied to PUSCH transmission based on the SRI indicated by the base station.
  • the SRI may be indicated through a field SRS resource indicator in the DCI or may be set through an upper signaling srs-ResourceIndicator.
  • the SRS resource indicated by the SRI is SRS resource corresponding to the SRI among the SRS resourc transmitted prior to the PDCCH including the SRI. it means.
  • the UE can use one or more SRS resources for SRS transmission, and the maximum number of SRS resources that can be simultaneously transmitted in the same symbol within one SRS resource set and the maximum number of SRS resources are determined by the UE capability reported by the UE to the base station. Is determined. At this time, the SRS resources transmitted by the terminal at the same time occupy the same RB.
  • the terminal configures one SRS port for each SRS resource. Only one SRS resource set in which the usage value in the upper signaling SRS-ResourceSet is set to'nonCodebook' can be set, and up to four SRS resources for non-codebook-based PUSCH transmission can be set.
  • the base station transmits one NZP-CSI-RS connected to the SRS resource set to the terminal, and the terminal transmits one or more SRS resources in the corresponding SRS resource set based on the measurement result when receiving the corresponding NZP-CSI-RS.
  • the UE applies the calculated precoder when transmitting one or more SRS resources in the SRS resource set for which usage is set to'nonCodebook' to the base station, and the base station applies one or more of the received one or more SRS resources.
  • Select SRS resources In this case, in non-codebook based PUSCH transmission, the SRI represents an index capable of expressing a combination of one or a plurality of SRS resources, and the SRI is included in the DCI.
  • the number of SRS resources indicated by the SRI transmitted by the base station may be the number of transmission layers of the PUSCH, and the UE transmits the PUSCH by applying a precoder applied to transmission of the SRS resource to each layer
  • a PUSCH preparation procedure time When the base station schedules to transmit the PUSCH to the terminal using DCI format 0_0 or DCI format 0_1, the terminal uses the transmission method indicated through DCI (transmission precoding method of SRS resources, number of transmission layers, spatial domain transmission filter).
  • DCI transmission precoding method of SRS resources, number of transmission layers, spatial domain transmission filter.
  • each variable may have the following meanings.
  • -N 2 Number of symbols determined according to UE processing capability 1 or 2 and neurology ⁇ according to the capability of the UE. If it is reported as UE processing capability 1 according to the UE capability report, it has the value in Table 33, and if it is reported as UE processing capability 2 and that UE processing capability 2 is available through higher layer signaling, it has the value in Table 34. I can.
  • -d 2,1 The number of symbols determined as 0 when the first symbol of the PUSCH is configured to consist of DM-RS only, and 1 when not.
  • T proc,2 follows the larger value.
  • T proc,2 When considering the time axis resource mapping information of the PUSCH scheduled through the DCI and the timing advance (TA) effect between the uplink and the downlink, T proc,2 from the last symbol of the PDCCH including the DCI scheduling the PUSCH. Thereafter, when the first symbol of the PUSCH starts earlier than the first uplink symbol that the CP starts, it is determined that the PUSCH preparation process time is insufficient. If not, the base station and the terminal determine that the PUSCH preparation process time is sufficient. The UE transmits the PUSCH only when the PUSCH preparation process time is sufficient, and may ignore the DCI scheduling the PUSCH when the PUSCH preparation process time is insufficient.
  • TA timing advance
  • the UE If the UE has been scheduled for repeated PUSCH transmission in DCI format 0_1 in a plurality of slots, at least one of the slots in which PUSCH repeated transmission is performed according to the information of the upper layer signaling tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated. If one symbol is indicated as a downlink symbol, the UE does not perform PUSCH transmission in the slot in which the corresponding symbol is located.
  • the following additional methods may be defined for UL grant-based PUSCH transmission over a slot boundary and configured grant-based PUSCH transmission.
  • Method 1 Through one UL grant, two or more repeated PUSCH transmissions within one slot or beyond the boundary of consecutive slots are scheduled.
  • the time domain resource allocation information in the DCI indicates a resource of the first repeated transmission.
  • time-domain resource information of the first repetitive transmission and time-domain resource information of the remaining repetitive transmission may be determined according to the uplink or downlink direction determined for each symbol of each slot. Each repetitive transmission occupies consecutive symbols.
  • -Method 2 Two or more repeated PUSCH transmissions are scheduled in consecutive slots through one UL grant. In this case, one transmission is designated for each slot, and different starting points or repetition lengths may be different for each transmission. Also, in Method 2, the time domain resource allocation information in the DCI indicates a start point and a repetition length of all repetitive transmissions. In addition, when repetitive transmission is performed in a single slot through Method 2, if multiple bundles of consecutive uplink symbols exist in the corresponding slot, each repetitive transmission is performed for each uplink symbol bundle. If there is only a bundle of consecutive uplink symbols in the corresponding slot, one PUSCH repetition transmission is performed according to the method of NR release 15.
  • Two or more repeated PUSCH transmissions are scheduled in consecutive slots through two or more UL grants. In this case, one transmission is designated for each slot, and the n-th UL grant may be received before the PUSCH transmission scheduled for the n-1 th UL grant is finished.
  • -Method 4 Through one UL grant or one configured grant, one or several PUSCH repetition transmissions within a single slot, or two or more PUSCH repetition transmissions over the boundary of consecutive slots may be supported. .
  • the number of repetitions indicated by the base station to the terminal is only a nominal value, and the number of repeated PUSCH transmissions actually performed by the terminal may be greater than the nominal number of repetitions.
  • the time domain resource allocation information in the DCI or in the set grant refers to the resource of the first repeated transmission indicated by the base station.
  • the time domain resource information of the remaining repetitive transmission may be determined with reference to at least the resource information of the first repetition transmission and the uplink or downlink direction of the symbols.
  • the repetitive transmission may be divided into a plurality of repetitive transmissions. In this case, one repetitive transmission may be included for each uplink period within one slot.
  • FIG. 11 is a diagram illustrating a radio protocol structure of a base station and a terminal when performing single cell, carrier aggregation, and dual access according to an embodiment of the present disclosure.
  • radio protocols of a next-generation mobile communication system include NR SDAP (Service Data Adaptation Protocol 1125, 1170), NR PDCP (Packet Data Convergence Protocol 1130, 1165), NR RLC (Radio Link Control) in the terminal and the NR base station, respectively. 1135, 1160), and NR MAC (Medium Access Control 1140, 1155).
  • NR SDAP Service Data Adaptation Protocol 1125, 1170
  • NR PDCP Packet Data Convergence Protocol 1130, 1165
  • NR RLC Radio Link Control
  • NR MAC Medium Access Control
  • the main functions of the NR SDAPs 1125 and 1170 may include some of the following functions.
  • the UE may be configured with an RRC message to set whether to use the header of the SDAP layer device or the function of the SDAP layer device for each PDCP layer device, for each bearer, or for each logical channel, and the SDAP header
  • the UE uses the NAS QoS reflection configuration 1-bit indicator (NAS reflective QoS) and the AS QoS reflection configuration 1-bit indicator (AS reflective QoS) in the SDAP header to map the QoS flow of the uplink and downlink and the data bearer. Can be instructed to update or reset.
  • the SDAP header may include QoS flow ID information indicating QoS.
  • the QoS information may be used as data processing priority, scheduling information, etc. to support a smooth service.
  • the main functions of the NR PDCP 1130, 1165 may include some of the following functions.
  • the reordering function of the NR PDCP device refers to a function of rearranging the PDCP PDUs received from the lower layer in order based on the PDCP sequence number (SN), and the function of delivering data to the upper layer in the rearranged order.
  • SN PDCP sequence number
  • the reordering function of the NR PDCP device refers to a function of rearranging the PDCP PDUs received from the lower layer in order based on the PDCP sequence number (SN), and the function of delivering data to the upper layer in the rearranged order.
  • SN PDCP sequence number
  • the main functions of the NR RLCs 1135 and 1160 may include some of the following functions.
  • the in-sequence delivery function of the NR RLC device refers to the function of delivering RLC SDUs received from the lower layer to the upper layer in order, and originally, one RLC SDU is divided into several RLC SDUs and received. If so, it may include a function of reassembling and delivering it, and may include a function of rearranging the received RLC PDUs based on an RLC sequence number (SN) or a PDCP sequence number (SN), and rearranging the order It may include a function of recording lost RLC PDUs, may include a function of reporting a status of lost RLC PDUs to a transmitting side, and a function of requesting retransmission of lost RLC PDUs.
  • SN RLC sequence number
  • SN PDCP sequence number
  • If there is a lost RLC SDU it may include a function of transferring only RLC SDUs before the lost RLC SDU to a higher layer in order, or if a predetermined timer expires even if there is a lost RLC SDU, the timer It may include a function of delivering all RLC SDUs received before the start of the RLC to the upper layer in order, or if a predetermined timer expires even if there is a lost RLC SDU, all RLC SDUs received so far are sequentially transferred to the upper layer. It may include the ability to deliver.
  • the RLC PDUs can be processed in the order of reception (regardless of the order of serial number and sequence number, in the order of arrival) and delivered to the PDCP device regardless of the order (Out-of sequence delivery), and the PDU is segmented.
  • segments stored in a buffer or to be received in the future may be received, reconstructed into a complete RLC PDU, processed, and delivered to the PDCP device.
  • the NR RLC layer 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 out-of-sequence delivery function of the NR RLC device refers to the function of directly delivering RLC SDUs received from the lower layer to the upper layer regardless of the order.
  • it may include a function of reassembling and transmitting them, and includes a function of storing the RLC SN or PDCP SN of the received RLC PDUs, sorting the order, and recording the lost RLC PDUs. I can.
  • the NR MACs 1140 and 1155 may be connected to several NR RLC layer devices configured in one terminal, and the main functions of the NR MAC may include some of the following functions.
  • Multiplexing/demultiplexing of MAC SDUs Multiplexing/demultiplexing of MAC SDUs
  • the NR PHY layer (1145, 1150) performs channel coding and modulation of upper layer data, making it into OFDM symbols and transmitting it to the radio channel, or demodulating and channel decoding the OFDM symbol received through the radio channel and transmitting it to the upper layer. You can do it.
  • the detailed structure of the radio protocol structure may be variously changed according to a carrier (or cell) operation method.
  • a base station transmits data to a terminal based on a single carrier (or cell)
  • the base station and the terminal use a protocol structure having a single structure for each layer, such as 1100.
  • the base station and the terminal have a single structure up to the RLC layer, such as 1110, but a protocol structure that multiplexes the PHY layer through the MAC layer. Will be used.
  • the base station and the terminal when a base station transmits data to a terminal based on dual access using multiple carriers in multiple TRP, the base station and the terminal have a single structure up to the RLC layer, such as 1120, but multiplex the PHY layer through the MAC layer.
  • the protocol structure is used.
  • TRP transmission reception point, transmission point
  • PUCCH-PathlossReferenceRS used for repeated PUCCH transmission considered starting RB point and frequency hopping pattern are also considered for transmission to a single TRP.
  • transmission to a single TRP is considered regardless of codebook-based or non-codebook-based transmission.
  • the transmission beam of the terminal may be determined by the SRI and TPMI transmitted from the base station, that is, a single TRP to the terminal.
  • a base station that is, an NZP CSI-RS that can be configured from a single TRP, can be set to the terminal, and a transmission beam of the terminal can be determined by SRI transmitted from a single TRP.
  • the UE in NR release 16 or later, it is possible to support repeated PUCCH and PUSCH transmission for multiple TRP.
  • the UE must support configuration for repeated PUCCH and PUSCH transmission to a plurality of TRPs.
  • a plurality of beam directions should be considered for transmission to a plurality of TRPs, but a method of setting a plurality of beams for one PUCCH resource, or transmission using a plurality of PUCCH resources for repeated PUCCH transmission How to do this was not defined in Release 15.
  • PUCCH-PathlossReferenceRS considered starting RB point and frequency hopping pattern, codebook-based or non-codebook-based transmission scheme for repeated PUSCH transmission, and multiple TRPs as in the case of repeated PUCCH transmission
  • the present invention by providing a processing method for the above-described case, it is possible to minimize the loss of uplink control information and data and transmission delay time when repeatedly transmitting PUCCH and PUSCH considering a plurality of TRPs.
  • the present invention can be applied to a PUSCH repetitive transmission scheme that exceeds a slot boundary considered in NR release 16, and in the case of PUSCH repetition transmission, a DCI-based dynamic scheduling and a configured grant-based higher signaling configuration scheme are both applicable.
  • Do. A method of setting and determining repetitive PUCCH and PUSCH transmission to a plurality of TRPs by the UE for the number of various cases will be 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, BS (Base Station), 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
  • a computer or a multimedia system capable of performing a communication function.
  • an embodiment of the present disclosure will be described below using an NR or LTE/LTE-A system as an example, but an embodiment of the present disclosure may be applied to other communication systems having a similar technical background or channel type.
  • embodiments of the present disclosure may be applied to other communication systems through some modifications without significantly departing from the scope of the present disclosure, as determined by a person having skilled technical
  • the contents of the present disclosure are 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, It may also be referred to as RRC signaling, PDCP signaling, or a medium access control (MAC) control element (MAC control element, MAC CE).
  • RRC signaling PDCP signaling
  • MAC control element MAC control element
  • the PDCCH(s) for allocating the PDSCH to which the cooperative communication is applied has a specific format, or the PDCCH(s) for allocating the PDSCH to which the cooperative communication is applied cooperate. Includes a specific indicator indicating whether or not communication is applied, or the PDCCH(s) allocating a PDSCH to which cooperative communication is applied are scrambled with a specific RNTI, or assuming the application of cooperative communication in a specific section indicated by a higher layer, etc. It is possible to use a variety of methods. For convenience of explanation later, it will be referred to as an NC-JT case that the UE receives the PDSCH to which cooperative communication is applied based on conditions similar to those described above.
  • determining the priority between A and B refers to selecting the one having a higher priority according to a predetermined priority rule and performing the corresponding operation or having a lower priority. It may be mentioned in various ways, such as omitting or dropping the operation for.
  • TRP transmission and reception points
  • Joint Transmission is a representative transmission technology for cooperative communication as described above, and supports one terminal through different cells, TRPs, or/and beams through the joint transmission technology to increase the strength of the signal received by the terminal.
  • I can. Meanwhile, different precoding, MCS, resource allocation, etc. need to be applied to each cell, TRP, or/and the link between the beam and the terminal, since the characteristics of each cell, TRP or/and the beam and the channel between the terminal may be significantly different. .
  • NC-JT non-coherent joint transmission
  • each cell, TRP or/and beam It is important to set individual DL transmission information for each cell, TRP, or/or beam, while setting the individual DL transmission information for each cell, TRP, or/or beam becomes a major factor in increasing the payload required for DL DCI transmission, which is Therefore, it is necessary to carefully design a tradeoff between the amount of DCI information and the PDCCH reception performance in order to support JT.
  • FIG. 12 is a diagram illustrating an example of an antenna port configuration and resource allocation for cooperative communication according to some embodiments in a wireless communication system according to an embodiment of the present disclosure.
  • FIG. 12 examples of radio resource allocation for each TRP according to a joint transmission (JT) technique and a situation are shown.
  • 1200 is an example of coherent joint transmission (C-JT) supporting coherent precoding between each cell, TRP, or/and beam.
  • C-JT coherent joint transmission
  • PDSCH single data
  • TRP A 1205 and TRP B 1210 transmit the same DMRS ports (eg, DMRS ports A and B in both TRPs) for the same PDSCH transmission.
  • the UE may receive one DCI information for receiving one PDSCH demodulated based on the DMRS transmitted through the DMRS ports A and B.
  • 1220 is an example of non-coherent joint transmission supporting non-coherent precoding between each cell, TRP, or/and beam.
  • a PDSCH is transmitted to the terminal 1235 for each cell, TRP, or/and beam, and individual precoding may be applied to each PDSCH.
  • Each cell, TRP, or/and beam transmits a different PDSCH to improve throughput compared to single cell, TRP, or/and beam transmission, or each cell, TRP, or/and beam repeatedly transmits the same PDSCH to a single cell, TRP Alternatively, it is possible to improve reliability compared to beam transmission.
  • radio resource allocations may be considered, such as when some of the resources overlap (1250).
  • the present 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. 13 is a diagram illustrating an example configuration of downlink control information for cooperative communication in a wireless communication system according to an embodiment of the present disclosure.
  • case #1 (1300) is each other in (N-1) additional TRPs (TRP#1 to TRP#(N-1)) in addition to the serving TRP (TRP#0) used when transmitting a single PDSCH.
  • control information for PDSCHs transmitted in (N-1) additional TRPs is in the same form as control information for PDSCHs transmitted in the serving TRP (same DCI format). This is an example that is transmitted.
  • the terminals are all different TRPs (TRP#0 to TRP#(N-1)) through DCIs having the same DCI format and the same payload (DCI#0 to DCI#(N-1)) Control information on PDSCHs transmitted in may be obtained.
  • Case #2(1305) is different (N-1) in (N-1) additional TRPs (TRP#1 to TRP#(N-1)) in addition to the serving TRP (TRP#0) used when transmitting a single PDSCH.
  • 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 the serving TRP. This is an example.
  • 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 cooperation TRP (TRP#1)
  • TRP#1 cooperation TRP (TRP#1)
  • sDCI shortened DCI
  • sDCI#0 to sDCI#(N-2) which is control information for PDSCHs transmitted from TRP#(N-1)
  • information of DCI format 1_0 to DCI format 1_1 It may contain only some of the elements.
  • the payload is smaller than normal DCI (nDCI) that transmits PDSCH-related control information transmitted from the serving TRP, or less than nDCI. It is possible to include reserved bits as many as the number of bits.
  • 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, but since the reception performance of sDCI is superior to that of nDCI, the coverage difference for each DCI is increased. It may be less likely to occur.
  • Case #3 (1310) is different (N-1) in (N-1) additional TRPs (TRP#1 to TRP#(N-1)) other than the serving TRP (TRP#0) used when transmitting a single PDSCH
  • 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 the serving TRP. This is an example.
  • 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, and cooperation TRP (TRP#1) To TRP#(N-1))
  • TRP#1 cooperation TRP
  • 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.
  • the DCI (DCI#0, normal DCI, nDCI) of the serving TRP may be followed.
  • the degree of freedom for controlling (allocation) of each PDSCH may be limited depending on the contents of the information element included in the sDCI, but the reception performance of sDCI can be adjusted and compared with case #1 or case #2, the terminal's The complexity of DCI blind decoding may be reduced.
  • sDCI may refer to various auxiliary DCIs, such as shortened DCI, secondary DCI, or normal DCI (DCI formats 1_0 to 1_1 described above) including PDSCH control information transmitted in the cooperative TRP, and has special restrictions. If not specified, the description is similarly applicable to the various auxiliary DCIs.
  • Case #1, case #2, and case #3 in which one or more DCI (PDCCH) is used for NC-JT support is divided into a plurality of 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.
  • the cooperation TRP may be replaced with various terms such as a cooperation panel or a cooperation beam in actual application.
  • when NC-JT is applied means "when a terminal receives one or more PDSCHs at the same time in one BWP", "a terminal provides two or more TCI indications at the same time in one BWP. Based on the case of receiving the PDSCH", “when the PDSCH received by the terminal is associated with one or more DMRS port groups”, it is possible to be interpreted in various ways according to the situation, but it is used as an expression for convenience of description. .
  • the radio protocol structure for NC-JT can be used in various ways according to the TRP deployment scenario. For example, when there is no or small backhaul delay between cooperative TRPs, it is possible to use a structure based on MAC layer multiplexing similar to 1110 of FIG. 11 (CA-like method). On the other hand, when the backhaul delay between cooperative TRPs is so large that it cannot be ignored (e.g., when more than 2 ms time is required for information exchange such as CSI, scheduling, HARQ-ACK, etc. between cooperative TRPs) By using an independent structure for each TRP, it is possible to secure characteristics that are robust against delay (DC-like method).
  • ⁇ Embodiment 1-1 A method of setting a downlink control channel for transmission of a plurality of PDCCH-based NC-JTs>
  • the CORESET setting information set for the higher layer may include an index value, and the TRP that transmits the PDCCH from the corresponding CORESET can be identified as the set index value for each CORESET. That is, in a set of CORESETs having the same upper layer index value, it may be considered that the same TRP transmits the PDCCH or that the PDCCH scheduling the PDSCH of the same TRP is transmitted.
  • each PDCCH-Config may include a PDCCH configuration for each TRP. That is, a list of CORESETs for each TRP and/or a list of search spaces for each TRP can be configured in one PDCCH-Config, and one or more CORESETs and one or more search spaces included in one PDCCH-Config are considered to correspond to a specific TRP. can do.
  • TRP corresponding to the corresponding CORESET can be classified through a beam or beam group set for each CORESET.
  • the corresponding CORESETs may be regarded as being transmitted through the same TRP, or a PDCCH scheduling a PDSCH of the same TRP may be regarded as being transmitted in the corresponding CORESETs.
  • a beam or beam group is configured for each search space, and through this, the TRP for each search space can be classified. For example, when the same beam/beam group or TCI state is set in multiple search spaces, it can be considered that the same TRP transmits the PDCCH in the search space or that the PDCCH scheduling the PDSCH of the same TRP is transmitted in the search space. have.
  • the following embodiment provides a detailed method of transmitting HARQ-ACK information for NC-JT transmission.
  • 14 to 17 are diagrams illustrating a method of transmitting HARQ-ACK information according to various DCI configurations and PUCCH configurations for NC-JT transmission.
  • FIG. 14 is a diagram illustrating an example in which HARQ-ACK information is transmitted in case of a single PDCCH-based NC-JT.
  • HARQ-ACK information for one or a plurality of PDSCHs 1405 scheduled by a TRP through a single PDCCH 1400 is transmitted through one PUCCH resource 1410.
  • the PUCCH resource may be indicated through the above-described PRI value and K1 value in DCI.
  • each case may be classified according to the number of PUCCH resources to transmit HARQ-ACK information corresponding to the PDSCH of each TRP and the position on the time axis of the PUCCH resource.
  • the UE may transmit HARQ-ACK information corresponding to the PDSCHs 1510 and 1515 of each TRP scheduled by a plurality of PDCCHs 1500 and 1505 through one PUCCH resource 1520.
  • 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 may be concatenated and transmitted in one PUCCH resource.
  • FIG. 16 is a diagram illustrating an example in which PUCCH resources for transmitting HARQ-ACK information are located in different slots in case of a plurality of PDCCH-based NC-JTs.
  • the UE transmits HARQ-ACK information corresponding to the PDSCHs 1610 and 1615 of each TRP scheduled by a plurality of PDCCHs 1600 and 1605 to PUCCH resources 1620 and 1625 of different slots 1630 and 1635. ) Can be transmitted.
  • the slot in which the PUCCH resource for each TRP is transmitted may be determined by the aforementioned K1 value.
  • a K1 value indicated by a plurality of PDCCHs indicates the same slot, all corresponding PDCCHs are considered to be transmitted in the same TRP, and all HARQ-ACK information corresponding to them may be transmitted. In this case, HARQ-ACK information concatenated in one PUCCH resource located in the same slot may be transmitted to the TRP.
  • FIG. 17 is a diagram illustrating an example in which HARQ-ACK information is transmitted through PUCCH resources located in one slot in the case of a plurality of PDCCH-based NC-JTs.
  • the UE transmits HARQ-ACK information corresponding to the PDSCHs 1710 and 1715 of each TRP scheduled by a plurality of PDCCHs 1700 and 1705 in different symbols in the same slot 1730. 1720, 1725).
  • the slot in which the PUCCH resource per TRP is transmitted may be determined by the above-described K1 value, and if the K1 values indicated by multiple PDCCHs indicate the same slot, the UE selects PUCCH resources and transmits symbols through at least one of the following methods. You can make the decision.
  • a PUCCH resource group for HARQ-ACK transmission for each TRP may be configured. As in Embodiment 1-1, when a CORESET or/and a TRP for each search space is classified, a PUCCH resource for HARQ-ACK transmission for each TRP may be selected within a PUCCH resource group for the corresponding TRP. TDM may be expected between PUCCH resources selected from different PUCCH resource groups, that is, it may be expected that the selected PUCCH resources do not overlap on a symbol basis (within the same slot). The UE may generate an individual HARQ-ACK codebook for each TRP and then transmit it in the PUCCH resource selected for each TRP as described above.
  • a PUCCH resource for each TRP may be selected according to the PRI. That is, the above-described PUCCH resource selection process may be independently performed for each TRP.
  • the PRIs used to determine PUCCH resources for each TRP should be different. For example, the UE may not expect that the PRI used for determining PUCCH resources for each TRP is indicated with the same value.
  • TDM can be expected between the PUCCH resources indicated by the PRI for each TRP.
  • an individual HARQ-ACK codebook for each TRP may be generated in the PUCCH resource selected for each TRP and then transmitted.
  • the K1 value may be defined in units of subslots.
  • the UE may generate a HARQ-ACK codebook for PDSCH/PDCCHs instructed to report HARQ-ACK in the same subslot, and then transmit the generated HARQ-ACK codebook to the PUCCH resource indicated by the PRI.
  • the HARQ-ACK codebook generation and PUCCH resource selection process may be irrelevant to whether CORESET and/or TRP classification for each search space is performed.
  • one of the above options may be set through an upper layer or may be implicitly selected according to a situation.
  • a terminal supporting a plurality of PDCCH-based NC-JTs may receive one of the options of FIGS. 15 to 17 as an upper layer.
  • the former option of FIG. 14 may be selected from one of the options of FIGS. 16 to 17.
  • an option to be used may be determined according to the selection of a PUCCH resource.
  • PUCCH resources of the same slot correspond to different TRPs
  • HARQ-ACK is transmitted according to the option of FIG. 17, and the PUCCH resources overlap on a symbol basis or an allocated symbol is If the same, HARQ-ACK may be transmitted according to the option of FIG. 15.
  • HARQ-ACK may be transmitted according to the option of FIG. 16.
  • the setting of the option may be dependent on the terminal capability.
  • the base station may receive the capability of the terminal according to the above-described procedure, and may set the option based on this. For example, only a terminal having the ability to support intra-slot TDMed separate HARQ-ACK (intra-slot TDMed separate HARQ-ACK) that is time division multiplexed in a slot is allowed to set the option of FIG. You may not be expecting to set up according to your options.
  • the terminal may receive PUCCH configuration information from the base station through higher-level signaling (step 1800).
  • the PUCCH configuration information may include at least one of information related to Table 19, Table 20, Table 27, and Table 28, and information for setting the relationship between the PUCCH group configuration information and the PRI and PUCCH resources as shown in Table 24.
  • the terminal receives the DCI for scheduling downlink data from the base station on the PDCCH (this may be mixed with PDCCH reception) (step 1810), and HARQ-ACK to be transmitted according to the method described above based on the applied option.
  • the payload, the PDSCH-to-HARQ feedback timing indicator included in the DCI, and the PRI are checked to determine the PUCCH resource for transmitting the HARQ-ACK (step 1820).
  • the UE transmits HARQ-ACK information in the determined PUCCH resource (step 1830).
  • FIG. 19 is a diagram 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 for the described option transmitted by the UE, and explicitly set which option is applied to the UE based on the capability information transmitted by the UE. Or you can implicitly apply certain options.
  • the base station may transmit PUCCH configuration information to the terminal through higher-level signaling (step 1900).
  • the PUCCH configuration information may include at least one of Table 19, Table 20, Table 27, and Table 28, and information for setting the relationship between the PUCCH group configuration information and the PRI and PUCCH resources as shown in Table 24, and Table 19.
  • At least one of information for setting a candidate of the K1 value such as K1 may be included.
  • the base station transmits the DCI for scheduling downlink data to the terminal on the PDCCH (this can be mixed with PDCCH transmission) (step 1910), and the terminal HARQ to be transmitted according to the above-described method based on the applied option.
  • -ACK payload, a PDSCH-to-HARQ feedback timing indicator included in the DCI, and a PRI are checked to determine a PUCCH resource to transmit HARQ-ACK.
  • the UE transmits HARQ-ACK information in the determined PUCCH resource, and the base station receives HARQ-ACK information in the PUCCH resource determined in the same manner (step 1920).
  • the UE may report the capability for repeated PUCCH transmission to the base station.
  • the capability of the UE may be an indicator for repeated PUCCH transmission to a plurality of TRPs.
  • the repetitive transmission may be divided into repetitive transmission in units of slots or repetition transmission in units of symbols over a slot boundary.
  • the capability of the terminal may indicate whether repetitive transmission in units of slots and repetitive transmission in units of symbols exceeding a slot boundary are possible.
  • a method for the UE to support or determine repeated PUCCH transmission for a plurality of TRPs may be based on condition or configuration information in consideration of at least one of the following conditions or configuration information.
  • the PUCCH resource group may consist of a plurality of PUCCH resources, and all PUCCH resources in the PUCCH resource group may receive the same information for some configuration information, and each in the PUCCH resource group for some configuration information. It may be set differently for each PUCCH resource.
  • Information that may have the same or different configuration information for all PUCCH resources in the PUCCH resource group may include spatialRelationInfo, pathlossReferenceRS, starting PRB point, frequency hopping information, and the like as described above.
  • the UE may be configured for transmission of a plurality of PUCCHs using one PUCCH resource or a PUCCH resource group for repeated PUCCH transmission to a plurality of TRPs.
  • the UE may acquire configuration information for repeated PUCCH transmission to a plurality of TRPs by using configuration information for one PUCCH resource or a PUCCH resource group.
  • the UE may configure a plurality of PUCCH transmission beams by receiving a plurality of PUCCH-spatialRelationInfos for one PUCCH resource or a PUCCH resource group.
  • the base station may configure a plurality of PUCCH transmission beams by activating two or more PUCCH-spatialRelationInfo per PUCCH resource through MAC-CE.
  • the base station may configure a plurality of PUCCH transmission beams corresponding to each referenceSignal by setting two or more referenceSignals in PUCCH-spatialRelationInfo for one PUCCH resource.
  • the base station activates the PUCCH-spatialRelationInfo using the MAC CE
  • the base station activates one PUCCH-spatialRelationInfo per one PUCCH resource through the MAC CE, and can configure the PUCCH transmission beams corresponding to two referenceSignals. have.
  • the terminal sets the referenceSignal value in the PUCCH-spatialRelationInfo for one PUCCH resource: ⁇ SSB#1, SSB#2 ⁇ , ⁇ SSB#1, CSI-RS#1 ⁇ , ⁇ SSB#1, SRS#1 As in ⁇ , ..., two reference signals can be set as one out of a plurality of settings that form a pair.
  • PUCCH transmission beams according to different reference signals may be applied to transmission of an even number of repeated transmissions and transmission of an odd number of repeated transmissions during each repeated transmission.
  • the base station may activate a plurality of PUCCH-spatialRelationInfo per one PUCCH resource by using the MAC-CE as described above.
  • the terminal sets the referenceSignal value in the PUCCH-spatialRelationInfo for one PUCCH resource equal to the number of repetitive transmissions, such as ⁇ SSB#1, CSI-RS#1, SRS#1, ... ⁇ , ...
  • the base station may activate a plurality of PUCCH-spatialRelationInfo per one PUCCH resource by using the MAC-CE as described above.
  • the UE can receive a plurality of PUCCH-pathlossReferenceRSs for one PUCCH resource or a PUCCH resource group and use it for power adjustment when transmitting a plurality of PUCCHs.
  • the UE may perform equal power adjustment using all of the set PUCCH-pathlossReferenceRSs.
  • the UE may select to achieve a maximum RSRP value among a plurality of set PUCCH-pathlossReferenceRSs and use it for power adjustment.
  • all methods of operating, setting, and determining the PUCCH-spatialRelationInfo may be considered.
  • the UE may configure a plurality of starting PRB information such as startingPRB or secondHopPRB, and frequency hopping information such as intraSlotFrequencyHopping or InterslotFrequencyHopping for one PUCCH resource or PUCCH resource group.
  • frequency hopping information may be the same or different for each of a plurality of PUCCH resources in one PUCCH resource group.
  • all methods of operating, setting, and determining the PUCCH-spatialRelationInfo and PUCCH-pathlossReferenceRS may be considered as a method of operating, setting, and determining a plurality of start PRBs or frequency hopping information.
  • the UE may acquire configuration information for repeated PUCCH transmission by using the configuration of a plurality of PUCCH resources or PUCCH resource groups for repeated PUCCH transmission to a plurality of TRPs.
  • the UE may obtain configuration information of repeated PUCCH transmission for each TRP through configuration information of each PUCCH resource or PUCCH resource group.
  • the setting information in the PUCCH resource or the PUCCH resource group may be the same as the current NR release 15, and as above, PUCCH-spatialRelationInfo, PUCCH-pathlossReferenceRS, start PRB, or frequency hopping information is plural for each PUCCH resource and PUCCH resource group. Dogs may exist.
  • the UE performs PUCCH transmission using the setting of one PUCCH resource or a PUCCH resource group in the even-numbered index of the repeated PUCCH transmission It may be performed, and PUCCH transmission may be performed using the setting of the remaining one PUCCH resource or a PUCCH resource group in an odd-numbered index.
  • the UE may report the capability for repetitive PUCCH transmission as the UE capability. Details of the above capabilities are as described above.
  • the base station Upon receiving the UE capability, the base station transmits PUCCH configuration information to the terminal through higher-level signaling, and the terminal receives the PUCCH configuration information (step 2000).
  • the PUCCH configuration information may include at least one of Table 19, Table 20, Table 27, and Table 28, and for PUCCH transmission to a plurality of TRPs, as described above, PUCCH resource and/or PUCCH resource group configuration, a plurality of It may include at least one of PUCCH-spatialRelationInfo information, a plurality of PUCCH-pathlossReferenceRS information, a start PRB in a plurality of PUCCH resources, or frequency hopping information that may indicate the TRP of.
  • the UE receives the MAC CE for activating the PUCCH-spatialRelationInfo from the base station (step 2010), and the MAC CE may indicate a plurality of PUCCH-spatialRelationInfo.
  • a UE receiving the PUCCH configuration information and/or MAC CE may transmit a PUCCH by sequentially or alternately applying a PUCCH transmission beam corresponding to each TRP, and at least some of a plurality of PUCCH-pathlossReferenceRSs according to the above-described method PUCCH transmission power may be controlled by using (step 2020).
  • FIG. 21 is a diagram illustrating an example of a method for a base station to receive a PUCCH repeatedly transmitted by a terminal through a plurality of TRPs.
  • the base station may receive the UE capability for repeated PUCCH transmission reported by the UE. Details of the above capabilities are as described above.
  • the base station receiving the terminal capability transmits the PUCCH configuration information to the terminal through higher-level signaling (step 2100).
  • the PUCCH configuration information may include at least one of Table 19, Table 20, Table 27, and Table 28, and for PUCCH transmission to a plurality of TRPs, as described above, PUCCH resource and/or PUCCH resource group configuration, a plurality of It may include at least one of PUCCH-spatialRelationInfo information, a plurality of PUCCH-pathlossReferenceRS information, a start PRB in a plurality of PUCCH resources, or frequency hopping information that may indicate the TRP of.
  • the base station transmits the MAC CE that activates the PUCCH-spatialRelationInfo to the terminal (step 2110), and the MAC CE may indicate a plurality of PUCCH-spatialRelationInfo.
  • a UE receiving the PUCCH configuration information and/or MAC CE may transmit a PUCCH by sequentially or alternately applying a PUCCH transmission beam corresponding to each TRP, and at least some of a plurality of PUCCH-pathlossReferenceRSs according to the above-described method PUCCH transmission power can be controlled by using.
  • the base station receives the PUCCH repeatedly transmitted by the terminal (step 2120).
  • the corresponding MAC CE is a bitmap indicating one PUCCH resource Id and a plurality of PUCCH-spatialRelationInfo, or It may include a combination index indicating a plurality of PUCCH-spatialRelationInfo.
  • the UE When the UE is scheduled to transmit PUSCH through DCI format 0_0, it may not support repeated PUSCH transmission. If the UE is scheduled for repeated PUSCH transmission to a plurality of TRPs through DCI format 0_0, the UE may configure a plurality of transmission beams for repeated PUSCH transmission, and a method of configuring a plurality of PUSCH transmission beams is as follows. You can follow at least one of them.
  • the UE configures a plurality of PUSCH transmission beams based on the PUCCH-spatialRelationInfo set in the lowest index PUCCH resource in which a plurality of PUCCH-spatialRelationInfos are set.
  • -Method 3 Set a plurality of PUSCH transmission beams based on the PUCCH-spatialRelationInfo corresponding to the number of repeated transmissions from the lowest index among the PUCCH resources for which one PUCCH-spatialRelationInfo is set.
  • -Method 4 Set a plurality of PUSCH transmission beams based on a plurality of PUCCH-spatialRelationInfoId irrespective of PUCCH resources, and a certain number of information is used from a low ID among PUCCH-spatialRelationInfoId, or a certain number of information is used from a high ID. I can.
  • the UE may not expect to receive scheduling in DCI format 0_0 in the BWP in which PUCCH-spatialRelationInfo is not configured.
  • 23A is a diagram illustrating an example of a method of repeatedly transmitting PUSCH based on DCI format 0_0 of a terminal according to some embodiments.
  • FIG. 23A a method of selecting a PUSCH transmission beam based on a PUCCH resource of the lowest index in which two PUCCH-spatialRelationInfos are configured when the UE repeatedly transmits PUSCH based on DCI format 0_0 is illustrated.
  • the terminal may have a plurality of PUCCH resource configuration 2310 in which two PUCCH-spatialRelationInfos are configured through higher-level signaling.
  • the UE since the PUCCH-spatialRelationInfo information of the lowest index among the two PUCCH-spatialRelationInfo is configured, the UE uses PUCCH-spatialRelationInfo#0 and #1 of PUCCH resource #0 during repeated PUSCH transmission. Based on the PUSCH transmission beam can be configured. That is, the UE performs PUSCH repeated transmission #0, #2 (2320, 2330) using PUCCH-spatialRelationInfo#0, and PUSCH repeated transmission #1, #3 (2325, 2335) using PUCCH-spatialRelationInfo#1. I can. Or vice versa.
  • 23B is a diagram illustrating another example of a method of repeatedly transmitting PUSCH based on DCI format 0_0 of a terminal according to some embodiments.
  • the PUCCH resource used in PUCCH transmission that occurs the most recent out of the PUCCH resources for which two PUCCH-spatialRelationInfos are set, or the closest to the PUSCH repetition transmission is based on the PUCCH resource.
  • An example of selecting a PUSCH transmission beam is shown.
  • FIG. 23B it is assumed that two TRPs and repeated PUSCH transmissions of a total of four times (transmitted twice in each TRP) are assumed, and it is assumed that the UE receives one DCI format 0_0 across a plurality of TRPs (2350).
  • PUCCH-spatialRelationInfo setting (2355) for each PUCCH resource was set by higher signaling.
  • the UE is a PUCCH transmission situation #0 based on PUCCH resource #0 (2360), a PUCCH transmission situation #1 based on PUCCH resource #1 (2365), and a PUCCH transmission situation #2 based on PUCCH resource #2 ( 2370) can be set.
  • the UE may select a PUSCH transmission beam based on a PUCCH resource used in a PUCCH transmission situation that occurs closest to the PUSCH repeated transmission in selecting a transmission beam to be used in PUSCH repetition transmission, and this criterion is PUCCH Transmission situation #2 2370 is selected, and the UE may configure a PUSCH transmission beam by selecting PUCCH-spatialRelationInfo#2 and #4 of PUCCH resource #2. That is, the UE performs PUSCH repetitive transmission #0 and #2 (2375, 2385) using PUCCH-spatialRelationInfo#2, and PUSCH repetitive transmission #1, #3 (2380, 2390) using PUCCH-spatialRelationInfo#4. I can. Or vice versa.
  • the UE may not support repeated PUSCH transmission when codebook-based PUSCH transmission is dynamically scheduled through DCI or semi-statically configured through a set grant. If the UE is dynamically scheduled for codebook-based PUSCH repeated transmission through DCI, the UE may configure a plurality of transmission beams for repeated PUSCH transmission, and a method of configuring a plurality of PUSCH transmission beams is at least one of the following methods. You can follow one.
  • Method 1 The UE performs SRS transmission through a plurality of TRPs through SRS resources existing in the SRS resource set whose usage value is a codebook.
  • Each TRP receives the SRS, transmits TPMI information to the terminal through DCI, and does not transmit the SRI.
  • each TRP may transmit an individual TPMI to the terminal by transmitting a DCI, or may transmit a single DCI through a plurality of TRPs to transmit the TPMI.
  • the UE In order to perform repeated PUSCH transmission without SRI, the UE is configured with SRS switching order information by higher layer signaling.
  • the SRS switching order information may be composed of a plurality of SRS resources.
  • PUSCH may be transmitted by applying a PUSCH transmission beam corresponding to a transmission beam of SRS resource #0 at an even-numbered transmission time and SRS resource #1 at an odd-numbered transmission time.
  • the UE may determine whether to transmit a PUSCH through a transmission beam corresponding to an SRS resource for a specific transmission among repeated transmissions of all PUSCHs.
  • the UE may receive one TPMI through DCI and apply the same to all SRS resources, or receive TPMI as much as the number of SRS resources used for repeated PUSCH transmission and apply the TPMI corresponding to each SRS resource. It is also possible to perform repeated PUSCH transmission.
  • Method 2 The terminal performs SRS transmission through a plurality of TRPs through SRS resources existing in the SRS resource set whose usage value is a codebook. Each TRP receives the SRS and delivers TPMI and SRI information to the terminal through DCI. At this time, the UE may receive one TPMI through DCI and apply the same to all SRS resources, or receive TPMI as much as the number of SRS resources used for repeated PUSCH transmission and apply the TPMI corresponding to each SRS resource. It is also possible to perform repeated PUSCH transmission.
  • the SRI information may be an index of a combination expressing a specific number of SRS resources among all SRS resources, or may be an index of a specific SRS resource group when a predefined SRS resource group is set by grouping specific SRS resources. .
  • the UE performs repeated PUSCH transmission based on the received TPMI and SRI information. For example, if the SRI information indicates the index of the combination of two SRS resources, the UE uses a transmission beam of one SRS resource at an even-numbered transmission time among all repeated PUSCH transmissions, and the remaining one at an odd-numbered transmission time.
  • Repeated PUSCH transmission may be performed using a transmission beam of an SRS resource.
  • the UE may use a transmission beam of one SRS resource at a transmission time point of the first half of all repeated PUSCH transmissions, and may use a transmission beam of the other SRS resource at a transmission time point of the other half.
  • the TPMI may have the same value for all transmissions in repeated transmission, or may have a different value for each SRS resource.
  • the terminal may be semi-statically configured through a grant configured for codebook-based PUSCH repetitive transmission.
  • one or more precodingAndNumberOfLayers or srs-ResourceIndicators in rrc-ConfiguredUplinkGrant, which is the higher layer signaling may be set.
  • SRS switching order information may be configured without srs-ResourceIndicator, which is higher layer signaling, and may be used for repeated PUSCH transmission.
  • 24A is a diagram illustrating an example of a method of repeatedly transmitting a codebook-based PUSCH by a terminal according to some embodiments.
  • the UE performs codebook-based PUSCH repetition transmission using TPMI#0 and TPMI#1 in the received DCI and preset SRS switching order information.
  • the UE transmits PUSCH to TRP#0 using TPMI#0, and transmits PUSCH to TRP#1 using TPMI#1.
  • SRS switching order information it is assumed that the UE has previously been configured to transmit using SRS resource #0 at an even-numbered transmission time point and SRS resource #1 at an odd-numbered transmission time point during repeated PUSCH transmission.
  • 24B is a diagram illustrating another example of a method of repeatedly transmitting a codebook-based PUSCH by a terminal according to some embodiments.
  • the UE may perform repeated codebook-based PUSCH transmission based on SRI information.
  • SRI information it is assumed that two TRPs, two SRS resources, and a total of four repeated PUSCH transmissions (twice transmitted to each TRP) are assumed, and TPMI#0 to be applied to transmission to each TRP through one DCI across a plurality of TRPs.
  • TPMI#1 it is assumed that TPMI#1 is delivered.
  • SRI information to be used for transmission from the terminal to each TRP is transmitted to the DCI.
  • the UE performs SRS transmission for a plurality of TRPs in SRS resource #0 (2450, 2455) and SRS resource #1 (2460, 2465).
  • a DCI for dynamically scheduling codebook-based PUSCH repetition transmission in TRP#0 is transmitted to the terminal (2470), and this DCI includes TPMI#0, TPMI#1, and SRI. .
  • the UE transmits TRP#0 using TPMI#0, and transmits TRP#1 using TPMI#1.
  • the UE transmits PUSCH according to SRS resource #0 in PUSCH repetition transmission #0 (2475) and #1 (2480) using the received SRI, and SRS in PUSCH repetition transmission #2 (2485) and #3 (2490).
  • PUSCH can be transmitted according to resource #1.
  • the codebook-based PUSCH repetition transmission based on the DCI-based dynamic scheduling of FIGS. 24A and 24B may be semi-statically configured based on a grant set as described above.
  • repetitive transmission of a slot unit, a symbol unit within a slot, or a symbol unit exceeding a slot boundary may be performed.
  • the UE may not support repeated PUSCH transmission when non-codebook-based PUSCH transmission is dynamically scheduled through DCI or semi-statically configured through a set grant.
  • the UE may receive one or more SRS resource sets whose usage value, which is higher layer signaling, is nonCodebook.
  • a plurality of NZP CSI-RS resources connected to the corresponding SRS resource set may be configured.
  • a plurality of NZP CSI-RS resources connected to the corresponding SRS resource set may have the same or different time domain behavior.
  • the terminal may be configured with a plurality of periodic, semi-permanent, or aperiodic NZP CSI-RS resources connected to a periodic, semi-permanent or aperiodic SRS resource set.
  • a plurality of connected NZP CSI-RS resources may be considered as NZP CSI-RS resources transmitted in each TRP.
  • the base station receives the SRS resource transmission of the terminal and transmits SRI information.
  • the SRI information may be a plurality of combinations of indexes representing a specific number of SRS resources among all SRS resources, or a plurality of SRS resources when a pre-defined SRS resource group is set by grouping specific SRS resources. It can also be passing the index of the group.
  • PUSCH transmission may be performed according to the index of the first SRS resource combination at the even-numbered transmission time point, and PUSCH transmission may be performed according to the index of the second SRS resource combination at the odd-numbered transmission time point.
  • the UE is configured with a plurality of SRS resource sets whose usage value is nonCodebook, one or more NZP CSI-RS resources connected to the corresponding SRS resource set may be configured.
  • one or a plurality of NZP CSI-RS resources connected to the SRS resource set may have the same or different time domain behavior.
  • the terminal may be configured with a plurality of periodic, semi-permanent, or aperiodic NZP CSI-RS resources connected to a periodic, semi-permanent or aperiodic SRS resource set.
  • the UE may consider each of a plurality of SRS resource sets whose usage value is a nonCodebook as information corresponding to the TRP.
  • the UE may operate similarly to non-codebook-based PUSCH repeated transmission in NR Release 15 for each SRS resource set. In this case, SRS resources that do not overlap each other for each SRS resource set should be set.
  • the UE uses the most recently received NZP CSI-RS resource or selects the SRS resource based on the time domain behavior of the plurality of NZP CSI-RS resources. You can calculate the precoder to be used when transmitting. In this case, when the UE selects the NZP-CSI-RS, which is the basis for precoder calculation, using the time domain behavior of the NZP CSI-RS resources, it is selected in the order of aperiodic, semi-permanent, and periodic NZP CSI-RS resources, or , Or vice versa.
  • the UE may calculate one precoder through reception and measurement of a plurality of NZP CSI-RS resources in the corresponding SRS resource set. In addition, as described above, the UE may calculate each precoder through reception and measurement of each of a plurality of NZP CSI-RS resources.
  • the terminal transmits the SRS resource using the precoder calculated by the above methods.
  • the base station receives the SRS resource transmission of the terminal and transmits the SRI information as described above, and the terminal can perform non-codebook-based PUSCH repetition transmission using the SRS resource according to the interpretation of the SRI information as described above.
  • the UE may be semi-statically configured through a grant configured for repetitive non-codebook-based PUSCH transmission.
  • one or more srs-ResourceIndicators in rrc-ConfiguredUplinkGrant which is higher layer signaling, may be configured.
  • the srs-ResourceIndicator may be an index of a combination of a plurality of SRS resources, or an index of an SRS resource group consisting of a plurality of predefined SRS resources.
  • FIGS. 25A and 25B are diagrams illustrating an example of a method of repeatedly transmitting a non-codebook based PUSCH by a terminal according to some embodiments.
  • FIG. 25A is a diagram illustrating an example of a method of repeatedly transmitting a non-codebook based PUSCH of a terminal when one SRS resource set is set
  • FIG. 25B is a non-codebook of the terminal when two SRS resource sets are set. It is a diagram illustrating an example of a method for repetitive transmission of a base PUSCH.
  • the UE may perform non-codebook-based PUSCH repeated transmission using one SRS resource set whose usage value is nonCodebook.
  • SRS resource set whose usage value is nonCodebook.
  • FIG. 25a it is assumed that two TRPs, four SRS resources, and a total of four repeated PUSCH transmissions (two transmissions to each TRP) are assumed, and an SRI to be applied to transmission to each TRP is transmitted through one DCI across a plurality of TRPs. was assumed to be.
  • NZP CSI-RS resources #0 and #1 connected to the SRS resource set were considered.
  • TRP#0 and TRP#1 transmit NZP CSI-RS resources #0 (2500) and #1 (2505) to the terminal, respectively.
  • the UE calculates a precoder to be applied to SRS resources #0 to #3 (2510) to be transmitted to TRP#0 based on the reception and measurement of NZP CSI-RS resource #0. Likewise, the UE calculates a precoder to be applied to SRS resources #0 to #3 (2515) to be transmitted to TRP#1 based on the reception and measurement of NZP CSI-RS resource #1.
  • a DCI for dynamically scheduling non-codebook-based PUSCH repetition transmission in TRP#0 is transmitted to the terminal (2520), and this DCI includes SRI.
  • the UE performs non-codebook-based PUSCH repetitive transmission using the SRI in the received DCI.
  • the SRI may indicate a combination of SRS resources for each TRP.
  • the SRI in the DCI may be an index indicating a pair of SRS resources #0 and #1 for PUSCH transmission to TRP#0 and a pair of SRS resources #2 and #3 for PUSCH transmission to TRP#1. .
  • the UE performs PUSCH transmission using SRS resources #0 and #1 in repeated PUSCH transmission #0 (2525) and #2 (2535), and repeated PUSCH transmission #1 (2530), #3 In (2540), PUSCH transmission is performed using SRS resources #2 and #3.
  • the UE performs 2-layer transmission based on SRS resources #0 and #1 in PUSCH repetitive transmission #0 and #2 (2525, 2535), and at this time, SRS resources #0 and #1 in each layer of PUSCH
  • a precoder based on the precoder applied to each is applied, and the precoder may be the same as or different from the one applied to the SRS resource.
  • the UE performs 2-layer transmission based on SRS resources #2 and #3 in PUSCH repetitive transmission #1 and #3 (2530, 2540).
  • a precoder based on a coder is applied, and this precoder may be the same as or different from that applied to the SRS resource.
  • the UE when two SRS resource sets having a usage value of nonCodebook are set to the UE, and there are two NZP CSI-RS resources connected for each SRS resource set, the UE can perform non-codebook-based PUSCH repetitive transmission.
  • Figure 27b it is assumed that two TRPs, four SRS resources for each SRS resource set, and a total of four repetitive PUSCH transmissions (transmitted twice to each TRP), and transmission to each TRP through one DCI across a plurality of TRPs. It is assumed that the SRI to be applied is delivered.
  • aperiodic NZP CSI-RS resource #0 connected to SRS resource set #0
  • aperiodic NZP CSI-RS resource #2 connected to periodic NZP CSI-RS resource #1 and SRS resource set #1
  • aperiodic NZP CSI- Considered RS resource #3 aperiodic NZP CSI-RS resource #0 connected to SRS resource set #0
  • aperiodic NZP CSI-RS resource #2 connected to periodic NZP CSI-RS resource #1 and SRS resource set #1
  • aperiodic NZP CSI- Considered RS resource #3 aperiodic NZP CSI- Considered RS resource #3.
  • TRP#0 transmits aperiodic NZP CSI-RS resource #0 (2550) and periodic NZP CSI-RS resource #1 (2560) to the terminal, and TRP#1 is aperiodic NZP CSI-RS resource #2 (2550) And aperiodic NZP CSI-RS resource #3 (2565) is transmitted to the terminal.
  • the UE may calculate a precoder to be applied when transmitting SRS resources #0 to #3 to TRP #0 (2570) based on reception and measurement of aperiodic NZP CSI-RS resource #0.
  • the condition in which the NZP CSI-RS resource #0 is selected is because the resource having the most dynamic time domain behavior among the two NZP CSI-RS resources.
  • the condition for selecting the corresponding NZP CSI-RS resource may be to select the resource having the most static time domain behavior.
  • the UE may calculate a precoder to be applied when transmitting SRS resources #4 to #7 to TRP#1 (2575) based on reception and measurement of NZP CSI-RS resource #3.
  • the condition in which the NZP CSI-RS resource #3 is selected is because the most recently received resource among two NZP CSI-RS resources having the same time domain behavior.
  • one DCI is transmitted in TRP#0 (2580), and the corresponding DCI includes an SRI that can be used by the terminal.
  • the SRI may indicate a combination of SRS resources for each TRP.
  • the SRI may include a pair of SRS resources #0 and #1 for PUSCH transmission to TRP#0 and set information of SRS resources #5, #6, and #7 for PUSCH transmission to TRP#1. .
  • the UE Based on the above SRI information, the UE performs PUSCH transmission at repetitive PUSCH transmission times #1 (2590) and #3 (2599) using SRS resources #0 and #1 for repeated PUSCH transmission to TRP#0, and , PUSCH transmission may be performed at repetitive PUSCH transmission times #0 (2585) and #2 (2595) using SRS resources #5, #6, and #7 for repeated PUSCH transmission to TRP#1.
  • the UE performs 2-layer transmission based on SRS resources #0 and #1 in repeated PUSCH transmissions #1 and #3 (2590, 2599) for TRP#0, and at this time, each layer of PUSCH has SRS resource # A precoder based on a precoder applied to 0 and #1, respectively, is applied, and the precoder may be the same as or different from the one applied to the SRS resource.
  • the UE performs 3-layer transmission based on SRS resources #5, #6, #7 in repeated PUSCH transmissions #0 and #2 (2585, 2595) for TRP#1, and at this time, each layer has SRS resource # A precoder based on a precoder applied to each of 5, #6, and #7 is applied, and the precoder may be the same as or different from that applied to the SRS resource.
  • the non-codebook-based PUSCH repetitive transmission based on the DCI-based dynamic scheduling of FIGS. 25A and 25B may be semi-statically configured based on a grant set as described above.
  • repetitive transmission of a slot unit, a symbol unit within a slot, or a symbol unit exceeding a slot boundary may be performed.
  • 26 is a diagram illustrating a terminal structure in a wireless communication system according to an embodiment of the present disclosure.
  • the terminal may include transceivers 2600 and 2610, a memory and a processor 2605.
  • the transmission/reception units 2600 and 2610 of the terminal and the processor 2605 may operate.
  • 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, the memory, and the processor may be implemented in the form of a single chip.
  • the transceivers 2600 and 2610 may transmit and receive signals to and from the base station.
  • the signal may include control information and data.
  • the transceivers 2600 and 2610 may include an RF transmitter that up-converts and amplifies a frequency of a transmitted signal, and an RF receiver that amplifies a received signal with low noise and down-converts a frequency.
  • this is only an example of the transmitting and receiving units 2600 and 2610, and components of the transmitting and receiving units 2600 and 2610 are not limited to the RF transmitter and the RF receiver.
  • the transceivers 2600 and 2610 may receive signals through a wireless channel, output them to the processor 2605, and transmit a signal output from the processor 2605 through the wireless channel.
  • the memory may store programs and data necessary for the operation of the terminal.
  • the memory may store control information or data included in signals transmitted and received by the terminal.
  • the memory may be composed 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).
  • the processor 2605 may control a series of processes so that the terminal can operate according to the above-described embodiment. There may be a plurality of processors 2605, and the processor 2605 may perform a component control operation of the terminal by executing a program stored in the memory.
  • FIG. 27 is a diagram illustrating a structure of a base station in a wireless communication system according to an embodiment of the present disclosure.
  • the base station may include transceivers 2700 and 2710, a memory and a processor 2705. According to the above-described communication method of the base station, the transmission/reception units 2700 and 2710 of the base station and the processor 2705 may operate.
  • 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, the memory, and the processor may be implemented in the form of a single chip.
  • the transceivers 2700 and 2710 may transmit and receive signals to and from the terminal.
  • the signal may include control information and data.
  • the transceivers 2700 and 2710 may include an RF transmitter that up-converts and amplifies a frequency of a transmitted signal, and an RF receiver that amplifies a received signal with low noise and down-converts a frequency.
  • this is only an embodiment of the transmitting and receiving units 2700 and 2710, and components of the transmitting and receiving units 2700 and 2710 are not limited to the RF transmitter and the RF receiver.
  • the transceivers 2700 and 2710 may receive signals through a wireless channel, output them to the processor 2705, and transmit signals output from the processor 2705 through the wireless channel.
  • the memory may store programs and data required for the operation of the base station.
  • the memory may store control information or data included in signals transmitted and received by the base station.
  • the memory may be composed 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.
  • the processor 2705 may control a series of processes so that the base station can operate according to the above-described embodiment of the present disclosure. There may be a plurality of processors 2705, and the processor 2705 may perform a component control operation of the base station by executing a program stored in the memory.
  • a computer-readable storage medium storing one or more programs (software modules) may be provided.
  • One or more programs stored in a computer-readable storage medium are configured to be executable by one or more processors in an electronic device (device).
  • the one or more programs include instructions for causing the electronic device to execute methods according to embodiments described in the claims or specification of the present disclosure.
  • These programs include random access memory, non-volatile memory including flash memory, read only memory (ROM), and electrically erasable programmable ROM.
  • EEPROM Electrically Erasable Programmable Read Only Memory
  • magnetic disc storage device Compact Disc-ROM (CD-ROM), Digital Versatile Discs (DVDs), or other types of It may be stored in an optical storage device or a magnetic cassette. Alternatively, it may be stored in a memory composed of a combination of some or all of them. In addition, a plurality of configuration memories may be included.
  • the program is accessed through a communication network such as Internet, Intranet, Local Area Network (LAN), Wide LAN (WLAN), or Storage Area Network (SAN), or a combination of these. It may be stored in an (access) attachable storage device. Such a storage device may access a device performing an embodiment of the present disclosure through an external port. In addition, a separate storage device on the communication network may access a device performing an embodiment of the present disclosure.
  • a communication network such as Internet, Intranet, Local Area Network (LAN), Wide LAN (WLAN), or Storage Area Network (SAN), or a combination of these. It may be stored in an (access) attachable storage device.
  • Such a storage device may access a device performing an embodiment of the present disclosure through an external port.
  • a separate storage device on the communication network may access a device performing an embodiment of the present disclosure.
  • the constituent elements included in the invention are expressed in the singular or plural according to the presented specific embodiments.
  • the singular or plural expression is selected appropriately for the situation presented for convenience of description, and the present disclosure is not limited to the singular or plural constituent elements, and even constituent elements expressed in plural are composed of the singular or in the singular. Even the expressed constituent elements may be composed of pluralities.
  • each of the above embodiments may be combined and operated as necessary.
  • parts of one embodiment of the present disclosure and another embodiment may be combined with each other to operate a base station and a terminal.
  • parts of the first and second embodiments of the present disclosure may be combined with each other to operate a base station and a terminal.
  • the above embodiments have been presented based on the FDD LTE system, other systems such as a TDD LTE system, a 5G or NR system may be implemented with other modifications based on the technical idea of the embodiment.
  • the method of the present invention may be implemented by combining some or all of the contents included in each embodiment within a range not impairing the essence of the present invention.

Landscapes

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

Abstract

La présente invention concerne une technique de communication et un système associé qui permettent de combiner un système de communication 5G avec une technologie IdO pour prendre en charge une transmission de données supérieure à celle d'un système 4G. La présente invention peut être appliquée à des services intelligents (par exemple, une maison intelligente, un immeuble intelligent, une ville intelligente, une voiture intelligente ou une voiture connectée, des soins de santé, l'éducation numérique, la vente au détail, la sécurité et les services liés à la sécurité, etc.) en fonction de la technologie de communication 5G et de la technologie liée à l'IdO. La présente invention concerne un procédé et un appareil de transmission en liaison montante pour une pluralité de points d'émission-réception (TRPs).
PCT/KR2020/012516 2019-09-18 2020-09-16 Procédé et appareil de répétition d'une transmission en liaison montante pour communication coopérative en réseau WO2021054726A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20864484.9A EP4016910A4 (fr) 2019-09-18 2020-09-16 Procédé et appareil de répétition d'une transmission en liaison montante pour communication coopérative en réseau
US17/761,584 US20220353698A1 (en) 2019-09-18 2020-09-16 Method and apparatus for repeating uplink transmission for network cooperative communication

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR1020190115029A KR102688462B1 (ko) 2019-09-18 2019-09-18 네트워크 협력 통신을 위한 상향링크 반복 전송 방법 및 장치
KR10-2019-0115029 2019-09-18

Publications (1)

Publication Number Publication Date
WO2021054726A1 true WO2021054726A1 (fr) 2021-03-25

Family

ID=74883263

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2020/012516 WO2021054726A1 (fr) 2019-09-18 2020-09-16 Procédé et appareil de répétition d'une transmission en liaison montante pour communication coopérative en réseau

Country Status (4)

Country Link
US (1) US20220353698A1 (fr)
EP (1) EP4016910A4 (fr)
KR (1) KR102688462B1 (fr)
WO (1) WO2021054726A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022212860A1 (fr) * 2021-04-01 2022-10-06 Qualcomm Incorporated Indication de capacité pour des transmissions de canal physique partagé de liaison montante (pusch) sur la base ou non d'un livre de codes
WO2023177167A1 (fr) * 2022-03-15 2023-09-21 엘지전자 주식회사 Procédé et appareil pour effectuer une émission et une réception en liaison montante dans un système de communication sans fil
WO2023212008A1 (fr) * 2022-04-26 2023-11-02 Interdigital Patent Holdings, Inc. Procédé et appareil pour l'amélioration des srs à trp multiples dans la tdd

Families Citing this family (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11271626B2 (en) * 2018-12-06 2022-03-08 Samsung Electronics Co., Ltd. Full power uplink transmission for advanced wireless communication systems
EP3697013A1 (fr) * 2019-02-14 2020-08-19 Panasonic Intellectual Property Corporation of America Équipement utilisateur et système pour effectuer des opérations d'émission et de réception
US11831438B2 (en) * 2019-04-09 2023-11-28 Samsung Electronics Co., Ltd Method and apparatus for transmission and reception of HARQ-ACK feedback in wireless communication system
US11910430B2 (en) * 2019-10-07 2024-02-20 Qualcomm Incorporated Collision resolution for channel state information reporting on a physical uplink control channel
WO2021080394A1 (fr) * 2019-10-25 2021-04-29 엘지전자 주식회사 Procédé d'émission et de réception de canal de commande de liaison montante physique dans un système de communication sans fil, et appareil associé
EP3820051A1 (fr) * 2019-11-07 2021-05-12 Comcast Cable Communications LLC Répétition de transmission pour communication sans fil
EP4059276A4 (fr) * 2019-11-15 2023-07-26 Lenovo (Beijing) Limited Transmission de commande de contrôle de puissance
WO2021156107A1 (fr) * 2020-02-03 2021-08-12 Sony Group Corporation Procédés et dispositifs de communication pour la transmission de signaux de liaison montante en fonction de priorités
CN113271681B (zh) * 2020-02-17 2023-04-07 维沃移动通信有限公司 Pusch传输方法、终端及网络设备
JP2023524309A (ja) * 2020-05-11 2023-06-09 鴻穎創新有限公司 マルチ送信／受信点動作のための方法及びユーザ機器
US11871410B2 (en) * 2020-05-12 2024-01-09 Qualcomm Incorporated Joint shared channel timing allocation in downlink control information
WO2022016349A1 (fr) * 2020-07-21 2022-01-27 Zte Corporation Solution de signalisation pour diversité de faisceau rapide
WO2022031024A1 (fr) * 2020-08-05 2022-02-10 Samsung Electronics Co., Ltd. Procédé et dispositif pour transmission en liaison montante
US12022469B2 (en) * 2020-10-02 2024-06-25 Apple Inc. PUCCH repetition to increase the reliability of PUCCH transmission
US11901982B2 (en) * 2020-10-09 2024-02-13 Qualcomm Incorporated Uplink spatial filter and precoder for joint channel estimation across physical uplink shared channels
US11824803B2 (en) * 2021-03-25 2023-11-21 Telefonaktiebolaget Lm Ericsson (Publ) Phase tracking reference signaling for a wireless communication network
US20240243881A1 (en) * 2021-05-12 2024-07-18 Lg Electronics Inc. Method for transmitting and receiving pucch in wireless communication system and device therefor
WO2022250404A1 (fr) * 2021-05-25 2022-12-01 엘지전자 주식회사 Procédé pour une transmission/réception de pusch dans un système de communication sans fil, et dispositif associé
US11985597B2 (en) * 2021-08-05 2024-05-14 Qualcomm Incorporated Techniques for aperiodic discontinuous reception mode communications
US12041000B2 (en) 2021-08-05 2024-07-16 Qualcomm Incorporated Techniques for communicating data channel transmissions

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20180122818A (ko) * 2017-05-04 2018-11-14 삼성전자주식회사 무선 통신 시스템에서 상향 제어 채널 전송 방법 및 장치

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018128376A1 (fr) * 2017-01-05 2018-07-12 엘지전자(주) Procédé de transmission/de réception d'un canal de commande de liaison montante dans un système de communication sans fil, et dispositif associé
CN110224802B (zh) * 2018-09-28 2021-05-04 华为技术有限公司 一种通信方法、装置、存储介质及处理装置
CN110972251B (zh) * 2018-09-28 2021-10-22 华为技术有限公司 信号传输方法、相关设备及系统
WO2020250404A1 (fr) * 2019-06-13 2020-12-17 株式会社Ｎｔｔドコモ Terminal et procédé de communication sans fil
EP3986040A4 (fr) * 2019-06-13 2023-01-11 Ntt Docomo, Inc. Terminal et procédé de communication sans fil
WO2020250403A1 (fr) * 2019-06-13 2020-12-17 株式会社Ｎｔｔドコモ Terminal et procédé de communication sans fil
US12058624B2 (en) * 2019-06-21 2024-08-06 Ntt Docomo, Inc. Terminal and radio communication method

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20180122818A (ko) * 2017-05-04 2018-11-14 삼성전자주식회사 무선 통신 시스템에서 상향 제어 채널 전송 방법 및 장치

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
CATT: "Considerations on multi-TRP/panel transmission", 3GPP DRAFT; R1-1908602, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Prague, CZ; 20190826 - 20190830, 17 August 2019 (2019-08-17), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051765210 *
NTT DOCOMO, INC: "Enhancements on multi-TRP/panel transmission", 3GPP DRAFT; R1-1909201, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Prague, CZ; 20190826 - 20190830, 17 August 2019 (2019-08-17), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051765806 *
QUALCOMM INCORPORATED: "Multi-TRP Enhancements", 3GPP DRAFT; R1-1909272 MULTI-TRP ENHANCEMENTS, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Prague, Czech Republic; 20190826 - 20190830, 17 August 2019 (2019-08-17), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051765877 *
See also references of EP4016910A4 *
SHARP: "Discussion on multi-TRP/panel techniques for URLLC", 3GPP DRAFT; R1-1909105_MTRP, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Prague, CZ; 20190826 - 20190830, 16 August 2019 (2019-08-16), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051765708 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022212860A1 (fr) * 2021-04-01 2022-10-06 Qualcomm Incorporated Indication de capacité pour des transmissions de canal physique partagé de liaison montante (pusch) sur la base ou non d'un livre de codes
WO2023177167A1 (fr) * 2022-03-15 2023-09-21 엘지전자 주식회사 Procédé et appareil pour effectuer une émission et une réception en liaison montante dans un système de communication sans fil
WO2023212008A1 (fr) * 2022-04-26 2023-11-02 Interdigital Patent Holdings, Inc. Procédé et appareil pour l'amélioration des srs à trp multiples dans la tdd

Also Published As

Publication number Publication date
US20220353698A1 (en) 2022-11-03
KR102688462B1 (ko) 2024-07-26
KR20210033370A (ko) 2021-03-26
EP4016910A4 (fr) 2022-10-19
EP4016910A1 (fr) 2022-06-22

Similar Documents

Publication Publication Date Title
WO2021054726A1 (fr) Procédé et appareil de répétition d'une transmission en liaison montante pour communication coopérative en réseau
WO2021034052A1 (fr) Appareil et procédé de transmission d'informations de commande de liaison montante dans une communication collaborative de réseau
WO2021162510A1 (fr) Procédé et dispositif de transmission répétitive d'informations de commande de liaison montante pour une communication collaborative de réseau
WO2021101285A1 (fr) Procédé et dispositif permettant de mesurer un signal d'interférence dans un système de communication sans fil
WO2021141444A1 (fr) Procédé et appareil d'émission ou de réception de signal de référence dans un système de communication sans fil
WO2018143740A1 (fr) Procédé pour transmettre des informations de commande de liaison montante dans un système de communication sans fil et appareil le permettant
WO2018030783A1 (fr) Procédé et dispositif de transmission de canal dans un système de communication cellulaire sans fil
WO2022086259A1 (fr) Procédé et appareil pour la transmission et la réception répétitives de données en liaison montante pour la communication coopérative dans un réseau
WO2021107564A1 (fr) Procédé et appareil pour la configuration d'un faisceau par défaut pour la communication coopérative en réseau
WO2021158087A1 (fr) Procédé et appareil de transmission d'informations de commande pour une communication collaborative en réseau
WO2021133121A1 (fr) Procédé et appareil pour la transmission répétée de données de transmission en liaison montante pour une communication coopérative en réseau
WO2018021881A1 (fr) Procédé et appareil de remise d'informations d'état de canal dans un système de communication mobile
WO2022025628A1 (fr) Procédé et dispositif pour émettre/recevoir des informations de commande dans un système de communication coopératif sans fil
WO2021221428A1 (fr) Procédé et appareil de sondage dans un système de communication sans fil
WO2022225328A1 (fr) Procédé et dispositif de transmission répétée d'informations de commande de liaison descendante lors de la réalisation d'une communication collaborative de réseau
WO2022146082A1 (fr) Procédé et appareil pour déterminer un temps de traitement d'un ue dans un système de communication sans fil
WO2022154589A1 (fr) Procédé et dispositif de transmission ou de réception de rétroaction harq-ack pour une communication coopérative de réseau
WO2023132579A1 (fr) Procédé et appareil de transmission et de réception répétitives tenant compte du temps d'application de faisceau dans un système de communication sans fil
WO2021066536A1 (fr) Procédé et appareil de transmission de données pour la communication sans fil
WO2023075526A1 (fr) Procédé et appareil pour une planification de canaux partagés physiques multiples dans des systèmes de communication sans fil
WO2021201554A1 (fr) Procédé et dispositif de transmission et de réception de signal de référence dans un système de communication sans fil
WO2022260498A1 (fr) Procédé et dispositif de transmission et de réception d'informations de commande de liaison descendante et de données dans un système de communication sans fil
WO2023153864A1 (fr) Procédé et dispositif de transmission de harq-ack dans un système de communication sans fil
WO2022154458A1 (fr) Procédé et appareil pour transmettre/recevoir une rétroaction harq-ack pour une communication collaborative de réseau
WO2022260471A1 (fr) Procédé et appareil de transmission et de réception de données dans une communication coopérative en réseau

Legal Events

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

Ref document number: 20864484

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020864484

Country of ref document: EP

Effective date: 20220317