Terminal device and base station device

Abstract

This terminal device comprises: an upper layer processing unit that receives a first upper layer parameter including a plurality of first TCI-States, a second upper layer parameter, and one second TCI-State for each SRS resource; a reception unit that receives a PDCCH that is carrying DCI; and a transmission unit that transmits an SRS in a plurality of the SRS resources included in an SRS resource set. The second upper layer parameter is a parameter that instructs the application of a TCI-State indicated by the DCI to the SRS resource set. When the first upper layer parameter is provided, the SRS transmission power of the SRS is determined on the basis of the pathloss offset. When a second upper layer parameter is provided for the SRS resource set, the value of the pathloss offset is provided by one of the plurality of first TCI-States that is indicated by the DCI. When the second upper layer parameter is not provided for the SRS resource set, the value of the pathloss offset is provided by the second TCI-State of the SRS resource having the lowest SRS resource ID in the SRS resource set.

Description

Terminal equipment and base station equipment

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

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

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

[0004] 3GPP is considering expanding the services supported by NR (Non-Patent 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] The present invention provides a terminal device for efficient communication, a communication method used in the terminal device, a base station device for efficient communication, and a communication method used in the base station device.

[0007] (1) A first aspect of the present invention is a terminal device comprising: an upper layer processing unit that receives a first upper layer parameter including a plurality of first TCI-States, a second upper layer parameter, and one second TCI-State for each SRS resource; a receiving unit that receives a PDCCH on which a DCI is located; and a transmitting unit that transmits SRS to a plurality of SRS resources included in an SRS resource set, wherein the second upper layer parameter is a parameter that instructs the SRS resource set to apply a TCI-State indicated by the DCI; when the first upper layer parameter is provided, the transmit power of the SRS is determined based on the path loss offset; when the second upper layer parameter is provided for the SRS resource set, the value of the path loss offset is provided by one of the plurality of first TCI-States indicated by the DCI; and when the second upper layer parameter is not provided for the SRS resource set, the value of the path loss offset is provided by the second TCI-State of the SRS resource with the lowest SRS resource ID in the SRS resource set.

[0008] (2) A second aspect of the present invention is a base station device comprising: an upper layer processing unit that transmits a first upper layer parameter including a plurality of first TCI-States, a second upper layer parameter, and one second TCI-State for each SRS resource; a transmitting unit that transmits a PDCCH on which a DCI is located; and a receiving unit that receives SRS in a plurality of SRS resources included in an SRS resource set, wherein the second upper layer parameter is a parameter that instructs the SRS resource set to apply a TCI-State indicated by the DCI; when the first upper layer parameter is provided, the transmit power of the SRS is determined based on the path loss offset; when the second upper layer parameter is provided for the SRS resource set, the value of the path loss offset is provided by one of the plurality of first TCI-States indicated by the DCI; and when the second upper layer parameter is not provided for the SRS resource set, the value of the path loss offset is provided by the second TCI-State of the SRS resource with the lowest SRS resource ID in the SRS resource set.

[0009] According to this invention, terminal devices can communicate efficiently. Furthermore, base station devices can communicate efficiently.

[0010] This is a conceptual diagram of a wireless communication system according to one aspect of this embodiment. The subcarrier spacing setting μ and the number of OFDM symbols per slot N according to one aspect of this embodiment. slot symb This is an example showing the relationship between the CP (cyclic prefix) settings. This is a diagram showing an example of a resource grid configuration method according to one aspect of this embodiment. This is a diagram showing an example of the configuration of resource grid 3001 according to one aspect of this embodiment. This is a schematic block diagram showing an example of the configuration of base station device 3 according to one aspect of this embodiment. This is a schematic block diagram showing an example of the configuration of terminal device 1 according to one aspect of this embodiment. This is a diagram showing an example of the configuration of SS / PBCH block according to one aspect of this embodiment. This is a diagram showing an example of the monitoring opportunity of the search area set according to one aspect of this embodiment.

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

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

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

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

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

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

[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. Also, a serving cell is also referred to as a cell.

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

[0019] For example, one resource grid may be given for each component carrier. Also, one resource grid may be given for each set of a component carrier and a subcarrier spacing configuration μ. Here, the subcarrier spacing configuration μ is also referred to as numerology. For example, one resource grid may be given 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 N size，μ grid，x N RB sc includes N subcarriers. Here, the resource grid starts from the common resource block N start，μ grid，x Also, the common resource block N start，μ grid，x is also referred to as the reference point of the resource grid.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[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 the setting μ for the subcarrier interval. １ This is indicated by the number of common resource blocks for the resource grid 3001, starting from the reference point of the resource grid 3001. size，μ grid１，x Includes several common resource blocks.

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

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

[0038] Among the common resource block sets 3200, the common resource block that includes the point 3000 (the black solid-color 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 indicated by the number of common resource blocks with respect to the subcarrier spacing μ ２ The resource grid 3002 includes N size，μ grid２，x common resource blocks starting from the reference point of the resource grid 3002.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0079] For example, the wireless transmitter 10a may generate and transmit a PRACH baseband signal. For example, the wireless transmitter 10a may generate and transmit a PUCCH baseband signal. The wireless transmitter 10a may generate and transmit a PUSCH baseband signal. For example, the wireless transmitter 10a may generate and transmit a PUCCH DMRS baseband signal. For example, the wireless transmitter 10a may generate and transmit a PUSCH DMRS baseband signal. For example, the wireless transmitter 10a may generate and transmit a UL PTRS baseband signal. For example, the wireless transmitter 10a may generate and transmit an SRS baseband signal. Generating an SRS baseband signal may also mean generating an SRS sequence.

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

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

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

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

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

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

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

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

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

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

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

[0091] Physical signals are a collective term for downlink physical channels, downlink physical signals, uplink physical channels, and uplink physical channels. Physical channels are a collective term for downlink physical channels and uplink physical channels. Physical signals are a collective term for downlink physical signals and uplink physical signals.

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

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

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

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

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

[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 from the UL-SCH (UpLink-Shared Channel) of the transport layer.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[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 that PUCCH may be represented (or triggered) by a single DCI format. The resource element mapping of the PUCCH and the resource element mapping of the DMRS for that PUCCH, or both, may be given by a single PUCCH format. The PUCCH and the DMRS for that PUCCH may be collectively referred to as PUCCH. Transmission of a PUCCH may be equivalent to transmission of both the PUCCH and the DMRS for that PUCCH.

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

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

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

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

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

[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 the radio frame. Here, the half-radio frame may consist of five subframes. Alternatively, the half-radio frame may consist of the first five subframes of the ten subframes included in the radio frame. Alternatively, the half-radio frame may consist of the last five subframes of the ten subframes included in the radio frame.

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

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

[0122] A PDCCH may be transmitted to transmit Downlink Control Information (DCI). Downlink Control Information may be mapped onto the PDCCH. Terminal device 1 may receive a PDCCH on which Downlink Control Information is mapped. Base station device 3 may transmit a PDCCH on which Downlink Control Information is mapped.

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

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

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

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

[0127] The frequency domain resource allocation field included in DCI format 0_0 may be used to indicate the allocation of frequency resources for 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 PUSCH.

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

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

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

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

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

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

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

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

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

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

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

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

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

[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 to indicate the allocation of frequency resources for PDSCH.

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

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

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

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

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

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

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

[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 to indicate the allocation of frequency resources for PDSCH.

[0156] The time domain resource allocation field included in DCI format 1_1 may be used to indicate the allocation of time resources for 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 PDSCH.

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

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

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

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

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

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

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

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

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

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

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

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

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

[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 a DMRS for a PDSCH (DMRS associated with a PDSCH, DMRS included in a PDSCH, DMRS corresponding to a PDSCH) may be given based on the set of antenna ports for the PDSCH. In other words, the set of antenna ports for a DMRS for a PDSCH may be the same as the set of antenna ports for the PDSCH.

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

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

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

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

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

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

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

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

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

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

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

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

[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 that is not an MIB is delivered to the DL-SCH of the transport layer. CCCH is mapped to DL-SCH or UL-SCH. That is, a transport block mapped to CCCH is delivered to DL-SCH or UL-SCH. DCCH is mapped to DL-SCH or UL-SCH. That is, a transport block mapped to DCCH is delivered to DL-SCH or UL-SCH.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[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 consist of continuous resources (non-interleaved mapping) or distributed resources (interleaver mapping).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0230] A DL symbol may be an OFDM symbol set or indicated for the downlink in time-division duplexing. The DL symbol may be an OFDM symbol set or indicated for PDSCH or PDCCH. The DL symbol may be provided by the upper layer parameter tdd-UL-DL-ConfigurationCommon. The DL symbol may be provided by the upper layer parameter tdd-UL-DL-ConfigurationDedicated. DL slots may be provided by the upper layer parameter tdd-UL-DL-ConfigurationCommon. DL slots may be provided by the upper layer parameter tdd-UL-DL-ConfigurationDedicated.

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

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

[0233] Base station device 3 may send a terminal capability request to terminal device 1. Terminal device 1 may send one or more terminal capability information to base station device 3. Terminal capability information may include one or more terminal capabilities. RRC messages may include terminal capability information. Base station device 3 may receive RRC messages. Base station device 3 may receive RRC messages that include higher layer parameters. If terminal capability information is to be sent, terminal device 1 may send an RRC message to base station device 3.

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

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

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

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

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

[0239] When the upper-level parameter tci-PresentInDCI is set, or tci-PresentDCI-1-2 is set for CORESET, 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 downlink assignments. If applicable, DCI format 1_1 / 1_2 may not have downlink assignments. If DCI format 1_1 / 1_2 does not have downlink assignments, terminal device 1 may assume certain conditions. For example, certain conditions may include the use of CS-RNTI to scramble the CRC for DCI. It may assume that all RVs in the DCI field are 1. It may assume that all MCSs in the DCI field are 1. It may assume that the NDI in the DCI field is 0. You can assume that all FDRA values ​​in the DCI field are 0.

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

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

[0242] When terminal device 1 receives a higher-layer configuration dl-OrJointTCI-StateList having one TCI-state, that TCI-state may be used as the instructed TCI state. When terminal device 1 receives a higher-layer configuration dl-OrJointTCI-StateList having one TCI-state, terminal device 1 may obtain a QCL assumption from the configured TCI state.

[0243] When terminal device 1 receives a higher-layer configuration ul-TCI-StateList having one TCI-UL-state, that TCI-state may be used as the instructed TCI state.

[0244] If the indicated TCI state differs from a previously indicated TCI state, either or both of the indicated TCI-state and TCI-UL-State may be applied starting from a slot. This slot may be the first slot after the last symbol of PUSCH or PUCCH and at least after the beamAppTime symbol.

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

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

[0247] If terminal device 1 is configured with SSB-MTC-AdditionalPCI and is configured with PDCCH-Config which includes different coresetPoolIndex values ​​in the ControlResourceSet, 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 a serving cell physical cell ID. In that 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] Terminal device 1 may receive an activation command when it indicates two TCI states in the code point of the DCI field 'Transmission Configuration Indication'. The activation command may be used to map up to eight combinations of one or two TCI states to that code point. Terminal device 1 is not expected to receive more than eight TCI states in the activation command.

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

[0250] Terminal device 1 may be configured with the upper-layer parameter tci-PresentInDCI. tci-PresentInDCI may be set to enable for CORESET to schedule the PDSCH. In that case, terminal device 1 may assume that the TCI field exists in the DCI format 1_1 or 1_3 of the PDCCH transmitted over CORESET.

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

[0252] Terminal device 1 may be configured with both sfnSchemePDCCH and sfnSchemePDSCH. The offset time between the reception of the downlink DCI and the reception of the corresponding PDSCH may be greater than or equal to the threshold timeDuraionForQCL. Terminal device 1 may support sfn-DefaultDL-BeamSetup-r17 for DCIs scheduled without a TCI field. In that case, 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 receiving downlink DCIs in the serving cell's active BWP, regardless of the number of active TCIs in the CORESET. If terminal device 1 does not instruct SchemeA-DynamicSwitching-r17 or sfn-SchemeB-DynamicSwitching-r17, terminal device 1 may be activated with two TCI states in its CORESET.

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

[0254] If 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, terminal device 1 may expect the TCI field to exist.

[0255] Terminal device 1 may set sfnSchemePDCCH to 'sfnschemeA'. In that case, terminal device 1 does not need to set sfnSchemePDSCH. In that case, there does not need to 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 greater than or equal to the threshold timeDuraionForQCL, and the CORESET that schedules the PDSCH is indicated with two TCI states, terminal device 1 may assume that the TCI state or QCL assumption for the PDSCH is the same as the first TCI state or QCL assumption applied for the CORESET used to transmit the PDCCH.

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

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

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

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

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

[0261] Regardless of the settings of tci-PresentInDCI and tci-PresentDCI-1-2 in RRC connected mode, if dl-OrJointTCI-StateList-r17 is not provided to terminal device 1, and the offset between receiving the downlink DCI corresponding to the PDSCH is less than timeDurationForQCL, then at least one configured TCI state may include a qcl-Type set to 'typeD'. In that case, 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 lowest controlResourceSetId in the latest slot among one or more CORESETs in the active BWP of the serving cell monitored by terminal device 1, the CORESET associated with the monitored search space, and the QCL instruction of the CORESET associated with that CORESET.

[0262] Terminal device 1 may be configured with enableDefaultTCI-StatePerCoresetPoolIndex. Terminal device 1 may also be configured with the higher-level parameter PDCCH-Config. PDCCH-Config may contain two different coresetPoolIndex values ​​in different ControlResourceSets. In that case, 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. That PDCCH may be the PDCCH that schedules the PDSCH in the active BWP of the serving cell monitored by terminal device 1, and may be based on the lowest controlResourceSetId among the CORESETs and the QCL instruction of the CORESET associated with the monitored search space.

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

[0264] Terminal device 1 may be configured with the upper-layer parameter repetitionScheme. repetitionScheme may also be set with tdmSchemeA. In that case, or when configured with the upper-layer parameter repetitionNumber, and when the offset between the first PDSCH transmitter and the reception of the downlink DCI is less than the threshold timeDurationForQCL, the mapping of the TCI state to the PDSCH transmitter opportunity may be determined by a certain method.

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

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

[0267] Regardless of the settings of tci-PresentInDCI and tci-PresentDCI-1-2 in RRC connected mode, terminal device 1 may be given dl-OrJointTCI-StateList-r17. In that case, if the offset between the DCI of the downlink and the corresponding PDSCH is less than timeDurationForQCL, regardless of the setting of followUnifiedTCI-State, it may include qcl-Type in which at least one set TCI state is set to typeD. In this case, if the indicated TCI state is associated with the PCI of a different serving cell, terminal device 1 may assume that the DMRS port of a PDSCH of a serving cell is in the RS and QCL state used for the PDCCH. That 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 terminal device 1, and the CORESET indication associated with the monitored search space. In the case of CA, if the 'QCL-TypeD' of the DMRS of the PDSCH for each component carrier within a band is different, the assumption of the 'QCL-TypeD' of the DMRS of the component carrier's PDSCH for the lowest ID component carrier within that band may apply to all PDSCH DMRS of that component carrier in that band.

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

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

[0270] CSI-RS resources in NZP-CSI-RS-resourceSet may be set periodically. In the NZP-CSI-RS-resourceSet set by the upper layer parameter trs-Info, terminal device 1 may expect a certain TCI-state to indicate a certain QCLtype for periodic CSI-RS resources. A certain QCLtype may be SSB and type C. A certain QCLtype may be the same SSB and type D. An SSB may have a PCI different from the PCI of its serving cell. 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 its serving cell. A certain QCLtype may be a CSI-RS resource in the NZP-CSI-RS-resourceSet set by the upper layer parameter repetition and type D. An SSB may have a PCI different from the PCI of its serving cell. Terminal device 1 may assume that the SSB with a different PCI from the serving cell and the serving SSB have the same center frequency, subcarrier spacing, and SFN offset.

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

[0272] The CSI-RS resources in NZP-CSI-RS-resourceSet may be configured aperiodicly. The NZP-CSI-RS-resourceSet may be configured using the higher-layer parameter trs-Info. For aperiodic CSI-RS resources in the NZP-CSI-RS-resourceSet configured by the higher-layer parameter trs-Info, terminal device 1 may expect the TCI-state to indicate a periodic CSI-RS resource in the NZP-CSI-RS-resourceSet and qcl-Type 'typeA'. For aperiodic CSI-RS resources in the NZP-CSI-RS-resourceSet configured by the higher-layer parameter trs-Info, terminal device 1 may expect the TCI-state to indicate a periodic CSI-RS resource in the NZP-CSI-RS-resourceSet and qcl-Type 'typeD'.

[0273] For CSI-RS resources in the NZP-CSI-RS-resourceSet that are not set by the upper-level parameter trs-Info and are not set by the upper-level parameter repetition, terminal device 1 may expect TCI-state to indicate a certain QCLtype. This certain QCLtype may be typeA of the CSI-RS resource in the NZP-CSI-RS-resourceSet that is set by the upper-level parameter trs-Info. For example, it may be typeD of the same CSI-RS resource.

[0274] For CSI-RS resources in the NZP-CSI-RS-resourceSet that are not set by the upper-layer parameter trs-Info and are not set by the upper-layer parameter repetition, terminal device 1 may expect TCI-state to indicate a certain QCLtype. This certain QCLtype may be a CSI-RS resource in the NZP-CSI-RS-resourceSet set by the upper-layer parameter trs-Info and type A. For example, it may be an SSB and type D. That SSB may have a different PCI than its serving cell. Terminal device 1 may assume that the center frequency, SFN offset, and subcarrier spacing are the same for the SSB with a different PCI than the serving cell and the SSB of the serving cell.

[0275] For CSI-RS resources in the NZP-CSI-RS-resourceSet that are not set by the upper-layer parameter trs-Info and are not set by the upper-layer parameter repetition, terminal device 1 may expect TCI-state to indicate a certain QCLtype. This certain QCLtype may be typeA for a CSI-RS resource in the NZP-CSI-RS-resourceSet that is set by the upper-layer parameter trs-Info. For example, it may be typeD for a CSI-RS resource in the NZP-CSI-RS-resourceSet that is set by the upper-layer parameter repetition.

[0276] For CSI-RS resources in the NZP-CSI-RS-resourceSet that are not set by the upper-level parameter trs-Info and are not set by the upper-level parameter repetition, terminal device 1 may expect TCI-state to indicate a certain QCLtype. This certain QCLtype may be a CSI-RS resource in the NZP-CSI-RS-resourceSet that is set by the upper-level parameter trs-Info and type B when type D is not applicable.

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

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

[0279] For the CSI-RS resources in the NZP-CSI-RS-resourceSet set by the upper-layer parameter repetition, terminal device 1 may expect the TCI-state to indicate a QCLtype. A certain QCLtype may be SSB and type C. For example, it may also be a similar SSB and type D, and its reference signal may be an SSB with a different PCI than that of its serving cell. Terminal device 1 may assume that an SSB with a different PCI than that of the serving cell has the same center frequency, subcarrier spacing, and SFN offset as the serving cell's SSB.

[0280] For PDCCH's DMRS, if terminal device 1 is not configured with dl-OrJointTCI-StateList, terminal device 1 may be expected to indicate a QCLtype in which the TCI-state is. A certain QCLtype may be a CSI-RS resource in the NZP-CSI-RS-resourceSet configured by the higher-layer parameter trs-Info that is type A. For example, it may also be a similar CSI-RS resource that is type D.

[0281] For PDCCH's DMRS, if terminal device 1 is not configured with dl-OrJointTCI-StateList, terminal device 1 may be expected to indicate a QCLtype in which the TCI-state is. A certain QCLtype may be a CSI-RS resource in the NZP-CSI-RS-resourceSet configured by the higher-layer parameter trs-Info that is type A. For example, it may also be a CSI-RS resource in the NZP-CSI-RS-resourceSet configured by the higher-layer parameter repetition that is type D.

[0282] For PDCCH's DMRS, if terminal device 1 is not configured with dl-OrJointTCI-StateList, terminal device 1 may be expected to indicate a QCLtype in which the TCI-state is. A certain QCLtype may be a CSI-RS resource in NZP-CSI-RS-resourceSet that is type A, which is not configured with the upper-level parameter trs-Info and is not configured with the upper-level parameter repetition. For example, it may also be a similar CSI-RS resource that is type D.

[0283] If terminal device 1 is configured with sfnSchemePdcch set with 'sfnschemeA' and CORESET is activated with two TCI states, terminal device 1 may assume that the DMRS port of its CORESET PDCCH is the downlink reference signal and QCL for the two TCI states. If terminal device 1 is configured with sfnSchemePdcch set with 'sfnschemeB' and CORESET is activated with two TCI states, terminal device 1 may assume that the DMRS port of its PDCCH is the downlink reference signal and QCL for the two TCI states excluding the second specified TCI state {Doppler shift, delay spread}.

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

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

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

[0287] For PDSCH's DMRS, if terminal device 1 is not configured with dl-OrJointTCI-StateList, terminal device 1 may be expected to indicate a QCLtype in which TCI-State exists. A QCLtype may be a CSI-RS resource of type A in the NZP-CSI-RS-resourceSet configured by the higher-layer parameter trs-Info. For example, it may be a similar CSI-RS resource of type D.

[0288] For PDSCH's DMRS, if terminal device 1 is not configured with dl-OrJointTCI-StateList, terminal device 1 may be expected to indicate a QCLtype in TCI-State. A QCLtype may be a CSI-RS resource of type A in the NZP-CSI-RS-resourceSet configured by the higher-layer parameter trs-Info. For example, it may be a CSI-RS resource of type D in the NZP-CSI-RS-resourceSet configured by the higher-layer parameter repetition.

[0289] For PDSCH's DMRS, if terminal device 1 is not configured with dl-OrJointTCI-StateList, terminal device 1 may be expected to indicate a QCLtype with a TCI-State. This QCLtype may be a CSI-RS resource in NZP-CSI-RS-resourceSet of type A that is not configured with the upper-level parameter trs-Info and is not configured with the upper-level parameter repetition. For example, it could be a similar CSI-RS resource of type D.

[0290] For PDCCH's DMRS, if terminal device 1 is configured with dl-OrJointTCI-StateList, terminal device 1 may expect the indicated TCI-State to indicate a certain QCLtype. This QCLtype may be a CSI-RS resource in the NZP-CSI-RS-resourceSet, configured by the higher-layer parameter trs-Info, and could be type A. For example, it could be a similar CSI-RS resource and type D.

[0291] For PDCCH's DMRS, if terminal device 1 is configured with dl-OrJointTCI-StateList, terminal device 1 may expect the specified TCI-State to indicate a certain QCLtype. This QCLtype may be type A of the CSI-RS resource in the NZP-CSI-RS-resourceSet, which is configured with the higher-layer parameter trs-Info. For example, it may also be type D of the CSI-RS resource in the NZP-CSI-RS-resourceSet, which is configured with the higher-layer parameter repetition.

[0292] For PDSCH's DMRS, if terminal device 1 is configured with dl-OrJointTCI-StateList, terminal device 1 may expect the indicated TCI-State to indicate a certain QCLtype. This QCLtype may be a CSI-RS resource in the NZP-CSI-RS-resourceSet, configured by the higher-layer parameter trs-Info, and could be type A. For example, it could be a similar CSI-RS resource and type D.

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

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

[0295] Terminal device 1 may be configured with sfnSchemePDSCH. sfnSchemePDSCH may be configured with 'sfnSchemeB'. Terminal device 1 may be indicated by two TCI states in the code point of the DCI field. The DCI field may be 'Transmission Conifguration Indication'. The DCI field may be the DCI that schedules the PDSCH. When terminal device 1 is configured with sfnSchemePDSCH configured with 'sfnSchemeB' and is indicated by two TCI states in the code point of the DCI field 'Transmission Conifguration Indication', terminal device 1 may assume that the DMRS port of the PDSCH is the downlink reference signal and QCL in the two TCI states, with the exception of {Doppler Shift, Doppler Spread} in the second indicated TCI state.

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

[0297] Terminal device 1 may hold two specified TCI states. If terminal device 1 is configured with dl-OrJointTCI-StateList and holds two specified TCI states, and if 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 a DCI format 1_0 / 1_1 / 1_2 to be scheduled or activated is less than timeDurationForQCL in a certain frequency range, terminal device 1 may apply the first specified TCI state to the reception of the activated or scheduled PDSCH. The certain frequency range may be Frequency range 2. The certain frequency range may be FR2. The certain terminal capability may be [two default beams for S-DCI based MTRP]. The certain terminal capability may be the capability to determine two default beams for single DCI-based MTRP transmission. The certain terminal capability may be the capability to set two default beams for single DCI-based MTRP transmission.

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

[0299] When terminal device 1 is configured with dl-OrJointTCI-StateList and configured by the upper-layer parameter PDCCH-Config which includes two different coresetPoolIndex in ControlResourceSet, if terminal device 1 does not report a 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 in CORESET associated with coresetPoolIndex value 0 is less than [timeDurationForQCL] in a certain frequency domain, 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 higher-layer parameter PDCCH-Config which includes two different coresetPoolIndex in ControlResourceSet, if terminal device 1 does not report a terminal capability in a certain frequency domain, terminal device 1 does not need to expect that the offset between the reception of a scheduled or activated PDSCH and the reception of DCI format 1_0 / 1_1 / 1_2 in CORESET associated with the coresetPoolIndex value 1 is less than [timeDurationForQCL] in a certain frequency domain.

[0301] Terminal device 1 may be configured with dl-OrJointTCI-StateList and may hold two specified 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, terminal device 1 may operate in frequency range 1.

[0302] Terminal device 1 may be configured with dl-OrJointTCI-StateList and hold two designated 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, terminal device 1 may report terminal capability for [two default beams for S-DCI based MTRP] in frequency range 2.

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

[0304] 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 the activation or scheduled reception of PDSCH in DCI format 1_0. Terminal device 1 may be configured with cjtScheme. Terminal device 1 may be configured with sfnPDSCH. Terminal device 1 may report a terminal capability. A terminal capability may be [support for two joint TCI states for PDSCH-CJT]. A terminal capability may be the capability to support two joint TCIs for PDSCH-CJT. When terminal device 1 is configured with cjtScheme and reports a terminal capability, terminal device 1 may set only both values ​​in applyIndicatedTCIState. When terminal device 1 is configured with sfnPDSCH, terminal device 1 may set only both values ​​in applyIndicatedTCIState. If terminal device 1 is configured with only both values, terminal device 1 may be applied to receiving a PDSCH. That PDSCH may be a PDSCH scheduled or activated by DCI format 1_0. That DCI format 1_0 may be a DCI on a search space other than a certain search space on CORESET #0. That certain search space may be a search space other than Type0 / 0A / 2 CSS.

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

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

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

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

[0309] TCI selection method A may apply the second of two indicated joint / downlink TCI states to all PDSCH DMRS ports corresponding to PDSCH transmission opportunities to be activated or scheduled, according to DCI format 1_1 / 1_2, if DCI format 1_1 / 1_2 indicates code point “01” for [TCI selection field].

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

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

[0312] DCI format 1_1 / 1_2 may include a TCI selection field. The TCI selection field may contain TCI selection information. The TCI selection information may be transmitted by means of DCI format 1_1 / 1_2. The number of bits in the TCI selection may be determined based on a higher-layer parameter. That higher-layer parameter may be tciSelection-PresentInDCI. If tciSelection-PresentInDCI is not set, the TCI selection may consist of 0 bits. If tciSelection-PresentInDCI is set, the TCI selection may consist of 2 bits. If asymmetricTRP is set, the TCI selection may consist of 2 bits. If asymmetricTRP is set, the TCI selection may consist of 1 bit. If asymmetricTRP is set, the TCI selection may consist of 0 bits. Setting asymmetricTRP may mean that the TCI selection consists of at least 1 bit.

[0313] Terminal device 1 may be configured by the higher-level parameter repetitionScheme. repetitionScheme may be set to one of 'fdmSchemeA', 'fdmSchemeB', or 'tdmScheme'. Terminal device 1 not configured by dl-OrJointTCI-StateList may have two TCI states indicated by the code point of the DCI field 'TransmissionConfiguration Indication'. Terminal device 1 configured by dl-OrJointTCI-StateList may hold two indicated TCI states for application to PDSCH. Terminal device 1 may be indicated by a DMRS port. That DMRS port may be a CDM group with the DCI field 'Anntena Port(s)'. Terminal device 1 may be indicated by a DMRS port in a CDM group with the DCI field 'Anntena Port(s)'.

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

[0315] Terminal device 1 may be set to 'fdmSchemeB'. Terminal device 1 may receive two PDSCH transmission opportunities. The two PDSCH transmission opportunities may be transmission opportunities for similar TBs in their respective TCI states. 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 terminal device 1 is set to 'fdmSchemeB', terminal device 1 may receive two PDSCH transmission opportunities for its TB in their respective TCI states, each associated with a PDSCH transmission opportunity having a frequency domain resource allocation that does not overlap with other PDSCH transmission opportunities.

[0316] Terminal device 1 may be set to 'tdmSchemeA'. Terminal device 1 may receive two PDSCH transmission opportunities. The two PDSCH transmission opportunities may be transmission opportunities for similar TBs in their respective TCI states. Each TCI state may be associated with a certain PDSCH transmission opportunity. A certain PDSCH transmission opportunity may have a time-domain resource allocation that does not overlap with the other PDSCH transmission opportunity. Both PDSCH transmission opportunities may be received in a given slot. When terminal device 1 is set to 'tdmSchemeA', terminal device 1 may receive two PDSCH transmission opportunities for its TB in their respective TCI states, each associated with a PDSCH transmission opportunity, having a time-domain resource allocation that does not overlap with the other PDSCH transmission opportunities.

[0317] Receiving a PDSCH transmission opportunity in terminal device 1 may also mean receiving a PDSCH. PDSCH may also refer to a PDSCH transmission.

[0318] Terminal device 1 may be configured by the higher-level parameter repetitionNumber. Terminal device 1 may be configured by the higher-level parameter repetitionNumber in PDSCH-TimeDomainResourceAllocation. Terminal device 1 not configured in dl-OrJointTCI-StateList may be expected to be indicated by one or two TCI states by the code point in the DCI field 'Transmission Configuration Indication'. Terminal device 1 configured in dl-OrJointTCI-StateList may be expected to apply one or two indicated TCI states 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 contain repetitionNumber in PDSCH-TimeDomainResourceAllocation. A DMRS port may be a CDM group with the DCI field 'Antenna Port(s)'.

[0319] When two TCI states are indicated in the DCI's 'Transmission Configuration Indication' for terminal device 1, which is not set in dl-OrJointTCI-StateList, or when terminal device 1 holds the two indicated TCI states applied to the PDSCH, which are set in dl-OrJointTCI-StateList, terminal device 1 may expect to receive PDSCH transmission opportunities at multiple slot levels. PDSCH transmission opportunities may be the same TB. Terminal device 1 may receive with two TCI states. These two TCI states may be used across multiple PDSCH transmission opportunities in consecutive slots. Terminal device 1 may expect to receive PDSCH transmission opportunities at multiple slot levels of the same TB with two TCIs. These two TCI states may be used across multiple PDSCH transmission opportunities in consecutive slots.

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

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

[0322] Terminal device 1 may have inter-slot repetition set. The setting of inter-slot repetition may be indicated by the DCI field 'Time domain resource assignment' which indicates an entry containing repetitionNumber in PDSCH-TimeDomainResourceAllocation. When terminal device 1 does not have inter-slot repetition set, and terminal device 1 is not set in dl-OrJointTCI-StateList, and is indicated by one TCI state of the code point in the DCI field 'Transmission Configuration Indication', terminal device 1 may follow certain procedures for receiving PDSCH for PDCCH detection. When terminal device 1 does not have inter-slot repetition set, and terminal device 1 is set in dl-OrJointTCI-StateList, and terminal device 1 is expected to apply one indicated TCI state to PDSCH, terminal device 1 may follow certain procedures for receiving PDSCH for PDCCH detection.

[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 terminal capability. A terminal capability may be sfn-SchemeA-DynamicSwitching. A terminal capability may be sfn-SchemeB-DynamicSwitching. When terminal device 1 is configured with the upper-layer parameter sfnSchemePDSCH, which is set with sfnSchemeA or sfnSchemeB, and terminal device 1 reports a terminal capability, terminal device 1, which is not configured in dl-OrJointTCI-StateList, may be indicated by one or two TCI states in the code point of the DCI field 'Transmission Configuration Indication' in DCI format 1_1 / 1_2. When terminal device 1 is configured with the upper-level parameter sfnSchemePDSCH set in sfnSchemeA or sfnSchemeB, and terminal device 1 reports a terminal capability, terminal device 1 may maintain one or two specified TCI states that apply to PDSCH, as 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 terminal capability. A terminal capability may be sfn-SchemeA-DynamicSwitching. A terminal capability may be sfn-SchemeB-DynamicSwitching. When terminal device 1 is configured with the upper-layer parameter sfnSchemePDSCH, which is set with sfnSchemeA or sfnSchemeB, and terminal device 1 does not report a terminal capability, terminal device 1, which is not configured in dl-OrJointTCI-StateList, does not need to be expected by MACCE to be indicated by a single TCI state at any code point. When terminal device 1 is configured with the upper-layer parameter sfnSchemePDSCH set in sfnSchemeA or sfnSchemeB, and terminal device 1 does not report a terminal capability, terminal device 1 may maintain two specified TCI states that apply to PDSCH, as set in dl-OrJointTCI-StateList.

[0325] When terminal device 1 is configured with both sfnSchemePDSCH and sfnSchemePDCCH, terminal device 1 may be expected to be configured using the same method for both sfnSchemePDSCH and sfnSchemePDCCH. These methods may be 'sfnSchemeA' or 'sfnSchemeB'.

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

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

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

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

[0330] Terminal device 1 may be configured with a list of up to M TCI-UL-State settings, where M may be 64. TCI-UL-State may be configured within the upper-layer parameter BWP-UplinkDedicated. Each TCI-UL-State may include certain parameters, which may be parameters for a single reference signal. If applicable, certain parameters may be parameters for determining uplink space filters for PUSCH, PUCCH, and SRS.

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

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

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

[0334] When terminal device 1 is configured with dl-OrJointTCI-StateList or TCI-UL-State and holds two indicated TCI-States or TCI-UL-States, terminal device 1 configured with Type1 configredgrant2 corresponding PUSCH transmission 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, terminal device 1 may apply the first indicated TCI state to the PUSCH transmission opportunity or the PUSCH antenna port associated with the first SRS resource set. If both TCI states are indicated, terminal device 1 may apply the second indicated TCI state to the PUSCH transmission opportunity or the PUSCH antenna port associated with the second SRS resource set. If any TCI state other than both is indicated, terminal device may apply the first or second indicated TCI state to all PUSCH transmission opportunities.

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

[0336] Terminal device 1 may be configured with two uplinks on a serving cell. For terminal device 1 configured with two uplinks on a serving cell, a push retransmission for a TB on the serving cell does not need to be expected to be on a different uplink than the one used for the initial push transmission of that TB.

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

[0338] The two SRS resource sets may be configured with srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2. The two SRS resource sets may be configured with srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 in the upper-level parameter usage of the SRS resource set which is set as 'codebook' or 'nonCodebook'. The upper-level parameter enableSTx2PofmDCI may be set. PDCCH-Config may contain two different coresetPoolIndex values ​​in the ControlResourceSet for the active BWP of a serving cell. Operation 1 may occur when two SRS resource sets are configured with the upper-level parameter usage in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, in an SRS resource set set to 'codebook' or 'nonCodebook', and the upper-level parameter enableSTx2PofmDCI is set, and PDCCH-Config contains two different coresetPoolIndex values ​​in the ControlResourceSet for the active BWP of a serving cell. Operation 1 may occur when the two PUSCHs partially / completely overlap in the time domain. Operation 1 may occur when the two PUSCHs partially / completely overlap in the frequency domain, or do not overlap in the frequency domain. Operation 1 may occur when two PUSCHs that partially / completely overlap in the time domain and partially / completely overlap in the frequency domain, or do not overlap in the frequency domain, are dynamically scheduled by the DCI uplink grant. Operation 1 may be that the two PUSCHs partially / completely overlap in the frequency domain, or do not overlap in the frequency domain.Operation 1 may schedule two PUSCHs by configured grant that partially / completely overlap in the time domain and partially / completely overlap in the frequency domain, or do not overlap in the frequency domain. Operation 1 may not have to be present in each PDCCH if it is dynamically scheduled by DCI uplink grant or activated by DCI for configured grant if it is scheduled by DCI. Operation 1 may not expect terminal device 1 to be configured with different numbers of SRS resources in the two SRS resource sets. Operation 1 may expect terminal device 1 to be set to maxNrofPorts as 1 if uplink PTRS is configured.

[0339] The two SRS resource sets may be configured using srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2. The upper-level parameter usage within the SRS resource set may be set to 'codebook' or 'noncodebook'. The two SRS resource sets may be configured using the upper-level parameter usage within the SRS resource set, which is set to 'codebook' or 'noncodebook'. The two SRS resource sets may be configured using srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 using the upper-level parameter usage within the SRS resource set, which is set to 'codebook' or 'noncodebook'. The upper-level parameter multipanelScheme may be set to 'SDMscheme' or 'SFNscheme'. The upper-layer parameter rrc-ConfiguredUplinkGrant does not need to 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 terminal device 1 is configured with dl-OrJointTCI-StateList or TCI-UL-State, and the SRS resource set is set with 'codebook' or 'noncodebook', two SRS resource sets are configured with srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 in the upper layer parameter usage, and the upper layer parameter multipanelScheme is set with 'SDMscheme' or 'SFNscheme'. When this is the case, and the upper-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 in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2. The upper layer parameter usage in the SRS resource set may be set to 'codebook' or 'noncodebook'. Only one SRS resource set may be configured with the upper layer parameter usage in the SRS resource set set to 'codebook' or 'noncodebook'. Only one SRS resource set may be configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with the upper layer parameter usage in the SRS resource set set to 'codebook' or 'noncodebook'. The PUSCH transmission opportunity may be scheduled or activated by DCI format 0_1 or DCI format 0_2. The 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 configured 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 configured 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 configured by PUSCH-Config. When asymmetricTRP is configured, the upper layer parameter applyIndicatedTCIState-r18 configured by PUSCH-Config may be set to only both.

[0341] Terminal device 1 may be configured with the upper-level parameter enableSTx2PofmDCI. Terminal device 1 may be configured with the upper-level parameter PDCCH-Config. The PDCCH-Config may contain two different coresetPoolIndex values ​​for the ControlResourceSet for the active BWP of a serving cell. Terminal device 1 may be expected to be configured with two SRS resource sets. Terminal device 1 may be expected to be configured with two SRS resource sets in usage'codebook' or 'nonCodebook' in srs-ResourceSetToAddModList. When terminal device 1 is configured with the upper-level parameter enableSTx2PofmDCI, and when terminal device 1 is configured with the upper-level parameter PDCCH-Config, terminal device 1 may be expected to be configured with two SRS resource sets in usage'codebook' or 'nonCodebook' in srs-ResourceSetToAddModList. The PDCCH-Config may contain two different coresetPoolIndex values ​​for the ControlResourceSet for the active BWP of a serving cell. 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. That SRS resource set may be usage 'codebook' or 'nonCodebook'.When terminal device 1 is configured with the upper-level parameter enableSTx2PofmDCI, and when terminal device 1 is configured with the upper-level parameter PDCCH-Config, which includes two different coresetPoolIndex values ​​for 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', terminal device 1 may search only the CORESETs associated with coresetPoolIndex value 0.

[0342] The SRS resource set indicator may be 0 bits or 2 bits. The SRS resource set may indicate a first value. When the first value indicates 0, the SRI and Precoding information and number of layers may be associated with the first SRS resource set. When the first value indicates 0, the second SRI and the 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 and Precoding information and number of layers may be associated with the second SRS resource set. When the first value indicates 1, the second SRI and the 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 and Precoding information and number of layers may be associated with the first SRS resource set. When the first value indicates 2, the second SRI and the second Precoding information and number of layers may be associated with the 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 the PUSCH transmit 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 the PUSCH transmit opportunity / antenna port associated with the second SRS resource set. When the first value indicates 3, if a multipanelScheme is set, the first value may be reserved. The first value may be the code point of the 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 set in the list, two SRS resource set indicators, two Precoding information and number of layer fields, two SRIs, and two TPMIs may be provided by the DCI fields. The code point of the SRS resource set indicator may be indicated by '10'. When the code point 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 an 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 number of layers may be less than or equal to maxRankSdm or maxRankSdmDCI-0-2. The second number of layers 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 code point '00' or '01' of the SRS resource set indicator may be indicated. When the code point '00' or '01' of the SRS resource set indicator is indicated, the second SRI and the second TPMI may be reserved. When the code point '00' or '01' of the SRS resource set indicator is indicated, the first TPMI may be used to indicate a precoder. That precoder may be applied across a third number of layers.The third layer number may be less than or equal to maxRank. maxRank may define the maximum number of layers. When the upper layer parameter multipanelScheme is set to 'SDMScheme' and two SRS resource sets are set in the list, the code point '11' of 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 set in the list, two SRS resource set indicators, two Precoding information and number of layer fields, two SRIs and two TPMIs may be provided by the DCI fields. When the code point '10' of the SRS resource set indicator is indicated, the first TPMI may be used to indicate a precoder. That precoder may be applied across a fourth number of layers. The second TPMI may be used to indicate a precoder. That 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 code point '00' or '01' of the SRS resource set inidicator is indicated, the second SRI and second TPMI may be reserved. When the code point '00' or '01' of the SRS resource set inidicator is indicated, the first TPMI may be used to indicate a precoder. That 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 or second SRS resource set. The upper layer parameter multipanelScheme may be set to 'SFNScheme'. When the upper-level parameter multipanelScheme is set to 'SFNScheme' and two SRS resource sets are set in the list, the code point '11' of the SRS resource set indicator may be reserved.

[0345] PUSCH may be restricted to one layer. For PUSCH repetition Type A, if K is greater than 1, the same symbol assignment may be applied to K consecutive slots. When two SRS resource sets are set in the list by the upper layer parameter usage'codebook' or 'nonCodebook', for PUSCH repetition Type A, if K is greater than 1, the same symbol assignment may be applied to K consecutive slots, and PUSCH may be restricted to one layer. Terminal device 1 may repeat TB across K consecutive slots. The same symbol assignment may be applied to each of those K consecutive slots. The association of the first and second SRS resource sets in the list to each slot may be determined according to the repetition rule. In the repetition rule, if DCI format 0_3 schedules 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 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 in PUSCH-Config is enabled, 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 in PUSCH-Config is enabled, the first and second SRS resource sets are 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 K consecutive slots. In Repetition Mapping Rule 1, when K > 2 and sequentialMapping in PUSCH-Config is enabled, the first SRS resource set is applied to the first and second slots of K consecutive slots, the second SRS resource set is applied to the third and fourth slots of K consecutive slots, and the same SRS resource set mapping pattern may continue to the remaining slots of the 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 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 to the remaining slots of K consecutive slots.

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

[0347] When terminal device 1 is configured with dl-OrJointTCI-StateList or TCI-UL-State and holds two TCI-states or TCI-UL-States, and when two SRS resource sets are configured in the list with the upper layer parameter usage set to 'codebook' or 'nonCodebook' in the SRS resource set, the association of the first and second indicated TCI states to a PUSCH transmission opportunity or to the corresponding antenna port may be determined according to repetition rule 2, for PUSCH repetition Type A or Type B, or when the upper layer parameter multipanelScheme is set to 'SDMScheme' or 'SFNScheme'. In Repetition Rule 2, if DCI format 0_1 ​​or DCI format 0_2 indicates code point '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 code point '10' or '11' for the SRS resource set indicator, and no multipanelScheme is set, the first indicated TCI state may be applied to the PUSCH transmission opportunity associated with the first SRS resource set, and the second indicated TCI state may be applied to the PUSCH transmission opportunity associated with the second SRS resource set. The association of a PUSCH transmission opportunity to an SRS resource set may be determined for K=2 or K>2, or it may be determined by whether cyclicMapping or sequentialMapping is enabled based on Repetition Mapping Rule 1 or 2.In Repetition Rule 2, if DCI format 0_1 ​​or DCI format 0_2 indicates code point '10' for the SRS resource set indicator, and a multipanelScheme is set, and the 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 code point '10' for the SRS resource set indicator, and a multipanelScheme is set, and the 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 the corresponding PUSCH transmission opportunity. The PUSCH transmission opportunity may be associated with a second SRS resource set.

[0348] Terminal device 1 may be configured with a Unified TCI state. Configuring a Unified TCI state may also mean configuring dl-OrJointTCI-StateList. Configuring a Unified TCI state may also mean configuring ul-TCI-StateList. Configuring a Unified TCI state may mean configuring dl-OrJointTCI-StateList for the downlink and ul-TCI-StateList for the uplink. Configuring a Unified TCI state may mean configuring either dl-OrJointTCI-StateList or ul-TCI-StateList. Configuring a Unified TCI state may also mean providing a TCI-State or TCI-UL-State from dl-OrJointTCI-StateList.

[0349] Terminal device 1 may be provided with a TCI-State or TCI-UL-State from dl-OrJointTCI-StateList. If terminal device 1 is provided with a TCI-State or TCI-UL-State from dl-OrJointTCI-StateList, it may be provided with a reference signal index for each of the one or two indicated TCI states of the uplink physical channel. If a unified TCI state is set, a reference signal index may be provided for each of the one or two TCI states. For example, if an asymmetricTRP is not set and a unified TCI state is set, one reference signal index may be provided for each of the one or two TCI states. For example, if an asymmetricTRP is set and a unified TCI state is set, one reference signal index may be provided for each of the one or two TCI states. Setting a unified TCI state may mean providing a TCI-State or TCI-UL-State from dl-OrJointTCI-StateList. The reference signal index may be an index for obtaining a propagation loss estimate of the downlink for the uplink channel. The reference signal index may be provided by a higher-layer parameter. The higher-layer parameter may be contained within an indicated TCI-State or TCI-UL-State. The higher-layer parameter may be associated with an indicated TCI-State or TCI-UL-State. The reference signal index may be provided by a higher-layer parameter contained within an indicated TCI-state or TCI-UL-State. The reference signal index may be provided by a higher-layer parameter associated with an 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 propagation loss reference signal for asymmetricTRP. If p0AlphaSetforPUSCH is provided, then 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 specified TCI-State or TCI-UL-State.

[0350] Closed-loop power value f b，f，c (i, l) may be determined based on formula 1. b，f，c (i, l) may be determined based on the TPC command field. The TPC command field may be included in the DCI. b，f，c (i, l) may be determined based on Equation 1 if the first upper-level parameter is not provided. The first upper-level parameter may be the upper-level parameter tpc-Accumulation. The first upper-level parameter may be a dedicated upper-level parameter. The first upper-level parameter may be provided in the upper-level parameter PUSCH-Config. The first upper-level parameter does not have to be provided in the upper-level parameter ConfiguredGrantConfig. b，f，c (i, l) may be determined at the PUSCH transmission opportunity i. Closed-loop power value f b，f，c (i, l) may be determined based on equation 2. b，f，c (i, l) may be determined based on Equation 2 if a first upper-level parameter is provided.

[0351] δPUSCH, b, f, c(m, l) and δPUSCH, b, f, c(i, l) may be values ​​of a TPC command. δ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 PUSCH. The DCI may be a DCI corresponding to DCI format 2_2 with CRC scrambled by 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 be 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.

[0352] δPUSCH,b,f,c(m,l) and δPUSCH,b,f,c(i,l) corresponding to a power control state may be determined based on the TPC command field corresponding to that 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. A DCI format may include both the first and second TPC command fields. For example, if the upper-level parameter SecondTPCFieldDCI is set, a DCI format may include both the first and second TPC command fields. For example, if the upper-level parameter SecondTPCFieldDCI is set, the power control parameter set may correspond to one power control state. For example, if the upper-level parameter SecondTPCFieldDCI is not set, the power control parameter set may not correspond to one power control state. q d , α b，f，c (j), P O＿UE＿PUSCH，b，f，c (j), and P O＿PUSCH，b，f，c (j) part or all of it may be referred to as a power control parameter set. The power control parameter set may be provided based on an indicated DLorJoint-TCIState or an indicated UL-TCIState. For example, the power control parameter set may be provided by one or both of a first and second upper-level parameter associated with an indicated DLorJoint-TCIState or an indicated UL-TCIState. The first upper-level parameter may be p0-Alpha-CLID-PUSCH-Set or ul-powerControl. The second upper-level parameter may be PL-RS or pathlossReferenceRS-Id.

[0353] D i This may be a set of one or more TPC command values. C(D 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 PUSCH transmission opportunities i-i ０ K PUSCH (i-i ０ ) Symbol before the symbol and K of the PUSCH transmission opportunity i PUSCH (i) The symbol before the symbol may include the value of the TPC command received between it and the symbol. ０ i can be an integer greater than 0. For example, i ０ This may be the minimum value when condition 1 is satisfied. For example, condition 1 is PUSCH transmission opportunity i-i ０ K PUSCH (i-i ０ ) The symbol before the symbol is K of the PUSCH transmission opportunity i PUSCH (i) It may also be before the symbol preceding the symbol. i0 is the K of the PUSCH transmission opportunity i-i0. PUSCH (i-i0) The symbol before the PUSCH transmission opportunity i is K PUSCH (i) The smallest integer that is earlier than the symbol. i0 may be greater than 0.

[0354] Based on at least transmission opportunities i and i0, a certain PUSCH may not be transmitted. For example, K of PUSCH transmission opportunities i-i0. PUSCH (i-i0) Symbol from before PUSCH transmission opportunity i K PUSCH (i) A certain PUSCH may not be transmitted before the symbol. For example, a certain PUSCH may not be transmitted between PUSCH transmission opportunities i-i0 and PUSCH transmission opportunity i. For example, a certain PUSCH may not be transmitted in the middle of the sequence from the PUSCH in PUSCH transmission opportunities i-i0 to the PUSCH in PUSCH transmission opportunity i.

[0355] For each of the PUSCH, PUCCH, and SRS transmission opportunities, the terminal device 1 may provide the TCI-state or TCI-UL-State in the dl-OrJointTCI-StateList for the one or two TCI-states or TCI-UL-States specified. d The RS index may also be an RS index. The RS index may also be an index for downlink estimated propagation loss for PUSCH, PUCCH, and SRS transmissions. RS index q d This 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. SRS transmission opportunities do not have to be provided by followUnifiedTCI-StateSRS. If terminal device 1 provides a TCI-state or TCI-UL-State in dl-OrJointTCI-StateList for one or two indicated TCI-states or TCI-UL-States for each of the PUSCH, PUCCH, and SRS transmission opportunities, then RS index q for downlink estimated propagation loss for PUSCH, PUCCH, and SRS transmissions. d This 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.

[0356] PLoffset may be used for the uplink. PLoffset may be calculated by base station equipment 3. PLoffset is G b,f,c----(i) may also be the case. PLoffset may be the estimated uplink propagation loss in dB. PLoffset may be the estimated uplink propagation loss in dB between TRPs. PLoffset may be the estimated uplink propagation loss in dB between two different TRPs. PLoffset may be the difference in estimated uplink propagation loss in dB between two different TRPs and terminal device 1. When the TCI state associated with PLoffset is applied to SRS transmission, terminal device 1 may determine the SRS transmission power according to equation 3 or equation 4. In equation 4, G b,f,c---- (i) may be provided by a higher-level parameter, which may be a PLoffset, or it may be set within the TCI state.

[0357] In SRS transmission opportunity i, P SRS,b,f,c (i,q s P(l) may be determined by formula 3. In SRS transmission opportunity i, P SRS,b,f,c (i,q s ,l) may be determined by formula 4. If terminal device 1 transmits SRS based on the settings by SRS-ResourceSet, terminal device 1 shall, at the SRS transmission opportunity i, set the SRS transmission power P SRS,b,f,c (i,q s ,l) may be determined by formula 17. When terminal device 1 transmits SRS based on settings by upper layer parameters, the transmission power P of the SRS SRS,b,f,c (q s ) may be determined for each SRS transmission opportunity i. The upper layer parameter may be SRS-ResourceSet. P CMAX,b,f,c (i) The UE of the carrier f of serving cell c in the SRS transmission opportunity i may be the maximum transmit power set. O_SRS,b,f,c (q s ) may be provided by the upper layer parameter p0 in the active UL BWP b of the carrier f of serving cell c. SRS resource set q s This may be provided by the upper-level parameter SRS-ResourceSetId.SRS,b,f,c α may be the SRS bandwidth, expressed as the number of resource blocks for the SRS transmission opportunity i. SRS,b,f,c (q s ) is SRS resource set q s And, in the active UL BWP b of the carrier f of serving cell c, it may be provided by the upper layer parameter alpha. b,f,c (q d ) is SRS resource set q s This may also be an estimate of the downlink propagation loss in the active DL BWP of serving cell c. b,f,c (q d ) is when terminal device 1 has RS resource index q d The downlink propagation loss estimate may be calculated using the RS resource index q. d is SRS resource set q s The associated pathlossReferenceRS may provide the RS resource index. The RS resource index may also be ssb-Index, which provides the SSB index. The RS resource index may also be csi-RS-Index, which provides the CSI-RS resource index. If enablePL-RS-UpdateForPUSCH-SRS is provided to terminal device 1, a MAC CE will set the SRS resource q s RS resource index q d This may also be provided by the corresponding SRS-PathlossReferenceRS-Id.

[0358] h b,f,c (i,l) may be the power control applied state for SRS transmission opportunity i. b,f,c (i,l) may be the power control applied state for the SRS closed-loop index l. b,f,c(i,l) may be the power control applied state at the SRS transmission opportunity i and the active UL BWP b of the carrier f of the serving cell c. srs-PowerControlAdjustmentStates may indicate the same power control applied state for both the PUSCH transmission and the SRS transmission. If srs-PowerControlAdjustmentStates indicates the same power control applied state for both the PUSCH transmission and the SRS transmission, then h b,f,c (i,l) may be formula 5. In formula 5, f b,f,c (i,l) may be in a PUSCH power applied state. If terminal device 1 does not set PUSCH transmission in the active BWP b of carrier f of serving cell c, h b,f,c (i,l) may be formula 6. If srs-PowerControlAdjustmentStates indicates different power control application states for PUSCH transmission and SRS transmission, h b,f,c (i,l) may be Equation 6. Some upper-layer parameters may indicate different power control application states for PUSCH transmission and SRS transmission, and for SRS, two different closed-loop power control application states. If some upper-layer parameters are provided, h b,f,c (i,l) may be Equation 7. A certain upper layer parameter may be set for SRS for a certain carrier and for a certain BWP. A certain upper layer parameter may indicate two different closed-loop power control application states for SRS.

[0359] δ SRS,b,f,c This may be given by a table. If some upper layer parameters indicate two different closed-loop power control application states for SRS, then δ SRS,b,f,c (l) may be given by a table. δ SRS,b,f,c(m) may be co-coded with other TPC commands in PDCCH of DCI format 2_3. Equation 8 may be the sum of the values ​​of the TPC commands. Equation 8 may be the sum of the TPC commands in a set Si of TPC command values ​​of C(Si). The TPC commands in a set Si of TPC command values ​​of C(Si) are K of the transmission opportunity i of the SRS. SRS (i) Symbol before and SRS transmission opportunity i-i0 K SRS (i-i0)-1 may be a TPC command received between these two symbols. If a certain upper-layer parameter indicates two different closed-loop power control application states for the SRS, then Equation 9 may be the sum of the TPC command values.

[0360] PLoffset may be a path loss offset. PLoffset may be provided by the path loss offset value associated with the indicated TCI state. If a unified TCI state is set, PLoffset may be expected to be provided by the indicated TCI state.

[0361] If a Unified TCI state is provided, one or two TCI states may be indicated. If a Unified TCI state is provided, the reference signal index may be provided by the pathlossReferenceRS-Id associated with the indicated TCI state. If a Unified TCI state is provided, the PLoffset may be provided by the path loss offset value associated with the indicated TCI state. If a Unified TCI state is set, and p0AlphaSetforSRS is provided, and followUnifiedTCI-StateSRS is provided for the SRS resource, P O_UE_SRS , α SRSThe closed-loop index value may be provided by p0AlphaSetforSRS, associated with the indicated TCI state. If a unified TCI state is set and p0AlphaSetforSRS is provided and followUnifiedTCI-StateSRS is not provided for the SRS resource, P O_UE_SRS , α SRS The closed-loop index value may be provided by p0AlphaSetforSRS, which is associated with the TCI state of the SRS resource with the lowest SRS-ResourceId in the SRS resource set. If a unified TCI state is set and p0AlphaSetforSRS is provided and followUnifiedTCI-StateSRS is not provided for the SRS resources in the SRS resource set, P O_UE_SRS , α SRS The closed-loop index value may be provided by p0AlphaSetforSRS, associated with the TCI state of the SRS resource with the lowest SRS-ResourceId in the SRS resource set. O_SRS is P O_UE_SRS This may be the sum of p0 provided by the SRS resource set and P O_SRS is P O_UE_SRS It may also be the sum of p0 provided by the SRS resource set and .

[0362] If unifiedTCI-StateType is set for a serving cell, the network does not need to set SRS-specific power control parameters. SRS-specific power control parameters may be alpha. SRS-specific power control parameters may be pathlossRefereneRS. If followUnifiedTCI-StateSRS is not provided for an SRS-ResourceSet, the network may set SRS-specific power control parameters. If a TCI state is provided for an SRS resource, srs-TCI-State may be provided. When an SRS-Resource in an SRS-ResourceSet is set by followUnifiedTCI-StateSRS, srs-TCI-State for that SRS-Resource does not need to be provided. Providing followUnifiedTCI-StateSRS may mean that followUnifiedTCI-StateSRS is enabled. When enabled and set, terminal device 1 may apply the indicated TCI state for the SRS resource set. followUnifiedTCI-StateSRS may be set for aperiodic SRS for BM. `followUnifiedTCI-StateSRS` may be set for codebook, non-codebook, or antenna-switching SRS.

[0363] If a Unified TCI state is set and followUnifiedTCI-StateSRS is not provided, terminal device 1 may assume that the SRS resource can be set in the TCI state. If a Unified TCI state is set and followUnifiedTCI-StateSRS is not provided, terminal device 1 may assume that the SRS resource can be updated. If a Unified TCI state is set and followUnifiedTCI-StateSRS is not provided, terminal device 1 may assume that the SRS resource can be updated in MACCE. The reference signal for that TCI state may be a CSI-RS resource in the NZP-CSI-RS-Resourceset set in repetition. The reference signal for that TCI state may be a CSI-RS resource in the NZP-CSI-RS-Resourceset set in trs-Info. The reference signal for that TCI state may be an SRS resource set in beamManagement. The reference signal for that TCI state may be an SSB associated with a PCI different from the PCI of the serving cell, or the same PCI.

[0364] If a Unified TCI state is set and followUnifiedTCI-StateSRS is provided, terminal device 1 may transmit a target SRS resource in the SRS resource set in a certain spatial relationship. If applicable, the spatial relationship may refer to a reference signal used to determine the uplink transmission spatial filter. That reference signal may be determined based on the reference signal of the indicated TCI state. That reference signal may be determined based on the reference signal set in qcl-Type, which is set to 'TypeD' in the QCL-Info of the indicated TCI state. That TCI state reference reference signal may be a CSI-RS resource of the NZP-CSI-RS-Resourceset set in repetition. That TCI state reference reference signal may be a CSI-RS resource of the NZP-CSI-RS-Resourceset set in trs-Info. That TCI state reference reference signal may be an SRS resource set in beamManagement. That TCI state reference reference signal may be an SSB associated with a different PCI than the serving cell's PCI, or the same PCI.

[0365] When a unified TCI state is set and has one or two indicated TCI states, terminal device 1 may be configured with followUnifiedTCI-StateSRS. Terminal device 1 may be configured with followUnifiedTCI-StateSRS for the SRS resource sets 'codebook', 'noncodebook', and 'antennaSwitching'. Terminal device 1 may be configured with followUnifiedTCI-StateSRS for the aperiodic SRS resource set 'beamManagement'. When a unified TCI state is set and has one or two indicated TCI states, and terminal device 1 is configured with followUnifiedTCI-StateSRS, terminal device 1 may be configured with applyIndicatedTCIState. applyIndicatedTCIState may be a parameter that indicates whether the terminal device applies the first indicated TCI state to its SRS resource set or the second indicated TCI state to its SRS resource set. Terminal device 1 may be configured with a PDCCH-config that includes two different values ​​for coresetPoolIndex of ControlResourceSet. If terminal device 1 is configured with a PDCCH-config that includes two different values ​​for coresetPoolIndex of ControlResourceSet, the first and second indicated TCI states may correspond to the coresetPoolIndex values ​​of 0 and 1, respectively, for the indicated TCI states. If terminal device 1 is configured with a PDCCH-config that includes two different values ​​for coresetPoolIndex of ControlResourceSet, and an aperiodic SRS resource set not configured with applyIndicatedTCIState is triggered by PDCCH on the CORESET associated with the coresetPoolIndex value, terminal device 1 may apply the indicated TCI state of the coresetPoolIndex value to the aperiodic SRS resource set.When two SRS resource sets are configured as 'codebook' or 'nonCodebook', terminal device 1 does not need to expect the first specified TCI state to apply to the second SRS resource set.

[0366] The first upper layer parameter may be p0AlphaSetforSRS. The first upper layer parameter may be a power control parameter for SRS. The second upper layer parameter may be followUnifiedTCI-StateSRS. When the second upper layer parameter is set to enabled, the terminal may apply the TCI state indicated for the SRS resource set. The second upper layer parameter may be set for aperiodic SRS of beamManagement. The second upper layer parameter may be set for SRS of codebook, nonCodebook, or antennaswitching. The third upper layer parameter may be PLoffset. The third upper layer parameter may be a parameter for setting the propagation loss offset. Setting a unified TCI state may mean setting the first upper layer parameter. Setting a unified TCI state may mean setting dlOrJointTCI-StateList. Setting a unified TCI state may mean providing a TCI state in dlOrJointTCI-StateList. Providing a unified TCI state may mean setting a unified TCI state.

[0367] The fifth upper layer parameter may be the closedLoopIndex. The fifth upper layer parameter may be a parameter for indicating a closed loop index. The fifth upper layer parameter may be set within the SRS resource set. The sixth upper layer parameter may be the PLoffset. The sixth upper layer parameter may indicate a propagation loss offset. The sixth upper layer parameter may be set within the SRS resource set. When a unified TCI state is provided and no second upper layer parameter is provided for the SRS resource set, the sixth upper layer parameter may be set for the SRS resource set. When a unified TCI state is provided and no second upper layer parameter is provided for the SRS resource set, the fifth upper layer parameter may be set for the SRS resource set.

[0368] The first MAC CE may be a MAC CE for updating a path loss offset for a TCI state. The TCI state may be an indicated TCI state. The TCI state may be an activated TCI state. When a unified TCI state is provided and a second upper layer parameter is set, the third upper layer parameter may be updated by the first MAC CE. The TCI state may be an activated TCI state. When a unified TCI state is provided and a second upper layer parameter is set, the third upper layer parameter may be considered not to be updated by the first MAC CE. The second MAC CE may be a MAC CE for updating a path loss offset for the SRS resource set. When a unified TCI state is provided and a second upper layer parameter is set, the sixth upper layer parameter may be updated by the first MAC CE. The third upper layer parameter and the sixth upper layer parameter may be the same. The third upper layer parameter and the sixth upper layer parameter may be different parameters.

[0369] The reference signal may be provided by the referenceSignal in the TCI state. The referenceSignal may be optional. The spatial filter may be a spatial filter.

[0370] If a second upper-level parameter is provided for the SRS resource set, the indicated TCI state may be associated with the SRS resource set.

[0371] If a second upper-level parameter is provided for the SRS resource set, the closed-loop index may be provided by the first TCI state. If a second upper-level parameter is provided for the SRS resource set, the path loss offset may be provided by the first TCI state. If a second upper-level parameter is not provided for the SRS resource set, the closed-loop index may be provided by the second TCI state. If a second upper-level parameter is not provided for the SRS resource set, the path loss offset may be provided by the second TCI state. The first TCI state and the second TCI state may be different TCI states. The first TCI state may be an indicated TCI state. The second TCI state may be a TCI state associated with an SRS resource in the SRS resource set. The second TCI state may be a TCI state associated with the SRS resource with the lowest ID in the SRS resource set.

[0372] If a second upper-level parameter is not provided, it is expected that at least one SRS resource in the SRS resource set will have a TCI state.

[0373] If a second upper-layer parameter is not provided, the closed-loop index may be provided by the SRS resource set. If a second upper-layer parameter is not provided, the path loss offset may be provided by the SRS resource set.

[0374] The first MACCE may update the path loss offset for the indicated TCI state. The first MACCE may update the path loss offset for the activated TCI state. The first MACCE may update the path loss offset for the set TCI state. If a second upper layer parameter is provided, the first MACCE may update the path loss offset for the indicated TCI state. If a second upper layer parameter is provided, the first MACCE may update the path loss offset for the activated TCI state. If a second upper layer parameter is provided, the first MACCE may update the path loss offset for the set TCI state. If a second upper layer parameter is not provided for an SRS resource set, the first MACCE does not need to update the path loss offset for the indicated TCI state. If a second upper layer parameter is not provided for an SRS resource set, the first MACCE does not need to update the path loss offset for the activated TCI state. If a second upper layer parameter is not provided, the first MACCE does not need to update the path loss offset for the set TCI state. If a second upper layer parameter is not provided, the first MACCE does not need to update the path loss offset for the second TCI state.

[0375] The first upper-level parameter may be a parameter for introducing a TPC command for SRS for DCI format 1_1. When the first upper-level parameter is set, a TPC command for SRS may exist for DCI format 1_1. When the first upper-level parameter is set to 'enabled', a TPC command for SRS may exist for DCI format 1_1. When the first terminal capability is reported, it can be expected that the first upper-level parameter will be set. The second upper-level parameter may be a parameter for providing a closed-loop instruction field for SRS for DCI format 1_1. When the second upper-level parameter is set, a closed-loop instruction field for SRS may exist for DCI format 1_1. When the second terminal capability is reported, it can be expected that the second upper-level parameter will be set. The first and second terminal capabilities may be different terminal capabilities. The first and second terminal capabilities may be the same terminal capability. The first upper-level parameter may be set in SRS-Config. The second upper-level parameter may be set in SRS-Config. A third upper-layer parameter may be a parameter for enabling two different closed-loop power control application states for the SRS. The third upper-layer parameter may be set within SRS-Config.

[0376] If a third upper-level parameter is set, it may be expected that both the first and second upper-level parameters are set simultaneously. The first and second upper-level parameters may be the same parameter. The first and second upper-level parameters may be different parameters. The DCI may be DCI format 1_1. If a third upper-level parameter is set and a TPC command is obtained from DCI format 1_1, the closed-loop index may be provided by the closed-loop instruction of the DCI. If index 0 is provided by the closed-loop instruction field, l=0 may be applied. If closed-loop index 1 is provided by the closed-loop instruction field, l=1 may be applied. If index 0 is provided by the closed-loop instruction field, i0 may be applied. If closed-loop index 1 is provided by the closed-loop instruction field, i1 may be applied.

[0377] The first value may be 0. The first value may be 1. If a third upper-level parameter is set, and the first upper-level parameter is set, and the second upper-level parameter is not set, the closed-loop index may be 0. If a third upper-level parameter is set, and the first upper-level parameter is set, and the second upper-level parameter is not set, the closed-loop index may be 1. The first value may be set by some upper-level parameter. Some upper-level parameter may be set within an SRS resource set. Some upper-level parameter may be set within an SRS resource.

[0378] A nonperiodic SRS resource set may be triggered by DCI format 1_1. The triggered SRS resource set may be provided with followUnifiedTCI-StateSRS. The triggered SRS resource set may not be provided with followUnifiedTCI-StateSRS.

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

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

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

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

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

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

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

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

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

[0388] While embodiments of this invention have been described in detail above with reference to the drawings, the specific configuration is not limited to these embodiments, and design modifications and the like that do not depart from the gist of this invention are also included. Furthermore, the present invention can be modified in various ways 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 this invention. In addition, configurations in which elements described in each of the above embodiments that produce similar effects are substituted for each other are also included.

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

[0390] 1 (1A, 1B, 1C) Terminal device 3 Base station device 10, 30 Wireless transceiver unit 10a, 30a Wireless transmitter unit 10b, 30b Wireless receiver unit 11, 31 Antenna unit 12, 32 RF unit 13, 33 Baseband unit 14, 34 Upper layer processing unit 15, 35 Media access control layer processing unit 16, 36 Wireless resource control layer processing unit 91, 92, 93, 94 Search area set 300 Component carrier 301 Primary cell 302, 303 Secondary cell 700 Set of resource elements for PSS 710, 711, 712, 713 Set of resource elements for PBCH and DMRS for PBCH 720 Set of resource elements for SSS 3000 Point 3001, 3002 Resource grid 3003, 3004 BWP 3011, 3012, 3013, 3014 Offset 3100, 3200 Common Resource Block Set

Claims

1. A terminal device comprising: a first upper layer parameter including a plurality of first TCI-States; a second upper layer parameter and one second TCI-State for each SRS resource; a receiving unit that receives a PDCCH on which a DCI is located; and a transmitting unit that transmits SRS to a plurality of SRS resources included in an SRS resource set, wherein the second upper layer parameter is a parameter that instructs the SRS resource set to apply a TCI-State indicated by the DCI; when the first upper layer parameter is provided, the transmit power of the SRS is determined based on the path loss offset; when the second upper layer parameter is provided for the SRS resource set, the value of the path loss offset is provided by one of the plurality of first TCI-States indicated by the DCI; and when the second upper layer parameter is not provided for the SRS resource set, the value of the path loss offset is provided by the second TCI-State of the SRS resource with the lowest SRS resource ID in the SRS resource set.

2. The terminal device according to claim 1, wherein the value of the path loss offset is updated by the first MACCE.

3. A base station device comprising: an upper layer processing unit that transmits a first upper layer parameter including a plurality of first TCI-States, a second upper layer parameter, and one second TCI-State for each SRS resource; a transmitting unit that transmits a PDCCH on which a DCI is located; and a receiving unit that receives SRS in a plurality of SRS resources included in an SRS resource set, wherein the second upper layer parameter is a parameter that instructs the SRS resource set to apply a TCI-State indicated by the DCI; when the first upper layer parameter is provided, the transmit power of the SRS is determined based on the path loss offset; when the second upper layer parameter is provided for the SRS resource set, the value of the path loss offset is provided by one of the plurality of first TCI-States indicated by the DCI; and when the second upper layer parameter is not provided for the SRS resource set, the value of the path loss offset is provided by the second TCI-State of the SRS resource with the lowest SRS resource ID in the SRS resource set.

4. The base station device according to claim 3, wherein the value of the path loss offset is updated by the first MACCE.

Images