Terminal device

Abstract

This terminal device comprises: a transmission unit that transmits an SRS and a PUSCH; and a reception unit that receives a PDCCH with a DCI therein. The DCI indicates an SRS resource for the SRS. The DCI instructs transmission of the PUSCH. If a first codebook type is set for the PUSCH and TDM-based mapping is set for the SRS, a dropping rule 1 is applied to the SRS. If a second codebook type is set for the PUSCH and TDM-based mapping is set for the SRS, the dropping rule 1 is applied to the SRS. If non-TDM based mapping is set for the SRS, the dropping rule 1 is applied to the SRS.

Description

terminal device

[0001] The present invention relates to a terminal device. This application claims priority to Japanese Patent Application No. 2023-164667, 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: eMBB (enhanced Mobile BroadBand), mMTC (massive Machine Type Communication), and URLLC (Ultra Reliable and Low Latency Communication) within a single technology framework.

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

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

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

[0007] (1) A first aspect of the present invention is a terminal device comprising: a transmitter that transmits an SRS and a PUSCH; and a receiver that receives a PDCCH on which a DCI is arranged, wherein the DCI indicates an SRS resource for the SRS; the DCI indicates transmission of the PUSCH; when a first codebook type is configured for the PUSCH and TDM-based mapping is configured for the SRS, dropping rule 1 is applied to the SRS; when a second codebook type is configured for the PUSCH and TDM-based mapping is configured for the SRS, dropping rule 1 is applied to the SRS; and when non-TDM-based mapping is configured for the SRS, dropping rule 1 is applied to the SRS.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0026] The transmission of the signal in the downlink and / or the transmission of the signal in the uplink may be of length Tf 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.

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

[0028] A slot may consist of multiple OFDM symbols, for example, 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.

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

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

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

[0032] 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

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

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

[0035] 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

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

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

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

[0039] 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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0091] 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)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0114] 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)

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

[0116] 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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0164] 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)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0234] 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 an SRS resource indicator DCI field of 1 or 2. For example, the TPMI may be provided by a precoding information DCI field of 1 or 2. For example, the transmission rank may be provided by a layer number (number of transmission layers) DCI field. For example, the TPMI and transmission rank may be provided by one or two "precoding information and number of layers" DCI fields. 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.

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

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

[0237] When one SRS resource set is configured, the SRI and TPMI may be provided by DCI fields. The DCI fields may include one SRS resource indication and one "precoding information and layer number" DCI field. The TPMI may be used to indicate a precoder. The precoder may be applied across v layers {0,...,v-1}. When multiple SRS resources are configured, one SRS resource may be selected by the SRI. The precoder may correspond to one SRS resource. The transmit precoder (precoder) may be selected from a codebook (uplink codebook). For example, the codebook may include 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. For example, the indicated SRI may be related to the most recent transmission of the SRS resource identified by the SRI, and the SRS resource may be prior to the PDCCH carrying the SRI.

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

[0239] In codebook transmission, the terminal device 1 may determine a codebook subset. For example, the codebook subset may be determined based at least on the TPMI. The codebook subset may be determined in response to receiving a certain higher layer parameter. The certain higher layer parameter may be codebookSubset or codebookSubsetDCI-0-2. The certain higher layer parameter may be set to 'fullyAndPartialAndNonCoherent', 'partialAndNonCoherent', or 'nonCoherent'. If the higher layer parameter ul-FullPowerTransmission is set to 'fullpowerMode2', if the certain higher layer parameter is set to 'AndNonCoherent', and if the SRS resource set for the codebook includes at least one SRS resource with four ports and at least one SRS resource with two ports, the codebook subset associated with the two-port SRS resource (the SRS resource with two ports) may be 'nonCoherent'. The maximum transmission rank (or maximum rank) may be configured for the PUSCH by the upper layer parameter maxRank or the upper layer parameter maxRankDCI-0-2.

[0240] The terminal device 1 may report a UE capability. If the terminal device 1 reports a UE capability of 'partialAndNonCoherent' transmission, the terminal device 1 may not expect a codebook subset having 'fullyAndPartialAndNonCoherent' to be configured.

[0241] If the terminal device 1 reports a UE capability of 'nonCoherent' transmission, the terminal device 1 may not expect a codebook subset with 'fullyAndPartialAndNonCoherent' or 'partialAndNonCoherent' to be configured.

[0242] If the higher layer parameter for the codebook, nrofSRS-Ports, indicates that the maximum number of SRS antenna ports to be configured is 2, the terminal device 1 may not expect that the higher layer parameter to be set to 'partialAndNonCoherent' is configured. The higher layer parameter may be codebookSubset or codebookSubsetForDCI-Format0-2. The number of antenna ports may be determined by the higher layer parameter nrofSRS-Ports.

[0243] 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 upper layer parameter is set to 'fullpowerMode2'. The first upper 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 (trigger) transmission of the aperiodic SRS resource. The terminal device 1 may not expect the first upper layer parameter to be set to 'fullpowerMode1' and the second upper layer parameter to be set to 'fullAndPartialAndNonCoherent'.

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

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

[0246] 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 the SRS resource set for the codebook. When 'fullpowerMode2' is set for the upper layer parameters and multiple SRS resource sets are configured in the SRS resource set, up to two different spatial relations may be configured for all SRS resources in the SRS resource set for the codebook. When 'fullpowerMode2' is set for the upper layer parameters, up to two or four SRS resources may be configured in the SRS resource set for the codebook. Also, up to eight SRS resources may be configured in one SRS resource set. The SRS resource set for the codebook may be an SRS resource set with the upper layer parameter usage set to 'codebook'.

[0247] In non-codebook transmission, the PUSCH may be scheduled using DCI format 0_0, DCI format 0_1, or DCI format 0_2. In non-codebook transmission, the PUSCH may be configured semi-statically. 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 higher layer parameters. The SRS resource set applied to the PUSCH may be defined by an entry in the higher layer parameters. The higher layer parameters may be srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2.

[0248] 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 UE capability. SRS resources may be configured for simultaneous transmission in the same OFDM symbol. In one SRS resource set, the maximum number of SRS resources configured for simultaneous transmission in the same OFDM symbol, the maximum number of SRS resources, and the UE capability may be used. 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 with the upper layer parameter usage set to 'nonCodebook' in the upper layer parameter SRS-ResourceSet. When 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.

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

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

[0251] 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 the NZP CSI-RS resources. One NZP CSI-RS resource may be configured for the SRS resource set for non-codebook. For example, the SRS resource set for non-codebook may be an SRS resource set with higher layer parameters set to 'nonCodebook'.

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

[0253] If an aperiodic SRS associated with an aperiodic NZP CSI-RS resource is configured, the presence of the associated 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 part scheduling, the presence of the CSI-RS may be indicated by the SRS request field.

[0254] If a periodic or semi-persistent SRS resource set is configured, the NZP-CSI-RS-ResourceId for measurement may be indicated via the higher layer parameter associatedCSI-RS.

[0255] The terminal device 1 may perform one-to-one mapping. The one-to-one mapping may be mapping from the SRI to a DMRS port and mapping from the SRI to a corresponding PUSCH layer {0,...,v-1}. 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.

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

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

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

[0259] 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 24th higher layer parameters. The one or more SRS parameters may include parameters having the same functions as some or all of the first to 24th higher layer parameters. The one or more SRS parameters may be determined based on a DCI format.

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

[0261] 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 set by the eighth higher layer parameter. If the repetition number is not set by the eighth higher layer parameter, the repetition number may be the same as the number of OFDM symbols in the SRS resource, or the repetition number may be 1. SRS bandwidth (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.

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

[0263] The cyclic shift (or the cyclic shift offset value) may be determined based on one or more values. One of the one or more values ​​may be an OFDM symbol index. 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 a 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 cyclic shift (or the cyclic shift offset value) may be determined based on some or all of the OFDM symbol index in the SRS resource, the number of OFDM symbols, the repetition count, and the maximum number of cyclic shifts.

[0264] The first SRS sequence ID may be set by the sixteenth higher layer parameter A. The second SRS sequence ID may be determined based on the sixteenth higher layer parameter B. The third SRS sequence ID may be determined based on the sixteenth higher layer parameter C. The first SRS sequence ID may be used for group hopping or sequence hopping. The second SRS sequence ID may be used for comb offset hopping. The third SRS sequence ID may be used for cyclic shift hopping.

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

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

[0267] The 21st upper layer parameter may configure a TDM-based mapping. If the 21st upper layer parameter is configured, a TDM-based mapping may be configured for the SRS. If the 21st upper layer parameter is not configured, a TDM-based mapping may not be configured, or a non-TDM-based mapping may be configured. The 21st upper layer parameter may be tdmScheme. If the number of SRS ports is 8, the 21st upper layer parameter may be configured. A TDM-based mapping may be configured for an SRS resource or an SRS resource set.

[0268] The 22nd upper layer parameter may determine a subset for comb offset hopping. For example, the 22nd upper layer parameter may limit the value of the comb offset. The 22nd upper layer parameter may be subsetForCOH. If comb offset hopping is configured, the 22nd upper layer parameter may be configured.

[0269] The 23rd upper layer parameter may determine a subset for cyclic shift hopping. For example, the 23rd upper layer parameter may restrict the value of a cyclic shift offset. The 23rd upper layer parameter may be subsetForCSH. The 23rd upper layer parameter may be set if cyclic shift hopping is configured.

[0270] The 24th upper layer parameter may determine a scaling factor for cyclic shift hopping. For example, the 24th upper layer parameter may be K CS SRS The value of K may be determined. CS SRS may be multiplied by the cyclic shift maximum value. If cyclic shift hopping is configured, the 24th higher layer parameter may be configured.

[0271] The one or more SRS parameters may include some or all of the second to twenty-fourth higher 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.

[0272] 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 ap N antenna ports may be mapped to each OFDM symbol of the resource. SRS symb N can be 1, 2, 4, 8, or 12. SRSsymb may be 1, 2, 4, 8, 10, 12, or 14.

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

[0274] 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 ap If 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.

[0275] If the higher layer parameter resourceType is set to 'periodic', a target SRS resource (SRS resource) with a spatial domain filter (spatial domain transmission filter) may be transmitted. If a higher layer parameter includes an ID, a target SRS resource with a spatial domain filter may be transmitted. The spatial domain filter may be used to receive or transmit a reference reference signal (reference signal). The reference reference signal may be an SS / PBCH block, a CSI-RS, or an SRS. For example, if a higher layer parameter includes any of the IDs 'ssb-Index', 'ssb-IndexServing', and 'ssb-IndexNcell', the reference reference signal may be an SS / PBCH block. For example, if a higher layer parameter includes any of the IDs 'csi-RS-Index' and 'csi-RS-IndexServing', the reference reference signal may be a periodic CSI-RS or a semi-persistent CSI-RS. For example, if a certain higher layer parameter includes an ID of either 'srs' or 'srs-spatialRelation', the reference reference signal may be a periodic SRS. The reference reference signal may also be a DL PRS.

[0276] If 'semi-persistent' is set for the upper layer parameter resourceType, the first slot (n+3N subframe,μ slotSRS transmission may start from the first slot after slot n (slot n). For example, an assumption for SRS transmission may be applied from the first slot. Slot n may be a slot in which a PUCCH is transmitted. For example, the PUCCH may have HARQ-ACK information corresponding to a PDSCH carrying an activation command. That is, when an activation command is received, SRS transmission may start from the first slot. Also, when an activation command is received, an assumption for SRS transmission may be applied from the first slot. The activation command may include an assumption for spatial relationship (or spatial relationship). The assumption for spatial relationship may be provided by a list. The list may be a list of reference signal IDs. For example, each reference signal ID may refer to one of an SS / PBCH block, an NZP CSI-RS resource, or an SRS resource. NZP CSI-RS resources may be configured in one serving cell. SRS resources may be configured in one serving cell and one uplink BWP. For example, one serving cell may be indicated by a first field in the activation command. For example, one uplink BWP may be indicated by a second field in the activation command. The first field may be a Resource Serving Cell ID field. The second field may be a Resource BWP ID field. For example, one serving cell may be the same serving cell as the SRS resource set. For example, one uplink BWP may be the same uplink BWP as the SRS resource set.

[0277] When one SRS resource in the activated SRS resource set (resource set) is configured by a higher layer parameter, it may be assumed that the ID of the first reference signal in the activation command overrides the ID of the second reference signal in the higher layer parameter. The higher layer parameter may be spatialRelationInfo or spatialRelationInfoPos.

[0278] If a deactivation command is received and if a PUCCH is transmitted in slot n, the suspension of SRS transmission may be applied from the first slot. The deactivation command may be conveyed by a PDSCH. The PUCCH may include HARQ-ACK information corresponding to the PDSCH. The suspension of SRS transmission corresponding to the deactivated SRS resource set may be applied from the first slot. The first slot may be n+3N. subframe,μ slot μ may be the first slot after the slot. μ may be the SCS setting for the PUCCH.

[0279] If the terminal device 1 has an active semi-persistent SRS resource configuration and does not receive a deactivation command, the semi-persistent SRS resource configuration may be considered active in one uplink BWP. One uplink BWP may be active. Also, if the terminal device 1 has an active semi-persistent SRS resource configuration and receives a deactivation command, the semi-persistent SRS resource configuration may be suspended.

[0280] If 'aperiodic' is set for the higher layer parameter resourceType, some or all of actions 1 to 7 may apply.

[0281] Operation 1 may be receiving a configuration of one of one or more SRS resource sets.

[0282] Operation 2 may be receiving one command. The one command may be one downlink DCI-based command. The one command may be one group common DCI-based command. The one command may be one uplink DCI-based command. The minimal time interval is N2 OFDM symbols plus an additional time period T switch The minimum time interval may be the minimum time interval from the last OFDM symbol of the PDCCH that triggers aperiodic SRS transmission to the first OFDM symbol of the SRS resource. The minimum time interval may be N2+14 OFDM symbols plus an additional time period T switch The minimum time interval may be determined based at least on a minimum SCS. The minimum SCS may be the minimum SCS among the SCSs of the PDCCH, the first uplink carrier, the second uplink carrier, and the SRS. The additional time period T switch may be 0.

[0283] Operation 3 may be to trigger an aperiodic SRS without data and CSI. For example, DCI format 0_1 ​​and DCI format 0_2 may trigger an aperiodic SRS. The aperiodic SRS may not include data and CSI.

[0284] In operation 4, the terminal device 1 may transmit an SRS in each of one or more SRS resource sets and in the t+1th available slot. The SRS may be an aperiodic SRS. The one or more SRS resource sets may be triggered by a DCI. The DCI triggering the aperiodic SRS may be received in the first slot n. At least one resource set (SRS resource set) may be configured by an upper layer parameter availableSlotOffset. The available slot may be counted from the second slot. The second slot may be determined based on at least the first slot and an offset value (slot k). The offset value may be configured by a second upper layer parameter. The second upper layer parameter may be slotOffset. The second upper layer parameter may be configured for each of the one or more triggered SRS resource sets. The available slot may be a slot that satisfies a condition. The condition may be that a UL symbol or a flexible symbol exists for time domain positions corresponding to multiple SRS resources in one resource set (SRS resource set). The condition may be that the UE capability of a minimum timing requirement is satisfied. The minimum timing requirement may be the minimum timing requirement between the triggering PDCCH and all SRS resources in one resource set. From the first OFDM symbol carrying the DCI of the SRS request to the last OFDM symbol of the triggered SRS resource set, the terminal device 1 may not expect to receive the SFI indication, the UL cancellation indication, and dynamic scheduling of the downlink channel / signal in the flexible symbol. From the first OFDM symbol carrying the DCI of the SRS request to the last OFDM symbol of the triggered SRS resource set, the terminal device 1 may not expect to change the determination of the available slot. The time t may be set by a third higher layer parameter. The third higher layer parameter may be availableSlotOffset.For example, t may be configured with up to four values ​​for each of one or more triggered SRS resource sets. t may be based on the subcarrier spacing of the triggered SRS transmission. For SRS resource sets for which the third higher layer parameter is not configured, t may be 0.

[0285] Operation 5 may be transmitting an SRS in each of one or more SRS resource sets and in the first slot. The SRS may be an aperiodic SRS. DCI triggering the aperiodic SRS may be received in slot n. There may be no resource set (SRS resource set) for which the first higher layer parameter is configured. A second higher layer parameter may be configured. The second higher layer parameter may be ca-SlotOffset. The first slot may be determined based at least on slot n and slot k.

[0286] Act 6 may be transmitting the target SRS resource with one spatial domain filter.

[0287] Operation 7 may be that the spatial relationship update for one SRS resource is applied to an SRS transmission. subframe,μ slot The update command may start from the first slot after the nth slot. μ may be the SCS setting of the PUCCH. The update command may be transmitted by the PDSCH. A HARQ-ACK corresponding to the PDSCH may be transmitted in slot n. One SRS resource may be configured by the higher layer parameter SRS-Resource. The terminal device 1 may receive an update command (spatial relation update command). The update command may include an assumption of the spatial relationship. The assumption of the spatial relationship may be provided by a list. The list may refer to one or more reference signal IDs.

[0288] Setting 'aperiodic' for the higher layer parameter resourceType may indicate that the SRS resource corresponds to aperiodic SRS (aperiodic). Setting 'semi-persistent' for the higher layer parameter resourceType may indicate that the SRS resource corresponds to semi-persistent SRS (semi-persistent). Setting 'periodic' for the higher layer parameter resourceType may indicate that the SRS resource corresponds to periodic SRS (periodic).

[0289] The time domain behavior corresponding to one or more SRS resources in one SRS resource set may not be expected to differ. For example, different time domain behaviors may not be expected to be configured for one or more SRS resources in one SRS resource set. Different time domain behaviors may not be expected to be configured between SRS resources and their associated SRS resource sets.

[0290] It may not be expected that the first SRS resource and the second SRS resource on one carrier overlap one or more OFDM symbols. For example, the first SRS resource may be configured by the higher layer parameter SRS-PosResource. The second SRS resource may be configured by the higher layer parameter SRS-Resource. The resourceType of both the first SRS resource and the second SRS resource may be 'periodic'.

[0291] The first SRS may not be expected to trigger or activate transmission of the first SRS. For example, the first SRS may be an SRS in one or more OFDM symbols. One or more OFDM symbols may overlap the first SRS resource and the second SRS resource. For example, the first SRS resource may be configured by the higher layer parameter SRS-PosResource. The second SRS resource may be configured by the higher layer parameter SRS-Resource. The resourceType of both the first SRS resource and the second SRS resource may be 'semi-persistent' or 'aperiodic'.

[0292] In one carrier, configuration of multiple OFDM symbols overlapping with multiple SRS resources may not be expected. Multiple SRS resources may be configured by the higher layer parameter SRS-PosResource where the resourceType of the multiple SRS resources is 'periodic'.

[0293] A carrier may not be expected to trigger or activate SRS transmission in multiple OFDM symbols, which may overlap with the SRS resources. The SRS resources may be configured by the higher layer parameter SRS-PosResource, where the resourceType of the SRS resources is 'semi-persistent' or 'aperiodic'.

[0294] For PUCCH and SRS on one carrier, the terminal device 1 may not transmit an SRS when a first SRS is configured. The first SRS may be configured in the same OFDM symbol as the PUCCH. The PUCCH may carry only a CSI report. The PUCCH may carry only an L1-RSRP report. The PUCCH may carry only an L1-SINR report. The terminal device 1 may not transmit an SRS when transmission of a second SRS is configured or triggered. The second SRS may be either a semi-persistent SRS or a periodic SRS configured to be transmitted in the same OFDM symbol as the PUCCH. The second SRS may be an aperiodic SRS triggered to be transmitted in the same OFDM symbol as the PUCCH. The PUCCH may carry some or all of an HARQ-ACK, a link recovery request, and a scheduling request (SR). If the SRS is not transmitted due to overlap with the PUCCH, only the SRS symbols that overlap with the PUCCH symbols may be dropped. SRS ap If is 8, SRS symbols that overlap with PUCCH symbols and SRS symbols that do not overlap with PUCCH symbols may be dropped. If an aperiodic SRS is triggered to be transmitted because it overlaps with PUCCH, PUCCH may not be transmitted.

[0295] When one SRS resource corresponding to a resourceType set to 'aperiodic' is triggered in one or more OFDM symbols for which periodic or semi-persistent SRS transmission is configured, the terminal device 1 may transmit the aperiodic SRS resource, and the periodic or semi-persistent SRS in the overlapping OFDM symbols may be dropped. The periodic or semi-persistent SRS in the non-overlapping OFDM symbols may be transmitted. SRS apIf N is 8, periodic or semi-persistent SRS in non-overlapping OFDM symbols may be dropped. Dropping may also mean not transmitting. If an SRS resource corresponding to resourceType set to 'semi-persistent' is triggered in one or more OFDM symbols for which periodic SRS transmission is configured, the terminal device 1 may transmit the semi-persistent SRS resource, and periodic SRS in overlapping OFDM symbols may be dropped. Periodic SRS in non-overlapping OFDM symbols may be transmitted. N SRS ap If is 8, periodic or semi-persistent SRS in overlapping OFDM symbol sets may be dropped.

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

[0297] Number of SRS ports N SRS ap may be 8. For example, N for one SRS resource SRSap 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 S ap 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.

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

[0299] 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}.

[0300] The codebook subset is 'fullCoherent' because each layer has N SRS ap (e.g., 8) antenna ports. When the codebook subset is '4port-partialCoherent', each layer may be mapped to 4 antenna ports. When the codebook subset is '2port-partialCoherent', each layer may be mapped to 2 antenna ports. When the codebook subset is 'nonCoherent', each layer may be mapped to 1 antenna port.

[0301] S ap If S is 2, then antenna ports {1000, 1001, 1004, 1005} may be mapped to the first OFDM symbol. ap If is 2, then antenna ports {1002, 1003, 1006, 1007} ​​may be mapped to the second OFDM symbol.

[0302] For one SRS resource, the repetition factor R fac may be set. The number of repetitions may be set by a higher layer parameter. The number of repetitions may be 1, 2, or 4. The number of repetitions may be 1, 2, 3, 4, 5, 6, 7, 8, 10, 12, or 14. The number of repetitions R fac may be set by the upper layer parameter resourceMapping in the upper layer parameter SRS-Resource. fac may be determined based on the DCI format. SRS symb It may be the following:

[0303] R fac N SRS symb It may be the same as that frequency hopping is not set. fac N SRS symb The same as N may be the case when one or both of cyclic shift hopping and sequence hopping are not configured. Each of the multiple antenna ports of one SRS resource may be mapped to the first set. For example, when frequency hopping is not configured, each of the multiple antenna ports of one SRS resource in each slot may be mapped to N SRS symb All of the OFDM symbols may be mapped to the first set. The first set may be a set of one or more subcarriers. The first set may be a set of one or more subcarriers in the second set. The second set may be a set of one or more PRBs. For example, if frequency hopping is not configured within one SRS resource in each slot, each of the multiple antenna ports of one SRS resource in each slot may be mapped to N SRS symb All of the OFDM symbols may be mapped to the first set.SRS symb is R fac It may be divisible by R fac is S ap X can be divisible by Y if mod(X,Y) is 0. ap When is used, R fac is S ap It may be more than that. ap When is used, R fac is S ap may be divisible by

[0304] S ap The fact that S is used ap It is also possible that S is greater than 1. ap The fact that S is not used ap may be 1. S ap The use of S may be to set the TDM base mapping. ap The fact that S is not used may mean that TDM-based mapping is not set. ap It is also possible that the number of TDM-based mappings is 2. ap may be 1. S ap is used because at least N SRS ap may include that is 8.

[0305] S ap and R fac The product of R s For example, R s R may be the repetition number for the SRS ports mapped to one OFDM symbol. s may be the number of OFDM symbols. s is N SRS symb It may be less than N SRS symb is R s It may be. S ap If is greater than 1, R s may be used.ap If is set, R s If TDM-based mapping is configured, R s may be used. R s When is used, R s is N SRS symb The following may be used: R s When is used, N SRS symb is R s R s When is used, R s is not expected to be 1. s N SRS symb It may be the same as that frequency hopping is not set. s N SRS symb The same as N may be the case when one or both of cyclic shift hopping and sequence hopping are not configured. For example, when frequency hopping is not configured, each of the multiple antenna ports of one SRS resource in each slot is N SRS symb may be mapped to the same set of subcarriers in all of the OFDM symbols. s S ap The same as R may be set to frequency hopping without repetition. s S ap If the SRS resource is the same as S, multiple antenna ports (or each of the antenna ports) of one SRS resource may be mapped to different sets. The different sets may be sets of subcarriers. The different sets may be S ap may be the subcarrier sets in each set of OFDM symbols (or adjacent OFDM symbols). s S ap If greater than N SRS symb is 2R s If R is larger than R, each of the antenna ports of one SRS resource in each slot iss In each set of N adjacent OFDM symbols, the subcarriers may be mapped to the same subcarrier set. SRS symb / R s The frequency hopping in this set may be in accordance with the SRS hopping parameters. SRS symb is R s It can be divisible by N SRS symb and R s The remainder of the division may be 0.

[0306] The first one or more antenna ports may correspond to a first cyclic shift (CS) set. For example, if cyclic shift hopping is not configured, the first one or more antenna ports in each slot may correspond to N SRS symb All of the OFDM symbols may correspond to a first CS set. The first CS set may be a set of cyclic shifts αi corresponding to the first one or more antenna ports pi. For example, if cyclic shift hopping is not configured within one SRS resource in each slot, the first one or more antenna ports in each slot may correspond to N SRS symb All of the OFDM symbols may correspond to the first CS set.

[0307] Furthermore, frequency hopping is configured within one SRS resource in each slot, and there is no repetition (the number of repetitions is 1 or S ap If , each of the antenna ports of one SRS resource in each slot may be mapped to a different set in each OFDM symbol. A set may be a set of one or more subcarriers. The same comb number (transmission comb value) may be assumed for the different sets.

[0308] Furthermore, cyclic shift hopping is configured within one SRS resource in each slot, and there is no repetition (the number of repetitions is 1 or Sap , the first one or more antenna ports in each slot are S ap Each set of adjacent OFDM symbols may be mapped to a different CS set. A CS set may be a set of cyclic shifts αi corresponding to the first one or more antenna ports pi. The same comb number (transmission comb value) may be assumed for the different CS sets.

[0309] When frequency hopping and repetition are configured, each of one or more antenna ports of one SRS resource may be mapped to a subcarrier included in an n-th subcarrier set in an OFDM symbol included in an n-th OFDM symbol set. The n-th OFDM symbol set is denoted by R fac R fac may be the number of repetitions. The nth subcarrier set may be composed of one or more subcarriers. n may be an integer equal to or greater than 1. For example, n may be N SRS symb / R fac In this case, mod(R fac , S ap ) may be 0. The nth subcarrier set may be configured with one or more subcarriers different from the subcarrier sets other than the nth subcarrier set. When frequency hopping and repetition are configured within one SRS resource in each slot, each of the antenna ports of one SRS resource in each slot is fac The subcarriers may be mapped to the same subcarrier set within each of the pairs of OFDM symbols, and frequency hopping between the two pairs may follow an SRS frequency hopping pattern. Frequency hopping according to the SRS frequency hopping pattern may mean that frequency hopping is applied, performed, or configured.

[0310] When frequency hopping and repetition are configured, each of one or more antenna ports of one SRS resource may be mapped to a subcarrier included in an n-th subcarrier set in an OFDM symbol included in an n-th OFDM symbol set. The n-th OFDM symbol set is denoted by R s The nth subcarrier set may be a pair of adjacent OFDM symbols. The nth subcarrier set may consist of one or more subcarriers. n may be an integer equal to or greater than 1. For example, n may be N SRS symb / R s The n-th subcarrier set may be configured by one or more subcarriers different from the subcarrier sets other than the n-th subcarrier set. When frequency hopping and repetition are configured within one SRS resource in each slot, each of the antenna ports of one SRS resource in each slot may be configured by R s Within each of the pairs of OFDM symbols, the subcarriers may be mapped to the same subcarrier set, and frequency hopping between the two pairs may follow the SRS frequency hopping pattern.

[0311] When cyclic shift hopping is configured, one or more antenna ports (SRS ports) may correspond to an n-th cyclic shift in the OFDM symbols included in the n-th OFDM symbol set. fac The nth cyclic shift may be a pair of adjacent OFDM symbols. The nth cyclic shift may be the nth CS set. n may be an integer equal to or greater than 1. For example, the maximum number of n is N SRS symb / R fac In this case, mod(R fac , S ap ) may be 0. When cyclic shift hopping and repetition are configured within one SRS resource in each slot, the antenna port of one SRS resource in each slot is R facThe same cyclic shift may be assigned to a pair of OFDM symbols, and cyclic shift hopping between the two pairs may follow a cyclic shift hopping pattern. The cyclic shift hopping following the cyclic shift hopping pattern may mean that cyclic shift hopping is applied, performed, or configured. Whether cyclic shift hopping is applied may be configured by a higher layer parameter.

[0312] When cyclic shift hopping is configured, one or more antenna ports (SRS ports) may correspond to an n-th cyclic shift in the OFDM symbols included in the n-th OFDM symbol set. s The nth cyclic shift may be a pair of adjacent OFDM symbols. The nth cyclic shift may be the nth CS set. n may be an integer equal to or greater than 1. For example, the maximum number of n is N SRS symb / R s When cyclic shift hopping and repetition are configured within one SRS resource in each slot, the antenna port of one SRS resource in each slot may be R s Within a pair of OFDM symbols, the symbols may correspond to the same cyclic shift, and the cyclic shift hopping between the two pairs may follow a cyclic shift hopping pattern.

[0313] If the number of antenna ports is 8, N SRS symb / R fac can be an even number. If the number of antenna ports is 8, N SRS symb / R fac may be 2 or more. If the number of antenna ports is 8, and S apIf the number of antenna ports is 2, a first antenna port set and a second antenna port set may be determined. The antenna port sets may consist of four antenna ports. The first subcarrier set to which the first antenna port set is mapped in the first OFDM symbol may be the same as the second subcarrier set to which the second antenna port set is mapped in the second OFDM symbol. The first OFDM symbol may be different from the second OFDM symbol. If the number of antenna ports is 8, cyclic shift hopping may be applied.

[0314] For example, each of the antenna ports included in the first antenna port set of one SRS resource may be mapped to a first subcarrier set in a first OFDM symbol included in the first OFDM symbol set. Each of the antenna ports included in the second antenna port set may be mapped to a first subcarrier set in a second OFDM symbol included in the first OFDM symbol set. Each of the antenna ports included in the first antenna port set may be mapped to a second subcarrier set in a first OFDM symbol included in the second OFDM symbol set. Each of the antenna ports included in the second antenna port set may be mapped to a second subcarrier set in a second OFDM symbol included in the second OFDM symbol set. Switching the mapping from the first subcarrier set to the second subcarrier set may be referred to as frequency hopping. For example, if the number of antenna ports is 8, N SRS symb / R fac Frequency hopping may be applied to every OFDM symbol. In this case, mod(R fac , S ap ) may be 0. For example, if the number of antenna ports is 8, N SRS symb / R sFrequency hopping may be applied to each OFDM symbol. An OFDM symbol set may consist of two or more OFDM symbols. A subcarrier set may consist of one or more subcarriers. An antenna port set may consist of N SRS ap / S ap It may be configured with antenna ports.

[0315] For example, if the number of antenna ports is four or less, a first hopping frequency (first SRS hopping pattern) may be applied. If the number of antenna ports is eight, a second hopping frequency (second SRS hopping pattern) may be applied. The first SRS hopping pattern may be different from the second SRS hopping pattern.

[0316] Aperiodic SRS resources with intra-slot frequency hopping within one BWP may be configured. fac If is 1 and frequency hopping is configured, the full hopping bandwidth is N SRS symb The full hopping bandwidth is N SRS symb / R fac may be sounded with subbands of equal size across the set of N SRS symb / R fac Each of the sets is R fac may consist of adjacent OFDM symbols. In this case, mod(R fac , S ap ) may be 0. Each of the antenna ports of the SRS resource may be mapped to the same subcarrier set within each OFDM symbol set. The OFDM symbol set is R fac A subcarrier set may be a set of one or more subcarriers. facThe pair of adjacent OFDM symbols may be an OFDM symbol of the resource.

[0317] Aperiodic SRS resources with intra-slot frequency hopping within one BWP may be configured. s If is 1 and frequency hopping is configured, the full hopping bandwidth is N SRS symb The full hopping bandwidth is N SRS symb / R s may be sounded with subbands of equal size across the set of N SRS symb / R s Each of the sets is R s Each of the antenna ports of the SRS resource may be mapped to the same subcarrier set within each OFDM symbol set. An OFDM symbol set is a set of R s A subcarrier set may be a set of one or more subcarriers. s The pair of adjacent OFDM symbols may be an OFDM symbol of the resource.

[0318] Periodic or semi-persistent SRS resources may be configured with inter-slot or intra-slot hopping within one BWP. The SRS resources may occupy the same OFDM symbol position in each slot. An N-symbol SRS resource may occupy the same OFDM symbol position in each slot. N SRS symb is 4, and R facIf R is 2 and frequency hopping is configured, intra-slot hopping and inter-slot hopping may be supported for each of the multiple antenna ports. Each of the multiple antenna ports may be mapped to a different subcarrier set across two pairs in each slot. Each of the two pairs is mapped to a different subcarrier set across R. fac The SRS resource may be located in adjacent OFDM symbols. Each of the antenna ports of the SRS resource may be mapped to the same subcarrier set within each pair. Also, a first portion of the antenna ports of the SRS resource may be mapped to a first subcarrier set within each pair. A second portion of the antenna ports of the SRS resource may be mapped to a second subcarrier set within each pair.

[0319] Periodic or semi-persistent SRS resources with cyclic shift hopping within one BWP may be configured. The SRS resources may occupy the same OFDM symbol position in each slot. An N-symbol SRS resource may occupy the same OFDM symbol position in each slot. N SRS symb If R is 4, the number of repetitions is 2, and cyclic shift hopping is configured, one or more antenna ports may correspond to different CS sets across two pairs in each slot. Each of the two pairs corresponds to R fac adjacent OFDM symbols. One or more antenna ports may be mapped to the same CS set within each pair. Also, a first portion of the antenna ports of the SRS resources may be mapped to a first CS set within each pair. A second portion of the antenna ports of the SRS resources may be mapped to a second CS set within each pair.

[0320] FIG. 9 illustrates two example dropping rules for an SRS according to an aspect of the present embodiment. An SRS resource 900 may be determined in a slot. The terminal device 1 may transmit the SRS resource 900. The terminal device 1 may transmit an SRS corresponding to the SRS resource 900. The terminal device 1 may transmit an SRS in the SRS resource 900. The terminal device 1 may transmit an SRS resource set corresponding to the SRS resource 900. The SRS resource 900 may be associated with an aperiodic SRS. The SRS resource 900 may be associated with a periodic SRS. The SRS resource 900 may be associated with a semi-persistent SRS. That is, the resourceType of the SRS resource set including the SRS resource 900 may be set to 'aperiodic', 'semi-persistent', or 'periodic'. The SRS resource 900 to which one or more SRS sequences are mapped may be transmitted. The SRS resource 900 to which one or more SRSs are mapped may be transmitted. The SRS resource 900 may be indicated by an SRS Resource Indicator (SRI) field in the DCI. The SRS resource 900 may be identified by the SRI. The SRS resource 900 may be indicated by a higher layer parameter. For example, the higher layer parameter may be srs-ResourceIndicator or srs-ResourceIndicator2. The usage of the SRS resource set associated with the SRS resource 900 may be 'codebook'. The usage of the SRS resource set associated with the SRS resource 900 may be 'non-Codebook'. The SRS resource 900 may have one, two, four, or eight ports. For example, the SRS ports in the SRS resource 900 may be indexed as pi = 1000 + i. The SRS resource 900 may be one of K SRS resources included in one SRS resource set. One or more SRS parameters for the SRS resource 900 may be configured.For example, one or more SRS parameters may be configured by an SRS-Resource or an SRS-PorResource corresponding to the SRS resource 900. The SRS resource 900 may be a target SRS resource. The SRS resource 900 may be configured by a higher layer parameter. For example, the SRS resource 900 may be configured in one serving cell and / or one uplink BWP. The SRS resource 900 may have one spatial domain filter.

[0321] The SRS may be transmitted in the SRS resource 900. The SRS sequence may be mapped to resource elements. For example, when the SRS is transmitted in the SRS resource 900, a sequence (SRS sequence) corresponding to each OFDM symbol and each antenna port may be mapped to a resource element (physical resource). The SRS resource 900 may be used for SRS transmission.

[0322] The number N of consecutive OFDM symbols for the SRS resource 900 SRS symb may be 2. SRS resource 900 may consist of at least OFDM symbol 920 and OFDM symbol 921. SRS resource 900 may occupy at least OFDM symbol 920 and OFDM symbol 921. OFDM symbol 920 and OFDM symbol 921 may be adjacent OFDM symbols.

[0323] The number of antenna ports for the SRS resource 900 (number of SRS ports) N SRS ap may be 8. In FIG. 9, the number of OFDM symbols S ap may be 1 or 2. ap may be determined for the SRS resource 900. ap may be determined for an SRS resource set that includes SRS resource 900.

[0324] The SRS resource 900 may be configured with SRS ports {1000, 1001, 1002, 1003, 1004, 1005, 1006, 1007}. A TDM-based mapping may be configured for the SRS resource 900. For example, ap SRS port sets may be determined. ap If S is 2, a first SRS port set and a second SRS port set may be determined. ap It may not be expected that frequency hopping will be performed within the OFDM symbols S ap If S is 2, the first SRS port set may be mapped to OFDM symbol 920. ap If ≠ 2, then a second SRS port set may be mapped to OFDM symbol 921. The first SRS port set may include SRS ports {1000, 1001, 1004, 1005}. The second SRS port set may include SRS ports {1002, 1003, 1006, 1007}.

[0325] For example, up to eight SRS sequences may be mapped to SRS resource 900. For example, up to eight SRS sequences may be multiplexed in SRS resource 900.

[0326] For example, some or all of the first SRS sequence, the second SRS sequence, the third SRS sequence, the fourth SRS sequence, the fifth SRS sequence, the sixth SRS sequence, the seventh SRS sequence, and the eighth SRS sequence may be mapped to SRS resource 900. The first SRS sequence may be determined based at least on the first antenna port. The second SRS sequence may be determined based at least on the second antenna port. The third SRS sequence may be determined based at least on the third antenna port. The fourth SRS sequence may be determined based at least on the fourth antenna port. The fifth SRS sequence may be determined at least on the fifth antenna port. The sixth SRS sequence may be determined at least on the sixth antenna port. The seventh SRS sequence may be determined at least on the seventh antenna port. The eighth SRS sequence may be determined based at least on the eighth antenna port.

[0327] For example, the first antenna port may be 1000. For example, the second antenna port may be 1001. For example, the third antenna port may be 1002. For example, the fourth antenna port may be 1003. For example, the fifth antenna port may be 1004. For example, the sixth antenna port may be 1005. For example, the seventh antenna port may be 1006. For example, the eighth antenna port may be 1007. For example, the first antenna port may be 1000. For example, the second antenna port may be 1002. For example, the third antenna port may be 1004. For example, the fourth antenna port may be 1006. For example, the fifth antenna port may be 1001. For example, the sixth antenna port may be 1003. For example, the seventh antenna port may be 1005. For example, the eighth antenna port may be 1007.

[0328] In means 3, if dropping rule 2 is applied, OFDM symbol 920 and OFDM symbol 921 may be dropped. For example, if dropping rule 2 is applied, SRS resource 900 may be dropped. If dropping rule 2 is applied, SRS resources may not be transmitted in OFDM symbol 920 and OFDM symbol 921. SRS resource 900 may start after a certain period 940. Transmission of SRS resource 900 may be after a certain period 940. If dropping rule 2 is applied and the uplink physical channel 910 overlaps after CORESET 900 after a certain period 940, SRS on OFDM symbol 920 and OFDM symbol 921 may be dropped. If dropping rule 2 is applied and OFDM symbol 920 is after a certain period 940, OFDM symbol 920 and OFDM symbol 921 may be dropped. If dropping rule 2 is applied and OFDM symbol 920 is after fixed period 940, SRS resource 900 in OFDM symbol 920 and OFDM symbol 921 may be dropped. If dropping rule 2 is applied and OFDM symbol 920 is within fixed period 940, dropping rule 1 may be applied.

[0329] The uplink physical channel 910 may be any of a PUSCH, a PRACH, and a PUCCH. The uplink physical channel 910 may overlap with the SRS resource 900. For example, the uplink physical channel 910 may overlap with the SRS resource 900 in OFDM symbol 920. The uplink physical channel 910 may not overlap with the SRS resource 900 in OFDM symbol 921. The uplink physical channel 910 may be scheduled by a DCI associated with a CORESET 930. The period 940 may start from the last OFDM symbol of the CORESET 930.

[0330] If dropping rule 1 is applied, OFDM symbol 920 may be dropped. If dropping rule 1 is applied, SRS resource 900 (e.g., the SRS corresponding to SRS resource 900) in OFDM symbol 920 may be dropped. If dropping rule 1 is applied, OFDM symbol 921 may not be dropped. If dropping rule 1 is applied, SRS resource 900 (e.g., the SRS corresponding to SRS resource 900) in OFDM symbol 921 may be transmitted.

[0331] The terminal device 1 may monitor a set of multiple PDCCH candidates within a search space set. The search space set may be configured monitoring opportunities within one or more configured CORESETs corresponding to search space configurations. The search space set may be determined based on the CORESET. The search space set may be configured based on the CORESET. The CORESET 900 may be a CORESET. The CORESET 900 may be composed of the number of RBs and the number of symbols. Multiple CORESETs 900 may be configured in the terminal device 1. The CORESET 900 may be determined based on higher layer parameters. The CORESET 900 may be configured by higher layer parameters. The higher layer parameter may be ControlResourceSet. The size of the frequency domain of the CORESET 900 may be given by higher layer parameters. The higher layer parameter may be frequencyDomainResources. The time period of the CORESET 900 may be given by higher layer parameters. The higher layer parameter may be duration.

[0332] For a certain period 940 is T proc,2 may be.

[0333] The problem is that, although the SRS may be used to measure channel quality, when the SRS overlaps with an uplink physical channel, it is necessary to appropriately refer to or drop the SRS for transmitting the PUSCH. Means 1, 2, and 3 may be used to solve the problem.

[0334] The terminal device 1 may include a generating unit. For example, the generating unit may generate a baseband signal. The generating unit may generate an SRS sequence (SRS signal, SRS). The transmitting unit in the terminal device 1 may transmit the SRS. That is, the transmitting unit in the terminal device 1 may transmit an SRS resource. Transmitting the SRS may be transmitting the SRS resource. The terminal device 1 may transmit the SRS in the SRS resource. The terminal device 1 may transmit the SRS in the SRS resource to which the SRS sequence is mapped. The SRS sequence corresponding to the SRS resource may be multiplexed. The generating unit in the terminal device 1 may generate the SRS sequence corresponding to the SRS resource.

[0335] The SRS sequences may be mapped to the SRS resources. The SRS sequences may be multiplexed in the SRS resources. The SRS resources may consist of at least the number of OFDM symbols. For example, the number of OFDM symbols may be N SRS symb The SRS resource may be SRS symb The SRS resource may be composed of OFDM symbols. An OFDM symbol index for the SRS resource may be determined. For example, the OFDM symbol index may be from 0 to N SRS symb It may have a value up to -1.

[0336] The terminal device 1 may include a generating unit. For example, the generating unit may generate a baseband signal. The generating unit may generate a PUSCH. A transmitting unit in the terminal device 1 may transmit the PUSCH.

[0337] 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. The higher layer parameters may provide either codebook transmission or non-codebook transmission. For example, if 'codebook' is set for the higher layer parameters, the terminal device 1 may be configured for codebook transmission. The higher layer parameters may be txConfig. The higher layer parameters may be usage.

[0338] The codebook transmission may be transmission based on codebook type 1 or codebook type 2. If a first higher layer parameter is configured, the codebook transmission may be transmission based on codebook type 1. If a second higher layer parameter is configured, the codebook transmission may be transmission based on codebook type 2.

[0339] The PUSCH transmission may be a transmission based on codebook type 1 or codebook type 2. If a first higher layer parameter is configured, the PUSCH transmission may be a transmission based on codebook type 1. If a second higher layer parameter is configured, the PUSCH transmission may be a transmission based on codebook type 2.

[0340] The terminal device 1 may determine a codebook. The codebook may be determined by a DCI field (e.g., a precoding information field and a number of layers field). The codebook may be determined based on a codebook type. The codebook type may be determined by an upper layer parameter. The codebook may be determined based on an upper layer parameter. The upper layer parameter may be one or both of CodebookType and ULcodeboookFC-N1N2. The upper layer parameter may be set to Ng=1. If the upper layer parameter is set to Ng=1, the codebook may be determined based on codebook type 1. The upper layer parameter may be set to Codebook1. If the upper layer parameter is set to Codebook1, the codebook may be determined based on codebook type 1. The upper layer parameter may be set to Fullcoherent. If the upper layer parameter is set to Fullcoherent, the codebook may be determined based on codebook type 1. The upper layer parameter may be set to Codebook2, Codebook3, or Codebook4. When an upper layer parameter is set to Codebook2, Codebook3, or Codebook4, the codebook may be determined based on codebook type 2. The upper layer parameter may be set to Ng=2, Ng=4, or Ng=8. When an upper layer parameter is set to Ng=2, Ng=4, or Ng=8, the codebook may be determined based on codebook type 2. The upper layer parameter may be set to Partialcoherent or Noncoherent. When an upper layer parameter is set to Partialcoherent or Noncoherent, the codebook may be determined based on codebook type 2.

[0341] The number of bits in the DCI field for "Precoding information and number of layers" may be determined based on higher layer parameters. The higher layer parameters may be some or all of CodebookType, maxRank, and ULcodebookFC-N1N2. When codebook type 1 is configured, the number of bits in the DCI field for "Precoding information and number of layers" may be a first number of bits. When codebook type 2 is configured, the number of bits in the DCI field for "Precoding information and number of layers" may be a second number of bits.

[0342] The TPMI may be determined based on a first table. The first table may be determined based on higher layer parameters. The higher layer parameters may be some or all of CodebookType, maxRank, and ULcodebookFC-N1N2. When codebook type 1 is set, the TPMI may be determined based on the first table. Codebook Type

[0343] The TPMI may be determined based on a second table. The second table may be determined based on higher layer parameters. The higher layer parameters may be some or all of CodebookType, maxRank, and ULcodebookFC-N1N2. When Codebook Type 2 is configured, the TPMI may be determined based on the second table.

[0344] Setting codebook type 1 may mean that CodebookType is set to Codebook1. Setting codebook type 1 may mean that CodebookType is set to Codebook1. Setting codebook type 1 may mean that CodebookType=Codebook1. Setting codebook type 1 may mean that CodebookType=Codebook1. Setting codebook type 1 may mean that CodebookType is set to Ng=1. Setting codebook type 1 may mean that CodebookType is set to Ng=1. Setting codebook type 1 may mean that CodebookType is set to Fullcoherent. Setting codebook type 1 may mean that CodebookType is set to Fullcoherent.

[0345] Setting codebook type 2 may mean that CodebookType is set to Codebook2, Codebook3, or Codebook4. Setting codebook type 2 may mean that CodebookType is set to Codebook2, Codebook3, or Codebook4. Setting codebook type 2 may mean that CodebookType=Codebook2, CodebookType=Codebook3, or CodebookType=Codebook4. Setting codebook type 2 may mean that CodebookType=Codebook2, CodebookType=Codebook3, or CodebookType=Codebook4. Setting codebook type 1 may mean that CodebookType is set to Ng=2, Ng=4, or Ng=8. Setting codebook type 1 may mean that CodebookType is set to Ng=2, Ng=4, or Ng=8. Setting codebook type 1 may mean that CodebookType is set to PartialCoherent or NonCoherent. Setting codebook type 1 may mean that CodebookType is set to PartialCoherent or NonCoherent.

[0346] Setting codebook type 1 may mean setting a first codebook type, and setting codebook type 2 may mean setting a second codebook type.

[0347] The terminal device 1 may include a receiving unit that receives a PDCCH. The DCI may be arranged (mapped) to the PDCCH. The DCI may indicate an SRS resource. For example, the DCI may indicate an SRS resource in an SRI field. The number of antenna ports for the SRS resource (the number of SRS ports) N SRS apmay be any of 1, 2, 4, and 8. The SRS resource may be determined for one or more antenna ports. That is, the SRS resource may be N SRS ap may be determined for the antenna ports.

[0348] The terminal device 1 may include a receiving unit that receives a PDCCH. The DCI may be mapped to the PDCCH. The DCI may indicate transmission of a PUSCH. The DCI may schedule the PUSCH or PUSCH transmission. For example, the DCI may indicate an SRS resource for transmitting the PUSCH in an SRI field.

[0349] 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 resources.

[0350] The SRS sequence may be determined based on a first function. For example, when TDM-based mapping is configured, the SRS sequence may be generated based on a first function. The first function is w TDM The first function may be determined based on a first parameter and a second parameter. The first parameter may be pi. The second parameter may be l'. l' may be an OFDM symbol index. l' may take a first value. The first value may be greater than or equal to 0 and less than or equal to N SRS symbThe first function may take a value equal to or less than -1. When TDM-based mapping is configured, if l' is an even number, and if pi is 1000, 1001, 1004, or 1005, the first function may take a second value. When TDM-based mapping is configured, if l' is an odd number, and if pi is 1002, 1003, 1006, or 1007, the first function may take a second value. When non-TDM-based mapping is configured, the SRS sequence may be generated without using the first function. When non-TDM-based mapping is configured, the SRS sequence may be generated using the first function with the second value. The second value may be 1. When TDM-based mapping is configured, if the value of the second parameter is an odd number, and if the value of the first parameter is 1000, 1001, 1004, or 1005, the first function may take a third value. If TDM-based mapping is configured, and if the value of the second parameter is an even number, and if the value of the first parameter is 1002, 1003, 1006, or 1007, the first function may be a third value. The third value may be 0.

[0351] The SRS sequence may be determined based at least on a cyclic shift, which may be αi or n CS,i SRS One cyclic shift may be determined for one antenna port. One cyclic shift may be determined for one SRS port. The SRS ports may be indexed as pi = 1000 + i. The cyclic shift is determined by pi bar and N SRSbar ap It may be determined based on pi bar may be determined based on pi. If TDM-based mapping is configured and pi-1000 is less than the first value, pi bar = 1000 + mod(pi, 2). If TDM-based mapping is configured and pi - 1000 is equal to or greater than the first value, pi bar= 1000 + mod(pi, 2) + 2. The first value may be 4. When non-TDM base mapping is configured, pi bar If TDM-based mapping is configured, N SRSbar ap may be a first value. The first value may be 4. If non-TDM based mapping is configured, N SRSbar ap may be the second value. The second value may be 8. The second value may be N SRS ap If non-TDM based mapping is configured, N SRSbar ap =N SRS ap may be.

[0352] The terminal device 1 may not expect that cyclic shift hopping and TDM base mapping are configured at the same time. If cyclic shift hopping is configured, the terminal device 1 may not expect that TDM base mapping is configured. The terminal device 1 may not expect that comb offset hopping and TDM base mapping are configured at the same time. If comb offset hopping is configured, the terminal device 1 may not expect that TDM base mapping is configured.

[0353] 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 If the number of SRS ports is 8, the 8 SRS ports may be provided. ap may be evenly mapped to S OFDM symbols. ap may be determined by higher layer parameters. ap may be determined by higher layer parameters for the SRS resource set. apmay be determined by higher layer parameters for the SRS resource. If the number of SRS ports configured for the SRS resource is not 8, S ap The upper layer parameter that determines the port number may be ignored. The upper layer parameter may be nrofSRS-Ports-n8. The upper layer parameter may be ports8tdm. The upper layer parameter may be tdm. The upper layer parameter may be some or all of nrofSRS-Ports-n8 and ports8tdm and tdm.

[0354] The TDM base mapping is configured ap may be 2. Configuring a TDM-based mapping may mean that TDM is configured. Configuring a TDM-based mapping may mean that a first parameter is configured with a second parameter. Configuring a TDM-based mapping may mean that a first parameter is configured with a second parameter. Configuring a TDM-based mapping may mean that a first parameter indicating the second parameter is configured. The first parameter may be nrofSRS-Ports-n8. The second parameter may be ports8tdm. The second parameter may be tdm. Configuring a non-TDM-based mapping may mean that S ap may be 1. When non-TDM-based mapping is configured, non-TDM may be configured. When non-TDM-based mapping is configured, TDM-based mapping may not be configured. When non-TDM-based mapping is configured, TDM may not be configured. 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.

[0355] S apmay 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.

[0356] In the means 1, when codebook type 1 is configured, only non-TDM-based mapping may be configured. When codebook type 1 is configured, it may not be expected that TDM-based mapping will be configured. When codebook type 2 is configured, non-TDM-based mapping or TDM-based mapping may be configured. When the first codebook type is configured for the PUSCH, only non-TDM may be configured for the SRS. When the second codebook type is configured for the PUSCH, non-TDM or TDM may be configured for the SRS. When the first codebook type is configured for the PUSCH, only non-TDM-based mapping may be configured for the SRS. When the second codebook type is configured for the PUSCH, non-TDM-based mapping or TDM-based mapping may be configured for the SRS.

[0357] The time domain behavior of SRS resource configuration may be determined by a higher layer parameter. The higher layer parameter may be resourceType. ResourceType may be set to "aperiodic", "periodic", or "semi-persistent". The OFDM symbol on which SRS is transmitted may be dropped based on either Dropping Rule 1 or Dropping Rule 2. SRS transmission may be dropped based on either Dropping Rule 1 or Dropping Rule 2. The symbols to be dropped may be determined based on either Dropping Rule 1 or Dropping Rule 2. The terminal device 1 may transmit an aperiodic SRS or an aperiodic SRS resource in a first symbol. For example, if an SRS resource with a resourceType set to aperiodic is triggered on the first symbol, the terminal device 1 may transmit an aperiodic SRS resource. If an SRS resource with a resourceType set to aperiodic is triggered on the first symbol, only periodic or semi-persistent SRS symbols that overlap within the first symbol may be dropped. When an SRS resource with a resourceType set to Aperiodic is triggered on a first symbol, periodic or semi-persistent SRS symbols that do not overlap with aperiodic SRS resources may be transmitted. The first symbol may be an OFDM symbol for which periodic or semi-persistent SRS transmission is set. When an SRS resource with a resourceType set to Semi-persistent is triggered on a second symbol, the terminal device 1 may transmit the semi-persistent SRS resource. When an SRS resource with a resourceType set to Semi-persistent is triggered on a second symbol, only overlapping periodic SRS symbols within the second symbol may be dropped.If an SRS resource with resourceType set to semi-persistent is triggered on the second symbol, a periodic SRS symbol that does not overlap with the semi-persistent SRS resource may be transmitted. The second symbol may be the OFDM symbol where periodic SRS transmission is configured.

[0358] When Dropping Rule 1 is applied, the first SRS (or the first SRS resource) may be transmitted in the first OFDM symbol. When Dropping Rule 1 is applied, the other uplink physical channel / signal may be dropped in the second OFDM symbol. When Dropping Rule 1 is applied, the other uplink physical channel / signal may be transmitted in the third OFDM symbol. The first OFDM symbol and the second OFDM symbol may be the same. For example, the first SRS may overlap with the other uplink physical channel / signal in the second OFDM symbol. For example, the first SRS may not overlap with the other uplink physical channel / signal in the third OFDM symbol. When the first SRS (or the first SRS resource) is an aperiodic SRS (or an aperiodic SRS resource), the other uplink physical channel / signal may be a periodic SRS or a semi-persistent SRS. When the first SRS (or the first SRS resource) is a semi-persistent SRS (or a semi-persistent SRS resource), another uplink physical channel / signal may be a periodic SRS. Dropping an SRS in a certain OFDM symbol may mean dropping the certain OFDM symbol.

[0359] The OFDM symbol on which the SRS is transmitted may be dropped based on dropping rule 1 or dropping rule 2. The SRS transmission may be dropped based on dropping rule 1 or dropping rule 2. The symbols to be dropped may be determined based on dropping rule 1 or dropping rule 2. When periodic or semi-persistent SRS is configured in the same symbol as the first PUCCH, the terminal device 1 may not transmit the SRS. The first PUCCH may carry only CSI-report(s). The first PUCCH may carry only L1-RSRP report(s). The first PUCCH may carry only L1-SINR report(s). When periodic or semi-persistent SRS is configured in the same symbol as the second PUCCH, or when aperiodic SRS transmission is triggered in the same symbol as the second PUCCH, the terminal device 1 may not transmit the SRS. The second PUCCH may carry some or all of the HARQ-ACK, link recovery request, and SR. If no SRS is transmitted due to overlap with the first and second PUCCHs, only the SRS symbols that overlap with the PUCCH symbols may be dropped.

[0360] When Dropping Rule 1 is applied, the first SRS (or the first SRS resource) may not be transmitted in the first OFDM symbol. When Dropping Rule 1 is applied, the first SRS (or the first SRS resource) may be dropped in the first OFDM symbol. When Dropping Rule 1 is applied, the other uplink physical channel / signal may be transmitted in the second OFDM symbol. When Dropping Rule 1 is applied, the first SRS (or the first SRS resource) may be transmitted in the third OFDM symbol. The first OFDM symbol and the second OFDM symbol may be the same. For example, the first SRS may overlap with the other uplink physical channel / signal in the first OFDM symbol. For example, the first SRS may not overlap with the other uplink physical channel / signal in the third OFDM symbol. When the other uplink physical channel / signal is the first PUCCH, the first SRS may be a periodic or semi-persistent SRS. If the other uplink channel physical / signal is a second PUCCH, the first SRS may be a periodic, semi-persistent, or aperiodic SRS. The first PUCCH may be a PUCCH for a CSI report, an L1-RSRP report, or an L1-SINR report. The second PUCCH may be a PUCCH for a HARQ-ACK, a Link recovery request, or an SR.

[0361] If Dropping Rule 1 is applied, the second OFDM symbol may be dropped. The second OFDM symbol may be an OFDM symbol for SRS. The second OFDM symbol may overlap with the first OFDM symbol. The first OFDM symbol may be an OFDM symbol for an uplink physical channel. The uplink physical channel may be a PUCCH.

[0362] In means 2, if dropping rule 2 is applied, the second OFDM symbol may be dropped. The second OFDM symbol may be an OFDM symbol for SRS. The second OFDM symbol may overlap with the first OFDM symbol. The first OFDM symbol may be an OFDM symbol for an uplink physical channel. The uplink physical channel may be a PUCCH.

[0363] In Means 2, when Dropping Rule 2 is applied and the SRS transmission symbols are not consecutive, it may be assumed that the SRS is not being transmitted. The SRS transmission symbols not being consecutive may mean that the phase continuity of the SRS transmission is not maintained. The SRS transmission symbols not being consecutive may mean that the SRS is not transmitted in two consecutive symbols. The assumption that the SRS is not being transmitted may mean that the SRS transmission is canceled. The assumption that the SRS is not being transmitted may mean that the SRS transmission is dropped. The assumption that the SRS is not being transmitted may mean that the SRS transmission is not expected.

[0364] In the means 2, when Dropping Rule 2 is applied, Dropping Rule 1 may be applied. When Dropping Rule 2 is applied and the first SRS (or the first SRS resource) is transmitted in the first OFDM symbol set, it may be assumed that the first SRS (or the first SRS resource) is not being transmitted. The first OFDM symbol set may include multiple OFDM symbols. The multiple OFDM symbols may not be consecutive to each other. The first OFDM symbol set may not include two consecutive OFDM symbols.

[0365] In the means 3, if Dropping Rule 2 is applied and the second symbol is within a certain period, the second symbol may be dropped. If Dropping Rule 2 is applied and the second symbol is after a certain period, the symbol group may be dropped. The second symbol may be a symbol for SRS. The symbol group may include the second symbol. The symbol group may include multiple OFDM symbols. If TDM-based mapping is configured, the symbol group may be multiple OFDM symbols. If non-TDM-based mapping is configured, the symbol group may be one OFDM symbol. For example, the symbol group may be S ap The symbol group may be OFDM symbols to which eight antenna ports are assigned (mapped). The symbol group may be OFDM symbols to which all antenna ports are assigned (mapped). The symbol group may be symbol subsets. The symbol group may be symbols to which a first subset and a second subset are assigned (mapped). The first subset may be pi = {1000, 1001, 1004, 1005}. The second subset may be pi = {1002, 1003, 1006, 1007}. A certain period is T proc,2 T proc,2 T may be the preparation time of the terminal device 1. proc,2 may be used in both normal CP and extended CP cases. After the end of reception of the last symbol of the PDCCH carrying DCI for scheduling the PUSCH, T proc,2 Later, the terminal device 1 may transmit the TB and the scheduled PUSCH.

[0366] In the means 3, if dropping rule 2 is applied and a first OFDM symbol overlaps with a second OFDM symbol, the symbol group may be dropped. For example, if dropping rule 2 is applied and a first OFDM symbol overlaps with a second OFDM symbol and the second OFDM symbol is within a certain period, the second OFDM symbol may be dropped. If dropping rule 2 is applied and a first OFDM symbol overlaps with a second OFDM symbol and the second OFDM symbol is not within the certain period, the symbol group may be dropped. The first OFDM symbol may be an OFDM symbol for an uplink physical channel. The second OFDM symbol may be an OFDM symbol for an SRS or an SRS resource. The uplink physical channel may be a PUCCH. The certain period may be a period from the last OFDM symbol of a PDCCH. The DCI in a PDCCH may schedule the uplink physical channel.

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

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

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

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

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

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

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

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

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

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

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

[0378] 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 900 SRS resource 910 Uplink physical channel 920, 921 OFDM symbol 930 CORESET 940 Fixed period

Claims

1. A terminal device comprising: a transmitter for transmitting an SRS and a PUSCH; and a receiver for receiving a PDCCH in which a DCI is placed; wherein the DCI indicates an SRS resource for the SRS; the DCI indicates transmission of the PUSCH; and, when a first codebook type is set for the PUSCH and TDM-based mapping is set for the SRS, dropping rule 1 is applied to the SRS; when a second codebook type is set for the PUSCH and TDM-based mapping is set for the SRS, dropping rule 1 is applied to the SRS; and, when non-TDM-based mapping is set for the SRS, dropping rule 1 is applied to the SRS.

2. The terminal device of claim 1, wherein the transmitting unit transmits an uplink physical channel, a first OFDM symbol for the uplink physical channel overlaps with a second OFDM symbol for the SRS, and when the dropping rule 1 is applied, the second OFDM symbol is dropped and when the OFDM symbols of the SRS transmission are not consecutive to each other, it is assumed that the SRS is not being transmitted.

Images