Method and apparatus for acquiring channel state information in network cooperative communication system

Abstract

A method performed by a UE in a wireless communication system according to an embodiment of the present disclosure may comprise the steps of: receiving, from a BS, configuration information related to a channel state information (CSI) report through higher layer signaling; identifying, from the configuration information related to the CSI report, a parameter indicating one of at least one CLI measurement resource set for CLI measurement; and measuring CLI in a CSI measurement resource set indicated by the identified parameter.

Description

Method and device for acquiring channel state information in a network cooperative communication system

[0001] The present disclosure relates to the operation of a terminal and a base station in a wireless communication system. Specifically, the present disclosure relates to a method for acquiring channel state information in a network cooperative communication system and an apparatus capable of performing the same.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in frequency bands below 6 GHz ('Sub 6 GHz'), such as 3.5 gigahertz (3.5 GHz), but also in ultra-high frequency bands called millimeter waves (mmWave), such as 28 GHz and 39 GHz ('Above 6 GHz'). In addition, for 6G mobile communication technology, which is referred to as a system beyond 5G, implementation in the terahertz band (e.g., the 3 terahertz (3 THz) band at 95 GHz) is being considered to achieve transmission speeds 50 times faster and ultra-low latency reduced to one-tenth compared to 5G mobile communication technology.

[0003] In the early stages of 5G mobile communication technology, aiming to satisfy service support and performance requirements for enhanced Mobile BroadBand (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), technologies such as beamforming and Massive MIMO to mitigate path loss and increase transmission distance in ultra-high frequency bands, support for various numerologies (such as the operation of multiple subcarrier spacings) and dynamic operation of slot formats for the efficient utilization of ultra-high frequency resources, initial access techniques to support multi-beam transmission and broadband, definition and operation of Band-Width Parts (BWP), Low Density Parity Check (LDPC) codes for high-volume data transmission, new channel coding methods such as Polar Codes for the reliable transmission of control information, and L2 pre-processing (L2 Standardization has been carried out for pre-processing, network slicing which provides a dedicated network specialized for specific services, and other methods.

[0004] Currently, discussions are underway to improve and enhance the performance of the initial 5G mobile communication technology, taking into account the services that the 5G mobile communication technology was intended to support. Additionally, standardization of the physical layer is in progress for technologies such as V2X (Vehicle-to-Everything), which helps autonomous vehicles make driving decisions and enhance user convenience based on their own location and status information transmitted by the vehicle; NR-U (New Radio Unlicensed), which aims for system operation in unlicensed bands to comply with various regulatory requirements; NR terminal low power consumption technology (UE Power Saving); Non-Terrestrial Network (NTN), which is direct terminal-satellite communication for securing coverage in areas where communication with the terrestrial network is impossible; and positioning.

[0005] In addition, standardization is underway in the field of wireless interface architecture / protocols for technologies such as the Industrial Internet of Things (IIoT) for supporting new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) which provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement including Conditional Handover and Dual Active Protocol Stack (DAPS) Handover, and 2-step Random Access (2-step RACH for NR) which simplifies random access procedures. Standardization is also underway in the field of system architecture / services for 5G baseline architectures (e.g., Service based Architecture, Service based Interface) for incorporating Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC), which provides services based on the location of the terminal.

[0006] When such 5G mobile communication systems are commercialized, connected devices, which are increasing explosively, will be connected to communication networks. Accordingly, it is expected that there will be a need to enhance the functionality and performance of 5G mobile communication systems and to integrate the operation of connected devices. To this end, new research is planned to be conducted on 5G performance improvement and complexity reduction, support for AI services, support for metaverse services, and drone communication using eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] Furthermore, the advancement of these 5G mobile communication systems encompasses multi-antenna transmission technologies such as new waveforms to guarantee coverage in the terahertz band of 6G mobile communication technology, Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas; metamaterial-based lenses and antennas to improve terahertz band signal coverage; high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum); and Reconfigurable Intelligent Surface (RIS) technology; as well as Full Duplex technology for enhancing frequency efficiency and system networks in 6G mobile communication technology; AI-based communication technologies that realize system optimization by utilizing satellites and AI from the design stage and internalizing end-to-end AI support functions; and the realization of services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could serve as a foundation for the development of next-generation distributed computing technologies.

[0008] The present disclosure aims to provide a method for obtaining channel state information in a network cooperative communication system and an apparatus capable of performing the same.

[0009] A method performed by a UE in a wireless communication system according to one embodiment of the present disclosure may include: receiving configuration information regarding a CSI (channel state information) report through upper layer signaling from a BS; identifying a parameter indicating one of at least one set of CLI measurement resources for CLI measurement from the configuration information regarding the CSI report; and measuring the CLI in the set of CSI measurement resources indicated by the identified parameter.

[0010] FIG. 1 is a diagram illustrating the basic structure of the time-frequency domain in a wireless communication system according to one embodiment of the present disclosure.

[0011] FIG. 2 is a drawing illustrating a frame, subframe, and slot structure in a wireless communication system according to one embodiment of the present disclosure.

[0012] FIG. 3 is a drawing illustrating an example of a bandwidth portion setting in a wireless communication system according to one embodiment of the present disclosure.

[0013] FIG. 4 is a diagram illustrating the wireless protocol structure of a base station and a terminal in a single cell, carrier aggregation, dual connectivity situation in a wireless communication system according to one embodiment of the present disclosure.

[0014] FIG. 5 is a diagram of the beam application time that can be considered when using an integrated TCI method in a wireless communication system according to one embodiment of the present disclosure.

[0015] FIG. 6 is a diagram showing another MAC-CE structure for activating and indicating a joint TCI state or a separate DL or UL TCI state in a wireless communication system according to one embodiment of the present disclosure.

[0016] Figure 7 is a diagram illustrating an example of a non-periodic CSI reporting method.

[0017] FIG. 8 is a diagram illustrating an example of setting a control area of ​​a downlink control channel in a wireless communication system according to one embodiment of the present disclosure.

[0018] FIG. 9 is a diagram illustrating the structure of a downlink control channel in a wireless communication system according to one embodiment of the present disclosure.

[0019] Figure 10 illustrates the process for beam setting and activation of PDSCH.

[0020] FIG. 11 is a diagram showing an SRS antenna switching operation according to one embodiment of the present disclosure.

[0021] FIG. 12 is a drawing illustrating an example of antenna port configuration and resource allocation for cooperative communication in a wireless communication system according to one embodiment of the present disclosure.

[0022] FIG. 13 is a diagram illustrating an example of downlink control information (DCI) configuration for cooperative communication in a wireless communication system according to one embodiment of the present disclosure.

[0023] Figure 14 is a diagram showing the Enhanced PDSCH TCI state activation / deactivation MAC-CE structure.

[0024] FIG. 15a is a drawing illustrating elements constituting a base station according to one embodiment of the present disclosure.

[0025] FIG. 15b is a diagram showing an example of the process in which a base station obtains channel state information of a terminal through CSI transmitted by the terminal.

[0026] FIG. 16 is another diagram illustrating an example of a process in which a base station obtains channel status information of a terminal through CSI transmitted by a terminal according to an embodiment of the present disclosure.

[0027] FIG. 17 is a drawing showing the operation of a terminal according to one embodiment of the present disclosure.

[0028] FIG. 18 is a drawing showing the operation of a base station according to one embodiment of the present disclosure.

[0029] FIG. 19a is a diagram illustrating an example of a terminal and a base station exchanging information between MMUs through a direct communication link between MMUs according to an embodiment of the present disclosure.

[0030] FIG. 19b is a diagram illustrating an example of the process of exchanging channel state information between a terminal and a base station during information exchange between MMUs via a direct communication link between MMUs according to one embodiment of the present disclosure.

[0031] FIG. 20 is a drawing illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure.

[0032] FIG. 21 is a drawing illustrating the structure of a base station in a wireless communication system according to one embodiment of the present disclosure.

[0033] A method performed by a UE in a wireless communication system according to one embodiment of the present disclosure may include: receiving configuration information regarding a CSI (channel state information) report through upper layer signaling from a BS (base station); identifying a parameter indicating one of at least one set of CLI measurement resources for measuring cross-link interference (CLI) from the configuration information regarding the CSI report; and measuring CLI in the set of CSI measurement resources indicated by the identified parameter.

[0034] A method performed by a base station (BS) in a wireless communication system according to one embodiment of the present disclosure may include: transmitting configuration information regarding a channel state information (CSI) report to a user equipment (UE) through upper layer signaling; and receiving from the UE a report regarding a CLI measured in a CLI measurement resource set indicated by a parameter included in the configuration information regarding the CSI report among at least one CLI measurement resource set for cross-link interference (CLI) measurement.

[0035] A UE (user equipment) in a wireless communication system according to one embodiment of the present disclosure comprises: a transceiver; and at least one processor connected to the transceiver. The at least one processor receives configuration information regarding a CSI (channel state information) report through upper layer signaling from a BS (base station), identifies a parameter indicating one of at least one CLI measurement resource set for measuring cross-link interference (CLI) from the configuration information regarding the CSI report, and can measure CLI in the CSI measurement resource set indicated by the identified parameter.

[0036] A base station (BS) in a wireless communication system according to one embodiment of the present disclosure comprises: a transceiver; and at least one processor connected to the transceiver. The at least one processor transmits configuration information regarding a channel state information (CSI) report to a user equipment (UE) through upper layer signaling, and can receive from the UE a report regarding a CLI measured in a CLI measurement resource set indicated by a parameter included in the configuration information regarding the CSI report among at least one CLI measurement resource set for cross-link interference (CLI) measurement.

[0037] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings.

[0038] In describing the embodiments, technical details that are well known in the art to which this disclosure belongs and are not directly related to this disclosure are omitted. This is intended to convey the essence of this disclosure more clearly without obscuring it by omitting unnecessary explanations.

[0039] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the dimensions of each component do not entirely reflect their actual dimensions. Identical or corresponding components in each drawing have been assigned the same reference numbers.

[0040] The advantages and features of the present disclosure, and the methods for achieving them, will become clear by referring to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below but may be implemented in various different forms. These embodiments are provided merely to ensure that the disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Throughout the specification, the same reference numerals refer to the same components. Furthermore, in describing the present disclosure, if it is determined that a detailed description of a related function or configuration might unnecessarily obscure the essence of the present disclosure, such detailed description is omitted. Additionally, the terms described below are defined considering their functions in the present disclosure, and these may vary depending on the intentions or conventions of the user or operator. Therefore, their definitions should be based on the content throughout the specification.

[0041] Hereinafter, a base station is an entity that performs resource allocation for terminals and may be at least one of a gNode B, eNode B, Node B, BS (Base Station), wireless access unit, base station controller, or a node on a network. A terminal may include a UE (User Equipment), MS (Mobile Station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions. In this disclosure, a downlink (DL) refers to a wireless transmission path of a signal transmitted by a base station to a terminal, and an uplink (UL) refers to a wireless transmission path of a signal transmitted by a terminal to a base station. Furthermore, while LTE or LTE-A systems may be described as examples below, embodiments of this disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, 5th generation mobile communication technologies (5G, new radio, NR) developed after LTE-A may be included therein, and the 5G below may be a concept that includes existing LTE, LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems with some modifications made at the discretion of a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.

[0042] At this point, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams can be executed by computer program instructions. Since these computer program instructions can be loaded into the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, the instructions executed through the processor of the computer or other programmable data processing equipment create means to perform the functions described in the flow diagram block(s). Since these computer program instructions can also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the function in a specific way, the instructions stored in computer-available or computer-readable memory can also produce a manufactured item containing instruction means to perform the function described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer can also provide steps for executing the functions described in the flowchart block(s).

[0043] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specific logical function(s). It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For example, two blocks described in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order according to their corresponding functions.

[0044] In this embodiment, the term "part" refers to a software or hardware component such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit), and the "part" performs certain roles. However, the meaning of "part" is not limited to software or hardware. The "part" may be configured to reside in an addressable storage medium or configured to run one or more processors. Thus, as an example, the "part" includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and "parts" may be combined into a smaller number of components and "parts" or further separated into additional components and "parts." In addition, the components and 'parts' may be implemented to utilize one or more CPUs within the device or secure multimedia card. Also, in the embodiments, 'parts' may include one or more processors.

[0045] Wireless communication systems are evolving from providing early voice-oriented services to broadband wireless communication systems that provide high-speed, high-quality packet data services, such as communication standards like 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’s HRPD (High Rate Packet Data), UMB (Ultra Mobile Broadband), and IEEE’s 802.16e.

[0046] As a representative example of the above-mentioned broadband wireless communication system, the LTE system employs the Orthogonal Frequency Division Multiplexing (OFDM) method for the downlink (DL) and the Single Carrier Frequency Division Multiple Access (SC-FDMA) method for the uplink (UL). The uplink refers to a wireless link through which a terminal (User Equipment (UE) or Mobile Station (MS)) transmits data or control signals to a base station (eNode B, or base station (BS)), and the downlink refers to a wireless link through which a base station transmits data or control signals to a terminal. The above-mentioned multiple access method can distinguish the data or control information of each user by allocating and operating time-frequency resources to be sent for each user so that they do not overlap, that is, so that orthogonality is established.

[0047] As a future communication system following LTE, that is, a 5G communication system, it must be able to freely reflect the diverse requirements of users and service providers, and therefore, services that satisfy various requirements simultaneously must be supported. Services being considered for the 5G communication system include enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliability Low Latency Communication (URLLC).

[0048] eMBB aims to provide data transmission speeds that are superior to those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must be able to provide a peak data rate of 20 Gbps in the downlink and 10 Gbps in the uplink from the perspective of a single base station. Furthermore, while providing these peak data rates, the 5G communication system must also provide an increased user-perceived data rate. To satisfy these requirements, it necessitates improvements in various transmission and reception technologies, including enhanced Multi-Input Multi-Output (MIMO) transmission technology. Additionally, while LTE transmits signals using a maximum bandwidth of 20 MHz in the 2 GHz band, the 5G communication system can meet the data transmission speeds required by using a frequency bandwidth wider than 20 MHz in frequency bands of 3–6 GHz or above 6 GHz.

[0049] Simultaneously, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide IoT, mMTC requires support for a large number of terminal connections within a cell, improved terminal coverage, enhanced battery life, and reduced terminal costs. Since IoT devices are attached to various sensors and equipment to provide communication functions, the system must be able to support a large number of terminals within a cell (e.g., 1,000,000 terminals / km²). Furthermore, due to the nature of the service, terminals supporting mMTC are likely to be located in dead zones not covered by cells, such as building basements; therefore, they may require wider coverage compared to other services provided by 5G communication systems. Terminals supporting mMTC must consist of low-cost devices, and since it is difficult to frequently replace terminal batteries, a very long battery life of 10 to 15 years may be required.

[0050] Finally, URLLC is a mission-critical cellular-based wireless communication service. For example, consider services used for remote control of robots or machinery, industrial automation, unmanned aerial vehicles, remote health care, and emergency alerts. Therefore, the communication provided by URLLC must offer very low latency and very high reliability. For instance, services supporting URLLC must satisfy an air interface latency of less than 0.5 milliseconds, and simultaneously 10 -5The following packet error rate requirements apply. Therefore, for services supporting URLLC, 5G systems must provide a Transmit Time Interval (TTI) smaller than other services, and at the same time, design considerations may be required to allocate a wide resource in the frequency band to ensure the reliability of the communication link.

[0051] The three 5G services, namely eMBB, URLLC, and mMTC, can be multiplexed and transmitted within a single system. In this case, different transmission and reception techniques and parameters may be used between the services to satisfy the different requirements of each service. Of course, 5G is not limited to the three services mentioned above.

[0052] a / b can be understood as at least one of a or b.

[0053] The terms used in this invention have been selected based on currently widely used general terms, taking into account their functions within the invention; however, these terms may vary depending on the intent of those skilled in the art, case law, the emergence of new technologies, etc. Additionally, in specific cases, terms have been arbitrarily selected by the applicant, and in such cases, their meanings will be described in detail in the relevant description of the invention. Therefore, the terms used in this invention should be defined not merely by their names, but based on their meanings and the overall content of the invention.

[0054] When a part of a specification is described as "including" a certain component, this means that, unless specifically stated otherwise, it does not exclude other components but may include additional components. Furthermore, terms such as "...part" or "module" as used in the specification refer to a unit that processes at least one function or operation, and this may be implemented in hardware or software, or as a combination of hardware and software.

[0055] Additionally, the description 'at least one of A, B, and C' means that it may be any one of 'A', 'B', 'C', 'A and B', 'A and C', 'B and C', and 'A, B, and C'.

[0056] It should be understood that the combinations of blocks and flowcharts in each flowchart can be executed by one or more computer programs containing computer-executable instructions. One or more computer programs may be stored entirely in a single memory or may be partitioned and stored in multiple different memories.

[0057] All functions or operations described in this document may be processed by a single processor or a combination of processors. A single processor or a combination of processors is a circuitry that performs processing and may include circuitry such as an AP (Application Processor), CP (Communication Processor), GPU (Graphical Processing Unit), NPU (Neural Processing Unit), MPU (Microprocessor Unit), SoC (System on Chip), IC (Integrated Chip), etc.

[0058] A processor may include various processing circuits and / or multiple processors. For example, the term “processor” as used herein, including in the claims, may include at least one processor and various processing circuits. In the at least one processor, one or more processors may be configured to perform the various functions described herein individually and / or collectively in a distributed manner. As used herein, “processor,” “at least one processor,” and “one or more processors” may be configured to perform various functions. However, these terms cover, without limitation, situations where one processor performs some of the functions and other processor(s) perform other parts of the functions, and situations where a single processor can perform all functions. Additionally, at least one processor may include a combination of processors performing various functions of the disclosed functions in a distributed manner. At least one processor may execute program instructions to achieve or perform various functions.

[0059] The following describes embodiments with reference to the attached drawings so that those skilled in the art can easily implement the present invention. However, the present invention may be embodied in various different forms and is not limited to the embodiments described herein. Furthermore, in order to clearly explain the present invention in the drawings, parts unrelated to the explanation have been omitted, and similar parts throughout the specification are denoted by similar reference numerals.

[0060] [NR Time-Frequency Resources]

[0061] The frame structure of the 5G system will be explained in more detail below with reference to the drawings.

[0062] Figure 1 is a diagram illustrating the basic structure of the time-frequency domain, which is a wireless resource domain where data or control channels are transmitted in a 5G system.

[0063] The horizontal axis of FIG. 1 represents the time domain, and the vertical axis represents the frequency domain. In the time and frequency domains, the basic unit of a resource is a resource element (RE, 101), which can be defined as one OFDM symbol (102) on the time axis and one subcarrier (103) on the frequency axis. In the frequency domain (For example, 12) consecutive REs can form a single resource block (Resource Block, RB, 104). In the time axis, a single subframe (110) may contain multiple OFDM symbols (102). For example, the length of one subframe may be 1 ms.

[0064] FIG. 2 is a drawing illustrating a frame, subframe, and slot structure in a wireless communication system according to one embodiment of the present disclosure.

[0065] FIG. 2 illustrates an example of a frame (200), subframe (201), and slot (202) structure. One frame (200) can be defined as 10ms. One subframe (201) can be defined as 1ms, and thus one frame (200) can be composed of a total of 10 subframes (201). One slot (202, 203) can be defined as 14 OFDM symbols (i.e., the number of symbols per slot ( =14)). A subframe (201) may be composed of one or more slots (202, 203), and the number of slots (202, 203) per subframe (201) may vary depending on the setting value μ (204, 205) for the subcarrier spacing. In one example of FIG. 2, cases where μ=0 (204) and μ=1 (205) are shown as the setting value for the subcarrier spacing. When μ=0 (204), a subframe (201) may be composed of one slot (202), and when μ=1 (205), a subframe (201) may be composed of two slots (203). That is, the number of slots per subframe ( ) may vary, and accordingly, the number of slots per frame ( ) may vary. Depending on each subcarrier spacing setting μ and It can be defined by [Table 1] below.

[0066] [Table 1]

[0067]

[0068] [Bandwidth Section (BWP)]

[0069] Next, the Bandwidth Part (BWP) setting in the 5G communication system will be explained in detail with reference to the drawing.

[0070] FIG. 3 is a drawing illustrating an example of a bandwidth portion setting in a wireless communication system according to one embodiment of the present disclosure.

[0071] FIG. 3 shows an example in which the terminal bandwidth (UE bandwidth) (300) is configured into two bandwidth portions, namely bandwidth portion #1 (BWP#1) (301) and bandwidth portion #2 (BWP#2) (302). The base station may configure one or more bandwidth portions for the terminal and may configure the information in [Table 2] below for each bandwidth portion.

[0072] [Table 2]

[0073]

[0074] Of course, the above examples are not limited, and various parameters related to bandwidth portions may be configured for the terminal in addition to the above configuration information. The above information may be transmitted by the base station to the terminal via higher-layer signaling, for example, Radio Resource Control (RRC) signaling. At least one of the configured bandwidth portions may be activated. Whether a configured bandwidth portion is activated may be transmitted semi-statically from the base station to the terminal via RRC signaling or dynamically via DCI.

[0075] According to some embodiments, prior to the RRC connection, the terminal may receive an Initial Bandwidth Part (Initial BWP) for initial connection from the base station via a Master Information Block (MIB). More specifically, during the initial connection phase, the terminal may receive configuration information for a Control Resource Set (CORESET) and a Search Space via the MIB, through which a PDCCH can be transmitted to receive system information required for initial connection (which may correspond to Remaining System Information (RMSI) or System Information Block 1 (SIB1)). The Control Resource Set and Search Space configured via the MIB may each be considered as Identity (ID) 0. The base station may notify the terminal via the MIB of configuration information, such as frequency allocation information, time allocation information, and numerology, for Control Resource Set #0. Additionally, the base station may notify the terminal via the MIB of configuration information regarding the monitoring period and monitoring occasion for Control Resource Set #0, i.e., configuration information for Search Space #0. The terminal may consider the frequency region set as control region #0 obtained from the MIB as the initial bandwidth portion for initial access. In this case, the identifier (ID) of the initial bandwidth portion may be considered as 0.

[0076] The settings for the bandwidth portion supported by the above 5G can be used for various purposes.

[0077] According to some embodiments, if the bandwidth supported by the terminal is smaller than the system bandwidth, this can be supported through the bandwidth portion setting. For example, by setting the frequency position of the bandwidth portion (setting information 2) to the terminal, the terminal can transmit and receive data at a specific frequency position within the system bandwidth.

[0078] In addition, according to some embodiments, a base station may set multiple bandwidth portions for a terminal for the purpose of supporting different numerologies. For example, to support data transmission and reception using both a 15 kHz subcarrier interval and a 30 kHz subcarrier interval for a terminal, two bandwidth portions may be set to subcarrier intervals of 15 kHz and 30 kHz, respectively. Different bandwidth portions may be frequency division multiplexed (FDM), and when data transmission and reception is to be performed with a specific subcarrier interval, the bandwidth portion set to that subcarrier interval may be activated.

[0079] In addition, according to some embodiments, a base station may set a bandwidth portion having different bandwidth sizes for the purpose of reducing the power consumption of the terminal. For example, if the terminal supports a very large bandwidth, such as 100 MHz, and always transmits and receives data using that bandwidth, very large power consumption may occur. In particular, in a situation where there is no traffic, performing monitoring of an unnecessary downlink control channel using a large bandwidth of 100 MHz can be very inefficient in terms of power consumption. To reduce the power consumption of the terminal, the base station may set a bandwidth portion of a relatively small bandwidth, such as 20 MHz, for the terminal. In a situation where there is no traffic, the terminal can perform monitoring operations in the 20 MHz bandwidth portion, and when data is generated, it can transmit and receive data using the 100 MHz bandwidth portion according to the instructions of the base station.

[0080] In the method for configuring the above bandwidth portion, terminals prior to RRC connection (Connected) can receive configuration information for the Initial Bandwidth Part (Initial BWP) through the MIB during the initial connection phase. More specifically, the terminal can receive a configuration of a control area (i.e., CORESET) for a downlink control channel through which a DCI scheduling a System Information Block (SIB) can be transmitted from the MIB of the Physical Broadcast Channel (PBCH). The bandwidth of the control area configured by the MIB can be considered as the Initial Bandwidth Part, and through the configured Initial Bandwidth Part, the terminal can receive the Physical Downlink Shared Channel (PDSCH) through which the SIB is transmitted. In addition to the purpose of receiving the SIB, the Initial Bandwidth Part may also be utilized for other system information (OSI), paging, and random access.

[0081] [Bandwidth Section (BWP) Change]

[0082] When one or more bandwidth parts are set for a terminal, the base station may instruct the terminal to change (or switch, transition) the bandwidth part using the Bandwidth Part Indicator field within the DCI. For example, in FIG. 3, if the currently active bandwidth part of the terminal is Bandwidth Part #1 (301), the base station may instruct the terminal to Bandwidth Part #2 (302) using the Bandwidth Part Indicator within the DCI, and the terminal may perform a bandwidth part change to Bandwidth Part #2 (302) indicated by the received Bandwidth Part Indicator within the DCI.

[0083] As mentioned above, since DCI-based bandwidth portion changes can be directed by the DCI scheduling PDSCH or PUSCH, when a terminal receives a bandwidth portion change request, it must be able to receive or transmit the PDSCH or PUSCH scheduled by the corresponding DCI in the changed bandwidth portion without difficulty. To this end, the standard specifies the delay time (T) required when changing the bandwidth portion. BWP The requirements for ) have been specified and can be defined, for example, as shown in [Table 3] below.

[0084] [Table 3]

[0085]

[0086] The requirements for bandwidth portion change delay time support Type 1 or Type 2 depending on the terminal's capability. The terminal can report the supported bandwidth portion delay time type to the base station.

[0087] In accordance with the aforementioned requirements for bandwidth portion change delay time, if the terminal receives a DCI containing a bandwidth portion change indicator in slot n, the terminal performs a change to the new bandwidth portion indicated by the bandwidth portion change indicator in slot n+T BWP Completion can be performed at a time no later than the new bandwidth portion, and transmission and reception for the data channel scheduled by the corresponding DCI can be performed in the changed new bandwidth portion. If the base station intends to schedule a data channel in the new bandwidth portion, the terminal's bandwidth portion change delay time (T BWP By considering ), time-domain resource allocation for a data channel can be determined. That is, when a base station schedules a data channel with a new bandwidth portion, in the method for determining time-domain resource allocation for a data channel, the data channel can be scheduled after the bandwidth portion change delay time. Accordingly, the terminal [is notified] that the DCI instructing the bandwidth portion change is the bandwidth portion change delay time (TBWP You may not expect to indicate a slot offset (K0 or K2) value smaller than )

[0088] If a terminal receives a DCI (e.g., DCI format 1_1 or 0_1) instructing a change in the bandwidth portion, the terminal may not perform any transmission or reception during a time interval corresponding to the time interval from the third symbol of the slot in which the PDCCH containing the said DCI was received to the beginning of the slot indicated by the slot offset value (K0 or K2) indicated by the time domain resource allocation indicator field within the said DCI. For example, if a terminal receives a DCI instructing a change in the bandwidth portion in slot n, and the slot offset value indicated by the said DCI is K, the terminal may not perform any transmission or reception from the third symbol of slot n to the symbol before slot n+K (i.e., the last symbol of slot n+K-1).

[0089] [CA / DC Related]

[0090] FIG. 4 is a diagram illustrating the wireless protocol structure of a base station and a terminal in a single cell, carrier aggregation, dual connectivity situation according to one embodiment of the present disclosure.

[0091] Referring to Fig. 4, the wireless protocol of the next-generation mobile communication system consists of NR SDAP (Service Data Adaptation Protocol S25, S70), NR PDCP (Packet Data Convergence Protocol S30, S65), NR RLC (Radio Link Control S35, S60), and NR MAC (Medium Access Control S40, S55) at the terminal and the NR base station, respectively.

[0092] The main functions of NR SDAP (S25, S70) may include some of the following functions.

[0093] - User data transfer function (transfer of user plane data)

[0094] - Mapping function between a QoS flow and a DRB for both DL and UL for uplink and downlink

[0095] - Marking QoS flow ID for uplink and downlink (marking QoS flow ID in both DL and UL packets)

[0096] - Function to map reflective QoS flow to data bearers for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

[0097] Regarding the SDAP layer device, the terminal may receive a setting via an RRC message indicating whether to use the header of the SDAP layer device or the functions of the SDAP layer device for each PDCP layer device, for each bearer, or for each logical channel. If the SDAP header is set, the terminal may be instructed to update or reset the mapping information for the uplink and downlink QoS flows and data bearers to the NAS reflective QoS and AS reflective QoS 1-bit indicators of the SDAP header. The SDAP header may include QoS flow ID information indicating QoS. The QoS information may be used for data processing priority, scheduling information, etc., to support seamless service.

[0098] The main functions of NR PDCP (S30, S65) may include some of the following functions.

[0099] - Header compression and decompression features (ROHC only)

[0100] - User data transfer function (Transfer of user data)

[0101] - Sequential delivery function (In-sequence delivery of upper layer PDUs)

[0102] - Out-of-sequence delivery of upper layer PDUs

[0103] - Reordering function (PDCP PDU reordering for reception)

[0104] - Duplicate detection function (Duplicate detection of lower layer SDUs)

[0105] - Retransmission of PDCP SDUs

[0106] - Encryption and decryption functions (Ciphering and deciphering)

[0107] - Timer-based SDU discard in uplink.

[0108] In the above, the reordering function of the NR PDCP device refers to a function that reorders PDCP PDUs received from a lower layer in order based on the PDCP SN (sequence number), and may include a function that transmits data to an upper layer in the reordered order. Alternatively, the reordering function of the NR PDCP device may include a function that transmits immediately without considering the order, a function that records lost PDCP PDUs by reordering, a function that reports the status of lost PDCP PDUs to the transmitting side, and a function that requests retransmission of lost PDCP PDUs.

[0109] The main functions of NR RLC(S35, S60) may include some of the following functions.

[0110] - Data transfer function (Transfer of upper layer PDUs)

[0111] - Sequential delivery function (In-sequence delivery of upper layer PDUs)

[0112] - Out-of-sequence delivery of upper layer PDUs

[0113] - ARQ function (Error Correction through ARQ)

[0114] - Concatenation, segmentation, and reassembly functions of RLC SDUs

[0115] - Re-segmentation function (Re-segmentation of RLC data PDUs)

[0116] - Reordering function (Reordering of RLC data PDUs)

[0117] - Duplicate detection

[0118] - Error detection function (Protocol error detection)

[0119] - RLC SDU discard function

[0120] RLC re-establishment function

[0121] In the above, the in-sequence delivery function of the NR RLC device refers to the function of delivering RLC SDUs received from a lower layer to an upper layer in order. The in-sequence delivery function of the NR RLC device may include a function of reassembling and delivering the RLC SDUs when the original RLC SDU is received divided into multiple RLC SDUs, a function of rearranging the received RLC PDUs based on an RLC SN (sequence number) or PDCP SN (sequence number), a function of recording lost RLC PDUs by rearranging the order, a function of reporting the status of lost RLC PDUs to the transmitting side, and a function of requesting retransmission of lost RLC PDUs. The in-sequence delivery function of the NR RLC device may include a function to deliver only the RLC SDUs prior to the lost RLC SDU in order to the upper layer if there is a lost RLC SDU, or a function to deliver all RLC SDUs received before the timer started in order to the upper layer if a predetermined timer has expired even if there is a lost RLC SDU. Alternatively, the in-sequence delivery function of the NR RLC device may include a function to deliver all RLC SDUs received up to the present in order to the upper layer if a predetermined timer has expired even if there is a lost RLC SDU.In addition, the RLC PDUs described above may be processed in the order they are received (regardless of the order of sequence numbers, in the order of arrival) and delivered to the PDCP device out of order (out-of-sequence delivery). In the case of segments, segments stored in a buffer or to be received later may be received, reconstructed into a single complete RLC PDU, processed, and delivered to the PDCP device. The NR RLC layer may not include a concatenation function, and this function may be performed by the NR MAC layer or replaced by the multiplexing function of the NR MAC layer.

[0122] In the above, the out-of-sequence delivery function of the NR RLC device refers to a function of delivering RLC SDUs received from a lower layer directly to an upper layer regardless of order. It may include a function of reassembling and delivering RLC SDUs when a single RLC SDU is received divided into multiple RLC SDUs, and may include a function of storing the RLC SN or PDCP SN of the received RLC PDUs and sorting the order to record the lost RLC PDUs.

[0123] The NR MAC (S40, S55) can be connected to multiple NR RLC layer devices configured in a terminal, and the main functions of the NR MAC may include some of the following functions.

[0124] - Mapping function (Mapping between logical channels and transport channels)

[0125] - Multiplexing and demultiplexing functions (Multiplexing / demultiplexing of MAC SDUs)

[0126] - Scheduling information reporting function

[0127] - HARQ function (Error correction through HARQ)

[0128] - Priority handling between logical channels of one UE

[0129] - Priority handling between UEs by means of dynamic scheduling

[0130] - MBMS service identification function

[0131] - Transport format selection function

[0132] - Padding

[0133] The NR PHY layer (S45, S50) can perform the operation of channel coding and modulating upper layer data, creating OFDM symbols and transmitting them to the wireless channel, or demodulating OFDM symbols received through the wireless channel and channel decoding them to transmit them to the upper layer.

[0134] The above wireless protocol structure may vary in detail depending on the carrier (or cell) operation method. For example, when a base station transmits data to a terminal based on a single carrier (or cell), the base station and the terminal use a protocol structure having a single structure for each layer, as shown in S00. On the other hand, when a base station transmits data to a terminal based on Carrier Aggregation (CA) using multiple carriers in a single TRP, the base station and the terminal use a protocol structure that has a single structure up to the RLC, as shown in S10, but multiplexes the PHY layer through the MAC layer. As another example, when a base station transmits data to a terminal based on Dual Connectivity (DC) using multiple carriers in multiple TRPs, the base station and the terminal use a protocol structure that has a single structure up to the RLC, as shown in S20, but multiplexes the PHY layer through the MAC layer.

[0135] [Unified TCI state]

[0136] The following describes a method for directing and activating a single TCI state based on the unified TCI scheme. The unified TCI scheme refers to a method of managing transmit and receive beams by integrating the TCI state method used for downlink reception and the spatial relation info method used for uplink transmission, which were distinguished in the existing Rel-15 and Rel-16, into a single TCI state. Therefore, when a terminal receives a directive from a base station based on the unified TCI scheme, it can perform beam management using the TCI state for uplink transmission as well. If the terminal receives a TCI-State from the base station, which is a higher-layer signaling with the tci-stateId-r17, the terminal can perform operations based on the unified TCI scheme using that TCI-State. The TCI-State can exist in two forms: a joint TCI state or a separate TCI state.

[0137] The first form is a joint TCI state, and the terminal can receive instructions from the base station regarding the TCI state to be applied for both uplink transmission and downlink reception through a single TCI-State. If the terminal receives a TCI-State based on the joint TCI state, the terminal can receive instructions regarding parameters to be used for downlink channel estimation using the RS corresponding to qcl-Type1 within the joint TCI state-based TCI-State, and parameters to be used as a downlink reception beam or reception filter using the RS corresponding to qcl-Type2. If the terminal receives a TCI-State based on the joint TCI state, the terminal can receive instructions regarding parameters to be used as an uplink transmission beam or transmission filter using the RS corresponding to qcl-Type2 within the joint DL / UL TCI state-based TCI-State. In this case, if the terminal receives a joint TCI state, the terminal can apply the same beam to both uplink transmission and downlink reception.

[0138] The second form is a separate TCI state, and the terminal can individually receive instructions from the base station for an UL TCI state to be applied for uplink transmission and a DL TCI state to be applied for downlink reception. If the terminal is instructed with an UL TCI state, the terminal can be instructed with parameters to be used as an uplink transmission beam or transmission filter using a reference RS or source RS set within the corresponding UL TCI state. If the terminal is instructed with a DL TCI state, the terminal can be instructed with parameters to be used for downlink channel estimation using an RS corresponding to qcl-Type1 set within the corresponding DL TCI state, and parameters to be used as a downlink reception beam or reception filter using an RS corresponding to qcl-Type2.

[0139] If the terminal is instructed with both a DL TCI state and a UL TCI state, the terminal may be instructed with parameters to be used as an uplink transmission beam or transmission filter using a reference RS or source RS set within the corresponding UL TCI state, parameters to be used for downlink channel estimation using an RS corresponding to qcl-Type1 set within the corresponding DL TCI state, and parameters to be used as a downlink reception beam or reception filter using an RS corresponding to qcl-Type2. In this case, if the reference RS or source RS set within the DL TCI state and the UL TCI state instructed to the terminal are different, the terminal may apply beams individually to uplink transmission and downlink reception, respectively, based on the instructed UL TCI state and DL TCI state.

[0140] A terminal can receive up to 128 upper-layer signalings for each specific bandwidth part within a specific cell from the base station for joint TCI states, and among the separate TCI states, DL TCI states can be received as upper-layer signalings for each specific bandwidth part within a specific cell, up to 64 or 128 based on terminal capability reports, and among the separate TCI states, DL TCI states and joint TCI states can use the same upper-layer signaling structure. For example, if 128 joint TCI states are set and 64 DL TCI states are set among the separate TCI states, the 64 DL TCI states can be included in the 128 joint TCI states.

[0141] Among the separate TCI states, the UL TCI state can be configured with up to 32 or 64 upper layer signalings for each specific bandwidth part within a specific cell based on terminal capability reporting, and like the relationship between the DL TCI state and the joint TCI state among the separate TCI states, the UL TCI state and the joint TCI state among the separate TCIs may also use the same upper layer signaling structure, or the UL TCI state among the separate TCIs may use a different upper layer signaling structure from the joint TCI state and the DL TCI state among the separate TCIs.

[0142] Using different or identical upper-layer signaling structures in this way may be defined in the specifications, or may be distinguished through another upper-layer signaling configured by the base station based on a terminal capability report containing information on which of the two usage modes the terminal can support.

[0143] The terminal can receive instructions regarding transmit / receive beams in an integrated TCI manner by utilizing one of the joint TCI state and separate TCI state configured by the base station. The terminal can receive a configuration from the base station via upper-layer signaling regarding whether to use one of the joint TCI state or separate TCI state.

[0144] The terminal receives instructions related to the transmit / receive beam using one of the selected methods among the joint TCI state and the separate TCI state through upper layer signaling, and at this time, there may be two types of transmit / receive beam instructions from the base station: a MAC-CE based instruction method and a MAC-CE based activation and DCI based instruction method.

[0145] If a terminal receives instructions related to transmit / receive beams using the joint TCI state method through upper layer signaling, the terminal can perform a transmit / receive beam application operation by receiving a MAC-CE indicating the joint TCI state from the base station, and the base station can schedule the terminal to receive a PDSCH containing the corresponding MAC-CE through the PDCCH. If there is only one joint TCI state included in the MAC-CE, the terminal can determine the uplink transmit beam or transmit filter and the downlink receive beam or receive filter using the indicated joint TCI state starting 3 ms after the PUCCH transmission containing HARQ-ACK information indicating whether reception of the PDSCH including the MAC-CE was successful. If there are two or more joint TCI states included in the MAC-CE, the terminal can confirm that the multiple joint TCI states indicated by the MAC-CE correspond to each code point in the TCI state field of DCI format 1_1 or 1_2 starting 3 ms after the PUCCH transmission containing HARQ-ACK information indicating whether reception of the PDSCH including the MAC-CE was successful, and activate the indicated joint TCI states. Subsequently, the terminal can receive DCI format 1_1 or 1_2 and apply the one joint TCI state indicated by the TCI state field within the DCI to the uplink transmit and downlink receive beams. In this case, DCI format 1_1 or 1_2 may include downlink data channel scheduling information (with DL assignment) or may not include it (without DL assignment).

[0146] If a terminal receives instructions regarding transmit / receive beams using a separate TCI state method through upper layer signaling, the terminal can perform a transmit / receive beam application operation by receiving a MAC-CE from the base station that indicates a separate TCI state, and the base station can schedule the terminal to receive a PDSCH containing the MAC-CE via a PDCCH. If there is only one set of separate TCI states included in the MAC-CE, the terminal can determine the uplink transmit beam or transmit filter and the downlink receive beam or receive filter by using the separate TCI states included in the indicated set of separate TCI states starting 3 ms after the transmission of a PUCCH containing HARQ-ACK information indicating whether the PDSCH was successfully received. At this time, a separate TCI state set may refer to a single or multiple separate TCI states that a single code point of the TCI state field in DCI format 1_1 or 1_2 may have, and a separate TCI state set may include one DL TCI state, one UL TCI state, or one DL TCI state and one UL TCI state. If there are two or more separate TCI state sets included by MAC-CE, the terminal may confirm that the multiple separate TCI state sets indicated by MAC-CE correspond to each code point of the TCI state field in DCI format 1_1 or 1_2 starting 3 ms after a PUCCH transmission containing HARQ-ACK information indicating whether the PDSCH was successfully received, and activate the indicated separate TCI state sets.In this case, each code point in the TCI state field of DCI format 1_1 or 1_2 may indicate one DL TCI state, one UL TCI state, or one DL TCI state and one UL TCI state each. The terminal receives DCI format 1_1 or 1_2 and can apply the separate set of TCI states indicated by the TCI state field within the corresponding DCI to the uplink transmit and downlink receive beams. In this case, DCI format 1_1 or 1_2 may include downlink data channel scheduling information (with DL assignment) or may not include it (without DL assignment).

[0147] FIG. 5 is a diagram of the beam application time that can be considered when using an integrated TCI method in a wireless communication system according to one embodiment of the present disclosure. As described above, the terminal receives DCI format 1_1 or 1_2 from a base station that includes downlink data channel scheduling information (with DL assignment) or does not include it (without DL assignment), and can apply one joint TCI state or a set of separate TCI states indicated by the TCI state field within the DCI to the uplink transmit and downlink receive beams.

[0148] DCI format 1_1 or 1_2 with DL assignment (500): If a terminal receives DCI format 1_1 or 1_2 containing downlink data channel scheduling information from a base station (501) and indicates a set of one joint TCI state or separate TCI state based on the integrated TCI method, the terminal receives a PDSCH scheduled based on the received DCI (505) and can transmit a PUCCH containing a HARQ-ACK indicating whether the reception of the DCI and PDSCH was successful (510). At this time, the HARQ-ACK may include the meaning of whether the reception of the DCI and PDSCH was successful, and if at least one of the DCI and PDSCH is not received, the terminal can transmit a NACK, and if both are successfully received, the terminal can transmit an ACK.

[0149] DCI format 1_1 or 1_2 without DL assignment (550): If a terminal receives DCI format 1_1 or 1_2 from a base station that does not include downlink data channel scheduling information (555) and indicates one joint TCI state or a separate set of TCI states based on a combined TCI method, the terminal may assume at least one combination of the following for the DCI.

[0150] - Includes scrambled CRC using CS-RNTI.

[0151] - The value of all bits assigned to all fields used as RV (Redundancy Version) fields is 1.

[0152] - The value of all bits assigned to all fields used as MCS (Modulation and Coding Scheme) fields is 1.

[0153] - The value of all bits assigned to all fields used as NDI (New Data Indication) fields is 0.

[0154] - For FDRA (Frequency Domain Resource Allocation) Type 0, the value of all bits allocated to the FDRA field is 0; for FDRA Type 1, the value of all bits allocated to the FDRA field is 1; and for the FDRA method dynamicSwitch, the value of all bits allocated to the FDRA field is 0.

[0155] The terminal may transmit a PUCCH containing a HARQ-ACK indicating whether reception of DCI format 1_1 or 1_2, in which the above-described items are assumed, was successful (560).

[0156] For both DCI format 1_1 or 1_2 with DL assignment (500) and without DL assignment (550), if the new TCI state indicated by the DCI (501, 555) is the same as the TCI state that was previously indicated and applied to the uplink transmit and downlink receive beams, the terminal may maintain the previously applied TCI state; if the new TCI state is different from the previously indicated TCI state, the terminal may determine the application time of the joint TCI state or separate TCI state set that can be indicated from the TCI state field included in the DCI as after the first slot (520, 570) (530, 580) after a time equal to BAT (beam application time, 515, 565) after PUCCH transmission, and may use the previously indicated TCI-state until before the slot (525, 575).

[0157] For both DCI format 1_1 or 1_2 with DL assignment (500) and without DL assignment (550), the BAT can be set to upper layer signaling based on terminal capability reporting information as a specific number of OFDM symbols, and the numerology for the BAT and the first slot after the BAT can be determined based on the smallest numerology among all cells to which the joint TCI state or separate TCI state set indicated through the DCI is applied.

[0158] A terminal can apply a single joint TCI state indicated via MAC-CE or DCI to the reception of control resource sets connected to all terminal-specific search spaces, the reception of PDSCH scheduled to PDCCH transmitted from said control resource set, the transmission of PUSCH, and the transmission of all PUCCH resources.

[0159] If a separate set of TCI states indicated via MAC-CE or DCI includes a DL TCI state, the terminal can apply the separate set of TCI states to the reception of control resource sets connected to all terminal-specific search spaces, and to the reception of PDSCH scheduled to PDCCH transmitted from said control resource sets, and can apply it to all PUSCH and PUCCH resources based on the previously indicated UL TCI state.

[0160] If a separate set of TCI states indicated via MAC-CE or DCI includes one UL TCI state, the terminal can apply it to all PUSCH and PUCCH resources, and based on the previously indicated DL TCI state, it can apply it to receiving control resource sets connected to all terminal-specific search spaces, and receiving PDSCH scheduled to PDCCH transmitted from said control resource set.

[0161] If a separate set of TCI states indicated by MAC-CE or DCI includes one DL TCI state and one UL TCI state, the terminal may apply the DL TCI state to the reception of control resource sets connected to all terminal-specific search spaces and to the reception of PDSCH scheduled to PDCCH transmitted from said control resource sets, and may apply the UL TCI state to all PUSCH and PUCCH resources.

[0162] [Unified TCI state MAC-CE]

[0163] The following describes a single TCI state instruction and activation method based on an integrated TCI method. A terminal receives a PDSCH containing the following MAC-CE from a base station and, starting from the third slot after transmitting a HARQ-ACK for the PDSCH to the base station, can interpret each code point of the TCI state field in DCI format 1_1 or 1_2 based on the information within the MAC-CE received from the base station. That is, the terminal can activate each entry of the MAC-CE received from the base station to each code point of the TCI state field in DCI format 1_1 or 1_2.

[0164] FIG. 6 is a diagram showing another MAC-CE structure for activating and indicating a joint TCI state or a separate DL or UL TCI state in a wireless communication system according to one embodiment of the present disclosure. The meaning of each field within the MAC-CE structure may be as follows.

[0165] - Serving Cell ID (600): This field may indicate which serving cell the MAC-CE is to be applied to. The length of this field may be 5 bits. If the serving cell indicated by this field is included in one or more of the upper layer signalings simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, or simultaneousU-TCI-UpdateList4, the MAC-CE may be applied to all serving cells included in one or more of the lists simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, or simultaneousU-TCI-UpdateList4 that contain the serving cell indicated by this field.

[0166] - DL BWP ID (605): This field may indicate which DL BWP the MAC-CE is to be applied to, and the meaning of each code point in this field may correspond to each code point of the bandwidth part indicator in the DCI. The length of this field may be 2 bits.

[0167] - UL BWP ID (610): This field may indicate which UL BWP the MAC-CE is to be applied to, and the meaning of each code point in this field may correspond to each code point of the bandwidth part indicator in the DCI. The length of this field may be 2 bits.

[0168] - P i (615): This field may indicate whether each code point of the TCI state field in DCI format 1_1 or 1_2 has multiple TCI states or one TCI state. If P i If the value of is 1, it means that the corresponding i-th code point has multiple TCI states, which may mean that the code point can include a separate DL TCI state and a separate UL TCI state. If P i If the value of is 0, it means that the corresponding i-th code point has a single TCI state, which means that the code point may contain one of a joint TCI state, a separate DCI TCI state, or a separate UL TCI state.

[0169] - D / U (620): This field may indicate whether the TCI state ID field within the same octet is a joint TCI state, a separate DL TCI state, or a separate UL TCI state. If this field is 1, the TCI state ID field within the same octet may be a joint TCI state or a separate DL TCI state, and if this field is 0, the TCI state ID field within the same octet may be a separate UL TCI state.

[0170] - TCI state ID (625): This field may indicate a TCI state that can be identified by the upper layer signaling TCI-StateId. If the D / U field is set to 1, this field may be used to represent the TCI-StateId, which can be represented by 7 bits. If the D / U field is set to 0, the MSB (most significant bit) of this field may be considered a reserved bit, and the remaining 6 bits may be used to represent the upper layer signaling UL-TCIState-Id. The maximum number of TCI states that can be enabled is 8 for joint TCI states and 16 for separate DL or UL TCI states.

[0171] - R (630): Represents a reserved bit and can be set to 0.

[0172] Regarding the MAC-CE structure of FIG. 6 described above, the terminal may include a third octet containing fields P1, P2, ..., P8 in FIG. 6 in the MAC-CE structure, regardless of whether unifiedTCI-StateType-r17 in MIMOparam-r17 within ServingCellConfig, which is an upper layer signaling, is set to joint or separate. In this case, the terminal may perform TCI state activation using a fixed MAC-CE structure, regardless of the upper layer signaling received from the base station. As another example, regarding the MAC-CE structure of FIG. 6 described above, if unifiedTCI-StateType-r17 in MIMOparam-r17 within ServingCellConfig, which is an upper layer signaling, is set to joint, the terminal may omit the third octet containing fields P1, P2, ..., P8 in FIG. 6. In this case, the terminal can save up to 8 bits of the payload of the corresponding MAC-CE according to the upper layer signaling set by the base station. Additionally, all D / U fields located from the fourth octet to the first bit in FIG. 6 can be considered as R fields, and all corresponding R fields can be set to 0 bits.

[0173] [CSI resource configuration]

[0174] NR has a CSI framework for directing the measurement and reporting of channel state information (CSI) from a terminal at a base station. The CSI framework of NR can be composed of at least two elements: a resource setting and a report setting, and the report setting can have a connection relationship with the resource setting by referencing at least one ID of the resource setting.

[0175] According to one embodiment of the present disclosure, a resource setting may include information related to a reference signal (RS) for a terminal to measure channel state information. A base station may set at least one resource setting for the terminal. For example, the base station and the terminal may exchange signaling information such as [Table 4] to transmit information regarding the resource setting.

[0176] [Table 4]

[0177]

[0178] In [Table 4], the signaling information CSI-ResourceConfig contains information for each resource setting. According to the signaling information, each resource setting may include a resource setting index (csi-ResourceConfigId), a BWP index (bwp-ID), a resource time-axis transmission setting (resourceType), or a resource set list (csi-RS-ResourceSetList) containing at least one resource set. The resource time-axis transmission setting may be set to aperioditic transmission, semi-persistent transmission, or periodic transmission. The resource set list may be a set containing resource sets for channel measurement or a set containing resource sets for interference measurement. If the resource set list is a set containing resource sets for channel measurement, each resource set may include at least one resource, which may be a CSI reference signal (CSI-RS) resource or an index of a synchronous / broadcast channel block (SS / PBCH block, SSB). If the resource set list is a set containing resource sets for interference measurement, each resource set may include at least one interference measurement resource (CSI interference measurement, CSI-IM).

[0179] For example, if the resource set includes CSI-RS, the base station and the terminal can exchange signaling information such as [Table 5] to transmit information about the resource set.

[0180] [Table 5]

[0181]

[0182] [Table 5] The signaling information NZP-CSI-RS-ResourceSet contains information for each resource set. According to the signaling information, each resource set contains at least information regarding the resource set index (nzp-CSI-ResourceSetId) or the set of indices of the included CSI-RS (nzp-CSI-RS-Resources), and may include some information regarding the spatial domain transmission filter of the included CSI-RS resource (repetition) or whether the included CSI-RS resource is used for tracking (trs-Info).

[0183] CSI-RS can be the most representative reference signal included in the resource set. The base station and the terminal can exchange signaling information such as [Table 6] to transmit information regarding the CSI-RS resource.

[0184] [Table 6]

[0185]

[0186] In [Table 6], the signaling information NZP-CSI-RS-Resource contains information for each CSI-RS. The information included in the above signaling information NZP-CSI-RS-Resource may have the following meanings.

[0187] - nzp-CSI-RS-ResourceId: CSI-RS resource index

[0188] - resourceMapping: Resource mapping information of CSI-RS resources

[0189] - powerControlOffset: Ratio between PDSCH EPRE (Energy Per RE) and CSI-RS EPRE

[0190] - powerControlOffsetSS: Ratio between SS / PBCH block EPRE and CSI-RS EPRE

[0191] - scramblingID: Scrambling index of the CSI-RS sequence

[0192] - periodicityAndOffset: Transmission period and slot offset of the CSI-RS resource

[0193] - qcl-InfoPeriodicCSI-RS: TCI-state information if the corresponding CSI-RS is a periodic CSI-RS

[0194] The resourceMapping included in the above signaling information NZP-CSI-RS-Resource represents resource mapping information of the CSI-RS resource and may include frequency resource element (RE) mapping, number of ports, symbol mapping, CDM type, frequency resource density, and frequency band mapping information. The number of ports, frequency resource density, CDM type, and time-frequency axis RE mapping that can be configured through this may have a value set in one of the rows of [Table 7] below.

[0195] [Table 7]

[0196]

[0197] [Table 7] shows the frequency resource density, CDM type, and frequency and time axis start positions of the CSI-RS component RE pattern configurable according to the number of CSI-RS ports (X). , represents the number of frequency axis REs (k') and the number of time axis REs (l') of the CSI-RS component RE pattern. The aforementioned CSI-RS component RE pattern may be a basic unit constituting a CSI-RS resource. Through Y=1+max(k') REs on the frequency axis and Z=1+max(l') REs on the time axis, the CSI-RS component RE pattern may be composed of YZ REs. When the number of CSI-RS ports is 1 port, the CSI-RS RE location can be specified without subcarrier restrictions within the PRB (Physical Resource Block), and the CSI-RS RE location can be specified by a 12-bit bitmap. When the number of CSI-RS ports is {2, 4, 8, 12, 16, 24, 32} ports and Y=2, CSI-RS RE locations can be assigned for every two subcarriers within the PRB and can be assigned by a 6-bit bitmap. When the number of CSI-RS ports is 4 ports and Y=4, CSI-RS RE locations can be assigned for every four subcarriers within the PRB and can be assigned by a 3-bit bitmap. Similarly, time axis RE locations can be assigned by a total of 14-bit bitmaps.

[0198] [CSI report configuration]

[0199] According to one embodiment of the present disclosure, a report setting may have a connection relationship with a resource setting by referencing at least one ID of the resource setting, and the resource setting(s) having a connection relationship with the report setting provide setting information including information about a reference signal for measuring channel information. When the resource setting(s) having a connection relationship with the report setting are used for measuring channel information, the measured channel information may be used for channel information reporting according to a reporting method set in the report setting having a connection relationship.

[0200] According to one embodiment of the present disclosure, the report setting may include setting information related to the CSI reporting method. For example, a base station and a terminal may exchange signaling information such as [Table 8] to transmit information regarding the report setting.

[0201] [Table 8]

[0202]

[0203]

[0204] In [Table 8], the signaling information CSI-ReportConfig contains information for each report setting. The information included in the above signaling information CSI-ReportConfig may have the following meanings.

[0205] - reportConfigId: report setting index

[0206] - carrier: Serving cell index

[0207] - resourcesForChannelMeasurement: Resource setting index for channel measurement linked to report setting

[0208] - csi-IM-ResourcesForInterference: Resource setting index containing CSI-IM resources for interference measurement that have a connection with the report setting

[0209] - nzp-CSI-RS-ResourcesForInterference: Resource setting index containing CSI-RS resources for interference measurement that have a relationship with the report setting

[0210] - reportConfigType: Indicates the time-axis transmission settings and transmission channel of the channel report, and can have aperioditic transmission, semi-persistent PUCCH (Physical Uplink Control Channel) transmission, semi-persistent PUSCH transmission, or periodic transmission settings.

[0211] - reportQuantity: Indicates the type of channel information being reported, and may have the type of channel information when no channel report is transmitted ('none') or when channel report is transmitted ('cri-RI-PMI-CQI', 'cri-RI-i1', 'cri-RI-i1-CQI', 'cri-RI-CQI', 'cri-RSRP', 'ssb-Index-RSRP', 'cri-RI-LI-PMI-CQI'). Here, the elements included in the type of channel information refer to CQI (Channel Quality Indicator), PMI (Precoding Matric Indicator), CRI (CSI-RS Resource Indicator), SSBRI (SS / PBCH block Resource Indicator), Layer Indicator (LI), Rank Indicator (RI), and / or L1-RSRP (Reference Signal Received Power).

[0212] - reportFreqConfiguration: Indicates whether the reported channel information includes only wideband information or information for each subband; if information for each subband is included, it can have configuration information for the subband containing the channel information.

[0213] - timeRestrictionForChannelMeasurements: Whether there are time axis constraints on the reference signal for channel measurement among the reference signals referenced by the reported channel information.

[0214] - timeRestrictionForInterferenceMeasurements: Whether there are time axis constraints on the reference signal for interference measurement among the reference signals referenced by the reporting channel information.

[0215] - codebookConfig: Codebook information referenced by the reporting channel information

[0216] - groupBasedBeamReporting: Whether to group beams in channel reporting

[0217] - cqi-Table: CQI table index referenced by the reporting channel information

[0218] - subbandSize: An index indicating the subband size of the channel information

[0219] - non-PMI-PortIndication: Port mapping information referenced when reporting non-PMI channel information

[0220] When a base station instructs a channel information report through upper layer signaling or L1 signaling, the terminal can perform the channel information report by referring to the above-mentioned setting information included in the instructed report setting.

[0221] The base station may instruct the terminal to report channel state information (CSI) through upper layer signaling, including RRC (Radio Resource Control) signaling or MAC (Medium Access Control) CE (Control Element) signaling, or L1 signaling (e.g., common DCI, group-common DCI, terminal-specific DCI).

[0222] For example, a base station may instruct a terminal to report aperiodic channel information (CSI report) via upper-layer signaling or DCI using DCI format 0_1. The base station sets parameters for the terminal's aperiodic CSI report, or a plurality of CSI report trigger states, which include parameters for the CSI report, via upper-layer signaling. The parameters for the CSI report or the CSI report trigger states may include a slot interval or a set of possible slot intervals between a PDCCH containing DCI and a PUSCH containing the CSI report, a reference signal ID for measuring channel state, and the type of channel information included. When the base station instructs some of the plurality of CSI report trigger states to the terminal via DCI, the terminal reports channel information according to the CSI report settings of the report settings configured in the instructed CSI report trigger states. The channel information reporting may be performed via a PUSCH scheduled in DCI format 0_1. The time-domain resource allocation of a PUSCH containing a terminal's CSI report can be achieved through the slot interval with the PDCCH indicated via the DCI, and the indication of the starting symbol and symbol length within the slot for the time-domain resource allocation of the PUSCH. For example, the location of the slot in which the PUSCH containing the terminal's CSI report is transmitted can be indicated via the slot interval with the PDCCH indicated via the DCI, and the starting symbol and symbol length within the slot can be indicated via the time domain resource assignment field of the aforementioned DCI.

[0223] For example, a base station may instruct a terminal to send a semi-persistent CSI report via PUSCH using a DCI with DCI format 0_1. The base station may activate or deactivate the semi-persistent CSI report sent via PUSCH using a DCI scrambled with SP-CSI-RNTI. When the semi-persistent CSI report is activated, the terminal may periodically report channel information according to a set slot interval. When the semi-persistent CSI report is deactivated, the terminal may stop the periodic channel information reporting that was activated. The base station establishes a number of CSI report trigger states containing parameters for the terminal's semi-persistent CSI report or parameters for the semi-persistent CSI report through upper layer signaling. Parameters for a CSI report, or CSI report trigger states, may include a set of possible slot intervals or slot intervals between a PDCCH containing a DCI directing a CSI report and a PUSCH containing a CSI report, a slot interval between a slot where an upper-layer signaling directing a CSI report is activated and a PUSCH containing a CSI report, a slot interval period of the CSI report, and the type of channel information included. When a base station activates some of a plurality of CSI report trigger states or some of a plurality of report settings to a terminal via upper-layer signaling or DCI, the terminal may report channel information according to the report setting included in the directed CSI report trigger state or the CSI report setting configured in the activated report setting.The above channel information reporting can be performed through a PUSCH that is semi-continuously scheduled in DCI format 0_1 ​​scrambled with SP-CSI-RNTI. Time-axis resource allocation for a PUSCH containing a terminal's CSI report can be achieved through the slot interval period of the CSI report, the slot interval with the slot where upper-layer signaling is activated, the slot interval with the PDCCH indicated via DCI, and the indication of the start symbol and symbol length within the slot for time-axis resource allocation of the PUSCH. For example, the location of the slot in which the PUSCH containing the terminal's CSI report is transmitted can be indicated through the slot interval with the PDCCH indicated via DCI, and the start symbol and symbol length within the slot can be indicated through the time domain resource assignment field of the aforementioned DCI format 0_1.

[0224] For example, a base station may instruct a terminal to transmit a semi-persistent CSI report via PUCCH through upper-layer signaling such as MAC-CE. Through the MAC-CE signaling, the base station may activate or deactivate the semi-persistent CSI report transmitted via PUCCH. When the semi-persistent CSI report is activated, the terminal may periodically report channel information according to a set slot interval. When the semi-persistent CSI report is deactivated, the terminal may stop the periodic channel information reporting that was activated. The base station sets parameters for the terminal's semi-persistent CSI report through upper-layer signaling. The parameters for the CSI report may include the PUCCH resource to which the CSI report is transmitted, the slot interval period of the CSI report, and the type of channel information included. The terminal may transmit the CSI report via PUCCH. Alternatively, if the PUCCH for the CSI report overlaps with the PUSCH, the CSI report can be transmitted via the PUSCH. The location of the PUCCH transmission slot containing the CSI report is indicated by the slot interval period of the CSI report set through upper-layer signaling, and the slot interval between the slot where the upper-layer signaling is activated and the PUCCH containing the CSI report. The starting symbol and symbol length within the slot can be indicated by the starting symbol and symbol length assigned to the PUCCH resource set through upper-layer signaling.

[0225] For example, a base station may instruct a terminal to issue a periodic CSI report through upper-layer signaling. The base station may enable or disable the periodic CSI report through upper-layer signaling, including RRC signaling. When the periodic CSI report is enabled, the terminal may periodically report channel information according to the configured slot interval. When the periodic CSI report is disabled, the terminal may stop the periodic channel information reporting that was enabled. The base station establishes a report setting containing parameters for the terminal's periodic CSI report through upper-layer signaling. The parameters for the CSI report may include the PUCCH resource setting for the CSI report, the slot interval between the slot where the upper-layer signaling instructing the CSI report is enabled and the PUCCH containing the CSI report, the slot interval period of the CSI report, a reference signal ID for measuring channel status, and the type of channel information included. The terminal may transmit the CSI report via the PUCCH. Alternatively, if the PUCCH for the CSI report overlaps with the PUSCH, the CSI report can be transmitted via the PUSCH. The slot location where the PUCCH containing the CSI report is transmitted is indicated by the slot interval period of the CSI report set through upper-layer signaling, and the slot interval between the slot where the upper-layer signaling is activated and the PUCCH containing the CSI report; furthermore, the starting symbol and symbol length within the slot can be indicated by the starting symbol and symbol length assigned to the PUCCH resource set through upper-layer signaling.

[0226] Regarding the aforementioned CSI report settings (CSI-ReportConfig), each report setting CSI-ReportConfig can be associated with a single downlink (DL) bandwidth portion identified by the upper-layer parameter bandwidth portion identifier (bwp-id) given by the CSI-ResourceConfig, which is associated with the corresponding report setting. As for the time domain reporting operation for each report setting CSI-ReportConfig, 'Aperiodic', 'Semi-Persistent', and 'Periodic' methods are supported, and these can be configured from the base station to the terminal by the reportConfigType parameter set from the upper layer. The semi-persistent CSI reporting methods support 'PUCCH-based semi-persistent (semi-PersistentOnPUCCH)' and 'PUSCH-based semi-persistent (semi-PersistentOnPUSCH)'. In the case of a periodic or semi-permanent CSI reporting method, the terminal may receive a PUCCH or PUSCH resource to transmit the CSI from the base station via upper layer signaling. The period and slot offset of the PUCCH or PUSCH resource to transmit the CSI may be given as the numerology of the uplink (UL) bandwidth portion configured for transmitting the CSI report. In the case of a non-periodic CSI reporting method, the terminal may receive a PUSCH resource to transmit the CSI scheduled from the base station via L1 signaling (the aforementioned DCI format 0_1).

[0227] For the aforementioned CSI resource setting (CSI-ResourceConfig), each CSI resource setting CSI-ReportConfig is S( 1) It may include CSI resource sets (given by the upper-level parameter csi-RS-ResourceSetList). The CSI resource set list may consist of non-zero power (NZP) CSI-RS resource sets and SS / PBCH block sets, or may consist of CSI-interference measurement (CSI-IM) resource sets. Each CSI resource setting may be located in a downlink (DL) bandwidth portion identified by the upper-level parameter bwp-id, and the CSI resource setting may be associated with a CSI reporting setting in the same downlink bandwidth portion. The time domain operation of the CSI-RS resources within the CSI resource setting may be set to one of 'non-periodic', 'periodic', or 'semi-permanent' by the upper-level parameter resourceType. For periodic or semi-permanent CSI resource settings, the number of CSI-RS resource sets may be limited to S=1, and the set period and slot offset may be given by the numerology of the downlink bandwidth portion identified by bwp-id. The terminal may receive one or more CSI resource settings for channel or interference measurement from the base station via upper layer signaling, and may include, for example, the following CSI resources.

[0228] - CSI-IM resources for interference measurement

[0229] - NZP CSI-RS resources for interference measurement

[0230] - NZP CSI-RS resources for channel measurement

[0231] For CSI-RS resource sets associated with a resource setting where the upper-level parameter resourceType is set to 'Aperiodic', 'Periodic', or 'Semi-permanent', the Trigger State for a CSI reporting setting where reportType is set to 'Aperiodic' and the resource setting for channel or interference measurements for one or more component cells (CC) can be set as the upper-level parameter CSI-AperiodicTriggerStateList.

[0232] Non-periodic CSI reporting of the terminal can be performed using PUSCH, periodic CSI reporting can be performed using PUCCH, and semi-permanent CSI reporting can be performed using PUSCH when triggered or activated by DCI, and using PUCCH after being activated by the MAC control element (MAC CE). As described above, CSI resource settings can also be configured as non-periodic, periodic, or semi-permanent. Combinations between CSI reporting settings and CSI resource settings can be supported based on [Table 9] below.

[0233] [Table 9]

[0234]

[0235] Aperiodic CSI reporting can be triggered by the "CSI request" field of the aforementioned DCI format 0_1, which corresponds to the scheduling DCI for PUSCH. The terminal can monitor PDCCH, obtain DCI format 0_1, and obtain scheduling information and CSI request indicators for PUSCH. The CSI request indicator can be set to NTS (=0, 1, 2, 3, 4, 5, or 6) bits and can be determined by the upper layer signaling (reportTriggerSize). One trigger state among one or more aperiodic CSI reporting trigger states that can be set by the upper layer signaling (CSI-AperiodicTriggerStateList) can be triggered by the CSI request indicator.

[0236] - If all bits of the CSI request field are 0, this may mean that a CSI report is not requested.

[0237] - If the number of CSI trigger states (M) in the configured CSI-AperiodicTriggerStateLite is greater than 2NTs-1, then M CSI trigger states can be mapped to 2NTs-1 according to the selected mapping relationship, and one of the trigger states of 2NTs-1 can be indicated as a CSI request field.

[0238] - If the number of CSI trigger states (M) in the configured CSI-AperiodicTriggerStateLite is less than or equal to 2NTs-1, one of the M CSI trigger states may be indicated as a CSI request field.

[0239] The following [Table 10] shows an example of the relationship between CSI request indicators and CSI trigger states that can be indicated by those indicators.

[0240] [Table 10]

[0241]

[0242] For a CSI resource within a CSI trigger state triggered by a CSI request field, the terminal can perform a measurement and generate a CSI therefrom (including at least one of the aforementioned CQI, PMI, CRI, SSBRI, LI, RI, or L1-RSRP, etc.). The terminal can transmit the acquired CSI using a PUSCH scheduled by the corresponding DCI format 0_1. When the 1 bit corresponding to the uplink data indicator (UL-SCH indicator) in DCI format 0_1 ​​indicates "1", the uplink data (UL-SCH) and the acquired CSI can be multiplexed and transmitted to the PUSCH resource scheduled by DCI format 0_1. If the 1 bit corresponding to the uplink data indicator (UL-SCH indicator) in DCI format 0_1 ​​indicates "0", CSI can be mapped and transmitted without uplink data (UL-SCH) to the PUSCH resource scheduled by DCI format 0_1.

[0243] Figure 7 is a diagram illustrating an example of a non-periodic CSI reporting method.

[0244] In one example (700) of FIG. 7, the terminal can monitor PDCCH (701) to obtain DCI format 0_1, from which it can obtain scheduling information and CSI request information for PUSCH (705). The terminal can obtain resource information for CSI-RS (702) to be measured from the received CSI request indicator. The terminal can determine at what point in time to perform a measurement on the CSI-RS (702) resource being transmitted based on the time when it receives the DCI format 0_1 ​​and the parameter (the aforementioned aperiodicTriggeringOffset) for the offset (703) within the CSI resource set setting (e.g., NZP CSI-RS resource set setting (NZP-CSI-RS-ResourceSet)). More specifically, the terminal may receive the offset value X of the parameter aperiodicTriggeringOffset within the NZP-CSI-RS resource set setting as an upper layer signaling from the base station, and the set offset value X may represent the offset between the slot in which the DCI triggering the non-periodic CSI report is received and the slot in which the CSI-RS resource is transmitted. For example, the aperiodicTriggeringOffset parameter value and the offset value X may have a mapping relationship as described in [Table 11] below.

[0245] [Table 11]

[0246]

[0247] In one example (700) of FIG. 7, an example is shown in which the aforementioned offset value is set to X=0. In this case, the terminal can receive CSI-RS (702) in a slot (corresponding to slot 0 (706) in FIG. 7) that receives DCI format 0_1 ​​that triggers a non-periodic CSI report, and can report the CSI information measured by the received CSI-RS to the base station via PUSCH (705). The terminal can obtain scheduling information for PUSCH (705) for CSI reporting (information corresponding to each field of the aforementioned DCI format 0_1) from DCI format 0_1. For example, the terminal can obtain information about the slot to transmit PUSCH (705) from the aforementioned time domain resource allocation information for PUSCH (705) in DCI format 0_1. In one example (700) of FIG. 7, the terminal obtains a K2 value (704) corresponding to a slot offset value for PDCCH-to-PUSCH as 3, and accordingly, PUSCH (705) can be transmitted from slot 3 (709), which is 3 slots away from slot 0 (706), at the time when PDCCH (701) is received among slots 0 to 3 (706, 707, 708, 709).

[0248] In one example (710) of FIG. 7, the terminal can monitor the PDCCH (711) to obtain DCI format 0_1, from which it can obtain scheduling information and CSI request information for the PUSCH (715). The terminal can obtain resource information for the CSI-RS (712) to be measured from the received CSI request indicator. One example (710) of FIG. 7 shows an example in which the offset value (713) for the aforementioned CSI-RS is set to X=1. In this case, the terminal can receive the CSI-RS (712) in slot 1 (717), which is the next slot after the slot (corresponding to slot 0 (716) in FIG. 7) that received the DCI format 0_1 ​​triggering the non-periodic CSI report. Additionally, the terminal has obtained a K2 value (714) of 3, and can report the CSI information measured by the received CSI-RS to the base station via PUSCH (715) at slot 3 (719), which is 3 slots away from slot 0 (716), at the time of receiving PDCCH (711) among slots 0 to 3 (716, 717, 718, 719).

[0249] Aperiodic CSI reports may include at least one or both of CSI part 1 or CSI part 2, and when the aperiodic CSI reports are transmitted via PUSCH, they may be multiplexed with the transport block. For multiplexing, a CRC is inserted into the input bits of the aperiodic CSI, followed by encoding and rate matching, and then mapped to a specific pattern in a resource element within PUSCH and transmitted. The above CRC insertion may be omitted depending on the coding method or the length of the input bits. The number of modulation symbols calculated for rate matching during the multiplexing of CSI part 1 or CSI part 2 included in the aperiodic CSI reports can be calculated as shown in [Table 12] below.

[0250] [Table 12]

[0251]

[0252]

[0253] In particular, for PUSCH repetition transmission methods A and B, the terminal can transmit aperiodic CSI reports by multiplexing them only during the first repetition of the PUSCH repetition. This is because the aperiodic CSI report information being multiplexed is encoded in a polar code format, and for it to be multiplexed across multiple PUSCH repetitions, each PUSCH repetition must have the same frequency and time resource allocation. Specifically, in the case of PUSCH repetition type B, since each actual repetition can have a different OFDM symbol length, the aperiodic CSI reports can be multiplexed and transmitted only during the first PUSCH repetition.

[0254] Additionally, regarding PUSCH repetitive transmission method B, if the terminal receives a DCI that schedules a non-periodic CSI report or enables semi-permanent CSI report without scheduling for the transport block, the value of the nominal repetition may be assumed to be 1 even if the number of PUSCH repetitive transmissions set by the upper layer signaling is greater than 1. Additionally, if the terminal schedules or enables a non-periodic or semi-permanent CSI report without scheduling for the transport block based on PUSCH repetitive transmission method B, the terminal may expect the first nominal repetition to be the same as the first actual repetition. For a PUSCH transmitted including the semi-permanent CSI based on PUSCH repetitive transmission method B without scheduling for the DCI after semi-permanent CSI report is enabled by the DCI, if the first nominal repetition is different from the first actual repetition, the transmission for the first nominal repetition may be ignored.

[0255] [CSI computation time]

[0256] When a base station instructs a terminal to provide an aperiodic CSI report or a semi-persistent CSI report via DCI, the terminal can determine whether it can perform a valid channel report through the instructed CSI report by considering the channel computation time required for the CSI report. For the aperiodic CSI report or semi-persistent CSI report instructed via DCI, the terminal can perform a valid CSI report starting from the uplink symbol after the Z symbol, after the last symbol included in the PDCCH containing the DCI instructing the CSI report has ended. The aforementioned Z symbol may vary depending on the numerology of the downlink bandwidth part corresponding to the PDCCH containing the DCI instructing the CSI report, the numerology of the uplink bandwidth part corresponding to the PUSCH transmitting the CSI report, and the type or characteristics of the channel information reported in the CSI report (report quantity, frequency band granularity, number of reference signal ports, codebook type, etc.). In other words, for a CSI report to be determined as a valid CSI report (for the CSI report to be valid), the uplink transmission of the CSI report, including the timing advance, must not be performed before the Zref symbol. In this case, the Zref symbol is time from the moment the last symbol of the aforementioned triggering PDCCH ends. It is an uplink symbol that initiates the CP (cyclic prefix). Here, the detailed value of Z follows the explanation below, , , , , and is numerology. At this time Is The largest of them It can be promised to use something that causes a value, is the subcarrier interval used for PDCCH transmission, is the subcarrier spacing used for CSI-RS transmission, can refer to the subcarrier spacing of the uplink channel used for transmitting UCI (Uplink control information) for CSI reporting. As another example Is The largest of them It is also possible to promise to use something that causes a value. and Refer to the explanation above for the definition. For convenience of future explanation, satisfying the above conditions will be referred to as satisfying CSI reporting validity condition 1.

[0257] Furthermore, if the reference signal for channel measurement regarding the aperiodic CSI report instructed to the terminal via the DCI is an aperiodic reference signal, a valid CSI report can be executed starting from the uplink symbol following the Z' symbol after the end of the last symbol containing the reference signal. The aforementioned Z' symbol may vary depending on the numerology of the downlink bandwidth part corresponding to the PDCCH containing the DCI instructing the CSI report, the numerology of the bandwidth corresponding to the reference signal for channel measurement regarding the CSI report, the numerology of the uplink bandwidth part corresponding to the PUSCH transmitting the CSI report, and the type or characteristics of the channel information reported in the CSI report (report quantity, frequency band granularity, number of ports of the reference signal, codebook type, etc.). In other words, for a CSI report to be determined as a valid CSI report (for the CSI report to be a valid CSI report), the uplink transmission of the CSI report, including the timing advance, must not be executed before the Zref' symbol. At this time, the Zref' symbol is time from the moment the last symbol of the non-periodic CSI-RS or non-periodic CSI-IM triggered by the aforementioned triggering PDCCH ends. It is an uplink symbol that initiates the CP (cyclic prefix). Here, the detailed value of Z' follows the explanation below, , , , , and is numerology. At this time Is The largest of them It can be promised to use something that causes a value, is the subcarrier interval used for triggering PDCCH transmission, is the subcarrier spacing used for CSI-RS transmission, can refer to the subcarrier spacing of the uplink channel used for transmitting UCI (Uplink control information) for CSI reporting. As another example, Is The largest of them It can be promised to use what causes a value. In this case, and Refer to the explanation above for the definition. For convenience of future explanation, satisfying the above conditions will be referred to as satisfying CSI reporting validity condition 2.

[0258] If a base station instructs a terminal to perform an aperiodic CSI report on an aperiodic reference signal via DCI, the terminal may perform a valid CSI report starting from the first uplink symbol that satisfies both the time point Z after the end of the last symbol included in the PDCCH containing the DCI instructing the CSI report and the time point Z' after the end of the last symbol containing the reference signal. That is, in the case of aperiodic CSI reporting based on an aperiodic reference signal, it is determined to be a valid CSI report only if it satisfies both CSI reporting validity conditions 1 and 2.

[0259] If the timing of the CSI report instructed by the base station does not satisfy the CSI computation time requirements, the terminal may determine that the CSI report is invalid and not consider updating the channel information status for the CSI report.

[0260] The Z and Z' symbols for the aforementioned CSI computation time calculation follow [Table 13] and [Table 14] below. For example, if the channel information reported in the CSI report includes only wideband information, the number of reference signal ports is 4 or less, there is one reference signal resource, the codebook type is 'type I-SinglePanel', or the type of reported channel information (report quantity) is 'cri-RI-CQI', the Z and Z' symbols are those in [Table 14]. It follows the value. This will be named Delay Requirement 2 in the future. In addition, if the PUSCH containing the CSI report does not contain a TB or HARQ-ACK and the terminal's CPU occupation is 0, the Z and Z' symbols are from [Table 13]. It follows the value and is named Delay Requirement 1. The explanation regarding the aforementioned CPU occupation is described in detail below. Additionally, if the report quantity is 'cri-RSRP' or 'ssb-Index-RSRP', the Z and Z' symbols are from [Table 14]. Follows the values. X1, X2, X3, and X4 in [Table 14] represent the terminal's capability (UE capability) regarding beam reporting time, and KB1 and KB2 in [Table 14] represent the terminal's capability regarding beam switching time. In cases where the channel information does not correspond to the type or characteristic reported in the aforementioned CSI report, the Z and Z' symbols are [Table 14] Follows the value.

[0261] [Table 13]

[0262]

[0263] [Table 14]

[0264]

[0265] [CSI reference resource]

[0266] When a base station instructs a terminal to issue an aperiodic / semi-persistent / periodic CSI report, it may set a CSI reference resource to determine the reference time and frequency for the channel to be reported in the CSI report. The frequency of the CSI reference resource may be the carrier and subband information to be measured for the CSI, as specified in the CSI report configuration, and may correspond to the carrier and reportFreqConfiguration, respectively, within the upper-layer signaling CSI-ReportConfig. The time of the CSI reference resource may be defined based on the time at which the CSI report is transmitted. For example, if CSI report #X is instructed to be transmitted in the uplink slot n' of the carrier and BWP to which the CSI report is to be transmitted, the time of the CSI reference resource for CSI report #X may be defined as the downlink slot n-nCSI-ref of the carrier and BWP measuring the CSI. When downlink slot n is named μDL for the numerology of the carrier and BWP measuring CSI, and μUL for the numerology of the carrier and BWP transmitting CSI report #X It is calculated as follows. nCSI-ref, the slot interval between downlink slot n and the CSI reference signal, depends on the number of CSI-RS / SSB resources for channel measurement when CSI report #X transmitted in uplink slot n' is a semi-persistent or periodic CSI report, if a single CSI-RS / SSB resource is connected to the said CSI report If it follows and multiple CSI-RS / SSB resources are connected to the relevant CSI report Follows. If the CSI report #X transmitted in uplink slot n' is an aperiodic CSI report, considering the CSI computation time Z' for channel measurement It is calculated as. The aforementioned is the number of symbols included in a slot, and in NR Assume =14.

[0267] When a base station instructs a terminal to transmit a CSI report in uplink slot n' via upper layer signaling or DCI, the terminal may report a CSI by performing channel measurement or interference measurement on a CSI-RS resource, CSI-IM resource, or SSB resource associated with the CSI report that is transmitted no later than the CSI reference resource slot of the CSI report transmitted in uplink slot n'. The CSI-RS resource, CSI-IM resource, or SSB resource connected to the above CSI report may refer to a CSI-RS resource, CSI-IM resource, or SSB resource included in a resource set configured in a resource setting referenced by a report setting for a CSI report of a terminal configured through upper layer signaling, or a CSI-RS resource, CSI-IM resource, or SSB resource referenced by a CSI report trigger state containing parameters for the CSI report, or a CSI-RS resource, CSI-IM resource, or SSB resource pointed to by an ID of a reference signal (RS) set.

[0268] In embodiments of the present disclosure, a CSI-RS / CSI-IM / SSB occasion refers to the transmission time of a CSI-RS / CSI-IM / SSB resource(s) determined by an upper layer setting or a combination of an upper layer setting and DCI triggering. For example, for a semi-persistent or periodic CSI-RS resource, the slot to be transmitted is determined by the slot period and slot offset set by the upper layer signaling, and the transmitted symbol(s) within the slot are determined by the resource mapping information. For another example, for an aperiodic CSI-RS resource, the slot to be transmitted is determined by the slot offset with the PDCCH containing the DCI indicating channel reporting set by the upper layer signaling, and the transmitted symbol(s) within the slot are determined by the resource mapping information.

[0269] The aforementioned CSI-RS occasion can be determined by independently considering the transmission time of each CSI-RS resource or by comprehensively considering the transmission time of one or more CSI-RS resource(s) included in the resource set; accordingly, the following two interpretations are possible for the CSI-RS occasion according to each resource set setting.

[0270] - Interpretation 1-1: From the start time of the earliest symbol to the end time of the latest symbol during which a specific resource among one or more CSI-RS resources included in the resource set(s) configured in the resource setting referenced by the report setting configured for the CSI report is transmitted.

[0271] - Interpretation 1-2: Among all CSI-RS resources included in the resource set(s) configured in the resource setting referenced by the report setting configured for the CSI report, from the start time of the earliest symbol transmitted by the earliest transmitted CSI-RS resource to the end time of the latest symbol transmitted by the latest transmitted CSI-RS resource

[0272] In the embodiments of the present disclosure below, it is possible to individually apply both interpretations of the CSI-RS occasion. Additionally, while it is possible to consider both interpretations for the CSI-IM occasion and the SSB occasion, just as with the CSI-RS occasion, the principle is similar to the explanation above, so redundant explanations will be omitted below.

[0273] In embodiments of the present disclosure, 'CSI-RS / CSI-IM / SSB occasion for CSI report #X transmitted in uplink slot n'' refers to a set of CSI-RS occasions, CSI-IM occasions, and SSB occasions among the CSI-RS resource, CSI-IM resource, and SSB resource CSI-RS occasions, CSI-IM occasions, and SSB occasions included in the resource set of the resource setting referenced by the report setting set for CSI report #X, which are not later than the CSI reference resource of CSI report #X transmitted in uplink slot n'.

[0274] In the embodiments of the present disclosure, the latest CSI-RS / CSI-IM / SSB occasion among the CSI-RS / CSI-IM / SSB occasions for CSI report #X transmitted in 'uplink slot n' can be interpreted in the following two ways.

[0275] - Interpretation 2-1: A set of occasions including the latest CSI-RS occasion for CSI report #X transmitted in uplink slot n', the latest CSI-IM occasion for CSI report #X transmitted in uplink slot n', and the latest SSB occasion for CSI report #0 transmitted in uplink slot n'.

[0276] - Interpretation 2-2: The latest occasion among the CSI-RS occasion, CSI-IM occasion, and SSB occasion for CSI report #X transmitted in uplink slot n'.

[0277] In the embodiments of the present disclosure below, it is possible to apply individually by considering both interpretations of the ‘latest CSI-RS / CSI-IM / SSB occasion among the CSI-RS / CSI-IM / SSB occasions for CSI report #X transmitted in uplink slot n’. Additionally, when considering the two interpretations (interpretation 1-1, interpretation 1-2) described above for the CSI-RS occasion, CSI-IM occasion, and SSB occasion, in the embodiments of the present disclosure, the “latest CSI-RS / CSI-IM / SSB occasion among the CSI-RS / CSI-IM / SSB occasions for CSI report #X transmitted in uplink slot n’” can be applied individually by considering all four different interpretations (applying interpretation 1-1 and interpretation 2-1, applying interpretation 1-1 and interpretation 2-2, applying interpretation 1-2 and interpretation 2-1, applying interpretation 1-2 and interpretation 2-2).

[0278] The base station may instruct a CSI report by considering the amount of channel information that the terminal can simultaneously calculate for the CSI report, that is, the number of the terminal's channel information processing units (CSI processing units, CPUs). The number of channel information processing units that the terminal can simultaneously calculate If so, the terminal If you do not expect CSI report instructions from base stations that require more channel information calculations, or Updates to channel information that require more channel information calculations may not be considered. The terminal can report to the base station via upper layer signaling, or the base station can configure it via upper layer signaling.

[0279] The CSI report instructed by the base station to the terminal is the total number of channel information that the terminal can calculate simultaneously. It is assumed that some or all of the CPU is occupied for channel information calculation. For each CSI report, for example, CSI report The number of channel information calculation units required for If so, the number of channel information calculation units required for a total of N CSI reports is It can be said that the calculation unit of channel information required per reportQuantity set in the CSI report can be set as follows [Table 15].

[0280] [Table 15]

[0281]

[0282] The number of channel information calculations required by the terminal for multiple CSI reports at a specific point in time is the number of channel information calculation units that the terminal can calculate simultaneously. In more cases, the terminal may not consider updating channel information for some CSI reports. Among multiple directed CSI reports, the CSI reports for which channel information updates are not considered are determined by taking into account at least the time the calculation of channel information required for the CSI report occupies the CPU and the priority of the reported channel information. For example, it may not consider updating channel information for a CSI report where the calculation of channel information required for the CSI report starts at the latest time, and it is possible to prioritize not considering channel information updates for CSI reports with lower channel information priority.

[0283] The priority of the above channel information can be determined by referring to [Table 16] below.

[0284] [Table 16]

[0285]

[0286] The CSI priority for a CSI report is determined by the priority value PriiCSI(y,k,c,s) in [Table 16]. Referring to [Table 16], the CSI priority value is determined by the type of channel information included in the CSI report, the time-axis reporting characteristics of the CSI report (aperiodic, semi-persistent, periodic), the channel through which the CSI report is transmitted (PUSCH, PUCCH), the serving cell index, and the CSI report configuration index. The CSI priority for a CSI report is determined by comparing the priority value PriiCSI(y,k,c,s) and judging that the CSI report with the smaller priority value has a higher CSI priority.

[0287] If CPU occupation time is defined as the time the CPU is occupied by calculating channel information required for the CSI report instructed by the base station to the terminal, then CPU occupation time is determined by considering the type of channel information included in the CSI report (report quantity), the time-axis characteristics of the CSI report (aperiodic, semi-persistent, periodic), the slots or symbols occupied by the upper-layer signaling or DCI instructing the CSI report, and part or all of the slots or symbols occupied by the reference signal for channel state measurement.

[0288] [PDCCH: DCI related]

[0289] Next, we will explain downlink control information (DCI) in 5G systems in detail.

[0290] In a 5G system, scheduling information for uplink data (or Physical Uplink Shared Channel (PUSCH)) or downlink data (or Physical Downlink Shared Channel (PDSCH)) is transmitted from the base station to the terminal via DCI. The terminal can monitor the fallback DCI format and the non-fallback DCI format for PUSCH or PDSCH. The fallback DCI format may consist of fixed fields selected between the base station and the terminal, and the non-fallback DCI format may include configurable fields.

[0291] DCI can be transmitted through the Physical Downlink Control Channel (PDCCH) after undergoing channel coding and modulation processes. A Cyclic Redundancy Check (CRC) is attached to the DCI message payload, and the CRC can be scrambled into a Radio Network Temporary Identifier (RNTI) corresponding to the terminal's identity. Different RNTIs may be used depending on the purpose of the DCI message, such as UE-specific data transmission, power control commands, or random access responses. In other words, the RNTI is not transmitted explicitly but is included in the CRC calculation process. Upon receiving a DCI message transmitted over the PDCCH, the terminal checks the CRC using the assigned RNTI; if the CRC check result is correct, the terminal knows that the message has been transmitted to it.

[0292] For example, a DCI scheduling a PDSCH for System Information (SI) can be scrambled to SI-RNTI. A DCI scheduling a PDSCH for Random Access Response (RAR) messages can be scrambled to RA-RNTI. A DCI scheduling a PDSCH for Paging messages can be scrambled to P-RNTI. A DCI notifying a Slot Format Indicator (SFI) can be scrambled to SFI-RNTI. A DCI notifying Transmit Power Control (TPC) can be scrambled to TPC-RNTI. A DCI scheduling a terminal-specific PDSCH or PUSCH can be scrambled to C-RNTI (Cell RNTI).

[0293] DCI format 0_0 can be used as a countermeasure DCI for scheduling PUSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 0_0 with the CRC scrambled with C-RNTI may include, for example, the information in [Table 17] below.

[0294] [Table 17]

[0295]

[0296] DCI format 0_1 ​​can be used as a non-defense DCI for scheduling PUSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 0_1 ​​with the CRC scrambled with C-RNTI may include, for example, the information in [Table 18] below.

[0297] [Table 18]

[0298]

[0299]

[0300] DCI format 1_0 can be used as a countermeasure DCI for scheduling PDSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 1_0 with the CRC scrambled with C-RNTI may include, for example, the information in [Table 19] below.

[0301] [Table 19]

[0302]

[0303] DCI format 1_1 can be used as a non-defense DCI for scheduling PDSCH, whereby the CRC can be scrambled with C-RNTI. DCI format 1_1 with the CRC scrambled with C-RNTI may include, for example, the information in [Table 20] below.

[0304] [Table 20]

[0305]

[0306]

[0307] [PDCCH: CORESET, REG, CCE, Search Space]

[0308] In the following, the downlink control channel in a 5G communication system will be explained in more detail with reference to the drawings.

[0309] FIG. 8 illustrates an example of a control resource set (CORESET) in which a downlink control channel is transmitted in a 5G wireless communication system. FIG. 8 illustrates an example in which two control resources (control resource #1 (801), control resource #2 (802)) are set within a terminal bandwidth part (UE bandwidth part) (810) on the frequency axis and one slot (820) on the time axis. The control resources (801, 802) can be set in a specific frequency resource (803) within the entire terminal bandwidth part (810) on the frequency axis. On the time axis, they can be set with one or more OFDM symbols and can be defined as the control resource set duration (Control Resource Set Duration, 804). Referring to the example illustrated in FIG. 8, control resource #1 (801) is set with a control resource length of 2 symbols, and control resource #2 (802) is set with a control resource length of 1 symbol.

[0310] The control domain in the aforementioned 5G can be configured by the base station to the terminal through upper-layer signaling (e.g., System Information, MIB (Master Information Block), RRC (Radio Resource Control) signaling). Configuring the control domain to the terminal means providing information such as the control domain identifier (Identity), the frequency location of the control domain, and the symbol length of the control domain. For example, it may include the information in [Table 21] below.

[0311] [Table 21]

[0312]

[0313] In [Table 21], the tci-StatesPDCCH (simply named TCI (Transmission Configuration Indication) state) configuration information may include information on one or more SS (Synchronization Signal) / PBCH (Physical Broadcast Channel) block indices or CSI-RS (Channel State Information Reference Signal) indices that are in a QCL (Quasi Co Located) relationship with the DMRS transmitted in the corresponding control area.

[0314] FIG. 9 is a diagram illustrating the structure of a downlink control channel in a wireless communication system according to one embodiment of the present disclosure. FIG. 9 is a diagram showing an example of a basic unit of time and frequency resources that constitute a downlink control channel that can be used in 5G. According to FIG. 9, the basic unit of time and frequency resources that constitute the control channel can be called a REG (Resource Element Group, 903), and the REG (903) can be defined as 1 OFDM symbol (901) on the time axis and 1 PRB (Physical Resource Block, 902) on the frequency axis, that is, 12 subcarriers. A base station can construct a downlink control channel allocation unit by concatenating REGs (903).

[0315] As illustrated in FIG. 9, if the basic unit to which a downlink control channel is allocated in 5G is called a CCE (Control Channel Element, 904), then 1 CCE (904) can be composed of multiple REGs (903). For example, if the REG (903) illustrated in FIG. 9 is described, the REG (903) can be composed of 12 REs, and if 1 CCE (904) is composed of 6 REGs (903), then 1 CCE (904) can be composed of 72 REs. When a downlink control area is established, the area can be composed of multiple CCEs (904), and a specific downlink control channel can be mapped to one or multiple CCEs (904) and transmitted according to the Aggregation Level (AL) within the control area. The CCEs (904) in the control area are distinguished by numbers, and the numbers of the CCEs (904) can be assigned according to a logical mapping method.

[0316] The basic unit of the downlink control channel, namely the REG (903) illustrated in FIG. 9, may include both the REs to which the DCI is mapped and the DMRS (905), which is a reference signal for decoding, to which the area is mapped. As shown in FIG. 9, three DMRS (905) may be transmitted within one REG (903). The number of CCEs required to transmit the PDCCH may be 1, 2, 4, 8, or 16 depending on the Aggregation Level (AL), and different numbers of CCEs may be used to implement link adaptation of the downlink control channel. For example, when AL=L, one downlink control channel may be transmitted through L CCEs. The terminal must detect the signal without knowing information about the downlink control channel, and a search space representing a set of CCEs is defined for blind decoding. A search space is a set of downlink control channel candidates consisting of CCEs that a terminal must attempt to decode at a given aggregation level, and since there are various aggregation levels that form a group of 1, 2, 4, 8, or 16 CCEs, a terminal may have multiple search spaces. A search space set can be defined as a set of search spaces at all configured aggregation levels.

[0317] Search spaces can be classified into common search spaces and UE-specific search spaces. A certain group of terminals or all terminals may examine the common search space of the PDCCH to receive cell-common control information, such as dynamic scheduling or paging messages regarding system information. For example, PDSCH scheduling allocation information for the transmission of SIBs containing cell operator information can be received by examining the common search space of the PDCCH. In the case of the common search space, since a certain group of terminals or all terminals must receive the PDCCH, it can be defined as a pre-arranged set of CCEs. Scheduling allocation information for a UE-specific PDSCH or PUSCH can be received by examining the UE-specific search space of the PDCCH. The UE-specific search space can be defined specifically as a function of the terminal's identity and various system parameters.

[0318] In 5G, parameters for the search space for a PDCCH can be configured from the base station to the terminal via upper-layer signaling (e.g., SIB, MIB, RRC signaling). For example, the base station may configure the terminal the number of PDCCH candidates at each aggregation level L, the monitoring period for the search space, the occasion for monitoring in slot-symbol units for the search space, the search space type (common search space or terminal-specific search space), the combination of DCI format and RNTI to be monitored in the search space, and the control domain index to be monitored in the search space. For example, the information in [Table 22] below may be included.

[0319] [Table 22]

[0320]

[0321]

[0322] According to the configuration information, the base station may set one or multiple sets of search spaces for the terminal. According to some embodiments, the base station may set search space set 1 and search space set 2 for the terminal, and may set DCI format A scrambled with X-RNTI in search space set 1 to be monitored in a common search space, and may set DCI format B scrambled with Y-RNTI in search space set 2 to be monitored in a terminal-specific search space.

[0323] According to the configuration information, one or more sets of search spaces may exist in a common search space or a terminal-specific search space. For example, Search Space Set #1 and Search Space Set #2 may be configured as a common search space, and Search Space Set #3 and Search Space Set #4 may be configured as a terminal-specific search space.

[0324] In the common search space, the following combinations of DCI formats and RNTI can be monitored. Of course, they are not limited to the examples below.

[0325] - DCI format 0_0 / 1_0 with CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, RA-RNTI, TC-RNTI, P-RNTI, SI-RNTI

[0326] - DCI format 2_0 with CRC scrambled by SFI-RNTI

[0327] - DCI format 2_1 with CRC scrambled by INT-RNTI

[0328] - DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI, TPC-PUCCH-RNTI

[0329] - DCI format 2_3 with CRC scrambled by TPC-SRS-RNTI

[0330] In terminal-specific search spaces, the following combinations of DCI formats and RNTI can be monitored. Of course, they are not limited to the examples below.

[0331] - DCI format 0_0 / 1_0 with CRC scrambled by C-RNTI, CS-RNTI, TC-RNTI

[0332] - DCI format 1_0 / 1_1 with CRC scrambled by C-RNTI, CS-RNTI, TC-RNTI

[0333] The specified RNTIs may follow the definitions and uses below.

[0334] C-RNTI (Cell RNTI): Used for terminal-specific PDSCH scheduling

[0335] TC-RNTI (Temporary Cell RNTI): Used for terminal-specific PDSCH scheduling

[0336] CS-RNTI (Configured Scheduling RNTI): Used for semi-statically configured terminal-specific PDSCH scheduling.

[0337] RA-RNTI (Random Access RNTI): Used for PDSCH scheduling during the random access phase

[0338] P-RNTI (Paging RNTI): Used for PDSCH scheduling where paging is transmitted.

[0339] SI-RNTI (System Information RNTI): Used for PDSCH scheduling where system information is transmitted.

[0340] INT-RNTI (Interruption RNTI): Used to indicate whether PDSCH is pucturing.

[0341] TPC-PUSCH-RNTI (Transmit Power Control for PUSCH RNTI): Used to instruct power control commands to the PUSCH

[0342] TPC-PUCCH-RNTI (Transmit Power Control for PUCCH RNTI): Used to instruct power control commands to the PUCCH

[0343] TPC-SRS-RNTI (Transmit Power Control for SRS RNTI): Used to instruct power regulation commands to the SRS

[0344] The aforementioned specified DCI formats may follow the definitions in [Table 23] below.

[0345] [Table 23]

[0346]

[0347] In 5G, the search space of aggregation level L in the control domain p and search space set s can be expressed as [Equation 1] below.

[0348] [Mathematical Formula 1]

[0349]

[0350] In the case of a terminal-specific search space, the value may correspond to a value that changes according to the terminal's identity (C-RNTI or ID set by the base station for the terminal) and the time index.

[0351] In 5G, as multiple sets of search spaces can be configured with different parameters (e.g., parameters in [Table 22]), the set of search space sets monitored by the terminal at each point in time may vary. For example, if search space set #1 is configured for an X-slot period and search space set #2 is configured for a Y-slot period and X and Y are different, the terminal may monitor both search space set #1 and search space set #2 in a specific slot, and monitor either search space set #1 or search space set #2 in a specific slot.

[0352] [Regarding SRS]

[0353] Next, a method for estimating the uplink channel using the transmission of the terminal's Sounding Reference Signal (SRS) is described. To transmit configuration information for SRS transmission to the terminal, the base station may set at least one SRS configuration for each uplink BWP, and may also set at least one SRS resource set for each SRS configuration. For example, the base station and the terminal may exchange upper-level signaling information as follows to transmit information regarding the SRS resource set.

[0354] - srs-ResourceSetId: SRS resource set index

[0355] - srs-ResourceIdList: A set of SRS resource indices referenced by the SRS resource set

[0356] - resourceType: This is the time-axis transmission setting for the SRS resource referenced in the SRS resource set, and can be set to one of 'periodic', 'semi-persistent', or 'aperiodic'. If set to 'periodic' or 'semi-persistent', associated CSI-RS information may be provided depending on the usage of the SRS resource set. If set to 'aperiodic', a non-periodic SRS resource trigger list and slot offset information may be provided, and associated CSI-RS information may be provided depending on the usage of the SRS resource set.

[0357] - usage: A setting regarding the usage of the SRS resource referenced in the SRS resource set, which can be set to one of 'beamManagement', 'codebook', 'nonCodebook', or 'antennaSwitching'.

[0358] - alpha, p0, pathlossReferenceRS, srs-PowerControlAdjustmentStates: Provides parameter settings for controlling the transmit power of the SRS resource referenced in the SRS resource set.

[0359] The terminal can understand that the SRS resources included in the set of SRS resource indices referenced in the SRS resource set follow the information set in the SRS resource set.

[0360] Additionally, the base station and the terminal may transmit and receive upper-layer signaling information to convey individual configuration information for the SRS resource. For example, the individual configuration information for the SRS resource may include time-frequency axis mapping information within the slot of the SRS resource, which may include information regarding frequency hopping within or between slots of the SRS resource. Furthermore, the individual configuration information for the SRS resource may include the time-axis transmission setting of the SRS resource, which may be set to one of 'periodic', 'semi-persistent', or 'aperiodic'. This may be restricted to having the same time-axis transmission setting as the SRS resource set containing the SRS resource. If the time-axis transmission setting of the SRS resource is set to 'periodic' or 'semi-persistent', the SRS resource transmission period and slot offset (e.g., periodicityAndOffset) may additionally be included in the time-axis transmission setting.

[0361] A base station may enable, deactivate, or trigger SRS transmission to a terminal via upper-layer signaling, including RRC signaling or MAC CE signaling, or L1 signaling (e.g., DCI). For example, a base station may enable or deactivate periodic SRS transmission to a terminal via upper-layer signaling. A base station may instruct an SRS resource set with resourceType set to periodic to be enabled via upper-layer signaling, and the terminal may transmit an SRS resource referenced in the enabled SRS resource set. The time-frequency axis resource mapping within the slot of the transmitted SRS resource follows the resource mapping information set in the SRS resource, and the slot mapping, including the transmission period and slot offset, follows the periodicityAndOffset set in the SRS resource. Additionally, a spatial domain transmission filter applied to the transmitted SRS resource may refer to spatial relation info set in the SRS resource, or may refer to associated CSI-RS information set in the SRS resource set containing the SRS resource. The terminal can transmit an SRS resource within an active uplink BWP for a periodic SRS resource activated through upper layer signaling.

[0362] For example, a base station can enable or disable semi-persistent SRS transmission to a terminal via upper-layer signaling. The base station can instruct the terminal to enable an SRS resource set via MAC CE signaling, and the terminal can transmit an SRS resource referenced in the enabled SRS resource set. The SRS resource set enabled via MAC CE signaling may be limited to an SRS resource set where resourceType is set to semi-persistent. The time-frequency axis resource mapping within the slot of the transmitted SRS resource follows the resource mapping information set in the SRS resource, and the slot mapping, including the transmission period and slot offset, follows the periodicityAndOffset set in the SRS resource. Additionally, the spatial domain transmission filter applied to the transmitted SRS resource may refer to spatial relation info set in the SRS resource, or may refer to associated CSI-RS information set in the SRS resource set containing the SRS resource. If spatial relation info is configured in the SRS resource, the spatial domain transmission filter can be determined by referring to the configuration information regarding the spatial relation info transmitted via MAC CE signaling that enables semi-persistent SRS transmission without following it. The terminal can transmit the SRS resource within the uplink BWP enabled for the semi-persistent SRS resource activated via upper layer signaling.

[0363] For example, a base station can trigger an aperiodic SRS transmission to a terminal via the DCI. The base station can specify one of the aperiodic SRS resource triggers (aperiodicSRS-ResourceTrigger) through the SRS request field of the DCI. The terminal can understand that among the configuration information of the SRS resource set, an SRS resource set containing the aperiodic SRS resource trigger specified via the DCI from the list of aperiodic SRS resource triggers has been triggered. The terminal can transmit the SRS resource referenced in the triggered SRS resource set. The time-frequency axis resource mapping within the slot of the transmitted SRS resource follows the resource mapping information set in the SRS resource. Additionally, the slot mapping of the transmitted SRS resource can be determined through the slot offset between the PDCCH containing the DCI and the SRS resource, which can refer to the value(s) included in the set of slot offsets set in the SRS resource set. Specifically, the slot offset between the PDCCH containing the DCI and the SRS resource may be the value specified in the time domain resource assignment field of the DCI among the offset value(s) included in the slot offset set configured in the SRS resource set. Additionally, the spatial domain transmission filter applied to the transmitted SRS resource may refer to the spatial relation info configured in the SRS resource, or may refer to the associated CSI-RS information configured in the SRS resource set containing the SRS resource. The terminal may transmit the SRS resource within an uplink BWP that is enabled for a non-periodic SRS resource triggered via the DCI.

[0364] When a base station triggers aperiodic SRS transmission to a terminal via DCI, a minimum time interval may be required between the PDCCH containing the DCI triggering the aperiodic SRS transmission and the transmitted SRS so that the terminal can apply configuration information for the SRS resource and transmit the SRS. The time interval for the terminal's SRS transmission can be defined as the number of symbols between the last symbol of the PDCCH containing the DCI triggering the aperiodic SRS transmission and the first symbol mapped to the first transmitted SRS resource(s). The minimum time interval can be determined by referencing the PUSCH preparation procedure time required for the terminal to prepare for PUSCH transmission. Additionally, the minimum time interval may have different values ​​depending on the usage of the SRS resource set containing the transmitted SRS resource. For example, the minimum time interval can be determined by N2 symbols defined by considering the terminal's processing capability based on the terminal's capability, referencing the terminal's PUSCH preparation procedure time. Additionally, considering the usage of the SRS resource set including the transmitted SRS resource, if the usage of the SRS resource set is set to 'codebook' or 'antennaSwitching', the minimum time interval can be set to N2 symbols, and if the usage of the SRS resource set is set to 'nonCodebook' or 'beamManagement', the minimum time interval can be set to N2+14 symbols.The terminal transmits an aperiodic SRS when the time interval for the aperiodic SRS transmission is greater than or equal to the minimum time interval, and can ignore the DCI that triggers the aperiodic SRS when the time interval for the aperiodic SRS transmission is less than the minimum time interval.

[0365] [Table 24]

[0366]

[0367]

[0368] The spatialRelationInfo setting information in [Table 24] above is intended to apply the beam information of a reference signal to the beam used for SRS transmission by referencing a single reference signal. For example, the spatialRelationInfo setting may include information such as that shown in [Table 25] below.

[0369] [Table 25]

[0370]

[0371] Referring to the spatialRelationInfo setting above, the index of the reference signal to be referenced in order to use the beam information of a specific reference signal—namely, the SS / PBCH block index, CSI-RS index, or SRS index—can be set. The upper signaling referenceSignal is configuration information indicating which reference signal's beam information to reference for the corresponding SRS transmission, and ssb-Index represents the SS / PBCH block index, csi-RS-Index represents the CSI-RS index, and srs represents the SRS index, respectively. If the value of the upper signaling referenceSignal is set to 'ssb-Index', the terminal can apply the receiving beam used when receiving the SS / PBCH block corresponding to ssb-Index as the transmitting beam for the corresponding SRS transmission. If the value of the upper signaling referenceSignal is set to 'csi-RS-Index', the terminal can apply the receiving beam used when receiving the CSI-RS corresponding to csi-RS-Index as the transmitting beam for the corresponding SRS transmission. If the value of the upper signaling referenceSignal is set to 'srs', the terminal can apply the transmission beam used during the transmission of the SRS corresponding to srs as the transmission beam for the transmission of the SRS.

[0372] [SRS: Antenna switching]

[0373] The following describes the SRS for antenna switching.

[0374] The SRS transmitted from the terminal can be used by the base station to acquire Channel State Information (DL CSI) information (e.g., DL CSI acquisition). As a specific example, in a single-cell or multi-cell (e.g., carrier aggregation (CA)) situation based on Time Division Duplex (TDD), the Base Station (BS) can measure the SRS transmitted from the UE after scheduling the transmission of the SRS to the User Equipment (UE). In this case, the base station can assume reciprocity between the DL (downlink) and UL (uplink) channels and consider the uplink channel information estimated based on the SRS transmitted from the terminal as downlink channel information, and use this to perform scheduling of downlink signals / channels for the terminal. At this time, the terminal can receive a setting from the base station for the use of the SRS for acquiring downlink channel information as antenna switching.

[0375] For example, according to the standard (e.g., 3gpp TS38.214), the use of the SRS can be configured for the base station and / or terminal using a higher layer parameter (e.g., the usage of the RRC parameter SRS-ResourceSet). Here, the use of the SRS can be configured for beam management, codebook transmission, non-codebook transmission, antenna switching, etc.

[0376] As described above, if the terminal receives the parameter 'usage' within the upper layer signaling SRS-ResourceSet from the base station as 'antennaSwitching', the terminal may receive at least one upper layer signaling setting from the base station according to the reported terminal capability. In this case, the terminal may report 'supportedSRS-TxPortSwitch' as ​​the terminal capability, and the value may be as follows. In the following, 'mTnR' may refer to the terminal capability to support transmission through m antennas and reception through n antennas.

[0377] - 't1r2': A terminal capability report value indicating that the terminal is capable of 1T2R operation

[0378] - 't1r1-t1r2': A terminal capability report value indicating that the terminal is capable of 1T1R or 1T2R operation

[0379] - 't2r4': A terminal capability report value indicating that the terminal is capable of 2T4R operation.

[0380] - 't1r4': A terminal capability report value indicating that the terminal is capable of 1T4R operation

[0381] - 't1r6': A terminal capability report value indicating that the terminal is capable of 1T6R operation

[0382] - 't1r8': A terminal capability report value indicating that the terminal is capable of 1T8R operation

[0383] - 't2r6': A terminal capability report value indicating that the terminal is capable of 2T6R operation

[0384] - 't2r8': A terminal capability report value indicating that the terminal is capable of 2T8R operation

[0385] - 't4r8': A terminal capability report value indicating that the terminal is capable of 4T8R operation.

[0386] - 't1r1-t1r2-t1r4': A terminal capability report value indicating that the terminal is capable of 1T1R, 1T2R, or 1T4R operation.

[0387] - 't1r4-t2r4': A terminal capability report value indicating that the terminal is capable of 1T4R or 2T4R operation.

[0388] - 't1r1-t1r2-t2r2-t2r4': A terminal capability report value indicating that the terminal is capable of 1T1R, 1T2R, 2T2R, or 2T4R operations.

[0389] - 't1r1-t1r2-t2r2-t1r4-t2r4': A terminal capability report value indicating that the terminal is capable of 1T1R, 1T2R, 2T2R, 1T4R, or 2T4R operations.

[0390] - 't1r1': A terminal capability report value indicating that the terminal is capable of 1T1R operation

[0391] - 't2r2': A terminal capability report value indicating that the terminal is capable of 2T2R operation.

[0392] - 't1r1-t2r2': A terminal capability report value indicating that the terminal is capable of 1T1R or 2T2R operation.

[0393] - 't4r4': A terminal capability report value indicating that the terminal is capable of 4T4R operation.

[0394] - 't1r1-t2r2-t4r4': A terminal capability report value indicating that the terminal is capable of 1T1R, 2T2R, or 4T4R operation.

[0395] When a terminal performs antenna switching operations, that is, when the terminal transmits different SRS resources connected to different antenna port(s), the time interval between two adjacent SRS resources among all transmitted SRS resources may generally be about 15 μs. Taking this into consideration, a (minimum) guard period as shown in [Table 26] below can be defined.

[0396] [Table 26]

[0397]

[0398] In [Table 26], μ represents numerology, and f represents the subcarrier spacing, and Y can represent the number of OFDM symbols representing the guard interval, i.e., the length of the guard interval. Referring to [Table 26], the guard interval can be set based on the parameter μ, which determines the numerology. During the guard interval, the terminal is configured not to transmit any other signals, and the guard interval can be configured to be used entirely for antenna switching.

[0399] For example, the above protection interval can be set between the transmission times of two adjacent SRS resources, taking into account SRS resources transmitted at different OFDM symbol positions within the same slot.

[0400] As another example, if a terminal is configured with two SRS resource sets for antenna switching, and these two SRS resource sets are configured or triggered to be transmitted in two consecutive slots, and the terminal reports the capability to transmit SRS at all OFDM symbol positions within the slots, the terminal can expect that there will be at least Y OFDM symbols for the protection interval for antenna switching between the last OFDM symbol transmitted in the first slot where SRS transmission for the first SRS resource set is performed, and the first OFDM symbol transmitted in the second slot where SRS transmission for the second SRS resource set is performed, based on [Table 26] above. That is, the actual time difference between the two SRS transmissions may be greater than or equal to Y OFDM symbols.

[0401] - Regarding such a slot-to-slot protection interval, similar to the protection interval between two SRS resources within a slot described above, if the actual time difference between the last SRS transmission of the first slot and the first SRS transmission of the next slot within two consecutive slots is Y OFDM symbols, the terminal may not transmit any signal during the corresponding Y OFDM symbol interval.

[0402] - For such an inter-slot guard interval, if the actual time difference between the last SRS transmission of the first slot and the first SRS transmission of the next slot within two consecutive slots is Y OFDM symbols, and if both SRS transmissions before and after the inter-slot guard interval are dropped (all canceled) due to overlap with other signals, the terminal may determine that the inter-slot guard interval defined by Y OFDM symbols has been dropped (canceled) by applying the same priority as the SRS transmissions before and after the guard interval, and if it is determined that it has been dropped, it may perform uplink transmission in this inter-slot guard interval.

[0403] For all antenna switching methods described above, the terminal can expect that all SRS resources within all SRS resource sets, where the usage of the upper layer signaling within the SRS resource set is set to 'antennaSwitching', will be configured with the same number of SRS ports from the base station.

[0404] Regarding the antenna switching method based on the aforementioned 1T24, 1T4R, 2T4R, 1T6R, 1T8R, 2T6R, 2T8R, and 4T8R operations, the terminal may not expect that two or more of the SRS resource sets, for which the usage of the upper layer signaling from the base station is set to 'antennaSwitching', are set or triggered in the same slot.

[0405] Regarding the antenna switching method based on the above-described 1T1R, 2T2R, and 4T4R operations, the terminal may not expect that two or more of the SRS resource sets, in which the usage of the upper layer signaling from the base station is set to 'antennaSwitching', are set or triggered on the same OFDM symbol.

[0406] FIG. 11 is a diagram showing an SRS antenna switching operation according to one embodiment of the present disclosure.

[0407] The terminal may be in a state where it operates in 1T4R and has received two non-periodic SRS resource sets (e.g., SRS resource set #0 and #1). The terminal receives a PDCCH from the base station (1100) and may be instructed to trigger non-periodic SRS for SRS resource set #0 (1110) and SRS resource set #1 (1120) through the PDCCH. At this time, the slot offset value for SRS resource set #0 (1110) may be set to slotOffset, which is an upper layer signaling, and the value is 1, and may perform non-periodic SRS transmission for SRS resource set #0 at a position one slot after the slot in which the PDCCH was received (i.e., at slot #1). Additionally, the slot offset value for SRS resource set #1 (1120) can be set to slotOffset, which is an upper layer signaling, and the value is 2, and a non-periodic SRS transmission for SRS resource set #1 can be performed at a position 2 slots after the slot that received the PDCCH (i.e., at slot #2).

[0408] SRS resource #0 (1111) and SRS resource #1 (1112) included in SRS resource set #0 (1110) are transmitted at different OFDM symbol locations within slot #1, and there may be Y number of OFDM symbols as a guard interval between SRS resource #0 and #1 (1113). Additionally, when transmitting for SRS resource #0 (1130), the terminal can perform SRS transmission by connecting one SRS port to the terminal's first receiving antenna port (1135), and when transmitting for SRS resource #1 (1140), the terminal can perform SRS transmission by connecting one SRS port to the terminal's second receiving antenna port (1145).

[0409] SRS resource #2 (1121) and SRS resource #3 (1122) included in SRS resource set #1 (1120) are transmitted at different OFDM symbol locations within slot #1, and there may be Y number of OFDM symbols as a guard interval between SRS resource #2 and #3 (1123). Additionally, when transmitting for SRS resource #2 (1150), the terminal can perform SRS transmission by connecting one SRS port to the terminal's third receiving antenna port (1155), and when transmitting for SRS resource #3 (1160), the terminal can perform SRS transmission by connecting one SRS port to the terminal's fourth receiving antenna port (1165).

[0410] By connecting the four SRS resources #0 to #3 described above to the receiving antenna ports of different terminals and transmitting SRS, the terminal can transmit SRS from all different receiving antenna ports so as to acquire channel information connected to all receiving antennas of the terminal, and through this, the base station can acquire channel information between the base station and the terminal and use it for uplink or downlink scheduling.

[0411] [Regarding Terminal Capability Reporting]

[0412] In LTE and NR, a terminal can perform a procedure to report the capabilities supported by the terminal to the base station while connected to the serving base station. In the description below, this is referred to as a UE capability report.

[0413] A base station may transmit a UE capability enquiry message requesting capability reporting to a connected terminal. The message may include a request for terminal capability specific to the base station's RAT (radio access technology) type. The request for each RAT type may include information such as supported frequency band combinations. Furthermore, in the case of the UE capability enquiry message, multiple UE capabilities for each RAT type may be requested through a single RRC message container transmitted by the base station, or the base station may transmit the UE capability enquiry message, which includes the request for each RAT type, to the terminal multiple times. That is, the UE capability inquiry may be repeated multiple times within a single message, and the terminal may construct and report the corresponding UE capability information message multiple times. In next-generation mobile communication systems, UE capability requests can be made for NR, LTE, EN-DC (E-UTRA - NR dual connectivity), and MR-DC (Multi-RAT dual connectivity). Additionally, while the UE capability enquiry message is generally transmitted initially after the terminal connects with the base station, the base station may request it under any conditions when necessary.

[0414] In the above step, the terminal that receives a request for a UE capability report from the base station configures the terminal capability according to the RAT type and band information requested from the base station. The method by which the terminal configures the UE capability in the NR system is summarized below.

[0415] 1. If the terminal receives a list of LTE and / or NR bands from the base station via a UE capability request, the terminal configures a band combination (BC) for EN-DC and NR stand-alone (SA). That is, it constructs a candidate list of BCs for EN-DC and NR SA based on the bands requested from the base station via FreqBandList. Additionally, the bands have priority in the order listed in FreqBandList.

[0416] 2. If the base station requests a UE capability report by setting the “eutra-nr-only” flag or the “eutra” flag, the terminal completely removes NR SA BCs from the above-mentioned list of configured BC candidates. This operation may occur only when the LTE base station (eNB) requests the “eutra” capability.

[0417] 3. Subsequently, the terminal removes fallback BCs from the candidate list of BCs configured in the above step. Here, a fallback BC refers to a BC that can be obtained by removing a band corresponding to at least one SCell from any BC; this step can be omitted because the BC before removing the band corresponding to at least one SCell already covers the fallback BC. This step applies to MR-DC as well, meaning it applies to LTE bands. The BCs remaining after this step constitute the final "candidate BC list."

[0418] 4. The terminal selects the BCs to be reported by selecting BCs that match the requested RAT type from the final "Candidate BC List" above. In this step, the terminal constructs the supportedBandCombinationList in a predetermined order. That is, the terminal constructs the BCs and UE capabilities to be reported according to the pre-set order of rat-Type (nr -> eutra-nr -> eutra). Additionally, it constructs a featureSetCombination for the constructed supportedBandCombinationList and constructs a list of "Candidate Feature Set Combinations" from the Candidate BC List from which the list of fallback BCs (containing capabilities of the same or lower level) has been removed. The above "Candidate Feature Set Combinations" include feature set combinations for both NR and EUTRA-NR BCs and can be obtained from the feature set combinations of the UE-NR-Capabilities and UE-MRDC-Capabilities containers.

[0419] 5. Additionally, if the requested rat Type is eutra-nr and has an influence, featureSetCombinations is included in both the UE-MRDC-Capabilities and UE-NR-Capabilities containers. However, the NR feature set is included only in UE-NR-Capabilities.

[0420] After the terminal capability is configured, the terminal transmits a terminal capability information message containing the terminal capability to the base station. Based on the terminal capability received from the terminal, the base station subsequently performs appropriate scheduling and transmission / reception management for the terminal.

[0421] [Regarding NC-JT]

[0422] According to one embodiment of the present disclosure, non-coherent joint transmission (NC-JT) may be used for a terminal to receive PDSCH from a plurality of TRPs.

[0423] Unlike existing systems, 5G wireless communication systems can support not only services requiring high transmission speeds but also services requiring very short transmission delays and high connection densities. In a wireless communication network comprising multiple cells, TRPs (transmission and reception points), or beams, coordinated transmission between each cell, TRP, or / and beam can satisfy various service requirements by increasing the signal strength received by the terminal or efficiently performing interference control between each cell, TRP, or / and beam.

[0424] Joint Transmission (JT) is a representative transmission technology for the aforementioned cooperative communication that increases the signal strength or throughput received by a terminal by transmitting signals to a single terminal through multiple different cells, TRPs, and / or beams. In this case, the characteristics of the channels between each cell, TRP, or / or beam and the terminal may differ significantly. In particular, in the case of Non-Coherent Joint Transmission (NC-JT), which supports non-coherent precoding between each cell, TRP, or / or beam, individual precoding, MCS, resource allocation, TCI instructions, etc., may be required depending on the link-specific channel characteristics between each cell, TRP, or / or beam and the terminal.

[0425] The aforementioned NC-JT transmission may be applied to at least one of the downlink data channel (PDSCH), downlink control channel (PDCCH), uplink data channel (PUSCH), and uplink control channel (PUCCH). During PDSCH transmission, transmission information such as precoding, MCS, resource allocation, and TCI is indicated as DL DCI, and for NC-JT transmission, said transmission information must be indicated independently by cell, TRP, and / or beam. This is a major factor in increasing the payload required for DL ​​DCI transmission, which can adversely affect the reception performance of the PDCCH transmitting DCI. Therefore, to support JT in PDSCH, it is necessary to carefully design the tradeoff between the amount of DCI information and the reception performance of control information.

[0426] FIG. 12 is a diagram illustrating an example of antenna port configuration and resource allocation for transmitting PDSCH using cooperative communication in a wireless communication system according to one embodiment of the present disclosure.

[0427] Referring to Fig. 12, examples for PDSCH transmission are described according to the Joint Transmission (JT) technique, and examples for allocating radio resources by TRP are illustrated.

[0428] Referring to FIG. 12, an example (1200) of a Coherent Joint Transmission (C-JT) that supports coherent precoding between each cell, TRP or / and beam is shown.

[0429] In the case of C-JT, TRP A (1205) and TRP B (1210) transmit a single data (PDSCH) to the terminal (1215), and joint precoding can be performed in multiple TRPs. This may mean that DMRS is transmitted through the same DMRS ports for TRP A (1205) and TRP B (1210) to transmit the same PDSCH. For example, TRP A (1205) and TRP B (1210) each can transmit DRMS ​​to the terminal through DMRS port A and DMRS B. In this case, the terminal can receive one DCI information for receiving a single PDSCH that is demodulated based on the DMRS transmitted through DMRS port A and DMRS B.

[0430] FIG. 12 shows an example (1220) of Non-Coherent Joint Transmission (NC-JT) that supports non-coherent precoding between each cell, TRP or / and beam for PDSCH transmission.

[0431] In the case of NC-JT, a PDSCH is transmitted to a terminal (1235) by each cell, TRP or / and beam (1225, 1230), and individual precoding may be applied to each PDSCH. Each cell, TRP or / and beam can transmit a different PDSCH or a different PDSCH layer to the terminal to improve throughput compared to single cell, TRP or / and beam transmission. Additionally, each cell, TRP or / and beam can repeatedly transmit the same PDSCH to the terminal to improve reliability compared to single cell, TRP or / and beam transmission. For convenience of explanation, the cell, TRP or / and beam is collectively referred to as TRP below.

[0432] At this time, various wireless resource allocations may be considered, such as when the frequency and time resources used by multiple TRPs for PDSCH transmission are all the same (1240), when the frequency and time resources used by multiple TRPs do not overlap at all (1245), or when some of the frequency and time resources used by multiple TRPs overlap (1250).

[0433] To support NC-JT, DCIs of various forms, structures, and relationships can be considered to simultaneously allocate multiple PDSCHs to a single terminal.

[0434] FIG. 13 is a diagram illustrating an example of the configuration of downlink control information (DCI) for NC-JT in which each TRP transmits different PDSCH or different PDSCH layers to a terminal in a wireless communication system according to one embodiment of the present disclosure.

[0435] Referring to FIG. 13, case #1 (1300) is an example in which, in addition to the serving TRP (TRP#0) used for a single PDSCH transmission, (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)), and control information for the PDSCHs transmitted from the (N-1) additional TRPs is transmitted independently of the control information for the PDSCH transmitted from the serving TRP. That is, the terminal can obtain control information for the PDSCHs transmitted from different TRPs (TRP#0 to TRP#(N-1)) through independent DCIs (DCI#0 to DCI#(N-1)). The formats between the independent DCIs may be the same or different from each other, and the payloads between the DCIs may also be the same or different from each other. In the aforementioned case #1, the degrees of freedom for each PDSCH control or allocation can be fully guaranteed, but if each DCI is transmitted from different TRPs, coverage differences per DCI may occur, which may degrade reception performance.

[0436] Case #2 (1305) shows an example in which (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) in addition to the serving TRP (TRP#0) used for a single PDSCH transmission, and control information (DCI) for the PDSCHs of the (N-1) additional TRPs is transmitted to each, and each of these DCIs is dependent on the control information for the PDSCH transmitted from the serving TRP.

[0437] For example, DCI#0, which is control information for PDSCH transmitted from a serving TRP (TRP#0), includes all information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2, but shortened DCI (hereinafter sDCI) (sDCI#0 to sDCI#(N-2)), which is control information for PDSCH transmitted from cooperative TRPs (TRP#1 to TRP#(N-1)), may include only some of the information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2. Therefore, in the case of sDCI transmitting control information for PDSCH transmitted from cooperative TRPs, since the payload is smaller compared to normal DCI (nDCI) transmitting PDSCH-related control information transmitted from a serving TRP, it is possible to include reserved bits compared to nDCI.

[0438] In the aforementioned case #2, the degree of freedom for each PDSCH control or allocation may be limited depending on the content of the information elements included in sDCI, but since the receiving performance of sDCI becomes superior to that of nDCI, the probability of coverage difference between DCIs occurring may be reduced.

[0439] Case #3 (1310) illustrates an example in which (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) other than the serving TRP (TRP#0) used for a single PDSCH transmission, and a single control information for the PDSCHs of the (N-1) additional TRPs is transmitted, and this DCI is dependent on the control information for the PDSCH transmitted from the serving TRP.

[0440] For example, DCI#0, which is control information for a PDSCH transmitted from a serving TRP (TRP#0), includes all information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2, and for control information for PDSCHs transmitted from cooperative TRPs (TRP#1 to TRP#(N-1)), it is possible to collect and transmit only some of the information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2 into a single 'secondary' DCI (sDCI). For example, the sDCI may include at least one piece of HARQ-related information such as frequency domain resource assignment, time domain resource assignment, and MCS of cooperative TRPs. In addition, for information not included in sDCI, such as BWP (bandwidth part) indicators or carrier indicators, the DCI of the serving TRP (DCI#0, normal DCI, nDCI) may be followed.

[0441] In case #3 (1310), the degree of freedom for each PDSCH control or allocation may be limited depending on the content of the information element included in the sDCI, but the reception performance of the sDCI can be adjusted, and the complexity of the terminal's DCI blind decoding can be reduced compared to case #1 (1300) or case #2 (1305).

[0442] Case #4 (1315) is an example in which, in a situation where (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) in addition to the serving TRP (TRP#0) used for a single PDSCH transmission, control information for the PDSCHs transmitted from the (N-1) additional TRPs is transmitted in the same DCI (Long DCI) as the control information for the PDSCH transmitted from the serving TRP. That is, the terminal can obtain control information for the PDSCHs transmitted from different TRPs (TRP#0 to TRP#(N-1)) through a single DCI. In the case of Case #4 (1315), the complexity of the terminal's DCI blind decoding may not increase, but the freedom of PDSCH control or allocation may be low, such as when the number of cooperating TRPs is limited by the long DCI payload limit.

[0443] In the following descriptions and embodiments, sDCI may refer to various auxiliary DCIs, such as shortened DCI, secondary DCI, or normal DCI (DCI formats 1_0 to 1_1 described above) containing PDSCH control information transmitted from a cooperative TRP, and unless a specific limitation is specified, such description may be similarly applied to the various auxiliary DCIs.

[0444] In the following description and embodiments, the aforementioned cases #1 (1300), #2 (1305), and #3 (1310), in which one or more DCIs (PDCCHs) are used to support NC-JT, may be classified as multiple PDCCH-based NC-JT, and the aforementioned case #4 (1315), in which a single DCI (PDCCH) is used to support NC-JT, may be classified as single PDCCH-based NC-JT. In PDCCH transmission based on multiple PDCCHs, a CORESET in which the DCI of the serving TRP (TRP#0) is scheduled and a CORESET in which the DCIs of the cooperating TRPs (TRP#1 to TRP#(N-1)) are scheduled may be distinguished. Methods for distinguishing the CORESETs may include distinguishing them through upper layer indicators for each CORESET, or distinguishing them through beam settings for each CORESET. In addition, in a single PDCCH-based NC-JT, instead of a single DCI scheduling multiple PDSCHs, a single PDSCH having multiple layers is scheduled, and the aforementioned multiple layers can be transmitted from multiple TRPs. In this case, the connection relationship between a layer and the TRP transmitting that layer can be indicated through a TCI (Transmission Configuration Indicator) indication for the layer.

[0445] In the embodiments of the present disclosure, "cooperative TRP" may be replaced with various terms such as "cooperative panel" or "cooperative beam" in actual application.

[0446] In the embodiments of the present disclosure, the phrase “where NC-JT is applied” can be interpreted in various ways depending on the situation, such as “where a terminal receives one or more PDSCHs simultaneously in one BWP,” “where a terminal receives PDSCHs based on two or more TCI (Transmission Configuration Indicator) indications simultaneously in one BWP,” or “where the PDSCHs received by the terminal are associated with one or more DMRS port groups,” but for the convenience of explanation, it has been used as a single expression.

[0447] In the present disclosure, the wireless protocol structure for NC-JT can be used in various ways depending on the TRP deployment scenario. For example, when there is no or small backhaul delay between cooperative TRPs, a method using a structure based on MAC layer multiplexing similar to S10 in FIG. 4 (CA-like method) is possible. On the other hand, when the backhaul delay between cooperative TRPs is large enough to be negligible (e.g., when more than 2 ms is required for information exchange such as CSI, scheduling, and HARQ-ACK between cooperative TRPs), a method using a structure independent of each TRP from the RLC layer to secure delay-robust characteristics (DC-like method) is possible, similar to S20 in FIG. 4.

[0448] A terminal supporting C-JT and / or NC-JT can receive C-JT and / or NC-JT related parameters or setting values, etc., from the upper layer configuration and set the terminal's RRC parameters based thereon. For the upper layer configuration, the terminal can utilize UE capability parameters, for example, tci-StatePDSCH. Here, UE capability parameters, for example, tci-StatePDSCH, can define TCI states for the purpose of PDSCH transmission, and the number of TCI states can be set to 4, 8, 16, 32, 64, or 128 in FR1, and to 64 or 128 in FR2. Among the set number, up to 8 states can be configured, which can be indicated by the 3 bits of the TCI field of the DCI via a MAC CE message. The maximum value 128 refers to the value indicated by maxNumberConfiguredTCIstatesPerCC within the tci-StatePDSCH parameter included in the terminal's capability signaling. In this way, a series of configuration processes from upper layer configuration to MAC CE configuration can be applied to beamforming instructions or beamforming change commands for at least one PDSCH in one TRP.

[0449] [Multi-DCI-based Multi-TRP]

[0450] As an embodiment of the present disclosure, a multi-DCI-based multi-TRP transmission method is described. The multi-DCI-based multi-TRP transmission method can establish a downlink control channel for NC-JT transmission based on a multi-PDCCH.

[0451] In NC-JT based on multiple PDCCH, when transmitting DCI for the PDSCH schedule of each TRP, a CORESET or search space separate for each TRP may be provided. The CORESET or search space per TRP can be configured as in at least one of the following cases.

[0452] * Setting the upper layer index per CORESET: The CORESET setting information configured as the upper layer may include an index value, and the TRP transmitting the PDCCH from the corresponding CORESET can be distinguished by the configured CORESET-specific index value. That is, in a set of CORESETs with the same upper layer index value, it can be assumed that the same TRP transmits the PDCCH, or that a PDCCH scheduling the PDCCH of the same TRP is transmitted. The aforementioned CORESET-specific index may be named as CORESETPoolIndex, and for CORESETs with the same CORESETPoolIndex value configured, it can be assumed that the PDCCH is transmitted from the same TRP. For a CORESET where the CORESETPoolIndex value is not configured, it can be assumed that the default value of CORESETPoolIndex is configured, and the aforementioned default value may be 0.

[0453] In the present disclosure, if the type of CORESETPoolIndex that each of the multiple CORESETs included in the upper layer signaling PDCCH-Config has exceeds one, that is, if each CORESET has a different CORESETPoolIndex, the terminal may consider that the base station can use a multi-DCI-based multi-TRP transmission method.

[0454] In contrast, in the present disclosure, if there is only one type of CORESETPoolIndex that each of the multiple CORESETs included in the upper layer signaling PDCCH-Config has, that is, if all CORESETs have the same CORESETPoolIndex of 0 or 1, the terminal may consider that the base station transmits using single-TRP rather than using a multi-DCI-based multi-TRP transmission method.

[0455] Multiple PDCCH-Config Settings: Multiple PDCCH-Configs are configured within a single BWP, and each PDCCH-Config may include PDCCH settings per TRP. That is, a single PDCCH-Config may contain a list of CORESETs and / or a list of search spaces per TRP, and one or more CORESETs and one or more search spaces included in a single PDCCH-Config may be considered to correspond to a specific TRP.

[0456] CORESET Beam / Beam Group Configuration: TRPs corresponding to a given CORESET can be distinguished through beams or beam groups configured per CORESET. For example, if the same TCI state is configured for multiple CORESETs, those CORESETs can be considered to be transmitted through the same TRP, or a PDCCH scheduling a PDSCH of the same TRP within that CORESET can be considered to be transmitted.

[0457] Search Space Beam / Beam Group Configuration: Beams or beam groups are configured for each search space, allowing TRPs to be distinguished by search space. For example, if the same beam / beam group or TCI state is set in multiple search spaces, it can be assumed that the same TRP is transmitting a PDCCH in that search space, or that a PDCCH scheduling a PDSCH for the same TRP is being transmitted in that search space.

[0458] As described above, by separating the CORESET or search space by TRP, it is possible to classify PDSCH and HARQ-ACK information for each TRP, which enables the creation of independent HARQ-ACK codebooks and the use of independent PUCCH resources for each TRP.

[0459] The above settings may be independent per cell or per BWP. For example, two different CORESETPoolIndex values ​​may be set for a PCell, while a specific SCell may not have a CORESETPoolIndex value set. In this case, NC-JT transmission may be configured for the PCell, whereas NC-JT transmission may not be configured for the SCell where the CORESETPoolIndex value is not set.

[0460] Figure 10 illustrates the process for beam setting and activation of PDSCH.

[0461] A PDSCH TCI state activation / deactivation MAC-CE applicable to a multi-DCI-based multi-TRP transmission method may follow FIG. 10. A base station may set M TCI states (TCI state #0, TCI state #1,..., TCI state #M-1) to a terminal via upper layer signaling (1000). The base station may activate some of the M TCI states, for example, TCI state #0', TCI state #1',..., TCI state #K-1, via MAC CE signaling for PDSCH (1020). This may be referred to as MAC CE-based beam indication. The base station may indicate one of the activated TCI states, for example, TCI state #0', TCI state #1',..., TCI state #K-1, a TCI state (TCI state #I), via DCI (1040). This can be called DCI-based beam selection. If the terminal has not received a CORESETPoolIndex for each of the CORESETs in the upper layer signaling PDCCH-Config, the terminal may ignore the CORESET Pool ID field (1055) in the corresponding MAC-CE (1050).If the terminal can support a multi-DCI-based multi-TRP transmission method, that is, if the terminal has different CORESETPoolIndexes for each CORESET within the upper layer signaling PDCCH-Config, the terminal can activate the TCI state within the DCI containing the PDCCH transmitted from CORESETs having a CORESETPoolIndex value equal to the CORESET Pool ID field (1055) value within the MAC-CE (1050). For example, if the CORESET Pool ID field (1055) value within the MAC-CE (1050) is 0, the TCI state within the DCI containing the PDCCH transmitted from CORESETs with a CORESETPoolIndex of 0 can follow the activation information of the MAC-CE.

[0462] When a terminal is configured by a base station to use a multi-DCI-based multi-TRP transmission method, that is, when the types of CORESETPoolIndexes possessed by each of the multiple CORESETs included in the upper layer signaling PDCCH-Config exceed one, or when each CORESET has different CORESETPoolIndexes, the terminal can see that the following constraints exist for PDSCHs scheduled from PDCCHs within each CORESET having two different CORESETPoolIndexes.

[0463] 1) When the terminals have PDSCHs indicated from PDCCHs within each CORESET with two different CORESETPoolIndexes that completely or partially overlap, the TCI states indicated from each PDCCH can be applied to different CDM groups. That is, two or more TCI states may not be applied to a single CDM group.

[0464] 2) When the terminal completely or partially overlaps the PDSCHs indicated from the PDCCHs within each CORESET having two different CORESETPoolIndexes, the actual number of front-loaded DMRS symbols, the actual number of additional DMRS symbols, the location of the actual DMRS symbols, and the DMRS type of each PDSCH can be expected not to differ.

[0465] 3) The terminal can expect that the bandwidth portion indicated by the PDCCH in each CORESET having two different CORESETPoolIndexes will be the same and the subcarrier spacing will also be the same.

[0466] 4) The terminal can expect that each PDCCH will fully contain information about the PDSCH scheduled from the PDCCH within each CORESET having two different CORESETPoolIndexes.

[0467] [Single-DCI-based Multi-TRP]

[0468] As an embodiment of the present disclosure, a single-DCI-based multi-TRP transmission method is described. The single-DCI-based multi-TRP transmission method can establish a downlink control channel for NC-JT transmission based on a single-PDCCH.

[0469] In a single DCI-based multi-TRP transmission method, a PDSCH transmitted by multiple TRPs can be scheduled using a single DCI. In this case, the number of TCI states can be used as a method to indicate the number of TRPs transmitting the PDSCH. That is, if the number of TCI states indicated in the DCI scheduling the PDSCH is 2, it can be considered as single PDCCH-based NC-JT transmission, and if the number of TCI states is 1, it can be considered as single-TRP transmission. The TCI states indicated in the above-mentioned DCI may correspond to one or two TCI states among the TCI states activated by MAC-CE. When the TCI states of the DCI correspond to two TCI states activated by MAC-CE, a correspondence relationship is established between the TCI codepoint indicated in the DCI and the TCI states activated by MAC-CE, and this may be the case when there are two TCI states activated by MAC-CE corresponding to the said TCI codepoint.

[0470] As another example, if at least one of the codepoints in the TCI state field within the DCI points to two TCI states, the terminal can assume that the base station can transmit based on a single-DCI-based multi-TRP method. In this case, at least one codepoint pointing to two TCI states within the TCI state field can be activated via the Enhanced PDSCH TCI state activation / deactivation MAC-CE.

[0471] Figure 14 is a diagram showing the Enhanced PDSCH TCI state activation / deactivation MAC-CE structure. The meaning of each field within the MAC-CE and the values ​​that can be set for each field are as shown in [Table 27] below.

[0472] [Table 27]

[0473]

[0474] In FIG. 14, if the value of the C0 field (1405) is 1, the corresponding MAC-CE is the TCI state ID 0,1 In addition to field (1410), TCI state ID 0,2 It may include a field (1415). This is the TCI state ID for the 0th codepoint of the TCI state field included in the DCI. 0,1 and TCI state ID 0,2 This means that it is activated, and if the base station instructs the terminal with the corresponding codepoint, the terminal may be instructed with two TCI states. If the value of the C0 field (1405) is 0, the MAC-CE is the TCI state ID 0,2 The field (1415) cannot be included, which is the TCI state ID for the 0th codepoint of the TCI state field included in the DCI. 0,1 This means that one TCI state corresponding to it is activated.

[0475] The above-described settings may be independent per cell or per BWP. For example, a PCell may have up to two activated TCI states corresponding to a single TCI codepoint, whereas a specific SCell may have up to one activated TCI state corresponding to a single TCI codepoint. In this case, it can be considered that NC-JT transmission is configured in the PCell, whereas NC-JT transmission is not configured in the aforementioned SCell.

[0476] [How to Distinguish Single-DCI-based Multi-TRP PDSCH Iterative Transmission Techniques (TDM / FDM / SDM)]

[0477] Next, a method for distinguishing single-DCI-based multi-TRP PDSCH repetitive transmission techniques is described. Depending on the value indicated by the DCI field from the base station and the upper layer signaling settings, the terminal may be instructed to use different single-DCI-based multi-TRP PDSCH repetitive transmission techniques (e.g., TDM, FDM, SDM). Table 28 below shows a method for distinguishing between single or multi-TRP-based techniques instructed to the terminal based on the value of a specific DCI field and the upper layer signaling settings.

[0478] [Table 28]

[0479]

[0480] In the above [Table 28], each column can be described as follows.

[0481] - Number of TCI states (Column 2): Refers to the number of TCI states indicated by the TCI state field within the DCI, and can be 1 or 2.

[0482] - Number of CDM groups (Column 3): Refers to the number of different CDM groups of DMRS ports indicated by the Antenna port field within the DCI. It can be 1, 2 to 3.

[0483] - RepetitionNumber setting and indication conditions (Column 4): There can be 3 conditions depending on whether the repetitionNumber is set for all TDRA entries that can be indicated by the Time Domain Resource Allocation field within the DCI and whether the actual indicated TDRA entry has the repetitionNumber setting.

[0484] Condition 1: If at least one of all TDRA entries that can be indicated by the Time Domain Resource Allocation field contains a setting for repetitionNumber, and a TDRA entry indicated by the Time Domain Resource Allocation field within the DCI contains a setting for repetitionNumber greater than 1

[0485] Condition 2: If at least one of all TDRA entries that can be indicated by the Time Domain Resource Allocation field includes a setting for repetitionNumber, and the TDRA entry indicated by the Time Domain Resource Allocation field within the DCI does not include a setting for repetitionNumber

[0486] Condition 3: If all TDRA entries that can be indicated by the Time Domain Resource Allocation field do not include a setting for repetitionNumber

[0487] - Regarding repetitionScheme settings (Column 5): Indicates whether the upper layer signaling repetitionScheme is set. The upper layer signaling repetitionScheme can be set to one of 'tdmSchemeA', 'fdmSchemeA', or 'fdmSchemeB'.

[0488] - Transmission technique instructed to the terminal (Column 6): Refers to single or multiple TRP techniques instructed according to each combination (Column 1) expressed in [Table 28] above.

[0489] Single-TRP: Refers to a single TRP-based PDSCH transmission. If the terminal has the pdsch-AggegationFactor configured within the upper-layer signaling PDSCH-config, the terminal can be scheduled for repeated single-TRP-based PDSCH transmissions as many times as configured. Otherwise, the terminal can be scheduled for a single single-TRP-based PDSCH transmission.

[0490] Single-TRP TDM scheme B: Refers to PDSCH repetitive transmission based on time resource partitioning between slots based on a single TRP. In accordance with Condition 1 regarding the repetitionNumber described above, the terminal repetitively transmits PDSCH in the time dimension for a number of slots equal to the repetitionNumber set in the TDRA entry specified by the Time Domain Resource Allocation field, which is greater than 1. At this time, for each slot corresponding to the repetitionNumber, the starting symbol and symbol length of the PDSCH specified by the TDRA entry are applied identically, and the same TCI state is applied for each PDSCH repetitive transmission. This technique is similar to the slot aggregation method in that it performs PDSCH repetitive transmission between slots in the time resource, but it differs from slot aggregation in that it can dynamically determine whether to instruct repetitive transmission based on the Time Domain Resource Allocation field within the DCI.

[0491] Multi-TRP SDM: Refers to a multi-TRP-based spatial resource partitioning PDSCH transmission method. This is a method of receiving layers by dividing them from each TRP; although it is not a repetitive transmission method, it can increase the reliability of PDSCH transmission by increasing the number of layers and lowering the coding rate. For each of the two CDM groups instructed by the base station, the terminal can receive PDSCH by applying the two TCI states instructed through the TCI state field within the DCI.

[0492] Multi-TRP FDM scheme A: This refers to a multi-TRP-based Frequency Resource Allocation PDSCH transmission method. It utilizes a single PDSCH transmission occasion; unlike multi-TRP SDM, it does not involve repetitive transmission, but it is a technique that enables high-reliability transmission by increasing the amount of frequency resources and lowering the coding rate. Multi-TRP FDM scheme A can apply two TCI states, indicated via the TCI state field within the DCI, to non-overlapping frequency resources. If the PRB bundling size is determined to be wideband, the terminal receives the first ceil(N / 2) RBs by applying the first TCI state and the remaining floor(N / 2) RBs by applying the second TCI state, provided that the number of RBs indicated by the Frequency Domain Resource Allocation field is N. Here, ceil(.) and floor(.) are operators representing rounding up and rounding down to the first decimal place. If the PRB bundling size is determined to be 2 or 4, even-numbered PRGs apply the first TCI state and odd-numbered PRGs apply the second TCI state to receive.

[0493] Multi-TRP FDM scheme B: This refers to a multi-TRP-based frequency resource partitioning PDSCH repetitive transmission scheme. It has two PDSCH transmission occasions, allowing for the repetitive transmission of PDSCH to each occasion. Similar to A, Multi-TRP FDM scheme B can apply two TCI states, indicated via the TCI state field within the DCI, to non-overlapping frequency resources. If the PRB bundling size is determined to be wideband, the terminal receives the first ceil(N / 2) RBs by applying the first TCI state and the remaining floor(N / 2) RBs by applying the second TCI state, provided that the number of RBs indicated by the Frequency Domain Resource Allocation field is N. Here, ceil(.) and floor(.) are operators representing rounding up and rounding down to the first decimal place. If the PRB bundling size is determined to be 2 or 4, even-numbered PRGs apply the first TCI state and odd-numbered PRGs apply the second TCI state to receive.

[0494] Multi-TRP TDM scheme A: Refers to a PDSCH repetitive transmission scheme within a time resource allocation slot based on multiple TRPs. A terminal has two PDSCH transmission occasions within a single slot, and the first reception occasion can be determined based on the starting symbol and symbol length of the PDSCH indicated by the Time Domain Resource Allocation field within the DCI. The starting symbol of the second reception occasion of the PDSCH can be the position obtained by applying a symbol offset of StartingSymbolOffsetK, an upper-layer signaling, from the last symbol of the first transmission occasion, and the transmission occasion can be determined by the indicated symbol length from this. If the upper-layer signaling StartingSymbolOffsetK is not set, the symbol offset can be considered as 0.

[0495] Multi-TRP TDM scheme B: Refers to a PDSCH repetitive transmission scheme between slots based on multi-TRP time resource allocation. A terminal has one PDSCH transmission occasion within a slot and can receive repetitive transmissions based on the same PDSCH start symbol and symbol length for a number of slots specified by the repetitionNumber in the Time Domain Resource Allocation field within the DCI. If the repetitionNumber is 2, the terminal can receive the PDSCH repetitive transmissions of the first and second slots by applying the first and second TCI states, respectively. If the repetitionNumber is greater than 2, the terminal can use different TCI state application methods depending on how the upper layer signaling, tciMapping, is set. If tciMapping is set to cyclicMapping, the first and second TCI states are applied to the first and second PDSCH transmission occasions, respectively, and this same TCI state application method is applied to the remaining PDSCH transmission occasions. If tciMapping is set to sequenticalMapping, the first TCI state is applied to the first and second PDSCH transmission locations, the second TCI state is applied to the third and fourth PDSCH transmission locations, and the same method of applying TCI states is applied to the remaining PDSCH transmission locations.

[0496] Embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. The contents of the present disclosure are applicable to FDD (frequency division duplex), TDD (time division duplex) and / or XDD (cross division duplex) (and / or SBFD (subband non-overlapping full duplex), full duplex) systems. In the present disclosure below, upper signaling (or upper layer signaling) is a signal transmission method transmitted from a base station to a terminal using a downlink data channel of the physical layer, or from a terminal to a base station using an uplink data channel of the physical layer, and may be referred to as RRC signaling, PDCP signaling, or a MAC (medium access control) control element (MAC control element; MAC CE).

[0497] For convenience in the following description of the present disclosure, cells, transmission points, panels, beams, and / or transmission directions that can be distinguished through upper layer / L1 parameters such as TCI state or spatial relation information, or indicators such as cell ID, TRP ID, and panel ID, may be described uniformly as TRP (transmission reception point), beam, or TCI state. Therefore, in actual application, TRP, beam, or TCI state can be appropriately replaced with one of the above terms.

[0498] In the present disclosure, when determining whether cooperative communication is applied, the terminal may use various methods, such as the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied having a specific format, or the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied including a specific indicator indicating whether cooperative communication is applied, or the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied being scrambled with a specific RNTI, or assuming the application of cooperative communication in a specific section indicated to an upper layer. For convenience of explanation thereafter, the case in which the terminal receives a PDSCH to which cooperative communication is applied based on conditions similar to those above will be referred to as the NC-JT case.

[0499] Hereinafter, the base station is an entity that performs resource allocation for terminals and may be at least one of a gNode B, gNB, eNode B, Node B, BS (Base Station), wireless access unit, base station controller, or a node on a network. The terminal may include a UE (User Equipment), MS (Mobile Station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions. Although embodiments of the present disclosure are described below using a 5G system as an example, embodiments of the present disclosure may be applied to other communication systems having similar technical backgrounds or channel types. For example, LTE or LTE-A mobile communication and mobile communication technologies developed after 5G may be included therein. Accordingly, embodiments of the present disclosure may be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure, in the judgment of a person skilled in the art.

[0500] Furthermore, in describing the present disclosure, if it is determined that a detailed description of related functions or configurations could unnecessarily obscure the essence of the present disclosure, such detailed description is omitted. Additionally, the terms described below are defined in consideration of their functions within the present disclosure, and these definitions may vary depending on the intent or practices of the user or operator. Therefore, their definitions should be based on the content throughout this specification.

[0501] In describing the present disclosure below, the term "upper layer signaling" may refer to a signaling corresponding to at least one or a combination of at least one of the following signalings.

[0502] - MIB (Master Information Block)

[0503] - SIB (System Information Block) or SIB

[0504] - RRC (Radio Resource Control)

[0505] - MAC (Medium Access Control) CE (Control Element)

[0506] In addition, L1 signaling may be a signaling corresponding to at least one or a combination of at least one of the following physical layer channels or signaling methods using signaling.

[0507] - PDCCH (Physical Downlink Control Channel)

[0508] - DCI (Downlink Control Information)

[0509] - Terminal-specific (UE-specific) DCI

[0510] - Group common DCI

[0511] - Common DCI

[0512] - Scheduling DCI (e.g., DCI used for the purpose of scheduling downlink or uplink data)

[0513] - Non-scheduling DCI (e.g., DCI not intended for scheduling downlink or uplink data)

[0514] - PUCCH (Physical Uplink Control Channel)

[0515] - UCI (Uplink Control Information)

[0516] In the following disclosure, determining the priority between A and B may be referred to in various ways, such as selecting the one with the higher priority according to a predetermined priority rule and performing the corresponding action, or omitting or dropping the action for the one with the lower priority.

[0517] The term "slot" used in the present disclosure below is a general term that may refer to a specific time unit corresponding to TTI (Transmit Time Interval), and specifically, it may refer to a slot used in a 5G NR system, or a slot or subframe used in a 4G LTE system.

[0518] In the following disclosure, the examples are described through a number of embodiments, but these are not independent, and one or more embodiments may be applied simultaneously or in combination.

[0519] In one embodiment of the present disclosure, the process by which a base station acquires a CSI report transmitted by a terminal to a base station is described. This embodiment may operate in combination with other embodiments.

[0520] To flexibly and efficiently perform control and scheduling for multiple cells, a base station may be configured with a structure in which multiple Radio Units (RUs) or Massive MIMO Units (MMUs) are connected to a Distributed Unit (DU). In this case, a single DU can perform scheduling to transmit DL signals and channels to terminals through multiple RUs or multiple MMUs, and conversely, UL signals and channels transmitted from terminals can be received by multiple RUs or multiple MMUs and processed by a single DU. In the following description, MMU or RU may be used interchangeably with TRP. In the description of the present disclosure, MMU, RU, and TRP may be used interchangeably or substituted. In the description of the present disclosure, the operation of MMU, RU, and DU may also be understood as the operation of a base station including MMU, RU, and DU. It may be an operation based on each MMU, RU, and DU of a base station including MMU, RU, and DU.

[0521] FIG. 15a is a drawing illustrating elements constituting a base station according to one embodiment of the present disclosure.

[0522] A base station may be composed of one DU (1500) and two MMUs (e.g., a first MMU (1505) (MMU#1) and a second MMU (1510) (MMU#2)). One DU and one MMU may be connected to each other via a fronthaul (FH) (1515).

[0523] A terminal (1520) may transmit a CSI report (1525, 1530) to a specific MMU or to all MMUs in common to transmit it to a base station. The terminal (1520) may transmit the CSI report to either the first MMU (1505) or the second MMU (1510). Alternatively, the terminal (1520) may transmit the CSI report to both the first MMU (1505) and the second MMU (1510). At this time, a base station composed of one DU connected to multiple MMUs may receive the CSI report transmitted by the terminal and perform scheduling for the terminal based on it. That is, the CSI transmitted by the terminal is decoded by the DU so that the base station can verify the information, and by decoding the CSI reported by multiple terminals in this way, the DU can determine how to allocate each terminal to which time and frequency resources. Multiple CSIs received from multiple terminals are decoded in the DU, and the DU (base station) can perform time / frequency resource scheduling for multiple terminals based on the decoding results. A more specific process for this can be described as follows. In the following description, the MMU may be at least one of the first MMU (1505) or the second MMU (1510).

[0524] FIG. 15b is a diagram showing an example of the process in which a base station obtains channel state information of a terminal through CSI transmitted by the terminal.

[0525] FIG. 15b illustrates an exemplary method that may be implemented according to the principles of the present disclosure, and various modifications may be made to the method illustrated in FIG. 15b. For example, although illustrated as a series of steps, the various steps in each figure may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.

[0526] At step 1550, the terminal can transmit a CSI report to the MMU. The CSI report may be transmitted within a PUCCH or PUSCH.

[0527] In step 1555, the MMU may transmit information regarding a PUCCH or PUSCH containing a CSI report of the terminal to the DU via the fronthall, and this information may be transmitted via the user plane, which is an interface within the fronthall, whereby the real part or imaginary part data of the PUCCH or PUSCH may be transmitted by quantizing into a specific number of bits, respectively. The number of bits that may be considered may be 9, 11, or 16 bits for the real part and the imaginary part, respectively. The real part and / or imaginary part of the PUCCH and / or PUSCH may be transmitted by quantizing into 9 bits, 11 bits, or 16 bits.

[0528] In step 1560, a DU that receives information about a PUCCH or PUSCH containing the terminal's CSI can decode the CSI contained within the PUCCH or PUSCH to identify / identify the CSI information reported by the terminal.

[0529] In step 1565, the DU can determine the scheduling for the terminal based on the CSI information. At this time, the scheduling for the terminal may be in the form of SU-MIMO (Single-User Multiple-Input Multiple-Output), which allocates only the terminal to a specific time and frequency resource, or in the form of MU-MIMO (Multi-User Multiple-Input Multiple-Output), which allocates the terminal and other terminals together to the same time and frequency resource.

[0530] In step 1570, the DU may transmit the scheduling information to the MMU. The information included therein may include time and frequency resource allocation information, information related to the precoder to be used by the terminal, and the MCS level. The information related to the precoder to be used by the terminal may include information on which PMI to use and what the rank value is when using an already defined PMI, and how to process the channel estimated through the SRS when using an SRS-based precoder.

[0531] In step 1575, the MMU can generate and apply a downlink precoder to the corresponding terminal based on scheduling information received from the DU. The MMU may store a complete set of PMIs in preparation for receiving information from the DU regarding the application of a PMI-based downlink precoder. A complete set of PMIs may be pre-configured in the MMU. Based on the complete set of PMIs, operations related to the application of a PMI-based downlink precoder may be performed. Therefore, if the scheduling information received from the DU includes information that a PMI is to be used as a downlink precoder to be applied to a specific terminal, the MMU can identify the specific PMI instructed by the DU within the complete set of PMIs stored in the MMU and select it as the downlink precoder to be applied to the terminal. The DU may instruct the MMU to use a specific PMI, instruct it to generate a specific precoder through a linear combination of one or more PMIs, or instruct it to use each element of the specific PMI with some modifications. Additionally, the DU may transmit instructions to the MMU to update the entire set of PMIs, and after such updates, the DU and MMU may send and receive instructions for the use of specific PMIs under the assumption that the entire set of PMIs is different from that before the updates. The entire set of PMIs may change before and after the updates. After the updates, instructions for the use of specific PMIs within the updated entire set of PMIs may be sent and received.

[0532] In step 1580, the MMU can apply the downlink precode to transmit PDSCH to the terminal. The MMU can transmit scheduling information for PDSCH. Additionally, the MMU can transmit PDSCH to the terminal. At this time, as described above, the terminal can be scheduled in the form of SU-MIMO or MU-MIMO.

[0533] When the above process is performed, if the terminal is scheduled to receive a PDSCH from the base station (1580), the precoder applied to the PDSCH may be based on information from the CSI previously reported by the terminal. Applying the precoder to the PDSCH may be performed based on information from the CSI previously reported by the terminal. For convenience of explanation, the time when the terminal reports the CSI and the time when it receives the PDSCH are named T1 and T2, respectively. If the time interval between T1 and T2 is large (e.g., if the time interval is above / exceeds a certain threshold), the downlink precoder applied to the PDSCH transmitted to the terminal may be the one reported at time T1, which is a time much earlier than T2, the time when the downlink precoder is actually applied, and thus a downlink precoder that does not match the channel between the base station and the terminal at time T2 may be applied.

[0534] The primary reason for this situation is that the CSI reported by the terminal is identified in the DU and can be used for scheduling based on that CSI. The degradation factors that may occur during this process may be as follows.

[0535] - (Fronthall Quantization) The CSI reported by the terminal is transmitted to the MMU via PUCCH or PUSCH, and when the MMU receives it and sends it to the fronthall, it undergoes a quantization process as described above. At this time, quantization errors may occur in the real part and / or imaginary part symbols of PUCCH and / or PUSCH, and this may affect subsequent decoding in the DU.

[0536] - (Fronthall Latency) The CSI reported by the terminal is transmitted from the MMU to the DU via fronthall, and the transmission of the corresponding PUCCH or PUSCH may be delayed depending on what information is being transmitted via fronthall. As a result, the time at which the DU starts CSI decoding may be delayed.

[0537] - (DU Uplink Processing) The CSI reported by a terminal can undergo a decoding process in the DU. At this time, since the DU must perform uplink data processing for other terminals as well as the terminal in question, the more terminals requiring uplink data processing there are, the later the start of CSI decoding for the terminal may be, and consequently, the time until the decoding of the CSI is completed and reflected in the scheduling may be delayed.

[0538] - (CSI applied to PDSCH is the CSI used for scheduling) The DU performs scheduling based on the CSI reported by the terminal, and the CSI used for scheduling can be applied directly to PDSCH transmission. Therefore, if there is a difference between the time the terminal reports the CSI and the time the terminal receives the PDSCH, performance degradation may occur when the CSI reported by the terminal is applied to PDSCH transmission. In addition, even if the terminal reports the CSI not only at T1 but also at T1-1 and T1-2 before time T2 and the MMU receives it, since CSI decoding can occur in the DU, the base station cannot utilize the CSI reported at T1-1 (1551) and T1-2 (1552) to apply to PDSCH.

[0539] At the base station, a method of decoding the CSI at the MMU can be used to utilize the CSI reported by the terminal more quickly and apply it to the terminal's downlink signal. If the CSI reported by the terminal is decoded at the MMU, the MMU can identify the terminal's CSI more quickly and use it for receiving the terminal's uplink channel / signal or transmitting it to the terminal's downlink channel / signal.

[0540] - If a terminal transmits an uplink channel / signal, and if channel reciprocity between the uplink and downlink channels is established, the MMU can receive the terminal's uplink transmission based on the PMI included in the CSI reported by the terminal. Since the PMI included in the CSI reported by the terminal is the information that best represents the channel between the terminal and the base station when the terminal receives the downlink channel / signal, this information can be similarly applied to the reception of an uplink channel / signal using the same channel between the base station and the terminal. If channel reciprocity between the uplink and downlink channels is established, the PMI included in the CSI reported by the terminal to the base station can also be applied to the uplink channel / signal between the same base station and the terminal.

[0541] - If a terminal receives a downlink channel / signal, when the MMU determines the downlink precoder to apply to the PDCCH or PDSCH to be transmitted to the terminal, if the MMU can decode the CSI reported by the terminal, the most recent PMI that can be included within the CSI reported by the terminal may be one of the candidates for the downlink precoder to be finally determined. Through this, the terminal can expect to receive the most recently reported CSI applied to the downlink channel / signal, which better represents the channel at the current time than the CSI reported at the previous time. That is, as described above, if the PDSCH reception time determined based on the CSI reported by the terminal at time T1 is T2, and the terminal performs additional CSI reporting at T1-1 (1551) and T1-2 (1552) between T1 and T2, and if the MMU can decode the corresponding CSI, then the MMU can apply the PMI within the latest CSI reported by the terminal at time T1-2 (1552) when transmitting the PDSCH at time T2.

[0542] - If a terminal reports to a base station information capable of correcting time, frequency, or / and phase differences between different MMUs (information for correcting time, frequency, or / and phase differences between different MMUs) (i.e., such CSI reporting may be of a different type than information such as PMI, RI, and CQI for the terminal's channel state information), an MMU without CSI decoding capability transmits such information to a DU, and the DU receives it, decodes the CSI information, and can retransmit the information required by each MMU to each MMU. Each MMU can perform correction based on the information capable of correcting time, frequency, or / and phase differences for each MMU that was retransmitted by the DU. If an MMU capable of CSI decoding is considered, the information capable of correcting time, frequency, or / and phase differences reported by the terminal can be decoded directly at the MMU to correct the value corresponding to each MMU. The MMU can provide information to the DU so that the DU can know the status of the MMU (whether it has received information that can correct the time, frequency, or / and phase difference reported by the terminal and / or whether correction has been applied relative to another MMU by applying it). Based on the status of the MMU, the DU can perform scheduling to transmit downlink data to a specific terminal in the form of coherent joint transmission (CJT).

[0543] In cases where the MMU can decode the CSI in this way, the signaling exchange between the terminal, MMU, and DU, and the scheduling process through the CSI, can be explained as follows.

[0544] FIG. 16 is another diagram illustrating an example of a process in which a base station obtains channel state information of a terminal through CSI transmitted by a terminal according to an embodiment of the present disclosure. FIG. 16 illustrates an exemplary method that can be implemented according to the principles of the present disclosure, and various modifications may be made to the method illustrated in FIG. 16. For example, although illustrated as a series of steps, the various steps of each figure may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, steps may be omitted or replaced with other steps. In the following description, the MMU may be at least one of a first MMU (1605) or a second MMU (1610).

[0545] In step 1650, the terminal (1620) may transmit a CSI report to the MMU. The CSI report may be transmitted within a PUCCH or PUSCH. According to one embodiment, the terminal (1620) may periodically perform CSI reports (1651, 1652).

[0546] In step 1655, the MMU can obtain CSI information of the corresponding terminal (1620) by decoding the CSI. At this time, the MMU can perform decoding only on the CSI portion of the PUCCH or PUSCH. If CSI reporting is performed periodically, the MMU can perform CSI decoding (1661, 1662) for it.

[0547] In step 1660, when the MMU subsequently transmits CSI information to the DU, the MMU may transmit to the DU the CSI information decoded by the MMU and the non-CSI parts (parts other than CSI) of the PUCCH or PUSCH. This information may be transmitted via the user plane, which is an interface within the fronthall, whereby the real or imaginary data of the PUCCH or PUSCH may be transmitted after being quantized into a specific number of bits. The number of bits that may be considered may be 9, 11, or 16 bits for the real and imaginary parts, respectively. The real and / or imaginary parts of the PUCCH and / or PUSCH may be transmitted after being quantized into 9 bits, 11 bits, or 16 bits.

[0548] In step 1665, the DU (1600) can determine the scheduling for the terminal (1620) based on the CSI information decoded and transmitted from the MMU. At this time, the scheduling for the terminal (1620) may be in the form of SU-MIMO (Single-User Multiple-Input Multiple-Output) which allocates only the terminal (1620) to a specific time and frequency resource, or in the form of MU-MIMO (Multi-User Multiple-Input Multiple-Output) which allocates the terminal (1620) and other terminals together to the same time and frequency resource.

[0549] In step 1670, the DU (1600) can transmit the scheduling information to the MMU. The information included therein may include time and frequency resource allocation information, information related to the precoder to be used by the terminal (1620), and the MCS level. In this case, regarding the information related to the precoder to be used by the terminal (1620), information may be transmitted regarding which PMI to use and what the rank value is if a predefined PMI is used, and how to process the channel estimated through the SRS if an SRS-based precoder is used. Additionally, since the DU (1600) knows that the MMU is capable of CSI decoding, the DU (1600) can transmit scheduling information related to downlink precoding by considering the presence or absence of CSI information received by the MMU at a later time than the CSI used when the DU (1600) generated the scheduling information. For example, the DU (1600) can transmit the PMI index and rank value to be used for the terminal (1620) to the MMU, and can additionally inform the MMU of at what time the scheduling information was generated based on the CSI reported by the terminal (1620). If the MMU receives a new CSI after that time and is decoding and storing it, the MMU can ignore the downlink precoder-related information in the scheduling information received from the DU (1600) and determine the downlink precoder based on the CSI stored by the MMU. In this case, if the rank value specified by the DU (1600) and the rank value in the CSI most recently stored by the MMU are different, the MMU may use the corresponding PMI by matching it to one of the rank values ​​(for example, matching it to the rank value specified by the DU (1600). For another example, matching it to the rank in the CSI most recently stored by the MMU), or prioritize the PMI specified by the DU.For example, if the PMI obtainable through the latest CSI has a rank of 1 and the PMI instructed by the DU (1600) has a rank of 2, the MMU can use the PMI instructed by the DU. Alternatively, the MMU can identify the most recent CSI value among the CSIs reported by the terminal (1620) that has the same value as the rank instructed by the DU (1600) and use the PMI contained within that CSI. For example, if the rank value contained within the downlink precoder information instructed by the DU (1600) is 2, and the scheduling information is derived from the CSI reported by the terminal at time T1, the MMU can determine the downlink precoder by using the CSI among the CSIs reported by the terminal (1620) after time T1 that has the same rank value as 2, the rank value instructed by the DU (1600). If there is no such CSI, the MMU can use the PMI directed by the DU (1600) as is.

[0550] In step 1675, the MMU can generate a downlink precoder based on the PMI determined in step (1670). If a specific terminal is scheduled in SU-MIMO mode, the terminal may use the PMI as is, make partial adjustments, or use a linear combination with another PMI as instructed by the DU. If a specific terminal is scheduled in MU-MIMO mode, the MMU can generate and apply a downlink precoder to the terminal by considering all channel state information of one or more terminals scheduled in MU-MIMO mode together, based on the scheduling information instructed / received from the DU (1600). This scheduling information may be provided to the MMU by the DU (1600). The MMU may include the index of terminals to be scheduled in a MU-MIMO manner from the DU (1600), the time and frequency resource locations of the terminals, information on whether to use the SRS information or PMI available to each terminal when generating a downlink precoder for each terminal, information on which PMI index to use if a specific terminal operates based on PMI, and rank information for each terminal. Additionally, if the DU (1600) knows that a specific MMU is capable of CSI decoding, when instructing the MMU to generate a downlink precoder, it may provide the MMU with information such as whether to generate the downlink precoder based on the most recent CSI information decoded by the MMU or to generate the downlink precoder based on the CSI used by the DU (1600) when generating the scheduling information.

[0551] In step 1680, the MMU can transmit PDSCH to the terminal (1620) by applying the downlink precoder. The MMU can transmit scheduling information for the PDSCH. Additionally, the MMU can transmit PDSCH to the terminal (1620). At this time, as described above, the terminal (1620) can be scheduled in the form of SU-MIMO or MU-MIMO.

[0552] For the above-described operation, the MMU can transmit capability information that CSI decoding is possible to the DU (1600). After the DU (1600) detects the existence of such an MMU (after confirming that the MMU is capable of CSI decoding), it can instruct the MMU whether to decode all incoming CSIs or only decode some specific CSIs.

[0553] For example, the MMU can decode and store all received CSIs. That is, all CSIs transmitted by the terminal (1620) are stored in the MMU, and the MMU can update with the latest CSI for each terminal. Through this, there may be an advantage that a DU that receives CSI information from different terminals from multiple MMUs does not have to decode the CSI, but only processes information other than the CSI (uplink data, HARQ-ACK information, scheduling request information, etc.).

[0554] As another example, the MMU can decode and store only some of the received CSIs, and pass the rest to the DU to have the DU perform decoding on the CSIs. CSIs decodingable by the MMU and CSIs decodingable by the DU (CSIs that cannot be decoded by the MMU) can be defined separately. The reason for defining CSIs that the MMU can selectively decode separately is that decoding all CSIs can cause computational burden in the MMU. For example, if the total bit length of the CSI is less than or equal to a specific value, or if the calculation time for the CSI defined for the terminal is less, the decoding time at the base station can be less, or / or if the CSI has relatively significant meaning (for example, if the priority value of the CSI defined / set for the terminal is less than or equal to a specific reference value, and thus has a higher priority compared to the CSI with that reference value (or the CSI with a priority value greater than or equal to that reference value)), the application time of the CSI can be advanced through decoding in the MMU.

[0555] When decoding CSI in the MMU, there is a possibility that a decoding block supporting relatively lower computational performance than the DU (1600) may be included, so the delay time for decoding CSI may increase when the same channel coding scheme is used. Therefore, different channel codings with optimized decoding complexity may be applied depending on the bit length of the CSI, and to this end, the terminal and the base station may assume that different channel codings are applied depending on the bit length of the CSI. The terminal may report to the base station whether it supports the application of different channel codings based on different CSI bit lengths.

[0556] - If a specific terminal supports this function, the terminal may receive upper-layer signaling from the base station, and this upper-layer signaling may mean that different channel coding schemes can be applied to CSI reports of different lengths. When the terminal reports a CSI to the base station, it may determine the channel encoding scheme for the CSI differently depending on the bit length of the CSI. If the base station receives a CSI report from such a terminal, and the MMU receiving the CSI provides a CSI decoding function, the MMU may decode the CSI report and store it. If the MMU does not provide a CSI decoding function, the MMU does not decode the received CSI but transmits it to the DU, so that the DU can perform the decoding.

[0557] - If a specific terminal does not support this function, the terminal may not receive upper-layer signaling from the base station indicating that different channel coding schemes may be applied to CSI reports of different lengths. Therefore, the terminal may not support different channel coding schemes for CSI reports of different lengths. If a specific terminal does not support this function, the terminal may not receive upper-layer signaling from the base station indicating that different channel coding schemes may be applied to CSI reports of different lengths. Therefore, the terminal may not support different channel coding schemes for CSI reports of different lengths. If the MMU provides a CSI decoding function, the MMU may perform decoding on the terminal's CSI and transmit the information to the DU, or perform decoding only on CSIs of a specific length and transmit the information to the DU, and transmit directly to the DU without decoding in other cases. If the MMU cannot provide CSI decoding functionality, the MMU does not decode the received CSI and passes it to the DU so that the DU can perform the decoding.

[0558] FIG. 17 is a drawing showing the operation of a terminal according to one embodiment of the present disclosure.

[0559] In step 1700, the terminal may transmit terminal capabilities to the base station. At this time, the terminal capability signaling that can be received by the base station may be a combination of at least one of the following: different channel coding schemes according to the bit length of the CSI, a multiplexing location determination method for the CSI within the PUSCH, the additional beta offset indication, the plurality of non-periodic CSI report slot offsets, and support for the CSI report information generation method. Step 1700 may be omitted.

[0560] In step 1705, the terminal can receive upper layer signaling from the base station. At this time, the terminal can receive from the base station at least one combination of each upper layer signaling related to different channel coding schemes according to the bit length of the CSI, a multiplexing location determination method for the CSI within the PUSCH, an additional beta offset instruction, a plurality of non-periodic CSI report slot offsets, and a method for generating CSI report information.

[0561] In step 1710, the terminal may be notified of a CSI report from the base station using at least one combination of upper layer signaling, MAC-CE signaling, and L1 signaling. Based on this notification, the terminal may identify the CSI report method that the base station transmitted to the terminal.

[0562] At step 1715, the terminal can perform a CSI report. This CSI report may be transmitted to a specific MMU or may be transmitted commonly to multiple MMUs.

[0563] In step 1720, the terminal may receive a DCI from the base station that may (or includes) PDSCH scheduling information. Based on the DCI, the terminal may obtain information related to PDSCH scheduling from the base station. Such scheduling information may be related to a CSI reported by the terminal. Such scheduling information may be determined based on the CSI reported by the terminal.

[0564] At step 1725, the terminal may receive a PDSCH from the base station. At this time, the downlink precoder applied to the PDSCH received by the terminal may be based on the CSI reflected in the scheduling of the PDSCH at the DU, or, if the MMU supports decoding of the CSI, may be CSI information that was received and updated more recently than the CSI reflected in the scheduling of the PDSCH.

[0565] The above-described flowchart illustrates an exemplary method that may be implemented in accordance with the principles of the present disclosure, and various modifications may be made to the method illustrated in the flowchart in this specification. For example, although illustrated as a series of steps, the various steps in each figure may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.

[0566] FIG. 18 is a drawing showing the operation of a base station according to one embodiment of the present disclosure.

[0567] In step 1800, the base station may receive terminal capabilities from the terminal. The terminal capability signaling that can be received by the base station may be a combination of at least one of the following: different channel coding schemes based on the bit length of the CSI, a multiplexing location determination method for the CSI within the PUSCH, an additional beta offset indication, multiple non-periodic CSI report slot offsets, and support for the CSI report information generation method. Step 1800 may be omitted.

[0568] In step 1805, the base station may transmit upper layer signaling to the terminal. At this time, the base station may set to the terminal at least one combination of each upper layer signaling related to different channel coding schemes according to the bit length of the CSI, a multiplexing location determination method for the CSI within the PUSCH, an additional beta offset instruction, a plurality of non-periodic CSI report slot offsets, and a method for generating CSI report information.

[0569] In step 1810, the base station may notify the terminal of a CSI report using at least one combination of upper layer signaling, MAC-CE signaling, and L1 signaling. Based on this notification, the terminal can verify the CSI report method that the base station has transmitted to the terminal.

[0570] At step 1815, the base station can receive CSI reports. These CSI reports may be received by a specific MMU or may be received commonly by multiple MMUs.

[0571] In step 1820, a specific MMU within the base station can decode the CSI received in step 1815. Subsequently, the MMU can transmit the decoded CSI to the DU.

[0572] In step 1825, the DU can perform scheduling for the terminal based on the CSI information received from the MMU and transmit this information to the MMU. At this time, the terminal may be scheduled in the SU-MIMO mode or the MU-MIMO mode at a specific time and frequency resource depending on the scheduling result.

[0573] In step 1830, the MMU can determine a downlink precoder to apply to the terminal by combining scheduling information received from the DU and additionally decoded CSI information from the MMU. At this time, the downlink precoder applied to the corresponding PDSCH received by the terminal may be based on the CSI reflected during scheduling for the corresponding PDSCH at the DU, or, if the MMU supports decoding for the CSI, it may be CSI information that was received and updated more recently than the CSI reflected during scheduling for the PDSCH.

[0574] In step 1835, the base station may transmit a DCI to the terminal that may (or includes) PDSCH scheduling information. The terminal may obtain information related to PDSCH scheduling from the base station based on the DCI. Such scheduling information may be related to a CSI reported by the terminal. Such scheduling information may be determined based on the CSI reported by the terminal.

[0575] In step 1840, the base station can transmit PDSCH to the terminal, and the downlink precoder applicable thereto can be determined in step 1830.

[0576] The above-described flowchart illustrates an exemplary method that may be implemented in accordance with the principles of the present disclosure, and various modifications may be made to the method illustrated in the flowchart in this specification. For example, although illustrated as a series of steps, the various steps in each figure may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.

[0577] In one embodiment of the present disclosure, a method for directly sharing information between MMUs without passing through a DU is described when receiving specific information from a specific MMU to another MMU. This embodiment may operate in combination with other embodiments.

[0578] A terminal can connect to a base station composed of one or more MMUs. A base station may be composed of one DU connected to one or more MMUs. The base station may receive specific information transmitted by the terminal at a specific MMU (e.g., the first MMU), and if the information needs to be transmitted to another MMU (e.g., the second MMU), the base station may transmit the information from the first MMU to the DU, and then transmit the information from the DU to the second MMU. In this case, the delay time for the information to be transmitted from the first MMU to the second MMU may become significantly longer due to passing through the DU, and the longer the delay time, the lower the validity of the information may be.

[0579] To resolve this, an interface between MMUs can be created to facilitate information exchange between MMUs by using a method to directly share information between the first MMU and the second MMU.

[0580] To facilitate the method of directly sharing information between the MMUs, the interface between the MMUs may be a wired connection. In this case, multiple MMUs may exist in different locations, and since a wired connection is required between each MMU, costs may be reduced if two MMUs are located close to each other, but if two MMUs are far apart, a significant cost may be incurred to connect the two MMUs by wire. Additionally, if three or more MMUs are connected to a single DU, the number of interfaces between MMUs may be equal to the number of cases where two are selected from the total MMUs. If a wired connection between MMUs is possible, when the first MMU transmits specific information to the second MMU, the information can be transmitted directly from the first MMU to the second MMU without using the conventional method of transmitting the specific information from the first MMU to the DU and then from the DU to the second MMU. In this case, the format of the information transmitted by the first MMU to the second MMU can reuse the format previously used for information exchange between the MMU and the DU, and the indices of the transmitting MMU and the receiving MMU are included within the format, so that the receiving MMU can determine which MMU transmitted the information when it receives the format. The transmitting MMU can transmit the same information to the DU while transmitting it to the receiving MMU. Additionally, the transmitting MMU can prevent the DU from transmitting additional information to the receiving MMU by transmitting an indicator to the DU that specific information has been transmitted to the receiving MMU. The receiving MMU can feed back a signal to the transmitting MMU that signifies that the information transmitted by the transmitting MMU has been properly received. In this case, the information may be transmitted only to the transmitting MMU, or it may be transmitted to both the transmitting MMU and the DU.

[0581] For a method of directly sharing information between the above MMUs, the interface between the MMUs may be a wireless connection. The first MMU and the second MMU may be wirelessly connected to each other, and wireless channels and signals between a terminal and a base station may be reused for transmitting and receiving information between the first MMU and the second MMU. At this time, the wireless channels and signals that can be reused may be a combination of at least one of the following items.

[0582] - For example, when a base station establishes a wireless connection between MMUs, it may use a downlink control channel (PDCCH) and a downlink data channel (PDSCH) that can be used for communication between the base station and the terminal to transmit and receive control information and data between MMUs. That is, when the first MMU intends to transmit data to the second MMU, the first MMU transmits a PDCCH to the second MMU, and the second MMU receives the PDCCH to receive scheduling information regarding at what time and frequency location the data intended by the first MMU can be received. In this case, when each MMU transmits control information or data to another MMU, it may reuse the transmission method used for the terminal, but when each MMU receives control information or data from another MMU, new receiving algorithms and hardware may be required. In particular, if a specific MMU receives a PDCCH transmitted from another MMU to determine the data scheduling information that the other MMU is to transmit to that MMU, a decoder for the PDCCH control information must be implemented, which may constitute additional overhead during MMU configuration. The aforementioned PDCCH may be downlink control information for a specific MMU to instruct a single other MMU on data transmission scheduling information, or it may be group-common downlink control information for a specific MMU to instruct a multiple other MMUs on data scheduling information. An MMU receiving the PDCCH and PDSCH can estimate the valid channel information between MMUs through the DMRS transmitted along with the PDCCH and PDSCH by the MMU that transmitted them, and receive the PDCCH and PDSCH information based on this.Alternatively, the base station may set reserved time and frequency resources similar to semi-persistent scheduling-based PDSCH for each MMU, and a specific MMU may transmit data to another MMU within those time and frequency resources. In this case, the specific time and frequency resources may only allow the first MMU to transmit SPS PDSCH to the second MMU, and the reverse transmission (the second MMU transmitting to the first MMU) may require the use of additional resources.

[0583] As another example, when establishing a wireless connection between MMUs, a base station may use the uplink control channel (PUCCH) and uplink data channel (PUSCH) available for communication between the base station and the terminal to transmit and receive control information and data between MMUs. That is, if the first MMU intends to transmit data to the second MMU, the first MMU transmits a PUCCH to the second MMU, and the second MMU receives the PUCCH to receive scheduling information regarding at which time and frequency location the data intended by the first MMU can be received. In this case, each MMU may reuse the method of receiving uplink data and control information from the terminal when receiving data and control information from another MMU, but new transmission algorithms and hardware may be required when each MMU transmits control information or data to another MMU. In particular, if a specific MMU needs to receive a PUCCH transmitted from another MMU, a decoder for the PUCCH control information must be implemented, which may constitute additional overhead during MMU configuration. An MMU receiving PUCCH and PUSCH can estimate valid channel information between MMUs through DMRS transmitted along with the PUCCH and PUSCH by the MMU that transmitted the PUCCH and PUSCH, and receive PUCCH and PUSCH information based on this. Alternatively, the PUCCH that an MMU can transmit may be based on a specific sequence, and based on this, the receiving MMU can estimate which MMU transmitted the PUCCH through a reception method using different sequences. In another way, the base station may set reserved time and frequency resources similar to configured grant-based PUSCH for each MMU, and a specific MMU can transmit data to another MMU within those time and frequency resources.At this time, the specific time and frequency resources may only enable the first MMU to transmit CG PUSCH to the second MMU, and transmission in the opposite direction (transmission from the second MMU to the first MMU) may require the use of additional resources.

[0584] As another example, to support wireless connectivity between multiple MMUs, CSI-RS transmission and reception resources between each MMU can be defined for the purpose of obtaining channel information between MMUs. When the first MMU transmits CSI-RS to a terminal, the second MMU can receive from the DU via upper layer signaling the time and frequency resources, sequence information, and frequency axis density information, etc., at which the CSI-RS resources are transmitted, and based on this information, the second MMU can receive the CSI-RS transmitted by the first MMU to obtain information about the wireless channel between the first MMU and the second MMU. Similarly, SRS transmitted by each MMU can be defined to support wireless connectivity between MMUs.

[0585] In order to perform data, control information, and reference signal transmission and reception operations between any MMUs described above, that is, to have the first MMU transmit and the second MMU receive at a specific time, the base station may set up multiple different TDD configurations corresponding to different MMUs within any serving cell. As an example, if the base station sets the first MMU to DDDSU and the second MMU to DDDSU, and when determining the transmission and reception direction for each symbol in the fourth slot (S) of the first MMU and the second MMU, the first MMU may be considered as "DDDDDDDDDDDDDD" and the second MMU as "DDDDDDDDDDUUUU". In this case, the first MMU can perform a downlink transmission operation by being set to D in the 11th to 14th symbols of the fourth slot (S) and can transmit information to the second MMU, and the second MMU can perform an uplink reception operation by being set to U in the 11th to 14th symbols of the corresponding fourth slot (S) and can receive the information from the first MMU.

[0586] Alternatively, the base station may set up multiple different SBFD (Sub-Band Full-Duplex) configurations corresponding to different MMUs within any serving cell in order to perform data, control information, and reference signal transmission and reception operations between any MMUs described above, that is, to have the first MMU transmit and the second MMU receive at a specific time. That is, the base station may set up multiple different UL subband locations corresponding to different MMUs and use them so that each MMU operates a different UL subband. For example, if the base station is configured with both the first MMU and the second MMU as DDDSU, and the first MMU is configured with the UL subband for the central 20 RBs of the downlink and uplink bandwidth portions, and the second MMU is configured with the UL subband for the upper 20 RBs of the downlink and uplink bandwidth portions, the first MMU can receive data, control information, and reference signals from the second MMU through the central 20 RBs, and the second MMU can receive data, control information, and reference signals from the first MMU through the upper 20 RBs.

[0587] In a specific serving cell configured to facilitate information exchange by configuring links between multiple MMUs as described above, the base station can define information that can be exchanged between multiple MMUs to enable one or more terminals to smoothly perform cooperative transmission and reception operations between multiple MMUs.

[0588] When connected to a DU, an MMU can transmit MMU capability information to the DU regarding whether the MMU can communicate directly with other MMUs. In this case, each MMU can individually transmit whether it is capable of one-to-one communication (unicast) or / and one-to-many communication (multi- / group-cast) with other MMUs. Additionally, when connected to a DU, an MMU can transmit to the DU the dimension size of the SVD operations that can be performed within the MMU. For example, any MMU can perform SVD operations on MIMO channels of size 64x64, which may be greater than or equal to the number of transmit and receive antennas of that MMU. For instance, an arbitrary MMU may have 32 transmit and receive antennas, but for SVD operations, it may support a 64x64 MIMO channel, which is twice the size. Another arbitrary MMU may not be able to perform SVD operations. In addition, when an MMU connects to a DU, it can transmit to the DU information regarding the channel encoding / decoding methods that can be performed within the MMU and whether such methods are supported. For example, since an arbitrary MMU is capable of encoding / decoding for polar coding, it can decode CSI reports reported by terminals directly without passing them to the DU, allowing them to be utilized immediately within the MMU; or, since it is capable of PDCCH encoding / decoding, it can transmit and receive data scheduling information via PUCCH and PDCCH when directly connecting with other MMUs via a wireless channel. As another example, since an arbitrary MMU is capable of encoding / decoding for LDPC coding, it can perform PDSCH encoding / decoding, allowing it to transmit and receive data information via PDSCH and PUSCH when directly connecting with other MMUs via a wireless channel. Through this, it can be utilized to create containers containing relevant information when exchanging information between MMUs.

[0589] The DU may assign a specific index between MMUs that have received MMU capability information regarding whether direct communication with the other MMUs described above is possible (e.g., may be referred to as an MMU ID). The DU may determine a transmission method per MMU to enable direct communication between MMUs to which the specific index has been assigned. For example, the DU may assign a high priority during transmission and reception to MMUs capable of the SVD operation or / and polar / LDPC code encoding / decoding operation, or instruct the terminal to report to these MMUs first when performing a CSI report.

[0590] For example, if two MMUs are connected to one DU in a specific serving cell, and among the two MMUs, the first MMU reports to the DU that it is capable of SVD, Polar / LDPC encoding / decoding, and direct communication between MMUs, and the second MMU reports to the DU that it is capable of Polar / LDPC encoding / decoding and direct communication between MMUs, the base station can schedule terminals connected to the serving cell to perform uplink transmission to the first MMU. Accordingly, the base station can determine an appropriate transmission beam direction and / or uplink transmission power to have the terminal report CSI to the first MMU. Subsequently, the terminal can report CSI to the first MMU in accordance with the instructions of the base station. After receiving the CSI, the first MMU may directly decode the CSI and use it immediately in accordance with the instructions of the DU, or send the CSI to the DU without decoding it. If the CSI received by the first MMU is a CJT CSI, that is, a CSI available for use by multiple MMUs, the first MMU can decode the CSI, extract the portion available for use by the second MMU, and transmit scheduling information for data to be transmitted from the first MMU to the second MMU via PDSCH. Subsequently, the first MMU can report to the second MMU by including CSI information corresponding to the second MMU among the entire CJT CSI within the PDSCH. The second MMU can decode this and schedule it for downlink data transmission to the terminal.

[0591] At this time, information that can be transmitted from a specific MMU to another MMU through direct communication between MMUs may consider at least one combination of the following items.

[0592] - Among the CSI information transmitted by the terminal to a specific MMU, CSI information generated based on multiple MMUs (e.g., NCJT CSI, CJT CSI, or CJT calibration CSI)

[0593] - Estimated channel between the terminal and a specific MMU based on the SRS transmitted by the terminal

[0594] - Channel correlation information between the terminal and the specific MMU based on the SRS transmitted by the terminal

[0595] - AIML (Artificial Intelligence Machine Learning) model exchange between MMUs

[0596] FIG. 19a is a diagram illustrating an example of a terminal and a base station exchanging information between MMUs through a direct communication link between MMUs according to an embodiment of the present disclosure.

[0597] For example, a base station may be composed of one DU (1900) and two MMUs (e.g., a first MMU (1905) (MMU#1) and a second MMU (1910) (MMU#2)). One DU and one MMU may be connected to each other via a fronthaul (FH) (1915).

[0598] The terminal (1920) can transmit to the first MMU (1925) to transmit a CSI report to the base station. The terminal (1920) may be notified to perform a CSI report from the base station to the first MMU through a combination of at least one of upper layer signaling, MAC-CE signaling, and L1 signaling. This may be because the first MMU has higher CSI and SRS estimation capabilities than the second MMU (e.g., the first MMU reported to the DU that it has capabilities in SVD and Polar / LDPC encoding / decoding and direct communication between MMUs, and the second MMU reported to the DU that it has capabilities in Polar / LDPC encoding / decoding and direct communication between MMUs). The first MMU (1905) can decode the CSI received from the terminal and share it with the second MMU (1910) via a direct communication link between MMUs. The sharing of CSI information from the first MMU to the second MMU can be similarly applied to the sharing of SRS information. At the same time, the first MMU can share the corresponding CSI information with the DU, and the DU can process the CSI information of not only the terminal but also other terminals to ultimately determine the scheduling information for the terminal. The specific process for this can be explained as follows.

[0599] FIG. 19b is a diagram illustrating an example of the process of exchanging channel state information between a terminal and a base station during information exchange between MMUs via a direct communication link between MMUs according to an embodiment of the present disclosure. FIG. 19b illustrates an exemplary method that can be implemented according to the principles of the present disclosure, and various modifications may be made to the method illustrated in FIG. 19b. For example, although illustrated as a series of steps, the various steps in each figure may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.

[0600] At step 1950, the terminal may transmit a CSI report to the first MMU. The CSI report may be transmitted within a PUCCH or PUSCH.

[0601] In step 1955, the first MMU decodes the CSI report information of the terminal, and if the CSI report is a CSI based on multiple MMUs (e.g., NCJT CSI or CJT CSI), the first MMU can prepare to transmit the part of the CSI corresponding to the second MMU through a direct communication link between MMUs.

[0602] In step 1960, as described above, if the CSI reported by the terminal is a CSI based on multiple MMUs (e.g., NCJT CSI or CJT CSI), the first MMU may transmit the portion of the CSI corresponding to the second MMU through a direct communication link between MMUs. In this case, the transmission method may be based on PDCCH, PDSCH, PUCCH, or / and PUSCH as described above.

[0603] In step 1961, the first MMU can transmit decoded CSI information or information about the PUCCH or PUSCH received from the terminal to the DU via the fronthall. This information can be transmitted via the user plane, which is an interface within the fronthall, whereby the real part or imaginary part data of the PUCCH or PUSCH can be transmitted by quantizing into a specific number of bits, respectively. The number of bits that can be considered can be 9, 11, or 16 bits for the real part and the imaginary part, respectively. The real part and / or imaginary part of the PUCCH and / or PUSCH can be transmitted by quantizing into 9 bits, 11 bits, or 16 bits.

[0604] In step 1962, a DU that receives information about a PUCCH or PUSCH containing the terminal's CSI can decode the CSI contained within the PUCCH or PUSCH to identify / identify the CSI information reported by the terminal. Additionally, the DU can determine the scheduling for the terminal based on the CSI information. At this time, the scheduling for the terminal may be in the form of SU-MIMO (Single-User Multiple-Input Multiple-Output), which allocates only the terminal to a specific time and frequency resource, or in the form of MU-MIMO (Multi-User Multiple-Input Multiple-Output), which allocates the terminal and other terminals together to the same time and frequency resource, and may be scheduled by a single MMU or by multiple MMUs.

[0605] In steps 1965 and 1968, the terminal may periodically report a CSI, and the CSI may be transmitted to the first MMU.

[0606] In steps 1966 and 1969, the first MMU can decode the CSI reported by the terminal as described above.

[0607] In steps 1967 and 1970, if the CSI reported by the terminal is a CSI based on multiple MMUs (e.g., NCJT CSI or CJT CSI), the first MMU may transmit the portion of the CSI corresponding to the second MMU via a direct communication link between MMUs. In this case, the transmission method may be based on PDCCH, PDSCH, PUCCH, or / and PUSCH as described above. Through this, the first MMU and the second MMU can update to the latest CSI value at every cycle of CSI reporting received from the terminal, which may be faster than the time required to transmit the previously decoded CSI to the DU and for the DU to calculate final scheduling information by considering all CSIs of other terminals. That is, the CSI reported by the terminal and stored by the first MMU and the second MMU may be more up-to-date than the CSI used by the DU for scheduling.

[0608] In step 1975, the DU may transmit the scheduling information to the first MMU and the second MMU. The information included therein may include time and frequency resource allocation information, information related to the precoder to be used by the terminal, MCS level, etc. The information related to the precoder to be used by the terminal may include information on which PMI to use and what the rank value is when using an already defined PMI, and how to process the channel estimated through the SRS when using an SRS-based precoder.

[0609] In step 1976, the first MMU can generate and apply a downlink precoder. The first MMU may store a complete set of PMIs in preparation for receiving information from the DU regarding the application of a PMI-based downlink precoder. The complete set of PMIs may be pre-configured in the first MMU. Based on the complete set of PMIs, operations related to the application of a PMI-based downlink precoder may be performed. Thus, if the scheduling information received from the DU includes information that a PMI is to be used as a downlink precoder to be applied to a specific terminal, the first MMU may identify the specific PMI instructed by the DU within the complete set of PMIs stored in the first MMU and select it as the downlink precoder to be applied to the terminal. The DU may instruct the first MMU to use a specific PMI, may instruct it to generate a specific precoder through a linear combination of one or more PMIs, or may instruct it to use each element of the specific PMI with some modifications. Additionally, the DU may transmit instructions to the first MMU to update the entire set of PMIs, and after such updates, the DU and the first MMU may transmit and receive instructions for the use of specific PMIs under the assumption that the entire set of PMIs is different from that before the updates. The entire set of PMIs may change before and after the updates. After the updates, instructions for the use of specific PMIs within the entire set of updated PMIs may be transmitted and received.

[0610] In step 1978, the first MMU may transmit downlink precoder-related information to the second MMU. In this step, if the DU instructs the first MMU to generate a downlink precoder by performing processing that only the first MMU can perform (e.g., performing SVD or ZF (Zero-Forcing) operations of a dimension size corresponding to the number of all antennas installed in the first MMU and the second MMU), the first MMU may generate the downlink precoder and transmit the portion thereof to the second MMU.

[0611] In step 1980, the first MMU and the second MMU may apply the downlink precode to transmit PDSCH to the terminal. At this time, as described above, the terminal may be scheduled in a SU-MIMO or MU-MIMO form and may be transmitted from a single MMU or multiple MMUs in the first MMU or / and the second MMU.

[0612] In order to utilize the direct communication link between the first MMU and the second MMU, the base station may use different TDD configurations for each MMU as described above, or use different SBFD configurations for each MMU. At this time, the first MMU may measure the reference signal transmitted by the second MMU to determine channel state information between the first MMU and the second MMU and determine the interference strength.

[0613] Similarly, if a terminal receives an SBFD configuration from a base station—that is, if the terminal receives a UL subband—frequency resources in a slot operating as a downlink can be divided so that a portion is configured as a resource capable of downlink reception, i.e., a DL subband, and the remaining portion is defined as a resource capable of uplink transmission, i.e., a UL subband. In this case, if the terminal receives a downlink signal in the DL subband in the corresponding slot, and another terminal with the same UL subband configuration in the same slot performs an uplink transmission in that UL subband, the terminal receiving the downlink signal in the DL subband may be subject to strong interference from the uplink transmission of the other terminal in the adjacent UL subband, which may result in a degradation of downlink reception performance. In particular, if the terminal transmitting the uplink signal in the UL subband and the terminal receiving the downlink signal in the DL subband are located close to each other, the performance degradation of the downlink receiving terminal may become severe.

[0614] To control interference (CLI: Cross-Link Interference) between different links (i.e., between downlink and uplink) between such terminals, the terminal may receive the following upper-layer signaling settings from the base station.

[0615] - When the terminal reports CLI measurements to the base station, it may refer to a specific CSI-ReportConfig, and the CSI-ReportConfig may be set to cli-RSSI, cli-SRS-RSRP, L1-SRS-RSRP, or L1-CLI-RSSI as the reportQuantity value, which is an upper layer signaling.

[0616] - The terminal can receive a list of CLI measurement reference signals for L1-SRS-RSRP measurement or L1-CLI-RSSI measurement within CSI-ResourceConfig, which is an upper layer signaling from the base station.

[0617] - The terminal can be configured with SRS-ResourceListConfigCLI-r19, an upper-layer signaling, as a set of CLI measurement reference signals for L1-SRS-RSRP measurement. Within SRS-ResourceListConfigCLI-r19, up to maxNrofCLI-SRS-Resources-r16 (=32) or up to maxNrofCLI-SRS-Resources-r19 (=X1) SRS-ResourceConfigCLI-r19s can be configured, and within each SRS-ResourceConfigCLI-r19, one or more SRS resources, the subcarrier spacing of the SRS resources, the serving cell index, and the bandwidth portion index can be configured. The terminal can be configured with one of periodic, semi-persistent, or aperiodic as the value of resourceType, an upper-layer signaling within the above SRS resources, and through this parameter, can determine whether the corresponding CLI measurement reference signal is a periodic, semi-persistent, or aperiodic SRS resource. In this case, the above X1 may be a natural number greater than or equal to 1, for example, 32, 48, 64, 96, or 128. The names of the upper layer signaling described above are merely examples and may have different names for the same purpose.

[0618] - The terminal can receive RSSI-ResourceListConfigCLI-r19, which is an upper layer signaling, as a set of CLI measurement reference signals for L1-CLI-RSSI measurement. Within RSSI-ResourceListConfigCLI-r19, up to maxNrofCLI-RSSI-Resources-r16 (=64) or up to maxNrofCLI-RSSI-Resources-r19 (=X2) RSSI-ResourceConfigCLI-r19s can be set, and within each RSSI-ResourceConfigCLI-r19, one or more RSSI-ResourceId-r19s, RSSI-Resource subcarrier spacing, start RB position, number of RBs, start OFDM symbol position, number of OFDM symbols, RSSI-Resource period and offset, serving cell index, resourceType, etc. can be set. In this case, the period and offset of the RSSI-Resource can be set only when the resourceType is periodic or semi-persistent, and if it is aperiodic, the period and offset of the RSSI-Resource may not be set, or even if they are set, they may be ignored. In this case, X2 may be a natural number greater than or equal to 1, for example, 32, 48, 64, 96, or 128. The names of the upper layer signaling described above are merely examples and may have different names for the same purpose.

[0619] - When the terminal reports the above CLI measurements to the base station, the terminal may receive a non-periodic CSI reporting method set by default from the base station. Additionally, the terminal may receive a periodic or semi-continuous CSI reporting method for CLI measurement reporting from the base station only when the terminal capabilities are reported.

[0620] - If the terminal receives a non-periodic CLI measurement reporting method from the base station, the terminal may receive one or more CSI-AperiodicTriggerStates within the upper layer signaling CSI-AperiodicTriggerStateList, and each CSI-AperiodicTriggerState may correspond to each code point of the CSI request field in DCI format 0_1, 0_2, or 0_3. Additionally, one CSI-AperiodicTriggerState may include one or more CSI-AssociatedReportConfigInfos, and each CSI-AssociatedReportConfigInfo may include one CSI-ReportConfig.

[0621] As a method, the terminal may always receive resourcesForChannelMeasurement within the upper-layer signaling CSI-ReportConfig regarding information on the CLI measurement reference signal to be measured for reporting CLI measurements, and CSI-ResourceConfigId is set as the value of resourcesForChannelMeasurement. By referencing the information within CSI-ResourceConfig corresponding to the CSI-ResourceConfigId, the terminal can obtain information on the CLI measurement reference signal. In this case, the terminal may select one of the CSI-RS, SSB, CSI-IM, SRS, or RSSI resources by receiving a specific upper-layer signaling (e.g., RS-ResourceSetList-r19 or csi-RS-ResourceSetList-r19) within CSI-ResourceConfig. In this case, if RS-ResourceSetList-r19 is set, the terminal may ignore csi-RS-ResourceSetList, which is always set within CSI-ResourceConfig, even if the terminal receives it. In this case, RS-ResourceSetList-r19 or csi-RS-ResourceSetList2-r19 are merely examples as described above, and the names of the specific parameters may differ. As an example, the structure of the upper-layer signaling of RS-ResourceSetList-r19 may be as follows.

[0622] As described above, X1 and X2 below may respectively represent the maximum number of SRS-ResourceListConfigCLI-r19s that can be set to upper layer signaling from the base station and the maximum number of RSSI-ResourceListConfigCLI-r19s that can be set.

[0623] csi-RS-ResourceSetList2-r19 CHOICE {

[0624] nzp-CSI-RS-SSB2 SEQUENCE {

[0625] nzp-CSI-RS-ResourceSetList2 SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig)) OF NZP-CSI-RS-ResourceSetId OPTIONAL, -- Need R

[0626] csi-SSB-ResourceSetList2 SEQUENCE (SIZE (1..maxNrofCSI-SSB-ResourceSetsPerConfig)) OF CSI-SSB-ResourceSetId OPTIONAL -- Need R

[0627] },

[0628] csi-IM-ResourceSetList2 SEQUENCE (SIZE (1..maxNrofCSI-IM-ResourceSetsPerConfig)) OF CSI-IM-ResourceSetId

[0629] srs-ResourceListConfigCLI-r19 SEQUENCE (SIZE (1..X1)) OF SRS-ResourceConfigCLI-r19

[0630] rssi-ResourceListConfigCLI-r19 SEQUENCE (SIZE (1..X2)) OF RSSI-ResourceListConfigCLI-r19

[0631] },

[0632] - Alternatively, the terminal may always receive resourcesForChannelMeasurement within the upper-layer signaling CSI-ReportConfig regarding information on the CLI measurement reference signal to be measured for CLI measurement reporting, and CSI-ResourceConfigId is set as the value of resourcesForChannelMeasurement. By referencing the information within CSI-ResourceConfig corresponding to the CSI-ResourceConfigId, the terminal can obtain information on the CLI measurement reference signal. In this case, the terminal may select either an SRS resource for SRS-RSRP measurement or an RSSI resource for CLI-RSSI measurement by receiving a specific upper-layer signaling (e.g., CLI-ResourceSetList-r19) within CSI-ResourceConfig. In this case, if CLI-ResourceSetList-r19 is set, the terminal may ignore csi-RS-ResourceSetList, which is always set within CSI-ResourceConfig, even if the terminal receives it. In this case, CLI-ResourceSetList-r19 is merely an example as described above, and the names of specific parameters may vary. As an example, the structure of the upper-layer signaling of CLI-ResourceSetList-r19 may be as follows.

[0633] - The following X1 and X2 may respectively represent the maximum number of SRS-ResourceListConfigCLI-r19s that can be set to upper layer signaling from the base station and the maximum number of RSSI-ResourceListConfigCLI-r19s that can be set.

[0634] csi-RS-ResourceSetList2-r19 CHOICE {

[0635] srs-ResourceListConfigCLI-r19 SEQUENCE (SIZE (1..X1)) OF SRS-ResourceConfigCLI-r19

[0636] rssi-ResourceListConfigCLI-r19 SEQUENCE (SIZE (1..X2)) OF RSSI-ResourceListConfigCLI-r19

[0637] }, OPTIONAL -- Need R

[0638] - Alternatively, the terminal may receive resourcesForCLIMeasurement within the upper-layer signaling CSI-ReportConfig regarding information on the CLI measurement reference signal to be measured for reporting CLI measurements, and CSI-ResourceConfigId is set as the value of resourcesForCLIMeasurement. By referencing the information within CSI-ResourceConfig corresponding to the CSI-ResourceConfigId, the terminal can obtain information on the CLI measurement reference signal. In this case, the terminal may select either an SRS resource for SRS-RSRP measurement or an RSSI resource for CLI-RSSI measurement by receiving a specific upper-layer signaling (e.g., CLI-ResourceSetList-r19) within CSI-ResourceConfig. If CLI-ResourceSetList-r19 is set, the terminal may ignore csi-RS-ResourceSetList, which is always set within CSI-ResourceConfig, even if the terminal receives it. In this case, CLI-ResourceSetList-r19 is merely an example as described above, and the names of specific parameters may vary. As an example, the structure of the upper-layer signaling of CLI-ResourceSetList-r19 may be as follows.

[0639] - The following X1 and X2 may respectively represent the maximum number of SRS-ResourceListConfigCLI-r19s that can be set to upper layer signaling from the base station and the maximum number of RSSI-ResourceListConfigCLI-r19s that can be set.

[0640] csi-RS-ResourceSetList2-r19 CHOICE {

[0641] srs-ResourceListConfigCLI-r19 SEQUENCE (SIZE (1..X1)) OF SRS-ResourceConfigCLI-r19

[0642] rssi-ResourceListConfigCLI-r19 SEQUENCE (SIZE (1..X2)) OF RSSI-ResourceListConfigCLI-r19

[0643] }, OPTIONAL -- Need R

[0644] - If the set of CLI measurement signals associated with CSI-ReportConfig included in the one CSI-AssociatedReportConfigInfo received by the terminal as upper layer signaling is a periodic or semi-persistent measurement signal (i.e., resourceType is set to periodic or semi-persistent), the terminal can expect the set of CLI measurement signals to be set in CSI-ResourceConfig.

[0645] If the terminal receives the CLI measurement reference signal set from the base station in FR1 or FR2 as a periodic measurement reference signal, the terminal may receive a TCI state for each periodic CLI measurement reference signal resource within the periodic CLI measurement reference signal set, and each TCI state may include a QCL-TypeD source RS. The terminal may receive a TCI state for each periodic CLI measurement reference signal resource within the periodic CLI measurement reference signal set, or may not receive a TCI state for all periodic CLI measurement reference signal resources. That is, the terminal may not expect to receive a TCI state for only some periodic CLI measurement reference signal resources within the periodic CLI measurement reference signal set.

[0646] If the terminal has not received a TCI state for each periodic CLI measurement reference signal resource within the periodic CLI measurement reference signal set, the terminal may consider different methods for receiving the corresponding periodic CLI measurement reference signal resource in a situation where TCI state information and QCL-TypeD information for that specific periodic CLI measurement reference signal resource are unavailable, depending on whether integrated TCI state-based operation is configured.

[0647] If the terminal is configured to perform an integrated TCI state-based operation within a specific serving cell by receiving upper layer signaling (i.e., if the terminal is configured with the upper layer signaling unifiedTCI-StateType from the base station), the terminal may receive a periodic CLI measurement reference signal resource in which QCL-TypeD is not configured or TCI state is not configured, based on the TCI state indicated by DCI format 1_1 or 1_2.

[0648] Alternatively, if the terminal is not configured with upper-layer signaling to perform unified TCI state-based operations within a specific serving cell (i.e., if the terminal is not configured with the upper-layer signaling unifiedTCI-StateType from the base station), the terminal can measure the L1 CLI-RSSI or L1-CLI-SRS-RSRP by receiving the periodic CLI measurement reference signal resource based on the same assumptions as in L3-based CLI measurement.

[0649] If the terminal receives the set of CLI measurement resources from the base station in FR1 or FR2 as a semi-persistent measurement resource set, the terminal may receive a Semi-Persistent CLI measurement resource set activation / deactivation MAC-CE from the base station and be notified of an activation or deactivation command for a set of CLI measurement resources containing one or more semi-persistent measurement resource resources. Through the MAC-CE, the terminal may receive a command to activate a TCI state for each semi-persistent CLI measurement resource within the set of semi-persistent CLI measurement resources, and each TCI state may include a QCL-TypeD source RS. In this case, the TCI state activation command for each semi-persistent CLI measurement resource may be made through an individual field within the MAC-CE that indicates the TCI state activation command for each semi-persistent CLI measurement resource. The terminal may receive a command to activate a TCI state for each semi-persistent CLI measurement resource within the set of semi-persistent CLI measurement resources, or may not receive a command to activate a TCI state for all semi-persistent CLI measurement resources. In other words, the terminal may not expect to receive a command to enable the TCI state only for some of the semi-persistent CLI reference signal resources within the semi-persistent CLI reference signal set.

[0650] - If one or more sets of non-periodic CLI measurement signals associated with CSI-ReportConfig included in one CSI-AssociatedReportConfigInfo configured by the terminal is configured as an upper layer signaling, the terminal may be selected from one of the said sets of non-periodic CLI measurement signals through a specific upper layer signaling, and said specific upper layer signaling may be, for example, resourceForChannelCLI-r19, but since this is merely an example, the name of the specific parameter may differ. In this case, the terminal may ignore this value even if it is configured with resourceForChannel, which is an upper layer signaling that is always (mandatory) configured for selecting one of the multiple non-periodic CSI-RS resource sets that can be configured within CSI-AssociatedReportConfigInfo.

[0651] - In addition, the specific upper layer signaling that the terminal can be configured to receive from the base station to select one of the above-mentioned sets of one or more non-periodic CLI measurement reference signals (e.g., named resourceForChannelCLI-r19) may be used only for the purpose of selecting one of the above-mentioned sets of one or more non-periodic CLI measurement reference signals and may not include the purpose of resourceForChannel, which is the upper layer signaling always configured above (for the purpose of selecting one of a plurality of non-periodic CSI-RS resource sets). In such cases, the terminal may assume that a specific upper layer signaling is set as a condition (which can be considered as a condition corresponding to "CLIreport" in the signaling structure below), that the reportQuantity of the CSI-ReportConfig connected within the CSI-AssociatedReportConfigInfo where the specific upper layer signaling is set is cli-RSSI, cli-SRS-RSRP, L1-SRS-RSRP, or L1-CLI-RSSI, and / or assume that one or more sets of non-periodic CLI measurement signals are set within the CSI-ReportConfig connected within the CSI-AssociatedReportConfigInfo where the specific upper layer signaling is set, and / or assume that the upper layer signaling resourcesForChannel2-r17 is not set (i.e., if resourcesForChannel2-r17 is set, resourceForChannelCLI-r19 may not be set), and / or assume that it is an upper layer signaling that can be optionally set for the Need R condition. If the terminal is configured with the above resourceForChannelCLI-r19, the terminal may ignore the higher-layer signaling resourceForChannel even if it is always configured.In this case, resourceForChannelCLI-r19 is merely an example as described above, and the names of specific parameters may differ. As an example, the structure of the corresponding specific upper-layer signaling may be as follows.

[0652] - The following X1 and X2 may respectively represent the maximum number of SRS-ResourceListConfigCLI-r19s that can be set to upper layer signaling from the base station and the maximum number of RSSI-ResourceListConfigCLI-r19s that can be set.

[0653] - Among the upper layer signalings below, qcl-info-CLI1-r19 and qcl-info-CLI2-r19 are setting conditions from the base station (which can be considered as conditions corresponding to "Aperiodic2" in the signaling structure below). If the connected resourceSetSRS-r19 or resourceSetRSSI-r19 is a non-periodic reference signal (i.e., when aperiodic is set as resourceType) and the upper layer signaling unifiedTCI-StateType is not set, the terminal can expect qcl-info-CLI1-r19 or qcl-infoCLI2-r19 to always be set, and otherwise, it can expect not to be set. As another setting condition (which can be considered as a condition corresponding to "Aperiodic2" in the signaling structure below), the terminal can expect that if the connected resourceSetSRS-r19 or resourceSetRSSI-r19 is a non-periodic reference signal (i.e., when aperiodic is set as resourceType) and the upper layer signaling unifiedTCI-StateType is set, qcl-info-CLI1-r19 or qcl-infoCLI2-r19 is optionally set, and otherwise, it can expect that it is not set.

[0654] resourceForChannelCLI-r19 CHOICE {

[0655] srs-rsrp-r19 SEQUENCE {

[0656] resourceSetSRS-r19 INTEGER (1,...,X1),

[0657] qcl-info-CLI1-r19 SEQUENCE (SIZE(1..X1)) OF TCI-StateId OPTIONAL -- Cond Aperiodic2

[0658] },

[0659] cli-rssi-r19 SEQUENCE {

[0660] resourceSetRSSI-r19 INTEGER (1,...,X2),

[0661] qcl-info-CLI2-r19 SEQUENCE (SIZE(1..X2)) OF TCI-StateId OPTIONAL -- Cond Aperiodic2

[0662] }

[0663] } OPTIONAL -- Cond CLIreport

[0664] In addition, the specific upper layer signaling that the terminal can be configured to receive from the base station to select one of the above-mentioned sets of one or more non-periodic CLI measurement reference signals may also include the purpose of resourceForChannel, which is the above-mentioned always-configured upper layer signaling (for the purpose of selecting one of a plurality of non-periodic CSI-RS resource sets). If the specific upper layer signaling includes the purpose of resourceForChannel, the terminal may select one of the CSI-RS resource set, SSB resource set, or SRS resource set through the specific upper layer signaling (e.g., resourceForChannel3-r19). If the terminal receives resourceForChannel3-r19 from the base station, the terminal may ignore the always-configured resourcesForChannel. Additionally, if srs-rsrp-r19 or cli-rssi-r19 is configured via resourceForChannel3-r19, the terminal can expect that resourcesForChannel2-r17 is not configured. If resourcesForChannel2-r17 is configured, the terminal can expect that the aforementioned resourcesForChannel3-r19 does not exist. If resourcesForChannel2-r17 is not configured, the aforementioned resourcesForChannel3-r19 may be configured optionally. In this case, resourceForChannel3-r19 is merely an example as described above, and the specific parameter names may differ. As an example, the structure of the corresponding specific upper layer signaling may be as follows.

[0665] - The following X1 and X2 may respectively represent the maximum number of SRS-ResourceListConfigCLI-r19s that can be set to upper layer signaling from the base station and the maximum number of RSSI-ResourceListConfigCLI-r19s that can be set.

[0666] - Among the upper layer signalings below, qcl-info-CLI1-r19 and qcl-info-CLI2-r19 are setting conditions from the base station (which can be considered as conditions corresponding to "Aperiodic2" in the signaling structure below). If the connected resourceSetSRS-r19 or resourceSetRSSI-r19 is a non-periodic reference signal (i.e., when aperiodic is set as resourceType) and the upper layer signaling unifiedTCI-StateType is not set, the terminal can expect qcl-info-CLI1-r19 or qcl-infoCLI2-r19 to always be set, and otherwise, it can expect not to be set. As another setting condition (which can be considered as a condition corresponding to "Aperiodic2" in the signaling structure below), the terminal can expect that if the connected resourceSetSRS-r19 or resourceSetRSSI-r19 is a non-periodic reference signal (i.e., when aperiodic is set as resourceType) and the upper layer signaling unifiedTCI-StateType is set, qcl-info-CLI1-r19 or qcl-infoCLI2-r19 is optionally set, and otherwise, it can expect that it is not set.

[0667] resourceForChannel3-r19 CHOICE {

[0668] nzp-CSI-RS3-r19 SEQUENCE {

[0669] resourceSet3-r19 INTEGER (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig),

[0670] qcl-info3-r19 SEQUENCE (SIZE(1..maxNrofAP-CSI-RS-ResourcesPerSet)) OF TCI-StateId OPTIONAL -- Cond Aperiodic

[0671] },

[0672] csi-SSB-ResourceSet3-r19 INTEGER (1..maxNrofCSI-SSB-ResourceSetsPerConfig)

[0673] srs-rsrp-r19 SEQUENCE {

[0674] resourceSetSRS-r19 INTEGER (1,...,X1),

[0675] qcl-info-CLI1-r19 SEQUENCE (SIZE(1..X1)) OF TCI-StateId OPTIONAL -- Cond Aperiodic2

[0676] },

[0677] cli-rssi-r19 SEQUENCE {

[0678] resourceSetRSSI-r19 INTEGER (1,...,X2),

[0679] qcl-info-CLI2-r19 SEQUENCE (SIZE(1..X2)) OF TCI-StateId OPTIONAL -- Cond Aperiodic2

[0680] }

[0681] } OPTIONAL - OPTIONAL - - Need R

[0682] - If a terminal is configured with one or more non-periodic CLI measurement signal sets associated with CSI-ReportConfig included in one CSI-AssociatedReportConfigInfo configured as an upper layer signaling, the terminal may ignore resourceForChannel, which is an upper layer signaling that is always configured, even if it is configured.

[0683] - The terminal may receive the upper layer signaling resourceForChannelCJTC-r19 and may receive resourceSet2CJTC-r19, resourceSet3CJTC-r19, or / and resourceSet2CJTC-r19 within the said upper layer signaling. resourceForChannelCJTC-r19 may be used to receive up to four CSI-RS resource sets to perform aperiodic CSI reporting to the base station by measuring time or / and frequency offsets between different TRPs at the terminal. In this case, up to three additional CSI-RS resource sets that may be set within resourceForChannelCJTC-r19 may have the upper layer signaling trs-info set to true. The terminal may receive the first CSI-RS resource set for measuring time or / and frequency offsets between different TRPs from resourceForChannel or the said resourceForChannel3-r19. In addition, the terminal can expect that all CSI-RS resources configured through the resourceForChannelCJTC-r19 have the same frequency resources as all CSI-RS resources within the first CSI-RS resource set configured through the resourceForChannel or the resourceForChannel3-r19. In addition, the terminal can expect that all CSI-RS resources within the first CSI-RS resource set configured through the resourceForChannel or the resourceForChannel3-r19 and up to three CSI-RS resource sets configured through the resourceForChannelCJTC-r19 have different QCL information.In this case, resourceForChannelCJTC-r19, resourceSet2CJTC-r19, resourceSet3CJTC-r19, or / and resourceSet2CJTC-r19 are merely examples as described above, and the names of the specific parameters may differ. As an example, the structure of the corresponding specific upper-layer signaling may be as follows.

[0684] - As a condition for the existence of the following resourceForChannelCJTC-r19 (for example, it may be a condition of the following "CJTC-DF"), if the upper layer signaling resourceForChannel2 is configured, the above resourceForChannelCJTC-r19 may not be configured. If resourceForChannel2 is not configured, the above resourceForChannelCJTC-r19 may be configured optionally.

[0685] - As another condition for the existence of the resourceForChannelCJTC-r19 below (for example, it may be the condition of the "CJTC-DF" below), the resourceForChannelCJTC-r19 may be set only when the reportQuantity in the CSI-ReportConfig that can be set in CSI-AssociatedReportConfigInfo is 'cjtc-Dd', 'cjtc-F', or 'cjtc-Dd-F', and may not be set otherwise.

[0686] resourceForChannelCJTC-r19 SEQUENCE {

[0687] resourceSet2CJTC-r19 INTEGER (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig);

[0688] resourceSet3CJTC-r19 INTEGER (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig), OPTIONAL -- Need R

[0689] resourceSet4CJTC-r19 INTEGER (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig), OPTIONAL -- Need R

[0690] } OPTIONAL - Cond CJTC-DF

[0691] FIG. 20 is a drawing illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure.

[0692] Referring to FIG. 20, the terminal may include a transceiver (referring to a terminal receiver (2000) and a terminal transmitter (2010)), a memory (not shown), and a terminal processing unit (2005, or a terminal control unit or processor). Depending on the communication method of the terminal described above, the transceiver (2000, 2010), memory, and terminal processing unit (2005) of the terminal may operate. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more components or fewer components than the components described above. Furthermore, the transceiver, memory, and processor may be implemented in the form of a single chip.

[0693] The transceiver can transmit and receive signals with a base station. Here, the signal may include control information and data. To this end, the transceiver may be composed of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. However, this is merely one embodiment of the transceiver, and the components of the transceiver are not limited to an RF transmitter and an RF receiver.

[0694] In addition, the transceiver can receive a signal through a wireless channel and output it to a processor, and transmit the signal output from the processor through a wireless channel.

[0695] Memory can store programs and data necessary for the operation of the terminal. Additionally, memory can store control information or data included in signals transmitted and received by the terminal. Memory may be composed of storage media or combinations of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD. Additionally, there may be multiple memories.

[0696] Additionally, the processor can control a series of processes to enable the terminal to operate according to the aforementioned embodiment. For example, the processor can receive a DCI composed of two layers and control the components of the terminal to receive multiple PDSCHs simultaneously. There may be multiple processors, and the processors can perform the operation of controlling the components of the terminal by executing a program stored in memory.

[0697] FIG. 21 is a drawing illustrating the structure of a base station in a wireless communication system according to one embodiment of the present disclosure.

[0698] Referring to FIG. 21, the base station may include a transceiver unit (referring to a base station receiver unit (2100) and a base station transmitter unit (2110), a memory (not shown), and a base station processing unit (2105, or a base station control unit or processor). Depending on the communication method of the base station described above, the transceiver unit (2100, 2110), the memory, and the base station processing unit (2105) of the base station may operate. However, the components of the base station are not limited to the examples described above. For example, the base station may include more components or fewer components than the components described above. In addition, the transceiver unit, the memory, and the processor may be implemented in the form of a single chip.

[0699] The transceiver can transmit and receive signals with a terminal. Here, the signal may include control information and data. To this end, the transceiver may be composed of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts its frequency. However, this is merely one embodiment of the transceiver, and the components of the transceiver are not limited to an RF transmitter and an RF receiver.

[0700] In addition, the transceiver receives a signal through a wireless channel and outputs it to a processor, and can transmit the signal output from the processor through a wireless channel.

[0701] Memory can store programs and data necessary for the operation of the base station. Additionally, memory can store control information or data included in signals transmitted and received by the base station. Memory can be composed of storage media or combinations of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD. Additionally, there may be multiple memories.

[0702] A processor can control a series of processes to enable a base station to operate according to the embodiments of the present disclosure described above. For example, the processor can control each component of the base station to configure two layers of DCIs containing allocation information for a plurality of PDSCHs and to transmit them. There may be multiple processors, and the processors can perform control operations on the components of the base station by executing a program stored in memory.

[0703] Methods according to the claims or embodiments described in the specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0704] When implemented in software, a computer-readable storage medium may be provided for storing one or more programs (software modules). One or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. One or more programs include instructions that cause the electronic device to execute methods according to the claims or embodiments described in the specification of this disclosure.

[0705] Such programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, ROM (Read Only Memory), Electrically Erasable Programmable Read Only Memory (EEPROM), magnetic disc storage devices, Compact Disc-ROM (CD-ROM), Digital Versatile Discs (DVDs), or other forms of optical storage devices, magnetic cassettes. Alternatively, they may be stored in memory composed of some or all of these. Additionally, each constituent memory may include multiple units.

[0706] Additionally, the program may be stored on an attachable storage device accessible via a communication network such as the Internet, Intranet, Local Area Network (LAN), Wide LAN (WLAN), or Storage Area Network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure through an external port. Additionally, a separate storage device on a communication network may be connected to a device performing an embodiment of the present disclosure.

[0707] In the specific embodiments of the present disclosure described above, the components included in the embodiments are expressed in a singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the situation presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural form, it may be composed of a singular form, and even if a component is expressed in the singular form, it may be composed of a plural form.

[0708] Meanwhile, the embodiments of the present disclosure disclosed in this specification and drawings are merely specific examples provided to facilitate the explanation of the technical content of the present disclosure and to aid in understanding the present disclosure, and are not intended to limit the scope of the present disclosure. That is, it is obvious to those skilled in the art that other variations based on the technical concept of the present disclosure are possible. Furthermore, each of the above embodiments may be combined and operated as needed. For example, a base station and a terminal may be operated by combining parts of one embodiment of the present disclosure with parts of another embodiment. For example, a base station and a terminal may be operated by combining parts of the first embodiment and the second embodiment of the present disclosure. In addition, although the above embodiments are presented based on an FDD LTE system, other variations based on the technical concept of the above embodiments may be implemented in other systems such as TDD LTE systems, 5G, or NR systems.

[0709] Meanwhile, the order of description in the drawings illustrating the method of the present disclosure does not necessarily correspond to the order of execution, and the order of execution may be changed or executed in parallel.

[0710] Alternatively, drawings describing the method of the present disclosure may omit some components and include only some components to the extent that the essence of the present disclosure is not impaired.

[0711] Additionally, the method of the present disclosure may be executed by combining some or all of the contents included in each embodiment to the extent that it does not impair the essence thereof.

[0712] Various embodiments of the present disclosure have been described above. The foregoing description of the present disclosure is for illustrative purposes only and is not limited to the embodiments disclosed. Those skilled in the art will understand that other specific forms can be easily modified without altering the technical spirit or essential features of the present disclosure. The scope of the present disclosure is defined by the claims set forth below rather than by the foregoing detailed description, and all modifications or variations derived from the meaning and scope of the claims and equivalent concepts should be interpreted as being included within the scope of the present disclosure.

Claims

1. A method performed by UE (user equipment) in a wireless communication system, A step of receiving configuration information regarding a CSI (channel state information) report from a BS (base station) via upper layer signaling; A step of identifying a parameter indicating one of at least one set of CLI (cross-link interference) measurement resources for CLI measurement from configuration information regarding the above CSI report; and A method comprising the step of measuring CLI in a set of CSI measurement resources indicated by the identified parameters.

2. In Paragraph 1, A method in which, when a parameter indicating one of the above at least one CLI measurement resource set is set, a parameter indicating a resource for channel measurement included in the setting information regarding the CSI report is ignored.

3. In Paragraph 1, A method further comprising the step of identifying resourceForChannelCJTC, which is information indicating a set of N channel measurement resources for CJTC (coherent joint transmission calibration), from configuration information regarding the above CSI report.

4. In Paragraph 3, The above resourceForChannelCJTC is information that can be optionally set when resourcesForChannel2 is not set in the configuration information regarding the above CSI report, a method.

5. In a method performed by a BS (base station) in a wireless communication system, A step of transmitting configuration information regarding a CSI (channel state information) report to a UE (user equipment) via upper layer signaling; and A method comprising the step of receiving from the UE a report regarding CLI measured in a CLI measurement resource set indicated by a parameter included in the configuration information regarding the CSI report among at least one CLI measurement resource set for measuring CLI (cross-link interference).

6. In Paragraph 5, A method in which, when a parameter indicating one of the above at least one CLI measurement resource set is set, a parameter indicating a resource for channel measurement included in the setting information regarding the CSI report is ignored.

7. In Paragraph 5, A method comprising: the configuration information regarding the above CSI report further including resourceForChannelCJTC, which is information indicating a set of N channel measurement resources for CJTC (coherent joint transmission calibration).

8. In Paragraph 7, The above resourceForChannelCJTC is information that can be optionally set when resourcesForChannel2 is not set in the configuration information regarding the above CSI report, a method.

9. In a UE (user equipment) in a wireless communication system, Transmitter / receiver; and It includes at least one processor connected to the above-mentioned transmitting and receiving unit, and the at least one processor, Receive configuration information regarding the CSI (channel state information) report from the BS (base station) via upper layer signaling, and Identifying a parameter from the configuration information regarding the above CSI report that indicates one of at least one set of CLI measurement resources for CLI (cross-link interference) measurement, and A UE measuring CLI in the set of CSI measurement resources indicated by the above-identified parameters.

10. In Paragraph 9, A UE in which, when a parameter indicating one of the above-mentioned sets of at least one CLI measurement resource is set, a parameter indicating a resource for channel measurement included in the configuration information regarding the CSI report is ignored.

11. In paragraph 9, the above at least one processor, A UE that identifies resourceForChannelCJTC, which is information indicating a set of N channel measurement resources for CJTC (coherent joint transmission calibration), from configuration information regarding the above CSI report.

12. In Paragraph 11, The above resourceForChannelCJTC is information that can be optionally set in the case where resourcesForChannel2 is not set in the configuration information regarding the above CSI report, for the UE.

13. In a BS (base station) in a wireless communication system, Transmitter / receiver; and It includes at least one processor connected to the above-mentioned transmitting and receiving unit, and the at least one processor, Transmit configuration information regarding CSI (channel state information) reports to the UE (user equipment) via upper-layer signaling, and A BS that receives from the UE a report regarding CLI measured in a CLI measurement resource set indicated by a parameter included in the configuration information regarding the CSI report among at least one CLI measurement resource set for measuring CLI (cross-link interference).

14. In Paragraph 13, BS, where if a parameter indicating one of the above-mentioned sets of at least one CLI measurement resource is set, a parameter indicating a resource for channel measurement included in the configuration information regarding the CSI report is ignored.

15. In Paragraph 13, The configuration information regarding the above CSI report further includes resourceForChannelCJTC, which is information indicating a set of N channel measurement resources for CJTC (coherent joint transmission calibration), BS.

Images