Terminal device, base station device, and communication method

Abstract

The present invention comprises: a higher layer processing unit that receives information including a first parameter and a second parameter; a reception unit that receives downlink control information (DCI) which is carried via a downlink control channel (PDCCH); and a transmission unit that transmits a PUSCH which is scheduled by the DCI. When an SRS resource set indicator included in the DCI indicates 00 or 01, a maximum number of layers is determined by the first parameter. When the SRS resource set indicator included in the DCI indicates 10, a maximum number of layers is determined by the second parameter. When the SRS resource set indicator included in the DCI indicates 00 or 01, the DCI designates a first precoder that is used for the PUSCH, and the transmission unit transmits the PUSCH on the basis of the first precoder. When the SRS resource set indicator included in the DCI indicates 10, the DCI designates a second precoder and a third precoder that are used for the PUSCH, and the transmission unit transmits the PUSCH on the basis of the second precoder and the third precoder.

Description

Terminal device, base station device, and communication method

[0001] The present invention relates to a terminal device, a base station device, and a communication method. This application claims priority to Japanese Patent Application No. 2023-164666, filed on September 27, 2023, the contents of which are incorporated herein by reference.

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

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

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

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

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

[0007] (1) A first aspect of the present invention is a terminal device, comprising: an upper layer processing unit that receives information including a first parameter and a second parameter; a receiving unit that receives downlink control information (DCI) carried by a downlink control channel (PDCCH); and a transmitting unit that transmits a PUSCH scheduled by the DCI. When an SRS resource set indicator included in the DCI indicates 00 or 01, the maximum number of layers is determined by the first parameter; when the SRS resource set indicator included in the DCI indicates 10, the maximum number of layers is determined by the second parameter; when the SRS resource set indicator included in the DCI indicates 00 or 01, the DCI indicates a first precoder to be used for the PUSCH; and the transmitting unit transmits the PUSCH based on the first precoder. If the indicator indicates 10, the DCI indicates the second precoder and the third precoder to be used for the PUSCH, and the transmitter transmits the PUSCH based on the second precoder and the third precoder.

[0008] (2) Furthermore, a second aspect of the present invention is a base station apparatus comprising: an upper layer processing unit that transmits information including a first parameter and a second parameter; a transmitting unit that transmits downlink control information (DCI) carried on a downlink control channel (PDCCH); and a receiving unit that receives a PUSCH scheduled by the DCI. When an SRS resource set indicator included in the DCI indicates 00 or 01, the maximum number of layers is determined by the first parameter; when the SRS resource set indicator included in the DCI indicates 10, the maximum number of layers is determined by the second parameter; when the SRS resource set indicator included in the DCI indicates 00 or 01, the DCI indicates a first precoder to be used for the PUSCH; and when the SRS resource set indicator included in the DCI indicates 10, the DCI indicates a second precoder and a third precoder to be used for the PUSCH.

[0009] (3) Also, a third aspect of the present invention is a communication method used in a terminal device, the communication method comprising: receiving information including a first parameter and a second parameter; receiving downlink control information (DCI) carried by a downlink control channel (PDCCH); and transmitting a PUSCH scheduled by the DCI. When an SRS resource set indicator included in the DCI indicates 00 or 01, the maximum number of layers is determined by the first parameter; when the SRS resource set indicator included in the DCI indicates 10, the maximum number of layers is determined by the second parameter; and when the SRS resource set indicator included in the DCI indicates 00 or 01, the DCI indicates a first precoder to be used for the PUSCH; and the transmission unit transmits the PUSCH based on the first precoder. If the indicator indicates 10, the DCI indicates the second precoder and the third precoder to be used for the PUSCH, and the transmitter transmits the PUSCH based on the second precoder and the third precoder.

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

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

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

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

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

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

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

[0017] The base station device 3 may be configured to include one or more transmitting devices (or transmission points, transmitting / receiving devices, or transmitting / receiving points). When the base station device 3 is configured with multiple transmitting devices, each of the multiple transmitting devices may be located at a different location. For example, the base station device 3 may be configured with a transmitting device 3a and a transmitting device 3b. For example, the base station device 3 may be configured with a transmitting / receiving point 3a and a transmitting / receiving point 3b. For example, the base station device 3 may be configured with a transmitting / receiving device 3a and a transmitting / receiving device 3b.

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

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

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

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

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

[0023] The subscript x added to the resource grid related parameters indicates the transmission direction, for example, the subscript x may be used to indicate downlink or uplink.

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

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

[0026] FIG. 2 shows a subcarrier spacing setting μ and the number of OFDM symbols per slot N according to one aspect of this embodiment. slot symb 2A, for example, when the subcarrier spacing setting μ is 2 and the CP setting is normal cyclic prefix (CP), N slot symb = 14, N frame，μslot = 40, N subframe，μ slot In addition, in FIG. 2B, for example, when the subcarrier spacing setting μ is 2 and the CP setting is an extended cyclic prefix (CP), N slot symb = 12, N frame，μ slot = 40, N subframe，μ slot =4.

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

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

[0029] The length of one slot may be determined based on the subcarrier spacing setting μ. When μ is 0, the length of one slot may be 1 ms. When μ is 1, the length of one slot may be 0.5 ms. When μ is 2, the length of one slot may be 0.25 ms. When μ is 3, the length of one slot may be 0.125 ms.

[0030] In one carrier, there is a first set of one or more frames in the uplink and a second set of one or more frames in the downlink. The uplink frame for transmission from the terminal device 1 is T 10 15 20 25 30 35 40 45 50 55 60 65 2 before the start of the downlink frame. TA It starts from the front. TA is (N TA ・N TA,offset )T c may be.

[0031] An OFDM symbol is a time domain unit of a communication system. 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.

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

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

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

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

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

[0037] In the common resource block set 3100, the common resource block including the point 3000 (the black block in the common resource block set 3100 in FIG. 3 ) is also referred to as the reference point of the common resource block set 3100. The reference point of the common resource block set 3100 may be the common resource block with index 0 in the common resource block set 3100.

[0038] The offset 3011 is the offset from the reference point of the common resource block set 3100 to the reference point of the resource grid 3001. The offset 3011 is determined by the subcarrier spacing setting μ １ The resource grid 3001 is represented by the number of common resource blocks for N size，μ grid１，x It contains common resource blocks.

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

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

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

[0042] The offset 3012 is the offset from the reference point of the common resource block set 3200 to the reference point of the resource grid 3002. The offset 3012 is the offset from the reference point of the common resource block set 3200 to the reference point of the resource grid 3002. ２The resource grid 3002 is represented by the number of common resource blocks relative to the N size，μ grid２，x It contains common resource blocks.

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

[0044] 4 is a diagram showing an example of the configuration of a resource grid 3001 according to one aspect of this embodiment. In the resource grid of FIG. 4, the horizontal axis represents the OFDM symbol index l sym and the vertical axis is the subcarrier index k sc The resource grid 3001 is size，μ grid１，x N RB sc contains N subcarriers, subframe，μ symb Within the resource grid, subcarrier index k sc and OFDM symbol index l sym The resource specified by is also called a resource element (RE).

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

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

[0047] The common resource blocks for a given subcarrier spacing setting μ are indexed in a given common resource block set in the frequency domain in ascending order starting from 0. The common resource block with index 0 for a given subcarrier spacing setting μ contains (or collides with, or coincides with) point 3000. The index n of the common resource block for a given subcarrier spacing setting μ μ CRB is n μ CRB = ceil(k sc / N RB sc ) relationship is satisfied. Here, k sc The subcarrier with .gt.=0 is a subcarrier having the same center frequency as the subcarrier corresponding to point 3000.

[0048] The physical resource blocks for a given subcarrier spacing setting μ are indexed in the frequency domain in ascending order starting from 0 in a given BWP. The index n of the physical resource block for a given subcarrier spacing setting μ is μ PRB is n μ CRB = n μ PRB +N start，μ BWP，i where N start，μ BWP，i denotes the reference point of the BWP with index i.

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

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

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

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

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

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

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

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

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

[0058] The medium access control layer processing unit 35 included in the upper layer processing unit 34 performs MAC layer processing. The MAC layer processing may be processing by a MAC entity.

[0059] The radio resource control layer processing unit 36 ​​included in the upper layer processing unit 34 performs processing of the RRC layer. The radio resource control layer processing unit 36 ​​manages various setting information / parameters (RRC parameters) of the terminal device 1. The radio resource control layer processing unit 36 ​​sets parameters based on an RRC message received from the terminal device 1.

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

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

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

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

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

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

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

[0067] Each of the serving cells configured for the terminal device 1 may be any of a PCell (Primary cell), a PSCell (Primary SCG cell), and an SCell (Secondary Cell). An SpCell may refer to one or both of a PCell and a PSCell.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0086] The radio resource control layer processing unit 16 included in the upper layer processing unit 14 performs processing of the RRC layer. The radio resource control layer processing unit 16 manages various setting information / parameters (RRC parameters) of the terminal device 1. The radio resource control layer processing unit 16 sets the RRC parameters based on an RRC message received from the base station device 3.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0113] The transmission of the PUSCH and the transmission of the DMRS for the PUSCH may be indicated (or scheduled) by one DCI format. The PUSCH and the DMRS for the PUSCH may be collectively referred to as the PUSCH. Transmitting the PUSCH may be equivalent to transmitting the PUSCH and the DMRS for the PUSCH.

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

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

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

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

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

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

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

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

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

[0123] The SS / PBCH block index bits are used to indicate the SS / PBCH block index. The SS / PBCH block index bits include three bits. The SS / PBCH block index bits may be configured with three bits of a six-bit SS / PBCH block index indicator. The SS / PBCH block index indicator may be used to identify at least SS / PBCH blocks from index 0 to index 63. The SS / PBCH blocks may be referred to as SSBs.

[0124] The subcarrier offset bits are used to indicate a subcarrier offset, which may be used to indicate the difference between the first subcarrier to which the PBCH is mapped and the first subcarrier to which the control resource set with index 0 is mapped.

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

[0126] The downlink control information may be transmitted with a DCI format. The DCI format may be interpreted as a format of the downlink control information. The DCI format may also be interpreted as a set of downlink control information set in a certain downlink control information format.

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

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

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

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

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

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

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

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

[0135] DCI format 0_0 may not include a carrier indicator field. That is, the serving cell to which the uplink component carrier on which the PUSCH scheduled by DCI format 0_0 is allocated may be the same as the serving cell of the uplink component carrier on which the PDCCH including the DCI format 0_0 is allocated. By detecting DCI format 0_0 on a downlink component carrier of a serving cell, the terminal device 1 may recognize that the PUSCH scheduled by DCI format 0_0 is allocated on the uplink component carrier of the serving cell.

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

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

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

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

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

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

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

[0143] The DCI format 0_1 ​​that does not include a BWP field may be a DCI format for scheduling a PUSCH without changing the active uplink BWP. The terminal device 1 may recognize that the PUSCH is to be transmitted without switching the active uplink BWP based on detecting the DCI format 0_1 ​​that is used for scheduling a PUSCH and does not include a BWP field.

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

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

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

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

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

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

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

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

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

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

[0154] DCI format 1_0 may not include a carrier indicator field. That is, a downlink component carrier on which a PDSCH scheduled by DCI format 1_0 is arranged may be the same as a downlink component carrier on which a PDCCH including DCI format 1_0 is arranged. By detecting DCI format 1_0 in a certain downlink component carrier, the terminal device 1 may recognize that a PDSCH scheduled by DCI format 1_0 is to be arranged on the downlink component carrier.

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

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

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

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

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

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

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

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

[0163] The BWP field of DCI format 1_1 may be used to indicate the downlink BWP in which the PDSCH scheduled by the DCI format 1_1 is arranged. That is, DCI format 1_1 may involve a change of the active downlink BWP. The terminal device 1 may recognize the downlink BWP in which the PUSCH is arranged by detecting DCI format 1_1 used for scheduling the PDSCH.

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

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

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

[0167] The PDSCH may be transmitted to transmit a transport block. The PDSCH may be used to transmit a transport block delivered by the DL-SCH. The PDSCH may be used to transmit a transport block. A transport block may be allocated to the PDSCH. A transport block corresponding to the DL-SCH may be allocated to the PDSCH. The base station device 3 may transmit the PDSCH. The terminal device 1 may receive the PDSCH.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0181] The BCH of the transport layer is mapped to the PBCH of the physical layer. That is, transport blocks carried on the BCH of the transport layer are delivered to the PBCH of the physical layer. The UL-SCH of the transport layer is mapped to the PUSCH of the physical layer. That is, transport blocks carried on the UL-SCH of the transport layer are delivered to the PUSCH of the physical layer. The DL-SCH of the transport layer is mapped to the PDSCH of the physical layer. That is, transport blocks carried on the DL-SCH of the transport layer are delivered to the PDSCH of the physical layer.

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

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

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

[0185] For example, system information (SI) may be composed of an MIB and several SIBs (System Information blocks). Also, system information may be divided into Minimum SI and Other SI. Minimum SI may include basic information required for initial access. Furthermore, Minimum SI may include information for acquiring Other SI. Minimum SI may be composed of an MIB and SIB1. Other SI may include all SIBs not broadcast in Minimum SI. These SIBs may be broadcast or transmitted in DL-SCH.

[0186] SIB1 may define the scheduling of Other SI. SIB1 may include information required for initial access. SIB1 may be referred to as RMSI (Remaining Minimum SI). SIB1 may be periodically left on the DL-SCH. SIB1 may be transmitted in a dedicated manner on the DL-SCH to some UEs in RRC_CONNECTED state.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0211] One CORESET pool index may be provided for one or more control resource sets (CORESETs). For example, the CORESET pool index may be provided by a higher layer parameter. For example, if not provided by the higher layer parameter, the CORESET pool index may be 0. The value of the CORESET pool index may be 0 or 1. The CORESET pool index may also be referred to as the index of the CORESET resource pool. For example, in one active downlink BWP of one serving cell, the CORESET pool index may be provided. For example, a CORESET pool index of value 0 may be provided for the first plurality of CORESETs.

[0212] The terminal device 1 may apply a first procedure for reporting HARQ-ACK information associated with first CORESETs and a second procedure for reporting HARQ-ACK information associated with second CORESETs. The terminal device 1 may apply the first procedure and the second procedure separately. The first CORESETs and the second CORESETs may be CORESETs in an active downlink BWP of one serving cell. A CORESET pool index of value 0 may be provided for the first CORESETs. A CORESET pool index of value 1 may be provided for the second CORESETs. The first CORESETs may be one or more first CORESETs. The second CORESETs may be one or more second CORESETs.

[0213] A Transmission Configuration Indication state (TCI state) may be provided by a DCI format. One or more TCI state configurations (or a list of configurations) may be provided by higher layer parameters for decoding the PDSCH. For example, the terminal device 1 may decode the PDSCH according to the PDCCH to be decoded. One TCI state may include parameters for setting a QCL relationship between a downlink reference signal and a first antenna port. For example, the first antenna port may be a DMRS port (an antenna port associated with DMRS) of the PDSCH. The first antenna port may be a DMRS port of the PDCCH. The first antenna port may be a CSI-RS port of the CSI-RS resource. The QCL relationship may be set by higher layer parameters. For example, the QCL relationship may be set by higher layer parameters qcl-Type1 for the first downlink reference signal. For example, the QCL relationship may be set by higher layer parameters qcl-Type2 for the second downlink reference signal. For example, the QCL relationship between the first antenna port and the second antenna port may indicate that the first antenna port and the second antenna port are QCLs. The downlink reference signal may be a CSI-RS or an SS / PBCH block.

[0214] The CORESET pool index of the first CORESET may be different from the CORESET pool index of the second CORESET. The inclusion of two different values ​​of the CORESET pool index in different CORESETs may be configured by a higher layer parameter. A first antenna port associated with one CORESET pool index of one serving cell may be assumed to be a first reference signal and a QCL.

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

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

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

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

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

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

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

[0222] The upper layer parameter tdd-UL-DL-ConfigurationCommon may be a parameter for configuring a UL slot, a DL slot, or a special slot for each of one or more slots. The upper layer parameter tdd-UL-DL-ConfigurationDedicated may be a parameter for configuring a UL symbol, a DL symbol, or a flexible symbol for each of the one or more slots. The tdd-UL-DL-ConfigurationCommon may be a common upper layer parameter. The tdd-UL-DL-ConfigurationDedicated may be a dedicated upper layer parameter. Configuring a UL slot, a DL slot, or a special slot for each of one or more slots may be configuring a TDD pattern or a slot format.

[0223] PUSCH-Config may be a dedicated upper layer parameter. PUSCH-ConfigCommon may be a common upper layer parameter. PUSCH-Config may be set for each BWP for PUSCH transmission. PUSCH-Config may include multiple upper layer parameters related to PUSCH transmission. PUSCH-Config may be a UE-specific setting. For example, PUSCH-Config or multiple upper layer parameters included in PUSCH-Config may be different for terminal device 1A, terminal device 1B, and terminal device 1C in one cell. PUSCH-ConfigCommon may be set for each BWP for PUSCH transmission. PUSCH-ConfigCommon may include multiple upper layer parameters related to PUSCH transmission. PUSCH-ConfigCommon may be a cell-specific setting. For example, PUSCH-ConfigCommon may be common for terminal device 1A, terminal device 1B, and terminal device 1C in one cell. For example, PUSCH-ConfigCommon may be provided by system information.

[0224] At least two transmission schemes may be supported for the PUSCH. For example, codebook-based transmission may be one of the transmission schemes for the PUSCH. For example, non-codebook-based transmission may be one of the transmission schemes for the PUSCH. A higher layer parameter may provide either codebook transmission or non-codebook transmission. For example, if 'codebook' is set for the higher layer parameter, the terminal device 1 may be configured for codebook transmission. For example, if 'nonCodebook' is set for the higher layer parameter, the terminal device 1 may be configured for non-codebook transmission. The higher layer parameter may be txConfig. The higher layer parameter may be usage. For example, if the higher layer parameter is not set, the terminal device 1 may not expect to be scheduled by either DCI format 0_1 ​​or DCI format 0_2. If the PUSCH is scheduled by DCI format 0_0, transmission of the PUSCH may be based on at least one antenna port.

[0225] In codebook transmission, the PUSCH may be scheduled by a DCI format. The DCI format may be any of DCI format 0_0, DCI format 0_1, and DCI format 0_2. In codebook transmission, the PUSCH may be configured to be transmitted semi-statically. The terminal device 1 may determine one or more precoders for PUSCH transmission. For example, the precoder may be determined based on at least some or all of an SRS resource indicator (SRI), a transmitted precoding matrix indicator (TPMI), and a transmission rank (transmission rank). For example, the SRI may be provided by a DCI field of an SRS resource indicator of 1 or 2. The DCI fields indicating the SRI may be referred to as a first SRI field and a second SRI field. For example, the TPMI may be provided by a DCI field of precoding information of 1 or 2. For example, the transmission rank may be provided by a DCI field for the number of layers (number of transmission layers). The fields indicating the TPMI may be referred to as a first TPMI field and a second TPMI field. The number of layers may be provided by a first TPMI field and part or all of a second TPMI field. The number of layers may be provided by a first SRI field and part or all of a second SRI field. The SRI may be provided by a first higher layer parameter. The TPMI and transmission rank may be provided by a second higher layer parameter. The first higher layer parameter may be srs-ResourceIndicator or srs-ResourceIndicator2. The second higher layer parameter may be precodingAndNumberOfLayers or precodingAndNumberOfLayers2.

[0226] The SRS resource set applied to the PUSCH may be determined based on a higher layer parameter. The PUSCH may be scheduled by DCI format 0_1 ​​or DCI format 0_2. The higher layer parameter may be srs-ResourceSetToAddModList or srs-ResourceSetToAddModeListDCI-0-2. The higher layer parameter may be an upper layer parameter configured in SRS-Config.

[0227] If the upper layer parameter usage is set to 'codebook', one or two SRS resource sets may be configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2. The upper layer parameter usage may be configured in the upper layer parameter SRS-ResourceSet.

[0228] When one SRS resource set is configured, the SRI and TPMI may be provided by the DCI field. The TPMI may be used to indicate a precoder. The precoder may be applied across v layers. When multiple SRS resources are configured, one SRS resource may be selected by the SRI. The transmit precoder (precoder) may be selected from a codebook (uplink codebook). For example, the codebook may have the number of antenna ports. The number of antenna ports may be equal to the upper layer parameter nrofSRS-Ports. When the upper layer parameter txConfig is set to 'codebook', the terminal device 1 may be configured with at least one SRS resource. The indicated SRI may be related to transmission of the SRS resource identified by the SRI.

[0229] When two SRS resource sets are configured, one or two SRIs and one or two TPMIs may be provided by DCI fields. For example, the DCI field may be one or both of an SRS resource indication DCI field and a "precoding information and layer number" DCI field. The terminal device 1 may apply the indicated SRI and TPMI to one or more PUSCH repetitions. For example, the terminal device 1 may apply the indicated SRI and TPMI to one or more PUSCH repetitions according to the SRS resource set of the PUSCH repetition. Each TPMI may be used to indicate a precoder based on a codepoint in the SRS resource set indication. The precoder may be applied to the 0th to v-1th layers. The precoder may correspond to the SRS resource selected by the SRI. Multiple SRS resources may be configured for the applicable SRS resource set. For example, when multiple SRS resources are configured for the applicable SRS resource set, the precoder may correspond to the SRS resource selected by the corresponding SRI. In one or two TPMIs, the transmit precoder (precoder) may be selected from a codebook (uplink codebook). When two SRIs are indicated, the terminal device 1 may expect the number of antenna ports for the two indicated SRS resources to be the same. The number of antenna ports may be provided by a higher layer parameter. When two SRS resources are configured and the higher layer parameter usage is set to 'codebook', the terminal device 1 may not expect different numbers of SRS resources to be configured in the two SRS resource sets.

[0230] If the SRS upper layer parameter multipanelScheme is set to "SDMScheme", two SRS resource sets are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, and the upper layer parameter usage of SRS-ResourceSet is set to "codebook", the two SRI(s) and two TPMI(s) may be given by the two SRS resource indicators and two precoding information and number of layers DCI fields of DCI format 0_1 ​​and DCI format 0_2.

[0231] When the SRS resource set indicator codepoint "10" is indicated, the first TPMI may be used to indicate a precoder applied across layers {0...v1-1}, where v1 may be the number of layers indicated by the first TPMI. When multiple SRS resources are configured for the corresponding SRS resource set, or when a single SRS resource is configured for the corresponding SRS resource set, the precoder, the layer, or the TPMI may correspond to the SRS resource selected by the corresponding SRI. The second TPMI may be used to indicate a precoder applied across layers {v1...v2+v1-1}, where v2 may be the number of layers indicated by the second TPMI. When multiple SRS resources are configured for the corresponding SRS resource set, or when a single SRS resource is configured for the corresponding SRS resource set, the precoder, the layer, or the TPMI may correspond to the SRS resource selected by the corresponding SRI. v1≦maxRankSdm and v2≦maxRankSdm or maxRankSdmDCI-0-2 and maxRankSdm or maxRankSdmDCI-0-2 may define the maximum number of layers applied to the first and second SRS resource sets, respectively.

[0232] If the SRS resource set indicator codepoint "00" or "01" is indicated, the second SRI and second TPMI are reserved, and the first TPMI may be used to indicate the precoder applied to layers {0...v-1}.

[0233] The SRS resource set indicator codepoint "11" may be reserved.

[0234] For one or two TPMIs, a transmit precoder may be selected from an uplink codebook with a number of antenna ports equal to nrofSRS-Ports in SRS-Config for the indicated SRI.

[0235] If two SRIs are indicated, the UE may expect the number of SRS antenna ports associated with the two indicated SRIs to be the same. If the UE is configured with the higher layer parameter txConfig set to "codebook", the UE may be configured with at least one SRS resource. Each of the one or two indicated SRI(s) in slot n is associated with the most recent transmission of an SRS resource in the associated SRS resource set identified by the SRI, and the SRS resource may have priority over the PDCCH carrying the SRI. If two SRS resource sets are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with the higher layer parameter usage of SRS-ResourceSet set to "codebook", the UE may not expect to configure different numbers of SRS resources in the two SRS resource sets.

[0236] If the SRS upper layer parameter multipanelScheme is set to "SFNScheme", two SRS resource sets are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, and the upper layer parameter usage of SRS-ResourceSet is set to "codebook", the two SRI(s) and two TPMI(s) may be given by the two SRS resource indicators and two precoding information and number of layers DCI fields of DCI format 0_1 ​​and DCI format 0_2.

[0237] When the SRS resource set indicator codepoint "10" is indicated, the first TPMI may be used to indicate a precoder applied across layers {0...v-1}, and the second TPMI may be used to indicate a precoder applied across layers {0...v-1}, where v≦maxRankSfn or maxRankSfnDCI-0-2, and maxRankSfn or maxRankSfnDCI-0-2 may define the maximum number of layers applied across the first SRS resource set and the second SRS resource set separately.

[0238] The terminal device 1 may expect the number of layers v to be less than or equal to half the number of SRS antenna ports. The terminal device 1 may not expect the number of layers v to be more than half the number of SRS antenna ports. The terminal device 1 may expect the number of SRS antenna ports to be more than twice the number of layers v. The terminal device 1 may not expect the number of SRS antenna ports to be less than twice the number of layers v. The number of layers v may be less than or equal to half the number of SRS antenna ports. The number of layers v may not be more than half the number of SRS antenna ports. The number of SRS antenna ports may be more than twice the number of layers v. The number of SRS antenna ports may be less than twice the number of layers v.

[0239] The terminal device 1 may expect the first precoder and the second precoder to be applied to the same layer {0...v-1}. The terminal device 1 may expect the first precoder and the second precoder indicated by the first SRI field or the first TPMI field to be applied to the same layer {0...v-1}. The terminal device 1 may expect the first precoder and the second precoder to be applied to the same layer {0...v-1} and mapped to different antenna ports. The first precoder and the second precoder may be applied to the same layer {0...v-1}. The first precoder and the second precoder indicated by the first SRI field or the first TPMI field may be applied to the same layer {0...v-1}. The first precoder and the second precoder may be applied to the same layer {0...v-1} and mapped to different antenna ports. For example, when the number of layers v=2, layers l0 and l1 may correspond to antenna ports p0, p1, p2, and p3 as follows, where W1 is the first precoder and W2 is the second precoder: [p0; p1; p2; p3] = [W1, 0; 0, W2] [l0; l1; l0; l1]

[0240] The terminal device 1 may expect the first precoded information and the second precoded information to be mapped to different antenna ports. The terminal device 1 may expect the first precoded information and the second precoded information to correspond to different antenna ports. The first precoded information and the second precoded information may be mapped to different antenna ports. The first precoded information and the second precoded information may correspond to different antenna ports. The first precoded information may be a layer {0...v-1} to which a first precoder is applied. The second precoded information may be a layer {0...v-1} to which a second precoder is applied.

[0241] If the SRS resource set indicator codepoint "00" or "01" is indicated, the second SRI and second TPMI are reserved, and the first TPMI may be used to indicate the precoder to be applied to layers {0...v-1}, where v ≤ maxRank, and maxRank may define the maximum number of layers to be applied to the first SRS resource set or the second SRS resource set.

[0242] The SRS resource set indicator codepoint "11" may be reserved.

[0243] For one or two TPMIs, a transmit precoder may be selected from an uplink codebook with a number of antenna ports equal to nrofSRS-Ports in SRS-Config for the indicated SRI.

[0244] If two TPMIs are indicated, the UE may expect the number of SRS antenna ports associated with the two indicated SRIs to be the same. If the UE is configured with the higher layer parameter txConfig set to "codebook", the UE may be configured with at least one SRS resource. Each of the one or two indicated SRI(s) in slot n is associated with the most recent transmission of an SRS resource in the associated SRS resource set identified by the SRI, and the SRS resource may have priority over the PDCCH carrying the SRI. If two SRS resource sets are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with the higher layer parameter usage of SRS-ResourceSet set to "codebook", the UE may not expect to configure different numbers of SRS resources in the two SRS resource sets.

[0245] In codebook transmission, one SRS resource may be determined from the SRS resource set based on the SRI. The maximum number of SRS resources to be configured for codebook transmission may be two, except when the first higher layer parameter is set to 'fullpowerMode2'. The first higher layer parameter may be ul-FullPowerTransmission. The DCI may indicate transmission of the SRS resource. For example, when aperiodic SRS is configured, the SRS request field in the DCI may indicate transmission of the aperiodic SRS resource. The terminal device 1 may not expect the first higher layer parameter to be set to 'fullpowerMode1' and the second higher layer parameter to be set to 'fullAndPartialAndNonCoherent'.

[0246] The terminal device 1 may transmit the PUSCH using the same one or more antenna ports as one or more SRS ports in the SRS resource indicated by the DCI format or higher layer parameters. For example, the SRS ports may be the same as the antenna ports for PUSCH transmission. The DMRS antenna ports may be determined according to the ordering of the DMRS ports.

[0247] If multiple SRS resources are configured by an SRS resource set, the terminal device 1 may expect that the higher layer parameter nrofSRS-Ports with the same value is configured for these SRS resources. The SRS resource set may be the higher layer parameter SRS-ResourceSet with the higher layer parameter usage set to 'codebook'.

[0248] When 'fullpowerMode2' is set for the upper layer parameters, one or more SRS resources with the same or different SRS port numbers may be configured in one SRS resource set. When 'fullpowerMode2' is set for the upper layer parameters, up to two different spatial relations may be configured for all SRS resources in one SRS resource set. When 'fullpowerMode2' is set for the upper layer parameters, up to two or four SRS resources may be configured in one SRS resource set. Also, up to eight SRS resources may be configured in one SRS resource set. An SRS resource set may be an SRS resource set with the upper layer parameter usage set to 'codebook'.

[0249] In non-codebook transmission, the PUSCH may be scheduled using DCI format 0_0, DCI format 0_1, or DCI format 0_2. The terminal device 1 may determine the precoder and transmission rank of the PUSCH based on the SRI. For example, when multiple SRS resources are configured, the SRI may be provided by one or two SRS resource indications in the DCI. For example, the SRI may be provided by a higher layer parameter. The SRS resource set applied to the PUSCH may be defined by an entry in the higher layer parameter. The higher layer parameter may be srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2.

[0250] The terminal device 1 may use one or more SRS resources for SRS transmission. The maximum number of SRS resources in one SRS resource set may be transmitted to the base station device 3 as a UE capability. SRS resources may be configured for simultaneous transmission in the same OFDM symbol. Multiple SRS resources transmitted simultaneously may occupy the same resource block. One SRS port may be configured for each SRS resource. One or two SRS resource sets may be configured in the upper layer parameter srs-ResourceSetToAddModList, in which the upper layer parameter usage in the upper layer parameter SRS-ResourceSet is set to 'nonCodebook'. If two SRS resource sets are configured, one or two SRIs may be provided by the DCI field. The DCI field may be a DCI field for two SRS resource indications.

[0251] The terminal device 1 may apply the indicated SRI to one or more PUSCH repetitions. For example, the terminal device 1 may apply the indicated SRI to one or more PUSCH repetitions according to the SRS resource set of the PUSCH repetition. The maximum number of SRS resources per SRS resource set configured for non-codebook transmission may be four. The maximum number of SRS resources per SRS resource set configured for non-codebook transmission may be eight. Each of the one or two indicated SRIs may be associated with the most recent transmission of an SRS resource in the SRS resource set identified by the SRI. The SRS transmission may precede the PDCCH carrying the SRI. The terminal device 1 may not expect different numbers of SRS resources to be configured in the two SRS resource sets.

[0252] If the upper layer parameter multipanelScheme is set to "SDMScheme", two SRS resource sets are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, and the upper layer parameter usage of SRS-ResourceSet is set to "nonCodebook", the two SRIs may be given by the DCI fields of the two SRS resource indicators in DCI formats 0_1 and 0_2.

[0253] When the SRS resource set indicator codepoint "10" is indicated, the first SRI may be used to indicate resources associated with layers {0...v1-1}, where v1 may be the number of layers indicated by the first SRI. The second SRI may be used to indicate resources associated with layers {v1...v2+v1-1}, where v2 may be the number of layers indicated by the second SRI. v1≦L max and v2 ≤ L max may be.

[0254] maxMIMO-LayersforSdm is set, L max may be given by max{maxMIMO-Layers, maxMIMO-LayersforSdm}. If maxMIMO-LayersforSfn is set, L max may be given by max{maxMIMO-Layers, maxMIMO-LayersforSfn}. Otherwise, L max may be given by maxMIMO-Layers.

[0255] If the SRS resource set indicator codepoint "00" or "01" is indicated, the second SRI is reserved and the first SRI may be used to indicate resources associated with layers {0...v-1}, where v may be the number of layers indicated by the first SRI. v≦Lmax may be.

[0256] If the upper layer parameter multipanelScheme is set to "SFNScheme", two SRS resource sets are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, and the upper layer parameter usage of SRS-ResourceSet is set to "nonCodebook", the two SRIs may be given by the DCI fields of the two SRS resource indicators in DCI formats 0_1 and 0_2.

[0257] When the SRS resource set indicator codepoint "10" is indicated, the first SRI may be used to indicate resources associated with layers {0...v-1}, and the second SRI may be used to indicate resources associated with layers {0...v-1}, where v≦L. max may be.

[0258] If the SRS resource set indicator codepoint "00" or "01" is indicated, the second SRI is reserved and the first SRI may be used to indicate resources associated with layers {0...v-1}, where v may be the number of layers indicated by the first SRI. v≦L max If two SRIs are indicated, the UE may expect the number of SRS antenna ports associated with the two indicated SRIs to be the same.

[0259] The SRS resource set indicator codepoint "11" may be reserved.

[0260] If the UE is configured with the higher layer parameter txConfig set to "Noncodebook", the UE may be configured with at least one SRS resource. Each of the one or two indicated SRI(s) in slot n relates to the most recent transmission of an SRS resource in the associated SRS resource set identified by the SRI, and the SRS resource may have priority over the PDCCH carrying the SRI. If two SRS resource sets with the higher layer parameter usage of SRS-ResourceSet set to "Noncodebook" are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, the UE may not expect to configure different numbers of SRS resources in the two SRS resource sets.

[0261] When multiple PDCCH candidates (PDCCH candidate(s)) are associated with a search space set configured by a higher layer parameter, one PDCCH candidate is used. The one PDCCH candidate may be an earlier-started PDCCH candidate of the two PDCCH candidates. The higher layer parameter may be searchSpaceLinking.

[0262] For non-codebook transmission, the UE may calculate a precoder. For example, the precoder used for SRS transmission may be calculated based on measurements of NZP CSI-RS resources. One NZP CSI-RS resource may be configured for one SRS resource set. For example, one SRS resource set may be an SRS resource set with higher layer parameters set to 'nonCodebook'.

[0263] When an aperiodic SRS resource set is configured, the NZP-CSI RS may be indicated via the SRS request field. The SRS request field may be one of the DCI fields in any of DCI Format 0_1, DCI Format 0_2, DCI Format 1_1, and DCI Format 1_2. A first upper layer parameter may indicate an association between the aperiodic SRS (aperiodic SRStriggering state) and the SRS resource set. The first upper layer parameter, the triggered SRS resource, srs-ResourceSetId, and csi-RS may be configured in the upper layer parameter SRS-ResourceSet. The upper layer parameter csi-RS may indicate the NZP-CSI-RS-ResourceId. The upper layer parameter SRS-ResourceSet associated with the SRS request may be defined by an entry in a list of upper layer parameters. The list, which is an upper layer parameter, may be the upper layer parameter srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2. The terminal device 1 may not be expected to update the precoding information (SRS precoding information). For example, if the gap from the last OFDM symbol of reception of the aperiodic NZP-CSI-RS resource to the first OFDM symbol of aperiodic SRS transmission is 42 OFDM symbols or less, the terminal device 1 may not be expected to update the precoding information.

[0264] If an aperiodic SRS associated with an aperiodic NZP CSI-RS resource is configured, the presence of the CSI-RS may be indicated by the SRS request field. If the value of the SRS request field is not '00' and the scheduling DCI is not used for cross carrier scheduling or cross bandwidth partscheduling (BWP), the presence of the CSI-RS may be indicated by the SRS request field.

[0265] The terminal device 1 may perform one-to-one mapping. The one-to-one mapping may be mapping from the SRI to the DMRS port and the corresponding PUSCH layer. PUSCH layers from 0 to v-1 may be provided. v may be the number of layers. The number of layers may be set by a higher layer parameter. The terminal device 1 may transmit the PUSCH using the same antenna port as the SRS port. For example, the SRS port in the SRS resource indicated by the SRI may be indexed as pi = 1000 + i. For example, the SRS port in the (i + 1)-th SRS resource may be pi. Also, the SRS port in the (i + 1)-th SRS resource may be indexed as pi. pi may be 1000 + i. That is, pi = 1000 + i.

[0266] In non-codebook transmission, the terminal device 1 may not expect that both spatial relation information (info) for the SRS resource and the upper layer parameter associatedCSI-RS in the upper layer parameter SRS-ResourceSet for the SRS resource set are configured. The spatial relation information may be determined by the upper layer parameter. The spatial relation information may be the upper layer parameter spatialRelationInfo. In non-codebook transmission, when at least one SRS resource is configured in an SRS resource set with the upper layer parameter set to 'nonCodebook', the terminal device 1 may be scheduled by DCI format 0_1 ​​or DCI format 0_2.

[0267] One or more SRS resource sets (Sounding Reference Signal resource sets) may be configured by a first higher layer parameter. The first higher layer parameter may be SRS-ResourceSet or SRS-PosResourceSet. K SRS resources may be configured in each SRS resource set. K may be an integer greater than or equal to 1. The maximum value of K may be indicated by the UE capability. The maximum value of K may be 16. The adaptability of the SRS resource set may be configured by a second higher layer parameter. The second higher layer parameter may be usage. For example, if the second higher layer parameter is set to 'beamManagement', one SRS resource in each of one or more SRS resource sets may be transmitted at a given time instance. Multiple SRS resources in different SRS resource sets may be transmitted simultaneously. For example, multiple SRS resources with the same time domain behavior in different SRS resource sets of the same BWP may be transmitted simultaneously.

[0268] For aperiodic SRS, at least one DCI field may be used to select at least one from the configured SRS resource set.

[0269] The one or more SRS parameters may be configured by a first higher layer parameter. For example, the one or more SRS parameters may be configured semi-statically by a second higher layer parameter. The first higher layer parameter may be SRS-Resource or SRS-PosResource. The second higher layer parameter may determine an SRS resource configuration identity. The second higher layer parameter may be srs-ResourceId or SRS-PosResourceId. The one or more SRS parameters may be some or all of the first to twentieth higher layer parameters. The one or more SRS parameters may include parameters having the same functions as some or all of the first to twentieth higher layer parameters. The one or more SRS parameters may be determined based on a DCI format.

[0270] Number of SRS ports N SRS apmay be determined by a third higher layer parameter. The third higher layer parameter may be nrofSRS-Ports. The SRS ports may be antenna ports. For example, the SRS ports may be antenna ports for SRS. The time domain behavior of the SRS resource configuration may be determined by a fourth higher layer parameter. The fourth higher layer parameter may be resourceType. For example, the time domain behavior may be periodic, semi-persistent, or aperiodic. The periodicity and offset may be determined by a fifth higher layer parameter. The periodicity and offset may be at the slot level. The periodicity and offset may be defined for periodic SRS resources or semi-persistent SRS resources. The fifth higher layer parameter may be periodicityAndOffset-p or periodicityAndOffset-sp. For example, it may not be expected that multiple SRS resources with different periodicities are configured in the same SRS resource set. If 'aperiodic' is set for the fourth higher layer parameter, the slot-level offset may be defined by a sixth higher layer parameter. The sixth higher layer parameter may be slotOffset. If 'aperiodic' is set for the fourth higher layer parameter, a list of available slot offset values ​​may be defined by a seventh higher layer parameter. The seventh higher layer parameter may be AvailableSlotOffset. The list of available slot offset values ​​may be a list of different available slot offset values ​​from 0 to 4. If the reference slot is n+k, the available slot offset may be an offset from the n+k slot to a certain slot. In a certain slot, an aperiodic SRS resource set may be transmitted. Slot n may be the slot of a triggering DCI. The triggering DCI may trigger transmission of an aperiodic SRS. Slot k may be determined by the sixth higher layer parameter.The seventh higher layer parameter may be configured with up to four values. In an aperiodic SRS resource set, a slot-level offset may be defined by the sixth higher layer parameter for each SRS resource.

[0271] Furthermore, the number of OFDM symbols in the SRS resource (the number of consecutive OFDM symbols) N SRS symb The start OFDM symbol (start position in the time domain) of the SRS resource may be defined by an eighth higher layer parameter. The eighth higher layer parameter may be resourceMapping. Also, a repetition factor R fac may be configured by the eighth higher layer parameter. If the number of repetitions is not configured by the eighth higher layer parameter, the number of repetitions may be equal to the number of OFDM symbols in the SRS resource. SRS bandwidth B SRS and C SRS may be defined by the ninth higher layer parameter. If the ninth higher layer parameter is not set, B SRS may be 0. The ninth upper layer parameter may be freqHopping. A partial frequency sounding factor and a starting resource block index for partial frequency sounding may be defined by a tenth upper layer parameter. The tenth upper layer parameter may be FreqScalingFactor and StartRBIndex. The frequency domain position may be defined by an eleventh upper layer parameter. The configurable shift may be defined by a twelfth upper layer parameter. The eleventh upper layer parameter may be freqDomainPosition. The twelfth upper layer parameter may be freqDomainShift.

[0272] The first number of OFDM symbols may be configured by an eighth higher layer parameter. The second number of OFDM symbols may be determined based on the DCI format. If the first number of OFDM symbols is configured and the second number of OFDM symbols is given, the number of OFDM symbols in the SRS resource may correspond to the second number of OFDM symbols.

[0273] The first repetition number may be set by an eighth higher layer parameter. The second repetition number may be determined based on the DCI format. If the first repetition number is set and the second repetition number is determined, the second repetition number may be used and the first repetition number may not be used.

[0274] Furthermore, the comb number (transmission comb number) may be defined by a thirteenth upper layer parameter. The thirteenth upper layer parameter may be transmissionComb. The comb number may be any one of 2, 4, 8, and 16. The cyclic shift (cyclic shift initial value) may be defined by a fourteenth upper layer parameter. The fourteenth upper layer parameter may be any one of cyclicShift-n2, cyclicShift-n4, cyclicShift-n8, and cyclicShift-n16. The fourteenth upper layer parameter may be included in the thirteenth upper layer parameters. The comb offset (transmission comb offset) may be defined by a fifteenth upper layer parameter. The fifteenth upper layer parameter may be any one of combOffset-n2, combOffset-n4, combOffset-n8, and combOffset-n16. The fifteenth upper layer parameter may be included in the thirteenth upper layer parameters. The SRS sequence ID may be defined by a sixteenth upper layer parameter. The sixteenth upper layer parameter may be sequenceId.

[0275] The first cyclic shift (or the cyclic shift initial value) may be configured by the fourteenth higher layer parameter. The second cyclic shift (or the cyclic shift initial value) may be determined based on the DCI format. When the first cyclic shift initial value is configured and the second cyclic shift initial value is determined, the second cyclic shift initial value may be used, and the first cyclic shift initial value may not be used. When the first cyclic shift initial value is configured and the second cyclic shift initial value is determined, the sum of the first cyclic shift initial value and the second cyclic shift initial value may be used.

[0276] The third cyclic shift (or the initial cyclic shift value) may be determined based on one or more values. One of the one or more values ​​may be the number of OFDM symbols in the SRS resource (the number of OFDM symbols constituting the SRS resource). One of the one or more values ​​may be the repetition count (the number of repetitions for SRS). One of the one or more values ​​may be the maximum number of cyclic shifts. That is, the third cyclic shift (or the initial cyclic shift value) may be determined based on some or all of the number of OFDM symbols in the SRS resource, the repetition count, and the maximum number of cyclic shifts.

[0277] When the first cyclic shift initial value is set and the third cyclic shift initial value is determined, the third cyclic shift initial value may be used and the first cyclic shift initial value may not be used. When the first cyclic shift initial value is set and the third cyclic shift initial value is determined, the sum of the first cyclic shift initial value and the third cyclic shift initial value may be used.

[0278] The first SRS sequence ID may be configured by the 16th higher layer parameter. The second SRS sequence ID may be determined based on the DCI format. If the first SRS sequence ID is configured and the second SRS sequence ID is determined, the second SRS sequence ID may be used and the first SRS sequence ID may not be used. If the first SRS sequence ID is configured and the second SRS sequence ID is determined, the sum of the first SRS sequence ID and the second SRS sequence ID may be used.

[0279] The third SRS sequence ID may be determined based on some or all of the number of OFDM symbols in the SRS resource, the number of repetitions, and the maximum number of cyclic shifts. When the first SRS sequence ID is set and the third SRS sequence ID is determined, the third SRS sequence ID may be used, and the first SRS sequence ID may not be used. When the first SRS sequence ID is set and the third SRS sequence ID is determined, the sum of the first SRS sequence ID and the third SRS sequence ID may be used.

[0280] Furthermore, a spatial relation between a reference signal (RS) and an SRS may be defined by a 17th higher layer parameter. For example, the spatial relation between a reference RS and a target SRS may be configured by the 17th higher layer parameter. The 17th higher layer parameter may be spatialRelationInfo or spatialRelationInfoPos. The spatial relation configuration may include an ID of the reference signal (reference RS). The reference signal may be an SS / PBCH block. The reference signal may be a CSI-RS. The reference signal may be a certain SRS. The reference signal may be configured in one serving cell. For example, one serving cell may be indicated by the 18th higher layer parameter. A certain SRS may be configured in one BWP in one serving cell. For example, one serving cell may be the same serving cell as the target SRS. For example, one BWP may be configured by the 19th higher layer parameter. The eighteenth upper layer parameter may be servingCellId. The nineteenth upper layer parameter may be uplinkBWP. One or more SRS parameters may be configured by the first upper layer parameter. For example, the first upper layer parameter may be SRS-Resource or SRS-PosResource.

[0281] If the 20th upper layer parameter is not set, the number of combs may be any of 2, 4, and 8. If the 20th upper layer parameter is set, the number of combs may be any of 2, 4, 8, and 16. If the 20th upper layer parameter is not set, the 14th upper layer parameter may be any of cyclicShift-n2, cyclicShift-n4, and cyclicShift-n8. If the 20th upper layer parameter is set, the 14th upper layer parameter may be any of cyclicShift-n2, cyclicShift-n4, cyclicShift-n8, and cyclicShift-n16.

[0282] The one or more SRS parameters may include some or all of the second to twentieth upper layer parameters. Transmitting an SRS may be transmitting an SRS resource. Transmitting an SRS may be transmitting an SRS resource set. The SRS transmission may be an SRS resource transmission. The SRS transmission may be an SRS resource set transmission.

[0283] The SRS resource may occupy one or more OFDM symbols. For example, the SRS resource may occupy N of the last 6 OFDM symbols of a slot. SRS symb may occupy N OFDM symbols. SRS symb may be 1, 2, or 4. For example, the SRS resource may occupy any of the OFDM symbol positions in one slot. For example, the SRS resource may occupy N OFDM symbol positions in one slot. SRS symb may occupy N adjacent OFDM symbols. SRS ap N antenna ports may be mapped to each OFDM symbol of the resource. SRS ap can be 4 or 8. For example, N of SRS resources SRS apN antenna ports may be mapped to each OFDM symbol of the resource. SRS symb N can be 1, 2, 4, 8, or 12. SRS symb N can be 1, 2, 4, 8, 10, 12, or 14. SRS ap If is 8, then N SRS symb can be even. For example, N SRS ap,1 The antenna ports may be mapped to slots with even slot indices. For example, N SRS ap,2 N antenna ports may be mapped to slots with odd slot indices. SRS ap is N SRS ap,1 + N SRS ap,2 may be.

[0284] When the PUSCH and the SRS are transmitted in the same slot, the SRS may be configured to be transmitted after the PUSCH. For example, when the PUSCH and the SRS are transmitted in one slot in one serving cell, the SRS may be configured to be transmitted after the PUSCH and the corresponding DMRS.

[0285] When PUSCH transmission or PUCCH transmission overlaps with SRS transmission, the SRS may not be transmitted in the overlapping OFDM symbol. For example, in one serving cell, when PUSCH transmission or PUCCH transmission overlaps with SRS transmission in the time domain, the SRS may not be transmitted in the overlapping OFDM symbol. Also, when PUSCH transmission or PUCCH transmission overlaps with SRS transmission, the SRS may not be transmitted. For example, SRS ap If N is 8 and a PUSCH or PUCCH transmission overlaps with an SRS, the SRS may not be transmitted. SRS apIf is 8 and a PUSCH or PUCCH transmission overlaps with an SRS, the SRS may not be transmitted in the overlapping OFDM symbol set. An OFDM symbol set may consist of two OFDM symbols.

[0286] When a spatial relation (spatialRelationInfo) is activated or updated for a first SRS resource, the spatial relation may be applied to a second SRS resource. The first SRS resource may be a semi-persistent SRS resource or an aperiodic SRS resource. The second SRS resource may be a semi-persistent SRS resource or an aperiodic SRS resource with the same SRS resource ID. The second SRS resource may be a semi-persistent SRS resource or an aperiodic SRS resource with the same SRS resource ID for all BWPs in the determined multiple CCs. The first SRS resource may be configured by a higher layer parameter. The spatial relation may be activated or updated by a MAC CE for a set of multiple CCs (component carriers) and / or multiple BWPs. The list of multiple CCs may be determined by a higher layer parameter. The higher layer parameter may be simultaneousSpatial-UpdatedList1 or simultaneousSpatial-UpdatedList2.

[0287] Number of SRS ports N SRS ap may be 8. For example, N for one SRS resource SRS ap may be 8. Either TDM (Time Division Multiplexing) based mapping or non-TDM based mapping may be configured for the SRS or SRS resource. When TDM based mapping is configured, the number of OFDM symbols S ap The TDM base mapping may be configured based on the number of OFDM symbols S ap The TDM base mapping may be configured by Sap The non-TDM base mapping may be set by S ap may be 1. N SRS ap If is not 8, then S ap It may not be expected that N SRS ap If is not 8, then S ap may be ignored.

[0288] S ap may be the number of OFDM symbols to which the SRS port is mapped. For example, S ap If is 1, then N SRS ap SRS ports may be arranged in one OFDM symbol. For example, S ap If is 2, then N SRS ap The SRS ports may be arranged in two OFDM symbols. ap If is 4, N SRS ap The SRS ports may be arranged in four OFDM symbols. ap may be equal to the number of antenna port groups. For example, if the codebook subset is 'fullCoherent', then S ap may be 1. For example, if the codebook subset is '4port-partialCoherent', S ap may be 2. For example, if the codebook subset is '2port-partialCoherent', then S ap may be 4. If the codebook subset is 'nonCoherent', S ap may be 1 or 8.

[0289] An antenna port group may be a group of antenna ports that maintain coherence. The distance between antenna port groups may not depend on wavelength. For example, if the number of antenna port groups is two, a first antenna port group may be composed of antenna ports {1000, 1001, 1004, 1005}. If the number of antenna port groups is two, a second antenna port group may be composed of antenna ports {1002, 1003, 1006, 1007}. For example, if the number of antenna port groups is four, a first antenna port group may be composed of antenna ports {1000, 1004}. If the number of antenna port groups is four, a second antenna port group may be composed of antenna ports {1001, 1005}. If the number of antenna port groups is four, a third antenna port group may be composed of antenna ports {1002, 1006}. If the number of antenna port groups is four, a fourth antenna port group may be composed of antenna ports {1003, 1007}.

[0290] 8 is a diagram illustrating an example of a method for applying a precoding matrix and a transmit spatial filter according to one aspect of this embodiment. In FIG. 8, W represents a precoding matrix, F represents a transmit spatial filter, and precoding for a PUSCH is performed based on the precoding matrix W and the transmit spatial filter F. Furthermore, a first precoding matrix W1 and a first transmit spatial filter F1 correspond to a first uplink physical channel 8100, and a second precoding matrix W2 and a second transmit spatial filter F2 correspond to a second uplink physical channel 8101.

[0291] In Figure 8, vectors d1, d2, ..., d K Precoding is performed based on the precoding matrix W for the vectors x1, x2,…, x M Vectors d1,d2,…,d K may be PUSCH data with the number of layers K. Vectors x1, x2, ..., x Mmay be transmission data for the number M of SRS antenna ports. In this case, d1, d2, ..., d K from x1, x2, …, x M The conversion to is obtained by multiplying by a precoding matrix W. The size of the precoding matrix W may be determined based on the number of layers K and the number of SRS antenna ports M.

[0292] Also, the vectors x1,x2,…,x M Precoding is performed based on the transmit spatial filter F for the vectors y1, y2, ..., y N The vectors y1,y2,…,y N may be transmission data for the number N of physical antenna ports on the transmitting side.

[0293] 9 is a diagram showing an example of an antenna layout of a terminal device 1 according to one aspect of this embodiment. 9001 indicates two antenna elements with different polarizations, and 9002 indicates the range of an antenna group. H denotes the horizontal distance between the antennas, and d V denotes the vertical distance between the antennas. d G-H denotes the horizontal distance between antenna groups, and d G-V denotes the vertical distance between antenna groups.

[0294] PUSCH transmission may be dynamically scheduled by an UL grant in the DCI. A PUSCH dynamically scheduled by an uplink grant in the DCI may be referred to as a DynamicGrant - PUSCH (DG-PUSCH). PUSCH transmission may correspond to configured grant (CG) Type 1 or Type 2. A PUSCH scheduled by a CG may be referred to as a Configured Grant - PUSCH (CG-PUSCH). CG Type 1 PUSCH transmission may be semi-statically configured to operate upon reception of higher layer parameters in configuredGrantConfig including rrc-ConfiguredUplinkGrant, without detecting an UL grant in the DCI. After receiving higher layer parameters in configuredGrantConfig without rrc-ConfiguredUplinkGrant, CG Type 2 PUSCH transmission may be semi-permanently scheduled by an UL grant in a valid activated DCI. If configuredGrantConfigToAddModList is set, multiple configurations of configuredGrant Type 1 and / or configuredGrant Type 2 may be active simultaneously in the active BWP of the serving cell.

[0295] The UE may configure a list of up to 64 TCI-UL-State configurations in the higher layer parameter BWP-UplinkDedicated. Each TCI-UL-State configuration may contain parameters for configuring one reference signal, if applicable, to determine the dynamic and configuration grant-based PUSCH and PUCCH resources within the CC, as well as the UL TX spatial filter for the SRS.

[0296] If a UE is configured with the higher layer parameters PDCCH-Config including ControlResourceSets with two different coresetPoolIndex values ​​for the active BWP of the serving cell, or if a UE is configured with SSB-MTC-AdditionalPCI and a PDCCH-Config including two different coresetPoolIndex values ​​in ControlResourceSet, and if twoTAGs are configured and configured in dl-OrJointTCI-StateList or TCI-UL-State for the serving cell, each TCI-State or TCI-UL-State may be associated with a TAG-ID to determine the timing adjustment of the corresponding UL transmission. The UE may not expect that the TCI-State or TCI-UL-State associated with one coresetPoolIndex corresponds to two TAGs, except when reported by the UE capability.

[0297] For a PUSCH transmission corresponding to Type 1 CG or Type 2 CG activated by DCI format 0_0 or 0_1, the parameters applied to the transmission may be provided by the configuredGrantConfig provided by pusch-Config, except for dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and scaling of UCI-OnPUSCH. For a PUSCH transmission corresponding to Type 2 CG activated by DCI format 0_2, the parameters applied to the transmission may be provided by the configuredGrantConfig provided by pusch-Config, except for dataScramblingIdentityPUSCH, txConfig, codebookSubsetDCI-0-2, maxRankDCI-0-2, scaling of UCI-OnPUSCH, and resourceAllocationType1GranularityDCI-0-2. If the UE is provided with transformPrecoder in configuredGrantConfig, the UE may apply the higher layer parameter tp-pi2BPSK for PUSCH transmissions corresponding to the configured grant, if provided in pusch-Config.

[0298] If the UE is configured with dl-OrJointTCI-StateList or ul-TCI-StateList, it may reference an RS for determining the UL Tx spatial filter and perform PUSCH transmission corresponding to Type 1 CG, Type 2 CG, or DG, if applicable, according to the spatial relationship. The RS may be determined based on the RS whose qcl-Type of the indicated TCI-State is set to "type D" or the RS of the indicated TCI-UL-State. The reference RS of the indicated TCI-State may be a CSI-RS resource in the NZP-CSI-RS-ResourceSet configured by the higher layer parameter "repetition" or a CSI-RS resource in the NZP-CSI-RS-ResourceSet configured by the higher layer parameter "trs-Info." The reference RS of the indicated TCI-UL-State may be a CSI-RS resource of NZP-CSI-RS-ResourceSet configured with the upper layer parameter repetition, a CSI-RS resource of NZP-CSI-RS-ResourceSet configured with the upper layer parameter trs-Info, an SRS resource of an SRS resource set with the upper layer parameter usage set to "beamManagement", or an SS / PBCH block associated with a PCI that is the same as or different from the PCI of the serving cell.

[0299] If a UE is configured with dl-OrJointTCI-StateList or TCI-UL-State and has two indicated TCI-States or TCI-UL-States, a UE with a PUSCH transmission scheduled or activated by DCI format 0_0 may apply the first indicated TCI state to the PUSCH transmission. Also, a UE with a PUSCH transmission corresponding to a grant configured for Type 1 may expect the higher layer parameter applyIndicatedTCIState to be set, indicating the first, second, or both indicated TCI states to apply to the PUSCH transmission. If both TCI states are indicated, the UE applies the first indicated TCI state to the PUSCH transmission opportunity(s) or PUSCH antenna ports associated with the first SRS resource set for CB / NCB transmission and the second indicated TCI state to the PUSCH transmission opportunity(s) or PUSCH antenna ports associated with the second SRS resource set for CB / NCB transmission; otherwise, the UE may apply either the "first" or "second" indicated TCI state to all PUSCH transmission opportunities. Also, if the UE is configured with the higher layer parameter PDCCH-Config including two different values ​​of coresetPoolIndex in different ControlResourceSets, the first and second indicated TCI states correspond to the indicated TCI-States or TCI-UL-States specific to coresetPoolIndex values ​​0 and 1, respectively, and applyIndicatedTCIState does not have to indicate both indicated TCI states to apply to PUSCH transmission.

[0300] For PUSCH retransmissions scheduled on a CRC-scrambled PDCCH with CS-RNTI of NDI=1, the parameters of pusch-Config may be applied to the PUSCH transmission, except for p0-NominalWithoutGrant, p0-PUSCH-Alpha, powerControlLoopToUse, pathlossReferenceIndex, mcs-Table, mcs-TableTransformPrecoder, and transformPrecoder.

[0301] For a UE configured with two uplinks in a serving cell, PUSCH retransmissions for a TB on the serving cell may not be expected to occur on an uplink different from the uplink used for the initial PUSCH transmission for that TB.

[0302] When the UE detects a PDCCH with DCI format 0_0, 0_1, or 0_2 configured, it may transmit the corresponding PUSCH indicated by that DCI, as long as the UE does not generate a TB. If a non-zero "CSI request" with the UL-SCH indicator set to "0" and the associated reportQuantity in CSI-ReportConfig set to "none" is detected in DCI format 0_1 ​​or 0_2, the UE shall ignore all fields other than the "CSI request" of this DCI, and the UE shall not transmit the corresponding PUSCH indicated by this DCI format 0_1 ​​or 0_2. If a UE is scheduled for multiple PUSCHs by a DCI, the HARQ process ID indicated by this DCI may be applied to the first PUSCH that does not overlap with a DL symbol indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, or a symbol of the SS / PBCH block with an index indicated by ssb-PositionsInBurst. The HARQ process ID may be incremented by 1 for each subsequent PUSCH(s) in the scheduled order, modulo nrofHARQ-ProcessesForPUSCH if nrofHARQ-ProcessesForPUSCH is provided, modulo nrofHARQ-ProcessesForPUSCH-r17 if nrofHARQ-ProcessesForPUSCH-r17 is provided, or modulo 16 otherwise.The HARQ process ID may not be incremented for a non-transmitted PUSCH if at least one of the symbols indicated in the indexed row of the used resource allocation table in the slot overlaps with the DL symbol indicated in tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated (if provided) or with a symbol of the SS / PBCH block with index indicated in ssb-PositionsInBurst. For any HARQ process ID(s) in a given scheduled cell, the UE may not be expected to transmit a PUSCH that overlaps in time with other PUSCHs, except when the UE is configured by the higher layer parameter PDCCH-Config and the ControlResourceSet of the active BWP of the serving cell contains two different values ​​of coresetPoolIndex, and when the PDCCHs scheduling two PUSCHs that do not overlap in the time domain are associated with different ControlResourceSets with different values ​​of coresetPoolIndex. For any two HARQ process IDs in a given scheduling cell, if a UE is scheduled to start transmitting the first PUSCH starting at symbol j by a PDCCH ending at symbol i in the scheduling cell, the UE may be expected not to start transmitting a PUSCH starting earlier than the end of the first PUSCH by a PDCCH ending after symbol i in the scheduling cell. If the PDCCH reception contains two PDCCH candidates from two search space sets, the PDCCH candidate ending later in time may be used to determine the PDCCH ending at symbol i. The UE may not transmit another PUSCH in a given HARQ process using DCI received by DCI format 0_0 CRC-scrambled by TC-RNTI or by an UL grant in an RA response before the scheduled end of the last PUSCH transmission of that HARQ process.The UE is not expected to be scheduled to transmit another PUSCH for a given HARQ process with DCI format 0_0, 0_1, or 0_2 scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI, and may be scheduled by DCI received before the end of the expected transmission of the last PUSCH for that HARQ process if the latter is scheduled by DCI whose CRC is scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0303] If a UE is configured by the higher layer parameter PDCCH-Config containing two different values ​​of coresetPoolIndex in the ControlResourceSet of the active BWP of the serving cell, and the PDCCHs scheduling two PUSCHs that do not overlap in the time domain are associated with different ControlResourceSets with different values ​​of coresetPoolIndex for any two HARQ process IDs in a given scheduled cell, and the UE is scheduled to start transmitting the first PUSCH starting at symbol j via a PDCCH associated with a value of coresetPoolIndex that ends at symbol i, then the UE may also be scheduled to transmit a PUSCH that starts earlier than the end of the first PUSCH via a PDCCH associated with a different value of coresetPoolIndex that ends after symbol i.

[0304] If two SRS resource sets are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with the higher layer parameter "usage" of SRS-ResourceSet set to "codebook" or "nonCodebook", the higher layer parameter "enableSTx2PofmDCI" is set, and the PDCCH-Config contains two different values ​​for coresetPoolIndex of the ControlResourceSet of the active BWP of the serving cell, two PUSCHs that fully / partially overlap in the time domain and fully / partially / non-overlapping in the frequency domain may be dynamically scheduled by the UL grant of DCI and / or may be scheduled by the configured grant type 1 or type 2. In the case of dynamic scheduling by the UL grant of DCI, the DCI field SRS Resource Set Indicator is not present in each PDCCH, and the two scheduled PUSCHs may be associated with different ControlResourceSets with different values ​​for coresetPoolIndex.

[0305] The UE is configured with the higher layer parameter PDCCH-Config, which contains two different coresetPoolIndex values ​​in the ControlResourceSet, and enableSTx2PofmDCI, and two PUSCHs have different coresetPoolIndex values. If the UE is not provisioned with prioLowDG-HighCG or prioHighDG-LowCG, or if the UE is provisioned with prioLowDG-HighCG or prioHighDG-LowCG and two PUSCHs have the same priority index, and if the UE is not provisioned with enableSTx2PofmDCI or is provisioned with enableSTx2PofmDCI and two PUSCHs are associated with the same coresetPoolIndex value, then the UE may not expect to be scheduled by a PDCCH ending at symbol i to transmit a PUSCH on a given serving cell that overlaps in time with a transmission opportunity where the UE is allowed to transmit a PUSCH with a configured grant starting at symbol j on the same serving cell, unless the end of symbol i is at least N symbols before the start of symbol j.

[0306] The value N2 in symbols may be determined according to the processing capability of the UE, and N2 and the symbol duration may be based on the minimum of the subcarrier spacing corresponding to the PUSCH with the configured grant and the subcarrier spacing of the PDCCH scheduling the PUSCH.

[0307] The terminal device 1 may edit the terminal capability information. The terminal device 1 may transmit (transfer) the terminal capability information. When the terminal device 1 receives a UECapabilityEnquiry from the network, the terminal device 1 may edit and transfer the terminal capability information (UE capability information). Furthermore, notification of the terminal capability information may be performed according to the procedure shown below.

[0308] If the network requires (additional) UE radio access capability information, the procedure may be initiated for the terminal in RRC_CONNECTED. UE capabilities may only be obtained after AS security activation. UE capabilities obtained before AS security activation may not be forwarded to the CN.

[0309] When the ue-CapabilityRAT-RequestList includes a UE-CapabilityRAT-Request with rat-Type set to nr, the terminal device 1 may set the contents of the UECapabilityInformation message as follows: The ue-CapabilityRAT-ContainerList may include a UE-CapabilityRAT-Container whose type is UE-NR-Capability and whose rat-Type is set to nr. SupportedBandCombinationList, featureSets, and featureSetCombinations may be included.

[0310] If the ue-CapabilityRAT-RequestList includes a UE-CapabilityRAT-Request with rat-Type set to eutra-nr and the UE supports (NG)EN-DC or NE-DC, the terminal device 1 may set the contents of the UECapabilityInformation message as follows: The ue-CapabilityRAT-ContainerList may include a UE-CapabilityRAT-Container with a type of UE-MRDC-Capability and rat-Type set to eutra-nr. A supportedBandCombinationList and a featureSetCombinations may be included.

[0311] If the ue-CapabilityRAT-RequestList includes a UE-CapabilityRAT-Request with rat-Type set to eutra and the UE supports E-UTRA, the terminal device 1 may set the content of the UECapabilityInformation message as follows: The ue-CapabilityRAT-ContainerList may include, when received, a ue-CapabilityRAT-Container of type UE-EUTRA-Capability and with rat-Type set to eutra.

[0312] If the ue-CapabilityRAT-RequestList includes a UE-CapabilityRAT-Request with rat-Type set to utra-fdd and the UE supports UTRA-FDD, the terminal device 1 may set the contents of the UECapabilityInformation message as follows: The ue-CapabilityRAT-Container may include UE radio access capability for UTRA-FDD with rat-Type set to utra-fdd.

[0313] If RRC message segmentation is enabled based on the received field rrc-SegAllowed and the encoded RRC message is larger than the maximum supported size of the PDCP SDU, the terminal device 1 may set the content of the UECapabilityInformation message as follows: A UL message segment transfer procedure may be initiated.

[0314] In cases other than those described above, the terminal device 1 may set the content of the UECapabilityInformation message as follows: The terminal device 1 may send the UECapabilityInformation message to a lower layer, and the procedure may be terminated at that point.

[0315] The terminal device 1 may invoke the procedure when the NR or E-UTRA network requests the UE's capabilities for nr, eutra-nr, or eutra. This procedure may be invoked once for each requested rat-type. The terminal device 1 may ensure that the capability set IDs are consistent across capability sets, capability set combinations, and band combinations in all three UE capability containers for which the network queries the same fields with the same values. The UE capability containers may be fields in the UE-CapabilityRequestFilterNR, UE-CapabilityRequestFilterCommon, and UECapabilityEnquiry messages.

[0316] Capability queries that do not use frequencyBandListFilter do not have to be supported.

[0317] In EN-DC, the gNB may require capabilities for RAT types nr and eutra-nr. It may also use featureSets in UE-NR-Capability together with featureSetCombinations in UE-MRDC-Capability to determine NR UE capabilities for supported MRDC band combinations. Similarly, the eNB may require capabilities for RAT types eutra and eutra-nr. It may also use featureSetsEUTRA in UE-EUTRA-Capability together with featuresSetCombinations in UE-MRDC-Capability to determine E-UTRA UE capabilities for supported MRDC band combinations. The IDs used in featureSets may match the IDs referenced in featureSetCombinations in all three containers. The consistency requirement may mean that there are no undefined feature sets and feature set combinations.

[0318] If the UE is unable to include all feature sets and feature set combinations due to message size or list size constraints, it may be up to the UE implementation to decide which feature sets and feature set combinations to prioritize.

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

[0320] The TRP information may be used to select one TRP. Also, one control resource set (CORESET) may be associated with an index of a CORESET resource pool. The terminal device 1 may transmit a PUSCH based on the index of the CORESET resource pool.

[0321] The TRP information may be a CORESET pool index. The TRP information may be associated with an index of a CORESET resource pool. For example, a first CORESET pool index may be associated with a first TRP, and a second CORESET pool index may be associated with a second TRP. The TRP information may be associated with a pool (or pool index) of TCI states. A first one or more TCI states may be associated with a pool index of the first TCI state. A second one or more TCI states may be associated with a pool index of the second TCI state.

[0322] Multiple panels may be used. The terminal device 1 may be configured with multiple panels (multi-panel). The terminal device 1 may be scheduled for two panels in one terminal device. In multi-panel, one of single-DCI and multi-DCI operation modes may be used. In multi-panel or SDM scheme, uplink control may be completed in the MAC layer and the physical layer. In multi-panel or SDM scheme, downlink control may be completed in the MAC layer and the physical layer. In single-DCI mode, the terminal device 1 may be scheduled by the same DCI for two panels. In multi-DCI mode, the terminal device 1 may be scheduled by independent DCI for each panel. In multi-DCI mode, each panel in multi-panel may be identified by panel information. That is, one panel of multi-panel may be identified by one piece of panel information.

[0323] Multiple transmit spatial filters may be used. Multiple transmit spatial filters may be configured in the terminal device 1. The terminal device 1 may transmit the PUSCH according to an SDM scheme. In the SDM scheme, one of single-DCI and multi-DCI operation modes may be used. In the SDM scheme, uplink control may be completed in the MAC layer and the physical layer. In the SDM scheme, downlink control may be completed in the MAC layer and the physical layer. In the single-DCI mode, the terminal device 1 may be scheduled by the same DCI for two transmit spatial filters. In the multi-DCI mode, the terminal device 1 may be scheduled by an independent DCI for each transmit spatial filter. In the multi-DCI mode, each transmit spatial filter in the SDM scheme may be identified by transmit spatial filter information. That is, one transmit spatial filter in the SDM scheme may be identified by one transmit spatial filter information.

[0324] The panel information or the transmission spatial filter information may be used to select one panel or one transmission spatial filter. Also, a CORESET resource pool index may be associated with one control resource set (CORESET). Also, a TCI state pool index may be associated with one TCI state set. Also, a spatial relationship information pool index may be associated with one spatial relationship information set. The terminal device 1 may transmit a PUSCH based on some or all of the CORESET resource pool index, the TCI state pool index, and the spatial relationship information pool index.

[0325] The panel information or transmit spatial filter information may be a CORESET pool index. The panel information or transmit spatial filter information may be associated with an index of a CORESET resource pool. For example, a first CORESET pool index may be associated with a first panel or transmit spatial filter, and a second CORESET pool index may be associated with a second panel or transmit spatial filter. The panel information or transmit spatial filter information may be a TCI state pool index. The panel information or transmit spatial filter information may be associated with an index of a TCI state pool. For example, a first TCI state pool index may be associated with a first panel or transmit spatial filter, and a second TCI state pool index may be associated with a second panel or transmit spatial filter. The panel information or transmit spatial filter information may be a spatial relationship information pool index. The panel information or transmit spatial filter information may be associated with an index of a spatial relationship information pool. For example, a first spatial relationship information pool index may be associated with a first panel or transmit spatial filter, and a second spatial relationship information pool index may be associated with a second panel or transmit spatial filter.

[0326] Simultaneous Transmission with Multi Panel (STxMP) may be applied to the terminal device 1. STxMP may be applied for one or both of the first uplink physical channel 8100 and the second uplink physical channel 8101. When STxMP is applied, the terminal device 1 may simultaneously transmit one or both of the first uplink physical channel 8100 and the second uplink physical channel 8101. When STxMP is applied, the terminal device 1 may transmit the first uplink physical channel 8100 and the second uplink physical channel 8101 in the same time resource and some or all of the same frequency resource. Here, the time resource may be one or more OFDM symbols or slots. The frequency resource may be one or more subcarriers or physical resource blocks. When STxMP is applied, a first Code Division Multiplexing (CDM) group of a first DMRS port indicated for a first uplink physical channel 8100 may be different from a second CDM group of a second DMRS port indicated for a second uplink physical channel 8101. The first CDM group and the second CDM group need not be the same. One or both of the first DMRS port and the second DMRS port may be indicated by an antenna port field in one DCI format. The first CDM group and the second CDM group may be indicated by an antenna port field. When STxMP is applied, the first uplink physical channel 8100 and the second uplink physical channel 8101 may correspond to one precoding matrix. The one precoding matrix may be determined by a TPMI field in the DCI format. When STxMP is applied, the first uplink physical channel 8100 may correspond to a first TCI state, and the second uplink physical channel 8101 may correspond to a second TCI state.The first TCI state and the second TCI state may be indicated by a TCI (Transmission Configuration Indication) field in DCI format 1_1 / 1_2. When STxMP is applied, the first uplink physical channel 8100 may correspond to a first uplink transmit spatial filter (UL Tx Spatial filter), and the second uplink physical channel 8101 may correspond to a second uplink transmit spatial filter. The first uplink transmit spatial filter may be determined by an SRS resource indication (SRI) field in the DCI format. The second uplink transmit spatial filter may be determined by a Second SRI field in the DCI format.

[0327] When STxMP is applied, the number of first transmission layers (rank number) corresponding to the first uplink physical channel 8100 may be the same as or different from the number of second transmission layers (rank number) corresponding to the second uplink physical channel 8101. The difference between the number of first transmission layers and the number of second transmission layers is not required to be two or more. When STxMP is applied, the first uplink physical channel 8100 and the second uplink physical channel 8101 may fully overlap. When STxMP is applied, the first uplink physical channel 8100 and the second uplink physical channel 8101 may partially overlap. When STxMP is applied, the first uplink physical channel 8100 and the second uplink physical channel 8101 are not required to partially overlap. When STxMP is applied, it may not be expected that the first transport block corresponding to the first uplink physical channel 8100 is different from the second transport block corresponding to the second uplink physical channel 8101. When STxMP is applied, it may not be expected that each of the first uplink physical channel 8100 and the second uplink physical channel 8101 carries two transport blocks (codewords). When STxMP is applied, it may not be expected that the upper layer parameter sfnSchemePusch or the upper layer parameter sfnSchemePucch is configured for one or both of the first uplink physical channel 8100 and the second uplink physical channel 8101. When the upper layer parameter sfnSchemePusch is configured for a PUSCH, a DMRS port of a PUSCH may carry reference signals and QCLs for multiple (e.g., two) TCI states. When the higher layer parameter sfnSchemePucch is configured for a certain PUCCH, the DMRS port of a certain PUCCH may be a reference signal and a QCL for multiple (eg, two) TCI states.

[0328] The application of STxMP may be configured for one or both of the first uplink physical channel and the second uplink physical channel. The application of STxMP may be configured by higher layer parameters. The application of STxMP may be configured or determined based on terminal capabilities. For example, the application of STxMP for the PUSCH may be configured by dedicated higher layer parameters for the PUSCH. For example, the application of STxMP for the PUCCH may be configured by dedicated higher layer parameters for the PUCCH. The application of STxMP may be indicated by a DCI format. The application of STxMP may be indicated by configuring one or more SRS resource sets. For example, if the SRS resource set indicator indicates 00 or 01, one SRS resource set may be configured, and if the SRS resource set indicator indicates 10 or 11, multiple SRS resource sets may be configured. For example, if the SRS resource set indicator indicates 00 or 01, single-panel transmission may be assumed. For example, if the SRS resource set indicator indicates 10 or 11, multi-panel transmission may be assumed. If single-panel transmission is instructed after multi-panel transmission is instructed, fallback to single-panel transmission may be performed. Application of STxMP may mean that the PUSCH is transmitted in at least one OFDM symbol using parameters associated with each of multiple SRS resource sets. Application of STxMP may mean that the PUSCH is transmitted in at least one OFDM symbol using parameters associated with some or all of multiple SRS resource sets. Application of STxMP may mean that the PUSCH is transmitted in at least one subcarrier using parameters associated with some or all of multiple SRS resource sets.The application of STxMP may be indicated by two SRS resource sets being set to srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 and the upper layer parameter "usage" of the SRS-ResourceSet being set to "codebook" or "nonCodebook". The application of STxMP may be indicated by two SRS resource sets being set to srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 and the upper layer parameter "usage" of the SRS-ResourceSet being set to "codebook" or "nonCodebook".

[0329] By setting any of sdmSchemePusch, sdm, sfnSchemePusch, sfn, multiPanel, multiTRP, multiPanelAndMultiTRP, puschRepetition, multiPanelAndPuschRepetition, multiTRPAndPuschRepetition, multipanelScheme, multipanelSfnScheme, SDMScheme, and SFNScheme in the RRC parameters or DCI format, it may be configured that STxMP is applied to one or both of the first uplink physical channel and the second uplink physical channel. By setting some or all of sdmSchemePusch, sdm, sfnSchemePusch, sfn, multiPanel, multiTRP, multiPanelAndMultiTRP, puschRepetition, multiPanelAndPuschRepetition, multiTRPAndPuschRepetition, multipanelScheme, multipanelSfnScheme, SDMScheme, and SFNScheme in the RRC parameters or DCI format, it may be configured that STxMP is applied to one or both of the first uplink physical channel and the second uplink physical channel.

[0330] sTRP may be a single-TRP transmission / communication. mTRP may be a multi-TRP transmission / communication.

[0331] STxMP may be replaced with STx2P. The application of STx2P may be configured by enableSTx2P. STxMP may be multi-panel simultaneous transmission. When STxMP is applied, a first uplink physical channel may be associated with a first SRS resource set and a second uplink physical channel may be associated with a second SRS resource set. The application of STxMP may mean that STxMP is enabled, that STxMP is configured, or that STxMP is executed. STxMP may be applied based on multiple DCIs. STxMP based on multiple DCIs may be referred to as Multi-DCI based STxMP. The application of Multi-DCI based STxMP may be configured by enableSTx2PofmDCI.

[0332] The terminal device 1 receives information including a first parameter, receives downlink control information (DCI) carried on a downlink control channel (PDCCH), and transmits a PUSCH scheduled by the DCI, and if the first parameter is set and an SRS resource set indicator included in the DCI indicates 10, the DCI indicates a first precoder and a second precoder to be used for the PUSCH, and the first precoder and the second precoder are applied to layer 0 to layer v-1, and the number of layers v may be less than or equal to 1 / 2 of the number of antenna ports from which the PUSCH is transmitted.

[0333] The terminal device 1 may receive information including a first parameter. The terminal device 1 may receive downlink control information (DCI) carried on a downlink control channel (PDCCH). The terminal device 1 may transmit a PUSCH scheduled by the DCI. When the first parameter is configured and an SRS resource set indicator included in the DCI indicates 10, the DCI may indicate a first precoder and a second precoder to be used for the PUSCH. When the first parameter is configured and an SRS resource set indicator included in the DCI indicates 10, the first precoder and the second precoder may be applied to layer 0 to layer v-1. When the first parameter is configured and an SRS resource set indicator included in the DCI indicates 10, the number of layers v may be equal to or less than half the number of antenna ports from which the PUSCH is transmitted.

[0334] The first parameter may be a multipanelScheme. The first parameter may be an SFNScheme. The first parameter may represent two different SRS resource sets. The first parameter may be information indicating an STxMP SFN scheme. The first precoder may be determined based at least on a first SRI field or a first TPMI field. The second precoder may be determined based at least on a second SRI field or a second TPMI field. The number of layers of the first precoder and the second precoder may be the same. The first precoder and the second precoder may be applied to the same layer. The number of layers v may be determined based on a part or all of a first TPMI field and a first SRI field. The layers may be layers {0...v-1}. Layers {0...v-1} obtained after the first precoder and the second precoder are applied may correspond to different antenna ports. Layers {0...v-1} after the first precoder and the second precoder are applied may be mapped to different antenna ports. Layers {0...v-1} after the first precoder is applied may be first information. Layers {0...v-1} after the second precoder is applied may be second information. The first information and the second information may be information in which the same or different precoders are applied to layers {0...v-1}. If the UE capability indicates a first capability, the first information and the second information may correspond to different antenna ports. If the UE capability indicates a second capability, the first information and the second information may correspond to the same antenna port. Corresponding to certain information on a certain antenna port may mean that the information is transmitted from that antenna port. Corresponding to certain information on a certain antenna port may mean that the information is mapped to that antenna port. The first capability may be a capability to transmit information of the same layer on different antenna ports.The first capability may be a capability to combine one or more precoders. The first capability may be a capability to remove inter-panel interference. The second capability may be the same as or different from the first capability. The second capability may be a capability that does not indicate the first capability. For example, when the number of layers v is 2, the first information may correspond to antenna ports {1000, 1001}, and the second information may correspond to antenna ports {1002, 1003}. For example, when the number of layers v is 2, the first information may correspond to antenna ports {1000, 1002}, and the second information may correspond to antenna ports {1001, 1003}. For example, when the number of layers v is 1, the first information may correspond to antenna port {1000}, and the second information may correspond to antenna port {1001}. For example, when the first capability is indicated and the number of layers v=2, the first information may correspond to antenna ports {1000, 1001}, and the second information may correspond to antenna ports {1002, 1003}. For example, when the first capability is indicated and the number of layers v=2, the first information may correspond to antenna ports {1000, 1002}, and the second information may correspond to antenna ports {1001, 1003}. For example, when the first capability is indicated and the number of layers v=1, the first information may correspond to antenna port {1000}, and the second information may correspond to antenna port {1001}.

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

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

[0337] Note that a part of the terminal device 1 and the base station device 3 in the above-described embodiment may be realized by a computer. In this case, a program for realizing this control function may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be read into a computer system and executed to realize the function.

[0338] The term "computer system" used here refers to a computer system built into the terminal device 1 or base station device 3, and includes hardware such as an OS and peripheral devices. Also, the term "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, as well as storage devices such as hard disks built into the computer system.

[0339] Furthermore, the term "computer-readable recording medium" may include a medium that dynamically stores a program for a short period of time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line, or a medium that stores a program for a fixed period of time, such as volatile memory within a computer system that serves as a server or client in such a case. The program may also be one that realizes part of the above-mentioned functions, or one that can realize the above-mentioned functions in combination with a program already stored in the computer system.

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

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

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

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

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

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

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

Claims

1. A terminal device comprising: an upper layer processing unit that receives information including a first parameter and a second parameter; a receiving unit that receives downlink control information (DCI) carried on a downlink control channel (PDCCH); and a transmitting unit that transmits a PUSCH scheduled by the DCI, wherein if an SRS resource set indicator included in the DCI indicates 00 or 01, a maximum number of layers is determined by the first parameter; if an SRS resource set indicator included in the DCI indicates 10, a maximum number of layers is determined by the second parameter; if an SRS resource set indicator included in the DCI indicates 00 or 01, the DCI indicates a first precoder to be used for the PUSCH, and the transmitting unit transmits the PUSCH based on the first precoder; and if an SRS resource set indicator included in the DCI indicates 10, the DCI indicates a second precoder and a third precoder to be used for the PUSCH, and the transmitting unit transmits the PUSCH based on the second precoder and the third precoder.

2. A base station apparatus comprising: an upper layer processing unit that transmits information including a first parameter and a second parameter; a transmitting unit that transmits downlink control information (DCI) carried on a downlink control channel (PDCCH); and a receiving unit that receives a PUSCH scheduled by the DCI, wherein, if an SRS resource set indicator included in the DCI indicates 00 or 01, the first parameter determines a maximum number of layers; if an SRS resource set indicator included in the DCI indicates 10, the second parameter determines the maximum number of layers; if the SRS resource set indicator included in the DCI indicates 00 or 01, the DCI indicates a first precoder to be used for the PUSCH; and if the SRS resource set indicator included in the DCI indicates 10, the DCI indicates a second precoder and a third precoder to be used for the PUSCH.

3. A communication method for use in a terminal device, comprising: a step of receiving information including a first parameter and a second parameter; a step of receiving downlink control information (DCI) carried by a downlink control channel (PDCCH); and a step of transmitting a PUSCH scheduled by the DCI; wherein, when an SRS resource set indicator included in the DCI indicates 00 or 01, a maximum number of layers is determined by the first parameter; when an SRS resource set indicator included in the DCI indicates 10, a maximum number of layers is determined by the second parameter; when an SRS resource set indicator included in the DCI indicates 00 or 01, the DCI indicates a first precoder to be used for the PUSCH, and the transmission unit transmits the PUSCH based on the first precoder; when an SRS resource set indicator included in the DCI indicates 10, the DCI indicates a second precoder and a third precoder to be used for the PUSCH, and the transmission unit transmits the PUSCH based on the second precoder and the third precoder. Communication methods.

Images