Terminal device and base station device

Abstract

A terminal device includes: a receiving unit for receiving N CSI-RS; and a transmitting unit for transmitting CSI, linking CSI resource settings for the N CSI-RS with CSI report settings for the CSI, wherein the CSI is composed of at least N-1 frequency differences, one of the N CSI-RS is a reference CSI-RS, and the N-1 frequency differences are respectively the difference between a frequency associated with the reference CSI-RS and a frequency associated with one of the N CSI-RS other than the reference CSI-RS.

Description

Technical Field

[0001] This invention relates to terminal devices and base station devices.

[0002] This application claims priority to Japanese Patent Application No. 2024-021508, filed on February 15, 2024, the contents of which are incorporated herein by reference. Background Technology

[0003] In the third generation partnership program (3GPP: 3 rd The Generation Partnership Project studied radio access methods and wireless networks for cellular mobile communication (hereinafter also referred to as "Long Term Evolution (LTE)" or "Evolved Universal Terrestrial Radio Access (EUTRA)"). 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 that uses multiple base station equipment configured in a cell-like structure to cover an area. A single base station equipment can manage multiple serving cells.

[0004] Within 3GPP, research was conducted on the next-generation standard (NR: New Radio) in order to make recommendations to IMT (International Mobile Telecommunication)-2020, the standard for next-generation mobile communication systems developed by the International Telecommunication Union (ITU) (Non-Patent Document 1). NR was required to meet the requirements of three hypothetical scenarios within a single technology framework: eMBB (enhanced Mobile Broadband), mMTC (massive Machine-Type Communication), and URLLC (Ultra-Reliable and Low-Latency Communication).

[0005] In 3GPP, the expansion of services supported by NR has been studied (Non-Patent Document 2, Non-Patent Document 3 and Non-Patent Document 4).

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

[0007] The problem the invention aims to solve The present invention provides a terminal device for efficient communication, a communication method for the terminal device, a base station device for efficient communication, and a communication method for the base station device.

[0008] Solution for solving the problem (1) The first aspect of the present invention is a terminal device comprising: a receiving unit for receiving N CSI-RS; and a transmitting unit for transmitting CSI, wherein CSI resource settings for the N CSI-RS are linked to CSI report settings for the CSI, wherein the CSI is composed of at least N-1 frequency differences, one of the N CSI-RS is a reference CSI-RS, and the N-1 frequency differences are the difference between a frequency associated with the reference CSI-RS and a frequency associated with one of the N CSI-RS other than the reference CSI-RS.

[0009] (2) Furthermore, a second aspect of the present invention is a base station apparatus comprising: a transmitting unit for transmitting N CSI-RS; and a receiving unit for receiving CSI, wherein CSI resource settings for the N CSI-RS are linked to CSI report settings for the CSI, wherein the CSI is composed of at least N-1 frequency differences, one of the N CSI-RS is a reference CSI-RS, and the N-1 frequency differences are respectively the difference between the frequency associated with the reference CSI-RS and the frequency associated with one of the N CSI-RS other than the reference CSI-RS.

[0010] Invention Effects According to the present invention, the terminal device can perform communication efficiently. Furthermore, the base station device can perform communication efficiently. Attached Figure Description

[0011] Figure 1 This is a conceptual diagram of a wireless communication system according to one embodiment of this invention.

[0012] Figure 2 This represents a scheme in this embodiment where the subcarrier spacing is set to μ and the number of OFDM symbols N per time slot. slot symb And an example of the relationship set by CP (cyclic Prefix).

[0013] Figure 3 This is a diagram illustrating an example of a method for constructing a resource grid according to one embodiment of this invention.

[0014] Figure 4 This is a diagram illustrating an example of the configuration of a resource grid 3001 according to one embodiment of this invention.

[0015] Figure 5 This is a schematic block diagram illustrating a configuration example of a base station device 3 according to one embodiment of this invention.

[0016] Figure 6 This is a schematic block diagram illustrating a configuration example of a terminal device 1 according to one embodiment of this invention.

[0017] Figure 7 This is a diagram illustrating an example of the configuration of the SS / PBCH block in one embodiment of this invention.

[0018] Figure 8 This is a diagram illustrating an example of the monitoring opportunities for a set of search regions in one embodiment of this invention.

[0019] Figure 9This is a diagram representing an example of a CSI report illustrating one aspect of this implementation. Detailed Implementation

[0020] The embodiments of the present invention will be described below.

[0021] `floor(C)` can be a function that rounds down a real number C. For example, `floor(C)` can be a function that outputs the largest integer not exceeding C. `ceil(D)` can be a function that rounds up a real number D. For example, `ceil(D)` can be a function that outputs the smallest integer not less than D. `mod(E, F)` can be a function that outputs the remainder when E is divided by F. `mod(E, F)` can also be a function that outputs the value corresponding to the remainder when E is divided by F. `exp(G) = e^G`. Here, e is the Napier number. `H^I` represents H raised to the power of I. `max(J, K)` is a function that outputs the maximum value between J and K. When J and K are equal, `max(J, K)` outputs either J or K. `min(L, M)` is a function that outputs the maximum value between L and M. When L and M are equal, `min(L, M)` outputs either L or M. `round(N)` is a function that outputs the integer value closest to N. " indicates multiplication.

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

[0023] An OFDM symbol can be a term that includes a CP appended to the OFDM symbol. That is, an OFDM symbol can be constituted as including that OFDM symbol and a CP appended to that OFDM symbol.

[0024] Figure 1 This is a conceptual diagram of a wireless communication system according to one embodiment of this invention. Figure 1 In this case, the wireless communication system is configured to include at least terminal devices 1A to 1C and base station device 3 (BS#3). Hereinafter, terminal devices 1A to 1C are also referred to as terminal device 1 (UE#1).

[0025] The base station device 3 may be configured to include one or more transmitting devices (or transmitting points, transceivers, or receivers). When the base station device 3 is composed of multiple transmitting devices, these multiple transmitting devices may be configured in different locations.

[0026] Base station device 3 can provide one or more serving cells. A serving cell can be defined as a collection of resources used for wireless communication. Furthermore, a serving cell is also referred to as a cell.

[0027] A serving cell can be configured to include one or both of a downlink component carrier and an uplink component carrier. A serving cell can also 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 collectively referred to as component carriers.

[0028] For example, a resource grid can be provided for each component carrier. Furthermore, a resource grid can also be provided for each set of subcarrier spacing configurations μ for a component carrier. Here, the subcarrier spacing configuration μ is also referred to as a parameter set (numerology). For example, a resource grid can be provided for a set of antenna ports p, subcarrier spacing configurations μ, and transmission directions x.

[0029] Resource grid includes N size，μ grid，x N RB sc There are 1 subcarrier. The resource grid originates from the common resource block N. start，μ grid，x Begin. Additionally, public resource block N start，μ grid，x Also known as the reference point of the resource grid.

[0030] Resource grid includes N subframe，μ symb OFDM symbols.

[0031] The subscript 'x' added to the parameters associated with the resource grid indicates the transmission direction. For example, the subscript 'x' can be used to represent either a downlink or an uplink.

[0032] N size，μ grid，x Set the offset represented by parameters provided by the RRC layer (e.g., the parameter CarrierBandwidth). N start，μ grid，x This refers to the bandwidth setting represented by parameters provided by the RRC layer (e.g., the parameter OffsetToCarrier). The offset setting and bandwidth setting are settings used to construct an SCS-specific carrier.

[0033] For a given subcarrier spacing, the subcarrier spacing (SCS) Δf can be Δf=2. μ 15kHz. The subcarrier spacing μ can be any one of 0, 1, 2, 3 or 4.

[0034] Figure 2 This represents the subcarrier spacing setting μ and the number of OFDM symbols N per time slot in one embodiment of this scheme. slot symb And an example of the relationship defined by CP (cyclic prefix). Figure 2 In A, for example, when the subcarrier spacing μ is set to 2 and the CP is set to normal CP (normal cyclic prefix), N slot symb =14, N frame，μ slot =40, N subframe，μ slot =4. Furthermore, in Figure 2 In B, for example, when the subcarrier spacing μ is set to 2 and CP is set to extended CP (extended cyclic prefix), N slot symb =12, N frame，μ slot =40, N subframe，μ slot =4.

[0035] Time unit (T)c It can be used to represent the length of time. The time unit is T. c It is T c =1 / (Δf max N f ). Δf max =480kHz. N f =4096. The constant κ is κ=Δf max N f / (Δf) ref N f，ref ) = 64. Δf ref It's 15kHz. N f，ref It is 2048.

[0036] The transmission of signals in the downlink and / or the transmission of signals in the uplink can be carried out by a length of T. f It is composed of radio frames (system frames, frames) (organized into). T f =(Δf max N f / 100) T s =10ms. The radio frame consists of 10 subframes. The length of each subframe is T. sf =(Δf max N f / 1000) T s =1ms. The number of OFDM symbols in each subframe is N. subframe，μ symb =N slot symb N subframe，μ slot The uplink radio frames (uplink frames, uplink timing) can be T-ordered ahead of the downlink radio frames (downlink frames, downlink timing). TA T TA This can also be referred to as scheduled advance.

[0037] OFDM symbols are time-domain units of a communication method. For example, an OFDM symbol can be a time-domain unit of CP-OFDM. Furthermore, an OFDM symbol can be a time-domain unit of DFT-s-OFDM.

[0038] A time slot can be configured to include multiple OFDM symbols. For example, a time slot can consist of N consecutive symbols. slot symb It consists of several OFDM symbols. For example, in a standard CP configuration, it can be N. slot symb=14. Furthermore, in a standard CP setting, it can be N. slot symb =12.

[0039] The number and index of the time slots included in a subframe can be given for setting the subcarrier interval μ. For example, the time slot index n μ s It can be in the subframe from 0 to N subframe，μ slot Integer values ​​within the range of -1 are given in ascending order. The number and index of time slots included in the radio frame can also be given for setting the subcarrier spacing μ. Additionally, the time slot index n... μ s，f It can also be in the wireless frame from 0 to N frame，μ slot Integer values ​​within the range of -1 are given in ascending order.

[0040] Figure 3 This is a diagram illustrating an example of a method for constructing a resource grid according to one embodiment of this invention. Figure 3 The horizontal axis represents the frequency domain. Figure 3 The diagram shows an example of the resource grid configuration for subcarrier spacing μ1 in component carrier 300 and an example of the resource grid configuration for subcarrier spacing μ2 in that component carrier. In this way, one or more subcarrier spacings can be set for a given component carrier. Figure 3 In this embodiment, it is assumed that μ1 = μ2 - 1, but the various schemes of this embodiment are not limited to the condition that μ1 = μ2 - 1.

[0041] Component carrier 300 is a frequency band with a specified width in the frequency domain.

[0042] Point 3000 is an identifier used to identify a specific subcarrier. Point 3000 is also known as point A. The Common Resource Block (CRB) set 3100 is a collection of common resource blocks for setting the subcarrier spacing μ1.

[0043] Public resource block set 3100 includes public resource block 3000. Figure 3 The black monochrome block in the public resource block set 3100 is also called the reference point of the public resource block set 3100. The reference point of the public resource block set 3100 can also be the public resource block with index 0 in the public resource block set 3100.

[0044] 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. Offset 3011 is represented by the number of common resource blocks with a subcarrier spacing of μ1. Resource grid 3001 includes N starting from the reference point of resource grid 3001. size，μ grid1，x A public resource block.

[0045] Offset 3013 is the distance from the reference point of resource grid 3001 to the reference point of BWP (BandWidth Part) 3003 at index i1 (N). start，μ BWP，i1 The offset of ).

[0046] The common resource block set 3200 is a set of common resource blocks with a subcarrier spacing of μ2.

[0047] The public resource block set 3200 includes the public resource block at point 3000. Figure 3 The black monochrome block in the public resource block set 3200 (also known as the reference point of the public resource block set 3200) is also called the reference point of the public resource block set 3200. The reference point of the public resource block set 3200 can also be the public resource block with index 0 in the public resource block set 3200.

[0048] Offset 3012 is the offset from the reference point of the common resource block set 3200 to the reference point of the resource grid 3002. Offset 3012 is represented by the number of common resource blocks for subcarrier spacing μ2. Resource grid 3002 includes N starting from the reference point of resource grid 3002. size，μ grid2，x A public resource block.

[0049] Offset 3014 is the distance from the reference point of resource grid 3002 to the reference point of BWP3004 at index i2 (N). start，μ BWP，i2 The offset of ).

[0050] Figure 4 This is a diagram illustrating an example of the configuration of a resource grid 3001 according to one embodiment of this invention. Figure 4 In the resource grid, the horizontal axis represents the OFDM symbol index. sym The vertical axis represents the subcarrier index k. sc Resource grid 3001 includes N size，μ grid1，x N RB sc N subcarriers, including N subframe，μ symb One OFDM symbol. Within the resource grid, via subcarrier index k sc and OFDM symbol index l symA defined resource is called a resource element (RE).

[0051] A resource block (RB) includes N RB sc A series of 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.

[0052] A resource block cell is a collection of resources corresponding to one OFDM symbol in a resource block. That is, a resource block cell includes 12 resource elements corresponding to one OFDM symbol in a resource block.

[0053] For a given subcarrier interval, the common resource blocks of a given setting μ are indexed in the frequency domain, starting from 0 and proceeding in ascending order. The common resource block with index 0 for a given subcarrier interval includes (or competes for, agrees with) point 3000. The index n of the common resource block for a given subcarrier interval is... μ CRB Satisfying n μ CRB =ceil(k) sc / N RB sc The relationship between k and k. sc A subcarrier with a center frequency of 0 is a subcarrier that has the same center frequency as the subcarrier corresponding to point 3000.

[0054] For a given subcarrier interval, a physical resource block with a specified value μ is indexed in a specific BWP (Block Window) in ascending order starting from 0 in the frequency domain. The index n of the physical resource block with a specified value μ for a given subcarrier interval is... μ PRB Satisfying n μ CRB =n μ PRB +N start ，μ BWP，i The relationship. Here, N start，μ BWP，i This represents the base point of the BWP at index i.

[0055] A BWP is defined as a subset of common resource blocks included in a resource grid. A BWP includes the base point N of that BWP. start，μ BWP，i The beginning of Nsize，μ BWP，i A common resource block. The BWP set for the downlink carrier is also called the downlink BWP. The BWP set for the uplink component carrier is also called the uplink BWP.

[0056] An antenna port can 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 can correspond to a physical channel. Furthermore, a symbol can also correspond to an OFDM symbol. Additionally, a symbol can also correspond to a resource block cell. Furthermore, a symbol can also correspond to a resource element.

[0057] The large-scale property of a channel transmitting symbols in one antenna port can be inferred from the channel transmitting symbols in another antenna port, referred to as the QCL (Quasi Co-Located) for both antenna ports. The large-scale property can include at least the long-term characteristics of the channel. The large-scale property can also include at least some or all of the following: delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters. The QCL for the first and second antenna ports can be that the assumed receive beam for the first antenna port and the assumed receive beam for the second antenna port are the same (or corresponding). Alternatively, the QCL for the first and second antenna ports can be that the assumed transmit beam for the first antenna port and the assumed transmit beam for the second antenna port are the same (or corresponding). Terminal device 1 can assume that both antenna ports are QCLs if the large-scale characteristics of the channel transmitting symbols at one antenna port can be inferred from the channel transmitting symbols at the other antenna port. The two antenna ports being QCLs can also be assumed to be QCLs. The large-scale characteristics can be referred to as QCL parameters.

[0058] QCL types can be any of type A, type B, type C, and type D.

[0059] A QCL (Quadrant Classification) of type A with two antenna ports can be a first large-scale characteristic of a channel transmitting symbols at one antenna port, presumed from a channel transmitting symbols at the other antenna port. A QCL of type B with two antenna ports can be a second large-scale characteristic of a channel transmitting symbols at one antenna port, presumed from a channel transmitting symbols at the other antenna port. A QCL of type C with two antenna ports can be a third large-scale characteristic of a channel transmitting symbols at one antenna port, presumed from a channel transmitting symbols at the other antenna port. A QCL of type D with two antenna ports can be a fourth large-scale characteristic of a channel transmitting symbols at one antenna port, presumed from a channel transmitting symbols at the other antenna port. The first large-scale characteristic can include all of Doppler shift, Doppler spread, average delay, and delay spread. The second large-scale characteristic can include all of Doppler shift and Doppler spread. The third large-scale characteristic can include all of Doppler shift and average delay. The fourth large-scale characteristic can include spatial reception parameters (information on spatial direction, beam information). The antenna port for DMRS can be a DMRS port. The antenna port for PTRS can be a PTRS port. The antenna port associated with PTRS can be a PTRS port. The antenna port used for SRS can be an SRS port. The antenna port used for DMRS can be a DMRS port. The antenna port associated with DMRS can be a DMRS port.

[0060] Carrier aggregation can use multiple aggregated serving cells for communication. Furthermore, carrier aggregation can also use multiple aggregated component carriers for communication. Additionally, carrier aggregation can use multiple aggregated downlink component carriers for communication. Furthermore, carrier aggregation can use multiple aggregated uplink component carriers for communication.

[0061] Figure 5 This is a schematic block diagram illustrating an example configuration of a base station device 3 according to one embodiment of this invention. Figure 5As shown, the base station device 3 includes at least a portion 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 portion 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 portion or all of a media access control layer processing unit 35 and a radio resource control (RRC) layer processing unit 36.

[0062] The wireless transceiver unit 30 includes at least a portion or all of a wireless transmitting unit 30a and a wireless receiving unit 30b. Here, the baseband section included in the wireless transmitting unit 30a and the baseband section included in the wireless receiving unit 30b may have the same or different configurations. Furthermore, the RF section included in the wireless transmitting unit 30a and the RF section included in the wireless receiving unit 30b may have the same or different configurations. Additionally, the antenna section included in the wireless transmitting unit 30a and the antenna section included in the wireless receiving unit 30b may have the same or different configurations.

[0063] For example, the wireless transmitter 30a can generate and transmit a baseband signal for PDSCH. For example, the wireless transmitter 30a can also generate and transmit a baseband signal for PDCCH. For example, the wireless transmitter 30a can also generate and transmit a baseband signal for PBCH. For example, the wireless transmitter 30a can also generate and transmit a baseband signal for synchronization. For example, the wireless transmitter 30a can also generate and transmit a baseband signal for PDSCH DMRS. For example, the wireless transmitter 30a can also generate and transmit a baseband signal for PDCCH DMRS. For example, the wireless transmitter 30a can also generate and transmit a baseband signal for CSI-RS. For example, the wireless transmitter 30a can also generate and transmit a baseband signal for DL ​​PTRS.

[0064] For example, wireless receiver 30b can receive PRACH. For example, wireless receiver 30b can also receive and demodulate PUCCH. Wireless receiver 30b can also receive and demodulate PUSCH. For example, wireless receiver 30b can also receive PUCCH DMRS. For example, wireless receiver 30b can also receive PUSCH DMRS. For example, wireless receiver 30b can also receive ULPTRS. For example, wireless receiver 30b can also receive SRS.

[0065] The upper-layer processing unit 34 outputs downlink data (transmission blocks) to the wireless transceiver unit 30 (or the wireless transmitter 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.

[0066] The media access control layer processing unit 35 of the upper layer processing unit 34 performs MAC layer processing.

[0067] The Radio Resource Control (RRC) layer processing unit 36, included in the upper-layer processing unit 34, performs RRC layer processing. The RRC layer processing unit 36 ​​manages various setting information / parameters (RRC parameters) of the terminal device 1. The RRC layer processing unit 36 ​​sets RRC parameters based on RRC messages received from the terminal device 1. For example, setting upper-layer parameters can be based on received RRC messages. For example, receiving upper-layer parameters can be based on received RRC messages.

[0068] The wireless transceiver unit 30 (or wireless transmitter 30a) performs modulation, encoding, and other processing. The wireless transceiver unit 30 (or wireless transmitter 30a) generates a physical signal by modulating, encoding, and generating a baseband signal (converting it to a time-continuous signal) the downlink data, and then transmits it to the terminal device 1. The wireless transceiver unit 30 (or wireless transmitter 30a) can also assign the physical signal to a component carrier and transmit it to the terminal device 1.

[0069] The wireless transceiver unit 30 (or wireless receiver 30b) performs demodulation and decoding processes. The wireless transceiver unit 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 unit 30 (or wireless receiver 30b) can perform the channel access process before the physical signal is transmitted.

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

[0071] The baseband unit 33 converts the analog signal input from the RF unit 32 into a digital signal. The baseband unit 33 removes the part equivalent to the CP (Cyclic Prefix) from the converted digital signal, performs a Fast Fourier Transform (FFT) on the signal after removing the CP, and extracts the signal in the frequency domain.

[0072] The baseband unit 33 performs an inverse fast fourier transform (IFFT) on the data to generate OFDM symbols, and appends a CP to the generated OFDM symbols to generate a digital baseband signal. The baseband unit 33 then converts the digital baseband signal into an analog signal. The baseband unit 33 outputs the converted analog signal to the RF unit 32.

[0073] The RF unit 32 uses a low-pass filter to remove unwanted frequency components from the analog signal input from the baseband unit 33, up-converts the analog signal to a carrier frequency, and transmits it via the antenna unit 31. Furthermore, the RF unit 32 may also have the function of controlling the transmission power. The RF unit 32 is also referred to as the transmit power control unit.

[0074] One or more serving cells (or component carriers, downlink component carriers, uplink component carriers) can be set for terminal device 1.

[0075] The serving cells set for terminal device 1 can be any one of PCell (Primary cell), PSCell (Primary SCG cell), and SCell (Secondary cell).

[0076] PCell is a serving cell included in MCG (Master Cell Group). PCell is a cell (the cell that has been implemented) through terminal device 1 in performing the initial connection establishment procedure or the connection re-establishment procedure.

[0077] A PSCell is a serving cell included in a SCG (Secondary Cell Group). A PSCell is the serving cell for which terminal device 1 performs random access.

[0078] SCell can be included in either MCG or SCG.

[0079] 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). The one or more serving cells (or component carriers) included in a serving cell group can be utilized through carrier aggregation.

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

[0081] One downlink BWP among one or more downlink BWPs configured for the serving cell (or downlink component carrier) can be set to activate the downlink BWP (or one downlink BWP can be activated). One uplink BWP among one or more uplink BWPs configured for the serving cell (or uplink component carrier) can be set to activate the uplink BWP (or one uplink BWP can be activated).

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

[0083] PDSCH, PDCCH, and CSI-RS may also not be received in downlink BWPs other than the active downlink BWP (inactive downlink BWPs). Terminal device 1 may also attempt to receive PDSCH, PDCCH, and CSI-RS in downlink BWPs that are not active downlink BWPs. It may also not transmit PUCCH and PUSCH in uplink BWPs that are not active uplink BWPs (inactive uplink BWPs). Terminal device 1 may also not 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.

[0084] Downlink BWP switching is the process of deactivating an active downlink BWP for a serving cell and activating any of the inactive downlink BWPs for that serving cell. Downlink BWP switching can be controlled via the BWP field included in the downlink control information. Downlink BWP switching can also be controlled based on upper-layer parameters.

[0085] Uplink BWP switching is used to deactivate an active uplink BWP and activate any of the inactive uplink BWPs that are not the active one. Uplink BWP switching can be controlled via the BWP field included in the downlink control information. Uplink BWP switching can also be controlled based on upper-layer parameters.

[0086] You may choose not to set more than two downlink BWPs out of one or more downlink BWPs configured for the serving cell as active downlink BWPs. Alternatively, you may activate one downlink BWP for the serving cell at a certain time.

[0087] Alternatively, more than two uplink BWPs from one or more uplink BWPs configured for the serving cell may not be set as active uplink BWPs. Alternatively, one uplink BWP may be activated for the serving cell at a specific time.

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

[0089] The wireless transceiver unit 10 includes at least a portion or all of a wireless transmitting unit 10a and a wireless receiving unit 10b. Here, the baseband unit 13 included in the wireless transmitting unit 10a and the baseband unit 13 included in the wireless receiving unit 10b may have the same or different configurations. Furthermore, the RF unit 12 included in the wireless transmitting unit 10a and the RF unit 12 included in the wireless receiving unit 10b may have the same or different configurations. Additionally, the antenna unit 11 included in the wireless transmitting unit 10a and the antenna unit 11 included in the wireless receiving unit 10b may have the same or different configurations.

[0090] For example, the wireless transmitter 10a can generate and transmit a PRACH baseband signal. For example, the wireless transmitter 10a can also generate and transmit a PUCCH baseband signal. For example, the wireless transmitter 10a can also generate and transmit a PUSCH baseband signal. For example, the wireless transmitter 10a can also generate and transmit a PUCCH DMRS baseband signal. For example, the wireless transmitter 10a can also generate and transmit a PUSCH DMRS baseband signal. For example, the wireless transmitter 10a can also generate and transmit an ULPTRS baseband signal. For example, the wireless transmitter 10a can also generate and transmit an SRS baseband signal.

[0091] For example, the wireless receiver 10b can receive and demodulate the PDSCH. For example, the wireless receiver 10b can also receive and demodulate the PDCCH. For example, the wireless receiver 10b can also receive and demodulate the PBCH. For example, the wireless receiver 10b can also receive synchronization signals. For example, the wireless receiver 10b can also receive PDSCH DMRS. For example, the wireless receiver 10b can also receive PDCCH DMRS. For example, the wireless receiver 10b can also receive CSI-RS. For example, the wireless receiver 10b can also receive DLPTRS.

[0092] The upper-layer processing unit 14 outputs uplink data (transmission blocks) to the wireless transceiver unit 10 (or the wireless transmitter 10a). The upper-layer processing unit 14 performs processing at the MAC layer, packet convergence protocol layer, radio link control layer, and RRC layer.

[0093] The media access control layer processing unit 15 of the upper layer processing unit 14 performs MAC layer processing.

[0094] The Radio Resource Control (RRC) layer processing unit 16, included in the upper-layer processing unit 14, performs RRC layer processing. The RRC layer processing unit 16 manages various setting information / parameters (RRC parameters) of the terminal device 1. The RRC layer processing unit 16 sets the RRC parameters based on the RRC messages received from the base station device 3. For example, setting upper-layer parameters can be based on the received RRC messages. For example, receiving upper-layer parameters can be based on the received RRC messages.

[0095] The wireless transceiver unit 10 (or wireless transmitter 10a) performs modulation, encoding, and other processing. The wireless transceiver unit 10 (or wireless transmitter 10a) generates a physical signal by modulating, encoding, and generating a baseband signal (converting it to a time-continuous signal) on the uplink data, and then transmits it to the base station device 3. The wireless transceiver unit 10 (or wireless transmitter 10a) can also configure the physical signal to a specific BWP (activate the uplink BWP) and transmit it to the base station device 3.

[0096] The wireless transceiver unit 10 (or wireless receiver 10b) performs demodulation and decoding processes. The wireless transceiver unit 10 (or wireless receiver 10b) can receive physical signals in a specific BWP (Active Downlink BWP) of a serving cell. The wireless transceiver unit 10 (or wireless receiver 10b) separates, demodulates, and decodes the received physical signals, and outputs the decoded information to the upper-layer processing unit 14. The wireless transceiver unit 10 (wireless receiver 10b) can perform the channel access procedure before transmitting the physical signals.

[0097] The RF unit 12 converts the signal received by the antenna unit 11 into a baseband signal through quadrature demodulation (down-conversion) and removes unwanted frequency components. The RF unit 12 then outputs the processed analog signal to the baseband unit 13.

[0098] The baseband unit 13 converts the analog signal input from the RF unit 12 into a digital signal. The baseband unit 13 removes the part equivalent to the CP (Cyclic Prefix) from the converted digital signal, performs a Fast Fourier Transform (FFT) on the signal after removing the CP, and extracts the signal in the frequency domain.

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

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

[0101] The following is an explanation of physical signals (signals).

[0102] Physical signals refer to the downlink physical channel, uplink physical channels, and the collective term for the uplink physical channel. A physical channel is the collective term for both downlink and uplink physical channels. A physical signal is also referred to as a reference signal.

[0103] An uplink physical channel can correspond to a set of resource elements used to transmit information generated in the higher layer. The uplink physical channel can be a physical channel used in uplink component carriers. The uplink physical channel can be transmitted by terminal device 1. The uplink physical channel can be received by base station device 3. In one embodiment of the wireless communication system, at least some or all of the following uplink physical channels can be used.

[0104] ・PUCCH (Physical Uplink Control CHannel) ・PUSCH (Physical Uplink Shared CHannel) • PRACH (Physical Random Access Channel) PUCCH can be used to transmit uplink control information (UCI). PUCCH can be sent to deliver, transmit, or convey uplink control information. Uplink control information can be mapped onto the PUCCH. Terminal device 1 can send a PUCCH configured with uplink control information. Base station device 3 can receive a PUCCH configured with uplink control information.

[0105] The uplink control information (uplink control information bits, uplink control information sequence, uplink control information type) includes at least some or all of the following: Channel State Information (CSI), Scheduling Request (SR), and HARQ-ACK (Hybrid Automatic Repeat request ACK knowledgement).

[0106] Channel state information is also referred to as channel state information bits or channel state information sequence. Scheduling requests are also referred to as scheduling request bits or scheduling request sequence. HARQ-ACK information is also referred to as HARQ-ACK information bits or HARQ-ACK information sequence.

[0107] HARQ-ACK information may include at least the HARQ-ACK corresponding to a transport block (TB). HARQ-ACK can represent either ACK (acknowledgment) or NACK (negative-acknowledgment) corresponding to the transport block. ACK indicates successful decoding of the transport block. NACK indicates unsuccessful decoding of the transport block. HARQ-ACK information may also include a HARQ-ACK codebook containing one or more HARQ-ACK bits.

[0108] A transport block is a sequence of information bits delivered from the upper layer. This sequence of information bits is also called a bit sequence. Transport blocks can be distributed via the UL-SCH (Uplink-Shared Channel) of the transport layer.

[0109] There is a case called HARQ-ACK for PDSCH that is a HARQ-ACK for a transport block. In this case, "HARQ-ACK for PDSCH" means that the PDSCH contains the HARQ-ACK for the transport block.

[0110] HARQ-ACK can also represent ACK or NACK corresponding to a CBG (Code Block Group) included in the transport block.

[0111] A scheduling request can be used at least to request UL-SCH resources for initial transmission (new transmission). The scheduling request bit can be used to represent either a positive SR or a negative SR. A scheduling request bit representing a positive SR is also called "transmitting a positive SR." A positive SR can indicate that terminal device 1 is requesting UL-SCH resources for initial transmission. A positive SR can also indicate that a scheduling request is triggered by an upper layer. A positive SR can be transmitted when indicating that a scheduling request is sent by an upper layer. A scheduling request bit representing a negative SR is also called "a negative SR being transmitted." A negative SR can indicate that terminal device 1 is not requesting UL-SCH resources for initial transmission. A negative SR can also indicate that a scheduling request is not triggered by an upper layer. A negative SR can be transmitted when not indicating that a scheduling request is sent by an upper layer.

[0112] Channel state information may include at least some or all of the following: Channel Quality Indicator (CQI), Precoder Matrix Indicator (PMI), and Rank Indicator (RI). CQI is an indicator associated with the quality of the propagation path (e.g., propagation strength) or the quality of the physical channel; PMI is an indicator associated with precoding; and RI is an indicator associated with the transmission rank (or transmission layer number).

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

[0114] PUCCH can correspond to the PUCCH format. A PUCCH can be a collection of resource elements used to transmit a PUCCH format. A PUCCH can include the PUCCH format. A PUCCH can be sent in a certain PUCCH format. It should be noted that the PUCCH format can be interpreted as a message format. Furthermore, the PUCCH format can also be interpreted as a collection of information set in a certain message format.

[0115] The PUSCH can also be used to transmit one or both of the transport block and uplink control information. The transport block can be configured in the PUSCH. Transport blocks distributed by the UL-SCH can be configured in the PUSCH. Uplink control information can be configured in the PUSCH. Terminal device 1 can send a PUSCH configured with one or both of the transport block and uplink control information. Base station device 3 can receive a PUSCH configured with one or both of the transport block and uplink control information.

[0116] A PRACH can also be sent to transmit a random access preamble. Terminal device 1 can send a PRACH. Base station device 3 can receive a PRACH. The sequence x of the PRACH. u，v (n) by x u，v (n) = x u (mod(n+C)) v L RA Defined by )). Where, x u It is a ZC (Zadoff Chu) sequence. Furthermore, x u It can be done through x u =exp(-jπui(i+1) / L RA Let j be the imaginary unit. Furthermore, π is the value of pi. Additionally, C... vThis corresponds to the cyclic shift of the PRACH sequence. Furthermore, L RA This corresponds to the length of the PRACH sequence. Furthermore, L RA It is 839 or 139. Furthermore, i is 0 to L. RA Integers in the range of -1. Furthermore, u is the sequence index of the PRACH sequence.

[0117] 64 random access preambles are defined for each PRACH opportunity. The random access preambles are based on a cyclic shift C of the PRACH sequence. v The sequence index u of the PRACH sequence is used to determine this. An index can be added for each of the 64 determined random access preambles.

[0118] Uplink physical signals can correspond to a set of resource elements. Uplink physical signals may not be used to transmit information generated at the upper layer. It should be noted that uplink physical signals can also be used to transmit information generated at the physical layer. Uplink physical signals can be physical signals used in uplink component carriers. Terminal device 1 can transmit uplink physical signals. Base station device 3 can receive uplink physical signals. In a wireless communication system according to one embodiment, at least some or all of the following uplink physical signals can be used.

[0119] • UL DMRS (Uplink Demodulation Reference Signal) • SRS (Sounding Reference Signal) • UL PTRS (Uplink Phase Tracking Reference Signal) UL DMRS is a general term for DMRS used for PUSCH and DMRS used for PUCCH.

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

[0121] The transmission of a PUSCH and the transmission of the DMRS used for that PUSCH can be represented (or scheduled) by a DCI format. The PUSCH and the DMRS used for that PUSCH can be collectively referred to as the PUSCH. Transmitting a PUSCH can also consist of transmitting both the PUSCH and the DMRS used for that PUSCH.

[0122] The propagation path of a PUSCH can be inferred from the DMRS used for that PUSCH.

[0123] The set of antenna ports for the DMRS used for the PUCCH (DMRS associated with the PUCCH, DMRS included in the PUCCH, and DMRS corresponding to the PUCCH) can be the same as the set of antenna ports for the PUCCH.

[0124] The transmission of a PUCCH and the transmission of the DMRS used for that PUCCH can be indicated (or triggered) by a DCI format. One or both of the following can be provided in a PUCCH format: a PUCCH-to-resource element mapping and a DMRS-to-resource element mapping used for that PUCCH. The PUCCH and the DMRS used for that PUCCH can be collectively referred to as PUCCH. Transmitting a PUCCH can also consist of transmitting both the PUCCH and the DMRS used for that PUCCH.

[0125] The propagation path of a PUCCH can be estimated based on the DMRS used for that PUCCH.

[0126] A downlink physical channel can correspond to a set of resource elements that transmit information generated at the upper layer. The downlink physical channel can be a physical channel used in downlink component carriers. Base station device 3 can transmit the downlink physical channel. Terminal device 1 can receive the downlink physical channel. In a wireless communication system according to one embodiment, at least some or all of the following downlink physical channels can be used.

[0127] • PBCH (Physical Broadcast Channel) ・PDCCH (Physical Downlink Control Channel) ・PDSCH (Physical Downlink Shared Channel) The PBCH can transmit one or both of the MIB (Master Information Block) and physical layer control information. Here, the physical layer control information is information generated at the physical layer. The MIB is a set of parameters configured in the BCCH (Broadcast Control Channel), which is a logical channel of the MAC layer. This BCCH is configured in the BCH, which is a transport layer channel. The BCH can be mapped onto the PBCH. Terminal device 1 can receive a PBCH configured with one or both of the MIB and physical layer control information. Base station device 3 can transmit a PBCH configured with one or both of the MIB and physical layer control information.

[0128] For example, physical layer control information can consist of 8 bits. Physical layer control information can include at least some or all of the following 0A to 0D.

[0129] 0A) Wireless frame bits 0B) Half-wireless frame (half-system frame, half-frame) bits 0C) SS / PBCH block index bits 0D) Subcarrier offset bits The radio frame bit is used to indicate the radio frame transmitting the PBCH (including radio frames in the time slot of the PBCH transmission). The radio frame bit consists of 4 bits. The radio frame bit can be composed of 4 bits from the 10-bit radio frame indicator. For example, the radio frame indicator can be used to identify radio frames at least from index 0 to index 1023.

[0130] The half-frame bit is used to indicate which of the first five subframes or the second five subframes of a radio frame containing a PBCH should be transmitted. Here, a half-frame can be configured to include five subframes. Alternatively, a half-frame can consist of the first five subframes of a radio frame containing ten subframes. Furthermore, a half-frame can also consist of the second five subframes of a radio frame containing ten subframes.

[0131] The SS / PBCH block index bits are used to indicate the SS / PBCH block index. The SS / PBCH block index bits consist of 3 bits. Alternatively, the SS / PBCH block index bits can be composed of 3 bits from a 6-bit SS / PBCH block index indicator. The SS / PBCH block index indicator can be used to identify at least SS / PBCH blocks with indices 0 to 63.

[0132] The subcarrier offset bit is used to represent the subcarrier offset. The subcarrier offset can also be used to represent the difference between the subcarrier at the start of the mapped PBCH and the subcarrier at the start of the control resource set at mapping index 0.

[0133] The PDCCH can transmit downlink control information (DCI). Downlink control information can be configured in the PDCCH. Terminal device 1 can receive a PDCCH configured with downlink control information. Base station device 3 can transmit a PDCCH configured with downlink control information.

[0134] Downlink control information can be sent along with DCI format. It should be noted that DCI format can be interpreted as the form of downlink control information. Furthermore, DCI format can also be interpreted as a collection of downlink control information formatted in a certain way.

[0135] DCI formats 0_0, 0_1, 1_0, and 1_1 are DCI formats. The uplink DCI format is a collective term for DCI formats 0_0 and 0_1. The downlink DCI format is a collective term for DCI formats 1_0 and 1_1.

[0136] DCI format 0_0 is used at least to configure PUSCH scheduling in a cell. DCI format 0_0 consists of at least some or all of the fields 1A to 1E.

[0137] 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 (MCS field: Modulation and Coding Scheme field) A DCI format-specific field can indicate whether the DCI format including this field is an uplink DCI format or a downlink DCI format. That is, a DCI format-specific field can be included in each uplink and downlink DCI format. Here, the DCI format-specific field included in DCI format 0_0 can represent 0.

[0138] The frequency domain resource allocation field contained in DCI format 0_0 can be used to represent the frequency resource allocation of PUSCH.

[0139] The time-domain resource allocation field contained in DCI format 0_0 can be used to represent the time resource allocation of PUSCH.

[0140] The frequency hopping flag field can be used to indicate whether frequency hopping is applied to the PUSCH.

[0141] The MCS field in DCI format 0_0 can be used to represent at least one or both of the modulation scheme and target coding rate of the PUSCH. The target coding rate can be the target coding rate used to configure the transport block in the PUSCH. The size of the transport block (TBS) configured in the PUSCH can be determined based on one or both of the target coding rate and the modulation scheme of the PUSCH.

[0142] DCI format 0_0 may also exclude the field used for CSI request.

[0143] DCI format 0_0 may also omit the carrier indicator field. That is, the serving cell to which the uplink component carrier configured with a PUSCH scheduled by DCI format 0_0 belongs and the serving cell to which the uplink component carrier configured with a PDCCH containing DCI format 0_0 belongs can be the same. Terminal device 1 can identify that the PUSCH scheduled by DCI format 0_0 will be configured on the uplink component carrier of a certain serving cell based on the detection of DCI format 0_0 in a certain downlink component carrier of a certain serving cell.

[0144] DCI format 0_0 may also exclude the BWP field (BWP indicator field). Here, DCI format 0_0 can be a DCI format for scheduling PUSCH without changing the active uplink BWP. Terminal device 1 can identify that the PUSCH should be sent without switching the active uplink BWP based on the detection of DCI format 0_0 for PUSCH scheduling.

[0145] DCI format 0_1 ​​is used at least to configure PUSCH scheduling in a cell. DCI format 0_1 ​​consists of at least some or all of the fields 2A to 2H.

[0146] 2A) Specific fields in DCI format 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 The DCI format-specific fields included in DCI format 0_1 ​​can represent 0.

[0147] The frequency domain resource allocation field contained in DCI format 0_1 ​​can be used to represent the frequency resource allocation for PUSCH.

[0148] The time-domain resource allocation field contained in DCI format 0_1 ​​can be used to represent the time resource allocation used for PUSCH.

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

[0150] The BWP field of DCI format 0_1 ​​can be used to represent an uplink BWP configured with a PUSCH scheduled by that DCI format 0_1. That is, DCI format 0_1 ​​can change depending on the activation of the uplink BWP. Terminal device 1 can identify the uplink BWP configured with the PUSCH based on the detected DCI format 0_1 ​​used for PUSCH scheduling.

[0151] DCI format 0_1 ​​without the BWP field can be a DCI format for scheduling PUSCH without changing the active uplink BWP. Terminal device 1 uses DCI format 0_1 ​​for PUSCH scheduling and can identify that the PUSCH is sent without switching the active uplink BWP based on the detection of DCI format D0_1 without the BWP field.

[0152] DCI format 0_1 ​​includes a BWP field, but if terminal device 1 does not support the function of switching BWP via DCI format 0_1, terminal device 1 can ignore the BWP field. That is, terminal device 1, which does not support BWP switching, uses DCI format 0_1 ​​for PUSCH scheduling, and can identify that the PUSCH is sent without switching to activate the uplink BWP based on the detection of DCI format 0_1 ​​containing the BWP field. Where terminal device 1 supports BWP switching, it can report "Terminal device 1 supports BWP switching" during the RRC layer function information reporting process.

[0153] The CSI Request field is used to indicate the CSI report.

[0154] Alternatively, if the DCI format 0_1 ​​includes a carrier indicator field, this carrier indicator field is used to indicate the uplink component carrier configured with a PUSCH. Alternatively, if the DCI format 0_1 ​​does not include a carrier indicator field, the uplink component carrier configured with a PUSCH is the same as the uplink component carrier configured with a PDCCH in DCI format 0_1 ​​that includes scheduling for that PUSCH. Alternatively, if the number of uplink component carriers assigned to terminal device 1 in a certain serving cell group is 2 or more (in the case of uplink carrier aggregation in a certain serving cell group), the number of bits in the carrier indicator field included in DCI format 0_1 ​​used for scheduling the PUSCH for that certain serving cell group is 1 bit or more (e.g., 3 bits). Alternatively, if the number of uplink component carriers assigned to terminal device 1 in a certain serving cell group is 1 (in the case where uplink carrier aggregation is not used in a certain serving cell group), the number of bits in the carrier indicator field included in the DCI format 0_1 ​​used to configure the PUSCH for that certain serving cell group is 0 (or the carrier indicator field may not be included in the DCI format 0_1 ​​used to configure the PUSCH for that certain serving cell group).

[0155] DCI format 1_0 is used at least to configure PDSCH scheduling in a cell. DCI format 1_0 is configured to include at least some or all of 3A to 3F.

[0156] 3A) Specific fields in DCI format 3B) Frequency domain resource allocation field 3C) Time-domain resource allocation field 3D) MCS field 3E) PDSCH_HARQ feedback timing indicator field 3F) PUCCH resource indicator field The DCI format-specific fields included in DCI format 1_0 can represent 1.

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

[0158] The time-domain resource allocation field included in DCI format 1_0 can at least be used to indicate the allocation of time resources for PDSCH.

[0159] The MCS field included in DCI format 1_0 can be used to represent at least one or both of the modulation scheme and target coding rate used for PDSCH. The target coding rate can be the target coding rate used for transport blocks configured in PDSCH. The size of the transport block (TBS) configured in PDSCH can be determined based on one or both of the target coding rate and the modulation scheme used for PDSCH.

[0160] The PDSCH_HARQ feedback timing indication field can be used to indicate the offset from the time slot of the OFDM symbol including the end of PDSCH to the time slot of the OFDM symbol including the beginning of PUCCH.

[0161] The PUCCH resource indicator field can be a field that indicates any index of one or more PUCCH resources included in a PUCCH resource set. A PUCCH resource set can include one or more PUCCH resources.

[0162] DCI format 1_0 may also exclude the carrier indicator field. That is, a downlink component carrier configured with a PDSCH scheduled by DCI format 1_0 can be the same as a downlink component carrier configured with a PDCCH including DCI format 1_0. Terminal device 1 can identify that a PDSCH scheduled by DCI format 1_0 is configured on a downlink component carrier based on the detection of DCI format 1_0 in that downlink component carrier.

[0163] DCI format 1_0 may also exclude the BWP field. DCI format 1_0 can be a DCI format for scheduling PDSCH without changing the active downlink BWP. Terminal device 1 can identify that it can receive the PDSCH without switching the active downlink BWP based on the detection of DCI format 1_0 used for PDSCH scheduling.

[0164] DCI format 1_1 is used at least to configure PDSCH scheduling in a cell. DCI format 1_1 may include at least some or all of 4A to 4I.

[0165] 4A) Specific fields in DCI format 4B) Frequency domain resource allocation field 4C) Time-domain resource allocation field 4E) MCS field 4F) PDSCH_HARQ Feedback Timing Indicator Field 4G) PUCCH Resource Indication Field 4H) BWP field 4I) Carrier Indicator Field The DCI format-specific fields included in DCI format 1_1 can represent 1.

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

[0167] The time-domain resource allocation field included in DCI format 1_1 can at least be used to indicate the allocation of time resources for PDSCH.

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

[0169] Alternatively, if the DCI format 1_1 includes a PDSCH_HARQ feedback timing indication field, this field is used to indicate at least the offset from the time slot containing the last OFDM symbol including the PDSCH to the time slot containing the starting OFDM symbol including the PUCCH. Alternatively, if the DCI format 1_1 does not include a PDSCH_HARQ feedback timing indication field, the offset from the time slot containing the last OFDM symbol including the PDSCH to the time slot containing the starting OFDM symbol including the PUCCH is determined by parameters from the upper layer.

[0170] The PUCCH resource indicator field can be a field that indicates any index of one or more PUCCH resources included in a PUCCH resource set.

[0171] The BWP field of DCI format 1_1 can be used to represent a downlink BWP configured with a PDSCH scheduled by DCI format 1_1. That is, DCI format 1_1 can change depending on the activation of the downlink BWP. Terminal device 1 can identify the downlink BWP configured with the PUSCH based on the detection of DCI format 1_1 for PDSCH scheduling.

[0172] The DCI format 1_1 excluding the BWP field can be a DCI format for scheduling PDSCH without a change in activating the downlink BWP. The terminal device 1 can identify that the PDSCH was received without switching the activation of the downlink BWP based on the detection of the DCI format 1_1 used for PDSCH scheduling and excluding the BWP field.

[0173] DCI format 1_1 contains a BWP field, but if terminal device 1 does not support the function of switching BWP via DCI format 1_1, terminal device 1 can ignore the BWP field. That is, terminal device 1, which does not support BWP switching, uses DCI format 1_1 for PDSCH scheduling, and can identify that it receives the PDSCH without switching to activate the downlink BWP based on the detection of DCI format 1_1 containing the BWP field. Where terminal device 1 supports BWP switching, it can report "Terminal device 1 supports BWP switching" during the RRC layer function information reporting process.

[0174] Alternatively, if the DCI format 1_1 includes a carrier indicator field, this carrier indicator field is used to indicate the downlink component carrier configured with PDSCH. Alternatively, if the DCI format 1_1 does not include a carrier indicator field, the downlink component carrier configured with PDSCH is the same as the downlink component carrier configured with PDCCH in DCI format 1_1, which includes scheduling for the PDSCH. Alternatively, if the number of downlink component carriers assigned to terminal device 1 in a certain serving cell group is 2 or more (in the case of downlink carrier aggregation in a certain serving cell group), the number of bits in the carrier indicator field included in DCI format 1_1 used for scheduling the PDSCH for that serving cell group is 1 bit or more (e.g., 3 bits). Alternatively, if the number of downlink component carriers assigned to terminal device 1 in a certain serving cell group is 1 (in the case where downlink carrier aggregation is not used in a certain serving cell group), the number of bits in the carrier indicator field included in the DCI format 1_1 used to configure the PDSCH for that certain serving cell group is 0 (or, the carrier indicator field may not be included in the DCI format 1_1 used to configure the PDSCH for that certain serving cell group).

[0175] PDSCH can be sent to transmit transport blocks. PDSCH can also be used to send transport blocks distributed by DL-SCH. PDSCH can be used to transmit transport blocks. Transport blocks can be configured in PDSCH. Transport blocks corresponding to DL-SCH can also be configured in PDSCH. Base station device 3 can send PDSCH. Terminal device 1 can receive PDSCH.

[0176] Downlink physical signals can correspond to a set of resource elements. Downlink physical signals may also not carry information generated at the upper layer. Downlink physical signals can be physical signals used in downlink component carriers. Downlink physical signals can be transmitted via base station device 3. Downlink physical signals can also be transmitted via terminal device 1. In a wireless communication system according to one embodiment, at least some or all of the following downlink physical signals can be used.

[0177] • Synchronization signal (SS) • DL DMRS (Downlink Demodulation Reference Signal) • CSI-RS (Channel State Information-Reference Signal) • DL PTRS (Downlink Phase Tracking Reference Signal) Synchronization signals can be used by terminal device 1 to synchronize one or both of the downlink frequency and time domains. Synchronization signals are a collective term for PSS (Primary Synchronization Signal) and SSS (Secondary Synchronization Signal).

[0178] Figure 7 This is a diagram illustrating an example of the configuration of the SS / PBCH block in one embodiment of this invention. Figure 7 In the middle, the horizontal axis is the time axis (OFDM symbol index l). sym The vertical axis represents the frequency domain. Furthermore, block 700 represents the set of resource elements used for the PSS. Additionally, block 702 represents the set of resource elements used for the SSS. Furthermore, four blocks (blocks 710, 711, 712, and 713) represent the set of resource elements used for the PBCH and the DMRS used for that PBCH (DMRS associated with the PBCH, DMRS contained in the PBCH, and DMRS corresponding to the PBCH).

[0179] like Figure 7As shown, the SS / PBCH block includes PSS, SSS, and PBCH. Furthermore, the SS / PBCH block comprises four consecutive OFDM symbols. The SS / PBCH block includes 240 subcarriers. PSS is configured on subcarriers 57 to 183 in the first OFDM symbol. SSS is configured on subcarriers 57 to 183 in the third OFDM symbol. Subcarriers 1 to 56 of the first OFDM symbol can be set to zero. Subcarriers 184 to 240 of the first OFDM symbol can also be set to zero. Subcarriers 49 to 56 of the third OFDM symbol can also be set to zero. Subcarriers 184 to 192 of the third OFDM symbol can also be set to zero. PBCH is configured on subcarriers 1 to 240 of the second OFDM symbol that are not configured with DMRS for PBCH. PBCH is configured on subcarriers 1 to 48 of the third OFDM symbol that are not configured with DMRS for PBCH. Configure the PBCH in subcarriers 193 to 240, which are the third OFDM symbol, where no DMRS is configured for the PBCH. Configure the PBCH in subcarriers 1 to 240, which are the fourth OFDM symbol, where no DMRS is configured for the PBCH.

[0180] The antenna ports for PSS, SSS, PBCH, and DMRS used for PBCH can be the same.

[0181] The PBCH that transmits the symbol of the PBCH in a certain antenna port can be estimated based on the DMRS for the PBCH configured as the time slot mapping the PBCH and the DMRS for the PBCH included in the SS / PBCH block of the PBCH.

[0182] DL DMRS is a general term for DMRS used in PBCH, DMRS used in PDSCH, and DMRS used in PDCCH.

[0183] The set of antenna ports for the DMRS used in the PDSCH (DMRS associated with the PDSCH, DMRS included in the PDSCH, and DMRS corresponding to the PDSCH) can be given based on the set of antenna ports used in the PDSCH. That is, the set of antenna ports for the DMRS used in the PDSCH can be the same as the set of antenna ports used in the PDSCH.

[0184] The transmission of a PDSCH and the transmission of the DMRS used for that PDSCH can be indicated (or scheduled) by a DCI format. The PDSCH and the DMRS used for that PDSCH can be collectively referred to as the PDSCH. Transmitting a PDSCH can also consist of transmitting both the PDSCH and the DMRS used for it.

[0185] The propagation path of a PDSCH can be inferred from the DMRS used for that PDSCH. If the set of resource elements that transmit the symbols of a PDSCH and the set of resource elements that transmit the symbols of the DMRS used for that PDSCH are included in the same Precoding Resource Group (PRG), then the PDSCH that transmits the symbols of that PDSCH in a certain antenna port can be inferred from the DMRS used for that PDSCH.

[0186] The antenna ports of the DMRS used for PDCCH (DMRS associated with PDCCH, DMRS included in PDCCH, and DMRS corresponding to PDCCH) can be the same as those used for PDCCH.

[0187] The PDCCH can be inferred from the DMRS used for it. That is, the transmission path of the PDCCH can be inferred from the DMRS used for it. If the same precoding is applied (assumed to be applied) in the set of resource elements transmitting the symbols of a PDCCH and the set of resource elements transmitting the symbols of the DMRS used for that PDCCH, then the PDCCH transmitting the symbols of that PDCCH in a given antenna port can be inferred from the DMRS used for it.

[0188] 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 known as logical channels).

[0189] The transport layer's BCH is mapped to the physical layer's PBCH. That is, transport blocks via the transport layer's BCH are distributed to the physical layer's PBCH. Furthermore, the transport layer's UL-SCH is mapped to the physical layer's PUSCH. That is, transport blocks via the transport layer's UL-SCH are distributed to the physical layer's PUSCH. Additionally, the transport layer's DL-SCH is mapped to the physical layer's PDSCH. That is, transport blocks via the transport layer's DL-SCH are distributed to the physical layer's PDSCH.

[0190] One UL-SCH and one DL-SCH can be provided for each serving cell. The BCH can be provided by the PCell. Alternatively, the BCH may not be provided by the PSCell or SCell.

[0191] In the MAC layer, HARQ (Hybrid Automatic Repeat reQuest) control is performed on each transport block.

[0192] 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. Furthermore, CCCH (Common Control Channel) can be used to transmit RRC messages common to multiple terminal devices 1. Here, CCCH can be used, for example, for terminal device 1 that has not established an RRC connection. Additionally, DCCH (Dedicated Control Channel) can be used at least to transmit RRC messages specific to terminal device 1. Here, DCCH can be used, for example, for terminal device 1 that has established an RRC connection.

[0193] Upper-layer parameters shared by multiple terminal devices 1 are also called common upper-layer parameters. These common upper-layer parameters can be defined as parameters specific to the serving cell. Specifically, parameters specific to the serving cell can be parameters shared by the terminal devices that set up the serving cell (e.g., terminal devices 1-A, B, C).

[0194] For example, shared upper-layer parameters can be included in the RRC message distributed to the BCCH. Similarly, shared upper-layer parameters can be included in the RRC message distributed to the DCCH.

[0195] Among certain upper-layer parameters, those different from the common upper-layer parameters are also called dedicated upper-layer parameters. These dedicated upper-layer parameters provide dedicated RRC parameters to terminal device 1-A, which is configured to serve a specific cell. In other words, dedicated RRC parameters are upper-layer parameters that can provide specific settings for each of terminal devices 1-A, B, and C.

[0196] The BCCH of a logical channel can be mapped to either the BCH or DL-SCH of the transport layer. For example, a transport block containing MIB information is distributed to the BCH of the transport layer. Furthermore, a transport block containing system information other than MIB information is distributed to the DL-SCH of the transport layer. Additionally, the CCCH is mapped to either the DL-SCH or UL-SCH. That is, a transport block mapped to the CCCH is distributed to either the DL-SCH or UL-SCH. Furthermore, the DCCH is mapped to either the DL-SCH or UL-SCH. That is, a transport block mapped to the DCCH is distributed to either the DL-SCH or UL-SCH.

[0197] An RRC message contains one or more parameters managed by the RRC layer. These parameters are also called RRC parameters. For example, an RRC message may include the MIB. Furthermore, an RRC message may include system information. Additionally, an RRC message may include messages corresponding to the CCCH. Furthermore, an RRC message may include messages corresponding to the DCCH. RRC messages that include messages corresponding to the DCCH are also called dedicated RRC messages.

[0198] Upper-level parameters (or upper-level parameters) are the parameters contained in RRC parameters or MAC CE (Medium Access Control Control Element). In other words, upper-level parameters are the collective term for parameters included in the MIB, system information, messages corresponding to CCCH, messages corresponding to DCCH, and MAC CE. Parameters included in the MAC CE are sent via MAC CE (Control Element) commands.

[0199] The process performed by terminal device 1 includes at least some or all of the following 5A to 5C.

[0200] 5A) Cell search 5B) Random access 5C) Data communication Cell search is the process by which terminal device 1 synchronizes with a specific cell in both the time and frequency domains and detects the physical cell ID. In other words, terminal device 1 can use cell search to synchronize with a specific cell in both the time and frequency domains and detect the physical cell ID.

[0201] The sequence of PSS is given at least based on the physical cell ID. The sequence of SSS is given at least based on the physical cell ID.

[0202] SS / PBCH block candidates indicate resources that allow (can, reserve, set, specify, may) the transmission of SS / PBCH blocks.

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

[0204] The base station device 3 transmits one or more indexed SS / PBCH blocks at a predetermined period. The terminal device 1 can detect at least one SS / PBCH block among the one or more indexed SS / PBCH blocks and attempt to decode the PBCH included in that SS / PBCH block.

[0205] 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 can be triggered in response to a request sent via PRACH based on upper-layer parameters or the PDCCH order.

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

[0207] Terminal device 1 sends a random access preamble selected from the PRACH opportunity corresponding to the index of the SS / PBCH block candidate for detecting the SS / PBCH block.

[0208] Terminal device 1 can attempt detection of DCI format 1_0 with CRC scrambled by RA-RNTI. Message 2 is the process by which terminal device 1 attempts detection of DCI format 1_0 with CRC scrambled by RA-RNTI (Random Access-Radio Network Temporary Identifier). Terminal device 1 attempts detection of PDCCH including this DCI format in resources indicated by the settings of the control resource set and search area set, wherein the settings of the control resource set and search area set are given based on the MIB of the PBCH included in the SS / PBCH block detected based on cell search. Message 2 is also referred to as a Random Access Response (RAR). Terminal device 1 can receive a Random Access Response (or a Random Access Response message) with PDCCH / PDSCH attached as a message.

[0209] Message 3 is the process of sending the PUSCH scheduled by the random access response grant included in DCI format 1_0 detected by the process of message 2. Here, the random access response grant is indicated by the MAC CE included in the PDSCH scheduled by this DCI format 1_0.

[0210] The PUSCH scheduled based on the random access response grant is either message 3 PUSCH or any of the PUSCH messages. Message 3 PUSCH includes the Contention Resolution Identifier (MAC CE). The Contention Resolution Identifier (MAC CE) includes the Contention Resolution Identifier.

[0211] The retransmission of message 3 PUSCH is scheduled by DCI format 0_0 with CRC scrambled based on TC-RNTI (Temporary Cell-Radio Network Temporary Identifier).

[0212] Message 4 is a process of attempting detection with DCI format 1_0 accompanied by a scrambled CRC based on either C-RNTI (Cell - Radio Network Temporary Identifier) ​​or TC-RNTI. Terminal device 1 receives a PDSCH scheduled based on this DCI format 1_0. This PDSCH may include a contention resolution ID.

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

[0214] In data communication, terminal device 1 attempts to detect (monitor PDCCH, monitor PDCCH) in resources determined based on the set of control resources and the set of search areas.

[0215] A control resource set (CORESET) is a collection of resources consisting of a specified number of resource blocks and a specified number of OFDM symbols. In the frequency domain, the control resource set can consist of either contiguous resources (non-interleaved mapping) or dispersed resources (interleaved mapping).

[0216] The set of resource blocks that constitute a control resource set can be represented by upper-level parameters. The number of OFDM symbols that constitute a control resource set can also be represented by upper-level parameters.

[0217] Terminal device 1 attempts to detect PDCCH in the search area set. Here, attempting to detect PDCCH in the search area set can be attempting to detect PDCCH candidates 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 PDCCH candidates in the control resource set, or attempting to detect DCI format in the control resource set.

[0218] The search area set is defined as a set of candidate PDCCHs. The search area set can 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 sets: 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 PDCCH search space set.

[0219] The type 0 PDCCH public search region set can be used as the public search region set of index 0. The type 0 PDCCH public search region set can also be the public search region set of index 0.

[0220] The CSS set is a collective term for the Type 0 PDCCH public search area set, the Type 0a PDCCH public search area set, the Type 1 PDCCH public search area set, the Type 2 PDCCH public search area set, and the Type 3 PDCCH public search area set. The USS set is also known as the UE-specific PDCCH search area set.

[0221] A search region set is associated with (includes, corresponds to) a control resource set. The index of the control resource set associated with the search region set can be represented by a higher-level parameter.

[0222] For a given search region set, at least a portion or all of 6A to 6C can be represented by the upper-level parameters.

[0223] 6A) PDCCH monitoring periodicity 6B) PDCCH monitoring pattern within a slot 6C) PDCCH monitoring offset A monitoring occasion for a search region set can correspond to an OFDM symbol configured with the starting point of the control resource set associated with that search region set. A monitoring occasion for a search region set can also correspond to the resources of that control resource set starting from the starting point of the control resource set associated with that search region set. The monitoring occasion for the search region set is given based on at least some or all of the following: the PDCCH monitoring interval, the PDCCH monitoring mode within the time slot, and the PDCCH monitoring offset.

[0224] Figure 8 This is a diagram illustrating an example of the monitoring opportunities for a set of search areas in one embodiment of this method. Figure 8 In the main cell 301, search area set 91 and search area set 92 are set; in the secondary cell 302, search area set 93 is set; and in the secondary cell 303, search area set 94 is set.

[0225] exist Figure 8 In the main cell 301, the monochrome white block represents the search area set 91, the monochrome black block represents the search area set 92, the block in the secondary cell 302 represents the search area set 93, and the block in the secondary cell 303 represents the search area set 94.

[0226] The monitoring interval of search region set 91 is set to 1 time slot, the monitoring offset of search region set 91 is set to 0 time slot, and the monitoring mode of search region set 91 is set to [1, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0]. That is to say, the monitoring opportunities of search region set 91 correspond to the OFDM symbol at the beginning of each time slot (OFDM symbol #0) and the 8th OFDM symbol (OFDM symbol #7).

[0227] The monitoring interval of search region set 92 is set to 2 time slots, the monitoring offset of search region set 92 is set to 0 time slots, and the monitoring mode of search region set 92 is set to [1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]. That is to say, the monitoring opportunities of search region set 92 correspond to the OFDM symbol (OFDM symbol #0) of the starting point in each even-numbered time slot.

[0228] The monitoring interval of search region set 93 is set to 2 time slots, the monitoring offset of search region set 93 is set to 0 time slots, and the monitoring mode of search region set 93 is set to [0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0]. That is to say, the monitoring opportunity of search region set 93 corresponds to the 8th OFDM symbol (OFDM symbol #7) in each even-numbered time slot.

[0229] The monitoring interval of search region set 94 is set to 2 time slots, the monitoring offset of search region set 94 is set to 1 time slot, and the monitoring mode of search region set 94 is set to [1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]. That is to say, the monitoring opportunities of search region set 94 correspond to the OFDM symbol (OFDM symbol #0) of the starting point in each odd time slot.

[0230] The type 0PDCCH common search region set can be used at least for DCI formats with CRC (Cyclic Redundancy Check) sequences scrambled by SI-RNTI (System Information-Radio Network Temporary Identifier).

[0231] The type 0aPDCCH common search area set can be used at least for DCI formats with CRC (Cyclic Redundancy Check) sequences scrambled by SI-RNTI (System Information-Radio Network Temporary Identifier).

[0232] Type 1 PDCCH common search area set can be used at least for DCI formats accompanied by CRC sequences scrambled by RA-RNTI (Random Access-Radio Network Temporary Identifier) ​​and / or TC-RNTI (Temporary Cell-Radio Network Temporary Identifier).

[0233] Type 2 PDCCH common search area set can be used with DCI format accompanied by CRC sequences scrambled by P-RNTI (Paging-Radio Network Temporary Identifier).

[0234] Type 3 PDCCH common search area set can be used with DCI format accompanied by CRC sequences scrambled by C-RNTI (Cell-Radio Network Temporary Identifier).

[0235] The UE-specific PDCCH search area set can be used at least for DCI formats that include CRC sequences scrambled by C-RNTI.

[0236] In downlink communication, terminal device 1 detects the downlink DCI format. The detected downlink DCI format is used at least for PDSCH resource allocation. This detected downlink DCI format is also referred to as downlink assignment. Terminal device 1 attempts to receive the PDSCH. Based on the PUCCH resource, it reports the HARQ-ACK corresponding to the PDSCH (the HARQ-ACK corresponding to the transport block included in the PDSCH) to base station device 3, wherein the PUCCH resource is indicated based on the detected downlink DCI format.

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

[0238] In the configured grant, the uplink grant for scheduling a PUSCH is set per transmission cycle of that PUSCH. When scheduling a PUSCH via the uplink DCI format, some or all of the information shown in that uplink DCI format can be represented by the configured uplink grant under the configured grant.

[0239] PUSCH transmission can correspond to either the configured schedule type 1 or the configured schedule type 2. That is, the configured schedule can be either the configured schedule type 1 or the configured schedule type 2. PUSCH transmission for configured schedule type 1 can also be configured semi-statically. For example, PUSCH transmission for configured schedule type 1 can also operate in response to the reception of a certain upper-layer parameter. This upper-layer parameter can be `configuredGrantConfig`. For example, `configuredGrantConfig` can include `rrc-ConfiguredUplinkGrant`. PUSCH transmission can also operate without uplink grant detection in the DCI.

[0240] PUSCH transmissions configured for scheduling type 2 can be scheduled semi-persistently. For example, they can also be scheduled via an uplink grant. An uplink grant can be included in an activation DCI (or valid activation DCI). For example, after receiving an upper-layer parameter, PUSCH transmissions configured for scheduling type 2 can also be scheduled via an uplink grant. The upper-layer parameter can be `configuredGrantConfig`. For example, `configuredGrantConfig` may not include `rrc-ConfiguredUplinkGrant`.

[0241] System frame number (SFN) n f This can be a number assigned to a radio frame and / or an index used for the radio frame. The system frame number can consist of 10 bits. At least a portion of the system frame number can be notified by the MIB. For example, 6 bits (e.g., the 6 topmost bits) of the 10-bit system frame number can be notified by the MIB. At least a portion of the system frame number can also be determined based on the PBCH used to transmit the MIB. For example, 4 bits (e.g., the 4 bottommost bits) of the 10-bit system frame number can be transmitted by the PBCH transport block as part of the channel coding.

[0242] PDCCH-Config can be a dedicated upper-level parameter. PDCCH-Config can set parameters used for PDCCH. Multiple (e.g., up to three) CORESETs can be set in PDCCH-Config. A CORESET ID can be set in a CORESET. A CORESET pool index can be set in a CORESET.

[0243] The PDCCH setting can include two different CORESET pool indices. For example, two CORESET pool index values ​​(0 and 1) can be provided. For example, two CORESET pool index values ​​can be provided for the first CORESET and the second CORESET. The PDCCH setting can be PDCCH-Config.

[0244] PDSCH-Config can be a dedicated upper-level parameter. PDSCH-Config can set parameters used for PDSCH.

[0245] When multiple PDCCH candidates (PDCCH candidate(s)) are associated with a set of search regions defined by a higher-level parameter, a single PDCCH candidate is used. This single PDCCH candidate can be the earlier of the two PDCCH candidates. The higher-level parameter can be searchSpaceLinking.

[0246] Multiple TRPs (Transmission Reception Points or Transmit / Receive Points) can be used. Base station device 3 can consist of multiple TRPs (Multi-TRPs). Terminal device 1 can be scheduled through two TRPs in a serving cell. A serving cell can schedule terminal device 1 from two TRPs for PDSCH, PDCCH, PUSCH, and PUCCH.

[0247] In a multi-TRP (Multi-TRP), either a single-DCI or a multi-DCI operation mode can be used. Uplink and downlink control can be performed at the MAC and physical layers in a multi-TRP. Downlink control can also be performed at the MAC and physical layers in a multi-TRP. In single-DCI mode, terminal device 1 can be scheduled using the same DCI used for multiple TRPs. In multi-DCI mode, terminal device 1 can be scheduled using independent DCIs from each TRP.

[0248] There are two modes for PDCCH transmission in multiple TRPs: PDCCH repetition and SFN (Single Frequency Network) based PDCCH transmission. In both modes, terminal device 1 can receive two PDCCH transmissions, and the PDCCH transmissions can carry the same DCI. In PDCCH repetition, terminal device 1 can receive two PDCCH transmissions carrying the same DCI from search areas of two links associated with different CORESETs. In SFN based PDCCH transmission, terminal device 1 can use different TCI states to receive two PDCCH transmissions carrying the same DCI from one search area / CORESET.

[0249] In the repetition of PUSCH / PUCCH in multiple TRPs, terminal device 1 can perform the same PUSCH transmission for multiple TRPs according to the instructions in a single DCI or the instructions in the authorization set by RRC.

[0250] In multiple TRPs and multiple DCI modes within an inter-cell, one or more TCI states can be associated with an SSB that includes an additional PCI index. An active TCI state can be associated with at most one additional PCI index. The additional PCI index can be a different PCI (Physical Cell ID) than the serving cell.

[0251] When a unified TCI state is set and multiple DCI modes are configured, the DMRS port used for first PDSCH reception can be QCL with the first reference signal. First PDSCH reception can be scheduled using the DCI format provided by the PDCCH reception in the first CORESETs. The first reference signal can be provided by the "indicated TCI state" corresponding to the first CORESETs. When a unified TCI state is set and multiple DCI modes are configured, the DMRS port used for second PDSCH reception can be QCL with the second reference signal. Second PDSCH reception can be scheduled using the DCI format provided by the PDCCH reception in the second CORESETs. The second reference signal can be provided by the "indicated TCI state" corresponding to the second CORESETs. Setting multiple DCI modes can be achieved by providing CORESET pool index 0 for the first CORESETs in a BWP, providing CORESET pool index 1 for the second CORESETs in a BWP, and providing some or all of the followingUnifiedTCI-State for both the first and second CORESETs.

[0252] When multiple DCI modes are configured, the MAC CE activation command for the first CORESET may include the first CORESET pool index. When multiple DCI modes are configured, the MAC CE activation command for the second CORESET may include the second CORESET pool index. Furthermore, when multiple TRP modes are configured between cells, the "activated TCI state" of the first CORESET may be associated with the physical cell ID from the serving cell (e.g., ServingCellConfigCommon), and the "activated TCI state" of the second CORESET may be associated with the physical cell ID from the appended PCI index (e.g., AdditionalPCI). Configuring multiple TRP modes between cells can be done by configuring SSB_MTC_AdditionalPCI. Configuring multiple TRP modes between cells can be done by configuring an appended PCI index. Configuring multiple DCI modes can be done by providing two CORESET pool index values, 0 and 1, for the first and second CORESETs.

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

[0254] Terminal device 1 can receive PDSCH. Base station device 3 can transmit PDSCH. A transmission method can be defined for each PDSCH. Alternatively, a single transmission method can be used for all PDSCH transmissions.

[0255] Terminal device 1 can receive data in the PDSCH. Base station device 3 can transmit data in the PDSCH. One transmission method is transmission method 1. In transmission method 1, it can be assumed that the transmission in the PDSCH is performed at a maximum of 8 layers. Each layer can be mapped to one or more antenna ports. The one or more antenna ports can be some or all of antenna ports 1000-1023. For example, without an extended CSI port, the one or more antenna ports can be some or all of antenna ports 1000-1023. For example, with an extended CSI port, the one or more antenna ports can be some or all of antenna ports 1000-1127.

[0256] Terminal device 1 can schedule the reception of PDSCH. For example, terminal device 1 can schedule the reception of PDSCH via DCI. PDSCH reception can be scheduled using the DCI format in PDCCH. PDSCH can be scheduled using the DCI format. Terminal device 1 can receive scheduling authorization via the DCI format. Upon receiving scheduling authorization, downlink resource allocation can be used.

[0257] Terminal device 1 can configure upper-layer parameters TCI-State. For example, terminal device 1 can configure a list in the upper-layer parameter PDSCH-Config. A list can include up to M upper-layer parameters TCI-State. A list can be a list of up to M upper-layer parameters TCI-State. Terminal device 1 can configure a list for decoding (receiving) PDSCH based on the PDCCH with DCI. M can depend on the terminal capability (UE capability). For example, M can also depend on the terminal capability maxNumberConfiguredTCIStatePerCC. TCI-State can be referred to as TCI state.

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

[0259] QCL relationships can be set using one or both of the upper-layer parameters qcl-Type1 and qcl-Type2. For example, QCL relationships can also be set using one or both of the upper-layer parameters qcl-Type1 for the first downlink reference signal (DL RS) and qcl-Type2 for the second downlink reference signal. If the first and second downlink reference signals are different, the QCL type of qcl-Type1 can also be different from the QCL type of qcl-Type2. The QCL type corresponding to each downlink reference signal can be given by the upper-layer parameter qcl-Type in the upper-layer parameter QCL-Info. The QCL type can be any one of type A, type B, type C, and type D.

[0260] A list can be set through the upper-layer parameter dlOrJointTCI-StateList. For example, a list can be set in the upper-layer parameter PDSCH-Config. A list can include up to 128 upper-layer parameters TCI-State. A list can be a list of up to 128 upper-layer parameters TCI-State. A list can be set to provide a reference signal. An upper-layer parameter TCI-State can be set to provide a reference signal. A reference signal can be a reference signal used for the QCL of the DMRS of PDSCH and the DMRS of PDCCH. A reference signal can also be a reference signal used for CSI-RS. A list can also be set to provide a reference. An upper-layer parameter TCI-state can also be set to provide a reference. A reference can be used to determine the uplink transmit spatial filter (UL TX spatial filter). The uplink transmit spatial filter can be used for PUSCH, PUCCH, and SRS. That is, a reference can be provided to determine the uplink transmit spatial filter used for PUSCH, PUCCH, and SRS. TCI-State can be referred to as DL / Joint TCI State or Unified TCI State. Setting the upper-level parameter dlOrJointTCI-StateList can set the unified TCI state.

[0261] TCI-State (e.g., upper-layer parameter TCI-State) and TCI-UL-State (e.g., upper-layer parameter TCI-UL-State) can be set in a BWP of a component carrier. If no TCI-State or TCI-UL-State setting exists in a BWP, the terminal device 1 can apply the TCI-State or TCI-UL-State setting based on a reference BWP. TCI-UL-State can also be referred to as UL TCI state or unified TCI state. Setting ul-TCI-StateList can be used to set the unified TCI state.

[0262] Terminal device 1 may not require setting either the first upper-layer parameter or the second upper-layer parameter. The first upper-layer parameter can be any one of tci-StatesToAddModList, SpatialRelationInfo, and PUCCH-SpatialRelationInfo. The second upper-layer parameter can be any one of dl-OrJointTCI-StateList and TCI-UL-StateList. If tci-StatesToAddModList is set in any component carrier of a certain list, the second upper-layer parameter may not be set in any component carrier within the same frequency band of that certain list. This certain list can be set using the upper-layer parameter simultaneousTCI-UpdateList1, simultaneousTCI-UpdateList2, simultaneousSpatial-UpdatedList1, or simultaneousSpatial-UpdatedList2.

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

[0264] When a first set of one or more TCI state IDs is activated in a second set, the first set can be applied to the downlink BWP in the indicated component carrier. When a first set of one or more TCI state IDs is activated in a third set, the first set can be applied to both the downlink BWP and the uplink BWP in the indicated component carrier. The second set can be a set of one or both of the component carriers and the one or more downlink BWPs. The third set can be a set of some or all of the one or more component carriers, the one or more downlink BWPs, and the one or more uplink BWPs.

[0265] When the activation command maps one or both of the DL / joint TCI state and the UL TCI state to a TCI code point (the code point of the DCI field 'Transmission Configuration Indication'), the terminal device 1 can apply one or both of the indicated DL / joint TCI state and the indicated UL TCI state.

[0266] Terminal device 1 can receive a DCI format that provides an indication of the DL / joint TCI status or an indication of the UL TCI status. The DCI format may not include downlink allocation. For example, in the case where the DCI format does not include downlink allocation, terminal device 1 may assume some or all of the following: CS-RNTI is used to scramble the CRC used for DCI; RV (Redundancy version) is all 1; MCS is all 1; NDI is 0; all are set to 0 for FDRA type 0; and all are set to 1 for FDRA type 1.

[0267] Terminal device 1 can receive upper-layer settings. After terminal device 1 receives the first upper-layer setting of "set TCI state" and before applying an "indicated TCI state" from the "set TCI state", terminal device 1 can assume that the DMRS of PDSCH, the DMRS of PDCCH, and the CSI-RS and SS / PBCH blocks of the "indicated TCI state" are QCLs. Setting the upper-layer parameter DLorJoint-TCIStateList can set the "set TCI state". Setting the upper-layer parameter DLorJoint-TCIStateList can set a unified TCI state. Setting the "set TCI state" can set a unified TCI state. DLorJoint-TCIStateList can be accompanied by multiple upper-layer parameters TCI-State.

[0268] After terminal device 1 receives the first upper-layer setting of the "set TCI state" and before applying an "indicated TCI state" from the "set TCI state", terminal device 1 may assume that the first uplink transmission space filter for PUSCH, PUCCH, and SRS using the "indicated TCI state" is the same as the second uplink transmission space filter. The second uplink transmission space filter may be the uplink transmission space filter used for PUSCH transmission scheduled through random access response authorization in the initial access procedure. Setting the upper-layer parameter ul-TCI-StateList can set the "set TCI state". Setting the upper-layer parameter ul-TCI-StateList can set a unified TCI state. Setting the "set TCI state" can set a unified TCI state. ul-TCI-StateList may include multiple upper-layer parameters TCI-State.

[0269] Terminal device 1 can receive upper-layer settings. After terminal device 1 receives the first upper-layer setting of the "set TCI state" as part of a synchronized reset and before applying an "indicated TCI state" from the "set TCI state", the DMRS of the PDSCH, the DMRS of the PDCCH, and the CSI-RS of the applied indicated TCI state can be QCL with the SS / PBCH block or CSI-RS resource. For example, the SS / PBCH block or CSI-RS resource can be identified during a random access process that begins with a synchronized reset.

[0270] Terminal device 1 can receive upper-layer settings. After terminal device 1 receives the first upper-layer setting of "set TCI state" as part of a synchronized reset and before applying an "indicated TCI state" from the "set TCI state", it can be assumed that the first uplink transmission space filter for PUSCH, PUCCH, and SRS using the indicated TCI state is the same as the second uplink transmission space filter. The second uplink transmission space filter can be an uplink space filter for PUSCH transmission scheduled by the random access response grant (RAR UL grant) in the random access procedure. The second uplink transmission space filter can be an uplink transmission space filter for PUSCH transmission scheduled by the random access response grant in the random access procedure that begins with a synchronized reset.

[0271] When terminal device 1 receives a "set TCI state" containing a TCI state, terminal device 1 can obtain the QCL assumption from the set TCI state. The set TCI state can be the TCI state used by the CSI-RS, DMRS of PDSCH, and DMRS of PDCCH, which are TCI states indicated by the application. The set TCI state can be the upper-layer parameter dl-OrJointTCI-StateList.

[0272] When terminal device 1 receives a "set TCI state" message with a TCI state attached, terminal device 1 can determine the uplink transmission space filter based on the set TCI state. The set TCI state can be the TCI state indicated by the application for PUSCH, PUCCH, and SRS. The set TCI state can be the upper-layer parameter dl-OrJointTCI-StateList or ul-TCI-StateList.

[0273] When a unified TCI state is set and terminal device 1 transmits the first channel, and the first "indicated TCI state" differs from the second "indicated TCI state," the first "indicated TCI state" can be applied from the first timeslot. The first channel can be a PUCCH with HARQ-ACK information or a PUSCH with HARQ-ACK information. The HARQ-ACK information can be HARQ-ACK information corresponding to a DCI that transmits a TCI state indication without downlink allocation. Alternatively, the HARQ-ACK information can be HARQ-ACK information corresponding to a PDSCH scheduled by a DCI that transmits a TCI state indication. The second indicated TCI state can be indicated before (before) the first indicated TCI state. The first timeslot can be the first timeslot after at least beamAppTime symbols from the last OFDM symbol of the first channel. BeamAppTime can be the number of OFDM symbols. BeamAppTime can be set by upper-layer parameters. BeamAppTime can also be determined by terminal capabilities. The indicated TCI state can be the indicated TCI-State or the indicated TCI-UL-State.

[0274] When multiple DCI modes are configured, terminal device 1 can receive activation commands (“activated TCI states”) for CORESETs associated with each CORESET pool index. The activation command can be used to map up to eight TCI states to code points in the DCI field 'Transmission Configuration Indication'. When a set of TCI state IDs is activated for a CORESET pool index, the “activated TCI state” corresponding to that CORESET pool index can be associated with a physical cell ID, and the “activated TCI state” corresponding to a CORESET pool index different from that CORESET pool index can be associated with a physical cell ID different from that physical cell ID. The activation command can be received as a MAC CE. One or more CORESETs can be configured in a BWP. A CORESET can correspond to a CORESET pool index of '0' or '1'. Configuring multiple DCI modes can include two different values ​​for the upper-layer parameter PDCCH-Config, including the CORESET pool index (CORESETPool Index or coresetPoolIndex).

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

[0276] When terminal device 1 transmits the first PUCCH in the first time slot, the mapping between TCI state and code point can be applied starting from the second time slot. The first PUCCH may be accompanied by first HARQ-ACK information. The first PUCCH may be transmitted in correspondence with the first PDSCH. The first PDSCH may convey an activation command.

[0277] If the TCI field is present, the time offset is above a threshold, and the terminal device 1 receives the first TCI state setting but before receiving the activation command, it can assume that the DMRS and SS / PBCH blocks of the PDSCH in a serving cell are QCL with respect to QCL type A. The presence of the TCI field can be achieved by setting 'enabled' in the upper-layer parameter tci-PresentInDCI. The presence of the TCI field can also be achieved by setting the upper-layer parameter tci-PresentDCI-1-2 for the CORESET of the scheduled PDSCH. The time offset can be the offset between the reception of the DL DCI and the PDSCH. The threshold can be timeDurationForQCL. The threshold can be based on the reported terminal capabilities.

[0278] With the first upper-layer parameter set, terminal device 1 can assume that the DCI format of the PDCCH transmitted in the CORESET contains a TCI field. The first upper-layer parameter can be tci-PresentInDCI with 'enabled' set. The first upper-layer parameter can be tci-PresentInDCI with 'enabled' set for the CORESET of the scheduling PDSCH or multicast PDSCH. The first upper-layer parameter can also be tci-PresentDCI-1-2.

[0279] In the absence of a TCI field and when the time offset exceeds a threshold, the TCI state or QCL assumption for the PDSCH antenna port can be the same as the TCI state or QCL assumption for the CORESET application used for the PDCCH in order to determine the QCL. The time offset can be the time offset between the DL DCI reception and the corresponding PDSCH. The threshold can be timeDurationForQCL.

[0280] When both SFN and PDSCH are configured, and PDSCH is scheduled via DCI format, with a time offset exceeding a threshold, and with default beam support, the QCL assumption or TCI state for PDSCH can be the same as the QCL assumption or TCI state for CORESET application. Furthermore, if dynamic switching is not supported, CORESET can be activated in both TCI states. CORESET can be the CORESET used for DL ​​DCI reception. When both SFN and PDSCH are configured, and PDSCH is scheduled via DCI format, with a time offset exceeding a threshold, and with default beam support, a TCI field can be assumed to exist. Setting SFN for PDCCH can be done by setting the upper-layer parameter sfnSchemePdcch. Setting SFN for PDSCH can be done by setting the upper-layer parameter sfnSchemePdsch. The DCI format can be any one of DCI format 1_0, DCI format 1_1, and DCI format 1_2. The default beam can be sfn-DefaultDL-BeamSetup for DCI without the TCI field. The time offset can be the time offset between the DL DCI reception and the corresponding PDSCH. The threshold can be timeDurationForQCL.

[0281] If an SFN is set for PDSCH but not for PDCCH, and PDSCH is scheduled by DCI format 1_1 / 1_2 with a time offset above the threshold, the existence of a TCI field can also be expected.

[0282] In the case where PDSCH is scheduled by DCI format 1_0 / 1_1 / 1_2, SFN method A is set for PDCCH, SFN is not set for PDSCH, there is no TCI code point (TCI field code point) with two TCI states, the time offset is above the threshold, and the CORESET for scheduling PDSCH is indicated in both TCI states, the TCI state or QCL assumption for PDSCH can be the same as the first TCI state and first QCL assumption applied to CORESET. Setting SFN method A for PDCCH can be setting sfnSchemePdcch with 'sfnSchemeA' set.

[0283] When no unified TCI state is set, 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 can be QCL with RS for a certain QCL parameter. A certain QCL parameter can be used for the PDCCH QCL indication of a certain CORESET. A certain CORESET can be the CORESET associated with the search area with the lowest CORESET ID (controlResourceSetId) among the CORESETs monitored by terminal device 1 in the latest time slot.

[0284] When a unified TCI state is set, the time offset is less than a threshold, and at least one set TCI state includes a qcl-Type with type D set, and the indicated TCI state is associated with the PCI (Physical Cell ID) of the serving cell, the indicated TCI state can be applied to PDSCH reception. When a unified TCI state is set, the time offset is less than a threshold, and at least one set TCI state includes a qcl-Type with type D set, and the indicated TCI state is associated with a PCI (Physical Cell ID) other than that of the serving cell, the DMRS port of the PDSCH in the serving cell can be associated with the reference signal of the QCL parameter of the CORESET associated with the lowest CORESET ID as the QCL. Setting a unified TCI state can be done by setting the upper-layer parameter dl-OrJointTCI-StateList.

[0285] When instructing terminal device 1 of a first terminal capability, terminal device 1 can determine a spatial region filter. The spatial region filter can be used concurrently with the applicable channel access procedures prior to UL transmission in the channel. When instructing the SRI corresponding to the UL transmission, terminal device 1 can use the same spatial region filter associated with the instructed SRI. Terminal device 1 can use the same spatial region filter used for receiving the DL reference signal associated with the indicated TCI state. For example, when TCI-State or TCI-UL-State is set, terminal device 1 can use the same spatial region filter used for receiving the DL reference signal associated with the indicated TCI state. The first terminal capability can be beamCorrespondenceWithoutUL-BeamSweeping, which is set to '1'.

[0286] For Periodic CSI-RS resources, the TCI status can indicate that the SS / PBCH block is QCL with respect to type C. The SS / PBCH block can have a different PCI than the serving cell's PCI. Periodic CSI-RS resources can be CSI-RS resources in the NZP CSI-RS ResourceSet used for TRS (Tracking Reference Signal). NZP can be non-zero power. The CSI-RS ResourceSet used for TRS can be a CSI-RS ResourceSet with the upper-layer parameter trs-Info set.

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

[0288] For aperiodic CSI-RS resources, the TCI state can indicate that it is a QCL (Quality Class Principle) with respect to type A, similar to that of periodic CSI-RS resources. Aperiodic CSI-RS resources can be CSI-RS resources in the NZP CSI-RS resource set used for TRS. Periodic CSI-RS resources can also be CSI-RS resources in the NZP CSI-RS resource set used for TRS.

[0289] For the first CSI-RS resource, the TCI state can indicate that it has a QCL with the second CSI-RS resource regarding type A. For the first CSI-RS resource, the TCI state can indicate that it has a QCL with the third CSI-RS resource regarding type B. The first CSI-RS resource can be a CSI-RS resource in the NZP CSI-RS resource set used for TRS. The first CSI-RS resource may also not be a CSI-RS resource in a repeating NZP CSI-RS resource set. The second CSI-RS resource can be a CSI-RS resource in the NZP CSI-RS resource set used for TRS. If type D cannot be applied, the third CSI-RS resource can be a CSI-RS resource in the NZPC CSI-RS resource set used for TRS. The repeating CSI-RS resource set can be a CSI-RS resource set with the upper-level parameter repetition.

[0290] For the fourth CSI-RS resource, the TCI state can indicate that it has a QCL with the second CSI-RS resource regarding type A. For the fourth CSI-RS resource, the TCI state can indicate that it has a QCL with the SS / PBCH block regarding type C. The fourth CSI-RS resource can be a CSI-RS resource used in a repeating NZP CSI-RS resource set.

[0291] Without a unified TCI status, for the DMRS of the PDCCH, the TCI status can indicate that it is QCL with respect to CSI-RS resources of type A. The CSI-RS resources can be CSI-RS resources in the NZP CSI-RS resource set.

[0292] When SFN method A is configured for the PDCCH and CORESET is activated in both TCI states, the DMRS port of the PDCCH in the CORESET can be QCL with the DL RS (downlink reference signal) of both TCI states. When SFN method B is configured for the PDCCH and CORESET is activated in both TCI states, the DMRS port of the PDCCH in the CORESET can be QCL with the DL RS of both TCI states, and the second TCI state may not include the QCL parameters {Doppler shift, Doppler spread}. Configuring SFN method A for the PDCCH can be configuring sfnSchemePdcch with 'sfnSchemeA' configured. Configuring SFN method B for the PDCCH can be configuring sfnSchemePdcch with 'sfnSchemeB' configured.

[0293] CJT (Coherent Joint Transmission) can also be configured for PDSCH. Configuring CJT involves setting the upper-layer parameter cjtSchemePDSCH. CJT method A involves setting the upper-layer parameter cjtSchemeA. CJT method B involves setting the upper-layer parameter cjtSchemeB. When configuring CJT method A for PDSCH, the DMRS port of PDSCH can be QCL with respect to QCL type A, using two reference signals indicating TCI states. When configuring CJT method B for PDSCH, the DMRS port of PDSCH can be QCL with respect to QCL type A, excluding QCL parameters {Doppler shift, Doppler spread}.

[0294] Without a unified TCI status, for the DMRS of PDSCH, the TCI status can indicate that it is QCL with respect to CSI-RS resources of type A. CSI-RS resources can be CSI-RS resources in the NZP (Non-zero power) CSI-RS resource set.

[0295] With a unified TCI state set, for the DMRS of PDCCH, the TCI state can indicate that it is QCL with CSI-RS resources of type A. With a unified TCI state set, for the DMRS of PDSCH, the TCI state can indicate that it is QCL with CSI-RS resources of type A.

[0296] When SFN method A is configured for the PDSCH and two TCI states are indicated, the DMRS port of the PDSCH can be QCLed with the DL-RS of the two TCI states. When SFN method B is configured for the PDSCH and two TCI states are indicated, the DMRS port of the PDSCH can be QCLed with the DL-RS of the two TCI states. When SFN method B is configured for the PDSCH and two TCI states are indicated, the DMRS port of the PDSCH can be QCLed with the DL-RS of the two TCI states, and the second TCI state may not include the QCL parameters {Doppler shift, Doppler spread}. The two TCI states can be indicated by a code point in the 'Transmission Configuration Indication' field of the DCI in the scheduling PDSCH. Configuring SFN method A for the PDSCH can be configuring sfnSchemePdsch, which is configured with 'sfnSchemeA'. Setting SFN method B for PDSCH can be to set sfnSchemePdsch which has 'sfnSchemeB' set.

[0297] When a unified TCI state is set and multiple DCI modes are configured, and an indicated TCI state is indicated by the TCI field (DCI field 'TransmissionConfiguration Indication') in DCI format 1_1 / 1_2 associated with a CORESET pool index value, an indicated TCI state can correspond to a CORESET pool index value. Setting a unified TCI state can be done by setting dl-OrJointTCI-StateList or TCI-UL-State. Setting multiple DCI modes can be done by setting the upper-level parameter PDCCH-Config, which includes two different CORESET pool index values. The CORESET pool index can be set in the upper-level parameter ControlResourceSet.

[0298] When 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 can be applied to PDSCH reception. The terminal capability of the default beam can be the capability to buffer received signals before the threshold using both indicated TCI states. The terminal capability of the default beam can be the capability in FR2 (Frequency Range 2). For example, FR2 can be a frequency range of 24250MHz to 52600MHz. The time offset can be the offset between the reception of DCI format 1_0 / 1_1 / 1_2 to be scheduled and the scheduled PDSCH reception. The time offset can also be the offset between the reception of DCI format 1_0 / 1_1 / 1_2 to be activated and the activated PDSCH reception. The threshold can be a value less than timeDurationForQCL or timeDurationForQCL.

[0299] When a unified TCI state is set, multiple DCI modes are set, 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 can be applied to PDSCH reception. When a unified TCI state is set, multiple DCI modes are set, and the terminal capability of the default beam is not reported, a second time offset less than a threshold is not expected. The first time offset can be the offset between DCI format reception and PDSCH reception in the CORESET associated with CORESET pool index 0. The second time offset can be the offset between DCI format reception and PDSCH reception in the CORESET associated with CORESET pool index 1.

[0300] When a unified TCI state is set and terminal device 1 has two indicated TCI-States, and a certain condition is met, the upper-layer parameter applyIndicatedTCIState can 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 can 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. When CJT or SFN is set for the PDSCH, the upper-layer parameter applyIndicatedTCIState can indicate "both." The condition can be FR1 (Frequency Range 1). Another condition can be reporting the terminal capability of the default beam in FR2.

[0301] When a unified TCI state is set and the terminal device 1 has two indicated TCI-States, and a certain condition is met and the upper-layer parameter applyIndicatedTCIState is not set, the first indicated TCI-State can be applied to the PDSCH scheduled by DCI format 1_0.

[0302] When a unified TCI state is set, and terminal device 1 has two indicated TCI-States, and a certain condition is met, and the TCI indication field indicates "00", the first indicated DL / joint TCI state can be applied to the PDSCH. When a unified TCI state is set, and terminal device 1 has two indicated TCI-States, and a certain condition is met, and the TCI indication field indicates "01", the second indicated DL / joint TCI state can be applied to the PDSCH. When a unified TCI state is set, and terminal device 1 has two indicated TCI-States, and a certain condition is met, and the TCI indication field indicates "10", the two indicated DL / joint TCI states can be applied to the PDSCH. When a unified TCI state is set, and terminal device 1 has two indicated TCI-States, and a certain condition is met, and the TCI indication field is not set, the two DL / joint TCI states can be applied to the PDSCH. The PDSCH can be scheduled by DCI format 1_1 / 1_2. The TCI indication field can be the DCI field in DCI format 1_1 / 1_2. Whether the TCI indicator field exists in DCI format 1_1 / 1_2 can be determined by the upper-level parameter tciSelection-PresentInDCI.

[0303] Terminal device 1 can set the upper-layer parameter TCI-UL-State. For example, terminal device 1 can set a list in the upper-layer parameter BWP-UplinkDedicated. A list can include up to 64 upper-layer parameters TCI-UL-State. Each TCI-UL-State (or UL-TCI-State setting) can include a parameter for setting a reference signal. For example, each TCI-UL-State can include a parameter for setting a reference signal used to determine some or all of the uplink transmission spatial filters for PUSCH, PUCCH, and SRS. A list can be the upper-layer parameter ul-TCI-StateList. The TCI state can be TCI-UL-State. UL-TCIState (TCI-UL-State) can be referred to as UL TCI state or unified TCI state.

[0304] UL-TCIState can also be the upper-layer parameter TCI-UL-State. UL-TCIState can be set through the upper-layer parameter TCI-UL-State. The upper-layer parameter TCI-UL-State can associate one or two downlink reference signals with a corresponding QCL type.

[0305] CSI reports can be triggered by DCI (DCI format). For example, non-periodic CSI reports can be triggered by DCI format 0_1 / 0_2.

[0306] The time and frequency resources used for reporting CSI can be controlled by the base station device 3. CSI can be composed of some or all of the following: 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-NoiseRatio), CapabilityIndex, and TDCP (Time-Domain Channel Properties).

[0307] Terminal device 1 can set N CSI report settings. The CSI report settings can be the upper-level parameter CSI-ReportConfig.

[0308] Terminal device 1 can configure M CSI resource settings. The CSI resource settings can be the upper-layer parameter CSI-ResourceConfig.

[0309] Terminal device 1 can set one or two lists of trigger states(s). The list of trigger states can be one or both of the upper-level parameters CSI-AperiodicTriggerStateList and CSI-SemiPersistentOnPUSCH-TriggerStateList. For example, the list of trigger states for aperiodic CSI can be the upper-level parameter CSI-AperiodicTriggerStateList. Similarly, the list of trigger states for semi-persistent CSI can be the upper-level parameter CSI-SemiPersistentOnPUSCH-TriggerStateList. The list of trigger states can include one or more trigger states.

[0310] Each trigger state may include a list of CSI report settings. The list of CSI report settings may indicate one or more resource set IDs. Each trigger state in the list of trigger states for non-periodic CSI may include a list of CSI report settings. Each trigger state in the list of trigger states for semi-persistent CSI may include a CSI report setting.

[0311] Each CSI reporting setting (CSI-ReportConfig) can be associated with a downlink BWP. A downlink BWP can be indicated by a BWP ID (upper-layer parameter BWP-Id). A downlink BWP can be specified in the CSI resource settings. For example, a downlink BWP can be specified in the CSI resource settings used for channel measurement.

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

[0313] Each CSI report setting can 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 can be LI, L1-RSRP, L1-SINR, CRI, SSBRI, CapabilityIndex, and TDCP.

[0314] The time-domain action can be indicated by the upper-level parameter `reportConfigType`. The time-domain action can be set to 'aperiodic', 'semiPersistentOnPUCCH', 'semiPersistentOnPUSCH', or 'periodic'. When the time-domain action is set to 'aperiodic', the CSI reporting configuration can be for non-periodic CSI. When the time-domain action is set to 'semiPersistentOnPUCCH' or 'semiPersistentOnPUSCH', the CSI reporting configuration can be for semi-persistent CSI. When the time-domain action is set to 'periodic', the CSI reporting configuration can be for periodic CSI.

[0315] In CSI reports used for periodic and semi-persistent CSI, the period and time slot offset can be set. In CSI reports used for periodic and semi-persistent CSI, the period and time slot offset can be applied to the parameter set of the uplink BWP corresponding to the transmission of the CSI report.

[0316] Each CSI report setting can include a report quantity setting. The report quantity setting can indicate the CSI correlation quantity, L1-RSRP correlation quantity, L1-SINR correlation quantity, CapabilityIndex correlation quantity, or TDCP correlation quantity.

[0317] Frequency granularity can be indicated by the upper-level parameter `reportFreqConfiguration`. PMI and CQI reports can correspond to either the full-band or sub-band. For example, the frequency granularity of PMI and CQI can be either full-band or sub-band, respectively.

[0318] Measurement limits can be set as time limits. Time limits can be set for one or both of the channel measurement and interference measurement.

[0319] Codebook settings can 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. Codebook settings can also include codebook subset restrictions. Codebook settings can also include group-based reporting settings.

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

[0321] Each CSI resource setting can include one or more CSI-RS resource sets. Each CSI-RS resource set can be an NZPCSI-RS resource set. Each CSI-RS resource set can be an SS / PBCH block set. Each CSI-RS resource set can be a CSI-IM resource set. Each CSI-RS resource set can include one or more CSI-RS resources. Each NZP CSI-RS resource set can include one or more NZP CSI-RS resources.

[0322] The time-domain behavior of a CSI-RS resource in a CSI resource setting can be indicated by the upper-level parameter (resourceType). The time-domain behavior can be set to aperiodic, periodic, or semi-persistent. In CSI resource settings for periodic and semi-persistent CSI, the CSI resource setting can include one CSI-RS resource set. In CSI resource settings for periodic and semi-persistent CSI, if group-based reporting is configured, the CSI resource setting can include up to two CSI-RS resource sets.

[0323] In the CSI resource settings for periodic CSI and semi-persistent CSI, the period and time offset can be set. In the CSI resource settings for periodic CSI and semi-persistent CSI, the period and time offset can be given in the parameter set of the downlink BWP provided by the BWP ID.

[0324] When multiple CSI resource settings include the same NZP CSI-RS resource (or the same NZP CSI-RS resource ID), the same time-domain action can be set for multiple CSI resource settings. Similarly, when multiple CSI resource settings include the same CSI-IM resource (or the same CSI-IM resource ID), the same time-domain action can be set for multiple CSI resource settings. All CSI resource settings linked to a single CSI reporting setting can have the same time-domain action.

[0325] CSI-IM resources used for interference measurement can be configured for one or more CSI resource settings. NZP CSI-RS resources used for interference measurement can be configured for one or more CSI resource settings. NZPCSI-RS resources used for channel measurement can be configured for one or more CSI resource settings.

[0326] The NZP CSI-RS resources for channel measurement and the CSI-IM resources (or NZP CSI-RS resources) for interference measurement can be configured with type D as QCL. The NZP CSI-RS resources for channel measurement and the CSI-IM resources (or NZP CSI-RS resources) for interference measurement can be configured for a CSI report (CSI report settings).

[0327] For TDC measurements, a periodic CSI report setting can be configured (CSI report setting for periodic CSI). This CSI report setting can be used for channel measurements in the tracking CSI-RS. TDCP measurements can be measurements where the report quantity setting in the CSI report setting includes TDCP.

[0328] In L1-SINR measurements, if a CSI resource setting is configured, this setting can be used for both channel and interference measurements. Channel and interference measurements can be measurements within the NZPCSI-RS used for L1-SINR calculation. A CSI resource setting can be provided through resourcesForChannelMeasurement. L1-SINR measurements can also be performed when the report quantity setting in the CSI report settings includes L1-SINR.

[0329] In L1-SINR measurements, when two CSI resource settings are configured, the first CSI resource setting can be used for channel measurement, and the second CSI resource setting can be used for interference measurement. Channel measurement can be performed using SSB or NZP CSI-RS. Interference measurement can be performed using CSI-IM or a 1-port NZP CSI-RS. The first CSI resource setting can be provided via resourcesForChannelMeasurement. The second CSI resource setting can be provided via csi-IM-ResourcesForInterference or nzp-CSI-RS-ResourcesForInterference.

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

[0331] CSI reporting can be configured as aperiodic, periodic, or semi-persistent. CSI-RS resources can be periodic, semi-persistent, or aperiodic. CSI reporting can be triggered for each CSI resource. The combination of CSI reporting and CSI resource settings can be determined through time-domain actions. Periodic CSI-RS can be configured using upper-level parameters. Semi-persistent CSI-RS can be activated and disabled. Aperiodic CSI-RS can be configured, activated, and triggered.

[0332] Periodic CSI-RS can be combined with any of the periodic, semi-persistent, and non-periodic CSI reporting settings. Semi-persistent CSI-RS can be combined with any of the semi-persistent and non-periodic CSI reporting settings. Non-periodic CSI-RS can be combined with any non-periodic CSI reporting setting. For semi-persistent CSI reporting, in the case of a report in the PUCCH, terminal device 1 can receive an activation command. For semi-persistent CSI reporting, in the case of a report in the PUSCH, the terminal device can receive a trigger (trigger state) in the DCI. Non-periodic CSI reporting can be triggered by the DCI. Non-periodic CSI reporting can also be triggered by a MAC CE (e.g., subselection indication).

[0333] Terminal device 1 can determine a CRI. A CRI can be determined from a set of CRI values. Terminal device 1 can report the number of CRIs in each report. If a CSI-RS resource set for repetition is set and the CSI-RS resource set is used for channel determination, CRIs may not be reported. If any of the following are set in the codebook type: type II (type II-PortSelection), extended type 2-CSI (type II-r16), extended type 2-Port Selection (type II-r16), super extended type 2-CSI (type II-r17), super extended type 2-Port Selection (type II-PortSelection-r17), super extended type 2-CJT (type II-CJT-r18), super extended type 2-Port Selection CJT (type II-CJT-PortSelection-r18), extended type 2-Predictive PMI (type II-Doppler-r18), and super extended type 2-Port Selection-Predictive PMI (type II-Doppler-PortSelection-r18), then CSI reporting is not required.

[0334] In periodic or semi-persistent CSI reports in PUCCH, period T CSI and time slot offset T offset This can be set by upper-layer parameters (e.g., reportSlotConfig). Terminal device 1 can send CSI reports. Terminal device 1 can send CSI reports in one time slot within a radio frame. A radio frame can be associated with a System Frame Number (SFN). f Correspondence. A time slot can be associated with a time slot index n. μ s，f Correspondingly. A wireless frame and a time slot can be based on mod(N) frame，μ slot *n f +n μ s，f -T offset T CSI The value is set to 0. μ can be the subcarrier spacing setting of the uplink BWP that sends CSI reports.

[0335] In the semi-persistent CSI report in PUSCH, period T CSI This can be set by upper-layer parameters (e.g., reportSlotConfig). Terminal device 1 can transmit a CSI report in one slot within a radio frame. A radio frame and a slot can be based on mod(N). frame，μslot *(n f -n start f )+n μ s，f -n start s，f T CSI ) is determined by being 0. SFN n start f and time slot number n start s，f This can correspond to the first semi-persistent PUSCH transmission. The first semi-persistent PUSCH transmission can be based on the activated DCI.

[0336] In semi-persistent or aperiodic CSI reports within PUSCH, one or more slot offsets can be set via upper-level parameters. When the CSI report is triggered / activated by DCI format 0_2, the upper-level parameter can be `reportSlotOffsetListDCI-0-2`. When the CSI report is triggered / activated by DCI format 0_1, the upper-level parameter can be `reportSlotOffsetListDCI-0-1`. A slot offset can be selected from the triggered / activated DCI.

[0337] In a CSI report, one of two sub-band sizes can be specified. A sub-band can be defined by N... SB PRB A series of PRB definitions. In a BWP, when the number of PRBs is between 24 and 72, N SB PRB It can be 4 or 8. In a BWP, where the number of PRBs is between 73 and 144, N... SB PRB It can be 8 or 16. In a BWP, where the number of PRBs is between 145 and 275, N... SB PRB It can be 16 or 32.

[0338] Upper-level parameters (e.g., `reportFreqConfiguration`) can indicate the frequency granularity of CSI reporting. A CSI reporting configuration can define the frequency band of the CSI report as a subset of the sub-bands of a BWP. Upper-level parameters can indicate a subset of sub-bands within a BWP. Sub-bands can be continuous or discontinuous. A BWP can be a BWP that reports CSI. It is not expected that a configuration will have a sub-band with a frequency density lower than that of a CSI-RS resource. A CSI-RS resource can have a frequency density within a sub-band. A CSI-RS can be linked to a CSI reporting configuration. The frequency density can be the density of each CSI-RS port (CSI port, antenna port) of each PRB.

[0339] When CSI-IM resources and CSI reports are linked, it is not expected that a sub-band will be set. All PRBs in a sub-band may not have CSI-IM resource elements (REs).

[0340] Frequency granularity can be either wideband CQI or sub-band CQI reporting. When full-band CQI reporting is configured, full-band CQI can also be reported for the entire CSI reporting band. When sub-band CQI reporting is configured, a single CQI can be reported for each sub-band within the CSI reporting band.

[0341] Frequency granularity can be either full-band PMI or sub-band PMI reporting. When full-band PMI reporting is enabled, a single full-band PMI can be reported for the entire CSI reporting band. When sub-band PMI reporting is enabled, a single full-band indication (i1) can be reported for the entire CSI reporting band, or a sub-band indication (i2) can be reported for each sub-band within the CSI reporting band.

[0342] Under certain conditions, the frequency granularity can be full-band. These conditions could be setting up full-band PMI reporting and full-band CQI reporting, with CRI, RI, PMI, and CQI set in the report quantity ('cri-RI-PMI-CQI'). Alternatively, it could be setting up full-band PMI reporting and full-band CQI reporting, with CRI, LI, PMI, and CQI set in the report quantity ('cri-LI-PMI-CQI'). Another condition could be setting CRI, RI, and i1 in the report quantity ('cri-RI-i1'). If these conditions are not met, the frequency granularity can be sub-band.

[0343] When a CSI report setting is configured for a BWP with fewer than 24 PRBs, a CSI report setting with full-band frequency granularity can be expected.

[0344] One or N sub-bands can be set. This can be based on the starting PRB position N of the BWP. start BWP，i This limits the size of the first sub-band. The size of the Nth sub-band can be limited based on the starting PRB position of the BWP and the BWP size.

[0345] Terminal device 1 can report CSI. When semi-persistent CSI reporting is configured and both CSI-IM and NZP CSI-RS resources are configured as periodic or semi-persistent, terminal device 1 can report CSI. When non-periodic CSI reporting is configured and both CSI-IM and NZP CSI-RS resources are configured as periodic, semi-persistent, or non-periodic, terminal device 1 can report CSI.

[0346] DCI formats 0_1 / 0_2 / 0_3 can trigger CSI reports. Terminal device 1 may also not expect multiple CSI reports associated with the same CSI report settings to be triggered.

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

[0348] When a CSI resource setting is configured, it can correspond to either channel measurement for L1-RSRP or channel / interference measurement for L1-SINR calculation. A CSI resource setting can be specified using resourcesForChannelMeasurement.

[0349] With two CSI resource settings configured, the first CSI resource setting can be used for channel measurement, and the second CSI resource setting can be used for interference measurement performed in CSI-IM or NZP CSI-RS. The first CSI resource setting can be provided via resourcesForChannelMeasurement. The second CSI resource setting can be provided via csi-IM-ResourcesForInterference or nzp-CSI-RS-ResourcesForInterference.

[0350] Three CSI resource settings can be configured. The first CSI resource setting can be used for channel measurement. The second CSI resource setting can be used for interference measurement based on CSI-IM. The third CSI resource setting can be used for interference measurement based on NZP CSI-RS. The first CSI resource setting can be specified via resourcesForChannelMeasurement. The second CSI resource setting can be specified via csi-IM-ResourcesForInterference. The third CSI resource setting can be specified via nzp-CSI-RS-ResourcesForInterference. resourcesForChannelMeasurement, csi-IM-ResourcesForInterference, and nzp-CSI-RS-ResourcesForInterference can all be configured within a single CSI report setting.

[0351] For non-periodic CSI (CSI reporting) and for both periodic and non-persistent CSI resource settings, each trigger state can be associated with one or more CSI reporting settings. Each CSI reporting setting can be linked to either periodic or non-persistent CSI resource settings. Group-based reporting can be configured for each CSI reporting setting. When a CSI resource setting is configured, that setting can be used for L1-RSRP measurements. In this case, the number of CSI-RS resource sets in the CSI resource setting can be two.

[0352] For non-periodic CSI (CSI reports) and for non-periodic CSI resource settings, each trigger state can be associated with one or more CSI report settings. For each CSI report setting, group-based reports can be configured. Each CSI report setting can be associated with a first CSI-RS resource set and a second CSI-RS resource set used for L1-RSRP measurements.

[0353] For semi-persistent or periodic CSI (CSI reporting), each CSI reporting setting can be linked to a periodic or semi-persistent CSI resource setting. With one CSI resource setting configured, it can be used for channel measurements for L1-RSRP or for channel / interference measurements for L1-SINR. With two CSI resource settings configured, the first setting can be used for channel measurements, and the second setting can be used for interference measurements performed in CSI-IM. In the case of L1-SINR calculation, the second CSI resource setting can be used for interference measurements performed in CSI-IM or NZP CSI-RS.

[0354] When type 2 is set in the codebook settings, the number of CSI-RS resources in the CSI-RS resource set for channel determination in the CSI report settings can be 1.

[0355] In a CSI resource configuration, it is not necessary to expect more than 64 NZP CSI-RS resources and SS / PBCH block resources, or either one or both. A CSI resource configuration can be used for channel determination. In the CSI report configuration corresponding to the CSI resource configuration used for channel determination, the report quantity setting can 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 determination is performed in CSI-IM, each CSI-RS resource used for channel determination can be associated with a CSI-IM resource. The number of CSI-RS resources used for channel determination can be equal to the number of CSI-IM resources.

[0356] In measurements other than L1-SINR measurements (e.g., CSI measurements), the ports of each NZPCSI-RS configured for interference measurement can also correspond to the interference transmission layer. In measurements other than L1-SINR measurements (e.g., CSI measurements), all interference transmission layers in the ports of the NZP CSI-RS can be considered for EPRE. In L1-SINR measurements, dedicated interference measurement resources can be configured. The total received power in the dedicated resources can correspond to the interference-to-noise ratio.

[0357] In a CSI report setting, the report quantity can 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.

[0358] If none is set in the reporting quantity settings, terminal device 1 may not report CSI.

[0359] When cri-RI-PMI-CQI or cri-RI-LI-PMI-CQI is set in the reporting quantity settings, terminal device 1 can report the first PMI. The first PMI can be the precoder matrix for each sub-band. The first PMI can also be the precoder matrix for the entire CSI reporting band.

[0360] When cri-RI-i1 is set in the reporting quantity settings, terminal device 1 can report a second PMI. The second PMI can consist of a single full-band indication i1. Type 1 can be set in the codebook settings of the CSI reporting settings. The frequency granularity used for the PMI in the CSI reporting settings can be full-band.

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

[0362] When cri-RI-CQI is set in the reporting quantity settings, terminal device 1 can report RI. Terminal device 1 can calculate CQI for a rank.

[0363] When cri-RSRP, ssb-Index-RSRP, cri-RSRP-Index, or ssb-Index-RSRP-Index are set in the reporting quantity settings, and group-based reporting is not set, terminal device 1 can set N different CRIs or SSBRIs for each CSI report. Furthermore, terminal device 1 can also avoid being updated by requested measurements. N can be determined by upper-layer parameters (e.g., nrofReportedRS).

[0364] When cri-RSRP, ssb-Index-RSRP, cri-RSRP-Index, or ssb-Index-RSRP-Index are set in the reporting volume settings, and group-based reporting is configured, terminal device 1 can set two different CRIs or SSBRIs for each CSI report. Furthermore, terminal device 1 can be requested to update measurements for more than 64 CSI-RS / SSB resources. Terminal device 1 can simultaneously receive CSI-RS / SSB resources.

[0365] If cri-SINR, ssb-Index-SINR, cri-SINR-Index or ssb-Index-SINR-Index are set in the report quantity settings and no group-based reporting is set, the terminal device 1 can set N different CRIs or SSBRIs for each CSI report.

[0366] When cri-SINR, ssb-Index-SINR, cri-SINR-Index or ssb-Index-SINR-Index are set in the report quantity settings and group-based reporting is set, terminal device 1 can set two different CRIs or SSBRIs for each CSI report.

[0367] When TDCP is set in the reporting quantity settings, terminal device 1 can report the amplitude and phase measured by TDCP.

[0368] When the reporting quantity settings include 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 can calculate CSI parameters other than CRI based on CRI. The (k+1)th entry of the NZP CSI-RS resource in the NZP CSI-RS resource set for channel measurement can correspond to the CRI value k. The (k+1)th entry of the CSI-IM resource in the CSI-IM resource set for interference measurement can correspond to the CRI value k. The (k+1)th entry of the NZP CSI-RS resource in the NZP CSI-RS resource set for interference measurement can correspond to the CRI value k. K s It can be greater than 1. In K s With a value of 2, each CSI-RS resource can have a maximum of 16 CSI-RS ports (CSI ports, antenna ports). In K... s With a value of 3 or higher but less than 8, each CSI-RS resource can have a maximum of 8 CSI-RS ports. If cri-RI-PMI-CQI is set in the report quantity settings, type 2 does not need to be set in the codebook settings.

[0369] With CJT configured, each resource can include a maximum of 32 CSI-RS ports. CJT can be configured by setting 'cri-RI-PMI-CQI' in the report quantity setting within the CSI report settings and setting 'typeII-CJT-r18' or 'typeII-CJT-PortSelection-r18' in the codebook settings. With CJT configured, the NZP CSI-RS resource set used for channel determination can be configured with K resources. K can be an integer from 1 to 4.

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

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

[0372] In the case where cri-RSRP, cri-SINR, none, cri-RSRP-Index, or cri-SINR-Index are set in the reporting quantity settings, and a CSI reporting setting is linked to a non-periodic CSI resource setting, it is not expected that more than 16 CSI-RS resources will be set in a CSI-RS resource set within a CSI resource setting.

[0373] In L1-RSRP calculations, CSI-RS resources, SS / PBCH block resources, or both CSI-RS and SS / PBCH block resources can be configured. Up to 16 CSI-RS resource sets can be configured in L1-RSRP calculations, or up to 64 CSI-RS resources can be configured within each CSI-RS resource set.

[0374] In L1-RSRP calculation, when each CSI report is configured to report a CRI or SSBRI (e.g., nrofReportedRS is 1), the reported L1-RSRP value can be defined using 7 bits. The range of L1-RSRP values ​​can be from -140 dBm to -44 dBm. L1-RSRP values ​​can be given in 1 dB intervals.

[0375] In L1-RSRP calculation, when multiple CRIs or SSBRIs are specified for each CSI report (e.g., nrofReportedRS is 2 or higher), the first value of the reported L1-RSRP can be defined using 7 bits, and the second value of the reported L1-RSRP can be defined using 4 bits. The range of the first value can be -140dBm to -44dBm. The first value can be given in 1dB intervals. The second value can be calculated as the difference between the first values. The second value can be given in 2dB intervals.

[0376] In L1-SINR calculation, one or both of the NZP CSI-RS resources and SS / PBCH block resources can be configured for channel measurement. In L1-SINR calculation, either the NZP CSI-RS resources or the CSI-IM resources can be configured for interference measurement.

[0377] In L1-SINR calculation and channel determination, CSI resource settings with up to 16 CSI-RS resource sets can be configured, and a total of 64 CSI-RS resources or SS / PBCH block resources can be configured.

[0378] In L1-SINR calculation, when each CSI report is configured to report a CRI or SSBRI (e.g., nrofReportedRS is 1), the reported L1-SINR value can be defined using 7 bits. The range of L1-SINR values ​​can be from -23 to 40 dB. L1-SINR values ​​can be given in 0.5 dB intervals.

[0379] In L1-SINR calculation, when multiple CRIs or SSBRIs are reported for each CSI report (e.g., nrofReportedRS is 2 or higher), the first value of the reported L1-SINR can be defined by 7 bits, and the second value of the reported L1-SINR can be defined by 4 bits. The range of the first value can be -23dB to 40dB. The first value can be given in 0.5dB intervals. The second value can be calculated as the difference between the first values. The second value can be given in 1dB intervals.

[0380] Non-periodic CSI reports can correspond to non-periodic CSI-RS.

[0381] In the CSI-RS resource set associated with aperiodic, periodic, or semi-persistent CSI resource settings, trigger states can be set for aperiodic CSI reporting settings via upper-layer parameters (e.g., CSI-AperiodicTriggerStateList). Trigger states can be set for CSI resource settings used for channel measurement and interference measurement, or for both.

[0382] In the non-periodic CSI reporting settings, a set of trigger states can be set by the upper layer. A trigger state can be associated with any downlink BWP.

[0383] Terminal device 1 can receive DCIs with a CSI request field. It is not expected that more than two DCIs with a CSI request field having a non-zero value will be received in a time slot within a cell.

[0384] It is not expected that multiple aperiodic CSI-RS resource sets with the same trigger offset under the same trigger state will have different TCI states for the same aperiodic CSI-RS resource ID.

[0385] It is not advisable to expect more than two requests for non-periodic CSI reports to be received in a time slot within a cell.

[0386] The trigger state can be initiated by the CSI request field in the DCI. If all information bits in the CSI request field are set to zero, a CSI request can be omitted.

[0387] The number of triggered states is 2^N TS In cases where the value is -1 or higher, terminal device 1 can receive a subselection indication. The subselection indication can be used to select up to 2^N... TS -1 trigger state is mapped to a code point in the CSI request field. N TS This can be the number of bits in the CSI request field.

[0388] When terminal device 1 transmits the first PUCCH in time slot n, the mapping between the CSI request field and the trigger state is applied after time slot n+N. The first PUCCH may be a PUCCH with HARQ-ACK information corresponding to the PDSCH with the transmit subselection indication.

[0389] The CSI request field can indicate a trigger state. For example, when the number of trigger states is less than 2^N. TS In the case of -1, the CSI request field can indicate a trigger status.

[0390] A first QCL setting and a first QCL type can be indicated for each non-periodic CSI-RS resource in a set of CSI-RS resources associated with each CSI triggering state.

[0391] In cases where a list of trigger states for aperiodic CSI is configured (e.g., CSI-AperiodicTriggerStateList) and a CSI resource setting linked to a CSI reporting setting has multiple aperiodic CSI-RS resource sets, an aperiodic CSI-RS resource set can be associated with a trigger state. Within a trigger state of a CSI resource setting, a CSI-IM / NZP CSI-RS resource set can be selected.

[0392] When using aperiodic CSI reporting and aperiodic CSI-RS, a trigger offset (or CSI-RS offset) can be set within a CSI-RS resource set (NZP CSI-RS resource set, CMI-IM resource set, or SS / PBCH block resource set). The trigger offset can be set by upper-layer parameters (e.g., aperiodicTriggeringOffset). The trigger offset can include a number of time slots from 0 to N. N can be based on the subcarrier spacing of the CSI-RS. The trigger offset for CSI-IM can be based on the trigger offset of the NZP CSI-RS used for channel determination.

[0393] Terminal device 1 can receive CSI-RS. Non-periodic CSI-RS can be transmitted in time slot n+X. Time slot n can be the time slot that includes the DCI that triggers the CSI-RS. X can be the trigger offset.

[0394] Aperiodic CSI-RS may not be transmitted before the first OFDM symbol. The first OFDM symbol may be the symbol that transmits the DCI that triggers the CSI-RS transmission. When a minimum scheduling offset limit is applied and the trigger offset is below the minimum scheduling offset limit, triggering via the trigger state indicated by the CSI request field in the DCI is not expected. CSI-RS transmission can be triggered via the trigger state indicated by the DCI request field in the DCI.

[0395] When performing interference measurement in a non-periodic NZP CSI-RS, the trigger offset of the NZP CSI-RS used for interference measurement can be the same as the trigger offset of the NZP CSI-RS used for channel measurement.

[0396] In a single carrier, it is not expected that multiple CSI reports triggered by different DCIs will be transmitted in the same OFDM symbol.

[0397] The scheduling offset between the last symbol of the PDCCH that triggers the DCI of the aperiodic CSI-RS resource and the first symbol of the aperiodic CSI-RS resource can be determined. In the presence of two PDCCH candidates, the later-ending PDCCH candidate can be used to determine the scheduling offset. The last symbol of the earlier-ending PDCCH candidate can be the same as or follow the first symbol of the aperiodic CSI-RS resource.

[0398] Semi-persistent CSI can be equated with semi-persistent CSI-RS.

[0399] In a semi-persistent CSI report within PUSCH, the set of trigger states can be set via upper-layer parameters (e.g., SemiiPersistentOnPUSCH-TriggerStateList). A trigger state can be activated by the CSI request field in a DCI scrambled by SP-CSI-RNTI. Terminal device 1 may also choose not to receive a first DCI activating the first semi-persistent CSI report. The first semi-persistent CSI report may include the same CSI report ID as the second semi-persistent CSI report. The second semi-persistent CSI report can be activated by a second DCI. Both the first and second DCIs can be scrambled by SP-CSI-RNTI. Terminal device 1 may receive the second DCI before the first DCI.

[0400] In a semi-persistent CSI report within a PUCCH, the PUCCH resource used to send the CSI report can be configured via the upper-layer parameter (reportConfigType). A semi-persistent CSI report within a PUCCH can be activated by an activation command. The activation command can select a semi-persistent CSI report setting. Terminal device 1 can receive a PDSCH that transmits the activation command. Terminal device 1 can send a PUCCH with HARQ-ACK information corresponding to the PDSCH in time slot n. The selected semi-persistent CSI report setting can also be applied after time slot n+N.

[0401] When a semi-persistent CSI resource setting is configured (e.g., semiPersistent is set in resourceType) and terminal device 1 receives an activation command, it can apply CSI-RS / CSI-IM transmission starting from time slot n+N for the CSI-RS resource set used for channel determination and the CSI-IM / NZP CSI-RS resource set used for interference determination. Terminal device 1 can transmit a PUCCH in time slot n that includes HARQ-ACK information corresponding to the PDSCH used to transmit the command.

[0402] Terminal device 1 can receive a disable command. When a semi-persistent CSI resource setting is configured and terminal device 1 receives a disable command, the transmission of CSI-RS / CSI-IM can be suspended starting from time slot n+N. Terminal device 1 can transmit a PUCCH in time slot n, which includes HARQ-ACK information corresponding to the PDSCH transmitting the disable command.

[0403] A triggering state (e.g., SP-CSI triggering state) can be mapped to a code point in the CSI request field of the DCI. Terminal device 1 can verify the PDCCH in the DCI for the activation or deactivation (release) of semi-persistent CSI. For example, terminal device 1 can verify the PDCCH when the CRC in the DCI format is scrambled by SP-CSI-RNTI. For example, terminal device 1 can activate or disable semi-persistent CSI based on values ​​set in specific fields within the DCI format.

[0404] Terminal device 1 can activate or disable the CSI reporting settings indicated by the DCI request field in DCI.

[0405] CSI resource settings can be considered when CSI resource settings (e.g., CSI-RS / CSI-IM resource settings or ZP (Zero power) CSI-RS resource set settings) are active and the corresponding downlink BWP is active. CSI resource settings can be suspended when CSI resource settings (e.g., CSI-RS / CSI-IM resource settings or ZP (Zero power) CSI-RS resource set settings) are active and the corresponding downlink BWP is disabled.

[0406] Terminal device 1 can report CQI. Terminal device 1 can calculate a CQI index. The modulation scheme, coding, and transport block size of the PDSCH transport block can correspond to a CQI index. Terminal device 1 can receive PDSCH transport blocks in a manner that does not exceed the target error probability. The target error probability can be the transport block error probability. The target error probability can be 0.1 or 0.00001.

[0407] Terminal device 1 can report PMI. Terminal device 1 can determine 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 ν can be associated with RI. The PMI value corresponding to type 1 can be determined by i1∈i 1，1 i 1，2 i 1，3 i 1，4And constitutes part or all of i2. The PMI corresponding to type 1 can be the PMI in the case where type I-SinglePanel or type I-MultiPanel is set in the codebook setting. The value of the PMI corresponding to type 2 can be composed of i1∈i 1，1 i 1，2 i 1，3，1 i 1，3，2 i 1，4，1 i 1，4，2 And constitutes part or all of i2. The PMI corresponding to type 2 can be the PMI in the case where any one of 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 is set in the codebook setting.

[0408] Without an extended CSI port configured, the number of CSI ports can be any one of 4, 8, 12, 16, 24, and 32. With an extended CSI port configured, the number of CSI ports can be any one of 48, 64, 96, and 128. Not configuring an extended CSI port can be done by configuring any one of the following CSI port numbers: 4, 8, 12, 16, 24, and 32. Configuring an extended CSI port can be done by configuring any one of the following CSI port numbers: 48, 64, 96, and 128.

[0409] One or more NZP CSI-RS resource sets can be configured through CSI resource settings (CSI-ResourceConfig). Each NZP CSI-RS resource set can consist of one or more CSI-RS resources. One or more parameters P can be set for NZP CSI-RS resources, NZP CSI-RS resource sets, and some or all of the CSI resource settings.

[0410] One or more parameters may include the ID of the NZP CSI-RS resource. The ID of the NZP CSI-RS resource determines the identifier of the CSI-RS resource.

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

[0412] One or more parameters P may include the number of antenna ports, CDM (Code Domain Multiplexing) type, OFDM symbols, and first upper-layer parameters (e.g., resource mapping) of the subcarriers. The first upper-layer parameters may correspond to CSI-RS resources in a time slot.

[0413] One or more parameters P may include a second upper-level parameter that determines the number of antenna ports. The second upper-level parameter may be determined within the first upper-level parameter.

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

[0415] One or more parameters P may include a fourth higher-level parameter that determines the CDM type. This fourth higher-level parameter can be set within the first higher-level parameter. The fourth higher-level parameter can determine the CDM's value and mode.

[0416] One or more parameters P may include parameters that determine the energy per resource element (EPRE) ratio of PDSCH to NZP CSI-RS per RE.

[0417] One or more parameters P may include parameters that determine the power ratio of each RE in the NZP CSI-RS to the SS / PBCH block.

[0418] One or more parameters P may include a scrambling ID. The length of the scrambling ID can be 10 bits.

[0419] One or more parameters P may include the BWP ID. The BWP ID can be set in the CSI resource settings. The BWP ID can identify the BWP where the CSI-RS is located.

[0420] One or more parameters P may include a repeat setting. The repeat setting can be configured within a CSI-RS resource set. In an NZP CSI-RS resource set used for repeating (an NZP CSI-RS resource set with repeating configured), it can be assumed that the CSI-RS resources in the NZP CSI-RS resource set are transmitted through the same downlink spatial area transmission filter. The repeat setting can be configured when cri-RSRP, cri-SINR, cri-RSRP-Index, cri-SINR-Index, or none is set in the reporting quantity settings.

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

[0422] One or more parameters P may include a TRS (Tracking Reference Signal) setting. The TRS setting can be configured within a CSI-RS resource set. Within an NZP CSI-RS resource set used for TRS (an NZP CSI-RS resource set with TRS configured), the antenna ports of the NZP CSI-RS resources within the NZP CSI-RS resource set can be identical.

[0423] The same frequency density and the same number of antenna ports can be set for all CSI-RS resources used for channel measurement within a CSI-RS resource set. The same starting RB (Resource Block) location, the same number of RBs, and the same CDM type can be set for all CSI-RS resources within a CSI-RS resource set.

[0424] The frequency band and starting CRB (Common Resource Block) index of a CSI-RS resource can be determined by the starting RB position and the number of RBs. The starting RB position and the number of RBs can be determined by upper-level parameters (e.g., startingRB and nrofRBs). The starting RB position and the number of RBs can be set to integer multiples of 4 RBs. The reference position for the starting RB position can be CRB0. The frequency band (number of RBs) of the CSI-RS resource can be 24 RBs or larger and the BWP size or larger.

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

[0426] One or more parameters Q may include the CSI-IM resource ID. One or more parameters Q may include the subcarrier position k within a time slot of the CSI-IM resource. CSI-IM The parameters. One or more parameters Q may include determining the OFDM symbol location within a time slot of the CSI-IM resource. CSI-IM The parameters. One or more parameters Q may include parameters that determine the period and slot offset for periodic / semi-persistent CSI-IM. One or more parameters Q may include parameters that determine the frequency band of CSI-IM.

[0427] A CSI-IM resource can consist of four REs. For example, in Mode 1, a CSI-IM resource can consist of (k... CSI-IM , l CSI-IM ), (k CSI-IM , l CSI-IM +1), (k CSI-IM +1, l CSI-IM ) and (k CSI-IM +1, l CSI-IM +1) corresponds to the RE. For example, in mode 2, CSI-IM resources can be composed of (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 +1) corresponds to the RE structure.

[0428] CSI can be calculated based on CSI reference resources. In the frequency domain, the CSI reference resource can be a PRB (Physical Resource Block) corresponding to the frequency band where the CSI is calculated. In the time domain, the CSI reference resource can be a time slot. A time slot can be N timeslots ahead of the CSI reporting time slot. N time slots can be determined based on the delay time.

[0429] Terminal device 1 can calculate the CQI (CQI Index) based on CSI reference resources, and can also report it. Terminal device 1 can assume one or more conditions to calculate the CQI.

[0430] One or more of the following conditions may be: two OFDM symbols are occupied by control signals. One or more of the following conditions may be: the number of PDSCH and DMRS symbols is 12. One or more of the following conditions may be: the same subcarrier spacing as PDSCH reception. One or more of the following conditions may be: CSI reference resources use the same CP length and subcarrier spacing as PDSCH. One or more of the following conditions may be: no REs are available for PBCH, PSS, or SSS. One or more of the following conditions may be: redundancy version is 0. One or more of the following conditions may be: no REs are available allocated for NZP CSI-RS and ZP CSI-RS. One or more of the following conditions may be: using the maximum set front-loaded DMRS symbol count. One or more of the following conditions may be: using the set additional DMRS symbol count. One or more of the following conditions may be: OFDM symbols used for PDSCH do not include DMRS. One or more of the following conditions may be: two PRBs are bundled.

[0431] One of the conditions can be the signal of layer ν in the PDSCH multiplied by the precoder corresponding to the PMI. The maximum number of layers can be 8.

[0432] Terminal device 1 can use PUSCH to report CSI. Terminal device 1 can report non-periodic CSI via PUSCH based on the decoding of the DCI format triggered by the trigger state.

[0433] The DCI format can schedule two PUSCHs. In this case, non-periodic CSI reports can be executed in the second PUSCH. The DCI format can schedule more than three PUSCHs. In this case, non-periodic CSI reports can be executed in the penultimate PUSCH.

[0434] The non-periodic CSI report in PUSCH can correspond to the frequency granularity of the full band and sub-band.

[0435] Terminal device 1 can report a semi-persistent CSI in the PUSCH based on the decoding of the DCI format of the activation trigger state. The CSI request field in the DCI format can indicate whether the trigger state is used for activation or deactivation.

[0436] Non-periodic CSI reports in the PUSCH can be reused with uplink data in the PUSCH. Alternatively, the reuse of semi-persistent CSI reports in the PUSCH with uplink data can be disregarded.

[0437] When reporting (or responding to) PMI in PUSCH, the CSI report can consist of Part 1 and Part 2. Part 1 can be a fixed-size payload that indicates the number of information bits in Part 2. Part 1 can be appended or sent before Part 2.

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

[0439] Terminal device 1 can use PUCCH to report CSI. The CSI reporting in PUCCH can be configured by the upper layer. Multiple periodic CSI reports corresponding to multiple CSI reporting settings can be configured by the upper layer.

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

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

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

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

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

[0445] The TCI (Transmission Configuration Indication) field can be included in one or both of DCI format 1_1 and DCI format 1_2. For example, when setting upper-layer parameters, the TCI field can be included in one or both of DCI format 1_1 and DCI format 1_2. For example, when setting the upper-layer parameter tci-PresentInDCI, the TCI field can be included in one or both of DCI format 1_1 and DCI format 1_2. One or two TCI states can be indicated by the DCI format. One or more (e.g., two) TCI states can be indicated by the TCI field in the DCI format.

[0446] DCI formats 0_0 / 0_1 / 0_2 can be used for PUSCH scheduling. The BWP (Bandwidth Part Indicator) field can be included in some or all of DCI formats 0_1 and 0_2. The number of information bits constituting the BWP field can be determined based on the number of UL BWPs. The TPC command for scheduled PUSCH field can be included in one or both of DCI formats 0_1 and 0_2. The Second TPC command for scheduled PUSCH field can be included in one or both of DCI formats 0_1 and 0_2. For example, when setting the upper-layer parameter SecondTPCFieldDCI, the Second TPC command for scheduled PUSCH field can be included in DCI format 1_1.

[0447] CSI-RS (Channel State Information Reference Signal) can be either ZP (zero power) CSI-RS or NZP (Non-zero-power) CSI-RS.

[0448] The CSI-RS sequence can be r(m). r(m) can be determined by a pseudo-random sequence (e.g., gold code). The pseudo-random sequence can be based on the OFDM symbol index within a time slot and the time slot index n within a radio frame. μ s，f And initialize with a scrambling ID.

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

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

[0451] In r(m), m can be floor(n*α) + k' + floor((k bar *ρ) / N RB SC *This can be multiplication.

[0452] ρ can be the frequency density. When the number of antenna ports is 1, α can be ρ. When the number of antenna ports is 2 or more, α can be 2ρ. When ρ is 1, each antenna port can be mapped to every 1 RB. When ρ is 0.5, each antenna port can be mapped to every 2 RBs. When ρ is an even number (0.5), each antenna port can be mapped to the even-numbered RB every 2 RBs. When ρ is an odd number (0.5), each antenna port can be mapped to the odd-numbered RB every 2 RBs.

[0453] The subcarrier position k can be set by the PRB position n and the subcarrier position k. bar The index k' is used to determine this, along with the FD-OCC (Frequencydomain-Orthogonal cover code) index k'.

[0454] The subcarrier position k=0 can correspond to subcarrier 0 in CRB0.

[0455] The PRB position n can be a value from 0 to N-1. N can be the frequency band of the CSI-RS resource (e.g., the number of RBs: nrofRBs).

[0456] Subcarrier position setting k bar The subcarrier position within a time slot can be determined. The subcarrier position is set to k. bar The subcarrier position can be determined based on the number of antenna ports, frequency density, and CDM type. bar It can be a subcarrier location within an RB. k bar It can be ki k i-1 It can be f(i). f(i) can be the bit number of the i-th bit set to 1 in the bitmap. The bitmap can be provided by upper-layer parameters (e.g., frequencyDomainAllocation). The size of the bitmap can be determined based at least on the number of antenna ports. f(i) can be repeated every ceil(1 / ρ) RBs.

[0457] The FD-OCC index k' can be determined by the CDM type. If no CDM is specified in the CDM type, k' can be 0. If a CDM of length 2 is specified in the Frequency Domain (FD) of the CDM type, k' can be either 0 or 1.

[0458] The OFDM symbol position can be set by the OFDM symbol position. bar It is determined by the TD-OCC (Time domain-Orthogonal cover code) index l'.

[0459] OFDM symbol position setting l bar The symbol position within a time slot can be determined. OFDM symbol position setting l bar It can be determined based on the number of antenna ports, frequency density, and CDM type. bar It can be one or both of l0 and l1. l0 can be determined by a first upper-level parameter (e.g., firstOFDMSymbolInTimeDomain). l1 can be determined by a second upper-level parameter (e.g., firstOFDMSymbolInTimeDomain2). l0 can be an integer value from 0 to 13. l1 can be an integer value from 2 to 12.

[0460] The TD-OCC index l' can be determined by the CDM type. If no CDM is specified in the CDM type, l' can be 0. If a CDM of length 2 in the Time Domain (TD) is specified in the CDM type, l' can be 0 or 1. If a CDM of length 4 in the Time Domain is specified in the CDM type, l' can be 0, 1, 2, or 3.

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

[0462] When the FD-OCC index k' is 0, w f (k') can be 0. When the FD-OCC index k' is 0 or 1, [w f (0)w f (1)] can be vectors [+1 +1] and [+1 -1]. When the TD-OCC index l' is 0, wt(l') can be 0. When the TD-OCC index l' is 0 and 1, [w t (0)w t (1)] can be vectors [+1 +1] and [+1 -1]. When the TD-OCC index l' is 0, 1, 2, and 3, [w t (0)w t (1) w t (2) w t (3)] ​​can be vectors [+1 +1 +1 +1], [+1 -1 +1 -1], [+1 +1 -1 -1], and [+1 -1 -1 +1]. The sequence index s can be indexed first using FD-OCC and then using TD-OCC. For example, in the case where an FD-OCC of length 2 and a TD-OCC of length 4 are set in the 0DM type, the sequence index s=0 can be [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], the sequence index s=1 can be [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], the sequence index s = 2 can be [w f (0)w f (1)]=[+1 +1]and[w t (0)wt (1) w t (2) w t (3)] ​​= [+1 -1 +1 -1], the sequence index s = 3 can be [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], the sequence index s = 4 can be [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], the sequence index s = 5 can be [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], the sequence index s = 6 can be [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], the sequence index s = 7 can be [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].

[0463] CDM groups can be indexed first using frequency resources and then using time resources. For example, with 32 antenna ports and an FD-OCC (fd-CDM2) of length 2 set in the CDM type, the CDM group index j can be indexed in the order of time and 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).

[0464] Terminal device 1 may not expect to receive CSI-RS and DMRS in the same RE. Antenna ports within a CSI-RS resource may be QCL relative to each other with respect to type A. Terminal device 1 may expect antenna ports within a CSI-RS resource to have average gain.

[0465] CJT (Coherent Joint Transmission) can be applied to PDSCH. When CJT method A is configured and both "indicated TCI states" are applied to the PDSCH, the DMRS of the PDSCH can have a QCL with respect to the downlink reference signals of the two "indicated TCI states" about type A. When CJT method B is configured and both "indicated TCI states" are applied to the PDSCH, the DMRS of the PDSCH can also have a QCL with respect to the downlink reference signals of the two "indicated TCI states" about type A, but the {Doppler shift, Doppler spread} of the second indicated TCI state can be excluded.

[0466] CJT can be set to apply either CJT method A or CJT method B. CJT method A can be set by the upper-level parameter cjtSchemeA. CJT method B can be set by the upper-level parameter cjtSchemeB.

[0467] The "indicated TCI state" applied to PDSCH can be determined by the upper-level parameter applyIndicatedTCIState. When CJT is set, applyIndicatedTCIState can also indicate 'both'.

[0468] CJT can be set in the codebook settings.

[0469] For example, CJT can be set in the codebook settings as 'typeII-CJT-r18' or 'typeII-CJT-PortSelection-r18'. The codebook settings can be set in the CSI report settings.

[0470] If at least PMI is set in the report quantity settings of the CSI report settings and CJT is set in the codebook settings of the CSI report settings, K CSI-RS resources can be set in the CSI-RS resource set for channel measurement. K can be an integer from 1 to 4. K can be the number of TRPs. When performing interference measurement in CSI-IM, one CSI-IM resource can be set in the CSI-IM resource set. When performing interference measurement in NZP CSI-RS, one NZP CSI-RS resource can be set in the NZP CSI-RS resource set for interference measurement.

[0471] When N4 is configured in the CSI report settings and 'cri-RI-PMI-CQI' is configured in the report quantity settings, K aperiodic CSI-RS resources or one semi-persistent CSI-RS resource can be configured in the CSI-RS resource set for channel determination. In the aperiodic CSI-RS resource set, the K CSI-RS resources can be triggered by the same triggering instance, and two consecutive CSI-RS resources can be configured in one or two time slots. The K aperiodic CSI-RS resources can be transmitted in order of their CSI-RS resource IDs. CSI-RS resource IDs can be configured in a single CSI-RS resource set. The K aperiodic CSI-RS resources can correspond to the same antenna port with the same port index. When performing interference determination in CSI-IM, one resource (CSI-IM resource) can be configured in a single CSI-IM resource set. When performing interference measurements in NZP CSI-RS, a resource (NZP CSI-RS resource) can be set in the NZP CSI-RS resource set used for interference measurements. K can be 4, 8, or 12.

[0472] Two resource groups can be set. For example, an NZP CSI-RS resource set used for channel determination can be accompanied by K S There are K1 resources, and they can be set by two resource groups. In group 1, K1 resources can be set. In group 2, K2 resources can be set. K1 + K2 can be K... s In addition, N resource pairs can be set. Each resource pair can consist of one resource from group 1 and one resource from group 2. K sIt can be an integer from 2 to 8. N can be 1 or 2.

[0473] When 'cri-RI-PMI-CQI' is set in the report quantity setting of a CSI report configuration and 'typeII-CJT-r18' or 'typeII-CJT-PortSelection-r18' is set in the codebook setting of a CSI report configuration, an NZP CSI-RS resource set for channel determination can be configured by K resources (CSI-RS resources). Each resource (CSI-RS resource) can include up to 32 CSI-RS ports (antenna ports). K can be an integer from 1 to 4.

[0474] Setting 'typeII-CJT-r18' in the codebook settings allows you to configure the super-extended type 2-CJT. Setting 'typeII-CJT-r18' in the codebook settings also allows you to configure CJT. When CJT is configured and N is set... TRP In the case of N CSI-RS resources TRP For each CSI-RS resource, N1, N2, O1, and O2 can be the same. (N1, N2) and (O1, O2) can be determined by the number of antenna ports in the PCSI-RS. For example, with 4 antenna ports, (N1, N2) = (2, 1) and (O1, O2) = (4, 1). Similarly, with 8 antenna ports, (N1, N2) = (2, 2) and (O1, O2) = (4, 4). CSI-RS It can be 2*N1*N2. N TRP Each CSI-RS resource can be set within a resource set (CSI-RS resource set) used for channel determination. N TRP It can be 1, 2, 3 or 4.

[0475] With CJT set, PMI can be determined based on (N1, N2) and (O1, O2). (N1, N2) can be based on the number of antenna ports P. CSI-RS It is determined by the parameters of the upper layer.

[0476] Setting 'typeII-CJT-PortSelection-r18' in the codebook settings allows you to configure the super-extension type 2 - port selection CJT. Setting 'typeII-CJT-PortSelection-r18' in the codebook settings allows you to configure CJT.

[0477] With CJT configured, the slot offsets of K CSI-RS resources can be set within slot X. X can be 1 or 2. With X=1, the K CSI-RS resources can be set within the same slot. With X=2, the K CSI-RS resources can be set within two adjacent slots. Setting CJT can be a CSI report setting accompanied by a codebook setting of 'typeII-CJT-r18' or 'typeII-CJT-PortSelection-r18' linked to a CSI-RS resource set (e.g., an NZP CSI-RS resource set for channel determination). A CSI-RS resource set can include K resources (CSI-RS resources). K can be an integer from 1 to 4.

[0478] Not configuring CJT can be configured with NCJT (Non-Coherent Joint Transmission). When NCJT is configured and 'cri-RI-PMI-CQI' or 'cri-RI-LI-PMI-CQI' is set in the reporting quantity settings, the CSI-RS resource set used for channel determination can be configured with two resource groups and N resource pairs.

[0479] With CJT configured and 'cri-RI-PMI-CQI' set in the reporting settings, and a CSI-RS resource set for channel measurement consisting of N... TRP Given a set of CSI-RS resources, terminal device 1 can calculate the first formula for CQI. In the first formula, the PDSCH signal in antenna ports (DMRS ports) {1000…1000+ν-1} can be a signal equivalent to the symbol transmitted in antenna ports {3000…3000+ν-1} of each CSI-RS resource. In the first formula, vector [y... （3000） σ1 (i) ... y （3000+P-1） σ1 (i)y （3000） σ2 (i) ... y （3000+P-1） σ2 (i) ... y （3000） σN (i) ... y （3000+P-1） σN [(i)] can be the precoding matrix W(i) and the vector [x] （0） (i) ... x （ν-1） The product of (i). That is, N signal sets can also be determined from ν PDSCH signals x based on the precoding matrix W(i). Each signal set can be P P PDSCH signals y. {σ1……σN} can be NTRP An index of a CSI-RS resource. For example, it could also be 1 <= σ1 < ... < σN <= N. TRP Each signal set can repeat in time and frequency. W(i) can correspond to PMI. ν can be a layer. N TRP This can be the number of TRPs.

[0480] Terminal device 1 can assume that CJT is set for the downlink physical channel. As a technical problem, CJT is difficult when downlink physical channels from multiple TRPs, downlink reference signals have different propagation delay times, and different center frequencies. Methods A, B, and C are used as solutions to address this technical problem. Figure 9 This is a diagram representing an example of a CSI report illustrating one aspect of this implementation.

[0481] Setting CJT can be either synchronous CJT or asynchronous CJT. For example, even when CJT is set, it's possible to set either synchronous CJT or asynchronous CJT. Setting asynchronous CJT can involve setting at least multiple DCI modes. Setting synchronous CJT can involve setting at least a single DCI mode. Setting asynchronous CJT can involve setting upper-level parameter 900. Setting synchronous CJT can involve not setting upper-level parameter 900. Setting synchronous CJT can involve setting CJT without setting asynchronous CJT. Upper-level parameter 900 can be a parameter used to switch between synchronous and asynchronous CJT.

[0482] Upper-level parameter 900 can be set for a CSI-RS resource set 920 or a CSI resource setting 930. Upper-level parameter 900 can be set for one or both of the PDSCH and PDCCH. Upper-level parameter 900 can indicate N. TRP One of the CSI-RS.

[0483] Terminal device 1 receives N TRP CSI-RS {910……910+N} TRP -1}。 N TRP It can be 1, 2, 3, or 4. N TRP This can be the number of TRPs. N TRP The number of CSI-RS resources included in a CSI-RS resource set 920 can be determined. For example, with CJT (asynchronous CJT or synchronous CJT) configured, terminal device 1 can receive N TRP CSI-RS {910……910+N} TRP -1}. Receiving CSI-RS can be receiving CSI-RS resources.

[0484] N TRPCSI-RS {910……910+N} TRP -1} can correspond to a CSI-RS resource ID. For example, CSI-RS910 can correspond to the smallest CSI-RS resource ID in a CSI-RS resource set 920. For example, CSI-RS911 can correspond to the second smallest CSI-RS resource ID in a CSI-RS resource set 920. For example, CSI-RS 910+N TRP -1 can correspond to the largest CSI-RS resource ID in a CSI-RS resource set 920.

[0485] A CSI-RS resource set 920 can include N TRP CSI-RS {910……910+N} TRP -1}。 N TRP CSI-RS {910……910+N} TRP Resources can also be configured within a CSI-Resource Set 920. A CSI-RS Resource Set 920 can be used for channel determination. TRP CSI-RS {910……910+N} TRP Resources of type -1 can consist of the same number of antenna ports. N TRP CSI-RS {910……910+N} TRP Resources of type -1 can consist of resources of the same frequency (e.g., the same number of RBs). TRP CSI-RS {910……910+N} TRP Resources can have the same starting RB location. For example, if PMI is not set in the reporting quantity settings, the number of antenna ports can be 1. For example, if PMI is set in the reporting quantity settings, the number of antenna ports can be determined by the settings for each CSI-RS resource.

[0486] TRS does not need to be set for a CSI-RS resource set 920.

[0487] A CSI resource setting 930 can be associated with a CSI-RS resource set 920. A CSI-RS resource set 920 can be set within a CSI resource setting 930.

[0488] N TRP CSI-RS {910……910+N} TRP Each of the elements in {-1} can be QCL with respect to type A and a CSI-RS or SS / PBCH block. TRP CSI-RS {910……910+N} TRPEach of the values ​​in {-1} can be at least QCL with respect to Doppler frequency shift or average delay with a CSI-RS or SS / PBCH block. For example, in the case where at least the frequency difference is set in the reporting quantity setting, N TRP CSI-RS {910……910+N} TRP Each of the values ​​in {-1} can be at least QCL with respect to the Doppler frequency shift and a CSI-RS or SS / PBCH block. For example, if at least a time difference is set in the reporting quantity settings, N TRP CSI-RS {910……910+N} TRP Each of the following can be QCL with respect to at least the average delay and a CSI-RS or SS / PBCH block.

[0489] Without setting asynchronous CJT, N TRP CSI-RS {910……910+N} TRP Each of the values ​​in {-1} can be QCL with respect to type A or type B and a CSI-RS. In the case of a non-synchronous CJT, N TRP CSI-RS {910……910+N} TRP Each of the values ​​in {-1} can be QCL with respect to type A and a CSI-RS. It is not expected that N will be QCL when an asynchronous CJT is set. TRP CSI-RS {910……910+N} TRP Each of the elements in {-1} with respect to type B and a CSI-RS is a QCL.

[0490] With asynchronous CJT configured, terminal device 1 can operate in one or N locations. TRP Receive N from time resources TRP CSI-RS {910……910+N} TRP -1}.

[0491] Within a given time resource, terminal device 1 can receive N. TRP CSI-RS {910……910+N} TRP-1}. For example, when terminal capability 960 is reported, terminal device 1 can receive CSI-RS 910 and CSI-RS 911 in one time resource. For example, when terminal capability 960 is reported, terminal device 1 can receive CSI-RS 910 and CSI-RS 911 in different frequency resources. Terminal capability 960 can have multiple downlink reference timings. For example, terminal capability 960 can be larger-than CP-capability. For example, when terminal capability 960 is reported, the difference between the first downlink timing and the second downlink timing can exceed CP. For example, when the difference between the first downlink timing and the second downlink timing does not exceed the CP length, terminal device 1 can receive CSI-RS 910 and CSI-RS 911 in one time resource. When terminal capability 960 is reported, the number of CSI-RS that can be received in one time resource can be 2. When terminal capability 960 is reported and N TRP In the case of 4, terminal device 1 can receive four CSI-RS 910 / 911 / 912 / 913 in two time resources. This is without reporting terminal capability 960 and N TRP When the time resource is 4, terminal device 1 can receive four CSI-RS 910 / 911 / 912 / 913 in four time resources. One time resource can be one time slot.

[0492] In N TRP Of the time resources, terminal device 1 can receive N. TRP CSI-RS {910……910+N} TRP -1}. For example, without reporting terminal capability 960, terminal device 1 can receive CSI-RS 910 and CSI-RS 911 in different time resources. Each time resource can consist of one or more OFDM symbols. Different time resources do not need to repeat in the time domain. For example, different time resources can correspond to different time slots. For example, the difference between two time resources (e.g., the difference between the end of the first time resource and the beginning of the second time resource) can be X symbols or more than X time slots. X can be determined based on terminal capability 961. X can be determined based on the handover time of downlink timing (downlink reference timing).

[0493] With synchronous CJT configured, N TRP CSI-RS {910……910+N} TRP The time slot offset of {-1} can be set to 1 or 2. When the time slot offset is set to 1, N TRP CSI-RS {910……910+N} TRP-1} can be received in one time slot. With the time slot offset set to 2, N TRP CSI-RS {910……910+N} TRP -1 can be received in one time slot.

[0494] Does terminal device 1 receive N within a time resource? TRP CSI-RS {910……910+N} TRP -1} can be determined based on the reporting quantity setting. When a frequency difference is set in the reporting quantity setting, terminal device 1 can receive N within a time resource. TRP CSI-RS {910……910+N} TRP -1}. If no frequency difference is set in the report quantity settings, terminal device 1 can receive N in different time resources. TRP CSI-RS {910……910+N} TRP -1}. When a frequency difference is set in the reporting quantity settings, terminal device 1 can receive N in one or two consecutive time slots. TRP CSI-RS {910……910+N} TRP -1}. If no frequency difference is set in the reporting quantity settings, terminal device 1 can receive N in different time slots. TRP CSI-RS {910……910+N} TRP -1}. When a time difference is set in the report quantity settings, terminal device 1 can receive N in different time slots. TRP CSI-RS {910……910+N} TRP -1}.

[0495] Terminal device 1 can transmit CSI940. Transmitting CSI can be a CSI report, or it can be a CSI report. Terminal device 1 can transmit via the uplink physical channel. For example, terminal device 1 can transmit CSI940 via the uplink physical channel. For example, terminal device 1 can transmit via the uplink physical channel accompanied by CSI940. For example, terminal device 1 can use the uplink physical channel to transmit CSI940. Transmitting CSI can also be transmitting via the uplink physical channel accompanied by CSI.

[0496] CSI940 can be based on N TRP CSI-RS {910……910+N} TRP -1}N RE To determine. CSI940 can be based on N. TRP CSI-RS {910……910+N} TRPThe index (CRI) of N is used to determine this. For example, CSI940 can consist of one or more CSI parameters. One or more CSI parameters can be determined based on the CRI. The CRI can indicate N. TRP CSI-RS {910……910+N} TRP One of the -1}.

[0497] CSI940 can be composed of one or N TRP It may consist of some or all of the CRI, time difference, and frequency difference. For example, in method C1, if at least CRI, time difference, and frequency difference are set in the reporting quantity settings, CSI940 may consist of at least one CRI, time difference, and frequency difference. In method C2, if at least CRI, time difference, and frequency difference are set in the reporting quantity settings, CSI940 may consist of N TRP The CSI940 consists of at least a CRI, a time difference, and a frequency difference. In method C3, if at least a time difference and a frequency difference are set in the reporting quantity settings, the CSI940 can consist at least of a time difference and a frequency difference. Similarly, if at least a time difference is set in the reporting quantity settings, the CSI940 can consist at least of a time difference. And if at least a frequency difference is set in the reporting quantity settings, the CSI940 can consist at least of a frequency difference.

[0498] The settings for CSI940 can be determined based on CSI report settings 950. For example, the components of CSI940 (CSI parameters) can be determined by the report quantity setting in CSI report settings 950. The time domain behavior of CSI940 can be determined based on CSI report settings 950. The transmission opportunities (time resources) of CSI940 can be determined based on CSI report settings 950. The report quantity setting can be determined by CSI report settings 950.

[0499] For N TRP CSI-RS {910……910+N} TRP The setting of `-1}` can be determined based on CSI resource setting 930. For example, it is used to include N. TRP CSI-RS {910……910+N} TRP The settings for a CSI-RS resource set 920 (-1) can be configured in CSI resource settings 930. TRP CSI-RS {910……910+N} TRP The temporal action of -1} can be determined based on CSI resource setting 930. N TRPCSI-RS {910……910+N} TRP The transmission opportunity (time resource) of {-1} can be determined based on CSI resource setting 930. CSI resource setting 930 can be used for channel determination. CSI resource setting 930 can be linked to CSI report setting 950. For example, CSI resource setting 930 can be set in CSI report setting 950.

[0500] Terminal device 1 calculates the time difference. For example, if at least a time difference is set in the report quantity setting, terminal device 1 can calculate the time difference. If asynchronous CJT is set, the time difference can be set in the report quantity setting. If asynchronous CJT is not set, it is not necessary to set the time difference in the report quantity setting.

[0501] In method A1, terminal device 1 can calculate N. TRP -1 time difference. Terminal device 1 can be based on N TRP CSI-RS {910……910+N} TRP -1} to calculate N TRP -1 time difference. The first time difference can be the difference between the average delay of the first CSI-RS and the average delay of the second CSI-RS. The second time difference can be the difference between the average delay of the first CSI-RS and the average delay of the third CSI-RS. The Nth... TRP -1 time difference can be the average delay of the first CSI-RS and the Nth time difference. TRP The difference in average delay between the first CSI-RS and the second CSI-RS. Alternatively, the difference in average delay between the first CSI-RS and the second CSI-RS may not be calculated. The first CSI-RS can also be referred to as the reference CSI-RS. The average delay can be the propagation delay.

[0502] In method A1, terminal device 1 can calculate N. TRP -1 time difference. N TRP One of the CSI-RSs can be a reference CSI-RS. N TRP -1 time difference can be the average delay of the reference CSI-RS and N other than the reference CSI-RS. TRP The difference in average delay among CSI-RS.

[0503] The average delay of a CSI-RS can be estimated or determined based on the QCL assumption applied to that CSI-RS. For example, if the first CSI-RS and the second CSI-RS are QCL, the average delay can be estimated based on the second CSI-RS. For example, the average delay can be estimated based on the channel through which the second CSI-RS is transmitted. The first CSI-RS can be QCL at least with respect to the average delay and the second CSI-RS.

[0504] In method A2, terminal device 1 can calculate N. TRP There are time differences. This can be based on N. TRP CSI-RS {910……910+N} TRP -1} to calculate N TRP There are several time differences. The first time difference can be the difference between the first time and the average delay of the first CSI-RS. The second time difference can be the difference between the first time and the average delay of the second CSI-RS. The Nth time difference... TRP The time difference can be between the first time and the Nth time. TRP The difference in average delay between CSI-RS. The first time can be downlink timing. The first time can be determined based on downlink timing (downlink reference timing). Downlink timing can be the timing within the downlink radio frame. Downlink timing can be the start position of the downlink radio frame.

[0505] In method A2, terminal device 1 can calculate N. TRP A time difference. N TRP The time differences can be the first time and N. TRP The difference in average delay among CSI-RS.

[0506] Terminal device 1 can calculate the frequency difference. For example, if the frequency difference is set at least in the report quantity setting, terminal device 1 can calculate the frequency difference. If asynchronous CJT is set, the frequency difference can be set in the report quantity setting. If asynchronous CJT is not set, it is not necessary to set the frequency difference in the report quantity setting.

[0507] In method B1, terminal device 1 can calculate N. TRP -1 frequency difference. For example, terminal device 1 can be based on N TRP CSI-RS {910……910+N} TRP -1} to calculate N TRP -1 frequency difference. The first frequency difference can be the difference between the frequency associated with the first CSI-RS and the frequency associated with the second CSI-RS. The second frequency difference can be the difference between the frequency associated with the first CSI-RS and the frequency associated with the third CSI-RS. Nth TRP-1 frequency difference can be the frequency associated with the first CSI-RS and the frequency associated with the Nth CSI-RS. TRP The difference in frequencies associated with CSI-RS. Alternatively, the frequency associated with the first CSI-RS and the difference in frequencies associated with the first CSI-RS may not be calculated. The first CSI-RS may also be referred to as the reference CSI-RS. The frequency associated with a CSI-RS may be the center frequency of the CSI-RS. The frequency associated with a CSI-RS may be point 3000 of the CSI-RS. The frequency associated with a CSI-RS may be multiple resource elements mapping the CSI-RS.

[0508] In method B1, terminal device 1 can calculate N. TRP -1 frequency difference. N TRP One of the CSI-RSs can be a reference CSI-RS. N TRP -1 frequency difference can be either the frequency associated with the reference CSI-RS or the frequency associated with other frequencies besides the reference CSI-RS. TRP The difference in frequency associated with one of the CSI-RSs.

[0509] In method B2, terminal device 1 can calculate N. TRP A frequency difference. For example, terminal device 1 can be based on N. TRP CSI-RS {910……910+N} TRP -1} to calculate N TRP There are several frequency differences. The first frequency difference can be the difference between a first frequency and a frequency associated with a first CSI-RS. The second frequency difference can be the difference between a first frequency and a frequency associated with a second CSI-RS. The Nth frequency difference... TRP The frequency difference can be the sum of the first frequency and the Nth frequency. TRP The frequency difference associated with CSI-RS. A first frequency can be set. The first frequency can be point 3000. The first frequency can be the center frequency (carrier frequency). The center frequency can be determined for one or both of the serving cell and BWP. The first frequency can be a frequency based on ARFCN (Absolute Radio-Frequency Channel Number).

[0510] The frequency associated with a particular CSI-RS can be calculated based on one or both of the Doppler frequency shift and the reference time resource. The reference time resource can be the time resource of the reference CSI-RS. The Doppler frequency shift can be estimated based on the QCL assumption applied to that particular CSI-RS. For example, if the first CSI-RS and the second CSI-RS are QCL, the Doppler frequency shift can be estimated based on the second CSI-RS. For example, the Doppler frequency shift can be estimated based on the channel through which the second CSI-RS is transmitted. The first CSI-RS can be QCL at least with respect to the Doppler frequency shift and the second CSI-RS.

[0511] Having calculated the frequency difference, terminal device 1 can determine the reference time resource. The reference time resource can be the time resource of the reference CSI-RS. Having calculated the frequency difference, terminal device 1 can assume that N other than the reference CSI-RS will be transmitted within the reference time resource. TRP CSI-RS {910……910+N} TRP -1}. For example, when the frequency difference is calculated, terminal device 1 can correct N other than reference CSI-RS based on reference time resources. TRP CSI-RS {910……910+N} TRP The variation value used is denoted by -1. The variation value can be a phase variation or a Doppler frequency shift.

[0512] In method C1, the reference CSI-RS can be reported by a CRI. Terminal device 1 can determine the reference CSI-RS. A CRI can be included in CSI 940. CSI 940 can be composed of at least one CRI.

[0513] In method C2, the reference CSI-RS can be reported by the first CRI. Terminal device 1 can determine the reference CSI-RS. N including the first CRI TRP Each CRI can be included in CSI940. CSI940 can consist of at least N TRP It consists of CRIs.

[0514] In methods C2 and C3, the reference CSI-RS can be determined by upper-level parameter 901. Upper-level parameter 901 can be set to determine the reference CSI-RS. Upper-level parameter 901 can be set in CSI report settings 950 or CSI resource settings 930. Upper-level parameter 901 can indicate N. TRP CSI-RS {910……910+N} TRPOne of the following: -1}. The reference CSI-RS can also be the CSI-RS corresponding to the serving cell. For example, the reference CSI-RS may not correspond to the appended PCI index. The reference CSI-RS can also be CSI-RS 910.

[0515] In method C3, CRI may not be reported. For example, if one or both of time difference and frequency difference are set in the reporting quantity settings, CSI940 may not be expected to include CRI.

[0516] Hereinafter, various apparatus designs for one embodiment will be described.

[0517] The programs operating in the base station device 3 and terminal device 1 according to the present invention can be programs that control CPUs (Central Processing Units) and the like to achieve the functions of the above-described embodiments according to one aspect of the present invention (programs that enable the computer to function). Furthermore, the information processed 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) and HDDs (Hard Disk Drives), and read, corrected, and written by the CPU as needed.

[0518] It should be noted that a portion of the terminal device 1 and base station device 3 described above can also be implemented using a computer. In this case, it can be achieved by recording a program for implementing the control function on a computer-readable recording medium, reading the program recorded on the recording medium into a computer system, and executing it.

[0519] It should be noted that the "computer system" mentioned here refers to the computer system built into terminal device 1 or base station device 3, and includes hardware such as the OS (Operating System) and peripheral devices. Furthermore, "computer-readable recording media" refers to removable media such as floppy disks, magneto-optical disks, ROM (Read Only Memory), and CD-ROM (CompactDisc Read-Only Memory), as well as storage devices such as hard drives built into the computer system.

[0520] Furthermore, "computer-readable recording medium" may also include: a recording medium that dynamically stores a program for a short period of time, such as a communication line in the case of transmitting a program via a network such as the Internet or a communication line such as a telephone line; and a recording medium that stores a program for a fixed period of time, such as volatile memory inside a computer system that serves as a server or client in such cases. In addition, the aforementioned program may be a program used to implement the above-mentioned functions, or it may be a program that can implement the above-mentioned functions by combining with a program already recorded in the computer system.

[0521] Furthermore, the base station device 3 in the above embodiments can also be implemented as an assembly (device group) composed of multiple devices. Each device constituting the device group can possess some or all of the functions or functional blocks of the base station device 3 involved in the above embodiments. As a device group, it is sufficient to have all the functions or functional blocks of the base station device 3. In addition, the terminal device 1 in the above embodiments can also communicate with the base station device, which is an assembly.

[0522] Furthermore, the base station device 3 in the above embodiments can be EUTRAN (Evolved Universal Terrestrial Radio Access Network) and / or NG-RAN (NextGenRAN, NR RAN). Additionally, the base station device 3 in the above embodiments may also have some or all of the functions of a host node for the eNodeB and / or gNB.

[0523] Furthermore, the terminal device 1 and base station device 3 described above can be implemented, either partially or entirely, as LSIs (Large Scale Integration), typically integrated circuits, or as chipsets. Each functional block of the terminal device 1 and base station device 3 can be implemented as a separate chip, or partially or entirely integrated into a single chip. Moreover, the method of integrated circuit implementation is not limited to LSIs; it can also be implemented using dedicated circuits or general-purpose processors. Furthermore, if advancements in semiconductor technology lead to integrated circuit technologies that replace LSIs, integrated circuits based on such technologies can also be used.

[0524] Furthermore, while the above embodiments describe a terminal device as an example of a communication device, the present invention is not limited thereto and can also be applied to fixed or non-movable electronic devices installed indoors or outdoors, such as AV (Audio Video) devices, kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other household equipment, etc.

[0525] The embodiments of the present invention have been described in detail above with reference to the accompanying drawings. However, the specific configuration is not limited to these embodiments, and design changes that do not depart from the spirit of the present invention are also included. Furthermore, the present invention can be modified in various ways within the scope of the technical solutions shown, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included within the technical scope of the present invention. In addition, it also includes configurations obtained by replacing elements that have the same effect as those described in the above embodiments with each other.

[0526] Industrial availability This invention can be used, for example, in communication systems, communication devices (e.g., mobile phone devices, base station devices, wireless LAN devices, or sensor devices), integrated circuits (e.g., communication chips), or programs.

[0527] Explanation of reference numerals in the attached figures 1 (1A, 1B, 1C): Terminal device; 3: Base station equipment; 10, 30: Wireless transceiver unit; 10a, 30a: Wireless transmission unit; 10b, 30b: Wireless receiver; 11, 31: Antenna section; 12, 32: RF section; 13, 33: Baseband section; 14, 34: Upper processing unit; 15, 35: Media Access Control Layer Processing Department; 16, 36: Radio Resource Control Layer Processing Unit; 91, 92, 93, 94: Search area set; 300: Component carrier; 301: Main residential area; 302, 303: Auxiliary residential areas; 700: A collection of resource elements used in PSS; 710, 711, 712, 713: Sets of resource elements used for PBCH and DMRS used for PBCH; 720: A collection of resource elements used in SSS; 3000: points; 3001, 3002: Resource grid; 3003, 3004: BWP; 3011, 3012, 3013, 3014: Offset; 3100, 3200: Public resource block sets; 900, 901: Upper-level parameters; 910, 911, 912, 913: CSI-RS; 920: CSI-RS resource set; 930: CSI resource settings; 940: CSI; 950: CSI report settings; 960: Terminal capabilities.

Claims

1. A terminal device, the terminal device comprising: The receiving unit receives N CSI-RS; and The sending department sends CSI. The CSI resource settings for the N CSI-RS are linked to the CSI report settings for the CSI. The CSI consists of at least N-1 frequency differences. One of the N CSI-RS is a reference CSI-RS. The N-1 frequency differences are the differences between the frequency associated with the reference CSI-RS and the frequency associated with one of the N CSI-RS other than the reference CSI-RS.

2. The terminal device according to claim 1, wherein, The frequency associated with a particular CSI-RS is calculated based on the Doppler frequency shift and the time resources of the reference CSI-RS. The Doppler frequency shift is estimated based on the QCL assumption applied to the CSI-RS.

3. The terminal device according to claim 1, wherein, The CSI consists of a CRI and the N-1 frequency differences. The CRI indicates the resource index of the reference CSI-RS.

4. The terminal device according to claim 1, wherein, One CSI-RS resource set in the CSI resource configuration includes the N CSI-RS. The reference CSI-RS is set through upper-level parameters. The upper-level parameters are set in the CSI resource settings or the CSI report settings. The upper-level parameter indicates one of the N CSI-RS.

5. The terminal device according to claim 4, wherein, It is not expected that the CSI is composed of the CRI and the N-1 frequency differences.

6. A terminal device, the terminal device comprising: The receiving unit receives N CSI-RS; and The sending department sends CSI. The CSI resource settings for the N CSI-RS are linked to the CSI report settings for the CSI. The CSI consists of at least N frequency differences. The N frequency differences are the differences between the set frequency and the frequency associated with the N CSI-RS.

7. A base station apparatus, the base station apparatus comprising: The transmitting unit transmits N CSI-RS; and Receiving unit, receives CSI. The CSI resource settings for the N CSI-RS are linked to the CSI report settings for the CSI. The CSI consists of at least N-1 frequency differences. One of the N CSI-RS is a reference CSI-RS. The N-1 frequency differences are the differences between the frequency associated with the reference CSI-RS and the frequency associated with one of the N CSI-RS other than the reference CSI-RS.

8. The base station apparatus according to claim 7, wherein, The frequency associated with a particular CSI-RS is calculated based on the Doppler frequency shift and the time resources of the reference CSI-RS. The Doppler frequency shift is estimated based on the QCL assumption applied to the CSI-RS.

Images