WO2022086169A1 - Procédé et appareil de gestion de faisceau pour la communication coopérative cellule-à-cellule dans un système de communication sans fil - Google Patents

Procédé et appareil de gestion de faisceau pour la communication coopérative cellule-à-cellule dans un système de communication sans fil Download PDF

Info

Publication number
WO2022086169A1
WO2022086169A1 PCT/KR2021/014704 KR2021014704W WO2022086169A1 WO 2022086169 A1 WO2022086169 A1 WO 2022086169A1 KR 2021014704 W KR2021014704 W KR 2021014704W WO 2022086169 A1 WO2022086169 A1 WO 2022086169A1
Authority
WO
WIPO (PCT)
Prior art keywords
cell
control
message
trp
pdcch
Prior art date
Application number
PCT/KR2021/014704
Other languages
English (en)
Korean (ko)
Inventor
정의창
윤수하
노훈동
박진현
Original Assignee
삼성전자 주식회사
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 삼성전자 주식회사 filed Critical 삼성전자 주식회사
Publication of WO2022086169A1 publication Critical patent/WO2022086169A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/022—Site diversity; Macro-diversity
    • H04B7/024—Co-operative use of antennas of several sites, e.g. in co-ordinated multipoint or co-operative multiple-input multiple-output [MIMO] systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/0408—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas using two or more beams, i.e. beam diversity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0613—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission
    • H04B7/0615—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal
    • H04B7/0617—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal for beam forming
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0686—Hybrid systems, i.e. switching and simultaneous transmission
    • H04B7/0695—Hybrid systems, i.e. switching and simultaneous transmission using beam selection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/08—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the receiving station
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/08—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the receiving station
    • H04B7/0868—Hybrid systems, i.e. switching and combining
    • H04B7/088—Hybrid systems, i.e. switching and combining using beam selection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • 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

Definitions

  • the present disclosure relates to a wireless communication system, and more particularly, to cell-to-cell cooperative communication using a plurality of cells.
  • the 5G communication system or the pre-5G communication system is called a system after the 4G network (Beyond 4G Network) communication system or the LTE system after (Post LTE).
  • the 5G communication system is being considered for implementation in a very high frequency (mmWave) band (eg, such as a 60 gigabyte (60 GHz) band).
  • mmWave very high frequency
  • FD-MIMO Full Dimensional MIMO
  • array antenna analog beam-forming, and large scale antenna technologies are being discussed.
  • cloud radio access network cloud radio access network: cloud RAN
  • ultra-dense network ultra-dense network
  • D2D Device to Device communication
  • wireless backhaul moving network, cooperative communication, Coordinated Multi-Points (CoMP), and interference cancellation Technology development is underway.
  • CoMP Coordinated Multi-Points
  • ACM advanced coding modulation
  • FQAM Hybrid FSK and QAM Modulation
  • SWSC Small Cell Superposition Coding
  • advanced access technologies such as Filter Bank Multi Carrier (FBMC), NOMA (non orthogonal multiple access), and sparse code multiple access (SCMA) are being developed.
  • FBMC Filter Bank Multi Carrier
  • NOMA non orthogonal multiple access
  • SCMA sparse code multiple access
  • IoT Internet of Things
  • IoE Internet of Everything
  • M2M Machine Type Communication
  • MTC Machine Type Communication
  • IoT an intelligent IT (Internet Technology) service that collects and analyzes data generated from connected objects and creates new values in human life can be provided.
  • IoT is a field of smart home, smart building, smart city, smart car or connected car, smart grid, health care, smart home appliance, advanced medical service, etc. can be applied to
  • 5G communication technology is implemented by techniques such as beam forming, MIMO, and array antenna.
  • cloud radio access network cloud RAN
  • CoMP Coordinatd multi-point
  • CoMP is a technology that reduces inter-cell interference and increases the throughput of the UE at the cell boundary by enabling neighboring cells to cooperate with each other so that not only the serving cell but also other cells can communicate with the same UE.
  • the present disclosure provides a plurality of transmission reception point (TRP) (hereinafter, Multiple TRP)-based CoMP (eg, NC-JT (non- We propose various techniques for coherent joint transmission). Specifically, a signaling method for instructing a PDCCH beam change or update operation of each TRP in multiple scenarios of a multi-cell group including different cells is proposed. In addition, a method of instructing a PDCCH transmission beam change or update operation of each TRP for two or more different cells (serving cell, non-serving cell) with one signaling is proposed.
  • TRP transmission reception point
  • NC-JT non-JT
  • an inter-cell multi-transmission reception point (multi-TRP) operation receiving a setting message related to; receiving a control message from a node of a first cell related to the inter-cell multi-TRP operation; checking a change in a beam through which a physical downlink control channel (PDCCH) is transmitted from a node of a second cell related to the inter-cell multi-TRP operation based on the configuration message and the control message; and receiving the PDCCH from the node of the second cell through the changed beam based on the confirmation result.
  • PDCH physical downlink control channel
  • an inter-cell multi-transmission reception point (multi-TRP) operation Transmitting a configuration message related to (operation) to the terminal; and transmitting a control message to the terminal through a node of the first cell related to the inter-cell multi-TRP operation, Physical downlink from the node of the second cell related to the inter-cell multi-TRP operation is characterized in that it is based on configuration information included in the configuration message and control information included in the control message.
  • PDCCH physical downlink control channel
  • a transceiver in a terminal of a wireless communication system, a transceiver; and controlling the transceiver to receive a configuration message related to an inter-cell multi-transmission reception point (multi-TRP) operation, and a first cell related to the inter-cell multi-TRP operation controls the transceiver to receive a control message from a node of Downlink control channel (PDCCH) includes a control unit that controls to confirm a change in the transmitted beam, and controls the transceiver to receive the PDCCH from the node of the second cell through the changed beam based on the result of the confirmation characterized in that
  • PDCCH Downlink control channel
  • a transceiver in a base station of a wireless communication system, a transceiver; and controlling the transceiver to transmit a configuration message related to an inter-cell multi-transmission reception point (multi-TRP) operation to the terminal, and a first related to the inter-cell multi-TRP operation a control unit for controlling the transceiver to transmit a control message to the terminal through a node of one cell;
  • the change of the beam through which the control channel (PDCCH) is transmitted is characterized in that it is based on configuration information included in the configuration message and control information included in the control message.
  • the UE in various scenarios of a multi-cell group including different cells, the UE effectively determines the change of the PDCCH transmission beam and updates the link with the changed beam, so that the beam management is more efficient. can operate
  • FIG. 1 is a diagram illustrating a basic structure of a time-frequency domain, which is a radio resource domain in which data or a control channel is transmitted in a wireless communication system according to an embodiment of the present disclosure.
  • FIG. 2 is a diagram illustrating a frame, subframe, and slot structure in a 5G system.
  • FIG. 3 is a diagram for explaining a setting of a bandwidth portion in a wireless communication system according to an embodiment of the present disclosure.
  • FIG. 4 is a diagram illustrating a method of dynamically changing a setting for a bandwidth portion according to an embodiment of the present disclosure.
  • Control Resource Set Control Resource Set, CORESET
  • FIG. 6 is a diagram illustrating a procedure for reporting UE capability according to an embodiment of the present disclosure.
  • FIG. 7 is a diagram for explaining the configuration of a cooperative communication antenna port according to an embodiment of the present disclosure.
  • 8A is a diagram illustrating a scenario of configuring Multi-TRP according to an embodiment of the present disclosure.
  • 8B is a diagram illustrating a scenario of configuring Multi-TRP according to an embodiment of the present disclosure.
  • 8C is a diagram illustrating a scenario of configuring Multi-TRP according to an embodiment of the present disclosure.
  • 8D is a diagram illustrating a scenario of configuring Multi-TRP according to an embodiment of the present disclosure.
  • FIG. 9 is a diagram illustrating a CORESETPoolIndex setting method of M-TRP based on Multi-DCI according to an embodiment of the present disclosure.
  • FIG. 10 is a diagram illustrating a method of setting CORESETPoolIndex according to an embodiment of the present disclosure.
  • FIG. 11 is a diagram illustrating a method of setting CORESETPoolIndex according to an embodiment of the present disclosure.
  • FIG. 12 is a diagram illustrating a method of setting CORESETPoolIndex according to an embodiment of the present disclosure.
  • FIG. 13 is a flowchart illustrating a process in which a terminal and a base station transmit and receive signals for a multi-TRP operation according to an embodiment of the present disclosure.
  • 14A is a diagram illustrating a beam management procedure according to an embodiment.
  • 14B is a diagram illustrating a beam management procedure according to an embodiment.
  • 15 is a diagram illustrating a MAC CE-based beam indication method according to an embodiment of the present disclosure.
  • 16 is a diagram illustrating a MAC CE format for MAC CE-based beam indication according to an embodiment.
  • 17 is a flowchart illustrating an operation of instructing an intra-cell beam change according to an embodiment.
  • 18A is a diagram illustrating a MAC CE format according to a first embodiment of the present disclosure.
  • 18B is a diagram illustrating a MAC CE format according to a first embodiment of the present disclosure.
  • 18C is a diagram illustrating a MAC CE format according to a first embodiment of the present disclosure.
  • 18D is a diagram illustrating a MAC CE format according to a first embodiment of the present disclosure.
  • 19 is a flowchart illustrating a method of instructing an inter-cell beam change according to the first embodiment of the present disclosure.
  • 20A is a diagram illustrating a MAC CE format according to a second embodiment of the present disclosure.
  • 20B is a diagram illustrating a MAC CE format according to a second embodiment of the present disclosure.
  • 20C is a diagram illustrating a MAC CE format according to a second embodiment of the present disclosure.
  • 20D is a diagram illustrating a MAC CE format according to a second embodiment of the present disclosure.
  • 21 is a flowchart illustrating a method of simultaneously instructing to change beams of a first cell and a second cell through one control message according to a second embodiment of the present disclosure.
  • 22 is a flowchart illustrating an operation of a terminal according to the first embodiment of the present disclosure.
  • FIG. 23 is a flowchart illustrating an operation of a terminal according to a second embodiment of the present disclosure.
  • 24 is a flowchart illustrating an operation of a base station according to an embodiment of the present disclosure.
  • 25 is a diagram illustrating the structure of a terminal according to an embodiment of the present invention.
  • 26 is a diagram illustrating a structure of a base station according to an embodiment of the present invention.
  • each block of the flowchart diagrams and combinations of the flowchart diagrams may be performed by computer program instructions.
  • These computer program instructions may be embodied in a processor of a general purpose computer, special purpose computer, or other programmable data processing equipment, such that the instructions performed by the processor of the computer or other programmable data processing equipment are not described in the flowchart block(s). It creates a means to perform functions.
  • These computer program instructions may also be stored in a computer-usable or computer-readable memory that may direct a computer or other programmable data processing equipment to implement a function in a particular manner, and thus the computer-usable or computer-readable memory.
  • the instructions stored in the flow chart block(s) may also be possible for the instructions stored in the flow chart block(s) to produce an article of manufacture containing instruction means for performing the function described in the flowchart block(s).
  • the computer program instructions may also be mounted on a computer or other programmable data processing equipment, such that a series of operational steps are performed on the computer or other programmable data processing equipment to create a computer-executed process to create a computer or other programmable data processing equipment. It may also be possible that instructions for performing the processing equipment provide steps for performing the functions described in the flowchart block(s).
  • each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s). It should also be noted that in some alternative implementations it is also possible for the functions recited in blocks to occur out of order. For example, two blocks shown one after another may in fact be performed substantially simultaneously, or it may be possible that the blocks are sometimes performed in a reverse order according to a corresponding function.
  • ' ⁇ unit' used in this embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and ' ⁇ unit' performs certain roles do.
  • '-part' is not limited to software or hardware.
  • ' ⁇ ' may be configured to reside on an addressable storage medium or may be configured to refresh one or more processors.
  • ' ⁇ part' refers to components such as software components, object-oriented software components, class components, and task components, and processes, functions, properties, and programs. Includes procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables.
  • components and ' ⁇ units' may be combined into a smaller number of components and ' ⁇ units' or further separated into additional components and ' ⁇ units'.
  • components and ' ⁇ units' may be implemented to play one or more CPUs in a device or secure multimedia card.
  • ' ⁇ 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 gNode B, eNode B, Node B, a base station (BS), a radio access unit, a base station controller, or a node on a network.
  • the terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function.
  • UE user equipment
  • MS mobile station
  • a cellular phone a smart phone
  • a computer or a multimedia system capable of performing a communication function.
  • a description will be given of a technique for a terminal to receive broadcast information from a base station in a wireless communication system.
  • the present disclosure relates to a communication technique that converges a 5 th generation (5G) communication system for supporting a higher data rate after the 4 th generation (4G) system with Internet of Things (IoT) technology, and a system thereof.
  • the present disclosure provides intelligent services (eg, smart home, smart building, smart city, smart car or connected car, healthcare, digital education, retail business, security and safety-related services, etc.) based on 5G communication technology and IoT-related technology. ) can be applied to
  • Terms referring to, terms referring to messages, terms referring to components of an apparatus, 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.
  • 3GPP LTE 3rd generation partnership project long term evolution
  • present invention is not limited by the terms and names, and may be equally applied to systems conforming to other standards.
  • a wireless communication system for example, 3GPP's HSPA (High Speed Packet Access), LTE (Long Term Evolution or E-UTRA (Evolved Universal Terrestrial Radio Access)), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2 HRPD (High Rate Packet Data), UMB (Ultra Mobile Broadband), and IEEE 802.16e, such as communication standards such as broadband wireless broadband wireless providing high-speed, high-quality packet data service It is evolving into a communication system.
  • HSPA High Speed Packet Access
  • LTE-A Long Term Evolution-A
  • LTE-Pro LTE-Pro
  • 3GPP2 HRPD High Rate Packet Data
  • UMB Ultra Mobile Broadband
  • IEEE 802.16e such as communication standards such as broadband wireless broadband wireless providing high-speed, high-quality packet data service It is evolving into a communication system.
  • Uplink refers to a radio link in which a UE (User Equipment) or MS (Mobile Station) transmits data or control signals to a base station (eNode B, or base station (BS)). It means a wireless link that transmits data or control signals.
  • the multiple access method as described above divides the data or control information of each user by allocating and operating the time-frequency resources for each user to transmit data or control information so that they do not overlap each other, that is, orthogonality is established. .
  • the 5G communication system must be able to freely reflect various requirements such as users and service providers, so services that satisfy various requirements must be supported.
  • Services considered for the 5G communication system include Enhanced Mobile BroadBand (eMBB), Massive Machine Type Communication (mMTC), and Ultra Reliability Low Latency Communication (URLLC). etc.
  • the eMBB aims to provide a data transfer rate that is more improved than the data transfer rate supported by existing LTE, LTE-A, or LTE-Pro.
  • the eMBB should be able to provide a maximum data rate of 20 Gbps in the downlink and a maximum data rate of 10 Gbps in the uplink from the viewpoint of one base station.
  • it is necessary to provide an increased user perceived data rate of the terminal.
  • transmission/reception technology including a more advanced multi-input multi-output (MIMO) transmission technology.
  • MIMO multi-input multi-output
  • mMTC is being considered to support application services such as the Internet of Things (IoT) in the 5G communication system.
  • IoT Internet of Things
  • mMTC may require large-scale terminal access support, improved terminal coverage, improved battery life, and reduced terminal cost within a cell. Since the Internet of Things is attached to various sensors and various devices to provide communication functions, it must be able to support a large number of terminals (eg, 1,000,000 terminals/km2) within a cell.
  • a terminal supporting mMTC is highly likely to be located in a shaded area that a cell cannot cover, 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 should 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.
  • URLLC as a cellular-based wireless communication service used for a specific purpose (mission-critical), remote control for a robot or machine, industrial automation
  • a service used in an unmaned aerial vehicle, remote health care, emergency alert, etc. it is necessary to provide communication that provides ultra-low latency and ultra-reliability.
  • a service supporting URLLC must satisfy an air interface latency of less than 0.5 milliseconds, and at the same time has a requirement of a packet error rate of 10-5 or less. Therefore, for a service supporting URLLC, the 5G system must provide a smaller transmit time interval (TTI) than other services, and at the same time, a design requirement for allocating a wide resource in a frequency band is required.
  • TTI transmit time interval
  • the aforementioned mMTC, URLLC, and eMBB are only examples of different service types, and the service types to which the present disclosure is applied are not limited to the above-described examples.
  • each service considered in the above-mentioned 5G communication system should be provided by convergence with each other based on one framework. That is, for efficient resource management and control, it is preferable that each service is integrated and controlled and transmitted as a single system rather than being operated independently.
  • the embodiment of the present invention will be described below using LTE, LTE-A, LTE Pro, or NR system as an example, 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 can be applied to other communication systems through some modifications within the scope of the present invention as judged by a person having skilled technical knowledge.
  • Terms referring to, terms referring to messages, terms referring to components of an apparatus, 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.
  • 3GPP LTE 3rd generation partnership project long term evolution
  • present invention is not limited by the terms and names, and may be equally applied to systems conforming to other standards.
  • FIG. 1 is a diagram illustrating a basic structure of a time-frequency domain, which is a radio resource domain in which data or a control channel is transmitted in a wireless communication system.
  • the horizontal axis represents the time domain and the vertical axis represents the frequency domain.
  • a basic unit of a resource in the time and frequency domain is a resource element (RE) (1-01) as 1 OFDM (orthogonal frequency division multiplexing) symbol (1-02) on the time axis and 1 subcarrier on the frequency axis It can be defined as (1-03).
  • RE resource element
  • 1-02 1 OFDM (orthogonal frequency division multiplexing) symbol
  • 1-03 resource block
  • RB resource block
  • FIG. 2 is a diagram illustrating a frame, subframe, and slot structure in a 5G system.
  • FIG. 2 an example of a structure of a frame 2-00, a subframe 2-01, and a slot 2-02 is illustrated in FIG. 2 .
  • One frame (2-00) may be defined as 10 ms.
  • One subframe (2-01) may be defined as 1 ms, and one frame (2-00) may consist of a total of 10 subframes (2-01).
  • One subframe (2-01) may consist of one or a plurality of slots (2-02, 2-03), and the number of slots (2-02, 2-03) per one subframe (2-01) may be different depending on the set value ⁇ (2-04, 2-05) for the subcarrier spacing.
  • each subcarrier spacing setting ⁇ and may be defined as in [Table 1] below.
  • one component carrier (CC) or serving cell may consist of up to 250 or more RBs. Therefore, when the terminal always receives the entire serving cell bandwidth (serving cell bandwidth) like LTE, the power consumption of the terminal may be extreme, and in order to solve this, the base station provides one or more bandwidth parts (BWP) to the terminal. It can be configured to support the UE to change the reception area within the cell.
  • BWP bandwidth parts
  • the base station may set 'initial BWP', which is the bandwidth of CORESET #0 (or common search space, CSS), to the terminal through the MIB. Thereafter, the base station sets the 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 future downlink control information (DCI). . Thereafter, the base station may indicate which band the terminal uses by announcing the BWP ID through DCI. If the terminal does not receive DCI in the currently allocated BWP for a specific time or longer, the terminal returns to the 'default BWP' and attempts to receive DCI.
  • 'initial BWP' which is the bandwidth of CORESET #0 (or common search space, CSS)
  • the base station sets the 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 future downlink control information (DCI).
  • DCI downlink control
  • FIG. 3 is a diagram for explaining a setting of a bandwidth portion in a wireless communication system according to an embodiment of the present disclosure.
  • the terminal bandwidth 3-00 may include two bandwidth portions, namely, a bandwidth portion #1(3-05) and a bandwidth portion #2(3-10).
  • the base station may set one or more bandwidth portions to the terminal, and may set information as shown in [Table 2] below for each bandwidth portion.
  • Setting information 1 Bandwidth in the bandwidth portion (number of PRBs that make up the bandwidth portion)
  • Setting information 2 The frequency position of the bandwidth part (such information may include an offset value compared to the reference point A, and the reference point may include, for example, the center frequency of a carrier wave, a synchronization signal, a synchronization signal raster, etc.)
  • Setting information 3 Numerology of the bandwidth part (eg, subcarrier spacing, CP (Cyclic Prefix) length, etc.) etc.
  • various parameters related to the bandwidth portion may be set in the terminal.
  • the above-described information may be transmitted by the base station to the terminal through higher layer signaling, for example, RRC signaling.
  • At least one bandwidth part among the set one or a plurality of bandwidth parts may be activated. Whether to activate the set bandwidth portion may be semi-statically transmitted from the base station to the terminal through RRC signaling, or may be dynamically transmitted through a MAC control element (MAC CE) or DCI.
  • MAC CE MAC control element
  • the setting of the bandwidth part supported by the above-described 5G communication system may 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 by setting the bandwidth portion. For example, in [Table 2], the frequency position of the bandwidth part (setting information 2) is set for the terminal, so that the terminal can transmit and receive data at a specific frequency position within the system bandwidth.
  • the base station may configure a plurality of bandwidth portions for the terminal. For example, in order to support both data transmission and reception using a subcarrier interval of 15 kHz and a subcarrier interval of 30 kHz to an arbitrary terminal, two bandwidth portions may be configured to use a subcarrier interval of 15 kHz and 30 kHz, respectively. Different bandwidth portions may be subjected to frequency division multiplexing (FDM), and when data is transmitted/received at a specific subcarrier interval, a bandwidth portion set for the corresponding subcarrier interval may be activated.
  • FDM frequency division multiplexing
  • the base station may configure a bandwidth portion having different sizes of bandwidths for the terminal. For example, when the terminal supports a very large bandwidth, for example, a bandwidth of 100 MHz and always transmits/receives data using the corresponding bandwidth, very large power consumption may be caused. 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 in which there is no traffic. Therefore, for the purpose of reducing power consumption of the terminal, the base station may set a relatively small bandwidth portion for the terminal, for example, a bandwidth portion of 20 MHz. In the absence of traffic, the UE may perform a monitoring operation in the 20 MHz bandwidth portion, and when data is generated, it may transmit/receive data using the 100 MHz bandwidth portion according to the instruction of the base station.
  • FIG. 4 is a diagram illustrating a method of dynamically changing a setting for a bandwidth portion according to an embodiment of the present disclosure.
  • the base station may set one or more bandwidth parts to the terminal, and as settings for each bandwidth part, the bandwidth of the bandwidth part, the frequency position of the bandwidth part, Information on the numerology of the bandwidth part may be informed to the terminal.
  • bandwidth portion #1 bandwidth portion #1
  • BWP#2, 4- 10 bandwidth portion #2
  • One or a plurality of bandwidth portions may be activated among the set bandwidths, and an example in which one bandwidth portion is activated may be considered in FIG. 4 .
  • the bandwidth part #1 (4-02) is activated among the set bandwidth parts, and the terminal controls the control region #1 ( 4-45) may monitor a Physical Downlink Control Channel (PDCCH), and may transmit/receive data 4-55 in bandwidth part #1 (4-05).
  • a control region in which the terminal receives the PDCCH may be different depending on which bandwidth portion among the configured bandwidth portions is activated, and accordingly, the bandwidth in which the terminal monitors the PDCCH may vary.
  • the base station may additionally transmit an indicator for changing the configuration of the bandwidth portion to the terminal.
  • changing the setting for the bandwidth portion may be considered the same as an operation of activating a specific bandwidth portion (eg, changing the activation from the bandwidth portion A to the bandwidth portion B).
  • the base station may transmit a configuration switching indicator to the terminal in a specific slot.
  • the terminal After receiving the configuration change indicator from the base station, the terminal may determine a bandwidth portion to be activated by applying the changed configuration according to the configuration change indicator from a specific time point.
  • the UE may perform monitoring for the PDCCH in the control region set in the activated bandwidth portion.
  • the base station instructs the terminal to change the activated bandwidth part from the existing bandwidth part #1 (4-05) to the bandwidth part #2 (4-10) (Configuration Switching Indication, 4-15) can be transmitted in slot #1 (4-30).
  • the terminal may activate the bandwidth part #2 (6-10) according to the content of the indicator.
  • a transition time (4-20) for changing the bandwidth portion may be required, and accordingly, a time point for changing and applying the active bandwidth portion may be determined.
  • 4 shows a case in which a transition time 4-20 of one slot is required after receiving the setting change indicator 4-15. In the transition time (4-20), data transmission/reception may not be performed (4-60). Accordingly, the bandwidth part #2 (4-10) is activated in the slot #2 (4-35), so that the control channel and data can be transmitted/received through the corresponding bandwidth part.
  • the base station may preset one or more bandwidth parts to the terminal as higher layer signaling (eg, RRC signaling), and the configuration change indicator 4-15 is activated in a way that is mapped with one of the bandwidth part settings preset by the base station. can be instructed.
  • an indicator of log 2 N bits may indicate by selecting one of N preset bandwidth parts.
  • [Table 3] below an example of indicating configuration information for a bandwidth portion using a 2-bit indicator is described.
  • Bandwidth Partial Settings 00 Bandwidth setting A set by upper layer signaling 01
  • Bandwidth setting B set with higher layer signaling 10
  • Bandwidth setting C set with higher layer signaling 11
  • Bandwidth setting D set by higher layer signaling
  • the configuration change indicator 4-15 for the bandwidth portion described in FIG. 4 is in the form of MAC (Medium Access Control) CE (Control Element) signaling or L1 signaling (eg, common DCI, group-common DCI, terminal-specific DCI) may be transmitted from the base station to the terminal.
  • MAC Medium Access Control
  • CE Control Element
  • L1 signaling eg, common DCI, group-common DCI, terminal-specific DCI
  • the configuration change indicator 4-15 for the bandwidth portion described in FIG. 4 from which point in time the bandwidth portion activation is applied may depend on the following. From which point in time the setting change is applied, it follows a predefined value (eg, it is applied from N ( ⁇ 1) slots after receiving the setting change indicator), or is set from the base station to the UE through higher layer signaling (eg RRC signaling), or , may be partially included in the contents of the setting change indicator 4-15 and transmitted. Alternatively, the timing at which the setting change is applied may be determined by a combination of the above-described methods. After receiving the configuration change indicator 4-15 for the bandwidth portion, the terminal may apply the changed configuration from the point in time obtained by the above-described method.
  • a predefined value eg, it is applied from N ( ⁇ 1) slots after receiving the setting change indicator
  • RRC signaling eg RRC signaling
  • Control Resource Set Control Resource Set, CORESET
  • control region #1 (5-01), control Area #2 (5-02)
  • the control regions 5-01 and 5-02 may be set in a specific frequency resource 5-03 within the entire terminal bandwidth portion 5-10 on the frequency axis.
  • the control regions 5-01 and 5-02 may be set with one or more OFDM symbols on the time axis, and may be defined by a control region length (Control Resource Set Duration, 5-04).
  • the control region #1 (5-01) is set to a control region length of two symbols
  • the control region #2 (5-02) is set to a control region length of one symbol.
  • the control region in the 5G system described above may be set by the base station to the terminal through higher layer signaling (eg, system information, master information block (MIB), radio resource control (RRC) signaling).
  • Setting the control region to the terminal means providing the terminal with information such as a control region identifier (Identity), a frequency position of the control region, and a symbol length of the control region.
  • information according to Table 4 may be included in the information for setting the control region to the terminal.
  • ControlResourceSet SEQUENCE ⁇ -- Corresponds to L1 parameter 'CORESET-ID' controlResourceSetId ControlResourceSetId, (Control area identifier (Identity)) frequencyDomainResources BIT STRING (SIZE (45)), (frequency axis resource allocation information) duration INTEGER (1..maxCoReSetDuration), (Time axis resource allocation information) cce-REG-MappingType CHOICE ⁇ (CCE-to-REG mapping method) interleaved SEQUENCE ⁇ reg-BundleSize ENUMERATED ⁇ n2, n3, n6 ⁇ , (REG bundle size) precoderGranularity ENUMERATED ⁇ sameAsREG-bundle, allContiguousRBs ⁇ , interleaverSize ENUMERATED ⁇ n2, n3, n6 ⁇ (interleaver size) shiftIndex INTEGER(0..maxNrofPhysicalResourceBlocks-1) OPT
  • tci-StatesPDCCH configuration information includes one or more synchronization signal (SS)/physical broadcast channel (PBCH) blocks in a quasi co-located (QCL) relationship with a demodulation reference signal (DMRS) transmitted in the corresponding control region.
  • block (referred to as an SSB or SS/PBCH block) index or CSI-RS (channel state information reference signal) index information may be included.
  • one or more different antenna ports may be associated with each other by QCL configuration as shown in Table 5 below.
  • QCL-Info :: SEQUENCE ⁇ cell ServCellIndex (Serving cell index to which QCL reference RS is transmitted) bwp-Id BWP-Id (bandwidth partial index over which QCL reference RS is transmitted) referenceSignal CHOICE ⁇ (indicator indicating one of CSI-RS or SS/PBCH block as QCL reference RS) csi-rs NZP-CSI-RS-ResourceId, ssb SSB-Index ⁇ , qcl-Type ENUMERATED ⁇ typeA, typeB, typeC, typeD ⁇ , (QCL type indicator) ... ⁇
  • the QCL setting can connect two different antenna ports in a relationship between a (QCL) target antenna port and a (QCL) reference antenna port, and the terminal can perform statistical characteristics (e.g., For example, all or part of the large scale parameters of the channel such as Doppler shift, Doppler spread, average delay, delay spread, average gain, spatial Rx (or Tx) parameters or the reception spatial filter coefficient or transmission spatial filter coefficient of the terminal) are set to the target antenna port. It can be applied (or assumed) upon reception.
  • statistical characteristics e.g., For example, all or part of the large scale parameters of the channel such as Doppler shift, Doppler spread, average delay, delay spread, average gain, spatial Rx (or Tx) parameters or the reception spatial filter coefficient or transmission spatial filter coefficient of the terminal
  • the target antenna port means an antenna port for transmitting a channel or signal set by upper layer setting including the QCL setting, or an antenna port for transmitting a channel or signal to which a TCI state indicating the QCL setting is applied.
  • the reference antenna port means an antenna port for transmitting a channel or signal indicated (specific) by a referenceSignal parameter in the QCL configuration.
  • the statistical characteristics of the channel defined by the QCL setting may be classified according to the QCL type as follows.
  • ⁇ 'QCL-TypeA' ⁇ Doppler shift, Doppler spread, average delay, delay spread ⁇
  • the types of QCL type are not limited to the above four types, but all possible combinations are not listed in order not to obscure the gist of the description.
  • the bandwidth and transmission period of the target antenna port are both sufficient compared to the reference antenna port (that is, the number of samples and the transmission band/time of the target antenna port in both the frequency axis and the time axis are the number of samples and transmission of the reference antenna port. More than band/time)
  • QCL-TypeB is a QCL type used when the bandwidth of the target antenna port is sufficient to measure measurable statistical characteristics on the frequency axis, that is, Doppler shift and Doppler spreads.
  • QCL-TypeC is a QCL type used when the bandwidth and transmission period of the target antenna port are insufficient to measure second-order statistics, that is, Doppler spread and delay spreads, so that only first-order statistics, that is, Doppler shift and average delay, can be referred to. .
  • QCL-TypeD is a QCL type set when spatial reception filter values used when receiving a reference antenna port can be used when receiving a target antenna port.
  • the base station prefferably set or instruct up to two QCL settings to one target antenna port through the TCI state setting as shown in Table 6 below.
  • TCI-State SEQUENCE ⁇ tci-StateId TCI-StateId, (TCI state indicator) qcl-Type1 QCL-Info, (Set the first QCL for the target antenna port to which the TCI state is applied) qcl-Type2 QCL-Info (Set the second QCL for the target antenna port to which the TCI state is applied) OPTIONAL, -- Need R ... ⁇
  • the first QCL setting may be set to one of QCL-TypeA, QCL-TypeB, and QCL-TypeC.
  • the settable QCL type is specified according to the types of the target antenna port and the reference antenna port and will be described in detail below.
  • the second QCL setting among the two QCL settings included in the one TCI state setting may be set to QCL-TypeD, and may be omitted in some cases.
  • FIG. 6 is a diagram illustrating a procedure for reporting UE capability according to an embodiment of the present disclosure.
  • the terminal may perform a procedure of reporting the capability supported by the terminal to the corresponding base station while connected to the serving base station.
  • this may be referred to as UE capability report.
  • the base station may transmit a UE capability inquiry message for requesting a capability report to the terminal in the connected state (610).
  • the UE capability inquiry message may include a UE capability request for each RAT type.
  • the request for each RAT type may include requested frequency band information.
  • the UE capability enquiry message may include a plurality of RAT types in one RRC message container.
  • a UE capability enquiry message including a request for each RAT type may be delivered to the UE multiple times. That is, the UE capability enquiry message is repeatedly transmitted a plurality of times, and the UE may configure and report a corresponding UE capability information message.
  • the base station may request UE capability for MR-DC including NR, LTE, and EN-DC.
  • the base station may transmit a UE capability inquiry message after the terminal is connected, and may also request a UE capability report under any conditions when the base station is needed.
  • the terminal may configure or acquire UE capability according to the RAT type and band information included in the UE capability enquiry message.
  • the UE capability may include information on whether the terminal supports the multi-TRP operation. Also, the UE Capability may include information on whether the UE supports multi-TRP operation for inter-cell. Accordingly, the UE capability may be referred to as a Multi-TRP related capability.
  • the terminal may transmit a UE capability information message including the UE capability to the base station (602).
  • the base station may then perform scheduling and transmission/reception management appropriate for the corresponding terminal based on the UE capability received from the terminal.
  • FIG. 7 is a diagram for explaining the configuration of a cooperative communication antenna port according to an embodiment of the present disclosure.
  • FIG. 7 an example of radio resource allocation for each transmission reception point (TRP) according to a joint transmission (JT) technique and a situation is illustrated.
  • FIG. 7 are diagrams illustrating coherent joint transmission (C-JT) supporting coherent precoding between each cell, TRP, and/or beam.
  • C-JT coherent joint transmission
  • TRP A (7-05) and TRP B (7-10) transmit the same data (PDSCH), and joint precoding can be performed in multiple TRPs.
  • This may mean that the same DMRS ports (eg, DMRS ports A and B in both TRPs) are transmitted from TRP A (7-05) and TRP B (7-10).
  • the terminal may receive one piece of DCI information for receiving one physical downlink shared channel (PDSCH) demodulated by the reference signal received through DMRS ports A and B.
  • PDSCH physical downlink shared channel
  • NC-JT non-coherent joint transmission
  • different PDSCHs may be transmitted in each cell, TRP, and/or beam, and individual precoding may be applied to each PDSCH.
  • This may mean that different DMRS ports (eg, DMRS port A in TRP A, DMRS port B in TRP B) are transmitted from TRP A (7-25) and TRP B (7-30).
  • the UE may receive two types of DCI information for receiving PDSCH A demodulated by DMRS port A and PDSCH B demodulated by another DMRS port B.
  • NC-JT which transmits data from two or more transmission points to one terminal at the same time
  • PDSCHs transmitted from two (or more) different transmission points are allocated through a single PDCCH, or two It is necessary to allocate PDSCHs transmitted from the above different transmission points.
  • the UE acquires a QCL (quasi co-location) connection relationship between each reference signal or channel based on L1/L2/L3 signaling, and through this, efficiently estimates large scale parameters of each reference signal or channel can do. If the transmission point of the reference signal or channel is different, since large scale parameters are difficult to share with each other, when performing cooperative transmission, the base station simultaneously informs the terminal of quasi co-location information for two or more transmission points. It is necessary to inform through two or more TCI states.
  • non-coherent cooperative transmission is supported through multiple PDCCHs, that is, when two or more PDCCHs allocate two or more PDSCHs to the same serving cell and the same bandwidth portion at the same time, two or more TCI states are each PDCCH It may be allocated to each PDSCH to DMRS ports, respectively.
  • the two or more TCI states are one It may be allocated to each PDSCH to DMRS ports through the PDCCH of .
  • the DMRS ports allocated to the terminal at a specific time are divided into a DMRS port group A transmitted from a transmission point A and a DMRS port group B transmitted from a transmission point B, two or more TCI states are respectively connected to the DMRS port group. and a channel can be estimated based on different QCL assumptions for each group.
  • different DMRS ports may be subjected to code division multiplexing (CDM), frequency division multiplexing (FDM), or time domain multiplexing (TDM) in order to increase channel measurement accuracy and reduce transmission burden at the same time.
  • CDM code division multiplexing
  • FDM frequency division multiplexing
  • TDM time domain multiplexing
  • CDM group when the DMRS ports used for CDM are collectively referred to as the CDM group, code-based multiplexing works well when the channel characteristics of each port are similar to the DMRS ports in the CDM group (that is, if the channel characteristics of each port are similar, OCC (orthogonal It may be important to ensure that DMRS ports existing in the same CDM group do not have different TCI states because they are distinguished by the cover code).
  • a node may mean a physical or logical node in a wireless communication system that transmits and receives data with a terminal through a specific cell.
  • the node may mean a transmission/reception point (hereinafter, TRP), a base station, an evolved node B (eNodeB or eNB), a next generation node B (gNodeB, or gNB), and the like.
  • the first node may mean TRP for transmitting and receiving data to and from the terminal through the first cell
  • the second node is physically separated or separated from the first node and is different from the first cell. It may mean TRP for transmitting and receiving data with the terminal through the second cell.
  • the operation of transmitting data through a plurality of TRPs as described above may be referred to as a multi-TRP (M-TRP) operation.
  • M-TRP multi-TRP
  • an operation of transmitting data through a plurality of cells in a plurality of TRPs as described above may be referred to as an inter cell multi-TRP operation.
  • the plurality of cells may mean each cell operated by a plurality of base stations, may mean a plurality of cells operated by one base station, or a combination thereof.
  • the present disclosure proposes a method for the inter cell multi TRP operation.
  • an inter-cell can be configured through inter-cell configuration information, and the inter-cell configuration information includes a unit and method for configuring an inter-cell, a unit and method for grouping cells, and a method for identifying the cell.
  • the inter-cell configuration information includes a unit and method for configuring an inter-cell, a unit and method for grouping cells, and a method for identifying the cell.
  • At least one of information eg, cell id, serving cell id, physical cell id
  • the embodiment of the present disclosure is not limited thereto, and the above-described information may not be included in the inter-cell configuration information, and any information related to the inter-cell may be included.
  • the inter-cell configuration information may include SSB pattern (ssb-PositionsInBurst, ssb-periodicityServingCell), sub-carrier spacing (subcarrier Spacing), frequency (absoluteFrequencySSB), and the like.
  • the inter-cell configuration information refers to cell configuration information for inter-cell cooperative transmission, and may also be referred to as configuration information, cell configuration information, or the like.
  • the present disclosure may be applied to inter-cell multi-TRP cooperative transmission through serving cells and inter-cell multi-TRP cooperative transmission through serving cells and non-serving cells.
  • 8A to 8D are diagrams illustrating scenarios of configuring multi-TRP according to an embodiment of the present disclosure.
  • FIGS. 8A to 8D illustrate scenarios that can be used for cooperative communication between base stations (inter-gNB) or between cells within a base station (intra-gNB).
  • inter-gNB base stations
  • intra-gNB intra-gNB
  • the back-haul and front-haul of FIGS. 8A to 8D may be applied to both an ideal back-haul/front-haul and a non-ideal back-haul/front-haul.
  • 8A to 8D may be applied between co-channels or different channels, and may also be applied to different cell IDs or the same cell ID.
  • FIG. 8A is a diagram illustrating an example of a serving cell and PCI configuration according to a carrier aggregation (CA) operation.
  • CA carrier aggregation
  • the base station can set different serving cells (ServCellConfigCommon) for each cell in a CA situation in which the frequency resources occupied by each cell are different (that is, the frequency band value FrequencyInfoDL indicated by DownlinkConfigCommon in each serving cell setting is different), so you can set different indexes (ServCellIndex) for each cell and map different PCI values.
  • FIG. 8B illustrates an intra-cell multi-TRP operation in which one or more TRPs operate within one serving cell configuration.
  • the base station since the base station transmits the settings for channels and signals transmitted in different TRPs in one serving cell configuration, several TRPs operate based on one serving cell index (ServingCellIndex or ServCellIndex).
  • ServingCellIndex a serving cell index
  • a cell may be configured using the same physical cell Id.
  • frequency-side eg, frequency/channel/band
  • it is much more resource efficient to use all allocated resources in one CC so a method of classifying cells in the form of cell IDs rather than classifying cells in terms of time and frequency resources may be used during cell planning.
  • the inter-Cell for a new M-TRP is configured based on new cell ID information or the cell-related information (or may be referred to as cooperative cell configuration information, cooperative cell-related information, etc.) method can be considered. That is, according to an embodiment of the present disclosure, when a plurality of TRPs perform inter-cell cooperative transmission, a method of setting this to the UE (that is, notifying the UE that cells performing inter-cell cooperative transmission are related to other TRPs) method) is described. Meanwhile, a method of using a cell ID will be described below as an example, but the present disclosure is not limited thereto, and a method of using a physical cell ID, a serving cell index, or another identifier may also be considered.
  • a method of configuring a cell or a cell group according to an embodiment of the present disclosure will be described.
  • a method of setting a cell or a cell group may be configured differently according to each scenario and case.
  • FIG. 8c shows an inter-cell M-TRP operation in which the CA-framework is extended.
  • the base station can be configured by including settings for channels and signals transmitted in different TRPs in different serving cell settings.
  • each TRP has an independent serving cell configuration
  • the frequency band values FrequencyInfoDLs indicated by DownlinkConfigCommon in each serving cell configuration may indicate at least some overlapping bands.
  • PCI physical cell ID
  • a method for setting cooperative transmission in a plurality of TRPs using cell configuration information is as follows.
  • Method 1 Referring to Table 7 below, a method of setting information indicating activation or deactivation of intercell multi-TRP information (IntercellForMultiTRP) in SpCell configuration information (SpCellConfig) may be considered.
  • IntercellForMultiTRP indicates activation or deactivation with 1-bit information or indicates activation when IntercellForMultiTRP information is included and deactivation when IntercellForMultiTRP information is not included.
  • the UE may determine that the sCell or SPCell in which the IntercellForMultiTRP is set to enable (or includes IntercellForMultiTRP) is set as the cooperating set to perform cooperative transmission.
  • SpCellConfig SEQUENCE ⁇ servCellIndex ServCellIndex OPTIONAL, -- Cond SCG reconfigurationWithSync ReconfigurationWithSync OPTIONAL, -- Cond ReconfWithSync rlf-TimersAndConstants SetupRelease ⁇ RLF-TimersAndConstants ⁇ OPTIONAL, -- Need M rlmInSyncOutOfSyncThreshold ENUMERATED ⁇ n1 ⁇ OPTIONAL, -- Need S spCellConfigDedicated ServingCellConfig OPTIONAL, -- Need M IntercellForMultiTRP ENUMERATED ⁇ enable, disable ⁇ OPTIONAL, -- Need M ... ⁇ Example (omitting ScellConfig)
  • SpCellConfig has been described as an example, the present disclosure is not limited thereto, and the same may be applied to SCell configuration information (SCellConfig).
  • Method 2 Meanwhile, in consideration of another embodiment, a method of configuring the IntercellForMultiTRP using ServingCellConfig as shown in Table 8 may be considered.
  • IntercellForMultiTRP indicates activation or deactivation with 1-bit information, or indicates activation when IntercellForMultiTRP information is included, and instructs deactivation when IntercellForMultiTRP information is not included. Accordingly, when IntercellForMultiTRP is set to enable in the ServingCellConfig (or when IntercellForMultiTRP is included in the ServingCellConfig), the UE can determine that the SCells or SPCells corresponding to the ServingCellConfig perform cooperative transmission.
  • ServingCellConfig SEQUENCE ⁇ tdd-UL-DL-ConfigurationDedicated TDD-UL-DL-ConfigDedicated OPTIONAL, -- Cond TDD initialDownlinkBWP BWP-DownlinkDedicated OPTIONAL, -- Need M downlinkBWP-ToReleaseList SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Id OPTIONAL, -- Need N downlinkBWP-ToAddModList SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Downlink OPTIONAL, -- Need N IntercellForMultiTRP ENUMERATED ⁇ enable, disable ⁇ OPTIONAL, -- Need M
  • cooperative cell-related information may be transmitted using higher layer signaling (RRC) for inter-cell-based multiple TRP transmission.
  • RRC higher layer signaling
  • Cooperative cell-related information may be included in CellGroupConfig as shown in Table 9 below, for example, at least one information of inter-cell group information for Multi-TRP (hereinafter, InterCellGroupForMultiTRP) and TRP group ID (hereinafter, InterCellGroupForMultiTRPGroupID). may be added to the CellGroupConfig.
  • the cooperative cell-related information may be configured by being included in the aforementioned SpCellConfig, SCellConfig, ServingCellConfig, and the like.
  • CellGroupConfig :: SEQUENCE ⁇ cellGroupId CellGroupId, rlc-BearerToAddModList SEQUENCE (SIZE(1..maxLC-ID)) OF RLC-BearerConfig rlc-BearerToReleaseList SEQUENCE (SIZE(1..maxLC-ID)) OF LogicalChannelIdentity mac-CellGroupConfig MAC-CellGroupConfig OPTIONAL, -- Need M physicalCellGroupConfig PhysicalCellGroupConfig OPTIONAL, -- Need M spCellConfig SpCellConfig OPTIONAL, -- Need M sCellToAddModList SEQUENCE (SIZE (1..maxNrofSCells)) OF sCellToReleaseList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellIndex ..., dormancySCellGroups DormancySCellGroups OPTIONAL, -- Need N InterCellGroup
  • the InterCellGroupForMultiTRP may be included in CellGroupConfig, and the InterCellGroupForMultiTRP may be composed of InterCellGroupForMultiTRPGroupID and InterCellGroupForMultiTRPSCellList. Accordingly, SCells included in InterCellGroupForMultiTRPSCellList are grouped by InterCellGroupForMultiTRPGroupID, and the SCells or SPCells may be used for cooperative transmission.
  • InterCellGroupForMultiTRPGroupID At least one of 0 to 5 may be selected for InterCellGroupForMultiTRPGroupID.
  • the InterCellGroupForMultiTRPGroupID may be set to a value of 5 or more.
  • InterCellGroupForMultiTRPGroupID may be included in CellGroupConfig.
  • SCells corresponding to SCellConfig included in CellGroupConfig may have the same TRP Group ID. Therefore, a cell or cell groups having the same TRP Group ID may be used for cooperative transmission. In this way, the cooperating set of the inter-cell-based M-TR can be set by using or combining the two methods, respectively.
  • cooperative cell-related information may be transmitted using higher layer signaling (RRC) for inter-cell-based Multiple TRP transmission, and a set constituting a CellGroup (physical ID) #X, physical Id #Y) or (servicellId #X, servicellId #Y) can be defined in a list or table form.
  • RRC higher layer signaling
  • a set of physical cell IDs or a set of servingcellIDs may be configured in CellGroup, and the set may be used for cooperative transmission.
  • the set of the physical cell ID or the set of servingcellID may be configured through SpCellConfig, SCellConfig, ServingCellConfig, etc. in addition to CellGroupConfig.
  • FIG. 8D shows an inter-cell M-TRP operation based on a non-CA framework.
  • settings for channels and signals transmitted in different TRPs may be included in one serving cell configuration.
  • the UE may determine that the Inter-Cell M-TRP operation is performed.
  • a separate serving cell index (eg, ServCellIndex) may not be set for the non-serving cell.
  • ServCellIndex eg., ServCellIndex
  • the following describes a method of configuring the PCI of the TRP for transmitting and receiving a signal to the base station through a non-serving cell to the terminal. Through this, the UE can check whether the inter-cell M-TRP is configured.
  • Method 1 The method of setting the SSB based on the additional PCI as the QCL reference antenna port by adding a parameter that can connect additional PCI values other than the first PCI value mapped to the existing ServCellIndex to the TCI setting or QCL setting will be used can
  • parameters for referring to other PCIs in addition to the PCI allocated to the corresponding serving cell may be added to the QCL setting.
  • QCL-Info :: SEQUENCE ⁇ cell ServCellIndex (Serving cell index to which QCL reference RS is transmitted) bwp-Id BWP-Id (bandwidth partial index over which QCL reference RS is transmitted) referenceSignal CHOICE ⁇ (indicator indicating one of CSI-RS or SS/PBCH block as QCL reference RS) csi-rs NZP-CSI-RS-ResourceId, ssb SSB-Index ⁇ , qcl-Type ENUMERATED ⁇ typeA, typeB, typeC, typeD ⁇ , (QCL type indicator) physCellId PhysCellId ... ⁇
  • Second method Alternatively, as shown in Table 11 below, a parameter for referring to PCI other than the PCI allocated to the corresponding serving cell may be added to the TCI setting.
  • TCI-State SEQUENCE ⁇ tci-StateId TCI-StateId, (TCI state indicator) qcl-Type1 QCL-Info, (Set the first QCL for the target antenna port to which the TCI state is applied) qcl-Type2 QCL-Info (Set the second QCL for the target antenna port to which the TCI state is applied) OPTIONAL, -- Need R physCellId PhysCellId ... ⁇
  • TCI-State SEQUENCE ⁇ tci-StateId TCI-StateId, (TCI state indicator) qcl-Type1 QCL-Info, (Set the first QCL for the target antenna port to which the TCI state is applied) qcl-Type2 QCL-Info (Set the second QCL for the target antenna port to which the TCI state is applied) OPTIONAL, -- Need R physCellId1 PhysCellId physCellId2 PhysCellId ... ⁇
  • the base station can use a black cell list or a white cell list in the measurement configuration (eg, MeasConfig or MeasObject configuration).
  • the base station can set a list of PCI values connected to the black list (blackCellsToAddModList) and white list (whiteCellsToAddModList) of the PCI values that the terminal considers when measuring the SSB through MeasObject configuration.
  • MeasObjectNR SEQUENCE ⁇ ssbFrequency ARFCN-ValueNR OPTIONAL, -- Cond SSBorAssociatedSSB ssbSubcarrierSpacing SubcarrierSpacing OPTIONAL, -- Cond SSBorAssociatedSSB smtc1 SSB-MTC OPTIONAL, -- Cond SSBorAssociatedSSB smtc2 SSB-MTC2 OPTIONAL, -- Cond IntraFreqConnected refFreqCSI-RS ARFCN-ValueNR OPTIONAL, -- Cond CSI-RS referenceSignalConfig ReferenceSignalConfig, absThreshSS-BlocksConsolidation ThresholdNR OPTIONAL, -- Need R absThreshCSI-RS-Consolidation ThresholdNR OPTIONAL, -- Need R nrofSS-BlocksToAverage INTEGER (2..maxNrofSS-BlocksToAverage) OPTIONAL,
  • PCI #2 is included in whiteCellsToAddModList in MeasObjectNR (or not included in blackCellsToAddModList), but PCI #3 is not included in whiteCellsToAddModList in MeasObjectNR (or included in blackCellsToAddModList), the terminal has PCI #2 You can check that it has been set. Therefore, the UE has an obligation to measure SSB for PCI #2, but has no obligation to measure SSB for PCI #3. Therefore, the UE can apply the QCL reference antenna port setting to the SSB linked to PCI #2, but may not expect the QCL reference antenna port setting to the SSB linked to PCI #3.
  • the terminal does not expect the QCL reference antenna port setting means “if it is set in this way, ignore the corresponding setting” or “the terminal operation for the setting is not defined, so random processing is performed”
  • Various applications are possible, such as “allowed to do so” or “guaranteeing that the base station does not set this setting”.
  • the following method may be used for the UE to check whether the inter-cell M-TRP operation is configured in FIG. 8D .
  • At least one or more BWPs may be configured for TRP 1 and TRP 2, and cell-related higher layer signaling or parameters may be configured.
  • a plurality of TRP(s) may be set so that the BWP corresponding to the inter-cell M-TRP is active among the BWPs supported by each TRP. Therefore, a plurality of BWPs may be active for M-TRP transmission.
  • BWP-0 of TRP 1 is associated with CORESET 0, 1, 2, 3, 4
  • BWP-1 of TRP 2 is CORESET 0, 1, 2, 3, It can be set to be associated with 4.
  • the terminal may determine that the M-TRP operation is set. Accordingly, the terminal may perform the M-TRP operation according to the ControlResourceSet setting. That is, the terminal may transmit or receive a signal through a plurality of TRPs.
  • the above-described measurement configuration information may be used to determine whether BWP-1 of TRP 2 related to the non-serving cell is in the activation state.
  • BWP-1 of the TPR 2 may be activated by including at least a portion of the BWP-1 in the information.
  • the measurement setting information may include frequency information (eg, ARFCN-ValueNR in freqbandindicatorNR or ssbFrequency), and when it is set to include a part of the frequency information (BWP-1) of TRP 2 in the frequency information , BWP-1 of the TRP 2 may be activated.
  • the measurement configuration information may include an activated BWP or BWP ID to be used for multi-TRP inter-cell transmission, through which multi-TRP inter-cell transmission may be performed.
  • the measurement configuration information received from the serving cell may include information such as a measurement object (servingCellMO) and measurement Id of the serving cell.
  • the measurement configuration information received from the serving cell may include a measurement object related to a neighboring cell.
  • the measurement object may include at least one of information such as BWP ID and cell ID. Accordingly, the terminal may determine that BWP 0 of TRP 1 and BWP 1 of TRP 2 are activated according to the measurement object, and may perform an M-TRP operation.
  • information on CellsToAddModList may be included in the measurement object, and BWP 1 of TRP 2 may be activated by including a PCI list in the information.
  • the base station transmits the BWP ID for performing multi-TRP inter-cell cooperative transmission to the terminal through configuration information such as QCL information (QCL info), or transmits the BWP ID for BWP 1 of TRP 2 to the terminal.
  • QCL info QCL information
  • the following method may be used for the UE to check whether the inter-cell M-TRP operation is configured in FIG. 8D .
  • At least one BWP may be set or activated for TRP 1 and TRP 2, and a method of newly setting the CORESET Index set in the terminal may be considered.
  • a plurality of TRP(s) may each set one or more BWPs, where the same BWP-Id of each TRP for inter-cell M-TRP transmission may be set to be associated with a continuous (consecutive number) CORESET Index.
  • the UE may be configured such that the same BWP-Id is active from TRP 1 and TRP 2.
  • BWP-1 of TRP 1 may be set to be associated with CORESETs 0, 1, and 2, and BWP-1 of TRP 2 may be set to be associated with CORESETs 3 and 4.
  • the maximum number of COREESET Index is determined to be a value of 5 or more (eg 10)
  • BWP-1 of TRP 1 is associated with CORESET 0-4
  • BWP-1 of TRP 2 is associated with CORESET 5-9. It can be set to be
  • IntercellDownlinkBWP-Id may be added as follows to separately set the active BWP Id. Accordingly, when the BWP indicated by the IntercellDownlinkBWP-Id is activated as described above, the UE may perform the inter-cell M-TRP operation in the corresponding BWP. In case of using this method, there is an advantage of performing non-CA framework operation while maintaining the current standard in which only one BWP is active in inter-cell-based multi-TRP transmission.
  • ServingCellConfig SEQUENCE ⁇ tdd-UL-DL-ConfigurationDedicated TDD-UL-DL-ConfigDedicated OPTIONAL, -- Cond TDD initialDownlinkBWP BWP-DownlinkDedicated OPTIONAL, -- Need M downlinkBWP-ToReleaseList SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Id OPTIONAL, -- Need N downlinkBWP-ToAddModList SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Downlink OPTIONAL, -- Need N firstActiveDownlinkBWP-Id BWP-Id IntercellDownlinkBWP-Id BWP-Id // Assign BWP Id ... ⁇
  • Rel-16 up to five CORESETs can be set within one BWP, and at this time, a set of CORESETs capable of performing multi-TRP transmission can be set to the same CORESETPoolIndex.
  • CORESETPoolIndex it is necessary to set CORESETPoolIndex for each of a plurality of TRPs corresponding to inter-cells in Rel-17.
  • the base station can set five or more CORESETs within one BWP, and can extend and use a plurality of existing CORESETPoolIndex for inter-cell-based multi-TRP transmission, and use new information (eg, CORESETPoolIndex-rel17 or CORESETPoolIndexForIntercell) can be used.
  • new information eg, CORESETPoolIndex-rel17 or CORESETPoolIndexForIntercell
  • FIG. 9 is a diagram illustrating a CORESETPoolIndex setting method of M-TRP based on Multi-DCI according to an embodiment of the present disclosure.
  • the UE may decode DCI by monitoring a plurality of PDCCHs included in CORESET in which CORESETPoolIndex is set to the same value in at least one BWP.
  • the UE can expect to receive fully/partially/non-overlapped PDSCHs scheduled by the DCI.
  • the UE may monitor CORESET #X (902) of TRP 1 and CORESET Y (903) of TRP #2 set to the same CORESETPoolIndex (901) in slot #0 (904), respectively. Accordingly, the UE may receive data in PDSCH #2 905 and PDSCH #1 906 based on the DCI received through CORESET #X and CORESET #Y.
  • CORESETPoolIndex may be set in the UE, and the UE may perform M-TRP operation through CORESET having the same CORESETPoolIndex. For example, if CORESETPoolIndex 0 includes CORESETs 1 and 2 and CORESETPoolIndex 1 includes CORESETs 3 and 4, the UE may perform an M-TRP operation through CORESETs 1 and 2, and CORESET 3 and 4 through the M-TRP operation.
  • a first method for setting CORESETPoolIndex will be described.
  • the UE when CORESETPoolIndex is set for the serving cell, the UE can expect that the same CORESETPoolIndex is set for the inter-cell (non-serving cell). That is, the same CORESETPoolIndex may be applied even in the inter-cell. In this case, it can be determined that the inter-cell (non-serving cell) is set implicitly without a separate CORESETPoolIndex setting.
  • CORESETPoolIndex 0 for the cell for TRP 1 is set to include CORESETs 1 and 2
  • CORESETPoolIndex 1 is set to include CORESET 3 and 4
  • the UE CORESETPoolIndex 0 for the cell for TPR2 is also CORESET 1
  • CORESETPoolIndex 1 can be determined to include CORESETs 3 and 4.
  • FIG. 10 is a diagram illustrating a second method of setting CORESETPoolIndex according to an embodiment of the present disclosure.
  • the number of CORESETPoolIndex settings can be fixed, and the present disclosure describes a case where, for example, it is set to two.
  • the embodiment of the present disclosure is not limited thereto, and the number of CORESETPoolIndex settings may be changed.
  • the base station may set CORESETPoolIndex to 0 or 1 for each PCI. At this time, there may be two or more CORESETs included in CORESETPoolIndex 0 or 1.
  • the base station may set at least one CORESET to be configured as a pool to have the same index for each PCI in order to set the CORESETPoolIndex between inter-cells.
  • At least two CORESETs may be included in CORESETPoolIndex, and CORESETs having the same CORESETPoolIndex may be used for inter-cell cooperative transmission.
  • the base station may set CORESET 1 for TRP 1 and CORESET 1 for TRP 2 as inter-cell CORESETPoolIndex 0 for a specific terminal.
  • the PDCCH for multi-TRP transmission may be monitored in the inter-cell using the same CORESETIndex.
  • CORESET 1 for TRP 1 and CORESET 2 for TRP 1 may be set to CORESETPoolIndex 0 (1010) for TRP 1
  • CORESET 1 for TRP 2 and CORESET 3 for TRP 2 may be set to TRP 2
  • CORESETPoolIndex may be set to 0 (1020). Therefore, CORESETPoolIndex 0 for TRP 1 and TRP 2 may be used for PDCCH monitoring for inter-cell multi-TRP transmission.
  • CORESET 3 for TRP 1 CORESET 4 for TRP 1 may be set to CORESETPoolIndex 1 (1011) for TRP 1
  • CORESET 3 for TRP 2 CORESET 4 for TRP 2 may be set to CORESETPoolIndex 1 (1021) for TRP 2 can be set to Therefore
  • CORESETPoolIndex 1 for TRP 1 and TRP 2 may be used for PDCCH monitoring for inter-cell multi-TRP transmission.
  • the UE may perform PDCCH monitoring for multi-TRP transmission by checking only CORESETPoolIndex regardless of PCI. In this way, the base station can set/determine so that the total number of CORESETPoolIndex is fixed and the terminal monitors all pools having the same index.
  • CORESETPoolIndex information for setting CORESET ID and CORESETPoolIndex in the second method may be shown in Table 15 below.
  • the case where there are two CORESETPoolIndex will be described as an example, but the number of CORESETPoolIndex may be increased, and accordingly, the number of bits of the corresponding information may also be increased.
  • the UE may operate assuming that CORESETPoolIndex is 0 if there is no separate value setting in the RRC setting.
  • ControlResourceSet SEQUENCE ⁇ controlResourceSetId ControlResourceSetId, OPTIONAL, -- Need S ... [[ coresetPoolIndex-r17 INTEGER (0..1) // fixed 2 OPTIONAL, -- Need R controlResourceSetId-r17 ControlResourceSetId-r16 OPTIONAL -- Need S ]] ⁇
  • FIG. 11 is a diagram illustrating a third method of setting CORESETPoolIndex according to an embodiment of the present disclosure.
  • the number of CORESETPoolIndex settings can be fixed, and the present disclosure describes a case where, for example, it is set to two.
  • the embodiment of the present disclosure is not limited thereto, and the number of CORESETPoolIndex settings may be changed.
  • the base station may set CORESETPoolIndex to 0 or 1 for each PCI. In this case, there may be two or more CORESETs included in CORESETPoolIndex 0 or 1.
  • the base station may set at least one CORESET to be configured as a pool to have the same index for each PCI in order to set the CORESETPoolIndex between inter-cells.
  • CORESETs having different PCIs may be set to be included in one CORESETPoolIndex for inter-cell cooperative transmission.
  • the base station may set CORESET 1 for TRP 1 and CORESET 2 for TRP 2 as inter-cell CORESETPoolIndex 0 1110 for a specific terminal.
  • the base station may set CORESET 4 for TRP 1 and CORESET 3 for TRP 2 as CORESETPoolIndex 1 (1120) between inter-cells.
  • the terminal does not support inter-cell-based M-TRP transmission for CORESET indexes that are not set as CORESETPoolIndex (CORESET 2 for TRP 1, CORESET 3 for TRP 2, CORESET 1 for TRP 2, CORESET 4 for TRP2) in this figure. can be judged as In this way, the base station can set/determine so that the total number of CORESETPoolIndex is fixed and the terminal monitors all pools having the same index.
  • the CORESET setting according to the present embodiment may be configured as shown in Table 16 below.
  • the CORESETPoolIndex-r17 field may be set to ENUMERATED ⁇ n0, n1 ⁇
  • the CORESETPoolIndex-r17 field is set to ENUMERATED ⁇ n0, n1, n3 ⁇ can be set.
  • CORESETPoolIndex may be set by dividing intra-cell and inter-cell.
  • the CORESETPoolIndex-r17 field may be set to ENUMERATED ⁇ n0, n1, n2 ⁇ , and n0, n1 may be set for intra-cell and n2 may be set for inter-cell.
  • CORESETPoolIndex-r17 field may also be set to information such as n4, n5, and the like.
  • CORESETPoolIndex when configured by distinguishing between intra-cell and inter-cell, information on intra-cell and information on inter-cell may be determined according to a setting of a base station or a predetermined rule.
  • ControlResourceSet SEQUENCE ⁇ controlResourceSetId ControlResourceSetId, OPTIONAL, -- Need S ... [[ coresetPoolIndex-r17 ENUMERATED ⁇ n0, n1, n2 ⁇ OPTIONAL, -- Need R controlResourceSetId-r17 ControlResourceSetId-r16 OPTIONAL -- Need S ]]
  • CORESETPoolIndex may be set for intra-cell use, and CORESETPoolIndex CORESETPoolIndexFor-IntercellId (new parameter)) for inter-cell may be newly defined.
  • CORESETPoolIndexForIntercellId may be set to include CORESETPoolIndex including the CORESET Id of each cell.
  • CORESETPoolIndexForIntercellId 0 can be set to include CORESETPoolIndex 0 or CORESETPoolIndex 0 and CORESETPoolIndex 1 to be included.
  • CORESETPoolIndexForIntercellId may be directly set to include the CORESET Id of each cell.
  • the CORESETPoolIndexForIntercellId setting may be configured as shown in Table 17 below.
  • ControlResourceSet SEQUENCE ⁇ controlResourceSetId ControlResourceSetId, OPTIONAL, -- Need S ... [[ // coresetPoolIndex-r17 INTEGER (0..1) // 2 fixed OPTIONAL, -- Need R coresetPoolIndexForIntercellId-r17 INTEGER (0..2*maxIntercell) // N Cells controlResourceSetId-r17 ControlResourceSetId-r17 OPTIONAL -- Need S ]] ⁇
  • FIG. 12 is a diagram illustrating a fifth method of setting CORESETPoolIndex according to an embodiment of the present disclosure.
  • the fifth method describes a method of extending the number of CORESETPoolIndex settings.
  • the base station may expand the number of pools considering the entire inter-cell by the number of PCIs. For example, it is assumed that only five CORESETs that can be included in one BWP are set, and when N PCIs are set, 2 x N CORESETPoolIndex can be set.
  • CORESETPoolIndex 0 (1210) may include CORESET 1 for TRP 1 and CORESET 2 for TRP 1
  • CORESETPoolIndex 1 (1220) is CORESET 3 for TRP 1
  • CORESET 3 for TRP 2 may include
  • CORESETPoolIndex 2 (1230) may include CORESET 4 for TRP 1
  • CORESETPoolIndex 3 (1240) may include CORESET 1 for TRP 2
  • it may be set to include CORESET 2 for TRP 2.
  • the CORESETPoolIndex mapping may be set similarly.
  • the UE may perform PDCCH monitoring for the Mult-TRP operation according to the set CORESETPoolIndex.
  • FIG. 13 is a flowchart illustrating a process in which a terminal and a base station transmit and receive signals for a multi-TRP operation according to an embodiment of the present disclosure.
  • the terminal 1300 may report (transmit) the terminal capability to the base station 1310 in step S1305 .
  • the terminal 1300 may receive the terminal capability report request from the base station 1310 and report the terminal capability accordingly.
  • the terminal capability may include information on terminal capability for each RAT type.
  • the terminal capability information may include information on whether the terminal supports the multi-TRP operation.
  • the UE capability may include information on whether the terminal 1300 supports the multi-TRP operation for inter-cell.
  • not all of the above information should be included in the terminal capability information, and some information may be omitted or other information may be added.
  • the base station 1310 may not request the terminal capability report, and step S1305 may be omitted.
  • the base station 1310 may transmit a multi-TRP related configuration message (eg, an RRC message) to the terminal 1300 in step S1310 .
  • the Multi-TRP related configuration information may include at least one of cell related information (or cooperative cell related information), BWP related information, and CORESETPoolIndex related information for an inter cell-based M-TRP operation. Specific details are the same as described above. Accordingly, the above-described cell setting method, BWP related method, CORESETPoolIndex setting method, etc. can be applied to this embodiment.
  • the terminal 1300 and the base station 1310 may perform an inter-cell multi-TRP operation in step S1315 .
  • the base station 1310 may indicate to the terminal 1300 that the inter-cell Multi-TRP operation is configured through the cell-related information.
  • the terminal 1300 may confirm that the inter-cell Multi-TRP operation is configured through the cell-related information.
  • the terminal 1300 may receive the CORESETPoolIndex information transmitted by the base station 1310 and check information on CORESET to be monitored for a plurality of TRPs.
  • the base station 1310 may transmit DCI in the CORESET for the plurality of TRPs.
  • the terminal 1300 may monitor the PDCCH in the CORESET for the plurality of TRPs and acquire DCI.
  • the terminal 1300 may receive data through the PDSCH scheduled by the DCI.
  • the base station 1310 may transmit data through the PDSCH.
  • 14A to 14B are diagrams illustrating a beam management procedure according to an embodiment.
  • NR or 5G
  • One of the main functions in NR is to support a large number of controllable antenna elements for both transmit and receive.
  • a large number of antenna elements may be mainly used for beamforming for the purpose of extending coverage.
  • All NR channels and signals, including those used for control and synchronization, are designed to support beamforming.
  • NR can support analog beamforming as well as digital precoding and beamforming for implementation flexibility.
  • analog beamforming that converts a signal from digital to analog and then forms a beam may be used.
  • analog beamforming a receive beam or a transmit beam may be formed in one direction at a given point in time.
  • analog beamforming may require a process (beam sweeping) in which the same signal is repeated in a plurality of OFDM symbols but must be transmitted using different transmission beams. Since a signal can be transmitted with a high gain in any direction through the beam sweeping function, the signal can be transmitted through a narrow beam up to an intended entire coverage area.
  • the base station may indicate to the terminal information for selecting a beam through which the terminal receives data and control information.
  • Various signaling methods supporting such a beam management procedure may be considered.
  • the beam management aims to select and maintain a combination of the direction of the transmission beam on the transmission side and the direction of the reception beam on the reception side so that the channel gain is maximized. If the beam management is efficiently operated, data rate and throughput can be maximized.
  • the optimal beam pair may be a beam pair 1420 in which the direction of the downlink transmission beam of the base station 1410 and the direction of the downlink reception beam of the terminal 1400 directly coincide. there is.
  • the beam pair 1430 in the transmission beam direction and the reception beam direction along the reflection path may be an optimal beam pair. This can happen especially in high frequency bands where there is little diffraction at the edges of obstacles.
  • the base station 1410 and the terminal 1400 can determine an optimal beam pair even when the above-described direct path between the transmitting side and the receiving side is blocked.
  • FIG. 14A illustrates beamforming in the downlink direction
  • the optimal transmission/reception beam pair in the downlink direction may be the optimal beam pair in the uplink direction as well.
  • the optimal beam pair in the uplink direction may be the optimal beam pair in the downlink direction as well. In this case, it may be said that beam correspondence (or beam correspondence) is established for downlink and uplink.
  • initial beam establishment may refer to a procedure for establishing an initial beam pair.
  • the base station may transmit a synchronization signal block (SS/PBCH block, or SSB) corresponding to each beam using different downlink beams in an initial access process.
  • the UE may attempt random access to the BS by selecting one of a PRACH occasion (physical random access channel occasion) and a preamble corresponding to each beam.
  • the base station may check the downlink transmission beam for the terminal based on the received random access preamble.
  • SS/PBCH block synchronization signal block
  • the procedure for reconfirming the beam pair as described above may be referred to as a beam adjustment procedure.
  • the beam adjustment may include a downlink transmission side (eg, a base station) (downlink transmitter-side) beam adjustment and a downlink reception side (eg, a terminal) (downlink receiver-side) beam adjustment.
  • the reception beam of the terminal 1400 may be maintained and the transmission beam of the base station 1410 may be adjusted.
  • the base station 1410 may sequentially transmit signals using different downlink beams. In this way, the base station 1410 sequentially transmits signals using different beams may be referred to as beam sweeping.
  • the terminal 1400 may measure a reference signal (RS) corresponding to the different downlink beams while maintaining the reception beam 1450 .
  • the RS may be a channel state information reference signal (CSI-RS) or an SSB. Accordingly, the terminal 1400 may measure the quality of different downlink beams on the transmission side. Also, the terminal 1400 may report different measured beam qualities to the base station 1410 . According to the above process, the optimal beam 1440 of the downlink transmission side can be identified.
  • the base station 1410 maintains the downlink transmission beam 1460 and the terminal 1400 may adjust the downlink reception beam (or beam sweep).
  • the terminal 1400 may be configured with a set of downlink RSs.
  • the terminal 1400 may perform measurement on the RS by sequentially applying a reception beam to the configured RS.
  • the terminal 1400 may identify the optimal beam 1470 of the downlink reception side based on the measurement value.
  • 15 is a diagram illustrating a MAC CE-based beam indication method according to an embodiment of the present disclosure.
  • the NR supports beam indication (or beam indication).
  • the beam indication may mean indicating (or specifying) to the UE that the PDSCH or PDCCH is being transmitted in the same beam as the configured RS (CSI-RS or SSB). Alternatively, it may mean indicating (or specifying) that the PDSCH or PDCCH is transmitted using the same spatial filter as the configured RS.
  • transmitting or receiving the PDSCH may mean transmitting or receiving data through the PDSCH.
  • transmitting or receiving a PDCCH may mean transmitting or receiving a DCI through the PDCCH.
  • the PDCCH transmission beam may mean a transmission beam used by the base station to transmit the PDCCH to the terminal.
  • the beam indication may be made through downlink signaling using transmission configuration indicator state (TCI state) information.
  • TCI state information may include information on RS (CSI-RS or SSB).
  • the base station may inform the terminal of beam information related to downlink transmission (PDSCH or PDCCH transmission) through the TCI state information. For example, the UE may assume that the PDSCH or PDCCH is transmitted through the same beam as the downlink transmission beam through which the RS (CSI-RS or SSB) included in the TCI state information is transmitted.
  • the base station may configure N (eg, up to 128) TCI states to the terminal.
  • the N TCI states may be included in an information element (IE) (eg, PDSCH-Config) in a configuration message (eg, RRC message) transmitted from the base station to the terminal.
  • IE information element
  • M eg, up to 64
  • candidate TCI states used to indicate (or specify) a beam through which a PDCCH is transmitted among the N, through the configuration message.
  • Candidate TCI states used to indicate a beam through which the PDCCH is transmitted may be referred to as, for example, tci-StatesPDCCH.
  • each CORESET configuration information may include a list of candidate TCI states (eg, tci-StatesPDCCH-ToAddList).
  • Each CORESET setting information may include information according to Table 4 as described above.
  • a configuration for each TCI state in the list of candidate TCI states may be as shown in Table 18 below. The relationship between the QCL setting and the TCI state according to each TCI state setting is as described above.
  • TCI-State SEQUENCE ⁇ tci-StateId TCI-StateId, qcl-Type1 QCL-Info, qcl-Type2 QCL-Info OPTIONAL, -- Need R ...
  • ⁇ QCL-Info :: SEQUENCE ⁇ cell ServCellIndex OPTIONAL, -- Need R bwp-Id BWP-Id OPTIONAL, -- Cond CSI-RS-Indicated referenceSignal CHOICE ⁇ csi-rs NZP-CSI-RS-ResourceId, ssb SSB-Index ⁇ , qcl-Type ENUMERATED ⁇ typeA, typeB, typeC, typeD ⁇ , ...
  • NZP-CSI-RS-Resource SEQUENCE ⁇ nzp-CSI-RS-ResourceId NZP-CSI-RS-ResourceId, resourceMapping CSI-RS-ResourceMapping, powerControlOffset INTEGER (-8..15), powerControlOffsetSS ENUMERATED ⁇ db-3, db0, db3, db6 ⁇ OPTIONAL, -- Need R scramblingID ScramblingId, periodicityAndOffset CSI-ResourcePeriodicityAndOffset OPTIONAL, -- Cond PeriodicOrSemiPersistent qcl-InfoPeriodicCSI-RS TCI-StateId OPTIONAL, -- Cond Periodic ... ⁇ -- TAG-NZP-CSI-RS-RESOURCE-STOP -- ASN1STOP
  • the base station transmits the configuration information to the terminal through a configuration message, and the terminal may store it.
  • the configuration message may be a message including the above-described Multi-TRP related configuration information.
  • the base station may transmit a control message (eg, MAC CE) to the terminal to indicate (or specify) the changed beam.
  • a control message eg, MAC CE
  • the UE can confirm that the PDCCH is transmitted through the same beam as the RS (eg, CSI-RS or SSB) associated with the TCI state set for each CORESET (eg, the UE is the It can be assumed that the PDCCH is transmitted through a spatial filter such as RS).
  • indicating to the UE the beam through which the PDCCH is transmitted through the MAC CE message may be referred to as MAC CE based beam indication.
  • 16 is a diagram illustrating a MAC CE format for MAC CE-based beam indication according to an embodiment.
  • the MAC CE 1610 shown in FIG. 16 may include at least one of the following fields (filed).
  • - Serving Cell ID may indicate the identifier of the serving cell to which the corresponding MAC CE is applied.
  • - CORESET ID may indicate the identifier of the control resource set (control resource set, CORESET) indicated by the TCI state.
  • - TCI state ID may indicate the identifier of the TCI state included in the CORESET setting identified by the CORESET ID field.
  • the UE may receive the MAC CE 1610 and check a change in the beam through which the PDCCH is transmitted based thereon.
  • the UE can confirm that the cell indicated by the Serving Cell ID field 1611 is a cell to which the MAC CE 1610 is applied.
  • the UE can confirm that the PDCCH transmitted through the CORESET resource indicated by the CORESET ID field 1612 is transmitted through the same beam as the RS configured in association with the TCI state indicated by the TCI state ID field 1613 . Thereafter, the UE may receive the PDCCH through the changed beam.
  • 17 is a flowchart illustrating an operation of instructing an intra-cell beam change according to an embodiment.
  • the serving cell (or the node for the serving cell, hereinafter the same) 1710 may transmit a control message (eg, MAC CE) to the UE 1700 in step S1705 .
  • a control message eg, MAC CE
  • step S1710 the terminal 1700 may confirm a change in the beam through which the PDCCH is transmitted in the serving cell 1710 .
  • the terminal 1700 checks the change-related control message (eg, MAC CE) of the beam through which the PDCCH is transmitted, and a response message thereto may be transmitted to the serving cell 1710 (not shown).
  • the response message may be defined in MAC CE format.
  • the terminal 1700 includes a MAC subheader (subheader) including a logical channel ID (LCID) corresponding to the response message (MAC CE) and the MAC sub PDU including the response message (MAC CE) may be transmitted to the serving cell 1710 .
  • MAC subheader including a logical channel ID (LCID) corresponding to the response message (MAC CE)
  • MAC sub PDU including the response message (MAC CE) may be transmitted to the serving cell 1710 .
  • the terminal 1700 may perform a subsequent operation without transmitting the above response message.
  • the serving cell 1710 may transmit the PDCCH to the UE 1700 through the changed beam in step S1715 .
  • the terminal 1700 may receive the PDCCH through the changed beam.
  • the serving cell 1710 confirms that the control message (eg, MAC CE) has been successfully received by the terminal 1700 based on the response message, and transmits the PDCCH through the changed beam to the terminal (1700).
  • the terminal 1700 may receive the PDCCH through the changed beam.
  • the method may indicate only a beam change of one serving cell. Therefore, the present disclosure proposes a method of instructing a beam change of a cell other than a serving cell (non-serving cell) in an inter-cell Multi TRP operation in the following. In addition, we propose a method of simultaneously instructing the beam change of the serving cell and the non-serving cell.
  • a non-serving cell and a serving cell may be configured in association with each other in the RRC message.
  • the following method may be used as a method of establishing a non-serving cell and a serving cell in connection with each other.
  • this may be understood with reference to the methods proposed in the above-described FIGS. 8C to 8D and the description thereof.
  • a Physical Cell index (PCI) can be designated for non-serving cells.
  • the reason for configuring the PCI may be to inform the UE by classifying the TCI state setting of the non-serving cell for each PCI.
  • PCI PhysicalCellId
  • each PCI may be added to the QCL type setting in the TCI-State of the RRC setting.
  • CSI-RS-CellMobility it may be configured by adding a QCL type to the PCI configuration.
  • PCI#2 can be implicitly signaled through the setting of TCI state id.
  • 00: PCI #2, 01: PCI#7, 10: PCI#9, 11: PCI#20 can be set through separate indexing.
  • non-serving cells can be designated based on the serving cell index (ServCellIndex). Specifically, set it in the ServCellIndex format, use a separate additional index (eg, intercell Added Index 0, 1, 2, 3, 4, 5, 6, 7, 8, etc.), or group cells to create a separate ID. You can also specify
  • Method 3 Grouping of non-serving cells and serving cells can be indexed by setting a cell group based on PCI and serving cell index and designating a separate index for it.
  • Method 4 In RRC, a separate configuration may not be performed for a non-serving cell. In this case, it may not be possible to distinguish whether cells other than the Pcell configured in RRC are configured for CA purpose or operation for Multi-TRP for NC-JT purpose.
  • the first embodiment proposes a method of instructing a beam change of a non-serving cell in an inter-cell Multi TRP operation.
  • a serving cell may be simply referred to as a first cell, and a TRP operating the first cell may be referred to as a first TRP.
  • a non-serving cell may be simply referred to as a second cell, and a TRP operating the second cell may be referred to as a second TRP.
  • 18A to 18D are diagrams illustrating a MAC CE format according to a first embodiment of the present disclosure.
  • the base station or the terminal distinguishes the first cell from the second cell.
  • One way to do this is to use PCI.
  • the UE in order to change the configuration of the spatial domain of the beam through which the PDCCH is transmitted in the second TRP, the UE includes the TCI included in the RRC configuration (eg, ControlResourceSet, PDSCH-Config, NZP-CSI-RS-Resource, etc.) You can refer to -stateId.
  • the referenced TCI-stateID is as described above in Table 18. (QCL-info: set the RS of the source for QCL setting)
  • the MAC CE for indicating (or specifying) the change of the PDCCH beam is shown in FIG. 18a It may have a structure as shown in It goes without saying that the MAC CE below can be operated even if it is not set in RRC as in method 3.
  • a separate serving cell ID eg, ServCellIndex
  • the MAC CE 1810 may include a serving cell ID field 1811 , a CORESET ID field 1812 , and a TCI state ID field 1813 (when a resource created for the purpose of setting the TCI states ID is reused).
  • MAC CE (1820) is Serving cell ID field (1821), CORESET Pool index field (1822) (can be omitted), CORESET ID field (1823), TCI state ID field (1824) (for inter-cell Multi TRP operation) It may include an extended (extended TCI state ID field) capable of additionally setting 128 TCI state IDs.
  • each of the Serving Cell ID field 1811 may have a length of 5 bits
  • the CORESET ID field 1812 may have a length of 4 bits
  • the TCI state ID field 1813 may have a length of 7 bits.
  • the Serving Cell ID field 1821 may have a length of 5 bits
  • the CORESET ID field 1823 may have 5 bits
  • the TCI state ID field 1824 may have a length of 8 bits.
  • the order of the fields and the number of bits of each field are merely examples and are not limited thereto.
  • not all of the fields (or information) should be included in the MAC CE, and some fields may be omitted or some fields may be added.
  • the identifier of the second cell (eg PCI) It is possible to indicate the beam change or update configuration of the PDCCH while omitting .
  • the UE may refer to the RRC configuration for the cell (the first cell) indicated by the Serving Cell ID field 1811 .
  • the RRC configuration a part of the TCI state indicated by the (extended) TCI state ID fields 1813 and 1824 may be preset for the first cell and another part for the second cell.
  • the UE may receive the MAC CE from the first TRP and check the PCI of the second cell by using the (extended) TCI state ID fields 1813 and 1824 of the MAC CE.
  • the UE transmits the PDCCH beam through the CORESET resource indicated by the CORESET ID fields 1812 and 1821 (and the CORESET Pool Index field 1822) in the second TRP, the (extended) TCI state ID field 1813 , 1824) can be confirmed that it is transmitted in the same beam as the RS configured in association with the TCI state indicated.
  • the CORESET Pool index field 1822 when the CORESET Pool index field 1822 is included, the UE may confirm that the corresponding PCI is a cell configured for the purpose of inter-cell Multi TRP operation. In this case, the TCI state ID may be reflected according to the setting of QCL-info of RRC.
  • one PDCCH transmission beam is changed. It can be interpreted as an instruction. Or, as shown below in Figure 18a, when the terminal receives a MAC CE message including a plurality of CORESET ID fields (1812, 1823) and a plurality of TCI state IDs (1813, 1824), each CORESET of the second cell It can be interpreted as that the PDCCH transmission beam for the PDCCH is updated to each TCI state (that is, transmitted through the same beam as the RS configured in association with each TCI state).
  • one CORESET ID field 1812 and 1823 and a plurality of TCI state ID fields 1813 and 1824 may be included in the MAC CE. That is, the UE may determine that a plurality of TCI states are set in one CORESET ID. For example, it may be determined that each TCI state indicated by a plurality of TCI state IDs is set to be applied to correspond to a plurality of search spaces (sets) in one CORESET.
  • the base station or the terminal distinguishes the first cell from the second cell.
  • One way to do this is to use PCI.
  • the UE in order to change the configuration of the spatial domain of the beam through which the PDCCH is transmitted in the second TRP, the UE includes the TCI included in the RRC configuration (eg, ControlResourceSet, PDSCH-Config, NZP-CSI-RS-Resource, etc.) You can refer to -stateId.
  • the referenced TCI-stateID is as described above in Table 18. (QCL-info: set the RS of the source for QCL setting)
  • the MAC CE for instructing (or specifying) the change of the PDCCH beam is as shown in FIG. 18B .
  • the MAC CE below can be operated even if it is not set in RRC as in method 3.
  • the MAC CE 1830 may include a Physical Cell ID (PCI) field 1831 , a CORESET ID field 1832 , a CORESET Pool index field (optionally omitted) 1833 , and a TCI state ID field 1834 .
  • PCI Physical Cell ID
  • each PCI field 1831 is 10 bits
  • the CORESET ID field 1832 is 5 bits (or 4 bits)
  • the CORESET Pool index field (can be omitted) 1833 is 1 bit
  • the TCI state ID field ( 1834) may have a length of 7 bits.
  • the order of the fields and the number of bits of each field are merely examples and are not limited thereto.
  • not all of the fields (or information) should be included in the MAC CE, and some fields may be omitted or some fields may be added.
  • the UE may identify a cell (second cell) having PCI indicated by the PCI field 1831 .
  • the UE in the second TRP, the beam through which the PDCCH is transmitted through the CORESET resource indicated by the CORESET ID field 1832 (and the CORESET Pool Index field 1833) is the TCI indicated by the TCI state ID field 1834. It can be confirmed that it is transmitted in the same beam as the RS configured in association with the state. In this case, the TCI state ID may be reflected according to the setting of QCL-info of RRC.
  • PCI may be a case in which PCI is not set together in TCI state ID, QCL info, etc. through an RRC message. Alternatively, it may be included when PCI has been established, but replacement of the serving cell ID is explicitly required. For example, the PCI included in the MAC CE may be one of PCI used to report uplink feedback.
  • the UE may confirm that the corresponding PCI is a cell configured for the purpose of inter-cell Multi TRP operation.
  • the TCI state ID may be reflected according to the setting of QCL-info of RRC.
  • the UE when the UE receives a MAC CE message including one CORESET ID field 1832 and one TCI state ID field 1834, it is interpreted as indicating a change of one PDCCH transmission beam. can do.
  • the UE receives a MAC CE message including a plurality of CORESET ID fields 1832 and a plurality of TCI state ID fields 1834 as shown below in FIG. 18b , the PDCCH transmission beam for each CORESET of the second cell It can be interpreted as being updated to each TCI state (that is, transmitted through the same beam as RS configured in association with each TCI state).
  • one CORESET ID field 1832 and a plurality of TCI state ID fields 1834 may be included in the MAC CE. That is, the UE may determine that a plurality of TCI states are set in one CORESET ID. For example, it may be determined that each TCI state indicated by a plurality of TCI state IDs is set to be applied to correspond to a plurality of search spaces (sets) in one CORESET.
  • the Serving Cell ID field 1611 can be used as it is or partially extended to indicate a change in the beam through which the PDCCH is transmitted in the second TRP. . Since the second cell has a serving cell configuration according to an independent ServCellIndex, and one PCI can be allocated per ServCellIndex, the ServCellIndex and PCI of the second cell can be indicated through the Serving Cell ID field 1611 .
  • the MAC CE for instructing (or specifying) the change of the PDCCH beam is as shown in FIG. 18C .
  • MAC CE (1840) includes a Serving Cell ID field (1841), an identifier field that additionally defines an inter cell in addition to the basic serving cell ID (eg, an Intercell field) (1842), a CORESET ID field (1843), and a CORESET Pool index field ( may be omitted) 1844 , and a TCI state ID field 1845 .
  • each of the Serving Cell ID field 1841 is 5 bits
  • the Intercell field 1842 is 1 bit (1 to 4 bits)
  • the CORESET ID field 1843 is 5 bits (or 4 bits)
  • the CORESET Pool index field (Can be omitted) 1844 may have a length of 1 bit
  • the TCI state ID field 1844 may have a length of 7 bits.
  • the order of the fields and the number of bits of each field are merely examples and are not limited thereto.
  • not all of the fields (or information) should be included in the MAC CE, and some fields may be omitted or some fields may be added.
  • the inter cell identifier field 1842 may be used to distinguish it from the ServCellindex used for the existing carrier aggregation (CA). For example, in the above-described RRC configuration, whether the ServCellIndex of the second cell is for CA or for inter-cell Multi TRP operation may not be distinguished. In this case, when the value of the inter cell identifier field 1842 is indicated as 1, the UE may determine that the ServCellIndex of the second cell configured in a higher layer (eg, RRC) is for inter-cell Multi TRP. In another embodiment, CA and inter-cell Multi TRP operation may be independently configured in the above-described RRC configuration.
  • CA carrier aggregation
  • the inter cell identifier field 1842 may be omitted. That is, when the ServCellIndex is set to be clearly distinguished for the purpose of carrier aggregation in the RRC configuration, the inter cell identifier field 1842 may be unnecessary, and if it is implicitly indicated without being distinguished, the inter cell identifier field 1842 may be required.
  • the inter cell identifier field 1842 is 1 bit is illustrated, but it may be extended to a plurality of bits according to the number of non-serving cells linked for the inter-cell Multi TRP operation with a specific serving cell.
  • the UE may regard the cell indicated by the serving cell ID field 1841 as the first cell.
  • the UE may identify the PCI of the second cell through the serving cell configuration of the cell (second cell) indicated by the Serving Cell ID field 1841 (and the inter cell identifier field 1842).
  • the UE transmits the PDCCH beam through the CORESET resource indicated by the CORESET ID field 1843 (and the CORESET Pool Index field 1844) in the second TRP is the TCI state indicated by the TCI state ID field 1845. It can be confirmed that it is transmitted on the same beam as the RS configured in association with .
  • the TCI state ID may be reflected according to the setting of QCL-info of RRC.
  • the UE when the UE receives a MAC CE message including one CORESET ID field 1843 and one TCI state ID field, it can be interpreted as indicating a change of one PDCCH transmission beam. .
  • the PDCCH transmission beam for each CORESET of the second cell is transferred to each TCI state. It can be interpreted as being updated (that is, transmitted through the same beam as the RS configured in association with each TCI state).
  • one CORESET ID field 1843 and a plurality of TCI state ID fields 1845 may be included in the MAC CE. That is, the UE may determine that a plurality of TCI states are set in one CORESET ID. For example, it may be determined that each TCI state indicated by a plurality of TCI state IDs is set to be applied to correspond to a plurality of search spaces (sets) in one CORESET.
  • the PCI of the second cell When the PCI of the second cell is configured through the RRC configuration (eg, MeasConfig or MeasObject) for measurement, the PCI (PCI) of the second cell to indicate the change of the beam through which the PDCCH is transmitted in the second TRP You can use the SSB index linked to #2).
  • RRC configuration eg, MeasConfig or MeasObject
  • the MAC CE for instructing (or specifying) the change of the PDCCH beam may have a structure as shown in FIG. 18D.
  • FIG. 18D it is also possible to utilize the PCI and serving cell ID described above.
  • QCL association of CORESET ID can be used for measurement or QCL assumption operation by setting QCL parameters not only CORESET ID of the corresponding serving cell ID but also SSB ID.
  • MAC CE (1850) may include a Serving Cell ID field (1851), a CORESET ID field (1852), a CORESET Pool index (can be omitted) (1853), a TCI state ID field (1854), and an SSB ID field (1855). there is.
  • the Serving Cell ID field 1851 may indicate the second cell, and an identifier that additionally defines an inter cell by applying the above-described embodiment. Fields can also be used.
  • each of the Serving Cell ID field 1851 is 5 bits
  • the CORESET ID field 1852 is 5 bits (or 4 bits)
  • the TCI state ID field 1854 is 7 bits
  • the SSB ID field 1855 is It can have a length of 6 bits.
  • the order of the fields and the number of bits of each field are merely examples and are not limited thereto.
  • not all of the fields (or information) should be included in the MAC CE, and some fields may be omitted or some fields may be added.
  • the UE may refer to the serving cell configuration of the serving cell (first cell) indicated by the Serving Cell ID field 1851 . Accordingly, the UE can check the PCI of the second cell associated with the SSB index indicated by the SSB ID field 1855 .
  • the UE in the second TRP, the beam through which the PDCCH is transmitted through the CORESET resource indicated by the CORESET ID field 1852 (and the CORESET Pool Index field 1853) is indicated by the existing TCI state ID field 1854. It can be confirmed that the transmission is carried out in the same beam as the RS configured in association with the TCI state.
  • the CORESET Pool index field 1853 the UE may confirm that the corresponding PCI is a cell configured for the purpose of inter-cell Multi TRP operation. In this case, the TCI state ID may be reflected according to the setting of QCL-info of RRC.
  • the UE when the UE receives a MAC CE message including one CORESET ID field 1852 and one TCI state ID field 1854, it is interpreted as indicating a change of one PDCCH transmission beam. can do. Or, as shown below in FIG. 18D, when the UE receives a MAC CE message including a plurality of CORESET ID fields 1852 and a plurality of TCI state IDs 1854, PDCCH transmission for each CORESET of the second cell It can be interpreted that the beam is updated to each TCI state (that is, transmitted through the same beam as the RS configured in association with each TCI state).
  • one CORESET ID field 1852 and a plurality of TCI state ID fields 1854 may be included in the MAC CE. That is, the UE may determine that a plurality of TCI states are set in one CORESET ID. For example, it may be determined that each TCI state indicated by a plurality of TCI state IDs is set to be applied to correspond to a plurality of search spaces (sets) in one CORESET.
  • the UE receives the configuration message from the first TRP, and the MAC CE for instructing the change of the beam through which the PDCCH is transmitted in the second TRP is received from the second TRP. It is possible.
  • PDCCH monitoring for the second cell may be performed using the above-described method, and the MAC CE may be received from the second TRP through the PDSCH scheduled by the DCI received through the PDCCH.
  • 19 is a flowchart illustrating a method of instructing an inter-cell beam change according to the first embodiment of the present disclosure.
  • the first node may mean a node (eg, TRP) that transmits and receives data to and from the terminal through the first cell, and the second node physically communicates with the first node. It may refer to a node (eg, TRP) that is divided or separated and transmits and receives data to and from the terminal through the second cell different from the first cell.
  • TRP node
  • the first node 1910 may transmit a control message (eg, MAC CE) to the terminal 1900 in step S1905 .
  • a control message eg, MAC CE
  • step S1910 the terminal 1900 may check a change in the beam through which the PDCCH is transmitted from the second node 1920 based on the control message.
  • the terminal 1900 checks the beam change related control message (eg, MAC CE) through which the PDCCH is transmitted, and a response message thereto may be transmitted to the first node 1910 (not shown).
  • the response message may be defined in MAC CE format.
  • the terminal 1900 includes a MAC subheader (subheader) including a logical channel ID (LCID) corresponding to the response message (MAC CE) and the MAC sub PDU including the response message (MAC CE) may be transmitted to the first node 1910 .
  • MAC subheader including a logical channel ID (LCID) corresponding to the response message (MAC CE)
  • MAC sub PDU including the response message (MAC CE) may be transmitted to the first node 1910 .
  • the terminal 1900 may perform the subsequent operation without transmitting the above response message.
  • the second node 1920 may transmit the PDCCH to the terminal 1900 through the changed beam in step S1915.
  • the terminal 1900 may receive the PDCCH transmitted from the second node 1920 through the changed beam.
  • the first node 1910 confirms that the control message (eg, MAC CE) has been successfully received by the terminal 1900 based on the response message, and the second node 1920, in step S1915, The PDCCH may be transmitted to the UE 1900 through the changed beam.
  • the terminal 1900 may receive the PDCCH through the changed beam.
  • the first node 1910 sends the response message to the second node 1920 through a separate message (eg, an X2 interface message). is transmitted, and the second node 1920 may transmit the PDCCH to the UE 1900 through a beam changed based on this. can do.
  • the UE receives the configuration message from the first node 1910, and the MAC CE for instructing the change of the beam through which the PDCCH is transmitted from the second node 1920 is the second A method of receiving from node 1920 is also possible.
  • PDCCH monitoring for the second cell may be performed, and the MAC CE may be received from the second node 1920 through the PDSCH scheduled by the DCI received through the PDCCH.
  • the second embodiment proposes a method of instructing a beam change of a serving cell and a non-serving cell through one MAC CE in an inter-cell multi TRP operation.
  • a serving cell may be simply referred to as a first cell, and a TRP operating the first cell may be referred to as a first TRP.
  • a non-serving cell may be simply referred to as a second cell, and a TRP operating the second cell may be referred to as a second TRP.
  • the UE may receive one MAC CE and simultaneously check an indication (or specify) of a change in the PDCCH transmission beam of each of the first cell and the second cell.
  • the base station may transmit information on two PDCCH beams through one signaling.
  • the terminal can change the beam at once without distinguishing the type of TRP.
  • 20A to 20D are diagrams illustrating a MAC CE format according to a second embodiment of the present disclosure.
  • a separate serving cell id is not configured in the second cell (for example, it may be the case that there is no ServCellIndex or it is assumed that it is the same as the ServCellIndex of the first cell).
  • the PCI of the second cell can be checked by using the same method as in 2 .
  • the MAC CE for indicating (or specifying) the change of the PDCCH transmission beams of the first cell and the second cell with one MAC CE may have a structure as shown in FIG. 20A . It goes without saying that the MAC CE below can be operated even if it is not set in RRC as in method 3.
  • MAC CE (2010) includes Serving cell ID 1 field (2011), CORESET ID 1 field (2012), CORESET ID 2 field (2013), TCI state ID 1 field (2014), and TCI state ID 2 field (2015) can do.
  • each Serving Cell ID field (2011) is 5 bits
  • the CORESET ID 1 field (2012) is 5 bits
  • the CORESET ID 2 field (2013) is 5 bits
  • the TCI state ID 1 field (2014) is 7 bits (or 8 bits)
  • the TCI state ID 2 field 2015 may have a length of 7 bits (or 8 bits).
  • the order of the fields and the number of bits in each field are merely examples and are not limited thereto.
  • not all of the fields (or information) should be included in the MAC CE, and some fields may be omitted or some fields may be added.
  • the identifier of the second cell (eg PCI) It is possible to indicate the beam change or update configuration of the PDCCH while omitting .
  • the UE may refer to the serving cell configuration of the cell (first cell) indicated by the Serving Cell ID 1 field 2011 .
  • CORESET ID 1 means the CORESET index of the cell (first cell) indicated by the Serving cell ID 1 field (2011)
  • CORESET ID 2 is implicit in the TCI state setting indicated by the TCI state ID 2 field (2015). It may mean the CORESET index of the PCI cell (second cell). Therefore, the UE can confirm that the cell indicated by the Serving cell ID 1 field (2011) is the first cell, and the PCI of the second cell is performed through the PCI embedded in the TCI state setting indicated by the TCI state ID 2 field (2015). can be checked
  • the UE transmits the PDCCH through the CORESET resource indicated by the CORESET ID 1 field 2012 in the first TRP is the same beam as the RS set in association with the TCI state indicated by the TCI state ID 1 field 2014 It can be confirmed that it is transmitted to At the same time, the UE transmits the PDCCH beam through the CORESET resource indicated by the CORESET ID 2 field 2013 in the second TRP is set in association with the TCI state indicated by the TCI state ID 2 field 2015 Same as RS. It can be confirmed that the beam is transmitted.
  • the TCI state ID may be reflected according to the setting of QCL-info of RRC.
  • one PDCCH transmission beam It can be interpreted as indicating a change.
  • the UE upon receiving a MAC CE message including a plurality of CORESET fields and a plurality of TCI state ID fields for one cell, the UE updates the PDCCH transmission beam for each CORESET for one cell to each TCI state (that is, each It can be interpreted as being transmitted through the same beam as the RS configured in connection with the TCI state).
  • one TCI state ID corresponds to one CORESET ID
  • the above-described embodiment 1-1) or embodiment 1 -2) can be used to check the PCI of the second cell.
  • the MAC CE for indicating (or specifying) the change of the PDCCH transmission beams of the first cell and the second cell with one MAC CE may have a structure as shown in FIG. 20B . It goes without saying that the MAC CE below can be operated even if it is not set in RRC as in method 3.
  • MAC CE (2020) is 5 bits of Serving cell ID 1 field 2021, PCI field 2022, CORESET ID 1 field 2023, CORESET ID 2 field 2024, TCI state ID 1 field 2025, TCI state ID 2 field 2026 .
  • each of the Serving Cell ID field 2021 is 5 bits
  • the PCI field 2022 is 10 bits
  • the CORESET ID 1 field 2023 is 4 bits (or 5 bits)
  • the CORESET ID 2 field 2024 is 4 bits (or 5 bits)
  • the TCI state ID 1 field 2025 may have a length of 7 bits
  • the TCI state ID 2 field 2026 may have a length of 7 bits.
  • the order of the fields and the number of bits of each field are merely examples and are not limited thereto.
  • not all of the fields (or information) should be included in the MAC CE, and some fields may be omitted or some fields may be added.
  • MAC CE omits the identifier of the second cell (eg PCI) and changes the beam of the PDCCH Or you can instruct the update settings.
  • the UE may identify a cell (second cell) having PCI indicated by the PCI field 2022 .
  • CORESET ID 1 means the CORESET index of the cell (first cell) indicated by the serving cell ID 1 field 2021
  • CORESET ID 2 is the CORESET index of the cell (second cell) indicated by the PCI field 2022.
  • the UE can confirm that the cell indicated by the Serving cell ID 1 field 2021 is the first cell, and can identify the PCI of the second cell through the PCI field 2022 .
  • the UE in the first TRP, the beam through which the PDCCH is transmitted through the CORESET resource indicated by the CORESET ID 1 field 2022 is linked to the TCI state indicated by the TCI state ID 1 field 2025. It can be confirmed that the beam is transmitted.
  • the UE transmits the PDCCH through the CORESET resource indicated by the CORESET ID 2 field 2024 in the second TRP is the same beam as the RS set in association with the TCI state indicated by the TCI state ID 2 field 2026 It can be confirmed that it is transmitted to In this case, the TCI state ID may be reflected according to the setting of QCL-info of RRC.
  • one PDCCH transmission beam It can be interpreted as indicating a change.
  • the UE upon receiving a MAC CE message including a plurality of CORESET fields and a plurality of TCI state ID fields for one cell, the UE updates the PDCCH transmission beam for each CORESET for one cell to each TCI state (that is, each It can be interpreted as being transmitted through the same beam as the RS configured in connection with the TCI state).
  • one TCI state ID corresponds to one CORESET ID
  • the Serving Cell ID field 2031 can be used as it is or partially extended to indicate a change in the beam through which the PDCCH is transmitted in the second TRP. . Since the second cell has a serving cell configuration according to an independent ServCellIndex, and one PCI can be allocated per ServCellIndex, the ServCellIndex and PCI of the second cell can be indicated through the Serving Cell ID field 2031 .
  • the MAC CE for instructing (or specifying) the change of the PDCCH beam is as shown in FIG. 20C .
  • MAC CE (2030) includes a Serving Cell ID field (2031), an identifier field that additionally defines an inter cell (eg, an Intercell field) (2032), a CORESET ID 1 field (2033), and a CORESET ID 2 field in addition to the basic serving cell ID. 2034 , a TCI state ID 1 field 2035 , and a TCI state ID 2 field 2036 may be included.
  • each of the Serving Cell ID field 2031 is 5 bits
  • the Intercell field 2032 is 1 bit (1 to 4 bits)
  • the CORESET ID 1 field 2033 is 4 bits (or 5 bits)
  • CORESET ID 2 The field 2034 may have a length of 4 bits (or 5 bits)
  • the TCI state ID 1 field 2035 may have a length of 7 bits
  • the TCI state ID 2 field 2036 may have a length of 7 bits.
  • the order of the fields and the number of bits of each field are merely examples and are not limited thereto.
  • not all of the fields (or information) should be included in the MAC CE, and some fields may be omitted or some fields may be added.
  • the inter cell identifier field 2032 may be used to distinguish it from the ServCellindex used for the existing carrier aggregation (CA). For example, in the above-described RRC configuration, whether the ServCellIndex of the second cell is for CA or for inter-cell Multi TRP operation may not be distinguished. In this case, when the value of the inter cell identifier field 2032 is indicated as 1, the UE may determine that the ServCellIndex of the second cell configured in a higher layer (eg, RRC) is for inter-cell Multi TRP. In another embodiment, CA and inter-cell Multi TRP operation may be independently configured in the above-described RRC configuration.
  • CA carrier aggregation
  • the inter cell identifier field 2032 may be omitted. That is, when ServCellIndex is set to be clearly distinguished for the purpose of carrier aggregation in RRC configuration, the inter cell identifier field 2032 may be unnecessary, and if it is implicitly indicated without distinction, the inter cell identifier field 2032 may be required.
  • inter cell identifier field 2032 is 1 bit is illustrated, but it may be extended to a plurality of bits according to the number of non-serving cells linked for the inter-cell Multi TRP operation with a specific serving cell.
  • the UE is a serving cell of the cell (second cell) indicated by the Serving Cell ID field 2031 .
  • the UE in the first TRP, the beam through which the PDCCH is transmitted through the CORESET resource indicated by the CORESET ID 1 field 2033 is linked to the TCI state indicated by the TCI state ID 1 field 2035. It can be confirmed that the beam is transmitted.
  • the beam through which the PDCCH is transmitted through the CORESET resource indicated by the CORESET ID 2 field 2034 is the same beam as the RS set in association with the TCI state ID indicated by the TCI state ID 2 field 2036. can confirm that it is being transmitted.
  • the TCI state ID may be reflected according to the setting of QCL-info of RRC.
  • the inter cell identifier field 2032 is indicated as 0, it may be assumed that only TCI states ID 1 exists.
  • one PDCCH transmission beam It can be interpreted as indicating a change.
  • the UE upon receiving a MAC CE message including a plurality of CORESET fields and a plurality of TCI state ID fields for one cell, the UE updates the PDCCH transmission beam for each CORESET for one cell to each TCI state (that is, each It can be interpreted as being transmitted through the same beam as the RS configured in connection with the TCI state).
  • one TCI state ID corresponds to one CORESET ID
  • a separate serving cell id eg, ServCellIndex
  • a plurality of Serving Cell ID fields (2041, 2042) are used to indicate the change of the PDCCH transmission beam of each of the first cell and the second cell.
  • the first cell and the second cell have independent serving cell settings according to ServCellIndex, and one PCI may be allocated per ServCellIndex. Accordingly, the first cell may be indicated through the Serving Cell ID 1 field 2041 and the second cell may be indicated through the Serving Cell ID 2 field 2042 .
  • the MAC CE may have a structure as shown in FIG. 20D .
  • MAC CE 2040 is Serving Cell ID 1 field 2041, Serving Cell ID 2 field 2042, CORESET ID 1 field 2043, CORESET ID 2 field 2044, TCI state ID 1 field 2045, TCI It may include a state ID 2 field 2046 .
  • each of the Serving Cell ID 1 field 2041 is 5 bits
  • the Serving Cell ID 2 field 2042 is 5 bits
  • the CORESET ID 1 field 2043 is 4 bits (or 5 bits)
  • the CORESET ID 2 field 2044 may have 4 bits (or 5 bits)
  • the TCI state ID 1 field 2045 may have 7 bits
  • the TCI state ID 2 field 2046 may have 7 bits.
  • the order of the fields and the number of bits of each field are merely examples and are not limited thereto.
  • not all fields (or information) should be included in the MAC CE, and some fields may be omitted or fields may be added.
  • the UE may confirm that the cell indicated by the Serving Cell ID 1 field 2041 is the first cell, and may confirm that the cell indicated by the Serving Cell ID 2 field 2042 is the second cell.
  • the UE in the first TRP, the beam through which the PDCCH is transmitted through the CORESET resource indicated by the CORESET ID 1 field 2043 is linked to the TCI state indicated by the TCI state ID 1 field 2045. It can be confirmed that the beam is transmitted.
  • the beam through which the PDCCH is transmitted through the CORESET resource indicated by the CORESET ID 2 field 2044 is the same beam as the RS set in association with the TCI state ID indicated by the TCI state ID 2 field 2046. can confirm that it is being transmitted.
  • the TCI state ID may be reflected according to the setting of QCL-info of RRC.
  • one PDCCH transmission beam It can be interpreted as indicating a change.
  • the UE upon receiving a MAC CE message including a plurality of CORESET fields and a plurality of TCI state ID fields for one cell, the UE updates the PDCCH transmission beam for each CORESET for one cell to each TCI state (that is, each It can be interpreted as being transmitted through the same beam as the RS configured in connection with the TCI state).
  • one TCI state ID corresponds to one CORESET ID
  • the UE receives the configuration message in the first TRP, and the MAC CE for simultaneously indicating the change of the beam through which the PDCCH is transmitted in the first TRP and the second TRP is the second It is also possible to receive from TRP.
  • PDCCH monitoring for the second cell may be performed, and the MAC CE may be received from the second TRP through the PDSCH scheduled by the DCI received through the PDCCH.
  • 21 is a flowchart illustrating a method of simultaneously instructing to change beams of a first cell and a second cell through one control message according to a second embodiment of the present disclosure.
  • the first node may mean a node (eg, TRP) that transmits and receives data to and from the terminal through the first cell, and the second node is physically connected to the first node. It may refer to a node (eg, TRP) that is divided or separated and transmits and receives data to and from the terminal through the second cell different from the first cell.
  • TRP node
  • the first node 2110 may transmit a control message (eg, MAC CE) to the terminal 2100 in step S2105 .
  • a control message eg, MAC CE
  • the terminal 2100 may check a change in a beam through which each PDCCH is transmitted from at least one of the first node 2110 and the second node 2120 based on the control message.
  • the terminal 2100 checks the change-related control message (eg, MAC CE) of the beam through which the PDCCH is transmitted, and a response message thereto may be transmitted to the first node 2110 (not shown).
  • the response message may be defined in MAC CE format.
  • the terminal 2100 includes a MAC subheader (subheader) including a logical channel ID (LCID) corresponding to the response message (MAC CE) and the MAC sub PDU including the response message (MAC CE) may be transmitted to the first node 2110 .
  • MAC subheader including a logical channel ID (LCID) corresponding to the response message (MAC CE)
  • MAC sub PDU including the response message (MAC CE) may be transmitted to the first node 2110 .
  • the terminal 2100 may perform the subsequent operation without transmitting the above response message.
  • the first node 2110 or the second node 2120 may transmit the PDCCH to the terminal 2100 through the changed beam in step S2115.
  • the terminal 2100 may receive each transmitted PDCCH from at least one of the first node 2110 and the second node 2120 through the changed beam.
  • the first node 2110 confirms that the control message (eg, MAC CE) has been successfully received by the terminal 2100 based on the response message, and the first node 2110 or the second node ( The 2120 may transmit the PDCCH to the terminal 2100 through the changed beam in step S2115.
  • the terminal 2100 may receive each transmitted PDCCH from at least one of the first node 2110 and the second node 2120 through the changed beam.
  • the first node 2110 sends the response message to the second node 2120 through a separate message (eg, an X2 interface message). is transmitted, and the second node 2120 may transmit the PDCCH to the terminal 1900 through a beam changed based on this.
  • the terminal receives the configuration message from the first node 2110, and each PDCCH is transmitted from at least one of the first node 2110 and the second node 2120.
  • a method of receiving the MAC CE for instructing the change of m from the second node 2120 is also possible.
  • PDCCH monitoring for the second cell may be performed, and the MAC CE may be received from the second node 2120 through the PDSCH scheduled by the DCI received through the PDCCH.
  • 22 is a flowchart illustrating an operation of a terminal according to the first embodiment of the present disclosure.
  • step S2205 the terminal may report to the base station the terminal capability information (eg, UE capability) related to the multi-TRP operation to the base station.
  • the terminal capability information eg, UE capability
  • step S2205 may be omitted.
  • the UE may receive a configuration message (eg, RRC message) including configuration information related to (Inter-cell) Multi TRP operation.
  • a configuration message eg, RRC message
  • RRC message configuration information related to (Inter-cell) Multi TRP operation.
  • the terminal may receive a control message (eg, MAC CE) through the first node.
  • a control message eg, MAC CE
  • step S2220 based on the information included in the configuration message or the control message, the terminal checks the change of the beam through which the PDCCH is transmitted in the second node, and can receive the PDCCH from the second node through the changed beam. there is.
  • FIG. 23 is a flowchart illustrating an operation of a terminal according to a second embodiment of the present disclosure.
  • the terminal may report to the base station multi-TRP operation-related terminal capability information (eg, UE capability) to the base station in step S2305.
  • the base station multi-TRP operation-related terminal capability information eg, UE capability
  • step S2305 may be omitted.
  • the UE may receive a configuration message (eg, RRC message) including configuration information related to the (Inter-cell) Multi TRP operation.
  • a configuration message eg, RRC message
  • RRC message configuration information related to the (Inter-cell) Multi TRP operation.
  • the terminal may receive a control message (eg, MAC CE) through the first node.
  • a control message eg, MAC CE
  • step S2320 the terminal checks the change of the beam through which each PDCCH is transmitted from at least one of the first node and the second node based on the information included in the configuration message or the control message, and uses the changed beam
  • the PDCCH may be received from at least one of the first node and the second node.
  • 24 is a flowchart illustrating an operation of a base station according to an embodiment of the present disclosure.
  • a serving cell may be simply referred to as a first cell, and a non-serving cell may be simply referred to as a second cell.
  • the first cell and the second cell may mean each cell operated by a plurality of base stations, or may mean a plurality of cells operated by one base station.
  • the first node may mean a TRP for transmitting and receiving data to and from the terminal through the first cell, and the second node is physically separated or separated from the first node and is a terminal through a second cell different from the first cell and TRP for transmitting and receiving data.
  • the base station may receive multi-TRP operation-related terminal capability information (eg, UE capability) in step S2405. On the other hand, if the base station has previously received or already stored the terminal capability, step S2405 may be omitted.
  • multi-TRP operation-related terminal capability information eg, UE capability
  • the base station may transmit a configuration message (eg, an RRC message) including configuration information related to the (Inter-cell) Multi TRP operation in step S2410.
  • a configuration message eg, an RRC message
  • RRC message configuration information related to the (Inter-cell) Multi TRP operation in step S2410.
  • the base station may transmit a control message (eg, MAC CE) in step S2415.
  • the control message may be used to instruct the UE to change the beam through which the PDDCH is transmitted in the second node.
  • the base station may transmit a PDCCH to the terminal through a beam changed by the second node.
  • 25 is a diagram illustrating a structure of a terminal according to an embodiment of the present disclosure.
  • the terminal may include a transceiver 2510 , a controller 2520 , and a storage 2530 .
  • the controller may be defined as a circuit or an application specific integrated circuit or at least one processor.
  • the transceiver 2510 may transmit/receive signals to and from other network entities.
  • the transceiver 2510 may receive, for example, system information from a base station, and may receive a synchronization signal or a reference signal.
  • the controller 2520 may control the overall operation of the terminal according to the embodiment proposed in the present invention.
  • the controller 2520 may control a signal flow between blocks to perform an operation according to the above-described flowchart.
  • the controller 2520 may control to receive a control message instructing a PDCCH beam change or update operation of each TRP in an inter-cell multi TRP operation.
  • the storage unit 2530 may store at least one of information transmitted and received through the transceiver 2510 and information generated through the control unit 2520 .
  • the storage unit 2530 may store configuration information (eg, information included in an RRC message) for an inter-cell Multi TRP operation.
  • 26 is a diagram illustrating a structure of a base station according to an embodiment of the present disclosure.
  • the base station may include a transceiver 2610 , a control unit 2620 , and a storage unit 2630 .
  • the controller may be defined as a circuit or an application specific integrated circuit or at least one processor.
  • the transceiver 2610 may transmit/receive signals to and from other network entities.
  • the transceiver 2610 may transmit, for example, system information to the terminal, and may transmit a synchronization signal or a reference signal.
  • the controller 2620 may control the overall operation of the base station according to the embodiment proposed in the present invention.
  • the controller 2620 may control a signal flow between blocks to perform an operation according to the above-described flowchart.
  • the controller 2620 may control to transmit a control message instructing a PDCCH beam change or update operation of each TRP in an inter-cell Multi TRP operation according to an embodiment of the present invention.
  • the storage unit 2630 may store at least one of information transmitted and received through the transceiver 2610 and information generated through the control unit 2520 .
  • the storage unit 2630 may store configuration information (eg, information included in an RRC message) for an inter-cell Multi TRP operation.

Landscapes

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

Abstract

La présente divulgation concerne : une technique de communication permettant de fusionner une technologie IdO avec un système de communication 5G permettant de prendre en charge un débit de transmission de données supérieur à celui d'un système 4G ; et un système associé. La présente divulgation peut être appliquée à des services intelligents (par exemple, des maisons intelligentes, des immeubles intelligents, des villes intelligentes, des voitures intelligentes ou des voitures connectées, des soins de santé, l'enseignement numérique, le commerce de détail, les services associés à la sécurité et à la sûreté et analogues) sur la base de la technologie de communication 5G et de la technologie relative à l'IdO. La présente invention concerne un procédé permettant de gérer de façon plus efficace un faisceau dans un système de communication coopérative cellule-à-cellule utilisant une pluralité de cellules.
PCT/KR2021/014704 2020-10-21 2021-10-20 Procédé et appareil de gestion de faisceau pour la communication coopérative cellule-à-cellule dans un système de communication sans fil WO2022086169A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR1020200137062A KR20220052758A (ko) 2020-10-21 2020-10-21 무선 통신 시스템에서 셀 간 협력 통신을 위한 빔 관리 방법 및 장치
KR10-2020-0137062 2020-10-21

Publications (1)

Publication Number Publication Date
WO2022086169A1 true WO2022086169A1 (fr) 2022-04-28

Family

ID=81290899

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2021/014704 WO2022086169A1 (fr) 2020-10-21 2021-10-20 Procédé et appareil de gestion de faisceau pour la communication coopérative cellule-à-cellule dans un système de communication sans fil

Country Status (2)

Country Link
KR (1) KR20220052758A (fr)
WO (1) WO2022086169A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230163831A1 (en) * 2021-11-23 2023-05-25 Qualcomm Incorporated Beam switching in near-field operations

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200187047A1 (en) * 2016-10-19 2020-06-11 Huawei Technologies Co., Ltd. Method and apparatus for transmitting buffer status report

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200187047A1 (en) * 2016-10-19 2020-06-11 Huawei Technologies Co., Ltd. Method and apparatus for transmitting buffer status report

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
INTEL CORPORATION: "Multi-TRP enhancements for inter-cell operation", 3GPP DRAFT; R1-2005860, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20200817 - 20200828, 8 August 2020 (2020-08-08), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051917761 *
NOKIA, NOKIA SHANGHAI BELL: "Enhancements to enable inter-cell multi-TRP operations", 3GPP DRAFT; R1-2006845, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20200817 - 20200828, 7 August 2020 (2020-08-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051915490 *
VIVO: "Discussion on inter-cell multi-TRP operation", 3GPP DRAFT; R1-2005365, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20200817 - 20200828, 8 August 2020 (2020-08-08), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051917390 *
XIAOMI: "Enhancement on Inter-cell Multi-TRP operations", 3GPP DRAFT; R1-2006545, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20200817 - 20200828, 7 August 2020 (2020-08-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051915391 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230163831A1 (en) * 2021-11-23 2023-05-25 Qualcomm Incorporated Beam switching in near-field operations
US11909496B2 (en) * 2021-11-23 2024-02-20 Qualcomm Incorporated Beam switching in near-field operations

Also Published As

Publication number Publication date
KR20220052758A (ko) 2022-04-28

Similar Documents

Publication Publication Date Title
WO2021060766A1 (fr) Procédé et appareil de modification de faisceau de terminal dans un système de communication sans fil
WO2021040338A1 (fr) Procédé et appareil d'émission et de réception de multiples éléments de données dans un système de communication coopératif sans fil
WO2020032580A1 (fr) Procédé de fonctionnement de nœud dans un système de communication sans fil et appareil utilisant ledit procédé
WO2019160353A1 (fr) Procédé et appareil pour économies d'énergie au niveau d'un équipement d'utilisateur
WO2020032578A1 (fr) Procédé utilisant une ressource d'un nœud dans un système de communication sans fil et dispositif utilisant ledit procédé
WO2020032666A1 (fr) Procédé et appareil de mesure d'interférence de liaison croisée à distance
WO2018203650A1 (fr) Procédé et appareil d'attribution de ressources dans un système de communication sans fil
WO2018203680A1 (fr) Procédé d'émission et de réception de signal au moyen d'un faisceau dans un système de communication sans fil, et appareil pour ledit procédé
WO2021172942A1 (fr) Procédé et appareil permettant de prendre en charge un canal d'indication de faisceau
WO2018012899A1 (fr) Procédé et appareil pour émettre et recevoir un préambule d'accès aléatoire dans un système de communication cellulaire sans fil
WO2022031142A1 (fr) Procédé et appareil d'indication, de mesure et d'établissement de rapport sur des faisceaux de liaison descendante et de liaison montante entre des cellules
WO2018203679A1 (fr) Procédé d'émission et de réception de signal au moyen d'un faisceau dans un système de communication sans fil, et appareil pour ledit procédé
WO2019050323A1 (fr) Procédé et système de gestion de surveillance de liaison radio (rlm) à l'aide de configurations de partie de bande passante (bwp)
WO2019027242A1 (fr) Procédé et appareil de détection d'informations d'indication et procédés et dispositifs de relais de transmission
EP3685619A1 (fr) Procédé et noeud de réseau permettant d'effectuer une transmission de données et des mesures sur de multiples parties de bande passante
WO2021066630A1 (fr) Procédé d'émission et de réception de signal de référence de suivi de phase dans un système de communication sans fil, et appareil associé
WO2021015475A1 (fr) Procédé et dispositif de rapport d'informations d'état de canal dans un système de communications sans fil
WO2021066622A1 (fr) Procédé d'émission et de réception de signal de référence de suivi de phase dans un système de communication sans fil, et appareil associé
WO2020096433A1 (fr) Appareil et procédé de sélection de technologie d'accès radio pour communication directe entre terminaux dans un système de communication sans fil
WO2022015028A1 (fr) Procédé et appareil pour traiter la mini transmission de données avec rrc à l'état inactif dans un système de communication sans fil
WO2019031879A1 (fr) Procédé de signalisation d'informations d'état de canal dans un système de communication sans fil et appareil associé
WO2021075939A1 (fr) Procédé et appareil permettant de transmettre et de recevoir des données multiples dans un système de communication coopératif sans fil
WO2021086147A1 (fr) Procédé de fonctionnement pour nœud iab dans un système de communication sans fil, et dispositif utilisant le procédé
WO2021066624A1 (fr) Procédé d'émission et de réception de pdsch dans un système de communication sans fil, et dispositif à cet effet
WO2014109580A2 (fr) Procédé d'amélioration de petite cellule

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21883237

Country of ref document: EP

Kind code of ref document: A1