Method by user equipment, apparatus, storage medium, method by base station, and base station

Abstract

A UE may determine a CSI payload by performing omission of part 2 CSI for one or more CSI reports configured to be transmitted in a slot, and transmit the CSI payload on a physical uplink channel within the slot. The omission of the part 2 CSI is performed according to the priority order starting from the lowest priority level. The omission of the part 2 CSI for the priority 0, which is the highest priority, may be performed at a CSI report sub-configuration level for a CSI report n including CSI corresponding to one or more CSI report sub-configurations.

Description

[Revised on 08.04.2025 under Article 91 of the Rules] Methods, devices and storage media by user devices, and methods and base stations by base stations

[0001] This specification relates to wireless communication systems.

[0002] Various devices and technologies, such as machine-to-machine (M2M) communication, machine-type communication (MTC), and smartphones and tablet PCs (personal computers) that require high data transmission rates, are emerging and becoming widespread. Consequently, the amount of data required to be processed on cellular networks is rapidly increasing. To meet this rapidly increasing data processing demand, technologies such as carrier aggregation and cognitive radio are being developed to efficiently utilize more frequency bands, while multi-antenna technology and multi-BS cooperation technology are being developed to increase the data capacity transmitted within a limited frequency range.

[0003] As more and more communication devices demand greater capacity, the need for enhanced mobile broadband (eMBB) communications is emerging, surpassing legacy radio access technology (RAT). Furthermore, massive machine type communication (mMTC), which connects multiple devices and objects to provide diverse services anytime, anywhere, is a key issue to be considered in next-generation communications.

[0004] Additionally, discussions are underway on communication systems designed to accommodate reliability- and latency-sensitive services and user equipment (UE). The introduction of next-generation wireless access technologies is being discussed, including enhanced mobile broadband (eMBB), mMTC, and ultra-reliable and low latency communication (URLLC).

[0005] As the number of services / UEs that a network must support rapidly increases, the need for energy conservation in the network as well as power conservation in the UE is also gradually increasing.

[0006] One technical task of this specification is to provide methods and procedures for network energy conservation.

[0007] Another technical challenge of this specification is to provide channel state information (CSI) reporting used for network energy conservation without mismatch between BS and UE.

[0008] Another technical challenge of this specification is to reduce the decoding complexity of BS for CSI reports.

[0009] Another technical challenge of this specification is to provide methods and procedures to include as much CSI as possible in an uplink channel of limited size.

[0010] The technical tasks that this specification aims to achieve are not limited to the technical tasks mentioned above, and other technical tasks that are not mentioned will be clearly understood by those skilled in the art related to this specification from the detailed description below.

[0011] In one aspect of this specification, a method by a user equipment (UE) is provided.

[0012] In another aspect of the present disclosure, a device is provided. The device includes at least one processor; and at least one memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations for a user equipment (UE).

[0013] In another aspect of the present disclosure, a computer-readable, non-transitory storage medium is provided, wherein the storage medium stores at least one program code comprising instructions that, when executed, cause at least one processor to perform operations for a user equipment (UE).

[0014] The method by the UE, or the operations for the UE, comprises: determining a physical uplink channel within a slot for reporting channel state information (CSI); determining a CSI payload by performing omission of Part 2 CSI for one or more CSI reports configured to be transmitted in the slot; and transmitting the CSI payload on the physical uplink channel within the slot, wherein the omission of Part 2 CSI is performed in priority order starting from the lowest priority level, and based on which the omission of Part 2 CSI for priority 0 is performed, the omission of Part 2 CSI for priority 0 can be performed at a CSI reporting sub-configuration level for CSI reports n that include CSI corresponding to one or more CSI reporting sub-configurations.

[0015] In another aspect of the present specification, a method by a base station (BS) is provided.

[0016] In another aspect of the present disclosure, a base station (BS) is provided. The BS includes at least one processor; and at least one memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations for the BS.

[0017] The method by the BS, or the operations for the BS, comprises: determining a physical uplink channel in a slot for reporting channel state information (CSI); and receiving a CSI payload on the physical uplink channel in the slot, wherein the CSI payload includes CSI after omission of Part 2 CSI for one or more CSI reports scheduled in the slot, wherein the omission of Part 2 CSI is performed in priority order starting from the lowest priority level, and based on which the omission of Part 2 CSI for priority 0 is performed, the omission of Part 2 CSI for priority 0 can be performed at a CSI reporting sub-configuration level for CSI reports n that include CSI corresponding to one or more CSI reporting sub-configurations.

[0018] In each aspect of this specification, the omission of the Part 2 CSI for the priority 0 may be performed, for the CSI report n, starting from the CSI report sub-configuration of a larger sub-configuration index among the CSI report sub-configurations for the CSI report n, in descending order of sub-configuration index, to the CSI report sub-configuration level.

[0019] In each aspect of this specification, the omission of the Part 2 CSI for the priority 0 may be performed in descending order of the CSI report index, starting from the CSI report of the largest CSI report index, for the multiple CSI reports associated with the priority 0.

[0020] In each aspect of this specification, based on the fact that each CSI report associated with priority 0 includes CSI corresponding to at least one CSI reporting sub-configuration, omission of the Part 2 CSI for priority 0 may be performed at the CSI reporting sub-configuration level.

[0021] In each aspect of this specification, the omission of the Part 2 CSI for the priority 0 may be performed at the CSI reporting sub-configuration level for a CSI report that includes CSI for at least one CSI reporting sub-configuration among the multiple CSI reports associated with the priority 0.

[0022] In each aspect of this specification, the omission of the Part 2 CSI for the priority 0 may not be performed for a CSI report that does not include CSI for any CSI report sub-set among the multiple CSI reports associated with the priority 0.

[0023] In each aspect of this specification, the omission of the Part 2 CSI for priority 0 may be performed until a predetermined condition is met.

[0024] In each aspect of this specification, the predetermined condition may include: the size of the CSI payload is less than or equal to the amount of CSI that the physical uplink channel can carry.

[0025] The above problem solving methods are only some of the examples of this specification, and various examples reflecting the technical features of this specification can be derived and understood by a person having ordinary knowledge in the relevant technical field based on the detailed description below.

[0026] According to some implementation(s) of this specification, methods and procedures for energy saving of a network, BS and / or UE may be provided.

[0027] Some implementation(s) of this specification may reduce the likelihood that BS and UE will interpret CSI reports differently for network energy conservation.

[0028] According to some implementation(s) of this specification, the decoding complexity of BS for CSI reports can be reduced.

[0029] Another technical challenge of this specification is to provide methods and procedures that can include as much CSI as possible in an uplink channel of limited size.

[0030] The effects according to this specification are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art related to this specification from the detailed description below.

[0031] To aid in understanding implementations of this specification, the accompanying drawings, which are included as part of the detailed description, provide examples of implementations of this specification and, together with the detailed description, illustrate implementations of this specification:

[0032] Figure 1 illustrates an example of a communication system 1 to which implementations of the present specification are applied;

[0033] FIG. 2 is a block diagram illustrating examples of communication devices capable of performing a method according to the present specification;

[0034] FIG. 3 illustrates another example of a wireless device capable of performing implementation(s) of the present specification;

[0035] FIG. 4 illustrates an example of a frame structure available in a 3rd generation partnership project (3GPP) based wireless communication system;

[0036] Figure 5 illustrates a resource grid of slots;

[0037] Figure 6 shows an example of multiplexing UCI onto PUSCH;

[0038] Figure 7 illustrates the flow of a process related to channel state information (CSI);

[0039] Figure 8 illustrates the priorities of Part 2 CSI;

[0040] Figure 9 illustrates the omission of Part 2 wideband CSI according to legacy rules;

[0041] FIG. 10 illustrates the structure of Part 2 CSI for priority 0 including multi-CSI reporting;

[0042] Figure 11 illustrates CSI omission according to some implementations of this specification;

[0043] FIG. 12 illustrates the flow of CSI report transmission in a UE according to some implementations of the present specification;

[0044] Figure 13 illustrates the flow of receiving CSI reports at a BS according to some implementations of this specification.

[0045] Hereinafter, implementations according to this specification will be described in detail with reference to the attached drawings. The detailed description provided below, together with the attached drawings, is intended to describe exemplary implementations of this specification and is not intended to represent the only possible implementations of this specification. The detailed description below includes specific details to provide a thorough understanding of this specification. However, one of ordinary skill in the art will appreciate that this specification may be practiced without these specific details.

[0046] In some cases, to avoid ambiguity in the concepts of this specification, known structures and devices may be omitted or illustrated in block diagram form focusing on the core functions of each structure and device. Furthermore, identical components are described using the same drawing reference numerals throughout this specification.

[0047] The techniques, devices, and systems described below can be applied to various wireless multiple access systems. Examples of multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and multi-carrier frequency division multiple access (MC-FDMA) systems. CDMA can be implemented in wireless technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented in wireless technologies such as Global System for Mobile communication (GSM), General Packet Radio Service (GPRS), and Enhanced Data Rates for GSM Evolution (EDGE) (i.e., GERAN). OFDMA can be implemented in wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (WiFi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (evolved-UTRA). UTRA is part of UMTS (Universal Mobile Telecommunication System), and 3GPP (3rd Generation Partnership Project) LTE (Long Term Evolution) is a part of E-UMTS that uses E-UTRA.3GPP LTE adopts OFDMA for the downlink (DL) and SC-FDMA for the uplink (UL). LTE-A (LTE-advanced) is an evolved form of 3GPP LTE.

[0048] For convenience of explanation, the following description assumes that this specification applies to 3GPP-based communication systems, such as LTE and NR. However, the technical features of this specification are not limited to this. For example, although the detailed description below is based on a mobile communication system corresponding to a 3GPP LTE / NR system, it can also be applied to any other mobile communication system, except for features specific to 3GPP LTE / NR.

[0049] For terms and technologies used in this specification that are not specifically explained, reference may be made to 3GPP-based standard documents, such as 3GPP TS 36.211, 3GPP TS 36.212, 3GPP TS 36.213, 3GPP TS 36.321, 3GPP TS 36.300 and 3GPP TS 36.331, 3GPP TS 37.213, 3GPP TS 38.211, 3GPP TS 38.212, 3GPP TS 38.213, 3GPP TS 38.214, 3GPP TS 38.300, 3GPP TS 38.304, 3GPP TS 38.331, etc.

[0050] In the examples of this specification described below, the expression "assumes" that a device "assumes" that the entity transmitting the channel transmits the channel in a manner consistent with the "assume." The entity receiving the channel may mean that, under the assumption that the channel was transmitted in a manner consistent with the "assume," the entity receiving the channel receives or decodes the channel in a manner consistent with the "assume."

[0051] In this specification, UE may be fixed or mobile, and includes various devices that communicate with a BS (base station) to transmit and / or receive user data and / or various control information. UE may be called (Terminal Equipment), MS (Mobile Station), MT (Mobile Terminal), UT (User Terminal), SS (Subscribe Station), wireless device, PDA (Personal Digital Assistant), wireless modem, handheld device, etc. In addition, in this specification, BS generally refers to a fixed station that communicates with UE and / or other BS, and exchanges various data and control information with UE and other BS. BS may be called by other terms such as ABS (Advanced Base Station), NB (Node-B), eNB (evolved-NodeB), BTS (Base Transceiver System), Access Point, PS (Processing Server), etc. In particular, the BS in UTRAN is called a Node-B, the BS in E-UTRAN is called an eNB, and the BS in a new radio access technology network is called a gNB. For convenience of explanation, BSs are collectively referred to as BSs below, regardless of the type or version of communication technology.

[0052] In this specification, a node refers to a fixed point that can transmit / receive radio signals by communicating with a UE. Various types of BSs can be used as nodes regardless of their names. For example, BSs, NBs, eNBs, pico-cell eNBs (PeNBs), home eNBs (HeNBs), relays, and repeaters can be nodes. Furthermore, a node may not be a BS. For example, it can be a radio remote head (RRH) or a radio remote unit (RRU). RRHs, RRUs, etc. generally have a lower power level than the BS. Since an RRH or RRU (hereinafter referred to as RRH / RRU) is generally connected to a BS via a dedicated line such as an optical cable, cooperative communication between an RRH / RRU and a BS can be performed more smoothly than cooperative communication between BSs that are generally connected via a wireless line. Each node is equipped with at least one antenna. The antenna may be a physical antenna, an antenna port, a virtual antenna, or an antenna group. A node is also called a point.

[0053] In this specification, a cell refers to a certain geographical area where one or more nodes provide communication services. Therefore, in this specification, communicating with a specific cell may mean communicating with a BS or node that provides communication services to the specific cell. In addition, the downlink / uplink signal of a specific cell refers to a downlink / uplink signal from / to a BS or node that provides communication services to the specific cell. A cell that provides uplink / downlink communication services to a UE is specifically referred to as a serving cell. In addition, the channel state / quality of a specific cell refers to the channel state / quality of a channel or communication link formed between a BS or node that provides communication services to the specific cell and the UE. In a 3GPP-based communication system, a UE can measure a downlink channel state from a specific node using CRS (Cell-specific Reference Signal) resources transmitted by antenna port(s) of the specific node on CRS resources allocated to the specific node and / or CSI-RS (Channel State Information Reference Signal) resources transmitted.

[0054] Meanwhile, 3GPP-based communication systems use the concept of cells to manage radio resources, and cells associated with radio resources are distinguished from cells in geographical areas.

[0055] A "cell" in a geographical area can be understood as the coverage over which a node can provide a service using a carrier, and a "cell" in a radio resource is associated with a bandwidth (BW), which is a frequency range configured by the carrier. Since downlink coverage, which is the range over which a node can transmit a valid signal, and uplink coverage, which is the range over which a node can receive a valid signal from a UE, depend on the carrier carrying the signal, the coverage of a node is also associated with the coverage of the "cell" of the radio resource used by the node. Therefore, the term "cell" can sometimes be used to mean the coverage of a service provided by a node, sometimes a radio resource, and sometimes the range over which a signal using the radio resource can reach with a valid intensity.

[0056] Meanwhile, the 3GPP communication standard uses the concept of a cell to manage radio resources. A "cell" associated with radio resources is defined as a combination of downlink resources (DL resources) and uplink resources (UL resources), i.e., a combination of a DL component carrier (CC) and an UL CC. A cell can be configured with DL resources alone or a combination of DL resources and UL resources. If carrier aggregation is supported, the linkage between the carrier frequency of the DL resources (or DL ​​CC) and the carrier frequency of the UL resources (or UL CC) can be indicated by system information. For example, the combination of DL resources and UL resources can be indicated by a System Information Block Type 2 (SIB2) linkage. Here, the carrier frequency can be the same as or different from the center frequency of each cell or CC. When carrier aggregation (CA) is established, the UE has only one radio resource control (RRC) connection with the network. One serving cell provides non-access stratum (NAS) mobility information during RRC connection establishment / re-establishment / handover, and one serving cell provides security input during RRC connection re-establishment / handover. Such a cell is called a primary cell (Pcell). A Pcell is a cell operating on the primary frequency where the UE performs initial connection establishment procedures or initiates connection re-establishment procedures.Depending on the UE capability, secondary cells (Scells) can be configured to form a set of serving cells together with Pcells. An Scell ​​can be configured after an RRC (Radio Resource Control) connection establishment has been made, and is a cell that provides additional radio resources in addition to the resources of a special cell (SpCell). The carrier corresponding to a Pcell in downlink is called a downlink primary CC (DL PCC), and the carrier corresponding to a Pcell in uplink is called an UL primary CC (UL PCC). The carrier corresponding to an Scell ​​in downlink is called a DL secondary CC (DL SCC), and the carrier corresponding to the Scell ​​in uplink is called an UL secondary CC (UL SCC).

[0057] For dual connectivity (DC) operation, the term special cell (SpCell) refers to a Pcell of a master cell group (MCG) or a primary secondary cell (PSCell) of a secondary cell group (SCG). A SpCell supports PUCCH transmission and contention-based random access and is always activated. An MCG is a group of serving cells associated with a master node (e.g., BS) and consists of a SpCell (Pcell) and optionally one or more Scells. For a UE configured for DC, an SCG is a subset of serving cells associated with a secondary node and consists of a primary secondary cell (PSCell) and zero or more Scells. A PSCell is a primary Scell ​​of an SCG. For a UE in RRC_CONNECTED state that is not configured for CA or DC, there is only one serving cell consisting of Pcells. For a UE in RRC_CONNECTED state that is configured for CA or DC, the term serving cells refers to the set of cells consisting of SpCell(s) and all Scell(s). In DC, two medium access control (MAC) entities are configured in the UE: one for the MCG and one for the SCG.

[0058] For a UE for which CA is set and DC is not set, a Pcell PUCCH group (also referred to as a primary PUCCH group) consisting of a Pcell and zero or more Scells and a Scell ​​PUCCH group (also referred to as a secondary PUCCH group) consisting of only Scell(s) may be set. In the case of an Scell, an Scell ​​(hereinafter referred to as a PUCCH Scell) on which a PUCCH associated with the cell is transmitted may be set. An Scell ​​for which a PUCCH Scell ​​is indicated belongs to an Scell ​​PUCCH group (i.e., a secondary PUCCH group), and PUCCH transmission of the relevant UCI is performed on the PUCCH Scell, and an Scell ​​for which a PUCCH Scell ​​is not indicated or which is a Pcell and is indicated as a cell for PUCCH transmission belongs to a Pcell PUCCH group (i.e., a primary PUCCH group), and PUCCH transmission of the relevant UCI is performed on the Pcell. Hereinafter, if a UE is configured with an SCG and some implementations of this specification related to PUCCH are applied to the SCG, the primary cell may refer to a PSCell of the SCG. If a UE is configured with a PUCCH Scell ​​and some implementations of this specification related to PUCCH are applied to a secondary PUCCH group, the primary cell may refer to a PUCCH Scell ​​of the secondary PUCCH group.

[0059] In a wireless communication system, a UE receives information from a base station (BS) via the downlink (DL), and the UE transmits information to the base station via the uplink (UL). The information transmitted and / or received by the BS and UE includes data and various control information, and various physical channels exist depending on the type and purpose of the information they transmit and / or receive.

[0060] 3GPP-based communication standards define downlink physical channels corresponding to resource elements that carry information originating from higher layers, and downlink physical signals corresponding to resource elements that are used by the physical layer but do not carry information originating from higher layers. For example, the physical downlink shared channel (PDSCH), physical broadcast channel (PBCH), and physical downlink control channel (PDCCH) are defined as downlink physical channels, and reference signals and synchronization signals are defined as downlink physical signals. A reference signal (RS), also referred to as a pilot, refers to a signal with a predefined special waveform that is known to the BS and the UE. For example, the demodulation reference signal (DMRS), the channel state information RS (CSI-RS), and the positioning reference signal (PRS) are defined as downlink reference signals. 3GPP-based communication standards define uplink physical channels corresponding to resource elements that carry information originating from higher layers, and uplink physical signals corresponding to resource elements that are used by the physical layer but do not carry information originating from higher layers.For example, a physical uplink shared channel (PUSCH), a physical uplink control channel (PUCCH), and a physical random access channel (PRACH) are defined as uplink physical channels, and a demodulation reference signal (DMRS) for uplink control / data signals and a sounding reference signal (SRS) used for uplink channel measurement are defined.

[0061] In this specification, PDCCH (Physical Downlink Control CHannel) refers to a set of time-frequency resources (e.g., resource elements (REs)) that carry DCI (Downlink Control Information), and PDSCH (Physical Downlink Shared CHannel) refers to a set of time-frequency resources that carry downlink data. In addition, PUCCH (Physical Uplink Control CHannel), PUSCH (Physical Uplink Shared CHannel), and PRACH (Physical Random Access CHannel) refer to sets of time-frequency resources that carry UCI (Uplink Control Information), uplink data, and random access signals, respectively (respectively). Hereinafter, the expression that a user equipment transmits / receives a PUCCH / PUSCH / PRACH is used with the same meaning as that uplink control information / uplink data / random access signals are transmitted / received on or through the PUCCH / PUSCH / PRACH, respectively. Additionally, the expression that BS transmits / receives PBCH / PDCCH / PDSCH is used with the same meaning as transmitting broadcast information / downlink control information / downlink data on or through PBCH / PDCCH / PDSCH, respectively.

[0062] In this specification, radio resources (e.g., time-frequency resources) scheduled or configured by the BS to the UE for transmission or reception of PUCCH / PUSCH / PDSCH are also referred to as PUCCH / PUSCH / PDSCH resources.

[0063] Since the communication device receives a synchronization signal (SS), DMRS, CSI-RS, PRS, PBCH, PDCCH, PDSCH, PUSCH, and / or PUCCH in the form of radio signals on a cell, it cannot selectively receive through an RF receiver only radio signals including only a specific physical channel or only a specific physical signal, or selectively receive through an RF receiver only radio signals excluding only a specific physical channel or only a physical signal. In actual operation, the communication device first receives radio signals on a cell through an RF receiver, converts the radio signals, which are RF band signals, into baseband signals, and decodes a physical signal and / or a physical channel within the baseband signals using one or more processors. Thus, in some implementations of the present specification, not receiving a physical signal and / or a physical channel may not actually mean that the communication device does not receive wireless signals containing the physical signal and / or physical channel at all, but rather that it does not attempt to recover the physical signal and / or physical channel from the wireless signals, e.g., does not attempt to decode the physical signal and / or the physical channel.

[0064] As more and more communication devices demand greater communication capacity, the need for improved mobile broadband communication over existing radio access technology (RAT) is emerging. Furthermore, massive MTC, which connects numerous devices and objects to provide diverse services anytime, anywhere, is also a key issue to be considered in next-generation communications. Furthermore, communication system design that considers reliability and latency-sensitive services / UEs is being discussed. The introduction of next-generation RATs that take advanced mobile broadband communication, massive MTC, and URLLC (Ultra-Reliable and Low Latency Communication) into account is currently under discussion. 3GPP is currently conducting studies on next-generation mobile communication systems beyond EPC. For convenience, this technology is referred to as new RAT (NR) or 5G RAT, and a system that uses or supports NR is referred to as an NR system.

[0065] FIG. 1 illustrates an example of a communication system 1 to which implementations of the present specification are applied. Referring to FIG. 1, the communication system (1) applied to the present specification includes a wireless device, a BS, and a network. Here, the wireless device refers to a device that performs communication using a wireless access technology (e.g., 5G NR (New RAT), LTE (e.g., E-UTRA)) and may be referred to as a communication / wireless / 5G device. Although not limited thereto, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Things) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing vehicle-to-vehicle communication, etc. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). XR devices include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, and may be implemented in the form of a Head-Mounted Device (HMD), a Head-Up Display (HUD) installed in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, digital signage, a vehicle, a robot, etc. Mobile devices may include a smartphone, a smart pad, a wearable device (e.g., a smart watch, smart glasses), a computer (e.g., a laptop, etc.), etc. Home appliances may include a TV, a refrigerator, a washing machine, etc. IoT devices may include sensors, smart meters, etc. For example, a BS or network may also be implemented as a wireless device, and a specific wireless device may act as a BS / network node to other wireless devices.

[0066] Wireless devices (100a to 100f) can be connected to a network (300) via a BS (200). Artificial Intelligence (AI) technology can be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) via a network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, etc. The wireless devices (100a to 100f) can communicate with each other via the BS (200) / network (300), but can also communicate directly (e.g., sidelink communication) without going through the BS / network. For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to Everything) communication). In addition, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0067] Wireless communication / connection (150a, 150b) can be performed between wireless devices (100a~100f) / BS (200) - BS (200) / wireless devices (100a~100f). Here, the wireless communication / connection can be performed through various wireless access technologies (e.g., 5G NR) for uplink / downlink communication (150a) and sidelink communication (150b) (or D2D communication). Through the wireless communication / connection (150a, 150b), the wireless device and the BS / wireless device can transmit / receive wireless signals to / from each other. To this end, at least some of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes can be performed based on various proposals of this specification.

[0068] FIG. 2 is a block diagram illustrating examples of communication devices capable of performing a method according to the present specification. Referring to FIG. 2, a first wireless device (100) and a second wireless device (200) can transmit and / or receive wireless signals via various wireless access technologies (e.g., LTE, NR). Here, {the first wireless device (100), the second wireless device (200)} can correspond to {the wireless device (100x), the BS (200)} and / or {the wireless device (100x), the wireless device (100x)} of FIG. 1.

[0069] A first wireless device (100) includes one or more processors (102) and one or more memories (104), and may further include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memories (104) and / or the transceivers (106), and may be configured to implement functions, procedures, and / or methods described / suggested below. For example, the processor (102) may process information in the memory (104) to generate first information / signals, and then transmit a wireless signal including the first information / signals via the transceivers (106). In addition, the processor (102) may receive a wireless signal including second information / signals via the transceivers (106), and then store information obtained from signal processing of the second information / signals in the memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may perform some or all of the processes controlled by the processor (102), or may store software code including commands for performing the procedures and / or methods described / proposed below. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). The transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In this specification, a wireless device may also mean a communication modem / circuit / chip.

[0070] The second wireless device (200) includes one or more processors (202), one or more memories (204), and may further include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memories (204) and / or the transceivers (206), and may be configured to implement the functions, procedures, and / or methods described / suggested below. For example, the processor (202) may process information in the memory (204) to generate third information / signals, and then transmit a wireless signal including the third information / signals via the transceivers (206). In addition, the processor (202) may receive a wireless signal including fourth information / signals via the transceivers (206), and then store information obtained from signal processing of the fourth information / signals in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including commands for performing the procedures and / or methods described / proposed below. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF unit. In this specification, a wireless device may also mean a communication modem / circuit / chip.

[0071] The wireless communication technology implemented in the wireless device (100, 200) of the present specification may include not only LTE, NR, and 6G, but also Narrowband Internet of Things for low-power communication. At this time, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification may perform communication based on LTE-M technology. At this time, for example, LTE-M technology may be an example of LPWAN technology, and may be called by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology can be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification can include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create personal area networks (PAN) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.

[0072] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as a physical (PHY) layer, a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, and a service data adaptation protocol (SDAP) layer). One or more processors (102, 202) may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs) according to the functions, procedures, proposals, and / or methods disclosed in this specification. One or more processors (102, 202) may generate messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed in this specification. One or more processors (102, 202) may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed in this specification, and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) may receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed in this specification.

[0073] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The functions, procedures, proposals, and / or methods disclosed in this specification may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. Firmware or software configured to perform the functions, procedures, suggestions and / or methods disclosed in this specification may be included in one or more processors (102, 202) or stored in one or more memories (104, 204) and executed by one or more processors (102, 202). The functions, procedures, suggestions and / or methods disclosed in this specification may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.

[0074] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0075] One or more transceivers (106, 206) may transmit user data, control information, wireless signals / channels, etc., as described in the methods and / or flowcharts of this specification, to one or more other devices. One or more transceivers (106, 206) may receive user data, control information, wireless signals / channels, etc., as described in the functions, procedures, proposals, methods and / or flowcharts of this specification, from one or more other devices. For example, one or more transceivers (106, 206) may be coupled to one or more processors (102, 202) and may transmit and / or receive wireless signals. For example, one or more processors (102, 202) may control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be coupled to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and / or receive user data, control information, wireless signals / channels, or the like, as referred to in the functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this specification, via one or more antennas (108, 208). In this specification, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) may convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals for processing using one or more processors (102, 202).One or more transceivers (106, 206) may convert user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.

[0076] FIG. 3 illustrates another example of a wireless device capable of performing implementation(s) of the present specification. Referring to FIG. 3, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 2 and may be composed of various elements, components, units / units, and / or modules. For example, the wireless device (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and additional elements (140). The communication unit may include a communication circuit (112) and a transceiver(s) (114). For example, the communication circuit (112) may include one or more processors (102, 202) and / or one or more memories (104, 204) of FIG. 2. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 2. The control unit (120) is electrically connected to the communication unit (110), the memory unit (130), and the additional elements (140) and controls the overall operation of the wireless device. For example, the control unit (120) may control the electrical / mechanical operation of the wireless device based on the program / code / command / information stored in the memory unit (130). In addition, the control unit (120) may transmit information stored in the memory unit (130) to an external device (e.g., another communication device) via a wireless / wired interface through the communication unit (110), or store information received from an external device (e.g., another communication device) via a wireless / wired interface in the memory unit (130).

[0077] The additional element (140) may be configured in various ways depending on the type of the wireless device. For example, the additional element (140) may include at least one of a power unit / battery, an input / output (I / O) unit, a driving unit, and a computing unit. Although not limited thereto, the wireless device may be implemented in the form of a robot (Fig. 1, 100a), a vehicle (Fig. 1, 100b-1, 100b-2), an XR device (Fig. 1, 100c), a portable device (Fig. 1, 100d), a home appliance (Fig. 1, 100e), an IoT device (Fig. 1, 100f), a UE for digital broadcasting, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or a financial device), a security device, a climate / environmental device, an AI server / device (Fig. 1, 400), a BS (Fig. 1, 200), a network node, etc. Wireless devices may be mobile or stationary depending on the use / service.

[0078] In FIG. 3, various elements, components, units / parts, and / or modules within the wireless device (100, 200) may be entirely interconnected via a wired interface, or at least some may be wirelessly connected via a communication unit (110). For example, within the wireless device (100, 200), the control unit (120) and the communication unit (110) may be wired, and the control unit (120) and a first unit (e.g., 130, 140) may be wirelessly connected via the communication unit (110). In addition, each element, component, unit / part, and / or module within the wireless device (100, 200) may further include one or more elements. For example, the control unit (120) may be composed of one or more processor sets. For example, the control unit (120) may be composed of a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing processor, a memory control processor, etc. As another example, the memory unit (130) may be composed of RAM (Random Access Memory), DRAM (Dynamic RAM), ROM (Read Only Memory), flash memory, volatile memory, non-volatile memory, and / or a combination thereof.

[0079] In this specification, at least one memory (e.g., 104 or 204) can store instructions or programs that, when executed, cause at least one processor operably connected to the at least one memory to perform operations according to some embodiments or implementations of the present specification.

[0080] In this specification, a computer-readable (non-transitory) storage medium can store at least one instruction or computer program, which when executed by at least one processor causes the at least one processor to perform operations according to some embodiments or implementations of this specification.

[0081] In this specification, a processing device or apparatus may include at least one processor and at least one computer memory operatively connected to the at least one processor. The at least one computer memory may store instructions or programs, which, when executed, cause at least one processor operatively connected to the at least one memory to perform operations according to some embodiments or implementations of the present specification.

[0082] In this specification, a computer program may be stored in at least one computer-readable (non-transitory) storage medium and may include program code that, when executed, performs operations according to some implementations of the present specification or causes at least one processor to perform operations according to some implementations of the present specification. The computer program may be provided in the form of a computer program product. The computer program product may include at least one computer-readable (non-transitory) storage medium.

[0083] A communications device of the present specification comprises at least one processor; and at least one computer memory operably connected to said at least one processor and storing instructions that, when executed, cause said at least one processor to perform operations according to the example(s) of the present specification described below.

[0084] Figure 4 illustrates an example of a frame structure available in a 3GPP-based wireless communication system.

[0085] The structure of the frame in Fig. 4 is merely an example, and the number of subframes, the number of slots, and the number of symbols in the frame can be varied. In an NR system, OFDM numerology (e.g., subcarrier spacing (SCS)) may be set differently between multiple cells aggregated to a single UE. Accordingly, the (absolute time) duration of a time resource (e.g., a subframe, a slot, or a transmission time interval (TTI)) consisting of the same number of symbols may be set differently between the aggregated cells. Here, the symbol may include an OFDM symbol (or a cyclic prefix - orthogonal frequency division multiplexing (CP-OFDM) symbol), an SC-FDMA symbol (or a discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbol). In this specification, the terms symbol, OFDM-based symbol, OFDM symbol, CP-OFDM symbol, and DFT-s-OFDM symbols are interchangeable.

[0086] Referring to Figure 4, in the NR system, uplink and downlink transmissions are organized into frames. Each frame is T f= (△f max *N f / 100)*T c = 10 ms duration, divided into two half-frames of 5 ms each. Here, T is the basic time unit for NR. c = 1 / (△f max *N f ) and △f max = 480*10 3 Hz, and N f =4096. For reference, T is the basic time unit for LTE. s = 1 / (△f ref *N f,ref ) and △f ref = 15*10 3 Hz, and N f,ref =2048. T s Wow T c is a constant κ = T s / T c = 64 relationship. Each half-frame consists of 5 subframes, and the duration of a single subframe (SF) is T sf is 1ms. Subframes are further divided into slots, and the number of slots in a subframe depends on the subcarrier spacing. Each slot consists of 14 or 12 OFDM symbols based on the cyclic prefix. For a normal cyclic prefix (CP), each slot consists of 14 OFDM symbols, and for an extended CP, each slot consists of 12 OFDM symbols. The numerology is exponentially scalable with a subcarrier spacing △f = 2. u *Depends on 15 kHz. The following table shows the subcarrier spacing for regular CP △f = 2. u *Number of OFDM symbols per slot at 15 kHz (N) slot symb ), number of slots per frame (Nframe,u slot ) and the number of slots per subframe (N subframe,u slot ) is shown.

[0087]

[0088] The following table shows the subcarrier spacing for extended CP △f = 2. u *Indicates the number of OFDM symbols per slot, the number of slots per frame, and the number of slots per subframe at 15 kHz.

[0089]

[0090] For a subcarrier spacing setting u, slots are n in increasing order within a subframe. u s ∈ {0, ..., nsubframe,u slot - 1} and n in increasing order within the frame u s,f ∈ {0, ..., n frame,u slot - Numbered as 1}.

[0091] Figure 5 illustrates the resource grid of a slot. A slot contains multiple symbols (e.g., 14 or 12) in the time domain. For each numeral (e.g., subcarrier spacing) and carrier, a common resource block (CRB) N is indicated by higher layer signaling (e.g., radio resource control (RRC) signaling). start,u grid Starting from,N size,u grid,x *N RB sc Dog subcarriers and N subframe,u symb A resource grid of OFDM symbols is defined, where N size,u grid,xis the number of resource blocks (RBs) in the resource grid, and the subscript x is DL for downlink and UL for uplink. N RB sc is the number of subcarriers per RB, and in 3GPP-based wireless communication systems, N RB sc is typically 12. For a given antenna port p, subcarrier spacing configuration u, and transmission direction (DL or UL), there is one resource grid. The carrier bandwidth N for subcarrier spacing configuration u size,u grid is given to the UE by higher layer parameters (e.g., RRC parameters) from the network. Each element in the resource grid for antenna port p and subcarrier spacing configuration u is called a resource element (RE), and one complex symbol can be mapped to each RE. Each RE in the resource grid is uniquely identified by an index k in the frequency domain and an index l indicating the symbol position relative to a reference point in the time domain. In an NR system, an RB is defined by 12 consecutive subcarriers in the frequency domain. In an NR system, RBs can be classified into common resource blocks (CRBs) and physical resource blocks (PRBs). CRBs are numbered upwards from 0 in the frequency domain for the subcarrier spacing configuration u. The center of subcarrier 0 of CRB 0 for the subcarrier spacing configuration u coincides with 'Point A', which is a common reference point for the resource block grids. PRBs for subcarrier spacing u are defined within the bandwidth part (BWP) and range from 0 to N. size,u BWP,i -1, where i is the number of the bandwidth part. Common resource block n u CRBand bandwidth part i within physical resource block n PRB The relationship between the two is as follows: n u PRB = n u CRB +N start,u BWP,i , here N start,u BWP,i is a common resource block (BRB) whose bandwidth part starts relative to CRB 0. A BWP comprises multiple consecutive RBs in the frequency domain. For example, a BWP may be a given numeral u within a BWP i on a given carrier. i A subset of contiguous CRBs defined for a carrier. A carrier may include up to N (e.g., 5) BWPs. A UE may be configured to have one or more BWPs on a given component carrier. Data communication is performed through the activated BWPs, and only a predetermined number (e.g., 1) of BWPs configured for the UE may be activated on the carrier.

[0092] For each serving cell in a set of DL BWPs or UL BWPs, the network configures at least an initial DL BWP and one (if the serving configuration is configured with uplink) or two (if supplementary uplink is used) initial UL BWPs. The network may also configure additional UL and DL BWPs for the serving cell. For each DL BWP or UL BWP, the UE is provided with the following parameters for the serving cell: i) subcarrier spacing, ii) cyclic prefix, and iii) N start BWP = Offset RB with the assumption of 275 set and length L RB CRBN provided by the RRC parameter locationAndBandwidth, which indicates the resource indicator value (RIV) start BWP=O carrier +RB start and the number of contiguous RBs N size BWP =L RB , and the subcarrier spacing is provided by the RRC parameter offsetToCarrierO carrier ; an index within the set of DL BWPs or UL BWPs; a set of BWP-common parameters and a set of BWP-specific parameters.

[0093] Virtual resource blocks (VRBs) are defined within the bandwidth part and are numbered from 0 to N. size,u BWP,i Numbered from -1, where i is the number of the bandwidth part. VRBs are mapped to physical resource blocks (PRBs) according to interleaved or non-interleaved mapping. In some implementations, for non-interleaved VRB-to-PRB mapping, VRB n may be mapped to PRB n.

[0094] NR frequency bands are defined by two types of frequency ranges, FR1 and FR2, with FR2 also referred to as millimeter wave (mmW). The following table lists the frequency ranges in which NR can operate.

[0095]

[0096] Below, the physical channels that can be used in 3GPP-based wireless communication systems are described in more detail.

[0097] The PDCCH carries DCI. For example, the PDCCH (i.e., DCI) carries the transmission format and resource allocation of the downlink shared channel (DL-SCH), resource allocation information for the uplink shared channel (UL-SCH), paging information for the paging channel (PCH), system information on the DL-SCH, resource allocation information for control messages of a layer (hereinafter, upper layer) located above the physical layer in the protocol stacks of the UE / BS, such as a random access response (RAR) transmitted on the PDSCH, transmission power control commands, activation / release of configured scheduling (CS), etc. The DCI that includes resource allocation information for the DL-SCH is also called PDSCH scheduling DCI, and the DCI that includes resource allocation information for the UL-SCH is also called PUSCH scheduling DCI. The DCI includes a cyclic redundancy check (CRC), and the CRC is masked / scrambled with various identifiers (e.g., radio network temporary identifier (RNTI)) depending on the owner or intended use of the PDCCH. For example, if the PDCCH is for a specific UE, the CRC is masked with the UE identifier (e.g., cell RNTI (C-RNTI)). If the PDCCH is for paging, the CRC is masked with the paging RNTI (P-RNTI). If the PDCCH is for system information (e.g., system information block (SIB)), the CRC is masked with the system information RNTI (SI-RNTI). If the PDCCH is for a random access response, the CRC is masked with the random access RNTI (RA-RATI).

[0098] When a PDCCH on one serving cell schedules a PDSCH or PUSCH on another serving cell, this is called cross-carrier scheduling. Cross-carrier scheduling using the carrier indicator field (CIF) can allow the PDCCH of a serving cell to schedule resources on another serving cell. On the other hand, when a PDSCH on a serving cell schedules a PDSCH or PUSCH on the serving cell, this is called self-carrier scheduling. When cross-carrier scheduling is used in a cell, the BS can provide the UE with information about the cell that schedules the cell. For example, the BS can provide the UE with information about whether the serving cell is scheduled by a PDCCH on another (scheduling) cell or by the serving cell, and if the serving cell is scheduled by another (scheduling) cell, which cell signals downlink assignments and uplink grants for the serving cell. In this specification, a cell that carries a PDCCH is called a scheduling cell, and a cell in which transmission of a PUSCH or PDSCH is scheduled by DCI included in the PDCCH, i.e., a cell that carries a PUSCH or PDSCH scheduled by the PDCCH, is called a scheduled cell.

[0099] The PDSCH is a physical layer UL channel for UL data transport. PDSCH carries downlink data (e.g., DL-SCH transport blocks) and employs modulation methods such as Quadrature Phase Shift Keying (QPSK), 16 Quadrature Amplitude Modulation (QAM), 64 QAM, and 256 QAM. Transport blocks (TBs) are encoded to generate codewords. PDSCH can carry up to two codewords. Scrambling and modulation mapping are performed for each codeword, and the modulation symbols generated from each codeword can be mapped to one or more layers. Each layer is mapped to radio resources along with the DMRS, generating an OFDM symbol signal and transmitting it through the corresponding antenna port.

[0100] PUCCH refers to a physical layer UL channel for UCI transmission. PUCCH carries UCI (Uplink Control Information). The types of UCI transmitted on PUCCH include hybrid automatic repeat request (HARQ)-acknowledgement (ACK) information, scheduling request (SR), and channel state information (CSI). UCI bits include HARQ-ACK information bits, SR information bits, LRR information bits, and CSI bits, if any. In this specification, the HARQ-ACK information bits correspond to a HARQ-ACK codebook. In particular, a bit sequence in which HARQ-ACK information bits are listed according to a predetermined rule is called a HARQ-ACK codebook.

[0101] - Scheduling request (SR): Information used to request UL-SCH resources.

[0102] - Hybrid automatic repeat request (HARQ)-acknowledgement (ACK): This is a response to a downlink data packet (e.g., a codeword) on the PDSCH. It indicates whether the downlink data packet was successfully received by the communication device. One HARQ-ACK bit may be transmitted in response to a single codeword, and two HARQ-ACK bits may be transmitted in response to two codewords. HARQ-ACK responses include positive ACK (simply, ACK), negative ACK (NACK), DTX, or NACK / DTX. Here, the term HARQ-ACK is used interchangeably with HARQ ACK / NACK, ACK / NACK, or A / N.

[0103] - Channel state information (CSI): Feedback information about the downlink channel. CSI may include channel quality information (CQI), rank indicator (RI), precoding matrix indicator (PMI), CSI-RS resource indicator (CRI), SS / PBCH resource block indicator (SSBRI), layer indicator (LI), etc.

[0104] - Link recovery request (LRR)

[0105] In this specification, for convenience, the PUCCH resources set and / or instructed by the BS to the UE for HARQ-ACK, SR, and CSI transmission are referred to as HARQ-ACK PUCCH resources, SR PUCCH resources, and CSI PUCCH resources, respectively.

[0106] PUCCH formats can be categorized as follows based on the UCI payload size and / or transmission length (e.g., the number of symbols constituting the PUCCH resource). For more information on PUCCH formats, please refer to Table 4.

[0107] (0) PUCCH format 0 (PF0, F0)

[0108] - Supported UCI payload sizes: up to K bits (e.g., K = 2)

[0109] - Number of OFDM symbols constituting a single PUCCH: 1 to X symbols (e.g., X = 2)

[0110] - Transmission structure: PUCCH format 0 consists of only UCI signals without DMRS, and the UE transmits the UCI status by selecting and transmitting one of multiple sequences. For example, the UE transmits a specific UCI to the BS by transmitting one of multiple sequences through the PUCCH of PUCCH format 0. The UE transmits the PUCCH of PUCCH format 0 within the PUCCH resources for the corresponding SR configuration only when transmitting a positive SR.

[0111] - The configuration for PUCCH format 0 includes the following parameters for the corresponding PUCCH resource: an index for the initial cyclic shift, the number of symbols for PUCCH transmission, and the first symbol for the PUCCH transmission.

[0112] (1) PUCCH format 1 (PF1, F1)

[0113] - Supported UCI payload sizes: up to K bits (e.g., K = 2)

[0114] - Number of OFDM symbols constituting a single PUCCH: Y to Z symbols (e.g., Y = 4, Z = 14)

[0115] - Transmission structure: DMRS and UCI are configured / mapped to different OFDM symbols in TDM format. That is, DMRS is transmitted in symbols where modulation symbols are not transmitted. UCI is expressed by multiplying a specific sequence (e.g., orthogonal cover code (OCC)) by a modulation (e.g., QPSK) symbol. Code division multiplexing (CDM) is supported between multiple PUCCH resources (following PUCCH format 1) (within the same RB) by applying cyclic shift (CS) / OCC to both UCI and DMRS. PUCCH format 1 carries UCI of up to 2 bits in size, and the modulation symbols are spread in the time domain by an orthogonal cover code (OCC) (configured differently depending on whether frequency hopping is performed).

[0116] - The configuration for PUCCH format 1 includes the following parameters for the corresponding PUCCH resource: an index for the initial cyclic shift, the number of symbols for PUCCH transmission, the first symbol for the PUCCH transmission, and an index for the orthogonal cover code.

[0117] (2) PUCCH format 2 (PF2, F2)

[0118] - Supported UCI payload size: more than K bits (e.g., K = 2)

[0119] - Number of OFDM symbols constituting a single PUCCH: 1 to X symbols (e.g., X = 2)

[0120] - Transmission structure: DMRS and UCI are configured / mapped in the form of frequency division multiplexing (FDM) within the same symbol. The UE transmits the coded UCI bits by applying only IFFT without DFT. PUCCH format 2 carries UCI with a bit size greater than K bits, and the modulation symbols are transmitted in FDM with DMRS. For example, DMRS are located at symbol indices #1, #4, #7, and #10 within a given resource block with a density of 1 / 3. A pseudo-noise (PN) sequence is used for the DMRS sequence. Frequency hopping can be activated for the 2-symbol PUCCH format 2.

[0121] - The configuration for PUCCH format 2 includes the following parameters for the corresponding PUCCH resource: the number of PRBs, the number of symbols for PUCCH transmission, and the first symbol for the PUCCH transmission.

[0122] (3) PUCCH format 3 (PF3, F3)

[0123] - Supported UCI payload size: more than K bits (e.g., K = 2)

[0124] - Number of OFDM symbols constituting a single PUCCH: Y to Z symbols (e.g., Y = 4, Z = 14)

[0125] - Transmission structure: DMRS and UCI are configured / mapped to different symbols in TDM format. The UE applies DFT to the coded UCI bits and transmits them. PUCCH format 3 does not support UE multiplexing for the same time-frequency resources (e.g., the same PRB).

[0126] - The configuration for PUCCH format 3 includes the following parameters for the corresponding PUCCH resource: the number of PRBs, the number of symbols for PUCCH transmission, and the first symbol for the PUCCH transmission.

[0127] (4) PUCCH format 4 (PF4, F4)

[0128] - Supported UCI payload size: more than K bits (e.g., K = 2)

[0129] - Number of OFDM symbols constituting a single PUCCH: Y to Z symbols (e.g., Y = 4, Z = 14)

[0130] - Transmission Structure: DMRS and UCI are configured / mapped to different symbols in TDM format. PUCCH Format 4 can multiplex up to 4 UEs within the same PRB by applying OCC in the DFT front-end and CS (or interleaved FDM (IFDM) mapping) to DMRS. In other words, UCI modulation symbols are transmitted by TDM (Time Division Multiplexing) with DMRS.

[0131] - The configuration for PUCCH format 4 includes the following parameters for the corresponding PUCCH resource: the number of symbols for PUCCH transmission, the length for the orthogonal cover code, the index for the orthogonal cover code, and the first symbol for the PUCCH transmission.

[0132] The following table shows examples of PUCCH formats. Depending on the PUCCH transmission length, they can be classified into short PUCCH (formats 0 and 2) and long PUCCH (formats 1, 3, and 4).

[0133]

[0134] PUCCH resources can be determined by UCI type (e.g., A / N, SR, CSI). PUCCH resources used for UCI transmission can be determined based on the UCI (payload) size. For example, the BS configures multiple PUCCH resource sets to the UE, and the UE can select a specific PUCCH resource set corresponding to a specific range according to the range of the UCI (payload) size (e.g., the number of UCI bits). For example, the UE can set the number of UCI bits (N UCI ) can select one of the following PUCCH resource sets.

[0135] - PUCCH resource set #0, if UCI bit count =< 2

[0136] - PUCCH resource set #1, if 2< UCI bits =< N1

[0137] ...

[0138] - PUCCH resource set #(K-1), if N K-2 < UCI bit count =< N K-1

[0139] Here, K is the number of PUCCH resource sets (K>1), and N i is the maximum number of UCI bits supported by PUCCH resource set #i. For example, PUCCH resource set #1 may be composed of resources of PUCCH formats 0 to 1, and other PUCCH resource sets may be composed of resources of PUCCH formats 2 to 4 (see Table 4).

[0140] The configuration for each PUCCH resource includes a PUCCH resource index, an index of a starting PRB, and a configuration for one of PUCCH formats 0 to 4. The UE is configured by the BS via a higher layer parameter maxCodeRate to multiplex HARQ-ACK, SR, and CSI report(s) within a PUCCH transmission using PUCCH format 2, PUCCH format 3, or PUCCH format 4. The higher layer parameter maxCodeRate is used to determine how to feed back UCI on the PUCCH resource for PUCCH format 2, 3, or 4.

[0141] When the UCI type is SR or CSI, the PUCCH resources to be used for UCI transmission within the PUCCH resource set can be configured to the UE by the network via higher layer signaling (e.g., RRC signaling). When the UCI type is HARQ-ACK for SPS (Semi-Persistent Scheduling) PDSCH, the PUCCH resources to be used for UCI transmission within the PUCCH resource set can be configured to the UE by the network via higher layer signaling (e.g., RRC signaling). On the other hand, when the UCI type is HARQ-ACK for PDSCH scheduled by DCI, the PUCCH resources to be used for UCI transmission within the PUCCH resource set can be scheduled based on the DCI.

[0142] In case of DCI-based PUCCH resource scheduling, the BS transmits DCI to the UE via PDCCH, and can indicate PUCCH resources to be used for UCI transmission within a specific PUCCH resource set via an ACK / NACK resource indicator (ARI) in the DCI. The ARI is used to indicate PUCCH resources for ACK / NACK transmission and may also be referred to as a PUCCH resource indicator (PRI). Here, the DCI is a DCI used for PDSCH scheduling, and the UCI may include HARQ-ACK for the PDSCH. Meanwhile, the BS can configure a PUCCH resource set consisting of more PUCCH resources than the number of states that the ARI can express, to the UE, using (UE-specific) higher layer (e.g., RRC) signaling. At this time, the ARI indicates a PUCCH resource subset within the PUCCH resource set, and which PUCCH resource to use within the indicated PUCCH resource subset can be determined according to an implicit rule based on transmission resource information for the PDCCH (e.g., a start control channel element (CCE) index of the PDCCH, etc.).

[0143] UCI can also be transmitted via PUSCH, where UL data is transmitted, or only UCI can be transmitted without UL-SCH.

[0144] A UE must have uplink resources available to it for UL-SCH data transmission, and downlink resources available to it for DL-SCH data reception. Uplink and downlink resources are assigned to the UE through resource allocation by the BS. Resource allocation may include time domain resource allocation (TDRA) and frequency domain resource allocation (FDRA). In this specification, uplink resource allocation is also referred to as uplink grant, and downlink resource allocation is also referred to as downlink assignment. An uplink grant is dynamically received by the UE on the PDCCH or within the RAR, or is semi-persistently configured to the UE by RRC signaling from the BS. A downlink assignment is dynamically received by the UE on the PDCCH, or is semi-persistently configured to the UE by RRC signaling from the BS.

[0145] In UL, the BS can dynamically allocate uplink resources to the UE via PDCCH(s) addressed to a cell radio network temporary identifier (C-RNTI). The UE monitors the PDCCH(s) to find possible uplink grant(s) for UL transmission. Furthermore, the BS can allocate uplink resources to the UE using the configured grant(s). Two types of configured grants can be used: Type 1 and Type 2. For Type 1, the BS directly provides the configured uplink grant (including the periodicity) via RRC signaling. For Type 2, the BS can configure the period of the RRC configured uplink grant via RRC signaling, and signal and activate or deactivate the configured uplink grant via a PDCCH addressed to a configured scheduling RNTI (CS-RNTI). For example, for Type 2, a PDCCH addressed to CS-RNTI implicitly indicates that the corresponding uplink grant can be reused according to a period set by RRC signaling until it is deactivated.

[0146] In DL, the BS can dynamically allocate downlink resources to the UE via PDCCH(s) addressed with the C-RNTI. The UE monitors the PDCCH(s) to discover possible downlink assignments. Additionally, the BS can allocate downlink resources to the UE using semi-static scheduling (SPS). The BS can set the period of the configured downlink assignments via RRC signaling, and signal and activate or deactivate the configured downlink assignments via the PDCCH addressed with the CS-RNTI. For example, a PDCCH addressed with the CS-RNTI implicitly indicates that the corresponding downlink assignment can be reused according to the period set by the RRC signaling until it is deactivated.

[0147] Figure 6 illustrates an example of multiplexing UCI onto PUSCH. If PUCCH resources(s) and PUSCH resources overlap within a slot and simultaneous PUCCH-PUSCH transmission is not configured, UCI can be transmitted via PUSCH as illustrated. Transmitting UCI via PUSCH is referred to as UCI piggybacking or PUSCH piggybacking. Figure 6 illustrates a case where HARQ-ACK and channel state information (CSI) are carried on PUSCH resources.

[0148] <S1_채널 채널 상태 정보(channel state information, CSI) 보고하기(reporting)>

[0149] CSI reporting is used to allow the UE to measure the radio channel status and report it to the network. The time and frequency resources that can be used by the UE for CSI reporting are controlled by the BS. In a 3GPP-based system, CSI may consist of the following indicators / reports: 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), layer-1 reference signal received power (L1-RSRP), or layer-1 signal to interference and noise ratio (L1-SINR).

[0150] In 3GPP-based systems (e.g., NR), CSI-RS is used for time and / or frequency tracking, CSI computation, L1-RSRP computation, and mobility management. Here, CSI computation is related to CSI acquisition, and L1-RSRP computation is related to beam management (BM).

[0151] CSI is a general term for information that can indicate the quality of the wireless channel (or link) formed between the UE and the antenna port(s).

[0152] Figure 7 illustrates the flow of CSI-related processes.

[0153] Referring to FIG. 7, a UE may receive configuration information related to CSI from a BS via RRC signaling (S710). The configuration information related to CSI may include at least CSI interference management (CSI-IM) resource-related information, CSI measurement configuration-related information, CSI resource configuration-related information, CSI-RS resource-related information, or CSI report configuration-related information.

[0154] CSI resource configuration related information can be expressed as CSI-ResourceConfig IE. The CSI resource configuration related information defines a group including at least a non-zero power (NZP) CSI-RS resource set, a CSI-IM resource set, or a CSI-SSB resource set. That is, the CSI resource configuration related information includes a CSI-RS resource set list, and the CSI-RS resource set list can include at least an NZP CSI-RS resource set list, a CSI-IM resource set list, or a CSI-SSB resource set list. A CSI-RS resource set is identified by a CSI-RS resource set ID, and a CSI-RS resource set includes at least one CSI-RS resource. Each CSI-RS resource is identified by a CSI-RS resource ID.

[0155] As shown in the following table, which is an example of the NZP-CSI-RS-ResourceSet IE, parameters indicating the purpose of CSI-RS (e.g., BM-related 'repetition' parameter, tracking-related 'trs-Info' parameter) can be set for each NZP CSI-RS resource set.

[0156]

[0157] Here, the repetition parameter corresponding to the upper layer parameter corresponds to the 'CSI-RS-ResourceRep' of the L1 parameter.

[0158] The following table is part of the NZP-CSI-RS-Resource IE defined in 3GPP TS 38.331.

[0159]

[0160] Information related to CSI reporting configuration includes a reportConfigType parameter indicating time domain behavior and a reportQuantity parameter indicating the CSI-related quantity to be reported. The time domain behavior may be periodic, aperiodic, or quasi-persistent.

[0161] Information related to CSI reporting configuration can be expressed in the CSI-ReportConfig IE (see CSI-ReportConfig IE in 3GPP TS 38.331).

[0162] Additionally, the following table provides an example CSI-ResourceConfigIE, which defines one or more groups of NZP-CSI-RS-ResourceSet, CSI-IM-ResourceSet, and / or CSI-SSB-ResourceSet.

[0163]

[0164] The UE performs CSI measurement based on configuration information related to CSI (S720).

[0165] The above CSI measurement may include (1) a process of receiving a CSI-RS of a UE (S721) and (2) a process of performing CSI calculation (S722) using the received CSI-RS.

[0166] CSI-RS resource element (RE) mapping of CSI-RS resources in the time and frequency domains is established by the upper layer parameter CSI-RS-ResourceMapping. The following table provides an example of CSI-RS-ResourceMappingIE.

[0167]

[0168] In the table above, density represents the density of CSI-RS resources measured in RE / port / PRB, and nrofPorts represents the number of antenna ports.

[0169] The UE can transmit a CSI report based on the calculated CSI (S730). Here, if the parameter quantity of CSI-ReportConfig is set to 'none (or No report)', the UE can skip transmitting the CSI report. However, even if the parameter quantity is set to 'none (or No report)', the UE can still transmit the CSI report to the BS. The case where the parameter quantity is set to 'none' is when an aperiodic tracking reference signal (TRS) is triggered or when repetition is set. Here, the transmission of the CSI report can be skipped only when repetition is set to 'ON' (see Table 5).

[0170] <S1.1_CSI 측정>

[0171] 3GPP-based systems (e.g., NR systems) support more flexible and dynamic CSI measurement and CSI reporting. Here, the CSI measurement may include a process in which the UE receives a CSI-RS and performs CSI calculation based on the received CSI-RS to obtain CSI.

[0172] As a time domain behavior for CSI measurement and CSI reporting, aperiodic / quasi-persistent / periodic channel measurement (CM) and interference measurement (IM) are supported. A 4-port NZP CSI-RS resource element (RE) pattern can be used to configure CSI-IM.

[0173] The BS can transmit precoded NZP CSI-RS to the UE on each port of the configured NZP CSI-RS-based IM resource (IMR).

[0174] The UE can assume a channel / interference layer for each port in the CSI-RS resource set and perform interference measurements.

[0175] A set of multiple CSI-RS resources can be configured, and the BS or network can indicate a subset of NZP CSI-RS resources for channel / interference measurements via DCI.

[0176] <S1.1.1_자원 세팅(resource setting)>

[0177] Each CSI resource set 'CSI-ResourceConfig' contains a configuration of a list of S≥1 CSI resource sets (given by the upper layer parameter csi-RS-ResourceSetList), wherein the list consists of references to one or both of non-zero power (NZP) CS-RS resource set(s) and SS / PBCL block set(s), or wherein the list consists of references to CSI interference measurement (CSI-IM) resource set(s). The configuration for S≥1 CSI resource sets includes each CSI resource set containing CSI-RS resources (consisting of NZP CSI-RS or CSI-IM) and SS / PBCH block (SS / PBCH) resources used for L1-RSRP computation.

[0178] The time domain behavior of CSI-RS resource(s) within the CSI resource setting included in the CSI-ResourceConfig IE is indicated by the upper layer parameter resourceType, and can be configured as aperiodic, periodic, or quasi-persistent. For periodic and quasi-persistent CSI resource settings, the number S of configured CSI-RS resource sets is limited to '1'. For periodic and quasi-persistent CSI resource settings, the configured periodicity and slot offset are determined based on the numerology (e.g., subcarrier spacing) of the associated DL BWP, which is given by bwp-id.

[0179] When a UE is configured with multiple CSI-ResourceConfigs containing the same NZP CSI-RS resource ID, the same time domain behavior is configured for the CSI-ResourceConfigs.

[0180] When a UE is configured with multiple CSI-ResourceConfigs containing the same CSI-IM resource ID, the same time domain behavior is configured for the CSI-ResourceConfigs.

[0181] <S1.1.2_자원 세팅 설정(resource setting configuration)>

[0182] As mentioned above, CSI resource settings can be provided by a list of CSI resource sets. For aperiodic CSI, each trigger state configured using the upper-layer parameter CSI-AperiodicTriggerState is associated with one or more CSI-ReportConfigs, each of which links to a periodic, quasi-persistent, or aperiodic resource setting. A single report setting can be associated with up to three resource settings.

[0183] <S.1.1.3_CSI 계산(computation)>

[0184] When interference measurements are performed on CSI-IM, each CSI-RS resource for channel measurements is associated with a CSI-IM resource in the order of the CSI-RS resource and CSI-IM resource within the corresponding resource sets. The number of CSI-RS resources for channel measurements is equal to the number of CSI-IM resources. For CSI measurements, the UE assumes the following:

[0185] - Each NZP CSI-RS port configured for interference measurement corresponds to an interference transport layer.

[0186] - All interference transmission layers on the NZP CSI-RS ports for interference measurements consider the associated energy per resource element (EPRE) ratios.

[0187] - Other interference signals on resource elements of NZP CSI-RS resources for channel measurement, NZP CSI-RS resources for interference measurement, or CSI-IM resources for interference measurement.

[0188] For L1-SINR with dedicated interference measurement resources, the UE assumes:

[0189] - The total received power on the dedicated NZP CSI-RS resource for interference measurement or the dedicated CSI-IM resource for interference measurement corresponds to interference and noise.

[0190] <S1.2_CSI 보고>

[0191] For CSI reporting, the time and frequency resources available to the UE are controlled by the BS.

[0192] The CSI may include at least one of a channel quality indicator (CQI), a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), an SS / PBCH block resource indicator (SSBRI), a layer indicator (LI), a rank indicator (RI), or a L1-RSRP.

[0193] For CQI, PMI, CRI, SSBRI, LI, RI, L1-RSRP, the UE is configured with N≥1 CSI-ReportConfig reporting settings, M≥1 CSI-ResourceConfig resource settings, and a list of one or two trigger states (e.g., higher layer parameters aperiodicTriggerStateList and semiPersistentOnPUSCH-TriggerStateList). Each trigger state in the aperiodicTriggerStateList includes a list of associated CSI-ReportConfigs indicating channel and optionally interference resource set IDs. Each trigger state in the semiPersistentOnPUSCH-TriggerStateList includes one associated CSI-ReportConfig.

[0194] Additionally, the time domain behavior of CSI reporting supports periodic, quasi-persistent, and aperiodic behavior.

[0195] i) Periodic CSI reporting is performed on short PUCCH and long PUCCH. The periodicity and slot offset of periodic CSI reporting can be configured by RRC, and refer to CSI-ReportConfigIE.

[0196] ii) Semi-persistent (SP) CSI reporting is performed on short PUCCH, long PUCCH, or PUSCH. In case of SP CSI on short / long PUCCH, the periodicity and slot offset are set by RRC, and CSI reporting is activated / deactivated by a separate MAC control element (CE). In case of SP CSI on PUSCH, the periodicity of SP CSI reporting is set by RRC, but the slot offset is not set by RRC, and SP CSI reporting is activated / deactivated by DCI (e.g., DCI format 0_1). For SP CSI reporting on PUSCH, a separate RNTI (e.g., SP-CSI C-RNTI) may be used. The initial CSI reporting timing follows the PUSCH time domain allocation value indicated in the DCI, and subsequent CSI reporting timings follow the cycle configured by RRC. DCI format 0_1 ​​includes a CSI request field and can activate / deactivate a specific configured SP-CSI trigger state. SP CSI reporting can be activated / deactivated in the same or similar manner as the mechanism for data transmission on the SPS PUSCH.

[0197] iii) Aperiodic (AP) CSI reporting is performed on the PUSCH and can be triggered by DCI. In this case, information related to the triggering of aperiodic CSI reporting can be transmitted / indicated / configured via MAC CE. For AP CSI with AP CSI-RS, the AP CSI-RS timing is configured by RRC, and the timing for AP CSI reporting can be dynamically controlled by DCI.

[0198] NR does not apply the method of reporting CSI separately across multiple viewing instances (e.g., transmitting in the order of RI, WB PMI / CQI, and SB PMI / CQI) applied to PUCCH-based CSI reporting in LTE. Instead, NR restricts certain CSI reporting configurations on short / long PUCCHs, and defines CSI omission rules. In addition, with respect to AP CSI reporting timing, PUSCH symbol / slot positions are dynamically indicated by DCI. And candidate slot offsets can be configured by RRC. For CSI reporting, the slot offset Y can be configured for each reporting configuration. For UL-SCH, the slot offset K2 can be configured separately.

[0199] Two CSI latency classes (e.g., low latency class and high latency class) can be defined in terms of CSI computation complexity. For low latency CSI, it is wideband (WB) CSI including up to 4 ports Type-I codebook or up to 4-port non-PMI feedback CSI. High latency CSI refers to any CSI other than low latency CSI. For a normal UE, (Z, Z') is defined in units of OFDM symbols. Here, Z represents the minimum CSI processing time from receiving an aperiodic CSI triggering DCI to performing CSI reporting. In addition, Z' represents the minimum CSI processing time from receiving a CSI-RS for a channel / measurement to performing CSI reporting.

[0200] Additionally, the UE can report the number of CSIs it can compute simultaneously.

[0201] The UE computes the CSI parameters (if reported) assuming the following dependencies between the CSI parameters:

[0202] - LI is calculated conditioned on the reported CQI, PMI, RI and CRI.

[0203] - CQI is calculated based on reported PMI, RI and CRI.

[0204] - PMI is calculated based on the reported RI and CRI.

[0205] - RI is calculated based on the reported CRI.

[0206] In some scenarios (e.g., NR-based systems), CSI (feedback) can be broadly divided into two types: Type 1 CSI (also called Type I CSI) and Type 2 CSI (also called Type II CSI). Both Type 1 CSI (feedback) and Type 2 CSI (feedback) are codebook-based CSI reporting schemes, where Type 1 CSI is a PMI feedback scheme with normal spatial resolution and requires a relatively small payload size, while Type 2 CSI is a feedback scheme with higher spatial resolution and requires a relatively large payload size. Additionally, each type of CSI can have three reporting methods: wideband (WB) reporting > partial band (PB) reporting > subband (SB) reporting, depending on the size of the bandwidth over which the measurement is to be performed, where PB can mean an active BWP, WB can mean a bandwidth larger than PB, and SB can mean a bandwidth smaller than PB. Each type of CSI can be composed of CSI Part 1 (also referred to as 'Part 1 CSI') and CSI Part 2 (also referred to as 'Part 2 CSI'). For example, CQIs for CRI, RI, and / or the first codeword can be included in CSI Part 1, and CQIs for LI, PMI, and the second codeword can be included in CSI Part 2. In some implementations, CSI Part 1 may have a fixed payload size and may be used to identify the number of information bits in CSI Part 2, which are included in the entire CSI report before CSI Part 2. The payload of CSI Part 2 may be variable.

[0207] Reporting configurations for CSI can be aperiodic (using PUSCH), periodic (using PUCCH), or semi-persistent (using PUCCH and DCI-enabled PUSCH). CSI-RS resources can be periodic, semi-persistent, or aperiodic. Semi-persistent CSI-RS can be activated and deactivated as described in section 5.2.1.5.2 of 3GPP TS 38.214, and aperiodic CSI-RS can be configured and triggered / activated as described in section 5.2.1.5.1 of 3GPP TS 38.214. The following table, which illustrates triggering / activation for possible CSI-RS configurations, shows supported combinations of CSI reporting configurations and CSI-RS resource configurations, and how the CSI reporting is triggered for each CSI-RS resource configuration.

[0208]

[0209] Referring to 3GPP TS 38.321, the network may select CSI reporting state(s) to be reported from among the aperiodic CSI trigger states of the serving cell configured in the RRC configuration aperiodicTriggerStateList, which includes trigger states for dynamically selecting one or more aperiodic and quasi-persistent reporting configurations and / or for triggering one or more aperiodic CSI-RS resource sets for channel and / or interference measurements, by sending an Aperiodic CSI Trigger State Subselection MAC CE.

[0210] <S2. 네트워크 에너지 절약(Network Energy Saving, NES)>

[0211] Energy conservation of base stations (BSs) is a key consideration in wireless communication systems, including 3GPP, as it can contribute to building eco-friendly networks by reducing carbon emissions and reducing the operational expenditure (OPEX) of telecommunications operators. In particular, the introduction of 5G communications will require higher transmission rates, necessitating BSs to be equipped with more antennas and provide services over wider bandwidths and frequency bands. Consequently, recent studies have shown that BS energy costs have reached up to 20% of total OPEX. This heightened interest in BS energy conservation led to the approval of a new study item, "Study on Network Energy Savings," in 3GPP NR Release 18. For example, to improve the energy saving capability of BS from the perspective of transmission and reception, the study investigates how to achieve dynamic and / or semi-static and finer granularity adaptation of transmission and / or reception to more efficient operation with one or more network energy saving techniques in time, frequency, space and power domains using potential assistance / feedback of UE and potential UE assistance information.

[0212] Hereinafter, when a BS operates in a network energy saving (NES) mode for energy saving (ES), it can mean, for example, that the BS sets multiple OFF intervals (i.e., discontinuous transmixxion (DTX) intervals of the BS) in advance to turn off transmission of a specific DL signal during a specific time interval, and dynamically indicates one of the OFF intervals to indicate that the corresponding DL signal will not be transmitted during the predefined time interval, thereby achieving power consumption savings of the BS and UE. Hereinafter, the NES mode can also mean an operation mode in which power consumption savings of the BS and UE are achieved not only in the domain but also in the frequency domain, such as BWP switching, dynamic resource block (RB) adaptation, etc., and in the spatial domain, for example, when a specific receive antenna port of the BS is turned off semi-statically or dynamically, by the BS not performing transmission and / or reception through the corresponding antenna port.

[0213] In this specification, a scenario can be considered in which a BS obtains NES gain by controlling the number of APs to use when transmitting downlink signals / channels to a UE (or turning on / off some of the antenna elements / transceiver units (TxRUs) connected to the AP) or controlling the transmit power based on CSI reported by the UE for multiple antenna ports (APs) and / or multiple power offsets at once. If the BS can reduce the number of APs or reduce the transmit power based on the CSI reported by the UE, it can obtain energy saving (ES) gain by controlling unnecessary antenna elements (AEs) or transmit power. For example, a BS may include one CSI-RS resource or multiple CSI-RS resources in a CSI-RS resource set, and may set CSI assuming plural numbers of APs (e.g., 64 APs and 32 APs) and / or CSI for multiple CSI-RS to PDSCH power offset values ​​(e.g., -3 dB, 0 dB) for each CSI-RS resource in the CSI-RS resource set to be reported in one CSI report, and may determine an optimal number of APs and PDSCH transmission power / modulation and coding scheme (MCS) based on information in the CSI report, thereby reducing power consumption of the BS.

[0214] In this specification, NAP stands for "number of antenna ports" and PCO stands for "power control offset" (i.e., powerControlOffset). Here, PCO may mean either the RRC parameter powerControlOffset indicating the power offset of PDSCH RE to NZP CSI-RS RE with respect to non-zero power (NZP) CSI-RS RE, or powerControlOffsetSS indicating the ratio of NZP CSI-RS EPRE to SS / PBCH block EPRE. In the former case, PDSCH power may be adjusted based on CSI-RS power, and in the latter case, CSI-RS power may be adjusted based on SSB power.

[0215] The following is a description of the parameters powerControlOffset and powerControlOffsetSS described in 3GPP TS 38.331, and the parameters powerControlOffset and powerControlOffsetSS are provided to the UE by the BS via RRC signaling.

[0216] -powerControlOffset: This is the assumed ratio of PDSCH EPRE to NZP CSI-RS EPRE when the UE derives CSI feedback and takes values ​​in the range of [-8, 15] dB with a step size of 1 dB. For CQI calculation based on a pair of NZP CSI-RS resources, the powerControlOffset of each NZP CSI-RS resource within the pair of NZP CSI-RS resources for channel measurement is the assumed ratio of EPRE when the UE derives CSI feedback and takes values ​​in the range of [-8, 15] dB with a step size of 1 dB.

[0217] -powerControlOffsetSS: This is the assumed ratio of NZP CSI-RS EPRE to SS / PBCH block EPRE.

[0218] Below are described some implementations of this specification regarding how a UE configures a CSI report when a BS requests the UE to report multiple CSI sub-reports for a plurality of pre-configured CSI reporting sub-configurations for energy saving purposes via spatial (e.g., antenna element) and / or power (e.g., DL power) domain adaptation.

[0219] In this specification, the following may be considered in relation to CSI reporting:

[0220] A CSI reporting configuration may include sub-configurations. If a CSI reporting configuration includes L>1 sub-configurations, zero or more of the following parameters may be included for each sub-configuration for Type 1 spatial domain adaptation.

[0221] - Number of antenna elements N1 in the panel in the horizontal direction, number of antenna elements N2 in the panel in the vertical direction, number of antenna panels Ng

[0222] - Port subset indication if the resource set in the resource set within the resource setting can be associated with one or more spatial adaptation patterns.

[0223] - Rank restriction

[0224] - Codebook subset limitation

[0225] - Supported codebook types for PMI (e.g., Type-I or Type-II)

[0226] - Report quantity

[0227] - reportFreqConfiguration, which indicates the granularity of reporting in the frequency domain, including whether CSI reporting bands, PMI / CQI reporting are wideband, subband, or wideband and subband.

[0228] - When a resource set with multiple resources is configured within a resource setting and each resource is associated with only one spatial adaptation pattern, a group identifier of non-zero power (NZP) CSI-RS resource(s) within the resource set for channel measurement.

[0229] For example, one CSI reporting configuration (e.g., RRC configurationCSI-ReportConfig) may contain one or more CSI-ReportSubConfigs. The following RRC configurationCSI-ReportSubConfigs may be used to configure parameters of sub-configurations within a CSI reporting configuration.

[0230]

[0231] In Table 10, the parameter port-subsetIndicator indicates the number of ports of the NZP CSI-RS resources indicated in nzp-CSI-RS-resourceList (the value is equal to the portNumber of these NZP CSI-RS resources) and the (sub)set of CSI-RS antenna ports used for CSI calculation of the sub-configuration. In the bit stream, each bit corresponds to an antenna port. If the bit is set to 1, the corresponding antenna port is enabled for CSI calculation corresponding to the sub-configuration. If the bit is set to 0, the corresponding antenna port is not enabled for CSI calculation corresponding to the sub-configuration.

[0232] In Table 10, the parameter nzp-CSI-RS-resourceList is a list of NZP CSI-RS resources for the sub-configuration, which is a (sub)set of NZP CSI-RS resource(s) of the CSI-RS resource set for channel measurement associated with the sub-configuration in the CSI reporting configuration. A value of 0 refers to the first NZP CSI-RS resource of the CSI-RS resource set, a value of 1 refers to the second NZP CSI-RS resource of the CSI-RS resource set, and so on. The CSI reporting configuration includes an ID of a CSI-ResourceConfigIE regarding a CSI-RS resource set for channel measurement, and the CSI-ResourceConfigIE defines a group of one or more NZP-CSI-RS-ResourceSet, CSI-IM-ResourceSet and / or CSI-SSB-ResourceSet.

[0233] In Table 10, when powerControlOffset is set within the NZP CSI-RS resource indicated by nzp-CSI-RS-Resource, the power offset of the PDSCH RE for the NZP CSI-RS RE is equal to powerControlOffset.

[0234] In Table 10, the parameter port-subsetIndicator may correspond to the NAP-related settings described above, and the parameter powerOffset may correspond to the PCO-related settings described above.

[0235] A BS can turn on or off certain spatial elements (in this specification, spatial elements may mean antenna ports, active transceiver chains, panels, or TRPs) or adjust the power value for a downlink signal / channel for the purpose of NES. To dynamically apply various NES techniques in these power and power domains, the BS can associate CSI-RS resources (sets) with different antenna ports for a single CSI reporting setting (e.g., CSI-ReportConfig) or associate multiple power offsets (e.g., parameter powerControlOffset, which is a power offset value between PDSCH and CSI-RS, parameter powerControlOffsetSS, which is a power offset value between SSS and CSI-RS, etc.).

[0236] Meanwhile, at least one CSI framework may be introduced among the following methods.

[0237] - Method#1: Multiple CSI-RS resource sets are linked for one CMR (CMR is an abbreviation for channel measurement resource, which can be set by parameter resourcesForChannelMeasurement) or one IMR (IMR is an abbreviation for interference measurement resource, which can be set by parameter csi-IM-ResourcesForInterference or nzp-CSI-RS-ResourcesForInterference) within the CSI-ReportConfig configuration. For example, for CMR, CSI-RS resource set#1 and CSI-RS resource set#2 are linked, and the CSI-RS resources belonging to set#1 can be configured with 16 antenna ports (APs) and the CSI-RS resources belonging to set#2 can be configured with 8 APs.

[0238] - Method#2: When there is one CSI-RS resource set linked to one CMR or one IMR in the CSI-ReportConfig configuration, it is composed of one or more CSI-RS resources with different properties such as the number of APs and / or power offsets in the set. For example, for CSI-RS resource set#1 configured as CMR, CSI-RS resource#1 belonging to set#1 can be composed of 16 APs (or the power offset#1 value is set), and CSI-RS resource#2 belonging to the same set can be composed of 8 APs (or the power offset#2 value is set).

[0239] - Method#3: When there is a CSI-RS resource set linked to a CMR or an IMR in the CSI-ReportConfig configuration, some or all of the CSI-RS resource(s) within the set can be configured with multiple AP numbers and / or power offsets. For example, for CSI-RS resource set#1 configured with CMR, CSI-RS resource#1 belonging to set#1 can be configured with up to 16 APs, and CSI reporting utilizing some of the AP(s) can be configured, or CSI-RS resource#2 belonging to the same set can be configured with multiple power offset values, and CSI reporting utilizing all or some of the power offsets can be configured.

[0240] Under the above CSI framework, a CSI reporting method can be defined through at least one of the following options.

[0241] - Option#1: CSIs considering multiple AP numbers and / or multiple power offset values ​​set in a single CSI report can all be included in a single CSI report. Alternatively, CSIs considering multiple AP numbers and / or multiple power offsets through configuration / instruction of the base station (in this case, the AP numbers and / or power offsets set / instructed through the BS may be part of the AP numbers and / or power offset values ​​set in the corresponding CSI report) can be included in a single CSI report.

[0242] - Option#2: Even if multiple AP counts and / or multiple power offset values ​​are set in one CSI report, CSIs considering a single AP count and / or a single power offset can be included in one CSI report through the BS's configuration / instruction.

[0243] - Option#3: Even if multiple AP numbers and / or multiple power offset values ​​are set in one CSI report, CSIs considering some AP numbers and / or some power offsets may be included in one CSI report through the UE's judgment / decision (using criteria set in advance by the BS or pre-defined).

[0244] A CSI-ReportConfig configuration may have L(>1) sub-configurations, each of which may correspond to a spatial or power domain adaptation pattern. The spatial domain adaptation pattern may correspond to a specific number of antenna ports (or antenna port on / off pattern) or to a specific CSI-RS power value (e.g., a CSI-RS power value determined by the powerControlOffsetSS parameter, which is a power offset value between SSS and CSI-RS, since turning off some antenna elements corresponding to one antenna port may affect the CSI-RS power value). When Method#2 is applied, when the CSI-RS index #n1 (i.e., CSI-RS resource index #n1) belonging to the resource set is set to the number of A1 APs (or P1 power value) and the CSI-RS index #n2 belonging to the same set is set to the number of A2 APs (or P2 power value), the sub-configuration index #s1 is set to be linked to the CSI-RS index #n1 and the sub-configuration index #s2 is set to be linked to the CSI-RS index #n2, so that a different spatial domain adaptation pattern can be set for each sub-configuration. When applying Method#3, when the number of A1 APs (or P1 / P2 power values) is set for CSI-RS index #n1 belonging to the resource set, the number of A1 APs (or P1 power value) is linked to sub-configuration index #s1, and the number of A2 APs (or P2 power value) which is less than A1 constituting CSI-RS index #n1 is linked to sub-configuration index #s2, so that the spatial domain adaptation pattern can be set differently for each sub-configuration. In addition, the power domain adaptation pattern means a power offset value (e.g., which may mean that the power offset value determined by the parameter powerControlOffset, which is the power offset value between PDSCH and CSI-RS, and the parameter powerControlOffsetSS, which is the power offset value between SSS and CSI-RS, are changed. In case of applying Method#2, when the CSI-RS index #n1 belonging to the resource set is set to the P1 power value and the CSI-RS index #n2 belonging to the same set is set to the P2 power value, the sub-configuration index #s1 is set to be linked with the CSI-RS index #n1 and the sub-configuration index #s2 is set to be linked with the CSI-RS index #n2, so that the power domain adaptation pattern can be set differently for each sub-configuration. When Method#3 is applied, when the P1 power value (and the P2 power value) are set for the CSI-RS index #n1 belonging to the resource set, the P1 power value is linked to the sub-configuration index #s1 and the P2 power value is linked to the sub-configuration index #s2, so that the power domain adaptation pattern can be set differently for each sub-configuration. A CSI report composed of CSIs (i.e., CSI sub-reports) corresponding to N (N value greater than or equal to L and less than or equal to 1) sub-configurations among the L sub-configurations (using one of the methods of Option#1 / 2 / 3 above) can be fed back to the BS.

[0245] However, when configuring CSIs corresponding to multiple NAP and / or power control offset (PCO) values ​​within a single CSI report (i.e., CSI sub-reports), the UE's computational complexity and CSI overhead / payload size may become very large compared to configuring the CSI report with the number of antenna ports (NAP) and PCO value, which may reduce the efficiency of configuring and transmitting CSI reports.

[0246] Meanwhile, in the NR system, when UCI is piggybacked on PUSCH, the beta_offset value may be set / indicated by a semi-static setting by RRC and / or a dynamic indication by a UL grant depending on the UCI type and the payload size of the corresponding UCI type. beta_offset may be defined as a coding rate adjustment parameter for UCI piggybacking. For example, beta_offset may be set separately for HARQ-ACK, CSI Part 1, and CSI Part 2. For HARQ-ACK, beta_offset values ​​may be set (respectively) for a payload size of less than 3 bits, a payload size of 3 bits or more but less than or equal to 11 bits, and a payload size exceeding 11 bits. For CSI Part 1 and CSI Part 2, separate beta_offset values ​​may be set for a payload size of less than or equal to 11 bits and a payload size exceeding 11 bits, respectively. For example, the number Q' of coded symbols carrying a specific UCI (e.g., HARQ-ACK, CSI, etc.) can be set as in the following mathematical equation.

[0247]

[0248] Here, O is the payload size of the corresponding UCI, M PUSCH sc is the size of the resource area on the allocated frequency axis of PUSCH, N PUSCH symb is the size of the allocated time axis resource region of PUSCH, K r may mean the information bit size of code block r (i.e., the number of bits in code block r). According to the mathematical formula above, this means that the corresponding UCI can be transmitted for a maximum of 4 symbols within the allocated PUSCH region, and a larger beta_offset value may mean that more coded symbols are transmitted for the corresponding UCI, i.e., a lower coding rate.

[0249] If the amount of CSI to be included in a CSI report is greater than the amount of resources allocated for CSI reporting (e.g., the payload size of the CSI report is larger than the payload size that the UL channel for reporting the CSI can carry), priority and omission rules may be needed to determine which CSI to sequentially omit or move to another CSI report based on priority.

[0250] Figure 8 illustrates the priorities of Part 2 CSI.

[0251] For UCI with a significantly large payload size, such as Part 2 CSI, some information may be omitted and not all information may be transmitted, depending on the size of the resource region of the PUCCH and / or PUSCH to be transmitted. Priorities may be set / determined based on the type of information carried on the PUCCH and / or PUSCH.

[0252] When the number of CSI types to be reported in one slot (i.e., the number of CSI reports) is N, the priority for the entire Part 2 CSI can be determined based on whether it is WB CSI, SB CSI, CSI type, etc., as shown in Figure 3-1, when the number of CSI types to be reported in one slot is N (e.g., which can be linked to the CSI process index, CC index), the priority for the entire Part 2 CSI can be determined based on whether it is WB CSI, SB CSI, CSI type, etc., and blocks with lower priorities can be sequentially omitted. For example, referring to FIG. 8, depending on the amount of information that the uplink channel to be used for transmission can carry, Part 2 CSI block(s) may be sequentially omitted from the UCI to be transmitted, starting with Part 2 CSI of odd RBs for CSI report #N.

[0253] According to section 5.2.3 of 3GPP TS 38.214, when CSI reported via PUSCH consists of two parts (i.e., Part 1 and Part 2), the UE may omit a portion of Part 2 CSI according to the priority order in the following table. According to the existing Part 2 CSI omission rules, when omitting Part 2 CSI for a specific priority level, the UE must omit all CSI for that priority level. In the following table, N Rep is the number of CSI reports set to be carried on PUSCH, priority 0 is the highest priority, priority 2N Rep This is the lowest priority, and CSI report #n is N as defined in section 5.2.5 of 3GPP TS 38.214. Rep The nth smallest Pri among the dog CSI reports iCSI Corresponds to a CSI report with values ​​(y, k, c, s).

[0254] The following table lists the priority reporting levels for Part 2 CSI.

[0255]

[0256] Referring to section 5.2.5 of 3GPP TS 38.214, CSI reports have priority value Pri iCSI (y, k, c, s) = 2*N cells *M s *y + N cells *M s *k + M s * is associated with c + s, where

[0257] - y=0 for aperiodic CSI reports to be carried on PUSCH, y=1 for semi-persistent CSI reports to be carried on PUSCH, y=3 for periodic CSI reports to be transmitted on PUCCH;

[0258] - k=0 for CSI reports carrying L1-RSRP or L1-SINR and k=1 for CSI reports not carrying L1-RSRP or L1-SINR;

[0259] - c is the serving cell index and N cells is the value of the upper layer parameter maxNrofServingCells regarding the maximum number of serving cells;

[0260] --An information element (IE) used to set up reporting on a cell containing LTM-CSI-ReportConfig. For CSI reporting set up with LTM-CSI-ReportConfig, c is the serving cell index value for which the reporting configuration is set.

[0261] - s is the reportConfigID used to identify the measurement reporting settings, and M s is the value of the upper layer parameter maxNrofCSI-ReportConfigurations regarding the maximum number of report configurations.

[0262] --For CSI reporting set to LTM-CSI-ReportConfig, s is LTE-CSI-ReportConfigID and M s is the value of the upper layer parameter maxNrofLTM-CSI-ReportConfigurations.

[0263] If the associated Pri iCSI If the (y, k, c, s) values ​​are lower for the first report than for the second report, the first CSI report is said to have priority over the second CSI report.

[0264] CSI reports set with LTM-CSI-ReportConfig are Pri in case of conflict with CSI reports(s) set with CSI-ReportConfig. iCSI(y, k, c, s) values ​​have higher priority than all CSI report(s) set with CSI-ReportConfig.

[0265] <Method #1> When a NES multi-CSI report is transmitted in which multiple CSI corresponding to multiple sub-configurations are transmitted as a single CSI report, a method of omitting / dropping priority 0 CSI reports (e.g., Part 2 wideband reports)

[0266] > (1) A method of applying sub-configuration unit omission / drop only when a priority 0 CSI report is composed of only one NES multi-CSI report or multiple NES multi-CSI reports.

[0267] > (2) If a priority 0 CSI report contains a legacy CSI report and at least one NES multi-CSI report.

[0268] >> A. The method of dropping the entire priority 0 as before or dropping it partially only by reporting unit rather than by sub-setting unit

[0269] >> B. A method of sequentially omitting / dropping only Part 2 wideband CSI reports corresponding to NES multi-CSI report(s) in sub-configuration units without omitting / dropping Part 2 wideband CSI reports corresponding to legacy CSI report(s).

[0270] >> C. Legacy CSI report is dropped starting from the highest index report, but legacy Part 2 wideband CSI is dropped by report unit and NES Part 2 wideband sub-config CSI is dropped by sub-config unit.

[0271] In the above methods (1) and (2), when omitting / dropping NES multi-CSI reports (e.g., CSI reports including N CSI sub-reports for N sub-configurations among L sub-configurations included in a CSI report configuration) on a sub-configuration basis, the UE sequentially omits / drops all but the Part 2 wideband CSI reports corresponding to the lowest sub-configuration index in each NES multi-CSI report, and if the remaining CSI cannot be included in the CSI report to be transmitted, the UE may omits / drop all priority 0 CSI reports.

[0272] Figure 9 illustrates the omission of Part 2 wideband CSI according to legacy rules.

[0273] Referring to Table 11, the priority reporting levels for Part 2 CSI are defined such that Part 2 subband CSI of CSI report #n is divided into two parts of even subband and odd subband, and the priority for Part 2 subband CSI of even subbands (hereinafter, even subband CSI) is higher than the priority for Part 2 subband CSI of odd subbands (hereinafter, odd subband CSI), and the omission / drop is sequentially performed starting from the odd subband CSI of the CSI report with lower priority, and continues until the omission / drop of Part 2 CSI can be contained in the resources allocated for CSI reporting. However, in the case of Part 2 wideband report containing wideband CSI, CSI reports #1 to #N Rep All of them have the same priority 0, and if the payload size is larger than the resources allocated for CSI reporting even after the UE has omitted / dropped all subband CSIs, the entire Part 2 wideband report is omitted / dropped. That is, in the case of Part 2 wideband reporting, the legacy behavior is not to perform omission / drop of (CSI) report units.

[0274] Figure 10 illustrates the structure of Part 2 CSI for priority 0 including multi-CSI reporting.

[0275] For NES multi-CSI reports containing multiple CSIs corresponding to multiple sub-configurations (i.e., multiple CSI sub-reports) in a single CSI report, the payload size may be significantly larger than a legacy CSI report without CSI corresponding to the sub-configuration, depending on the sub-configuration for which the CSI (sub-report) is configured / instructed to be included. For example, a Part 2 wideband CSI report corresponding to priority 0 may also occupy a large payload size per sub-configuration index, as illustrated in FIG. 10.

[0276] If the legacy rules are applied to NES multi-CSI reports (e.g., CSI report #m in FIG. 10) to omit / drop all Part 2 wideband CSI corresponding to priority 0, the likelihood of all priority 0 CSI report(s) being omitted / dropped increases. In this case, a BS that receives inaccurate or insufficient CSI may have difficulty performing accurate / appropriate spatial / power domain adaptation based on the information.

[0277] Therefore, in some implementations of this specification, it is considered to define detailed priority reporting levels for CSI within priority 0, similar to Part 2 subband CSI reporting, and allow the UE to sequentially skip / drop CSIs from lower priority ones, thereby feeding back more accurate and more CSI to the BS compared to dropping the entire Part 2 wideband report.

[0278] In one approach, it may be considered to apply omission / drop of Part 2 CSI on a per-subconfiguration basis only when the priority 0 CSI report consists of only one NES multi-CSI report or multiple NES multi-CSI reports. For example, if the priority 0 CSI report consists of only one NES multi-CSI report or multiple NES multi-CSI reports, instead of omission / dropping the entire priority 0 (i.e., the entire Part 2 CSI for priority 0), a new priority reporting level may be defined within priority 0 with lower priority as the CSI report index and sub-configuration index increase, and the UE may perform omission / drop on a per-subconfiguration basis (i.e., per CSI sub-report basis).

[0279] Figure 11 illustrates CSI omission according to some implementations of the present specification. In particular, Figure 11 illustrates CSI omission according to some implementations of the present specification that omit / drop CSI on a sub-configuration basis when there are only multi-CSI reports within priority 0.

[0280] For example, if only NES multi-CSI reporting #m is set within priority 0, then according to legacy rules, even after subband CSIs are sequentially dropped according to priority, if the CSI payload size is too large to be included in the CSI report, the entire priority 0 is dropped. However, if the priority reporting level is defined such that a larger sub-configuration index within priority 0 indicates a lower priority CSI report, then omission / drop of Part 2 CSI for priority 0 can be performed on a sub-configuration basis, and omission / drop of Part 2 CSI for priority 0 can be performed sequentially to the left starting from Part 2 wideband sub-configuration #x as illustrated in FIG. 11.

[0281] In some implementations, if priority 0 consists of only multiple NES multi-CSI reports, the UE may perform the omission / drop (of Part 2 CSI) on a sub-configuration basis as described above, and if it drops up to Part 2 wideband sub-configuration #2 report #m+1 (i.e., Part 2 wideband CSI for sub-configuration #2 for CSI report #m+1), it may be considered to not drop Part 2 wideband sub-configuration #1 report #m+1 and start dropping sequentially again from Part 2 wideband sub-configuration g#x report #m. That is, only the Part 2 wideband CSI report corresponding to the lowest sub-configuration index in each NES multi-CSI report is sequentially omitted / dropped, and if the rest cannot be included in the CSI report (i.e., if the Part 2 wideband CSI(s) corresponding to the lowest sub-configuration index(es) cannot be accommodated in a single UL channel transmission), then the entire priority 0 CSI report can be omitted / dropped.

[0282] If a priority 0 CSI report (i.e., Part 2 CSI for priority 0) is accompanied by a legacy CSI report (i.e., CSI for legacy CSI report(s)) and at least one NES multi-CSI report, some implementations of this specification may consider dropping the entire priority 0 report (i.e., the entire Part 2 CSI for priority 0) as per the legacy rule, without dropping on a sub-configuration basis, or only partially dropping on a CSI report basis rather than on a sub-configuration basis. For example, referring to FIG. 10, Part 2 CSI for priority 0 may be dropped first, followed by Part 2 Wideband Report #n (i.e., Part 2 Wideband CSI for CSI report #n), followed by Part 2 Wideband Report #m (i.e., all Part 2 Wideband CSI(s) for CSI report #m), and so on.

[0283] Alternatively, sequential omission / dropping of sub-configuration units may be applied only to Part 2 wideband CSI reports corresponding to NES multi-CSI report(s) without omission / dropping Part 2 wideband CSI reports corresponding to legacy CSI report(s). For example, referring to FIG. 10, the UE may perform CSI dropping sequentially in sub-configuration units starting from Part 2 wideband sub-configuration #x report#m, which is an NES multi-CSI report, without dropping Part 2 wideband report #n (i.e., Part 2 wideband CSI for CSI report #n). At this time, in some implementations, when the UE performs omitting / dropping of NES multi-CSI reports on a sub-configuration basis (e.g., for a CSI report containing CSI sub-report(s) with Part 2 CSI corresponding to the sub-configuration(s) included in CSI-ReportConfig, where omitting / dropping of Part 2 wideband CSI is performed at the sub-configuration level), it may sequentially omitting / drop all but the Part 2 wideband CSI report corresponding to the lowest sub-configuration index within each multi-CSI report, and if it still cannot accommodate it in the CSI report (i.e., if the Part 2 wideband CSI(s) corresponding to the lowest sub-configuration index(es) cannot be accommodated in one UL channel transmission), it may omitting / drop all priority 0 CSI reports (i.e., all Part 2 CSI for priority 0).

[0284] Alternatively, in some implementations of this specification, when legacy CSI reporting and NES multi-CSI reporting coexist within priority 0, the UE may drop legacy CSI reports starting with the report with the highest index, but may drop legacy Part 2 wideband CSI on a per-report basis and NES Part 2 wideband sub-configuration CSI (i.e., Part 2 wideband CSI of a CSI sub-report corresponding to a sub-configuration) on a per-sub-configuration basis. For example, referring to FIG. 10, the UE sequentially drops from Part 2 Wideband Report #n, and when it is the turn to drop an NES Multi-CSI report, the UE sequentially drops Part 2 CSI for CSI Report #m starting from Part 2 Wideband Sub-configuration #x Report #m (i.e., Part 2 Wideband CSI of the CSI sub-report corresponding to sub-configuration #x in the CSI Report configuration for CSI Report #m), but after dropping all Part 2 CSI for CSI Report #m up to Part 2 Wideband Sub-configuration #1 Report #m, it drops the CSI report with the next lower index, and so on, and can perform omission / drop of Part 2 CSI for priority 0. If Report #(m-1) following Report #m is also an NES Multi-CSI report, omission / drop of CSI for Report #(m-1) can also be sequentially performed in units of sub-configurations.

[0285] In some implementations of the present specification described above, CSI omission for priority 0 may be performed until certain conditions are satisfied. For example, Part 2 CSI omission for priority 0 may be performed until the amount of CSI to be reported is less than or equal to the amount of information that the uplink channel for CSI reporting can carry. Alternatively, as another example, considering that the code rate is equal to the payload size divided by the codeword bit size, Part 2 CSI omission for priority 0 may be performed until the Part 2 CSI code rate is less than or equal to a predetermined maximum code rate.

[0286] The BS may perform CSI reception assuming that the UE will perform CSI reporting according to some implementations of the present specification described above.

[0287] According to some implementations of this specification, sub-configuration-level CSI omission is performed when one or more NES multi-CSI reports are included in a priority 0 CSI report. In this case, as much CSI as possible is transmitted compared to omitting the entire priority 0 CSI report, enabling the BS to perform efficient scheduling (e.g., MCS adaptation, etc.) for the UE based on the CSI.

[0288] Figure 12 illustrates the flow of CSI report transmission in a UE according to some implementations of the present specification.

[0289] A UE may perform operations according to some implementations of the present disclosure in connection with CSI reporting. The UE may include at least one transceiver; at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present disclosure. A processing device for the UE may include at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present disclosure. A computer-readable (non-transitory) storage medium may store at least one computer program comprising instructions that, when executed by at least one processor, cause the at least one processor to perform operations according to some implementations of the present disclosure. A computer program or computer program product may be recorded on at least one computer-readable (non-transitory) storage medium and may contain instructions that, when executed, cause (at least one processor) to perform operations according to some implementations of the present specification.

[0290] A method performed by the UE, or in the UE, the processing device, the computer-readable (non-transitory) storage medium, and / or the computer program product, the operations may include: determining a physical uplink channel within a slot for reporting channel state information (CSI); performing omission of Part 2 CSI for one or more CSI reports configured to be transmitted in the slot to determine a CSI payload (S1201), wherein the omission of Part 2 CSI is performed in priority order starting from the lowest priority level, and based on the omission of Part 2 CSI for priority 0 being performed, the omission of Part 2 CSI for priority 0 is performed at a CSI reporting sub-configuration level for CSI reports n that include CSI corresponding to one or more CSI reporting sub-configurations; and transmitting the CSI payload on the physical uplink channel within the slot (S1203).

[0291] Figure 13 illustrates the flow of receiving CSI reports at a BS according to some implementations of this specification.

[0292] A BS may perform operations according to some implementations of the present disclosure in connection with receiving a CSI report. The BS may include at least one transceiver; at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present disclosure. A processing device for the BS may include at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present disclosure. A computer-readable (non-transitory) storage medium may store at least one computer program comprising instructions that, when executed by the at least one processor, cause the at least one processor to perform operations according to some implementations of the present disclosure. A computer program or computer program product may be recorded on at least one computer-readable (non-transitory) storage medium and may contain instructions that, when executed, cause (at least one processor) to perform operations according to some implementations of the present specification.

[0293] A method performed by the BS, or in the BS, the processing device, the computer-readable (non-transitory) storage medium, and / or the computer program product, the operations may include: determining a physical uplink channel in a slot for reporting channel state information (CSI); receiving (S1301) a CSI payload on the physical uplink channel in the slot. The CSI payload includes CSI after omission of Part 2 CSI for one or more CSI reports scheduled in the slot, and the omission of Part 2 CSI is performed in priority order starting from the lowest priority level, and based on the omission of Part 2 CSI for priority 0 being performed, the omission of Part 2 CSI for priority 0 may be performed at a CSI reporting sub-configuration level for CSI reports n that include CSI corresponding to one or more CSI reporting sub-configurations. The method or operations performed by the BS may include: obtaining CSI with part 2 CSI for priority 0 omitted from the CSI payload (S1303).

[0294] In some implementations related to FIG. 12 or FIG. 13, the omission of the Part 2 CSI for the priority 0 may be performed in descending order of sub-configuration index, starting from the CSI reporting sub-configuration of a larger sub-configuration index among the CSI reporting sub-configurations for the CSI report n, to the CSI reporting sub-configuration level.

[0295] In some implementations related to FIG. 12 or FIG. 13, the omission of the Part 2 CSI for the priority 0 may be performed in descending order of CSI report index, starting with the CSI report of the largest CSI report index, for the multiple CSI reports related to the priority 0.

[0296] In some implementations related to FIG. 12 or FIG. 13, the omission of the Part 2 CSI for the priority 0 may be performed at the CSI reporting sub-configuration level, based on each CSI report associated with the priority 0 including CSI corresponding to at least one CSI reporting sub-configuration.

[0297] In some implementations related to FIG. 12 or FIG. 13, the omission of the Part 2 CSI for priority 0 may be performed at the CSI reporting sub-configuration level for a CSI report that includes CSI for at least one CSI reporting sub-configuration among the multiple CSI reports associated with priority 0.

[0298] In some implementations related to FIG. 12 or FIG. 13, the omission of the Part 2 CSI for priority 0 may not be performed for a CSI report that does not include CSI for any CSI report sub-set among the multiple CSI reports related to priority 0.

[0299] In some implementations related to FIG. 12 or FIG. 13, the omission of the Part 2 CSI for priority 0 may be performed until a predetermined condition is met.

[0300] In some implementations related to FIG. 12 or FIG. 13, the predetermined condition may include: the size of the CSI payload is less than or equal to the amount of CSI that the physical uplink channel can carry.

[0301] As described above, the examples disclosed herein are provided to enable those skilled in the art to implement and practice the present disclosure. While the examples have been described above with reference to the examples of the present disclosure, those skilled in the art will appreciate that various modifications and variations may be made to the examples of the present disclosure. Accordingly, the present disclosure is not intended to be limited to the examples described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0302] Implementations of this specification can be used in wireless communication systems, BSs, user equipment, and other equipment.

Claims

1. Determine the physical uplink channel within the slot for reporting channel state information (CSI); Determining the CSI payload by performing omission of Part 2 CSI for one or more CSI reports configured to be transmitted in the slot; and Including transmitting the CSI payload on the physical uplink channel within the slot, Omission of the above Part 2 CSI is performed in priority order starting from the lowest priority level, Based on the omission of Part 2 CSI for priority 0, which is the highest priority, the omission of Part 2 CSI for said priority 0 is performed at the CSI reporting sub-configuration level for CSI report n, which includes CSI corresponding to one or more CSI reporting sub-configurations. Method by user device.

2. In paragraph 1, Omission of the above Part 2 CSI for the above priority 0 is performed, for the above CSI report n, starting from the CSI report sub-set of a larger sub-set index among the CSI report sub-sets for the above CSI report n, in descending order of the sub-set index, to the CSI report sub-set level. Method by user device.

3. In paragraph 1, Omission of the above Part 2 CSI for the above priority 0 is performed in descending order of CSI report index, starting from the CSI report of the larger CSI report index, for multiple CSI reports related to the above priority 0. Method by user device.

4. In paragraph 1, Based on the fact that each CSI report associated with the priority 0 includes CSI corresponding to at least one CSI reporting sub-set, the omission of the Part 2 CSI for the priority 0 is performed at the CSI reporting sub-set level. Method by user device.

5. In paragraph 1, Omission of the above Part 2 CSI for the above priority 0 is performed at the CSI reporting sub-configuration level for a CSI report that includes CSI for at least one CSI reporting sub-configuration among the multiple CSI reports associated with the above priority 0. Method by user device.

6. In paragraph 5, The omission of the above Part 2 CSI for the above Priority 0 is not performed for a CSI report that does not include CSI for any CSI report sub-set among the multiple CSI reports associated with the above Priority 0. Method by user device.

7. In paragraph 1, Omission of the above Part 2 CSI for the above Priority 0 is performed until the predetermined condition is met. Method by user device.

8. In paragraph 7, The above-determined conditions include: The size of the CSI payload is less than or equal to the amount of CSI that the physical uplink channel can carry, Method by user device.

9. At least one processor; and At least one computer memory operably connectable to said at least one processor and storing instructions that, when executed, cause said at least one processor to perform operations, said operations comprising: Determine the physical uplink channel within the slot for reporting channel state information (CSI); Determining the CSI payload by performing omission of Part 2 CSI for one or more CSI reports configured to be transmitted in the slot; and Including transmitting the CSI payload on the physical uplink channel within the slot, Omission of the above Part 2 CSI is performed in priority order starting from the lowest priority level, Based on the omission of Part 2 CSI for priority 0, which is the highest priority, the omission of Part 2 CSI for said priority 0 is performed at the CSI reporting sub-configuration level for CSI report n, which includes CSI corresponding to one or more CSI reporting sub-configurations. device.

10. In a computer-readable storage medium, The storage medium stores at least one program code comprising instructions that, when executed, cause at least one processor to perform operations, the operations comprising: Determine the physical uplink channel within the slot for reporting channel state information (CSI); Determining the CSI payload by performing omission of Part 2 CSI for one or more CSI reports configured to be transmitted in the slot; and Including transmitting the CSI payload on the physical uplink channel within the slot, Omission of the above Part 2 CSI is performed in priority order starting from the lowest priority level, Based on the omission of Part 2 CSI for priority 0, which is the highest priority, the omission of Part 2 CSI for said priority 0 is performed at the CSI reporting sub-configuration level for CSI report n, which includes CSI corresponding to one or more CSI reporting sub-configurations. Storage media.

11. Determine the physical uplink channel within the slot for reporting channel state information (CSI); and Receiving a CSI payload on the physical uplink channel within the slot, The above CSI payload includes CSI after omission of Part 2 CSI for one or more CSI reports scheduled in the above slot, Omission of the above Part 2 CSI is performed in priority order starting from the lowest priority level, Based on the omission of Part 2 CSI for priority 0, which is the highest priority, the omission of Part 2 CSI for said priority 0 is performed at the CSI reporting sub-configuration level for CSI report n, which includes CSI corresponding to one or more CSI reporting sub-configurations. Method by base station.

12. At least one transmitter / receiver; at least one processor; and At least one computer memory operably connectable to said at least one processor and storing instructions that, when executed, cause said at least one processor to perform operations, said operations comprising: Determining a physical uplink channel within a slot for reporting channel state information (CSI); and Receiving a CSI payload on the physical uplink channel within the slot, The above CSI payload includes CSI after omission of Part 2 CSI for one or more CSI reports scheduled in the above slot, Omission of the above Part 2 CSI is performed in priority order starting from the lowest priority level, Based on the omission of Part 2 CSI for priority 0, which is the highest priority, the omission of Part 2 CSI for said priority 0 is performed at the CSI reporting sub-configuration level for CSI report n, which includes CSI corresponding to one or more CSI reporting sub-configurations. Base station.

13. In paragraph 12, Omission of the above Part 2 CSI for the above priority 0 is performed, for the above CSI report n, starting from the CSI report sub-set of a larger sub-set index among the CSI report sub-sets for the above CSI report n, in descending order of the sub-set index, to the CSI report sub-set level. Base station.

14. In paragraph 12, Omission of the above Part 2 CSI for the above priority 0 is performed in descending order of CSI report index, starting from the CSI report of the larger CSI report index, for multiple CSI reports related to the above priority 0. Base station.

15. In paragraph 12, Based on the fact that each CSI report associated with the priority 0 includes CSI corresponding to at least one CSI reporting sub-set, the omission of the Part 2 CSI for the priority 0 is performed at the CSI reporting sub-set level. Base station.

16. In paragraph 12, Omission of the above Part 2 CSI for the above priority 0 is performed at the CSI reporting sub-configuration level for a CSI report that includes CSI for at least one CSI reporting sub-configuration among the multiple CSI reports associated with the above priority 0. Base station.

17. In paragraph 16, The omission of the above Part 2 CSI for the above Priority 0 is not performed for a CSI report that does not include CSI for any CSI report sub-set among the multiple CSI reports associated with the above Priority 0. Base station.

18. In paragraph 12, Omission of the above Part 2 CSI for the above Priority 0 is performed until the predetermined condition is met. Base station.

19. In paragraph 18, The above-determined conditions include: The size of the CSI payload is less than or equal to the amount of CSI that the physical uplink channel can carry, Base station.

Images