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

Abstract

A user equipment may: receive a PUCCH-related configuration including PUCCH resource information for each rank; determine CSI to be reported; determine a PUCCH resource on the basis of the PUCCH-related configuration and a rank related to the CSI; and transmit, on the PUCCH resource, a CSI report including the CSI.

Description

Method performed by a user device, user device, processing device and storage medium, and method performed by a base station and base station

[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] One technical challenge of this specification is to provide a method and / or process that can avoid or reduce resource waste or omission of channel state information.

[0006] 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.

[0007] In one aspect of the present disclosure, a method by a user device is provided. In another aspect of the present disclosure, the user device is provided, comprising: 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. In another aspect of the present disclosure, a processing device is provided, comprising: 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. In another aspect of the present disclosure, a computer-readable, non-transitory storage medium is provided, storing at least one program code comprising instructions that, when executed, cause the at least one processor to perform operations. The method or the operations include: receiving a physical uplink control channel (PUCCH) related configuration, the PUCCH related configuration including rank-specific PUCCH resource information; The method may include determining channel state information (CSI) to be reported; determining PUCCH resources based on the PUCCH-related settings and the rank associated with the CSI; and transmitting a CSI report including the CSI on the PUCCH resources.

[0008] In one aspect of the present disclosure, a method is provided by a base station. In another aspect of the present disclosure, a BS is provided, comprising: 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. The method or the operations may include: transmitting a physical uplink control channel (PUCCH) related configuration, the PUCCH related configuration including rank-specific PUCCH resource information; and receiving a CSI report including channel state information (CSI) on a PUCCH resource based on the PUCCH related configuration, wherein the PUCCH resource may be for a rank associated with the CSI.

[0009] In each aspect of this specification, information about the rank associated with the CSI may be transmitted or received in slot n.

[0010] In each aspect of this specification, the CSI report may be transmitted or received in slot n+D, where D is a predetermined non-negative integer.

[0011] In each aspect of the present specification, based on multiple CSI reports including the CSI report being multiplexed, information regarding respective (respective) ranks associated with the multiple CSI reports can be transmitted or received in the slot n.

[0012] In each aspect of the present specification, based on multiple CSI reports including the CSI report being multiplexed, information about the smallest or largest rank among the respective (respective) ranks associated with the multiple CSI reports can be transmitted or received in the slot n.

[0013] In each aspect of the specification, information may be provided to the user device regarding whether the smallest or largest value among the respective (respective) ranks associated with the plurality of CSI reports is reported.

[0014] In each aspect of the present specification, based on including a plurality of CSI reports including the CSI report, the PUCCH resource may be determined based on a smallest or largest rank among the respective (respective) ranks associated with the plurality of CSI reports.

[0015] In each aspect of this specification, information may be provided to the user equipment as to whether the PUCCH resource is determined based on the smallest value or the largest value among the rank values ​​to be reported.

[0016] In each aspect of this specification, the CSI report may include information regarding the rank associated with the CSI.

[0017] In each aspect of this specification, the number of resource blocks for the PUCCH resource can be determined based on the size of the CSI payload transmitted on the PUCCH resource.

[0018] 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.

[0019] According to some implementations of this specification, methods and / or processes may be provided that can avoid or reduce resource waste or omission of channel state information.

[0020] 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.

[0021] 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:

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

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

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

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

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

[0027] FIG. 6 illustrates physical channels used in a 3rd generation partnership project (3GPP)-based communication system, which is an example of a wireless communication system, and a signal transmission / reception process using the channels;

[0028] FIG. 7 and FIG. 8 are part of a physical uplink control channel (PUCCH) configuration provided by upper layer signaling;

[0029] Figure 9 illustrates the flow of a process related to channel state information (CSI).

[0030] FIG. 10 illustrates an example of time domain resource allocation of a physical downlink shared channel (PDSCH) by a physical downlink control channel (PDCCH) and an example of time domain resource allocation of a physical uplink shared channel (PUSCH) by a PDCCH;

[0031] Figure 11 illustrates a processing process on the transmission side for a transport block (TB);

[0032] Figure 12 illustrates a general functional architecture relevant to both functionality-based life cycle management (LCM) and model-based LCM;

[0033] Figure 13 illustrates the flow of operations based on an artificial intelligence (AI) / machine learning (ML) model;

[0034] FIG. 14 illustrates the flow of uplink control information transmission in a UE according to some implementations of the present specification;

[0035] Figure 15 illustrates the flow of receiving uplink control information at a BS according to some implementations of this specification.

[0036] 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.

[0037] 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.

[0038] In this specification, "A or B" can mean "only A", "only B", or "both A and B". In other words, in this specification, "A or B" can be interpreted as "A and / or B". For example, in this specification, "A, B or C" can mean "only A", "only B", "only C", or "any combination of A, B and C".

[0039] The slash ( / ) or comma used in this specification can mean "and / or." For example, "A / B" can mean "A and / or B." Accordingly, "A / B" can mean "only A," "only B," or "both A and B." For example, "A, B, C" can mean "A, B, or C."

[0040] In this specification, "at least one of A and B" may mean "only A", "only B" or "both A and B". Additionally, in this specification, the expressions "at least one of A or B" or "at least one of A and / or B" may be interpreted identically to "at least one of A and B".

[0041] Additionally, in this specification, “at least one of A, B and C” can mean “only A”, “only B”, “only C”, or “any combination of A, B and C”. Additionally, “at least one of A, B or C” or “at least one of A, B and / or C” can mean “at least one of A, B and C”.

[0042] Additionally, in this specification, terms such as “first,” “second,” etc. are used only to distinguish one component from another and are not used to limit the components, and do not limit the order or importance between the components unless specifically limited. Accordingly, a first component in one embodiment of this specification may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment.

[0043] In the following explanation, ‘when ~, if ~, in case of ~’ can be replaced with ‘based on ~.’

[0044] In this specification, higher layer parameters can be configured, preset, or predefined for the UE. For example, the BS can transmit higher layer parameter(s) to the UE. For example, the UE can transmit parameters such as capabilities to the BS as higher layer parameters. For example, the higher layer parameters can be transmitted via radio resource control (RRC) signaling or medium access control (MAC) signaling.

[0045] In this specification, "configured or pre-configured" information / state / parameters can be interpreted as information / state / parameters being provided / pre-provided to the UE through pre-defined signaling from the BS (e.g., system information block (SIB), medium access control (MAC), radio resource control (RRC)). In this specification, "defined or pre-defined" information / state / parameters can be interpreted as information that the BS and the UE know in advance or pre-store without signaling between the BS and the UE.

[0046] Technical features individually described within a single drawing in this specification may be implemented individually or simultaneously.

[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 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 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.

[0058] 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.

[0059] 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.

[0060] 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.

[0061] 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.

[0062] 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.

[0063] As more and more communication devices demand greater communication capacity, the need for improved mobile broadband communication is growing compared to existing radio access technology (RAT). 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 being discussed. Currently, 3GPP is 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.

[0064] 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.

[0065] 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).

[0066] 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.

[0067] 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.

[0068] 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.

[0069] 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.

[0070] 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.

[0071] 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.

[0072] 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.

[0073] 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.

[0074] 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.

[0075] 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).

[0076] 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.

[0077] 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, transitory memory, non-transitory memory, and / or a combination thereof.

[0078] 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.

[0079] 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.

[0080] 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.

[0081] 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.

[0082] 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.

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

[0084] 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.

[0085] 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 / (△fmax *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 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. In the normal cyclic prefix (CP), each slot consists of 14 OFDM symbols, and in the case of the extended CP, each slot consists of 12 OFDM symbols. The numerology is exponentially scalable with the 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 (N frame,u slot ) and the number of slots per subframe (N subframe,u slot ) is shown.

[0086]

[0087] 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.

[0088]

[0089] 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}.

[0090] 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,x is 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 scis 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 CRB and 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,iis 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.

[0091] 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 size 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.

[0092] Switching between configured BWPs can occur using RRC signaling, DCI, an inactivity timer, or upon initiation of a random access. If an inactivity timer is configured for a serving cell, expiration of the inactivity timer associated with the serving cell switches the active BWP to the default BWP configured by the network.

[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] Figure 6 illustrates physical channels used in a 3GPP-based communication system, which is an example of a wireless communication system, and a signal transmission / reception process using the channels.

[0097] When a UE is powered on again after being powered off or has been disconnected from a wireless communication system, it first searches for a suitable cell to camp on (search cell) and performs an initial cell search process, such as synchronizing with the cell or the BS of the cell (S11). During the initial cell search process, the UE receives a synchronization signal block (SSB) (also called an SSB / PBCH block) from the BS. The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). The UE synchronizes with the BS based on the PSS / SSS and obtains information such as a cell identity (ID). In addition, the UE can obtain broadcast information within the cell based on the PBCH. Meanwhile, the UE can check the downlink channel status by receiving a downlink reference signal (DL RS) during the initial cell search process.

[0098] A UE that has completed initial cell search can camp on the cell. After camping on the cell, the UE monitors the PDCCH on the cell and receives the PDSCH based on the downlink control information (DCI) carried by the PDCCH to obtain more specific system information (S12).

[0099] Thereafter, the UE may perform a random access procedure to complete access to the BS (S13 to S16). For example, in the random access procedure, the UE may transmit a preamble through a physical random access channel (PRACH) (S13) and receive a random access response (RAR) to the preamble through a PDCCH and a corresponding PDSCH (S14). If reception of the RAR for the UE fails, the UE may retry transmitting the preamble. In the case of contention-based random access, a contention resolution procedure (S16) may be performed, including transmission of a PUSCH based on UL resource allocation included in the RAR (S15) and reception of a PDCCH and a corresponding PDSCH.

[0100] The UE, which has performed the procedure described above, can then perform reception of PDCCH / PDSCH (S17) and transmission of PUSCH / PUCCH (S18) as a general uplink / downlink signal transmission process. The control information that the UE transmits to the BS is collectively referred to as uplink control information (UCI). UCI includes HARQ ACK / NACK (Hybrid Automatic Repeat and reQuest Acknowledgement / Negative-ACK) (also referred to as HARQ-ACK), scheduling request (SR), channel state information (CSI), etc. CSI may include a channel quality indicator (CQI), a precoding matrix indicator (PMI), and / or a rank indicator. UCI is generally transmitted through PUCCH, but may be transmitted through PUSCH when control information and traffic data must be transmitted simultaneously. Additionally, based on a request / instruction from the network, the UE can transmit UCI aperiodically via PUSCH.

[0101] 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).

[0102] 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.

[0103] The PDSCH is a physical layer DL channel for DL ​​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. A 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.

[0104] PUSCH is a physical layer UL channel for UL data transport. PUSCH carries downlink data (e.g., UL-SCH transport blocks) and modulation methods such as Pi / 2 BPSK (Binary Phase Shift Keying), QPSK (Quadrature Phase Shift Keying), 16QAM (Quadrature Amplitude Modulation), 64QAM, and 256QAM are applied. A transport block (TB) is encoded to generate a codeword. PUSCH 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 a radio resource along with the DMRS, generated as an OFDM symbol signal, and transmitted through the corresponding antenna port.

[0105] 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.

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

[0107] - 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.

[0108] - 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.

[0109] - Link recovery request (LRR)

[0110] 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.

[0111] 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.

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

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

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

[0115] - 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.

[0116] - 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.

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

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

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

[0120] - 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).

[0121] - 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.

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

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

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

[0125] - 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.

[0126] - 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.

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

[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. 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).

[0131] - 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.

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

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

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

[0135] - 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.

[0136] - 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.

[0137] 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).

[0138]

[0139] If the UE does not have a dedicated PUCCH configuration provided by PUCCH-ResourceSet in RRC configuration PUCCH-Config, for example, before the UE acquires PUCCH-Config, the PUCCH resource set is N size BWPThe SIB can be provided by push-ResourceCommon through an index to the row of the following table for transmission of HARQ-ACK information on PUCCH within the initial UL BWP of the PRBs.

[0140] The following table is Table 9.2.1-1 of 3GPP TS 38.213, and illustrates PUCCH resource sets (also called initial PUCCH resource sets) and their parameters that can be used before establishing dedicated PUCCH resources. The BS configures / indicates one of the index values ​​0 to 15 in the following table cell-specifically via the parameter pucch-ResourceCommon in the SIB.

[0141]

[0142] The above PUCCH resource set is each, for PUCCH transmission, PUCCH format, first symbol, duration, PRB offset RB offset BWP and 16 (PUCCH) resources corresponding to a set of cyclic shift (CS) indices. The UE transmits PUCCH using frequency hopping. For a PUCCH resource set defined by index, 16 PUCCH resources (e.g., r) are defined using the parameters defined in the table above. PUCCH = 0, 1, 2, ..., 15) can be formed. For example, if the BS sets / indicates index 0 or 1 or 4 through SIB, the parameter values ​​for each of the 16 different PUCCH resources can be as follows.

[0143]

[0144] If the UE is not provided with an RRC parameter pdsch-HARQ-ACK-Codebook indicating whether the PDSCH HARQ-ACK codebook is semi-static or dynamic, the UE generates at most one HARQ-ACK bit. If the UE provides HARQ-ACK information in a PUCCH transmission in response to detecting DCI format 1_0 or DCI format 1_1, the UE selects a PUCCH resource for the PUCCH transmission among 16 PUCCH resources belonging to a PUCCH resource set corresponding to an index obtained through push-ReosurceCommon in SIB, the number N of CCEs in the CORESET of the PDCCH reception having DCI format 1_0 or DCI 1_1. CCE , index n of the first CCE for receiving the above PDCCH CCE,0 , the value of the PUCCH resource indicator (PRI) field in the DCI format 1_0 or DCI format 1_1 △ PRI can be determined based on. For example, if the UE provides HARQ-ACK information in a PUCCH transmission in response to detecting DCI format 1_0 or DCI format 1_1, the UE may determine based on the index r PUCCH r PUCCH resources PUCCH = floor{(2*n CCE,0 ) / N CCE} + 2*△ PRI is determined as , where 1 ≤ r PUCCH ≤ 15. floor(r PUCCH / 8) = 0, the UE sets the PRB index of the PUCCH transmission to RB in the first hop. offset BWP + floor(r PUCCH / N CS ) is determined as N, and in the second hop, the PRB index of the PUCCH transmission is N.size BWP - 1 - RB offset BWP - floor(r PUCCH / N CS ) is determined as, where N CS is the total number of initial cyclic transition indices in the set of initial cyclic transition indices, and the UE selects an initial cyclic transition index in the set of initial cyclic transition indices r PUCCH mod N CS can be determined as floor(r PUCCH / 8) = 1, the UE transmits the PRB index of the PUCCH transmission in the first hop to N. size BWP - 1 - RB offset BWP - floor{(r PUCCH - 8) / N CS} is determined as RB, and in the second hop, the PRB index of the PUCCH transmission is determined as RB. offset BWP + floor{(r PUCCH - 8) / N CS}, and the UE determines the initial cyclic shift index within the set of initial cyclic shift indices (r PUCCH - 8) mod N CS can be decided as.

[0145] Figures 7 and 8 are part of a physical uplink control channel (PUCCH) configuration provided by upper layer signaling.

[0146] When a UE has a dedicated PUCCH resource configuration, the UE is provided with one or more PUCCH resources by upper layer signaling. PUCCH resources can be determined according to 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, a 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 may set the number of UCI bits (N UCI ) can select one of the following PUCCH resource sets.

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

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

[0149] ...

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

[0151] 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).

[0152] 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.

[0153] 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.

[0154] 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.).

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

[0156] FIG. 9 illustrates a flow of a process related to channel state information (CSI). Referring to FIG. 9, a UE may receive CSI-related configuration information from a BS via RRC signaling (S910). The CSI-related configuration information may include information related to CSI-RS resources or resource sets (e.g., time-frequency resource information, sequence information, power information, etc.), information related to CSI reporting (e.g., report quantity information, report type information, report resource information, codebook information, etc.), information related to CSI measurement, etc. Here, in order to assist the BS with transceiver muting and / or transmission power adaptation of the BS, the UE may be configured to report multiple CSI entries in CSI reporting based on a plurality of sub-configurations. Here, each sub-configuration may correspond to a spatial domain adaptation pattern (e.g., a subset of available spatial elements) and / or a power offset. Additionally, with respect to CSI reporting, a higher layer configuration (e.g., CSI-ReportConfig) may include a list of sub-configurations. IEcsi-ReportSubConfig is used to set parameters for a sub-configuration within a CSI reporting configuration. Each sub-configuration is identified by an identifier (e.g., csi-ReportSubConfigID) and corresponds to a list of at least one CSI-RS resource (e.g., see parameter nzp-CSI-RS-ResourceList), or corresponds to a CSI-RS antenna port subset (e.g., see parameter portSubsetIndicator), and / or corresponds to a power control offset related parameter (e.g., powerControlOffset) of the CSI-RS resource(s), as well as a power offset for a PDSCH related to the CSI-RS (e.g., see parameter powerOffset).The parameter portSubsetIndicator may indicate the number of ports of non-zero power (NZP) CSI-RS resources indicated in nzp-CSI-RS-resourceList (the value is equal to portNumber of these NZP CSI-RS resources) and the (sub)set of CSI-RS antenna ports used for CSI computation of the sub-configuration. In the bit string of the parameter portSubsetIndicator, each bit corresponds to an antenna port, and if the bit is set to 1, the corresponding port is enabled for CSI computation corresponding to the sub-configuration, and if the bit is set to 0, the corresponding port is not enabled for CSI computation corresponding to the sub-configuration. 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, where the value 0 indicates the first NZP CSI-RS resource of the CSI-RS resource set, and the value 1 indicates the second NZP CSI-RS resource of the CSI-RS resource set. The parameter powerOffset is a power offset of a PDSCH RE for an NZP CSI-RS resource element (RE) equal to powerControlOffset-powerOffset, if the parameter powerControlOffset is set for the NZP CSI-RS resources indicated in nzp-CSI-RS-Resources.

[0157] A configuration related to CSI may include multiple sub-configurations. Accordingly, when interpreting configuration information for CSI, the UE may determine CSI-RS resources, CSI-RS port mapping, power offset, codebook type, report item (quantity), etc. by considering the sub-configuration(s). When the UE is configured with configuration information related to CSI reporting including sub-configuration(s) (e.g., CSI-ReportConfig), the UE does not expect that the upper layer parameter related to the report item (e.g., reportQuantity) is set to 'cri-RSRP', 'cri-SINR', 'cri-SINR- Index', 'cri-RSRP-Index', 'none', 'ssb-Index-RSRP', 'ssb-Index-SINR', 'ssb-Index-RSRP- Index', 'ssb-Index-SINR- Index' or 'tdcp'.

[0158] With respect to the configuration of the reporting items, the UE may be configured with CSI-ReportConfig with the upper layer parameter reportQuantity set to 'none', 'cri-RI-PMI-CQI', 'cri-RI-i1', 'cri-RI-i1-CQI', 'cri-RI-cqi', 'cri-RSRP', 'cri-SINR', 'ssb-Index-RSRP', 'ssb-Index-SINR', 'cri-RI-LI-PMI-CQI', 'cri-RSRP-Index', 'ssb-Index-RSRP-Index', 'cri-SINR-Index', ssb-Index-SINR-Index' or 'tdcp'. When a UE is configured with a CSI-ReportConfig with the upper layer parameter reportQuantity set to 'none', the UE does not report any item (quantity) for the CSI-ReportConfig.

[0159] CSI-ReportConfig may include CodebookConfig, which is used to configure Type-I and Type-II codebooks. In this specification, Type-I codebooks are also referred to as Type-1 codebooks, and Type-II codebooks are also referred to as Type-2 codebooks. The parameter codebookType in CodebookConfig may include subtypes and corresponding parameters for each subtype.

[0160] The UE may also determine the codebook type based on the presence of sub-configurations. For example, if sub-configurations are configured for CSI reporting, the UE may exclude the configuration of at least one codebook type. However, depending on the UE's capabilities, it is also possible for the at least one codebook type to be configured. For example, if the UE is configured with a CSI-ReportConfig that includes a list of sub-configurations provided by csi-ReportSubConfigList, the UE expects the upper layer parameter codebookType to be set to 'typeI-SinglePanel' or 'typeI-MultiPanel'. If the UE indicates the capability to support mixed codebook combinations within a slot, each sub-configuration may be configured with the upper layer parameter codebookType set to 'typeI-SinglePanel' or 'typeI-MultiPanel'. When a sub-configuration is set to an antenna port subset, the sub-configuration may be set to ri-Restriction, codebookMode, and if the number of antenna ports of the subset is greater than 2, to n1-n2 when the upper layer parameter codebookType is set to 'typeI-SinglePanel', or to ng-n1-n2 when the upper layer parameter codebookType is set to 'typeI-MultiPanel', and if the number of antenna ports of the subset is 2, to twoTX-CodebookSubsetRestriction, where the parameters ri-Restriction, codebookMode, n1-n2, ng-n1-n2, twoTX-CodebookSubsetRestriction are as per clauses 5.2.2.2.1 and 5.2.2.2 of 3GPP TS 38.214.As described in 2 (If a sub-configuration is configured with an antenna port subset, then the sub-configuration can be configured with ari-Restriction,codebookModeand, if the number of antenna ports of the subset greater than 2, withn1-n2if the higher layer parametercodebookTypeis set to 'typeI-SinglePanel' or withng-n1-n2if the higher layer parametercodebookTypeis set to 'typeI-MultiPanel', and, if the corresponding number of antenna ports of the subset is 2, withtwoTX-CodebookSubsetRestriction, where the parametersri-Restriction,codebookMode,n1-n2,ng-n1-n2,twoTX-CodebookSubsetRestrictionare as described in Clauses 5.2.2.2.1 and 5.2.2.2.2 of 3GPP TS 38.214). If the sub-configuration is set to an antenna port subset and the upper layer parameter reportQuantity is set to 'cri-RI-i1-CQI' and the upper layer parameter codebookType is set to 'typeI-SinglePanel', then the sub-configuration is set to the upper layer parameter typeI-SinglePanel-codebookSubsetRestriction-i2, where typeI-SinglePanel-codebookSubsetRestriction-i2 is as described in section 5.2.2.2.1 of 3GPP TS 38.214.When a sub-configuration is set to a subset of antenna ports and the CSI-ReportConfig contains a mix of sub-configuration(s), each corresponding to 'typeI-SinglePanel', and several other sub-configuration(s), each corresponding to 'typeI-MultiPanel', the sub-configuration(s) may be set to the upper layer parameter codebookMode.

[0161] When the type of CSI reporting is set to semi-persistent CSI reporting or aperiodic CSI reporting, the BS may activate / trigger only some of the sub-configurations configured for the UE through a MAC control element (CE) or DCI. The trigger state of the aperiodic CSI reporting may be configured as needed, and whether the semi-static CSI reporting is activated or not may be controlled by an activation command. For example, in order to activate / trigger only some of the sub-configurations configured for the UE, the BS may provide the UE with an IECSI-ReportSubConfigTriggerList, which is used to configure a list of sub-configuration ID(s) of N sub-configurations among L configured sub-configurations in the CSI-ReportConfig related to the triggering state for semi-persistent reporting and aperiodic CSI reporting on PUSCH.

[0162] 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.

[0163] For CSI-RS resource sets associated with resource settings with the higher layer parameter resourceType set to 'aperiodic', 'periodic' or 'semi-persistent', trigger states for reporting configuration(s) (configured with the higher layer parameter reportConfigType set to 'aperiodic') and / or resource settings for channel and / or interference measurements on one or more component carriers can be configured using the higher layer parameter CSI-AperiodicTriggerStateList. For a reporting setting for which the CSI-ReportConfigcontains a list of sub-configurations provided by the higher layer parameter csi-ReportSubConfigList, one or more trigger states can be configured with each indicating one or more of the sub-configurations. For aperiodic CSI reporting triggering, a single set of CSI triggering states can be configured by the upper layer, where a CSI triggering state can be associated with any candidate DL BWP.

[0164] For semi-persistent reporting on PUSCH, a set of trigger states can be configured by a higher layer parameter CSI-SemiPersistentOnPUSCH-TriggerStateList, where a CSI request field of DCI scrambled with SP-CSI-RNTI can activate one of the trigger states. For a reporting setting for which the CSI-ReportConfig contains a list of sub-configurations, provided by the higher layer parameter csi-ReportSubConfigList, one or more trigger states can be configured with each indicating one or more of the sub-configurations.

[0165] For semi-persistent reporting on PUCCH, the PUCCH resources used to transmit CSI reports can be configured by reportConfigType. Semi-persistent reporting on PUCCH can be activated by an activation command as described in 3GPP TS 38.321, which selects one of the semi-persistent reporting sets for the UE to use on PUCCH. For a selected reporting setting for which the CSI-ReportConfig contains a list of sub-configurations provided by the higher layer parameter csi-ReportSubConfigList, the activation command may select one or more sub-configurations for the UE to use. If the UE wants to transmit PUCCH with HARQ-ACK information in slot n corresponding to the PDSCH carrying the activation command, the above-indicated semi-persistent reporting setting is set to slot n+3*N subframe,u slot It is applied starting from the first slot, where u is the SCS setting for the PUCCH.

[0166] The UE performs CSI measurement based on CSI-related configuration information (S920). The CSI measurement may include (1) a process of receiving CSI-RS by the UE (S921) and (2) a process of performing CSI computation using the received CSI-RS (S922).

[0167] The UE can transmit a CSI report based on the calculated CSI (S930). 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 repetition is set. Here, the transmission of the CSI report can be skipped only when repetition is set to 'ON'.

[0168] A UE may transmit CSI(s) for at least one sub-configuration according to a report item parameter (e.g., reportQuantity) configured for configuration information related to CSI reporting (e.g., CSI-ReportConfig). For example, a CSI report may include at least one of PMI, CQI, RI, CRI, SSBRI, LI, and RSRP.

[0169] 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 CSI report before CSI Part 2. The payload of CSI Part 2 may be variable. The CSI report may be transmitted over at least one of the PUCCH or PUSCH.

[0170] When a UE multiplexes CSI reports including Part 2 CSI reports on a PUCCH resource, the UE may determine the number of PRBs for the PUCCH resource or the number of Part 2 CSI reports, assuming that each CSI report or each CSI sub-report included in the CSI report indicates rank 1 or rank combination {1, 1}. When a higher layer parameter related to the CSI reporting mode (e.g., csi-ReportMode) is set to 'Mode2', the UE may determine the number of PRBs for the PUCCH resource or the number of Part 2 CSI reports, assuming that each CRI of the CSI report is associated with a resource pair.

[0171] When a CSI report on PUSCH includes two parts, the UE may omit some of the Part 2 CSI. The omission of Part 2 CSI is in priority order. When omitting Part 2 CSI information for a particular priority level, the UE shall exclude all information for that priority level, except when the corresponding CSI report includes at least one CSI sub-report containing Part 2, which corresponds to a sub-configuration from the list of sub-configurations provided by a higher layer parameter (e.g., csi-ReportSubConfigList) included in the information related to the CSI report (e.g., CSI-ReportConfig).

[0172] For report settings related to CSI report-related information (e.g., CSI-ReportConfig) that include a list of sub-configurations, the following processing is possible: For a corresponding CSI report that includes at least one CSI sub-report, omission of Part 2 CSI is performed at the sub-configuration level within the same priority level, where the sub-configuration with the lower index value has the higher priority.

[0173] If a CSI report consists of two parts, the UE may omit some of the Part 2 CSI. Omission of Part 2 CSI is based on priority order. Starting with the lowest priority level, Part 2 CSI may be omitted up to the Part 2 CSI coding rate that is less than or equal to the coding rate set by the higher layer parameter (e.g., maxCodeRate).

[0174] CSI is transmitted through PUCCH or PUSCH and can be expressed by a bit sequence of a certain size. When CSI is transmitted through PUCCH, if a parameter (e.g., csi-ReportSubConfig) for CSI reporting per sub-configuration (hereinafter, CSI sub-report) is set in the CSI reporting configuration, the mapping order of CSI fields of one CSI sub-report may be as follows for the corresponding CSI sub-report. The following table is Table 6.3.1.1.2-11C of 3GPP TS 38.212, and N sub n The mapping order of the CSI fields of a CSI report including the dog CSI sub-report(s).

[0175]

[0176] The subbands for CSI reporting n indicated by the upper layer parameter csi-ReportingBand with the value set to '1' are numbered continuously in increasing order, starting with the lowest subband of csi-ReportingBand with the value set to '1' as subband 0: CSI Sub-Report #1, CSI Sub-Report #2, ..., CSI Sub-Report #N. sub n Corresponds to CSI sub-reports in increasing order of CSI-ReportSubConfigID.

[0177] 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.

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

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

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

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

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

[0183] In order for a UE to transmit UL-SCH data, it must have uplink resources available to the UE, and in order for the UE to receive DL-SCH data, it must have downlink resources available to the UE. 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. Uplink grant is dynamically received by the UE on the PDCCH or within the RAR, or semi-persistently configured to the UE by RRC signaling from the BS. Downlink assignment is dynamically received by the UE on the PDCCH, or semi-persistently configured to the UE by RRC signaling from the BS.

[0184] 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.

[0185] 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-persistent scheduling (SPS). The BS can configure 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 configured by the RRC signaling until it is deactivated.

[0186] Figure 10 illustrates an example of PDSCH time domain resource allocation by PDCCH and an example of PUSCH time domain resource allocation by PDCCH.

[0187] The DCI carried by the PDCCH for scheduling the PDSCH or PUSCH includes a time domain resource assignment (TDRA) field, which provides a value m for a row index m+1 of an allocation table for the PDSCH or PUSCH. A predefined default PDSCH time domain allocation is applied as the allocation table for the PDSCH, or a PDSCH time domain resource allocation table configured by the BS through RRC signaling pdsch-TimeDomainAllocationList is applied as the allocation table for the PDSCH. A predefined default PUSCH time domain allocation is applied as the allocation table for the PUSCH, or a PUSCH time domain resource allocation table configured by the BS through RRC signaling pushch-TimeDomainAllocationList is applied as the allocation table for the PUSCH. The PDSCH time domain resource allocation table to be applied and / or the PUSCH time domain resource allocation table to be applied may be determined according to fixed / predefined rules (e.g., see 3GPP TS 38.214).

[0188] In the PDSCH time domain resource configurations, each indexed row defines a DL allocation-to-PDSCH slot offset K0, a start and length indicator value SLIV (or directly a starting position (e.g., a starting symbol index S) and an allocation length (e.g., a number of symbols L) of a PDSCH within a slot), and a PDSCH mapping type. In the PUSCH time domain resource configurations, each indexed row defines a UL grant-to-PUSCH slot offset K2, a starting position (e.g., a starting symbol index S) and an allocation length (e.g., a number of symbols L) of a PUSCH within a slot, and a PUSCH mapping type. K0 for PDSCH or K2 for PUSCH indicates the difference between a slot with a PDCCH and a slot with a PDSCH or PUSCH corresponding to the PDCCH. SLIV is a joint indication of a starting symbol S relative to the start of a slot with a PDSCH or PUSCH and the number L of consecutive symbols counted from the symbol S. For PDSCH / PUSCH mapping type, there are two mapping types: one is mapping type A and the other is mapping type B. For PDSCH / PUSCH mapping type A, a demodulation reference signal (DMRS) is mapped to a PDSCH / PUSCH resource at the beginning of a slot, and one or two symbols of the PDSCH / PUSCH resource can be used as DMRS symbol(s) depending on other DMRS parameters. For example, for PDSCH / PUSCH mapping type A, the DMRS is located at the third symbol (symbol #2) or the fourth symbol (symbol #3) in a slot depending on RRC signaling. For PDSCH / PUSCH mapping type B, the DMRS is mapped based on the first OFDM symbol of the PDSCH / PUSCH resource, and one or two symbols from the first symbol of the PDSCH / PUSCH resource can be used as DMRS symbol(s) depending on other DMRS parameters.For example, in the case of PDSCH / PUSCH mapping type B, DMRS is located in the first symbol allocated for PDSCH / PUSCH. In this specification, PDSCH / PUSCH mapping type may be referred to as mapping type or DMRS mapping type. For example, in this specification, PUSCH mapping type A may be referred to as mapping type A or DMRS mapping type A, and PUSCH mapping type B may be referred to as mapping type B or DMRS mapping type B.

[0189] The above scheduling DCI includes a frequency domain resource assignment (FDRA) field that provides allocation information regarding resource blocks used for PDSCH or PUSCH. For example, the FDRA field provides the UE with information regarding the cell for PDSCH or PUSCH transmission, information regarding the BWP for PDSCH or PUSCH transmission, and information regarding resource blocks for PDSCH or PUSCH transmission.

[0190] A control resource set (CORESET), which is a set of time-frequency resources for which a UE can monitor PDCCH, may be defined and / or configured. A CORESET consists of a set of physical resource blocks (PRBs) with a duration of one to three OFDM symbols. The PRBs constituting the CORESET and the CORESET duration may be provided to the UE via higher layer (e.g., RRC) signaling. Within the configured CORESET(s), a set of PDCCH candidates is monitored according to the corresponding search space sets. In this specification, monitoring implies decoding (aka blind decoding) each PDCCH candidate according to the monitored DCI formats. The master information block (MIB) on the PBCH provides the UE with parameters (e.g., CORESET#0 configuration) for monitoring the PDCCH for scheduling the PDSCH carrying the system information block 1 (SIB1). The PBCH may also indicate that there is no associated SIB1, in which case the UE may be instructed on other frequencies to search for the SSB associated with SIB1, as well as a frequency range in which it can assume that there is no SSB associated with SSB1. At least CORESET#0, which is the CORESET for scheduling SIB1, may be configured via the MIB or dedicated RRC signaling.

[0191] More than one CORESET may be configured for a UE, and multiple CORESETs may overlap in the time / frequency domain.

[0192] The set of PDCCH candidates monitored by the UE is defined in terms of PDCCH search space sets. The search space set may be a common search space (CSS) set or a UE-specific search space (USS) set. Each CORESET configuration is associated with one or more search space sets, and each search space set is associated with one CORESET configuration.

[0193] A set of PDCCH candidates can be monitored in one or more CORESETs on an active DL BWP on each activated serving cell for which PDCCH monitoring is configured, where monitoring implies receiving each PDCCH candidate and decoding it according to the monitored DCI formats. For example, the following DCI formats may be available:

[0194]

[0195] SS sets can be configured via system information (e.g., MIB) or UE-specific higher layer (e.g., RRC) signaling. Each DL BWP of a serving cell can have up to S (e.g., 10) SS sets configured. For example, the following parameters / information can be provided for each SS set. Each SS set is associated with one CORESET, and each CORESET configuration can be associated with one or more SS sets.

[0196] -searchSpaceId: Indicates the ID of the SS set.

[0197] -controlResourceSetId: Indicates the CORESET associated with the SS set.

[0198] -monitoringSlotPeriodicityAndOffset: Indicates the PDCCH monitoring period period (in slots) and the PDCCH monitoring period offset (in slots).

[0199] -monitoringSymbolsWithinSlot: Indicates the first OFDMA symbol(s) for PDCCH monitoring within a slot where PDCCH monitoring is enabled. This is indicated via a bitmap, with each bit corresponding to each OFDMA symbol within the slot. The most significant bit (MSB) of the bitmap corresponds to the first OFDM symbol within the slot. The OFDMA symbol(s) corresponding to the bit(s) with a bit value of 1 corresponds to the first symbol(s) of the CORESET within the slot.

[0200] -nrofCandidates: Indicates the number of PDCCH candidates for each aggregation level (AL) = {1, 2, 4, 8, 16} (e.g., one of 0, 1, 2, 3, 4, 5, 6, 8).

[0201] -searchSpaceType: Indicates whether the SS type is CSS or USS.

[0202] - DCI format: Indicates the DCI format of the PDCCH candidate.

[0203] Based on the CORESET / SS set configuration, the UE can monitor PDCCH candidates in one or more SS sets within a slot. The occasions (e.g., time / frequency resources) during which PDCCH candidates should be monitored are defined as PDCCH (monitoring) occasions. One or more PDCCH (monitoring) occasions can be configured within a slot.

[0204] For uplink, there are two types of transmissions without dynamic grants: configured grant type 1 and configured grant type 2. For configured grant type 1, the UL grant is provided by RRC signaling and stored as a configured grant. For configured grant type 2, the UL grant is provided by PDCCH and stored or cleared as a configured uplink grant based on L1 signaling indicating activation or deactivation of the configured uplink grant. Type 1 and Type 2 can be configured by RRC signaling on a per-serving cell and per-BWP basis. Multiple configurations can be activated simultaneously on different serving cells.

[0205] When Grant Type 1 is configured, the UE can receive the following parameters from the BS via RRC signaling:

[0206] - cs-RNTI, CS-RNTI for retransmission;

[0207] - Periodicity of the set grant type 1;

[0208] - timeReferenceSFN, which indicates the system frame number (SFN) used to determine the offset of the resource in the time domain;

[0209] -timeDomainOffset, which is the offset relative to the reference SFN pointed to by -timeReferenceSFN;

[0210] - A timeDomainAllocation value m, which provides a row index m+1 pointing to an allocation table, representing a combination of a start symbol S, a length L, and a PUSCH mapping type;

[0211] - frequencyDomainAllocation, which provides frequency domain resource allocation; and

[0212] - I indicating the modulation order, target code rate, and transport block size MCSmcsAndTBS provides.

[0213] When configuring a configuration grant type 1 for a serving cell by RRC, the UE stores the UL grant provided by RRC as a configured uplink grant for the indicated serving cell, and initializes or re-initializes the configured uplink grant to start at a symbol according to timeDomainOffset and S (derived from SLIV) and to recur with periodicity. After the uplink grant is configured for Grant Type 1, the UE may consider that the uplink grant recurses in association with each symbol satisfying the following: [(SFN *numberOfSlotsPerFrame*numberOfSymbolsPerSlot+ (slot number in the frame *numberOfSymbolsPerSlot) + symbol number in the slot] = (timeReferenceSFN*numberOfSlotsPerFrame*numberOfSymbolsPerSlot+timeDomainOffset*numberOfSymbolsPerSlot+ S + N *periodicity) modulo (1024 *numberOfSlotsPerFrame*numberOfSymbolsPerSlot), for N >= 0, where numberOfSlotsPerFrame and numberOfSymbolsPerSlot represent the number of consecutive slots per frame and the number of consecutive OFDM symbols per slot, respectively (see Tables 1 and 2). 'SFN' is the uplink The system frame number of the frame in which the grant can occur, the 'slot number' is the slot number of the slot in which the uplink grant can occur within the frame, and the 'symbol number' is the symbol number of the symbol in which the uplink grant can occur within the slot.

[0214] When Grant Type 2 is configured, the UE can receive the following parameters from the BS via RRC signaling:

[0215] - cs-RNTI, which is a CS-RNTI for activation, deactivation, and retransmission; and

[0216] - Periodicity providing the period of the grant type 2 set above.

[0217] The actual uplink grant is provided to the UE by the PDCCH (addressed by the CS-RNTI). After the uplink grant is configured for Grant Type 2, the UE may consider the uplink grant to be recurring in association with each symbol satisfying: [(SFN *numberOfSlotsPerFrame*numberOfSymbolsPerSlot) + (slot number in the frame *numberOfSymbolsPerSlot) + symbol number in the slot] = [(SFN start time *numberOfSlotsPerFrame*numberOfSymbolsPerSlot+ slotstart time*numberOfSymbolsPerSlot+ symbolstart time) + N *periodicity] modulo (1024 *numberOfSlotsPerFrame*numberOfSymbolsPerSlot), for all N >= 0, where SFN start time, slotstart time, and symbolstart time represent, respectively, the SFN, slot, and symbol of the first transmission opportunity of the PUSCH after the configured grant is (re-)initialized, and numberOfSlotsPerFrame and numberOfSymbolsPerSlot represent the number of consecutive slots per frame and the number of consecutive OFDM symbols per slot, respectively (see Tables 1 and 2). 'SFN' is a system frame number of a frame in which the uplink grant can occur, 'slot number' is a slot number of a slot in which the uplink grant can occur within the frame, and 'symbol number' is a symbol number of a symbol in which the uplink grant can occur within the slot.

[0218] In some scenarios, the parameters harq-ProcID-Offset and / or harq-ProcID-Offset2 may be further provided by the BS to the UE to derive HARQ process IDs for the configured uplink grants. harq-ProcID-Offset is the offset of the HARQ process for the configured grant for operation with shared spectrum channel access, and harq-ProcID-Offset2 is the offset of the HARQ process for the configured grant. In this specification, cg-RetransmissionTimer is a duration during which the UE should not autonoumously perform a retransmission using the HARQ process of the (re)transmission after a (re)transmission based on a configured grant, and is a parameter that can be provided to the UE by the BS when a retransmission on the configured uplink grant is configured. For configured grants for which neither harq-ProcID-Offset nor cg-RetransmissionTimer is configured, the HARQ process ID associated with the first symbol of the UL transmission can be derived from the following equation: HARQ Process ID = [floor(CURRENT_symbol / periodicity)] modulonrofHARQ-Processes.For configured uplink grants with harq-ProcID-Offset2, the HARQ process ID associated with the first symbol of the UL transmission can be derived from the following equation: HARQ Process ID = [floor(CURRENT_symbol / periodicity)] modulonrofHARQ-Processes+harq-ProcID-Offset2, where CURRENT_symbol = (SFN *numberOfSlotsPerFrame*numberOfSymbolsPerSlot+ slot number in the frame *numberOfSymbolsPerSlot+ symbol number in the slot), where numberOfSlotsPerFrame and numberOfSymbolsPerSlot represent the number of consecutive slots per frame and the number of consecutive OFDM symbols per slot, respectively. For configured UL grants with cg-RetransmissionTimer, the UE may arbitrarily select a HARQ process ID from among the available HARQ process IDs for the configured grant.

[0219] For downlink, the UE can be configured with semi-persistent scheduling (SPS) on a per-serving cell and per-BWP basis via RRC signaling from the BS. For DL ​​SPS, DL assignments are provided to the UE via PDCCH and stored or removed based on L1 signaling indicating SPS activation or deactivation. When SPS is configured, the UE can receive the following parameters from the BS via RRC signaling (e.g., SPS configuration) used to configure semi-persistent transmission:

[0220] - cs-RNTI, CS-RNTI for activation, deactivation, and retransmission;

[0221] -nrofHARQ-Processes, which provides the number of HARQ processes configured for SPS;

[0222] - periodicity, which provides the period of set downlink allocation for SPS;

[0223] - n1PUCCH-AN providing HARQ resources for PUCCH for SPS (the network configures the HARQ resources as format 0 or format 1, and the actual PUCCH-resources are configured in PUCCH-Config and referred to in n1PUCCH-AN by their ID).

[0224] Multiple downlink SPS configurations can be configured within the BWP of a serving cell. After a downlink assignment is configured for SPS, the UE can sequentially consider the Nth downlink assignment to occur in a slot satisfying: (numberOfSlotsPerFrame*SFN + slot number in the frame) = [(numberOfSlotsPerFrame*SFN start time + slotstart time) + N *periodicity*numberOfSlotsPerFrame / 10] modulo(1024 *numberOfSlotsPerFrame), where SFN start timeand slotstart time represent the SFN, slot, and symbol of the first transmission of the PDSCH after the configured downlink assignment is (re-)initialized, respectively, and numberOfSlotsPerFrame and numberOfSymbolsPerSlot represent the number of consecutive slots per frame and the number of consecutive OFDM symbols per slot, respectively (see Tables 1 and 2). 'SFN' is the system frame number of the frame in which the downlink assignment can occur, and 'slot number' is the slot number of the slot in which the downlink assignment can occur within the frame.

[0225] In some scenarios, a parameter harq-ProcID-Offset, which is used to derive HARQ process IDs for configured downlink assignments, may be further provided by the BS to the UE. harq-ProcID-Offset is the offset of the HARQ process for the SPS. For configured downlink assignments without harq-ProcID-Offset, the HARQ process ID associated with the slot where the DL transmission starts may be determined from the following equation: HARQ Process ID = [floor (CURRENT_slot * 10 / (numberOfSlotsPerFrame*periodicity))] modulonrofHARQ-Processes, where CURRENT_slot = [(SFN *numberOfSlotsPerFrame) + slot number in the frame] and numberOfSlotsPerFrame means the number of consecutive slots per frame. For configured downlink assignments with harq-ProcID-Offset, the HARQ process ID associated with the slot where the DL transmission starts may be determined from the following equation: HARQ Process ID = [floor (CURRENT_slot * 10 / (numberOfSlotsPerFrame*periodicity))] modulonrofHARQ-Processes, where CURRENT_slot = [(SFN *numberOfSlotsPerFrame) + slot number in the frame] and numberOfSlotsPerFrame means the number of consecutive slots per frame. The ID can be determined from the following formula: HARQ Process ID = [floor (CURRENT_slot / periodicity)] modulonrofHARQ-Processes+harq-ProcID-Offset, where CURRENT_slot = [(SFN *numberOfSlotsPerFrame) + slot number in the frame], and numberOfSlotsPerFrame represents the number of consecutive slots per frame.

[0226] If the cyclic redundancy check (CRC) of the corresponding DCI format is scrambled with the CS-RNTI provided by the RRC parameter cs-RNTI and the new data indicator field for the enabled transport block is set to 0, the UE validates the DL SPS assignment PDCCH or the configured UL grant type 2 PDCCH for scheduling activation or descheduling. Validation of the DCI format is achieved if all fields for the DCI format are set according to Table 9 or Table 10. Table 9 illustrates special fields for DL ​​SPS and UL grant type 2 scheduling activation PDCCH validation, and Table 10 illustrates special fields for DL ​​SPS and UL grant type 2 scheduling release PDCCH validation.

[0227]

[0228]

[0229] The actual DL assignment or UL grant for DL ​​SPS or UL grant type 2, and the corresponding modulation and coding scheme, are provided by the resource allocation fields (e.g., a TDRA field providing a TDRA value m, an FDRA field providing a frequency resource block allocation, and a modulation and coding scheme field) in the DCI format carried by the corresponding DL SPS or UL grant type 2 scheduling activation PDCCH. If the validation is achieved, the UE considers the information in the DCI format as a valid activation or valid release of the DL SPS or the configured UL grant type 2.

[0230] In this specification, a PDSCH based on DL SPS is referred to as an SPS PDSCH, a PUSCH based on UL CG is referred to as a CG PUSCH, a PDSCH dynamically scheduled by DCI carried by a PDCCH is referred to as a DG PDSCH, and a PUSCH dynamically scheduled by DCI carried by a PDCCH is referred to as a DG PUSCH.

[0231] Figure 11 illustrates a processing process on the transmission side for a transport block (TB).

[0232] To enable the receiver to correct errors encountered in wireless signals over the wireless channel, the transmitter encodes the information it sends using a forward error correction code before transmitting it. The receiver demodulates the received signal and then decodes the error correction code to restore the transmitted information. This decoding process corrects errors in the received signal caused by the wireless channel.

[0233] Data arrives at the coding block in the form of up to two transport blocks per TTI per DL / UL cell. The following coding steps can be applied to each transport block in a DL / UL cell:

[0234] - Add cyclic redundancy check (CRC) code to the transport block;

[0235] - Code block segmentation and code block CRC attachment;

[0236] - Channel coding;

[0237] - Rate matching;

[0238] - Code block concatenation.

[0239] In actual communication systems, for ease of implementation, transport blocks larger than a certain size are divided into multiple smaller data blocks for encoding. These smaller data blocks are called code blocks.

[0240] Since the amount of radio resources for transmitting transport blocks and / or UCI is not dynamic but is fixed based on the setting or allocation by the BS, rate matching must be performed on the encoded code blocks to match this. Typically, rate matching is performed by puncturing or repetition. For example, if the number of transmission bits that can be transmitted by the corresponding radio resources is X, and the number of coded bit sequences, i.e., the number of output bits of the encoder, is Y, then if X and Y are different, rate matching is performed to adjust the length of the coded bit sequence to match X. If X>Y, all or part of the bits of the coded bit sequence are repeated so that the length of the rate-matched sequence becomes equal to X. X <Y이면, 레이트 매칭된 시퀀스의 길이가 X과 같아지도록, 코딩된 비트 시퀀스의 비트들 중 일부가 펑처링되며, 펑처링된 비트는 전송에서 제외된다. 할당된 / 설정된 무선 자원 내에 전송될 수 있는 비트 수는, 예를 들어, 상기 무선 자원에 포함되는 PRB들의 개수, OFDM 심볼들의 개수, 변조 차수 등에 기반하여 결정될 수 있다.

[0241] In a wireless communication system, a transmitter encodes data to be transmitted using channel coding having a specific code rate, and then adjusts the code rate of the data to be transmitted through a rate matching process consisting of puncturing and repetition.

[0242] The output bit sequence after rate matching and code block concatenation is modulated into modulation symbols through a modulator according to a modulation scheme. The modulation symbols are mapped to radio resources allocated by the BS and transmitted to the receiver through the radio resources. For example, if a PUCCH or PUSCH resource is configured / indicated with N PRBs and L OFDM symbols, modulation symbols can be mapped one-to-one to the remaining resource elements, excluding resource elements to which reference signals, etc. are mapped and cannot be used, among the resource elements in the PUCCH / PUSCH resource.

[0243] The decoding process of a channel code is the reverse of the encoding process, with a decoder corresponding to each encoder in the transmitter being used in the decoding process performed at the receiver. For example, the receiver decodes each code block (CB), then constructs a TB, and finally checks whether the TB CRC passes. In current 3GPP-based systems, the CB CRC is used to quickly terminate decoding. For example, if the CB CRC fails, the receiver can generate a NACK without decoding other CBs.

[0244] The introduction of artificial intelligence (AI) into communications can streamline and improve real-time data transmission. AI can use numerous analytics to determine how complex target tasks should be performed. AI can increase efficiency and reduce processing delays. Time-consuming tasks such as handovers, network selection, and resource scheduling can be performed instantly through AI. AI can also play a key role in machine-to-machine (M2M), machine-to-human, and human-to-machine communications. AI can also enable rapid communication in brain-computer interfaces (BCIs). AI-based communication systems can be supported by metamaterials, intelligent structures, intelligent networks, intelligent devices, intelligent cognitive radios, self-sustaining wireless networks, and machine learning (ML). The following describes a functional framework for AI / ML operations. To further explain AI (or AI / ML), the following terms can be defined:

[0245] - Data collection: Data collected from network nodes, management entities, or UEs as a basis for AI model training, data analysis, and inference.

[0246] - AI model: A data-driven algorithm that applies AI technology to generate a set of outputs containing predictive information and / or decision parameters based on a set of inputs.

[0247] - AI / ML training: An online or offline process of training an AI model by learning features and patterns that best represent the data and obtain a trained AI / ML model for inference.

[0248] - AI / ML inference: The process of making predictions or inducing decisions based on collected data and the AI ​​model using a trained AI model.

[0249] Life cycle management (LCM) procedures for AI / ML models (e.g., model training, model deployment, model inference, model monitoring, model updates, etc.) can be divided into functionality-based LCM and model-based LCM. In functionality-based LCM, AI / ML models may not be identified to the network, and the network can direct the activation / deactivation / fallback / switching of AI / ML functionality. In model identifier (ID)-based LCM, AI / ML models can be identified to the network, and the network / UE can activate / deactivate / select / switch AI / ML models based on the model ID.

[0250] Figure 12 illustrates a general functional architecture relevant to both functionality-based LCM and model-based LCM. Some of the functions or some data / information / command flows (e.g., arrows) illustrated in Figure 12 may be omitted. Referring to Figure 12, the general functional framework may include a data collection function (10), a model training function (20), a management function (30), an inference function (40), and a model storage function (50).

[0251] The data collection function (10) is a function that provides input data to the model training function (20), management function (30), and inference function (40). The data collection function (10) can perform data preparation based on raw data and provide input data processed through data preparation. The raw data may include, for example, received data / measurement data from UEs or other network entities, inference / output of AI / ML models, etc. The data collection function (10) may be performed by a single entity (e.g., UE, network node, etc.) or may be performed by multiple entities. Here, training data (11) refers to data required as input for the AI / ML model training function (20). Monitoring data (12) refers to data required as input for the management function (30) of the AI / ML model or AI / ML function. Inference data (13) refers to data required as input for the AI / ML inference function (30). The model training function (20) is a function that performs AI / ML model training, validation, and testing that can generate model performance metrics that can be used as part of the AI / ML model testing procedure. If necessary, the model training function (20) can perform data preparation (e.g., data pre-processing and cleaning, formatting, and transformation) based on training data (11) transmitted from the data collection function (10).The trained / updated model (21) is used to transfer the trained, validated and tested AI / ML model to the model repository function (50) if there is a model repository function (50) or to transfer an updated version of the model to the model repository function (50). The management function (30) is a function that supervises the operation of the AI / ML model or AI / ML function. In addition, the management function (30) may perform decisions to ensure appropriate inference operations based on data received from the data collection function (10) (e.g., monitoring data (12)) and / or data received from the inference function (40) (e.g., inference output (41)). The management instruction (32) is information required as input to manage the inference function (40). The relevant information may include selection / (de)activation / switching of an AI / ML model or AI / ML-based function, and may also include fallback to non-AI / ML operations (e.g., operations that do not rely on the inference process). A model transfer / delivery request (33) may be used to request model(s) from a model repository (50). A performance feedback / retraining request (31) refers to information required as input to a model training function (20) (e.g., for the purpose of (re)training or updating a model). An inference function (40) is a function that provides output from the process of applying an AI / ML model or AI / ML function using data provided by a data collection function (10) (e.g., inference data (13)) as input. Data preparation (e.g., data pre-processing and cleaning, formatting and transformation) may also be performed based on the inference data (13) delivered by the data collection function (10).The inference function (40) may perform data preparation (e.g., data pre-processing and cleaning, formatting, and transformation) based on the inference data (13) provided by the data collection function (10), if necessary. The inference output (41) is data used by the management function (30) to monitor the performance of the AI / ML model or AI / ML function. The inference output (41) may include the inference output of the AI / ML model generated by the inference function (30), and the details of the inference output may vary depending on the use case. The model repository function (50) is a function that stores a learned / updated model that can be used to perform the inference function (40). The model repository function (50) illustrated in FIG. 12 may be used as a reference point (if any) when applicable to protocol termination, model transmission / delivery, and related processes. In addition, the model repository function (50) is an example and is not intended to limit the storage location of an actual AI / ML model, and may be omitted. Model transfer / delivery (51) is used to transfer AI / ML models to inference functions.

[0252] Depending on whether AI / ML functions are possible between multiple nodes, the level of cooperation can be defined as follows, and variations due to combination of the multiple levels below or separation of any one level are also possible.

[0253] Cat 0a) No collaboration framework: AI / ML algorithms are purely implementation-based and do not require any changes to the wireless interface.

[0254] Cat 0b) This level corresponds to a framework with a modified wireless interface tailored to efficient implementation-based AI / ML algorithms, but without collaboration.

[0255] Category 1) involves inter-node support to improve the AI / ML algorithms of each node. For example, this applies when a specific node receives support from another node (for training, adaptation, etc.), and vice versa. At this level, model exchange between network nodes is not required.

[0256] Category 2) Joint AI / ML tasks can be performed across multiple nodes. This level requires the exchange of AI / ML model commands or data between network nodes.

[0257] FIG. 12 is a diagram illustrating an overall functional framework for an AI / ML model, and not all functions and / or all data / information / command signals illustrated in FIG. 12 may be performed within a specific node, but only some of them may be performed.

[0258] AI / ML models can be classified into one-side models and two-side models depending on whether training and / or inference are performed on a single node or jointly / sequentially on multiple nodes.

[0259] A unidirectional model can refer to an AI / ML model in which inference is performed entirely by a single node (e.g., a terminal or network). Here, AI / ML model training can also be performed entirely by that same node. AI / ML model training and inference can be performed by the same node, or alternatively, AI / ML model training and inference can be performed by separate nodes.

[0260] A bidirectional model may refer to an AI / ML model in which joint inference is performed across multiple nodes (e.g., UEs and networks). Joint inference means that inference is performed jointly across multiple nodes. For example, a first part of the inference may be performed by a first node, and the remaining part may be performed by a second node. Bidirectional models can be categorized into several types depending on the training method of the AI / ML model, as follows.

[0261] - First type: AI / ML models can be trained on a single node. In this case, joint training can be performed. The trained model can then be distributed to other nodes / objects.

[0262] - Second type: Joint training of AI / ML models can be performed on multiple nodes / entities (e.g., networks and UEs). Joint training can mean that model generation (e.g., CSI generation part) and model reconstruction (CSI compression by sub-use case) are trained in the same loop for forward activation and backward gradient. In this type, joint training can include both simultaneous training (e.g., model generation training and model reconstruction training are performed simultaneously) and sequential training (e.g., model reconstruction training is performed after model generation training).

[0263] - Third type: Separate training of AI / ML models can be performed on multiple nodes (e.g., the network and UE). Separate training may mean that training starts sequentially on one node and continues on other nodes. In this case, the first node first performs the AI / ML model and shares the training data with the second node. The second node can then use the shared training data to perform the AI / ML model. For example, training for the CSI generation part may be performed by the UE, and CSI reconstruction may be performed by the network.

[0264] Figure 13 illustrates the flow of operations based on an artificial intelligence (AI) / machine learning (ML) model. Operations described in some implementations of this specification described below can be described / interpreted based on an AI / ML model as in Figure 13 even without separate mention (e.g., without explicit mention of being by / based on / for an AI / ML model). Furthermore, unless specifically limited in some descriptions of this specification, an AI / ML model may correspond to a one-side model in which inference is entirely performed by a single node or a two-side model in which joint inference is performed by multiple nodes.

[0265] > Step 1: In some implementations of this specification described below, signaling (e.g., information / data / channel / signal, etc.) or a set of signaling between a specific node (e.g., UE, network, etc.) and another node may be interpreted as the signaling or set of signaling of Step 1 used to perform operations based on the AI / ML model, even if not otherwise stated. For example, in some implementations of this specification, the signaling or set of signaling may correspond to training data for training (e.g., generating and / or reconstructing) the AI / ML model of FIG. 12, or may correspond to inference data used for inference of the AI / ML model, or may correspond to feedback for the AI / ML model, etc. If some implementations of this specification do not require signaling between nodes prior to operations based on the AI / ML model, Step 1 may be omitted. If some implementations of this specification use a unidirectional model, the unidirectional / bidirectional signaling (set) of some implementations of this specification may correspond to the signaling of Step 1. Additionally, in some implementations of this specification where a bidirectional model is used, unidirectional / bidirectional signaling of some implementations of this specification may correspond to the signaling of step 1, and also repetitive signaling operations may correspond to the signaling of step 1. For example, in AI / ML model-based beam management (BM), if a BS predicts (e.g., infers) beam(s) with good quality based on an AI / ML model, the BS may receive quality / intensity information for multiple beams from the UE. Additionally, if a UE predicts (e.g., infers) beam(s) with good quality based on an AI / ML model, the UE may receive multiple beams from the BS.

[0266] > Step 2: In some implementations of this specification described below, an operation (e.g., calculation, selection, prediction, etc.) in a specific node (e.g., UE, network, etc.) or a joint operation (e.g., calculation, selection, prediction, etc.) in multiple nodes (e.g., UE, network, etc.) may correspond to the operation of Step 2 based on one or more functions in the functional framework of the AI / ML model, even if not otherwise stated. For example, it may correspond to training (e.g., generation and / or reconstruction) of the AI / ML model in FIG. 12, or it may correspond to inference of the AI / ML model, etc. When a one-way model is used, an operation performed by a single node in some implementations of this specification may correspond to the operation of Step 2, and also when a two-way model is used, a joint operation performed by multiple nodes in some implementations of this specification may correspond to the operation of Step 2. For example, in an AI / ML model-based BM, the BS can use quality / intensity information for multiple beams received from the UE as inference data to predict (e.g., infer) beam(s) with good quality based on the AI / ML model. Furthermore, the UE can measure multiple beams received from the BS and use the measurement results as inference data to predict (e.g., infer) beam(s) with good quality based on the AI / ML model.

[0267] > Step 3: In some implementations of the present specification described below, signaling (e.g., information / data / channel / signal, etc.) or a set of signaling between a specific node (e.g., UE, network, etc.) and another node may be interpreted as being the signaling or signaling set of step 3 generated (as a result) due to an operation based on an AI / ML model, even if not otherwise stated. For example, the signaling or signaling set may correspond to an output resulting from the inference of the AI / ML model of FIG. 12. If signaling between nodes is not required as a result of an operation based on an AI / ML model in the present invention, step 3 may be omitted. In some implementations of the present specification, when a one-way model is used, one-way / two-way signaling (set) may correspond to the signaling of step 3 in some implementations of the present specification. Additionally, in some implementations of the present specification where a bidirectional model is utilized, in some implementations of the present specification, unidirectional / bidirectional signaling may correspond to the signaling of step 3, and also, repetitive signaling operations may correspond to the signaling of step 3. For example, in an AI / ML model-based BM, the BS may transmit to the UE the beam(s) predicted based on the AI / ML model as candidates so that the UE can determine the optimal beam. Additionally, the UE may report to the BS the beam(s) predicted based on the AI / ML model to request the BS to transmit the candidate beams as candidates for determining the optimal beam.

[0268] In relation to CSI, RI is the number of spatially distinct layers and indicates whether spatial multiplexing is possible, which can increase the data rate. When a CSI report or CSI sub-report includes PMI, the bit width of the PMI field may vary depending on the RI. Therefore, the CSI payload size may vary depending on the RI value assumed or used in generating the CSI report or CSI sub-report.

[0269] Meanwhile, CRI is used to inform the UE of its preferred beam or to inform the CSI-RS resources used to calculate RI, PMI, CQI, LI, etc., which the UE reports through CSI reports. Since RI, PMI, CQI, LI, etc. are calculated based on CRI, the BS must know which CSI-RS resources were used to calculate RI, PMI, CQI, LI in order to determine the channel status. According to 3GPP TS 38.212, the bitwidth of the CRI field in the CSI report is log2(K CSI-RS s ) is determined based on, where K CSI-RS s is the number of CSI-RS resources, or if CSI-ReportSubConfig is set and the CSI-ReportSubConfig sets a list of CSI-RS resource IDs, it is the number of CSI-RS resources set in the corresponding CSI-ReportSubConfig. Referring to 3GPP TS 38.212, for example, the bitwidth of the CRI field is ceil{log2(K CSI-RS s )}, and K CSI-RS s The value of is the number of CSI-RS resources in the resource set. In this case, the UE has a bit width ceil{log2(K CSI-RS s )} within the set of CSI resources that are configured or triggered to report CSI via the CRI field. CSI-RS s One of the CSI-RS resources can be notified to the BS. As another example, if L sub-configurations are configured and CSIs for N sub-configurations are configured / instructed to be included in one CSI report, the value K CSI-RS sThe bit width of the CRI field may be calculated by replacing the number of CSI-RSs (i.e., the number of CSI-RS resources) in the sub-configuration (or the number of CSI-RSs (i.e., the number of CSI-RS resources) associated with the corresponding sub-configuration). If one CSI reporting configuration includes L sub-configurations, and one CSI report corresponding to the CSI reporting configuration includes M CSI sub-reports corresponding to M sub-configurations among the L sub-configurations according to configuration / instruction by the BS, the CSI report corresponding to the one CSI reporting configuration may include a CRI field in each of the M CSI sub-reports (if there is no sub-configuration in which the number of associated CSI-RS resources is 1). Therefore, the CSI payload size may vary depending on the CRI value assumed or used in generating the CSI report or the CSI sub-report.

[0270] Section 9.2.5 of 3GPP TS 38.213 states: If a UE would multiplex CSI reports that include Part 2 CSI reports in a PUCCH resource, the UE determines the PUCCH resource and a number of PRBs for the PUCCH resource or a number of Part 2 CSI reports assuming that each of the CSI reports and, if any, each CSI sub-report included in a CSI report, indicates rank 1, or rank combination of {1, 1} if applicable. When the upper layer parameter csi-ReportMode of the CSI reports is set to 'Mode2', the UE determines the number of PUCCH resources and PRBs for the PUCCH resources or the number of Part 2 CSI reports, assuming that each CRI in the CSI report is associated with a resource pair.

[0271] According to the description in section 9.2.5 of the previously extracted 3GPP TS 38.213, when transmitting CSI report(s) (and / or single / multiple CSI sub-report(s)) including CSI Part 2 over PUCCH, since the payload of CSI Part 2 is variable depending on the rank and rank information is included in CSI Part 1 with a fixed payload size, in order for the BS and the UE to make the same assumption on the number of PRBs of the PUCCH transmitted by the UE, the UE always assumes that the reference CSI Part 2 payload size is rank 1 to determine the number of PRBs for the PUCCH (e.g., regardless of the actual calculated rank value, the UE calculates the CSI Part 2 payload size based on rank 1 and determines the number of PRBs within the number of PRBs set for the PUCCH resource based on the determined UCI payload size), but the CSI Part 2 is transmitted over PUCCH. It can be configured based on the actual rank value included in 1.

[0272] According to the current standard, since CSI Part 1 and CSI Part 2, which constitute a CSI report transmitted via PUCCH, are always mapped and transmitted on the same single channel (e.g., PUCCH or PUSCH), when a UE selects a PUCCH resource or determines the number of resource elements of a PUSCH, it is based on the size of CSI Part 2 assuming rank = 1, rather than on the actual calculated rank value. This may result in inevitable omission of some of the CSI Part 2 information (if the actual rank value is greater than 1), or in a waste of resources if the coding rate is lowered to prepare for this (if the actual rank value is 1).

[0273] Additionally, even when multiple CSI sub-reports corresponding to multiple sub-configurations are included in a single CSI report according to the spatial / power domain adaptation introduced in Rel-18 network energy saving (NES), the CSI Part 2 payload size of each CSI sub-report may vary according to the rank value of each CSI sub-report, but the UE selects PUCCH resources (e.g., number of PRBs) assuming rank 1.

[0274] The payload size of CSI Part 2 may vary depending on which CSI-RS resource among the CSI-RS resource set configured by the UE for CSI reporting is selected to calculate CSI, in addition to the rank value. For example, if CSI-RS resource #1 and CSI resource #2 are configured within a specific CSI-RS resource set, and the number of ports for CSI-RS resource #1 is m and the number of ports for CSI-RS resource #2 is n (where, m is a natural number different from n), the payload size of CSI Part 2 may vary depending on which CSI-RS resource the UE selects for CSI reporting to configure the CSI report.

[0275] Therefore, to avoid such inefficient resource waste or omission of CSI, an enhancement may be needed to enable the UE to determine the number of RBs required to transmit a CSI report including the actual CSI Part 2.

[0276] <Method #1> A method in which a UE sets multiple PUCCH resources in advance according to the rank value / CRI value of a CSI report or the payload size (of the entire CSI or CSI Part 2), and selects a corresponding PUCCH resource according to the rank value / CRI value of the actually calculated CSI report or the payload size.

[0277] When the UE is configured with dedicated PUCCH resource(s) from the BS, the UE may be configured with one or more PUCCH resources per rank. For example, the UE may be configured with PUCCH resource #1 for rank 1, PUCCH resources #2 and #3 for rank 2, PUCCH resources #4, #5, and #6 for rank 3, and PUCCH resource #7 for rank 4. As another example, the UE may be configured with PUCCH resource #1 corresponding to rank 1, PUCCH resource #2 corresponding to rank 2, PUCCH resource #3 corresponding to rank 3, and PUCCH resource #4 corresponding to rank 4 in advance. Or, as another example, the UE may be configured with PUCCH resource #1 when the CSI payload size is 100 bits or less, and PUCCH resource #2 when the CSI payload size is greater than 100 bits and less than or equal to 200 bits. Alternatively, ranks 1 and 2 may be grouped and ranks 3 and 4 may be grouped, so that PUCCH resources for ranks 1 and 2 and PUCCH resources for ranks 3 and 4 are set separately, or the range of payload sizes may be set / defined more finely / coarsely.

[0278] When a UE is configured / instructed to transmit a periodic CSI (P-CSI) report or a semi-persistent CSI (SP-CSI) report, the UE may select the most appropriate PUCCH resource (e.g., the resource with the smallest resource that can contain all CSI) among the configured PUCCH resources, considering the rank value / CRI value of the calculated CSI or the payload size of the CSI report (all or CSI Part 2). In addition, in some implementations, in order to provide the BS with information on the rank value / CRI value actually calculated by the UE, only the CSI Part 1 or rank information among the contents of the CSI report may be transmitted first in slot n, and then the CSI Part 2 (and the remaining Part 1 information) calculated based on the actual rank or the remaining CSI excluding the rank information may be transmitted in slot n+D. In this case, the value of D may be preset or defined in the standard, taking into account channel aging and UE / BS processing / decoding, etc. When multiple CSI reports are multiplexed, the UE can be configured in advance whether to transmit all rank values / CRI values ​​for each CSI report for rank information to be transmitted in slot n, or only a single representative (e.g., smallest or largest) rank value / CRI value. For example, when there are multiple CSI reports to be transmitted in one slot, and each of the multiple CSI reports may have a single rank value / CRI value, the UE can, depending on the configuration, report all rank values / CRI values ​​corresponding to the multiple CSI reports one-to-one, or report a representative value. Furthermore, in some implementations, the UE can be configured in advance to select a PUCCH resource corresponding to which rank value (e.g., smallest or largest) is selected when the rank values / CRI values ​​are different between the multiple CSI reports.

[0279] For example, if the actual rank value of the CSI calculated by the UE is 1 or 2 (or if the part 2 CSI is between 100 bits and 200 bits), a PUCCH format 2 with 4 PRBs may be used to transmit a P-CSI or SP-CSI report, and if the rank is 3 or 4 (or if the CSI part 2 exceeds 200 bits and is less than or equal to 400 bits), a PUCCH format 3 with 8 PRBs resource may be selected to transmit a P-CSI or SP-CSI report. In some implementations, if multiple PUCCH resources are configured for the rank calculated by the UE, which PUCCH resource among the multiple PUCCH resources is to be used may be determined based on a PUCCH resource indicator value in the DCI format.

[0280] The BS can set appropriate PUCCH resources for the UE by considering the disadvantage of having to reserve multiple PUCCH resources for each rank or payload size range and the benefit of reducing unnecessary waste of resources or omission of CSI by using PUCCH resources that match the actual rank value / CRI value.

[0281] <Method #2> A method of transmitting on (CG-)PUSCH when the CSI report includes CSI Part 2 or the rank for the CSI report including Part 2 is higher than a specific rank value (e.g., rank 2) (or the payload size of the CSI report is higher than a specific payload size).

[0282] The UE may be configured / instructed to transmit the CSI report on (CG-)PUSCH instead of PUCCH if the CSI report includes Part 2 or if the calculated rank / RI for the CSI report including Part 2 is greater than or equal to a preset rank / RI value. In this case, the inclusion of Part 2 in the CSI report may mean that the BS sets a specific reportQuantity in the configuration for CSI report transmission (e.g., report setting / configuration), or instructs reporting (wideband / subband reporting) or a specific codebook. In some implementations, the UE may be configured with a rank threshold value to determine whether to switch over and transmit a CSI report (e.g., a P-CSI report or an SP-CSI report) that has been previously configured to be transmitted on PUCCH to the PUSCH. Additionally, in some implementations, the UE may also be configured with (CG-)PUSCH resources to transmit when the calculated rank value exceeds a rank threshold value, similar to method #1, wherein one or more (CG-)PUSCH resources may be configured for each rank value / rank group (or CRI value / CRI group) or for each payload size range of the CSI report.

[0283] For example, if the CSI calculated by the UE is higher than or equal to a preset rank / CRI value (e.g., rank 2), the CSI report can be transmitted on a preset (CG-)PUSCH resource instead of PUCCH (even if it is a P-CSI report or SP-CSI report on PUCCH). Alternatively, in some implementations, the UE can schedule the PUSCH to transmit the CSI report via a scheduling request (SR), wherein the SR resource can be configured before the PUCCH resource configured for the CSI report transmission in advance. In addition, as mentioned above, if the (CG-)PUSCH resource is configured according to the actual rank value of the CSI report or according to the payload size, the (CG-)PUSCH resource corresponding to the rank or having the smallest resource that can contain all the CSI can be selected to transmit the CSI report according to the actual rank or payload size of the calculated CSI.

[0284] <Method #3> A method for configuring / instructing the UE to perform different encoding of PUCCH depending on the rank value / CRI value of the calculated CSI.

[0285] The UE may be configured / instructed to one-part encode (e.g., encode CSI part 1 and CSI part 2 through one block) or two-part encode (e.g., encode CSI part 1 and CSI part 2 through separate encoding blocks) the CSI report transmitted on the PUCCH based on whether a reference rank value (e.g., a rank threshold) is set in advance and the rank value calculated for the actual CSI report is greater than or less than the set reference rank value.

[0286] For example, if the CSI calculated by the UE is less than or equal to rank 2, it can be transmitted as a one-part encoded PUCCH as before, and if it is rank 3 or higher, it can be stipulated or set to perform two-part encoding, and rank information or the CSI part 2 payload size can be included in Part 1, and additionally, the number of antenna ports, CSI type, rank indicator (RI) restriction, etc. can be included to configure Part 2 to have a fixed payload size, and Part 2 can be configured to have various payload sizes according to Part 1. Since the BS can determine the payload size of Part 2 through the Part 1 information, the CSI report can be configured / transmitted according to the rank / payload size of the actual CSI report without ambiguity between the BS and the UE.

[0287] The UE may be separately configured in advance for PUCCH resources to be used in case of one-part encoding and PUCCH resources to be used in case of two-part encoding, or, if separate PUCCH resources are not configured, the UE may be configured / instructed to configure PUCCH DMRS (e.g., symbol position / sequence) differently depending on the encoding method.

[0288] <Method #4> A method in which one CSI report or multiple CSI reports transmitted on one PUCCH instance are divided into CSI parts 1 and 2 (of each CSI report) (or information about rank information / payload size (of each CSI report) and the remaining CSIs) and transmitted by time division multiplexing (TDM) / frequency division multiplexing (FDM) / spatial division multiplexing (SDM) on two different PUCCHs (or PUCCH + (CG-)PUSCH), and the number of PRBs of the PUCCH including Part 2 (of each CSI report) (or the remaining CSI excluding information about rank information / payload size (of each CSI report)) is determined (or (CG-)PUSCH resources) according to the actually calculated rank / payload size.

[0289] The reason why PUCCH resources were selected assuming rank 1 when transmitting CSI reports using the existing one-part encoded PUCCH was because there was no way for the UE to inform the BS in advance of the actual calculated rank information / payload size. If there were a way for the UE to inform the BS of the actual rank value / CRI value (or payload size) of the CSI report calculated by the UE, the UE could select the PUCCH resource (or (CG-)PUSCH) corresponding to the actual rank value / CRI value to configure the CSI.

[0290] The UE may first transmit some or all information (e.g., only rank information or CSI Part 1) from among the information that can be included in the existing CSI Part 1, the number of ports, the CSI type, RI constraints, etc., on a sequence-based PUCCH (e.g., a PUCCH that changes the phase and / or cyclic shift value of the sequence mapped to the PUCCH to transmit information with a small UCI payload size (e.g., up to 2 bits), such as PUCCH format 0 currently used in NR) or a pre-arranged / configured UL signal / channel (e.g., SR PUCCH / RACH) in slot n to transmit information about the actual rank value / CRI value (or payload size) to the BS, and then select a PUCCH resource (or (CG-)PUSCH) that can configure CSI reporting with the remaining CSIs according to the actually calculated rank value in slot n+D to transmit. At this time, the value of D may be pre-configured or defined in the standard in consideration of channel aging and UE / BS processing / decoding. When multiple CSI reports are multiplexed, the UE can be configured in advance whether to transmit all rank values / CRI values ​​for each CSI report for rank information to be transmitted in slot n or to transmit only one representative (e.g., the smallest or largest) rank value / CRI value. Furthermore, when the rank values / CRI values ​​are different between multiple CSI reports, the UE can be configured in advance to select a PUCCH resource corresponding to which rank value / CRI value (e.g., the smallest or largest rank / CRI value).

[0291] At this time, sequence / frequency / time resources, such as sequence-based PUCCH or SR resources, through which information such as rank (or payload size) is transmitted, can be set in advance for the UE by rank (group) (or by payload size range), and the rank value / CRI value can be transmitted by TDM / FDM / SDM with the PUCCH (or (CG-)PUSCH) carrying the CSI report composed of the remaining CSI according to the actual rank value / CRI value.

[0292] In some implementations, when the UE transmits two PUCCHs or PUCCH+(CG-)PUSCH in TDM manner in Method #4, an additional restriction may be set on the transmission interval between the two PUCCHs (or PUCCH and (CG)-PUSCH) to take channel aging into account (e.g., the transmission interval shall be within X symbols / symbols). Also, when SDMing the CSI report(s), they are transmitted on a single PUCCH instead of two different PUCCHs (or PUCCH+(CG-)PUSCH), but may also be transmitted on a multi-rank PUCCH in SDM form (unlike the current NR PUCCH which only allows single layer transmission) or on a Simultaneous Transmission across Multi-Panel (STxMP) PUCCH that transmits UL signals simultaneously over different panels.

[0293] <Method #5> When multiple CSI reports are multiplexed in one PUCCH instance, a method of selecting / determining PUCCH resources by linking rank values / CRI values ​​to each PUCCH resource or linking rank values / CRI values ​​to CSI reports.

[0294] Since multiple CSI reports may be included for one PUCCH transmission point (e.g., one PUCCH instance), both a method of associating rank values / CRI values ​​to PUCCH resources and a method of associating rank values / CRI values ​​to CSI reports may be considered.

[0295] In the case of a method of associating a rank value to a PUCCH resource, for example, when a reference rank value is set to 1 for PUCCH resource #1 within a specific slot and a reference rank value is set to 3 for PUCCH resource #2 within the same slot, and when CSI report #1 and CSI report #2 are multiplexed, if the actually calculated rank value for at least one or both of the two CSI reports is 3 or greater, PUCCH resource #2 is selected, and the CSI payload sizes corresponding to CSI report #1 and CSI report #2 (e.g., the sum of the payload size of CSI report #1 and the payload size of CSI report #2) are determined based on the reference rank 3, and the number of PRBs for PUCCH resource #2 can be determined based on the size. Alternatively, if the actual calculated rank value for at least one or both of the above two CSI reports is less than 3, PUCCH resource #1 is selected, and the CSI payload sizes corresponding to CSI report #1 and CSI report #2 (e.g., the sum of the payload sizes of CSI report #1 and CSI report #2) are determined based on the reference rank 1, and the number of PRBs for PUCCH resource #1 can be determined based on the sizes.

[0296] In the case of a method of associating a rank value to a CSI report, for example, when a PUCCH resource is set within a specific slot and a reference rank value is set to 1 for CSI report #1 and a reference rank value is set to 3 for CSI report #2 and CSI report #1 and CSI report #2 are multiplexed, a total CSI payload size (= CSI payload size #1 + CSI payload size #2) may be determined based on a CSI payload size #1 corresponding to CSI report #1 based on a reference rank value 1 and a CSI payload size #2 corresponding to CSI report #2 based on a reference rank value 3, and the number of PRBs of the PUCCH resource may be determined based on the total CSI payload size.

[0297] <Method #6> In case the rank change is relatively static (e.g., the channel condition does not change quickly), a method in which the BS sets the UE a rank value to assume when determining the number of PUCCH resources and PRBs in advance (in a configurable manner), and a method in which the UE sets the rank value to assume when transmitting a CSI report including Part 2 via PUCCH by codebook type, and determines the number of PUCCH resources / PRBs based on the rank value.

[0298] Because channel conditions change over time, the UE reports channel conditions to the BS periodically / aperiodically by including RI, PMI, CQI, etc. in the CSI report. Here, RI is the number of spatially distinct layers and indicates whether spatial multiplexing is possible to increase the data rate. However, if the UE is relatively stationary or the channel does not change rapidly, the rank value may remain relatively static. In this case, when the UE periodically calculates the rank value for P-CSI reporting, the same rank value may be maintained for a relatively long period of time.

[0299] If the RI value of a CSI report reported by a UE remains constant for a specific period of time (e.g., a specific duration or while a timer is running) or a specific number of times (e.g., N), the BS can configure a rank value to be assumed when transmitting a CSI report including CSI Part 2 on PUCCH to the UE. For example, if the RI value in a P-CSI report periodically reported by the UE reports the same RI = 2 for 160 ms or 10 times, the UE can be configured by the BS to assume rank 2 instead of rank 1 when transmitting a CSI report including CSI Part 2 on PUCCH. Alternatively, the BS can predict the rank or payload size (e.g., via artificial intelligence (AI) / machine learning (ML)) and configure a rank value to be assumed by the UE. In some implementations, for multiple CSI reports, the rank value assumed by the UE when selecting / determining PUCCH resources may be individually configured for each CSI report. When a CSI report needs to be transmitted, the UE can determine the number of PUCCH resources / PRBs based on the rank value previously configured by the BS and transmit the CSI report.

[0300] A UE may be configured with a codebook type for CSI reporting. In some implementations, considering the relationship between each rank value for each codebook type and the payload size of the CSI report according to the rank value, the UE may be configured in advance with a rank value to assume when transmitting a CSI report including Part 2 CSI on PUCCH for each codebook type. For example, in the case of a Type 1 codebook, since the payload size of Rank 1 is usually the largest, the UE may determine PUCCH resources and PRB(s) by assuming Rank 1, and in the case of a Type 2 codebook, the UE may determine PUCCH resources and PRB(s) by assuming a specific rank defined in the standard or a rank value set by the BS, which may be specified or configured by the BS. Additionally, in some implementations, for Type 2 codebooks with relatively large payload sizes (in NR, only CSI Part 1 is transmitted on PUCCH for Type 2 codebooks), restrictions may be set so that CSI is only composed and transmitted with a specific rank / specific part / specific frequency granularity (e.g., wideband (WB)).

[0301] <Method #7> A method of transmitting a CSI report on PUCCH / PUSCH based on the actual rank / CRI / payload size by predicting the rank value / CRI value or payload size of the CSI report (e.g., through AI / ML)

[0302] The BS can use AI / ML training to predict the rank value / CRI value (or payload size) of the CSI report to be reported by the UE by using the rank value / CRI value(s) (or CQI history, payload size of CSI report, etc.) for a specific time interval in the past reported by the UE as input, and can set the rank value / CRI value to be assumed when transmitting the CSI report including CSI Part 2 to the UE on PUCCH or apply it to decoding.

[0303] For example, the BS may set multiple PUCCH resources in advance on which a CSI report including CSI Part 2 can be transmitted, and set the UE to select one of them for reporting. At this time, the BS may perform AI / ML training using as input the rank values / CRI values ​​(or CQI history, payload size of CSI report, etc.) for a specific time period reported by the UE, and set the rank value / CRI value to be assumed by the UE, or may predict the number of PUCCH resources and PRBs to be selected by the UE and attempt decoding.

[0304] In some implementations, both the BS and the UE may perform AI / ML model inference, and the UE may select a PUCCH resource based on the inference result among PUCCH resources of various configured payload sizes and perform operations such as reporting CSI through the selected PUCCH resource (the BS may perform a detection and then decoding operation using the inference result), or the UE may predict a rank (or payload size) value through the above AI / ML training and report it to the BS, and transmit the PUCCH based on the corresponding rank value / CRI value (or payload size) for actual CSI reporting.

[0305] Since rank / CRI values ​​may change due to changes in channel environment, the UE may periodically calculate and report a monitoring metric (associated with rank / CRI values) to the BS, and the BS may instruct / configure whether to fallback to non-AI / ML based on the report. Alternatively, the UE may calculate and judge the monitoring metric to decide whether to continue applying the AI / ML training-based rank / CRI assumption or fallback to non-AI / ML. In some implementations, since the UE continues to report actual measurement-based rank information via CSI reporting (in this case, for example, if the BS is also predicting rank via AI / ML, it can compare the predicted rank value with the rank value reported by the UE), the BS may instruct the UE whether to continue or switch AI / ML operation related to CSI reporting without the UE reporting a separate monitoring metric.

[0306] In the implementations of the present specification described above, a "CSI report" may refer to a CSI report and / or a CSI sub-report. For example, in some implementations of the present specification described above, a CSI report may be replaced with a CSI sub-report and such implementations may apply, or some implementations of the present specification described above may apply to each CSI sub-report when multiple CSI sub-reports are included in a single CSI report.

[0307] The methods or implementations of the present specification described above may be applied independently, but may also be applied in the form of a combination (or merge) of some proposed methods. Information regarding whether the methods / implementations of the present specification described above are applied (or information regarding the rules of the methods / implementations of the present specification described above) may be specified for the BS to inform the UE through a predefined signal (e.g., a physical layer signal or a higher layer signal). In the present specification, the higher layer may include one or more of functional layers such as MAC, RLC, PDCP, RRC, and SDAP, for example.

[0308] According to some implementations of this specification, inefficient resource waste or CSI omission can be reduced. According to some implementations of this specification, a UE can determine the number of RBs required for transmitting a CSI report including CSI Part 2. According to some implementations of this specification, the problem of reserving multiple PUCCH resources for each rank or payload size range can be solved. According to some implementations of this specification, PUCCH resources appropriate for the actual rank value and / or CRI value can be used. According to some implementations of this specification, appropriate PUCCH resources can be configured for the UE.

[0309] Figure 14 illustrates the flow of uplink control information transmission in a UE according to some implementations of this specification.

[0310] A UE may perform operations according to some implementations of the present disclosure in connection with transmitting uplink control information. 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.

[0311] 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: receiving a physical uplink control channel (PUCCH) related configuration (S1401), wherein the PUCCH related configuration includes PUCCH resource information by rank; determining channel state information (CSI) to be reported (S1403); determining a PUCCH resource based on the PUCCH related configuration and a rank associated with the CSI (S1405); and transmitting a CSI report including the CSI on the PUCCH resource (S1407).

[0312] Figure 15 illustrates the flow of receiving uplink control information at a BS according to some implementations of this specification.

[0313] A BS may perform operations according to some implementations of the present disclosure in connection with receiving uplink control information. 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 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.

[0314] 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: transmitting a physical uplink control channel (PUCCH) related configuration (S1501), wherein the PUCCH related configuration includes PUCCH resource information by rank; and receiving a CSI report including channel state information (CSI) on a PUCCH resource based on the PUCCH related configuration (S1507), wherein the PUCCH resource may be for a rank associated with the CSI.

[0315] In some implementations related to FIG. 14 or FIG. 15, information regarding the rank associated with the CSI may be transmitted or received in slot n.

[0316] In some implementations related to FIG. 14 or FIG. 15, the CSI report may be transmitted or received in slot n+D, where D is a predetermined non-negative integer.

[0317] In some implementations related to FIG. 14 or FIG. 15, based on multiple CSI reports being multiplexed, including the CSI report, information regarding respective (respective) ranks associated with the multiple CSI reports may be transmitted or received in the slot n.

[0318] In some implementations related to FIG. 14 or FIG. 15, based on multiplexing of multiple CSI reports including the CSI report, information regarding the smallest or largest rank among each of the (respective) ranks associated with the multiple CSI reports may be transmitted or received in the slot n.

[0319] In some implementations related to FIG. 14 or FIG. 15, information may be provided to the user device regarding whether the smallest or largest value among the respective (respective) ranks associated with the plurality of CSI reports is reported.

[0320] In some implementations related to FIG. 14 or FIG. 15, based on including a plurality of CSI reports including the CSI report, the PUCCH resource may be determined based on a smallest or largest rank among the respective (respective) ranks associated with the plurality of CSI reports.

[0321] In some implementations related to FIG. 14 or FIG. 15, information may be provided to the user equipment regarding whether the PUCCH resource is determined based on the smallest or largest value among the rank values ​​to be reported.

[0322] In some implementations related to FIG. 14 or FIG. 15, the CSI report may include information regarding the rank associated with the CSI.

[0323] In some implementations related to FIG. 14 or FIG. 15, the number of resource blocks for the PUCCH resource may be determined based on the size of the CSI payload transmitted on the PUCCH resource.

[0324] 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.

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

Claims

1. In a method performed by a user device, Receive physical uplink control channel (PUCCH) related settings, wherein the PUCCH related settings include PUCCH resource information by rank; Determine the channel state information (CSI) to be reported; Determine the PUCCH resource based on the PUCCH-related settings and the rank related to the CSI; and Including transmitting a CSI report including the CSI on the PUCCH resource, method.

2. In paragraph 1, Including transmitting information about the rank related to the CSI in slot n, The above CSI report is transmitted in slot n+D, where D is a predetermined non-negative integer. method.

3. In paragraph 2, Based on multiple CSI reports including the above CSI report being multiplexed, information about each (respective) rank related to the multiple CSI reports is transmitted in the slot n. method.

4. In paragraph 2, Based on multiple CSI reports including the above CSI report being multiplexed, information about the smallest or largest rank among the respective (respective) ranks related to the multiple CSI reports is transmitted in the slot n. method.

5. In paragraph 4, Further comprising receiving information as to whether the smallest value or the largest value is reported among the respective (respective) ranks associated with the plurality of CSI reports. method.

6. In paragraph 1, Based on including multiple CSI reports including the above CSI report, the PUCCH resource is determined based on the smallest or largest rank among the respective (respective) ranks related to the multiple CSI reports. method.

7. In paragraph 6, Further comprising receiving information as to whether the PUCCH resource is determined based on a smallest value or a largest value among the rank values ​​to be reported. method.

8. In paragraph 1, The above CSI report includes information about the rank associated with the above CSI. method.

9. In paragraph 1, Including determining the number of resource blocks for the PUCCH resource based on the CSI payload size transmitted on the PUCCH resource. method.

10. At least one transmitter / receiver; 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, said operations comprising: Receive physical uplink control channel (PUCCH) related settings, wherein the PUCCH related settings include PUCCH resource information by rank; Determine the channel state information (CSI) to be reported; Determine the PUCCH resource based on the PUCCH-related settings and the rank related to the CSI; and Including transmitting a CSI report including the CSI on the PUCCH resource, User device.

11. 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, said operations comprising: Receive physical uplink control channel (PUCCH) related settings, wherein the PUCCH related settings include PUCCH resource information by rank; Determine the channel state information (CSI) to be reported; Determine the PUCCH resource based on the PUCCH-related settings and the rank related to the CSI; and Including transmitting a CSI report including the CSI on the PUCCH resource, Processing unit.

12. In a computer-readable non-transitory 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: Receive physical uplink control channel (PUCCH) related settings, wherein the PUCCH related settings include PUCCH resource information by rank; Determine the channel state information (CSI) to be reported; Determine the PUCCH resource based on the PUCCH-related settings and the rank related to the CSI; and Including transmitting a CSI report including the CSI on the PUCCH resource, Storage media.

13. In a method performed by a base station, Transmitting physical uplink control channel (PUCCH) related settings, wherein the PUCCH related settings include PUCCH resource information by rank; and It includes receiving a CSI report including channel state information (CSI) on a PUCCH resource based on the above PUCCH-related settings, The above PUCCH resource is for the rank associated with the above CSI, method.

14. In paragraph 13, Including receiving information about the rank associated with the CSI in slot n, The above CSI report is received in slot n+D, where D is a predetermined non-negative integer. method.

15. In paragraph 14, Based on multiple CSI reports including the above CSI report being multiplexed, information about each (respective) rank related to the multiple CSI reports is received in the slot n. method.

16. In paragraph 14, Based on multiple CSI reports including the above CSI report being multiplexed, information about the smallest or largest rank among the respective (respective) ranks related to the multiple CSI reports is received in the slot n. method.

17. In paragraph 16, Further comprising transmitting information as to whether the smallest value or the largest value among the respective (respective) ranks associated with the plurality of CSI reports is reported. method.

18. In paragraph 13, Based on including multiple CSI reports including the above CSI report, the PUCCH resource is related to the smallest or largest rank among the respective (respective) ranks associated with the multiple CSI reports. method.

19. In paragraph 18, Further comprising transmitting information on whether the PUCCH resource is determined based on the smallest value or the largest value among the rank values ​​to be received. method.

20. In paragraph 13, The above CSI report includes information about the rank associated with the above CSI. method.

21. In paragraph 13, The number of resource blocks for the PUCCH resource is determined based on the size of the CSI payload received on the PUCCH resource. method.

22. At least one transmitter / receiver; 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, said operations comprising: Transmitting physical uplink control channel (PUCCH) related settings, wherein the PUCCH related settings include PUCCH resource information by rank; and It includes receiving a CSI report including channel state information (CSI) on a PUCCH resource based on the above PUCCH-related settings, The above PUCCH resource is for the rank associated with the above CSI, Base station.

Images