Terminal device and base station device

Abstract

This terminal device comprises: an upper layer processing unit that receives N first upper layer parameters and a second upper layer parameter; a reception unit that receives a PDCCH in which DCI is placed; and a transmission unit that transmits a PUSCH in which UCI is placed. N is an integer of 1 or greater. Each of the N first upper layer parameters is a parameter for configuring one CSI report configuration. The second upper layer parameter is a parameter for configuring an aperiodic trigger state list. Each of the N CSI report configurations is configured for one CSI report. The DCI includes a CSI request field. The CSI request field is associated with one trigger state in the aperiodic trigger state list. The one trigger state is associated with the N CSI report configurations. When the one trigger state is a trigger state for an event triggered report, only one CSI report among the N CSI reports is included in the UCI.

Description

Terminal equipment and base station equipment

[0001] The present invention relates to terminal equipment and base station equipment. This application claims priority to Japanese Patent Application No. 2025-053499, filed in Japan on March 27, 2025, the contents of which are incorporated herein by reference.

[0002] The cellular mobile communication radio access method and radio network (hereinafter also referred to as "Long Term Evolution (LTE)" or "EUTRA: Evolved Universal Terrestrial Radio Access") is part of the Third Generation Partnership Project (3GPP:3 rd This is being considered in the Generation Partnership Project. In LTE, base station equipment is also called eNodeB (evolved NodeB), and terminal equipment is also called UE (User Equipment). LTE is a cellular communication system in which multiple base station devices are arranged in a cell-like structure to cover different areas. A single base station device may manage multiple serving cells.

[0003] 3GPP is considering a next-generation standard (NR: New Radio) to propose to the International Mobile Telecommunication Union (ITU) for next-generation mobile communication systems, IMT-2020 (Non-Patent Literature 1). NR is required to meet the requirements of three scenarios—enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliable and Low Latency Communication (URLLC)—within a single technological framework.

[0004] 3GPP is considering expanding the services supported by NR (Non-Patent Documents 2, 3, and 4).

[0005] "New SID proposal: Study on New Radio Access Technology", RP-160671, NTT docomo, 3GPP TSG RAN Meeting #71, Goteborg, Sweden, 7th - 10th March, 2016. “Release 17 package for RAN”, RP-193216, RAN chairman, RAN1 chairman, RAN2 chairman, RAN3 chairman, 3GPP TSG RAN Meeting #86, Sitges, Spain, 9th ― 12th December, 2019 “Release 18 package summary”, RP-213469, RAN chairman, RAN1 chairman, RAN2 chairman, RAN3 chairman, 3GPP TSG RAN Meeting #94-e, 6th ― 17th December, 2021“Summary for RAN Rel-19 Package: RAN1 / 2 / 3-led”, RP-232745, RAN chair, 3GPP TSG RAN Meeting #102, 11th ― 15th December, 2023

[0006] One aspect of the present invention provides a terminal device for efficient communication, a communication method used in the terminal device, a base station device for efficient communication, and a communication method used in the base station device.

[0007] (1) A first aspect of the present invention is a terminal device comprising: a top-layer processing unit that receives N first top-layer parameters and a second top-layer parameter; a receiving unit that receives a PDCCH in which downlink control information (DCI) is placed; and a transmitting unit that transmits a PUSCH in which uplink control information (UCI) is placed, wherein N is an integer of 1 or more, each of the N first top-layer parameters is a parameter for setting one CSI report setting, the second top-layer parameter is a parameter for setting an aperiodic trigger state list, each of the N CSI report settings is set for one CSI report, the DCI includes a CSI request field, the CSI request field is associated with one trigger state from the aperiodic trigger state list, the one trigger state is associated with the N CSI report settings, and if the one trigger state is a trigger state for an event-triggered report, then the UCI includes only one CSI report from the N CSI reports.

[0008] (2) A second aspect of the present invention is a terminal device, The system comprises a top-layer processing unit that receives N first top-layer parameters and a second top-layer parameter, a receiving unit that receives a PDCCH in which downlink control information (DCI) is placed, and a transmitting unit that transmits a PUSCH in which uplink control information (UCI) is placed, wherein N is an integer of 1 or more, each of the N first top-layer parameters is a parameter for setting one CSI report setting, the second top-layer parameter is a parameter for setting an aperiodic trigger state list, each of the N CSI report settings is set for one CSI report, each of the N CSI reports is associated with one CSI report priority value, the DCI includes a CSI request field, the CSI request field is associated with one trigger state from the aperiodic trigger state list, the one trigger state is associated with the N CSI report settings, and if the one trigger state is a trigger state for an event-triggered report, the bit sequence for the UCI is determined based on only one CSI report from among the N CSI reports arranged in ascending order of the CSI report priority values.

[0009] (3) A third aspect of the present invention is a base station device comprising: an upper layer processing unit that transmits N first upper layer parameters and a second upper layer parameter; a transmitting unit that transmits a PDCCH in which downlink control information (DCI) is placed; and a receiving unit that receives a PUSCH in which uplink control information (UCI) is placed, wherein N is an integer of 1 or more, each of the N first upper layer parameters is a parameter for setting one CSI report setting, the second upper layer parameter is a parameter for setting an aperiodic trigger state list, each of the N CSI report settings is set for one CSI report, the DCI includes a CSI request field, the CSI request field is associated with one trigger state from the aperiodic trigger state list, the one trigger state is associated with the N CSI report settings, and if the one trigger state is a trigger state for an event-triggered report, then the UCI includes only one CSI report from the N CSI reports.

[0010] According to one aspect of this invention, a terminal device can communicate efficiently. Furthermore, a base station device can communicate efficiently.

[0011] This is a conceptual diagram of a wireless communication system according to one aspect of this embodiment. The subcarrier spacing setting μ and the number of OFDM symbols per slot N according to one aspect of this embodiment. slot symbThis is an example showing the relationship between the CP (cyclic Prefix) settings. This is a diagram showing an example of how to configure a resource grid according to one aspect of this embodiment. This is a diagram showing an example of the configuration of a resource grid 3001 according to one aspect of this embodiment. This is a schematic block diagram showing an example of the configuration of a base station device 3 according to one aspect of this embodiment. This is a schematic block diagram showing an example of the configuration of a terminal device 1 according to one aspect of this embodiment. This is a diagram showing an example of the configuration of an SS / PBCH block according to one aspect of this embodiment. This is a diagram showing an example of monitoring opportunities for a search area set according to one aspect of this embodiment. This is a diagram showing an example of sending only one CSI report for N requests for CSI reports in the case of an event-triggered report according to one aspect of this embodiment.

[0012] Embodiments of the present invention will be described below.

[0013] floor(C) may be the floor function for a real number C. For example, floor(C) may be a function that outputs the largest integer within the range not exceeding the real number C. ceil(D) may be the ceiling function for a real number D. For example, ceil(D) may be a function that outputs the smallest integer within the range not falling below the real number D. mod(E, F) may be a function that outputs the remainder when E is divided by F. mod(E, F) may also be a function that outputs the value corresponding to the remainder when E is divided by F. exp(G) = e^G, where e is Napier's number. H^I represents H to the power of I. max(J, K) is a function that outputs the maximum value among J and K. Here, if J and K are equal, max(J, K) is a function that outputs either J or K. min(L, M) is a function that outputs the maximum value among L and M. Here, if L and M are equal, min(L, M) is a function that outputs either L or M. `round(N)` is a function that outputs the integer value closest to N. The "•" indicates multiplication.

[0014] In a wireless communication system according to one aspect of this embodiment, at least OFDM (Orthogonal Frequency Division Multiplex) is used. An OFDM symbol is a time-domain unit of OFDM. An OFDM symbol includes at least one or more subcarriers. An OFDM symbol is converted into a time-continuous signal in baseband signal generation. At least CP-OFDM (Cyclic Prefix - Orthogonal Frequency Division Multiplex) is used in the downlink. In the uplink, either CP-OFDM or DFT-s-OFDM (Discrete Fourier Transform - spread - Orthogonal Frequency Division Multiplex) is used. DFT-s-OFDM may be given by applying transform precoding to CP-OFDM.

[0015] An OFDM symbol may be a designation that includes a CP (Character Protection) attached to the OFDM symbol. In other words, an OFDM symbol may consist of the OFDM symbol itself and a CP attached to it.

[0016] Figure 1 is a conceptual diagram of a wireless communication system according to one embodiment of this model. In Figure 1, the wireless communication system comprises at least terminal devices 1A to 1C and a base station device 3 (BS#3). Hereinafter, terminal devices 1A to 1C will also be referred to as terminal device 1 (UE#1).

[0017] The base station device 3 may consist of one or more transmitting devices (or a transmitting point, a transceiver, and a transceiver). If the base station device 3 consists of multiple transmitting devices, each of the multiple transmitting devices may be located in a different position.

[0018] The base station apparatus 3 may provide one or more serving cells. A serving cell may be defined as a set of resources used for wireless communication. A serving cell is also referred to as a cell.

[0019] A serving cell may be configured to include one or both of one downlink component carrier (downlink carrier) and one uplink component carrier (uplink carrier). A serving cell may be configured to include one or both of two or more downlink component carriers and two or more uplink component carriers. Downlink component carriers and uplink component carriers are also collectively referred to as component carriers (carriers).

[0020] For example, one resource grid may be provided for each component carrier. Also, one resource grid may be provided for each set of one component carrier and a subcarrier spacing configuration μ. Here, the subcarrier spacing configuration μ is also referred to as numerology. For example, one resource grid may be provided for a set of a certain antenna port p, a certain subcarrier spacing configuration μ, and a certain transmission direction x.

[0021] The resource grid includes N size，μ grid，x N RB sc subcarriers. Here, the resource grid starts from a common resource block N start，μ grid，x . The common resource block N start，μ grid，x is also referred to as a reference point of the resource grid.

[0022] The resource grid includes N subframe，μ symb OFDM symbols.

[0023] Subscript x, which is attached to a parameter related to the resource grid, indicates the transmission direction. For example, subscript x may be used to indicate either a downlink or an uplink.

[0024] N size，μ grid，x This is the offset setting indicated by the parameters provided by the RRC layer (e.g., the parameter CarrierBandwidth). start，μ grid，x This is the bandwidth setting, indicated by parameters provided by the RRC layer (e.g., parameter, OffsetToCarrier). The offset setting and bandwidth setting are settings used to configure the SCS-specific carrier.

[0025] For a given subcarrier spacing μ, the subcarrier spacing (SCS) Δf is given by Δf = 2 μ - It may be 15 kHz. Here, the subcarrier spacing μ may be 0, 1, 2, 3, or 4.

[0026] Figure 2 shows the subcarrier spacing setting μ and the number of OFDM symbols per slot N according to one aspect of this embodiment. slot symb This is an example illustrating the relationship between the cyclic prefix (CP) setting and the subcarrier spacing μ is 2, and the CP setting is normal CP (normal cyclic prefix). slot symb = 14, N frame，μ slot = 40, N subframe，μ slot = 4. Also, in Figure 2B, for example, if the subcarrier spacing setting μ is 2 and the CP setting is extended CP (extended cyclic prefix), then N slot symb = 12, N frame，μ slot = 40, N subframe，μ slot = 4.

[0027] Time unit T c This may be used to represent length in the time domain. Time unit T c is, T c = 1 / (Δf) max ・N f ) is Δf max = 480 kHz. f = 4096. The constant κ is given by κ = Δf max ・N f / (Δf ref N f，ref ) = 64. Δf ref It is 15 kHz. f，ref The answer is 2048.

[0028] The transmission of a signal on the downlink and / or the uplink is of length T. f It may be organized into wireless frames (system frames, frames). f = (Δf max N f / 100)・T s = 10 ms. A wireless frame consists of 10 subframes. The length of a subframe is T. sf = (Δf max N f / 1000)・T s = 1 ms. The number of OFDM symbols per subframe is N. subframe，μ symb = N slot symb N subframe，μ slot That is the case.

[0029] An OFDM symbol is a time-domain unit of a communication scheme. For example, an OFDM symbol may be a time-domain unit of CP-OFDM. Alternatively, an OFDM symbol may be a time-domain unit of DFT-s-OFDM.

[0030] A slot may consist of multiple OFDM symbols, for example, N consecutive symbols. slot symbOne slot may be composed of multiple OFDM symbols. For example, in a normal CP setting, N slot symb = 14 is also acceptable. Also, in the settings of the extended CP, N slot symb It can also be 12.

[0031] For a certain subcarrier interval setting μ, the number of slots and their indices within the subframe may be given. For example, slot index n μ s In the subframe, the range is from 0 to N subframe，μ slot The values ​​may be given in ascending order as integers in the range of -1. For setting the subcarrier interval μ, the number of slots and their indices in the wireless frame may be given. Also, slot index n μ s，f In wireless frames, the range is 0 to N frame，μ slot The integer values ​​may also be given in ascending order within the range of -1.

[0032] Figure 3 shows an example of a resource grid configuration method according to one aspect of this embodiment. The horizontal axis of Figure 3 represents the frequency domain. In Figure 3, the subcarrier spacing μ in the component carrier 300. １ An example of the configuration of the resource grid and the subcarrier spacing μ in a certain component carrier. ２ An example of the resource grid configuration is shown. As shown, one or more subcarrier intervals may be set for a given component carrier. In Figure 3, μ １ = μ ２ Assuming that -1, various aspects of this embodiment are μ １ = μ ２ Not limited to the -1 condition.

[0033] The component carrier 300 has a bandwidth with a predetermined width in the frequency domain.

[0034] Point 3000 is an identifier used to identify a particular subcarrier. Point 3000 is also referred to as Point A. The Common Resource Block (CRB) set 3100 sets the subcarrier interval μ. １ This is a set of common resource blocks for [the system / platform].

[0035] Among the common resource block set 3100, the common resource block containing point 3000 (the black block in the common resource block set 3100 in Figure 3) is also referred to as the reference point of the common resource block set 3100. The reference point of the common resource block set 3100 may also be the common resource block with index 0 in the common resource block set 3100.

[0036] The offset 3011 is the offset from the reference point of the common resource block set 3100 to the reference point of the resource grid 3001. The offset 3011 is the setting μ for the subcarrier interval. １ This is indicated by the number of common resource blocks for the resource grid 3001, starting from the reference point of the resource grid 3001. size，μ grid１，x Includes several common resource blocks.

[0037] Offset 3013 is measured from the reference point of resource grid 3001 to the reference point (N) of BWP (BandWidth Part) 3003 of index i1. start，μ BWP，i１ This is the offset up to ).

[0038] The common resource block set 3200 is the setting μ for the subcarrier interval. ２ This is a set of common resource blocks for [the system / platform].

[0039] Among the common resource block set 3200, a common resource block including point 3000 (the solid black block in the common resource block set 3200 in FIG. 3) is also referred to as a reference point of the common resource block set 3200. The reference point of the common resource block set 3200 may be a common resource block with index 0 in the common resource block set 3200.

[0040] Offset 3012 is an offset from the reference point of the common resource block set 3200 to the reference point of the resource grid 3002. The offset 3012 is the subcarrier spacing μ ２ represented by the number of common resource blocks for. The resource grid 3002 starts from the reference point of the resource grid 3002 and includes N size，μ grid２，x common resource blocks.

[0041] Offset 3014 is from the reference point of the resource grid 3002 to the reference point of BWP 3004 with index i2 (N start，μ BWP，i２ ).

[0042] FIG. 4 is a diagram showing a configuration example of the resource grid 3001 according to an aspect of the present embodiment. In the resource grid of FIG. 4, the horizontal axis is an OFDM symbol index l sym , and the vertical axis is a subcarrier index k sc . The resource grid 3001 includes N size，μ grid１，x N RB sc subcarriers, and includes N subframe，μ symb OFDM symbols. In the resource grid, a resource identified by a subcarrier index k sc and an OFDM symbol index l sym is also referred to as a resource element (RE).

[0043] A resource block (RB: Resource Block) includes N RBsc It contains n consecutive subcarriers. A resource block is a collective term for common resource blocks, physical resource blocks (PRBs), and virtual resource blocks (VRBs). Here, N RB sc = 12.

[0044] A resource block unit is a set of resources corresponding to one OFDM symbol in a single resource block. In other words, a resource block unit contains 12 resource elements corresponding to one OFDM symbol in a single resource block.

[0045] For a given subcarrier interval setting μ, common resource blocks are indexed in ascending order from 0 in the frequency domain within a set of common resource blocks. For a given subcarrier interval setting μ, the common resource block at index 0 includes (or coincides with) point 3000. The index n of the common resource block for a given subcarrier interval setting μ μ CRB is, n μ CRB =ceil(k sc / N RB sc The relationship ) is satisfied. Here, k sc A subcarrier with a frequency of =0 is a subcarrier that has the same center frequency as the subcarrier corresponding to point 3000.

[0046] For a given subcarrier interval setting μ, the physical resource blocks are indexed in ascending order from 0 in the frequency domain within a given BWP. The index n of the physical resource block for a given subcarrier interval setting μ. μ PRB is, n μ CRB = n μ PRB +N start，μ BWP，i The following relationship is satisfied. Here, N start，μBWP，i This indicates the baseline for BWP of index i.

[0047] A BWP is defined as a subset of common resource blocks included in a resource grid. The BWP has a reference point N. start，μ BWP，i N starting with size，μ BWP，i It includes a common resource block. The BWP set for a downlink carrier is also called the downlink BWP. The BWP set for an uplink component carrier is also called the uplink BWP.

[0048] An antenna port may be defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. For example, a channel may correspond to a physical channel. A symbol may correspond to an OFDM symbol. A symbol may correspond to a resource block unit. A symbol may correspond to a resource element.

[0049] When the large-scale properties of a channel through which symbols are transmitted at one antenna port can be estimated from the channel through which symbols are transmitted at another antenna port, the two antenna ports are referred to as QCL (Quasi Co-Located). Here, the large-scale properties may include at least the long-range properties of the channel. The large-scale properties may include at least some or all of the delay spread, Doppler spread, Doppler shift, average gain, average delay, and some or all of the spatial Rx parameters. The first and second antenna ports being QCL with respect to beam parameters may mean that the received beam assumed by the receiver for the first antenna port is the same (or corresponds) to the received beam assumed by the receiver for the second antenna port. The first and second antenna ports being QCL with respect to beam parameters means that the transmission beam assumed by the receiver for the first antenna port and the transmission beam assumed by the receiver for the second antenna port are identical (or correspond). Terminal device 1 may assume that the two antenna ports are QCL if the large-scale characteristics of the channel through which symbols are transmitted at one antenna port can be estimated from the channel through which symbols are transmitted at the other antenna port. The two antenna ports being QCL may also mean that the two antenna ports are assumed to be QCL. The large-scale characteristics may also be called QCL parameters.

[0050] The QCL type may be any of type A, type B, type C, or type D.

[0051] Two antenna ports being QCLs of type A may mean that the first large-scale characteristic of the channel through which symbols are transmitted in one antenna port can be estimated from the channel through which symbols are transmitted in the other antenna port. Two antenna ports being QCLs of type B may mean that the second large-scale characteristic of the channel through which symbols are transmitted in one antenna port can be estimated from the channel through which symbols are transmitted in the other antenna port. Two antenna ports being QCLs of type C may mean that the third large-scale characteristic of the channel through which symbols are transmitted in one antenna port can be estimated from the channel through which symbols are transmitted in the other antenna port. Two antenna ports being QCLs of type D may mean that the fourth large-scale characteristic of the channel through which symbols are transmitted in one antenna port can be estimated from the channel through which symbols are transmitted in the other antenna port. The first large-scale characteristic may include all of the following: Doppler shift, Doppler spread, mean delay, and delay spread. The second large-scale characteristic may include the Doppler shift and the entire Doppler spread. The third large-scale characteristic may include the Doppler shift and the entire mean delay. The fourth large-scale characteristic may include spatial reception parameters (spatial direction information, beam information). The antenna port for DMRS may be a DMRS port. The antenna port for PTRS may be a PTRS port. The antenna port associated with PTRS may be a PTRS port. The antenna port for SRS may be an SRS port. The antenna port for DMRS may be a DMRS port. The antenna port associated with DMRS may be a DMRS port.

[0052] Carrier aggregation may involve communication using multiple aggregated serving cells. It may also involve communication using multiple aggregated component carriers. Furthermore, it may involve communication using multiple aggregated downlink component carriers. Finally, it may involve communication using multiple aggregated uplink component carriers.

[0053] Figure 5 is a schematic block diagram showing an example of the configuration of a base station device 3 according to one aspect of this embodiment. As shown in Figure 5, the base station device 3 includes at least a part or all of a wireless transceiver unit (physical layer processing unit) 30 and / or a higher layer processing unit 34. The wireless transceiver unit 30 includes at least a part or all of an antenna unit 31, an RF (Radio Frequency) unit 32, and a baseband unit 33. The higher layer processing unit 34 includes at least a part or all of a media access control layer processing unit 35 and a radio resource control (RRC) layer processing unit 36.

[0054] The wireless transmitting / receiving unit 30 includes at least part or all of the wireless transmitting unit 30a and the wireless receiving unit 30b. Here, the device configuration of the baseband unit included in the wireless transmitting unit 30a and the baseband unit included in the wireless receiving unit 30b may be the same or different. Also, the device configuration of the RF unit included in the wireless transmitting unit 30a and the RF unit included in the wireless receiving unit 30b may be the same or different. Furthermore, the device configuration of the antenna unit included in the wireless transmitting unit 30a and the antenna unit included in the wireless receiving unit 30b may be the same or different.

[0055] For example, the wireless transmission unit 30a may generate and transmit a PDSCH baseband signal. For example, the wireless transmission unit 30a may generate and transmit a PDCCH baseband signal. For example, the wireless transmission unit 30a may generate and transmit a PBCH baseband signal. For example, the wireless transmission unit 30a may generate and transmit a synchronization signal baseband signal. For example, the wireless transmission unit 30a may generate and transmit a PDSCH DMRS baseband signal. For example, the wireless transmission unit 30a may generate and transmit a PDCCH DMRS baseband signal. For example, the wireless transmission unit 30a may generate and transmit a CSI-RS baseband signal. For example, the wireless transmission unit 30a may generate and transmit a DL PTRS baseband signal.

[0056] For example, the wireless receiver 30b may receive PRACH. For example, the wireless receiver 30b may receive and demodulate PUCCH. The wireless receiver 30b may receive and demodulate PUSCH. For example, the wireless receiver 30b may receive PUCCH DMRS. For example, the wireless receiver 30b may receive PUSCH DMRS. For example, the wireless receiver 30b may receive UL PTRS. For example, the wireless receiver 30b may receive SRS.

[0057] The upper layer processing unit 34 outputs downlink data (transport blocks) to the wireless transceiver unit 30 (or wireless transmission unit 30a). The upper layer processing unit 34 performs processing at the MAC (Medium Access Control) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the RRC layer.

[0058] The media access control layer processing unit 35, which is part of the upper layer processing unit 34, performs MAC layer processing.

[0059] The wireless resource control layer processing unit 36, located in the upper layer processing unit 34, performs RRC layer processing. The wireless resource control layer processing unit 36 ​​manages various setting information / parameters (RRC parameters) of the terminal device 1. The wireless resource control layer processing unit 36 ​​sets parameters based on RRC messages received from the terminal device 1. For example, setting upper layer parameters may be done by setting parameters based on received RRC messages. For example, receiving upper layer parameters may be done by setting parameters based on received RRC messages.

[0060] The wireless transceiver 30 (or wireless transmission unit 30a) performs processing such as modulation and encoding. The wireless transceiver 30 (or wireless transmission unit 30a) generates a physical signal by modulating, encoding, and generating a baseband signal (converting to a time-continuous signal) downlink data, and transmits it to the terminal device 1. The wireless transceiver 30 (or wireless transmission unit 30a) may also place the physical signal on a component carrier and transmit it to the terminal device 1.

[0061] The wireless transceiver 30 (or wireless receiver 30b) performs processing such as demodulation and decoding. The wireless transceiver 30 (or wireless receiver 30b) separates, demodulates, and decodes the received physical signal and outputs the decoded information to the upper layer processing unit 34. The wireless transceiver 30 (or wireless receiver 30b) may perform a channel access procedure prior to transmitting the physical signal.

[0062] The RF unit 32 converts the signal received via the antenna unit 31 into a baseband signal (downconvert) by quadrature demodulation, removing unwanted frequency components. The RF unit 32 outputs the processed analog signal to the baseband unit.

[0063] The baseband unit 33 converts the analog signal input from the RF unit 32 into a digital signal. The baseband unit 33 removes the portion corresponding to the Cyclic Prefix (CP) from the converted digital signal, and performs a Fast Fourier Transform (FFT) on the signal from which the CP has been removed to extract the signal in the frequency domain.

[0064] The baseband unit 33 performs an inverse fast Fourier transform (IFFT) on the data to generate an OFDM symbol, adds a CP to the generated OFDM symbol to generate a baseband digital signal, and converts the baseband digital signal into an analog signal. The baseband unit 33 outputs the converted analog signal to the RF unit 32.

[0065] The RF unit 32 removes unwanted frequency components from the analog signal input from the baseband unit 33 using a low-pass filter, upconverts the analog signal to the carrier frequency, and transmits it via the antenna unit 31. The RF unit 32 may also have a function to control the transmission power. The RF unit 32 is also referred to as the transmission power control unit.

[0066] One or more serving cells (or component carriers, downlink component carriers, uplink component carriers) may be configured for terminal device 1.

[0067] Each serving cell configured for terminal device 1 may be a PCell (Primary cell), a PSCell (Primary SCG cell), or a SCell (Secondary Cell).

[0068] A PCell is a serving cell included in an MCG (Master Cell Group). A PCell is a cell (a cell that has performed the initial connection establishment procedure or the connection re-establishment procedure) by terminal device 1.

[0069] PSCell is a serving cell included in SCG (Secondary Cell Group). PSCell is a serving cell that is randomly accessed by terminal device 1.

[0070] SCell may be included in either MCG or SCG.

[0071] A serving cell group (cell group) is a designation that includes at least an MCG and an SCG. A serving cell group may include one or more serving cells (or component carriers). One or more serving cells (or component carriers) included in a serving cell group may be operated by carrier aggregation.

[0072] One or more downlink BWPs may be configured for each serving cell (or downlink component carrier). One or more uplink BWPs may be configured for each serving cell (or uplink component carrier).

[0073] Of the one or more downlink BWPs configured for a serving cell (or downlink component carrier), one downlink BWP may be set as the active downlink BWP (or one downlink BWP may be activated). Of the one or more uplink BWPs configured for a serving cell (or uplink component carrier), one uplink BWP may be set as the active uplink BWP (or one uplink BWP may be activated).

[0074] PDSCH, PDCCH, and CSI-RS may be received on the active downlink BWP. Terminal device 1 may attempt to receive PDSCH, PDCCH, and CSI-RS on the active downlink BWP. PUCCH and PUSCH may be transmitted on the active uplink BWP. Terminal device 1 may transmit PUCCH and PUSCH on the active uplink BWP. The active downlink BWP and active uplink BWP are collectively referred to as active BWP.

[0075] PDSCH, PDCCH, and CSI-RS do not need to be received in downlink BWPs other than active downlink BWPs (inactive downlink BWPs). Terminal device 1 does not need to attempt to receive PDSCH, PDCCH, and CSI-RS in downlink BWPs that are not active downlink BWPs. PUCCH and PUSCH do not need to be transmitted in uplink BWPs that are not active uplink BWPs (inactive uplink BWPs). Terminal device 1 does not need to transmit PUCCH and PUSCH in uplink BWPs that are not active uplink BWPs. Inactive downlink BWPs and inactive uplink BWPs are collectively referred to as inactive BWPs.

[0076] Downlink BWP switching is a procedure for deactivating one of the active downlink BWPs of a serving cell and activating one of the inactive downlink BWPs of that serving cell. Downlink BWP switching may be controlled by a BWP field included in the downlink control information. Downlink BWP switching may also be controlled based on parameters of a higher layer.

[0077] Uplink BWP switching is used to deactivate one active uplink BWP and activate one of the inactive uplink BWPs that is not the active one. Uplink BWP switching may be controlled by a BWP field included in the downlink control information. Uplink BWP switching may also be controlled based on higher-level parameters.

[0078] Of the one or more downlink BWPs set for a serving cell, two or more do not have to be set as active downlink BWPs. For a serving cell, one downlink BWP may be active at any given time.

[0079] Of the one or more uplink BWPs set for a serving cell, two or more uplink BWPs do not need to be set as active uplink BWPs. For a serving cell, one uplink BWP may be active at a given time.

[0080] Figure 6 is a schematic block diagram showing an example of the configuration of a terminal device 1 according to one aspect of this embodiment. As shown in Figure 6, the terminal device 1 includes at least one or all of a wireless transceiver unit (physical layer processing unit) 10 and a higher layer processing unit 14. The wireless transceiver unit 10 includes at least part or all of an antenna unit 11, an RF unit 12, and a baseband unit 13. The higher layer processing unit 14 includes at least part or all of a media access control layer processing unit 15 and a wireless resource control layer processing unit 16.

[0081] The wireless transmitting / receiving unit 10 includes at least part or all of the wireless transmitting unit 10a and the wireless receiving unit 10b. Here, the device configuration of the baseband unit 13 included in the wireless transmitting unit 10a and the baseband unit 13 included in the wireless receiving unit 10b may be the same or different. Also, the device configuration of the RF unit 12 included in the wireless transmitting unit 10a and the RF unit 12 included in the wireless receiving unit 10b may be the same or different. Furthermore, the device configuration of the antenna unit 11 included in the wireless transmitting unit 10a and the antenna unit 11 included in the wireless receiving unit 10b may be the same or different.

[0082] For example, the wireless transmitter 10a may generate and transmit a PRACH baseband signal. For example, the wireless transmitter 10a may generate and transmit a PUCCH baseband signal. The wireless transmitter 10a may generate and transmit a PUSCH baseband signal. For example, the wireless transmitter 10a may generate and transmit a PUCCH DMRS baseband signal. For example, the wireless transmitter 10a may generate and transmit a PUSCH DMRS baseband signal. For example, the wireless transmitter 10a may generate and transmit a UL PTRS baseband signal. For example, the wireless transmitter 10a may generate and transmit an SRS baseband signal.

[0083] For example, the wireless receiver 10b may receive and demodulate PDSCH. For example, the wireless receiver 10b may receive and demodulate PDCCH. For example, the wireless receiver 10b may receive and demodulate PBCH. For example, the wireless receiver 10b may receive a synchronization signal. For example, the wireless receiver 10b may receive PDSCH DMRS. For example, the wireless receiver 10b may receive PDCCH DMRS. For example, the wireless receiver 10b may receive CSI-RS. For example, the wireless receiver 10b may receive DL PTRS.

[0084] The upper layer processing unit 14 outputs the uplink data (transport block) to the wireless transceiver unit 10 (or wireless transmission unit 10a). The upper layer processing unit 14 performs processing at the MAC layer, packet data integration protocol layer, wireless link control layer, and RRC layer.

[0085] The media access control layer processing unit 15, which is part of the upper layer processing unit 14, performs MAC layer processing.

[0086] The wireless resource control layer processing unit 16, located in the upper layer processing unit 14, performs RRC layer processing. The wireless resource control layer processing unit 16 manages various setting information / parameters (RRC parameters) of the terminal device 1. The wireless resource control layer processing unit 16 sets RRC parameters based on RRC messages received from the base station device 3. For example, setting upper layer parameters may also be done by setting parameters based on received RRC messages. For example, receiving upper layer parameters may also be done by setting parameters based on received RRC messages.

[0087] The wireless transceiver unit 10 (or wireless transmission unit 10a) performs processing such as modulation and encoding. The wireless transceiver unit 10 (or wireless transmission unit 10a) generates a physical signal by modulating, encoding, and generating a baseband signal (converting to a time-continuous signal) uplink data, and transmits it to the base station device 3. The wireless transceiver unit 10 (or wireless transmission unit 10a) may also place the physical signal on a BWP (active uplink BWP) and transmit it to the base station device 3.

[0088] The wireless transceiver 10 (or wireless receiver 10b) performs processing such as demodulation and decoding. The wireless transceiver 10 (or wireless receiver 30b) may receive a physical signal in a BWP (active downlink BWP) of a serving cell. The wireless transceiver 10 (or wireless receiver 10b) separates, demodulates, and decodes the received physical signal, and outputs the decoded information to the upper layer processing unit 14. The wireless transceiver 10 (or wireless receiver 10b) may perform a channel access procedure prior to transmitting the physical signal.

[0089] The RF unit 12 converts the signal received via the antenna unit 11 into a baseband signal by quadrature demodulation (downconvert) and removes unwanted frequency components. The RF unit 12 outputs the processed analog signal to the baseband unit 13.

[0090] The baseband unit 13 converts the analog signal input from the RF unit 12 into a digital signal. The baseband unit 13 removes the portion corresponding to the Cyclic Prefix (CP) from the converted digital signal, and performs a Fast Fourier Transform (FFT) on the signal from which the CP has been removed to extract the signal in the frequency domain.

[0091] The baseband unit 13 performs an inverse fast Fourier transform (IFFT) on the uplink data to generate an OFDM symbol, adds a CP to the generated OFDM symbol to generate a baseband digital signal, and converts the baseband digital signal into an analog signal. The baseband unit 13 outputs the converted analog signal to the RF unit 12.

[0092] The RF unit 12 uses a low-pass filter to remove unwanted frequency components from the analog signal input from the baseband unit 13, upconverts the analog signal to the carrier frequency, and transmits it via the antenna unit 11. The RF unit 12 may also have a function to control the transmission power. The RF unit 12 is also referred to as the transmission power control unit.

[0093] The following will explain physical signals (signals).

[0094] Physical signals are a collective term for downlink physical channels, downlink physical signals, uplink physical channels, and uplink physical channels. Physical channels are a collective term for downlink physical channels and uplink physical channels. Physical signals are a collective term for downlink physical signals and uplink physical signals. Physical signals may also be called reference signals.

[0095] An uplink physical channel may correspond to a set of resource elements that transmit information generated in the higher layer. An uplink physical channel may also be a physical channel used in an uplink component carrier. An uplink physical channel may be transmitted by terminal device 1. An uplink physical channel may be received by base station device 3. In a wireless communication system according to one aspect of this embodiment, at least some or all of the following uplink physical channels may be used: ・PUCCH (Physical Uplink Control Channel) ・PUSCH (Physical Uplink Shared Channel) ・PRACH (Physical Random Access Channel)

[0096] A PUCCH may be used to transmit uplink control information (UCI). A PUCCH may be transmitted to deliver, transmit, or convey uplink control information. Uplink control information may be mapped onto a PUCCH. Terminal device 1 may transmit a PUCCH on which uplink control information is mapped. Base station device 3 may receive a PUCCH on which uplink control information is mapped.

[0097] Uplink control information (uplink control information bits, uplink control information sequence, uplink control information type) includes at least some or all of the channel state information (CSI), scheduling request (SR), and HARQ-ACK (Hybrid Automatic Repeat request ACKnowledgement) information.

[0098] Channel status information is also referred to as channel status information bits or channel status information sequences. Scheduling requests are also referred to as scheduling request bits or scheduling request sequences. HARQ-ACK information is also referred to as HARQ-ACK information bits or HARQ-ACK information sequences.

[0099] HARQ-ACK information may include at least a HARQ-ACK corresponding to a transport block (TB). A HARQ-ACK may indicate an ACK (acknowledgement) or NACK (negative-acknowledgement) corresponding to a transport block. An ACK may indicate that the transport block has been decoded successfully. A NACK may indicate that the transport block has not been decoded successfully. HARQ-ACK information may include a HARQ-ACK codebook containing one or more HARQ-ACK bits.

[0100] A transport block is a sequence of information bits delivered from a higher layer. Here, the sequence of information bits is also called a bit sequence. Here, the transport block may be delivered from the UL-SCH (UpLink-Shared Channel) of the transport layer.

[0101] The HARQ-ACK for a transport block is sometimes referred to as the HARQ-ACK for a PDSCH. In this case, "HARQ-ACK for a PDSCH" refers to the HARQ-ACK for the transport block included in the PDSCH.

[0102] HARQ-ACK may represent an ACK or NACK corresponding to a single CBG (Code Block Group) contained within a transport block.

[0103] A scheduling request may be used to request UL-SCH resources for a new transmission. The scheduling request bit may be used to indicate either a positive SR or a negative SR. When the scheduling request bit indicates a positive SR, it is also referred to as "a positive SR is transmitted." A positive SR may indicate that terminal device 1 is requesting UL-SCH resources for a new transmission. A positive SR may indicate that the scheduling request is triggered by a higher layer. A positive SR may be transmitted when the scheduling request is instructed by a higher layer. When the scheduling request bit indicates a negative SR, it is also referred to as "a negative SR is transmitted." A negative SR may indicate that terminal device 1 is not requesting UL-SCH resources for a new transmission. A negative SR may indicate that the scheduling request is not triggered by a higher layer. A negative SR may be transmitted when the scheduling request is not instructed by a higher layer.

[0104] Channel status information may include at least some or all of the Channel Quality Indicator (CQI), Precoder Matrix Indicator (PMI), and Rank Indicator (RI). CQI is an indicator related to the quality of the propagation path (e.g., propagation intensity) or the quality of the physical channel, PMI is an indicator related to the precoder, and RI is an indicator related to the transmit rank (or transmit layer number).

[0105] Channel status information is an index of the reception status of at least the physical signal (e.g., CSI-RS) used for channel measurement. The value of the channel status information may be determined by the terminal device 1 based on the reception status assumed by at least the physical signal used for channel measurement. Channel measurement may include interference measurement.

[0106] PUCCH may support the PUCCH format. PUCCH may be a set of resource elements used to transmit the PUCCH format. PUCCH may contain the PUCCH format. PUCCH may be transmitted with a certain PUCCH format. The PUCCH format may be interpreted as a format of information. Alternatively, the PUCCH format may be interpreted as a set of information set into a certain format of information.

[0107] A PUSCH may be used to transmit either or both a transport block and / or uplink control information. The transport block may be placed in the PUSCH. Transport blocks delivered by UL-SCH may be placed in the PUSCH. Uplink control information may be placed in the PUSCH. Terminal device 1 may transmit a PUSCH containing either or both a transport block and / or uplink control information. Base station device 3 may receive a PUSCH containing either or both a transport block and / or uplink control information.

[0108] PRACH may be transmitted to transmit the random access preamble. Terminal device 1 may transmit PRACH. Base station device 3 may receive PRACH. PRACH sequence x u，v (n) is x u，v (n) = x u (mod(n+C) v , L RA Defined by )), where x u It belongs to the ZC (Zadoff Chu) series. Also, x u is x u =exp(-jπui(i+1) / L RA ) may be defined by j, where j is the imaginary unit, and π is the ratio of a circle's circumference to its diameter. v This corresponds to the cyclic shift of the PRACH series. Also, L RA This corresponds to the length of the PRACH sequence. Also, L RAIt is 839 or 139. Also, i is from 0 to L RA It is an integer in the range of -1. Also, u is the series index for the PRACH series.

[0109] For each PRACH opportunity, 64 random access preambles are defined. The random access preamble is a cyclic shift C of the PRACH sequence. v and are identified based on the series index u for the PRACH series. Each of the identified 64 random access preambles may be indexed.

[0110] Uplink physical signals may correspond to a set of resource elements. Uplink physical signals do not necessarily have to be used to transmit information generated in the upper layer. However, uplink physical signals may be used to transmit information generated in the physical layer. Uplink physical signals may also be physical signals used in the uplink component carrier. Terminal device 1 may transmit uplink physical signals. Base station device 3 may receive uplink physical signals. In a wireless communication system according to one aspect of this embodiment, at least some or all of the following uplink physical signals may be used: ・UL DMRS (UpLink Demodulation Reference Signal) ・SRS (Sounding Reference Signal) ・UL PTRS (UpLink Phase Tracking Reference Signal)

[0111] UL DMRS is a general term for DMRS for PUSCH and DMRS for PUCCH.

[0112] The set of antenna ports for a DMRS for a PUSCH (DMRS associated with a PUSCH, DMRS included in a PUSCH, and DMRS corresponding to a PUSCH) may be given based on the set of antenna ports for the PUSCH. For example, the set of antenna ports for a DMRS for a PUSCH may be the same as the set of antenna ports for the PUSCH.

[0113] The transmission of a PUSCH and the transmission of a DMRS for that PUSCH may be represented (or scheduled) by a single DCI format. The PUSCH and the DMRS for that PUSCH may be collectively referred to as PUSCH. Sending a PUSCH may be equivalent to sending a PUSCH and a DMRS for that PUSCH.

[0114] The propagation path of a pusher may be estimated from the DMRS for that pusher.

[0115] The set of antenna ports for DMRS for PUCCH (DMRS related to PUCCH, DMRS included in PUCCH, DMRS corresponding to PUCCH) may be the same as the set of antenna ports for PUCCH.

[0116] The transmission of a PUCCH and the transmission of a DMRS for the PUCCH may be represented (or triggered) by a single DCI format. The resource element mapping of the PUCCH and the resource element mapping of the DMRS for the PUCCH, or both, may be given by a single PUCCH format. The PUCCH and the DMRS for the PUCCH may be collectively referred to as PUCCH. Transmission of a PUCCH may be equivalent to transmission of both the PUCCH and the DMRS for the PUCCH.

[0117] The propagation path of PUCCH may be estimated from the DMRS for the PUCCH.

[0118] A downlink physical channel may correspond to a set of resource elements that transmit information generated in the upper layer. A downlink physical channel may also be a physical channel used in a downlink component carrier. Base station device 3 may transmit a downlink physical channel. Terminal device 1 may receive a downlink physical channel. In a wireless communication system according to one aspect of this embodiment, at least some or all of the following downlink physical channels may be used: ・PBCH (Physical Broadcast Channel) ・PDCCH (Physical Downlink Control Channel) ・PDSCH (Physical Downlink Shared Channel)

[0119] A PBCH may be transmitted to transmit either or both of the MIB (Master Information Block) and / or physical layer control information. Here, physical layer control information is information generated at the physical layer. The MIB is a set of parameters placed in the BCCH (Broadcast Control Channel), which is a logical channel of the MAC layer. The BCCH is placed in the BCH, which is a channel of the transport layer. The BCH may be placed (mapped) in the PBCH. Terminal device 1 may receive a PBCH containing either or both of the MIB and / or physical layer control information. Base station device 3 may transmit a PBCH containing either or both of the MIB and / or physical layer control information.

[0120] For example, the physical layer control information may consist of 8 bits. The physical layer control information may include at least some or all of the following 0A to 0D: 0A) Wireless frame bits 0B) Half wireless frame (half system frame, half frame) bits 0C) SS / PBCH block index bits 0D) Subcarrier offset bits

[0121] The wireless frame bits are used to indicate the wireless frame transmitted by the PBCH (the wireless frame containing the slot from which the PBCH is transmitted). The wireless frame bits consist of four bits. The wireless frame bits may consist of four bits from a 10-bit wireless frame indicator. For example, the wireless frame indicator may be used to identify wireless frames from index 0 to index 1023.

[0122] The half-radio frame bit is used to indicate whether the PBCH is transmitted in the first five subframes or the last five subframes of the radio frame. Here, the half-radio frame may consist of five subframes. Alternatively, the half-radio frame may consist of the first five subframes of the ten subframes included in the radio frame. Alternatively, the half-radio frame may consist of the last five subframes of the ten subframes included in the radio frame.

[0123] The SS / PBCH block index bits are used to indicate the SS / PBCH block index. The SS / PBCH block index bits consist of three bits. The SS / PBCH block index bits may consist of three bits from a six-bit SS / PBCH block index indicator. The SS / PBCH block index indicator may be used to identify SS / PBCH blocks from index 0 to index 63.

[0124] The subcarrier offset bit is used to indicate the subcarrier offset. The subcarrier offset may be used to indicate the difference between the leading subcarrier to which the PBCH is mapped and the leading subcarrier to which the control resource set at index 0 is mapped.

[0125] A PDCCH may be transmitted to transmit Downlink Control Information (DCI). Downlink Control Information may be placed on the PDCCH. Terminal device 1 may receive a PDCCH containing Downlink Control Information. Base station device 3 may transmit a PDCCH containing Downlink Control Information.

[0126] Downlink control information may be transmitted in DCI format. The DCI format may be interpreted as the format of the downlink control information. Alternatively, the DCI format may be interpreted as a set of downlink control information set in a specific downlink control information format.

[0127] DCI formats 0_0, 0_1, 1_0, and 1_1 are DCI formats. Uplink DCI formats are a collective term for DCI formats 0_0 and 0_1. Downlink DCI formats are a collective term for DCI formats 1_0 and 1_1.

[0128] DCI format 0_0 is used at least for scheduling PUSCHs placed in a given cell. DCI format 0_0 consists of at least some or all of the fields 1A to 1E: 1A) Identifier field for DCI formats 1B) Frequency domain resource assignment field 1C) Time domain resource assignment field 1D) Frequency hopping flag field 1E) MCS field (Modulation and Coding Scheme field)

[0129] The DCI format-specific field may indicate whether the DCI format containing the DCI format-specific field is an uplink DCI format or a downlink DCI format. In other words, the DCI format-specific field may be included in both the uplink DCI format and the downlink DCI format. Here, the DCI format-specific field included in DCI format 0_0 may indicate 0.

[0130] The frequency domain resource allocation field included in DCI format 0_0 may be used to indicate the allocation of frequency resources for PUSCH.

[0131] The time domain resource allocation field included in DCI format 0_0 may be used to indicate the allocation of time resources for PUSCH.

[0132] The frequency hopping flag field may be used to indicate whether or not frequency hopping is applied to PUSCH.

[0133] The MCS field included in DCI format 0_0 may be used to indicate at least one or both of the modulation scheme for the PUSCH and the target coding rate. The target coding rate may be the target coding rate for the transport block to be placed in the PUSCH. The size of the transport block (TBS) to be placed in the PUSCH may be determined based on one or both of the target coding rate and the modulation scheme for the PUSCH.

[0134] DCI format 0_0 does not need to include fields used in CSI requests.

[0135] DCI format 0_0 does not have to include a carrier indicator field. In other words, the serving cell to which the uplink component carrier on which a PUSCH scheduled by DCI format 0_0 is located belongs may be the same as the serving cell of the uplink component carrier on which a PDCCH containing DCI format 0_0 is located. Terminal device 1 may recognize that a PUSCH scheduled by DCI format 0_0 is located on the uplink component carrier of a serving cell based on the detection of DCI format 0_0 on a downlink component carrier of that serving cell.

[0136] DCI format 0_0 does not necessarily have to include a BWP field (BWP instruction field). Here, DCI format 0_0 may be a DCI format that schedules a PUSCH without changing the active uplink BWP. Terminal device 1 may recognize that it will transmit the PUSCH without switching the active uplink BWP based on detecting DCI format 0_0 used for scheduling the PUSCH.

[0137] DCI format 0_1 ​​is used at least for scheduling PUSCHs placed in a cell. DCI format 0_1 ​​consists of at least some or all of the fields 2A through 2H: 2A) DCI format specific field 2B) Frequency domain resource allocation field 2C) Uplink time domain resource allocation field 2D) Frequency hopping flag field 2E) MCS field 2F) CSI request field 2G) BWP field 2H) Carrier indicator field

[0138] The DCI format specific field included in DCI format 0_1 ​​may indicate 0.

[0139] The frequency domain resource allocation field included in DCI format 0_1 ​​may be used to indicate the allocation of frequency resources for PUSCH.

[0140] The time domain resource allocation field included in DCI format 0_1 ​​may be used to indicate the allocation of time resources for PUSCH.

[0141] The MCS field included in DCI format 0_1 ​​may be used to indicate at least part or all of the modulation scheme and / or target coding rate for PUSCH.

[0142] The BWP field of DCI format 0_1 ​​may be used to indicate the uplink BWP on which the PUSCH scheduled by DCI format 0_1 ​​is located. In other words, DCI format 0_1 ​​may involve changes to the active uplink BWP. Terminal device 1 may recognize the uplink BWP on which the PUSCH is located based on detecting the DCI format 0_1 ​​used for scheduling the PUSCH.

[0143] DCI format 0_1, which does not include the BWP field, may be a DCI format that schedules a PUSCH without changing the active uplink BWP. Terminal device 1 may recognize that it will transmit the PUSCH without switching the active uplink BWP, based on the detection of DCI format D0_1, which is used for scheduling a PUSCH and does not include the BWP field.

[0144] If DCI format 0_1 ​​includes a BWP field, but terminal device 1 does not support the BWP switching function using DCI format 0_1, the BWP field may be ignored by terminal device 1. In other words, terminal device 1, which does not support the BWP switching function, may recognize that DCI format 0_1 ​​is used for scheduling PUSCH and includes a BWP field, and therefore transmit the PUSCH without switching the active uplink BWP. If terminal device 1 does support the BWP switching function, it may report in the RRC layer's function information reporting procedure that "terminal device 1 supports the BWP switching function".

[0145] The CSI request field is used to instruct the CSI report.

[0146] If DCI format 0_1 ​​includes a carrier indicator field, the carrier indicator field may be used to indicate the uplink component carrier on which PUSCH is located. If DCI format 0_1 ​​does not include a carrier indicator field, the uplink component carrier on which PUSCH is located may be the same as the uplink component carrier on which PDCCH, which includes DCI format 0_1 ​​used for scheduling PUSCH, is located. If the number of uplink component carriers set on terminal device 1 in a serving cell group is two or more (when uplink carrier aggregation is operated in a serving cell group), the number of bits in the carrier indicator field included in DCI format 0_1 ​​used for scheduling PUSCH located in that serving cell group may be one or more bits (for example, three bits). If the number of uplink component carriers set on terminal device 1 in a serving cell group is 1 (i.e., uplink carrier aggregation is not operated in a serving cell group), the number of bits in the carrier indicator field included in DCI format 0_1 ​​used for scheduling PUSCH placed in that serving cell group may be 0 bits (or the carrier indicator field may not be included in DCI format 0_1 ​​used for scheduling PUSCH placed in that serving cell group).

[0147] DCI format 1_0 is used at least for scheduling PDSCHs located in a given cell. DCI format 1_0 consists of at least some or all of 3A through 3F: 3A) DCI format specific field; 3B) Frequency domain resource allocation field; 3C) Time domain resource allocation field; 3D) MCS field; 3E) PDSCH to HARQ feedback timing indicator field; 3F) PUCCH resource indicator field.

[0148] The DCI format specific field included in DCI format 1_0 may indicate 1.

[0149] The frequency domain resource allocation field included in DCI format 1_0 may be used to indicate the allocation of frequency resources for PDSCH.

[0150] The time domain resource allocation field included in DCI format 1_0 may be used to indicate the allocation of time resources for PDSCH.

[0151] The MCS field included in DCI format 1_0 may be used to indicate at least one or both of the modulation scheme and / or target coding rate for the PDSCH. The target coding rate may be the target coding rate for the transport blocks to be placed in the PDSCH. The size of the transport blocks (TBS) to be placed in the PDSCH may be determined based on one or both of the target coding rate and / or the modulation scheme for the PDSCH.

[0152] The PDSCH_HARQ feedback timing indicator field may be used to indicate an offset from the slot containing the last OFDM symbol of the PDSCH to the slot containing the first OFDM symbol of the PUCCH.

[0153] The PUCCH resource reference field may be a field that indicates the index of one or more PUCCH resources included in the PUCCH resource set. The PUCCH resource set may contain one or more PUCCH resources.

[0154] DCI format 1_0 does not have to include a carrier indicator field. In other words, the downlink component carrier on which a PDSCH scheduled by DCI format 1_0 is located may be the same as the downlink component carrier on which a PDCCH containing DCI format 1_0 is located. Terminal device 1 may recognize that a PDSCH scheduled by DCI format 1_0 is located on a downlink component carrier based on the detection of DCI format 1_0 on that downlink component carrier.

[0155] DCI format 1_0 does not necessarily have to include a BWP field. Here, DCI format 1_0 may be a DCI format that schedules a PDSCH without changing the active downlink BWP. Terminal device 1 may recognize that it will receive the PDSCH without switching the active downlink BWP based on detecting DCI format 1_0 used for scheduling the PDSCH.

[0156] DCI format 1_1 is used for scheduling PDSCHs located in a cell. DCI format 1_1 consists of at least some or all of 4A to 4I: 4A) DCI format specific field 4B) Frequency domain resource allocation field 4C) Time domain resource allocation field 4E) MCS field 4F) PDSCH_HARQ feedback timing instruction field 4G) PUCCH resource instruction field 4H) BWP field 4I) Carrier indicator field

[0157] The DCI format specific field included in DCI format 1_1 may indicate 1.

[0158] The frequency domain resource allocation field included in DCI format 1_1 may be used to indicate the allocation of frequency resources for PDSCH.

[0159] The time domain resource allocation field included in DCI format 1_1 may be used to indicate the allocation of time resources for PDSCH.

[0160] The MCS field included in DCI format 1_1 may be used to indicate at least one or both of the modulation scheme and the target coding rate for PDSCH.

[0161] If DCI format 1_1 includes a PDSCH_HARQ feedback timing indicator field, this field may be used to indicate at least the offset from the slot containing the last OFDM symbol of the PDSCH to the slot containing the first OFDM symbol of the PUCCH. If DCI format 1_1 does not include a PDSCH_HARQ feedback timing indicator field, the offset from the slot containing the last OFDM symbol of the PDSCH to the slot containing the first OFDM symbol of the PUCCH may be determined by a parameter in a higher layer.

[0162] The PUCCH resource reference field may be a field that indicates the index of one or more PUCCH resources included in the PUCCH resource set.

[0163] The BWP field of DCI format 1_1 may be used to indicate the downlink BWP on which the PDSCH scheduled by DCI format 1_1 is located. In other words, DCI format 1_1 may involve changes to the active downlink BWP. Terminal device 1 may recognize the downlink BWP on which the PDSCH is located based on detecting the DCI format 1_1 used for scheduling the PDSCH.

[0164] A DCI format 1_1 that does not include a BWP field may be a DCI format that schedules a PDSCH without changing the active downlink BWP. The terminal device 1 may recognize that it will receive the PDSCH without switching the active downlink BWP based on detecting a DCI format 1_1 that is used for scheduling a PDSCH and does not include a BWP field.

[0165] If DCI format 1_1 includes a BWP field, but terminal device 1 does not support the BWP switching function according to DCI format 1_1, the BWP field may be ignored by terminal device 1. In other words, terminal device 1, which does not support the BWP switching function, may recognize that it is a DCI format 1_1 used for scheduling PDSCHs and that includes a BWP field, and may receive the PDSCH without switching the active downlink BWP. If terminal device 1 does support the BWP switching function, it may report in the RRC layer's function information reporting procedure that "terminal device 1 supports the BWP switching function".

[0166] If DCI format 1_1 includes a carrier indicator field, the carrier indicator field may be used to indicate the downlink component carrier on which the PDSCH is located. If DCI format 1_1 does not include a carrier indicator field, the downlink component carrier on which the PDSCH is located may be the same as the downlink component carrier on which the PDCCH is located, which includes DCI format 1_1 used for scheduling the PDSCH. If the number of downlink component carriers set on terminal device 1 in a serving cell group is two or more (when downlink carrier aggregation is operated in a serving cell group), the number of bits in the carrier indicator field included in DCI format 1_1 used for scheduling the PDSCHs located in that serving cell group may be one or more bits (for example, three bits). If the number of downlink component carriers set on terminal device 1 in a serving cell group is 1 (i.e., downlink carrier aggregation is not operated in a serving cell group), the number of bits in the carrier indicator field included in DCI format 1_1 used for scheduling PDSCHs placed in that serving cell group may be 0 bits (or the carrier indicator field may not be included in DCI format 1_1 used for scheduling PDSCHs placed in that serving cell group).

[0167] PDSCH may be transmitted to transmit a transport block. PDSCH may be used to transmit a transport block delivered from DL-SCH. PDSCH may be used to transmit a transport block. A transport block may be placed on the PDSCH. A transport block corresponding to DL-SCH may be placed on the PDSCH. Base station device 3 may transmit a PDSCH. Terminal device 1 may receive a PDSCH.

[0168] Downlink physical signals may correspond to a set of resource elements. Downlink physical signals do not necessarily carry information generated in higher layers. Downlink physical signals may also be physical signals used in downlink component carriers. Downlink physical signals may be transmitted by base station device 3. Downlink physical signals may be transmitted by terminal device 1. In a wireless communication system according to one aspect of this embodiment, at least some or all of the following downlink physical signals may be used: ・Synchronization signal (SS) ・Downlink DeModulation Reference Signal (DL DMRS) ・Channel State Information-Reference Signal (CSI-RS) ・Downlink Phase Tracking Reference Signal (DL PTRS)

[0169] The synchronization signal may be used to synchronize the terminal device 1 in either the frequency domain or the time domain of the downlink, or both. The synchronization signal is a general term for PSS (Primary Synchronization Signal) and SSS (Secondary Synchronization Signal).

[0170] Figure 7 shows an example of the configuration of an SS / PBCH block according to one aspect of this embodiment. In Figure 7, the horizontal axis is the time axis (OFDM symbol index l sym The vertical axis represents the frequency domain. Block 700 shows a set of resource elements for PSS. Block 720 shows a set of resource elements for SSS. Four blocks (blocks 710, 711, 712, and 713) show sets of resource elements for PBCH and DMRS for the PBCH (DMRS associated with the PBCH, DMRS contained in the PBCH, and DMRS corresponding to the PBCH).

[0171] As shown in Figure 7, the SS / PBCH block includes PSS, SSS, and PBCH. The SS / PBCH block also includes four consecutive OFDM symbols. The SS / PBCH block contains 240 subcarriers. PSS is placed in subcarriers 57 through 183 of the first OFDM symbol. SSS is placed in subcarriers 57 through 183 of the third OFDM symbol. Subcarriers 1 through 56 of the first OFDM symbol may be set to zero. Subcarriers 184 through 240 of the first OFDM symbol may be set to zero. Subcarriers 49 through 56 of the third OFDM symbol may be set to zero. Subcarriers 184 through 192 of the third OFDM symbol may be set to zero. PBCH is placed in subcarriers 1 through 240 of the second OFDM symbol, where DMRS for PBCH are not placed. PBCH is placed in the subcarriers 1 through 48 of the third OFDM symbol, where a DMRS for PBCH is not placed. PBCH is placed in the subcarriers 193 through 240 of the third OFDM symbol, where a DMRS for PBCH is not placed. PBCH is placed in the subcarriers 1 through 240 of the fourth OFDM symbol, where a DMRS for PBCH is not placed.

[0172] The antenna ports for PSS, SSS, PBCH, and DMRS for PBCH may be the same.

[0173] The PBCH whose symbol is transmitted at a given antenna port may be estimated by a DMRS for the PBCH located in the slot to which the PBCH is mapped, and which is included in the SS / PBCH block containing the PBCH.

[0174] DL DMRS is a general term for DMRS for PBCH, DMRS for PDSCH, and DMRS for PDCCH.

[0175] The set of antenna ports for a DMRS for a PDSCH (DMRS associated with a PDSCH, DMRS included in a PDSCH, DMRS corresponding to a PDSCH) may be given based on the set of antenna ports for the PDSCH. In other words, the set of antenna ports for a DMRS for a PDSCH may be the same as the set of antenna ports for the PDSCH.

[0176] The transmission of a PDSCH and the transmission of a DMRS for the PDSCH may be represented (or scheduled) by a single DCI format. The PDSCH and the DMRS for the PDSCH may be collectively referred to as the PDSCH. Transmitting a PDSCH may be equivalent to transmitting the PDSCH and the DMRS for the PDSCH.

[0177] The propagation path of a PDSCH may be estimated from the DMRS for that PDSCH. If the set of resource elements on which a PDSCH symbol is transmitted and the set of resource elements on which the DMRS symbol for that PDSCH is transmitted belong to the same Precoding Resource Group (PRG), then the PDSCH on which the PDSCH symbol is transmitted at a given antenna port may be estimated from the DMRS for that PDSCH.

[0178] The antenna port for the DMRS for PDCCH (DMRS associated with PDCCH, DMRS included in PDCCH, DMRS corresponding to PDCCH) may be the same as the antenna port for PDCCH.

[0179] A PDCCH may be inferred from the DMRS for that PDCCH. That is, the propagation path of a PDCCH may be inferred from the DMRS for that PDCCH. If the same precoder is applied (or assumed to be applied) to the set of resource elements on which the symbol of a PDCCH is transmitted and to the set of resource elements on which the symbol of the DMRS for that PDCCH is transmitted, then the PDCCH on which the symbol of that PDCCH is transmitted at a given antenna port may be inferred from the DMRS for that PDCCH.

[0180] BCH (Broadcast Channel), UL-SCH (Uplink-Shared Channel), and DL-SCH (Downlink-Shared Channel) are transport channels. Transport channels define the relationship between physical layer channels and MAC layer channels (also called logical channels).

[0181] The BCH in the transport layer is mapped to the PBCH in the physical layer. That is, transport blocks passing through the BCH in the transport layer are delivered to the PBCH in the physical layer. Also, the UL-SCH in the transport layer is mapped to the PUSCH in the physical layer. That is, transport blocks passing through the UL-SCH in the transport layer are delivered to the PUSCH in the physical layer. Furthermore, the DL-SCH in the transport layer is mapped to the PDSCH in the physical layer. That is, transport blocks passing through the DL-SCH in the transport layer are delivered to the PDSCH in the physical layer.

[0182] Each serving cell may be provided with one UL-SCH and one DL-SCH. BCH may be provided to the PCell. BCH does not have to be provided to the PSCell or SCell.

[0183] At the MAC layer, HARQ (Hybrid Automatic Repeat request) control is performed for each transport block.

[0184] BCCH (Broadcast Control Channel), CCCH (Common Control Channel), and DCCH (Dedicated Control Channel) are logical channels. For example, BCCH is an RRC layer channel used to transmit MIB or system information. CCCH (Common Control Channel) may be used to transmit common RRC messages to multiple terminal devices 1. Here, CCCH may be used, for example, for terminal devices 1 that are not RRC connected. DCCH (Dedicated Control Channel) may be used to transmit dedicated RRC messages to terminal devices 1. Here, DCCH may be used, for example, for terminal devices 1 that are RRC connected.

[0185] Terminal device 1 may transmit or receive upper-layer parameters. Terminal device 1 may transmit or receive a message containing upper-layer parameters. The message may be an RRC message or a MAC CE. The upper-layer parameters may be RRC parameters.

[0186] Higher-level parameters common to multiple terminal devices 1 are also referred to as common higher-level parameters. Here, common higher-level parameters may be defined as parameters specific to a serving cell. Here, parameters specific to a serving cell may be parameters common to the terminal devices on which the serving cell is set (for example, terminal devices 1-A, B, C).

[0187] For example, common upper-layer parameters may be included in the RRC message delivered to the BCCH. For example, common upper-layer parameters may be included in the RRC message delivered to the DCCH.

[0188] Among the upper-level parameters, those that differ from common upper-level parameters are also called dedicated upper-level parameters. Here, dedicated upper-level parameters can provide dedicated RRC parameters for terminal device 1-A on which a serving cell is set. In other words, dedicated RRC parameters are upper-level parameters that can provide unique settings for each of terminal devices 1-A, B, and C.

[0189] The BCCH of the logical channel is mapped to the BCH or DL-SCH of the transport layer. For example, a transport block containing MIB information is delivered to the BCH of the transport layer. A transport block containing system information that is not an MIB is delivered to the DL-SCH of the transport layer. CCCH is mapped to DL-SCH or UL-SCH. That is, a transport block mapped to CCCH is delivered to DL-SCH or UL-SCH. DCCH is mapped to DL-SCH or UL-SCH. That is, a transport block mapped to DCCH is delivered to DL-SCH or UL-SCH.

[0190] An RRC message contains one or more parameters managed at the RRC layer. These parameters are also referred to as RRC parameters. For example, an RRC message may contain a MIB. It may also contain system information. Furthermore, an RRC message may contain a message corresponding to a CCCH. It may also contain a message corresponding to a DCCH. An RRC message containing a message corresponding to a DCCH is also referred to as an individual RRC message.

[0191] Higher-layer parameters are RRC parameters or parameters included in MAC CE (Medium Access Control Control Element). In other words, higher-layer parameters are a general term for MIBs, system information, messages corresponding to CCCH, messages corresponding to DCCH, and parameters included in MAC CE. Parameters included in MAC CE are sent by MAC CE (Control Element) commands.

[0192] The procedures performed by terminal device 1 include at least some or all of the following 5A to 5C: 5A) Cell search 5B) Random access 5C) Data communication

[0193] Cell search is a procedure used by terminal device 1 to synchronize with a certain cell in the time domain and frequency domain and to detect its physical cell identity. In other words, terminal device 1 may use cell search to synchronize with a certain cell in the time domain and frequency domain and detect its physical cell identity.

[0194] The PSS series is assigned based on at least the physical cell ID. The SSS series is assigned based on at least the physical cell ID.

[0195] SS / PBCH block candidates indicate resources that are permitted (possible, reserved, configured, specified, or potentially) to send SS / PBCH blocks.

[0196] A set of SS / PBCH block candidates in a half-radio frame is also called an SS burst set. An SS burst set is also called a transmission window, SS transmission window, or DRS transmission window (Discovery Reference Signal transmission window). An SS burst set is a general term that includes at least a first SS burst set and a second SS burst set.

[0197] The base station device 3 transmits SS / PBCH blocks of one or more indices at predetermined intervals. The terminal device 1 may detect at least one of the SS / PBCH blocks of the one or more indices and attempt to decode the PBCH contained in the SS / PBCH block.

[0198] A random access (random access procedure) is a procedure that includes at least some or all of messages 1, 2, 3, and 4. A random access procedure may be triggered in response to a request for PRACH transmission via higher-layer parameters or PDCCH order.

[0199] Message 1 is the procedure for sending a PRACH by terminal device 1. Terminal device 1 sends a random access preamble in the PRACH as message 1. Terminal device 1 sends a PRACH in one PRACH opportunity selected from one or more PRACH opportunities, based on at least the index of SS / PBCH block candidates detected based on cell search. Each PRACH opportunity is defined based on at least time-domain and frequency-domain resources.

[0200] Terminal device 1 transmits one random access preamble selected from among the PRACH opportunities corresponding to the index of the SS / PBCH block candidate in which the SS / PBCH block is detected.

[0201] Terminal device 1 may attempt to detect DCI format 1_0 accompanied by a CRC scrambled with RA-RNTI. Message 2 is a procedure for terminal device 1 to attempt to detect DCI format 1_0 accompanied by a CRC (Cyclic Redundancy Check) scrambled with RA-RNTI (Random Access - Radio Network Temporary Identifier). Terminal device 1 attempts to detect a PDCCH containing the DCI format in the resources indicated based on the settings of the control resource set given based on the MIB contained in the PBCH contained in the SS / PBCH block detected based on cell search, and the search area set. Message 2 is also called a Random Access Response (RAR). Terminal device 1 may receive a Random Access Response (or a Random Access Response message) accompanied by a PDCCH / PDSCH as a message.

[0202] Message 3 is a procedure for sending a PUSCH scheduled by a random access response grant contained in DCI format 1_0 detected by the Message 2 procedure. Here, the random access response grant is indicated by the MAC CE contained in the PDSCH scheduled by DCI format 1_0.

[0203] A PUSCH scheduled based on a random access response grant is either message 3 PUSCH or simply PUSCH. Message 3 PUSCH includes a contention resolution identifier (MAC CE). The contention resolution identifier (MAC CE) includes the contention resolution identifier.

[0204] Message 3, PUSCH, is retransmitted using DCI format 0_0 with a scrambled CRC based on TC-RNTI (Temporary Cell - Radio Network Temporary Identifier).

[0205] Message 4 is a procedure to attempt to detect DCI format 1_0 with a CRC scrambled based on either C-RNTI (Cell - Radio Network Temporary Identifier) ​​or TC-RNTI. Terminal device 1 receives a PDSCH scheduled based on the DCI format 1_0. The PDSCH may include a collision resolution ID.

[0206] Data communication is a general term encompassing both downlink communication and uplink communication.

[0207] In data communication, terminal device 1 attempts to detect PDCCH in resources identified based on the control resource set and the search area set (monitors PDCCH, monitors PDCCH).

[0208] A control resource set (CORESET) is a set of resources consisting of a predetermined number of resource blocks and a predetermined number of OFDM symbols. In the frequency domain, a control resource set may consist of continuous resources (non-interleaved mapping) or distributed resources (interleaver mapping).

[0209] The set of resource blocks that constitute the control resource set may be indicated by a higher-level parameter. The number of OFDM symbols that constitute the control resource set may also be indicated by a higher-level parameter.

[0210] Terminal device 1 attempts to detect PDCCH in the search area set. Here, attempting to detect PDCCH in the search area set may also mean attempting to detect candidate PDCCH in the search area set, attempting to detect DCI format in the search area set, attempting to detect PDCCH in the control resource set, attempting to detect candidate PDCCH in the control resource set, or attempting to detect DCI format in the control resource set.

[0211] A search space set is defined as a set of candidate PDCCHs. A search space set may be a CSS (Common Search Space) set or a USS (UE-specific Search Space) set. Terminal device 1 attempts to detect candidate PDCCHs in some or all of the following: Type 0 PDCCH common search space set, Type 0a PDCCH common search space set, Type 1 PDCCH common search space set, Type 2 PDCCH common search space set, Type 3 PDCCH common search space set, and / or UE-specific search space set.

[0212] A Type 0 PDCCH common search area set may be used as the common search area set for index 0. A Type 0 PDCCH common search area set may also be the common search area set for index 0.

[0213] The CSS set is a collective term for the Type 0 PDCCH Common Search Region Set, Type 0a PDCCH Common Search Region Set, Type 1 PDCCH Common Search Region Set, Type 2 PDCCH Common Search Region Set, and Type 3 PDCCH Common Search Region Set. The USS set is also called the UE Individual PDCCH Search Region Set.

[0214] A set of search domains is associated with (contains, corresponds to) a set of control resources. The index of the control resource set associated with the search domain set may be indicated by a higher-level parameter.

[0215] For a given set of search regions, some or all of 6A to 6C may be represented by at least the upper layer parameters: 6A) PDCCH monitoring periodicity; 6B) PDCCH monitoring pattern within a slot; 6C) PDCCH monitoring offset.

[0216] A monitoring occasion for a set of search regions may correspond to the OFDM symbol in which the first OFDM symbol of a control resource set associated with that search region is located. A monitoring occasion for a set of search regions may also correspond to a resource in a control resource set associated with that search region that starts from the first OFDM symbol of that control resource set. The monitoring occasion for a set of search regions is given based on at least some or all of the monitoring interval of the PDCCH, the monitoring pattern of the PDCCH in the slot, and the monitoring offset of the PDCCH.

[0217] Figure 8 shows an example of a monitoring opportunity for a search area set according to one aspect of this embodiment. In Figure 8, search area set 91 and search area set 92 are set in primary cell 301, search area set 93 is set in secondary cell 302, and search area set 94 is set in secondary cell 303.

[0218] In Figure 8, the white monochrome blocks in primary cell 301 represent search area set 91, the black monochrome blocks in primary cell 301 represent search area set 92, the blocks in secondary cell 302 represent search area set 93, and the blocks in secondary cell 303 represent search area set 94.

[0219] The monitoring interval for the search area set 91 is set to 1 slot, the monitoring offset for the search area set 91 is set to 0 slots, and the monitoring pattern for the search area set 91 is set to [1,0,0,0,0,0,0,1,0,0,0,0,0,0]. In other words, the monitoring opportunities for the search area set 91 correspond to the first OFDM symbol (OFDM symbol #0) and the eighth OFDM symbol (OFDM symbol #7) in each slot.

[0220] The monitoring interval for the search area set 92 is set to 2 slots, the monitoring offset for the search area set 92 is set to 0 slots, and the monitoring pattern for the search area set 92 is set to [1,0,0,0,0,0,0,0,0,0,0,0,0,0,0]. In other words, the monitoring opportunities for the search area set 92 correspond to the first OFDM symbol (OFDM symbol #0) in each of the even-numbered slots.

[0221] The monitoring interval for the search area set 93 is set to 2 slots, the monitoring offset for the search area set 93 is set to 0 slots, and the monitoring pattern for the search area set 93 is set to [0,0,0,0,0,0,0,1,0,0,0,0,0,0]. In other words, the monitoring opportunities for the search area set 93 correspond to the 8th OFDM symbol (OFDM symbol #7) in each of the even-numbered slots.

[0222] The monitoring interval for the search area set 94 is set to 2 slots, the monitoring offset for the search area set 94 is set to 1 slot, and the monitoring pattern for the search area set 94 is set to [1,0,0,0,0,0,0,0,0,0,0,0,0,0,0]. In other words, the monitoring opportunities for the search area set 94 correspond to the first OFDM symbol (OFDM symbol #0) in each of the odd-numbered slots.

[0223] The Type 0 PDCCH common search region set may be used for DCI formats with a Cyclic Redundancy Check (CRC) sequence scrambled by SI-RNTI (System Information-Radio Network Temporary Identifier).

[0224] The Type 0aPDCCH common search region set may be used for DCI formats with a Cyclic Redundancy Check (CRC) sequence scrambled by SI-RNTI (System Information-Radio Network Temporary Identifier).

[0225] The Type 1 PDCCH common search region set may be used for DCI formats with CRC sequences scrambled by RA-RNTI (Random Access-Radio Network Temporary Identifier) ​​and / or CRC sequences scrambled by TC-RNTI (Temporary Cell-Radio Network Temporary Identifier).

[0226] The Type 2 PDCCH common search region set may be used for the DCI format with a CRC sequence scrambled by P-RNTI (Paging-Radio Network Temporary Identifier).

[0227] The Type 3 PDCCH common search region set may be used for the DCI format with a CRC sequence scrambled by C-RNTI (Cell-Radio Network Temporary Identifier).

[0228] The UE individual PDCCH search region set may be used for the DCI format with a CRC sequence scrambled by C-RNTI.

[0229] In downlink communication, terminal device 1 detects the downlink DCI format. The detected downlink DCI format is used at least for resource allocation of the PDSCH. The detected downlink DCI format is also called the downlink assignment. Terminal device 1 attempts to receive the PDSCH. Based on the PUCCH resources indicated by the detected downlink DCI format, it reports the HARQ-ACK corresponding to the PDSCH (HARQ-ACK corresponding to the transport block contained in the PDSCH) to base station device 3.

[0230] In uplink communication, terminal device 1 detects the uplink DCI format. The detected DCI format is used at least for resource allocation in PUSCH. The detected uplink DCI format is also called an uplink grant. Terminal device 1 then transmits the PUSCH.

[0231] In configured grants, the uplink grant that schedules a PUSCH is set for each transmission cycle of the PUSCH. When a PUSCH is scheduled using the uplink DCI format, some or all of the information indicated by the uplink DCI format may be indicated by the uplink grant set in the configured grant.

[0232] A PUSCH transmission may correspond to either a configured scheduling type 1 or a configured scheduling type 2. That is, the configured scheduling may be either a configured scheduling type 1 or a configured scheduling type 2. A PUSCH transmission for configured scheduling type 1 may be configured semi-statically. For example, a PUSCH transmission for configured scheduling type 1 may operate in response to the reception of a certain upper-layer parameter. That upper-layer parameter may be configuredGrantConfig. For example, configuredGrantConfig may include rrc-ConfiguredUplinkGrant. A PUSCH transmission may operate without detection of an uplink grant in DCI.

[0233] A push transmission of scheduling type 2 may be scheduled semi-persistently. For example, it may be scheduled by an uplink grant. An uplink grant may be included in an activation DCI (or valid activation DCI). For example, a push transmission of scheduling type 2 may be scheduled by an uplink grant after receiving a certain upper-layer parameter. The upper-layer parameter may be configuredGrantConfig. For example, configuredGrantConfig does not have to include rrc-ConfiguredUplinkGrant.

[0234] System frame number (SFN) n ｆThis may be a number assigned to a radio frame, and / or an index for the radio frame. The system frame number may consist of 10 bits. At least a portion of the system frame number may be communicated in the MIB. For example, 6 bits of the 10-bit system frame number (e.g., 6 most significant bits) may be communicated in the MIB. At least a portion of the system frame number may be determined based on the PBCH for propagating the MIB. For example, 4 bits of the 10-bit system frame number (e.g., 4 least significant bits) may be communicated in the PBCH transport block as part of channel coding.

[0235] PDCCH-Config may be a dedicated upper-tier parameter. PDCCH-Config may set parameters for PDCCH. Multiple (e.g., up to 3) CORESETs may be configured in PDCCH-Config. A CORESET ID may be set for a single CORESET. A single CORESET pool index may be set for a single CORESET.

[0236] A PDCCH configuration may include two different CORESET pool indices. For example, two CORESET pool index values ​​(0 and 1) may be provided. For example, two CORESET pool index values ​​may be provided for First CORESET and Second CORESET. A PDCCH configuration may also be PDCCH-Config.

[0237] PDSCH-Config may be a dedicated higher-level parameter. PDSCH-Config may also set parameters for PDSCH.

[0238] If multiple PDCCH candidates (PDCCH candidate(s)) are related to the search space set defined by the higher-level parameter, one PDCCH candidate is used. This one PDCCH candidate may be the earlier-started PDCCH candidate of two PDCCH candidates. The higher-level parameter may be searchSpaceLinking.

[0239] Multiple TRPs (Transmission Reception Points, or Transmit / Receive Points) may be used. Base station equipment 3 may consist of multiple TRPs (Multi-TRP). Terminal equipment 1 may be scheduled by two TRPs in one serving cell. In Multi-TRP, either single-DCI or multi-DCI operating modes may be used. In Multi-TRP, uplink control may be completed at the MAC layer and physical layer. In Multi-TRP, downlink control may be completed at the MAC layer and physical layer. In Single-DCI mode, terminal equipment 1 may be scheduled by the same DCI for multiple TRPs. In Multi-DCI mode, terminal equipment 1 may be scheduled by independent DCIs from each TRP.

[0240] One or both of terminal device 1 and base station device 3 may form a beam (beamforming). For example, one or both of terminal device 1 and base station device 3 may transmit radio waves (electromagnetic waves) in a specific spatial direction by beamforming. For example, one or both of terminal device 1 and base station device 3 may receive radio waves from a specific spatial direction by beamforming. One or more antennas may be provided and used for one or both of the transmission and / or reception of radio waves. Directional radio waves may be referred to as beams. Information related to beams may be referred to as beam information. For example, beam information may be a specific spatial direction. For example, beam information may be the direction of arrival of radio waves. Beam information may be TCI status. Beam information may be an uplink transmit spatial filter. Beam information may be an SRS resource indication. Beam information may be a QCL assumption or QCL relationship.

[0241] Terminal device 1 may receive PDSCH. Base station device 3 may transmit PDSCH. One transmission method may be defined for PDSCH. One transmission method may be used for all PDSCH transmissions.

[0242] Terminal device 1 may perform reception in PDSCH. Base station device 3 may perform transmission in PDSCH. One transmission method may be transmission method 1. In transmission method 1, it may be assumed that transmission in PDSCH is performed at up to 8 layers. Each layer may be mapped to one or more antenna ports. One or more antenna ports may be some or all of antenna ports 1000-1023. For example, if an extended CSI port is not configured, one or more antenna ports may be some or all of antenna ports 1000-1023. For example, if an extended CSI port is configured, one or more antenna ports may be some or all of antenna ports 1000-1127.

[0243] Terminal device 1 may schedule to receive PDSCH. For example, terminal device 1 may schedule to receive PDSCH by DCI. PDSCH reception may be scheduled by the DCI format in PDCCH. PDSCH may be scheduled in DCI format. Terminal device 1 may receive scheduling grants in DCI format. When scheduling grants are received, downlink resource allocation may be used.

[0244] Terminal device 1 may have a higher-layer parameter TCI-State set. For example, terminal device 1 may have one list set in the higher-layer parameter PDSCH-Config. One list may contain up to M higher-layer parameters TCI-State. One list may also be a list of up to M higher-layer parameters TCI-State. Terminal device 1 may have one list set to decode (receive) the PDSCH according to the PDCCH with DCI. M may depend on the terminal capability (UE capability). For example, M may depend on the terminal capability maxNumberConfiguredTCIStatePerCC. TCI-State may also be referred to as TCI state.

[0245] Each TCI-State may include parameters for setting a QCL (Quasi co-location relationship). A QCL relationship may be a relationship between one or two downlink reference signals (downlink physical signals) and a DMRS (DMRS port) of a PDSCH. A QCL relationship may be a relationship between one or two downlink reference signals (downlink physical signals) and a DMRS (DMRS port) of a PDCCH. A QCL relationship may be a relationship between one or two downlink reference signals (downlink physical signals) and a CSI-RS (CSI-RS port) of a CSI-RS resource. For example, the QCL relationship between channel / signal A and channel / signal B may indicate that channel / signal A is QCL with channel / signal B.

[0246] QCL relationships may be defined by either or both of the upper-layer parameters qcl-Type1 and qcl-Type2. For example, a QCL relationship may be defined by either or both of the upper-layer parameter qcl-Type1 for the first downlink reference signal (DL RS) and the upper-layer parameter qcl-Type2 for the second downlink reference signal. If the first and second downlink reference signals are different, the QCL type of qcl-Type1 does not have to be the same as the QCL type of qcl-Type2. The QCL type corresponding to each downlink reference signal may be given by the upper-layer parameter qcl-Type in the upper-layer parameter QCL-Info. The QCL type may be one of typeA, typeB, typeC, and typeD.

[0247] One list may be set by the upper-layer parameter dlOrJointTCI-StateList. For example, one list may be set in the upper-layer parameter PDSCH-Config. One list may contain up to 128 upper-layer parameter TCI-States. One list may be a list of up to 128 upper-layer parameter TCI-States. One list may be set to provide one reference signal. The upper-layer parameter TCI-State may be set to provide one reference signal. One reference signal may be a reference signal for the DMRS of the PDSCH and for the QCL for the DMRS of the PDCCH. One reference signal may be a reference signal for the CSI-RS. One list may be set to provide one reference. The upper-layer parameter TCI-state may be set to provide one reference. One reference may be used to determine the uplink transmit spatial filter (UL TX spatial filter). The uplink transmit spatial filter may be used for PUSCH, PUCCH, and SRS. That is, one reference may be provided to determine the uplink transmit space filter for PUSCH, PUCCH, and SRS. The TCI-State may be referred to as the DL / Joint TCI state or the Unified TCI state. Setting the upper layer parameter dlOrJointTCI-StateList may mean setting the Unified TCI state. Setting the upper layer parameter dlOrJointTCI-StateList may mean setting the Unified TCI state.

[0248] TCI-State (e.g., upper-layer parameter TCI-State) and TCI-UL-State (e.g., upper-layer parameter TCI-UL-State) may be set in one BWP of one component carrier. If the TCI-State or TCI-UL-State is not set in one BWP, terminal device 1 may apply the TCI-State or TCI-UL-State setting from a reference BWP. TCI-UL-State may also be referred to as UL TCI state or unified TCI state. Setting ul-TCI-StateList may also mean setting the unified TCI state.

[0249] Terminal device 1 does not need to expect both the first and second upper-layer parameters to be set. The first upper-layer parameter may be any of tci-StatesToAddModList, SpatialRelationInfo, and PUCCH-SpatialRelationInfo. The second upper-layer parameter may be any of dl-OrJointTCI-StateList and TCI-UL-StateList. If tci-StatesToAddModList is set for any component carrier in a certain list, the second upper-layer parameter does not need to be set for any component carrier in the same band in that list. That list may be set by the upper-layer parameters simultaneousTCI-UpdateList1, simultaneousTCI-UpdateList2, simultaneousSpatial-UpdatedList1, or simultaneousSpatial-UpdatedList2.

[0250] Terminal device 1 may receive an activation command. An activation command may be used to map up to eight TCI states, and one or both of a pair of TCI states, to code points in the DCI field 'Transmission Configuration Indication'. A pair of TCI states may consist of one or both of a TCI state for a downlink channel / signal and a TCI state for an uplink channel / signal. An activation command may be used to map up to eight sets of TCI states to code points in the DCI field 'Transmission Configuration Indication'. Each set may contain up to two TCI states for the uplink and downlink channels / signals. An activation command may be used to map up to two TCI states for the downlink channel / signal and up to two TCI states for the uplink channel / signal to code points in the DCI field 'Transmission Configuration Indication'. A TCI state for a downlink channel / signal may be referred to as a DL TCI state. The TCI state for the uplink channel / signal may be referred to as the UL TCI state. The downlink channel / signal may be part or all of the PDSCH, PDCCH, and CSI-RS. The uplink channel / signal may be part or all of the PUSCH, PUCCH, and SRS. The DCI (DCI format) may consist of one or more DCI fields. For example, the DCI (DCI format) may consist of a TCI field ('Transmission Configuration Indication' field).

[0251] If a first set of one or more TCI state IDs is activated in a second set, the first set may be applied for the downlink BWP on the indicated component carrier. If a first set of one or more TCI state IDs is activated in a third set, the first set may be applied for the downlink BWP and uplink BWP on the indicated component carrier. The second set may be a set of one or more component carriers and one or more downlink BWPs, or both. The third set may be a set of some or all of the component carriers, one or more downlink BWPs, and one or more uplink BWPs.

[0252] If the activation command maps either or both of the DL / Joint TCI state and / or the UL TCI state to a single TCI code point (the code point of the DCI field 'Transmission Configuration Indication'), terminal device 1 may apply either or both of the indicated DL / Joint TCI state and / or the indicated UL TCI state.

[0253] Terminal device 1 may receive a DCI format that provides a specified DL / Joint TCI state or a specified UL TCI state. The DCI format does not have to include a downlink assignment. For example, if the DCI format does not include a downlink assignment, terminal device 1 may assume that CS-RNTI is used to scramble the CRC for DCI, that RV (Redundancy version) is all 1, that MCS is all 1, that NDI is 0, that all 0 is set for FDRA type 0, and that all 1 is set for FDRA type 1.

[0254] Terminal device 1 may receive upper-layer settings. After terminal device 1 receives the first upper-layer setting of “Set TCI State”, and before one “Indicated TCI State” is applied from “Set TCI State”, terminal device 1 may assume that the PDSCH DMRS, PDCCH DMRS, and CSI-RS to which the “Indicated TCI State” is applied are the SS / PBCH block and QCL. Setting the upper-layer parameter DLorJoint-TCIStateList may also mean setting “Set TCI State”. Setting the upper-layer parameter DLorJoint-TCIStateList may also mean setting a unified TCI state. Setting “Set TCI State” may also mean setting a unified TCI state. DLorJoint-TCIStateList may be accompanied by multiple upper-layer parameters TCI-State.

[0255] After terminal device 1 receives the first upper-layer setting of “Set TCI State”, and before one “Instructed TCI State” is applied from “Set TCI State”, terminal device 1 may assume that the first uplink transmit space filter for PUSCH, PUCCH, and SRS to which the “Instructed TCI State” is applied is the same as the second uplink transmit space filter. The second uplink transmit space filter may be the uplink transmit space filter for PUSCH transmissions scheduled by random access response grants in the Initial access procedure. Setting the upper-layer parameter ul-TCI-StateList may mean setting “Set TCI State”. Setting the upper-layer parameter ul-TCI-StateList may mean setting a unified TCI State. Setting “Set TCI State” may mean setting a unified TCI State. ul-TCI-StateList may be accompanied by multiple upper-layer parameter TCI-States.

[0256] Terminal device 1 may receive upper-layer settings. After terminal device 1 receives the first upper-layer setting of “Set TCI State” as part of a synchronized reconfiguration, and before one “Indicated TCI State” is applied from “Set TCI State”, the PDSCH DMRS, PDCCH DMRS, and CSI-RS to which the indicated TCI State is applied may be an SS / PBCH block or a CSI-RS resource and QCL. For example, an SS / PBCH block or a CSI-RS resource may be identified in a random access procedure initiated by a synchronized reconfiguration.

[0257] Terminal device 1 may receive upper-layer settings. After terminal device 1 receives the first upper-layer setting of “Set TCI State” as part of a synchronous reconfiguration, and before one “Indicated TCI State” is applied from “Set TCI State”, it may be assumed that the first uplink transmit space filter for PUSCH, PUCCH, and SRS to which the indicated TCI State is applied is the same as the second uplink transmit space filter. The second uplink transmit space filter may be an uplink transmit space filter for PUSCH transmissions scheduled by a Random Access Response Grant (RAR UL grant) in a Random Access procedure. The second uplink transmit space filter may be an uplink transmit space filter for PUSCH transmissions scheduled by a Random Access Response Grant in a Random Access procedure initiated by a synchronous reconfiguration.

[0258] When terminal device 1 receives a setting of “Set TCI State” accompanied by one TCI state, terminal device 1 may obtain a QCL assumption from the Set TCI State. The Set TCI State may be a TCI state for the CSI-RS, PDSCH DMRS, and PDCCH DMRS to which the indicated TCI state applies. The Set TCI State may also be the upper-layer parameter dl-OrJointTCI-StateList.

[0259] When the terminal device 1 receives configuration of a "configured TCI state" accompanied by one TCI state, the terminal device 1 may determine an uplink transmission spatial filter from the configured TCI state. The configured TCI state may be a TCI state for PUSCH, PUCCH, and SRS to which the indicated TCI state is applied. The configured TCI state may be a higher layer parameter dl-OrJointTCI-StateList or ul-TCI-StateList.

[0260] When a unified TCI state is configured, when the terminal device 1 transmits a first channel, and when a first "indicated TCI state" is different from a second "indicated TCI state", the first "indicated TCI state" may be applied from a first slot. The first channel may be PUCCH with HARQ-ACK information or PUSCH with HARQ-ACK information. The HARQ-ACK information may be HARQ-ACK information corresponding to DCI that carries a TCI State indication without downlink assignment. The HARQ-ACK information may be HARQ-ACK information corresponding to a PDSCH scheduled by DCI that carries a TCI state indication. The second indicated TCI state may be indicated before (earlier than) the first indicated TCI state. The first slot may be the first slot that is at least beamAppTime symbols after the last OFDM symbol of the first channel. BeamAppTime may be the number of OFDM symbols. BeamAppTime may be configured by a higher layer parameter. BeamAppTime may be determined based on terminal capability. The indicated TCI state may be an indicated TCI-State or an indicated TCI-UL-State.

[0261] When multi-DCI mode is configured, terminal device 1 may receive activation commands ("Activated TCI states") for each CORESET associated with each CORESET pool index. The activation command may be used to map up to eight TCI states to code points in the DCI field 'Transmission Configuration Indication'. The TCI states mapped to code points in the TCI field may be referred to as activated TCI states. The TCI states indicated by the activation command may be referred to as activated TCI states. When a set of TCI state IDs is activated for one CORESET pool index, the "activated TCI state" corresponding to that one CORESET pool index may be associated with one physical cell ID, and the "activated TCI state" corresponding to a different CORESET pool index may be associated with a different physical cell ID. The activation command may be received as MAC CE. One or more CORESETs may be configured in a single BWP. A single CORESET may correspond to a CORESET pool index of '0' or '1'. Multi-DCI mode may be configured if the upper-level parameter PDCCH-Config contains two different values ​​for the CORESET pool index (CORESET Pool Index, or coresetPoolIndex).

[0262] A single code point in the DCI field 'Transmission Configuration Indication' (i.e., the TCI field) may contain up to two TCI states. Terminal device 1 may receive an activation command. The activation command may be used to map up to eight combinations of two or fewer TCI states to the code points in the DCI field 'Transmission Configuration Indication'. Terminal device 1 does not need to expect to receive more than eight TCI states in the activation command.

[0263] When the terminal device 1 transmits a first PUCCH in a first slot, the mapping between TCI states and code points may be applied from the second slot. The first PUCCH may be accompanied with first HARQ-ACK information. The first PUCCH may be transmitted in correspondence with a first PDSCH. The first PDSCH may carry an activation command.

[0264] When a TCI field is present, a time offset is greater than or equal to a threshold, after a first configuration of a TCI state is received and before an activation command is received, the terminal device 1 may assume that a DMRS of a PDSCH in one serving cell is quasi-colocation with an SS / PBCH block with respect to QCL Type A. The presence of the TCI field may mean that 'enabled' is set in the higher layer parameter tci-PresentInDCI. The presence of the TCI field may mean that the higher layer parameter tci-PresentDCI-1-2 is configured for a CORESET scheduling a PDSCH. The time offset may be an offset between reception of DL DCI and the PDSCH. The threshold may be timeDurationForQCL. The threshold may be based on reported terminal capability.

[0265] When a first higher layer parameter is configured, the terminal device 1 may assume that a TCI field is present in a DCI format of a PDCCH transmitted in a CORESET. The first higher layer parameter may be tci-PresentInDCI with 'enabled' set. The first higher layer parameter may be tci-PresentInDCI with 'enabled' set for a CORESET that schedules a PDSCH or a multicast PDSCH. The first higher layer parameter may be tci-PresentDCI-1-2.

[0266] If the TCI field is not present and the time offset is greater than or equal to a threshold, the TCI state or QCL assumption for the PDSCH may be the same as the TCI state or QCL assumption applied for the CORESET used for the PDCCH in order to determine the PDSCH antenna port QCL. The time offset may be the time offset between the reception of the DL DCI and the corresponding PDSCH. The threshold may be timeDurationForQCL.

[0267] If an SFN is set for PDCCH, and an SFN is set for PDSCH, and PDSCH is scheduled in DCI format, and the time offset is greater than or equal to a threshold, and the default beam is supported, then the QCL assumption or TCI state for PDSCH may be the same as the QCL assumption or TCI state applied for CORESET. Also, if dynamic switching is not supported, CORESET may be activated in two TCI states. CORESET may be CORESET for receiving DL DCI. If an SFN is set for PDCCH, and an SFN is set for PDSCH, and PDSCH is scheduled in DCI format, and the time offset is greater than or equal to a threshold, and the default beam is not supported, then the existence of a TCI field may be assumed. Setting an SFN for PDCCH may mean setting the upper layer parameter sfnSchemePdcch. Setting an SFN for PDSCH may mean setting the upper layer parameter sfnSchemePdsch. The DCI format may be any of DCI format 1_0, DCI format 1_1, or DCI format 1_2. The default beam may be sfn-DefaultDL-BeamSetup for DCI without a TCI field. The time offset may be the time offset between the reception of the DL DCI and the corresponding PDSCH. The threshold may be timeDurationForQCL.

[0268] The presence of a TCI field may be expected if an SFN is set for PDSCH, and an SFN is not set for PDCCH, and PDSCH is scheduled according to DCI format 1_1 / 1_2, and the time offset is greater than or equal to a threshold.

[0269] If PDSCH is scheduled by DCI format 1_0 / 1_1 / 1_2, and SFN method A is set for PDCCH, and SFN is not set for PDSCH, and there are no TCI code points (code points in the TCI field) with two TCI states, and the time offset is greater than or equal to a threshold, and the CORESET that schedules PDSCH is indicated by two TCI states, then the TCI state or QCL assumption for PDSCH may be the same as the first TCI state and first QCL assumption applied for CORESET. Setting SFN method A for PDCCH may mean setting sfnSchemePdcch with 'sfnSchemeA' set.

[0270] If no unified TCI state is set, and the time offset is less than the threshold, and at least one set TCI state includes a qcl-Type with typeD set, the DMRS port of the PDSCH may be RS and QCL for a certain QCL parameter. A certain QCL parameter may be used for PDCCH QCL indication of a certain CORESET. A certain CORESET may be a CORESET associated with the search area with the lowest CORESET ID (controlResourceSetId) among the CORESETs monitored by terminal device 1 in the latest slot.

[0271] If a unified TCI state is set, and the time offset is less than the threshold, and at least one set TCI state includes a qcl-Type with typeD set, and the indicated TCI state is related to the PCI (Physical Cell ID) of the serving cell, then the indicated TCI state may be applied to PDSCH reception. If a unified TCI state is set, and the time offset is less than the threshold, and at least one set TCI state includes a qcl-Type with typeD set, and the indicated TCI state is related to a PCI (Physical Cell ID) other than that of the serving cell, then the DMRS port of the PDSCH in the serving cell may be a reference signal and QCL related to the QCL parameter of the CORESET associated with the lowest CORESET ID. Setting a unified TCI state may also mean setting the upper layer parameter dl-OrJointTCI-StateList.

[0272] If a first terminal capability is specified for terminal device 1, terminal device 1 may determine a spatial domain filter. The spatial domain filter may be used while performing applicable channel access procedures before UL transmission on the channel. If an SRI corresponding to UL transmission is specified, terminal device 1 may use the same spatial domain filter as the spatial domain filter associated with the specified SRI. Terminal device 1 may use the same spatial domain filter as the spatial domain filter used to receive the DL reference signal associated with the specified TCI state. For example, if a TCI-State or TCI-UL-State is set, terminal device 1 may use the same spatial domain filter as the spatial domain filter used to receive the DL reference signal associated with the specified TCI state. The first terminal capability may be beamCorrespondenceWithoutUL-BeamSweeping, which is set to '1'.

[0273] For periodic CSI-RS resources, the TCI state may indicate that it is QCL with respect to the SS / PBCH block and type C. The SS / PBCH block may have a different PCI than the serving cell's PCI. Periodic CSI-RS resources may also be CSI-RS resources in an NZP-CSI-RS resource set for a Tracking Reference Signal (TRS). The NZP may be non-zero power. The CSI-RS resource set for the TRS may be a CSI-RS resource set in which the upper-layer parameter trs-Info is set.

[0274] When a unified TCI state is set for periodic CSI-RS and semi-persistent CSI-RS resources, terminal device 1 may assume that the indicated TCI state does not apply.

[0275] For aperiodic CSI-RS resources, the TCI state may indicate that it is QCL with respect to periodic CSI-RS resources and type A. Aperiodic CSI-RS resources may be CSI-RS resources in the NZP CSI-RS resource set for TRS. Periodic CSI-RS resources may be CSI-RS resources in the NZP CSI-RS resource set for TRS.

[0276] For the first CSI-RS resource, the TCI state may indicate that it is QCL with respect to type A with respect to the second CSI-RS resource. For the first CSI-RS resource, the TCI state may indicate that it is QCL with respect to type B with respect to the third CSI-RS resource. The first CSI-RS resource may be a CSI-RS resource in the NZP CSI-RS resource set for TRS. The first CSI-RS resource may not be a CSI-RS resource in the NZP CSI-RS resource set for repetition. The second CSI-RS resource may be a CSI-RS resource in the NZP CSI-RS resource set for TRS. The third CSI-RS resource may be a CSI-RS resource in the NZP CSI-RS resource set for TRS when type D is not applicable. The CSI-RS resource set for repetition may be a CSI-RS resource set with the upper-level parameter repetition.

[0277] For a fourth CSI-RS resource, the TCI state may indicate that it is QCL with respect to the second CSI-RS resource and type A. For a fourth CSI-RS resource, the TCI state may indicate that it is QCL with respect to the SS / PBCH block and type C. The fourth CSI-RS resource may be a CSI-RS resource in the NZP CSI-RS resource set for iteration.

[0278] If a unified TCI status is not set, the TCI status may indicate to the DMRS of PDCCH that it is QCL with respect to CSI-RS resources and type A. The CSI-RS resources may be CSI-RS resources in the NZP CSI-RS resource set.

[0279] When SFN method A is set for PDCCH and CORESET is activated in two TCI states, the DMRS port of PDCCH in CORESET may be DL RS (downlink reference signal) and QCL in the two TCI states. When SFN method B is set for PDCCH and CORESET is activated in two TCI states, the DMRS port of PDCCH in CORESET may be DL RS and QCL in the two TCI states, and the second TCI state does not have to include the QCL parameters {Doppler shift, Doppler spread}. Setting SFN method A for PDCCH may mean setting sfnSchemePdcch with 'sfnSchemeA' set. Setting SFN method B for PDCCH may mean setting sfnSchemePdcch with 'sfnSchemeB' set.

[0280] A Coherent Joint Transmission (CJT) may be configured for PDSCH. Configuring CJT may also involve configuring the upper-level parameter cjtSchemePDSCH. Configuring CJT method A may involve configuring the upper-level parameter cjtSchemeA. Configuring CJT method B may involve configuring the upper-level parameter cjtSchemeB. When CJT method A is configured for PDSCH, the DMRS port of PDSCH may be QCL with respect to two indicated TCI state reference signals and QCL type A. When CJT method B is configured for PDSCH, the DMRS port of PDSCH may be QCL with respect to two indicated TCI state reference signals and QCL type A, excluding the QCL parameters {Doppler shift, Doppler spread}.

[0281] If a unified TCI state is not set, the TCI state may indicate to the DMRS of PDSCH that it is QCL with respect to CSI-RS resources and type A. The CSI-RS resource may be a CSI-RS resource in the NZP (Non-zero power) CSI-RS resource set.

[0282] When a unified TCI state is set, the TCI state may indicate to the DMRS of PDCCH that it is QCL with respect to CSI-RS resources and Type A.

[0283] If SFN method A is configured for PDSCH and two TCI states are indicated, the DMRS port of PDSCH may be DL-RS and QCL of the two TCI states. If SFN method B is configured for PDSCH and two TCI states are indicated, the DMRS port of PDSCH may be DL-RS and QCL of the two TCI states. If SFN method B is configured for PDSCH and two TCI states are indicated, the DMRS port of PDSCH may be DL-RS and QCL of the two TCI states, and the second TCI state does not have to include the QCL parameters {Doppler shift, Doppler spread}. The two TCI states may be indicated by a single code point in the DCI field 'Transmission Configuration Indication' in the DCI that schedules PDSCH. Configuring SFN method A for PDSCH may mean configuring sfnSchemePdsch with 'sfnSchemeA' set. Setting SFN method B for PDSCH may also mean setting sfnSchemePdsch, which has 'sfnSchemeB' set to it.

[0284] If a unified TCI state is set, and multi-DCI mode is set, and one indicated TCI state is indicated by a TCI field (DCI field 'Transmission Configuration Indication') in DCI format 1_1 / 1_2 related to a value of one CORESET pool index, then one indicated TCI state may correspond to a value of one CORESET pool index. Setting a unified TCI state may also mean setting dl-OrJointTCI-StateList or TCI-UL-State. Setting multi-DCI mode may also mean setting the upper-level parameter PDCCH-Config which contains two different CORESET pool index values. The CORESET pool index may be set in the upper-level parameter ControlResourceSet.

[0285] If a unified TCI state is set, and terminal device 1 has two indicated TCI-States, and the terminal capability of the default beam is not reported, and the time offset is less than a threshold, the first indicated TCI-State may be applied to PDSCH reception. The terminal capability of the default beam may be the capability to use the two indicated TCI states to buffer received signals before the threshold. The terminal capability of the default beam may be the capability in FR2 (Frequency Range 2). For example, FR2 may be a frequency range from 24250MHz to 52600MHz. The time offset may be the offset between the reception of the scheduled DCI format 1_0 / 1_1 / 1_2 and the scheduled PDSCH reception. The time offset may be the offset between the reception of the activated DCI format 1_0 / 1_1 / 1_2 and the activated PDSCH reception. The threshold may be timeDurationForQCL, or a value less than timeDurationForQCL.

[0286] If a unified TCI state is set, and multi-DCI mode is set, and the terminal capability of the default beam is not reported, and the first time offset is less than a threshold, the “indicated TCI state” corresponding to CORESET pool index 0 may be applied to PDSCH reception. If a unified TCI state is set, and multi-DCI mode is set, and the terminal capability of the default beam is not reported, it is not expected that the second time offset will be less than a threshold. The first time offset may be the offset between the reception of the DCI format in CORESET related to CORESET pool index 0 and the PDSCH reception. The second time offset may be the offset between the reception of the DCI format in CORESET related to CORESET pool index 1 and the PDSCH reception.

[0287] If a unified TCI state is set, and terminal device 1 has two indicated TCI-States, and certain conditions are met, the upper layer parameter applyIndicatedTCIState may indicate that the first indicated TCI-State, the second indicated TCI-State, or both indicated TCI-States are applied to PDSCH reception scheduled by DCI format 1_0. The upper layer parameter applyIndicatedTCIState may indicate "first", "second", or "both", where "first" corresponds to the first indicated TCI state, "second" corresponds to the second indicated TCI state, and "both" corresponds to both indicated TCI states. If a CJT is set for PDSCH, or if an SFN is set for PDSCH, the upper layer parameter applyIndicatedTCIState may indicate "both". Certain conditions may be FR1 (Frequency Range 1). One condition may be that the terminal capability of the default beam is reported in FR2.

[0288] If a unified TCI state is set, and terminal device 1 has two indicated TCI-States, and certain conditions are met, and the upper-level parameter applyIndicatedTCIState is not set, then the first indicated TCI-State may be applied to the PDSCH scheduled by DCI format 1_0.

[0289] If a unified TCI state is set, and terminal device 1 has two indicated TCI-States, and certain conditions are met, and the TCI indication field indicates "00", then the first indicated DL / Joint TCI state may be applied to the PDSCH. If a unified TCI state is set, and terminal device 1 has two indicated TCI-States, and certain conditions are met, and the TCI indication field indicates "01", then the second indicated DL / Joint TCI state may be applied to the PDSCH. If a unified TCI state is set, and terminal device 1 has two indicated TCI-States, and certain conditions are met, and the TCI indication field indicates "10", then both indicated DL / Joint TCI states may be applied to the PDSCH. If a unified TCI state is set, and terminal device 1 has two indicated TCI-States, and certain conditions are met, and no TCI indication field is set, then two DL / Joint TCI states may be applied to the PDSCH. The PDSCH may be scheduled according to DCI format 1_1 / 1_2. The TCI indication field may be a DCI field in DCI format 1_1 / 1_2. Whether a TCI indication field exists in DCI format 1_1 / 1_2 may be determined by the upper-level parameter tciSelection-PresentInDCI.

[0290] Terminal device 1 may have the upper layer parameter TCI-UL-State set. For example, terminal device 1 may have one list set in the upper layer parameter BWP-UplinkDedicated. One list may contain up to 64 upper layer parameters TCI-UL-State. One list may also be a list of up to 64 upper layer parameters TCI-UL-State. Each TCI-UL-State (or UL-TCI-State setting) may include a parameter for setting one reference signal. For example, each TCI-UL-State may include a parameter for setting one reference signal for determining PUSCH, PUCCH, and uplink transmit space filters for some or all of the SRS. One list may also be the upper layer parameter ul-TCI-StateList. The TCI state may also be a TCI-UL-State. UL-TCIState (TCI-UL-State) may also be referred to as the UL TCI state or unified TCI state.

[0291] UL-TCIState may be a higher-layer parameter TCI-UL-State. UL-TCIState may be set by a higher-layer parameter TCI-UL-State. The higher-layer parameter TCI-UL-State may associate one or two downlink reference signals with one corresponding QCL type.

[0292] CSI reports may be triggered by DCI (DCI format). For example, aperiodic CSI reports may be triggered by DCI format 0_1 / 0_2.

[0293] The time-frequency resource used for reporting CSI may be controlled by the base station apparatus 3. CSI may consist of part or all of CQI (Channel Quality Indicator), PMI (Precoding Matrix Indicator), CRI (CSI-RS resource indicator), SSBRI (SS / PBCH Block Resource indicator), LI (Layer Indicator), RI (Rank Indicator), L1-RSRP (Layer 1-Reference Signal Received Power), L1-SINR (Layer 1-Signal-to-Interference-plus-Noise Ratio), CapabilityIndex, and TDCP (Time-Domain Channel Properties). CQI, PMI, CRI, SSBRI, LI, RI, L1-RSRP, L1-SINR, CapabilityIndex, and TDCP may be referred to as CSI parameters.

[0294] The terminal apparatus 1 may be configured with N pieces of CSI report configuration. The CSI report configuration may be a higher layer parameter CSI-ReportConfig.

[0295] The terminal apparatus 1 may be configured with M pieces of CSI report configuration. The CSI resource configuration may be a higher layer parameter CSI-ResourceConfig.

[0296] Terminal device 1 may have a list of one or two trigger states (Trigger state(s)). The list of trigger states may be one or both of the upper-layer parameters CSI-AperiodicTriggerStateList and CSI-SemiPersistentOnPUSCH-TriggerStateList. For example, the list of trigger states for aperiodic CSI may be the upper-layer parameter CSI-AperiodicTriggerStateList. For example, the list of trigger states for semi-persistent CSI may be the upper-layer parameter CSI-SemiPersistentOnPUSCH-TriggerStateList. The list of trigger states may contain one or more trigger states.

[0297] Each trigger state may include one associated CSI reporting setting or a list of one associated CSI reporting settings. The list of CSI reporting settings may indicate one or more resource set IDs. For example, each trigger state in the list of trigger states for aperiodic CSI may include a list of associated CSI reporting settings. For example, each trigger state in the list of trigger states for semi-persistent CSI may include one CSI reporting setting.

[0298] Each CSI reporting setting (Reporting Setting CSI-ReportConfig) may be associated with one downlink BWP. A downlink BWP may be indicated by a BWP ID (higher-level parameter BWP-Id). A downlink BWP may be provided in the CSI resource settings. For example, a downlink BWP may be provided in the CSI resource settings for channel measurement.

[0299] Each CSI reporting setting may include some or all of the CSI resource settings for channel measurement (upper layer parameter resourceForChannelMeasurement) and the CSI resource settings for interference measurement (upper layer parameter csi-IM-ResourcesForInterference, upper layer parameter nzp-CSI-RS-ResourcesForInterference).

[0300] Each CSI reporting setting may include codebook settings, time-domain behavior, frequency granularity for CQI and PMI, measurement restriction configuration, and CSI-related quantity settings. For example, CSI-related quantities may be LI, L1-RSRP, L1-SINR, CRI, SSBRI, CapabilityIndex, and TDCP.

[0301] The time-domain behavior may be indicated by the higher-level parameter reportConfigType. The time-domain behavior may be set to 'aperiodic', 'semiPersistentOnPUCCH', 'semiPersistentOnPUSCH', or 'periodic'. If the time-domain behavior is set to 'aperiodic', the CSI reporting setting may be the CSI reporting setting for aperiodic CSI. If the time-domain behavior is set to 'semiPersistentOnPUCCH' or 'semiPersistentOnPUSCH', the CSI reporting setting may be the CSI reporting setting for semi-persistent CSI. If the time-domain behavior is set to 'periodic', the CSI reporting setting may be the CSI reporting setting for periodic CSI.

[0302] For periodic CSI and semi-persistent CSI reports, a period and slot offset may be set. For periodic CSI and semi-persistent CSI reports, a period and slot offset may be applied in the numerology of the uplink BWP corresponding to the transmission of the CSI report.

[0303] Each CSI reporting setting may include a report quantity setting. The report quantity setting may specify a CSI-related quantity, an L1-RSRP-related quantity, an L1-SINR-related quantity, a Capability Index-related quantity, or a TDCP-related quantity.

[0304] The frequency granularity may be indicated by the higher-layer parameter reportFreqConfiguration. PMI and CQI reports may cover the entire band (wideband) or sub-band. For example, the frequency granularity for PMI and CQI may be either wideband or sub-band, respectively.

[0305] The measurement limit setting may also be a time limit. The time limit may be set for either channel measurement or interference measurement, or both.

[0306] The codebook configuration may include Type 1, Type 2, Extended Type 2-CSI, Super Extended Type 2-CSI, Super Extended Type 2-Port Selection, Super Extended Type 2-CJT, Super Extended Type 2-Port Selection CJT, Extended Type 2-Predictive PMI, or Super Extended Type 2-Port Selection-Predictive PMI. The codebook configuration may include codebook subset restrictions. The codebook configuration may include group-based reporting settings.

[0307] Each CSI resource configuration (CSI-ResourceConfig) may contain one list of S CSI resource sets (CSI-RS resource sets). One list may be provided by the higher-level parameter csi-RS-ResourceSetList. One list may contain references to one or both of the NZP CSI-RS resource sets and SS / PBCH block sets. One list may contain references to the CSI-IM (CSI-Interference Measurement) resource set. Each CSI resource configuration may be associated with one downlink BWP. One downlink BWP may be indicated by a BWP ID. All CSI resource configurations linked to one CSI reporting configuration may have the same downlink BWP. One or more CSI resource configurations may be linked to one CSI reporting configuration. For example, one or more CSI resource configurations with the same downlink BWP may be linked to one CSI reporting configuration.

[0308] Each CSI resource configuration may contain one or more CSI-RS resource sets. Each CSI-RS resource set may be an NZP CSI-RS resource set. Each CSI-RS resource set may be an SS / PBCH block set. Each CSI-RS resource set may be a CSI-IM resource set. Each CSI-RS resource set may contain one or more CSI-RS resources. Each NZP CSI-RS resource set may contain one or more NZP CSI-RS resources.

[0309] The time-domain behavior of a CSI-RS resource in a single CSI resource configuration may be indicated by a higher-level parameter (resourceType). The time-domain behavior may be set to aperiodic, periodic, or semi-persistent. For periodic and semi-persistent CSIs, the CSI resource configuration may contain one set of CSI-RS resources. For periodic and semi-persistent CSIs, if group-based reporting is configured, the CSI resource configuration may contain two or fewer sets of CSI-RS resources.

[0310] In CSI resource configuration for periodic CSI and semi-persistent CSI, the period and time offset (slot offset) may be set. In CSI resource configuration for periodic CSI and semi-persistent CSI, the period and time offset may be given in the numerology of the downlink BWP given by the BWP ID.

[0311] If multiple CSI resource settings contain the same NZP CSI-RS resource (or the same NZP CSI-RS resource ID), the same time-domain behavior may be configured for all of the CSI resource settings. If multiple CSI resource settings contain the same CSI-IM resource (or the same CSI-IM resource ID), the same time-domain behavior may be configured for all of the CSI resource settings. All CSI resource settings linked to a single CSI reporting setting may have the same time-domain behavior.

[0312] CSI-IM resources for interference measurement may be configured for one or more CSI resource settings. NZP CSI-RS resources for interference measurement may be configured for one or more CSI resource settings. NZP CSI-RS resources for channel measurement may be configured for one or more CSI resource settings.

[0313] The NZP CSI-RS resource for channel measurement and the CSI-IM resource (or NZP CSI-RS resource) for interference measurement may be QCL with respect to type D. The NZP CSI-RS resource for channel measurement and the CSI-IM resource (or NZP CSI-RS resource) for interference measurement may be configured for a single CSI report (CSI report configuration).

[0314] For TDCP measurement, one periodic CSI reporting setting (CSI reporting setting for periodic CSI) may be set up. This CSI reporting setting may be a setting for channel measurement in CSI-RS for tracking. TDCP measurement may be a measurement where the reportQuantity setting in the CSI reporting setting includes TDCP.

[0315] In L1-SINR measurement, if one CSI resource setting is configured, that one CSI resource setting may be for channel measurement and interference measurement. Channel measurement and interference measurement may be measurements in NZP CSI-RS for L1-SINR calculation. One CSI resource setting may be provided by resourcesForChannelMeasurement. L1-SINR measurement may be a measurement where the report quantity setting (reportQuantity) in the CSI reporting setting includes L1-SINR.

[0316] In L1-SINR measurement, if two CSI resource settings are configured, the first CSI resource setting may be for channel measurement, and the second CSI resource setting may be for interference measurement. Channel measurement may be performed using SSB or NZP CSI-RS. Interference measurement may be performed using CSI-IM or a single-port NZP CSI-RS. The first CSI resource setting may be provided by resourcesForChannelMeasurement. The second CSI resource setting may be provided by csi-IM-ResourcesForInterference or nzp-CSI-RS-ResourcesForInterference.

[0317] Terminal device 1 may calculate CSI parameters. CSI parameters may be some or all of LI, CQI, PMI, RI, and CRI. Terminal device 1 may calculate RI based on CRI. Terminal device 1 may calculate PMI based on RI and CRI. Terminal device 1 may calculate CQI based on PMI, RI, and CRI. Terminal device 1 may calculate LI based on CQI, PMI, RI, and CRI.

[0318] CSI reporting settings may be aperiodic, periodic, or semi-persistent. CSI-RS resources may be periodic, semi-persistent, or aperiodic. CSI reporting may be triggered for each CSI resource setting. The combination of CSI reporting settings and CSI resource settings may be determined by time-domain behavior. Periodic CSI-RS may be set by the upper layer. Semi-persistent CSI-RS may be activated and deactivated. Aperiodic CSI-RS may be set, activated, and triggered.

[0319] Periodic CSI-RS may be combined with any of periodic, semi-permanent, or aperiodic CSI reporting settings. Semi-permanent CSI-RS may be combined with any of semi-permanent or aperiodic CSI reporting settings. Aperiodic CSI-RS may be combined with aperiodic CSI reporting setting. For semi-permanent CSI reporting, in the case of a report in PUCCH, terminal device 1 may receive an activation command. For semi-permanent CSI reporting, in the case of a report in PUSCH, terminal device may receive a triggering (trigger state) in DCI. Aperiodic CSI reporting may be triggered by DCI. Aperiodic CSI reporting may be triggered by MAC CE (e.g., a subset indication).

[0320] Terminal device 1 may determine one CRI. One CRI may be determined from a set of CRI values. Terminal device 1 may report a number in each CRI report. If a CSI-RS resource set for repetition is configured and the CSI-RS resource set is for channel measurement, the CRI does not need to be reported. If any of the following are set in the codebook setting (codebookType): type2 (typeII, typeII-PortSelection), extended type2-CSI (typeII-r16), extended type2-port selection (typeII-r16), super-extended type2-CSI (typeII-r17), super-extended type2-port selection (typeII-PortSelection-r17), super-extended type2-CJT (typeII-CJT-r18), super-extended type2-port selection CJT (typeII-CJT-PortSelection-r18), extended type2-predictive PMI (typeII-Doppler-r18), and super-extended type2-port selection-predictive PMI (typeII-Doppler-PortSelection-r18), then CSI does not need to be reported.

[0321] In periodic or semi-permanent CSI reporting in PUCCH, period T CSI and slot offset T offsetThis may be set by a higher-level parameter (e.g., reportSlotConfig). Terminal device 1 may send a CSI report. Terminal device 1 may send a CSI report in one slot in one wireless frame. One wireless frame is a System frame number (SFN) n ｆ It may also be compatible with slot index n. μ s，f It may also support this. One wireless frame and one slot, mod(N frame,μ slot *n f + n μ s，f -T offset , T CSI ) may be determined based on the fact that ) is 0. μ may be the subcarrier spacing setting of the uplink BWP to which the CSI report is sent.

[0322] In the semi-permanent CSI report at PUSCH, period T CSI This may be set by a higher-layer parameter (e.g., reportSlotConfig). Terminal device 1 may transmit a CSI report in one slot in one wireless frame. One wireless frame and one slot are mod(N frame,μ slot *(n f -n start f ) + n μ s，f - n start s,f , T CSI ) may be determined based on the fact that ) is 0. SFN n start f and slot number n start s,f This may correspond to the first semi-persistent push transmission. The first semi-persistent push transmission may follow an activated DCI.

[0323] In semi-permanent or aperiodic CSI reporting in PUSCH, one or more slot offsets may be set by a higher-level parameter. If the CSI reporting is triggered / activated by DCI format 0_2, the higher-level parameter may be reportSlotOffsetListDCI-0-2. If the CSI reporting is triggered / activated by DCI format 0_1, the higher-level parameter may be reportSlotOffsetListDCI-0-1. One slot offset may be selected in the DCI that triggers / activates.

[0324] In the CSI report, one of the two subband sizes may be set. The subband is N SB PRB It may also be defined by a number of consecutive PRBs. If the number of PRBs in a single BWP is between 24 and 72, then N SB PRB This may be 4 or 8. If the number of PRBs in one BWP is between 73 and 144, then N SB PRB This may be 8 or 16. If the number of PRBs in one BWP is between 145 and 275, then N SB PRB This can be 16 or 32.

[0325] A higher-level parameter (e.g., reportFreqConfiguration) may specify the frequency granularity of the CSI report. A single CSI report configuration may define the CSI report bandwidth as a subset of subbands of a BWP. The higher-level parameter may specify a subset of subbands in a single BWP. Subbands may be continuous or discontinuous. A single BWP may be a BWP on which CSI is reported. It is not expected that a single subband will have a lower frequency density than that of a single CSI-RS resource. A single CSI-RS resource may have a frequency density in a single subband. A single CSI-RS may be linked to a single CSI report configuration. The frequency density may be the density of each CSI-RS port (CSI port, antenna port) per PRB.

[0326] If a CSI-IM resource is linked to a CSI reporting configuration, it is not expected that a subband will be configured. Not all PRBs in a single subband have to have a CSI-IM Resource Element (RE).

[0327] The frequency granularity may be either wideband CQI or subband CQI reporting. If wideband CQI reporting is configured, a wideband CQI may be reported for the entire CSI reporting band. If subband CQI reporting is configured, one CQI may be reported for each subband within the CSI reporting band.

[0328] The frequency granularity may be full-band PMI or sub-band PMI reporting. If full-band PMI reporting is configured, one full-band PMI may be reported for the entire CSI reporting band. If sub-band PMI reporting is configured, one single wideband indication (i1) may be reported for the entire CSI reporting band, or one sub-band indication (i2) may be reported for each sub-band within the CSI reporting band.

[0329] If certain conditions are met, the frequency granularity may be full-band. These conditions may be that a full-band PMI report is set, a full-band CQI report is set, and the report quantity setting (reportQuantity) is set to CRI, RI, PMI, and CQI ('cri-RI-PMI-CQI'). These conditions may be that a full-band PMI report is set, a full-band CQI report is set, and the report quantity setting (reportQuantity) is set to CRI, LI, PMI, and CQI ('cri-LI-PMI-CQI'). These conditions may be that the report quantity setting (reportQuantity) is set to CRI, RI, and i1 ('cri-RI-i1'). If certain conditions are not met, the frequency granularity may be sub-band.

[0330] If one CSI reporting setting is configured for one BWP with 24 or fewer PRBs, it may be expected that the one CSI reporting setting has frequency granularity across the entire bandwidth.

[0331] One or N subbands may be configured. The size of the first subband is N, where N is the start PRB position of the BWP. start BWP,i The size of the Nth subband may be limited based on the BWP start PRB position and the BWP size.

[0332] Terminal device 1 may report CSI. If semi-persistent CSI reporting is configured and both the CSI-IM and NZP CSI-RS resources are configured as periodic or semi-persistent, terminal device 1 may report CSI. If aperiodic CSI reporting is configured and both the CSI-IM and NZP CSI-RS resources are configured as periodic, semi-persistent, or aperiodic, terminal device 1 may report CSI.

[0333] DCI formats 0_1 / 0_2 / 0_3 may trigger a CSI report. Terminal device 1 does not need to expect multiple CSI reports associated with the same CSI reporting setting to be triggered.

[0334] For aperiodic CSIs, each trigger state may be associated with one or more CSI reporting settings. Each trigger state may be set by a higher-level parameter (e.g., CSI-AperiodicTriggerState). Each CSI report may be linked to one or more CSI resource settings. Each CSI reporting setting may be linked to periodic, semi-permanent, or aperiodic CSI resource settings. Group-based reporting may not be configured for each CSI reporting setting.

[0335] If a single CSI resource setting is configured, that single CSI resource setting may correspond to channel measurements for L1-RSRP or channel / interference measurements for L1-SINR calculation. The single CSI resource setting may be provided by resourcesForChannelMeasurement.

[0336] When two CSI resource settings are configured, the first CSI resource setting may be for channel measurement, and the second CSI resource setting may be for interference measurement performed in CSI-IM or NZP CSI-RS. The first CSI resource setting may be provided by resourcesForChannelMeasurement. The second CSI resource setting may be provided by csi-IM-ResourcesForInterference or nzp-CSI-RS-ResourcesForInterference.

[0337] Three CSI resource settings may be configured. The first CSI resource setting may be for channel measurement. The second CSI resource setting may be for interference measurement using CSI-IM. The third CSI resource setting may be for interference measurement using NZP CSI-RS. The first CSI resource setting may be provided by resourcesForChannelMeasurement. The second CSI resource setting may be provided by csi-IM-ResourcesForInterference. The third CSI resource setting may be provided by nzp-CSI-RS-ResourcesForInterference. resourcesForChannelMeasurement, csi-IM-ResourcesForInterference, and nzp-CSI-RS-ResourcesForInterference may all be configured in a single CSI reporting setting.

[0338] For non-periodic CSI (CSI reporting) and for periodic and non-persistent CSI resource configurations, each trigger state may be associated with one or more CSI reporting configurations. Each CSI reporting configuration may be linked to a periodic or non-persistent CSI resource configuration. Group-based reporting may be configured for each CSI reporting configuration. If one CSI resource configuration is configured, that one CSI resource configuration may be for L1-RSRP measurement. In this case, the number of CSI-RS resource sets in the CSI resource configuration may be two.

[0339] For aperiodic CSI (CSI reporting) and for aperiodic CSI resource configuration, each trigger state may be associated with one or more CSI reporting configurations. Group-based reporting may be configured for each CSI reporting configuration. Each CSI reporting configuration may be associated with a first CSI-RS resource set and a second CSI-RS resource set for L1-RSRP measurement.

[0340] For semi-permanent or periodic CSI (CSI reporting), each CSI reporting setting may be linked to a periodic or semi-permanent CSI resource setting. If one CSI resource setting is set, that one CSI resource setting may be for channel measurements for L1-RSRP or for channel / interference measurements for L1-SINR. If two CSI resource settings are set, the first CSI resource setting may be for channel measurements, and the second CSI resource setting may be for interference measurements performed in CSI-IM. For L1-SINR calculations, the second CSI resource setting may be for interference measurements performed in CSI-IM or NZP CSI-RS.

[0341] If Type 2 is set in the codebook settings, the number of CSI-RS resources in the CSI-RS resource set for channel measurement in the CSI reporting settings may be 1.

[0342] In a single CSI resource configuration, more than 64 NZP CSI-RS resources and / or SS / PBCH block resources may not be expected. A single CSI resource configuration may be for channel measurement. In a CSI reporting configuration corresponding to a CSI resource configuration for channel measurement, the reporting quantity setting may be set to none, cri-RI-CQI, cri-RSRP, ssb-Index-RSRP, cri-SINR, ssb-Index-SINR, cri-RSRP-Index, ssb-Index-RSRP-Index, cri-SINR-Index, or ssb-Index-SINR-Index. When interference measurement is performed in CSI-IM, each CSI-RS resource for channel measurement may be associated with one CSI-IM resource. The number of CSI-RS resources for channel measurement may be equal to the number of CSI-IM resources.

[0343] In measurements other than L1-SINR measurements (e.g., CSI measurements), each NZP CSI-RS port configured for interference measurement may correspond to an interference transmission layer. In measurements other than L1-SINR measurements (e.g., CSI measurements), all interference transmission layers in the NZP CSI-RS ports may take EPRE into consideration. In L1-SINR measurements, a dedicated interference measurement resource may be configured. The total received power in the dedicated resource may correspond to the interference-to-noise ratio.

[0344] In a single CSI reporting configuration, the reportQuantity setting may be 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.

[0345] If "none" is set for the reporting volume setting, terminal device 1 does not need to report CSI.

[0346] If cri-RI-PMI-CQI or cri-RI-LI-PMI-CQI is set in the reporting quantity setting, terminal device 1 may report the first PMI. The first PMI may be a precoder matrix for each subband. The first PMI may be a precoder matrix for the entire CSI reporting band.

[0347] If cri-RI-i1 is set in the reporting amount setting, terminal device 1 may report a second PMI. The second PMI may consist of a single full-band instruction i1. Type 1 may be set in the codebook setting in the CSI reporting setting. The frequency granularity for PMI in the CSI reporting setting may be full-band.

[0348] If cri-RI-i1-CQI is set in the reporting quantity setting, terminal device 1 may report a third PMI. The third PMI may consist of a single full-band indication. The CQI may be calculated based on the third PMI. Terminal device 1 may report the CQI.

[0349] If cri-RI-CQI is set in the reporting quantity settings, terminal device 1 may report RI. Terminal device 1 may calculate CQI for one rank.

[0350] If the reporting quantity setting is set to cri-RSRP, ssb-Index-RSRP, cri-RSRP-Index, or ssb-Index-RSRP-Index, and group-based reporting is not set, terminal device 1 may report N different CRIs or SSBRIs for each CSI reporting setting. Furthermore, terminal device 1 may not be required to update the measurements. N may be determined by a higher-level parameter (e.g., nrofReportedRS).

[0351] If the reporting volume setting is set to cri-RSRP, ssb-Index-RSRP, cri-RSRP-Index, or ssb-Index-RSRP-Index, and group-based reporting is configured, terminal device 1 may report two different CRIs or SSBRIs for each CSI reporting setting. Furthermore, terminal device 1 may request updates of measurements for more than 64 CSI-RS / SSB resources. Terminal device 1 may receive CSI-RS / SSB resources simultaneously.

[0352] If the reporting volume setting is set to cri-SINR, ssb-Index-SINR, cri-SINR-Index, or ssb-Index-SINR-Index, and group-based reporting is not set, terminal device 1 may report N different CRIs or SSBRIs for each CSI reporting setting.

[0353] If the reporting volume setting is set to cri-SINR, ssb-Index-SINR, cri-SINR-Index, or ssb-Index-SINR-Index, and group-based reporting is set, terminal device 1 may report two different CRIs or SSBRIs for each CSI reporting setting.

[0354] If TDCP is set as the reporting quantity setting, terminal device 1 may report the amplitude and phase of the TDCP measurement.

[0355] If the reporting quantity setting includes cri-RSRP, cri-RI-PMI-CQI, cri-RI-i1, cri-RI-i1-CQI, cri-RI-CQI, cri-RI-LI-PMI-CQI, cri-SINR, or cri-SINR-Index, and K CSI-RS resources are set in the CSI-RS resource set for channel measurement, terminal device 1 may calculate CSI parameters other than CRI based on CRI. One CRI may correspond to one CSI-RS. For example, the (k+1)th entry of an NZP CSI-RS resource in the NZP CSI-RS resource set for channel measurement may correspond to the CRI value k. The (k+1)th entry of a CSI-IM resource in the CSI-IM resource set for interference measurement may correspond to the CRI value k. The (k+1)th entry of an NZP CSI-RS resource in the NZP CSI-RS resource set for interference measurement may correspond to the CRI value k. K may be greater than 1. If K is 2, each CSI-RS resource may have up to 16 CSI-RS ports (CSI ports, antenna ports). If K is 3 or greater and 8 or less, each CSI-RS resource may have up to 8 CSI-RS ports. If cri-RI-PMI-CQI is set in the reporting volume setting, type 2 does not need to be set in the codebook setting.

[0356] If the reporting quantity setting is set to ssb-Index-RSRP or ssb-Index-RSRP-Index, terminal device 1 may report the SSBRI. The (k+1)th entry of the CRI-SSB resource in the CSI-SSB resource set may correspond to the SSBRI value k.

[0357] If ssb-Index-SINR or ssb-Index-SINR-Index is set in the reporting quantity setting, terminal device 1 may calculate L1-SINR based on SSBRI. The (k+1)th entry of the CRI-SSB resource in the CSI-SSB resource set for channel measurement may correspond to the SSBRI value k. The (k+1)th entry of the CSI-IM resource in the CSI-IM resource set for interference measurement may correspond to the SSBRI value k. The (k+1)th entry of the NZP CSI-RS resource in the NZP CSI-RS resource set for interference measurement may correspond to the SSBRI value k.

[0358] If the reporting volume setting is set to cri-RSRP, cri-SINR, none, cri-RSRP-Index, or cri-SINR-Index, and one CSI reporting setting is linked to one aperiodic CSI resource setting, then it is not expected that more than 16 CSI-RS resources will be configured in one CSI-RS resource set within one CSI resource setting.

[0359] In an L1-RSRP calculation, CSI-RS resources, SS / PBCH block resources, or both CSI-RS and SS / PBCH block resources may be configured. An L1-RSRP calculation may have up to 16 CSI-RS resource sets, and each CSI-RS resource set may have up to 64 CSI-RS resources. The number of different CSI-RS resources across all CSI-RS resource sets may be 128 or less.

[0360] In L1-RSRP calculations, if one CRI or SSBRI is reported for each CSI reporting setting (for example, if nrofReportedRS is 1), the reported L1-RSRP value may be defined as 7 bits. The range of the L1-RSRP value may be from -140 dBm to -44 dBm. The L1-RSRP value may be given in 1 dB intervals.

[0361] In L1-RSRP calculations, if multiple CRIs or SSBRIs are reported for each CSI reporting setting (for example, if nrofReportedRS is 2 or more), the first value of the reported L1-RSRP may be defined with 7 bits, and the second value of the reported L1-RSRP may be defined with 4 bits. The range of the first value may be from -140 dBm to -44 dBm. The first value may be given in 1 dB intervals. The second value may be calculated as the difference between the first values. The second value may be given in 2 dB intervals.

[0362] When group-based reporting is configured, terminal device 1 may indicate one CSI-RS resource set. One CSI-RS resource set may be associated with the maximum value of L1-RSRP. The CRI or SSBRI of one CSI-RS resource set may be placed at the beginning.

[0363] Terminal device 1 may calculate L1-RSRP based on NZP CSI-RS or SS / PBCH blocks. For example, if no time limit is set, terminal device 1 may perform channel measurements based on SS / PBCH blocks or NZP CSI-RS for L1-RSRP calculation. For example, if a time limit is set, terminal device 1 may perform channel measurements based on the most recent opportunity in SS / PBCH blocks or NZP CSI-RS for L1-RSRP calculation.

[0364] In L1-SINR calculations, either or both of the NZP CSI-RS resource and / or the SS / PBCH block resource may be configured for channel measurement. In L1-SINR calculations, either the NZP CSI-RS resource or the CSI-IM resource may be configured for interference measurement.

[0365] For L1-SINR calculation and channel measurement, a CSI resource configuration may be set with up to 16 CSI-RS resource sets, and a total of 64 CSI-RS resources or SS / PBCH block resources may be set.

[0366] In L1-SINR calculations, if one CRI or SSBRI is reported for each CSI reporting setting (for example, if nrofReportedRS is 1), the reported L1-SINR value may be defined as 7 bits. The range of the L1-SINR value may be from -23 to 40 dB. The L1-SINR value may be given in 0.5 dB intervals.

[0367] In L1-SINR calculations, if multiple CRIs or SSBRIs are reported for each CSI reporting setting (for example, if nrofReportedRS is 2 or more), the first reported L1-SINR may be defined with 7 bits, and the second reported L1-SINR may be defined with 4 bits. The range of the first value may be from -23 dB to 40 dB. The first value may be given in 0.5 dB intervals. The second value may be calculated as the difference between the first values. The second value may be given in 1 dB intervals.

[0368] Aperiodic CSI reporting may correspond to aperiodic CSI-RS. In a CSI-RS resource set associated with aperiodic, periodic, or semi-persistent CSI resource settings, the trigger state for aperiodic CSI reporting settings may be set by a higher-level parameter (e.g., CSI-AperiodicTriggerStateList). The trigger state may be set for CSI resource settings for either channel measurement or interference measurement, or both.

[0369] In a non-periodic CSI reporting configuration, one set of trigger states may be configured by the upper layer. The trigger state may be associated with any one downlink BWP.

[0370] Terminal device 1 may receive DCIs with CSI request fields. It is not expected that two or more DCIs with CSI request fields having non-zero values ​​will be received in a single slot in a single cell.

[0371] In multiple aperiodic CSI-RS resource sets with the same trigger offset in the same trigger state, it is not necessary to expect different TCI states to be set for the same aperiodic CSI-RS resource ID.

[0372] It is not necessary to expect that two or more requests for aperiodic CSI reports will be received in a single slot within a single cell.

[0373] The trigger state may be initiated by the CSI request field in DCI. If all information bits in the CSI request field are set to zero, a CSI may not be requested.

[0374] The number of trigger states is 2^N TS If the value is -1 or greater, terminal device 1 may receive a subselection indication. The subselection indication has a maximum of 2^N code points in the CSI request field. TSIt may be used to map the trigger state of -1. TS This may also be the number of bits in the CSI request field.

[0375] When terminal device 1 transmits the first PUCCH in slot n, the mapping between the CSI request field and the trigger state may be applied after slot n+N. The first PUCCH may be a PUCCH accompanied by HARQ-ACK information corresponding to a PDSCH that transmits a subsettion indication.

[0376] The CSI request field may indicate a single trigger state. For example, the number of trigger states could be 2^N. TS If less than -1, the CSI request field may indicate one trigger state.

[0377] For each aperiodic CSI-RS resource in a set of CSI-RS resources associated with each triggering state (CSI triggering state), a first QCL setting and a first QCL type may be specified.

[0378] If a list of trigger states for aperiodic CSI (e.g., CSI-AperiodicTriggerStateList) is configured, and a single CSI resource configuration linked to a single CSI reporting configuration has multiple aperiodic CSI-RS resource sets, then one aperiodic CSI-RS resource set may be associated with one trigger state. In a single trigger state within a single CSI resource configuration, one CSI-IM / NZP CSI-RS resource set may be selected.

[0379] When aperiodic CSI reporting and aperiodic CSI-RS are used, one trigger offset (or, may be called, a CSI-RS offset) may be set in a single CSI-RS resource set (NZP CSI-RS resource set, CSI-IM resource set, or SS / PBCH block resource set). The trigger offset may be set by a higher-level parameter (e.g., aperiodicTriggeringOffset). The trigger offset may include a number of slots from 0 to N, where N is based on the subcarrier interval of the CSI-RS. The trigger offset for CSI-IM may follow the trigger offset for NZP CSI-RS for channel measurement.

[0380] Terminal device 1 may receive CSI-RS. Non-periodic CSI-RS may be transmitted in slot n+X. Slot n may be a slot containing a DCI that triggers the CSI-RS. X may be a trigger offset.

[0381] A non-periodic CSI-RS does not have to be transmitted before the first OFDM symbol. The first OFDM symbol may be a symbol that transmits a DCI that triggers the CSI-RS transmission. If a minimum scheduling offset limit is applied and the trigger offset is less than or equal to the minimum scheduling offset limit, it may not be expected to be triggered by the trigger condition indicated by the CSI request field in the DCI. The transmission of a CSI-RS may be triggered by the trigger condition indicated by the DCI request field in the DCI.

[0382] When interference measurements are performed in a non-periodic NZP CSI-RS, the trigger offset for the NZP CSI-RS used for interference measurements may be the same as the trigger offset for the NZP CSI-RS used for channel measurements.

[0383] It is not expected that multiple CSI reports triggered by different DCIs will be transmitted on a single carrier under the same OFDM symbol.

[0384] The scheduling offset between the last symbol of the PDCCH that transmits the DCI triggering the aperiodic CSI-RS resource and the first symbol of the aperiodic CSI-RS resource may be determined. If two PDCCH candidates exist, the later-terminating PDCCH candidate may be used to determine the scheduling offset. The last symbol of the earlier-terminating PDCCH candidate may be the same as or later than the first symbol of the aperiodic CSI-RS resource.

[0385] A semi-persistent CSI may correspond to a semi-persistent CSI-RS. In a semi-persistent CSI report in PUSCH, a set of trigger states may be set by a higher-level parameter (e.g., SemiPersistentOnPUSCH-TriggerStateList). The CSI request field in the DCI, scrambled by SP-CSI-RNTI, may activate one trigger state. Terminal device 1 does not need to expect to receive a first DCI that activates the first semi-persistent CSI report. The first semi-persistent CSI report may have the same CSI report setting ID as the second semi-persistent CSI report. The second semi-persistent CSI report may be activated by the second DCI. The first and second DCIs may be scrambled by SP-CSI-RNTI. Terminal device 1 may receive the second DCI before the first DCI.

[0386] In semi-persistent CSI reporting in PUCCH, the PUCCH resource used to send the CSI report may be configured by a higher-level parameter (reportConfigType). Semi-persistent CSI reporting in PUCCH may be activated by an activation command. The activation command may select one semi-persistent CSI reporting configuration. Terminal device 1 may receive a PDSCH that transmits the activation command. Terminal device 1 may send a PUCCH with HARQ-ACK information corresponding to the PDSCH in slot n. The selected semi-persistent CSI reporting configuration may be applied to slots n+N and beyond.

[0387] If a semi-persistent CSI resource setting is configured (for example, if resourceType is set to semiPersistent), and terminal device 1 receives an activation command, CSI-RS / CSI-IM transmissions may be applied from slot n+N for the CSI-RS resource set for channel measurement and the CSI-IM / NZP CSI-RS resource set for interference measurement. Terminal device 1 may also transmit a PUCCH with HARQ-ACK information to the PDSCH that transmits the command in slot n.

[0388] Terminal device 1 may receive a deactivation command. If a semi-persistent CSI resource setting is configured and terminal device 1 receives a deactivation command, the termination of CSI-RS / CSI-IM transmission may be applied from slot n+N. Terminal device 1 may send a PUCCH with HARQ-ACK information to the PDSCH that transmits the deactivation command in slot n.

[0389] A trigger state (e.g., SP-CSI triggering state) may be mapped to a code point in the CSI request field in DCI. Terminal device 1 may verify the PDCCH in DCI for activation or deactivation (release) of the semi-persistent CSI. For example, if the CRC in DCI format is scrambled with SP-CSI-RNTI, terminal device 1 may verify the PDCCH. For example, terminal device 1 may activate or deactivate the semi-persistent CSI based on a value set in a special field in DCI format.

[0390] Terminal device 1 may activate or deactivate the CSI reporting settings indicated by the DCI request field in DCI.

[0391] If a CSI resource setting (e.g., CSI-RS / CSI-IM resource setting, or ZP (Zero Power) CSI-RS resource set setting) is activated and the corresponding downlink BWP is active, the CSI resource setting may be considered. If a CSI resource setting (e.g., CSI-RS / CSI-IM resource setting, or ZP (Zero Power) CSI-RS resource set setting) is activated and the corresponding downlink BWP is inactive, the CSI resource setting may be suspended.

[0392] Terminal device 1 may report CQI. Terminal device 1 may calculate one CQI index. The modulation scheme, encoding, and transport block size of the PDSCH transport block may correspond to one CQI index. Terminal device 1 may receive the PDSCH transport block in such a way that it does not exceed the target error probability. The target error probability may be the error probability of the transport block. The target error probability may be 0.1 or 0.00001.

[0393] Terminal device 1 may report the PMI. Terminal device 1 may determine the PMI based on the number of antenna ports (number of CSI ports, number of CSI-RS ports) and the number of layers. The number of layers ν may be related to the RI. The PMI value corresponding to type 1 is i1∈i 1,1 i 1,2 i 1,3 i 1,4 And it may consist of part or all of i2. The PMI corresponding to type 1 may be the PMI when typeI-SinglePanel or typeI-MultiPanel is set in the codebook settings. The value of the PMI corresponding to type 2 is i1∈i 1,1 i 1,2 i 1,3,1 i 1,3,2 i 1,4,1 i 1,4,2And may consist of part or all of i2. A PMI corresponding to type 2 may also be a PMI when any of the following are set in the codebook settings: typeII, typeII-r16, typeII-PortSelection-r16, typeII-r17, typeII-PortSelection-r17, typeII-CJT-r18, typeII-CJT-PortSelection-r18, typeII-Doppler-r18, and typeII-Doppler-PortSelection-r18.

[0394] If the extended CSI port is not configured, the number of CSI ports may be 4, 8, 12, 16, 24, or 32. If the extended CSI port is configured, the number of CSI ports may be 48, 64, 96, or 128. Not configuring the extended CSI port may mean that the number of CSI ports is set to 4, 8, 12, 16, 24, or 32. Configuring the extended CSI port may mean that the number of CSI ports is set to 48, 64, 96, or 128.

[0395] One or more NZP CSI-RS resource sets may be configured by a CSI resource configuration (CSI-ResourceConfig). Each NZP CSI-RS resource set may consist of one or more CSI-RS resources. One or more parameters P may be set for some or all of the NZP CSI-RS resources, NZP CSI-RS resource sets, and CSI resource configurations.

[0396] One or more parameters P may include the ID of an NZP CSI-RS resource. The ID of an NZP CSI-RS resource may determine the identifier of the CSI-RS resource.

[0397] One or more parameters P may include a period and a slot offset. The period and slot offset may be used for periodic / semi-persistent CSI-RS. All CSI-RS resources in a single NZP CSI-RS resource set may have the same period.

[0398] One or more parameters P may include the number of antenna ports of the CSI-RS resource, the CDM (Code Domain Multiplexing) type, the OFDM symbol, and a first upper-layer parameter (e.g., resource mapping) that determines the subcarriers.

[0399] One or more parameters P may include a second higher-layer parameter that determines the number of antenna ports. The second higher-layer parameter may be set in the first higher-layer parameter.

[0400] One or more parameters P may include a third upper-layer parameter that determines the frequency density. The third upper-layer parameter may be set in the first upper-layer parameter. The third upper-layer parameter may determine the frequency density of each CSI port (antenna port, CSI-RS port) for each PRB. The third upper-layer parameter may be set to 0.5even, 0.5odd, 1, or 3.

[0401] One or more parameters P may include a fourth higher-level parameter that determines the CDM type. The fourth higher-level parameter may be set in the first higher-level parameter. The fourth higher-level parameter may determine the value and pattern of the CDM.

[0402] One or more parameters P may include parameters that determine the Energy per Resource element (EPRE) ratio for PDSCH and NZP CSI-RS.

[0403] One or more parameters P may include parameters that determine the power ratio per RE of the NZP CSI-RS and SS / PBCH block.

[0404] One or more parameters P may include a scrambled ID. The length of the scrambled ID may be 10 bits.

[0405] One or more parameters P may include a BWP ID. The BWP ID may be set in the CSI resource configuration. The BWP ID may determine the BWP where the CSI-RS is located.

[0406] One or more parameters P may include repeat settings. Repeat settings may be set in the CSI-RS resource set. In an NZP CSI-RS resource set for repeating (an NZP CSI-RS resource set in which repeat settings are set), it may be assumed that the CSI-RS resources in the NZP CSI-RS resource set are transmitted with the same downlink spatial domain transmit filter. Repeat settings may be set if the reporting amount setting is set to cri-RSRP, cri-SINR, cri-RSRP-Index, cri-SINR-Index, or none.

[0407] One or more parameters P may include QCL information for periodic CSI-RS. The QCL information may include a reference to the TCI state. The TCI state may indicate the QCL source RS and the QCL type.

[0408] One or more parameters P may include a TRS (Tracking Reference Signal) setting. The TRS setting may be configured in the CSI-RS resource set. In an NZP CSI-RS resource set for TRS (an NZP CSI-RS resource set in which the TRS setting is configured), the antenna ports of the NZP CSI-RS resources in the NZP CSI-RS resource set may be the same.

[0409] For all CSI-RS resources in a single CSI-RS resource set, the same frequency density and the same number of antenna ports may be configured. For all CSI-RS resources in a single CSI-RS resource set, the same starting RB (Resource Block) position, the same number of RBs, and the same CDM type may be configured.

[0410] The bandwidth and starting CRB (Common resource block) index of a CSI-RS resource may be determined by the starting RB location and number of RBs. The starting RB location and number of RBs may be determined by higher-level parameters (e.g., startingRB and nrofRBs). The starting RB location and number of RBs may be set as integer multiples of 4 RBs. The reference location for the starting RB location may be CRB0. The bandwidth (number of RBs) of a CSI-RS resource may be 24 RBs or more, and greater than or equal to the BWP size.

[0411] One or more CSI-IM resource sets may be configured. Each CSI-IM resource set may consist of one or more CSI-IM resources. One or more parameters Q may be set for each CSI-IM resource.

[0412] One or more parameters Q may include a CSI-IM resource ID. One or more parameters Q may include a subcarrier position k within one slot of the CSI-IM resource. CSI-IM It may include parameters that determine the OFDM symbol position l in one slot of the CSI-IM resource. One or more parameters Q are the OFDM symbol position l in one slot of the CSI-IM resource. CSI-IM The parameters may include those that determine the period and slot offset for periodic / semi-permanent CSI-IMs. The parameters may include those that determine the bandwidth of the CSI-IM.

[0413] A CSI-IM resource may consist of four REs. For example, in Pattern 1, the CSI-IM resource is (k CSI-IM , l CSI-IM ), (kCSI-IM , l CSI-IM (+1), (k CSI-IM +1, l CSI-IM ), and (k CSI-IM +1, l CSI-IM It may consist of REs corresponding to +1). For example, in pattern 2, the CSI-IM resource is (k CSI-IM , l CSI-IM ), (k CSI-IM +1, l CSI-IM ), (k CSI-IM +2, l CSI-IM ), and (k CSI-IM +2, l CSI-IM It may also consist of REs corresponding to +1).

[0414] The CSI may be calculated based on a CSI reference resource. The CSI reference resource in the frequency domain may be a Physical Resource Block (PRB) corresponding to the bandwidth in which the CSI is calculated. The CSI reference resource in the time domain may be a single slot. This single slot may be N slots ahead of the slot in which the CSI is reported. The N slots may be determined based on delay time.

[0415] Terminal device 1 may calculate and report the CQI (CQI Index) based on the CSI reference resource. Terminal device 1 may assume one or more scenarios for calculating the CQI.

[0416] One or more situations may be that two OFDM symbols are occupied by the control signal. One or more situations may be that the number of PDSCH and DMRS symbols is 12. One or more situations may be that the same subcarrier spacing as for PDSCH reception is used. One or more situations may be that the CSI reference resource uses the same CP length and subcarrier spacing as PDSCH. One or more situations may be that there is no RE used for PBCH, PSS, or SSS. One or more situations may be that the Redundancy Version is 0. One or more situations may be that there is no RE allocated for NZP CSI-RS and ZP CSI-RS. One or more situations may be that the maximum number of Front-loaded DMRS symbols set is used. One or more situations may be that the Additional number of DMRS symbols set is used. One or more situations may be that the OFDM symbols for PDSCH do not include DMRS. One of the situations in which one or more PRBs are bundled together may be that two PRBs are combined.

[0417] In one or more situations, the signal of the ν layer in PDSCH may be multiplied by a precoder corresponding to PMI. The number of layers may be up to 8.

[0418] Terminal device 1 may report CSI using PUSCH. Depending on the decoding of the DCI format that triggers the trigger state, terminal device 1 may report aperiodic CSI using PUSCH.

[0419] The DCI format may schedule two pushes. In this case, aperiodic CSI reporting may be performed in the second push. The DCI format may schedule three or more pushes. In this case, aperiodic CSI reporting may be performed in the second to last push.

[0420] Non-periodic CSI reports in PUSCH may correspond to full-band and sub-band frequency granularity.

[0421] Terminal device 1 may report a semi-persistent CSI in PUSCH in response to decoding a DCI format that activates a trigger state. The CSI request field in the DCI format may indicate a trigger state to activate or deactivate.

[0422] Non-periodic CSI reports in PUSCH may be multiplexed with uplink data in PUSCH. Semi-persistent CSI reports in PUSCH do not need to be expected to be multiplexed with uplink data in PUSCH.

[0423] When PMI is reported (or feedback) in PUSCH, the CSI report may consist of Part 1 and Part 2. Part 1 may be a fixed-size payload to indicate the number of information bits in Part 2. Part 1 may be appended to or transmitted before Part 2.

[0424] Part 1 may include CSIs corresponding to CSI parameters associated with the first codeword (transport block). Part 1 may include RI and CRI. Part 2 may include CSIs corresponding to CSI parameters associated with the second codeword. Part 2 may include PMI and LI.

[0425] Terminal device 1 may report CSI using PUCCH. CSI reporting in PUCCH may be configured by a higher layer. Multiple periodic CSI reports corresponding to multiple CSI reporting settings may be configured by a higher layer.

[0426] Terminal device 1 may report a semi-persistent CSI in PUCCH. The semi-persistent CSI report may be applied from slot n+N. In slot n, a PUCCH may be sent with HARQ-ACK information corresponding to a PDSCH that transmits an activation command. The activation command may include one or more CSI reporting settings.

[0427] CSI reports may be associated with a priority value. iCSI (y,k,c,s) is Pri iCSI (y,k,c,s) = 2・N cells ・M s ・y+N cells ・M s ・k+M s - May be given by c + s. Here, y may be y=0 when non-periodic CSI reports are transmitted in PUSCH, y=1 when semi-permanent CSI reports are transmitted in PUSCH, y=2 when semi-permanent CSI reports are transmitted in PUCCH, and y=3 when periodic CSI reports are transmitted in PUCCH. Here, k may be k=0 when the CSI report includes L1-RSRP or L1-SINR, and k=1 when the CSI report does not include L1-RSRP or L1-SINR. Here, c is the serving cell index, N cells This may be the value of the upper-level parameter maxNrofServingCells, where s is the report configuration identifier (reportConfigID), M s This can also be the value of the upper-level parameter maxNrofCSI-ReportConfigurations.

[0428] If the priority value associated with the first CSI report is lower than the priority value associated with the second CSI report, the first CSI report may be considered to have a higher priority than the second CSI report.

[0429] Terminal device 1 may report CSI. CSI may include some or all of PMI, RI, LI, CQI, CRI, SSBRI, RSRP, SINR, CapabilityIndex, and TDCP. CSI may also be a collective term for PMI, RI, LI, CQI, and CRI.

[0430] The bit size of the PMI (Precoding Matrix Indicator) may be determined based at least on the number of antenna ports and the number of layers.

[0431] The bit size of the RI (Rank Indicator) may be determined based on at least the number of antenna ports and the number of ranks to be set. The bit size of the LI (Layer Indicator) may be determined based on at least the number of ranks. The bit size of the CRI (CSI-RS resource indicator) may be determined based on the number of CSI-RS resources in the CSI-RS resource set.

[0432] DCI formats 1_0 / 1_1 / 1_2 may be used for scheduling PDSCH. The Bandwidth Part Indicator (BWP) field may be included in either or both DCI format 1_1 and DCI format 1_2. The number of information bits constituting the BWP indicator field may be determined based on the number of DL BWPs. The TPC command (TPC command for scheduled PUCCH) field may be included in either or both DCI format 1_1 and DCI format 1_2. The Second TPC command (Second TPC command for scheduled PUCCH) field may be included in either or both DCI format 1_1 and DCI format 1_2. For example, if the upper-level parameter SecondTPCFieldDCI is set, the Second TPC command (Second TPC command for scheduled PUCCH) field may be included in DCI format 1_1.

[0433] The TCI (Transmission configuration indication) field may be included in either or both of DCI format 1_1 and DCI format 1_2. For example, if a higher-level parameter is set, the TCI (Transmission configuration indication) field may be included in either or both of DCI format 1_1 and DCI format 1_2. For example, if the higher-level parameter tci-PresentInDCI is set, the TCI (Transmission configuration indication) field may be included in either or both of DCI format 1_1 and DCI format 1_2. One or two TCI states may be indicated by the DCI format. One or more (e.g., two) TCI states may be indicated by the TCI field in the DCI format.

[0434] DCI formats 0_0 / 0_1 / 0_2 may be used for scheduling PUSCH. The Bandwidth Part Indicator (BWP) field may be included in part or all of DCI formats 0_1 and 0_2. The number of information bits constituting the BWP indicator field may be determined based on the number of UL BWPs. The TPC command (TPC command for scheduled PUSCH) field may be included in either or both of DCI formats 0_1 and 0_2. The Second TPC command (Second TPC command for scheduled PUSCH) field may be included in either or both of DCI formats 0_1 and 0_2. For example, if the upper-level parameter SecondTPCFieldDCI is set, the Second TPC command (Second TPC command for scheduled PUSCH) field may be included in DCI format 1_1.

[0435] The CSI-RS (Channel State Information Reference Signal) may be either a ZP (zero power) CSI-RS or an NZP (non-zero-power) CSI-RS.

[0436] The CSI-RS sequence may be r(m). r(m) may be determined by a pseudorandom sequence (e.g., a Gold code). The pseudorandom sequence consists of the OFDM symbol index in one slot and the slot index n in one radio frame. μ s,f , and may be initialized based on a scrambled ID.

[0437] In each CSI-RS, the CSI-RS sequence r(m) is a Resource element (RE) (k,l) p,μ It may be mapped to β. For example, the CSI-RS sequence r(m) is β CSIRS *w f (k')*w t (l')*r(m) is a resource element (RE) (k,l) p,μ It may be mapped to: k is the subcarrier position, l is the OFDM symbol position, p is the antenna port (CSI port), and μ is the subcarrier spacing setting. β CSIRS is the scaling factor, w f (k') is FD-OCC (Frequency domain orthogonal cover code), w t (l') may also be TD-OCC (Time domain orthogonal cover code).

[0438] In ZP CSI-RS, β CSIRS It may be 0. In NZP CSI-RS, β CSIRS β can be greater than 0. CSIRS This may be determined based on higher-level parameters (e.g., powerControlOffsetSS).

[0439] In r(m), m is floor(n*α)+k'+floor((k bar *ρ) / N RB SC ) is also acceptable. * may also be multiplication.

[0440] ρ may be the frequency density. If the number of antenna ports is 1, α may be ρ. If the number of antenna ports is 2 or more, α may be 2ρ. If ρ is 1, each antenna port may be mapped to every 1RB. If ρ is 0.5, each antenna port may be mapped to every 2RB. If ρ is an even number of 0.5, each antenna port may be mapped to an even-numbered RB every 2RB. If ρ is an odd number of 0.5, each antenna port may be mapped to an odd-numbered RB every 2RB.

[0441] The subcarrier position k is determined by the PRB position n and the subcarrier position setting k. bar This may be determined by the FD-OCC (Frequency Domain-Orthogonal Cover Code) index k'.

[0442] Subcarrier position k=0 may correspond to subcarrier 0 in CRB0.

[0443] The PRB position n may be a value between 0 and N-1. N may be the bandwidth of the CSI-RS resource (e.g., the number of RBs: nrofRBs).

[0444] Subcarrier position setting k bar This may determine the subcarrier position within one slot. Subcarrier position setting k bar This may be determined based on the number of antenna ports, frequency density, and CDM type. Subcarrier position setting k bar k may be a subcarrier position within a single RB. bar is, k i It is also acceptable. i-1f(i) may be f(i), which may be the bit number of the i-th bit in the bitmap that is set to 1. The bitmap may be provided by higher-layer parameters (e.g., frequencyDomainAllocation). The size of the bitmap may be determined at least on the number of antenna ports. f(i) may be repeated for every ceil(1 / ρ) RBs.

[0445] The FD-OCC index k' may be determined by the CDM type. If the CDM type is set to "No CDM", k' may be 0. If the CDM type is set to a CDM of length 2 in the frequency domain (FD), k' may be 0 or 1.

[0446] OFDM symbol position l is OFDM symbol position setting l bar This may be determined by the TD-OCC (Time domain-Orthogonal cover code) index l'.

[0447] OFDM Symbol Positioning bar This may determine the symbol position within a single slot. OFDM Symbol Position Setting l bar This may be determined based on the number of antenna ports, frequency density, and CDM type. bar l0 and l1 may be one or both. l0 may be determined by a first upper-level parameter (e.g., firstOFDMSymbolInTimeDomain). l1 may be determined by a second upper-level parameter (e.g., firstOFDMSymbolInTimeDomain2). l0 may be an integer value from 0 to 13. l1 may be an integer value from 2 to 12.

[0448] The TD-OCC index l' may be determined by the CDM type. If the CDM type is set to No CDM, l' may be 0. If the CDM type is set to a CDM of length 2 in the Time Domain (TD), l' may be 0 and 1. If the CDM type is set to a CDM of length 4 in the Time Domain, l ’ This can be 0, 1, 2, or 3.

[0449] The antenna port p may be 3000 + s + j * L. The sequence index s may be an integer value from 0 to L-1. The CDM group size L may be any of 1, 2, 4, and 8. The CDM group size L may be determined based on the CDM type. For example, the CDM group size L may be the product of the length of the TD-OCC and the length of the FD-OCC. The CDM group index j may be an integer value from 0 to N / L-1. N may be the number of antenna ports (number of CSI-RS ports).

[0450] If the FD-OCC index k' is 0, w f (k') may be 0. If the FD-OCC index k' is 0 or 1, [w f (0) w f (1) may be the vectors [+1 +1] and [+1 -1]. If the TD-OCC index l' is 0, w t (l') may be 0. If the TD-OCC index l' is 0 or 1, [w t (0) w t (1) may be the vectors [+1 +1] and [+1 -1]. If the TD-OCC index l' is 0, 1, 2, and 3, then [w t (0) w t (1) w t (2) w t(3) may be the vectors [+1 +1 + 1 +1], [+1 -1 +1 -1], [+1 +1 -1 -1], and [+1 -1 -1 +1]. The sequence index s may be indexed first with FD-OCC and then with TD-OCC. For example, if a CDM type is set to FD-OCC of length 2 and TD-OCC of length 4, the sequence index s=0 is [w f (0) w f (1)]=[+1 +1]and[w t (0) w t (1) w t (2) w t (3) = [+1 +1 + 1 +1], and the sequence index s=1 is [w f (0) w f (1)] = [+1 -1] and [w t (0) w t (1) w t (2) w t (3) = [+1 +1 + 1 +1], and the sequence index s=2 is [w f (0) w f (1)]=[+1 +1]and[w t (0) w t (1) w t (2) w t (3) = [+1 -1 + 1 -1], and the sequence index s=3 is [w f (0) w f (1)] = [+1 -1] and [w t (0) w t (1) w t (2) w t (3) = [+1 -1 + 1 -1], and the sequence index s=4 is [w f (0) w f (1)]=[+1 +1]and[w t (0) w t (1) w t (2) w t (3) = [+1 +1 -1 -1], and the sequence index s=5 is [w f (0) w f (1)]=[+1 -1]and[wt (0) w t (1) w t (2) w t (3) = [+1 +1 -1 -1], and the sequence index s=6 is [w f (0) w f (1)]=[+1 +1]and[w t (0) w t (1) w t (2) w t (3) = [+1 -1 -1 +1], and the sequence index s=7 is [w f (0) w f (1)]=[+1 -1]and[w t (0) w t (1) w t (2) w t (3) = [+1 -1 -1 +1] is also acceptable.

[0451] CDM groups may be indexed first by frequency resources and then by time resources. For example, if the number of antenna ports is 32 and the CDM type is set to FD-OCC (fd-CDM2) of length 2, the CDM group index j may be indexed in the order of time-frequency resources (k0,l0), (k1,l0), (k2,l0), (k3,l0), (k0,l0+1), (k1,l0+1), (k2,l0+1), (k3,l0+1), (k0,l1), (k1,l1), (k2,l1), (k3,l1), (k0,l1+1), (k1,l1+1), (k2,l1+1), and (k0,l1+1).

[0452] Terminal device 1 does not need to expect to receive CSI-RS and DMRS in the same RE. Antenna ports within a single CSI-RS resource may be QCL with respect to Type A. Terminal device 1 may expect that antenna ports within a single CSI-RS resource have an average gain.

[0453] The settings for scheduling requests may be configured by higher-level parameters (e.g., SchedulingRequestResourceConfig). The settings for scheduling requests may determine a single PUCCH resource. A single PUCCH resource may correspond to PUCCH format 0 or PUCCH format 1. The settings for scheduling requests may determine the period T and offset ΔT for the PUCCH that transmits the scheduling request. The period may be represented by OFDM symbols or slots. Terminal device 1 may determine the opportunity to send a scheduling request in the PUCCH. mod(n f *N frame,μ slot +n μ s,f If -ΔT, T) is 0, the transmission opportunity is slot number n μ s,f It may also be a corresponding slot. The settings for the scheduling request may determine the transmission period. The transmission period may be the number of OFDM symbols.

[0454] The uplink grant configured for a PUSCH transmission may be set by a higher-tier parameter (e.g., configuredGrantConfig). The PUSCH resource (resource allocation) may also be set by a higher-tier parameter. The higher-tier parameter may be associated with a single uplink BWP. A PUSCH transmission may correspond to a single configured uplink grant. The higher-tier parameter may determine the time-domain resource allocation.

[0455] If terminal device 1 is scheduled to send a PUSCH in which no transport block is placed and one or more CSI reports are placed, according to the CSI request field in DCI, the value m in the Time domain resource assignment field of DCI may provide row number m+1 for the assigned table (pusch-TimeDomainAllocationList). The referenced row number may define the start and length indicator value SLIV, or directly the start symbol S and the assigned length L. The referenced row number may also define the PUSCH placement type and K2 value to apply in the PUSCH transmission.

[0456] The K2 value is K2 = max j Y j It may be determined by (m+1). The K2 value may also be a slot offset value. Here Y j ,j=0,…,N Rep -1 is N Rep Y is a corresponding list entry for a higher-level parameter in the CSI Report Configuration (CSI-ReportConfig) for configuring a triggered CSI report. j (m+1) Y includes the omitted CSI reporting setting for inactive DL BWP. jIt may also be the (m+1)th entry. The corresponding list entry for the upper-level parameter may be reportSlotOffsetListDCI-0-2 or reportSlotOffsetListDCI-0-2-r17 if PUSCH is scheduled by DCI format 0_2 and reportSlotOffsetListDCI-0-2 or reportSlotOffsetListDCI-0-2-r17 is set. The corresponding list entry for the upper-level parameter may be reportSlotOffsetListDCI-0-1 or reportSlotOffsetListDCI-0-1-r17 if PUSCH is scheduled by DCI format 0_1 ​​or DCI format 0_3 and reportSlotOffsetListDCI-0-1 or reportSlotOffsetListDCI-0-1-r17 is set. The corresponding list entry for the upper-level parameter may otherwise be reportSlotOffsetList or reportSlotOffsetList-r17. Terminal device 1 does not need to expect (m+1) to be greater than 16.

[0457] The slot from which terminal device 1 transmits PUSCH may be determined by a slot offset value. For example, slot K from which terminal device 1 transmits PUSCH. s This may be determined by K2. Terminal device 1 may apply the slot offset value indicated in DCI to the transmission of PUSCH.

[0458] For terminal device 1, where a CSI-ReportConfig is set with the upper-layer parameter eventType-r19 set, the L1-RSRP value may be determined for a periodic reference signal with the same periodicity set. The upper-layer parameter eventType-r19 may be set to event1, event2, or event7. The first L1-RSRP value may be determined for each reference signal set by the upper-layer parameter newBeamResourceSet-r19. The first L1-RSRP value may be determined for each occurrence of at least one of the same reference signals set by the upper-layer parameter newBeamResourceSet-r19. The second L1-RSRP value may be determined for a reference signal in an indicated TCI state, or for an SS / PBCH block that is a reference signal and QCL in an indicated TCI state. newBeamResourceSet-r19 may be the same component carrier (CC) as the CSI reporting configuration (CSI-ReportConfig), or in a component carrier provided by the carrier in the CSI reporting configuration. If two reference signals (QCL RS) exist in the indicated TCI state, the reference signal in the indicated TCI state may be the reference signal for QCL-TypeD.

[0459] If the reference signal set by newBeamResourceSet-r19 is a CSI-RS in an NZP-CSI-RS-ResourceSet where repetition is set, the second L1-RSRP value may be determined based on the reference signal in the indicated TCI state. The indicated TCI state may be the same component carrier as the CSI reporting setting, or the component carrier indicated in the CSI reporting setting.

[0460] If the reference signal set by newBeamResourceSet-r19 is a certain CSI-SSB-ResourceSet, the second L1-RSRP value may be determined based on the reference signal and the SS / PBCH block which is the QCL in the indicated TCI state. The indicated TCI state may be the same component carrier as in the CSI reporting setting, or in the component carrier indicated in the CSI reporting setting.

[0461] If the first L1-RSRP value becomes eventThreshold-r19 greater than the second L1-RSRP value at least eventInstanceCount-r19 times, terminal device 1 may send PUCCH format 0 or PUCCH format 1 in the PUCCH resource configured by firstPUCCHResourceConfig-UEIBR-r19 in the CSI reporting configuration (CSI-ReportConfig).

[0462] Terminal device 1 may report a CSI in a single reporting instance. The CSI may include nrofReportedRS-UEIBR-r19 CRIs or SSBRIs and their absolute L1-RSRPs or differential L1-RSRPs. The nrofReportedRS-UEIBR-r19 CRIs or SSBRIs and their absolute L1-RSRPs or differential L1-RSRPs may correspond to reference signals provided by newBeamResourceSet-r19, which includes at least one reference signal that satisfies the event. If enabledCurrentBeamReport-r19 is set, the CSI may include a reference signal in the indicated TCI state, or a differential L1-RSRP corresponding to the reference signal in the indicated TCI state and an SSB that is QCL.

[0463] Terminal device 1 may perform a CSI report in the PUSCH indicated by DCI format 0_1 / 0_2 if reportTransmissionMode-r19 is set to ModeA and the CSI trigger state related to the CSI report setting (CSI-ReportConfig) is indicated in the CSI request field of DCI format 0_1 / 0_2. DCI format 0_1 / 0_2 may also be received at the PDCCH reception opportunity after the completion of the PUCCH transmitted by the PUCCH resource.

[0464] If reportTransmissionMode-r19 is set to ModeB, terminal device 1 may perform a CSI report in type 1CG-PUSCH configured by configuredResourceForSecondChannelOfModeB-r19. The CSI may be transmitted in the PUCCH resource at the first available transmission opportunity after the numOfSymbold-ModeB-r19 symbol following the end of the PUCCH transmission. The periodicity of the PUCCH resource and the type 1CG-PUSCH resource may be the same. CG-PUSCH does not need to transmit UL-SCH.

[0465] The value of the event instance counter e may be set for any of the reference signals set by newBeamResourceSet-r19. The counter may operate from 0 to eventInstanceCount-r19. If the indicated TCI state of the measured reference signal is updated, the value of the event instance counter e may be set to 0.

[0466] Terminal device 1 does not need to expect that the reference signal in the instructed TCI state is on a different component carrier (CC) than the reference signal set by newBeamResourceSetEvent2-r19.

[0467] Terminal device 1 does not need to expect that a CSI trigger state associated with one or more CSI reporting settings in which the higher-layer parameter eventType-r19 is set will be further associated with other CSI reporting settings in which the higher-layer parameter eventType-r19 is not set.

[0468] For CSI reporting in PUSCH, two UCI bit sequences may be generated. The two bit sequences are a (1) 0, a (1) 1, a (1) 2, a (1) 3,…,a (1) A (1) -1 and, a (2) 0, a (2) 1, a (2) 2, a (2) 3,…,a (2) A (2) -1 This may also be the case. The CSI field of all CSI reports is a, in the order of CSI report #1, CSI report #2, ..., CSI report #n. (1) UCI bit sequence a starting from 0 (1) 0, a (1) 1, a (1) 2, a (1) 3,…,a (1) A (1) -1 It may be placed in the following order: CSI report #1, CSI report #2, ..., CSI report #n. (2) UCI bit sequence a starting from 0 (2) 0, a (2) 1, a (2) 2, a (2) 3,…,a (2) A (2) -1They may be placed in the following order. The order of CSI report #1, CSI report #2, ..., CSI report #n may correspond to the ascending order of the CSI report priority values ​​for each CSI report.

[0469] First UCI bit sequence a (1) 0, a (1) 1, a (1) 2, a (1) 3,…,a (1) A (1) -1 This may be a UCI bit sequence for CSI Part 1. If a CSI report is a CSI report for reporting any of the following: CRI / RSRP, SSBRI / RSRP, CRI / RSRP / CapabilityIndex, SSBRI / RSRP / CapabilityIndex, inter-cell SSBRI / RSRP, CRI / SINR, SSBRI / SINR, CRI / SINR / CapabilityIndex, SSBRI / SINR / CapabilityIndex, group-based CRI / RSRP, group-based SSBRI / RSRP, or SSBRI / RSRP for L1 / L2-triggered mobility, then the first UCI bit sequence a (1) 0, a (1) 1, a (1) 2, a (1) 3,…,a (1) A (1) -1 It may be placed in [location]. If a CSI report is a report for CRI / RSRP, SSBRI / RSRP, CRI / SINR, SSBRI / SINR, or TDCP, the procedures for CSI Part I may apply.

[0470] Second UCI bit sequence a (2) 0, a (2) 1, a (2) 2, a (2) 3,…,a (2) A (2) -1This may be a UCI bit sequence for CSI Part II. If CSI Part II exists for a CSI report, it may be placed in a second UCI bit sequence. For example, if CSI Part II exists for CSI report #1, it may be placed in the bit sequence for CSI report #1 in the second UCI bit sequence. If a CSI report is for reporting any of the following, CRI / RSRP, SSBRI / RSRP, CRI / RSRP / CapabilityIndex, SSBRI / RSRP / CapabilityIndex, inter-cell SSBRI / RSRP, CRI / SINR, SSBRI / SINR, CRI / SINR / CapabilityIndex, SSBRI / SINR / CapabilityIndex, group-based CRI / RSRP, group-based SSBRI / RSRP, or SSBRI / RSRP for L1 / L2-triggered mobility, CSI Part II may not exist.

[0471] If a CSI report is a CSI for a beam report originating from a UE, that CSI may include some or all of the following: a CSI report setting indicator, a CRI or SSBRI, an RSRP, a differential RSRP, a condition satisfaction indicator, or a differential RSRP for the current beam.

[0472] The CSI reporting configuration indicator i may indicate the (i+1)th CSI reporting configuration among those associated with the PUCCH that triggers beam reporting. The CSI reporting configurations associated with the PUCCH that trigger beam reporting may be sorted in ascending order of their CSI reporting configuration identifiers (CSI-ReportConfigID).

[0473] If the higher-level parameter PresenceOfConfditionMeetingIndicator is set on terminal device 1, the condition satisfaction indicator may be included in the CSI.

[0474] The differential RSRP for the current beam may be included in the CSI only if the upper-layer parameter enabledCurrentBeamReport-r19 is set on terminal device 1.

[0475] Terminal device 1 may transmit a CSI report for an event-triggered report. The problem is that in an event-triggered report, terminal device 1 needs to transmit only one CSI report from among multiple CSI reports. The following means may be used to solve the above problem. Figure 9 shows an example in which only one CSI report is transmitted for N requests for CSI reports in an event-triggered report according to one aspect of this embodiment.

[0476] Terminal device 1 may have a first upper-level parameter set. The first upper-level parameter may be a parameter relating to information for setting CSI reporting settings. The first upper-level parameter may be a CSI reporting setting. For example, the first upper-level parameter may be CSI-ReportConfig. Terminal device 1 may have N first upper-level parameters set. N may be an integer of 1 or more. CSI reporting settings may be set for CSI reporting. N CSI reporting settings may be set for N CSI reports.

[0477] Terminal device 1 may have a second upper-layer parameter set. The second upper-layer parameter may be a parameter relating to information for setting the aperiodic trigger state list 930. The second upper-layer parameter may be the aperiodic trigger state list 930. For example, the second upper-layer parameter may be CSI-AperiodicTriggerStateList.

[0478] The aperiodic trigger state list 930 may hold M trigger states, where M is an integer greater than or equal to 1. N CSI reporting settings may be associated with one of the M trigger states. All CSI reporting settings associated with a single trigger state may be CSI reporting settings for aperiodic CSI reporting. For example, if the reporting setting type in a CSI reporting setting is set to 'aperiodic', it may be a CSI reporting setting for aperiodic CSI reporting.

[0479] Terminal device 1 may transmit CSI920. Transmitting a CSI may also mean transmitting a CSI report, reporting a CSI, or transmitting a CSI. Terminal device 1 may transmit an uplink physical channel. For example, terminal device 1 may transmit a CSI on an uplink physical channel. For example, terminal device 1 may transmit an uplink physical channel with a CSI. For example, terminal device 1 may transmit a CSI using an uplink physical channel. Transmitting a CSI may also mean transmitting an uplink physical channel with a CSI. For example, terminal device 1 may transmit a CSI in the UCI. For example, terminal device 1 may transmit a PUSCH on which the UCI is located.

[0480] Terminal device 1 may receive DCI1000. Terminal device 1 may receive DCI in DCI format 0_1 ​​or DCI format 0_2. Terminal device 1 may receive PDCCH on which DCI is located. DCI1000 may schedule an uplink physical channel. DCI1000 may include a CSI request field. DCI1000 may include a time-domain resource allocation field. DCI1000 may schedule an uplink physical channel. The CSI request field in DCI1000 may indicate transmission of the uplink physical channel. The CSI request field in DCI1000 may indicate CSI reporting settings. The time-domain resource allocation field in DCI1000 may schedule an uplink physical channel. The time-domain resource allocation field in DCI1000 may indicate an opportunity to transmit the uplink physical channel.

[0481] A CSI request field in DCI1000 may indicate a single trigger state. A CSI request field in DCI1000 may be associated with a single trigger state. A CSI request field in DCI1000 may indicate a single trigger state in the aperiodic trigger state list. A CSI request field in DCI1000 indicating a single trigger state may mean that the trigger state is triggered. A CSI request field indicating a single trigger state may mean that all CSI reporting settings associated with the indicated single trigger state are triggered. For example, if a CSI request field indicates a single trigger state, N associated CSI reporting settings may be triggered. For example, if a CSI request field indicates a single trigger state, N associated CSI reports may be triggered. When a certain trigger state is triggered, terminal device 1 may perform CSI reporting based on all associated CSI reporting settings. For example, when a certain trigger state is triggered, terminal device 1 may send N CSI reports based on N associated CSI reporting settings.

[0482] The CSI request field in DCI1000 may indicate a single trigger state. This single indicated trigger state may be a trigger state for an event-triggered report. N CSI reporting settings may be associated with this single indicated trigger state. If the single indicated trigger state is a trigger state for an event-triggered report, all N associated CSI reporting settings may be CSI reporting settings for an event-triggered report. If the single indicated trigger state is not a trigger state for an event-triggered report, all N associated CSI reporting settings may not be CSI reporting settings for an event-triggered report. A CSI reporting setting for an event-triggered report may include a higher-level parameter for an event-triggered report. For example, this higher-level parameter may be eventType-r19. For example, this higher-level parameter may be reportTransmissionMode-r19. Being a CSI reporting setting for an event-triggered report may mean including a higher-level parameter for an event-triggered report. If all CSI reporting settings associated with a certain trigger state are CSI reporting settings for event-triggered reports, then a certain trigger state may also be a trigger state for event-triggered reports. A trigger state for an event-triggered report does not need to be associated with any CSI reporting settings other than those for event-triggered reports. Being an event-triggered report may mean that it is a beam report driven by terminal device 1, or that it is a beam report triggered by terminal device 1.

[0483] If a CSI reporting setting is a CSI reporting setting for event-triggered reporting, terminal device 1 may receive a downlink reference signal 900. Terminal device 1 may receive a downlink reference signal 900. Terminal device 1 may periodically receive a downlink reference signal 900. The downlink reference signal may be a CSI-RS or an SS / PBCH block. The CSI-RS may be an NZP-CS-RS. The downlink reference signal 900 may be a reference signal in an indicated TCI state, or an SS / PBCH block that is a reference signal and QCL in an indicated TCI state.

[0484] If a CSI reporting setting is a CSI reporting setting for event-triggered reporting, terminal device 1 may receive S downlink reference signals {901, ..., 901 + S - 1}. Terminal device 1 may receive some or all of the downlink reference signals {901, 902, 903, 904, 905, 906, 907, 908}. Terminal device 1 may periodically receive S downlink reference signals {901, ..., 901 + S - 1}. Terminal device 1 may receive S downlink reference signals {901, ..., 901 + S - 1}. S may be an integer greater than or equal to 1. Terminal device 1 may receive some or all of the S downlink reference signals. The S downlink reference signals {901, ..., 901 + S - 1} may correspond to different resource IDs (CSI-RS resource IDs or SSB indices). The downlink reference signals {901, ..., 901+S-1} may be included in the downlink reference signal set 910. The downlink reference signal set 910 may be a CSI-RS-ResourceSet or a CSI-SSB-ResourceSet. The downlink reference signal set 910 may be a resource set included in a higher-layer parameter. The downlink reference signal set 910 may be set in the CSI reporting settings. For example, the downlink reference signal set 910 may be the higher-layer parameter newBeamResourceSet-r19. For example, the downlink reference signal set 910 may be the higher-layer parameter resourceForChannelMeasurement.

[0485] If a CSI reporting setting is for event-triggered reporting, terminal device 1 may measure or determine the L1-RSRP. Terminal device 1 may determine the L1-RSRP associated with the downlink reference signal 900 and the downlink reference signal set 910. For example, terminal device 1 may determine the L1-RSRP for each occurrence of the downlink reference signal 900. For example, terminal device 1 may determine S L1-RSRPs for each occurrence of the S downlink reference signals included in the downlink reference signal set 910.

[0486] If a CSI reporting setting is a CSI reporting setting for event-triggered reporting, terminal device 1 may detect event 980. Terminal device 1 may detect event 980 based on L1-RSRP. Terminal device 1 may detect event 980 based on L1-RSRP associated with S downlink reference signals included in the downlink reference signal set 910. Detecting an event may mean that at least one of the S downlink reference signals included in the downlink reference signal set 910 that is associated with downlink reference signals satisfies event condition 990. For example, event condition 990 may mean that at least one of the S first L1-RSRP associated with the downlink reference signal set 910 is greater than a certain threshold at least C times than a second L1-RSRP associated with the downlink reference signal 900. C and the certain threshold may be set in the CSI reporting setting. For example, C may be the upper-layer parameter eventInstanceCount-r19. For example, the certain threshold may be the upper-layer parameter eventThreshold-r19. If the downlink reference signal set 910 is an NZP-CSI-RS-ResourceSet with repetition set, the downlink reference signal 900 may be a reference signal in the indicated TCI state. If the downlink reference signal set 910 is a CSI-SSB-ResourceSet, the downlink reference signal 900 may be a reference signal in the indicated TCI state and an SS / PBCH block which is QCL.

[0487] If a CSI reporting configuration is a CSI reporting configuration for event-triggered reporting, terminal device 1 may send a PUCCH. Terminal device 1 may send a PUCCH. Terminal device 1 may send a PUCCH to trigger beam reporting. Terminal device 1 may send a PUCCH to instruct beam reporting. Terminal device 1 may send PUCCH format 0 or PUCCH format 1. Terminal device 1 may send a PUCCH in a PUCCH resource configured by a higher-layer parameter. Terminal device 1 may send a PUCCH in a PUCCH resource configured in a CSI reporting configuration. For example, the higher-layer parameter may be firstPUCCHResourceConfig-r19. Terminal device 1 may send a PUCCH if event condition 990 is met.

[0488] If a CSI reporting setting is a CSI reporting setting for event-triggered reporting, terminal device 1 may receive DCI1000. If transmission means A is set in the CSI reporting setting, terminal device 1 may receive DCI1000. If ModeA is set in the upper layer parameter of the CSI reporting setting, terminal device 1 may receive DCI1000. For example, the upper layer parameter may be eventType-r19. Terminal device 1 may receive DCI1000 only after sending a PUCCH that triggers beam reporting. Terminal device 1 may receive DCI1000 only after sending a PUCCH when event condition 990 is met.

[0489] If a CSI report is based on CSI reporting settings for an event-triggered report, that CSI report may include some or all of the following: a CSI reporting setting indicator, R CSI resource indicators (CRIs), or SSB resource indicators (SSBRIs), one absolute L1-RSRP value, and R-1 differential L1-RSRP values, R condition satisfaction indicators, and a differential L1-RSRP value for the current beam.

[0490] The CSI reporting setting indicator may indicate which of all CSI reporting settings related to the trigger state for an event-triggered report the CSI report is related to. For example, if the CSI reporting setting indicator for a CSI report shows i, that CSI report may be based on the i+1th CSI reporting setting. All CSI reporting settings related to the trigger state for an event-triggered report may be all CSI reporting settings related to the PUCCH that triggers the beam report.

[0491] R may be an integer greater than or equal to 1. R may be set in the CSI reporting settings. R may be set in the higher-level parameters. For example, R may be nrofReportedRS-UEIBR-r19. A CRI or SSBRI may indicate which CSI-RS or SS / PBCH block in the downlink reference signal set it is related to. For example, if a CRI indicates i, that CRI may correspond to the i+1th CSI-RS in the downlink reference signal set. Of the R reference signals corresponding to CRIs or SSBRIs, at least one may satisfy event condition 990.

[0492] One absolute L1-RSRP value and R-1 differential L1-RSRP values ​​may correspond to R CSIs or SSBRIs. One absolute L1-RSRP value may correspond to the largest L1-RSRP value among the R L1-RSRP values. R-1 differential L1-RSRP values ​​may correspond to the difference between each of the R-1 L1-RSRP values ​​(excluding the largest L1-RSRP value) and the largest L1-RSRP value.

[0493] R condition satisfaction indicators may correspond to R CRIs or SSBRIs. A condition satisfaction indicator may be 1 bit. If a condition satisfaction indicator shows 0, the corresponding CRI or SSBRI does not necessarily satisfy event condition 990. If a condition satisfaction indicator shows 1, the corresponding CRI or SSBRI may satisfy event condition 990. For example, if the i-th condition satisfaction indicator shows 1, the i-th CRI or SSBRI may be a reference signal that satisfies event condition 990. If a higher-level parameter is set in the CSI reporting configuration, the associated CSI report may include R condition satisfaction indicators. If a higher-level parameter is not set in the CSI reporting configuration, the associated CSI report does not necessarily include R condition satisfaction indicators. For example, the higher-level parameter may be a PresenceOfConfitionMeetingIndicator.

[0494] The differential RSRP value for the current beam may be the reference signal in the indicated TCI state, or the L1-RSRP value for the SS / PBCH block which is the reference signal and QCL in the indicated TCI state. If a higher layer parameter is set in the CSI reporting settings, the associated CSI report may include the differential L1-RSRP value for the current beam. If a higher layer parameter is not set in the CSI reporting settings, the associated CSI report may not include the differential L1-RSRP value for the current beam. For example, the higher layer parameter may be enabledCurrentBeamReport-r19.

[0495] If a trigger state for an event-triggered report is triggered in DCI1000, terminal device 1 may transmit only one of the N CSI reports associated with the indicated trigger state. For example, terminal device 1 may transmit only the relevant CSI report if the downlink reference signal set 910 set in a certain CSI report setting satisfies the event condition 990 set in that CSI report setting. For example, if terminal device 1 has transmitted a PUCCH for a beam report associated with a certain CSI report setting, terminal device 1 may transmit only the CSI report associated with that CSI report setting. In this case, terminal device 1 may include only one of the N CSI reports associated with the indicated trigger state in the UCI. In this case, terminal device 1 may transmit one CSI report based on only one of the N CSI report settings associated with the indicated trigger state. In this case, terminal device 1 may determine the bit sequence for the UCI based on only one of the N CSI reports associated with the indicated trigger state. In this case, terminal device 1 may generate a bit sequence for UCI based on only one of the N CSI reports associated with the indicated trigger state. In this case, terminal device 1 may omit CSI reports other than one. In this case, terminal device 1 may omit CSI report settings other than one. In this case, terminal device 1 may not include CSI reports other than one in the UCI. In this case, terminal device 1 may not generate a bit sequence for UCI for CSI reports other than one.

[0496] The CSI reporting settings may include a slot offset list. The slot offset list may be the higher-level parameter reportSlotOffsetList, or repootSlotOffsetListDCI-0-1, or reportSlotOffsetListDCI-0-2. An offset value may be applied to send CSI920. The offset value may be the offset value from receiving DCI1000 to sending CSI920. The offset value may be the offset value from receiving PDCCH to sending PUSCH. The offset value may be a slot offset value. The slot offset list may be a list of allowed slot offsets. The offset value may be selected in the triggering DCI. The offset value may be selected by the time domain resource allocation field in the DCI.

[0497] DCI1000 may include a CSI request field and a time-domain resource allocation field. The time-domain resource allocation field in DCI1000 may indicate a row index corresponding to a slot offset list. The time-domain resource allocation field in DCI1000 may indicate one slot offset value from the slot offset list. If the CSI request field triggers N CSI reporting settings, the time-domain resource allocation field may indicate one slot offset value from each CSI reporting setting. If the CSI request field triggers N CSI reporting settings, the time-domain resource allocation field may indicate N slot offset values. If the trigger state triggered by DCI1000 is a trigger state for an event-triggered report, the time-domain resource allocation field may indicate N slot offset values. If the trigger state triggered by DCI1000 is a trigger state for an event-triggered report, the time domain resource allocation field may specify N slot offset values, including one CSI reporting setting and any omitted CSI reporting settings.

[0498] Terminal device 1 may send a PUSCH based on the slot offset value indicated by the time domain resource allocation field. If the time domain resource allocation field indicates N slot offset values, terminal device 1 may send a PUSCH based on the maximum value among the N slot offset values. When the DCI1000 triggers a trigger state for an event-triggered report, the time domain resource allocation field indicates N slot offset values, and terminal device 1 may send a PUSCH based on the maximum value among the N slot offset values.

[0499] A single CSI report may be associated with a single CSI report priority value. The CSI report priority value may be based on the report type of the CSI report, the uplink physical channel in which it is placed, the cell identifier, and the CSI report configuration identifier. The CSI report priority value may be a non-negative integer. A lower CSI report priority value may be considered to have higher priority. For example, a CSI report priority value of 0 may have a higher priority than a CSI report priority value of 1.

[0500] When N CSI reports are placed in the UCI, terminal device 1 may arrange the N CSI reports in ascending order of their CSI report priority values. When generating a bit sequence for the UCI based on N CSI reports, terminal device 1 may generate the bit sequence for the UCI by arranging the bit sequences for the N CSI reports in ascending order of their CSI report priority values. When the DCI 1000 triggers a trigger state for an event-triggered report, terminal device 1 may determine the bit sequence for the UCI based on only one CSI report out of the N CSI reports arranged in ascending order of their CSI report priority values. When the DCI 1000 triggers a trigger state for an event-triggered report, terminal device 1 may not arrange the CSI reports in ascending order of their CSI report priority values ​​and may determine the bit sequence for the UCI based on only one CSI report. When determining the UCI bit sequence for one CSI report, terminal device 1 may determine the bit sequence for the UCI based on only one CSI report. When determining the UCI bit sequence for a single CSI report, terminal device 1 may determine the bit sequence for the UCI based on only one CSI report, without sorting them in ascending order of CSI report priority values. When determining the UCI bit sequence for a single CSI report, terminal device 1 may sort them in ascending order of CSI report priority values ​​and determine the bit sequence for the UCI based on only one CSI report.

[0501] Terminal device 1 may select one of the N CSI reports. For example, if a trigger condition for an event-triggered report is triggered, terminal device 1 may select one of the N CSI reports. For example, if some or all of the N CSI reports correspond to event-triggered reports, terminal device 1 may select one of the N CSI reports. If one of the N CSI reports is selected, the N CSI reports do not have to be based on a CSI report priority value. If multiple CSI reports are selected, the N CSI reports may be sorted in ascending order of their CSI report priority values.

[0502] The following describes various aspects of the apparatus according to one embodiment of this invention.

[0503] The program running in the base station device 3 and terminal device 1 according to one aspect of the present invention may be a program that controls the CPU (Central Processing Unit) and the like (a program that makes the computer function) in order to realize the functions of the above embodiment according to one aspect of the present invention. The information handled by these devices is temporarily stored in RAM (Random Access Memory) during processing, and then stored in various ROMs such as Flash ROM (Read Only Memory) or HDD (Hard Disk Drive), and read, modified, and written by the CPU as needed.

[0504] Furthermore, the terminal device 1 and a part of the base station device 3 in the above-described embodiment may be implemented using a computer. In that case, the program for implementing this control function may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be read by a computer system and executed.

[0505] Furthermore, the term "computer system" as used herein refers to a computer system built into terminal device 1 or base station device 3, and includes hardware such as the OS and peripheral devices. In addition, "computer-readable recording medium" refers to portable media such as flexible disks, magneto-optical disks, ROMs, CD-ROMs, and storage devices such as hard disks built into computer systems.

[0506] Furthermore, "computer-readable recording media" may include those that dynamically hold programs for a short period of time, such as communication lines used when transmitting programs via networks such as the Internet or communication lines such as telephone lines, as well as those that hold programs for a certain period of time, such as volatile memory inside a computer system that acts as a server or client in such cases. In addition, the above-mentioned program may be for the purpose of realizing some of the functions described above, and may also be a program that can realize the above-mentioned functions in combination with a program already recorded in the computer system.

[0507] Furthermore, the base station device 3 in the above-described embodiment can also be realized as an assembly (device group) composed of multiple devices. Each device constituting the device group may have some or all of the functions or functional blocks of the base station device 3 related to the above-described embodiment. The device group only needs to have a complete set of the functions or functional blocks of the base station device 3. In addition, the terminal device 1 related to the above-described embodiment can also communicate with the base station device as an assembly.

[0508] Furthermore, the base station device 3 in the above-described embodiment may be EUTRAN (Evolved Universal Terrestrial Radio Access Network) and / or NG-RAN (NextGen RAN, NR RAN). Also, the base station device 3 in the above-described embodiment may have some or all of the functions of a higher-level node for eNodeB and / or gNB.

[0509] Furthermore, some or all of the terminal device 1 and base station device 3 in the above-described embodiment may be implemented as LSIs, which are typically integrated circuits, or as chipsets. Each functional block of the terminal device 1 and base station device 3 may be individually chipped, or some or all of them may be integrated into a single chip. In addition, the method of implementing the integrated circuit is not limited to LSIs; it may also be implemented using dedicated circuits or general-purpose processors. Moreover, if advances in semiconductor technology lead to the emergence of integrated circuit technologies that can replace LSIs, it is also possible to use integrated circuits based on those technologies.

[0510] Furthermore, although the above-described embodiment mentions a terminal device as an example of a communication device, the present invention is not limited to this and can also be applied to stationary or non-movable electronic devices installed indoors or outdoors, such as terminal devices or communication devices for AV equipment, kitchen equipment, cleaning and washing machines, air conditioning equipment, office equipment, vending machines, and other household appliances.

[0511] While embodiments of this invention have been described in detail above with reference to the drawings, the specific configuration is not limited to these embodiments, and design modifications and the like that do not depart from the gist of this invention are also included. Furthermore, various modifications are possible within the scope of the claims for one aspect of the present invention, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. In addition, configurations in which elements described in each of the above embodiments that produce similar effects are substituted for each other are also included.

[0512] One aspect of the present invention can be used, for example, in communication systems, communication equipment (e.g., mobile phone devices, base station devices, wireless LAN devices, or sensor devices), integrated circuits (e.g., communication chips), or programs.

[0513] 1 (1A, 1B, 1C) Terminal device 3 Base station device 10, 30 Wireless transceiver unit 10a, 30a Wireless transmitter unit 10b, 30b Wireless receiver unit 11, 31 Antenna unit 12, 32 RF unit 13, 33 Baseband unit 14, 34 Upper layer processing unit 15, 35 Media access control layer processing unit 16, 36 Wireless resource control layer processing unit 91, 92, 93, 94 Search area set 300 Component carrier 301 Primary cell 302, 303 Secondary cell 700 Set of resource elements for PSS 710, 711, 712, 713 Set of resource elements for PBCH and DMRS for PBCH 720 Set of resource elements for SSS 3000 Point 3001, 3002 Resource grid 3003, 3004 BWP 3011, 3012, 3013, 3014 Offset 3100, 3200 Common Resource Block Set 900, 901, 902, 903, 904, 905, 906, 907, 908 Downlink Reference Signal 910 Downlink Reference Signal Set 920 CSI 930 CSI Aperiodic Trigger State List 980 Event 990 Event Condition 1000 DCI

Claims

1. A terminal device comprising: an upper layer processing unit that receives N first upper layer parameters and a second upper layer parameter; a receiving unit that receives a PDCCH in which downlink control information (DCI) is placed; and a transmitting unit that transmits a PUSCH in which uplink control information (UCI) is placed, wherein N is an integer of 1 or more; each of the N first upper layer parameters is a parameter for setting one CSI report setting; the second upper layer parameter is a parameter for setting an aperiodic trigger state list; each of the N CSI report settings is set for one CSI report; the DCI includes a CSI request field; the CSI request field is associated with one trigger state from the aperiodic trigger state list; the one trigger state is associated with the N CSI report settings; and if the one trigger state is a trigger state for an event-triggered report, then only one CSI report from the N CSI reports is included in the UCI.

2. The terminal device according to claim 1, wherein each of the N CSI reporting settings includes information for setting up one slot offset list, the DCI further includes a time domain resource allocation field, and when the one trigger state is a trigger state for an event-triggered report, the time domain resource allocation field indicates one slot offset from each of the N slot offset lists, and the transmitting unit transmits the PUSCH based on the maximum value among the N indicated slot offsets.

3. The system comprises a top-layer processing unit that receives N first top-layer parameters and a second top-layer parameter, a receiving unit that receives a PDCCH in which downlink control information (DCI) is placed, and a transmitting unit that transmits a PUSCH in which uplink control information (UCI) is placed, wherein N is an integer of 1 or more, each of the N first top-layer parameters is a parameter for setting one CSI report setting, the second top-layer parameter is a parameter for setting an aperiodic trigger state list, each of the N CSI report settings is set for one CSI report, each of the N CSI reports is associated with one CSI report priority value, the DCI includes a CSI request field, the CSI request field is associated with one trigger state from the aperiodic trigger state list, and the one trigger state is associated with the N CSI report settings. A terminal device that determines the bit sequence for the UCI based on only one CSI report out of N CSI reports arranged in ascending order of the CSI report priority values, where the one trigger state is a trigger state for an event-triggered report.

4. A base station device comprising: an upper layer processing unit that transmits N first upper layer parameters and a second upper layer parameter; a transmitting unit that transmits a PDCCH in which downlink control information (DCI) is placed; and a receiving unit that receives a PUSCH in which uplink control information (UCI) is placed, wherein N is an integer of 1 or more; each of the N first upper layer parameters is a parameter for setting one CSI report setting; the second upper layer parameter is a parameter for setting an aperiodic trigger state list; each of the N CSI report settings is set for one CSI report; the DCI includes a CSI request field; the CSI request field is associated with one trigger state from the aperiodic trigger state list; the one trigger state is associated with the N CSI report settings; and if the one trigger state is a trigger state for an event-triggered report, then only one CSI report from the N CSI reports is included in the UCI.

5. The base station device according to claim 4, wherein each of the N CSI reporting settings includes information for setting up one slot offset list, the DCI further includes a time-domain resource allocation field, and if the one trigger state is a trigger state for an event-triggered report, the time-domain resource allocation field indicates one slot offset from each of the N slot offset lists, and the receiving unit receives the PUSCH based on the maximum value among the N indicated slot offsets.

Images