Method and apparatus for transmission and reception of reference signals in a wireless communication system

Abstract

This disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. Embodiments of this disclosure may include: receiving configuration information from a base station regarding a Channel State Information (CSI)-Reference Signal (RS) resource set having more than 32 antenna ports, wherein the CSI-RS resource set includes an aggregation of multiple CSI-RS resources as associated CSI-RS; receiving a downlink control channel (DCI) requesting a sounding reference signal (SRS) from the base station; receiving the associated CSI-RS from the base station; transmitting the SRS to the base station based on the DCI; and transmitting a non-codebook-based Physical Uplink Shared Channel (PUSCH) to the base station according to the SRS, wherein the number of the multiple CSI-RS resources is one of 2, 3, or 4.

Description

Technical Field

[0001] This disclosure relates to the operation of user equipment (UE) and base stations in a wireless communication system. More specifically, this disclosure relates to a method for transmitting and receiving reference signals in a wireless communication system, and an apparatus capable of performing transmission and reception. Background Technology

[0002] 5G mobile communication technology defines a wide frequency band, enabling high transmission rates and new services. It can be implemented not only in the "sub-6 GHz" band, such as 3.5 GHz, but also in the "above 6 GHz" band, including 28 GHz and 39 GHz, known as millimeter wave (mmWave). Furthermore, to achieve transmission rates 50 times faster than 5G and ultra-low latency one-tenth that of 5G, implementation of 6G mobile communication technology (referred to as "super 5G systems") in terahertz bands (e.g., the 95 GHz to 3 THz band) has been considered.

[0003] In the early stages of 5G mobile communication technology development, to support services and meet performance requirements related to enhanced Mobile Broadband (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), standardization has been underway for the following: beamforming and massive MIMO to mitigate radio wave path loss and increase radio wave transmission distance in millimeter waves; support for basic parameter sets (e.g., operating multiple subcarrier spacings) for efficient utilization of millimeter wave resources and dynamic operation of time slot formats; initial access technologies to support multi-beam transmission and broadband; definition and operation of the Bandwidth Part (BWP); new channel coding methods, such as low-density parity-check (LDPC) codes for large-scale data transmission and polar codes for highly reliable transmission of control information; L2 preprocessing; and network slicing to provide dedicated networks for specific services.

[0004] Currently, given the services that 5G mobile communication technology will support, discussions are underway regarding improvements and performance enhancements to the initial 5G mobile communication technology, and physical layer standardization already exists for technologies such as: Vehicle-to-everything (V2X), used to assist autonomous vehicles in determining driving based on information sent by the vehicle about its location and status, and to enhance user convenience; New Radio Unlicensed (NR-U), for system operation in compliance with various regulatory requirements in unlicensed frequency bands; NR UE power saving; Non-Terrestrial Network (NTN), which is UE-satellite direct communication used to provide coverage in areas where communication with terrestrial networks is unavailable; and positioning.

[0005] Furthermore, standardization is underway in air interface architecture / protocols for technologies such as: Industrial Internet of Things (IIoT) to support new services through interoperability and convergence with other industries; Integrated Access and Backhaul (IAB) to provide nodes for network service area extension by supporting radio backhaul and access links in an integrated manner; mobility enhancements, including conditional handover and Dual Active Protocol Stack (DAPS) handover; and two-step random access to simplify random access procedures (2-step RACH for NR). Standardization is also underway in system architecture / services for: 5G baseline architecture (e.g., service-based architecture or service-based interface) to combine Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies; and Mobile Edge Computing (MEC) for receiving services based on UE location.

[0006] With the commercialization of 5G mobile communication systems, the already exponentially growing number of connected devices will connect to the communication network. Accordingly, enhanced functionality and performance of 5G mobile communication systems, as well as the integrated operation of connected devices, are expected to be necessary. To this end, new research is planned related to the following: extended reality (XR) for effectively supporting augmented reality (AR), virtual reality (VR), mixed reality (MR), etc.; improving 5G performance and reducing complexity by leveraging artificial intelligence (AI) and machine learning (ML); AI service support; metaverse service support; and drone communication.

[0007] Furthermore, this development of 5G mobile communication systems will not only serve as the foundation for developing new waveforms for providing terahertz band coverage for 6G mobile communication technologies, multi-antenna transmission technologies (such as full-dimensional MIMO (FD-MIMO), array antennas, and massive MIMO), metamaterial-based lenses and antennas for improving terahertz band signal coverage, high-dimensional spatial multiplexing technologies using orbital angular momentum (OAM), and reconfigurable intelligent surfaces (RIS), but also as the foundation for developing full-duplex technologies to improve the frequency efficiency of 6G mobile communication technologies and improve system networks, AI-based communication technologies to implement system optimization by leveraging satellites and artificial intelligence (AI) from the design stage and internalizing end-to-end AI support capabilities, and next-generation distributed computing technologies to implement services with complexity exceeding the limits of UE operational capabilities by utilizing ultra-high-performance communication and computing resources.

[0008] The above information is presented as background information only to aid in understanding this disclosure. No determination or assertion has been made as to whether any of the above content can be used as prior art in this disclosure. Summary of the Invention

[0009] Solution to the problem

[0010] This disclosure relates to wireless communication networks, and more specifically to terminals in wireless communication systems and communication methods thereof.

[0011] According to one aspect of this disclosure, a method for processing control signals in a wireless communication system includes: receiving a first control signal transmitted from a base station; processing the received first control signal; and transmitting a second control signal generated based on the processing to the base station.

[0012] [Beneficial effects of the invention]

[0013] The present disclosure is intended to address at least the aforementioned problems and / or disadvantages, and to provide at least the following advantages. Therefore, one aspect of the present disclosure provides an efficient communication method in a wireless communication system. Attached Figure Description

[0014] The above and other aspects, features, and accompanying advantages of certain embodiments of this disclosure will become more apparent and readily understood from the following description taken in conjunction with the accompanying drawings, in which:

[0015] Figure 1 The basic structure of the time-frequency domain in a wireless communication system according to an embodiment of the present disclosure is shown;

[0016] Figure 2 The structure of frames, subframes, and time slots in a wireless communication system according to embodiments of the present disclosure is shown;

[0017] Figure 3 An example of bandwidth configuration in a wireless communication system according to an embodiment of the present disclosure is shown;

[0018] Figure 4 The radio protocol structures of a base station and a UE in a wireless communication system according to embodiments of the present disclosure are shown in single-cell, carrier aggregation, and dual connectivity scenarios;

[0019] Figure 5 An example of a non-periodic CSI reporting method according to an embodiment of the present disclosure is shown;

[0020] Figure 6 An example of the configuration of the control resource set of the downlink control channel in a wireless communication system according to an embodiment of the present disclosure is shown;

[0021] Figure 7 The structure of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure is shown;

[0022] Figure 8 A non-codebook-based PUSCH transmission process according to an embodiment of the present disclosure is illustrated;

[0023] Figure 9 The possible locations where non-periodic correlated CSI-RS may exist according to embodiments of the present disclosure are shown;

[0024] Figure 10 The operation of a UE according to an embodiment of the present disclosure is illustrated;

[0025] Figure 11 The operation of a base station according to an embodiment of the present disclosure is illustrated;

[0026] Figure 12 The structure of a UE in a wireless communication system according to an embodiment of the present disclosure is shown; and

[0027] Figure 13 The structure of a base station in a wireless communication system according to an embodiment of the present disclosure is shown. Detailed Implementation

[0028] [Best Mode for Performing the Invention]

[0029] The present disclosure is intended to address at least the aforementioned problems and / or disadvantages, and to provide at least the following advantages. Therefore, one aspect of the present disclosure is to provide a terminal in a wireless communication system and a communication method thereof.

[0030] The disclosed embodiments provide an apparatus and method for effectively providing services in a mobile communication system.

[0031] To address the aforementioned problems, this disclosure provides a method for processing control signals in a wireless communication system. The method includes: receiving a first control signal transmitted from a base station; processing the received first control signal; and transmitting a second control signal generated based on the processing to the base station.

[0032] The disclosed embodiments provide an apparatus and method for effectively providing services in a mobile communication system.

[0033] Before proceeding with the detailed implementation below, it may be advantageous to define certain words and phrases used throughout this patent document: the terms “include” and “comprise” and their derivatives mean including but not limited to; the term “or” is inclusive, meaning and / or; the phrases “associated with” and “associated with” and their derivatives may mean including, being included in, interconnected with, containing, being contained in, connected to or connected to, coupled to or coupled to, able to communicate with, cooperate with, interleaved with, juxtaposed, proximate, bound to or with, possessing, having the attributes of, etc.; the term “controller” means any device, system or part thereof that controls at least one operation, such device may be implemented in hardware, firmware or software, or some combination of at least two of these. It should be noted that the functionality associated with any particular controller, whether local or remote, can be centralized or distributed.

[0034] Furthermore, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by computer-readable program code and embodied in a computer-readable medium. The terms "application program" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation in appropriate computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, optical disc (CD), digital optical disc, video optical disc (DVD), or any other type of storage. "Non-transitory" computer-readable medium excludes wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable medium includes media that can permanently store data and media that can store data and subsequently be rewritten, such as rewritable optical discs or erasable memory devices.

[0035] Definitions of certain words and phrases are provided throughout this patent document, and those skilled in the art will understand that, in many (if not most) instances, such definitions apply to the prior and future use of the words and phrases defined in this document.

[0036] [Invention Model]

[0037] The following discussion Figures 1 to 13 The various embodiments described in this patent document to illustrate the principles of this disclosure are merely illustrative and should not be construed as limiting the scope of this disclosure in any way. Those skilled in the art will understand that the principles of this disclosure can be implemented in any suitably arranged system or device.

[0038] The embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.

[0039] In describing the embodiments, descriptions related to well-known technical content in the relevant art and not directly related to this disclosure will be omitted. This omission of unnecessary descriptions is intended to prevent obscuring the main ideas of this disclosure and to convey the main ideas more clearly.

[0040] For the same reason, some elements may be exaggerated, omitted, or shown schematically in the accompanying drawings. Furthermore, the size of each element does not perfectly reflect its actual size. In the corresponding figures, the same or corresponding elements are assigned the same reference numerals.

[0041] The advantages and features of this disclosure, as well as the ways in which they are implemented, will become apparent from the embodiments described in detail below with reference to the accompanying drawings. However, this disclosure is not limited to the embodiments set forth below, but can be implemented in various different forms. The following embodiments are provided only to fully disclose this disclosure and to inform those skilled in the art of its scope, and this disclosure is limited only by the scope of the appended claims. Throughout the specification, the same or similar reference numerals indicate the same or similar elements. Furthermore, in describing this disclosure, descriptions of known functions or configurations incorporated herein will be omitted where it is determined that a detailed description would unnecessarily obscure the subject matter of the disclosure. The terms to be described below are functionally defined according to this disclosure and may vary depending on the user, user intent, or custom. Therefore, the definitions of the terms should be made based on the entirety of the specification.

[0042] In the following description, a base station is an entity that allocates resources to terminals and can be at least one of a gNodeB, eNodeB, NodeB, base station (BS), radio access unit, base station controller, and nodes on a network. A terminal can include a user equipment (UE), mobile station (MS), cellular phone, smartphone, computer, or multimedia system capable of performing communication functions. In this disclosure, "downlink (DL)" refers to a radio link through which a base station transmits signals to a terminal, and "uplink (UL)" refers to a radio link through which a terminal transmits signals to a base station. Furthermore, while LTE or LTE-A systems are described by way of example in the following description, embodiments of this disclosure can also be applied to other communication systems with similar technical backgrounds or channel types. Examples of such communication systems may include fifth-generation mobile communication technologies (5G, new radio, and NR) developed beyond LTE-A, and in the following description, "5G" can be a concept covering existing LTE, LTE-A, and other similar services. Additionally, based on the assessment of those skilled in the art, this disclosure can be applied to other communication systems with modifications without explicitly departing from its scope. The content of this disclosure can be applied to FDD and TDD systems.

[0043] In this document, it should be understood that each box in a flowchart, and combinations of boxes in a flowchart, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to start a machine, such that instructions executed via the computer's processor or other programmable data processing apparatus produce means for implementing the functions specified in one or more flowchart boxes. These computer program instructions can also be stored in a computer-usable or computer-readable storage medium that can instruct a computer or other programmable data processing apparatus to function in a particular manner, such that instructions stored in the computer-usable or computer-readable storage medium produce an article of writing including instruction means for implementing the functions specified in one or more flowchart boxes. The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that instructions executing on the computer or other programmable apparatus provide steps for implementing the functions specified in one or more flowchart boxes.

[0044] Furthermore, each box in a flowchart can represent a module, code segment, or section, which includes one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the boxes may not appear in sequence. For example, two boxes shown consecutively may actually execute substantially concurrently, or the boxes may sometimes execute in reverse order, depending on the functionality involved.

[0045] As used in embodiments of this disclosure, "unit" refers to a software or hardware element that performs a predetermined function, such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC). However, "unit" does not always have a meaning limited to software or hardware. A "unit" can be configured to be stored in addressable storage media or to execute one or more processors. Thus, a "unit" includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and parameters. Elements and functions provided by a "unit" can be combined into a smaller number of elements or "units," or divided into a larger number of elements or "units." Furthermore, elements and "units" can be implemented to reproduce one or more CPUs within a device or secure multimedia card. Additionally, a "unit" in the embodiments may include one or more processors.

[0046] In the following description of this disclosure, descriptions will be omitted where it is determined that a detailed description of a known function or configuration incorporated herein may unnecessarily obscure the subject matter of this disclosure. Embodiments of this disclosure will now be described with reference to the accompanying drawings.

[0047] Wireless communication systems are evolving towards broadband wireless communication systems to provide high-speed and high-quality packet data services, as well as typical voice-based services, using communication standards such as 3GPP High-Speed ​​Packet Access (HSPA), LTE (Long Term Evolution or Evolved Universal Terrestrial Radio Access (E-UTRA)), LTE-A Advanced, LTE-Pro, 3GPP2 High-Speed ​​Packet Data (HRPD), Ultra Mobile Broadband (UMB), and IEEE 802.16e.

[0048] As a typical example of a broadband wireless communication system, the LTE system employs Orthogonal Frequency Division Multiplexing (OFDM) in the downlink (DL) and Single-Carrier Frequency Division Multiple Access (SC-FDMA) in the uplink (UL). The uplink refers to the radio link through which a User Equipment (UE) or Mobile Station (MS) transmits data or control signals to a Base Station (BS) or eNodeB, while the downlink refers to the radio link through which the Base Station transmits data or control signals to the UE. These multiple access schemes can separate the data or control information of each user by allocating and manipulating time-frequency resources to avoid overlap, that is, to establish orthogonality.

[0049] Because 5G communication systems (which follow LTE) must freely reflect the diverse needs of users, service providers, and others, they must support services that meet these diverse needs. Services considered for 5G communication systems include enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC).

[0050] eMBB aims to provide higher data rates than those supported by existing LTE, LTE-A, or LTE-Pro. For example, in 5G communication systems, eMBB must provide a peak data rate of 20 Gbps in the downlink and 10 Gbps in the uplink for a single base station. Furthermore, 5G communication systems must provide higher user-aware data rates and maximum data rates to the UE. To meet these requirements, improved transmit / receive technologies, including further enhanced multiple-input multiple-output (MIMO) transmission techniques, are needed. Moreover, the data rates required by 5G communication systems can be achieved by using frequency bandwidths exceeding 20 MHz in the 3 GHz to 6 GHz or higher frequency bands, rather than by transmitting signals using up to 20 MHz of transmission bandwidth in the 2 GHz band used in LTE.

[0051] In addition, mMTC is being considered for supporting application services such as the Internet of Things (IoT) in 5G communication systems. To effectively provide IoT services, mMTC has requirements such as supporting a large number of UEs within a cell, enhancing UE coverage, extending battery life, and reducing UE costs. Since IoT provides communication services while simultaneously enabling communication for various sensors and devices, it must support a large number of UEs within a cell (e.g., 1,000,000 UEs / km²). Furthermore, because mMTC-enabled UEs may be located in blind spots not covered by the cell due to the nature of the service (such as building basements), they may require a wider coverage area than other services provided by 5G communication systems. mMTC-enabled UEs must be configured to be inexpensive and may require very long battery lives, such as 10 to 15 years, due to the difficulty of frequently replacing UE batteries.

[0052] Finally, URLLC is a mission-critical wireless communication service based on cellular networks. For example, URLLC can be used for services such as remote control of robots or machines, industrial automation, drones, telemedicine, and emergency alerts. Therefore, URLLC must provide ultra-low latency and ultra-high reliability communication. For instance, services supporting URLLC must meet an air interface latency of less than 0.5 ms and may also require a packet error rate of 10⁻⁵ or less. Therefore, for services supporting URLLC, 5G systems must provide shorter Transmission Time Intervals (TTIs) than other services and may also require designs that allocate significant resources within the frequency band to ensure the reliability of the communication link.

[0053] In 5G, the three services—eMBB, URLLC, and mMTC—can be multiplexed and transmitted within a single system. In this case, different transmit / receive technologies and parameters can be used between the services to meet their different requirements. Of course, 5G is not limited to these three services.

[0054] In the following description, the term "a / b" can be understood as at least one of a and b.

[0055] [NR Time and Frequency Resources]

[0056] The frame structure of a 5G system will be described in detail below with reference to the accompanying drawings.

[0057] Figure 1 The basic structure of the time-frequency domain (which is the radio resource domain used for transmitting data or control channels in 5G systems) is shown.

[0058] Figure 1 The horizontal axis in the diagram represents the time domain, while... Figure 1The vertical axis in the time-frequency domain represents the frequency domain. The basic unit of a resource in the time-frequency domain is a resource element (RE) 101, which can be defined as an orthogonal frequency division multiplexing (OFDM) symbol 102 on the time axis and a subcarrier 103 on the frequency axis. In the frequency domain, One (e.g., 12) consecutive REs can constitute a resource block (RB) 104. In the time domain, a subframe 110 can include multiple OFDM symbols 102. For example, the length of a subframe can be 1 ms.

[0059] Figure 2 The structure of frames, subframes, and time slots in a wireless communication system according to embodiments of the present disclosure is shown.

[0060] refer to Figure 2 , Figure 2 An example of the structure of frame 200, subframe 201, and time slot 202 is shown. A frame 200 can be defined as 10 ms. A subframe 201 can be defined as 1 ms, and therefore, a frame 200 can include a total of ten subframes 201. A time slot 202 or 203 can be defined as 14 OFDM symbols (i.e., the number of symbols per time slot is (...)). (14). A subframe 201 may include one or more time slots 202 and 203, and the number of time slots 202 and 203 in each subframe 201 may vary depending on the configuration value μ 204 or 205 of the subcarrier spacing. Figure 2 The examples illustrate the cases where μ=0 (204) and μ=1 (205) are configured values ​​for the subcarrier spacing. In the case of μ=0 (204), a subframe 201 can contain one time slot 202, and in the case of μ=1 (205), a subframe 201 can contain two time slots 203. That is, the number of time slots per subframe... This may vary depending on the subcarrier spacing configuration value µ, and therefore the number of time slots per frame. They may be different. and The µ configuration can be defined according to each subcarrier spacing in Table 1 below.

[0061] [Table 1]

[0062]

[0063] [Bandwidth Component (BWP)]

[0064] The bandwidth portion (BWP) configuration in a 5G communication system will now be described in detail with reference to the accompanying drawings.

[0065] Figure 3An example of bandwidth configuration in a wireless communication system according to an embodiment of the present disclosure is shown.

[0066] Figure 3 An example is shown where the UE bandwidth 300 is configured to include two bandwidth portions (i.e., bandwidth portion #1 (BWP#1) 301 and bandwidth portion #2 (BWP#2) 302). The base station can configure one or more bandwidth portions for the UE, and can configure the following information as given in Table 2 for each bandwidth portion.

[0067] [Table 2]

[0068]

[0069] Of course, bandwidth configuration is not limited to the examples in Table 2, and various parameters related to bandwidth can be configured for the UE in addition to the configuration information in Table 2. The base station can transmit configuration information to the UE via upper-layer signaling (e.g., Radio Resource Control (RRC) signaling). A configured bandwidth portion can be activated, or at least one of multiple configured bandwidth portions can be activated. Whether a configured bandwidth portion is activated can be semi-statically transmitted from the base station to the UE via RRC signaling, or dynamically transmitted via downlink control information (DCI).

[0070] According to an embodiment, prior to Radio Resource Control (RRC) connection, the base station can configure an Initial Bandwidth Part (BWP) for initial access for the UE via the Master Information Block (MIB). More specifically, the UE can receive configuration information regarding the Control Resource Set (CORESET) and the search space, which can be used to transmit the PDCCH to receive system information (which may correspond to the Remaining System Information (RMSI) or System Information Block 1 (SIB1) required for initial access via the MIB during the initial access step). Each of the Control Resource Set and the search space configured via the MIB can be considered as ID 0. The base station can notify the UE of configuration information regarding Control Area #0 (such as frequency allocation information, time allocation information, and parameter sets) via the MIB. Additionally, the base station can notify the UE of configuration information regarding the listening period and timing for Control Resource Set #0 (i.e., configuration information regarding Search Space #0) via the MIB. The UE can consider the frequency domain configured by Control Resource Set #0 obtained from the MIB as the Initial Bandwidth Part for initial access. The ID of the Initial Bandwidth Part can be considered as 0.

[0071] According to various embodiments of this disclosure, the bandwidth-related configurations supported by 5G can be used for a variety of purposes.

[0072] According to an embodiment, if the bandwidth supported by the UE is less than the system bandwidth, this can be supported through bandwidth portion configuration. For example, the base station can configure the frequency location of the bandwidth portion for the UE (configuration information 2), enabling the UE to send / receive data at a specific frequency location within the system bandwidth.

[0073] Additionally, according to embodiments, the base station can be configured with multiple bandwidth portions for the UE to support different parameter sets. For example, to support the UE in transmitting / receiving data using 15 kHz and 30 kHz subcarrier intervals, the two bandwidth portions can be configured with 15 kHz and 30 kHz subcarrier intervals, respectively. The different bandwidth portions can be frequency-division multiplexed (FDM), and the bandwidth portion configured for the corresponding subcarrier interval can be activated if data needs to be transmitted / received at a specific subcarrier interval.

[0074] Additionally, according to embodiments, the base station can configure bandwidth portions with different bandwidth sizes for the UE to reduce the power consumed by the UE. For example, if the UE supports a fairly large bandwidth (e.g., 100 MHz) and always transmits / receives data at the corresponding bandwidth, it may result in a considerable amount of power consumption. Specifically, from a power consumption perspective, unnecessarily detecting a large 100 MHz downlink control channel in the absence of traffic can cause significant inefficiency. To reduce the power consumed by the UE, the base station can configure a relatively small bandwidth portion for the UE (e.g., a 20 MHz bandwidth portion). In the absence of traffic, the UE can perform listening operations in the 20 MHz bandwidth portion, and if data occurs, it can transmit / receive data at the 100 MHz bandwidth portion according to the base station's instructions.

[0075] Regarding the bandwidth configuration method, the UE can receive configuration information about the initial bandwidth portion via the MIB during the initial access step before RRC connection. More specifically, the UE can configure a control resource set (i.e., CORESET) for the downlink control channel, which can be used to transmit downlink control information (DCI) to schedule system information blocks (SIBs) from the MIB of the physical broadcast channel (PBCH). The bandwidth of the control resource set configured by the MIB can be regarded as the initial bandwidth portion, and the UE can receive the physical downlink shared channel (PDSCH) through the configured initial bandwidth portion, through which SIBs are transmitted. The initial bandwidth portion can be used not only for receiving SIBs but also for other system information (OSI), paging, random access, etc.

[0076] [Bandwidth Component (BWP) Changes]

[0077] If one or more bandwidth portions have been configured for the UE, the base station can indicate to the UE to change (or switch or transform) the bandwidth portion by using the bandwidth portion indication field within the DCI. For example, if the UE's currently active bandwidth portion is... Figure 3 If the bandwidth portion #1 301 is in the DCI, the base station can use the bandwidth portion indicator in the DCI to indicate the bandwidth portion #2 302, and the UE can change the bandwidth portion to the bandwidth portion #2 302 indicated by the bandwidth portion indicator inside the received DCI.

[0078] As mentioned above, the DCI can instruct the scheduling of PDSCH or PUSCH based on a bandwidth portion change. Therefore, when a bandwidth portion change request is received, the UE needs to be able to receive or transmit the PDSCH or PUSCH scheduled by the corresponding DCI in the changed bandwidth portion without any problems. To this end, the standard specifies the required delay time (T) during the bandwidth portion change. BWP The requirements are as follows, and these requirements can be defined, for example, as shown in Table 3 below. Clearly, the examples given below are not restrictive.

[0079] [Table 3]

[0080]

[0081] Depending on the UE's capabilities, the requirement for bandwidth portion change delay time supports either Type 1 or Type 2. The UE can report the supported bandwidth portion change delay time types to the base station.

[0082] If the UE receives a DCI including a bandwidth portion change indicator in time slot n, according to the aforementioned requirements regarding the bandwidth portion change delay time, the UE can complete the change to the new bandwidth portion indicated by the bandwidth portion change indicator at a time point no later than time slot n + TBWP, and can transmit / receive data channels scheduled by the corresponding DCI in the newly changed bandwidth portion. If the base station wants to schedule data channels using the new bandwidth portion, the base station can determine the temporal resource allocation for the data channels based on the UE's bandwidth portion change delay time (TBWP). That is, when scheduling data channels using the new bandwidth portion, the base station can schedule the corresponding data channels after the bandwidth portion change delay time using the method for determining the temporal resource allocation for the data channels. Therefore, the UE may not expect the DCI indicating the bandwidth portion change to indicate a time period less than the bandwidth portion change delay time (TBWP). BWP The time slot offset (K0 or K2).

[0083] If the UE receives a DCI indicating a partial bandwidth change (e.g., DCI format 1_1 or 0_1), the UE may not perform any transmission or reception during the time interval from the third symbol of the slot used to receive the PDCCH including the corresponding DCI to the start point of the slot indicated by the slot offset (K0 or K2) value indicated by the time domain resource allocation indicator field in the corresponding DCI. For example, if the UE receives a DCI indicating a partial bandwidth change in slot n, and if the slot offset value indicated by the corresponding DCI is K, the UE may not perform transmission or reception from the third symbol of slot n to the symbols preceding slot n+K (e.g., the last symbol of slot n+K-1).

[0084] [About CA / DC]

[0085] Figure 4 The radio protocol structures of a base station and a UE in a wireless communication system according to embodiments of the present disclosure are shown in single-cell, carrier aggregation, and dual-connectivity scenarios.

[0086] refer to Figure 4 The radio protocols for next-generation mobile communication systems include NR Service Data Adaptive Protocol (SDAP) 425 or 470, NR Packet Data Convergence Protocol (PDCP) 430 or 465, NR Radio Link Control (RLC) 435 or 460, and NR Media Access Control (MAC) 440 or 455 on both the UE and NR base station sides. Clearly, the above examples are not limiting, and radio protocols can include more or fewer layers.

[0087] The main functions of the NR SDAP 425 or 470 may include the following. Obviously, the examples given below are not limiting:

[0088] -Transmission of user plane data;

[0089] - Mapping between QoS flows and DRB for both DL and UL;

[0090] - Mark QoS flow IDs in downlink and uplink data packets; and / or

[0091] - UL SDAP PDU reflective QoS flow to DRB mapping.

[0092] Regarding SDAP layer devices 425 or 470, whether to use the SDAP layer device header or its functionality can be configured for the UE via RRC messages based on the PDCP layer device, the bearer, or the logical channel. If the SDAP header is configured, the base station can indicate the NAS QoS reflection configuration 1-bit indicator (NAS reflective QoS) and its AS QoS reflection configuration 1-bit indicator (AS reflective QoS) in the SDAP header, allowing the UE to update or reconfigure the mapping information of uplink and downlink QoS flows and data bearers. The SDAP header may include QoS flow ID information indicating QoS. QoS information can be used for data processing priority, scheduling information, etc., to smoothly support various services.

[0093] The main functions of NR PDCP 430 or 465 may include the following. Obviously, the examples given below are not limiting:

[0094] - Header compression and decompression: Robust header compression only (ROHC);

[0095] -Transmission of user data;

[0096] - Ordered delivery of upper-layer PDUs;

[0097] -Out-of-order delivery of upper-layer PDUs;

[0098] -PDCP PDU reordering for reception;

[0099] - Duplicate detection of lower-level SDUs;

[0100] -Retransmission of PDCP SDU;

[0101] - Encryption and decryption; and / or

[0102] - Timer-based SDU dropping in the uplink.

[0103] Reordering in NR PDCP devices 430 or 465 refers to the function of reordering PDCP PDUs received from the lower layer in order based on PDCP sequence numbers (SNs), and may include the function of passing data to the upper layer in the reordered order. Alternatively, reordering in NR PDCP devices 430 or 465 may include at least one of the following: the function of immediately transmitting data regardless of order; the function of recording PDCP PDUs lost due to reordering; the function of reporting the status of lost PDCP PDUs to the sender; and the function of requesting retransmission of lost PDCP PDUs.

[0104] The main functions of the NR RLC 435 or 460 may include the following. Obviously, the examples given below are not limiting:

[0105] -Transmission of upper-layer PDUs;

[0106] - Ordered delivery of upper-layer PDUs;

[0107] -Out-of-order delivery of upper-layer PDUs;

[0108] - Error correction via ARQ;

[0109] - Cascading, splitting, and reassembling of RLC SDUs;

[0110] - Re-segmentation of RLC data PDUs;

[0111] - Reordering of RLC data PDUs;

[0112] -Repeated detection;

[0113] - Protocol error detection;

[0114] -RLC SDU discarded; and / or

[0115] -RLC reconstruction.

[0116] The ordered delivery of NR RLC devices 435 or 460 can refer to the function of sequentially delivering RLC SDUs received from lower layers to upper layers. The ordered delivery of NR RLC devices can include at least one of the following: when an original RLC SDU is fragmented into multiple RLC SDUs and the fragmented RLC SDUs are received, the function of reassembling the RLC SDUs and delivering the reassembly RLC SDUs; the function of reordering received RLC PDUs according to the RLC sequence number (SN) or PDCP sequence number (SN); the function of recording RLC PDUs lost due to reordering; the function of reporting the status of lost RLC PDUs to the transmitter; and the function of requesting retransmission of lost RLC PDUs. The ordered delivery function of NR RLC devices 435 or 460 can include at least one of the following: when an RLC SDU is lost, the function of sequentially delivering only the RLC SDUs preceding the lost RLC SDU to the upper layer; and when a predetermined timer has expired but a lost RLC SDU exists, the function of sequentially delivering all RLC SDUs received before the timer starts to the upper layer.

[0117] Alternatively, ordered delivery by the NR RLC device may include the function of sequentially delivering all currently received RLC SDUs to the upper layer when a predetermined timer has expired but a lost RLC SDU exists. Additionally, ordered delivery by the NR RLC device 435 or 460 may include the function of processing RLC PDUs in the order of reception (arrival order regardless of sequence number order) and delivering the RLC PDUs to the PDCP device regardless of order (out-of-order delivery), and may include the function of receiving fragments stored in a buffer or received later, reconfiguring them into a complete RLC PDU, processing the complete RLC PDU, and delivering it to the PDCP device. The NR RLC layer may not include cascading functionality, which may be implemented in the NR MAC layer or replaced by multiplexing functionality of the NR MAC layer.

[0118] Out-of-order delivery of NR RLC devices 435 or 460 can refer to the function of delivering RLC SDUs received from lower layers directly to upper layers regardless of their order. Out-of-order delivery of NR RLC devices may include at least one of the following: when an original RLC SDU is fragmented into multiple RLC SDUs and the fragmented RLC SDUs are received, reassembling the RLC SDUs and delivering the reassembly RLC SDUs; and storing the RLC SN or PDCP SN of the received RLC PDUs and recording RLC PDUs lost due to reordering.

[0119] NR MAC 440 or 455 can connect to multiple NR RLC layer devices configured in a UE, and the main functions of NR MAC can include some of the following. Obviously, the examples given below are not limiting:

[0120] - Mapping between logical channels and transmission channels;

[0121] - Multiplexing / demultiplexing of MAC SDUs;

[0122] - Scheduling information report;

[0123] - Error correction via HARQ;

[0124] - Priority processing between logical channels of a UE;

[0125] - Priority processing between UEs is achieved through dynamic scheduling;

[0126] -MBMS service identifier;

[0127] -Transmission format selection; and / or

[0128] -filling.

[0129] The NRPHY layer 445 or 450 can perform channel coding and modulation of upper-layer data to obtain OFDM symbols, and deliver OFDM symbols via radio channels, or demodulate OFDM symbols received via radio channels, perform channel decoding, and deliver them to the upper layers. Clearly, the examples given above are not limiting.

[0130] Depending on the carrier (or cell) operation scheme, the detailed structure of the radio protocol architecture can vary. For example, if the base station transmits data to the UE based on a single carrier (or cell), the base station and UE can use a protocol architecture with a single structure for each layer, such as 400. On the other hand, if the base station transmits data to the UE based on carrier aggregation (CA) using multiple carriers in a single TRP, the base station and UE can use a protocol architecture with a single structure suitable for RLC but multiplexing the PHY layer through the MAC layer, such as 410. As another example, if the base station transmits data to the UE based on dual connectivity (DC) using multiple carriers in multiple TRPs, the base station and UE can use a protocol architecture with a single structure suitable for RLC but multiplexing the PHY layer through the MAC layer, such as 420.

[0131] [CSI Resource Configuration]

[0132] In NR, a CSI framework can exist, instructing the base station to measure and report Channel State Information (CSI) of the UE. An NR CSI framework can contain at least two elements, such as resource settings and reporting settings, and the reporting settings can be associated with each other by referencing at least one ID of the resource settings.

[0133] According to embodiments of this disclosure, resource settings may include information related to a reference signal (RS) used to measure channel state information via the UE. The base station may configure one or more resource settings in the UE. For example, the base station and the UE may exchange signaling information as described in Table 4 to transmit information related to resource settings. Of course, this is not limited to the following examples.

[0134] [Table 4]

[0135]

[0136]

[0137] In Table 4, the signaling information CSI-ResourceConfig can include information about each resource setting. According to the signaling information in Table 4, each resource setting can include a resource setting index (csi-ResourceConfigId), a BWP index (bwp-ID), the transmission configuration on the resource time axis, or a resource set list (csi-RS-ResourceSetList) that includes at least one resource set. The time-domain transmission configuration of the resource can be configured as aperiodic, semi-persistent, or periodic transmission. The resource set list can be a collection of resource sets used for channel measurements or a collection of resource sets used for interference measurements. If the resource set list is a collection of resource sets used for channel measurements, then each resource set can include at least one resource, and this at least one resource can correspond to an index of a CSI Reference Signal (CSI-RS) resource or a Synchronization / Broadcast Channel Block (SS / PBCH Block, SSB). If the resource set list is a collection of resource sets used for interference measurements, then each resource set can include at least one interference measurement resource (CSI Interference Measurement, CSI-IM).

[0138] For example, when the resource set includes CSI-RS, the base station and UE can exchange signaling information as described in Table 5 below to transmit information related to the resource set. Of course, this is not limited to the following examples.

[0139] [Table 5]

[0140]

[0141] The signaling information NZP-CSI-RS-ResourceSet in Table 5 may include information associated with each resource set. Depending on the signaling information, each resource set may include information associated with at least one resource set index (nzp-CSI-ResourceSetId) or CSI-RS index set (nzp-CSI-RS-Resources). Additionally, each resource set may include a portion of information (repeated) related to the spatial domain transmission filter of the CSI-RS resource or a portion of information related to whether the CSI-RS resource is used for tracking (trs-Info).

[0142] CSI-RS can be the most representative reference signal included in the resource set. The base station and UE can exchange signaling information as described in Table 6 below to transmit information related to CSI-RS resources. Of course, this is not limited to the examples below.

[0143] [Table 6]

[0144]

[0145] The signaling information NZP-CSI-RS-Resource in Table 6 may include information related to each CSI-RS. The information included in the signaling information NZP-CSI-RS-Resource may have the following meanings, but is not limited to:

[0146] -nzp-CSI-RS-ResourceId: CSI-RS resource index;

[0147] -resourceMapping: Resource mapping information for CSI-RS resources;

[0148] -powerControlOffset: The ratio between PDSCH energy per RE (EPRE) and CSI-RS EPRE;

[0149] -powerControlOffsetSS: The ratio between the SS / PBCH block EPRE and the CSI-RS EPRE;

[0150] -scramblingID: The scrambling index of the CSI-RS sequence;

[0151] -periodicityAndOffset: Transmission period and slot offset of CSI-RS resources; and / or

[0152] -qcl-InfoPeriodicCSI-RS: If the corresponding CSI-RS is a periodic CSI-RS, then the TCI status information.

[0153] The resourceMapping included in the signaling information NZP-CSI-RS-Resource indicates the resource mapping information of CSI-RS resources, and may include at least one of the following: mapping of resource elements (REs) of frequency resources, 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, which can be configured through resourceMapping, can have specific values ​​in one row of each row in Table 7 below. Of course, this is not limited to the examples below.

[0154] [Table 7]

[0155]

[0156]

[0157]

[0158] Table 7 shows the frequency resource density that can be configured based on the number of CSI-RS ports (X), CDM type, the frequency and time domain start positions (k, l) of the CSI-RS component RE pattern, and the number of frequency domain REs (k') and time domain REs (l') of the CSI-RS component RE pattern. The aforementioned CSI-RS component RE pattern can be the basic unit for configuring CSI-RS resources. The CSI-RS component RE pattern can be configured using YZ REs through Y=1+max(k') REs in the frequency domain and Z=1+max(l') REs in the time domain. When the number of CSI-RS ports is 1, the position of the CSI-RS RE can be specified in the Physical Resource Block (PRB) without restriction on subcarriers and can be specified by a 12-bit bitmap. When the number of CSI-RS ports is {2, 4, 8, 12, 16, 24, 32} and Y equals 2 (Y=2), the location of the CSI-RS RE can be specified at every two subcarriers in the PRB, and can be specified by a bitmap with 6 bits. When the number of CSI-RS ports is 4 and Y equals 4 (Y=4), the location of the CSI-RS RE can be specified at every four subcarriers in the PRB, and can be specified by a bitmap with 3 bits. Similarly, the location of the time-domain RE can be specified by a bitmap with a total of 14 bits.

[0159] [CSI Report Configuration]

[0160] According to embodiments of this disclosure, reporting settings can be associated with each other by referencing at least one ID of a resource setting. The resource settings(s) associated with a reporting setting can provide configuration information, including information about a reference signal used to measure channel information. When the resource settings(s) associated with a reporting setting are used to measure channel information, the measured channel information can be used for channel information reporting according to a reporting method configured in the associated reporting setting.

[0161] According to embodiments of this disclosure, resource settings may include configuration information related to the CSI reporting method. For example, the base station and the UE may exchange signaling information as described in Table 8 to transmit information related to resource settings. Of course, this is not limited to the following examples.

[0162] [Table 8]

[0163]

[0164]

[0165]

[0166]

[0167]

[0168] In Table 8, the signaling information CSI-ReportConfig can contain information about each report setting. The information included in the signaling information CSI-ReportConfig can have the following meanings. This is not limited to the following examples:

[0169] -reportConfigId: Report settings index;

[0170] -carrier: Serving cell index;

[0171] -resourcesForChannelMeasurement: Index of resource settings for channel measurements related to report settings;

[0172] -csi-IM-ResourcesForInterference: Index of resource settings with CSI-IM resources for interference measurements associated with the reporting settings;

[0173] -nzp-CSI-RS-ResourcesForInterference: An index of resource settings with CSI-RS resources for interference measurements associated with the reporting settings;

[0174] -reportConfigType: This can indicate the timeline transmission configuration and transmission channel used for channel reporting, and can be configured with non-periodic transmission, semi-persistent physical uplink control channel (PUCCH) transmission, semi-persistent PUSCH transmission, or periodic transmission.

[0175] -reportQuantity: Indicates the type of channel information reported, and may include channel information types ("cri-RI-PMI-CQI", "cri-RI-i1", "cri-RI-i1-CQI", "cri-RI-CQI", "cri-RSRP", "ssb-Index-RSRP", and "cri-RI-LI-PMI-CQI") when no channel report is transmitted and when a channel report is transmitted. Here, the elements included in the channel information type are Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), CSI-RS Resource Indicator (CRI), SS / PBCH Block Resource Indicator (SSBRI), Layer Indicator (LI), Rank Indicator (RI), and / or Reference Signal Received Power (L1-RSRP).

[0176] -reportFreqConfiguration: can indicate whether the reported channel information includes only information about the entire bandwidth (wideband), or whether it can include information about each subband, and if the reported channel information includes information about each subband, then it has configuration information for the subbands that include channel information;

[0177] -timeRestrictionForChannelMeasurements: The time axis restriction of the reference signal used for channel measurements in the reference signal cited in the reported channel information;

[0178] -timeRestrictionForInferenceMeasurements: The time axis restriction of the reference signal used for interference measurements in the reference signal cited in the reported channel information;

[0179] -codebookConfig: The codebook information referenced by the reported channel information;

[0180] -groupBasedBeamReporting: Beam grouping for channel reporting;

[0181] -cqi-Table: The CQI table index referenced by the reported channel information;

[0182] -subbandSize: An index indicating the size of the channel information subband; and / or

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

[0184] When the base station instructs the channel information report via higher-layer signaling or L1 signaling, the UE can refer to the configuration information included in the instructive report settings to perform the channel information report.

[0185] The base station can indicate Channel State Information (CSI) reports to the UE via higher-layer signaling (including Radio Resource Control (RRC) signaling, Media Access Control (MAC) Control Element (CE) signaling, or L1 signaling (e.g., common DCI, group common DCI, or UE-specific DCI)).

[0186] For example, a base station can indicate aperiodic channel information reporting to a UE via higher-layer signaling or DCI using DCI format 0_1. The base station can configure multiple CSI report trigger states, including parameters for aperiodic CSI reporting by the UE or parameters for CSI reporting via higher-layer signaling. Parameters for CSI reporting or CSI report trigger states can include at least one of the following: the time slot interval or a set of available time slot intervals between the PDCCH including DCI and the PUSCH including CSI reporting, a reference signal ID for channel state measurement, and the type of channel information included in the CSI report. When the base station indicates some of the multiple CSI report trigger states to the UE via DCI, the UE can report channel information according to the CSI report configuration set according to the report settings configured with the indicated CSI report trigger states. Channel information reporting can be performed via PUSCH scheduled in DCI format 0_1. The time axis resource allocation of the PUSCH containing the UE's CSI report can be accomplished via at least one of the following: the time slot interval of the PDCCH indicated by the DCI, or the start symbol and symbol length indication within the time slot using the time axis resource allocation of the PUSCH. For example, the location of the time slot in which the PUSCH containing the UE's CSI report is transmitted can be indicated by the time slot interval starting from the PDCCH indicated by the DCI, while the start symbol and symbol length within the time slot can be indicated by the time domain resource assignment field of the aforementioned DCI.

[0187] For example, the base station can instruct the UE to transmit semi-persistent CSI reports to the PUSCH via DCI using DCI format 0_1. The base station can activate or deactivate semi-persistent CSI reports transmitted to the PUSCH via DCI scrambled with SP-CSI-RNTI. When semi-persistent CSI reporting is activated, the UE can periodically report channel information according to the configured time slot interval. When semi-persistent CSI reporting is deactivated, the UE can stop the activated periodic channel information reporting. The base station can configure multiple CSI report trigger states, including parameters for semi-persistent CSI reporting for the UE or parameters for semi-persistent CSI reporting via higher-layer signaling. The parameters used for CSI reporting or CSI reporting triggering status may include at least one of the following: the time slot interval between the PDCCH (including DCI) indicating CSI reporting and the PUSCH including CSI reporting, or a set of available time slot intervals, the time slot interval between the time slot indicating that higher-layer signaling for CSI reporting is activated and the PUSCH including CSI reporting, the time slot interval period for CSI reporting, and the type of channel information included in the CSI report.

[0188] When a base station activates some or more reporting settings in multiple CSI report trigger states in a UE via higher-layer signaling or DCI, the UE can report channel information according to the reporting settings included in the indicated CSI report trigger state or the CSI report configuration configured in the activated reporting settings. Channel information reporting can be performed via semi-persistently scheduled PUSCH in DCI format 0_1 ​​scrambled with line SP-CSI-RNTI. The time-axis resource allocation of the PUSCH including the UE's CSI report can be implemented through at least one of the following: the slot interval period of the CSI report, the slot interval of the slot in which higher-layer signaling is activated or the slot interval of the PDCCH indicated by DCI, the start symbol within the slot of the PUSCH time-axis resource allocation, and the symbol length indication. For example, the position of the slot in which the PUSCH including the UE's CSI report is transmitted can be indicated by the slot interval of the PDCCH indicated by DCI. The start symbol and symbol length within the slot can be indicated by the time-domain resource assignment field of DCI format 0_1.

[0189] For example, a base station can instruct a UE to transmit semi-persistent CSI reports to the PUCCH via higher-layer signaling (such as MAC-CE). MAC-CE signaling allows the base station to activate or deactivate semi-persistent CSI reports transmitted to the PUCCH. When semi-persistent CSI reporting is activated, the UE can periodically report channel information according to a configured timeslot interval. When semi-persistent channel state information reporting is deactivated, the UE can stop reporting the activated periodic channel information. The base station can configure parameters for the UE's semi-persistent CSI reports via higher-layer signaling. CSI report parameters can include at least one of the following: the PUCCH resources on which the CSI reports are transmitted, the timeslot interval frequency of the CSI reports, or the type of channel information included in the CSI reports. The UE can transmit CSI reports via the PUCCH. Alternatively, if the PUCCH for CSI reporting overlaps with the PUSCH, the UE can transmit CSI reports via the PUSCH. The location of the PUCCH transmission slot containing the CSI report can be indicated by the slot interval period of the CSI report configured via higher-layer signaling, and / or by the slot interval between the slot in which the higher-layer signaling is activated and the PUCCH containing the CSI report. The start symbol and symbol length within the slot can be indicated by the start symbol and symbol length to be allocated to the PUCCH resource configured via higher-layer signaling.

[0190] For example, a base station can instruct a UE to periodically report CSI information via higher-layer signaling. The base station can activate or deactivate periodic CSI reporting via higher-layer signaling, including RRC signaling. When periodic CSI reporting is activated, the UE can periodically report channel information according to a configured time slot interval. When periodic CSI reporting is deactivated, the UE can stop the activated periodic channel information reporting. The base station can configure reporting settings via higher-layer signaling, which includes parameters for the UE's periodic CSI reporting. CSI reporting parameters can include at least one of the following: the PUCCH resource configuration for CSI reporting, the time slot interval between the time slot in which the higher-layer signaling indicating CSI reporting activation is activated and the PUCCH including the CSI report, the time slot interval period for CSI reporting, the reference signal ID for channel state measurement, or the type of channel information included in the CSI report. The UE can transmit CSI reports via PUCCH.

[0191] Alternatively, if the CSI report's PUCCH overlaps with the PUSCH, the UE can transmit the CSI report via the PUSCH. The location of the time slot in which the PUCCH including the CSI report is transmitted can be indicated by the time slot interval period of the CSI report configured via higher-layer signaling and the time slot interval between the time slot in which the higher-layer signaling is activated and the PUCCH including the CSI report. The start symbol and symbol length within the time slot can be indicated by the start symbol and symbol length to be allocated to the PUCCH resources configured via higher-layer signaling.

[0192] Regarding the aforementioned CSI report settings (CSI-ReportConfig), each report setting (CSI-ReportConfig) can be associated with a corresponding CSI resource setting and with a downlink (DL) BWP identified by the bandwidth portion identifier (bwp-id) given by the higher-layer parameter CSI-ResourceConfig. The time-domain reporting operation for each report setting (CSI-ReportConfig) can support "aperiodic," "semi-persistent," or "periodic" schemes, and the reporting method can be configured for the UE from the base station via the reportConfigType parameter configured by the higher layers. The semi-persistent CSI reporting method supports both "semi-persistentOnPUCCH based" and "semi-persistentOnPUSCH based" reporting methods. In the case of periodic or semi-persistent CSI reporting methods, the UE can transmit CSI from the base station configured with PUCCH or PUSCH resources via higher-layer signaling. The periodicity and slot offset of CSI transmission via PUCCH or PUSCH resources can be given by the set of parameters configured for the uplink (UL) BWP used to transmit CSI reports. In the case of a non-periodic CSI reporting method, the UE can receive the scheduling of PUSCH resources from the base station via L1 signaling (DCI format 0_1 ​​as described above) to transmit CSI.

[0193] Regarding CSI resource settings (CSI-ResourceConfig), each CSI resource setting (CSI-ReportConfig) can include S (≥1) CSI resource sets (given by the higher-layer parameter csi-RS-ResourceSetList). The list of CSI resource sets can be configured via non-zero power (NZP) CSI-RS resource sets and SS / PBCH block sets, or via CSI interference measurement (CSI-IM) resource sets. Each CSI resource setting can reside on a downlink (DL) BWP identified by the higher-layer parameter bwp-id, and CSI resource settings can be associated with CSI reporting settings on the same DL BWP. The time-domain operation of the CSI-RS resources within a CSI resource setting can be configured as "aperiodic," "periodic," or "semi-persistent" via the higher-layer parameter resourceType. For periodic or semi-persistent CSI resource settings, the number of CSI-RS resource sets can be limited to S=1, and the configured periodicity and slot offset can be given by the parameter set of the DL BWP identified by bwp-id.

[0194] The UE can configure one or more CSI resource settings from the base station via higher-layer signaling for channel or interference measurement, and for example, the CSI resource settings configured by the base station may include the following CSI resources:

[0195] CSI-IM resources for interference measurement;

[0196] - NZP CSI-RS resources for interference measurements; and / or

[0197] - NZP CSI-RS resources for channel measurements.

[0198] For a CSI-RS resource set associated with a resource setting configured as “aperiodic,” “periodic,” or “semi-persistent” via the higher-level parameter resourceType, the trigger state for the CSI report setting (where reportType is configured as “aperiodic”) and the resource settings for channel or interference measurements for one or more component cells (CCs) can be configured via the higher-level parameter CSI-AperiodicTriggerStateList.

[0199] Aperiodic CSI reporting by the UE can be performed using PUSCH. Periodic CSI reporting by the UE can be performed using PUCCH. If semi-persistent CSI reporting is triggered or activated by DCI, semi-persistent CSI reporting by the UE can be performed using PUSCH, and after semi-persistent CSI reporting is activated by the MAC control element (CE), semi-persistent CSI reporting by the UE can be performed using PUCCH. As mentioned above, CSI resource settings can also be configured as "aperiodic," "periodic," or "semi-persistent." Combinations of CSI reporting settings and CSI resource settings can be supported based on Table 9 below, but are not limited to these.

[0200] [Table 9]

[0201] Table 5.2.1.4-1: Triggering / activating CSI reports for possible CSI-RS configurations.

[0202]

[0203] Aperiodic CSI reports can be triggered by the "CSI Request" field of the aforementioned DCI format 0_1, corresponding to the scheduling DCI for PUSCH. The UE can listen to the PDCCH, obtain DCI format 0_1, and obtain scheduling information regarding the PUSCH and CSI request indicator. The CSI request indicator can be configured using NTS (=0, 1, 2, 3, 4, 5, or 6) bits and can be determined via higher-layer signaling (reportTriggerSize). The CSI request indicator can trigger one of one or more aperiodic CSI report trigger states that can be configured via higher-layer signaling (CSI-AperiodicTriggerStateList). Of course, this is not limited to the following examples.

[0204] - When all bits of the CSI request field are 0, this indicates that no CSI report has been requested.

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

[0206] - If the number (M) of CSI trigger states in the configured CSI-AperiodicTriggerStateLite is equal to or less than 2NTs-1, the CSI Request field can indicate one of the M CSI trigger states.

[0207] Table 10 below shows an example of the relationship between a CSI request indicator and the CSI triggering state indicated by that indicator. Of course, this is not limited to the following example.

[0208] [Table 10]

[0209]

[0210] The UE can perform measurements on CSI resources in a CSI-triggered state triggered by the CSI request field, and can generate CSIs (including at least one of CQI, PMI, CRI, SSBRI, LI, RI, or L1-RSRP) based on the measurement results. The UE can transmit the acquired CSI using a PUSCH scheduled by the corresponding DCI format 0_1. When a bit in DCI format 0_1 ​​corresponding to the uplink (UL) data indicator (UL-SCH indicator) is "1", the UE can multiplex the UL data (UL-SCH) and the acquired CSI with the PUSCH resource scheduled by DCI format 0_1 ​​and can transmit it. When a bit in DCI format 0_1 ​​corresponding to the UL data indicator (UL-SCH indicator) is "0", the UE can map only the CSI without UL data (UL-SCH) to the PUSCH resource scheduled by DCI format 0_1 ​​and can transmit it.

[0211] Figure 5 An example of a non-periodic CSI reporting method according to an embodiment of the present disclosure is shown.

[0212] refer to Figure 5 In one example (indicated by reference numeral 500), the UE can obtain DCI format 0_1 ​​by listening to PDCCH 501, and can obtain scheduling information and CSI request information about PUSCH 505 from DCI format 0_1. The UE can obtain resource information about the CSI-RS 502 to be measured from the received CSI request indicator. Based on the reception time of DCI format 0_1 ​​and the parameter (aperiodicTriggeringOffset mentioned above) regarding the offset within the CSI resource set configuration (e.g., NZP CSI-RS resource set configuration (NZP-CSI-RS-ResourceSet)), the UE can determine that the measurement of CSI-RS 502 transmitted at a predetermined time can be performed. More specifically, the UE can configure the offset value X of the parameter aperiodicTriggeringOffset in the NZP-CSI-RS resource set configuration from the base station via higher-layer signaling. The configured offset value X can indicate the offset between the time slot in which DCI is received to trigger an aperiodic CSI report and the time slot in which CSI-RS resources are to be sent. For example, the parameter value of aperiodicTriggeringOffset and the offset value X can have a mapping relationship as described in Table 11 below. Of course, this is not limited to the following examples.

[0213] [Table 11]

[0214]

[0215] exist Figure 5 In Example 500, the aforementioned offset value is configured as X=0. In this case, the UE can receive the DCI format 0_1 ​​slot (corresponding to) that triggers an aperiodic CSI report. Figure 5 The UE receives CSI-RS 502 in time slot 0 (506) of the PUSCH 505. Additionally, the UE can report CSI information to the base station via PUSCH 505, which is measured using the received CSI-RS. The UE can obtain scheduling information (multiple pieces of information corresponding to fields in DCI format 0_1) about the PUSCH 505 used for CSI reporting from DCI format 0_1. For example, the UE can obtain information about the time slot in which the PUSCH 505 is transmitted from the time-domain resource allocation information in DCI format 0_1 ​​about the PUSCH 505. Figure 5 In Example 500, the UE can obtain a K2 value of 3 as the time slot offset value from PDCCH to PUSCH. Therefore, PUSCH 505 can be transmitted in time slot 3 509, which is 3 time slots away from the time point in which PDCCH 501 is received (e.g., in time slot 0 506).

[0216] exist Figure 5 In Example 510, the UE can obtain DCI format 0_1 ​​by listening to PDCCH 511, and can obtain scheduling information and CSI request information about PUSCH 515 from DCI format 0_1. The UE can obtain resource information about the CSI-RS 512 to be measured from the received CSI request indicator. Figure 5 In Example 510, the aforementioned offset value for CSI-RS is configured as X=1. In this case, the UE can receive the DCI format 0_1 ​​slot that triggers an aperiodic CSI report ( Figure 5 The CSI-RS 512 is received in time slot 0 (516), and the CSI information measured by using the received CSI-RS can be reported to the base station via PUSCH 515.

[0217] Aperiodic CSI reports may include at least one of CSI Part 1 or CSI Part 2, or both. If an aperiodic CSI report is to be transmitted via PUSCH, it can be multiplexed with a transport block. For multiplexing, a CRC can be inserted into the input bits of the aperiodic CSI, and it can be encoded and rate-matched. The input bits can then be mapped to resource elements in the PUSCH according to a specific pattern and transmitted. Depending on the encoding method or the length of the input bits, the CRC insertion may be omitted. The number of modulation symbols required for rate matching in the multiplexing of CSI Part 1 or CSI Part 2 included in the aperiodic CSI report can be calculated according to Table 12 below. Of course, this is not limited to the examples below.

[0218] [Table 12]

[0219]

[0220]

[0221]

[0222] Specifically, in the cases of PUSCH repetition types A and B, the UE can multiplex the aperiodic CSI report and transmit it only in the first repetition of the PUSCH repetition transmission. According to the above transmission method, the aperiodic CSI report information to be multiplexed is encoded using a polar code scheme, and here, in order to multiplex the aperiodic CSI report information in multiple PUSCH repetitions, each PUSCH repetition can have the same frequency and time resource allocation. Specifically, in the case of PUSCH repetition type B, each actual repetition can have a different OFDM symbol length, and therefore, the aperiodic CSI report can be multiplexed and transmitted only in the first PUSCH repetition.

[0223] Additionally, for PUSCH repetition type B, when the UE receives a DCI to schedule an aperiodic CSI report or activates a semi-persistent CSI report without scheduling a transport block, the UE can set the nominal repetition value to 1 even if the number of PUSCH repetitions configured by higher-layer signaling is greater than 1. Furthermore, when the UE schedules or activates an aperiodic or semi-persistent CSI report without scheduling a transport block based on PUSCH repetition type B, the UE can expect the first nominal repetition to be the same as the first actual repetition. For PUSCHs transmitted based on PUSCH repetition type B after a semi-persistent CSI report is activated by the DCI, including semi-persistent CSI, without invoking the DCI, if the first nominal repetition is different from the first actual repetition, the transmission of the first nominal repetition can be ignored.

[0224] [CSI Calculation Time]

[0225] When a base station indicates a non-periodic CSI report or a semi-persistent CSI report to a UE via a DCI, it can be determined that the UE can execute a valid channel report based on the channel calculation time (CSI calculation time) required for the CSI report. For a non-periodic or semi-persistent CSI reports indicated via a DCI, the UE can execute a valid CSI report from the uplink symbols following the last Z symbols in the PDCCH that includes the DCI indicating the CSI report. These Z symbols may vary depending on the downlink BWP parameter set (corresponding to the PDCCH that includes the DCI indicating the CSI report), the uplink BWP parameter set (corresponding to the PUSCH that transmits the CSI report), and the type or characteristics of the channel information reported by the CSI report (e.g., number of reports, band granularity, number of ports of the reference signal, and codebook type).

[0226] In other words, it can be understood that, in order to determine whether a CSI report is valid (for a CSI report to be valid), the execution of the uplink transmission of the CSI report must not be earlier than symbol Zref (including timing advance). Here, symbol Zref can be an uplink symbol, which is the time elapsed since the end of the last symbol that triggered the PDCCH. Then the cyclic prefix (CP) begins. The detailed values ​​for Z are described below, and... , , , and It can be a set of parameters. In this case... It can be set to generate The largest The value, Indicates the subcarrier spacing used for PDCCH transmission. This indicates the subcarrier spacing used for CSI-RS transmission, and This indicates the subcarrier spacing of the uplink channel used for uplink control information (UCI) transmission in CSI reports. In one example, It can be set to generate The largest in The value of . and The definition is as described above. For ease of subsequent description, meeting the above conditions can be referred to as meeting CSI report validity condition 1.

[0227] When the channel measurement reference signal of the aperiodic CSI report indicated to the UE via the DCI is an aperiodic reference signal, the UE can perform a valid CSI report from the uplink symbols following Z' symbols from the end of the last symbol of the reference signal, and the Z' symbols may vary depending on the following: the parameter set of the downlink BWP corresponding to the PDCCH that includes the DCI indicating the CSI report, the parameter set of the BWP corresponding to the channel measurement reference signal of the CSI report, the parameters of the uplink BWP corresponding to the PUSCH that transmits the CSI report, and the type or characteristics of the channel information reported by the CSI report (e.g., number of reports, band granularity, number of ports of the reference signal, or codebook type).

[0228] In other words, to determine which CSI report is valid (for the corresponding CSI report to be considered valid), the execution of the uplink transmission for the corresponding CSI report must not be earlier than the symbol Zref plus a timing advance. Here, the symbol Zref can be an uplink symbol, which is the time elapsed since the end of the last symbol of the aperiodic CSI-RS or aperiodic CSI-IM triggered by the PDCCH. Then the cyclic prefix (CP) begins. In this case, the detailed values ​​of Z' are as follows, and , , , and It can be a set of parameters. In this case... It can be set to generate The largest The value, Indicates the subcarrier spacing used for PDCCH transmission. This indicates the subcarrier spacing used for CSI-RS transmission, and This indicates the subcarrier spacing of the uplink channel used for uplink control information (UCI) transmission in CSI reports. In one example, It can be set to generate The largest in The value of . and The definition is as described above. For ease of subsequent description, meeting the above conditions can be considered as meeting CSI report validity condition 2.

[0229] When a base station indicates an aperiodic CSI report based on an aperiodic reference signal to a UE via DCI, the UE can execute a valid CSI report from the first uplink symbol that satisfies both of the following: a time point Z symbols after the end of the last symbol included in the PDCCH indicating the CSI report, and a time point Z' symbols after the end of the last symbol of the reference signal. For example, an aperiodic CSI report based on an aperiodic reference signal can only be determined as a valid CSI report if CSI report validity conditions 1 and 2 are met.

[0230] When the CSI report time point indicated by the base station does not meet the CSI calculation time requirement, the UE can determine that the CSI report that does not meet the CSI calculation time requirement is invalid and may not consider updating the channel information status of the CSI report.

[0231] The Z symbols and Z' symbols used to calculate the CSI calculation time can be shown in Tables 13 and 14 below. For example, when the channel information reported by the CSI report only includes wideband information, the number of reference signal ports is equal to or less than 4, the number of reference signal resources is 1, and the codebook type is "typeI-SinglePanel" or the reported channel information type (report quantity) is "cri-RI-CQI", the Z symbols and Z' symbols follow the values ​​of Z1 and Z1' in Table 14. The above condition can be referred to as delay requirement 2. In addition, when the PUSCH including the CSI report does not include TB or HARQ-ACK and the UE's CPU utilization rate is 0, the Z symbols and Z' symbols follow the values ​​of Z1 and Z1' in Table 13. The above condition can be referred to as delay requirement 1. The above CPU utilization rate can be explained in more detail below. In addition, when the report quantity is "cri-RSRP" or "ssb-Index-RSRP", the Z symbols and Z' symbols can follow the values ​​of Z3 and Z3' in Table 14. X1, X2, X3, and X4 in Table 14 indicate the UE's beam reporting time capability, and KB1 and KB2 in Table 14 indicate the UE's beam switching time capability. If they do not correspond to the type or characteristics of channel information reported by the CSI report, then Z symbols and Z' symbols may follow Z2 and Z2' in Table 14. Of course, this is not limited to the following examples.

[0232] [Table 13]

[0233]

[0234] [Table 14]

[0235]

[0236] [CSI Reference Resources]

[0237] When instructing a non-periodic / semi-persistent / periodic CSI report to the UE, the base station can configure CSI reference resources to determine the reference time and frequency of the channel to be reported in the CSI report. The frequency of the CSI reference resource can be information about the carrier and the subband for which CSI is to be measured, as indicated in the CSI report configuration. Information about the carrier and subband used to measure CSI can correspond to the carrier and reportFreqConfiguration in the higher-layer signaling CSI-ReportConfig, respectively. The time of the CSI reference resource can be defined based on the transmission time of the CSI report. For example, when CSI report #X is transmitted in the uplink slot n' of the carrier and BWP in which CSI is transmitted, the CSI reference resource time for CSI report #X can be defined as the downlink slot n-nCSI-ref of the carrier and BWP in which CSI is measured. When the parameter set of the carrier and BWP for measuring CSI is referred to as μDL and the parameter set of the carrier and BWP for transmitting CSI report #X is referred to as μUL, the downlink slot n is calculated as... .

[0238] If the CSI report #X transmitted in uplink time slot n' is a semi-persistent or periodic CSI report, then depending on the number of CSI-RS / SSB resources used for channel measurements, if a single CSI-RS / SSB resource is connected to the corresponding CSI report, then nCSI-ref (which is the time slot interval between downlink time slot n and the CSI reference resource) can follow... If multiple CSI-RS / SSB resources are connected to CSI reporting, then... When the CSI report #X transmitted in uplink time slot n' is an aperiodic CSI report, the CSI calculation time Z' based on channel measurements is used to calculate... The above. It is the number of symbols included in a time slot, and it can be assumed that in NR... .

[0239] When a base station instructs a UE to transmit any CSI report in uplink time slot n' via higher-layer signaling or DCI, the UE can report the CSI by performing channel measurements or interference measurements on the CSI-RS, CSI-IM, or SSB resources associated with the CSI report to be transmitted by the base station, provided that the transmission time is no later than the CSI reference resource slot in uplink time slot n'. The CSI-RS, CSI-IM, or SSB resources associated with the CSI report instructing the base station to transmit can be CSI-RS, CSI-IM, or SSB resources included in a resource set configured in resource settings referenced by the UE's CSI report reporting settings configured via higher-layer signaling. Alternatively, the CSI-RS resource, CSI-IM resource, or SSB resource associated with the CSI report to be transmitted as indicated by the base station may indicate the CSI-RS resource, CSI-IM resource, or SSB resource referenced by the CSI report triggering state (including parameters of the CSI report), or the CSI-RS resource, CSI-IM resource, or SSB resource indicated by the ID of the reference signal (RS) set.

[0240] In some embodiments of this disclosure, the CSI-RS / CSI-IM / SSB timing can indicate the time point for transmission of CSI-RS / CSI-IM / SSB resources determined by higher-layer configuration or a combination of higher-layer configuration and DCI triggering. For example, with respect to semi-persistent or periodic CSI-RS resources, time slots for transmission based on time slot periods and time slot offsets configured via higher-layer signaling can be determined, and the transmission symbols(s) within the time slots can be determined based on resource mapping information. In one example, with respect to aperiodic CSI-RS resources, time slots for transmission via PDCCHs including DCIs indicating channel reporting configured via higher-layer signaling can be determined based on time slot offsets, and the transmission symbols(s) within the time slots can be determined based on resource mapping information.

[0241] The CSI-RS timing described above can be determined by independently considering the time point of transmission for each CSI-RS resource, or by comprehensively considering the time points of transmission for one or more CSI-RS resources included in the resource set. According to the above method, for CSI-RS timing, there are two possible interpretations depending on the configuration of each resource set. This is not limited to the following examples:

[0242] - Explanation 1-1: From the start of the earliest symbol to the end of the latest symbol, in that latest symbol, the transmission includes a specific resource from one or more CSI-RS resources included in the resource(s) set configured in the resource settings referenced by the resource settings configured for the CSI report, and

[0243] - Explanation 1-2: From the starting point of the earliest symbol to the ending point of the latest symbol, in the earliest symbol, CSI-RS resources transmitted at the earliest time point are transmitted, and in the latest symbol, CSI-RS resources transmitted at the latest time point are transmitted from all CSI-RS resources included in the resource set(s) configured in the resource settings referenced by the resource settings configured for the CSI report.

[0244] In the embodiments of this disclosure, both interpretations of the CSI-RS timing can be considered separately. Additionally, similar to the CSI-RS timing, both interpretations can be considered for the CSI-IM and SSB timings, but the principle is similar to the above description, and therefore redundant descriptions are omitted below.

[0245] In embodiments of this disclosure, the "CSI-RS / CSI-IM / SSB timing" of CSI report #X transmitted in "uplink slot n" can refer to the set of CSI-RS timing, CSI-IM timing, and SSB timing of CSI-RS resources, CSI-IM resources, and SSB resources included in the resource set configured in the resource settings referenced by the report settings configured for CSI report #X, which is no later than at least one of the CSI-RS timing, CSI-IM timing, and SSB timing of the CSI reference resource of CSI report #X transmitted in uplink slot n'.

[0246] In embodiments of this disclosure, the "latest CSI-RS / CSI-IM / SSB timing" in the CSI report #X transmitted in "uplink slot n" can be interpreted in two ways. Of course, this is not limited to the examples below.

[0247] - Explanation 2-1: A set of timings including the latest CSI-RS timing of CSI report #X transmitted in uplink time slot n', the latest CSI-RS timing of CSI report #X transmitted in uplink time slot n', and the latest SSB timing of CSI report #0 transmitted in uplink time slot n'.

[0248] - Explanation 2-2: The latest timing among all CSI-RS timings, CSI-IM timings, and SSB timings transmitted in uplink time slot n' of CSI report #X.

[0249] In embodiments of this disclosure, the "latest CSI-RS / CSI-IM / SSB timing" of the CSI report #X transmitted in "uplink slot n" can be applied individually based on two interpretations of the "latest CSI-RS / CSI-IM / SSB timing". When considering the two interpretations (interpretation 1-1 and interpretation 1-2) of the CSI-RS timing, CSI-IM timing, and SSB timing, in embodiments of this disclosure, the "latest CSI-RS / CSI-IM / SSB timing" of the CSI report #X transmitted in "uplink slot n" can be applied individually based on all four different interpretations (application of interpretation 1-1 and interpretation 2-1, application of interpretation 1-1 and interpretation 2-2, application of interpretation 1-2 and interpretation 2-1, and application of interpretation 1-2 and interpretation 2-2).

[0250] The base station can instruct the CSI report based on the amount of channel information the UE can simultaneously calculate for the CSI report (e.g., the number of channel information calculation units (CSI processing units (CPUs)) of the UE). When the number of channel information calculation units the UE can simultaneously calculate is... At that time, the UE may not expect the CSI report indication to the base station to need to be greater than The calculation of channel information may not consider the need for greater than Channel information is updated based on channel information calculation. The UE can report to the base station via higher-layer signaling, or the base station can configure it via higher-layer signaling.

[0251] It can be assumed that the CSI reports indicated by the base station to the UE occupy the total number of calculations that the UE can perform simultaneously. Some or all of the CPUs in a channel information segment are used for channel information calculation. For example, when each CSI report (e.g., CSI report) is processed... The number of channel information calculation units required is At that time, the number of channel information calculation units required for a total of N CSI reports can be... The channel information calculation units required for each reportQuantity configured in the CSI report can be configured as shown in Table 15 below. Of course, this is not limited to the examples below.

[0252] [Table 15]

[0253]

[0254] When the number of times the UE calculates the channel information required for multiple CSI reports at a specific time point exceeds the number of channel information calculation units that the UE can calculate simultaneously. In some cases, the UE may not consider updating the channel information in some CSI reports. Among multiple indicated CSI reports, the CSI report that does not consider updating channel information can be determined by considering the CPU time spent calculating at least the channel information required for the CSI report and the priority of the reported channel information. For example, updating the channel information in the CSI report from the latest CPU time point for calculating the channel information required for the CSI report may not be considered, and for CSI reports with low channel information priority, updating the channel information may not be prioritized.

[0255] The priority of channel information can be determined with reference to Table 16. Of course, this is not limited to the following examples.

[0256] [Table 16]

[0257]

[0258] CSI reports are prioritized using the priority values ​​Pri in Table 16. iCSI (y,k,c,s) is used to determine the priority value. Referring to Table 16, the CSI priority value can be determined by at least one of the following: the type of channel information included in the CSI report, the timeline reporting characteristics of the CSI report (aperiodic, semi-persistent, periodic), the channel through which the CSI report is transmitted (PUSCH or PUCCH), the serving cell index, or the CSI report configuration index. Regarding the CSI priority of the CSI report, the priority values ​​Pri are compared. iCSI (y,k,c,s), and it can be determined that CSI reports with smaller priority values ​​have higher CSI priority.

[0259] When the time taken by the CPU to calculate the channel information required for the CSI report indicated by the base station to the UE is called the CPU occupancy time, the CPU occupancy time can be determined by considering at least one of all of the following: the type of channel information included in the CSI report (number of reports), the time axis characteristics of the CSI report (aperiodic, semi-persistent, periodic), the time slots or symbols occupied by the higher-layer signaling or DCI indicating the CSI report, and the time slots or symbols occupied by the reference signal used for channel state measurement.

[0260] [PDCCH: About DCI]

[0261] Next, we will describe downlink control information (DCI) in a 5G communication system in detail.

[0262] In 5G systems, scheduling information for uplink data (or Physical Uplink Shared Channel (PUSCH)) or downlink data (or Physical Downlink Shared Channel (PDSCH)) can be transmitted from the base station to the UE via DCI. The UE can listen for both backoff DCI format and non-backoff DCI format for either PUSCH or PDSCH. The backoff DCI format may include predefined fixed fields between the base station and the UE, while the non-backoff DCI format may include configurable fields.

[0263] DCI messages undergo channel coding and modulation processing before being transmitted via or on the Physical Downlink Control Channel (PDCCH). Cyclic Redundancy Check (CRC) can be appended to the payload of the DCI message, and the CRC can be scrambled by a Radio Network Temporary Identifier (RNTI) corresponding to the UE's identifier. Different RNTIs can be used depending on the purpose of the DCI message, such as IE-specific data transmission, power control commands, or random access responses. That is, the RNTI may not be explicitly sent, but can be transmitted concurrently with the CRC calculation process. When a UE receives a DCI message transmitted via the PDCCH, the UE can identify the CRC using the assigned RNTI, and if the CRC identification result is correct, the UE knows that the corresponding message has been sent.

[0264] For example, the DCI used for scheduling PDSCH about System Information (SI) can be scrambled with SI-RNTI. The DCI used for scheduling PDSCH about Random Access Response (RAR) messages can be scrambled with RA-RNTI. The DCI used for scheduling PDSCH about paging messages can be scrambled with P-RNTI. The DCI used for notifying Slot Format Indicator (SFI) can be scrambled with SFI-RNTI. The DCI used for notifying Transmission Power Control (TPC) can be scrambled with TPC-RNTI. The DCI used for scheduling UE-specific PDSCH or PUSCH can be scrambled with Cell RNTI (C-RNTI).

[0265] DCI format 0_0 can be used as a fallback DCI for scheduling PUSCH, and in this case, the CRC can be scrambled by C-RNTI. DCI format 0_0 (where the CRC is scrambled by C-RNTI) can include, for example, the following information given in Table 17 below. Obviously, the examples given below are not limiting.

[0266] [Table 17]

[0267]

[0268] DCI format 0_1 ​​can be used as a non-back-off DCI for scheduling PUSCH, and in this case, the CRC can be scrambled by C-RNTI. DCI format 0_1 ​​(where the CRC is scrambled by C-RNTI) can include, for example, the following information given in Table 18 below. Obviously, the examples given below are not limiting.

[0269] [Table 18]

[0270]

[0271]

[0272] DCI format 1_0 can be used as a fallback DCI for scheduling PDSCH, and in this case, the CRC can be scrambled by C-RNTI. DCI format 1_0 (where the CRC is scrambled by C-RNTI) can include, for example, the following information given in Table 19 below. Obviously, the examples given below are not limiting.

[0273] [Table 19]

[0274]

[0275] DCI format 1_1 can be used as a non-back-off DCI for scheduling PDSCH, and in this case, the CRC can be scrambled by C-RNTI. DCI format 1_1 (where the CRC is scrambled by C-RNTI) can include, for example, the following information given in Table 20 below. Obviously, the examples given below are not limiting.

[0276] [Table 20]

[0277]

[0278]

[0279] [PDCCH: CORESET, REG, CCE, and Search Space]

[0280] The downlink control channel in a 5G communication system will be described in more detail below with reference to the accompanying drawings.

[0281] Figure 6 An example of the configuration of a control resource set (CORESET) for transmitting a downlink control channel in a wireless communication system, according to an embodiment of the present disclosure, is shown. Figure 6An example is shown where the UE bandwidth portion 610 is configured along the frequency axis and two control resource sets (control resource set #1 601 and control resource set #2 602) are configured along the time axis within a time slot 620. Control resource sets 601 and 602 can be configured within a specific frequency resource 603 along the frequency axis throughout the entire UE bandwidth portion 610. One or more OFDM symbols can be configured along the time axis, and this can be defined as the control resource set duration 604. Reference Figure 6 In the example shown, control resource set #1 601 is configured to have control resource set durations corresponding to two symbols, while control resource set #2 602 is configured to have control resource set durations corresponding to one symbol.

[0282] The control resource set in 5G described above can be configured for the UE by the base station via upper-layer signaling (e.g., system information, master information block (MIB), radio resource control (RRC) signaling). The description of configuring the control resource set for the UE provides information such as the control resource set identifier, the frequency location of the control resource set, and the symbol duration of the control resource set. For example, this configuration information may include several pieces of information given in Table 21.

[0283] [Table 21]

[0284]

[0285]

[0286] In Table 21, the tci-StatesPDCCH (Transmission Configuration Indication (TCI) status) configuration information may include information on one or more SS / PBCH block indices or Channel State Information Reference Signal (CSI-RS) indices, which are associated with the DMRS quasi-co-location (QCL) transmitted in the corresponding control resource set. Clearly, the examples given above are not restrictive.

[0287] Figure 7 The structure of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure is shown.

[0288] refer to Figure 7 , Figure 7 An example of the basic time and frequency resource units constituting the downlink control channel available in a 5G system is shown. According to... Figure 7The basic unit of time and frequency resources constituting the control channel can be called a resource element group (REG) 703, and REG 703 can be defined by an OFDM symbol 701 along the time axis and a physical resource block (PRB) 702 along the frequency axis (that is, 12 subcarriers). The base station can configure the downlink control channel allocation unit by cascading REG 703.

[0289] Assuming the basic unit of downlink control channel allocation in 5G is as follows: Figure 7 The control channel element 704 shown can be a single CCE 704 that may include multiple REG 703s. For example, to describe Figure 7 The REG 703 shown can include 12 REs, and if a CCE 704 includes six REG 703s, then a CCE 704 can include 72 REs. Once configured, a downlink control resource set can include multiple CCE 704s, and a specific downlink control channel can be mapped to one or more CCE 704s and then transmitted according to the aggregation level (AL) in the control resource set. CCE 704s in the control resource set are distinguished by numbering, and the CCE 704 numbers can be assigned according to a logical mapping scheme.

[0290] Figure 7 The basic unit of the downlink control channel shown (i.e., REG 703) may include the RE to which the DCI is to be mapped, and the region to which the reference signal (DMRS 705) for decoding the DCI is to be mapped. Figure 7 In this configuration, three DMRS 705s can be transmitted within a single REG 703. Depending on the aggregation level (AL), the number of CCEs required to transmit the PDCCH can be 1, 2, 4, 8, or 16, and different numbers of CCEs can be used to achieve link adaptation of the downlink control channel. For example, in the case of AL=L, a downlink control channel can be transmitted using L CCEs. The UE needs to detect the signal without information about the downlink control channel, and therefore a search space indicating the set of CCEs has been defined for blind decoding. The search space is the set of downlink control channel candidates that the UE needs to attempt to decode at a given AL, and since 1, 2, 4, 8, or 16 CCEs can be bundled at each AL, the UE can have multiple search spaces. The search space set can be defined as the set of search spaces for all configured aggregation levels.

[0291] The search space can be categorized into a general search space and a UE-specific search space. A group of UEs or all UEs can search the common search space of the PDCCH to receive cell common control information, such as dynamic scheduling of system information or paging messages. For example, the PDSCH scheduling allocation information for transmitting SIBs, including cell operator information, can be received by searching the common search space of the PDCCH. In the case of the common search space, a group of UEs or all UEs need to receive the PDCCH, and therefore the common search space can be defined as a predetermined set of CCEs. The UE-specific search space of the PDCCH can be searched to receive scheduling allocation information for UE-specific PDSCHs or PUSCHs. The UE-specific search space can be defined specifically for UEs based on various system parameters and the UE's identifier.

[0292] In 5G, base stations can configure search space parameters for PDCCH for the UE via upper-layer signaling (e.g., SIB, MIB, or RRC signaling). For example, the base station can provide the UE with configurations such as the number of PDCCH candidates for each aggregation level L, the listening period for the search space, the listening timing for each symbol in the time slots within the search space, the search space type (general search space or UE-specific search space), the combination of RNTI and DCI formats to be listened to in the corresponding search space, and the control resource set index used for listening to the search space. For example, this configuration information may include several items as shown in Table 22. Obviously, the examples given below are not restrictive.

[0293] [Table 22]

[0294]

[0295]

[0296] Based on the configuration information, the base station can configure one or more search space sets for the UE. According to an embodiment, the base station can configure search space set 1 and search space set 2 for the UE. It can configure the DCI format A scrambled by X-RNTI for listening in the common search space of search space set 1, and can configure the DCI format B scrambled by Y-RNTI for listening in the UE-specific search space of search space set 2.

[0297] Depending on the configuration information, one or more search space sets may exist in the public search space or the UE-specific search space. For example, search space set #1 and search space set #2 can be configured as a public search space, while search space set #3 and search space set #4 can be configured as UE-specific search spaces.

[0298] The combination of DCI format and RNTI given below can be listened to in the public search space. Obviously, the examples given below are not restrictive:

[0299] -DCI format 0_0 / 1_0, where CRC is scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, RA-RNTI, TC-RNTI, P-RNTI, SI-RNTI;

[0300] -DCI format 2_0, where CRC is scrambled by SFI-RNTI;

[0301] -DCI format 2_1, where CRC is scrambled by INT-RNTI;

[0302] -DCI format 2_2, where the CRC is scrambled by TPC-PUSCH-RNTI and TPC-PUCCH-RNTI; and / or

[0303] -DCI format 2_3, where CRC is scrambled by TPC-SRS-RNTI.

[0304] The combination of DCI format and RNTI given below can be listened to within a UE-specific search space. Obviously, the examples given below are not restrictive:

[0305] -DCI format 0_0 / 1_0, where CRC is scrambled by C-RNTI, CS-RNTI, TC-RNTI; and / or

[0306] -DCI format 1_0 / 1_1, where CRC is scrambled by C-RNTI, CS-RNTI, and TC-RNTI.

[0307] The listed RNTIs can be defined and used as follows:

[0308] - Cell RNTI (C-RNTI): Used for scheduling UE-specific PDSCH;

[0309] - Temporary Cell RNTI (TC-RNTI): Used to schedule UE-specific PDSCH;

[0310] -Configured Scheduling RNTI (CS-RNTI): Used to schedule UE-specific PDSCHs that are semi-statically configured;

[0311] - Random Access RNTI (RA-RNTI): Used to schedule PDSCH in the random access step;

[0312] - Paging RNTI (P-RNTI): Used to schedule the PDSCH that transmits paging information;

[0313] -System Information RNTI (SI-RNTI): Used to schedule the PDSCH that transmits system information;

[0314] - Interrupt RNTI (INT-RNTI): Used to indicate whether the PDSCH has been punched;

[0315] -PUSCH RNTI Transmission Power Control (TPC-PUSCH-RNTI): Used to indicate power control commands regarding the PUSCH;

[0316] -PUCCH RNTI Transmit Power Control (TPC-PUCCH-RNTI): Used to indicate power control commands regarding the PUCCH; and / or

[0317] -SRS RNTI Transmission Power Control (TPC-SRS-RNTI): Used to indicate power control commands related to the SRS.

[0318] The DCI formats listed above can follow the definitions given in Table 23 below.

[0319] [Table 23]

[0320]

[0321] In 5G, the search space of the aggregation level L associated with the control resource set p and the search space set s can be expressed by the following formula 1:

[0322] [Formula 1]

[0323]

[0324] -L: Aggregation level;

[0325] - Carrier index;

[0326] - : Control the total number of CCEs existing in resource set p;

[0327] - Time slot index;

[0328] - : The number of PDCCH candidates at aggregation level L;

[0329] - = 0、…、 -1: PDCCH candidate index at aggregation level L;

[0330] - = 0、…、 -1;

[0331] - , , , , , ;and

[0332] - UE identifier.

[0333] In the context of public search spaces, The value can correspond to 0.

[0334] In the case of a UE-specific search space The value can correspond to the UE's identifier (C-RNTI or ID configured by the base station for the UE) and the value of the time index change.

[0335] In a 5G system, multiple search space sets can be configured with different parameters (e.g., the parameters in Table 22), and the search space set that the UE listens to at each time point may differ accordingly. For example, if search space set #1 is configured with a time slot period of X, and search space set #2 is configured with a time slot period of Y, and if X and Y are different, then the UE can listen to both search space set #1 and search space set #2 in a specific time slot, and can listen to only one of search space set #1 and search space set #2 in another specific time slot.

[0336] [PUSCH: Regarding the transmission scheme]

[0337] Next, the PUSCH transmission scheduling scheme will be described. PUSCH transmissions can be dynamically scheduled via UL authorization within the DCI, or via configured authorization type 1 or type 2. Dynamic scheduling instructions for PUSCH transmissions can be given via DCI format 0_0 or 0_1.

[0338] Configured grant type 1 PUSCH transports can be semi-statically configured via upper-layer signaling by receiving a configuredGrantConfig including the rrc-ConfiguredUplinkGrant in Table 29, without receiving the UL grant within the DCI. Configured grant type 2 PUSCH transports can be semi-persistently scheduled via upper-layer signaling after receiving a configuredGrantConfig excluding the rrc-ConfiguredUplinkGrant in Table 24, with the UL grant within the DCI. If a PUSCH transport operates with a configured grant, the parameters applied to the PUSCH transport are applied via the configuredGrantConfig (upper-layer signaling) in Table 24, except for scaling of dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and UCI-OnPUSCH, which are provided by pusch-Config (upper-layer signaling) in Table 25. If a transformPrecoder is provided within the configuredGrantConfig (upper-layer signaling) in Table 24, the UE will apply tp-pi2BPSK from the pusch-Config in Table 25 to PUSCH transmissions with configured grant operations. Clearly, the examples given above are not restrictive.

[0339] [Table 24]

[0340]

[0341]

[0342]

[0343] Next, the PUSCH transmission method will be described. The DMRS antenna port used for PUSCH transmission is the same as the antenna port used for SRS transmission. Depending on whether the value of txConfig inside pusch-Config in Table 30 (which is the upper-layer signaling) is "codebook" or "nonCodebook", PUSCH transmission can follow either a codebook-based transmission method or a non-codebook-based transmission method.

[0344] As described above, PUSCH transmissions can be dynamically scheduled via DCI format 0_0 or 0_1, and can be semi-statically configured via configured authorization. Upon receiving an indication to schedule a PUSCH transmission via DCI format 0_0, the UE performs beam configuration for the PUSCH transmission using the pucch-spatialRelationInfoID corresponding to the UE-specific PUCCH resource corresponding to the smallest ID within the active uplink BWP within the serving cell, and the PUSCH transmission is based on a single antenna port. The UE may not expect PUSCH transmissions to be scheduled via DCI format 0_0 within a BWP without configured PUCCH resources (including pucch-spatialRelationInfo). If the UE has not configured txConfig within the pusch-Config in Table 25, the UE may not expect scheduling via DCI format 0_1.

[0345] [Table 25]

[0346]

[0347]

[0348] The codebook-based PUSCH transmission will be described below. Codebook-based PUSCH transmission can be dynamically scheduled using DCI format 0_0 or 0_1, and can be semi-statically configured using a configured license. If codebook-based PUSCH is dynamically scheduled using DCI format 0_1 ​​or semi-statically configured using a configured license, the UE determines the precoder for PUSCH transmission based on the SRS Resource Indicator (SRI), the Transport Precoding Matrix Indicator (TPMI), and the transport rank (the number of PUSCH transport layers).

[0349] The SRI can be given through the SRS resource indicator (a field within the DCI) or configured through the srs-ResourceIndicator (upper-layer signaling). During codebook-based PUSCH transmission, at least one SRS resource is configured for the UE, and up to two SRS resources can be configured for the UE. Similar to the codebook-based PUSCH transmission described above, if the SRI is provided to the UE through the DCI, the SRS resource indicated by the corresponding SRI refers to the SRS resource corresponding to that SRI in the SRS resources transmitted before the PDCCH including the corresponding SRI. Additionally, the TPMI and transport rank can be given through "precoding information and number of layers" (a field within the DCI) or configured through precodingAndNumberOfLayers (upper-layer signaling). The TPMI can be used to indicate the precoder to be applied to the PUSCH transmission. If one SRS resource is configured for the UE, the TPMI can be used to indicate the precoder to be applied to the configured SRS resource. If multiple SRS resources are configured for the UE, the TPMI is used to indicate the precoder to be applied to the SRS resource indicated by the SRI.

[0350] The precoder used for PUSCH transmission can be selected from the uplink codebook, whose number of antenna ports is the same as the nrofSRS-Ports value within the SRS-Config (upper-layer signaling). Combined with codebook-based PUSCH transmission, the UE can determine the codebook subset based on the codebookSubset and TPMI within the push-Config (upper-layer signaling). Based on the UE capabilities reported by the UE to the base station, the codebookSubset within the push-Config (upper-layer signaling) can be configured as "fullyAndPartialAndNonCoherent", "partialAndNonCoherent", or "noncoherent". If the UE reports "partialAndNonCoherent" as a UE capability, the UE may not expect the codebookSubset (upper-layer signaling) value to be configured as "fullyAndPartialAndNonCoherent". Additionally, if the UE reports "nonCoherent" as a UE capability, the UE may not expect the codebookSubset (upper-layer signaling) value to be configured as "fullyAndPartialAndNonCoherent" or "partialAndNonCoherent". If the nrofSRS-Ports within the SRS-ResourceSet (upper-layer signaling) indicates two SRS antenna ports, the UE does not expect the codebookSubset (upper-layer signaling) value to be configured as "partialAndNonCoherent".

[0351] An SRS resource set can be configured for the UE, where the value used within the SRS-ResourceSet (upper-layer signaling) is "codebook," and an SRS resource can be indicated by the SRI within the corresponding SRS resource set. If multiple SRS resources are configured within the SRS resource set, and the value used within the SRS-ResourceSet (upper-layer signaling) is "codebook," the UE may expect the nrofSRS-Ports value within the SRS-Resource (upper-layer signaling) to be the same for all SRS resources.

[0352] The UE can transmit one or more SRS resources included in the SRS resource set to the base station, where the usage value is configured as a "codebook" according to the upper-layer signaling. The base station can select an SRS resource from the SRS resources transmitted by the UE and instruct the UE to transmit PUSCH using the transmission beam information of the corresponding SRS resource. In conjunction with codebook-based PUSCH transmission, the SRI can be used as an index for selecting an SRS resource and can be included in the DCI. Additionally, the base station can add information to the DCI indicating the rank and TPMI used by the UE for PUSCH transmission. Using the SRS resource indicated by the SRI, the UE can apply a precoder indicated by the rank and TPMI based on the transmission beam of the corresponding SRS resource when performing PUSCH transmission, thereby performing PUSCH transmission.

[0353] Next, we will describe non-codebook-based PUSCH transmission. Non-codebook-based PUSCH transmission can be dynamically scheduled using DCI format 0_0 or 0_1, and can be semi-statically operated using configured licenses. If at least one SRS resource is configured within the SRS resource set, and the usage value within the SRS-ResourceSet (upper-layer signaling) is "nonCodebook", then non-codebook-based PUSCH transmission can be scheduled for the UE using DCI format 0_1.

[0354] For an SRS resource set, if the usage value within the SRS-ResourceSet (upper-layer signaling) is "nonCodebook", a connected NZP CSI-RS resource (non-zero power CSI-RS) can be configured for the UE. The UE can calculate the precoder for SRS transmissions by measuring the NZP CSI-RS resources connected to the SRS resource set. If the difference between the last received symbol of an aperiodic NZP CSI-RS resource connected to the SRS resource set and the first symbol of an aperiodic SRS transmission in the UE is less than 42 symbols, the UE does not expect to update the precoder information regarding SRS transmissions.

[0355] If the configured value of resourceType within the SRS-ResourceSet (upper-layer signaling) is "aperiodic," then a connected NZP CSI-RS can be indicated by an SRS request, which is a field within DCI format 0_1 ​​or 1_1. If the connected NZP CSI-RS resource is an aperiodic NZP CSI-RS resource, its presence can be indicated by the SRS request value (a field within DCI format 0_1 ​​or 1_1) not being "00." The corresponding DCI may not indicate cross-carrier or cross-BWP scheduling. Additionally, if the SRS request value indicates the presence of an NZP CSI-RS, then the NZP CSI-RS is located in a time slot used to transmit the PDCCH including the SRS request field. In this case, the TCI state configured for the scheduled subcarrier may not be configured as QCL-TypeD.

[0356] If a periodic or semi-persistent SRS resource set is configured, the associated CSI-RS within the SRS-ResourceSet (upper-layer signaling) can indicate the connected NZP CSI-RS. For non-codebook transmissions, the UE may not expect that the spatialRelationInfo, which serves as upper-layer signaling regarding SRS resources, and the associated CSI-RS within the SRS resource set (upper-layer signaling) will be configured together.

[0357] If multiple SRS resources are configured for the UE, the UE can determine the precoder and transmission rank to be applied to PUSCH transmission based on the SRI indicated by the base station. The SRI can be indicated by an SRS resource indicator (a field within the DCI) or configured via the srs-ResourceIndicator (upper-layer signaling). Similar to the codebook-based PUSCH transmission described above, if the SRI is provided to the UE via the DCI, the SRS resource indicated by the corresponding SRI can refer to the SRS resource corresponding to that SRI among those transmitted before the PDCCH including the corresponding SRI. The UE can use one or more SRS resources for SRS transmission, and the maximum number of SRS resources that can be transmitted simultaneously within the same symbol within an SRS resource set, as well as the maximum number of SRS resources, is determined by the UE's capabilities reported to the base station. SRS resources transmitted simultaneously by the UE can occupy the same RB. The UE can configure one SRS port for each SRS resource. There may be only one configured SRS resource set, where the usage value inside the SRS-ResourceSet (upper-layer signaling) is "nonCodebook", and up to four SRS resources can be configured for non-codebook PUSCH transmission.

[0358] The base station can transmit an NZP-CSI-RS connected to the SRS resource set to the UE, and the UE can calculate the precoder to be used when transmitting one or more SRS resources within the corresponding SRS resource set based on the measurement results when receiving the corresponding NZP-CSI-RS. The UE can apply the calculated precoder when transmitting one or more SRS resources within the SRS resource set to the base station, where the configured purpose is "nonCodebook," and the base station can select one or more SRS resources from the received one or more SRS resources. Combined with nonCodebook-based PUSCH transmission, the SRI can indicate an index that can represent one SRS resource or a combination of multiple SRS resources. The number of SRS resources indicated by the SRI transmitted by the base station can be the number of transmission layers for the PUSCH, and the UE can transmit the PUSCH by applying the precoder used for SRS resource transmission to each layer.

[0359] [About SRS]

[0360] Next, an uplink channel estimation method utilizing the UE's Sounding Reference Signal (SRS) transmission will be described. The base station can configure at least one SRS configuration for each uplink base station window (BWP) to transmit configuration information for SRS transmission to the UE, and can also configure at least one SRS resource set for each SRS configuration. As an example, the base station and UE can exchange upper-layer signaling information as follows to transmit information about the SRS resource set. Obviously, the following example is not restrictive:

[0361] -srs-ResourceSetId: SRS resource set index;

[0362] -srs-ResourceIdList: A collection of SRS resource indexes referenced by an SRS resource set;

[0363] -resourceType: The time-domain transport configuration of the SRS resources referenced by the SRS resource set, and can be configured as "periodic," "semi-persistent," or "aperiodic." If configured as "periodic" or "semi-persistent," associated CSI-RS information can be provided based on the location where the SRS resource set is used. If configured as "aperiodic," aperiodic SRS resource trigger list / slot offset information can be provided, and associated CSI-RS information can be provided based on the location where the SRS resource set is used.

[0364] - Purpose: Configures the usage location of SRS resources referenced by the SRS resource set, and can be configured as one of "beamManagement", "codebook", "nonCodebook", and "antennaSwitching"; and / or

[0365] -alpha, p0, pathlossReferenceRS, srs-PowerControlAdjustmentStates: Provides parameter configurations for adjusting the transmission power of SRS resources referenced by the SRS resource set.

[0366] The UE can understand that the SRS resources included in the SRS resource index set referenced by the SRS resource set follow the information configured for the SRS resource set.

[0367] Additionally, the base station and UE can send / receive upper-layer signaling information to convey individual configuration information about SRS resources. As an example, individual configuration information about SRS resources may include time-frequency domain mapping information within the time slots of the SRS resource, and this may include information about intra- or inter-time slot frequency hopping for the SRS resource. Individual configuration information about SRS resources may include the time-domain transmission configuration of the SRS resource and may be configured as "periodic," "semi-persistent," and "aperiodic." The time-domain transmission configuration of the SRS resource may be limited to having the same time-domain transmission configuration as the SRS resource set containing the SRS resource. If the time-domain transmission configuration of the SRS resource is configured as "periodic" or "semi-persistent," the time-domain transmission configuration may also include the SRS resource transmission period and time slot offset (e.g., periodityAndOffset).

[0368] The base station can activate or deactivate the UE's SRS transmission via upper-layer signaling (including RRC signaling or MAC CE signaling) or L1 signaling (e.g., DCI). For example, the base station can activate or deactivate the UE's periodic SRS transmission via upper-layer signaling. The base station can indicate the activation of an SRS resource set configured with resourceType as "periodic" via upper-layer signaling, and the UE can transmit SRS resources referenced by the activated SRS resource set. The intra-slot time-frequency domain resource mapping of the transmitted SRS resources follows the resource mapping information configured for the SRS resources, and the slot mapping (including transmission period and slot offset) follows periodicityAndOffset configured for the SRS resources. Additionally, the spatial domain transmission filter applied to the transmitted SRS resources can refer to spatial relation information configured for the SRS resources, or it can refer to associated CSI-RS information configured for an SRS resource set including the SRS resources. The UE can transmit SRS resources activated within the uplink BWP for periodic SRS resources activated via upper-layer signaling.

[0369] For example, a base station can activate or deactivate a UE's semi-persistent SRS transmission via upper-layer signaling. The base station can instruct the activation of an SRS resource set via MAC CE signaling, and the UE can transmit SRS resources referenced by the activated SRS resource set. The SRS resource set activated via MAC CE signaling may be limited to SRS resource sets with resourceType configured as "semi-persistent". The intra-slot time-frequency domain resource mapping of the transmitted SRS resources follows the resource mapping information configured for the SRS resources, and the slot mapping (including transmission period and slot offset) follows periodicityAndOffset configured for the SRS resources. Additionally, the spatial domain transmission filter applied to the transmitted SRS resources can refer to spatial relation information configured for the SRS resources, or it can refer to associated CSI-RS information configured for the SRS resource set including the SRS resources. If spatial relation information is configured for the SRS resources, the spatial domain transmission filter can be determined by referring to configuration information regarding the spatial relation information transmitted via MAC CE signaling to activate semi-persistent SRS transmission, without needing to follow that spatial relation information. The UE can transmit SRS resources activated within the uplink BWP for semi-persistent SRS resources activated via upper-layer signaling.

[0370] For example, a base station can trigger aperiodic SRS transmissions via DCI by a UE. The base station can indicate one of the aperiodic SRS triggers (aperiodicSRS-ResourceTrigger) through the SRS request field of the DCI. The UE understands that the SRS resource set whose configuration information includes the aperiodic SRS resource trigger list, as indicated by the DCI, has been triggered. The UE can transmit the SRS resources referenced by the triggered SRS resource set. The intra-slot time-frequency domain resource mapping of the transmitted SRS resources can follow the resource mapping information configured for the SRS resources. Furthermore, the slot mapping of the transmitted SRS resources can be determined by the slot offset between the SRS resources and the PDCCH including the DCI, and this can refer to the values ​​included in the slot offset set configured for the SRS resource set. Specifically, the value indicated in the time-domain resource assignment field of the DCI can be one of the offset values(s) included in the time-slot offset set configured for the SRS resource set as the time-slot offset between the SRS resource and the PDCCH including the DCI. Additionally, the spatial domain transmission filter applied to the transmitted SRS resource can refer to the spatial relationship information configured for the SRS resource, or it can refer to the associated CSI-RS information configured for the SRS resource set including the SRS resource. The UE can transmit SRS resources activated within the uplink BWP for aperiodic SRS resources triggered by the DCI.

[0371] If a base station initiates aperiodic SRS transmissions via DCI by the UE, a minimum time interval may be required between the transmitted SRS and the PDCCH containing the DCI that triggered the aperiodic SRS transmission, allowing the UE to transmit the SRS by applying configuration information about the SRS resources. The time interval for SRS transmissions by the UE can be defined as the number of symbols between the last symbol of the PDCCH containing the DCI that triggered the aperiodic SRS transmission and the first symbol of the first transmitted SRS resource(s) mapped to the first transmitted SRS resource(s). The minimum time interval can be determined with reference to the PUSCH preparation time required for the UE to prepare for PUSCH transmission. The minimum time interval may have different values ​​depending on the usage location of the SRS resource set including the transmitted SRS resources. For example, the minimum time interval can be determined as N² symbols based on the UE's processing capacity, which follows the UE's PUSCH preparation time.

[0372] Additionally, if the SRS resource set is configured as "codebook" or "antennaSwitching" based on the location of the SRS resource set including the transmitted SRS resources, the minimum time interval can be determined to be N² symbols. If the SRS resource set is configured as "nonCodebook" or "beamManagement," the minimum time interval can be determined to be N²+14 symbols. If the time interval used for aperiodic SRS transmission is greater than or equal to the minimum time interval, the UE can transmit aperiodic SRS. If the time interval used for aperiodic SRS transmission is less than the minimum time interval, the DCI triggering aperiodic SRS can be ignored. Clearly, the examples given below are not restrictive.

[0373] [Table 26]

[0374]

[0375]

[0376] The configuration information `spatialRelationInfo` in Table 26 above is applied to the beam used for SRS transmission with reference to a reference signal, which corresponds to the beam information of the corresponding reference signal. For example, the configuration of `spatialRelationInfo` can include the information shown in Table 27 below. Obviously, the examples given below are not limiting.

[0377] [Table 27]

[0378]

[0379] Referring to the `spatialRelationInfo` configuration, the SS / PBCH block index, CSI-RS index, or SRS index can be configured as the index of a reference signal to use the beam information of a specific reference signal. The upper-layer signaling `referenceSignal` corresponds to configuration information indicating which reference signal's beam information should be referenced for the corresponding SRS transmission. `ssb-Index` refers to the SS / PBCH block index, `csi-RS-Index` refers to the CSI-RS index, and `srs` refers to the SRS index. If the upper-layer signaling `referenceSignal` has the configured value "ssb-Index", the UE can use the receive beam used to receive the SS / PBCH block corresponding to `ssb-Index` as the transmit beam for the corresponding SRS transmission. If the upper-layer signaling referenceSignal has a configured value "srs", the UE can use the receive beam used to transmit the SRS corresponding to srs as the transmit beam used to transmit the corresponding SRS.

[0380] [Regarding UE Capability Report]

[0381] In LTE and NR, the UE can execute a procedure in which the UE reports the capabilities it supports to the corresponding base station when it connects to the serving base station. In the following description, the above procedure will be referred to as UE capability reporting.

[0382] A base station can transmit a UE capability query message to a connected UE to request capability reports. This message can include UE capability requests for each Radio Access Technology (RAT) type of the base station. RAT type-specific requests can include information such as supported frequency band combinations. Alternatively, in the case of a UE capability query message, UE capabilities for multiple RAT types can be requested through a single RRC message container transmitted by the base station, or the base station can transmit a UE capability query message including multiple UE capability requests for a corresponding RAT type. For example, a capability query can be repeated multiple times in a single message, and the UE can configure corresponding UE capability information messages and report the message multiple times. In next-generation mobile communication systems, the UE can request features such as NR, LTE, and E-UTRA-NR dual connectivity (EN-DC) with multiple RATs (MR-DC). Generally, a UE capability query message can be transmitted for the first time after the UE connects to the base station, but the base station can request this message at any time if needed.

[0383] According to the embodiment, after receiving a UE capability report request from the base station, the UE can configure UE capabilities based on the frequency band information and RAT type requested by the base station. The following summarizes the method for configuring UE capabilities in the NR system.

[0384] 1. If the UE receives a list of LTE and / or NR frequency bands from the base station in a UE capability request, the UE can construct a frequency band combination (BC) for EN-DC and NR Standalone (SA). In other words, the UE can configure a BC candidate list for EN-DC and NR SA based on the frequency bands received from the base station upon a request made via FreqBandList. Furthermore, the frequency bands can be prioritized according to the order described in the FreqBandList.

[0385] 2. If the base station sets the “eutra-nr-only” flag or the “eutra” flag and requests a UE capability report, the UE can remove all content related to NR SA BC from the configured BC candidate list. This operation can only be performed when the LTE base station (eNB) requests “eutra” capability.

[0386] 3. Then, the UE can remove the fallback BC from the BC candidate list configured in the above steps. As used herein, a "fallback BC" refers to a BC that can be obtained by removing the frequency band corresponding to at least one SCell from a specific BC, and since the BC may already cover the fallback BC before removing the frequency band corresponding to at least one SCell, the fallback BC can be omitted. This step can also be applied to MR-DC, that is, LTE frequency bands can also be applied. The remaining BCs after the above steps can constitute the final "candidate BC list".

[0387] 4. The UE can select a BC suitable for the requested RAT type from the final "Candidate BC List" and choose the BC to report. In this step, the UE can configure the supportedBandCombinationList in a predetermined order. That is, the UE can configure the BCs and UE capabilities for reporting according to the pre-configured rat-Type order (NR -> eutra - NR -> eutra). Additionally, the UE can configure the featureSetCombination for the configured supportedBandCombinationList and configure a "Candidate FeatureSet Combination" list from the candidate BC list, removing lists of fallback BCs (including capabilities of the same or lower tier). The "Candidate FeatureSet Combination" can include all feature set combinations for NR and EUTRA-NR BCs and can be provided from the feature set combinations of the containers of UE-NR-Capabilities and UE-MRDC-Capabilities.

[0388] 5. If the requested RAT type is eutra-nr and has an impact, featureSetCombinations can be included in both the UE-MRDC-Capabilities and UE-NR-Capabilities containers. However, the NR feature set may only be included in UE-NR-Capabilities.

[0389] After UE capabilities are configured, the UE can transmit UE capability information messages, including the UE capabilities, to the base station. The base station can then perform scheduling and transmit / receive management appropriate to the UE based on the UE capabilities received from the UE.

[0390] The embodiments of this disclosure will now be described in detail with reference to the accompanying drawings. The content of this disclosure can be applied to FDD and TDD systems. As used herein, "upper signaling" is a method for transmitting signals from a base station to a UE using a downlink data channel of the physical layer or from a UE to a base station using an uplink data channel of the physical layer, and may also be referred to as "RRC signaling," "PDCP signaling," or "MAC control element (MAC CE)."

[0391] In the following disclosure, the UE may use various methods to determine whether to apply cooperative communication, such as allocating cooperative communication to a PDSCH(s) to which the PDSCH(s) to be applied has a specific format, or the PDSCH(s) to which the cooperative communication is to be applied includes a specific indicator indicating whether cooperative communication is applied, or the PDSCH(s) to which the cooperative communication is to be applied is scrambled by a specific RNTI, or assuming that cooperative communication is applied within a specific range indicated by the upper layer. In the following, for ease of description, it is assumed that the NC-JT case refers to the case where the UE receives the PDSCH(s) to which the cooperative communication is to be applied based on conditions similar to those described above.

[0392] In the following text, determining the priority between A and B can be described in several ways, such as selecting the entity with higher priority according to a predetermined priority rule and performing the operation corresponding to that entity, or omitting or abandoning the operation on the entity with lower priority.

[0393] In the following description, the above examples may be described by means of multiple embodiments, but they are not independent of each other and one or more embodiments may be applied simultaneously or in combination.

[0394] In the following text, for ease of description, cells, transmission points, panels, beams, and / or transmission directions that can be distinguished by upper-layer / L1 parameters (such as TCI status or spatial relationship information, cell ID, TRP ID, or panel ID) can be collectively described as TRP, beam, or TCI status. Therefore, in practical applications, TRP, beam, or TCI status can be appropriately replaced by one of the aforementioned terms.

[0395] In the following disclosure, the UE may use various methods to determine whether to apply cooperative communication, such as allocating cooperative communication to a PDSCH(s) to which the PDSCH(s) to be applied has a specific format, or the PDSCH(s) to which the cooperative communication is to be applied includes a specific indicator indicating whether cooperative communication is applied, or the PDSCH(s) to which the cooperative communication is to be applied is scrambled by a specific RNTI, or assuming that cooperative communication is applied within a specific range indicated by the upper layer. In the following, for ease of description, it is assumed that the NC-JT case refers to the case where the UE receives the PDSCH(s) to which the cooperative communication is to be applied based on conditions similar to those described above.

[0396] In the following description of this disclosure, "upper-layer signaling" may refer to signaling corresponding to at least one of the following signaling, or a combination of one or more of them. Clearly, the examples given below are not limiting:

[0397] -Master Information Block (MIB);

[0398] - System Information Block (SIB) or SIB X (X=1, 2, ...);

[0399] - Radio Resource Control (RRC); and / or

[0400] -Media Access Control (MAC) Control Element (CE).

[0401] Additionally, L1 signaling can refer to signaling corresponding to at least one signaling method or a combination of one or more of the following physical layer channels or signaling methods. Clearly, the examples given below are not limiting:

[0402] -Physical Downlink Control Channel (PDCCH);

[0403] - Downlink Control Information (DCI);

[0404] -UE-specific DCI;

[0405] - A group of public DCIs;

[0406] -Public DCI;

[0407] - Scheduling DCI (e.g., DCI used to schedule downlink or uplink data);

[0408] - Non-scheduled DCI (e.g., DCI not used to schedule downlink or uplink data);

[0409] - Physical Uplink Control Channel (PUCCH); and / or

[0410] - Uplink Control Information (UCI).

[0411] In the following text, determining the priority between A and B can be described in several ways, such as selecting the entity with higher priority according to a predetermined priority rule and performing the operation corresponding to that entity, or omitting or abandoning the operation on the entity with lower priority.

[0412] As used herein, the term “slot” can generally refer to a specific unit of time corresponding to a transmission time interval (TTI), specifically referring to a slot used in a 5G NR system, or a slot or subframe used in a 4G LTE system.

[0413] In the following description, the above examples may be described by means of multiple embodiments, but they are not independent of each other and one or more embodiments may be applied simultaneously or in combination.

[0414] <First Embodiment: UE-based PUSCH Transmission Method without Codebook>

[0415] The embodiments disclosed herein describe a non-codebook-based PUSCH transmission method for a UE. This embodiment can be operated in conjunction with other embodiments.

[0416] Figure 8 A non-codebook-based PUSCH transmission process according to an embodiment of the present disclosure is illustrated.

[0417] refer to Figure 8 The UE can receive associated CSI-RS from the base station (Operation 800). The UE can estimate the channel between the base station and the UE based on the associated CSI-RS received from the base station, and then calculate a precoder for non-codebook-based PUSCH transmission based on the estimated channel (Operation 810). The UE can calculate the same precoder for all frequency resource regions for which it wants to calculate the precoder, or it can calculate different precoders for different partial frequency resource regions. For example, the UE can calculate a wideband precoder or a subband precoder. The UE can then apply the vectors of each layer of the calculated overall precoding matrix to each SRS resource and send the vectors to the base station. Depending on the UE's UE capability report and the base station's higher-layer signaling configuration (or one or more of the UE's UE capability report and the base station's higher-layer signaling configuration), the layer values ​​of the overall precoding matrix and the number of SRS resources can be determined. Therefore, the UE can simultaneously send one or more SRS resources with a precoding matrix applied to the base station. These one or more SRS resources with the precoding matrix applied are calculated by the UE by applying a vector of each layer of the overall precoding matrix configured by up to eight layers to each of the up to eight SRS resources.

[0418] The UE can report to the base station via its UE capability the maximum number of SRS resources that can be simultaneously transmitted to one or more SRS resources with applied precoding matrices (Operation 820). When the associated CSI-RS is aperiodic CSI-RS, and the SRS resources in the SRS resource set configured for non-codebook purposes are also aperiodic SRS, the UE may not anticipate that the time interval between receiving the associated CSI-RS from the base station and transmitting one or more precoded SRS resources is less than [a certain value]. A symbol. In this case, μ can be a value representing the subcarrier spacing. For example, the subcarrier spacing can be... kHz. Returning to reference operation 810, when the associated CSI-RS is an aperiodic CSI-RS and the SRS resources in the SRS resource set configured for non-codebook use are aperiodic SRS, the UE can estimate the channel and calculate the precoder based on the associated CSI-RS, and can apply precoding to the SRS resources using time corresponding to at least 42 symbols and perform transmission (operation 810).

[0419] After receiving one or more SRS resources with precoding applied, the base station can determine the SRS resource combination that has the best reception performance for each PUSCH precoding frequency resource element. The precoder combination applied to the one or more SRS resources selected based on the determined SRS resource combination can be determined as the precoder for the UE to perform non-codebook-based PUSCH transmission in the corresponding PUSCH precoding frequency resource element (operation 830). The UE can receive information about the SRS resource combination determined by the base station from the base station via the SRI field in the DCI (operation 840). In this case, the UE can understand the number of SRS resources indicated to the UE via the SRI as the rank information of the non-codebook-based PUSCH to be transmitted by the UE, and can also understand it as the precoder information of the non-codebook-based PUSCH to be transmitted by the UE through the one or more SRS resources indicated to the UE via the SRI. Based on the rank and precoder information, the UE can perform non-codebook-based PUSCH transmission (operation 850).

[0420] The UE can expect the SRS request field in DCI format 0_2 to be 0, 1, 2, or 3 bits long, and may interpret the SRS request field of each bit length as follows. Of course, this is not limited to the following examples.

[0421] - When srs-RequestDCI-0-2 is not configured as a higher-level signaling, the SRS request field in DCI format 0_2 may be zero.

[0422] When the higher-layer signaling srs-RequestDCI-0-2 is configured to 1 and the supplementaryUplink in ServingCellConfig is not configured, the UE can treat the SRS request field in DCI format 0_2 as a single bit. The interpretation of a single bit can follow the first two rows of Table 29 or Table 28. When using Table 28, when the value of the SRS request field is 0, the UE can interpret the operation corresponding to "00" in the first row of Table 28, and when the value of the SRS request field is 1, the UE can interpret the operation corresponding to "01" in the second row of Table 28.

[0423] When the higher-layer signaling srs-RequestDCI-0-2 is configured with a value of 1 and supplementaryUplink in ServingCellConfig is configured, the UE can treat the SRS request field in DCI format 0_2 as two bits. The first bit of these two bits can be interpreted as indicating either SUL or SUL, while the interpretation of the remaining bit can follow the first two rows of Table 29 or Table 28 below. When using Table 28 below, when the value of the SRS request field is 0, the UE can interpret the operation corresponding to "00" in the first row of Table 28 below, and when the value of the SRS request field is 1, the UE can interpret the operation corresponding to "01" in the second row of Table 28 below.

[0424] - When the higher-layer signaling srs-RequestDCI-0-2 is configured to have a value of 2 and supplementaryUplink in ServingCellConfig is not configured, the UE can treat the SRS request field in DCI format 0_2 as two bits, and the interpretation of these two bits can follow Table 28 below.

[0425] - When the higher-layer signaling srs-RequestDCI-0-2 is configured to have a value of 2 and supplementaryUplink in ServingCellConfig is configured, the UE can treat the SRS request field in DCI format 0_2 as three bits. The first bit of these three bits can be interpreted as indicating non-SUL or SUL, while the interpretation of the remaining two bits can follow Table 28 below.

[0426] The UE can expect the SRS request field in DCI format 1_2 to be 0, 1, 2 or 3 bits long, and may interpret the SRS request field of each bit length as follows.

[0427] - When SRS-RequestDCI-1-2 is not configured as a higher-level signaling, the SRS request field in DCI format 1_2 may be zero.

[0428] When the higher-layer signaling SRS-RequestDCI-1-2 is configured to have a value of 1 and the supplementaryUplink in ServingCellConfig is configured, the UE can treat the SRS request field in DCI format 1_2 as a single bit. The interpretation of a single bit can follow the first two rows of Table 29 or Table 28. When using Table 28, when the value of the SRS request field is 0, the UE can interpret the operation corresponding to "00" in the first row of Table 28, and when the value of the SRS request field is 1, the UE can interpret the operation corresponding to "01" in the second row of Table 28.

[0429] When the higher-layer signaling SRS-RequestDCI-1-2 is configured with a value of 1 and the supplementaryUplink in ServingCellConfig is configured, the UE can treat the SRS request field in DCI format 1_2 as two bits. The first bit of these two bits can be interpreted as indicating either SUL or SUL, while the interpretation of the remaining bit can follow the first two rows of Table 29 or Table 28 below. When using Table 28 below, when the value of the SRS request field is 0, the UE can interpret the operation corresponding to "00" in the first row of Table 28 below, and when the value of the SRS request field is 1, the UE can interpret the operation corresponding to "01" in the second row of Table 28 below.

[0430] - When the higher-layer signaling srs-RequestDCI-1-2 is configured to have a value of 2 and supplementaryUplink in ServingCellConfig is not configured, the UE can treat the SRS request field in DCI format 1_2 as two bits, and the interpretation of these two bits can follow Table 28 below.

[0431] - When the higher-layer signaling srs-RequestDCI-1-2 is configured to have a value of 2 and supplementaryUplink in ServingCellConfig is configured, the UE can treat the SRS request field in DCI format 1_2 as three bits. The first of these three bits can be interpreted as indicating non-SUL or SUL, while the interpretation of the remaining two bits can follow Table 28 below.

[0432] If the supplementaryUplink in the higher-layer signaling ServingCellConfig is not configured, the UE can interpret the higher-layer signaling srs-RequestDCI-0-2 as having the length of the SRS request field in DCI format 0_2. Alternatively, when the supplementaryUplink in the higher-layer signaling ServingCellConfig is configured, the UE can interpret the value of the higher-layer signaling srs-RequestDCI-0-2 as having one less than the length of the SRS request field in DCI format 0_2.

[0433] When the supplementaryUplink in the higher-layer signaling ServingCellConfig is not configured, the UE can configure and interpret the bit length of the SRS request field according to the following configuration settings of srs-RequestDCI-0-2. Of course, this is not limited to the following examples. When the higher-layer signaling srs-RequestDCI-0-2 is not configured, the UE can treat the length of the SRS request field in DCI format 0_2 as zero bits.

[0434] - When the SRS-RequestDCI-0-2, which is used as higher-layer signaling, is not configured to have a value of 1, the UE can treat the SRS request field in DCI format 0_2 as a single bit. This single bit can indicate one of the two values ​​in Table 28, or one of the first two values ​​in Table 28.

[0435] - When the higher-layer signaling srs-RequestDCI-0-2 is configured to have a value of 2, the UE can treat the SRS request field in DCI format 0_2 as two bits, and the corresponding two bits can indicate one of all the rows in Table 28 below.

[0436] When the supplementaryUplink in the higher-layer signaling ServingCellConfig is configured, the UE can consider an extra bit in the SRS request field starting from the first position, and this extra bit can indicate non-SUL or SUL. In this case, even if the supplementaryUplink in the higher-layer signaling ServingCellConfig is configured, the UE can still treat the bit length of the SRS request field in DCI format 0_2 as zero when the higher-layer signaling srs-RequestDCI-0-2 is not configured.

[0437] When the supplementaryUplink in the higher-layer signaling ServingCellConfig is not configured, the UE can interpret the value of the higher-layer signaling srs-RequestDCI-1-2 as the length of the SRS request field in DCI format 1_2. Alternatively, when the supplementaryUplink in the higher-layer signaling ServingCellConfig is configured, the UE can interpret the value of the higher-layer signaling srs-RequestDCI-1-2 as one less than the length of the SRS request field in DCI format 1_2.

[0438] When the supplementaryUplink in the higher-layer signaling ServingCellConfig is not configured, the UE can configure and interpret the bit length of the SRS request field according to the following configuration settings of srs-RequestDCI-1-2. Of course, this is not limited to the following examples.

[0439] - When the higher-layer signaling srs-RequestDCI-1-2 is not configured, the UE can treat the length of the SRS request field in DCI format 1_2 as zero bits.

[0440] - When the higher-layer signaling srs-RequestDCI-1-2 is configured to have a value of 1, the UE can treat the SRS request field in DCI format 1_2 as a single bit. This single bit can indicate one of the two values ​​in Table 29, or one of the first two values ​​in Table 28.

[0441] When the higher-layer signaling srs-RequestDCI-1-2 is configured to have a value of 2, the UE can treat the SRS request field in DCI format 1_2 as two bits. These two bits can indicate one of all rows in Table 28.

[0442] When the supplementaryUplink in the higher-layer signaling ServingCellConfig is configured, the UE can consider an extra bit in the SRS request field starting from the first position, and this extra bit can indicate non-SUL or SUL. In this case, even if the supplementaryUplink in the higher-layer signaling ServingCellConfig is configured, the UE can still treat the bit length of the SRS request field in DCI format 1_2 as zero when the higher-layer signaling srs-RequestDCI-1-2 is not configured.

[0443] [Table 28]

[0444]

[0445]

[0446]

[0447] [Table 29]

[0448]

[0449] When an aperiodic SRS resource set is configured (e.g., when the RRC parameter "resourceType" in the SRS resource set is aperiodic), the associated CSI-RS can be indicated via the SRS request field in DCI formats 0_1, 1_1, 0_2, or 1_2. However, in the case of DCI formats 0_2 or 1_2, the associated CSI-RS can only be indicated via the SRS request field if the SRS request field exists in the DCI. In this case, the UE can receive the configuration of the higher-layer signaling aperiodicSRS-ResourceTrigger, AperiodicSRS-ResourceTriggerList, srs-ResourceSetId, and csi-RS in the SRS resource set from the base station. The UE can define one or more SRS resource sets associated with the SRS request field in DCI formats 0_1 and 1_1 through entries in the higher-layer signaling srs-ResourceSetToAddModList. Additionally, the UE can define one or more SRS resource sets associated with the SRS request field in DCI formats 0_2 and 1_2 through entries in the higher-layer signaling srs-ResourceSetToAddModListDCI-0-2.

[0450] When a UE receives from a base station via higher-layer signaling an SRS resource set configured for non-codebook use, where the RRC parameter `resourceType` within the SRS resource set is aperiodic, and the associated CSI-RS configured in the same SRS resource set is also aperiodic NZP CSI-RS, the UE can receive a trigger command for aperiodic associated CSI-RS from the base station via the SRS request field in the DCI. The UE can interpret the trigger command for aperiodic associated CSI-RS from the base station using a combination of at least one of the following. Of course, the examples are not limited to the following.

[0451] - In cases where the SRS request field in DCI format 0_1 ​​or 1_1 is not "00" and the corresponding DCI is not used for cross-carrier scheduling or cross-BWP scheduling, the UE can expect an indication of the existence of aperiodic associated CSI-RS. For example, when an SRS resource set configured for non-codebook use is associated with an SRS request field value of "01" (e.g., when the value of the higher-layer signaling aperiodicSRS-ResourceTrigger is configured to have a value of 1 or an entry in aperiodicSRS-ResourceTriggerList is configured to have a value of 1), and when the UE receives an indication of "01" from the base station via the SRS request field of DCI format 0_1 ​​or 1_1, the UE can interpret that aperiodic associated CSI-RS has been triggered by the base station and sent to the UE, and can understand that aperiodic associated CSI-RS exists.

[0452] - If the last two digits of the SRS request field in DCI format 0_1 ​​or 1_1 are not "00" and the corresponding DCI is not used for cross-carrier scheduling or cross-BWP scheduling, the UE can expect an indication of the presence of aperiodic associated CSI-RS. When the UE is not configured with supplementaryUplink in the higher-layer signaling ServingCellConfig, the UE can assume that the SRS request field in DCI format 0_1 ​​or 1_1 is two-digit. When the UE is configured with supplementaryUplink in the higher-layer signaling ServingCellConfig, the UE can assume that the SRS request field in DCI format 0_1 ​​or 1_1 is three-digit. When the SRS request field is three-digit, the UE can interpret the first digit as indicating non-SUL or SUL, and can interpret the next two digits based on Table 28.

[0453] - Depending on the configuration value of the higher-layer signaling srs-RequestDCI-0-2 or srs-RequestDCI-1-2, the UE can interpret the SRS request field in DCI format 0_2 or 1_2 as a combination corresponding to at least one of the following.

[0454] --If the UE receives an srs-RequestDCI-0-2 or srs-RequestDCI-1-2 configured as 1, and does not receive a supplementaryUplink configured in the higher-layer signaling ServingCellConfig, the UE can assume that the SRS request field in DCI format 0_2 or 1_2 is a single bit. Additionally, if a single bit in the SRS request field is not "0" and the corresponding DCI is not used for cross-carrier or cross-BWP scheduling, the UE can expect an indication of the presence of aperiodic associated CSI-RS. For example, when an SRS resource set configured for non-codebook use is associated with an SRS request field value "1" (e.g., when the higher-layer signaling aperiodicSRS-ResourceTrigger is configured to have a value of 1 or when an entry in the aperiodicSRS-ResourceTriggerList is configured to have a value of 1), and when the UE receives an indication "1" from the base station via the SRS request field of DCI format 0_2 or 1_2, the UE can interpret that the aperiodic associated CSI-RS has been triggered by the base station and sent to the UE, and can understand that there is an aperiodic associated CSI-RS.

[0455] – When the UE receives an srs-RequestDCI-0-2 or srs-RequestDCI-1-2 configured as 1, and receives a supplementaryUplink configured in the higher-layer signaling ServingCellConfig, the UE can assume that the SRS request field in DCI format 0_2 or 1_2 is two bits. Additionally, if the last bit of the SRS request field is not "0" and the corresponding DCI is not used for cross-carrier or cross-BWP scheduling, the UE can expect an indication of the presence of aperiodic associated CSI-RS. For example, when an SRS resource set configured for non-codebook use is associated with the last bit of an SRS request field having a value of "1" (e.g., when the higher-layer signaling aperiodicSRS-ResourceTrigger is configured to have a value of 1 or when an entry in aperiodicSRS-ResourceTriggerList is configured to have a value of 1), and when the UE receives an indication of "1" for the last bit of the SRS request field in DCI format 0_2 or 1_2 from the base station, the UE can interpret that the aperiodic associated CSI-RS has been triggered by the base station and sent to the UE, and can understand that there is an aperiodic associated CSI-RS.

[0456] -- If the UE receives an SRS-RequestDCI-0-2 or SRS-RequestDCI-1-2 configured as 2, and does not receive a supplementaryUplink configured in the higher-layer signaling ServingCellConfig, the UE can assume that the SRS request field in DCI format 0_2 or 1_2 is two bits. Additionally, if the SRS request field is not "00" and the corresponding DCI is not used for cross-carrier or cross-BWP scheduling, the UE can expect an indication of the presence of aperiodic associated CSI-RS. For example, when an SRS resource set configured for non-codebook use is associated with an SRS request field value “01” (e.g., when the higher-layer signaling aperiodicSRS-ResourceTrigger is configured to have a value of 1 or when an entry in aperiodicSRS-ResourceTriggerList is configured to have a value of 1), and when the UE receives an indication “1” from the base station via the SRS request field in DCI format 0_2 or 01_2, the UE can interpret that the aperiodic associated CSI-RS has been triggered by the base station and sent to the UE, and can understand that there is an aperiodic associated CSI-RS.

[0457] --When the UE receives an srs-RequestDCI-0-2 or srs-RequestDCI-1-2 configured as 2, and receives a supplementaryUplink configured in the higher-layer signaling ServingCellConfig, the UE can assume that the SRS request field in DCI format 0_2 or 1_2 is three bits. Additionally, if the last two bits of the SRS request field are not "00" and the corresponding DCI is not used for cross-carrier scheduling or cross-BWP scheduling, the UE can expect an indication of the presence of aperiodic associated CSI-RS. For example, when an SRS resource set configured for non-codebook use is associated with the last two bits of an SRS request field having a value of "01" (e.g., when the higher-layer signaling aperiodicSRS-ResourceTrigger is configured to have a value of 1 or when an entry in aperiodicSRS-ResourceTriggerList is configured to have a value of 1), and when the UE receives the indication "01" via the last two bits of the SRS request field in DCI format 0_2 or 1_2, the UE can interpret that the aperiodic associated CSI-RS has been triggered by the base station and sent to the UE, and can understand that there is an aperiodic associated CSI-RS.

[0458] Cross-carrier scheduling can be understood as meaning that the scheduled cell for receiving DCI is different from the cell that performs transmission and reception via scheduling. Cross-BWP scheduling can be understood as meaning that the bandwidth portion used for receiving DCI is different from the bandwidth portion used for performing transmission and reception via scheduling.

[0459] In this case, the UE can understand that the aperiodic associated CSI-RS and the DCI that includes the SRS request field that triggered the aperiodic associated CSI-RS are in the same time slot.

[0460] When the UE has already received a DCI 860 in slot 0 that has triggered an aperiodic linked CSI-RS 865, the UE can expect that an aperiodic linked CSI-RS 865 that can be triggered via DCI 860 exists in the same slot 0. Furthermore, even within the same slot 0, the UE can define the location of the aperiodic linked CSI-RS 865 within the time interval between the first symbol in which DCI 860 is transmitted and the last symbol of the corresponding slot 0 (operation 870). If the DCI that triggers the aperiodic linked CSI-RS 885 is repeatedly transmitted (indicated by reference numerals 875 and 880) (e.g., if the two DCIs are repeated PDCCH candidates transmitted in two different search spaces configured with the same searchspacelinkingID), the UE can expect that a corresponding aperiodic linked CSI-RS 885 exists in slot 1 where the corresponding repeated DCI exists. Additionally, the UE can even define the location of the corresponding aperiodic associated CSI-RS 885 within the same time slot 1, which can exist within the time interval from the first symbol of the later DCI 880 in the two repeating DCIs to the last symbol of the corresponding time slot 1 (operation 890).

[0461] If a UE receives an SRS resource set configured for non-codebook use from a base station via higher-layer signaling, the corresponding RRC parameter resourceType in the SRS resource set is aperiodic, and the associated CSI-RS configured in the same SRS resource set is also aperiodic NZP CSI-RS, and if the UE receives the higher-layer signaling minimumSchedulingOffsetK0 configured in the activated downlink bandwidth portion and the value of this configuration is greater than zero, the UE may not expect to receive a scheduling DCI with an SRS request field value of "00".

[0462] When a UE receives from a base station via higher-layer signaling an SRS resource set configured for non-codebook use, an RRC parameter resourceType in the SRS resource set that is aperiodic, and an associated CSI-RS set within the same SRS resource set that is also aperiodic NZP CSI-RS, if the UE receives higher-layer signaling minimumSchedulingOffsetK0 configured in the activated downlink bandwidth portion and the value of this configuration is greater than zero, the UE can perform DCI reception operations based on at least one combination of the following: Of course, the examples are not limited to the following.

[0463] - When the UE receives a DCI format of 0_1 or 1_1, the UE may not expect to receive a value other than "00" for the SRS request field in the received DCI.

[0464] - When the UE receives a DCI format of 0_1 or 1_1, and the UE receives a supplementaryUplink configured in the higher-layer signaling ServingCellConFIG, the UE may not expect the last two digits of the SRS request field of the received DCI to be a value other than "00". When the UE does not receive a supplementaryUplink configured in the higher-layer signaling ServingCellConfig, the UE may not expect to receive a value other than "00" for the two digits of the SRS request field of the received DCI.

[0465] - If the UE receives DCI format 0_2 or 1_2, and if the UE receives srs-RequestDCI-0-2 or srs-RequestDCI-1-2 configured as 1, and does not receive the supplementaryUplink configured in the higher-layer signaling ServingCellConfig, the UE may consider the SRS request field in DCI format 0_2 or 1_2 to be a single bit and may not expect to receive a single bit with a value other than "0".

[0466] - If the UE receives DCI format 0_2 or 1_2, and if the UE receives srs-RequestDCI-0-2 or srs-RequestDCI-1-2 configured as 1, and receives supplementaryUplink configured in the higher-layer signaling ServingCellConfig, then the UE may consider that the SRS request field in DCI format 0_2 or 1_2 is two-digit and may not expect to receive the last bit of the SRS request field with a value other than "0".

[0467] - If the UE receives an SRS request field in DCI format 0_2 or 1_2, and the UE receives an SRS-RequestDCI-0-2 or SRS-RequestDCI-1-2 configured as 2, and does not receive a supplementaryUplink configured in the higher-layer signaling ServingCellConfig, the UE may consider that the SRS request field in DCI format 0_2 or 1_2 is two-digit and may not expect to receive an SRS request field with a value other than "00".

[0468] - If the UE receives DCI format 0_2 or 1_2, and if the UE receives srs-RequestDCI-0-2 or srs-RequestDCI-1-2 configured as 2, and receives supplementaryUplink configured in the higher-layer signaling ServingCellConfig, then the UE may consider that the SRS request field in DCI format 0_2 or 1_2 is three digits and may not expect to receive the last two digits of the SRS request field with a value other than "00".

[0469] When a UE is configured with a non-periodic associated CSI-RS linked to non-periodic SRS resources, all TCI states configured in the cell being scheduled may not expect to receive higher-layer signaling qcl-Type configured as type D. For example, all TCI states in the cell being scheduled may not include QCL-Type D, or it may mean that the UE is operating in FR1.

[0470] For the above operations, the UE can report the corresponding UE capabilities. According to an embodiment, the UE can report UE capabilities indicating support for aperiodic associated CSI-RS. According to an embodiment, the UE can report UE capabilities indicating that the UE can trigger aperiodic associated CSI-RS via DCI formats 0_1, 1_1, 0_2, or 1_2. According to an embodiment, the UE can report UE capabilities indicating support for supplementary uplink. According to an embodiment, the UE can report UE capabilities indicating support for minimumSchedulingOffsetK0.

[0471] <Second Embodiment: Method for Supporting CSI-RS Configured with More Than 32 CSI-RS Ports>

[0472] Embodiments of this disclosure describe a method for a UE to support CSI-RS configured with more than 32 CSI-RS ports. This embodiment can be operated in conjunction with other embodiments.

[0473] Based on Table 7 above, a UE can define up to 32 CSI-RS ports in a single CSI-RS resource. When the base station is able to use more than 32 antenna ports (e.g., 64, 96, or 128 antenna ports), the UE and base station can consider the following two methods to define more than 32 CSI-RS ports required to estimate the downlink channel between the base station and the UE. Of course, this is not limited to the examples below.

[0474] [Method 1-1] Support method based on a single CSI-RS resource

[0475] The UE and base station can define more than 32 CSI-RS ports in a single CSI-RS resource. For example, the base station and UE can include 64, 96, 128, or 256 CSI-RS ports, more than 32 ports, in a single CSI-RS resource. Additionally, the base station and UE can define CSI-RS-ResourceMapping, which is higher-layer signaling and includes RE mapping schemes on time and frequency resources, CDM types, and / or resource quantity density on frequency resources to support 64, 96, 128, or 256 CSI-RS ports.

[0476] When a single CSI-RS resource contains more than 32 CSI-RS ports, fd-CDM2, cdm4-FD2-TD2, and cdm8-FD2-TD4, defined for 32-port CSI-RS, can be used for the CDM type. Additionally, at least one of cdm16-FD4-TD4, cdm32-FD8-TD4, or cdm32-FD4-TD8 can also be used.

[0477] When a single CSI-RS resource contains more than 32 CSI-RS ports, a resource quantity density of 1 or 0.5 can be used on the frequency resource. Alternatively, resource quantity densities of 0.25, 0.125, etc., can also be used. In this case, the resource quantity density values ​​of 1, 0.5, 0.25, and 0.125 on the frequency resource can be understood as representing that the CSI-RS RE mapping is performed once per RB, every 2 RBs, every 4 RBs, or every 8 RBs, respectively.

[0478] - When a single CSI-RS resource contains more than 32 CSI-RS ports (e.g., 256 CSI-RS ports), complete RE mapping may not be possible because the number of REs in an RB is 168.

[0479] [Method 1-2] Support methods based on multiple CSI-RS resources

[0480] Based on multiple CSI-RS resources, the UE and base station can support more than 32 CSI-RS ports. When the number of CSI-RS ports to be represented by multiple CSI-RS resources is Ptot, the number of CSI-RS ports to be represented by the i-th CSI-RS resource is Pi, and there are N CSI-RS resources, P1 + ... + PN = Ptot can be established. In this case, each i-th CSI-RS resource can have the same number of CSI-RS ports, or they can have different numbers of CSI-RS ports. Furthermore, the minimum value of Pi can be 1, 2, 4, 8, 12, 16, 24, or 32. For example, the UE can represent support for 64 CSI-RS ports by using two CSI-RS resources, each containing 32 ports. These two CSI-RS resources can be included in the same CSI-RS resource set, and the CSI-RS resource with the lower index can use ports 3000 to 3031 out of 64 ports, while the CSI-RS resource with the higher index can use ports 3032 to 3063 out of 64 ports. In another example, the UE can represent support for 128 CSI-RS ports by using four CSI-RS resources, each containing 32 ports. These four CSI-RS resources can be included in the same CSI-RS resource set, and the CSI-RS resource with the nth lowest index can use ports 3000+(n-1)*32+1 to 3000+n*32-1.

[0481] When a UE supports more than 32 Ptot CSI-RS ports using multiple CSI-RS resources, the UE can receive configurations for multiple CSI-RS resources from the base station via higher-layer signaling. The UE can also receive configurations of the same or different values ​​for some or all of the higher-layer signaling included in the multiple CSI-RS resources from the base station. The UE can receive higher-layer signaling for each CSI-RS resource in the NZP-CSI-RS-Resource parameters from the base station. Regarding each of the following higher-layer signaling parameters that can be configured in NZP-CSI-RS-Resource (which are the higher-layer signaling parameters that can be identified in Table 6 above), the UE can have the same or different conditions for each of the multiple CSI-RS resources. Of course, this is not limited to the following examples:

[0482] -nzp-CSI-RS-ResourceId: The UE can expect to configure a different ID for each of the multiple CSI-RS resources;

[0483] -powerControlOffset: The UE can expect multiple CSI-RS resources to each have the same powerControlOffset value. Multiple CSI-RS resources with the same powerControlOffset value can be interpreted as indicating that multiple CSI-RS resources and PDSCH may have the same RE power ratio;

[0484] -powerControlOffsetSS: The UE can expect multiple CSI-RS resources to each have the same powerControlOffsetSS value. Multiple CSI-RS resources having the same powerControlOffsetSS value can be interpreted as indicating that multiple CSI-RS resources may have the same RE power ratio with the SSB;

[0485] -scramblingId: The UE can expect multiple CSI-RS resources to each have the same scramblingId value. Multiple CSI-RS resources that each have the same scramblingId value can be understood as indicating that all multiple CSI-RS resources are configured to have the same scrambling ID;

[0486] -periodicityAndOffset: The UE can expect multiple CSI-RS resources to each have the same periodicityAndOffset value. Multiple CSI-RS resources having the same periodicityAndOffset value can be understood as indicating that, in the case of periodic or semi-periodic CSI-RS, they all have the same periodicity and slot offset, or that Ptot CSI-RS ports supported by multiple CSI-RS resources transmit within the same slot. Alternatively, the UE can expect multiple CSI-RS resources to each have the same periodicity value and the same or different slot offset values ​​in their periodicityAndOffset values. For each of the multiple CSI-RS resources, the same periodicity value and the same or different slot offset values ​​can be understood as indicating that, in the case of periodic or semi-persistent CSI-RS, they all have the same periodicity, but the slot locations for CSI-RS port transmissions within each CSI-RS resource may differ. As an alternative approach, the UE can anticipate that the periodicityAndOffset values ​​for each of the multiple CSI-RS resources are unconstrained. This lack of constraint on the periodicity and offset values ​​for each of the multiple CSI-RS resources can be understood as meaning that, in the case of periodic or semi-persistent CSI-RS, there is no constraint on whether the periodicity and slot offset values ​​are identical. Furthermore, the lack of constraint on whether the periodicity and slot offset values ​​are identical can be understood as meaning that when the UE measures the CSI-RS ports included in each CSI-RS resource, it can update information about some of the Ptot CSI-RS ports, without having to update information about all CSI-RS ports simultaneously or within a small timeframe; and / or

[0487] -qcl-InfoPeriodicCSI-RS: The UE can expect multiple CSI-RS resources to each have the same qcl-InfoPeriodicCSI-RS value. The UE can define this parameter (qcl-InfoPeriodicCSI-RS) only for periodic CSI-RS. This parameter can have a value corresponding to TCI-StateId, which can refer to a specific TCI-State or a specific dl-Or-Joint-TCI-State. The UE having the same qcl-InfoPeriodicCSI-RS value for multiple CSI-RS resources can be interpreted as indicating that the UE receives Ptot CSI-RS ports transmitted in similar locations. For example, when the UE has the same qcl-InfoPeriodicCSI-RS value for multiple CSI-RS resources, it can be interpreted as indicating that all Ptot CSI-RS ports are transmitted from TRPs, Radio Units (RUs), or Massive MIMO Units (MMUs) located in the same or similar locations. On the other hand, the fact that the UE has different qcl-InfoPeriodicCSI-RS values ​​for multiple CSI-RS resources can be understood as indicating that the CSI-RS ports contained in each CSI-RS resource are transmitted from TRP, RU or MMU located in different locations.

[0488] Additionally, the UE and base station can define CSI-RS-ResourceMapping (which is the higher-layer signaling described in Table 6 above) in the form of detailed parameters as shown in Table 30 below, and the UE can receive configuration information for each parameter based on the higher-layer signaling from the base station. Of course, this is not limited to the following examples.

[0489] [Table 30]

[0490]

[0491]

[0492] For each higher-layer signaling in Table 30, the UE can receive the same or different information configured across multiple CSI-RS resources, and the configuration criteria and definitions can be determined based on a combination of at least one of the following. Of course, this is not limited to the examples below.

[0493] The UE can expect that at least one of the nrofPorts, cdm-Type, density, or nrofRB in the CSI-FrequencyOccupation of the higher-level signaling between multiple CSI-RS resources in Table 30 is the same.

[0494] The UE can expect that at least one of the higher-layer signaling frequencyDomainAllocation, firstOFDMSymbolInTimeDomain, firstOFDMSymbolInTimeDomain2, or startingRB among the multiple CSI-RS resources in Table 30 is the same or different.

[0495] Regarding the method by which the UE supports a total of Ptot CSI-RS ports based on the aforementioned multiple CSI-RS resources, the specific CSI-RS resources may include all parameters in Tables 6 and 30. On the other hand, the remaining CSI-RS resources among the multiple CSI-RS resources can be excluded from the configuration, specifically excluding parameters in Tables 6 and 30 that have the same value as the aforementioned specific CSI-RS resources. Exclusion from the configuration can be understood as indicating that the aforementioned specific CSI-RS resources have the same value as the parameters in Tables 6 and 30.

[0496] According to the embodiment, regarding the method in which the UE supports a total of Ptot CSI-RS ports based on the aforementioned multiple CSI-RS resources, the specific CSI-RS resources may include all the parameters in Tables 6 and 30. On the other hand, no parameters are configured for the remaining CSI-RS resources among the multiple CSI-RS resources. Furthermore, based on the aforementioned specific CSI-RS resources, time and frequency RE offsets are configured such that the REs to be mapped to for the remaining Ptot CSI-RS ports, excluding the CSI-RS ports represented by the aforementioned specific CSI-RS resources, can be expressed. The RE offset may be a symbol offset or a slot offset, and depending on the frequency resource, it may be a RE offset or an RB offset.

[0497] The UE can report to the base station indicating that it supports the UE capabilities described in [Method 1-1] and [Method 1-2] above. The base station can configure higher-layer signaling corresponding to the UE capabilities in the UE, or it can support more than 32 CSI-RS ports based on the single or multiple CSI-RS resources described above without specific higher-layer signaling configuration.

[0498] <Third Embodiment: Method for Supporting Associated CSI-RS Configured from More Than 32 CSI-RS Ports>

[0499] The embodiments disclosed herein describe a method when the UE supports associated CSI-RS configured with more than 32 CSI-RS ports. This embodiment can be operated in conjunction with other embodiments.

[0500] When the UE supports associated CSI-RS configured based on [Method 1-1] by more than 32 CSI-RS ports, the UE can receive higher-layer signaling of one associated CSI-RS configured in the SRS-resourceSet shown in Table 31.

[0501] When the UE receives a resourceType configured as non-periodic in the SRS-resourceSet from the base station, the UE can receive the configuration of the associated CSI-RS resource ID from the base station via higher-layer signaling csi-RS.

[0502] When the UE receives the configuration of a semi-permanent or periodic resourceType in the SRS-resourceSet from the base station, the UE can receive the configuration of the associated CSI-RS resource ID from the base station via the higher-layer signaling associatedCSI-RS.

[0503] The UE may assume that, for non-codebook-based transmissions, the higher-layer signaling csi-RS or associated CSI-RS may optionally be present; otherwise, it may assume that the corresponding field (e.g., csi-RS or associated CSI-RS) does not exist. In this case, non-codebook-based transmissions can be understood as indicating that the usage in the SRS-resourceSet (which is higher-layer signaling) is configured for the UE as non-Codebook.

[0504] The UE can expect that the CSI-RS resources configured via CSI-RS (which is a higher-layer signaling) are one of aperiodic, periodic, or semi-permanent CSI-RS resources. The base station can configure one of aperiodic, periodic, or semi-permanent CSI-RS resources for the UE via higher-layer signaling CSI-RS.

[0505] The UE may expect the CSI-RS resource configured via associatedCSI-RS (which is a higher-layer signaling) to be either a periodic or semi-permanent CSI-RS resource, and may not expect it to be an aperiodic CSI-RS resource. The base station may configure either a periodic or semi-permanent CSI-RS resource for the UE via the higher-layer signaling associatedCSI-RS, but cannot configure an aperiodic CSI-RS resource.

[0506] [Table 31]

[0507]

[0508]

[0509] When the UE supports associated CSI-RS configured based on [methods 1-2] by more than 32 CSI-RS ports, the UE can receive higher-layer signaling of associated CSI-RS configured in the SRS resource set by using a combination of at least one of the following methods. This is not limited to the following examples.

[0510] [Method 2-1]

[0511] When the UE receives a resourceType configured as aperiodic in the SRS-ResourceSet from the base station, the UE can receive multiple associated CSI-RS resource IDs configured via the higher-layer signaling csi-RS-List. When the UE receives the configuration of the csi-RS-List, the UE can expect not to receive the configuration of the higher-layer signaling csi-RS, or even if the csi-RS is configured, the UE can expect to ignore its value and use the value configured in the csi-RS-List instead.

[0512] When the UE receives a resourceType configured as semi-persistent or periodic in the SRS-ResourceSet from the base station, the UE can receive multiple associated CSI-RS resource IDs configured via the associatedCSI-RS-List via higher-layer signaling. When the UE receives the configuration of the associatedCSI-RS-List, the UE can expect not to receive the configuration of the associatedCSI-RS via higher-layer signaling, or even if associatedCSI-RS is configured, the UE can expect to ignore its value and instead use the value configured in the associatedCSI-RS-List.

[0513] The UE may assume that in the case of non-codebook-based transmissions and if the number of associated CSI-RS ports exceeds 32, the csi-RS-List or associatedCSI-RS-List (which is higher-layer signaling) may optionally exist; otherwise, it may assume that the corresponding fields (e.g., csi-RS-List or associatedCSI-RS-List) do not exist. In this case, non-codebook-based transmissions can be understood as indicating that the usage in the SRS-resourceSet (which is higher-layer signaling) is configured for the UE as nonCodebook. The name of the above conditions (e.g., non-codebook-based transmissions and the number of associated CSI-RS ports exceeding 32) can be defined as nonCodebook2 as shown in Table 32 below. However, nonCodebook2 is only an example and is used to distinguish it from nonCodebook, which is a condition that can be used when configuring csi-RS or associated CSI-RS. In addition, the actual name of the above conditions may be different from nonCodebook2, such as nonCodebookWithMoreThan32PortCSI-RS. Alternatively, the UE can expect to use the nonCodebook (which is a condition for csi-RS or associated CSI-RS) when configuring the csi-RS-List or associated CSI-RS-List.

[0514] The UE can expect that, for the purpose within the SRS-ResourceSet configured as nonCodebook and the number of ports associated with CSI-RS is 32 or less, the configuration condition nonCodebook for CSI-RS and associated CSI-RS may optionally exist.

[0515] The UE can consider the value of maxNumAssCSI-RSRes to be 2, 3, or 4, which is the maximum number of CSI-RS resources that the csi-RS-List and associatedCSI-RS-List can contain. The same value of maxNumAssCSI-RSRes can be applied to both the csi-RS-List and associatedCSI-RS-List, or individual values ​​can be applied to them. The UE can receive the value of maxNumAssCSI-RSRes from the base station via at least one of higher-layer signaling, MAC-CE signaling, or L1 signaling, or it can use a fixed value defined in the specification. The UE can report the maxNumAssCSI-RSRes value to the base station through UE capabilities.

[0516] The higher-layer signaling structure corresponding to [Method 2-1] can be considered as shown in Table 32 below (the UE can receive its configuration from the base station). Of course, this is not limited to the following examples.

[0517] [Table 32]

[0518]

[0519]

[0520] [Method 2-2]

[0521] When a UE receives a resourceType configured as a non-periodic type from an SRS-resourceSet from a base station, the UE can receive a configuration of a CSI-RS resource set from the base station via higher-layer signaling csi-RS-Set. Additionally, the UE can treat one or more CSI-RS resources in the CSI-RS resource set as associated CSI-RS resources. When the UE receives the configuration of the csi-RS-Set, the UE can expect not to receive the higher-layer signaling csi-RS, or even if csi-RS is configured, the UE can expect to ignore its value and instead use the value configured in the csi-RS-Set.

[0522] When a UE receives a resourceType configured as semi-persistent or periodic in an SRS-ResourceSet from a base station, the UE can receive a CSI-RS resource set configured via higher-layer signaling associatedCSI-RS-Set from the base station, and can consider all CSI-RS resources in one or more CSI-RS resources within the corresponding CSI-RS resource set as associated CSI-RS resources. When the UE receives the configuration of associatedCSI-RS-Set, the UE can expect not to receive the configuration of associatedCSI-RS in the higher-layer signaling, or even if associatedCSI-RS is configured, the UE can expect to ignore its value and instead use the value configured in associatedCSI-RS-Set.

[0523] The UE may assume that in the case of non-codebook-based transmissions and if the number of associated CSI-RS ports exceeds 32, the csi-RS-Set or associatedCSI-RS-Set (which is higher-layer signaling) may optionally exist; otherwise, the corresponding field (e.g., csi-RS-Set or associatedCSI-RS-Set) may not exist. In this case, non-codebook-based transmissions can be understood as indicating that the usage in the SRS-resourceSet (which is higher-layer signaling) is configured for the UE as nonCodebook. The name of the above conditions (e.g., non-codebook-based transmissions and the number of associated CSI-RS ports exceeding 32) can be defined as nonCodebook2 as shown in Table 33 below. However, nonCodebook2 is only an example and is used to distinguish it from nonCodebook, which is a condition that can be used when configuring csi-RS or associated CSI-RS. In addition, the actual name of the above conditions may be different from nonCodebook2, such as nonCodebookWithMoreThan32PortCSI-RS. Alternatively, the UE can expect to use the nonCodebook (which is a condition for csi-RS or associated CSI-RS) when configuring csi-RS-Set or associated CSI-RS-Set.

[0524] The UE can expect that, for the purpose of the SRS-ResourceSet to be configured as nonCodebook and the number of ports associated with the CSI-RS to be 32 or less, the configuration condition nonCodebook for the CSI-RS and associated CSI-RS may be optional.

[0525] The higher-layer signaling structure corresponding to [Method 2-2] can be considered as shown in Table 33 below (the UE can receive its configuration from the base station). Of course, this is not limited to the following examples.

[0526] [Table 33]

[0527]

[0528]

[0529] [Method 2-3]

[0530] When the UE receives a resourceType configured as non-periodic in the SRS-resourceSet from the base station, the UE can receive the configuration of a CSI-RS resource from the base station via the higher-layer signaling csi-RS. Additionally, when the number of ports associated with CSI-RS exceeds 32, the UE can also receive the configuration of one or more associated CSI-RS resource IDs from the base station via the higher-layer signaling csi-RS-List. When the UE receives the higher-layer signaling csi-RS and csi-RS-List from the base station, the UE can consider one or more CSI-RS resources configured via csi-RS and csi-RS-List as associated CSI-RS.

[0531] When a UE receives a resourceType configured as semi-persistent or periodic in the SRS-ResourceSet from the base station, the UE can receive the configuration of a CSI-RS resource from the base station via the higher-layer signaling associatedCSI-RS. Additionally, when the number of ports associated with CSI-RS exceeds 32, the UE can receive the configuration of one or more additional associated CSI-RS resource IDs from the base station via the higher-layer signaling associatedCSI-RS-List. When the UE receives the configurations of both associatedCSI-RS and associatedCSI-RS-List from the base station, the UE can consider one or more CSI-RS resources configured via associatedCSI-RS and associatedCSI-RS-List as associated CSI-RS.

[0532] The UE may assume that in the case of non-codebook-based transmissions and if the number of associated CSI-RS ports exceeds 32, the csi-RS-List or associatedCSI-RS-List (which is higher-layer signaling) may optionally exist; otherwise, the corresponding field (e.g., csi-RS-List or associatedCSI-RS-List) may not exist. In this case, non-codebook-based transmissions can be understood as indicating that the UE's purpose is configured as "nonCodebook" in the SRS resource set, where the purpose is higher-layer signaling. The name of the above conditions (e.g., non-codebook-based transmissions and the number of associated CSI-RS ports exceeding 32) can be defined as nonCodebook2 as shown in Table 32 below. However, nonCodebook2 is only an example and is used to distinguish it from nonCodebook, which is a condition that can be used when configuring csi-RS or associated CSI-RS. In addition, the actual name of the above conditions may be different from nonCodebook2, such as nonCodebookWithMoreThan32PortCSI-RS. Alternatively, the UE can expect to use the nonCodebook (which is a condition for csi-RS or associated CSI-RS) when configuring the csi-RS-List or associated CSI-RS-List.

[0533] The UE can expect that, for the purpose of the SRS-ResourceSet to be configured as nonCodebook and the number of ports associated with the CSI-RS to be 32 or less, the configuration condition nonCodebook for the CSI-RS and associated CSI-RS may be optional.

[0534] The UE can consider the value of maxNumAssCSI-RSRes to be 2 or 3, which is the maximum number of CSI-RS resources that the csi-RS-List and associatedCSI-RS-List can contain. The same value of maxNumAssCSI-RSRes can be applied to both the csi-RS-List and associatedCSI-RS-List, or individual values ​​can be applied to them. The UE can receive the value of maxNumAssCSI-RSRes from the base station via at least one of higher-layer signaling, MAC-CE signaling, or L1 signaling, or it can use a fixed value defined in the specification. The UE can report the maxNumAssCSI-RSRes value to the base station through its UE capabilities.

[0535] The higher-layer signaling structure corresponding to [Methods 2-3] can be considered as shown in Table 34 below (the UE can receive its configuration from the base station). Of course, this is not limited to the following examples.

[0536] [Table 34]

[0537]

[0538]

[0539] [Methods 2-4]

[0540] When a UE receives a resourceType configured as aperiodic from an SRS-resourceSet from a base station, the UE can receive a CSI-RS resource from the base station via higher-layer signaling CSI-RS. When a UE receives a configuration of associated CSI-RS with 32 or fewer ports from a base station, the UE can expect that the CSI-RS resources configurable via CSI-RS include 32 or fewer ports and can consider the configured CSI-RS resources as associated CSI-RS. When a UE receives a configuration of associated CSI-RS with more than 32 ports from a base station, the UE can expect that all CSI-RS resources in the CSI-RS resource set, including those configurable via CSI-RS, are configured as associated CSI-RS.

[0541] When a UE receives a resourceType configured as semi-persistent or periodic from an SRS-resourceSet via a base station, the UE can receive a configuration for a CSI-RS resource from the base station via higher-layer signaling associatedCSI-RS. When the UE receives a configuration for an associated CSI-RS with 32 or fewer ports from the base station, the UE can expect that the CSI-RS resources that can be configured via associatedCSI-RS include 32 or fewer ports and can consider the configured CSI-RS resources as associated CSI-RS. When the UE receives a configuration for an associated CSI-RS with more than 32 ports from the base station, the UE can expect that all CSI-RS resources in the CSI-RS resource set, including those that can be configured via associatedCSI-RS, are configured as associated CSI-RS.

[0542] In this scenario, the UE can receive information from the base station via at least one of higher-layer signaling, MAC-CE signaling, or L1 signaling indicating whether the associated CSI-RS (whose configuration the UE has received) includes 32, fewer, or more than 32 ports, or it can implicitly indicate this based on the configuration status of a CSI-RS resource set that includes configured CSI-RS resources. For example, the UE can receive specific higher-layer signaling configured in the CSI-RS resource set such that one or more CSI-RS resources in the CSI-RS resource set are considered to represent more than 32 ports. Additionally, each CSI-RS resource can be considered insufficient to represent a single CSI-RS. When the UE is implicitly indicated, based on the configuration status of the CSI-RS resource set including CSI-RS resources configured via CSI-RS or associated CSI-RS, whether the number of ports in the associated CSI-RS is less than or equal to 32 or greater than 32, the UE may make a determination based on at least one of the following: the number of CSI-RS resources included in the CSI-RS resource set, the total number of CSI-RS ports that can be calculated across all CSI-RS resources, whether a higher-layer signaling CMR group has been configured, or whether the CSI-RS resource set is associated with a CSI-ReportConfig in which the codebookType is configured for Type-II coherent joint transmission.

[0543] For example, if the total number of CSI-RS ports calculated across all CSI-RS resources in a CSI-RS resource set exceeds 32, and a higher-layer signaling CMR group is not configured, and the CSI-RS resource set is not associated with a CSI-ReportConfig in which the codebookType is configured for Type-II coherent joint transmission, the UE may consider that all CSI-RS resources in the CSI-RS resource set are used to represent more than 32 ports, and each CSI-RS resource cannot represent a single CSI-RS. These conditions may be included in the higher-layer signaling CSI-RS, or in the non-Codebook, which is a condition for the configuration of associated CSI-RS.

[0544] [Methods 2-5]

[0545] The UE can receive information from the base station indicating a combination of at least one of [Method 2-1] to [Method 2-4] via a combination of at least one of higher-layer signaling, MAC-CE signaling, or L1 signaling, or it can follow a method defined in the specification. For example, the UE can receive a configuration of associated CSI-RS including more than 32 ports according to [Method 2-1] defined in the specification. In another example, the UE can be configured via higher-layer signaling using one of [Method 2-1], [Method 2-3], or [Method 2-4], and can receive an associated CSI-RS configuration including more than 32 ports according to the configured method.

[0546] The UE can report to the base station via its UE capabilities whether it can support a combination of at least one of [Method 2-1] to [Method 2-5]. In this case, when the UE reports that it can support a specific method, it can be understood as indicating that only that specific method is supported among the multiple methods, while the other methods are not supported. For example, the UE can report to the base station one of [Method 2-1] and [Method 2-3]. When the UE reports that [Method 2-1] is supported, reporting that [Method 2-1] is supported may automatically mean that the UE cannot support [Method 2-3].

[0547] The UE can apply a combination of at least one of [Method 2-1] to [Method 2-5] based on the temporal behavior of the SRS resource set. For example, the UE can apply [Method 2-1] for an SRS resource set whose resourceType is configured as aperiodic. Alternatively, in the case of periodic or semi-persistent SRS, the UE may not apply any of [Method 2-1] to [Method 2-5] and can follow the conventional approach. Following the conventional approach can be understood as meaning that, when considering associated CSI-RS, only one CSI-RS resource is configured, and only that one CSI-RS resource is considered as associated CSI-RS. For example, when following the above approach, if the resourceType is configured as a periodic or semi-persistent SRS resource set, the UE may not be able to be configured with associated CSI-RS including more than 32 ports.

[0548] <Fourth Embodiment: Receive Position When Triggering Aperiodic Associated CSI-RS Configured with More Than 32 CSI-RS Ports>

[0549] The embodiments of this disclosure describe the reception location of aperiodic associated CSI-RS when the UE receives a trigger signal for aperiodic associated CSI-RS from a base station. This aperiodic associated CSI-RS includes more than 32 CSI-RS ports that can be configured by multiple CSI-RS resources. In this case, the UE can follow a combination of at least one of [Method 2-1] to [Method 2-5] regarding the method for supporting aperiodic associated CSI-RS including more than 32 CSI-RS ports. This embodiment can be operated in conjunction with other embodiments.

[0550] If an aperiodic associated CSI-RS, comprising more than 32 CSI-RS ports that can be configured by multiple CSI-RS resources, is triggered via DCI format 0_1, 0_2, 1_1, or 1_2, the UE can define the location of the aperiodic associated CSI-RS as follows. Of course, this is not limited to the examples below.

[0551] Figure 9 The possible locations where non-periodic correlated CSI-RS may exist according to embodiments of the present disclosure are shown.

[0552] [Method 3-1]

[0553] When a UE receives a DCI format 0_1, 0_2, 1_1, or 1_2 (indicated by reference numeral 900), the UE can expect to receive all of the non-periodic associated CSI-RS, including more than 32 CSI-RS ports, within the time slot where the DCI has been received. These 32 CSI-RS ports can be comprised of multiple CSI-RS resources. For example, when the UE has already received DCI 900 in time slot 0, the UE can consider the interval from the first symbol of the received DCI to the last symbol of the corresponding time slot (indicated by reference numeral 903) as a region where it can receive non-periodic associated CSI-RS, including more than 32 CSI-RS ports that can be configured by multiple CSI-RS resources. When the non-periodic associated CSI-RS is configured by two CSI-RS resources 901 and 902 (each resource containing 32 ports (64 ports in total)), the UE can expect to receive two CSI-RS resources within interval 903. In this scenario, downlink and uplink switching may not occur between the two CSI-RS resource transmissions.

[0554] [Method 3-2]

[0555] When a UE receives a DCI format 0_1, 0_2, 1_1, or 1_2 (indicated by reference numeral 905), the UE can expect to receive all of the non-periodic associated CSI-RS, including more than 32 CSI-RS ports configurable by multiple CSI-RS resources, within the time slot in which the DCI was received and in the time slots following the time slot in which the DCI was received (e.g., within two consecutive time slots including the time slot in which the DCI was received). For example, when the UE receives DCI 905 in time slot 0, the UE can consider the interval from the first symbol of the received DCI to the last symbol of the time slot following the time slot in which the corresponding DCI is located (indicated by reference numeral 910) as the area in which non-periodic associated CSI-RS, including more than 32 CSI-RS ports configurable by multiple CSI-RS resources, can be received. When aperiodic associated CSI-RS is configured by four CSI-RS resources 906, 907, 908, and 909 (each resource containing 32 ports (128 ports in total)), the UE can expect to receive two CSI-RS resources within time slot 910. In this case, downlink and uplink handover may not occur between each CSI-RS resource transmission. In this scenario, the UE can expect that the first CSI-RS resource received by the UE among the multiple CSI-RS resources configured with associated CSI-RS exists in the same time slot as the time slot in which the DCI is received. Alternatively, the UE can report the number of CSI-RS resources that can exist in the same time slot as the time slot in which the DCI is received among the multiple CSI-RS resources including the associated CSI-RS resources via UE capability.

[0556] The UE can receive information from the base station using a combination of at least one of [Method 3-1] and [Method 3-2], either by using higher-layer signaling, MAC-CE signaling, or L1 signaling, or by following a method defined in the specification.

[0557] The UE can define a combination of at least one of [Method 3-1] and [Method 3-2] based on the total number of ports included in the associated CSI-RS and the number of CSI-RS resources. For example, when the number of associated CSI-RS resources is 2, the UE can follow [Method 3-1], while when the number of associated CSI-RS resources is 3 or 4, the UE can follow [Method 3-2]. For example, when the total number of ports included in the associated CSI-RS is 64 or less, the UE can follow [Method 3-1], while when the total number of ports included in the associated CSI-RS is more than 64, the UE can follow [Method 3-2].

[0558] The UE can report to the base station whether it supports a combination of at least one of [Method 3-1] and [Method 3-2]. In this case, when the UE reports that it can support a specific method, it can be understood as indicating that only that specific method is supported among multiple methods, while the other methods are not supported. For example, the UE can report to the base station one of [Method 3-1] and [Method 3-3]. When the UE reports that [Method 3-1] is supported, reporting that [Method 2-1] is supported may automatically mean that the UE cannot support [Method 2-3].

[0559] When a UE is configured with non-periodic associated CSI-RS including more than 32 CSI-RS ports that can be configured by multiple CSI-RS resources, and the SRS resources in the SRS resource set that are configured for non-codebook purposes are non-periodic SRS, the UE may not expect the time interval to be less than The time interval is a symbol ranging from the last symbol of the last received CSI-RS resource among one or more CSI-RS resources configured with associated CSI-RS to the transmission time point of one or more SRS resources for which precoding has been applied.

[0560] here, It can be a value representing the subcarrier spacing, and "d" can be defined by considering a combination of at least one of the following:

[0561] -d can indicate a specific number of symbols (e.g., 3 symbols) regardless of the subcarrier spacing;

[0562] -d can represent the specific number of symbols associated with a subcarrier interval. This can also have different values ​​for each subcarrier interval (e.g., d=0 when μ=0; d=2 when μ=1; d=4 when μ=2; d=8 when μ=3; d=16 when μ=5; d=32 when μ=6), and this value can vary with the specific subcarrier (e.g., the value of d is...). Below 120 kHz, d=2; at 480 kHz and 960 kHz, d=8 and d=16, respectively.

[0563] -d can represent a specific absolute time (e.g., a value in milliseconds) independent of the subcarrier spacing (e.g., 1 ms); and / or

[0564] The value of -d may vary depending on the number of CSI-RS resources and / or the total number of ports included in the associated CSI-RS. For example, when the total number of ports in the associated CSI-RS is 64, the value of d can be 10, while when the total number of ports is 128, the value of d can be 30.

[0565] For example, when the associated CSI-RS is an aperiodic CSI-RS and the SRS resources in the SRS resource set configured for non-codebook use are also aperiodic SRS, the UE can estimate the channel based on the associated CSI-RS and compute a precoder to apply the precoding to the SRS resources and use time corresponding to at least 42 symbols before transmission.

[0566] The UE can receive the definition of "d" from the base station by using at least one of the following combinations: higher-layer signaling, MAC-CE signaling, or L1 signaling, or by using a value that is fixedly defined in the specification.

[0567] The UE can report the definition of "d" to the base station through UE capabilities. Depending on the definition of "d", the UE capability can report a different value for each subcarrier interval, or it can be defined such that its value varies with a specific subcarrier, or it can be considered independent of the subcarrier.

[0568] When some symbols configured for the UE via higher-layer signaling tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated are UL symbols, the UE may not receive CSI-RS that overlap with the UL symbols configured in the time slot. When the associated CSI-RS is configured by multiple CSI-RS resources and includes more than 32 ports, and / or when at least one CSI-RS resource including the associated CSI-RS overlaps with a configured UL symbol, the UE can expect not to receive the remaining CSI-RS resources configured with the corresponding associated CSI-RS. For example, the UE may not expect to receive only some of the multiple CSI-RS resources configured with the associated CSI-RS. For operations that prevent the reception of all CSI-RS resources due to overlap with UL symbols, the UE may apply the operation if the associated CSI-RS is at least periodic or semi-permanent, but may not apply the operation if the associated CSI-RS is non-periodic. Additionally, for operations that cannot receive all CSI-RS resources due to overlap with UL symbols, the UE can apply this operation regardless of whether the associated CSI-RS is periodic, semi-persistent, or aperiodic.

[0569] When the aforementioned aperiodic associated CSI-RS includes multiple CSI-RS resources and the total number of CSI-RS ports is greater than 32 (e.g., 48, 64, or 128), the UE may consider a combination of at least one of [Method 3-1] or [Method 3-2] to determine the reception location of the multiple CSI-RS resources. When the UE follows [Method 2-1] or [Method 2-3] regarding an aperiodic associated CSI-RS support scheme including more than 32 CSI-RS ports (e.g., the UE receives one or more CSI-RS resources in an SRS resource set configured via higher-layer signaling for non-Codebook use to facilitate aperiodic associated CSI-RS support), the UE may further consider the following details. The UE may consider at least one of the following. Of course, the examples are not limited to the following examples.

[0570] - In the absence of a slot offset configuration (which is higher-layer signaling) received by the UE, for each of one or more CSI-RS resources configured for non-Codebook SRS resource sets, if the UE receives a trigger for reception of an aperiodic associated CSI-RS (the total number of CSI-RS ports of which is greater than 32 (e.g., 48, 64, or 128)) via DCI, the reception location of that aperiodic associated CSI-RS may be restricted to the same slot as the DCI. In this case, reception of an aperiodic associated CSI-RS can be understood as reception of all CSI-RS resources in one or more CSI-RS resources. In this case, the UE can expect to receive all CSI-RS resources in one or more CSI-RS resources within the same slot. For example, when each of the N CSI-RS resources configured as aperiodic associated CSI-RS has M CSI-RS ports, the UE can receive a higher-layer signaling density value configured as evenPRB for some of the four CSI-RS resources and oddPRB for the remaining CSI-RS resources. In this case, the value of "N" can be 2, 3, or 4, and the value of "M" can be 16, 24, or 32. For example, regarding the case where N is 4 and M is 32, the UE can be configured as evenPRB for some CSI-RS resources and oddPRB for the remaining CSI-RS resources, as described above.

[0571] - When the UE receives a time slot offset set (which is higher-layer signaling), for one or more CSI-RS resources configured in an SRS resource set configured for non-Codebook use, if the UE receives a trigger for reception of an aperiodic associated CSI-RS (the total number of CSI-RS ports of which is greater than 32 (e.g., 48, 64, or 128)) via DCI, the UE can ignore the time slot offset configured in each CSI-RS resource and expect to receive the aperiodic associated CSI-RS by considering a new time slot offset for each CSI-RS resource. In this case, reception of an aperiodic associated CSI-RS can be understood as receiving all CSI-RS resources in one or more CSI-RS resources. If some of the corresponding CSI-RS resources receive a time slot offset configured as N, the UE can expect the remaining CSI-RS resources to receive a time slot offset configured as (N+1). For example, the UE can expect to receive higher-layer signaling configured to receive all CSI-RS resources in the CSI-RS resource set within two consecutive time slots. The UE can expect to receive some CSI-RS resources with a time slot offset configured as N as described above in the time slot where the DCI for triggering aperiodic associated CSI-RS is received (e.g., the UE can ignore the time slot offset N and treat it as a value of 0). Additionally, the UE can expect to receive some remaining CSI-RS resources with a time slot offset configured as (N+1) in the time slot where the DCI for triggering aperiodic associated CSI-RS is received (e.g., the UE can ignore the time slot offset (N+1) and treat it as a value of 1). For example, when there are N CSI-RS resources (each resource has M CSI-RS ports), the UE can expect N to be 2, 3, or 4, and M to be 16, 24, or 32.

[0572] - When the UE receives a slot offset (which is higher-layer signaling) configuration, for each of one or more CSI-RS resources configured in a non-Codebook SRS resource set, if the UE receives a trigger for reception of an aperiodic associated CSI-RS (where the total number of CSI-RS ports is greater than 32 (e.g., 48, 64, or 128)) via DCI, the UE can expect to receive the aperiodic associated CSI-RS by taking into account the slot offset configured for each CSI-RS resource. In this case, reception of an aperiodic associated CSI-RS can be understood as receiving all CSI-RS resources in one or more CSI-RS resources. In this case, if some of the corresponding CSI-RS resources receive a slot offset configured as N, the UE can expect the remaining CSI-RS resources to receive a slot offset configured as (N+1). For example, the UE can expect to receive higher-layer signaling configured such that all CSI-RS resources are received within two consecutive slots. The UE can anticipate receiving some CSI-RS resources with a time slot offset configured as N, as described above, in time slots N time slots away from the time slot where the DCI used to trigger aperiodic associated CSI-RS is received. Furthermore, the UE can anticipate receiving the remaining CSI-RS resources with a time slot offset configured as (N+1) in time slots (N+1) time slots away from the time slot where the DCI used to trigger aperiodic associated CSI-RS is received. For example, when there are N CSI-RS resources (each resource has M CSI-RS ports), the UE can anticipate that N is 2, 3, or 4, and M is 16, 24, or 32.

[0573] When the aforementioned aperiodic associated CSI-RS includes multiple CSI-RS resources and the total number of CSI-RS ports is greater than 32 (e.g., 48, 64, or 128), the UE may consider a combination of at least one of [Method 3-1] or [Method 3-2] to determine the reception location of the multiple CSI-RS resources. When the UE follows [Method 2-2] to implement an aperiodic associated CSI-RS support scheme including more than 32 CSI-RS ports (e.g., when the UE receives via higher-layer signaling a configuration of a CSI-RS resource set including at least one CSI-RS resource in an SRS resource set configured for non-Codebook use to facilitate aperiodic associated CSI-RS support), the UE may further consider the following details. The UE may consider at least one of these details. Of course, the examples are not limited to the following examples.

[0574] - If the UE does not receive a higher-layer signaling slot offset (e.g., aperiodicTriggeringOffset, aperiodicTriggeringOffset-r16, aperiodicTriggeringOffset-r17, or aperiodicTriggeringOffsetL2-r17) configured in a CSI-RS resource set configured for use as nonCodebook, and does not receive a resource-specific slot offset configured in all CSI-RS resources in the CSI-RS resource set, if the UE receives a trigger for reception of an aperiodic associated CSI-RS (the total number of CSI-RS ports of which is greater than 32 (e.g., 48, 64, or 128)) via DCI, the reception location of that aperiodic associated CSI-RS may be restricted to the same slot as the DCI. In this case, reception of an aperiodic associated CSI-RS can be understood as reception of all CSI-RS resources configured in the CSI-RS resource set. For example, the UE can expect all CSI-RS resources in the CSI-RS resource set to be received in the same time slot. For instance, when each of the N CSI-RS resources in the CSI-RS resource set has M CSI-RS ports, the UE can receive a higher-layer signaling density value configured as evenPRB for some of the four CSI-RS resources and oddPRB for the remaining CSI-RS resources. In this case, the value of "N" can be 2, 3, or 4, and the value of "M" can be 16, 24, or 32. For example, regarding the case where N is 4 and M is 32, the UE can be configured as evenPRB for some CSI-RS resources and oddPRB for the remaining CSI-RS resources, as described above.

[0575] - If the UE receives a higher-layer signaling slot offset configured in a CSI-RS resource set configured for use as non-Codebook in an SRS resource set, and does not receive a resource-specific slot offset configured in all CSI-RS resources in the CSI-RS resource set, and if the UE receives a trigger for reception of an aperiodic associated CSI-RS (the total number of CSI-RS ports of which is greater than 32 (e.g., 48, 64, or 128)) via DCI, the UE can ignore the slot offset configured in the CSI-RS resource set and expect to receive all aperiodic associated CSI-RS in the slot in which the DCI is received. In this case, reception of aperiodic associated CSI-RS can be understood as receiving all CSI-RS resources configured in the CSI-RS resource set. For example, the UE can expect all CSI-RS resources in the CSI-RS resource set to be received in the same slot. For example, when each of the N CSI-RS resources in a CSI-RS resource set has M CSI-RS ports, the UE can receive a higher-layer signaling density value configured as evenPRB for some of the four CSI-RS resources and oddPRB for the remaining CSI-RS resources. In this case, the value of "N" can be 2, 3, or 4, and the value of "M" can be 16, 24, or 32. For example, in the case where N is 4 and M is 32, the UE can be configured as evenPRB for some CSI-RS resources and oddPRB for the remaining CSI-RS resources, as described above.

[0576] - If a UE receives a higher-layer signaling slot offset configured in a CSI-RS resource set configured in an SRS resource set for non-Codebook use, and does not receive a resource-specific slot offset configured in all CSI-RS resources within the CSI-RS resource set, and if the UE receives a trigger via DCI for reception of an aperiodic associated CSI-RS (the total number of CSI-RS ports of which is greater than 32 (e.g., 48, 64, or 128)), the UE can expect to receive all aperiodic associated CSI-RS in a slot separated from the slot in which the DCI used to trigger the aperiodic associated CSI-RS is received by a slot offset configured in the CSI-RS resource set. In this case, reception of aperiodic associated CSI-RS can be understood as receiving all CSI-RS resources configured in the CSI-RS resource set. For example, the UE can expect to receive all CSI-RS resources in the same slot. As an example, when each of the N CSI-RS resources in a CSI-RS resource set has M CSI-RS ports, the UE can receive a higher-layer signaling density value configured as evenPRB for some of the four CSI-RS resources and oddPRB for the remaining CSI-RS resources. In this case, the value of "N" can be 2, 3, or 4, and the value of "M" can be 16, 24, or 32. For example, in the case where N is 4 and M is 32, the UE can be configured as evenPRB for some CSI-RS resources and oddPRB for the remaining CSI-RS resources, as described above.

[0577] - If the UE does not receive a higher-layer signaling slot offset configured in the CSI-RS resource set configured in the SRS resource set for non-Codebook use, and receives a resource-specific slot offset configured in all CSI-RS resources in the CSI-RS resource set, and if the UE receives a trigger for reception of an aperiodic associated CSI-RS (the total number of CSI-RS ports of which is greater than 32 (e.g., 48, 64, or 128)) via DCI, the UE can ignore the slot offset configured in each CSI-RS resource in the CSI-RS resource set and expect to receive the aperiodic associated CSI-RS by considering a new slot offset for each CSI-RS resource. In this case, reception of the aperiodic associated CSI-RS can be understood as receiving all CSI-RS resources configured in the CSI-RS resource set. In this scenario, if some CSI-RS resources in the corresponding CSI-RS resource set receive a slot offset configured as N, the UE can expect the remaining CSI-RS resources to receive a slot offset configured as (N+1). For example, the UE can expect to receive higher-layer signaling configured to receive all CSI-RS resources in the CSI-RS resource set within two consecutive slots. In this case, the UE can expect to receive some CSI-RS resources with a slot offset configured as N as described above in the slot where the DCI for triggering aperiodic associated CSI-RS is received (e.g., the UE can ignore the slot offset N and treat it as 0). Additionally, the UE can expect to receive the remaining CSI-RS resources with a slot offset configured as (N+1) in the slot where the DCI for triggering aperiodic associated CSI-RS is received (e.g., the UE can ignore the slot offset (N+1) and treat it as 1). For example, when there are N CSI-RS resources in the CSI-RS resource set (each resource has M CSI-RS ports), the UE can expect the value of N to be 2, 3 or 4, and the value of M to be 16, 24 or 32.

[0578] - If the UE does not receive a higher-layer signaling slot offset configured in the CSI-RS resource set configured in the SRS resource set for non-Codebook use, and receives a resource-specific slot offset configured in all CSI-RS resources in the CSI-RS resource set, and if the UE receives a trigger for reception of an aperiodic associated CSI-RS (the total number of CSI-RS ports of which is greater than 32 (e.g., 48, 64, or 128)) via DCI, the UE can expect to receive the aperiodic associated CSI-RS by taking into account the slot offset configured in each CSI-RS resource in the CSI-RS resource set. In this case, reception of the aperiodic associated CSI-RS can be understood as receiving all CSI-RS resources configured in the CSI-RS resource set. In this case, if some of the corresponding CSI-RS resources receive a slot offset configured as N, the UE can expect the remaining CSI-RS resources to receive a slot offset configured as (N+1). For example, the UE can expect to receive higher-layer signaling configured to receive all CSI-RS resources in the CSI-RS resource set within two consecutive time slots. In this case, the UE can expect to receive some CSI-RS resources with a time slot offset configured as N, as described above, in time slots N time slots away from the time slot where the DCI for triggering aperiodic associated CSI-RS is received. Furthermore, the UE can expect to receive the remaining CSI-RS resources with a time slot offset configured as (N+1) in time slots (N+1) time slots away from the time slot where the DCI for triggering aperiodic associated CSI-RS is received. For example, when there are N CSI-RS resources in the CSI-RS resource set (each resource has M CSI-RS ports), the UE can expect N to be 2, 3, or 4, and M to be 16, 24, or 32.

[0579] - If the UE has already received both the higher-layer signaling slot offset in the CSI-RS resource set configured in the SRS resource set for non-Codebook use and the resource-specific slot offset configured for all CSI-RS resources in the CSI-RS resource set, and if the UE receives a trigger via DCI for an aperiodic associated CSI-RS (the total number of CSI-RS ports of which is greater than 32 (e.g., 48, 64, or 128)), the UE can ignore the slot offset configured in the CSI-RS resource set and the slot offset configured in each CSI-RS resource in the CSI-RS resource set, and expects to receive the aperiodic associated CSI-RS by considering a new slot offset for each CSI-RS resource. In this case, the reception of the aperiodic associated CSI-RS can be understood as indicating that all CSI-RS resources configured in the CSI-RS resource set have been received. In this scenario, if some CSI-RS resources in the corresponding CSI-RS resource set receive a slot offset configured as N, the UE can expect the remaining CSI-RS resources to receive a slot offset configured as (N+1). For example, the UE can expect to receive higher-layer signaling configured to receive all CSI-RS resources in the CSI-RS resource set within two consecutive slots. In this case, the UE can expect to receive some CSI-RS resources with a slot offset configured as N as described above in the slot where the DCI for triggering aperiodic associated CSI-RS is received (e.g., the UE can ignore the slot offset N and treat it as zero). Additionally, the UE can expect to receive the remaining CSI-RS resources with a slot offset configured as (N+1) in the slot where the DCI for triggering aperiodic associated CSI-RS is received (e.g., the UE can ignore the slot offset (N+1) and treat it as 1). For example, when there are N CSI-RS resources in the CSI-RS resource set (each resource has M CSI-RS ports), the UE can expect the value of N to be 2, 3 or 4, and the value of M to be 16, 24 or 32.

[0580] - If the UE has already received both the higher-layer signaling slot offset and the resource-specific slot offset configured for all CSI-RS resources in the SRS resource set configured for non-Codebook as described above, and if the UE receives a trigger for reception of an aperiodic associated CSI-RS (the total number of CSI-RS ports of which is greater than 32 (e.g., 48, 64, or 128)) via DCI, the UE can expect to receive the aperiodic associated CSI-RS by taking into account the slot offset configured in each CSI-RS resource in the CSI-RS resource set. In this case, reception of the aperiodic associated CSI-RS can be understood as receiving all CSI-RS resources configured in the CSI-RS resource set. In this case, if some CSI-RS resources in the corresponding CSI-RS resources in the CSI-RS resource set receive a slot offset configured as N, the UE can expect the remaining CSI-RS resources to receive a slot offset configured as (N+1). For example, the UE can expect to receive higher-layer signaling configured to receive all CSI-RS resources in the CSI-RS resource set within two consecutive time slots. In this case, the UE can expect to receive some CSI-RS resources with a time slot offset configured as N, as described above, in time slots N time slots away from the time slot where the DCI for triggering aperiodic associated CSI-RS is received. Furthermore, the UE can expect to receive the remaining CSI-RS resources with a time slot offset configured as (N+1) in time slots (N+1) time slots away from the time slot where the DCI for triggering aperiodic associated CSI-RS is received. For example, when there are N CSI-RS resources in the CSI-RS resource set (each resource has M CSI-RS ports), the UE can expect N to be 2, 3, or 4, and M to be 16, 24, or 32.

[0581] As described in [Method 2-1] or [Method 2-3], when the UE receives one or more CSI-RS resources configured to be periodically, semi-periodically, or aperiodically associated with CSI-RS via higher-layer signaling, the UE may expect to configure the following for all CSI-RS resources in one or more CSI-RS resources via higher-layer signaling.

[0582] As described in [Method 2-2], when the UE receives a set of CSI-RS resources via higher-layer signaling, including one or more CSI-RS resources configured as aperiodic associated CSI-RS, the UE can expect to configure the following for all CSI-RS resources in the set of one or more CSI-RS resources via higher-layer signaling. This is not limited to the following examples:

[0583] - Each CSI-RS resource can have the same number of CSI-RS ports;

[0584] - In the case of periodic CSI-RS, qcl-InfoPeriodicCSI-RS can be the same;

[0585] - In the case of non-periodic CSI-RS, when the value of applyIndicatedTCI-State-r18 in CSI-AssociatedReportConfigInfo is perSet-r18 (perSet-r18 can be configured as either first or second, and the TCI state indicated by the first or second applies equally to all CSI-RS resources in the CSI-RS resource set), or when the value of applyIndicatedTCI-State-r18 is perResource-r18, all CSI-RS resources can be configured as either first or second.

[0586] - In the case of non-periodic CSI-RS, when the resourcesForChannel value in CSI-AssociatedReportConfigInfo is nzp-CSI-RS, the qcl-info value in nzp-CSI-RS can have the same value for all CSI-RS resources; and / or

[0587] - The values ​​of powerControlOffset, powerControlOffsetSS, startRB, and nrofRBs for each CSI-RS resource can be exactly the same.

[0588] The embodiments of this disclosure describe the reception location of aperiodic associated CSI-RS when the UE receives a trigger signal for aperiodic associated CSI-RS from a base station. This aperiodic associated CSI-RS includes more than 32 CSI-RS ports that can be configured by multiple CSI-RS resources. In this case, the UE can follow any combination of at least one of [Method 2-1] to [Method 2-5] to support aperiodic associated CSI-RS including more than 32 CSI-RS ports. This embodiment can be operated in conjunction with other embodiments.

[0589] When an aperiodic associated CSI-RS, comprising more than 32 CSI-RS ports that can be configured by multiple CSI-RS resources, is triggered via DCI format 0_1, 0_2, 1_1, or 1_2, the UE can define the location of the aperiodic associated CSI-RS as follows. This is not limited to the examples below.

[0590] Figure 10 Operation of a UE according to an embodiment of this disclosure is illustrated.

[0591] refer to Figure 10 In operation 1000, the UE may transmit UE capabilities to the base station. In this case, the UE capability signaling that can be reported may include a combination of at least one of the following: UE capabilities related to non-codebook-based PUSCH transmission support, UE capabilities related to SRS resource configuration and SRS resource set configuration in which the purpose can be configured as non-codebook, UE capabilities related to associated CSI-RS support, and UE capabilities obtained according to [Methods 2-1] to [Methods 2-5], [Methods 3-1] to [Methods 3-2], or the definition of “d” above. However, operation 1000 may be omitted.

[0592] In operation 1005, the UE can receive higher-layer signaling from the base station based on the reported UE capabilities. Here, the UE can receive higher-layer signaling related to supporting non-codebook-based PUSCH transmission, SRS resource configuration and SRS resource set configuration with the purpose of being configurable as non-codebook, higher-layer signaling related to supporting associated CSI-RS, and higher-layer parameters for at least one combination of the above [methods 2-1] to [methods 2-5], [methods 3-1] to [methods 3-2] or the above "d" related configuration, and can use one of them.

[0593] In operation 1010, the UE can receive a DCI from the base station. The DCI can be in DCI format 1_1, 1_2, 0_1, or 0_2. The UE can trigger an action on the SRS set indicated by the SRS request field in the DCI.

[0594] In operation 1015, the UE can receive associated CSI-RS from the base station. Here, the UE can know how to trigger aperiodic associated CSI-RS via MC-DCI, and / or know where the aperiodic associated CSI-RS exists according to [Methods 2-1] to [Methods 2-5] and [Methods 3-1] to [Methods 3-2].

[0595] In Operation 1020, the UE can estimate the channel between the base station and the UE based on the associated CSI-RS received from the base station and calculate the precoder.

[0596] In Operation 1025, the UE can apply the calculated precoder to one or more SRS resources and send these SRS resources to the base station.

[0597] In Operation 1030, the UE can receive DCI from the base station to schedule non-codebook-based PUSCH transmissions.

[0598] In Operation 1035, the UE can perform non-codebook-based PUSCH transmission by referring to precoding-related scheduling information in the DCI received from the base station.

[0599] The flowcharts above illustrate exemplary methods that can be implemented according to the principles of this disclosure, and various modifications can be made to the methods shown in the flowcharts herein. For example, although shown as a series of operations, the various operations in each diagram may overlap, occur in parallel, occur in different orders, or occur multiple times. In other examples, at least one operation may be omitted or replaced by another operation.

[0600] Figure 11 The operation of a base station according to an embodiment of the present disclosure is illustrated.

[0601] refer to Figure 11 In operation 1100, the base station can receive UE capabilities from the UE. In this case, the UE capability signaling that can be received by the base station may include a combination of at least one of the following: UE capabilities related to non-codebook-based PUSCH transmission support, UE capabilities related to SRS resource configuration and SRS resource set configuration in which the purpose can be configured as non-codebook, UE capabilities related to associated CSI-RS support, and UE capabilities obtained according to [Methods 2-1] to [Methods 2-5], [Methods 3-1] to [Methods 3-2] or the definition of "d" above. However, operation 1100 may be omitted.

[0602] In operation 1105, the base station can receive higher-layer signaling from the base station based on the UE capabilities reported by the UE. Here, the UE can define higher-layer signaling related to supporting non-codebook-based PUSCH transmission, SRS resource configuration and SRS resource set configuration with uses that can be configured as non-codebook, higher-layer signaling related to supporting associated CSI-RS, and higher-layer parameters for at least one combination of the above [methods 2-1] to [methods 2-5], [methods 3-1] to [methods 3-2] or the above "d" related configurations, and can use one of them.

[0603] In operation 1110, the base station can send a DCI to the UE. The DCI can be in DCI format 1_1, 1_2, 0_1, or 0_2.

[0604] In operation 1115, the base station can receive SRS resources sent by the UE.

[0605] In operation 1120, the base station can receive SRS resources sent by the UE and generate precoding information for scheduling non-codebook-based PUSCH transmissions to the UE.

[0606] In operation 1130, the base station can send a PUSCH for scheduling DCI to the UE.

[0607] In Operation 1135, the base station can receive a non-codebook-based PUSCH from the UE.

[0608] The flowcharts above illustrate exemplary methods that can be implemented according to the principles of this disclosure, and various modifications can be made to the methods shown in the flowcharts herein. For example, although shown as a series of operations, the various operations in each diagram may overlap, occur in parallel, occur in different orders, or occur multiple times. In other examples, at least one operation may be omitted or replaced by another operation.

[0609] [UE / Base Station Diagram]

[0610] Figure 12 The structure of a UE in a wireless communication system according to an embodiment of the present disclosure is shown.

[0611] refer to Figure 12 The UE may include a transceiver (referring to the UE receiver 1200 and UE transmitter 1210 as a whole), a memory (not shown), and a UE processor 1205 (or a UE controller or processor). The UE transceivers 1200 and 1210, the memory, and the UE processor 1205 can operate according to the UE communication method described above. The components of the UE are not limited to the examples described above. For example, the UE may include more or fewer components than those described above. Furthermore, the transceivers 1200 and 1210, the memory, and the UE processor 1205 may be implemented as a single chip.

[0612] Transceivers 1200 and 1210 can transmit / receive signals with a base station. Signals may include control information and data. For this purpose, the transceivers may include an RF transmitter (configured to up-convert and amplify the frequency of the transmitted signal), an RF receiver (configured to amplify the received signal with low noise and down-convert its frequency), etc. However, these are only embodiments of transceivers 1200 and 1210, and the components of transceivers 1200 and 1210 are not limited to RF transmitters and RF receivers.

[0613] In addition, transceivers 1200 and 1210 can receive signals via a radio channel, output signals to processor 1205, and transmit signals output from processor 1205 via a radio channel.

[0614] The memory can store programs and data required for the operation of the UE. Additionally, the memory can store control information or data included in signals sent / received by the UE. The memory can include storage media such as ROM, RAM, hard disk, CD-ROM, DVD, or combinations thereof. Furthermore, the memory can include multiple memories, and can store instructions for executing the aforementioned communication methods.

[0615] Furthermore, the UE processor 1205 can control a series of processes, enabling the UE to operate according to the above embodiments. For example, the UE processor 1205 can control the UE's components to receive DCIs configured in two layers, so as to receive multiple PDSCHs simultaneously. The processor may include multiple processors, and the UE processor 1205 can perform operations to control the UE components by executing programs stored in memory.

[0616] Figure 13 The structure of a base station in a wireless communication system according to an embodiment of the present disclosure is shown.

[0617] refer to Figure 13 The base station may include a transceiver, a memory (not shown), and a base station processor 1305 (or a base station controller or processor) representing the base station receiver 1300 and base station transmitter 1310 as a whole. The base station transceivers 1300 and 1310, the memory, and the base station processor 1305 can operate according to the base station communication method described above. However, the components of the base station are not limited to the examples described above. For example, the base station may include more or fewer components than those described above. Furthermore, the transceivers 1300 and 1310, the memory, and the base station processor may be implemented as a single chip.

[0618] Transceivers 1300 and 1310 can transmit / receive signals with the UE. These signals may include control information and data. For this purpose, transceivers 1300 and 1310 may include an RF transmitter (configured to up-convert and amplify the frequency of the transmitted signal), an RF receiver (configured to low-noise amplify the received signal and down-convert its frequency), etc. However, these are only embodiments of transceivers 1300 and 1310, and the components of transceivers 1300 and 1310 are not limited to RF transmitters and RF receivers.

[0619] In addition, transceivers 1300 and 1310 can receive signals via a radio channel, output signals to base station processor 1305, and transmit signals output from base station processor 1305 via a radio channel.

[0620] The memory can store programs and data required for the operation of the base station. Additionally, the memory can store control information or data included in signals transmitted / received by the base station. The memory can include storage media such as ROM, RAM, hard disk, CD-ROM, DVD, or combinations thereof. Furthermore, the memory can include multiple memories, and can store instructions for executing the aforementioned communication methods.

[0621] The base station processor 1305 can control a series of processes that enable the base station to operate as described in the above embodiments. For example, the base station processor 1305 can control the components of the base station to configure a DCI (including allocation information about multiple PDSCHs) configured in two layers and transmit the DCI. The base station processor 1305 may include multiple processors, and the base station processor 1305 can perform operations to control the base station components by executing programs stored in memory.

[0622] The methods disclosed in the claims and / or the methods of the embodiments described in this disclosure may be implemented in hardware, software, or a combination of hardware and software.

[0623] When these methods are implemented in software, a computer-readable storage medium may be provided for storing one or more programs (software modules). The one or more programs stored in the computer-readable storage medium may be configured to be executed by one or more processors within an electronic device. The at least one program includes instructions to cause the electronic device to perform methods as defined in the appended claims and / or as disclosed herein, according to various embodiments of this disclosure.

[0624] These programs (software modules or software) can be stored in non-volatile memory including random access memory and flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), disk storage devices, optical disc-ROM (CD-ROM), digital versatile optical disc (DVD), or other types of optical storage devices, or magnetic tape. Alternatively, any combination of some or all of these can form the memory in which the programs are stored. Furthermore, multiple such memories can be included in an electronic device.

[0625] Additionally, the program can be stored in an attachable storage device that can access the electronic device via a communication network such as the Internet, intranet, local area network (LAN), wide area network (WLAN), and storage area network (SAN), or a combination thereof. Such a storage device can access the electronic device via an external port. Furthermore, a separate storage device on a communication network can access portable electronic devices.

[0626] In the detailed embodiments described above, the elements included in this disclosure are expressed in a singular or plural form according to the presented detailed embodiments. However, for ease of description, the singular or plural form may be appropriately chosen depending on the presented situation, and this disclosure is not limited to elements expressed in a singular or plural form. Thus, an element expressed in a plural form may also include a single element, or an element expressed in a singular form may include multiple elements.

[0627] The embodiments of this disclosure described and illustrated in the specification and drawings are merely specific examples provided to facilitate the explanation of the technical content of the embodiments of this disclosure and to aid in understanding the embodiments of this disclosure, and are not intended to limit the scope of the embodiments of this disclosure. That is, it will be apparent to those skilled in the art that other variations based on the technical concept of this disclosure can be implemented. Furthermore, the corresponding embodiments described above can be combined as needed. For example, a portion of one embodiment of this disclosure can be combined with a portion of another embodiment to operate a base station and a terminal. As an example, a portion of a first embodiment of this disclosure can be combined with a portion of a second embodiment to operate a base station and a terminal. Moreover, although the above embodiments have been described based on an FDD LTE system, other variations based on the technical concept of the embodiments can also be implemented in other communication systems such as TDD LTE and 5G or NR systems.

[0628] In the accompanying drawings which describe the methods of this disclosure, the order described does not always correspond to the order in which the steps of each method are performed, and the order between the steps may be changed or the steps may be performed in parallel.

[0629] In the accompanying drawings which describe the methods of this disclosure, the order described does not always correspond to the order in which the steps of each method are performed, and the order between the steps may be changed or the steps may be performed in parallel.

[0630] Furthermore, in the methods of this disclosure, some or all of the contents of each embodiment can be combined to implement them without departing from the basic spirit and scope of this disclosure.

[0631] Various embodiments of this disclosure have been described above. The foregoing description is for illustrative purposes and is not intended to limit the embodiments of this disclosure to those set forth herein. Those skilled in the art will understand that other specific modifications and changes can be readily made to the form of this disclosure without altering its technical concept or essential characteristics. The scope of this disclosure is defined by the appended claims, not by the foregoing detailed description, and should be construed as including all changes or modifications derived from the meaning and scope of the claims and their equivalents.

[0632] Although this disclosure has been described with reference to various embodiments, various changes and modifications can be made by those skilled in the art. This disclosure is intended to cover such changes and modifications that fall within the scope of the appended claims.

Claims

1. A method performed by a terminal in a wireless communication system, the method comprising: Receive configuration information from the base station regarding a Channel State Information (CSI)-Reference Signal (RS) resource set with more than 32 antenna ports, wherein the CSI-RS resource set includes an aggregation of multiple CSI-RS resources as associated CSI-RS; Receive downlink control information (DCI) from the base station requesting a sounding reference signal (SRS); Receive associated CSI-RS from the base station; SRS is sent to the base station based on DCI; as well as According to SRS, the Physical Uplink Shared Channel (PUSCH) based on a non-codebook is sent to the base station. The number of CSI-RS resources is one of 2, 3 or 4.

2. The method of claim 1, wherein the SRS resource set of the SRS is configured to be used as a non-Codebook.

3. The method of claim 1, wherein the DCI and associated CSI-RS are received in the same time slot.

4. The method of claim 1, wherein the associated CSI-RS is aperiodic CSI-RS, and The SRS is a non-periodic SRS.

5. A method performed by a base station in a wireless communication system, the method comprising: Send configuration information to the terminal about a Channel State Information (CSI)-Reference Signal (RS) resource set with more than 32 antenna ports, wherein the CSI-RS resource set includes an aggregation of multiple CSI-RS resources as associated CSI-RS; Send downlink control information (DCI) to the terminal requesting a sounding reference signal (SRS); Send associated CSI-RS to the terminal; Receive SRS from the terminal based on DCI; as well as According to SRS, the terminal receives the non-codebook-based Physical Uplink Shared Channel (PUSCH). The number of CSI-RS resources is one of 2, 3 or 4.

6. The method of claim 5, wherein the SRS resource set of the SRS is configured to be used as a non-Codebook.

7. The method of claim 5, wherein the DCI and associated CSI-RS are transmitted in the same time slot.

8. The method of claim 5, wherein the associated CSI-RS is aperiodic CSI-RS, and The SRS is a non-periodic SRS.

9. A terminal in a wireless communication system, the terminal comprising: transceiver; as well as At least one processor, coupled to the transceiver and configured to: Receive configuration information from the base station regarding a Channel State Information (CSI)-Reference Signal (RS) resource set with more than 32 antenna ports, wherein the CSI-RS resource set includes an aggregation of multiple CSI-RS resources as associated CSI-RS; Receive downlink control information (DCI) from the base station requesting a sounding reference signal (SRS); Receive associated CSI-RS from the base station; SRS is sent to the base station based on DCI; as well as According to SRS, the Physical Uplink Shared Channel (PUSCH) based on a non-codebook is sent to the base station. The number of CSI-RS resources is one of 2, 3 or 4.

10. The terminal of claim 9, wherein the SRS resource set of the SRS is configured to be used as a non-Codebook.

11. The terminal of claim 9, wherein the DCI and associated CSI-RS are received in the same time slot.

12. The terminal of claim 9, wherein the associated CSI-RS is aperiodic CSI-RS, and The SRS is a non-periodic SRS.

13. A base station in a wireless communication system, the base station comprising: transceiver; as well as At least one processor, coupled to the transceiver and configured to: Send configuration information to the terminal about a Channel State Information (CSI)-Reference Signal (RS) resource set with more than 32 antenna ports, wherein the CSI-RS resource set includes an aggregation of multiple CSI-RS resources as associated CSI-RS; Send downlink control information (DCI) to the terminal requesting a sounding reference signal (SRS); Send associated CSI-RS to the terminal; Receive SRS from the terminal based on DCI; as well as According to SRS, the terminal receives the non-codebook-based Physical Uplink Shared Channel (PUSCH). The number of CSI-RS resources is one of 2, 3 or 4.

14. The base station of claim 13, wherein the SRS resource set of the SRS is configured to be used as a non-Codebook.

15. The base station of claim 13, wherein the DCI and associated CSI-RS are transmitted in the same time slot.

Images