Terminal device and base station device

Abstract

The present invention comprises a higher-layer processing unit that receives a first higher-layer parameter and a second higher-layer parameter. The present invention comprises a reception unit that receives a PDCCH in which DCI is placed. A first TCI state or a second TCI state is mapped to a TCI code point of the DCI, and when the TCI code point is received, both, or one, of the first TCI state and the second TCI state mapped to the TCI code point are updated. The second higher-layer parameter is configured in one, or both, of the first TCI state and the second TCI state. The first higher-layer parameter is for configuring a unified TCI state. When the first higher-layer parameter is configured, and the first TCI and the second TCI state are retained, and asymmetricTRP is configured, it is expected that the second higher-layer parameter in the first TCI state is not configured and that the second higher-layer parameter in the second TCI state is configured. When the first higher-layer parameter is configured, and the first TCI and the second TCI state are retained, and asymmetricTRP is not configured, it is not expected that the second higher-layer parameter in the first TCI state is configured or that the second higher-layer parameter in the second TCI state is configured.

Description

Terminal device and base station device

[0001] The present invention relates to a terminal device and a base station device. This application claims priority to Japanese Patent Application No. 2024-132129, filed on August 8, 2024, the contents of which are incorporated herein by reference.

[0002] The radio access method and radio network for cellular mobile communications (hereinafter referred to as "Long Term Evolution (LTE)" or "EUTRA: Evolved Universal Terrestrial Radio Access") is being developed by the Third Generation Partnership Project (3GPP). rd This is being studied under the LTE Generation Partnership Project (registered trademark). In LTE, base station devices are also called eNodeBs (evolved NodeBs), and terminal devices are also called UEs (User Equipment). LTE is a cellular communication system in which multiple areas covered by base station devices are arranged in the form of cells. A single base station device may manage multiple serving cells.

[0003] 3GPP is currently studying the next-generation standard (NR: New Radio) to be proposed for IMT (International Mobile Telecommunication)-2020, a standard for next-generation mobile communication systems formulated by the International Telecommunication Union (ITU) (Non-Patent Document 1). NR is required to satisfy requirements for three scenarios: eMBB (enhanced Mobile BroadBand), mMTC (massive Machine Type Communication), and URLLC (Ultra Reliable and Low Latency Communication) within a single technology framework.

[0004] 3GPP is currently studying the extension of services supported by NR (Non-Patent Document 2).

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

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

[0007] (1) A first aspect of the present invention is a terminal device, comprising: an upper layer processing unit that receives a first upper layer parameter and a second upper layer parameter; and a receiving unit that receives a PDCCH on which a DCI is mapped, wherein a first TCI state or a second TCI state is mapped to a TCI codepoint of the DCI; when the TCI codepoint is received, both or one of the first TCI state and the second TCI state mapped to the TCI codepoint is updated; the second upper layer parameter is set in one or both of the first TCI state and the second TCI state; the first upper layer parameter is a parameter for setting a unified TCI state; A terminal device in which, when an upper layer parameter is set, and when the first TCI state and the second TCI state are maintained, and if asymmetricTRP is set, the second upper layer parameter in the first TCI state is expected to be not set, and the second upper layer parameter in the second TCI state is expected to be set; and, when the first upper layer parameter is set, and when the first TCI state and the second TCI state are maintained, and if asymmetricTRP is not set, the second upper layer parameter in the first TCI state and the second upper layer parameter in the second TCI state are not expected to be set.

[0008] (2) A second aspect of the present invention is a base station apparatus, comprising: an upper layer processing unit that transmits first upper layer parameters and second upper layer parameters; and a transmission unit that transmits a PDCCH on which DCI is mapped, wherein a first TCI state or a second TCI state is mapped to a TCI codepoint of the DCI; when the TCI codepoint is received, both or one of the first TCI state and the second TCI state mapped to the TCI codepoint is updated; the second upper layer parameter is set in one or both of the first TCI state and the second TCI state; the first upper layer parameter is a parameter for setting a unified TCI state; When the upper layer parameter is set, and when the first TCI state and the second TCI state are maintained, and asymmetricTRP is set, the second upper layer parameter in the first TCI state is expected to be not set, and the second upper layer parameter in the second TCI state is expected to be set; when the first upper layer parameter is set, and when the first TCI state and the second TCI state are maintained, and asymmetricTRP is not set, the second upper layer parameter in the first TCI state and the second upper layer parameter in the second TCI state are not expected to be set.

[0009] According to one aspect of the present invention, a terminal device can perform communication efficiently, and a base station device can perform communication efficiently.

[0010] 1 is a conceptual diagram of a wireless communication system according to an aspect of the present embodiment. The subcarrier spacing setting μ and the number of OFDM symbols per slot N according to an aspect of the present embodiment are shown. slot symb, and an example showing the relationship between CP (cyclic prefix) configuration. FIG. 1 is a diagram showing an example of a method for configuring a resource grid according to an aspect of this embodiment. FIG. 2 is a diagram showing an example of the configuration of a resource grid 3001 according to an aspect of this embodiment. FIG. 3 is a schematic block diagram showing an example of the configuration of a base station device 3 according to an aspect of this embodiment. FIG. 4 is a schematic block diagram showing an example of the configuration of a terminal device 1 according to an aspect of this embodiment. FIG. 5 is a diagram showing an example of the configuration of an SS / PBCH block according to an aspect of this embodiment. FIG. 6 is a diagram showing an example of a monitoring opportunity for a search space set according to an aspect of this embodiment.

[0011] Hereinafter, an embodiment of the present invention will be described.

[0012] 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, where e is Napier's constant. H^I denotes 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.

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

[0014] The OFDM symbol may be a name including a CP added to the OFDM symbol. In other words, a certain OFDM symbol may be configured to include the certain OFDM symbol and the CP added to the certain OFDM symbol.

[0015] Fig. 1 is a conceptual diagram of a wireless communication system according to one aspect of the present embodiment. In Fig. 1, the wireless communication system includes at least terminal devices 1A to 1C and a 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).

[0016] The base station device 3 may be configured to include one or more transmitting devices (or transmission points, transmitting / receiving devices, or transmitting / receiving points). When the base station device 3 is configured by multiple transmitting devices, the multiple transmitting devices may be located at different positions.

[0017] 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 may also be referred to as a cell.

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

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

[0020] The resource grid is size，μ grid，x N RB sc where the resource grid includes common resource blocks N start，μ grid，x Also, common resource block N start，μ grid，x is also called the reference point of the resource grid.

[0021] The resource grid is subframe，μ symb It contains OFDM symbols.

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

[0023] N size，μ grid，x is the offset setting indicated by a parameter provided by the RRC layer (e.g., the parameter CarrierBandwidth). start，μ grid，x is a band configuration indicated by a parameter provided by the RRC layer (for example, the parameter OffsetToCarrier). The offset configuration and band configuration are configurations used to configure an SCS-specific carrier.

[0024] The subcarrier spacing (SCS: SubCarrier Spacing) Δf for a certain subcarrier spacing setting μ is Δf = 2 μ It may be 15 kHz. Here, the subcarrier spacing setting μ may represent any of 0, 1, 2, 3, or 4.

[0025] FIG. 2 shows a subcarrier spacing setting μ and the number of OFDM symbols per slot N according to one aspect of this embodiment. slot symb 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, N subframe，μ slot In addition, in FIG. 2B, for example, when the subcarrier spacing setting μ is 2 and the CP setting is an extended cyclic prefix (CP), N slot symb = 12, N frame，μ slot = 40, N subframe，μ slot =4.

[0026] Time unit T c may be used to express a length in the time domain. c is T c = 1 / (Δf max ・N f ) Δf max = 480 kHz. f = 4096. The constant κ is κ = Δf max ・N f / (Δf ref N f，ref ) = 64. Δf ref is 15 kHz. f，ref is 2048.

[0027] The transmission of the signal in the downlink and / or the transmission of the signal in the uplink may be of length T f The radio frame (system frame, frame) may be organized into T f =(Δf max N f / 100) T s = 10 ms. A radio frame is composed of 10 subframes. The length of a subframe is T sf =(Δf max N f / 1000) T s = 1 ms. The number of OFDM symbols per subframe is N subframe，μ symb = N slot symb N subframe，μ slot is.

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

[0029] A slot may consist of multiple OFDM symbols, e.g., N consecutive OFDM symbols. slot symbFor example, in the normal CP setting, N OFDM symbols may constitute one slot. slot symb In addition, in the setting of the extended CP, N slot symb =12.

[0030] For a given subcarrier spacing setting μ, the number and index of slots contained in the subframe may be given. For example, slot index n μ s is the number of subframes from 0 to N subframe，μ slot The number and index of slots included in the radio frame may be given for the subcarrier spacing setting μ. μ s，f ranges from 0 to N in the radio frame. frame，μ slot The values ​​may be given in ascending order as integers ranging from -1.

[0031] 3 is a diagram illustrating an example of a method for configuring a resource grid according to one aspect of the present embodiment. The horizontal axis of FIG. 3 represents the frequency domain. In FIG. 3, the subcarrier spacing μ １ and the subcarrier spacing μ ２ 3 shows an example of the configuration of a resource grid of . In this way, one or more subcarrier spacings may be set for a certain component carrier. １ = μ ２ -1, various aspects of the present embodiment １ = μ ２ It is not limited to the condition of -1.

[0032] The component carrier 300 is a band having a predetermined width in the frequency domain.

[0033] A point 3000 is an identifier for identifying a certain subcarrier. The point 3000 is also called point A. A common resource block (CRB) set 3100 is a set of subcarrier intervals μ １ is the set of common resource blocks for

[0034] In the common resource block set 3100, the common resource block including the point 3000 (the black block in the common resource block set 3100 in FIG. 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.

[0035] 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 determined by the subcarrier spacing setting μ １ The resource grid 3001 is represented by the number of common resource blocks for N size，μ grid１，x It contains common resource blocks.

[0036] The offset 3013 is the distance from the reference point of the resource grid 3001 to the reference point (N start，μ BWP，i１ ) is the offset to

[0037] The common resource block set 3200 is a set of subcarrier spacing μ ２ is the set of common resource blocks for

[0038] In the common resource block set 3200, the common resource block including the point 3000 (the black block in the common resource block set 3200 in FIG. 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.

[0039] 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 the offset from the reference point of the common resource block set 3200 to the reference point of the resource grid 3002. ２ The resource grid 3002 is represented by the number of common resource blocks relative to the N size，μ grid２，x It contains common resource blocks.

[0040] The offset 3014 is the distance from the reference point of the resource grid 3002 to the reference point of the BWP 3004 with index i2 (N start，μ BWP，i２ ) is the offset to

[0041] 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 is the subcarrier index k sc The resource grid 3001 is size，μ grid１，x N RB sc contains N subcarriers, subframe，μ symb Within the resource grid, subcarrier index k sc and OFDM symbol index l sym The resource specified by is also called a resource element (RE).

[0042] Resource Block (RB) is N RBsc A resource block is a collective term for a common resource block, a physical resource block (PRB), and a virtual resource block (VRB). RB sc =12.

[0043] A resource block unit is a set of resources corresponding to one OFDM symbol in one resource block, i.e., one resource block unit includes 12 resource elements corresponding to one OFDM symbol in one resource block.

[0044] 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. The common resource block with index 0 for a given subcarrier spacing setting μ contains (or collides with, or coincides with) point 3000. The index n of the common resource block for a given subcarrier spacing setting μ μ CRB is n μ CRB = ceil(k sc / N RB sc ) relationship is satisfied. Here, k sc The subcarrier with .gt.=0 is a subcarrier having the same center frequency as the subcarrier corresponding to point 3000.

[0045] 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 index n of the physical resource block for a given subcarrier spacing setting μ is μ PRB is n μ CRB = n μ PRB +N start，μ BWP，i where N start，μBWP，i denotes the reference point of the BWP with index i.

[0046] A BWP is defined as a subset of common resource blocks contained in the resource grid. start，μ BWP，i Starting with N size，μ BWP，i The BWP configured for a downlink carrier is also referred to as a downlink BWP. The BWP configured for an uplink component carrier is also referred to as an uplink BWP.

[0047] 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, or a symbol may correspond to a resource element.

[0048] When the large-scale properties of a channel through which symbols are transmitted at one antenna port can be estimated from the channel through which symbols are transmitted at another antenna port, the two antenna ports are said to be quasi-co-located (QCL). Here, the large-scale properties may include at least long-range properties of the channel. The large-scale properties may include at least some or all of 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 a receive beam assumed by the receiver for the first antenna port is the same as (or corresponds to) a receive beam assumed by the receiver for the second antenna port. The first antenna port and the second antenna port being QCLs in terms of beam parameters may mean that a transmission beam assumed by the receiving side for the first antenna port and a 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 a channel through which symbols are transmitted at one antenna port can be estimated from the channel through which symbols are transmitted at another antenna port. The two antenna ports being QCLs may mean that the two antenna ports are assumed to be QCLs.

[0049] Carrier aggregation may be performing communication using a plurality of aggregated serving cells. Also, carrier aggregation may be performing communication using a plurality of aggregated component carriers. Also, carrier aggregation may be performing communication using a plurality of aggregated downlink component carriers. Also, carrier aggregation may be performing communication using a plurality of aggregated uplink component carriers.

[0050] 5 is a schematic block diagram showing an example configuration of a base station device 3 according to one aspect of the present 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.

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

[0052] For example, the radio transmitting unit 30a may generate and transmit a PDSCH baseband signal. For example, the radio transmitting unit 30a may generate and transmit a PDCCH baseband signal. For example, the radio transmitting unit 30a may generate and transmit a PBCH baseband signal. For example, the radio transmitting unit 30a may generate and transmit a synchronization signal baseband signal. For example, the radio transmitting unit 30a may generate and transmit a PDSCH DMRS baseband signal. For example, the radio transmitting unit 30a may generate and transmit a PDCCH DMRS baseband signal. For example, the radio transmitting unit 30a may generate and transmit a CSI-RS baseband signal. For example, the radio transmitting unit 30a may generate and transmit a DL PTRS baseband signal. For example, a generating unit in the radio transmitting unit 30a may generate a baseband signal.

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

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

[0055] The medium access control layer processing unit 35 included in the upper layer processing unit 34 performs MAC layer processing.

[0056] The radio resource control layer processing unit 36 ​​included in the upper layer processing unit 34 performs processing of the RRC layer. 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.

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

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

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

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

[0061] 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 baseband digital signals, and converts the baseband digital signals into analog signals. The baseband unit 33 outputs the converted analog signals to the RF unit 32.

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

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

[0064] Each of the serving cells configured for the terminal device 1 may be any of a PCell (Primary cell), a PSCell (Primary SCG cell), and an SCell (Secondary Cell).

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

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

[0067] An SCell may be included in either an MCG or an SCG.

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

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

[0070] Of one or more downlink BWPs configured for a serving cell (or a downlink component carrier), one downlink BWP may be configured as an 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 configured as an active uplink BWP (or one uplink BWP may be activated).

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

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

[0073] A 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. The downlink BWP switch may be controlled by a BWP field included in downlink control information. The downlink BWP switch may also be controlled based on higher layer parameters.

[0074] The uplink BWP switching is used to deactivate one active uplink BWP and activate one of the inactive uplink BWPs other than the one active uplink BWP. The uplink BWP switching may be controlled by a BWP field included in the downlink control information. The uplink BWP switching may also be controlled based on higher layer parameters.

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

[0076] Of one or more uplink BWPs configured for a serving cell, two or more uplink BWPs may not be configured as active uplink BWPs. At any given time, one uplink BWP may be active for a serving cell.

[0077] Fig. 6 is a schematic block diagram showing an example configuration of a terminal device 1 according to one aspect of the present embodiment. As shown in Fig. 6, the terminal device 1 includes at least a radio transmission / reception unit (physical layer processing unit) 10 and one or all of an upper layer processing unit 14. The radio transmission / reception 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.

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

[0079] For example, the radio transmitting unit 10a may generate and transmit a baseband signal of a PRACH. For example, the radio transmitting unit 10a may generate and transmit a baseband signal of a PUCCH. The radio transmitting unit 10a may generate and transmit a baseband signal of a PUSCH. For example, the radio transmitting unit 10a may generate and transmit a baseband signal of a PUCCH DMRS. For example, the radio transmitting unit 10a may generate and transmit a baseband signal of a PUSCH DMRS. For example, the radio transmitting unit 10a may generate and transmit a baseband signal of a UL PTRS. For example, the radio transmitting unit 10a may generate and transmit a baseband signal of an SRS. Generating a baseband signal of an SRS may be generating an SRS sequence.

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

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

[0082] The medium access control layer processing unit 15 included in the upper layer processing unit 14 performs MAC layer processing.

[0083] The radio resource control layer processing unit 16 included in the upper layer processing unit 14 performs processing of the RRC layer. 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 the RRC parameters based on an RRC message received from the base station device 3.

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

[0085] The radio transceiver unit 10 (or the radio receiver unit 10b) performs processes such as demodulation and decoding. The radio transceiver unit 10 (or the 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 the 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.

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

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

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

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

[0090] The physical signals (signals) will be explained below.

[0091] The physical signal is a general term for a downlink physical channel, a downlink physical signal, an uplink physical channel, and an uplink physical channel. The physical channel is a general term for a downlink physical channel and an uplink physical channel. The physical signal is a general term for a downlink physical signal and an uplink physical signal.

[0092] The uplink physical channel may correspond to a set of resource elements that transmit 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 the terminal device 1. The uplink physical channel may be received by the 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)

[0093] 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 the PUCCH in which the uplink control information is mapped. The base station device 3 may receive the PUCCH in which the uplink control information is mapped.

[0094] The uplink control information (uplink control information bits, uplink control information sequence, uplink control information type) includes at least some or all of channel state information (CSI), scheduling request (SR), and hybrid automatic repeat request ACKnowledgement (HARQ-ACK) information.

[0095] The channel state information is also referred to as a channel state information bit or a channel state information sequence. The scheduling request is also referred to as a scheduling request bit or a scheduling request sequence. The HARQ-ACK information is also referred to as a HARQ-ACK information bit or a HARQ-ACK information sequence.

[0096] 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. The NACK may indicate that decoding of the transport block has not been successfully completed. The HARQ-ACK information may include a HARQ-ACK codebook including one or more HARQ-ACK bits.

[0097] 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 via the Uplink-Shared Channel (UL-SCH) of the transport layer.

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

[0099] The HARQ-ACK may indicate an ACK or NACK corresponding to one CBG (Code Block Group) included in the transport block.

[0100] 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 the initial transmission are requested by the terminal device 1. A positive SR may indicate that a scheduling request is triggered by a higher layer. A positive SR may be transmitted when a scheduling request is indicated by a higher 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 the initial transmission are not requested by the terminal device 1. A negative SR may indicate that a scheduling request is not triggered by a higher layer. A negative SR may be transmitted when a scheduling request is not indicated by a higher layer.

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

[0102] The channel state information is an indicator related to the reception state of at least a 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 a physical signal used for channel measurement. The channel measurement may include interference measurement.

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

[0104] The PUSCH may be used to transmit one or both of a transport block and uplink control information. The transport block may be allocated to the PUSCH. The transport block delivered by the UL-SCH may be allocated to the PUSCH. The 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.

[0105] The PRACH may be transmitted to transmit a random access preamble. The terminal device 1 may transmit the PRACH. The base station device 3 may receive the PRACH. The PRACH sequence x u，v (n) x u，v (n) = x u (mod(n+C v , L RA ) where x u is a ZC (Zadoff-Chu) series. u x u =exp(-jπui(i+1) / L RA ) where j is the imaginary unit. Also, π is the ratio of the circumference of a circle to its circumference. Also, C v corresponds to the cyclic shift of the PRACH sequence. RA corresponds to the length of the PRACH sequence. RAis 839 or 139. Also, i ranges from 0 to L RA is an integer in the range of -1, and u is the sequence index for the PRACH sequence.

[0106] For each PRACH opportunity, 64 random access preambles are defined. The random access preambles are cyclically shifted C v , and the sequence index u for the PRACH sequence. An index may be assigned to each of the 64 identified random access preambles.

[0107] 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 the 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)

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

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

[0110] The transmission of the PUSCH and the transmission of the 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 the PUSCH. Transmitting the PUSCH may be equivalent to transmitting the PUSCH and the DMRS for the PUSCH.

[0111] The propagation path of the PUSCH may be estimated from the DMRS for the PUSCH.

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

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

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

[0115] The downlink physical channel may correspond to a set of resource elements that transmit 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)

[0116] The PBCH may be transmitted to convey one or both of a Master Information Block (MIB) 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 allocated to a Broadcast Control Channel (BCCH), which is a logical channel of the MAC layer. The BCCH is allocated to a 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 one or both of the MIB and physical layer control information are allocated. The base station device 3 may transmit a PBCH in which one or both of the MIB and physical layer control information are allocated.

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

[0118] 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 configured by 4 bits of a 10-bit radio frame indicator. For example, the radio frame indicator may be used to identify at least radio frames with index 0 to index 1023.

[0119] 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 a radio frame in which the PBCH is transmitted. Here, a half radio frame may include five subframes. Alternatively, a half radio frame may include the first five subframes of ten subframes included in a radio frame. Alternatively, a half radio frame may include the last five subframes of ten subframes included in a radio frame.

[0120] 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 configured with three bits of a 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.

[0121] The subcarrier offset bits are used to indicate a subcarrier offset, which 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.

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

[0123] The downlink control information may be transmitted with a DCI format. The DCI format may be interpreted as a 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.

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

[0125] DCI format 0_0 is used at least for scheduling of PUSCHs allocated to a certain cell. DCI format 0_0 includes 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)

[0126] The DCI format identification field may indicate whether the DCI format including the DCI format identification field is an uplink DCI format or a downlink DCI format. That is, the DCI format identification field may be included in both the uplink DCI format and the downlink DCI format. Here, the DCI format identification field included in DCI format 0_0 may indicate 0.

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

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

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

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

[0131] DCI format 0_0 may not include fields used for CSI requests.

[0132] DCI format 0_0 may not include a carrier indicator field. That is, 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. By detecting DCI format 0_0 on a downlink component carrier of a serving cell, the terminal device 1 may recognize that the PUSCH scheduled by DCI format 0_0 is allocated on the uplink component carrier of the serving cell.

[0133] DCI format 0_0 may not include a BWP 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.

[0134] DCI format 0_1 ​​is used at least for scheduling PUSCHs allocated to a certain cell. DCI format 0_1 ​​includes 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

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

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

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

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

[0139] The BWP field of DCI format 0_1 ​​may be used to indicate an uplink BWP in which a PUSCH scheduled by the DCI format 0_1 ​​is arranged. That is, DCI format 0_1 ​​may involve a change of the active uplink BWP. The terminal device 1 may recognize the uplink BWP in which the PUSCH is arranged based on detecting DCI format 0_1 ​​used for scheduling the PUSCH.

[0140] The DCI format 0_1 ​​that 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 is to be transmitted without switching the active uplink BWP based on detecting the DCI format D0_1 that is DCI format 0_1 ​​used for scheduling a PUSCH and does not include a BWP field.

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

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

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

[0144] DCI format 1_0 is used at least for scheduling PDSCHs allocated to a certain cell. DCI format 1_0 includes 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, and 3F) PUCCH resource indicator field.

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

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

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

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

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

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

[0151] DCI format 1_0 may not include a carrier indicator field. That is, 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. By 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 allocated to the downlink component carrier.

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

[0153] DCI format 1_1 is used at least for scheduling PDSCHs allocated to a certain cell. DCI format 1_1 includes 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, and 4I) Carrier indicator field.

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

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

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

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

[0158] 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 an 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 parameter of a higher layer.

[0159] The PUCCH resource indication field may be a field indicating an index of one or more PUCCH resources included in a PUCCH resource set.

[0160] 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 arranged. That is, DCI format 1_1 may involve a change of the active downlink BWP. The terminal device 1 may recognize the downlink BWP in which the PUSCH is arranged by detecting DCI format 1_1 used for scheduling the PDSCH.

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

[0162] If DCI format 1_1 includes a BWP field but the terminal device 1 does not support the BWP switching function using DCI format 1_1, the BWP field may be ignored by the 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 the terminal device 1 supports the BWP switching function, it may report that "the terminal device 1 supports the BWP switching function" in the RRC layer capability information reporting procedure.

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

[0164] 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. A transport block may be allocated to the PDSCH. A transport block corresponding to the DL-SCH may be allocated to the PDSCH. The base station device 3 may transmit the PDSCH. The terminal device 1 may receive the PDSCH.

[0165] The downlink physical signal may correspond to a set of resource elements. The downlink physical signal does not need to 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)

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

[0167] FIG. 7 is a diagram showing an example of the configuration of an SS / PBCH block according to one aspect of this embodiment. In FIG. 7, the horizontal axis is the time axis (OFDM symbol index l sym ), where 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 associated with the PBCH, DMRS included in the PBCH, and DMRS corresponding to the PBCH).

[0168] As shown in Figure 7, the SS / PBCH block includes a PSS, SSS, and PBCH. The SS / PBCH block 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 the DMRS for the PBCH is not allocated. The PBCH is allocated to the 1st to 48th subcarriers of the third OFDM symbol, and to subcarriers where DMRS for the PBCH is not allocated. The PBCH is allocated to the 193rd to 240th subcarriers of the third OFDM symbol, and to subcarriers where DMRS for the PBCH is not allocated. The PBCH is allocated to the 1st to 240th subcarriers of the fourth OFDM symbol, and to subcarriers where DMRS for the PBCH is not allocated.

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

[0170] The PBCH on which the PBCH symbol is 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 is included in the SS / PBCH block to which the PBCH belongs.

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

[0172] The set of antenna ports for DMRS for PDSCH (DMRS related to PDSCH, DMRS included in PDSCH, DMRS corresponding to PDSCH) may be determined based on the set of antenna ports for the PDSCH, i.e., the set of antenna ports for DMRS for PDSCH may be the same as the set of antenna ports for the PDSCH.

[0173] The transmission of the PDSCH and the transmission of the 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 the PDSCH may also mean transmitting the PDSCH and the DMRS for the PDSCH.

[0174] A propagation path of a PDSCH may be estimated from a DMRS for the PDSCH. If a set of resource elements carrying a certain PDSCH symbol and a set of resource elements carrying a DMRS symbol for the PDSCH are included in the same precoding resource group (PRG), the PDSCH carrying the PDSCH symbol for a certain antenna port may be estimated by the DMRS for the PDSCH.

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

[0176] A PDCCH may be estimated from a DMRS for the PDCCH. That is, a propagation path of a PDCCH may be estimated from a DMRS for the PDCCH. If the same precoder is applied (or assumed to be applied) to a set of resource elements on which a certain PDCCH symbol is transmitted and a set of resource elements on which a DMRS symbol for the PDCCH is transmitted, the PDCCH on which the PDCCH symbol for a certain antenna port is transmitted may be estimated by the DMRS for the PDCCH.

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

[0178] The BCH of the transport layer is mapped to the PBCH of the physical layer. That is, transport blocks carried on 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 carried on 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 carried on the DL-SCH of the transport layer are delivered to the PDSCH of the physical layer.

[0179] One UL-SCH and one DL-SCH may be provided for each serving cell. The BCH may be provided for the PCell. The BCH does not necessarily have to be provided for the PSCell or SCell.

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

[0181] The BCCH (Broadcast Control CHannel), CCCH (Common Control CHannel), and DCCH (Dedicated Control CHannel) are logical channels. For example, the BCCH is a channel of the RRC layer used for transmitting MIB or system information. The CCCH (Common Control CHannel) may be used for transmitting RRC messages common to multiple terminal devices 1. Here, the CCCH may be used, for example, for terminal devices 1 that are not RRC connected. The DCCH (Dedicated Control CHannel) may be used at least for transmitting RRC messages dedicated to the terminal device 1. Here, the DCCH may be used, for example, for terminal devices 1 that are RRC connected.

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

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

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

[0185] The BCCH of the logical channel is mapped to the BCH or DL-SCH of the transport layer. For example, a transport block containing MIB information is delivered to the BCH of the transport layer. A transport block containing system information 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.

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

[0187] The upper layer parameters (upper layer parameters) are RRC parameters or parameters included in MAC CE (Medium Access Control Control Element). That is, the upper layer parameters are a collective term for MIB, system information, messages corresponding to CCCH, messages corresponding to DCCH, and parameters included in MAC CE. The parameters included in MAC CE are transmitted by MAC CE (Control Element) commands.

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

[0189] The cell search is a procedure used by the terminal device 1 to synchronize with a certain cell in the time domain and the frequency domain and detect a physical cell identity. That is, the terminal device 1 may perform the cell search to synchronize with a certain cell in the time domain and the frequency domain and detect a physical cell ID.

[0190] The sequence of PSSs is based at least on a physical cell ID. The sequence of SSSs is based at least on a physical cell ID.

[0191] The SS / PBCH block candidates indicate resources on which transmission of the SS / PBCH blocks is permitted (possibly, reserved, configured, defined, possible).

[0192] The set of SS / PBCH block candidates in a 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 (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.

[0193] The base station device 3 transmits SS / PBCH blocks of one or more indexes at a predetermined period. The terminal device 1 may detect at least one of the SS / PBCH blocks of the one or more indexes and attempt to decode the PBCH included in the SS / PBCH block.

[0194] Random access is a procedure that includes at least some or all of message 1, message 2, message 3, and message 4.

[0195] Message 1 is a procedure for transmitting a PRACH by a terminal device 1. The terminal device 1 transmits a PRACH in one PRACH opportunity selected from one or more PRACH opportunities based at least on an index of an SS / PBCH block candidate detected based on a cell search. Each PRACH opportunity is defined based at least on resources in the time domain and the frequency domain.

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

[0197] Message 2 is a procedure in which the terminal device 1 attempts to detect DCI format 1_0 with a CRC (Cyclic Redundancy Check) scrambled with an RA-RNTI (Random Access - Radio Network Temporary Identifier). The terminal device 1 attempts to detect a PDCCH including this DCI format in a control resource set provided based on an MIB included in a PBCH included in an SS / PBCH block detected based on a cell search and in resources indicated based on the setting of a search space set. Message 2 is also referred to as a random access response.

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

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

[0200] Message 3 PUSCH retransmissions are scheduled with DCI format 0_0 with CRC scrambled based on TC-RNTI (Temporary Cell - Radio Network Temporary Identifier).

[0201] Message 4 is a procedure for attempting to detect DCI format 1_0 with a CRC scrambled based on either a Cell-Radio Network Temporary Identifier (C-RNTI) or a 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.

[0202] Data communication is a general term for downlink communication and uplink communication.

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

[0204] A control resource set 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).

[0205] A set of resource blocks constituting the control resource set may be indicated by a higher layer parameter, and the number of OFDM symbols constituting the control resource set may be indicated by a higher layer parameter.

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

[0207] The search space set is defined as a set of PDCCH candidates. The search space set may be a Common Search Space (CSS) set or a UE-specific Search Space (USS) set. The terminal device 1 attempts to detect PDCCH candidates in some or all of a Type 0 PDCCH common search space set, a Type 0a PDCCH common search space set, a Type 1 PDCCH common search space set, a Type 2 PDCCH common search space set, a Type 3 PDCCH common search space set, and / or a UE-specific search space set.

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

[0209] The CSS set is a collective term for a Type 0 PDCCH common search space set, a Type 0a PDCCH common search space set, a Type 1 PDCCH common search space set, a Type 2 PDCCH common search space set, and a Type 3 PDCCH common search space set. The USS set is also called a UE-specific PDCCH search space set.

[0210] A search space set is associated with (included in, corresponds to) a control resource set, and the index of the control resource set associated with the search space set may be indicated by a higher layer parameter.

[0211] For a given search space set, some or all of 6A to 6C may be indicated by higher layer parameters: 6A) PDCCH monitoring periodicity, 6B) PDCCH monitoring pattern within a slot, and 6C) PDCCH monitoring offset.

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

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

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

[0215] 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 slot, and the monitoring pattern of search area set 91 is set to [1, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0]. That is, 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.

[0216] 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,0,0]. That is, the monitoring opportunity for search area set 92 corresponds to the first OFDM symbol (OFDM symbol #0) in each of the even slots.

[0217] 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 eighth OFDM symbol (OFDM symbol #7) in each of the even slots.

[0218] 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,0,0]. That is, the monitoring opportunity for search area set 94 corresponds to the first OFDM symbol (OFDM symbol #0) in each odd slot.

[0219] 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 a SI-RNTI (System Information-Radio Network Temporary Identifier).

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

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

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

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

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

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

[0226] In uplink communication, the terminal device 1 detects an 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.

[0227] In configured scheduling (configured grant), an uplink grant for scheduling a PUSCH is configured for each transmission period of the PUSCH. When a PUSCH is scheduled by 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.

[0228] The UL slot may be a slot consisting of UL symbols. The special slot may be a slot consisting of UL symbols, flexible symbols, and DL symbols. The DL slot may be a slot consisting of DL symbols.

[0229] The UL symbol may be an OFDM symbol configured or indicated for the uplink in time division duplex. The UL symbol may be an OFDM symbol configured or indicated for PUSCH, PUCCH, PRACH, or SRS. The UL symbol may be provided by the higher layer parameter tdd-UL-DL-ConfigurationCommon. The UL symbol may be provided by the higher layer parameter tdd-UL-DL-ConfigurationDedicated. The UL slot may be provided by the higher layer parameter tdd-UL-DL-ConfigurationCommon. The UL slot may be provided by the higher layer parameter tdd-UL-DL-ConfigurationDedicated.

[0230] The DL symbol may be an OFDM symbol configured or indicated for downlink in time division duplex. The DL symbol may be an OFDM symbol configured or indicated for PDSCH or PDCCH. The DL symbol may be provided by the higher layer parameter tdd-UL-DL-ConfigurationCommon. The DL symbol may be provided by the higher layer parameter tdd-UL-DL-ConfigurationDedicated. The DL slot may be provided by the higher layer parameter tdd-UL-DL-ConfigurationCommon. The DL slot may be provided by the higher layer parameter tdd-UL-DL-ConfigurationDedicated.

[0231] A flexible symbol may be an OFDM symbol within a period that is not configured or indicated as an UL symbol or DL ​​symbol. The period may be a period given by the higher layer parameter dl-UL-TransmissionPeriodicity. The flexible symbol may be an OFDM symbol configured or indicated for a PDSCH, PDCCH, PUSCH, PUCCH, or PRACH.

[0232] The upper layer parameter tdd-UL-DL-ConfigurationCommon may be a parameter that sets a UL slot, a DL slot, or a special slot for each of one or more slots. The upper layer parameter tdd-UL-DL-ConfigurationDedicated may be a parameter that sets a UL symbol, a DL symbol, or a flexible symbol for each of the flexible symbols in the one or more slots. The tdd-UL-DL-ConfigurationCommon may be a common upper layer parameter. The tdd-UL-DL-ConfigurationDedicated may be a dedicated upper layer parameter.

[0233] The base station device 3 may send a terminal capability request to the terminal device 1. The terminal device 1 may send one or more pieces of terminal capability information to the base station device 3. The terminal capability information may include one or more terminal capabilities. The RRC message may include the terminal capability information. The base station device 3 may receive the RRC message. The base station device 3 may receive an RRC message including upper layer parameters. When sending terminal capability information, the terminal device 1 may send an RRC message to the base station device 3.

[0234] The terminal device 1 may be configured with a list of up to M TCI state configurations. The TCI state configuration may be in PDSCH-Config. PDSCH-Config may be a configuration for decoding the PDSCH. M may depend on maxNumberConfiguredTCIstatesPerCC. Each TCI state may include a parameter for configuring a QCL. The QCL may be a relationship between one or two downlink reference signals and a DMRS port of the PDSCH. The QCL may be a relationship between one or two downlink reference signals and a DMRS port of the PDCCH. The QCL may be a relationship between one or two downlink reference signals and a CSI-RS port of a certain CSI-RS resource. The QCL relationship may be configured by the higher layer parameter qcl-Type1 for the first downlink reference signal. If configured, the QCL relationship may be configured by the higher layer parameter qcl-Type2 for the second downlink reference signal. The QCL may be a QCL relationship. For two downlink reference signals, the QCL types may not be the same regardless of whether the reference signals are the same downlink reference signal or different downlink reference signals. The QCL type corresponding to each downlink reference signal may be given by qcl-type in the higher layer parameter QCL-Info. For example, the value of qcl-type may be one of {typeA, typeB, typeC, typeD}. typeA may indicate {Doppler shift, Doppler spread, average delay, delay spread}. typeB may indicate {Doppler shift, Doppler spread}. typeC may indicate {Doppler shift, average delay}. typeD may indicate {spatial Rx filter}. QCLtype may be a value set by the higher layer parameter qcl-Type. QCLtype may be a value set by the higher layer parameter qcl-Type.

[0235] The terminal device 1 may be configured with a list of up to 128 TCI state configurations. The TCI state configuration may be in dlOrJointTCI-StateList in the upper layer parameter PDSCH-Config. For example, the TCI state configuration may be for providing a reference signal for a QCL for DMRS of PDSCH. For example, the TCI state configuration may be for providing a reference signal for a QCL for DMRS of PDCCH. For example, the TCI state configuration may be for providing a reference signal for a QCL for DMRS of PDSCH. For example, the TCI state configuration may be for providing a reference signal for a QCL for CSI-RS. For example, the TCI state configuration may be for providing a reference signal for determining an UL TX spatial filter (uplink transmit spatial filter). The UL TX spatial filter may be for PUSCH, PUCCH resources, and SRS.

[0236] The TCI state may refer to the higher layer parameter TCI-state.

[0237] If the TCI-state or TCI-UL-state setting is not within a BWP of that component carrier, the terminal device 1 may apply the TCI-state or TCI-UL-state setting of a reference BWP of a reference component carrier set by unifiedTCI-stateRef. If the terminal device 1 is set in dl-OrJoingtTCI-StateList or ul-TCI-StateList, the terminal device 1 does not need to expect to be set in tci-StatesToAddModList, SpatialRelationInfo, or PUCCH-SpatialRelationInfo. When the terminal device 1 is configured in the tci-StatesToAddModList of any component carrier in the component carrier list configured by simultaneousTCI-UpdateList1-r16, simultaneousTCI-UpdateList2-r16, simultaneousSpatial-UpdatedList1-r16, or simultaneousSpatial-UpdatedList2-r16, it may be assumed that it is not configured in the dl-OrJointTCI-StateList or ul-TCI-StateList in that component carrier list.

[0238] The terminal device 1 may receive an activation command. Receiving the activation command may be receiving a MAC CE. The activation command may be used to map up to eight TCI states or up to eight TCI state pairs to code points in the DCI field. For example, the DCI field may be Transmission Configuration Indication. One TCI state may be for one downlink physical channel. One TCI state may be for one uplink physical channel. The activation command may be used to map up to eight TCI state sets to code points in the DCI field. For example, each TCI state set may be configured with up to two TCI states for the downlink and uplink. Each TCI state set may be configured with up to two TCI states for the downlink and uplink.

[0239] When the upper layer parameter tci-PresentInDCI is set or tci-PresentDCI-1-2 is configured for CORESET, a terminal device 1 configured with dl-OrJointTCI-StateList having an activated TCI-state or ul-TCI-StateList having an activated TCI-UL-State may receive DCI format 1_1 / 1_2 / 1_3 providing the indicated TCI state. If applicable, DCI format 1_1 / 1_2 may have a downlink assignment. If applicable, DCI format 1_1 / 1_2 may not have a downlink assignment. If DCI format 1_1 / 1_2 does not have a downlink assignment, the terminal device 1 may assume certain conditions. For example, one condition may be that the CS-RNTI is used to scramble the CRC for the DCI. It may assume that the RV of the DCI field is all 1s. It may assume that the MCS of the DCI field is all 1s. It may assume that the NDI of the DCI field is 0. It may be assumed that the DCI field FDRA is all zeros.

[0240] When the terminal device 1 receives an initial upper layer configuration dl-OrJointTCI-StateList having one or more TCI-states and before applying the TCI state indicated from the configured TCI state, the DMRS of the PDSCH, the DMRS of the PDCCH and the CSI-RS to which the terminal device 1 applies the indicated TCI state may be the SS / PBCH block and QCL recognized by the UE at initial access.

[0241] When the terminal device 1 receives an initial higher layer configuration dl-OrJointTCI-StateList having one or more TCI-states or an initial higher layer configuration ul-TCI-StateList having one or more TCI-UL-States, and before applying a TCI state indicated by the configured TCI state, the terminal device 1 may assume that the UL TX spatial filter is the same as a certain PUSCH transmission. For example, a certain PUSCH transmission may be a PUSCH transmission scheduled by an RAR UL grant. For example, a certain PUSCH transmission may be an MsgA PUSCH transmission.

[0242] When terminal device 1 receives an upper layer configured dl-OrJointTCI-StateList with one TCI-state, that TCI-state may be used as the indicated TCI state. When terminal device 1 receives an upper layer configured dl-OrJointTCI-StateList with one TCI-state, terminal device 1 may derive a QCL assumption from that configured TCI state.

[0243] When the terminal device 1 receives an upper layer configured ul-TCI-StateList with one TCI-UL-state, that TCI-state may be used as the indicated TCI state.

[0244] If the indicated TCI state is different from the previously indicated TCI state, the indicated TCI-state and / or TCI-UL-state may be applied starting from a slot, which may be the first slot after the last symbol of the PUSCH or PUCCH and at least beamAppTime symbols later.

[0245] When terminal device 1 is configured with dl-OrJointTCI-StateList, and when terminal device 1 is configured with unifiedTCI-StateType as 'separate', and when terminal device 1 receives a TCI codepoint to which any of {TCI-State, TCI-UL-State} is mapped, terminal device 1 may update one of the indicated {TCI-State, TCI-UL-State}. For example, terminal device 1 may maintain the other {TCI-State, TCI-UL-State} that is not updated by the received TCI codepoint.

[0246] When the terminal device 1 is configured in dl-OrJointTCI-StateList and has two indicated TCI-states, if the terminal device 1 receives a TCI codepoint to which one or both of the first and second TCI-State subsets and the first and second TCI-UL-State subsets are mapped, the terminal device 1 may update either the first or second TCI-State or the first or second TCI-UL-State mapped to that TCI codepoint. The terminal device 1 may maintain a previously indicated TCI state that is not updated by the TCI codepoint. The TCI state may be a TCI-State. For example, the TCI state may be the first and second TCI-States. The TCI state may be a TCI-UL-State. For example, the TCI state may be the first and second TCI-UL-States.

[0247] When the terminal device 1 is configured with SSB-MTC-AdditionalPCI and with a PDCCH-Config including a different value of coresetPoolIndex in the ControlResourceSet, the terminal device 1 may receive an activation command. The activation command may be for a CORESET associated with each coresetPoolIndex. When a set of TCI state IDs is activated for a coresetPoolIndex, the activated TCI state corresponding to one coresetPoolIndex may be associated with the serving cell physical cell ID. In this case, the activated TCI state corresponding to another coresetPoolIndex may be associated with another physical cell ID. The physical cell ID may be a PCI.

[0248] When the terminal device 1 indicates two TCI states in a code point of the DCI field 'Transmission Configuration Indication', the terminal device 1 may receive an activation command. The activation command may be used to map up to eight combinations of one or two TCI states to that code point. The terminal device 1 may not be expected to receive more than eight TCI states in an activation command.

[0249] When the DCI field 'Transmission Configuration Indication' is present in DCI format 1_2 and the number S of codepoints in the DCI field 'Transmission Configuration Indication' is less than the number of TCI codepoints activated by the activation command, only the first S activated codepoints may be applied to DCI format 1_2.

[0250] The terminal device 1 may be configured with an upper layer parameter tci-PresentInDCI. tci-PresentInDCI may be set as enable for CORESET that schedules the PDSCH. In that case, the terminal device 1 may assume that the TCI field is present in DCI format 1_1 or 1_3 of the PDCCH transmitted on CORESET.

[0251] The terminal device 1 may be configured with the higher layer parameter tci-PresentInDCI-1-2 for CORESET to schedule the PDSCH. In that case, the terminal device 1 may assume that a TCI field is present in DCI format 1_2 of the PDCCH transmitted on CORESET. The size of the TCI field may be indicated by tci-PresentInDCI-1-2.

[0252] The terminal device 1 may be configured with both sfnSchemePDCCH and sfnSchemePDSCH. The offset time between reception of downlink DCI and reception of the corresponding PDSCH may be greater than or equal to the threshold timeDurationForQCL. The terminal device 1 may support sfn-DefaultDL-BeamSetup-r17 for DCI scheduling without a TCI field. In that case, the terminal device 1 may assume that the TCI state or QCL assumption for the PDSCH matches the TCI state or QCL assumption applied for the CORESET used for reception of downlink DCI in the active BWP of the serving cell, regardless of the number of TCIs active in the CORESET. If the terminal device 1 does not indicate SchemeA-DynamicSwitching-r17 or sfn-SchemeB-DynamicSwitching-r17, the terminal device 1 may be activated with two TCI states in that CORESET.

[0253] The terminal device 1 may be configured with both sfnSchemePDCCH and sfnSchemePDSCH. The offset time between reception of the downlink DCI and reception of the corresponding PDSCH may be greater than or equal to the threshold timeDurationForQCL. The terminal device 1 may not support sfn-DefaultDL-BeamSetup-r17 for DCIs scheduled without a TCI field. In that case, the terminal device 1 may not expect a TCI field to be present when scheduled with DCI format 1_1 or 1_2.

[0254] If the terminal device 1 is not configured in both sfnSchemePDCCH and sfnSchemePDSCH, and is scheduled in DCI format 1_1 or 1_2, and the offset time between the reception of the downlink DCI and the reception of the corresponding PDSCH is greater than or equal to the threshold timeDuraionForQCL, the terminal device 1 may expect the TCI field to be present.

[0255] The terminal device 1 may configure sfnSchemePDCCH with 'sfnschemeA'. At that time, the terminal device 1 may not configure sfnSchemePDSCH. In that case, there may not be a TCI code point with two TCI states in the activation command for the PDSCH. If the offset time between the reception of the downlink DCI and the reception of the corresponding PDSCH is equal to or greater than the threshold timeDurationForQCL, and if the CORESET scheduling the PDSCH is indicated with two TCI states, the terminal device 1 may assume that the TCI state or QCL assumption for the PDSCH is the same as the initial TCI state or QCL assumption applied for the CORESET used for PDCCH transmission.

[0256] 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 (a codepoint in the TCI field) with two TCI states, and the time offset is equal to or greater than a threshold, and the CORESET that schedules 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 the first QCL assumption applied for the CORESET. Configuring SFN scheme A for the PDCCH may also mean configuring sfnSchemePdcch with 'sfnSchemeA' set.

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

[0258] If the 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 set to typeD, 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 the 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 set to typeD, and the indicated TCI state is associated with the PCI (Physical Cell ID) of the serving cell, the DMRS port of the PDSCH in the serving cell may use the reference signal and QCL associated with the QCL parameter of the CORESET associated with the lowest CORESET ID. Configuring the unified TCI state may also mean configuring the higher layer parameter dl-OrJointTCI-StateList.

[0259] 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'.

[0260] 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 for 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 for 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.

[0261] Regardless of the settings of tci-PresentInDCI and tci-PresentDCI-1-2 in the RRC connected mode, if dl-OrJointTCI-StateList-r17 is not provided to the terminal device 1 and the offset between receptions of downlink DCI corresponding to the PDSCH is smaller than timeDurationForQCL, at least one configured TCI state may include qcl-Type set to 'typeD'. In that case, the terminal device 1 may assume that the DMRS port of the PDSCH is the RS and QCL used for the PDCCH. The PDCCH may be based on the QCL indication of the CORESET associated with the lowest controlResourceSetId in the latest slot among one or more CORESETs in the active BWP of the serving cell monitored by the terminal device 1 and the CORESET associated with the monitored search space.

[0262] The terminal device 1 may be configured with enableDefaultTCI-StatePerCoresetPoolIndex. The terminal device 1 may also be configured with the higher layer parameter PDCCH-Config. The PDCCH-Config may include two different coresetPoolIndex values ​​in different ControlResourceSets. In this case, the terminal device 1 may assume that the DMRS port of the PDSCH associated with the coresetPoolIndex value of the serving cell is the RS and QCL used for the PDCCH. The PDCCH may be the PDCCH that schedules the PDSCH in the active BWP of the serving cell monitored by the terminal device 1, and may be based on the lowest controlResourceSetId among the CORESETs and the QCL indication of the CORESET associated with the monitored search space.

[0263] The terminal device 1 may be configured with enableTwoDefaultTCI-States. In this case, at least one TCI code point may indicate two TCI states. The terminal device 1 may assume that the DMRS port of the PDSCH or the PDSCH transmission opportunity of the serving cell is in the RS and QCL state associated with the TCI state corresponding to the lowest code point between the TCI code points including two different TCI states.

[0264] The terminal device 1 may be configured with the higher layer parameter repetitionScheme. The repetitionScheme may be set with tdmSchemeA. In that case, or when configured with the higher layer parameter repetitionNumber and the offset between the first PDSCH transmission opportunity and the reception of downlink DCI is less than the threshold timeDurationForQCL, the mapping of TCI states to PDSCH transmission opportunities may be determined by a certain method.

[0265] If the TCI states set for the serving cell of the scheduled PDSCH are not all set to type-D, the terminal device 1 may derive other QCL assumptions from the indicated TCI states for that scheduled PDSCH.

[0266] Regardless of the settings of tci-PresentInDCI and tci-PresentDCI-1-2 in RRC connected mode, dl-OrJointTCI-StateList-r17 may be provided to the terminal device 1. In this case, when the offset between the downlink DCI and the corresponding PDSCH is smaller than timeDurationForQCL, regardless of the setting of followUnifiedTCI-State, at least one set TCI state may include qcl-Type set to type D. In this case, if the indicated TCI state is linked to the PCI of the serving cell, the indicated TCI state may be applied to reception of the PDSCH.

[0267] Regardless of the settings of tci-PresentInDCI and tci-PresentDCI-1-2 in the RRC connected mode, the terminal device 1 may be provided with dl-OrJointTCI-StateList-r17. In this case, when the offset between the downlink DCI and the corresponding PDSCH is smaller than timeDurationForQCL, regardless of the setting of followUnifiedTCI-State, at least one configured TCI state may include qcl-Type set to type D. In this case, if the indicated TCI state is associated with the PCI of a different serving cell, the terminal device 1 may assume that the DMRS port of the PDSCH of a certain serving cell is the RS and QCL state used for the PDCCH. The PDCCH may be based on the lowest controlResourceSetId in the latest slot among one or more CORESETs in the active BWP of the serving cell monitored by the terminal device 1 and the indication of the CORESET associated with the monitored search space. In the case of CA, if the 'QCL-TypeD' of the DMRS of the PDSCH of each component carrier in a band is different, the 'QCL-TypeD' assumption of the DMRS of the PDSCH of the component carrier with the lowest component carrier ID in that band may be applied to the DMRS of all PDSCHs of that component carrier in that band.

[0268] The terminal device 1 may retain the indicated terminal capability beamCorrespondenceWithoutUL-BeamSweeping. beamCorrespondenceWithoutUL-BeamSweeping may be set to 'supported'. In that case, the terminal device 1 may determine the spatial filter to be used during the channel access procedure prior to a certain uplink transmission. The terminal device 1 may be indicated by an SRI. If the terminal device 1 is indicated by an SRI corresponding to an uplink transmission, it may use the same spatial filter as the spatial filter associated with the indicated SRI. The terminal device 1 may be configured by SRS-spatialRelationInfo for uplink transmission. In that case, the terminal device 1 may use the same spatial filter as the spatial filter associated with the referenceSignal in the corresponding SRS-spatialRelationInfo. The terminal device 1 may be configured by a TCI-state in the dl-OrJointTCI-StateList or a TCI-UL-State in the ul-TCI-StateList. In that case, the terminal device 1 may use a certain spatial filter. The spatial filter may be the same as the receive spatial filter used to receive the downlink reference signal associated with the indicated TCI state.

[0269] The reception of a PDCCH may include two PDCCHs from two respective search spaces. In this case, the PDCCH candidate that ends later in time may be used for the purpose of determining the time offset between the reception of the corresponding PDSCH and downlink DCI. The reception of a PDCCH may include two PDCCH candidates from two respective search spaces. In this case, for the configuration of tci-PresentInDCI or tci-PresentDCI-1-2, the terminal device 1 may expect the same configuration in the first and second CORESETs associated with the two PDCCH candidates. The PDSCH may also be scheduled using a DCI format that does not have a TCI field. In this case, and if the scheduling offset is equal to or greater than timeDurationForQCL, the QCL assumption for the PDSCH may be determined based on the CORESET with the lowest ID between the first and second CORESETs associated with the two PDCCH candidates.

[0270] The CSI-RS resources in the NZP-CSI-RS-resourceSet may be configured to be periodic. For periodic CSI-RS resources in the NZP-CSI-RS-resourceSet configured in the higher layer parameter trs-Info, the terminal device 1 may expect a certain TCI-state to indicate a certain QCL type. A certain QCL type may be type C for an SSB. A certain QCL type may be type D for the same SSB. The SSB may have a PCI different from that of its serving cell. The terminal device 1 may assume that an SSB with a different PCI of its serving cell has the same center frequency, subcarrier spacing, and SFN offset as the SSB of the serving cell. A certain QCL type may be type D for the CSI-RS resources in the NZP-CSI-RS-resourceSet configured in the higher layer parameter repetition. The SSB may have a PCI different from that of its serving cell. The terminal device 1 may assume that an SSB having a PCI different from that of the serving cell and an SSB of that serving cell have the same center frequency, subcarrier spacing, and SFN offset.

[0271] The CSI-RS may be configured to be periodic or semi-persistent. If the terminal device 1 is configured with dl-OrJointTCI-StateList for periodic or semi-persistent CSI-RS, the terminal device 1 may assume that the indicated TCI-state does not apply.

[0272] The CSI-RS resources in the NZP-CSI-RS-resourceSet may be set to aperiodic. The NZP-CSI-RS-resourceSet may be set by the upper layer parameter trs-Info. For aperiodic CSI-RS resources in the NZP-CSI-RS-resourceSet set by the upper layer parameter trs-Info, the terminal device 1 may expect the TCI-state to indicate periodic CSI-RS resources in the NZP-CSI-RS-resourceSet and qcl-Type to be 'type A'. For aperiodic CSI-RS resources in the NZP-CSI-RS-resourceSet set by the upper layer parameter trs-Info, the terminal device 1 may expect the TCI-state to indicate periodic CSI-RS resources in the NZP-CSI-RS-resourceSet and qcl-Type to be 'type D'.

[0273] For CSI-RS resources in the NZP-CSI-RS-resourceSet that are not configured in the higher layer parameter trs-Info and are not configured in the higher layer parameter repetition, the terminal device 1 may expect the TCI-state to indicate a certain QCL type. A certain QCL type may be type A with the CSI-RS resources in the NZP-CSI-RS-resourceSet that are configured in the higher layer parameter trs-Info. For example, it may be type D with the same CSI-RS resources.

[0274] For CSI-RS resources in the NZP-CSI-RS-resourceSet that are not configured in the higher layer parameter trs-Info and are not configured in the higher layer parameter repetition, the terminal device 1 may expect the TCI-state to indicate a certain QCL type. A certain QCL type may be type A for the CSI-RS resources in the NZP-CSI-RS-resourceSet that are configured in the higher layer parameter trs-Info. For example, it may be type D for an SSB. The SSB may have a PCI different from the PCI of its serving cell. The terminal device 1 may assume that the center frequency, SFN offset, and subcarrier spacing of an SSB with a PCI different from that of the serving cell are the same as those of the serving cell.

[0275] For CSI-RS resources in the NZP-CSI-RS-resourceSet that are not configured in the higher layer parameter trs-Info and are not configured in the higher layer parameter repetition, the terminal device 1 may expect the TCI-state to indicate a certain QCL type. A certain QCL type may be type A for the CSI-RS resources in the NZP-CSI-RS-resourceSet that are configured in the higher layer parameter trs-Info. For example, it may be type D for the CSI-RS resources in the NZP-CSI-RS-resourceSet that are configured in the higher layer parameter repetition.

[0276] For CSI-RS resources in the NZP-CSI-RS-resourceSet that are not configured in the higher layer parameter trs-Info and are not configured in the higher layer parameter repetition, the terminal device 1 may expect the TCI-state to indicate a certain QCL type. A certain QCL type may be type B for the CSI-RS resources in the NZP-CSI-RS-resourceSet that are configured in the higher layer parameter trs-Info when type D is not applicable.

[0277] For a CSI-RS resource in the NZP-CSI-RS-resourceSet configured by the higher layer parameter repetition, the terminal device 1 may expect the TCI-state to indicate a certain QCL type. A certain QCL type may be type A with the CSI-RS resource in the NZP-CSI-RS-resourceSet configured by the higher layer parameter trs-Info. For example, it may be type D with the same CSI-RS resource.

[0278] For the CSI-RS resources in the NZP-CSI-RS-resourceSet configured by the higher layer parameter repetition, the terminal device 1 may expect the TCI-state to indicate a certain QCL type. A certain QCL type may be type A for the CSI-RS resources in the NZP-CSI-RS-resourceSet configured by the higher layer parameter trs-Info. For example, it may be type D for the CSI-RS resources in the NZP-CSI-RS-resourceSet configured by the higher layer parameter repetition.

[0279] For the CSI-RS resources in the NZP-CSI-RS-resourceSet configured by the higher layer parameter repetition, the terminal device 1 may expect the TCI-state to indicate a certain QCL type. A certain QCL type may be type C for an SSB. For example, it may be type D for a similar SSB, and its reference signal may be an SSB with a PCI different from the PCI of the serving cell. The terminal device 1 may assume that the center frequency, subcarrier spacing, and SFN offset for an SSB with a PCI different from that of the serving cell are the same as those for the SSB of the serving cell.

[0280] For DMRS of PDCCH, if the terminal device 1 is not configured in dl-OrJointTCI-StateList, the terminal device 1 may expect the TCI-state to indicate a certain QCL type. A certain QCL type may be that the CSI-RS resources in the NZP-CSI-RS-resourceSet configured in the higher layer parameter trs-Info are type A. For example, it may be that the same CSI-RS resources are type D.

[0281] For DMRS of PDCCH, if the terminal device 1 is not configured in dl-OrJointTCI-StateList, the terminal device 1 may expect that the TCI-state indicates a certain QCL type. A certain QCL type may be that the CSI-RS resources in the NZP-CSI-RS-resourceSet configured in the higher layer parameter trs-Info are type A. For example, it may be that the CSI-RS resources in the NZP-CSI-RS-resourceSet configured in the higher layer parameter repetition are type D.

[0282] For DMRS of PDCCH, if the terminal device 1 is not configured in dl-OrJointTCI-StateList, the terminal device 1 may expect the TCI-state to indicate a certain QCL type. A certain QCL type may be that the CSI-RS resources in the NZP-CSI-RS-resourceSet that are not configured in the higher layer parameter trs-Info and are not configured in the higher layer parameter repetition are type A. For example, it may be that the same CSI-RS resources are type D.

[0283] When the terminal device 1 is configured with sfnSchemePdcch set by 'sfnschemeA' and CORESET is activated in two TCI states, the terminal device 1 may assume that the DMRS ports of the PDCCH of that CORESET are the downlink reference signals and QCL of the two TCI states. When the terminal device 1 is configured with sfnSchemePdcch set by 'sfnschemeB' and CORESET is activated in two TCI states, the terminal device 1 may assume that the DMRS ports of the PDCCH are the downlink reference signals and QCL of the two TCI states excluding the {Doppler shift, delay spread} of the second specified TCI state.

[0284] Terminal device 1 may be configured with the upper layer parameter cjtScheme. Terminal device 1 may be configured with the upper layer parameter d dl-OrJointTCI-StateList. Terminal device 1 may report terminal capability A. The terminal capability may be the ability to support two joint TCI states for PDSCH-CJT. The terminal capability may be [support for two joint TCI states for PDSCH-CJT].

[0285] When a terminal device 1 is configured with the upper layer parameters cjtScheme and dl-OrJointTCI-StateList, and two TCI states to be applied for receiving PDSCH are indicated, and the terminal reports terminal capability A, if the terminal is configured with cjtSchemeA, the DMRS port of the PDSCH may be assumed to be QCL for the downlink reference signals of both indicated TCI-states and QCL-TypeA.

[0286] When a terminal device 1 is configured with the upper layer parameters cjtScheme and dl-OrJointTCI-StateList, and two TCI states to be applied for receiving a PDSCH are indicated, and the terminal reports terminal capability A, if the terminal is configured with cjtSchemeB, the DMRS port of the PDSCH may assume that the downlink reference signals of both indicated TCI-states are QCL, except for the {Doppler shift, delay spread} of the second indicated joint TCI state for QCL-TyoeA.

[0287] For DMRS of PDSCH, if the terminal device 1 is not configured in dl-OrJointTCI-StateList, the terminal device 1 may expect that the TCI-State indicates a certain QCL type. A certain QCL type may be type A with the CSI-RS resources in the NZP-CSI-RS-resourceSet configured in the higher layer parameter trs-Info. For example, it may be type D with the same CSI-RS resources.

[0288] For DMRS of PDSCH, if the terminal device 1 is not configured in dl-OrJointTCI-StateList, the terminal device 1 may expect that TCI-State indicates a certain QCL type. A certain QCL type may be type A with the CSI-RS resources in the NZP-CSI-RS-resourceSet configured in the higher layer parameter trs-Info. For example, it may be type D with the CSI-RS resources in the NZP-CSI-RS-resourceSet configured in the higher layer parameter repetition.

[0289] For DMRS of PDSCH, if the terminal device 1 is not configured in dl-OrJointTCI-StateList, the terminal device 1 may expect that the TCI-State indicates a certain QCL type. A certain QCL type may be type A with CSI-RS resources in the NZP-CSI-RS-resourceSet that are not configured in the higher layer parameter trs-Info and are not configured in the higher layer parameter repetition. For example, it may be type D with the same CSI-RS resources.

[0290] For DMRS of PDCCH, if the terminal device 1 is configured in dl-OrJointTCI-StateList, the terminal device 1 may expect the indicated TCI-State to indicate a certain QCL type. A certain QCL type may be type A with the CSI-RS resources in the NZP-CSI-RS-resourceSet configured in the higher layer parameter trs-Info. For example, it may be type D with the same CSI-RS resources.

[0291] For DMRS of PDCCH, if the terminal device 1 is configured with dl-OrJointTCI-StateList, the terminal device 1 may expect the indicated TCI-State to indicate a certain QCL type. The certain QCL type may be type A with the CSI-RS resources in the NZP-CSI-RS-resourceSet configured with the higher layer parameter trs-Info. For example, it may be type D with the CSI-RS resources in the NZP-CSI-RS-resourceSet configured with the higher layer parameter repetition.

[0292] For DMRS of PDSCH, if the terminal device 1 is configured in dl-OrJointTCI-StateList, the terminal device 1 may expect the indicated TCI-State to indicate a certain QCL type. A certain QCL type may be type A with the CSI-RS resources in the NZP-CSI-RS-resourceSet configured in the higher layer parameter trs-Info. For example, it may be type D with the same CSI-RS resources.

[0293] For DMRS of PDSCH, if the terminal device 1 is configured with dl-OrJointTCI-StateList, the terminal device 1 may expect the indicated TCI-State to indicate a certain QCL type. A certain QCL type may be type A with the CSI-RS resources in the NZP-CSI-RS-resourceSet configured with the higher layer parameter trs-Info. For example, it may be type D with the CSI-RS resources in the NZP-CSI-RS-resourceSet configured with the higher layer parameter repetition.

[0294] The terminal device 1 may be configured with sfnSchemePDSCH. The sfnSchemePDSCH may be set to 'sfnSchemeA'. The terminal device 1 may be indicated in two TCI states in the codepoint of the DCI field. The DCI field may be 'Transmission Configuration Indication'. The DCI field may be a DCI that schedules the PDSCH. When the terminal device 1 is configured with sfnSchemePDSCH set to 'sfnSchemeA' and indicated in two TCI states in the codepoint of the DCI field 'Transmission Configuration Indication', the terminal device 1 may assume that the DMRS port of the PDSCH is a downlink reference signal and QCL in the two TCI states.

[0295] The terminal device 1 may be configured with sfnSchemePDSCH. The sfnSchemePDSCH may be set to 'sfnSchemeB'. The terminal device 1 may be indicated in two TCI states within the code point of the DCI field. The DCI field may be 'Transmission Configuration Indication'. The DCI field may be a DCI that schedules the PDSCH. When the terminal device 1 is configured with sfnSchemePDSCH set to 'sfnSchemeB' and indicated in two TCI states within the code point of the DCI field 'Transmission Configuration Indication', the terminal device 1 may assume that the DMRS port of the PDSCH is the downlink reference signal and QCL for the two TCI states, excluding the {Doppler shift, Doppler spread} of the second indicated TCI state.

[0296] The terminal device 1 may be configured with TCI-UL-State. The terminal device 1 may be configured with the higher layer parameter PDCCH-Config. The PDCCH-Config may include two different coresetPoolIndex values ​​in the ControlResourceSet. The indicated TCI state may be specific to the value of coresetPoolIndex. When the terminal device 1 is configured with TCI-UL-State or dl-OrJointTCI-StateList and the terminal device 1 is configured by the higher layer parameter PDCCH-Conig that includes two different coresetPoolIndex values ​​in the ControlResourceSet, and when the terminal device 1 is indicated by the DCI field 'Transmission Configuration Indication' in DCI format 1_1 / 1_2 associated with the value of coresetPoolIndex, the indicated TCI state may be specific to the value of coresetPoolIndex.

[0297] The terminal device 1 may hold two indicated TCI-states. When the terminal device 1 is configured in dl-OrJointTCI-StateList and holds two indicated TCI-states, and the terminal device 1 does not report a terminal capability in a certain frequency range, and the offset time between the reception of an activated or scheduled PDSCH and the reception of scheduled or activated DCI format 1_0 / 1_1 / 1_2 is less than timeDurationForQCL in a certain frequency range, the terminal device 1 may apply the first indicated TCI state to the reception of an activated or scheduled PDSCH. A certain frequency range may be Frequency range 2. A certain frequency range may be FR2. A certain terminal capability may be [two default beams for S-DCI based MTRP]. A certain terminal capability may be the ability to determine two default beams for single DCI-based MTRP transmission. A certain terminal capability may be the ability to set two default beams for single DCI-based MTRP transmission.

[0298] When the terminal device 1 is configured with dl-OrJointTCI-StateList and configured by the higher layer parameter PDCCH-Config including two different coresetPoolIndex in ControlResourceSet, the terminal device 1 may not report a certain terminal capability in a certain frequency domain. A certain terminal capability may be [default beam per coresetPoolIndex for M-DCI based MTRP]. A certain terminal capability may be the ability to determine a default beam per coresetPoolIndex for multi-DCI based MTRP. A certain terminal capability may be the ability to set a default beam per coresetPoolIndex for multi-DCI based MTRP.

[0299] When the terminal device 1 is configured with dl-OrJointTCI-StateList and configured by the upper layer parameter PDCCH-Config including two different coresetPoolIndex in the ControlResourceSet, if the terminal device 1 does not report a certain terminal capability in a certain frequency domain, if the offset between the reception of a scheduled or activated PDSCH and the reception of DCI format 1_0 / 1_1 / 1_2 in the CORESET associated with coresetPoolIndex value 0 is less than [timeDurationForQCL] in a certain frequency domain, the terminal device 1 may apply the indicated joint / downlink TCI state specific to coresetPoolIndex value 0 to the reception of the scheduled or activated PDSCH.

[0300] When terminal device 1 is configured with dl-OrJointTCI-StateList and configured by the upper layer parameter PDCCH-Config including two different coresetPoolIndex in ControlResourceSet, if terminal device 1 does not report a certain terminal capability in a certain frequency domain, terminal device 1 does not expect the offset between the reception of a scheduled or activated PDSCH and the reception of DCI format 1_0 / 1_1 / 1_2 in the CORESET associated with coresetPoolIndex value 1 to be less than [timeDurationForQCL] in a certain frequency domain.

[0301] The terminal device 1 may set dl-OrJointTCI-StateList and hold two indicated TCI-states. Regardless of the offset between the reception of a scheduled or activated PDSCH and the reception of DCI format 1_0 / 1_1 / 1_2, the terminal device 1 may operate in frequency range 1.

[0302] The terminal device 1 may set dl-OrJointTCI-StateList and maintain two indicated TCI-states. Regardless of the offset between the reception of a scheduled or activated PDSCH and the reception of DCI format 1_0 / 1_1 / 1_2, the terminal device 1 may report terminal capabilities of [two default beams for S-DCI based MTRP] in frequency range 2.

[0303] If the terminal device 1 does not report a certain terminal capability in a certain frequency domain, and the offset between the reception of a scheduled or activated PDSCH and the reception of DCI format 1_0 / 1_1 / 1_2 may be greater than [timeDurationForQCL].

[0304] The terminal device 1 may be configured by the upper layer parameter applyIndicatedTCIState. applyIndicatedTCIState may indicate whether the first, second, or both indicated TCI-states are applied to reception of an activated or scheduled PDSCH by DCI format 1_0. The terminal device 1 may be configured with cjtScheme. The terminal device 1 may be configured with sfnPDSCH. The terminal device 1 may report a certain terminal capability. A certain terminal capability may be [support for two joint TCI states for PDSCH-CJT]. A certain terminal capability may be the capability to support two joint TCIs for PDSCH-CJT. When the terminal device 1 is configured with cjtScheme and reports a certain terminal capability, the terminal device 1 may set only both values ​​in applyIndicatedTCIState. When the terminal device 1 is configured with sfnPDSCH, the terminal device 1 may set only both values ​​in applyIndicatedTCIState. If the terminal device 1 is configured with only both values, the terminal device 1 may apply to receive a PDSCH. The PDSCH may be a PDSCH scheduled or activated by DCI format 1_0. The DCI format 1_0 may be a DCI on a search space other than CORESET #0. The search space may be a search space other than Type0 / 0A / 2 CSS.

[0305] If the terminal device 1 is not configured with applyIndicatedTCIState, the first indicated TCI-state may be applied to the reception of a PDSCH 2. The PDSCH may be a PDSCH scheduled or activated by DCI format 1_0.

[0306] The terminal device 1 may be configured with tci-Selection-PresentInDCI. The configuration may be for both DCI formats, DCI format 1_1 and DCI format 1_2. The terminal device 1 may receive DCI format 1_1 / 1_2. DCI format 1_1 / 1_2 may schedule or activate a PDSCH. When the terminal device 1 is configured with tci-Selection-PresentInDCI and receives DCI format 1_1 / 1_2 that schedules or activates a PDSCH, the terminal device 1 may determine the indicated joint / downlink TCI state for receiving the PDSCH according to TCI selection method A.

[0307] In TCI selection method A, when DCI format 1_1 / 1_2 indicates a certain code point, the terminal device 1 may apply one of the two indicated joint / downlink TCI states to PDSCH reception. The certain code point may be "00". The certain code point may be "01". The certain code point may be "10". The certain code point may be "11". The certain code point may be for the TCI selection field. The application to PDSCH reception may be application to all PDSCH DMRS ports corresponding to PDSCH transmission opportunities. The PDSCH transmission opportunities may be PDSCH transmission opportunities scheduled or activated by DCI format 1_1 / 1_2. The certain TCI state may be the first TCI state. The certain TCI state may be the second TCI state. The certain TCI state may be both TCI states.

[0308] In TCI selection method A, when DCI format 1_1 / 1_2 indicates code point "00" for the [TCI selection field], the terminal device 1 may apply the first indicated joint / downlink TCI state of the two indicated joint / downlink TCI states to all PDSCH DMRS ports corresponding to PDSCH transmission opportunities activated or scheduled by DCI format 1_1 / 1_2.

[0309] In TCI selection method A, when DCI format 1_1 / 1_2 indicates code point "01" for the [TCI selection field], the terminal device 1 may apply the second indicated joint / downlink TCI state of the two indicated joint / downlink TCI states to all PDSCH DMRS ports corresponding to PDSCH transmission opportunities activated or scheduled by DCI format 1_1 / 1_2.

[0310] In TCI selection method A, when DCI format 1_1 / 1_2 indicates code point "10" for the [TCI selection field], the terminal device 1 may apply both of the two indicated joint / downlink TCI states to all PDSCH DMRS ports corresponding to PDSCH transmission opportunities activated or scheduled by DCI format 1_1 / 1_2.

[0311] If the terminal device 1 is not configured with tciSelection-PresentInDCI and receives DCI format 1_1 / 1_2, the terminal device 1 may apply both indicated TCI states to the reception of the PDSCH. The DCI format 1_1 / 1_2 may schedule or activate the reception of the PDSCH. The reception of the PDSCH may be scheduled or activated.

[0312] DCI format 1_1 / 1_2 may include a TCI selection field. The TCI selection field may be TCI selection information. The TCI selection information may be transmitted by means of DCI format 1_1 / 1_2. The number of bits for the TCI selection may be determined based on a higher layer parameter. The higher layer parameter may be tciSelection-PresentInDCI. If tciSelection-PresentInDCI is not configured, the TCI selection may be configured with 0 bits. If tciSelection-PresentInDCI is configured, the TCI selection may be configured with 2 bits. If asymmetricTRP is configured, the TCI selection may be configured with 2 bits. If asymmetricTRP is configured, the TCI selection may be configured with 1 bit. If asymmetricTRP is configured, the TCI selection may be configured with 0 bit. Configuring the asymmetricTRP may mean that the TCI selection is configured with at least 1 bit or less.

[0313] The terminal device 1 may be configured by the upper layer parameter repetitionScheme. The repetitionScheme may be set to any one of 'fdmSchemeA', 'fdmSchemeB', and 'tdmScheme'. A terminal device 1 that is not configured by dl-OrJointTCI-StateList may have two TCI states indicated by the codepoint of the DCI field 'TransmissionConfigurationIndication'. A terminal device 1 that is configured by dl-OrJointTCI-StateList may hold two indicated TCI states to be applied to the PDSCH. The terminal device 1 may be indicated by a DMRS port. The DMRS port may be a CDM group with the DCI field 'Anntena Port(s)'. The terminal device 1 may be indicated by a DMRS port of a CDM group with the DCI field 'Anntena Port(s)'.

[0314] The terminal device 1 may be set in 'fdmSchemeA'. The terminal device 1 may receive a single PDSCH transmission opportunity. The single PDSCH transmission opportunity may be a transmission opportunity for the TB in each TCI state. Each TCI state may be associated with a non-overlapping frequency domain resource allocation. When the terminal device 1 is set in 'fdmSchemeA', the terminal device 1 may receive a single PDSCH transmission opportunity for that TB in each TCI state associated with a non-overlapping frequency domain resource allocation.

[0315] The terminal device 1 may be set in 'fdmSchemeB'. The terminal device 1 may receive two PDSCH transmission opportunities. The two PDSCH transmission opportunities may be transmission opportunities of the same TB in each TCI state. Each TCI state may be associated with a PDSCH transmission opportunity. A PDSCH transmission opportunity may be associated with a frequency domain resource allocation that does not overlap with other PDSCH transmission opportunities. When the terminal device 1 is set in 'fdmSchemeB', the terminal device 1 may receive two PDSCH transmission opportunities of that TB in each TCI state that are associated with a PDSCH transmission opportunity that has a frequency domain resource allocation that does not overlap with other PDSCH transmission opportunities.

[0316] The terminal device 1 may be set in 'tdmSchemeA'. The terminal device 1 may receive two PDSCH transmission opportunities. The two PDSCH transmission opportunities may be transmission opportunities of the same TB in each TCI state. Each TCI state may be associated with a PDSCH transmission opportunity. One PDSCH transmission opportunity may have a non-overlapping time domain resource allocation with respect to the other PDSCH transmission opportunity. Both PDSCH transmission opportunities may be received in a given slot. When the terminal device 1 is set in 'tdmSchemeA', the terminal device 1 may receive two PDSCH transmission opportunities of that TB in each TCI state associated with a PDSCH transmission opportunity with a time domain resource allocation that does not overlap with the other PDSCH transmission opportunity.

[0317] The terminal device 1 receiving a PDSCH transmission opportunity may be receiving a PDSCH by the terminal device 1. The PDSCH may be transmitting a PDSCH.

[0318] The terminal device 1 may be configured with the higher layer parameter repetitionNumber. The terminal device 1 may be configured with the higher layer parameter repetitionNumber in PDSCH-TimeDomainResourceAllocation. If not configured in dl-OrJointTCI-StateList, the terminal device 1 may expect one or two TCI states to be indicated in the codepoint of the DCI field 'Transmission Configuration Indication'. If configured in dl-OrJointTCI-StateList, the terminal device 1 may expect one or two indicated TCI states to be applied to the PDSCH. The DCI field may be 'Time domain resource assignment'. The DCI field 'Time domain resource assignment' may indicate an entry. An entry may include the repetitionNumber in PDSCH-TimeDomainResourceAllocation. The DMRS port may be a CDM group with the DCI field 'Antenna Port(s)'.

[0319] When two TCI states are indicated in the 'Transmission Configuration Indication' of the DCI for a terminal device 1 that is not configured in dl-OrJointTCI-StateList, or when the terminal device 1 that is configured in dl-OrJointTCI-StateList maintains the two indicated TCI states that apply to the PDSCH, the terminal device 1 may expect to receive PDSCH transmission opportunities at multiple slot levels. The PDSCH transmission opportunities may be of the same TB. The terminal device 1 may receive in two TCI states. The two TCI states may be used across multiple PDSCH transmission opportunities in repetitionNumber consecutive slots. The terminal device 1 may expect to receive PDSCH transmission opportunities at multiple slot levels of the same TB in two TCIs. The two TCI states may be used across multiple PDSCH transmission opportunities in repetitionNumber consecutive slots.

[0320] When one TCI state is indicated in the 'Transmission Configuration Indication' of the DCI for a terminal device 1 that is not set in the dl-OrJointTCI-StateList, or when the terminal device 1 that is set in the dl-OrJointTCI-StateList holds one indicated TCI state that applies to the PDSCH, the terminal device 1 may expect to receive PDSCH transmission opportunities at multiple slot levels. When one TCI state is indicated in the 'Transmission Configuration Indication' of the DCI for a terminal device 1 that is not set in the dl-OrJointTCI-StateList, or when the terminal device 1 that is set in the dl-OrJointTCI-StateList holds one indicated TCI state that applies to the PDSCH, the terminal device 1 may expect to receive PDSCH transmission opportunities in one TCI state at multiple slot levels. That one TCI state may be used across multiple PDSCH transmission opportunities in repetitionNumber consecutive slots.

[0321] The terminal device 1 may not be indicated by a DCI in the DCI field 'Time domain resource assignment' indicating an entry including the repetitionNumber. It may be indicated by two TCI states in the codepoint of the DCI field 'Transmission Configuration Indication' for the terminal device 1 that is not configured in the dl-OrJointTCI-StateList. The terminal device 1 that is configured in the dl-OrJointTCI-StateList may hold two indicated TCI states that apply to the PDSCH. The terminal device 1 may be indicated by the DMRS ports of the two CDM groups in the DCI field 'Antenna Port(s)'. It may not be configured in the upper layer parameter sfnSchemePDSCH. The terminal device 1 may expect to receive one PDSCH.

[0322] The terminal device 1 may be configured with inter-slot repetition. The configuration of inter-slot repetition may be indicated by the DCI field 'Time domain resource assignment' indicating an entry including repetitionNumber in PDSCH-TimeDomainResourceAllocation. When inter-slot repetition is not configured for the terminal device 1, and the terminal device 1 is not configured in dl-OrJointTCI-StateList, and is indicated in one TCI state of the codepoint of the DCI field 'Transmission Configuration Indication', the terminal device 1 may follow a certain procedure for receiving a PDSCH upon detection of a PDCCH. When inter-slot repetition is not configured for the terminal device 1, and the terminal device 1 is configured in dl-OrJointTCI-StateList, and the terminal device 1 is expected to apply one indicated TCI state to the PDSCH, the terminal device 1 may follow a certain procedure for receiving a PDSCH upon detection of a PDCCH.

[0323] Terminal device 1 may be configured with the upper layer parameter sfnSchemePDSCH. The upper layer parameter sfnSchemePDSCH may be set with sfnSchemeA or sfnSchemeB. Terminal device 1 may report a certain terminal capability. The certain terminal capability may be sfn-SchemeA-DynamicSwitching. The certain terminal capability may be sfn-SchemeB-DynamicSwitching. When terminal device 1 is configured with the upper layer parameter sfnSchemePDSCH set with sfnSchemeA or sfnSchemeB, and if terminal device 1 reports a certain terminal capability that is not set in dl-OrJointTCI-StateList, terminal device 1 may be indicated with one or two TCI states by the codepoint of the DCI field 'Transmission Configuration Indication' of DCI format 1_1 / 1_2. When the terminal device 1 is configured with the upper layer parameter sfnSchemePDSCH set in sfnSchemeA or sfnSchemeB, and when the terminal device 1 reports certain terminal capabilities, the terminal device 1 may maintain one or two indicated TCI states applied to the PDSCH, set in dl-OrJointTCI-StateList.

[0324] Terminal device 1 may be configured with the upper layer parameter sfnSchemePDSCH. The upper layer parameter sfnSchemePDSCH may be set with sfnSchemeA or sfnSchemeB. Terminal device 1 may report a certain terminal capability. The certain terminal capability may be sfn-SchemeA-DynamicSwitching. The certain terminal capability may be sfn-SchemeB-DynamicSwitching. When terminal device 1 is configured with the upper layer parameter sfnSchemePDSCH set with sfnSchemeA or sfnSchemeB, and if terminal device 1 does not report a certain terminal capability, not configured with dl-OrJointTCI-StateList, terminal device 1 may not be expected to be indicated in one TCI state at any codepoint by MACCE. When the terminal device 1 is configured with the upper layer parameter sfnSchemePDSCH set in sfnSchemeA or sfnSchemeB, and if the terminal device 1 does not report a certain terminal capability, the terminal device 1 may maintain two indicated TCI states that apply to the PDSCH, as set in dl-OrJointTCI-StateList.

[0325] When the terminal device 1 is configured with both sfnSchemePDSCH and sfnSchemePDCCH, the terminal device 1 may expect that the sfnSchemePDSCH and sfnSchemePDCCH are set in the same manner, which may be 'sfnSchemeA' or 'sfnSchemeB'.

[0326] If a terminal device 1 that is not configured in dl-OrJointTCI-StateList is configured with sfnSchemePDCCH set to 'sfnSchemeA' and activated in two TCI states by MACCE, and if the terminal device 1 does not report a certain terminal capability, the terminal device 1 may be expected to be configured with sfnSchemePDCCH set to 'sfnSchemeA' and may be expected to be indicated in two TCI states by the codepoint of the DCI field 'Transmission Configuration Indication'. A certain terminal capability may be a terminal capability for supporting higher layer parameters set in 'sfnSchemeA' for PDCCH only. A certain terminal capability may be sfn-SchemeA-PDCCH-only.

[0327] If a terminal device 1 configured in dl-OrJointTCI-StateList and holding two indicated TCI states is configured with sfnSchemePdcch set to 'sfnSchemeA' and is signaled by the upper layer parameter applyIndicatedTCIState to apply both indicated TCI states to the PDCCH on CORESET, and if the terminal device 1 does not report a certain terminal capability, the terminal device 1 may expect to be configured with sfnSchemePdsch set to 'sfnSchemeA' and the terminal device 1 may expect to apply both indicated TCI states to the PDSCH.

[0328] If a terminal device 1 that is not configured in dl-OrJointTCI-StateList is configured with sfnSchemePDCCH set to 'sfnSchemeB' and is activated in two TCI states by MACCE, the terminal device 1 may be expected to be configured with sfnSchemePDSCH set to 'sfnSchemeB' and may be expected to be indicated in two TCI states by the codepoint of the DCI field 'Transmission Configuration Indication'.

[0329] If a terminal device 1 configured in dl-OrJointTCI-StateList and holding two indicated TCI states is configured with sfnSchemePDCCH set to sfnSchemeB' and is signaled by the upper layer parameter applyIndicatedTCIState to apply both indicated TCI states to the PDCCH on CORESET, then the terminal device 1 may be expected to be configured with sfnSchemePdsch set to 'sfnSchemeB' and may expect both indicated TCI states to be applied to the PDSCH.

[0330] The terminal device 1 may be configured with a list of up to M TCI-UL-State configurations. M may be 64. The TCI-UL-State may be configured in the higher layer parameter BWP-UplinkDedicated. Each TCI-UL-State may include certain parameters. A parameter may be a parameter for one reference signal. If applicable, a parameter may be a parameter for determining uplink spatial filters for PUSCH, PUCCH, and SRS.

[0331] The terminal device 1 may be configured by the higher layer parameter PDCCH-Config. The PDCCH-Config may include ControlResourceSets of two different values ​​of coresetPoolIndex for an active BWP of a serving cell. The terminal device 1 may be configured with SSB-MTC-AdditionalPCI. The terminal device 1 may be configured with twoTAGs. Each TCI-State, TCI-UL-State may be associated with a TAG-ID for determining timing adjustment to accommodate uplink transmission. The terminal device 1 may expect the TCI-state or TCI-UL-State associated with coresetPoolIndex to correspond to two TAGs.

[0332] When the terminal device 1 is configured in dl-OrJointTCI-StateList or in ul-TCI-SateList, the terminal device 1 may perform PUSCH transmission according to a certain spatial relationship. The certain space may refer to a reference signal for determining an uplink spatial filter. The reference signal may be based on a reference signal configured in qcl-Type set to 'Type D'. The reference signal may be based on the indicated TCI-UL-State or TCI-State. The reference reference signal in the indicated TCI-State may be a CSI-RS resource in the NZP-CSI-RS-resourceSet configured in the higher layer parameter repetition. The reference reference signal in the indicated TCI-UL-State may be a CSI-RS resource in the NZP-CSI-RS-resourceSet configured in the higher layer parameter trs-Info. The reference signal in the indicated TCI-UL-State may be a CSI-RS resource in the NZP-CSI-RS-resourceSet configured by the higher layer parameter "repetition". The reference signal in the indicated TCI-State may be a CSI-RS resource in the NZP-CSI-RS-resourceSet configured by the higher layer parameter "trs-Info". The reference signal in the indicated TCI-UL-State may be an SRS resource in the SRS resource set configured by the higher layer parameter "usage" set in "beamManagement". The reference signal in the indicated TCI-State may be an SSB associated with a PCI different from or the same as the PCI of the serving cell. The SRS resource set may configure one or more SRS resources.

[0333] When a terminal device 1 is configured with dl-OrJointTCI-StateList or TCI-UL-State and holds two indicated TCI-States or TCI-UL-States, a terminal device 1 with a PUSCH transmission scheduled or activated by DCI format 0_0 may apply the first indicated TCI state to the PUSCH transmission.

[0334] When the terminal device 1 is configured with dl-OrJointTCI-StateList or TCI-UL-State and holds two indicated TCI-States or TCI-UL-States, the terminal device 1 configured with PUSCH transmission corresponding to Type1 configuration grant 2 may be expected to be configured with the upper layer parameter applyIndicatedTCIState. applyIndicatedTCIState may indicate the first, second, or both indicated TCI states to apply to PUSCH transmission opportunities. If both TCI states are indicated, the terminal device 1 may apply the first indicated TCI state to the PUSCH transmission opportunity or to the PUSCH antenna port associated with the first SRS resource set. If both TCI states are indicated, the terminal device 1 may apply the second indicated TCI state to the PUSCH transmission opportunity or to the PUSCH antenna port associated with the second SRS resource set. If a TCI state other than both is indicated, the terminal device may apply the first or second indicated TCI state to all PUSCH transmission opportunities.

[0335] If the terminal device 1 is configured by an upper layer parameter PDCCH-Config that includes two different values ​​of coresetPoolIndex in different ControlResourceSets, the first and second TCI states may correspond to the indicated TCI-State or TCI-UL-States, respectively, specific to the value of coresetPoolIndex, 0 or 1. If the terminal device 1 is configured by an upper layer parameter PDCCH-Config that includes two different values ​​of coresetPoolIndex in different ControlResourceSets, applyIndicatedTCIState may not indicate both of the indicated TCI states to be applied for PUSCH transmission.

[0336] A terminal device 1 may be configured with two uplinks on a serving cell. For a terminal device 1 configured with two uplinks on a serving cell, PUSCH retransmissions for a TB on the serving cell may not be expected to be on an uplink different from the uplink used for the initial PUSCH transmission of that TB.

[0337] A PDCCH may schedule two PUSCHs. The PDCCHs that schedule two PUSCHs may be associated with different ControlResourceSets. The PDCCHs may be associated with different ControlResourceSets with different coresetPoolIndex values. A terminal device 1 may have two HARQ process IDs in a given scheduled cell. The terminal device 1 may be configured by a higher layer parameter PDCCH-Config that includes two different values ​​of coresetPoolIndex in a ControlResourceSet for an active BWP. The terminal device 1 may be scheduled by a PDCCH associated with a value of coresetPoolIndex ending with symbol i. The terminal device 1 may be scheduled for a first PUSCH transmission starting with symbol j by a PDCCH associated with a value of coresetPoolIndex ending with symbol i. The terminal device 1 may be scheduled to start a first PUSCH transmission starting with symbol j by a PDCCH associated with a value of coresetPoolIndex ending with symbol i. Terminal device 1 may be scheduled by a PDCCH associated with a different coresetPoolIndex value that ends later than symbol i. Terminal device 1 may be scheduled to transmit a PUSCH by a PDCCH associated with a different coresetPoolIndex value that ends later than symbol i. The PUSCH may be a PUSCH that starts earlier than the end of the first PUSCH transmission. Terminal device 1 may be scheduled to transmit a PUSCH that starts earlier than the end of the first PUSCH transmission by a PDCCH associated with a different coresetPoolIndex value that ends later than symbol i.If the terminal device 1 is configured by the upper layer parameter PDCCH-Config, which includes two different values ​​of coresetPoolIndex in the ControlResourceSet for the active BWP, and the PDCCHs that schedule two PUSCHs are associated with different ControlResourceSets with different coresetPoolIndex values, then for some two HARQ process IDs, if the terminal device 1 is scheduled to start the first PUSCH transmission starting at symbol j by a PDCCH associated with a value of coresetPoolIndex that ends at symbol i, the terminal device 1 may be scheduled to transmit a PUSCH that starts earlier than the end of the first PUSCH transmission by a PDCCH associated with a different value of coresetPoolIndex that ends later than symbol i.

[0338] Two SRS resource sets may be configured with srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2. Two SRS resource sets may be configured with srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with the higher layer parameter usage in which the SRS resource set is set as 'codebook' or 'nonCodebook'. The higher layer parameter enableSTx2PofmDCI may be set. The PDCCH-Config may contain two different values ​​of coresetPoolIndex in the ControlResourceSet for the active BWP of a serving cell. Operation 1 may be performed when two SRS resource sets are configured by the higher layer parameter srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 in the SRS resource set set to 'codebook' or 'nonCodebook', the higher layer parameter enableSTx2PofmDCI is configured, and the PDCCH-Config includes two different values ​​of coresetPoolIndex in the ControlResourceSet for an active BWP of a serving cell. Operation 1 may be performed when two PUSCHs partially / completely overlap in the time domain. Operation 1 may be performed when two PUSCHs partially / completely overlap in the frequency domain or do not overlap in the frequency domain. Operation 1 may be performed when two PUSCHs partially / completely overlap in the time domain and partially / completely overlap in the frequency domain or do not overlap in the frequency domain, and are dynamically scheduled by the uplink grant of DCI. Action 1 may be that the two PUSCHs are partially / completely overlapping in the frequency domain, or are non-overlapping in the frequency domain.In operation 1, two PUSCHs that partially / fully overlap in the time domain and partially / fully overlap in the frequency domain or do not overlap in the frequency domain may be scheduled by a configured grant. In operation 1, if dynamically scheduled by an uplink grant of a DCI or activated by a DCI for a configured grant, the SRS Resource Set Indicator of the DCI field may not be present in each PDCCH. In operation 1, the terminal device 1 may not expect different numbers of SRS resources to be configured in the two SRS resource sets. In operation 1, if an uplink PTRS is configured, the terminal device 1 may expect maxNrofPorts in PTRS-UplinkConfig to be set to 1.

[0339] Two SRS resource sets may be configured by srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2. The upper layer parameter usage within the SRS resource set may be set to 'codebook' or 'noncodebook'. Two SRS resource sets may be configured with the upper layer parameter usage within the SRS resource set set to 'codebook' or 'noncodebook'. Two SRS resource sets may be configured by srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with the upper layer parameter usage within the SRS resource set set to 'codebook' or 'noncodebook'. The upper layer parameter multipanelScheme may be set to 'SDMscheme' or 'SFNscheme'. The higher layer parameter rrc-ConfiguredUplinkGrant may not include srs-ResourceIndicator2 or precodingAndNumberOfLayers2. If the first indicated TCI-State or TCI-UL-State applies, the PUSCH transmission opportunity may be associated with the first SRS resource set. If the second indicated TCI-State or TCI-UL-State applies, the PUSCH transmission opportunity may be associated with the second SRS resource set.When the terminal device 1 is configured with dl-OrJointTCI-StateList or TCI-UL-State, and the upper layer parameter usage of the SRS resource set is set to 'codebook' or 'noncodebook', when two SRS resource sets are configured with srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, and the upper layer parameter multipanelScheme is set to 'SDMscheme' or 'SFNscheme'. When the rrc-ConfiguredUplinkGrant parameter is set to 0, and the higher layer parameter rrc-ConfiguredUplinkGrant does not include srs-ResourceIndicator2 or precodingAndNumberOfLayers2, if the first indicated TCI-State or TCI-UL-State applies, the PUSCH transmission opportunity may be associated with the first SRS resource set, and if the second indicated TCI-State or TCI-UL-State applies, the PUSCH transmission opportunity may be associated with the second SRS resource set.

[0340] Only one SRS resource set may be configured by srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2. The upper layer parameter "usage" within an SRS resource set may be set to 'codebook' or 'noncodebook'. Only one SRS resource set may be configured with the upper layer parameter "usage" set to 'codebook' or 'noncodebook' within an SRS resource set. Only one SRS resource set may be configured by srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with the upper layer parameter "usage" set to 'codebook' or 'noncodebook' within an SRS resource set. A PUSCH transmission opportunity may be scheduled or activated by DCI format 0_1 ​​or DCI format 0_2. A PUSCH transmission opportunity may be associated with the first indicated TCI state or TCI-UL-States. The PUSCH transmission opportunity may be associated with the second indicated TCI state or TCI-UL-States. The upper layer parameter applyIndicatedTCIState-r18 may be set by PUSCH-Config. The PUSCH transmission opportunity may be associated with the first indicated TCI state or TCI-UL-States as indicated by the upper layer parameter applyIndicatedTCIState-r18 set by PUSCH-Config. The PUSCH transmission opportunity may be associated with the second indicated TCI state or TCI-UL-States as indicated by the upper layer parameter applyIndicatedTCIState-r18 set by PUSCH-Config. If asymmetricTRP is configured, the upper layer parameter applyIndicatedTCIState-r18 set by PUSCH-Config may only be set to both.

[0341] The terminal device 1 may be configured with the higher layer parameter enableSTx2PofmDCI. The terminal device 1 may be configured with the higher layer parameter PDCCH-Config. The PDCCH-Config may include two different coresetPoolIndex values ​​in the ControlResourceSet for an active BWP of a serving cell. The terminal device 1 may expect to be configured with two SRS resource sets. The terminal device 1 may expect to be configured with two SRS resource sets with usage 'codebook' or 'nonCodebook' in srs-ResourceSetToAddModList. When the terminal device 1 is configured with the higher layer parameter enableSTx2PofmDCI and when the terminal device 1 is configured with the higher layer parameter PDCCH-Config, the terminal device 1 may expect to be configured with two SRS resource sets with usage 'codebook' or 'nonCodebook' in srs-ResourceSetToAddModList. The PDCCH-Config may include two different coresetPoolIndex values ​​in the ControlResourceSet for an active BWP of a serving cell. The terminal device 1 may be configured to search for DCI format 0_2. Only one SRS resource set may be configured in srs-ResourceSetToAddModListDCI-0-2. There may be an srs-ResourceSetToAddModListDCI-0-2 in which only one SRS resource set is configured. The SRS resource set may be of usage 'codebook' or 'nonCodebook'.When the terminal device 1 is configured with the upper layer parameter enableSTx2PofmDCI, and when the terminal device 1 is configured with the upper layer parameter PDCCH-Config, which includes two different coresetPoolIndex values ​​in the ControlResourceSet for the active BWP of a serving cell, if it is configured to search DCI format 0_2 and only one SRS resource set is configured with srs-ResourceSetToAddModListDCI-0-2 and associated with usage 'codebook' or 'nonCodebook', the terminal device 1 may only search for CORESETs associated with coresetPoolIndex value 0.

[0342] The SRS resource set indicator may be 0 bit or 2 bits. The SRS resource set may indicate a first value. When the first value indicates 0, the SRI, precoding information, and number of layers may be associated with the first SRS resource set. When the first value indicates 0, the second SRI, second precoding information, and number of layers may be reserved. When the first value indicates 0, if there are two indicated TCI states, the first indicated TCI state may be applied to the corresponding PUSCH transmission opportunity. When the first value indicates 1, the SRI, precoding information, and number of layers may be associated with the second SRS resource set. When the first value indicates 1, the second SRI, second precoding information, and number of layers may be reserved. When the first value indicates 1, if there are two indicated TCI states, the second indicated TCI state may be applied to the corresponding PUSCH transmission opportunity. When the first value indicates 2, the SRI, precoding information, and number of layers may be associated with the first SRS resource set. When the first value indicates 2, a second SRI, second Precoding information, and number of layers may be associated with a second SRS resource set. When the first value indicates 2, if there are two indicated TCI states, the first indicated TCI state may be applied to a PUSCH transmission opportunity / antenna port associated with the first SRS resource set. When the first value indicates 2, if there are two indicated TCI states, the second indicated TCI state may be applied to a PUSCH transmission opportunity / antenna port associated with the second SRS resource set. When the first value indicates 3, if multipanelScheme is configured, the first value may be reserved. The first value may be a codepoint of an SRS resource set indicator.

[0343] The upper layer parameter multipanelScheme may be set to 'SDMScheme'. When the upper layer parameter multipanelScheme is set to 'SDMScheme' and two SRS resource sets are configured in the list, two SRIs and two TPMIs may be provided by the two SRS resource set indicator DCI fields and two Precoding information and number of layers DCI fields. The codepoint of the SRS resource set indicator may be indicated by '10'. When the codepoint of the SRS resource set indicator is indicated by '10', the first TPMI may be used to indicate a precoder. The precoder may be applied across a first number of layers. The first number of layers may be indicated by the first TPMI. The first TPMI may correspond to the SRS resource selected by the corresponding SRI. The second TPMI may be used to indicate a precoder. The precoder may be applied across a second number of layers. The second number of layers may be indicated by the second TPMI. The second TPMI may correspond to the SRS resource selected by the corresponding SRI. The first layer number may be less than or equal to maxRankSdm or maxRankSdmDCI-0-2. The second layer number may be less than or equal to maxRankSdm or maxRankSdmDCI-0-2. maxRankSdm or maxRankSdmDCI-0-2 may define the maximum number of layers applied across the first and second SRS resource sets, respectively. The SRS resource set indicator codepoint '00' or '01' may be indicated. When the SRS resource set indicator codepoint '00' or '01' is indicated, the second SRI and the second TPMI may be reserved. When the SRS resource set indicator codepoint '00' or '01' is indicated, the first TPMI may be used to indicate a precoder. The precoder may be applied across the third layer number.The number of third layers may be less than or equal to maxRank, which may define the maximum number of layers. When the upper layer parameter multipanelScheme is set to 'SDMScheme' and two SRS resource sets are configured in the list, the code point '11' for the SRS resource set indicator may be reserved.

[0344] The upper layer parameter multipanelScheme may be set to 'SFNScheme'. When the upper layer parameter multipanelScheme is set to 'SFNScheme' and two SRS resource sets are configured in the list, two SRIs and two TPMIs may be provided by the two SRS resource set indicator and two DCI fields for Precoding information and number of layers. When the SRS resource set indicator codepoint is set to '10', the first TPMI may be used to indicate a precoder. The precoder may be applied across a fourth number of layers. The second TPMI may be used to indicate a precoder. The precoder may be applied across a fourth number of layers. The fourth number of layers may be less than or equal to maxRankSfn or maxRankSfnDCI-0-2. maxRankSfn or maxRankSfnDCI-0-2 may define the maximum number of layers applied across the first SRS resource set and the maximum number of layers applied across the second SRS resource set, respectively. When the codepoint '00' or '01' in the SRS resource set indicator is indicated, the second SRI and the second TPMI may be reserved. When the codepoint '00' or '01' in the SRS resource set indicator is indicated, the first TPMI may be used to indicate a precoder. The precoder may be applied across a fifth layer. The number of fifth layers may be less than or equal to maxRank. maxRank may define the maximum number of layers applied across the first SRS resource set or the second SRS resource set. The upper layer parameter multipanelScheme may be set to 'SFNScheme'. When the upper layer parameter multipanelScheme is set to 'SFNScheme' and two SRS resource sets are configured in the list, the code point '11' of the SRS resource set indicator may be reserved.

[0345] The PUSCH may be restricted by one layer. For PUSCH repetition Type A, if K is greater than 1, the same symbol allocation may be applied to K consecutive slots. When two SRS resource sets are configured in a list with the upper layer parameter usage 'codebook' or 'nonCodebook', for PUSCH repetition Type A, if K is greater than 1, the same symbol allocation may be applied to K consecutive slots, and the PUSCH may be restricted by one layer. The terminal device 1 may repeat the TB over K consecutive slots. The same symbol allocation may be applied to each of the K consecutive slots. The association of the first and second SRS resource sets in the list to each slot may be determined according to a repetition rule. In the repetition rule, if DCI format 0_3 schedules the PUSCH, the first SRS resource set may be associated with all K consecutive slots. In the repetition rule, if DCI format 0_1 ​​or DCI format 0_2 indicates '00' for the SRS resource set indicator, the first SRS resource set may be associated with all K consecutive slots. In the repetition rule, if DCI format 0_1 ​​or DCI format 0_2 indicates '01' for the SRS resource set indicator, the second SRS resource set may be associated with all K consecutive slots. In the repetition rule, if DCI format 0_1 ​​or DCI format 0_2 indicates '10' for the SRS resource set indicator, the association of the first and second SRS resource sets to the K consecutive slots may be determined according to repetition mapping rule 1. In repetition mapping rule 1, when K=2, the first and second SRS resource sets may be applied to the first and second slots of two consecutive slots, respectively.In repetition mapping rule 1, when K>2 and cyclicMapping is enabled in the PUSCH-Config, the first and second SRS resource sets may be applied to the first and second slots of K consecutive slots, respectively. In repetition mapping rule 1, when K>2 and cyclicMapping is enabled in the PUSCH-Config, the first and second SRS resource sets may be applied to the first and second slots of K consecutive slots, respectively, and the same SRS resource set mapping pattern may be continued for the remaining slots of the K consecutive slots. In repetition mapping rule 1, when K>2 and sequentialMapping is enabled in PUSCH-Config, the first SRS resource set may be applied to the first and second slots of K consecutive slots, and the second SRS resource set may be applied to the third and fourth slots of K consecutive slots, and the same SRS resource set mapping pattern may be continued for the remaining slots of K consecutive slots. In the repetition rule, if DCI format 0_1 ​​or DCI format 0_2 indicates '11' for the SRS resource set indicator, the association of the first and second SRS resource sets to K consecutive slots may be determined according to repetition mapping rule 2. In repetition mapping rule 2, when K=2, the second and first SRS resource sets may be applied to the first and second slots of two consecutive slots, respectively. In repetition mapping rule 2, when K>2 and cyclicMapping in PUSCH-Config is enabled, the second and first SRS resource sets may be applied to the first and second slots of K consecutive slots, respectively, and the same SRS resource set mapping pattern may continue to the remaining slots of the K consecutive slots.In repetition mapping rule 2, when K>2 and sequentialMapping in PUSCH-Config is enabled, the second SRS resource set may be applied to the first and second slots of K consecutive slots, and the first SRS resource set may be applied to the third and fourth slots of K consecutive slots, and the same SRS resource set mapping pattern may continue for the remaining slots of the K consecutive slots.

[0346] Two SRS resource sets may be configured in the list for PUSCH repetition Type B. When two SRS resource sets are configured in the list for PUSCH repetition Type B with the upper layer parameter usage of the SRS resource set being 'codebook' or 'nonCodebook', the association of the SRS resource set to the nominal PUSCH repetition may follow the same as the association of the SRS resource set to the slot for PUSCH repetition Type A, by considering the nominal repetition instead of the slot.

[0347] When the terminal device 1 is configured with dl-OrJointTCI-StateList or TCI-UL-State and holds two TCI-states or TCI-UL-States, and the upper layer parameter usage is set to 'codebook' or 'nonCodebook' in the SRS resource set, and two SRS resource sets are configured in the list, for PUSCH repetition Type A or Type B, or when the upper layer parameter multipanelScheme is set to 'SDMScheme' or 'SFNScheme', the association of the first and second indicated TCI states to PUSCH transmission opportunities or to corresponding antenna ports may be determined according to repetition rule 2. In repetition rule 2, if DCI format 0_1 ​​or DCI format 0_2 indicates codepoint '00' or '01' for the SRS resource set indicator, the first or second indicated TCI state may be applied to all PUSCH transmission opportunities, respectively. In repetition rule 2, if DCI format 0_1 ​​or DCI format 0_2 indicates codepoint '10' or '11' for the SRS resource set indicator and multipanelScheme is not configured, the first indicated TCI state may be applied to PUSCH transmission opportunities associated with the first SRS resource set, and the second indicated TCI state may be applied to PUSCH transmission opportunities associated with the second SRS resource set. The association of PUSCH transmission opportunities to the SRS resource sets may be determined for K=2 or K>2 and may be determined based on repetition mapping rule 1 or 2, depending on whether cyclicMapping or sequentialMapping is enabled.In repetition rule 2, if DCI format 0_1 ​​or DCI format 0_2 indicates codepoint '10' for the SRS resource set indicator, and if multipanelScheme is configured, and if multipanelScheme is set to 'SDMScheme' or 'SFNScheme', the first indicated TCI state may be applied to the PUSCH antenna port. That PUSCH antenna port may be the antenna port of the corresponding PUSCH transmission opportunity. That PUSCH transmission opportunity may be associated with the first SRS resource set. In repetition rule 2, if DCI format 0_1 ​​or DCI format 0_2 indicates codepoint '10' for the SRS resource set indicator, and if multipanelScheme is configured, and if multipanelScheme is set to 'SDMScheme' or 'SFNScheme', the second indicated TCI state may be applied to the PUSCH antenna port. The PUSCH antenna port may be the antenna port of a corresponding PUSCH transmission opportunity, which may be associated with a second SRS resource set.

[0348] The terminal device 1 may be configured with a unified TCI state. Configuring the unified TCI state may mean configuring the dl-OrJointTCI-StateList. Configuring the unified TCI state may mean configuring the ul-TCI-StateList. Configuring the unified TCI state may mean configuring the dl-OrJointTCI-StateList for the downlink and configuring the ul-TCI-StateList for the uplink. Configuring the unified TCI state may mean configuring the dl-OrJointTCI-StateList or the ul-TCI-StateList. Configuring the unified TCI state may mean providing the TCI-State or the TCI-UL-State in the dl-OrJointTCI-StateList.

[0349] The terminal device 1 may be provided with a TCI-State or a TCI-UL-State in the dl-OrJointTCI-StateList. When the TCI-State or the TCI-UL-State in the dl-OrJointTCI-StateList is provided, the terminal device 1 may be provided with a reference signal index for each of the indicated one or two TCI states of the uplink physical channel. When the unified TCI state is configured, a reference signal index may be provided for each of the one or two TCI states. For example, when the asymmetric TRP is not configured and the unified TCI state is configured, one reference signal index may be provided for each of the one or two TCI states. For example, when the asymmetric TRP is configured and the unified TCI state is configured, one reference signal index may be provided for each of the one or two TCI states. Setting the unified TCI state may mean that the TCI-State or the TCI-UL-State in the dl-OrJointTCI-StateList is provided. The reference signal index may be an index for obtaining a downlink path loss estimate for the uplink channel. The reference signal index may be provided by a higher layer parameter. The higher layer parameter may be included in the indicated TCI-State or TCI-UL-State. The higher layer parameter may be associated with the indicated TCI-State or TCI-UL-State. The reference signal index may be provided by a higher layer parameter included in the indicated TCI-state or TCI-UL-State. The reference signal index may be provided by a higher layer parameter associated with the indicated TCI-state or TCI-UL-State. The higher layer parameter may be pathlossReferenceRS-Id-r17. The higher layer parameter may be pathlossReferenceRS-Id-r19.pathlossReferenceRS-Id-r19 may be the ID of the referenced path loss reference signal for asymmetricTRP. p0AlphaSetforPUSCH, if provided, P. O_UE_PUSCH,b,f,c (j), α b,f,c The value of (j) and the PUSCH power control adjustment l may be provided by p0AlphaSetforPUSCH associated with the indicated TCI-State or TCI-UL-State.

[0350] The terminal device 1 may be instructed to be in a first TCI-State or TCI-UL-State and a second TCI-State or TCI-UL-State. The terminal device 1 may be configured with a multipanelScheme. If the terminal device 1 is instructed to be in a first TCI-State or TCI-UL-State and a second TCI-State or TCI-UL-State, and if a multipanelScheme is configured, and if the terminal device 1 determines to apply both the first TCI-State or TCI-UL-State and the second TCI-State or TCI-UL-State to a PUSCH transmission opportunity, the terminal device 1 may determine the PUSCH transmission power for the kth instructed TCI-State or TCI-UL-State. The PUSCH transmission power is P PUSCH,b,f,c,k (i,j,q d, l) may also be used. PUSCH,b,f,c,k (i,j,q d, l) may be determined according to Equation 1. i may be a transmission opportunity for the PUSCH.

[0351] The terminal device 1 transmits the PUSCH with a transmission power of P PUSCH,b,f,c (i,j,q d,l) may be determined at the PUSCH transmission opportunity i. If the terminal device 1 is not instructed to apply the first TCI-State or TCI-UL-State and the second TCI-State or TCI-UL-State, or if the multipanelScheme is not configured, or if the terminal device 1 does not determine to apply both the first TCI-State or TCI-UL-State and the second TCI-State or TCI-UL-State to the PUSCH transmission opportunity, the terminal device 1 determines the PUSCH transmission power P PUSCH,b,f,c (i,j,q d, l) may be determined at PUSCH transmission opportunity i. PUSCH,b,f,c (i,j,q d, l) may be determined by Equation 2.

[0352] P CMAX,f,c,k (i) may be the maximum output power configured in the terminal for the kth indicated TCI-State or TCI-UL-State for the PUSCH transmission opportunity, for carrier f of serving cell c. P CMAX,f,c (i) may be the maximum output power configured in the terminal for carrier f of serving cell c for a PUSCH transmission opportunity.

[0353] P O_PUSCH,b,f,c (j) is the sum of PO_NOMINAL,PUSCH,b,f,c(j) and P O_UE_PUSCH,b,f,c (j), where j may be in the range {0, 1..., J-1}.

[0354] M PUSCH RB,b,f,c (i) may be the bandwidth of the PUSCH resource allocation. M PUSCH RB,b,f,c (i) may be the bandwidth of the PUSCH resource allocation expressed in resource blocks. M PUSCH RB,b,f,c (i) may be the bandwidth of the PUSCH resource allocation in PUSCH transmission opportunity i for PUSCH transmission opportunity i of the active ULBWP b of carrier f of serving cell c, expressed in resource blocks.

[0355] PL b,f,c- (q d ) may be the estimated downlink path loss in dB calculated by the terminal device 1. d may be a reference signal index for an active DLBWP of carrier f of serving cell c. The terminal device 1 may not be provided with PUSCH-PathlossReferenceRS. The terminal device 1 may not be provided with enableDefaultBeamPL-ForSRS. PUSCH-PathlossReferenceRS may be configured in a list. The list may be pathlossReferenceRSToAddModList. pathlossReferenceRSToAddModList may be a set of reference signals used for PUSCH path loss estimation. enableDefaultBeamPL-ForSRS may be configured only for FR2. enableDefaultBeamPL-ForSRS may be a parameter for the terminal device 1 to derive a path loss reference signal corresponding to a spatial relationship.

[0356] The terminal device 1 may be provided with PUSCH-PathlossReferenceRS. The terminal device 1 may be configured with the number of RS indices. This number may be up to the value of maxNrofPUSCH-PathlossReferenceRSs. The terminal device 1 may be configured with each of a set of RS configurations for the number of RS resources indexed by PUSCH-PathlossReferenceRS. The set of RS resource indices may include a set of SSB indices. The set of RS resource indices may include a set of CSI-RS resource indices. The terminal device 1 may be configured with PUSCH-PathlossReferenceRS up to the value of maxNrofPUSCH-PathlossReferenceRSs. PUSCH-PathlossReferenceRS may include an SSB index or a CSI-RS index. The terminal device 1 may assign q to either the SSB index or the CSI-RS index provided by pusch-PathlossReferenceRS-Id in PUSCH-PathlossReferenceRS. d It may be defined that

[0357] The terminal device 1 may be provided with SRI-PUSCH-PowerControl. The terminal device 1 may be provided with multiple PUSCH-PathlossReferenceRS-Id values. The terminal device 1 may be provided with multiple PUSCH-PathlossReferenceRS-Id values. The terminal device may derive a mapping from sri-PUSCH-PowerControlId in SRI-PUSCH-PowerControl. If the terminal device 1 is provided with two SRS resource sets, a first SRI and a second SRI may exist. A mapping may be a value associated with the value of the first SRI field and the value of the second SRI field. If asymmetricTRP is configured, a mapping may be associated with the value of the first SRI field. If asymmetricTRP is configured, a mapping may be associated with either the value of the first SRI field or the value of the second SRI field.

[0358] PUSCH transmission opportunity i is the slot index n μ s，f PUSCH transmission opportunity i may be defined by the following equation. The PUSCH transmission opportunity i may be a slot. For example, the PUSCH transmission opportunity i may be a time timing at which transmission power control is performed. For example, if the PUSCH transmission opportunity i is the first slot, transmission power control may be performed in the first slot. The PUSCH transmission opportunity i for PUSCH repetition type B may be a nominal repetition. The PUSCH transmission opportunity i may be determined based on a slot index, a starting OFDM symbol in the slot, and a number of consecutive OFDM symbols.

[0359] If j is 0, P PUSCH，b，f，c (i, j, q d , l) may be the transmit power for the PUSCH scheduled by the random access response grant. PUSCH，b，f，c (i, j, q d, l) may be the transmit power for the PUSCH scheduled by the configured uplink grant. If j is greater than 1, P PUSCH，b，f，c (i, j, q d , l) may be the transmit power for the PUSCH scheduled by the DCI. If j is greater than 1, l may be indicated by the scheduling DCI.

[0360] P O＿PUSCH，b，f，c (j) may be the target received power. O＿PUSCH，b，f，c (j) P O＿NOMINAL＿PUSCH，f，c (j) and P O＿UE＿PUSCH，b，f，c (j) and may be determined based on P O＿PUSCH，b，f，c (j) may be determined based on at least the DL / Joint TCI state or the UL TCI state. O＿PUSCH，b，f，c (j) may be determined based on the DL / Joint TCI state or the UL TCI state corresponding to the one power control state.

[0361] P O＿NOMINAL＿PUSCH，f，c (j) may be provided by a higher layer parameter. O＿UE＿PUSCH，b，f，c (j) may be provided by a higher layer parameter. O＿UE＿PUSCH，b，f，c (0) may be 0. P O＿UE＿PUSCH，b，f，c (j) may be determined based on at least the DL / JointTCI state or the UL TCI state. O＿UE＿PUSCH，b，f，c (j) may be determined based on the DL / Joint TCI state or the UL TCI state corresponding to the one power control state.

[0362] M PUSCH RB，b，f，c (j) may be the number of resource blocks allocated for the PUSCH. The transmit power of the PUSCH is PUSCH RB，b，f，c P determined at least based on (j) PUSCH，b，f，c (i, j, q d , l).

[0363] α b，f，c(j) may be a scaling factor, e.g., α b，f，c (j) may be equal to or less than 1. For example, α b，f，c (j) may be any of 0, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, and 1. b，f，c (j) may be provided by a higher layer parameter. b，f，c (j) may be determined based at least on the TCI state (e.g., the UL TCI state). b，f，c (j) may be determined based on the DL / Joint TCI state or the UL TCI state corresponding to the one power control state.

[0364] PL b，f，c (q d ) may be the propagation path loss. For example, PL b，f，c (q d ) is q d The propagation path loss may be a value estimated based on a reference signal specified by q. The propagation path loss may be a downlink propagation path loss. Also, the propagation path loss may be an uplink propagation path loss. d may be determined based at least on the TCI state (e.g., the UL TCI state). d may be determined based on the DL / Joint TCI state or the UL TCI state corresponding to the one power control state.

[0365] Δ TF，b，f，c (i) may be a transport format. TF，b，f，c (i) may be a power variation based on the number of information bits per resource element. TF，b，f，c (i) may be determined based on Equation 3. For example, if the number of transmission layers is greater than 1, Δ TF，b，f，c (i) may be 0. For example, when DMRS bundling is applied, Δ TF，b，f，c (i) may be 0.

[0366] The BPRE may be the number of information bits in one resource element among one or more resource elements. For example, the BPRE may be the number of information bits per resource element. Here, the information bits may include a transport block, a CRC sequence attached to the transport block, and part or all of a CRC sequence attached to each of one or more code blocks obtained by dividing the transport block. For example, for a PUSCH used to transmit a transport block, the BPRE may be determined based on the size of the transport block and the number of resource elements for the PUSCH. The BPRE may be determined based on Equation 4. For example, when a PUSCH is used to transmit a transport block delivered by an UL-SCH, the BPRE may be determined based on Equation 4.

[0367] C may be the number of code blocks. r may be the size of the r-th code block, where the size of the r-th code block may be determined by the sum of the number of bits of the r-th code block and the number of bits of the CRC sequence added to the r-th code block. RE N may be the number of resource elements. RE may be determined based on Equation 5.

[0368] N PUSCH symb,b,f,c(i) may be the number of OFDM symbols, e.g., the number of OFDM symbols in PUSCH transmission opportunity i, e.g., the number of OFDM symbols for the PUSCH transmitted in PUSCH transmission opportunity i. In Equation 5, N may be 1. N may be provided by a higher layer parameter.

[0369] N RB sc，data(i, j) may be the number of subcarriers for the PUSCH in OFDM symbol j. Furthermore, the determination of the number of subcarriers may not include subcarriers to which the DMRS and PTRS are mapped.

[0370] The BPRE may be determined based on Equation 6. For example, when the PUSCH is used to transmit uplink control information, the BPRE may be determined based on Equation 6.

[0371] Q m may be a modulation order of the PUSCH. R may be a maximum coding rate of the PUSCH (or simply referred to as a coding rate).

[0372] K s may be 1.25 or 0. When upper layer parameters are set, K s If the upper layer parameter is not set, K s may be 0. s If is 0, Δ TF，b，f，c (i) may be 0.

[0373] If the PUSCH is used to transmit the transport block delivered by the UL-SCH, β PUSCH offset may be 1. When the PUSCH is used to carry uplink control information, β PUSCH offset does not have to be 1. PUSCH offset may be determined based at least on the size of the uplink control information.

[0374] Closed loop power value f b，f，c (i, l) may be determined based on Equation 7. b，f，c (i, l) may be determined based on the TPC command field, which may be included in the DCI. b，f，cIf the first upper layer parameter is not provided, (i, l) may be determined based on Equation 7. The first upper layer parameter may be the upper layer parameter tpc-Accumulation. The first upper layer parameter may be a dedicated upper layer parameter. The first upper layer parameter may be provided in the upper layer parameter PUSCH-Config. The first upper layer parameter may not be provided in the upper layer parameter ConfiguredGrantConfig. b，f，c (i, l) may be determined at PUSCH transmission opportunity i. b，f，c (i, l) may be determined based on Equation 8. b，f，c (i, l) may be determined based on Equation 8 when the first upper layer parameter is provided.

[0375] δPUSCH,b,f,c(m,l) and δPUSCH,b,f,c(i,l) may be TPC command values. δPUSCH,b,f,c(m,l) and δPUSCH,b,f,c(i,l) may be values ​​specified by the value of the TPC command field in the DCI. The DCI may be a DCI that schedules a PUSCH. The DCI may be a DCI corresponding to DCI format 2_2 with a CRC scrambled by the TPC-PUSCH-RNTI. The DCI may be a DCI corresponding to DCI format 2_3. For example, if the value of the TPC command field is 0, δPUSCH,b,f,c(m,l) may be −1 dB. dB may also refer to decibels. For example, if the value of the TPC command field is 1, δPUSCH,b,f,c(m,l) may be 0 dB. For example, if the value of the TPC command field is 2, δPUSCH,b,f,c(m,l) may be 1 dB. For example, if the value of the TPC command field is 3, δPUSCH,b,f,c(m,l) may be 3 dB. For example, if the value of the TPC command field is 0, δPUSCH,b,f,c(i,l) may be −4 dB. For example, if the value of the TPC command field is 1, δPUSCH,b,f,c(i,l) may be −1 dB. For example, if the value of the TPC command field is 2, δPUSCH,b,f,c(i,l) may be 1 dB. For example, if the value of the TPC command field is 3, δPUSCH,b,f,c(i,l) may be 4 dB.

[0376] δPUSCH,b,f,c(m,l) and δPUSCH,b,f,c(i,l) corresponding to one power control state may be determined based on the TPC command field corresponding to the one power control state. For example, δPUSCH,b,f,c(m,l) and δPUSCH,b,f,c(i,l) corresponding to a first power control state (e.g., l=0) may be determined based on the first TPC command field. δPUSCH,b,f,c(m,l) and δPUSCH,b,f,c(i,l) corresponding to a second power control state (e.g., l=1) may be determined based on the second TPC command field. One DCI format may include both the first TPC command field and the second TPC command field. For example, when the upper layer parameter SecondTPCFieldDCI is configured, one DCI format may include both the first TPC command field and the second TPC command field. For example, if the upper layer parameter SecondTPCFieldDCI is set, the power control parameter set may correspond to one power control state. For example, if the upper layer parameter SecondTPCFieldDCI is not set, the power control parameter set may not correspond to one power control state. d , α b，f，c (j), P O＿UE＿PUSCH，b，f，c (j), and P O＿PUSCH，b，f，c Some or all of (j) may be referred to as a power control parameter set. The power control parameter set may be provided based on the indicated DLorJoint-TCIState or the indicated UL-TCIState. For example, the power control parameter set may be provided by one or both of a first higher layer parameter and a second higher layer parameter related to the indicated DLorJoint-TCIState or the indicated UL-TCIState. The first higher layer parameter may be p0-Alpha-CLID-PUSCH-Set or ul-powerControl. The second higher layer parameter may be PL-RS or pathlossReferenceRS-Id.

[0377] D i may be a set of values ​​for one or more TPC commands. i ) may be the number of values ​​included in the set. For example, the set of values ​​for one or more TPC commands may be the number of PUSCH transmission opportunities i-i ０ K PUSCH (i-i ０ ) symbol and K for PUSCH transmission opportunity i PUSCH (i) may include the value of a TPC command received between the previous symbol and the symbol i. ０ can be an integer greater than 0. For example, i ０ may be the minimum value when condition 1 is satisfied. For example, condition 1 satisfies the following condition: ０ K PUSCH (i-i ０ ) symbol is the K symbol of PUSCH transmission opportunity i PUSCH (i) symbol i0 may be earlier than the symbol before the symbol i-i0. PUSCH (i-i0) symbols ago is K of PUSCH transmission opportunity i PUSCH (i) It may be the smallest integer before the symbol. i0 may be greater than 0.

[0378] A PUSCH may not be transmitted based on at least transmission opportunity i and transmission opportunity i0. For example, K PUSCH K symbols before PUSCH transmission opportunity i PUSCH (i) A certain PUSCH may not be transmitted until a symbol before. For example, a certain PUSCH may not be transmitted from PUSCH transmission opportunity i-i0 to PUSCH transmission opportunity i. For example, a certain PUSCH may not be transmitted from the PUSCH at PUSCH transmission opportunity i-i0 to the PUSCH at PUSCH transmission opportunity i.

[0379] For one or two indicated TCI-states or TCI-UL-States for PUSCH, PUCCH, and SRS transmission opportunities, respectively, the terminal device 1 may be provided with a TCI-state or TCI-UL-State in the dl-OrJointTCI-StateList. d may be an RS index. The RS index may be an index for the downlink estimated path loss for PUSCH, PUCCH, and SRS transmission. d may be provided by pathlossReferenceRS-Id-r17. pathlossReferenceRS-Id-r17 may be associated with the indicated TCI-State or TCI-UL-State. pathlossReferenceRS-Id-r17 may be included in the indicated TCI-State or TCI-UL-State. The SRS transmission opportunity does not need to be provided in followUnifiedTCI-StateSRS. If the terminal device 1 is provided with a TCI-state or TCI-UL-State in dl-OrJointTCI-StateList for one or two indicated TCI-states or TCI-UL-States of the PUSCH, PUCCH, and SRS transmission opportunities, respectively, the RS index q for the downlink estimated path loss for PUSCH, PUCCH, and SRS transmission d may be provided by pathlossReferenceRS-Id-r17, which may be included in or associated with the indicated TCI-state or TCI-UL-State, except for SRS transmissions that do not provide followUnifiedTCI-StateSRS.

[0380] The PL offset may be used for the uplink. The PL offset may be calculated by the base station device 3. The PL offset may be calculated by the base station device 3. The PL offset is G b,f,c(i). PLoffset may be the estimated uplink path loss in dB. PLoffset may be the estimated uplink path loss in dB between TRPs. PLoffset may be the estimated uplink path loss in dB between two different TRPs. PLoffset may be the difference in the estimated uplink path loss in dB between two different TRPs and the terminal device 1. When the TCI state associated with PLoffset is applied to PUSCH transmission, the terminal device 1 may determine the PUSCH transmission power according to Equation 9 or Equation 10. In Equation 9 and Equation 10, G b,f,c (i) may be provided by a higher layer parameter, which may be PLoffset, which may be set in the TCI state.

[0381] The terminal device 1 may receive an upper layer processing unit that receives a first upper layer parameter. The first upper layer parameter may be tciSelection-PresentInDCI. The first upper layer parameter may be a parameter indicating whether a first field is present in DCI format 1_1 and DCI format 1_2. The first field may be a TCI selection field. The first upper layer parameter may be present in a downlink BWP.

[0382] The first higher layer parameter may be applyIndicatedTCIState. The first higher layer parameter may be a configuration for a PDSCH scheduled by DCI format 1_0. The first higher layer parameter may be a parameter indicating whether the terminal device 1 applies the first, second, or both indicated TCI states for a PDSCH scheduled by DCI format 1_0.

[0383] The first upper layer parameter may be applyIndicatedTCIState. If the first upper layer parameter is configured and asymmetricTRP is configured, the first upper layer parameter may not be expected to be configured 'both'. If the first upper layer parameter is configured and asymmetricTRP is configured, the first upper layer parameter may be configured 'first' or 'second'. If asymmetricTRP is configured, the first indicated TCI state may be applied to PDSCH reception. If the first upper layer parameter is configured and asymmetricTRP is configured, the first upper layer parameter may be configured only 'first'.

[0384] Configuring the asymmetricTRP may mean reporting a first terminal capability. The first terminal capability may be a capability for enabling the asymmetricTRP. Enabling the asymmetricTRP may mean configuring an mTRP for the uplink and configuring an sTRP for the downlink. Configuring the asymmetricTRP may mean configuring multiple transmission and reception points (mTRP) for the uplink and configuring a single transmission and reception point (sTRP) for the downlink.

[0385] The asymmetricTRP may be an upper layer parameter asymmetricTRP. Configuring the asymmetricTRP may mean configuring it for two uplinks and one downlink. Configuring the asymmetricTRP may mean maintaining two indicated TCI states and not applying one TCI state for the downlink. Configuring the asymmetricTRP may mean maintaining two indicated TCI states and applying only one TCI state for the downlink. One TCI state may be the first TCI state. One TCI state may be the second TCI state. Configuring the asymmetricTRP may mean maintaining only one TCI state for the downlink. Configuring the asymmetricTRP may mean indicating only one TCI state by a certain field of DCI. The certain field may be 'Transmission Configuration Indication'. Configuring the asymmetricTRP may mean indicating only one TCI state by a codepoint of a certain field of DCI. The downlink may be PDSCH.

[0386] Setting asymmetricTRP may mean that two indicated TCI states are maintained and both TCI states are applied for the uplink, which may be PUSCH. Setting asymmetricTRP may mean that dl-OrJointTCI-StateList or TCI-UL-State is set and two SRS resource sets are configured in a list with a certain upper layer parameter usage. The list may be srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2. A certain usage may be set to 'codebook' or 'nonCodebook' in the SRS resource set. Setting asymmetricTRP may mean that multipanelScheme is set. MultipanelScheme may be set to 'SDMscheme' or 'SFNscheme'. MultipanelScheme may set multiple panel simultaneous uplink transmission for PUSCH in a certain scheme. A certain scheme may be SFNS scheme. A certain scheme may be SDMS scheme.

[0387] Configuring an asymmetricTRP may mean configuring an mTRP for the uplink and configuring an sTRP for the downlink. Configuring an mTRP for the uplink may mean configuring a multipanelScheme. The multipanelScheme may be in PUSCH-Config. The multipanelScheme may be set to 'SDMScheme' or 'SFNScheme'. Configuring an mTRP for the uplink may mean configuring two SRS resource sets. Configuring an mTRP for the uplink may mean configuring two SRS resource sets in a list with usage 'codebook' or 'nonCodebook' in the SRS resource set. The list may be srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2.

[0388] For the uplink, configuring the mTRP may also mean configuring the sTx-2Panel. The sTx-2Panel may be a parameter for enabling simultaneous uplink transmission of multiple panels of the PUSCH. When the sTx-2Panel is configured, two coresetPoolIndex values ​​may be configured. When the sTx-2Panel is configured, two SRS resource sets may be configured. When the sTx-2Panel is configured, two SRS resource sets for the codebook or non-codebook may be configured. When the sTx-2Panel is configured, two coresetPoolIndex values ​​are configured, and two SRS resource sets are configured, a multi-DCI-based PUSCH and a PUSCH may be configured. For the uplink, configuring the mTRP may also mean configuring different coresetPoolIndex values.

[0389] For the downlink, the sTRP may be configured with a different coresetPoolIndex value but not configured, or may be configured with the same coresetPoolIndex value for the downlink.

[0390] The first TCI state and the second TCI state may be maintained. Maintaining the first TCI state and the second TCI state may mean maintaining two indicated TCI states. The first TCI state may be the first TCI state. The first TCI state may be the first indicated TCI state. The second TCI state may be the second indicated TCI state.

[0391] When asymmetricTRP is configured, the first higher layer parameter may not be expected to be configured. When asymmetricTRP is configured, a first TCI state may be applied. For example, when asymmetricTRP is configured, a first TCI state may be applied to the PDSCH, and a second TCI state may not be applied to the PDSCH. The first TCI state may be the first indicated TCI state. asymmetricTRP may be an upper layer parameter. asymmetricTRP may be an upper layer parameter for enabling asymmetricTRP. The upper layer parameter asymmetricTRP may be configured in PUSCH-Config. PUSCH-Config may be configured for an uplink physical channel. The upper layer parameter asymmetricTRP may be configured in BWP-UplinkDedicated. The first upper layer parameter may be tciSelection-PresentInDCI.

[0392] If the asymmetricTRP is not configured and the first higher layer parameter is configured, one or both of the first TCI state and the second TCI state for the PDSCH may be determined by the DCI. The first TCI state may be the first indicated TCI state. The second TCI state may be the second indicated TCI state. If the first higher layer parameter is configured, the first field may be configured in the DCI. The first field may be a TCI selection field. If the asymmetricTRP is configured and the first higher layer parameter is configured, the first field may be configured with 0 bits. For example, if the asymmetricTRP is configured, the first higher layer parameter may not be expected to be configured. If the asymmetricTRP is configured, the first TCI state may be applied to the PDSCH. If the asymmetricTRP is configured, the second TCI state may not be used for the downlink physical channel. If the asymmetricTRP is configured and the first higher layer parameter is configured, the first field may be configured with 1 bit. If asymmetricTRP is configured, if the first higher layer parameter is configured, and if the DCI indicates '0' in the first field, the first indicated TCI state may be applied to the PDSCH. If asymmetricTRP is configured, if the first higher layer parameter is configured, and if the DCI indicates '1' in the first field, the second indicated TCI state may be applied to the PDSCH. If asymmetricTRP is configured, and if the first higher layer parameter is configured, the first field may consist of 2 bits. If asymmetricTRP is not configured, if the first higher layer parameter is configured, and if the DCI indicates '00' in the first field, the first indicated TCI state may be applied to the PDSCH.If asymmetricTRP is not configured, and the first higher layer parameter is configured, and the DCI indicates '01' in the first field, the second indicated TCI state may be applied to the PDSCH. If asymmetricTRP is not configured, and the first higher layer parameter is configured, and the DCI indicates '10' in the first field, both indicated TCI states may be applied to the PDSCH. If asymmetricTRP is not configured, and the first parameter is not configured, both indicated TCI states may be applied to the PDSCH.

[0393] If the asymmetricTRP is configured and the first higher layer parameter is configured, one of a first TCI state and a second TCI state for the PDSCH may be determined by the DCI. The first TCI state may be a first indicated TCI state. The second TCI state may be a second indicated TCI state. If the first higher layer parameter is configured, a first field may be configured in the DCI. The first field may be a TCI selection field. If the asymmetricTRP is configured and the first higher layer parameter is configured, the first field may consist of a second number of bits. The second number of bits may be 1 bit. The second bit may be 2 bits. If the asymmetricTRP is configured and the first higher layer parameter is configured and the DCI indicates '00' in the first field, the first TCI state may be applied to the PDSCH. If asymmetricTRP is configured, and the first higher layer parameter is configured, and the DCI indicates '01' in the first field, the second TCI state may be applied to the PDSCH. If asymmetricTRP is configured, and the first higher layer parameter is configured, the DCI may reserve '10' or '11' in the first field. If asymmetricTRP is configured, and the first higher layer parameter is configured, the DCI may reserve '11' in the first field. This reservation may not be expected. If asymmetricTRP is not configured, and the first higher layer parameter is not configured, both the first TCI state and the second TCI state may be applied to the PDSCH. If asymmetricTRP is configured, and the first higher layer parameter is configured, the DCI may not be expected to indicate '10' or '11' in the first field. If asymmetricTRP is configured and the first upper layer parameter is configured, the DCI may not be expected to indicate '10' in the first field.

[0394] The second upper layer parameter may be PLoffset. PLoffset may be configured in TCI-State. PLoffset may be configured in TCI-UL-State. PLoffset may be a dB value. PLoffset may be configured with a dB value. The second upper layer parameter may be configured in one or both of the first TCI state and the second TCI state. The first TCI state may be a first indicated TCI state. The first TCI state may be a second indicated TCI state. The second TCI state may be a second indicated TCI state. The second TCI state may be the first indicated TCI state. The first upper layer parameter may be a parameter for configuring a unified TCI state. When the first higher layer parameter is configured, and the first TCI state and the second TCI state are maintained, and asymmetricTRP is configured, the second higher layer parameter in the first TCI state is not expected to be configured, and the second higher layer parameter in the second TCI state may be expected to be configured. When the first higher layer parameter is configured, and the first TCI state and the second TCI state are maintained, and asymmetricTRP is configured, the second higher layer parameter in the first TCI state may be ignored. When the first higher layer parameter is configured, and the first TCI state and the second TCI state are maintained, and asymmetricTRP is configured, the value of the second higher layer parameter in the first TCI state may be considered to be 0. When a first upper layer parameter is set, and when the first TCI state and the second TCI state are maintained, and when asymmetricTRP is not set, the second upper layer parameter in the first TCI state and the second upper layer parameter in the second TCI state may not be expected to be set.When the first higher layer parameter is set, and the first TCI state and the second TCI state are maintained, and if asymmetricTRP is not set, the second higher layer parameter in the first TCI state and the second higher layer parameter in the second TCI state may be ignored.When the first higher layer parameter is set, and the first TCI state and the second TCI state are maintained, and if asymmetricTRP is not set, the values ​​of the second higher layer parameter in the first TCI state and the second higher layer parameter in the second TCI state may be considered to be 0.

[0395] The first TCI state may be a joint TCI state or a UL TCI state. The second TCI state may be a joint TCI state or a UL TCI state. The first TCI state may be the first indicated joint TCI state or the first indicated UL TCI state. The second TCI state may be the second indicated joint TCI state or the second indicated UL TCI state. The first TCI state may be the second indicated joint TCI state or the second indicated UL TCI state. The second TCI state may be the first indicated joint TCI state or the first indicated UL TCI state. The unifiedTCI-StateType-r17 may be an upper layer parameter. The unifiedTCI-StateType-r17 may be an upper layer parameter for indicating the type of unified TCI state to be configured for this serving cell. A value of {separate} for unifiedTCI-StateType-r17 may mean that this serving cell is configured in dl-OrJointTCI-StateList for DL ​​TCI states and in ul-TCI-ToAddModList for UL TCI states. A value of {joint} for unifiedTCI-StateType-r17 may mean that this serving cell is configured in dl-OrJointTCI-StateList for joint TCI states for UL and DL. When the value of unifiedTCI-StateType-r17 is set to {joint}, the joint TCI states may be configured in dl-OrJointTCI-StateList. When the value of unifiedTCI-StateType-r17 is set to {separate}, the DL TCI states may be configured in dl-OrJointTCI-StateList. dl-OrJointTCI-StateList may be configured in higher layer parameters, which may be configured in PDSCH-Config.When the value of unifiedTCI-StateType-r17 is set to {separate}, the UL TCI state may be set in ul-TCI-ToAddModList. ul-TCI-ToAddModList may be set in an upper layer parameter, which may be BWP-UplinkDedicated. When the value of unifiedTCI-StateType-r17 is set to {joint}, the first TCI state may be the first indicated joint TCI state. When the value of unifiedTCI-StateType-r17 is set to {joint}, the second TCI state may be the second indicated joint TCI state. When the value of unifiedTCI-StateType-r17 is set to {joint}, the first TCI state may be the second indicated joint TCI state. When the value of unifiedTCI-StateType-r17 is set to {joint}, the second TCI state may be the first indicated joint TCI state. When the value of unifiedTCI-StateType-r17 is set to {separate}, the first TCI state may be a UL TCI state. When the value of unifiedTCI-StateType-r17 is set to {separate}, the first TCI state may be a first indicated UL TCI state. When the value of unifiedTCI-StateType-r17 is set to {separate}, the first TCI state may be a second indicated UL TCI state. When the value of unifiedTCI-StateType-r17 is set to {separate}, the second TCI state may be a second indicated UL TCI state. When the value of unifiedTCI-StateType-r17 is set to {separate}, the second TCI state may be a first indicated UL TCI state. The first TCI state and the second TCI state are not expected to be DL TCI states.

[0396] The second upper layer parameter may be pathlossReferenceRS-Id-r17. The second upper layer parameter may be pathlossReferenceRS-Id-r19. The uplink physical channel may be PUSCH. The uplink physical channel may be PUCCH. When the first upper layer parameter is configured, the transmit power of the uplink physical channel may be determined based on the indicated TCI state. The indicated TCI state may be the indicated first TCI state and the indicated second TCI state. When the first upper layer parameter is configured and the asymmetric TRP is configured, the reference signal index may be provided by the second upper layer parameter included in the first TCI state and the second upper layer parameter included in the second TCI state, and the value of the second upper layer parameter included in the first TCI state may be expected to be the same as the value of the second upper layer parameter included in the second TCI state. When the first higher layer parameter is configured and asymmetricTRP is configured, the reference signal index is provided by the second higher layer parameter included in the first TCI state and the second higher layer parameter included in the second TCI state, and the value of the second higher layer parameter included in the first indicated TCI state may be expected to be the same as the value of the second higher layer parameter included in the second indicated TCI state.When the first higher layer parameter is configured and asymmetricTRP is configured, the reference signal index is provided by the second higher layer parameter included in the first TCI state and the second higher layer parameter included in the second TCI state, and the value of the second higher layer parameter included in the first indicated TCI state may be expected to be the same as the value of the second higher layer parameter included in the second indicated TCI state.When the first upper layer parameter is configured and asymmetricTRP is configured, the reference signal index is provided by the second upper layer parameter included in the first TCI state and the second upper layer parameter included in the second TCI state, and the value of the second upper layer parameter included in the first indicated TCI state may be considered to be the same as the value of the second upper layer parameter included in the second indicated TCI state. When the first upper layer parameter is configured and asymmetricTRP is not configured, the reference signal index may be provided by the second upper layer parameter included in the first TCI state and the second upper layer parameter included in the second TCI state. The reference signal index is q. ｄ may be.

[0397] When asymmetricTRP is configured, the second upper layer parameter in TCI-UL-State does not have to be mandatory. When asymmetricTRP is configured, TCI-UL-State-r19 different from TCI-UL-State may be configured. When asymmetricTRP is configured, TCI-State-r19 different from TCI-State may be configured. That TCI-State-r19 may be configured in a dl-OrJointTCI-StateList-r19 different from dl-OrJointTCI-StateList. When asymmetricTRP is configured, TCI state may be configured in a dl-OrJointTCI-StateList-r19 different from dl-OrJointTCI-StateList. dl-OrJointTCI-StateList-r19 may be a parameter for configuring asymmetricTRP. When asymmetricTRP is configured, the second upper layer parameter in TCI-State does not have to be mandatory. When asymmetricTRP is configured and the joint TCI state is configured, the second higher layer parameter in TCI-State does not have to be mandatory. The joint TCI state may be configured by setting the value of unifiedTCI-StateType-r17 to {joint}. The separate TCI state may be configured by setting the value of unifiedTCI-StateType-r17 to {separate}. When asymmetricTRP is configured and the separate TCI state is configured, the second higher layer parameter in TCI-UL-State does not have to be mandatory.

[0398] When the first higher layer parameter is configured, the reference signal index may be provided by both the second higher layer parameter included in the first TCI state and the second higher layer parameter included in the second TCI state. When the asymmetric TRP is configured, the value of the second higher layer parameter included in the first TCI state may be the same as the value of the second higher layer parameter included in the second TCI state. When the asymmetric TRP is configured, the second higher layer parameter included in the first TCI state may be independent of the second higher layer parameter included in the second TCI state.

[0399] Various aspects of the device according to one aspect of this embodiment will be described below.

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

[0401] Note that a part of the terminal device 1 and the base station device 3 in the above-described embodiment may be realized by a computer. In this case, a program for realizing 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 realize the function.

[0402] The term "computer system" used here refers to a computer system built into the terminal device 1 or base station device 3, and includes hardware such as an OS and peripheral devices. Also, the term "computer-readable recording medium" 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 the computer system.

[0403] Furthermore, the term "computer-readable recording medium" may include a medium 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 a medium 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 a case. The program may also be one that realizes part of the above-mentioned functions, or one that can realize the above-mentioned functions in combination with a program already stored in the computer system.

[0404] 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 according 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 according to the above-described embodiment can also communicate with the base station device as a collection.

[0405] Furthermore, the base station device 3 in the above-described embodiment 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 embodiment may have some or all of the functions of an upper node for the eNodeB and / or the gNB.

[0406] 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 of them 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 is also possible to use an integrated circuit based on that technology.

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

[0408] Although the embodiments of the present invention have been described above in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design modifications and the like are also included within the scope of the gist of the present 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 in the technical scope of the present invention. Furthermore, configurations in which elements described in the above embodiments are substituted with elements that achieve the same effect are also included.

[0409] One aspect of the present invention can be used, for example, in a communication system, a communication device (e.g., a mobile phone device, a base station device, a wireless LAN device, or a sensor device), an integrated circuit (e.g., a communication chip), or a program.

[0410] 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 Point 3001, 3002 Resource grid 3003, 3004 BWP 3011, 3012, 3013, 3014 Offset 3100, 3200 Common resource block set

Claims

an upper layer processing unit that receives a first upper layer parameter and a second upper layer parameter; a receiving unit for receiving a PDCCH in which DCI is arranged, the first TCI state or the second TCI state is mapped to a TCI code point of the DCI; When the TCI codepoint is received, the first TCI state and / or the second TCI state mapped to the TCI codepoint are updated, and the second upper layer parameter is set in the first TCI state and / or the second TCI state, the first upper layer parameter being a parameter for setting a unified TCI state, and when the first upper layer parameter is set, and the first TCI state and the second TCI state are maintained, and an asymmetric TRP is set. When the first TCI state is set, the second upper layer parameter is expected not to be set, and when the second TCI state is set, the second upper layer parameter is expected to be set; when the first TCI state and the second TCI state are maintained, and when asymmetricTRP is not set, the second upper layer parameter in the first TCI state and the second upper layer parameter in the second TCI state are not expected to be set.

2. The terminal device of claim 1, wherein the first TCI state and the second TCI state are expected to be a joint TCI state or a UL TCI state, and the first TCI state and the second TCI state are not expected to be a DL TCI state. 　 an upper layer processing unit that transmits a first upper layer parameter and a second upper layer parameter; a transmitter unit for transmitting a PDCCH in which DCI is arranged, the first TCI state or the second TCI state is mapped to a TCI code point of the DCI; When the TCI codepoint is received, the first TCI state and / or the second TCI state mapped to the TCI codepoint are updated, and the second upper layer parameter is set in the first TCI state and / or the second TCI state, the first upper layer parameter being a parameter for setting a unified TCI state, and when the first upper layer parameter is set, and the first TCI state and the second TCI state are maintained, and asymmetricTRP is set. When the first TCI state is maintained, the second upper layer parameter is expected not to be set, and the second upper layer parameter is expected to be set, and when the first TCI state and the second TCI state are maintained, and when an asymmetric TRP is not set, the second upper layer parameter in the first TCI state and the second upper layer parameter in the second TCI state are not expected to be set.

4. The base station device according to claim 3, wherein the first TCI state and the second TCI state are expected to be a joint TCI state or a UL TCI state, and the first TCI state and the second TCI state are not expected to be a DL TCI state.

Images