WO2025173545A1 - Terminal device, base station device, and communication method - Google Patents

Abstract

Provided are a reception unit for receiving a downlink reference signal, and a transmission unit for transmitting a first uplink physical channel with CS and a second uplink physical channel. The CSI is determined on the basis of the downlink reference signal. The resource of the second uplink physical channel is determined by a first higher layer parameter. The first higher layer parameter does not link to a CSI resource setting corresponding to the downlink reference signal. If the CSI does not satisfy a certain criterion, the resource of the first uplink physical channel is determined by the first higher layer parameter. If the CSI satisfies the certain criterion, the resource of the first uplink physical channel is determined by a CSI report setting linked to the CSI resource setting.

Description

Terminal device, base station device, and communication method

The present invention relates to a terminal device, a base station device, and a communication method.
This application claims priority from Japanese Patent Application No. 2024-020048, filed February 14, 2024, the contents of which are incorporated herein by reference.

A radio access method and radio network for cellular mobile communications (hereinafter also referred to as "Long Term Evolution (LTE)" or "EUTRA: Evolved Universal Terrestrial Radio Access") is being studied by the 3rd Generation Partnership Project (3GPP, a ^registered trademark). In LTE, a base station device is also referred to as an evolved NodeB (eNodeB), and a terminal device is also referred to as User Equipment (UE). LTE is a cellular communication system in which multiple areas covered by a base station device are arranged in the form of cells. A single base station device may manage multiple serving cells.

3GPP is currently studying the next-generation standard (NR: New Radio) to propose it for IMT (International Mobile Telecommunication)-2020, the next-generation mobile communications system standard formulated by the International Telecommunication Union (ITU) (Non-Patent Document 1). NR is expected to meet the requirements of three scenarios within a single technology framework: eMBB (enhanced Mobile Broadband), mMTC (massive Machine Type Communication), and URLLC (Ultra Reliable and Low Latency Communication).

3GPP is currently studying the expansion of services supported by NR (Non-Patent Document 2, Non-Patent Document 3, and Non-Patent Document 4).

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

One aspect of the present invention provides a terminal device that communicates efficiently, a communication method used by the terminal device, a base station device that communicates efficiently, and a communication method used by the base station device.

(1) A first aspect of the present invention is a terminal device comprising: a receiver that receives a downlink reference signal; and a transmitter that transmits a first uplink physical channel accompanied by CSI and a second uplink physical channel, wherein the CSI is determined based on the downlink reference signal; resources for the second uplink physical channel are determined by first higher layer parameters; the first higher layer parameters are not linked to a CSI resource configuration corresponding to the downlink reference signal; if the CSI does not satisfy a certain criterion, resources for the first uplink physical channel are determined by the first higher layer parameters; and if the CSI satisfies the certain criterion, resources for the first uplink physical channel are determined by a CSI report configuration linked to the CSI resource configuration.

(2) A second aspect of the present invention is a base station device comprising: a transmitter that transmits a downlink reference signal; and a receiver that receives a first uplink physical channel accompanied by CSI and a second uplink physical channel, wherein the CSI is determined based on the downlink reference signal; resources for the second uplink physical channel are determined by first higher layer parameters; the first higher layer parameters are not linked to a CSI resource configuration corresponding to the downlink reference signal; if the CSI does not satisfy a certain criterion, resources for the first uplink physical channel are determined by the first higher layer parameters; and if the CSI satisfies the certain criterion, resources for the first uplink physical channel are determined by a CSI report configuration linked to the CSI resource configuration.

(3) A third aspect of the present invention is a communication method for a terminal device, comprising the steps of receiving a downlink reference signal and transmitting a first uplink physical channel accompanied by CSI and a second uplink physical channel, wherein the CSI is determined based on the downlink reference signal, and resources of the second uplink physical channel are determined by first higher layer parameters, the first higher layer parameters are not linked to a CSI resource configuration corresponding to the downlink reference signal, and if the CSI does not satisfy a certain criterion, the resources of the first uplink physical channel are determined by the first higher layer parameters, and if the CSI satisfies the certain criterion, the resources of the first uplink physical channel are determined by a CSI report configuration linked to the CSI resource configuration.

According to one aspect of the present invention, terminal devices can communicate efficiently. Furthermore, base station devices can communicate efficiently.

1 is a conceptual diagram of a wireless communication system according to an aspect of the present embodiment. 10 is an example showing the relationship between a subcarrier spacing setting μ, the number of OFDM symbols per slot N ^slot _symb , and a cyclic prefix (CP) setting according to one aspect of the present embodiment. FIG. 10 is a diagram illustrating an example of a method for configuring a resource grid according to an aspect of the present embodiment. FIG. 30 is a diagram illustrating an example of the configuration of a resource grid 3001 according to one aspect of the present embodiment. FIG. 2 is a schematic block diagram illustrating an example of the configuration of a base station device 3 according to one aspect of the present embodiment. 1 is a schematic block diagram illustrating an example of the configuration of a terminal device 1 according to an aspect of the present embodiment. FIG. 2 is a diagram illustrating an example of the configuration of an SS/PBCH block according to one aspect of this embodiment. FIG. 10 is a diagram illustrating an example of a monitoring opportunity for a set of search areas according to one aspect of the present embodiment. FIG. 10 is a diagram illustrating an example of a CSI report according to an aspect of the present embodiment.

The following describes an embodiment of the present invention.

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

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

The term "OFDM symbol" may also refer to a symbol that includes a CP added to the OFDM symbol. In other words, a certain OFDM symbol may be composed of that certain OFDM symbol and a CP added to that certain OFDM symbol.

FIG. 1 is a conceptual diagram of a wireless communication system according to one aspect of this embodiment. In FIG. 1, the wireless communication system includes at least terminal devices 1A to 1C and base station device 3 (BS#3: Base station#3). Hereinafter, terminal devices 1A to 1C will also be referred to as terminal device 1 (UE#1: User Equipment#1).

The base station device 3 may be configured to include one or more transmitting devices (or transmission points, transmitting/receiving devices, transmitting/receiving points). If the base station device 3 is configured with multiple transmitting devices, each of the multiple transmitting devices may be located in a different location.

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

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

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

The resource grid includes N ^size,μ _grid,x N ^RB _sc subcarriers, where the resource grid starts from a common resource block N ^{start,μ grid} _{, x} , which is also referred to as the reference point of the resource grid.

The resource grid contains N ^{subframes, μ} _symb OFDM symbols.

The subscript x added to the resource grid-related parameters indicates the transmission direction. For example, the subscript x may be used to indicate either the downlink or the uplink.

N ^{size, μ} _{grid, x} is an offset setting indicated by a parameter provided by the RRC layer (e.g., the parameter CarrierBandwidth). ^{N start, μ} _{grid, x} is a band setting indicated by a parameter provided by the RRC layer (e.g., the parameter OffsetToCarrier). The offset setting and band setting are settings used to configure an SCS-specific carrier.

The subcarrier spacing (SCS) Δf for a given subcarrier spacing setting μ may be Δf= ^2μ ·15 kHz, where the subcarrier spacing setting μ may represent any of 0, 1, 2, 3, or 4.

2 is an example showing the relationship between the subcarrier spacing setting μ, the number of OFDM symbols per slot N ^slot _symb , and the CP (cyclic prefix) setting according to one aspect of this embodiment. In FIG. 2A , for example, when the subcarrier spacing setting μ is 2 and the CP setting is normal cyclic prefix (CP), N ^slot _symb =14, N ^{frame, μ} _slot =40, and N ^{subframe, μ} _slot =4. Also, in FIG. 2B , for example, when the subcarrier spacing setting μ is 2 and the CP setting is extended cyclic prefix (CP), N ^slot _symb =12, N ^{frame, μ} _slot =40, and N ^{subframe, μ} _slot =4.

A time unit _Tc may be used to express a length in the time domain. The time unit _Tc is _Tc = 1/(Δf _max · N _f ). Δf _max = 480 kHz. N _f = 4096. The constant κ is κ = Δf _max · N _f / (Δf _ref N _f,ref ) = 64. Δf _ref is 15 kHz. _{N f,ref} is 2048.

The transmission of signals in the downlink and/or the transmission of signals in the uplink may be organized into radio frames (system frames, frames) of length _Tf , where _Tf = (Δf _max N _f /100)· _Ts = 10 ms. A radio frame is composed of 10 subframes. The length of a subframe is _Tsf = (Δf _max N _f /1000)· _Ts = 1 ms. The number of OFDM symbols per subframe is N ^subframe,μ _symb = N ^slot _symb N ^subframe,μ _slot .

An OFDM symbol is a unit of time in a communication method. For example, an OFDM symbol may be the unit of time in CP-OFDM. An OFDM symbol may also be the unit of time in DFT-s-OFDM.

A slot may be configured to include multiple OFDM symbols. For example, one slot may be configured by N ^slot _symb consecutive OFDM symbols. For example, in a normal CP setting, N ^slot _symb = 14. Also, in an extended CP setting, N ^slot _symb = 12.

For a certain subcarrier spacing setting μ, the number and index of slots included in a subframe may be given. For example, slot indexes n ^μ _s may be given in ascending order as integer values in the range from 0 to N ^{subframe, μ} _slot −1 in a subframe. For a certain subcarrier spacing setting μ, the number and index of slots included in a radio frame may be given. Also, slot indexes n ^μ _s,f may be given in ascending order as integer values in the range from 0 to N ^{frame, μ} _slot −1 in a radio frame.

Fig. 3 is a diagram showing an example of a resource grid configuration method according to one aspect of this embodiment. The horizontal axis in Fig. 3 represents the frequency domain. Fig. 3 shows an example of a resource grid configuration with subcarrier spacing μ ₁ in a component carrier 300, and an example of a resource grid configuration with subcarrier spacing μ ₂ in the component carrier. In this way, one or more subcarrier spacings may be set for a certain component carrier. In Fig. 3, it is assumed that μ ₁ = μ ₂ - 1, but various aspects of this embodiment are not limited to the condition μ ₁ = μ ₂ - 1.

Component carrier 300 is a band with a predetermined width in the frequency domain.

Point 3000 is an identifier for identifying a certain subcarrier. Point 3000 is also referred to as point A. Common resource block (CRB) set 3100 is a set of common resource blocks for the subcarrier spacing setting μ ₁ .

Of the common resource block set 3100, the common resource block that includes point 3000 (the solid black block in the common resource block set 3100 in Figure 3) is also referred to as the reference point of the common resource block set 3100. The reference point of the common resource block set 3100 may be the common resource block with index 0 in the common resource block set 3100.

The offset 3011 is the offset from the reference point of the common resource block set 3100 to the reference point of the resource grid 3001. The offset 3011 is indicated by the number of common resource blocks for the subcarrier spacing setting μ _1. The resource grid 3001 includes N ^{size, μ} _grid1,x common resource blocks starting from the reference point of the resource grid 3001.

Offset 3013 is the offset from the reference point of resource grid 3001 to the reference point (N ^{start, μ} _{BWP, i1} ) of BWP (BandWidth Part) 3003 of index i1.

Common resource block set 3200 is a set of common resource blocks for subcarrier spacing setting μ ₂ .

Of the common resource block set 3200, the common resource block that includes point 3000 (the black block in the common resource block set 3200 in Figure 3) is also referred to as the reference point of the common resource block set 3200. The reference point of the common resource block set 3200 may be the common resource block with index 0 in the common resource block set 3200.

The 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. The offset 3012 is indicated by the number of common resource blocks relative to the subcarrier spacing μ _2. The resource grid 3002 includes N ^{size μ} _{grid2 x} common resource blocks starting from the reference point of the resource grid 3002.

Offset 3014 is the offset from the reference point of resource grid 3002 to the reference point (N ^{start ,μ} _BWP,i2 ) of BWP 3004 with index i2.

Fig. 4 is a diagram showing an example of the configuration of a resource grid 3001 according to one aspect of this embodiment. In the resource grid of Fig. 4, the horizontal axis represents the OFDM symbol index l _sym , and the vertical axis represents the subcarrier index k _sc . The resource grid 3001 includes N ^{size, μ} _{grid 1, ×} N ^RB _sc subcarriers and N ^{subframe, μ} _symb OFDM symbols. Within the resource grid, a resource identified by the subcarrier index k _sc and the OFDM symbol index l _sym is also referred to as a resource element (RE).

A resource block (RB) includes N ^RB _sc consecutive subcarriers. Resource block is a collective term for common resource blocks, physical resource blocks (PRBs), and virtual resource blocks (VRBs), where N ^RB _sc =12.

A resource block unit is a set of resources corresponding to one OFDM symbol in one resource block. That is, one resource block unit contains 12 resource elements corresponding to one OFDM symbol in one resource block.

The common resource blocks for a given subcarrier spacing setting μ are indexed in a given common resource block set in the frequency domain in ascending order starting from 0. For a given subcarrier spacing setting μ, the common resource block with index 0 includes (or collides with, or coincides with) point 3000. The index n ^μ _CRB of the common resource block for a given subcarrier spacing setting μ satisfies the relationship n ^μ _CRB = ceil(k _sc /N ^RB _sc ), where the subcarrier with k _sc = 0 is the subcarrier with the same center frequency as the subcarrier corresponding to point 3000.

The physical resource blocks for a given subcarrier spacing setting μ are indexed in the frequency domain in ascending order starting from 0 in a given BWP. The physical resource block index n ^μ _PRB for a given subcarrier spacing setting μ satisfies the relationship n ^μ _CRB = n ^μ _PRB + N ^start,μ _BWP,i , where N ^start,μ _BWP,i denotes the reference point of the BWP with index i.

A BWP is defined as a subset of common resource blocks included in a resource grid. A BWP includes N size ^,μ _BWP,i common resource blocks starting from the reference point N start ^,μ _BWP,i of the BWP. A BWP configured for a downlink carrier is also called a downlink BWP. A BWP configured for an uplink component carrier is also called an uplink BWP.

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

When the large-scale properties of the channel through which symbols are transmitted at one antenna port can be estimated from the channel through which symbols are transmitted at another antenna port, the two antenna ports are said to be Quasi Co-Located (QCL). Here, the large-scale properties may include at least the long-range properties of the channel. The large-scale properties may include at least some or all of the delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters. The first and second antenna ports being QCL with respect to beam parameters may mean that the receiving beam assumed by the receiving side for the first antenna port and the receiving beam assumed by the receiving side for the second antenna port are the same (or correspond to each other). The first antenna port and the second antenna port being QCLs in terms of beam parameters may mean that the transmission beam assumed by the receiving side for the first antenna port and the transmission beam assumed by the receiving side for the second antenna port are the same (or correspond to each other). The terminal device 1 may assume that the two antenna ports are QCLs if the large-scale characteristics of the channel through which symbols are transmitted at one antenna port can be estimated from the channel through which symbols are transmitted at the other antenna port. The two antenna ports being QCLs may mean that the two antenna ports are assumed to be QCLs. The large-scale characteristics may be referred to as QCL parameters.

The QCL type may be any of type A, type B, type C, and type D.

The fact that the two antenna ports are (with respect to) type A QCLs may mean that a first large-scale characteristic of a channel through which symbols are transmitted at one antenna port can be estimated from a channel through which symbols are transmitted at another antenna port. The fact that the two antenna ports are (with respect to) type B QCLs may mean that a second large-scale characteristic of a channel through which symbols are transmitted at one antenna port can be estimated from a channel through which symbols are transmitted at another antenna port. The fact that the two antenna ports are (with respect to) type C QCLs may mean that a third large-scale characteristic of a channel through which symbols are transmitted at one antenna port can be estimated from a channel through which symbols are transmitted at another antenna port. The fact that the two antenna ports are (with respect to) type D QCLs may mean that a fourth large-scale characteristic of a channel through which symbols are transmitted at one antenna port can be estimated from a channel through which symbols are transmitted at another antenna port. The first large-scale characteristic may include all of Doppler shift, Doppler spread, mean delay, and delay spread. The second large-scale characteristic may include all of the Doppler shift and Doppler spread. The third large-scale characteristic may include all of the Doppler shift and average delay. The fourth large-scale characteristic may include spatial reception parameters (spatial direction information, beam information). An antenna port for a DMRS may be a DMRS port. An antenna port for a PTRS may be a PTRS port. An antenna port associated with a PTRS may be a PTRS port. An antenna port for an SRS may be an SRS port. An antenna port for a DMRS may be a DMRS port. An antenna port associated with a DMRS may be a DMRS port.

Carrier aggregation may be communication using multiple aggregated serving cells. Also, carrier aggregation may be communication using multiple aggregated component carriers. Also, carrier aggregation may be communication using multiple aggregated downlink component carriers. Also, carrier aggregation may be communication using multiple aggregated uplink component carriers.

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

The wireless transceiver unit 30 includes at least a wireless transmitter unit 30a and part or all of a wireless receiver unit 30b. Here, the baseband unit included in the wireless transmitter unit 30a and the baseband unit included in the wireless receiver unit 30b may have the same or different device configurations. Furthermore, the RF unit included in the wireless transmitter unit 30a and the RF unit included in the wireless receiver unit 30b may have the same or different device configurations. Furthermore, the antenna unit included in the wireless transmitter unit 30a and the antenna unit included in the wireless receiver unit 30b may have the same or different device configurations.

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

For example, the wireless receiving unit 30b may receive a PRACH. For example, the wireless receiving unit 30b may receive and demodulate a PUCCH. The wireless receiving unit 30b may receive and demodulate a PUSCH. For example, the wireless receiving unit 30b may receive a PUCCH DMRS. For example, the wireless receiving unit 30b may receive a PUSCH DMRS. For example, the wireless receiving unit 30b may receive a UL PTRS. For example, the wireless receiving unit 30b may receive an SRS.

The upper layer processing unit 34 outputs downlink data (transport blocks) to the radio transceiver unit 30 (or radio transmitter unit 30a). The upper layer processing unit 34 processes the MAC (Medium Access Control) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and RRC layer.

The media access control layer processing unit 35 provided in the upper layer processing unit 34 performs MAC layer processing.

The radio resource control layer processing unit 36 included in the upper layer processing unit 34 performs RRC layer processing. The radio resource control layer processing unit 36 manages various setting information/parameters (RRC parameters) of the terminal device 1. The radio resource control layer processing unit 36 sets parameters based on an RRC message received from the terminal device 1. For example, setting upper layer parameters may mean setting parameters based on a received RRC message. For example, receiving upper layer parameters may mean setting parameters based on a received RRC message.

The radio transceiver unit 30 (or radio transmitter unit 30a) performs processes such as modulation and encoding. The radio transceiver unit 30 (or radio transmitter unit 30a) generates a physical signal by modulating, encoding, and generating a baseband signal (converting it into a time-continuous signal) downlink data, and transmits it to the terminal device 1. The radio transceiver unit 30 (or radio transmitter unit 30a) may map the physical signal to a component carrier and transmit it to the terminal device 1.

The wireless transceiver unit 30 (or wireless receiver unit 30b) performs processes such as demodulation and decoding. The wireless transceiver unit 30 (or wireless receiver unit 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 unit 30b) may perform a channel access procedure prior to transmitting the physical signal.

The RF unit 32 converts (down-converts) the signal received via the antenna unit 31 into a baseband signal by quadrature demodulation and removes unnecessary frequency components. The RF unit 32 outputs the processed analog signal to the baseband unit.

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

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

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

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

Each of the serving cells configured for the terminal device 1 may be either a PCell (Primary cell), a PSCell (Primary SCG cell), or an SCell (Secondary Cell).

The PCell is a serving cell included in the MCG (Master Cell Group). The PCell is the cell on which the terminal device 1 performs the initial connection establishment procedure or the connection re-establishment procedure (the cell on which the procedure was performed).

The PSCell is a serving cell included in an SCG (Secondary Cell Group). The PSCell is a serving cell to which random access is performed by the terminal device 1.

A SCell may be included in either an MCG or an SCG.

Serving cell group (cell group) is a term that includes at least MCG and SCG. A serving cell group may include one or more serving cells (or component carriers). One or more serving cells (or component carriers) included in a serving cell group may be operated using carrier aggregation.

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

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

The PDSCH, PDCCH, and CSI-RS may be received in an active downlink BWP. The terminal device 1 may attempt to receive the PDSCH, PDCCH, and CSI-RS in an active downlink BWP. The PUCCH and PUSCH may be transmitted in an active uplink BWP. The terminal device 1 may transmit the PUCCH and PUSCH in an active uplink BWP. The active downlink BWP and the active uplink BWP are also collectively referred to as the active BWP.

The PDSCH, PDCCH, and CSI-RS do not have to be received in downlink BWPs other than the active downlink BWP (inactive downlink BWP). The terminal device 1 does not have to attempt to receive the PDSCH, PDCCH, and CSI-RS in downlink BWPs that are not active downlink BWPs. The PUCCH and PUSCH do not have to be transmitted in uplink BWPs that are not active uplink BWPs (inactive uplink BWPs). The terminal device 1 does not have to transmit the PUCCH and PUSCH in uplink BWPs that are not active uplink BWPs. The inactive downlink BWPs and inactive uplink BWPs are collectively referred to as inactive BWPs.

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

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

Among one or more downlink BWPs configured for a serving cell, two or more downlink BWPs may not be configured as active downlink BWPs. For a serving cell, one downlink BWP may be active at a given time.

Of the one or more uplink BWPs configured for a serving cell, two or more uplink BWPs may not be configured as active uplink BWPs. For a serving cell, one uplink BWP may be active at a given time.

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

The wireless transceiver unit 10 includes at least a wireless transmitter unit 10a and part or all of a wireless receiver unit 10b. Here, the baseband unit 13 included in the wireless transmitter unit 10a and the baseband unit 13 included in the wireless receiver unit 10b may have the same or different device configurations. Furthermore, the RF unit 12 included in the wireless transmitter unit 10a and the RF unit 12 included in the wireless receiver unit 10b may have the same or different device configurations. Furthermore, the antenna unit 11 included in the wireless transmitter unit 10a and the antenna unit 11 included in the wireless receiver unit 10b may have the same or different device configurations.

For example, the radio transmitting unit 10a may generate and transmit a PRACH baseband signal. For example, the radio transmitting unit 10a may generate and transmit a PUCCH baseband signal. The radio transmitting unit 10a may generate and transmit a PUSCH baseband signal. For example, the radio transmitting unit 10a may generate and transmit a PUCCH DMRS baseband signal. For example, the radio transmitting unit 10a may generate and transmit a PUSCH DMRS baseband signal. For example, the radio transmitting unit 10a may generate and transmit a UL PTRS baseband signal. For example, the radio transmitting unit 10a may generate and transmit an SRS baseband signal.

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

The upper layer processing unit 14 outputs uplink data (transport blocks) to the radio transceiver unit 10 (or radio transmitter unit 10a). The upper layer processing unit 14 processes the MAC layer, packet data integration protocol layer, radio link control layer, and RRC layer.

The media access control layer processing unit 15 provided in the upper layer processing unit 14 performs MAC layer processing.

The radio resource control layer processing unit 16 included in the upper layer processing unit 14 performs RRC layer processing. The radio resource control layer processing unit 16 manages various setting information/parameters (RRC parameters) of the terminal device 1. The radio resource control layer processing unit 16 sets RRC parameters based on an RRC message received from the base station device 3. For example, setting upper layer parameters may mean setting parameters based on a received RRC message. For example, receiving upper layer parameters may mean setting parameters based on a received RRC message.

The radio transceiver unit 10 (or radio transmitter unit 10a) performs processes such as modulation and encoding. The radio transceiver unit 10 (or radio transmitter unit 10a) generates a physical signal by modulating, encoding, and generating a baseband signal (converting it into a time-continuous signal) the uplink data, and transmits it to the base station device 3. The radio transceiver unit 10 (or radio transmitter unit 10a) may place the physical signal in a certain BWP (active uplink BWP) and transmit it to the base station device 3.

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

The RF unit 12 converts (down-converts) the signal received via the antenna unit 11 into a baseband signal by quadrature demodulation and removes unnecessary frequency components. The RF unit 12 outputs the processed analog signal to the baseband unit 13.

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

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

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

The following explains physical signals (signals).

Physical signal is a general term for downlink physical channel, downlink physical signal, uplink physical channel, and uplink physical channel. Physical channel is a general term for downlink physical channel and uplink physical channel. Physical signal is a general term for downlink physical signal and uplink physical signal. Physical signal may also be called reference signal.

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

The PUCCH may be used to transmit uplink control information (UCI). The PUCCH may be transmitted to deliver, transmit, or convey the uplink control information. The uplink control information may be mapped to the PUCCH. The terminal device 1 may transmit a PUCCH in which the uplink control information is mapped. The base station device 3 may receive a PUCCH in which the uplink control information is mapped.

The uplink control information (uplink control information bits, uplink control information sequence, uplink control information type) includes at least some or all of the channel state information (CSI: Channel State Information), scheduling request (SR: Scheduling Request), and HARQ-ACK (Hybrid Automatic Repeat request ACKnowledgement) information.

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

The HARQ-ACK information may include at least a HARQ-ACK corresponding to a transport block (TB). The HARQ-ACK may indicate an acknowledgement (ACK) or a negative acknowledgement (NACK) corresponding to the transport block. The ACK may indicate that decoding of the transport block has been successfully completed (has been decoded). The NACK may indicate that decoding of the transport block has not been successfully completed (has not been decoded). The HARQ-ACK information may include a HARQ-ACK codebook containing one or more HARQ-ACK bits.

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

HARQ-ACK for a transport block may be referred to as HARQ-ACK for a PDSCH. In this case, "HARQ-ACK for a PDSCH" refers to the HARQ-ACK for the transport block included in the PDSCH.

HARQ-ACK may indicate an ACK or NACK corresponding to one CBG (Code Block Group) included in a transport block.

The scheduling request may be used at least to request UL-SCH resources for an initial transmission. The scheduling request bit may be used to indicate either a positive SR or a negative SR. When the scheduling request bit indicates a positive SR, this is also referred to as "a positive SR is transmitted." A positive SR may indicate that UL-SCH resources for an initial transmission are requested by the terminal device 1. A positive SR may indicate that a scheduling request is triggered by an upper layer. A positive SR may be transmitted when a scheduling request is indicated by an upper layer. When the scheduling request bit indicates a negative SR, this is also referred to as "a negative SR is transmitted." A negative SR may indicate that UL-SCH resources for an initial transmission are not requested by the terminal device 1. A negative SR may indicate that a scheduling request is not triggered by an upper layer. A negative SR may be transmitted when a scheduling request is not indicated by an upper layer.

The channel state information may include at least some or all of the Channel Quality Indicator (CQI), Precoder Matrix Indicator (PMI), and Rank Indicator (RI). CQI is an indicator related to the quality of the propagation path (e.g., propagation strength) or the quality of the physical channel, and PMI is an indicator related to the precoder. RI is an indicator related to the transmission rank (or the number of transmission layers).

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

The PUCCH may correspond to a PUCCH format. The PUCCH may be a set of resource elements used to convey the PUCCH format. The PUCCH may include a PUCCH format. The PUCCH may be transmitted with a certain PUCCH format. The PUCCH format may be interpreted as a format of information. The PUCCH format may also be interpreted as a set of information set in a certain information format.

PUSCH may be used to transmit one or both of a transport block and uplink control information. A transport block may be allocated to the PUSCH. A transport block delivered by the UL-SCH may be allocated to the PUSCH. Uplink control information may be allocated to the PUSCH. The terminal device 1 may transmit a PUSCH in which one or both of a transport block and uplink control information are allocated. The base station device 3 may receive a PUSCH in which one or both of a transport block and uplink control information are allocated.

The PRACH may be transmitted to convey a random access preamble. The terminal device 1 may transmit the PRACH. The base station device 3 may receive the PRACH. The PRACH sequence xu _,v (n) is defined by xu _,v (n) = _xu (mod(n + _Cv , _LRA )). Here, _xu is a ZC (Zadoff Chu) sequence. Also, _xu may be defined by _xu = exp(-jπui(i+1)/ _LRA ). j is the imaginary unit. Also, π is the ratio of the circumference of a circle to its circumference. Also, _Cv corresponds to the cyclic shift of the PRACH sequence. Also, _LRA corresponds to the length of the PRACH sequence. Also, _LRA is 839 or 139. Also, i is an integer ranging from 0 to _LRA -1. Also, u is a sequence index for the PRACH sequence.

For each PRACH opportunity, 64 random access preambles are defined. The random access preambles are identified based on the cyclic shift _Cv of the PRACH sequence and the sequence index u for the PRACH sequence. Each of the 64 identified random access preambles may be assigned an index.

The uplink physical signal may correspond to a set of resource elements. The uplink physical signal does not have to be used to transmit information generated in a higher layer. The uplink physical signal may be used to transmit information generated in a physical layer. The uplink physical signal may be a physical signal used in an uplink component carrier. The terminal device 1 may transmit the uplink physical signal. The base station device 3 may receive the uplink physical signal. In a wireless communication system according to one aspect of the present embodiment, at least some or all of the following uplink physical signals may be used.
・UL DMRS (UpLink Demodulation Reference Signal)
・SRS (Sounding Reference Signal)
・UL PTRS (UpLink Phase Tracking Reference Signal)

UL DMRS is a general term for DMRS for PUSCH and DMRS for PUCCH.

The set of antenna ports for DMRS for a PUSCH (DMRS related to a PUSCH, DMRS included in a PUSCH, DMRS corresponding to a PUSCH) may be determined based on the set of antenna ports for the PUSCH. For example, the set of antenna ports for DMRS for a PUSCH may be the same as the set of antenna ports for the PUSCH.

Transmission of a PUSCH and transmission of a DMRS for the PUSCH may be indicated (or scheduled) by one DCI format. The PUSCH and the DMRS for the PUSCH may be collectively referred to as a PUSCH. Transmitting a PUSCH may also mean transmitting a PUSCH and a DMRS for the PUSCH.

The propagation path of the PUSCH may be estimated from the DMRS for that PUSCH.

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

The transmission of a PUCCH and the transmission of a DMRS for the PUCCH may be indicated (or triggered) by one DCI format. One or both of the mapping of the PUCCH to resource elements and the mapping of the DMRS for the PUCCH to resource elements may be provided by one PUCCH format. The PUCCH and the DMRS for the PUCCH may be collectively referred to as the PUCCH. Transmitting a PUCCH may also mean transmitting a PUCCH and a DMRS for the PUCCH.

The propagation path of the PUCCH may be estimated from the DMRS for that PUCCH.

The downlink physical channel may correspond to a set of resource elements that convey information generated in a higher layer. The downlink physical channel may be a physical channel used in a downlink component carrier. The base station device 3 may transmit the downlink physical channel. The terminal device 1 may receive the downlink physical channel. In a wireless communication system according to one aspect of the present embodiment, at least some or all of the following downlink physical channels may be used.
・PBCH (Physical Broadcast Channel)
・PDCCH (Physical Downlink Control Channel)
・PDSCH (Physical Downlink Shared Channel)

The PBCH may be transmitted to convey one or both of the MIB (Master Information Block) and physical layer control information. Here, the physical layer control information is information generated in the physical layer. The MIB is a set of parameters placed on the BCCH (Broadcast Control CHannel), which is a logical channel of the MAC layer. The BCCH is placed on the BCH, which is a channel of the transport layer. The BCH may be mapped to the PBCH. The terminal device 1 may receive a PBCH in which the MIB and one or both of the physical layer control information are placed. The base station device 3 may transmit a PBCH in which the MIB and one or both of the physical layer control information are placed.

For example, the physical layer control information may be configured with 8 bits. The physical layer control information may include at least some or all of the following 0A to 0D.
A) Radio frame bit B) Half radio frame (half system frame, half frame) bit C) SS/PBCH block index bit D) Subcarrier offset bit

The radio frame bits are used to indicate the radio frame in which the PBCH is transmitted (the radio frame including the slot in which the PBCH is transmitted). The radio frame bits include 4 bits. The radio frame bits may be composed of 4 bits of a 10-bit radio frame indicator. For example, the radio frame indicator may be used at least to identify radio frames from index 0 to index 1023.

The half radio frame bit is used to indicate whether the PBCH is transmitted in the first five subframes or the last five subframes of the radio frame in which the PBCH is transmitted. Here, a half radio frame may be composed of five subframes. Alternatively, a half radio frame may be composed of the first five subframes of the ten subframes included in a radio frame. Alternatively, a half radio frame may be composed of the last five subframes of the ten subframes included in a radio frame.

The SS/PBCH block index bits are used to indicate the SS/PBCH block index. The SS/PBCH block index bits include three bits. The SS/PBCH block index bits may be composed of three bits of the six-bit SS/PBCH block index indicator. The SS/PBCH block index indicator may be used at least to identify SS/PBCH blocks from index 0 to index 63.

The subcarrier offset bit is used to indicate the subcarrier offset. The subcarrier offset may be used to indicate the difference between the first subcarrier to which the PBCH is mapped and the first subcarrier to which the control resource set with index 0 is mapped.

The PDCCH may be transmitted to transmit downlink control information (DCI). The downlink control information may be placed in the PDCCH. The terminal device 1 may receive the PDCCH in which the downlink control information is placed. The base station device 3 may transmit the PDCCH in which the downlink control information is placed.

Downlink control information may be transmitted using a DCI format. The DCI format may be interpreted as the format of the downlink control information. The DCI format may also be interpreted as a set of downlink control information set in a certain downlink control information format.

DCI format 0_0, DCI format 0_1, DCI format 1_0, and DCI format 1_1 are DCI formats. The uplink DCI format is a general term for DCI format 0_0 and DCI format 0_1. The downlink DCI format is a general term for DCI format 1_0 and DCI format 1_1.

DCI format 0_0 is used at least for scheduling a PUSCH allocated to a certain cell, and is configured to include at least some or all of fields 1A to 1E.
1A) Identifier field for DCI formats
1B) Frequency domain resource assignment field
1C) Time domain resource assignment field
1D) Frequency hopping flag field
1E) MCS field (Modulation and Coding Scheme field)

The DCI format specification field may indicate whether the DCI format including the DCI format specification field is an uplink DCI format or a downlink DCI format. In other words, the DCI format specification field may be included in both the uplink DCI format and the downlink DCI format. Here, the DCI format specification field included in DCI format 0_0 may indicate 0.

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

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

The frequency hopping flag field may be used to indicate whether frequency hopping is applied to the PUSCH.

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

DCI format 0_0 does not have to include fields used for CSI requests.

DCI format 0_0 does not need to include a carrier indicator field. In other words, the serving cell to which the uplink component carrier on which the PUSCH scheduled by DCI format 0_0 is allocated may be the same as the serving cell of the uplink component carrier on which the PDCCH including DCI format 0_0 is allocated. Based on detecting DCI format 0_0 on a downlink component carrier of a serving cell, terminal device 1 may recognize that the PUSCH scheduled by DCI format 0_0 is to be allocated on the uplink component carrier of the serving cell.

DCI format 0_0 may not include a BWP field (BWP indication field). Here, DCI format 0_0 may be a DCI format for scheduling a PUSCH without changing the active uplink BWP. Based on detecting DCI format 0_0 used for scheduling a PUSCH, the terminal device 1 may recognize that the PUSCH will be transmitted without switching the active uplink BWP.

DCI format 0_1 is used at least for scheduling a PUSCH allocated to a certain cell, and is configured to include at least some or all of fields 2A to 2H.
2A) DCI format specific field 2B) Frequency domain resource allocation field 2C) Uplink time domain resource allocation field 2D) Frequency hopping flag field 2E) MCS field 2F) CSI request field
2G) BWP field
2H) Carrier indicator field

The DCI format specific field included in DCI format 0_1 may indicate 0.

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

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

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

The BWP field of DCI format 0_1 may be used to indicate the uplink BWP in which the PUSCH scheduled by DCI format 0_1 is placed. In other words, DCI format 0_1 may involve a change in the active uplink BWP. The terminal device 1 may recognize the uplink BWP in which the PUSCH is placed based on detecting DCI format 0_1 used for scheduling the PUSCH.

DCI format 0_1, which does not include a BWP field, may be a DCI format for scheduling a PUSCH without changing the active uplink BWP. The terminal device 1 may recognize that the PUSCH will be transmitted without switching the active uplink BWP based on detecting DCI format D0_1, which is DCI format 0_1 used for scheduling a PUSCH and does not include a BWP field.

If DCI format 0_1 includes a BWP field but terminal device 1 does not support the BWP switching function using DCI format 0_1, the BWP field may be ignored by terminal device 1. In other words, a terminal device 1 that does not support the BWP switching function may recognize that it will transmit the PUSCH without switching the active uplink BWP based on detecting DCI format 0_1 that is used for PUSCH scheduling and includes a BWP field. Here, if terminal device 1 supports the BWP switching function, it may report that "terminal device 1 supports the BWP switching function" in the RRC layer capability information reporting procedure.

The CSI request field is used to indicate the reporting of CSI.

If DCI format 0_1 includes a carrier indicator field, the carrier indicator field may be used to indicate the uplink component carrier on which the PUSCH is allocated. If DCI format 0_1 does not include a carrier indicator field, the uplink component carrier on which the PUSCH is allocated may be the same as the uplink component carrier on which the PDCCH including DCI format 0_1 used for scheduling the PUSCH is allocated. If the number of uplink component carriers configured in the terminal device 1 in a serving cell group is two or more (if uplink carrier aggregation is operated in a serving cell group), the number of bits of the carrier indicator field included in DCI format 0_1 used for scheduling the PUSCH allocated to the serving cell group may be one bit or more (e.g., three bits). If the number of uplink component carriers configured for terminal device 1 in a certain serving cell group is 1 (if uplink carrier aggregation is not operated 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 allocated to that certain serving cell group may be 0 bits (or the carrier indicator field may not be included in DCI format 0_1 used for scheduling the PUSCH allocated to that certain serving cell group).

DCI format 1_0 is used at least for scheduling PDSCHs allocated to a certain cell, and is configured to include at least some or all of 3A to 3F.
3A) DCI format specific field 3B) Frequency domain resource allocation field 3C) Time domain resource allocation field 3D) MCS field 3E) PDSCH to HARQ feedback timing indicator field
3F) PUCCH resource indicator field

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

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

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

The MCS field included in DCI format 1_0 may be used to indicate at least one or both of the modulation scheme and the target coding rate for the PDSCH. The target coding rate may be the target coding rate for the transport block to be placed in the PDSCH. The size of the transport block (TBS: Transport Block Size) to be placed in the PDSCH may be determined based on one or both of the target coding rate and the modulation scheme for the PDSCH.

The PDSCH_HARQ feedback timing indication field may be used to indicate the offset from the slot containing the last OFDM symbol of the PDSCH to the slot containing the first OFDM symbol of the PUCCH.

The PUCCH resource indication field may be a field indicating the index of one or more PUCCH resources included in a PUCCH resource set. A PUCCH resource set may include one or more PUCCH resources.

DCI format 1_0 may not include a carrier indicator field. In other words, the downlink component carrier on which the PDSCH scheduled by DCI format 1_0 is allocated may be the same as the downlink component carrier on which the PDCCH including DCI format 1_0 is allocated. Based on detecting DCI format 1_0 on a certain downlink component carrier, the terminal device 1 may recognize that the PDSCH scheduled by DCI format 1_0 is to be allocated to that downlink component carrier.

DCI format 1_0 may not include a BWP field. Here, DCI format 1_0 may be a DCI format for scheduling a PDSCH without changing the active downlink BWP. By detecting DCI format 1_0 used for scheduling a PDSCH, the terminal device 1 may recognize that it will receive the PDSCH without switching the active downlink BWP.

DCI format 1_1 is used at least for scheduling PDSCHs allocated to a certain cell, and is configured to include at least some or all of 4A to 4I.
4A) DCI format specific field 4B) Frequency domain resource allocation field 4C) Time domain resource allocation field 4E) MCS field 4F) PDSCH_HARQ feedback timing indication field 4G) PUCCH resource indication field 4H) BWP field 4I) Carrier indicator field

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

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

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

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

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

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

The BWP field of DCI format 1_1 may be used to indicate the downlink BWP in which the PDSCH scheduled by DCI format 1_1 is allocated. In other words, DCI format 1_1 may involve a change in the active downlink BWP. The terminal device 1 may recognize the downlink BWP in which the PUSCH is allocated based on detecting DCI format 1_1 used for scheduling the PDSCH.

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

If DCI format 1_1 includes a BWP field but terminal device 1 does not support the BWP switching function using DCI format 1_1, the BWP field may be ignored by terminal device 1. In other words, a terminal device 1 that does not support the BWP switching function may recognize that it will receive the PDSCH without switching the active downlink BWP based on detecting DCI format 1_1 that is used for PDSCH scheduling and includes a BWP field. Here, if terminal device 1 supports the BWP switching function, it may report that "terminal device 1 supports the BWP switching function" in the RRC layer capability information reporting procedure.

If DCI format 1_1 includes a carrier indicator field, the carrier indicator field may be used to indicate the downlink component carrier on which the PDSCH is allocated. If DCI format 1_1 does not include a carrier indicator field, the downlink component carrier on which the PDSCH is allocated may be the same as the downlink component carrier on which the PDCCH including DCI format 1_1 used for scheduling the PDSCH is allocated. If the number of downlink component carriers configured in the terminal device 1 in a serving cell group is two or more (if downlink carrier aggregation is operated in a serving cell group), the number of bits in the carrier indicator field included in DCI format 1_1 used for scheduling the PDSCH allocated to the serving cell group may be one bit or more (e.g., three bits). If the number of downlink component carriers configured for a terminal device 1 in a certain serving cell group is 1 (if downlink carrier aggregation is not operated 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 allocated to that certain serving cell group may be 0 (or the carrier indicator field may not be included in DCI format 1_1 used for scheduling the PDSCH allocated to that certain serving cell group).

The PDSCH may be transmitted to transmit a transport block. The PDSCH may be used to transmit a transport block delivered by the DL-SCH. The PDSCH may be used to transmit a transport block. The transport block may be placed in the PDSCH. The transport block corresponding to the DL-SCH may be placed in the PDSCH. The base station device 3 may transmit the PDSCH. The terminal device 1 may receive the PDSCH.

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

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

7 is a diagram showing an example of the configuration of an SS/PBCH block according to one embodiment of the present invention. In FIG. 7, the horizontal axis represents the time axis (OFDM symbol index l _sym ), and the vertical axis represents the frequency domain. Block 700 represents a set of resource elements for the PSS. Block 720 represents a set of resource elements for the SSS. Four blocks (blocks 710, 711, 712, and 713) represent sets of resource elements for the PBCH and DMRS for the PBCH (DMRS related to the PBCH, DMRS included in the PBCH, and DMRS corresponding to the PBCH).

As shown in Figure 7, the SS/PBCH block includes a PSS, SSS, and PBCH. The SS/PBCH block also includes four consecutive OFDM symbols. The SS/PBCH block includes 240 subcarriers. The PSS is allocated to the 57th to 183rd subcarriers in the first OFDM symbol. The SSS is allocated to the 57th to 183rd subcarriers in the third OFDM symbol. The 1st to 56th subcarriers in the first OFDM symbol may be set to zero. The 184th to 240th subcarriers in the first OFDM symbol may be set to zero. The 49th to 56th subcarriers in the third OFDM symbol may be set to zero. The 184th to 192nd subcarriers in the third OFDM symbol may be set to zero. The PBCH is allocated to the 1st to 240th subcarriers in the second OFDM symbol, which are subcarriers where no DMRS for the PBCH is allocated. The PBCH is allocated to the 1st to 48th subcarriers of the third OFDM symbol, which are subcarriers where DMRS for the PBCH is not allocated. The PBCH is allocated to the 193rd to 240th subcarriers of the third OFDM symbol, which are subcarriers where DMRS for the PBCH is not allocated. The PBCH is allocated to the 1st to 240th subcarriers of the fourth OFDM symbol, which are subcarriers where DMRS for the PBCH is not allocated.

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

The PBCH on which the PBCH symbols are transmitted at a certain antenna port may be estimated by the DMRS for the PBCH that is placed in the slot to which the PBCH is mapped and that is included in the SS/PBCH block to which the PBCH belongs.

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

The set of antenna ports for DMRS for a PDSCH (DMRS related to a PDSCH, DMRS included in a PDSCH, DMRS corresponding to a PDSCH) may be determined based on the set of antenna ports for the PDSCH. In other words, the set of antenna ports for DMRS for a PDSCH may be the same as the set of antenna ports for the PDSCH.

Transmission of a PDSCH and transmission of a DMRS for the PDSCH may be indicated (or scheduled) by one DCI format. The PDSCH and the DMRS for the PDSCH may be collectively referred to as the PDSCH. Transmitting a PDSCH may also mean transmitting a PDSCH and a DMRS for the PDSCH.

The propagation path of a PDSCH may be estimated from the DMRS for that PDSCH. If the set of resource elements on which a certain PDSCH symbol is transmitted and the set of resource elements on which a DMRS symbol for that PDSCH is transmitted are included in the same precoding resource group (PRG), the PDSCH on which the PDSCH symbol is transmitted at a certain antenna port may be estimated from the DMRS for that PDSCH.

The antenna port for DMRS for PDCCH (DMRS related to PDCCH, DMRS included in PDCCH, DMRS corresponding to PDCCH) may be the same as the antenna port for PDCCH.

The PDCCH may be estimated from the DMRS for that PDCCH. In other words, the propagation path of the PDCCH may be estimated from the DMRS for that PDCCH. If the same precoder is applied (assumed to be applied, assumed to be applied) to the set of resource elements on which a certain PDCCH symbol is transmitted and the set of resource elements on which a DMRS symbol for that PDCCH is transmitted, the PDCCH on which the PDCCH symbol is transmitted at a certain antenna port may be estimated by the DMRS for that PDCCH.

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

The BCH of the transport layer is mapped to the PBCH of the physical layer. That is, transport blocks that pass through the BCH of the transport layer are delivered to the PBCH of the physical layer. The UL-SCH of the transport layer is mapped to the PUSCH of the physical layer. That is, transport blocks that pass through the UL-SCH of the transport layer are delivered to the PUSCH of the physical layer. The DL-SCH of the transport layer is mapped to the PDSCH of the physical layer. That is, transport blocks that pass through the DL-SCH of the transport layer are delivered to the PDSCH of the physical layer.

One UL-SCH and one DL-SCH may be assigned to each serving cell. The BCH may be assigned to the PCell. The BCH does not have to be assigned to the PSCell or SCell.

At the MAC layer, HARQ (Hybrid Automatic Repeat reQuest) is controlled for each transport block.

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

Upper layer parameters that are common to multiple terminal devices 1 are also referred to as common upper layer parameters. Here, common upper layer parameters may be defined as parameters that are specific to the serving cell. Here, parameters that are specific to the serving cell may be parameters that are common to the terminal devices (e.g., terminal devices 1-A, 1-B, and 1-C) in which the serving cell is configured.

For example, the common upper layer parameters may be included in an RRC message delivered on the BCCH. For example, the common upper layer parameters may be included in an RRC message delivered on the DCCH.

Among certain upper layer parameters, upper layer parameters that differ from common upper layer parameters are also referred to as dedicated upper layer parameters. Here, dedicated upper layer parameters can provide dedicated RRC parameters to terminal device 1-A, in which the serving cell is configured. In other words, dedicated RRC parameters are upper layer parameters that can provide unique settings for each of terminal devices 1-A, 1-B, and 1-C.

The logical channel BCCH is mapped to the BCH or DL-SCH of the transport layer. For example, a transport block containing MIB information is delivered to the BCH of the transport layer. A transport block containing system information other than MIB is delivered to the DL-SCH of the transport layer. The CCCH is mapped to the DL-SCH or UL-SCH. In other words, a transport block mapped to the CCCH is delivered to the DL-SCH or UL-SCH. The DCCH is mapped to the DL-SCH or UL-SCH. In other words, a transport block mapped to the DCCH is delivered to the DL-SCH or UL-SCH.

An RRC message includes one or more parameters managed in the RRC layer. Here, parameters managed in the RRC layer are also referred to as RRC parameters. For example, an RRC message may include an MIB. An RRC message may also include system information. An RRC message may also include a message corresponding to a CCCH. An RRC message including a message corresponding to a DCCH is also referred to as an individual RRC message.

Upper layer parameters are RRC parameters or parameters included in the MAC CE (Medium Access Control Control Element). In other words, upper layer parameters are a collective term for the MIB, system information, messages corresponding to CCCH, messages corresponding to DCCH, and parameters included in the MAC CE. Parameters included in the MAC CE are sent using MAC CE (Control Element) commands.

The procedure performed by the terminal device 1 includes at least some or all of the following steps 5A to 5C.
5A) Cell Search
5B) Random Access
5C) Data communication

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

The PSS sequence is assigned based at least on the physical cell ID. The SSS sequence is assigned based at least on the physical cell ID.

SS/PBCH block candidates indicate resources on which SS/PBCH block transmission is permitted (possibly, reserved, configured, specified, possible).

The set of SS/PBCH block candidates in a given half 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.

The base station device 3 transmits SS/PBCH blocks with one or more indexes at a predetermined interval. The terminal device 1 may detect at least one of the SS/PBCH blocks with one or more indexes and attempt to decode the PBCH contained in that SS/PBCH block.

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

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

The terminal device 1 transmits one random access preamble selected from the PRACH opportunities corresponding to the index of the SS/PBCH block candidate in which the SS/PBCH block is detected.

The terminal device 1 may attempt to detect DCI format 1_0 with a CRC scrambled with RA-RNTI. Message 2 is a procedure by which the terminal device 1 attempts to detect DCI format 1_0 with a CRC (Cyclic Redundancy Check) scrambled with RA-RNTI (Random Access - Radio Network Temporary Identifier). The terminal device 1 attempts to detect a PDCCH including the DCI format in the control resource set given based on the MIB included in the PBCH included in the SS/PBCH block detected based on the cell search, and in the resources indicated based on the setting of the search area set. Message 2 is also called a random access response (RAR). The terminal device 1 may receive a random access response (or a random access response message) with a PDCCH/PDSCH as a message.

Message 3 is a procedure for transmitting a PUSCH scheduled by the random access response grant included in DCI format 1_0 detected by the message 2 procedure. Here, the random access response grant is indicated by the MAC CE included in the PDSCH scheduled by DCI format 1_0.

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

Message 3: PUSCH retransmissions are scheduled using DCI format 0_0 with a scrambled CRC based on the TC-RNTI (Temporary Cell-Radio Network Temporary Identifier).

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

Data communication is a general term for downlink communication and uplink communication.

During data communication, the terminal device 1 attempts to detect the PDCCH in resources identified based on the control resource set and the search space set (monitors the PDCCH).

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

The set of resource blocks that make up the control resource set may be indicated by higher layer parameters. The number of OFDM symbols that make up the control resource set may be indicated by higher layer parameters.

The terminal device 1 attempts to detect a PDCCH in the search space set. Here, attempting to detect a PDCCH in the search space set may mean attempting to detect a PDCCH candidate in the search space set, or attempting to detect a DCI format in the search space set, or attempting to detect a PDCCH in the control resource set, or attempting to detect a PDCCH candidate in the control resource set, or attempting to detect a DCI format in the control resource set.

The search space set is defined as a set of PDCCH candidates. The search space set may be a CSS (Common Search Space) set or a USS (UE-specific Search Space) set. The terminal device 1 attempts to detect PDCCH candidates in some or all of the 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 the UE-specific search space set.

The Type 0 PDCCH common search space set may be used as the common search space set with index 0. The Type 0 PDCCH common search space set may be the common search space set with index 0.

The CSS set is a collective term for the 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, and Type 3 PDCCH common search space set. The USS set is also called the UE-specific PDCCH search space set.

A search area set is associated with (contained in, corresponds to) a control resource set. The index of the control resource set associated with the search area set may be indicated by a higher layer parameter.

For a given search area set, some or all of 6A to 6C may be indicated by at least higher layer parameters.
6A) PDCCH monitoring periodicity
6B) PDCCH monitoring pattern within a slot
6C) PDCCH monitoring offset

A monitoring occasion for a search area set may correspond to an OFDM symbol in which the first OFDM symbol of a control resource set associated with the search area set is located. A monitoring occasion for a search area set may correspond to resources of a control resource set associated with the search area set starting from the first OFDM symbol of the control resource set. The monitoring occasion for the search area set is given based on at least some or all of the PDCCH monitoring interval, the PDCCH monitoring pattern within the slot, and the PDCCH monitoring offset.

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

In Figure 8, the solid white blocks in primary cell 301 indicate search area set 91, the solid black blocks in primary cell 301 indicate search area set 92, the blocks in secondary cell 302 indicate search area set 93, and the blocks in secondary cell 303 indicate search area set 94.

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

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

The monitoring interval of search area set 93 is set to 2 slots, the monitoring offset of search area set 93 is set to 0 slots, and the monitoring pattern of search area set 93 is set to [0,0,0,0,0,0,0,1,0,0,0,0,0,0]. That is, the monitoring opportunity for search area set 93 corresponds to the 8th OFDM symbol (OFDM symbol #7) in each of the even slots.

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

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

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

A Type 1 PDCCH common search space set may be used at least for DCI formats with a CRC sequence scrambled by a Random Access-Radio Network Temporary Identifier (RA-RNTI) and/or a CRC sequence scrambled by a Temporary Cell-Radio Network Temporary Identifier (TC-RNTI).

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

A Type 3 PDCCH common search space set may be used for DCI formats with a CRC sequence scrambled by the C-RNTI (Cell-Radio Network Temporary Identifier).

The UE-specific PDCCH search space set may be used at least for DCI formats with CRC sequences scrambled by the C-RNTI.

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

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

In configured scheduling (configured grant), the uplink grant for scheduling the PUSCH is configured for each transmission period of the PUSCH. When the PUSCH is scheduled using an uplink DCI format, some or all of the information indicated by the uplink DCI format may be indicated by the uplink grant configured in the case of configured scheduling.

PUSCH transmission may correspond to the configured scheduling type 1 or the configured scheduling type 2. That is, the configured scheduling may be either the configured scheduling type 1 or the configured scheduling type 2. PUSCH transmission of the configured scheduling type 1 may be configured semi-statically. For example, PUSCH transmission of the configured scheduling type 1 may be operated in response to reception of certain higher layer parameters. The certain higher layer parameters may be configuredGrantConfig. For example, configuredGrantConfig may include rrc-ConfiguredUplinkGrant. PUSCH transmission may be operated without detecting an uplink grant in DCI.

The configured scheduling type 2 PUSCH transmission may be scheduled semi-persistently. For example, it may be scheduled by a certain uplink grant. The certain uplink grant may be included in an activation DCI (activation DCI or valid activation DCI). For example, after receiving certain upper layer parameters, the configured scheduling type 2 PUSCH transmission may be scheduled by a certain uplink grant. The certain upper layer parameters may be configuredGrantConfig. For example, configuredGrantConfig may not include rrc-ConfiguredUplinkGrant.

The system frame number (SFN) n/ _f may be a number assigned to a radio frame and/or an index for a radio frame. The system frame number may be composed of 10 bits. At least a portion of the system frame number may be signaled in the MIB. For example, 6 bits (e.g., 6 most significant bits) of the 10-bit system frame number may be signaled in the MIB. At least a portion of the system frame number may be determined based on the PBCH that carries the MIB. For example, 4 bits (e.g., 4 least significant bits) of the 10-bit system frame number may be transmitted in the PBCH transport block as part of channel coding.

PDCCH-Config may be a dedicated upper layer parameter. PDCCH-Config may set parameters for the PDCCH. Multiple CORESETs (e.g., up to three) may be set in PDCCH-Config. A CORESET ID may be set in one CORESET. A CORESET pool index may be set in one CORESET.

The PDCCH configuration may include two different CORESET pool indices. For example, two CORESET pool index values (0 and 1) may be provided. For example, two CORESET pool index values may be provided for the First CORESET and the Second CORESET. The PDCCH configuration may be PDCCH-Config.

PDSCH-Config may be dedicated higher layer parameters. PDSCH-Config may set parameters for the PDSCH.

If multiple PDCCH candidates (PDCCH candidate(s)) are associated with a search space set configured by a higher layer parameter, one PDCCH candidate is used. This one PDCCH candidate may be the PDCCH candidate that is started earlier of the two PDCCH candidates. The higher layer parameter may be searchSpaceLinking.

Multiple TRPs (Transmission Reception Points, or Transmit/Receive Points) may be used. The base station device 3 may be configured with multiple TRPs (Multi-TRP). The terminal device 1 may be scheduled by two TRPs in one serving cell. In Multi-TRP, one of the operating modes of single-DCI and multi-DCI may be used. In Multi-TRP, uplink control may be completed in the MAC layer and the physical layer. In Multi-TRP, downlink control may be completed in the MAC layer and the physical layer. In Single-DCI mode, the terminal device 1 may be scheduled by the same DCI for multiple TRPs. In Multi-DCI mode, the terminal device 1 may be scheduled by independent DCI from each TRP.

One or both of the terminal device 1 and the base station device 3 may form a beam (beamforming). For example, one or both of the terminal device 1 and the base station device 3 may transmit radio waves (electromagnetic waves) in a specific spatial direction by beamforming. For example, one or both of the terminal device 1 and the base station device 3 may receive radio waves from a specific spatial direction by beamforming. One or more antennas may be provided and used for transmitting and/or receiving radio waves. A directional radio wave may be referred to as a beam. Information related to a beam may be referred to as beam information. For example, the beam information may be a specific spatial direction. For example, the beam information may be the direction of arrival of the radio waves. The beam information may be a TCI status. The beam information may be an uplink transmit spatial filter. The beam information may be an SRS resource indication. The beam information may be a QCL assumption or a QCL-related information.

The terminal device 1 may receive the PDSCH. The base station device 3 may transmit the PDSCH. One transmission method may be defined for the PDSCH. One transmission method may be used for all PDSCH transmissions.

The terminal device 1 may receive on the PDSCH. The base station device 3 may transmit on the PDSCH. One transmission method may be transmission method 1. In transmission method 1, it may be assumed that transmission on the PDSCH is performed in up to eight layers. Each layer may be mapped to one or more antenna ports. The one or more antenna ports may be some or all of antenna ports 1000-1023. For example, if an extended CSI port is not configured, the one or more antenna ports may be some or all of antenna ports 1000-1023. For example, if an extended CSI port is configured, the one or more antenna ports may be some or all of antenna ports 1000-1127.

The terminal device 1 may be scheduled to receive the PDSCH. For example, the terminal device 1 may be scheduled to receive the PDSCH by DCI. PDSCH reception may be scheduled by a DCI format in the PDCCH. The PDSCH may be scheduled in a DCI format. The terminal device 1 may receive a scheduling grant in a DCI format. When a scheduling grant is received, downlink resource allocation may be used.

The terminal device 1 may be configured with the upper layer parameter TCI-State. For example, the terminal device 1 may be configured with one list in the upper layer parameter PDSCH-Config. One list may include up to M upper layer parameters TCI-State. One list may be a list of up to M upper layer parameters TCI-State. The terminal device 1 may be configured with one list to decode (receive) the PDSCH according to the PDCCH with DCI. M may depend on the terminal capability (UE capability). For example, M may depend on the terminal capability maxNumberConfiguredTCIStatePerCC. TCI-State may be referred to as the TCI state.

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

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

One list may be configured by the upper layer parameter dlOrJointTCI-StateList. For example, one list may be configured in the upper layer parameter PDSCH-Config. One list may include up to 128 upper layer parameters TCI-State. One list may be a list of up to 128 upper layer parameters TCI-State. One list may be configured to provide one reference signal. The upper layer parameter TCI-State may be configured to provide one reference signal. One reference signal may be a reference signal for DMRS of PDSCH and QCL for DMRS of PDCCH. One reference signal may be a reference signal for CSI-RS. One list may be configured to provide one reference. The upper layer parameter TCI-state may be configured to provide one reference. One reference may be used to determine an uplink transmit spatial filter (UL TX spatial filter). The uplink transmit spatial filter may be used for PUSCH, PUCCH, and SRS. That is, one reference may be provided to determine the uplink transmit spatial filters for PUSCH, PUCCH, and SRS. The TCI-State may be referred to as the DL/Joint TCI state or the unified TCI state. Setting the upper layer parameter dlOrJointTCI-StateList may result in the unified TCI state being set. Setting the upper layer parameter dlOrJointTCI-StateList may result in the unified TCI state being set.

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

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

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

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

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

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

The terminal device 1 may receive an upper layer configuration. After the terminal device 1 receives the first upper layer configuration of the "TCI state to be set" and before one "indicated TCI state" is applied from the "TCI state to be set", the terminal device 1 may assume that the DMRS of the PDSCH, the DMRS of the PDCCH, and the CSI-RS to which the "indicated TCI state" applies are the SS/PBCH block and QCL. Setting the upper layer parameter DLorJoint-TCIStateList may mean that the "TCI state to be set" is set. Setting the upper layer parameter DLorJoint-TCIStateList may mean that a unified TCI state is set. Setting the "TCI state to be set" may mean that a unified TCI state is set. DLorJoint-TCIStateList may be accompanied by multiple upper layer parameters TCI-State.

After the terminal device 1 receives the first upper layer setting of the "TCI state to be set" and before one "indicated TCI state" is applied from the "TCI state to be set", the terminal device 1 may assume that the first uplink transmission spatial filter for PUSCH, PUCCH, and SRS to which the "indicated TCI state" is applied is the same as the second uplink transmission spatial filter. The second uplink transmission spatial filter may be an uplink transmission spatial filter for PUSCH transmission scheduled by a random access response grant in the initial access procedure. Setting the upper layer parameter ul-TCI-StateList may mean setting the "TCI state to be set". Setting the upper layer parameter ul-TCI-StateList may mean setting a unified TCI state. Setting the "TCI state to be set" may mean setting a unified TCI state. ul-TCI-StateList may be accompanied by multiple upper layer parameters TCI-State.

The terminal device 1 may receive an upper layer configuration. After the terminal device 1 receives the first upper layer configuration of the "TCI state to be set" as part of the synchronized reconfiguration and before one "indicated TCI state" is applied from the "TCI state to be set", the DMRS of the PDSCH, DMRS of the PDCCH, and CSI-RS to which the indicated TCI state is applied may be an SS/PBCH block or a CSI-RS resource and a QCL. For example, the SS/PBCH block or CSI-RS resource may be identified in a random access procedure initiated by the synchronized reconfiguration.

The terminal device 1 may receive an upper layer configuration. After the terminal device 1 receives the first upper layer configuration of the "TCI state to be set" as part of the synchronized reconfiguration and before one "indicated TCI state" is applied from the "TCI state to be set", it may be assumed that the first uplink transmission spatial filter for the PUSCH, PUCCH, and SRS that applies the indicated TCI state is the same as the second uplink transmission spatial filter. The second uplink transmission spatial filter may be an uplink spatial filter for PUSCH transmissions scheduled by a random access response grant (RAR UL grant) in a random access procedure. The second uplink transmission spatial filter may be an uplink transmission spatial filter for PUSCH transmissions scheduled by a random access response grant in a random access procedure initiated by the synchronized reconfiguration.

If the terminal device 1 receives a "TCI state to be set" configuration with one TCI state, the terminal device 1 may obtain a QCL assumption from the TCI state to be set. The TCI state to be set may be a TCI state for CSI-RS, DMRS of PDSCH, and DMRS of PDCCH to which the indicated TCI state applies. The TCI state to be set may be the upper layer parameter dl-OrJointTCI-StateList.

If the terminal device 1 receives a "TCI state to be set" configuration with one TCI state, the terminal device 1 may determine the uplink transmit spatial filter from the TCI state to be set. The TCI state to be set may be a TCI state for PUSCH, PUCCH, and SRS to which the indicated TCI state applies. The TCI state to be set may be the upper layer parameter dl-OrJointTCI-StateList or ul-TCI-StateList.

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

When multi-DCI mode is configured, the terminal device 1 may receive an activation command ("activated TCI state") for a CORESET associated with each CORESET pool index. The activation command may be used to map up to eight TCI states to code points in the DCI field 'Transmission Configuration Indication'. When a set of TCI state IDs is activated for one CORESET pool index, the "activated TCI state" corresponding to the one CORESET pool index may be associated with one physical cell ID, and the "activated TCI state" corresponding to a CORESET pool index different from the one CORESET pool index may be associated with a physical cell ID different from the one physical cell ID. The activation command may be received as a MAC CE. One or more CORESETs may be configured in one BWP. One CORESET may correspond to a CORESET pool index of '0' or '1'. The multi-DCI mode may be configured when the higher layer parameter PDCCH-Config contains two different values for the CORESET pool index (CORESET Pool Index or coresetPoolIndex).

A single code point in the DCI field 'Transmission Configuration Indication' (i.e., the TCI field) may contain up to two TCI states. The terminal device 1 may receive an activation command. The activation command may be used to map up to eight combinations of up to two TCI states to a code point in the DCI field 'Transmission Configuration Indication'. The terminal device 1 may not expect to receive more than eight TCI states in an activation command.

When the terminal device 1 transmits a first PUCCH in a first slot, the mapping between the TCI state and the code point may be applied from the second slot. The first PUCCH may be accompanied by first HARQ-ACK information. The first PUCCH may be transmitted in response to a first PDSCH. The first PDSCH may convey an activation command.

If the TCI field is present and the time offset is greater than or equal to the threshold, and after the first setting of the TCI state is received and before an activation command is received, the terminal device 1 may assume that the DMRS of the PDSCH in one serving cell is QCL for the SS/PBCH block and QCL type A. The presence of the TCI field may mean that the upper layer parameter tci-PresentInDCI is set to 'enabled'. The presence of the TCI field may mean that the upper layer parameter tci-PresentDCI-1-2 is set for CORESET scheduling the PDSCH. The time offset may be the offset between reception of the DL DCI and the PDSCH. The threshold may be timeDurationForQCL. The threshold may be based on the reported terminal capabilities.

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

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

If SFN is configured for the PDCCH, and if SFN is configured for the PDSCH, and if the PDSCH is scheduled by a DCI format, and if the time offset is greater than or equal to a threshold, and if the default beam is supported, the QCL assumption or TCI state for the PDSCH may be the same as the QCL assumption or TCI state applied for CORESET. Also, if dynamic switching is not supported, CORESET may be activated in two TCI states. CORESET may be the CORESET for receiving DL DCI. If SFN is configured for the PDCCH, and if SFN is configured for the PDSCH, and if the PDSCH is scheduled by a DCI format, and if the time offset is greater than or equal to a threshold, and if the default beam is not supported, it may be assumed that a TCI field is present. Configuring SFN for the PDCCH may mean configuring the upper layer parameter sfnSchemePdcch. Configuring SFN for the PDSCH may mean configuring the upper layer parameter sfnSchemePdsch. The DCI format may be one of DCI format 1_0, DCI format 1_1, and DCI format 1_2. The default beam may be sfn-DefaultDL-BeamSetup for DCI without a TCI field. The time offset may be the time offset between reception of the DL DCI and the corresponding PDSCH. The threshold may be timeDurationForQCL.

If SFN is configured for PDSCH, and SFN is not configured for PDCCH, and PDSCH is scheduled by DCI format 1_1/1_2, and the time offset is greater than or equal to a threshold, the presence of the TCI field may be expected.

If the PDSCH is scheduled by DCI format 1_0/1_1/1_2, and SFN scheme A is configured for the PDCCH, and SFN is not configured for the PDSCH, and there is no TCI codepoint (codepoint in the TCI field) with two TCI states, and the time offset is greater than or equal to the threshold, and the CORESET scheduling the PDSCH is indicated by two TCI states, the TCI state or QCL assumption for the PDSCH may be the same as the first TCI state and first QCL assumption applied for the CORESET. Configuring SFN scheme A for the PDCCH may also mean configuring sfnSchemePdcch with 'sfnSchemeA' set.

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

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

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

For periodic CSI-RS resources, the TCI state may indicate QCL for the SS/PBCH block and Type C. The SS/PBCH block may have a PCI different from the PCI of the serving cell. The periodic CSI-RS resources may be CSI-RS resources in the NZP CSI-RS resource set (NZP-CSI-RS-ResourceSet) for the Tracking Reference Signal (TRS). The NZP may be non-zero power. The CSI-RS resource set for the TRS may be the CSI-RS resource set for which the higher layer parameter trs-Info is set.

If a unified TCI state is configured for periodic CSI-RS and semi-persistent CSI-RS resources, the terminal device 1 may assume that the indicated TCI state does not apply.

For aperiodic CSI-RS resources, the TCI state may indicate QCL for periodic CSI-RS resources and type A. The aperiodic CSI-RS resources may be CSI-RS resources in the NZP CSI-RS resource set for TRS. The periodic CSI-RS resources may be CSI-RS resources in the NZP CSI-RS resource set for TRS.

For the first CSI-RS resource, the TCI state may indicate QCL with respect to the second CSI-RS resource and Type A. For the first CSI-RS resource, the TCI state may indicate QCL with respect to the third CSI-RS resource and Type B. The first CSI-RS resource may be a CSI-RS resource in the NZP CSI-RS resource set for TRS. The first CSI-RS resource may not be a CSI-RS resource in the NZP CSI-RS resource set for repetition. The second CSI-RS resource may be a CSI-RS resource in the NZP CSI-RS resource set for TRS. The third CSI-RS resource may be a CSI-RS resource in the NZP CSI-RS resource set for TRS when Type D is not applicable. The CSI-RS resource set for repetition may be a CSI-RS resource set with the upper layer parameter repetition.

For the fourth CSI-RS resource, the TCI state may indicate QCL for the second CSI-RS resource and type A. For the fourth CSI-RS resource, the TCI state may indicate QCL for the SS/PBCH block and type C. The fourth CSI-RS resource may be a CSI-RS resource in the NZP CSI-RS resource set for repetition.

If the unified TCI state is not configured, for DMRS of PDCCH, the TCI state may indicate QCL for the CSI-RS resource and type A. The CSI-RS resource may be a CSI-RS resource in the NZP CSI-RS resource set.

When SFN scheme A is configured for the PDCCH and CORESET is activated in two TCI states, the DMRS ports of the PDCCH in CORESET may be DL RS (downlink reference signal) and QCL in the two TCI states. When SFN scheme B is configured for the PDCCH and CORESET is activated in two TCI states, the DMRS ports of the PDCCH in CORESET may be DL RS and QCL in the two TCI states, and the second TCI state may not include the QCL parameters {Doppler shift, Doppler spread}. Configuring SFN scheme A for the PDCCH may mean configuring sfnSchemePdcch with 'sfnSchemeA' set. Configuring SFN scheme B for the PDCCH may mean configuring sfnSchemePdcch with 'sfnSchemeB' set.

CJT (Coherent Joint Transmission) may be configured for the PDSCH. Configuring CJT may mean configuring the upper layer parameter cjtSchemePDSCH. Configuring CJT scheme A may mean configuring the upper layer parameter cjtSchemeA. Configuring CJT scheme B may mean configuring the upper layer parameter cjtSchemeB. When CJT scheme A is configured for the PDSCH, the DMRS port of the PDSCH may be QCL for reference signals of two indicated TCI states and QCL type A excluding the QCL parameters {Doppler shift, Doppler spread}.

If the unified TCI state is not configured, for DMRS of PDSCH, the TCI state may indicate QCL for the CSI-RS resource and type A. The CSI-RS resource may be a CSI-RS resource in the NZP (Non-zero power) CSI-RS resource set.

When a unified TCI state is configured, for DMRS of PDCCH, the TCI state may indicate QCL for CSI-RS resources and Type A. When a unified TCI state is configured, for DMRS of PDSCH, the TCI state may indicate QCL for CSI-RS resources and Type A.

If SFN scheme A is configured for the PDSCH and two TCI states are indicated, the DMRS port of the PDSCH may be in the two TCI states DL-RS and QCL. If SFN scheme B is configured for the PDSCH and two TCI states are indicated, the DMRS port of the PDSCH may be in the two TCI states DL-RS and QCL. If SFN scheme B is configured for the PDSCH and two TCI states are indicated, the DMRS port of the PDSCH may be in the two TCI states DL-RS and QCL, and the second TCI state may not include the QCL parameters {Doppler shift, Doppler spread}. The two TCI states may be indicated by one code point of the DCI field 'Transmission Configuration Indication' in the DCI scheduling the PDSCH. Configuring SFN scheme A for the PDSCH may also mean configuring sfnSchemePdsch with 'sfnSchemeA' set. Configuring SFN scheme B for PDSCH may mean configuring sfnSchemePdsch to have 'sfnSchemeB' set.

When a unified TCI state is configured, and when multi-DCI mode is configured, and when one indicated TCI state is indicated by a TCI field in DCI format 1_1/1_2 associated with one CORESET pool index value (DCI field 'Transmission Configuration Indication'), one indicated TCI state may correspond to one CORESET pool index value. Configuring the unified TCI state may mean configuring dl-OrJointTCI-StateList or TCI-UL-State. Configuring multi-DCI mode may mean configuring the upper layer parameter PDCCH-Config, which includes two different CORESET pool index values. The CORESET pool index may be configured in the upper layer parameter ControlResourceSet.

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

If the unified TCI state is configured, and multi-DCI mode is configured, and the terminal capability of the default beam is not reported, and the first time offset is smaller than a threshold, the "indicated TCI state" corresponding to CORESET pool index 0 may be applied to PDSCH reception. If the unified TCI state is configured, and multi-DCI mode is configured, and the terminal capability of the default beam is not reported, the second time offset may not be expected to be smaller than a threshold. The first time offset may be the offset between reception of the DCI format in the CORESET associated with CORESET pool index 0 and PDSCH reception. The second time offset may be the offset between reception of the DCI format in the CORESET associated with CORESET pool index 1 and PDSCH reception.

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

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

When a unified TCI state is set, and the terminal device 1 has two indicated TCI-States, and when a certain condition is met, and the TCI indication field indicates "00", a first indicated DL/Joint TCI state may be applied to the PDSCH. When a unified TCI state is set, and the terminal device 1 has two indicated TCI-States, and when a certain condition is met, and the TCI indication field indicates "01", a second indicated DL/Joint TCI state may be applied to the PDSCH. When a unified TCI state is set, and the terminal device 1 has two indicated TCI-States, and when a certain condition is met, and the TCI indication field indicates "10", two indicated DL/Joint TCI states may be applied to the PDSCH. If the unified TCI state is set, and if the terminal device 1 has two indicated TCI-States, and if certain conditions are met, and if the TCI indication field is not set, two DL/Joint TCI states may be applied to the PDSCH. The PDSCH may be scheduled by DCI format 1_1/1_2. The TCI indication field may be a DCI field in DCI format 1_1/1_2. Whether the TCI indication field is present in DCI format 1_1/1_2 may be determined by the upper layer parameter tciSelection-PresentInDCI.

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

UL-TCIState may be the upper layer parameter TCI-UL-State. UL-TCIState may be set by the upper layer parameter TCI-UL-State. The upper layer parameter TCI-UL-State may associate one or two downlink reference signals with one corresponding QCL type.

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

The time-frequency resources used to report CSI may be controlled by the base station device 3. CSI may consist 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-Noise Ratio), Capability Index, and TDCP (Time-Domain Channel Properties). CQI, PMI, CRI, SSBRI, LI, RI, L1-RSRP, L1-SINR, Capability Index, and TDCP may be referred to as CSI parameters.

The terminal device 1 may be configured with N CSI report configurations. The CSI report configurations may be upper layer parameters CSI-ReportConfig.

The terminal device 1 may be configured with M CSI resource configurations. The CSI resource configurations may be higher layer parameters CSI-ResourceConfig.

The terminal device 1 may be configured with one or two lists of trigger states (Trigger state(s)). The list of trigger states may be one or both of the upper layer parameter CSI-AperiodicTriggerStateList and the upper layer parameter CSI-SemiPersistentOnPUSCH-TriggerStateList. For example, the list of trigger states for aperiodic CSI may be the upper layer parameter CSI-AperiodicTriggerStateList. For example, the list of trigger states for semi-persistent CSI may be the upper layer parameter CSI-SemiPersistentOnPUSCH-TriggerStateList. The list of trigger states may include one or more trigger states.

Each trigger state may include a list of CSI reporting configurations. The list of CSI reporting configurations may indicate one or more resource set IDs. Each trigger state in the list of trigger states for aperiodic CSI may include a list of CSI reporting configurations. Each trigger state in the list of trigger states for semi-persistent CSI may include one CSI reporting configuration.

Each CSI reporting configuration (Reporting Setting CSI-ReportConfig) may be associated with one downlink BWP. One downlink BWP may be indicated by a BWP ID (higher layer parameter BWP-Id). One downlink BWP may be given in a CSI resource configuration. For example, one downlink BWP may be given in a CSI resource configuration for channel measurement.

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

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

The time domain operation may be indicated by the higher layer parameter reportConfigType. The time domain operation may be set to 'aperiodic', 'semiPersistentOnPUCCH', 'semiPersistentOnPUSCH', or 'periodic'. If the time domain operation is set to 'aperiodic', the CSI reporting configuration may be the CSI reporting configuration for aperiodic CSI. If the time domain operation is set to 'semiPersistentOnPUCCH' or 'semiPersistentOnPUSCH', the CSI reporting configuration may be the CSI reporting configuration for semi-persistent CSI. If the time domain operation is set to 'periodic', the CSI reporting configuration may be the CSI reporting configuration for periodic CSI.

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

Each CSI report configuration may include a report quantity (reportQuantity) configuration. The report quantity configuration may indicate a CSI-related quantity, an L1-RSRP-related quantity, an L1-SINR-related quantity, a CapabilityIndex-related quantity, or a TDCP-related quantity.

The frequency granularity may be indicated by the higher layer parameter reportFreqConfiguration. PMI and CQI reports may correspond to wideband or sub-band. For example, the frequency granularity of each of the PMI and CQI may be wideband or sub-band.

The measurement limit setting may be a time limit. The time limit may be set for one or both of the channel measurement and the interference measurement.

The codebook configuration may include Type 1, Type 2, Extended Type 2-CSI, Super Extended Type 2-CSI, Super Extended Type 2-Port Selection, Super Extended Type 2-CJT, Super Extended Type 2-Port Selection CJT, Extended Type 2-Predicted PMI, or Super Extended Type 2-Port Selection-Predicted PMI. The codebook configuration may include codebook subset restriction. The codebook configuration may include group-based reporting configuration.

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

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

The time domain behavior of the CSI-RS resources in one CSI resource configuration may be indicated by a higher layer parameter (resourceType). The time domain behavior may be set to aperiodic, periodic, or semi-persistent. In a CSI resource configuration for periodic CSI and semi-persistent CSI, the CSI resource configuration may include one CSI-RS resource set. In a CSI resource configuration for periodic CSI and semi-persistent CSI, if group-based reporting is configured, the CSI resource configuration may include two or fewer CSI-RS resource sets.

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

If multiple CSI resource configurations contain the same NZP CSI-RS resource (or the same NZP CSI-RS resource ID), the same time domain behavior may be configured for multiple CSI resource configurations.If multiple CSI resource configurations contain the same CSI-IM resource (or the same CSI-IM resource ID), the same time domain behavior may be configured for multiple CSI resource configurations.All CSI resource configurations linked to one CSI reporting configuration may have the same time domain behavior.

CSI-IM resources for interference measurement may be configured for one or more CSI resource configurations. NZP CSI-RS resources for interference measurement may be configured for one or more CSI resource configurations. NZP CSI-RS resources for channel measurement may be configured for one or more CSI resource configurations.

The NZP CSI-RS resource for channel measurement and the CSI-IM resource for interference measurement (or the NZP CSI-RS resource) may be QCL for Type D. The NZP CSI-RS resource for channel measurement and the CSI-IM resource for interference measurement (or the NZP CSI-RS resource) may be configured for one CSI report (CSI report configuration).

For TDCP measurement, one periodic CSI reporting configuration (CSI reporting configuration for periodic CSI) may be configured. This CSI reporting configuration may be a configuration for channel measurement in CSI-RS for tracking. TDCP measurement may be a measurement when the report quantity setting (reportQuantity) in the CSI reporting configuration includes TDCP.

When one CSI resource configuration is configured for L1-SINR measurement, the one CSI resource configuration may be a configuration for channel measurement and interference measurement. The channel measurement and interference measurement may be measurements in the NZP CSI-RS for L1-SINR calculation. The one CSI resource configuration may be given by resourcesForChannelMeasurement. The L1-SINR measurement may be a measurement when the report quantity setting (reportQuantity) in the CSI report configuration includes L1-SINR.

When two CSI resource configurations are configured for L1-SINR measurement, the first CSI resource configuration may be a configuration for channel measurement, and the second CSI resource configuration may be a configuration for interference measurement. The channel measurement may be a measurement in SSB or NZP CSI-RS. The interference measurement may be a measurement in CSI-IM or 1-port NZP CSI-RS. The first CSI resource configuration may be given by resourcesForChannelMeasurement. The second CSI resource configuration may be given by csi-IM-ResourcesForInterference or nzp-CSI-RS-ResourcesForInterference.

The terminal device 1 may calculate CSI parameters. The CSI parameters may be some or all of the LI, CQI, PMI, RI, and CRI. The terminal device 1 may calculate the RI based on the CRI. The terminal device 1 may calculate the PMI based on the RI and CRI. The terminal device 1 may calculate the CQI based on the PMI, RI, and CRI. The terminal device 1 may calculate the LI based on the CQI, PMI, RI, and CRI.

CSI reporting configuration may be aperiodic, periodic, or semi-persistent. CSI-RS resources may be periodic, semi-persistent, or aperiodic. A CSI report may be triggered for each CSI resource configuration. The combination of CSI reporting configuration and CSI resource configuration may be determined by time-domain operations. Periodic CSI-RS may be configured by higher layers. Semi-persistent CSI-RS may be activated and deactivated. Aperiodic CSI-RS may be configured, activated, and triggered.

Periodic CSI-RS may be combined with any of periodic, semi-persistent, and aperiodic CSI reporting configurations. Semi-persistent CSI-RS may be combined with any of semi-persistent and aperiodic CSI reporting configurations. Aperiodic CSI-RS may be combined with any of aperiodic CSI reporting configurations. For semi-persistent CSI reporting, in the case of reporting in the PUCCH, the terminal device 1 may receive an activation command. For semi-persistent CSI reporting, in the case of reporting in the PUSCH, the terminal device may receive triggering (trigger state) in the DCI. Aperiodic CSI reporting may be triggered by the DCI. Aperiodic CSI reporting may be triggered by the MAC CE (e.g., subselection indication).

The terminal device 1 may determine one CRI. The one CRI may be determined from a set of CRI values. The terminal device 1 may report the number in each CRI report. If a CSI-RS resource set for repetition is configured and the CSI-RS resource set is for channel measurement, the CRI may not be reported. If the codebook setting (codebookType) is set to any of Type 2 (typeII, typeII-PortSelection), Extended Type 2-CSI (typeII-r16), Extended Type 2-Port Selection (typeII-r16), Super Extended Type 2-CSI (typeII-r17), Super Extended Type 2-Port Selection (typeII-PortSelection-r17), Super Extended Type 2-CJT (typeII-CJT-r18), Super Extended Type 2-Port Selection CJT (typeII-CJT-PortSelection-r18), Extended Type 2-Predicted PMI (typeII-Doppler-r18), and Super Extended Type 2-Port Selection-Predicted PMI (typeII-Doppler-PortSelection-r18), CSI need not be reported.

For periodic or semi-persistent CSI reporting in the PUCCH, the periodicity T _CSI and the slot offset T _offset may be configured by higher layer parameters (e.g., reportSlotConfig). The terminal device 1 may transmit a CSI report. The terminal device 1 may transmit a CSI report in one slot in one radio frame. One radio frame may correspond to a system frame number (SFN) n _f . One slot may correspond to a slot index n ^μ _s,f . One radio frame and one slot may be determined based on mod(N ^frame,μ _slot *n _f + n ^μ _s,f -T _offset , T _CSI ) being 0. μ may be a subcarrier spacing setting of an uplink BWP in which a CSI report is transmitted.

For semi-persistent CSI reporting in the PUSCH, the period T _CSI may be configured by a higher layer parameter (e.g., reportSlotConfig). The terminal device 1 may transmit a CSI report in one slot in one radio frame. One radio frame and one slot may be determined based on mod(N ^frame,μ _slot *(n _f - n ^start _f )+ n ^μ _s,f - n ^start _s,f , T _CSI ) being 0. The SFN n ^start _f and slot number n ^start _s,f may correspond to the first semi-persistent PUSCH transmission. The first semi-persistent PUSCH transmission may follow the activated DCI.

For semi-persistent or aperiodic CSI reporting on PUSCH, one or more slot offsets may be configured by higher layer parameters. If CSI reporting is triggered/activated by DCI format 0_2, the higher layer parameter may be reportSlotOffsetListDCI-0-2. If CSI reporting is triggered/activated by DCI format 0_1, the higher layer parameter may be reportSlotOffsetListDCI-0-1. One slot offset may be selected in the triggering/activating DCI.

In a CSI report, one of two subband sizes may be set. A subband may be defined by N ^SB _PRBs of consecutive PRBs. If the number of PRBs in one BWP is between 24 and 72, N ^SB _PRBs may be 4 or 8. If the number of PRBs in one BWP is between 73 and 144, N ^SB _PRBs may be 8 or 16. If the number of PRBs in one BWP is between 145 and 275, N ^SB _PRBs may be 16 or 32.

Higher layer parameters (e.g., reportFreqConfiguration) may indicate the frequency granularity of the CSI report. One CSI reporting configuration may define the band of the CSI report as a subset of the subbands of the BWP. Higher layer parameters may indicate the subset of subbands in one BWP. The subbands may be contiguous or non-contiguous. One BWP may be the BWP in which CSI is reported. It may not be expected that a subband be configured with a frequency density lower than the frequency density of one CSI-RS resource. One CSI-RS resource may have a frequency density in one subband. One CSI-RS may be linked to one CSI reporting configuration. The frequency density may be the density of each CSI-RS port (CSI port, antenna port) per PRB.

When CSI-IM resources are linked to a CSI reporting configuration, it is not expected that one sub-band will be configured. All PRBs in one sub-band may not have a CSI-IM resource element (RE).

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

The frequency granularity may be wideband PMI or subband PMI reporting. When wideband PMI reporting is configured, one wideband PMI may be reported for the entire CSI reporting band. When subband PMI reporting is configured, one single wideband indication (i ₁ ) may be reported for the entire CSI reporting band, and one subband indication (i ₂ ) may be reported for each subband in the CSI reporting band.

If a certain condition is met, the frequency granularity may be full band. One condition may be that full band PMI reporting is set, full band CQI reporting is set, and the report quantity setting (reportQuantity) is set to CRI, RI, PMI, and CQI ('cri-RI-PMI-CQI'). One condition may be that full band PMI reporting is set, full band CQI reporting is set, and the report quantity setting (reportQuantity) is set to CRI, LI, PMI, and CQI ('cri-LI-PMI-CQI'). One condition may be that the report quantity setting (reportQuantity) is set to CRI, RI, and _i1 ('cri-RI-i1'). If a certain condition is not met, the frequency granularity may be subband.

If one CSI reporting configuration is configured for one BWP with 24 or fewer PRBs, it may be expected that one CSI reporting configuration has full-band frequency granularity.

One or N sub-bands may be configured. The size of the first sub-band may be limited based on the starting PRB position N ^start _BWP,i of the BWP. The size of the Nth sub-band may be limited based on the starting PRB position of the BWP and the BWP size.

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

DCI formats 0_1/0_2/0_3 may trigger a CSI report. The terminal device 1 may not expect multiple CSI reports associated with the same CSI report configuration to be triggered.

For aperiodic CSI, each trigger state may be associated with one or more CSI reporting configurations. Each trigger state may be configured by higher layer parameters (e.g., CSI-AperiodicTriggerState). Each CSI report may be linked to one or more CSI resource configurations. Each CSI reporting configuration may be linked to periodic, semi-persistent, or aperiodic CSI resource configurations. Group-based reporting may not be configured for each CSI reporting configuration.

If one CSI resource configuration is configured, it may correspond to channel measurement for L1-RSRP or channel/interference measurement for L1-SINR calculation. The one CSI resource configuration may be given by resourcesForChannelMeasurement.

When two CSI resource configurations are configured, the first CSI resource configuration may be for channel measurement, and the second CSI resource configuration may be for interference measurement performed in CSI-IM or NZP CSI-RS. The first CSI resource configuration may be given by resourcesForChannelMeasurement. The second CSI resource configuration may be given by csi-IM-ResourcesForInterference or nzp-CSI-RS-ResourcesForInterference.

Three CSI resource configurations may be configured. The first CSI resource configuration may be for channel measurement. The second CSI resource configuration may be for interference measurement using CSI-IM. The third CSI resource configuration may be for interference measurement using NZP CSI-RS. The first CSI resource configuration may be given by resourcesForChannelMeasurement. The second CSI resource configuration may be given by csi-IM-ResourcesForInterference. The third CSI resource configuration may be given by nzp-CSI-RS-ResourcesForInterference. resourcesForChannelMeasurement, csi-IM-ResourcesForInterference, and nzp-CSI-RS-ResourcesForInterference may be configured in one CSI report configuration.

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

For aperiodic CSI (CSI reporting) and for aperiodic CSI resource configurations, each trigger condition may be associated with one or more CSI reporting configurations. For each CSI reporting configuration, group-based reporting may be configured. Each CSI reporting configuration may be associated with a first CSI-RS resource set and a second CSI-RS resource set for L1-RSRP measurements.

For semi-persistent or periodic CSI (CSI reporting), each CSI report configuration may be linked to a periodic or semi-persistent CSI resource configuration. If one CSI resource configuration is configured, it may be for channel measurements for L1-RSRP or for channel/interference measurements for L1-SINR. If two CSI resource configurations are configured, the first CSI resource configuration may be for channel measurements and the second CSI resource configuration may be for interference measurements performed in CSI-IM. For L1-SINR calculation, the second CSI resource configuration may be for interference measurements performed in CSI-IM or NZP CSI-RS.

If the codebook configuration is set to type 2, the number of CSI-RS resources in the CSI-RS resource set for channel measurement in the CSI report configuration may be 1.

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

For measurements other than L1-SINR measurements (e.g., CSI measurements), each NZP CSI-RS port configured for interference measurement may correspond to an interference transmission layer. For measurements other than L1-SINR measurements (e.g., CSI measurements), all interference transmission layers at NZP CSI-RS ports may take EPRE into account. For L1-SINR measurements, dedicated interference measurement resources may be configured. The total received power at the dedicated resources may correspond to the interference-to-noise ratio.

In one CSI reporting configuration, the report quantity setting (reportQuantity) may be set to none, cri-RI-PMI-CQI, cri-RI-i1, cri-RI-i1-CQI, cri-RI-CQI, cri-RSRP, cri-SINR, ssb-Index-RSRP, ssb-Index-SINR, cri-RI-LI-PMI-CQI, cri-RSRP-Index, ssb-Index-RSRP-Index, cri-SINR-Index, ssb-Index-SINR-Index, or tdcp.

If the reporting amount setting is set to none, terminal device 1 does not need to report CSI.

When cri-RI-PMI-CQI or cri-RI-LI-PMI-CQI is set as the reporting amount setting, the terminal device 1 may report a first PMI. The first PMI may be a precoder matrix for each subband. The first PMI may be a precoder matrix for the entire CSI reporting band.

When cri-RI-i1 is set in the reporting amount setting, the terminal device 1 may report a second PMI. The second PMI may be configured with a single all-band indication _i1 . Type 1 may be set in the codebook setting in the CSI reporting setting. The frequency granularity for the PMI in the CSI reporting setting may be all-band.

When the reporting amount setting is set to cri-RI-i1-CQI, the terminal device 1 may report a third PMI. The third PMI may be configured as a single full-band indication. The CQI may be calculated based on the third PMI. The terminal device 1 may report the CQI.

If cri-RI-CQI is set in the reporting amount setting, the terminal device 1 may report RI. The terminal device 1 may also calculate CQI for one rank.

If cri-RSRP, ssb-Index-RSRP, cri-RSRP-Index, or ssb-Index-RSRP-Index is set in the reporting quantity configuration and group-based reporting is not configured, the terminal device 1 may report N different CRIs or SSBRIs for each CSI reporting configuration. Furthermore, the terminal device 1 may not be required to update measurements. N may be determined by higher layer parameters (e.g., nrofReportedRS).

If the reporting quantity setting is set to cri-RSRP, ssb-Index-RSRP, cri-RSRP-Index, or ssb-Index-RSRP-Index, and group-based reporting is configured, the terminal device 1 may report two different CRIs or SSBRIs for each CSI reporting setting. Furthermore, the terminal device 1 may be requested to update measurements for more than 64 CSI-RS/SSB resources. The terminal device 1 may receive CSI-RS/SSB resources simultaneously.

If cri-SINR, ssb-Index-SINR, cri-SINR-Index, or ssb-Index-SINR-Index is set as the reporting quantity setting, and group-based reporting is not configured, the terminal device 1 may report N different CRIs or SSBRIs for each CSI reporting setting.

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

If tdcp is set in the reporting quantity setting, terminal device 1 may report the amplitude and phase of the TDCP measurement.

When 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 is set as the reporting amount setting, and when K CSI-RS resources are set in the CSI-RS resource set for channel measurement, the terminal device 1 may calculate CSI parameters other than the CRI based on the CRI. One CRI may correspond to one CSI-RS. For example, the (k+1)th entry of the NZPCSI-RS resource in the NZP CSI-RS resource set for channel measurement may correspond to the CRI value k. The (k+1)th entry of the CSI-IM resource in the CSI-IM resource set for interference measurement may correspond to the CRI value k. The k+1th entry of the NZP CSI-RS resource in the NZP CSI-RS resource set for interference measurement may correspond to CRI value k. K may be greater than 1. If K is 2, each CSI-RS resource may have a maximum of 16 CSI-RS ports (CSI ports, antenna ports). If K is greater than or equal to 3 and less than or equal to 8, each CSI-RS resource may have a maximum of 8 CSI-RS ports. If the reporting amount setting is set to cri-RI-PMI-CQI, the codebook setting may not be set to type 2.

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

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

If the reporting quantity configuration is set to cri-RSRP, cri-SINR, none, cri-RSRP-Index, or cri-SINR-Index, and one CSI reporting configuration links one aperiodic CSI resource configuration, it is not expected that more than 16 CSI-RS resources will be configured in one CSI-RS resource set in one CSI resource configuration.

The L1-RSRP calculation may configure CSI-RS resources, SS/PBCH block resources, or both CSI-RS and SS/PBCH block resources. The L1-RSRP calculation may configure up to 16 CSI-RS resource sets, and up to 64 CSI-RS resources in each CSI-RS resource set.

In L1-RSRP calculation, if one CRI or SSBRI is reported for each CSI reporting configuration (e.g., if nrofReportedRS is 1), the reported L1-RSRP value may be defined in 7 bits. The L1-RSRP value range may be from -140 dBm to -44 dBm. The L1-RSRP value may be given in 1 dB intervals.

In L1-RSRP calculation, if multiple CRIs or SSBRIs are reported for each CSI reporting configuration (e.g., if nrofReportedRS is 2 or greater), the first value of L1-RSRP to be reported may be defined by 7 bits, and the second value of L1-RSRP to be reported may be defined by 4 bits. The range of the first value may be -140 dBm to -44 dBm. The first value may be given in 1 dB intervals. The second value may be calculated as the difference between the first values. The second value may be given in 2 dB intervals.

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

The terminal device 1 may calculate the L1-RSRP based on the NZP CSI-RS or SS/PBCH block. For example, if a time limit is not set, the terminal device 1 may perform channel measurements based on the SS/PBCH block or NZP CSI-RS for L1-RSRP calculation. For example, if a time limit is set, the terminal device 1 may perform channel measurements based on the latest opportunity for the SS/PBCH block or NZP CSI-RS for L1-RSRP calculation.

For L1-SINR calculation, one or both of the NZP CSI-RS resource and the SS/PBCH block resource may be configured for channel measurement. For L1-SINR calculation, the NZP CSI-RS resource or the CSI-IM resource may be configured for interference measurement.

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

In L1-SINR calculation, if one CRI or SSBRI is reported for each CSI reporting configuration (e.g., if nrofReportedRS is 1), the reported L1-SINR value may be defined by 7 bits. The L1-SINR value may range from -23 to 40 dB. The L1-SINR value may be given in 0.5 dB intervals.

In L1-SINR calculation, if multiple CRIs or SSBRIs are reported for each CSI reporting configuration (e.g., if nrofReportedRS is 2 or greater), the first value of the reported L1-SINR may be defined with 7 bits, and the second value of the reported L1-SINR may be defined with 4 bits. The range of the first value may be -23 dB to 40 dB. The first value may be given in 0.5 dB intervals. The second value may be calculated as the difference of the first values. The second value may be given in 1 dB intervals.

The aperiodic CSI report may correspond to an aperiodic CSI-RS.
For a CSI-RS resource set associated with an aperiodic, periodic, or semi-persistent CSI resource setting, the trigger state for an aperiodic CSI reporting setting may be configured by a higher layer parameter (e.g., CSI-AperiodicTriggerStateList). The trigger state may be configured for one or both of the CSI resource settings for channel measurement and interference measurement.

In aperiodic CSI reporting configuration, one set of trigger conditions may be configured by higher layers. A trigger condition may be associated with any one downlink BWP.

The terminal device 1 may receive a DCI with a CSI request field. Two or more DCIs with a CSI request field having a non-zero value may not be expected to be received in one slot in one cell.

In multiple aperiodic CSI-RS resource sets with the same trigger offset in the same trigger state, different TCI states may not be expected to be configured for the same aperiodic CSI-RS resource ID.

It may not be expected that more than one request for aperiodic CSI reporting will be received in one slot in one cell.

The trigger condition may be initiated by the CSI request field in the DCI. If all information bits in the CSI request field are set to zero, no CSI may be requested.

If the number of trigger conditions is 2^N _TS −1 or more, the terminal device 1 may receive a subselection indication. The subselection indication may be used to map up to 2^N _TS −1 trigger conditions to code points in the CSI request field, where N _TS may be the number of bits in the CSI request field.

If terminal device 1 transmits a first PUCCH in slot n, the mapping of the CSI request field and the trigger state may be applied after slot n+N. The first PUCCH may be a PUCCH carrying HARQ-ACK information corresponding to a PDSCH carrying a subselection indication.

The CSI request field may indicate one trigger condition. For example, if the number of trigger conditions is less than 2^N _TS −1, the CSI request field may indicate one trigger condition.

A first QCL setting and a first QCL type may be indicated for each aperiodic CSI-RS resource in one CSI-RS resource set associated with each triggering state.

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

When aperiodic CSI reporting and aperiodic CSI-RS are used, one trigger offset (or may be referred to as a CSI-RS offset) may be configured in one CSI-RS resource set (NZP CSI-RS resource set, CMI-IM resource set, or SS/PBCH block resource set). The trigger offset may be configured by a higher layer parameter (e.g., aperiodicTriggeringOffset). The trigger offset may include a number of slots from 0 to N, where N may be based on the subcarrier spacing of the CSI-RS. The trigger offset of the CSI-IM may follow the trigger offset of the NZP CSI-RS for channel measurement.

The terminal device 1 may receive the CSI-RS. The aperiodic CSI-RS may be transmitted in slot n+X. Slot n may be the slot containing the DCI that triggers the CSI-RS. X may be the trigger offset.

The aperiodic CSI-RS may not be transmitted before the first OFDM symbol. The first OFDM symbol may be the symbol carrying DCI that triggers the CSI-RS transmission. If a minimum scheduling offset restriction applies, and if the trigger offset is less than or equal to the minimum scheduling offset restriction, it may not be expected to be triggered by the trigger condition indicated by the CSI request field in the DCI. The CSI-RS transmission may be triggered by the trigger condition indicated by the DCI request field in the DCI.

If interference measurements are performed on aperiodic NZP CSI-RS, the trigger offset of the NZP CSI-RS for interference measurements may be the same as the trigger offset of the NZP CSI-RS for channel measurements.

On one carrier, it may not be expected that multiple CSI reports triggered by different DCIs will be transmitted in the same OFDM symbol.

A scheduling offset may be determined between the last symbol of the PDCCH carrying DCI that triggers the aperiodic CSI-RS resource and the first symbol of the aperiodic CSI-RS resource. If two PDCCH candidates exist, the PDCCH candidate that ends later may be used to determine the scheduling offset. The last symbol of the PDCCH candidate that ends earlier may be the same as or later than the first symbol of the aperiodic CSI-RS resource.

The semi-persistent CSI may correspond to a semi-persistent CSI-RS.
For a semi-persistent CSI report on a PUSCH, a set of trigger states may be configured by a higher layer parameter (e.g., SemiPersistentOnPUSCH-TriggerStateList). A CSI request field in a DCI scrambled by the SP-CSI-RNTI may activate one trigger state. The terminal device 1 may not expect to receive a first DCI that activates the first semi-persistent CSI report. The first semi-persistent CSI report may have the same CSI report configuration ID as the second semi-persistent CSI report. The second semi-persistent CSI report may be activated by the second DCI. The first DCI and the second DCI may be scrambled by the SP-CSI-RNTI. The terminal device 1 may receive the second DCI before the first DCI.

For semi-persistent CSI reporting in the PUCCH, the PUCCH resources used to transmit the CSI report may be configured by a higher layer parameter (reportConfigType). The semi-persistent CSI reporting in the PUCCH may be activated by an activation command. The activation command may select one semi-persistent CSI reporting configuration. The terminal device 1 may receive a PDSCH carrying the activation command. The terminal device 1 may transmit a PUCCH with HARQ-ACK information corresponding to the PDSCH in slot n. The selected semi-persistent CSI reporting configuration may be applied from slot n+N onwards.

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

The terminal device 1 may receive a deactivation command. If semi-persistent CSI resource configuration is configured and the terminal device 1 receives a deactivation command, the suspension of CSI-RS/CSI-IM transmission may be applied from slot n+N. The terminal device 1 may transmit a PUCCH with HARQ-ACK information for the PDSCH conveying the deactivation command in slot n.

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

The terminal device 1 may activate or deactivate the CSI reporting setting indicated by the DCI request field in the DCI.

If CSI resource configuration (e.g., CSI-RS/CSI-IM resource configuration or ZP (Zero power) CSI-RS resource set configuration) is activated and the corresponding downlink BWP is active, CSI resource configuration may be taken into consideration. If CSI resource configuration (e.g., CSI-RS/CSI-IM resource configuration or ZP (Zero power) CSI-RS resource set configuration) is activated and the corresponding downlink BWP is inactive, CSI resource configuration may be suspended.

The terminal device 1 may report the CQI. The terminal device 1 may calculate one CQI index. The modulation scheme, coding, and transport block size of the PDSCH transport block may correspond to one CQI index. The terminal device 1 may receive the PDSCH transport block so as not to exceed a target error probability. The target error probability may be the error probability of the transport block. The target error probability may be 0.1 or 0.00001.

The terminal device 1 may report the PMI. The terminal device 1 may determine the PMI based on the number of antenna ports (number of CSI ports, number of CSI-RS ports) and the number of layers. The number of layers v may be related to the RI. The value of the PMI corresponding to Type ₁ may be composed of some or all of i1 ∈ _i1,1 , _i1,2 , _i1,3 , _i1,4 , and _i2 . The PMI corresponding to Type 1 may be the PMI when typeI-SinglePanel or _{typeI-MultiPanel is set in the codebook setting. The value of the PMI corresponding to Type 2 may be composed of some or all of i1 ∈ i1,1 , i1,2} , _i1,3,1 , _i1,3,2 , _i1,4,1 , _i1,4,2 , and _i2 . The PMI corresponding to type 2 may be the PMI when any of type II, type II-r16, type II-PortSelection-r16, type II-r17, type II-PortSelection-r17, type II-CJT-r18, type II-CJT-PortSelection-r18, type II-Doppler-r18, and type II-Doppler-PortSelection-r18 is set in the codebook setting.

If an extended CSI port is not set, the number of CSI ports may be any of 4, 8, 12, 16, 24, and 32. If an extended CSI port is set, the number of CSI ports may be any of 48, 64, 96, and 128. Not setting an extended CSI port may mean setting the number of CSI ports to any of 4, 8, 12, 16, 24, and 32. Setting an extended CSI port may mean setting the number of CSI ports to any of 48, 64, 96, and 128.

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

The one or more parameters P may include an NZP CSI-RS resource ID. The NZP CSI-RS resource ID may determine the identifier of the CSI-RS resource.

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

The one or more parameters P may include a first higher layer parameter (e.g., resourceMapping) that determines the number of antenna ports, CDM (Code Domain Multiplexing) type, OFDM symbol, and subcarrier of the CSI-RS resource.

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

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

The one or more parameters P may include a fourth upper layer parameter that determines the CDM type. The fourth upper layer parameter may be set in the first upper layer parameter. The fourth upper layer parameter may determine the value and pattern of the CDM.

The one or more parameters P may include a parameter determining the energy per resource element (EPRE) ratio between PDSCH and NZP CSI-RS.

The one or more parameters P may include a parameter that determines the power ratio per RE of the NZP CSI-RS and SS/PBCH blocks.

The one or more parameters P may include a scramble ID. The scramble ID may be 10 bits in length.

The one or more parameters P may include a BWP ID. The BWP ID may be configured in the CSI resource configuration. The BWP ID may determine the BWP in which the CSI-RS is located.

One or more parameters P may include a repetition setting. The repetition setting may be configured in a CSI-RS resource set. In an NZP CSI-RS resource set for repetition (an NZP CSI-RS resource set in which the repetition setting is configured), it may be assumed that the CSI-RS resources in the NZP CSI-RS resource set are transmitted using the same downlink spatial domain transmit filter. The repetition setting may be configured when the reporting amount setting is set to cri-RSRP, cri-SINR, cri-RSRP-Index, cri-SINR-Index, or none.

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

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

The same frequency density and the same number of antenna ports may be configured for all CSI-RS resources for channel measurement in one CSI-RS resource set. The same starting RB (Resource Block) position, the same number of RBs, and the same CDM type may be configured for all CSI-RS resources in one CSI-RS resource set.

The bandwidth and starting CRB (Common resource block) index of the CSI-RS resource may be determined by the starting RB position and the number of RBs. The starting RB position and the number of RBs may be determined by higher layer parameters (e.g., startingRB and nrofRBs). The starting RB position and the number of RBs may be set as an integer multiple of 4 RBs. The reference position for the starting RB position may be CRB0. The bandwidth (number of RBs) of the CSI-RS resource may be 24 RBs or more and the BWP size or more.

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

The one or more parameters Q may include a CSI-IM resource ID. The one or more parameters Q may include a parameter determining subcarrier position k _CSI-IM within one slot of the CSI-IM resource. The one or more parameters Q may include a parameter determining OFDM symbol position l _CSI-IM within one slot of the CSI-IM resource. The one or more parameters Q may include a parameter determining a period and slot offset for periodic/semi-persistent CSI-IM. The one or more parameters Q may include a parameter determining a band for CSI-IM.

A CSI-IM resource may be composed of four REs. For example, in pattern 1, the CSI-IM resource may be composed of REs corresponding to (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). For example, in pattern 2, the CSI-IM resource may be composed of REs corresponding to (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).

The CSI may be calculated based on a CSI reference resource. The CSI reference resource in the frequency domain may be a PRB (Physical Resource Block) corresponding to the band for which the CSI is calculated. The CSI reference resource in the time domain may be one slot. One slot may be N slots before the slot for which the CSI is reported. The N slots may be determined based on the delay time.

The terminal device 1 may calculate and report a CQI (CQI index) based on the CSI reference resource. The terminal device 1 may consider one or more situations to calculate the CQI.

In one or more situations, two OFDM symbols may be occupied by the control signal. In one or more situations, the number of PDSCH and DMRS symbols may be 12. In one or more situations, the subcarrier spacing may be the same as that for PDSCH reception. In one or more situations, the CSI reference resource may use the same CP length and subcarrier spacing as the PDSCH. In one or more situations, no REs may be used for the PBCH, PSS, or SSS. In one or more situations, the Redundancy Version may be 0. In one or more situations, no REs may be allocated for the NZP CSI-RS and ZP CSI-RS. In one or more situations, a configured maximum number of front-loaded DMRS symbols may be used. In one or more situations, a configured number of additional DMRS symbols may be used. In one or more situations, the OFDM symbols for the PDSCH may not include DMRS. One of the one or more situations may be when two PRBs are bundled together.

One of the one or more situations may be that the signal of the ν layer in the PDSCH is multiplied by a precoder corresponding to the PMI. The number of layers may be up to 8.

The terminal device 1 may report CSI using the PUSCH. In response to decoding of the DCI format that triggers the trigger state, the terminal device 1 may report aperiodic CSI via the PUSCH.

The DCI format may schedule two PUSCHs. In this case, aperiodic CSI reporting may be performed in the second PUSCH. The DCI format may schedule three or more PUSCHs. In this case, aperiodic CSI reporting may be performed in the penultimate PUSCH.

Aperiodic CSI reporting in PUSCH may support full-band and sub-band frequency granularity.

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

Aperiodic CSI reports on the PUSCH may be multiplexed with uplink data on the PUSCH. Semi-persistent CSI reports on the PUSCH may not be expected to be multiplexed with uplink data on the PUSCH.

When PMI is reported (or fed back) on the PUSCH, the CSI report may consist of Part 1 and Part 2. Part 1 may be a fixed-size payload that indicates the number of information bits in Part 2. Part 1 may be added or transmitted before Part 2.

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

The terminal device 1 may report CSI using the PUCCH. The CSI report in the PUCCH may be configured by a higher layer. Multiple periodic CSI reports corresponding to multiple CSI report configurations may be configured by a higher layer.

The terminal device 1 may report semi-persistent CSI in the PUCCH. The semi-persistent CSI report may be applied from slot n+N. In slot n, a PUCCH carrying HARQ-ACK information corresponding to a PDSCH carrying an activation command may be transmitted. The activation command may include one or more CSI report settings.

The terminal device 1 may report CSI. The CSI may include some or all of the PMI, RI, LI, CQI, CRI, SSBRI, RSRP, SINR, CapabilityIndex, and TDCP. CSI may be a collective term for PMI, RI, LI, CQI, and CRI.

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

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

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

The TCI (Transmission configuration indication) field may be included in one or both of DCI format 1_1 and DCI format 1_2. For example, if an upper layer parameter is set, the TCI (Transmission configuration indication) field may be included in one or both of DCI format 1_1 and DCI format 1_2. For example, if the upper layer parameter tci-PresentInDCI is set, the TCI (Transmission configuration indication) field may be included in one or both of DCI format 1_1 and DCI format 1_2. One or two TCI states may be indicated by the DCI format. One or more (e.g., two) TCI states may be indicated by the TCI field in the DCI format.

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

The CSI-RS (Channel state information reference signal) may be a ZP (zero power) CSI-RS or an NZP (Non-zero power) CSI-RS.

The CSI-RS sequence may be r(m), which may be determined by a pseudo-random sequence (e.g., a Gold code). The pseudo-random sequence may be initialized based on the OFDM symbol index within a slot, the slot index n ^μ _s,f within a radio frame, and the scrambling ID.

For each CSI-RS, a CSI-RS sequence r(m) may be mapped to resource elements (RE) (k,l) _p,μ . For example, a CSI-RS sequence r(m) may be mapped to resource elements (RE) (k,l) _p,μ as β _CSIRS *w _f (k')*w _t (l')*r(m), where k may be the subcarrier position, l may be the OFDM symbol position, p may be the antenna port (CSI port), and μ may be the subcarrier spacing setting. _{β CSIRS} may be a scaling factor, w _f (k') may be the frequency domain orthogonal cover code (FD-OCC), and w _t (l') may be the time domain orthogonal cover code (TD-OCC).

For ZP CSI-RS, β _CSIRS may be 0. For NZP CSI-RS, β _CSIRS may be greater than 0. β _CSIRS may be determined based on higher layer parameters (e.g., powerControlOffsetSS).

The m in r(m) may be floor(n*α)+k′+floor((k ^bar *ρ)/N ^RB _SC ). * may be multiplication.

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

The subcarrier position k may be determined by the PRB position n, the subcarrier position setting k ^bar , and the frequency domain-orthogonal cover code (FD-OCC) index k′.

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

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

The subcarrier positioning ^kbar may determine the subcarrier position within one slot. The subcarrier positioning ^{kbar may be determined based on the number of antenna ports, frequency density, and CDM type. The subcarrier positioning kbar} may be the subcarrier position within one RB. ^kbar may be ki. ^ki _-1 may be f( _i ). f(i) may be the bit number of the i-th bit set to 1 in the bitmap. The bitmap may be provided by a higher layer parameter (e.g., frequencyDomainAllocation). The size of the bitmap may be determined based at least on the number of antenna ports. f(i) may be repeated every ceil(1/ρ) RBs.

The FD-OCC index k' may be determined by the CDM type. If the CDM type is set to no CDM, k' may be 0. If the CDM type is set to length 2 CDM in the frequency domain (FD), k' may be 0 or 1.

The OFDM symbol position l may be determined by the OFDM symbol position setting l ^bar and a time domain-orthogonal cover code (TD-OCC) index l′.

The OFDM symbol position setting ^lbar may determine the symbol position within one slot. The OFDM symbol position setting ^lbar may be determined based on the number of antenna ports, frequency density, and CDM type. ^lbar may be one or both of _l0 and _l1 . _l0 may be determined by a first higher layer parameter (e.g., firstOFDMSymbolInTimeDomain). _l1 may be determined by a second higher layer parameter (e.g., firstOFDMSymbolInTimeDomain2). _l0 may be an integer value from 0 to 13. _l1 may be an integer value from 2 to 12.

The TD-OCC index l' may be determined by the CDM type. If the CDM type is set to no CDM, l' may be 0. If the CDM type is set to a length-2 CDM in the time domain (TD), l' may be 0 and 1. If the CDM type is set to a length-4 CDM in the time domain, l ^' may be 0, 1, 2, and 3.

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

When the FD-OCC index k' is 0, _wf (k') may be 0. When the FD-OCC index k' is 0 and 1, [ _wf (0) _wf (1)] may be the vectors [+1+1] and [+1-1]. When the TD-OCC index l' is 0, _wt (l') may be 0. When the TD-OCC index l' is 0 and 1, [ _wt (0) _wt (1)] may be the vectors [+1+1] and [+1-1]. When the TD-OCC index l' is 0, 1, 2, and 3, [ _wt (0) _wt (1) _wt (2) _wt (3)] may be the vectors [+1+1+1], [+1-1+1-1], [+1+1-1-1], and [+1-1-1+1]. The sequence index s may be indexed first with FD-OCC and then with TD-OCC. For example, if the CDM type is set to FD-OCC with a length of 2 and TD-OCC with a length of 4, the sequence index s=0 is [w _f (0) w _f (1)]=[+1 +1] and [w _t (0) w _t (1) w _t (2) w _t (3)]=[+1 +1 + 1 +1], the sequence index s=1 is [w _f (0) w _f (1)]=[+1 -1] and [w _t (0)w _t (1) w _t (2) w _t (3)]=[+1 +1 + 1 +1], the sequence index s=2 is [w _f (0) w _f (1)]=[+1+1] and [w _t (0) w t (1) w _t (2) w _{t (} 3)]=[+1 -1 + 1 -1], and the sequence index s=3 is [w _f (0) w _f (1)]=[+1 -1] and [w _t (0) w _t (1) w _t (2) w _t (3)]=[+1 -1 + 1 -1], sequence index s=4 is [w _f (0) w _f (1)]=[+1 +1] and [w _t (0) w _t (1) w _t (2) w _t (3)]=[+1 +1 -1 -1], sequence index s=5 is [w _f (0) w _f (1)]=[+1 -1] and [w _t (0) w _t (1) w _t (2) w _t (3)]=[+1 +1 -1 -1], sequence index s=6 is [w _f (0) w _f (1)]=[+1 +1] and [w _t (0) w _t (1) w _t (2) w _t (3)]=[+1 -1 -1 +1], and sequence index s=7 is [w _f (0) w _f (1)]=[+1 -1] and [w _t (0) w _t (1) w _t (2) w _t (3)] = [+1 -1 -1 +1].

The CDM groups may be indexed first by frequency resource and then by time resource. For example, if the number of antenna ports is 32 and the CDM type is set to FD-OCC of length 2 (fd-CDM2), the CDM group index j may be indexed in the order of time-frequency resources ( _k0 , _l0 ), ( _k1 , _l0 ), ( _k2 , _l0 ), ( _k3 , _l0 ), ( _k0 , _{l0+ 1} ), ( _k1 , _{l0 +} 1), ( _k2 ,l0+ ₁ ), ( _k3 , _l0 + ₁ ), ( _k0 , _l1 ), ( _k1 , _l1 ), ( _k2 , _l1 ), (k3, _l1 ), ( _k0 ,l1+ ₁ ), ( _k1 , _l1 +1), (k2, _l1 +1), and ( _k0 ,l1+1).

Terminal device 1 may not expect to receive CSI-RS and DMRS in the same RE. Antenna ports within one CSI-RS resource may be QCL with respect to Type A. Terminal device 1 may expect antenna ports within one CSI-RS resource to have average gain.

The configuration for the scheduling request may be configured by a higher layer parameter (e.g., SchedulingRequestResourceConfig). The configuration for the scheduling request may determine one PUCCH resource. The one PUCCH resource may correspond to PUCCH format 0 or PUCCH format 1. The configuration for the scheduling request may determine a periodicity T and an offset ΔT for the PUCCH carrying the scheduling request. The periodicity may be expressed in OFDM symbols or slots. The terminal device 1 may determine a transmission opportunity for the scheduling request in the PUCCH. If mod(n _f *N ^frame,μ _slot +n ^μ _s,f -ΔT, T) is 0, the transmission opportunity may be the slot corresponding to slot number n ^μ _s,f . The configuration for the scheduling request may determine a transmission period. The transmission period may be the number of OFDM symbols.

The configured uplink grant for a PUSCH transmission may be configured by higher layer parameters (e.g., configuredGrantConfig). The PUSCH resources (resource allocation) may be configured by higher layer parameters. The higher layer parameters may be associated with one uplink BWP. A PUSCH transmission may correspond to one configured uplink grant. The higher layer parameters may determine the time domain resource allocation.

The terminal device 1 may report (transmit) CSI. As a problem, it is necessary to efficiently determine the resources on which the CSI is reported. Means 1, 2, and 3 may be used to solve the problem. Figure 9 is a diagram showing an example of a CSI report according to one aspect of this embodiment.

The terminal device 1 may receive a downlink reference signal 900. The downlink reference signal 900 may be a CSI-RS or an SS/PBCH block. The CSI-RS may be an NZP CSI-RS. The CSI-RS may be a periodic CSI-RS or a semi-persistent CSI-RS. For example, the time domain operation in the CSI report configuration 960 may be set to 'periodic' or 'semi-persistent'.

The terminal device 1 may transmit CSI910. Transmitting CSI may be transmitting a CSI report, or may be reporting the CSI. The terminal device 1 may transmit an uplink physical channel 920. For example, the terminal device 1 may transmit CSI910 on the uplink physical channel 920. For example, the terminal device 1 may transmit the uplink physical channel 920 with CSI910. For example, the terminal device 1 may transmit CSI910 using the uplink physical channel 920. Transmitting CSI may be transmitting the uplink physical channel with CSI.

The terminal device 1 may transmit the uplink physical channel 921.

CSI 910 may be determined based on the downlink reference signal 900. CSI 910 may be determined based on an index (CRI or SSBRI) of the downlink reference signal 900. For example, CSI 910 may be composed of one or more CSI parameters. For example, CSI 910 may include one or more CSI parameters. The one or more CSI parameters may be determined based on the CRI. The CRI may indicate a CSI-RS, which is the downlink reference signal 900. The one or more CSI parameters may be determined based on the SSBRI. The SSBRI may indicate an SS/PBCH block, which is the downlink reference signal 900.

CSI 910 may be configured with one or both of L1-RSRP and CRI. CSI 910 may be configured with one or both of L1-RSRP and SSBRI. The terminal device 1 may calculate or determine L1-RSRP based on the downlink reference signal 900. The terminal device 1 may perform channel measurement for L1-RSRP based on the downlink reference signal 900. CRI or SSBRI may indicate the downlink reference signal 900. For example, the CSI resource configuration 940 may be for channel measurement for L1-RSRP calculation. For example, the downlink reference signal 900 may be for channel measurement.

CSI 910 may be composed of one or both of L1-SINR and CRI. CSI 910 may be composed of one or both of L1-SINR and SSBRI. The terminal device 1 may calculate or determine L1-SINR based on the downlink reference signal 900. The terminal device 1 may perform one or both of channel measurement and interference measurement for L1-SINR based on the downlink reference signal 900. CRI or SSBRI may indicate the downlink reference signal 900. For example, the CSI resource configuration 940 may be for channel and interference measurement for L1-SINR calculation. For example, the downlink reference signal 900 may be for channel and interference measurement.

CSI 910 may include CRI or SSBRI. The CSI-RS identified by the CRI may be the downlink reference signal 900. The SS/PBCH block identified by the SSBRI may be the downlink reference signal 900. One downlink BWP 1020 may be identified by the CSI resource configuration 940.

Transmission of the uplink physical channel 921 may be configured by upper layer parameters 930. For example, the resources of the uplink physical channel 921 may be configured by upper layer parameters 930. The resources of the uplink physical channel may determine some or all of the transmission position (slot position), transmission period, and transmission cycle. For example, the resources of the uplink physical channel may be transmission opportunities for the uplink physical channel.

The upper layer parameters 930 may be configured for one uplink BWP 1010 in one serving cell 1000. For example, the configuration of one serving cell 1000 may be ServingCellConfig. The configuration of one uplink BWP 1010 may be either BWP-UplinkDedicated or BWP-UplinkCommon. The upper layer parameters 930 may be configured in the configuration of one uplink BWP 1010 in the configuration of one serving cell 1000. The upper layer parameters 930 may be associated with one uplink BWP 1010. The upper layer parameters 930 may be associated with one uplink BWP 1010 in one serving cell 1000.

The uplink physical channel 921 may be a PUCCH. Upper layer parameters 930 may be configured for scheduling requests in the PUCCH. The upper layer parameters 930 may determine PUCCH resources for the scheduling request. The upper layer parameters 930 may be SchedulingRequestResourceConfig.

The uplink physical channel 921 may be a PUSCH. The upper layer parameters 930 may determine an uplink grant to be configured for the PUSCH. The upper layer parameters 930 may be configured for the PUSCH corresponding to the configured uplink grant. The upper layer parameters 930 may be ConfiguredGrantConfig.

The uplink physical channel 921 may be a PRACH. The higher layer parameters 930 may determine transmission opportunities for the PRACH. The higher layer parameters 930 may configure RACH resources.

The terminal device 1 may determine whether the uplink physical channel 921 is a PUSCH, a PUCCH, or a PRACH. For example, if the transmission opportunity for X when the uplink physical channel 921 is X is earlier than the transmission opportunity for Y when the uplink physical channel 921 is Y, the uplink physical channel 921 may be X. For example, if the transmission opportunity for X when the uplink physical channel 921 is X is earlier in the time domain than the transmission opportunity for Y when the uplink physical channel 921 is Y, the uplink physical channel 921 may be X.

The downlink reference signal 900 may correspond to a CSI resource configuration 940. For example, the CSI resource configuration 940 may determine one or more CSI-RS resource sets. At least one of the one or more CSI-RS resource sets may include the downlink reference signal 900. The CSI resource configuration 940 may be associated with one downlink BWP 1020. The CSI resource configuration 940 may be associated with one downlink BWP 1020 in one serving cell 1000. For example, the CSI resource configuration 940 may include the ID of one downlink BWP 1020.

The upper layer parameters 930 may not be linked to the CSI resource configuration 940. The CSI reporting configuration 960 may be linked to the CSI resource configuration 940. Linking a parameter to a CSI resource configuration may mean that the CSI resource configuration is configured in the parameter. Linking a parameter to a CSI resource configuration may mean that the BWP associated with the parameter is the same as the BWP associated with the CSI resource configuration. The upper layer parameters 930 may be associated with the uplink BWP 1010, and the CSI resource configuration 940 may be associated with the downlink BWP 1020.

The CSI reporting configuration 960 may include a time domain operation (e.g., an upper layer parameter reportConfigType) and a reporting quantity configuration (e.g., an upper layer parameter reportQuantity). The time domain operation in the CSI reporting configuration 960 may be set to 'semiPersistentOnPUCCH', 'semiPersistentOnPUSCH', or 'periodic'.

The terminal device 1 may determine whether the CSI910 satisfies the criterion 950. In the means 1, the CSI910 satisfying the criterion 950 may be that the received power value in the CSI910 is equal to or greater than a threshold. The CSI910 not satisfying the criterion 950 may be that the received power value in the CSI910 is below a threshold. The threshold may be determined by the upper layer parameter 931. The upper layer parameter 931 may be set for beam failure recovery or beam failure detection. The received power value may be L1-RSRP, L1-SINR, or propagation loss.

In the second means, CSI910 satisfying criterion 950 may be that the difference between the first received power value and the second received power value is equal to or less than a threshold. CSI910 not satisfying criterion 950 may be that the difference between the first received power value and the second received power value is greater than a threshold. The first received power value may be a received power value in CSI910 (e.g., L1-RSRP, L1-SINR, or path loss). The second received power value may be a received power value (e.g., L1-RSRP, L1-SINR, or path loss) determined based on a downlink reference signal having the same ID as downlink reference signal 900. The second received power value may be the most recent received power value. For example, the second received power value may be determined based on a previous downlink reference signal. The threshold may be determined by upper layer parameters 931.

In means 2, CSI910 satisfying criterion 950 may be that the first received power value is less than or equal to the second received power value. CSI910 not satisfying criterion 950 may be that the first received power value is greater than the second received power value. The first received power value may be a received power value in CSI910 (e.g., L1-RSRP, L1-SINR, or path loss). The second received power value may be a received power value in another CSI. The other CSI may be determined based on another downlink reference signal. The other downlink reference signal may be included in a resource set that includes downlink reference signal 900. The other CSI may be a previous CSI.

In means 3, CSI910 satisfying criterion 950 may mean that the resources determined in CSI reporting configuration 960 are earlier than the resources determined in upper layer parameters 930. CSI910 not satisfying criterion 950 may mean that the resources determined in CSI reporting configuration 960 are later than the resources determined in upper layer parameters 930. In means 3, CSI910 satisfying criterion 950 may mean that the resources determined in CSI reporting configuration 960 are earlier than the resources determined in upper layer parameters 930. CSI910 not satisfying criterion 950 may mean that the resources determined in CSI reporting configuration 960 are later than the resources determined in upper layer parameters 930.

If CSI 910 meets criteria 950, uplink physical channel 920 may be different from uplink physical channel 921. If CSI 910 meets criteria 950, the resources of uplink physical channel 920 may be determined by CSI reporting configuration 960. If CSI 910 meets criteria 950, CSI reporting configuration 960 may determine the period and slot offset for uplink physical channel 920. If CSI 910 meets criteria 950, CSI reporting configuration 960 may determine the transmission opportunity for uplink physical channel 920. If CSI 910 meets criteria 950, CSI reporting configuration 960 may determine the transmission opportunity for CSI 910.

If CSI910 does not satisfy criterion 950, uplink physical channel 920 may be the same as uplink physical channel 921. If CSI910 does not satisfy criterion 950, the resources of uplink physical channel 920 may be determined by upper layer parameters 930. If CSI910 does not satisfy criterion 950, CSI910 may be multiplexed with information conveyed by uplink physical channel 921. If CSI910 does not satisfy criterion 950, upper layer parameters 930 may determine the transmission opportunity for uplink physical channel 920. If CSI910 does not satisfy criterion 950, upper layer parameters 930 may determine the transmission opportunity for CSI910.

If CSI910 satisfies criterion 950, the time domain operation of CSI910 may be determined by CSI reporting configuration 960. The time domain operation in CSI reporting configuration 960 may be either periodic or semi-persistent. If CSI910 does not satisfy criterion 950, the time domain operation of CSI910 may not be determined. If CSI910 does not satisfy criterion 950, the combination of CSI910 and downlink reference signal 900 may not be restricted by the time domain operation.

The resources determined by the CSI report configuration 960 may be later in the time domain than the resources of the uplink physical channel 921. For example, the transmission opportunity determined by the CSI report configuration 960 may be later than the transmission opportunity of the uplink physical channel 921.

If CSI 910 does not satisfy criterion 950 and the resources determined by CSI reporting configuration 960 are earlier than the resources determined by upper layer parameters 930, the resources of uplink physical channel 920 may be determined by CSI reporting configuration 960. If CSI 910 does not satisfy criterion 950 and the resources determined by CSI reporting configuration 960 are later than the resources determined by upper layer parameters 930, uplink physical channel 920 may be the same as uplink physical channel 921. If CSI 910 satisfies criterion 950, the resources of uplink physical channel 920 may be determined by CSI reporting configuration 960.

If CSI910 does not satisfy criterion 950, the content of CSI910 may be determined by the reporting amount setting in CSI reporting configuration 960. If CSI910 satisfies criterion 950, the content of CSI910 may be determined by the reporting amount setting in CSI reporting configuration 960. If the reporting amount setting is set to 'cri-RSRP', CSI910 may be configured with CRI and L1-RSRP. If the reporting amount setting is set to 'ssb-Index-RSRP', CSI910 may be configured with SSBRI and L1-RSRP. If the reporting amount setting is set to 'cri-SINR', CSI910 may be configured with CRI and L1-SINR. If the reporting amount setting is set to 'ssb-Index-SINR', CSI910 may be configured with SSBRI and L1-SINR.

If CSI 910 satisfies criterion 950, the resources of the uplink physical channel 920 may be determined by the CSI report configuration 960. If CSI 910 does not satisfy criterion 950, CSI 910 may not be transmitted on the resources determined by the CSI report configuration 960. If CSI 910 does not satisfy criterion 950, the resources determined by the CSI report configuration 960 may be canceled.

The terminal device 1 may receive a downlink reference signal 901. The terminal device 1 may receive a PDCCH 980 in which a DCI 970 is arranged. The terminal device 1 may transmit a CSI 911. For example, the terminal device 1 may transmit an uplink physical channel 922 accompanied by a CSI 911.

DCI970 may trigger the reporting of CSI911. DCI970 may indicate one trigger state. CSI911 may be aperiodic CSI. CSI911 may be determined based on downlink reference signal 901. The terminal device may receive the triggering (trigger state) in DCI970. In response to decoding DCI970 that triggers one trigger state, the terminal device 1 may transmit CSI911. One trigger state may be associated with a CSI report configuration 961. One trigger state may include a list of CSI report configurations. The list of CSI report configurations may include CSI report configuration 961. One trigger state may be set by the upper layer parameter CSI-AperiodicTriggerState. One trigger state may be associated with one downlink BWP1020. One trigger state may be initiated by a CSI request field in DCI970. The CSI reporting configuration 960 may not be expected to be triggered by a trigger condition indicated by the CSI request field in the DCI. Transmission of the downlink reference signal 901 may be triggered by a trigger condition indicated by the DCI request field in the DCI 970.

The downlink reference signal 901 may correspond to or be associated with a CSI resource configuration 941. The CSI resource configuration 941 may be aperiodic, periodic, or semi-persistent. The CSI resource configuration 941 may be linked to a CSI report configuration 961. The CSI report configuration 961 may determine the first transmission opportunity (or resource). The CSI report configuration 961 may be aperiodic. For example, the time domain operation in the CSI report 961 may be set to 'aperiodic'.

The CSI reporting configuration 960 may determine the second transmission opportunity. The higher layer parameters 930 may determine the third transmission opportunity. The higher layer parameters 930 may determine the third transmission opportunity for the uplink physical channel 921.

The upper layer parameters 932 may be configured for switching CSI transmission opportunities. The upper layer parameters 932 may enable the terminal device 1 to trigger a CSI report. If the upper layer parameters 932 are not configured, the time-frequency resources used to report CSI may be controlled by the base station device 3. If the upper layer parameters 932 are configured, the time-frequency resources or time resources used to report CSI may be determined by the terminal device 1.

The uplink physical channel 922 may be transmitted at the first transmission opportunity. For example, the CSI 911 may be transmitted at the first transmission opportunity. For example, if the upper layer parameter 932 is set, the uplink physical channel 922 may be transmitted at the first transmission opportunity. If the upper layer parameter 932 is not set, the uplink physical channel 922 may be transmitted at the first transmission opportunity.

If the upper layer parameter 932 is not set, the uplink physical channel 920 may be transmitted at the second transmission opportunity. If the upper layer parameter 932 is set, the uplink physical channel 920 may be transmitted at the third transmission opportunity. If the upper layer parameter 932 is not set, the CSI 910 may be transmitted at the second transmission opportunity. If the upper layer parameter 932 is set, the CSI 910 may be transmitted at the third transmission opportunity. If the upper layer parameter 932 is set, the criterion 950 may determine whether the uplink physical channel 920 is transmitted at the second transmission opportunity or the third transmission opportunity.

The following describes various aspects of the device according to one aspect of this embodiment.

The programs running on the base station device 3 and terminal device 1 relating to one aspect of the present invention may be programs (programs that make a computer function) that control a CPU (Central Processing Unit) or the like so as to realize the functions of the above-described embodiment relating to one aspect of the present invention. Information handled by these devices is temporarily stored in RAM (Random Access Memory) during processing, and is then stored in various ROMs such as Flash ROM (Read Only Memory) or HDD (Hard Disk Drive), and is read, modified, and written by the CPU as necessary.

In addition, parts of the terminal device 1 and base station device 3 in the above-described embodiments may be implemented by a computer. In this case, the program for implementing this control function may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be read into a computer system and executed to implement the function.

In this context, "computer system" refers to a computer system built into terminal device 1 or base station device 3, and includes hardware such as the OS and peripheral devices. Furthermore, "computer-readable recording media" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, as well as storage devices such as hard disks built into computer systems.

Furthermore, "computer-readable recording medium" may include something that dynamically stores a program for a short period of time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line, or something that stores a program for a fixed period of time, such as volatile memory within a computer system that serves as a server or client in such cases. Furthermore, the above program may be one that realizes some of the functions described above, or may be one that can realize the functions described above in combination with a program already recorded in the computer system.

Furthermore, the base station device 3 in the above-described embodiment can also be realized as a collection (device group) consisting of multiple devices. Each of the devices constituting the device group may have some or all of the functions or functional blocks of the base station device 3 related to the above-described embodiment. It is sufficient for the device group to have all of the functions or functional blocks of the base station device 3. Furthermore, the terminal device 1 related to the above-described embodiment can also communicate with the base station device as a collection.

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

Furthermore, some or all of the terminal device 1 and base station device 3 in the above-described embodiments may be realized as an LSI, which is typically an integrated circuit, or as a chipset. Each functional block of the terminal device 1 and base station device 3 may be individually formed into a chip, or some or all may be integrated into a chip. Furthermore, the integrated circuit method is not limited to LSI, and may be realized using a dedicated circuit or a general-purpose processor. Furthermore, if an integrated circuit technology that can replace LSI emerges due to advances in semiconductor technology, it may also be possible to use an integrated circuit based on that technology.

Furthermore, while the above-described embodiment describes a terminal device as an example of a communications device, the present invention is not limited to this and can also be applied to terminal devices or communications devices such as stationary or non-mobile electronic devices installed indoors or outdoors, such as AV equipment, kitchen equipment, cleaning/washing equipment, air conditioning equipment, office equipment, vending machines, and other household appliances.

Although the embodiments of the present invention have been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment and includes design modifications within the scope of the invention. Furthermore, various modifications of one aspect of the present invention are possible within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included within the technical scope of the present invention. Furthermore, configurations in which elements described in the above embodiments are substituted for elements that achieve the same effect are also included.

One aspect of the present 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.

1 (1A, 1B, 1C) Terminal device 3 Base station device 10, 30 Radio transceiver unit 10a, 30a Radio transmitter unit 10b, 30b Radio receiver unit 11, 31 Antenna unit 12, 32 RF unit 13, 33 Baseband unit 14, 34 Upper layer processing unit 15, 35 Medium access control layer processing unit 16, 36 Radio resource control layer processing unit 91, 92, 93, 94 Search space set 300 Component carrier 301 Primary cell 302, 303 Secondary cell 700 Set of resource elements for PSS 710, 711, 712, 713 Set of resource elements for PBCH and DMRS for PBCH 720 Set of resource elements for SSS 3000 Points 3001, 3002 Resource grid 3003, 3004 BWP
3011, 3012, 3013, 3014 Offsets 3100, 3200 Common resource block sets 900, 901 Downlink reference signals 910, 911 CSI
920, 921, 922 Uplink physical channels 930, 931, 932 Higher layer parameters 940, 941 CSI resource configuration 950 Criteria 960, 961 CSI reporting configuration 970 DCI
980 PDCCH
1000 Serving cell 1010 Uplink BWP
1020 Downlink BWP

Claims (6)

a receiver for receiving a downlink reference signal;
a transmitter configured to transmit a first uplink physical channel with CSI and a second uplink physical channel;
the CSI is determined based on the downlink reference signal;
resources of the second uplink physical channel are determined by a first higher layer parameter;
the first higher layer parameter is not linked to a CSI resource configuration corresponding to the downlink reference signal;
If the CSI does not satisfy a certain criterion, resources of the first uplink physical channel are determined by the first higher layer parameter;
If the CSI satisfies the certain criterion, the resource of the first uplink physical channel is determined by a CSI report configuration linked to the CSI resource configuration. the first higher layer parameter is associated with one uplink BWP in one serving cell;
the CSI resource configuration is associated with one downlink BWP in the one serving cell;
The terminal device according to claim 1 , wherein the CSI reporting configuration is associated with the one downlink BWP in the one serving cell. The CSI satisfies the certain criterion when a received power value of the CSI is equal to or greater than a threshold,
The terminal device according to claim 1 , wherein the threshold is determined by a second upper layer parameter. The terminal device according to claim 1, wherein the CSI satisfies the certain criterion when the resource determined by the CSI report configuration precedes the resource determined by the first higher layer parameter. a transmitter for transmitting a downlink reference signal;
a receiver configured to receive a first uplink physical channel with CSI and a second uplink physical channel;
the CSI is determined based on the downlink reference signal;
resources of the second uplink physical channel are determined by a first higher layer parameter;
the first higher layer parameter is not linked to a CSI resource configuration corresponding to the downlink reference signal;
If the CSI does not satisfy a certain criterion, resources of the first uplink physical channel are determined by the first higher layer parameter;
If the CSI satisfies the certain criterion, the resource of the first uplink physical channel is determined by a CSI report configuration linked to the CSI resource configuration. A communication method for a terminal device, comprising:
receiving a downlink reference signal;
transmitting a first uplink physical channel with CSI and a second uplink physical channel;
the CSI is determined based on the downlink reference signal;
resources of the second uplink physical channel are determined by a first higher layer parameter;
the first higher layer parameter is not linked to a CSI resource configuration corresponding to the downlink reference signal;
If the CSI does not satisfy a certain criterion, resources of the first uplink physical channel are determined by the first higher layer parameter;
If the CSI satisfies the certain criterion, the resource of the first uplink physical channel is determined by a CSI report configuration linked to the CSI resource configuration.