Terminal device, base station device, and communication method

Abstract

A terminal device is provided with: a reception unit that receives a PDCCH in which DCI that schedules a PUSCH is disposed; and a transmission unit that transmits the PUSCH, the transmission unit transmitting capability information of a terminal, the capability information of the terminal being information for defining support of an uplink codebook subset by a terminal device.

Description

Technical Field

[0001] The present invention relates to a terminal device, a base station device and a communication method. This application claims priority to Japanese Patent Application No. 2022-125991 filed in Japan on August 8, 2022, and the contents are incorporated herein by reference. Background Art

[0002] In the Third Generation Partnership Project (3GPP: rd In the LTE (Global Network Operations Framework) project, the Wireless Access Method and the Wireless Network (hereinafter also referred to as "Long Term Evolution (LTE)" or "Evolved Universal Terrestrial Radio Access (EUTRA)") of cellular mobile communications were studied. In LTE, the base station device is also called eNodeB (evolved NodeB), and the terminal device is also called UE (User Equipment). LTE is a cellular communication system that configures the area covered by multiple base station devices in a cell shape. A single base station device can manage multiple service cells.

[0003] In 3GPP, the next generation standard (NR: New Radio) was studied in order to make recommendations to IMT (International Mobile Telecommunication)-2020, which is the next generation mobile communication system standard established by the International Telecommunication Union (ITU) (Non-patent document 1). NR is required to meet the requirements of the following three scenarios in a single technical framework: eMBB (enhanced Mobile BroadBand), mMTC (massive Machine Type Communication), and URLLC (Ultra Reliable and Low Latency Communication).

[0004] In 3GPP, research is being conducted on the extension of services supported by NR (Non-Patent Document 2). Prior art literature Non-patent literature

[0005] Non-patent document 1: “New SID proposal: Study on New Radio Access Technology”, RP-160671, NTT docomo, 3GPP TSG RAN Meeting #71, Goteborg, Sweden, 7th-10th March, 2016. Non-Patent Document 2: “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 Non-patent document 3: “Release 18 package summary”, RP-213469, RAN chairman, RAN1 chairman, RAN2 chairman, RAN3 chairman, 3GPP TSG RAN Meeting#94-e, 6th-17th December, 2021 Summary of the invention Problem that the invention aims to solve

[0006] One aspect of the present invention provides a terminal device that efficiently communicates, a communication method used for the terminal device, a base station device that efficiently communicates, and a communication method used for the base station device. Technical Solution

[0007] (1) A first scheme of the present invention is a terminal device, comprising: a receiving unit, receiving a PDCCH configured with a DCI for scheduling a PUSCH; and a transmitting unit, transmitting the PUSCH, wherein the transmitting unit transmits capability information of the terminal, wherein the capability information of the terminal is capability information for defining support of an uplink codebook subset by the terminal device, and the capability information of the terminal includes at least information of partial coherence of two transmitting antenna ports and partial coherence of four transmitting antenna ports.

[0008] (2) Furthermore, the terminal device receives a first RRC parameter, and when capability information of the terminal indicates fully-coherent support and the first RRC parameter is set to any one of fullyAndPartialAndNonCoherent, fullyCoherent, partialAndNonCoherent, partialCoherent, 4portsPartialCoherent, 2portsPartialCoherent, and non-coherent, a precoding matrix for the PUSCH is determined from a codebook subset corresponding to fully coherent, four-port partial coherence (4ports-partial-coherent), two-port partial coherence (2ports-partial-coherent), and non-coherent, and when the capability information of the terminal indicates four-port partial coherence support and the first RRC parameter is set to partial In the case of any one of AndNonCoherent, partialCoherent, 4portsPartialCoherent, 2portsPartialCoherent and nonCoherent, the precoding matrix for the PUSCH is determined from the codebook subset corresponding to four-port partial coherence, two-port partial coherence and non-coherence; in the case where the capability information of the terminal indicates support for two-port partial coherence and the first RRC parameter is set to any one of partialAndNonCoherent, partialCoherent, 2portsPartialCoherent and nonCoherent, the precoding matrix for the PUSCH is determined from the codebook subset corresponding to two-port partial coherence and non-coherence; in the case where the capability information of the terminal indicates support for incoherence and the first RRC parameter is set to nonCoherent, the precoding matrix for the PUSCH is determined from the codebook subset corresponding to non-coherence.

[0009] (3) Furthermore, the first RRC parameter is determined based on at least part or all of the number of SRS ports and the antenna configuration of the terminal.

[0010] (4) Furthermore, the first RRC parameter is set to any one of fullyAndPartialAndNonCoherent, partialAndNonCoherent, nonCoherent, fullyCoherent, partialCoherent, 4portsPartialCoherent, and 2portsPartialCoherent.

[0011] (5) In addition, a second scheme of the present invention is a base station device, comprising: a receiving unit, which sends a PDCCH configured with a DCI for scheduling a PUSCH; and a receiving unit, which receives the PUSCH, wherein the receiving unit receives capability information of a terminal, wherein the capability information of the terminal is capability information used to define support for an uplink codebook subset by the terminal device, and the base station device grasps the capability information of the terminal, including at least information on partial coherence of two transmitting antenna ports and partial coherence of four transmitting antenna ports.

[0012] (6) Furthermore, the base station apparatus sends a first RRC parameter, and the base station apparatus grasps the following situations: when the capability information of the terminal indicates support for full coherence and the first RRC parameter is set to any one of fullyAndPartialAndNonCoherent, fullyCoherent, partialAndNonCoherent, partialCoherent, 4portsPartialCoherent, 2portsPartialCoherent, and nonCoherent, a precoding matrix for the PUSCH is determined from a codebook subset corresponding to full coherence, four-port partial coherence, two-port partial coherence, and noncoherence; when the capability information of the terminal indicates support for four-port partial coherence and the first RRC parameter is set to any one of partialAndNonCoherent, partialCoherent, 4portsPartialCoherent, 2portsPartialCoherent, and nonCoherent. ortsPartialCoherent, 2portsPartialCoherent and nonCoherent, the precoding matrix for the PUSCH is determined from the codebook subset corresponding to the four-port partial coherence, the two-port partial coherence and the non-coherence; when the capability information of the terminal indicates support for two-port partial coherence and the first RRC parameter is set to any one of partialAndNonCoherent, partialCoherent, 2portsPartialCoherent and nonCoherent, the precoding matrix for the PUSCH is determined from the codebook subset corresponding to the two-port partial coherence and the non-coherence; when the capability information of the terminal indicates support for non-coherence and the first RRC parameter is set to nonCoherent, the precoding matrix for the PUSCH is determined from the codebook subset corresponding to the non-coherence.

[0013] (7) Furthermore, the first RRC parameter is determined based on at least part or all of the number of SRS ports and the antenna configuration of the terminal.

[0014] (8) Furthermore, the first RRC parameter is set to any one of fullyAndPartialAndNonCoherent, partialAndNonCoherent, nonCoherent, fullyCoherent, partialCoherent, 4portsPartialCoherent, and 2portsPartialCoherent.

[0015] (9) In addition, a third scheme of the present invention is a communication method for a terminal device, the communication method comprising the following steps: receiving a PDCCH configured with a DCI for scheduling a PUSCH; and sending the PUSCH, sending capability information of the terminal, the capability information of the terminal is capability information for defining support of an uplink codebook subset by the terminal device, the capability information of the terminal includes at least information about partial coherence of two transmit antenna ports and partial coherence of four transmit antenna ports. Beneficial Effects

[0016] According to one aspect of the present invention, a terminal device can efficiently communicate. In addition, a base station device can efficiently communicate. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 This is a conceptual diagram of a wireless communication system according to one aspect of the present embodiment. Figure 2 is a subcarrier spacing setting μ, the number of OFDM symbols per time slot N, and 时隙 码元 And an example of the relationship between CP (cyclic prefix) settings. Figure 3 This is a diagram showing an example of a resource grid configuration method according to one aspect of the present embodiment. Figure 4 This is a diagram showing a configuration example of a resource grid 3001 according to one aspect of the present embodiment. Figure 5 It is a schematic block diagram showing a configuration example of the base station device 3 according to one aspect of the present embodiment. Figure 6 It is a schematic block diagram showing a configuration example of the terminal device 1 according to one aspect of the present embodiment. Figure 7 This is a diagram showing an example configuration of an SS / PBCH block according to one scenario of the present embodiment. Figure 8 This is a diagram showing an example of monitoring opportunities of a search area set according to one scenario of the present embodiment. Fig. 9 This is a diagram showing an example of a method of applying a precoding matrix according to one scheme of the present embodiment. DETAILED DESCRIPTION

[0018] Hereinafter, embodiments of the present invention will be described.

[0019] floor(C) may be a floor function for a real number C. For example, floor(C) may be a function that outputs the largest integer within a range not exceeding the real number C. ceil(D) may be a ceiling function for a real number D. For example, ceil(D) may be a function that outputs the smallest integer within a range not less than D. mod(E,F) may be a function that outputs the remainder obtained by dividing E by F. mod(E,F) may also be a function that outputs a value corresponding to the remainder obtained by dividing E by F. exp(G) = e^G. Here, e is the Napier number. H^I represents H raised to the power of I. max(J,K) is a function that outputs the maximum value between J and K. When J and K are equal, max(J,K) is a function that outputs J or K. min(L,M) is a function that outputs the maximum value between L and M. When L and M are equal, min(L,M) is a function that outputs L or M. round(N) is a function that outputs the integer value closest to N. "·" indicates multiplication.

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

[0021] The OFDM symbol may be a name including the CP added to the OFDM symbol. That is, a certain OFDM symbol may be composed of the certain OFDM symbol and the CP added to the certain OFDM symbol.

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

[0023] The base station device 3 may be configured to include one or more transmission devices (or transmission points, transceiver devices, or transceiver points). When the base station device 3 is configured to include multiple transmission devices, the multiple transmission devices may be respectively arranged at different positions.

[0024] The base station device 3 may provide one or more serving cells. A serving cell may be defined as a collection of resources used for wireless communication. In addition, a serving cell is also referred to as a cell.

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

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

[0027] The resource grid includes N 尺寸，μ 网格，x N RB sc subcarriers. The resource grid is composed of a common resource block N 开始，μ 网格,x In addition, the public resource block N 开始，μ 网格,x Also known as the reference point of the resource grid.

[0028] The resource grid includes N 子帧，μ 码元 OFDM symbols.

[0029] The subscript x added in the parameters associated with the resource grid indicates the transmission direction. For example, the subscript x can be used to indicate either downlink or uplink.

[0030] N 尺寸,μ 网格,x The offset setting is indicated by the parameter provided by the RRC layer (for example, the parameter CarrierBandwidth). 开始,μ 网格,x The frequency band setting is indicated by a parameter (e.g., parameter OffsetToCarrier) provided by the RRC layer. The offset setting and the frequency band setting are settings for configuring an SCS-specific carrier.

[0031] For a certain subcarrier spacing setting μ, the subcarrier spacing (SCS: SubCarrier Spacing) Δf can be Δf=2 μ ·15kHz. The subcarrier spacing setting μ can represent any one of 0, 1, 2, 3 or 4.

[0032] Figure 2 is a setting μ of the subcarrier spacing and the number N of OFDM symbols per time slot according to one embodiment of the present invention. 时隙 码元 And an example of the relationship between CP (cyclic prefix) settings. Figure 2 In A, for example, when the subcarrier spacing μ is set to 2 and the CP is set to a normal cyclic prefix (CP), N 时隙 码元 =14, N 帧，μ 时隙 =40, N 子帧，μ 时隙 =4. In addition, Figure 2 In B, for example, when the subcarrier spacing μ is set to 2 and the CP is set to an extended CP (extended cyclic prefix), N 时隙 码元 =12, N 帧，μ 时隙 =40, N 子帧，μ 时隙 =4.

[0033] Time unit (time unit) T c Can be used to indicate the length of the time domain. Time unit T c It is T c =1 / (Δf max ·N f ). Δf max =480kHz. f =4096. The constant κ is κ = Δf max·N f / (Δf ref N f，ref )=64. Δf ref is 15kHz. f，ref It is 2048.

[0034] The transmission of the signal in the downlink and / or the transmission of the signal in the uplink may be performed by a transmission of length T f The wireless frames (system frames, frames) are organized into (organized into). f =(Δf max N f / 100)·T s = 10ms. The radio frame consists of 10 subframes. The length of the subframe is T sf =(Δf max N f / 1000)·T s =1ms. The number of OFDM symbols in each subframe is N 子帧，μ 码元 =N 时隙 码元 N 子帧，μ 时隙 .

[0035] An OFDM symbol is a unit of time domain of a communication method. For example, an OFDM symbol can be a unit of time domain of CP-OFDM. In addition, an OFDM symbol can be a unit of time domain of DFT-s-OFDM.

[0036] A time slot can be constructed to include multiple OFDM symbols. For example, a time slot can be composed of N consecutive OFDM symbols. 时隙 码元 OFDM symbols. For example, in the conventional CP setting, it can be N 时隙 码元 =14. In addition, in the extended CP setting, N 时隙 码元 =12.

[0037] The number and index of the time slots included in the subframe can be given for setting μ for a certain subcarrier spacing. For example, the time slot index n μ s It can be in the range of 0 to N in the subframe 子帧，μ 时隙 -1 in ascending order. The number and index of the time slots included in the radio frame can also be given for setting the subcarrier spacing μ. In addition, the time slot index n μ s，f It can also be in the wireless frame from 0 to N 帧，μ 时隙Integer values ​​in the range -1 are given in ascending order.

[0038] Figure 3 This is a diagram showing an example of a method of configuring a resource grid according to one aspect of the present embodiment. Figure 3 The horizontal axis represents the frequency domain. Figure 3 , an example of a resource grid configuration of a subcarrier spacing μ1 in component carrier 300 and an example of a resource grid configuration of a subcarrier spacing μ2 in a certain component carrier are shown. In this way, one or more subcarrier spacings can be set for a certain component carrier. Figure 3 In the example, it is assumed that μ1=μ2-1, but the various aspects of the present embodiment are not limited to the condition of μ1=μ2-1.

[0039] Component carrier 300 is a frequency band having a predetermined width in the frequency domain.

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

[0041] The common resource block set 3100 includes the common resource blocks of point 3000 ( Figure 3 The black monochrome block in the common resource block set 3100 in FIG. 3 is also referred to as a reference point of the common resource block set 3100 . The reference point of the common resource block set 3100 may also be a common resource block of index 0 in the common resource block set 3100 .

[0042] Offset 3011 is the offset from the reference point of common resource block set 3100 to the reference point of resource grid 3001. Offset 3011 is represented by the number of common resource blocks for the setting μ1 of subcarrier spacing. Resource grid 3001 includes N starting from the reference point of resource grid 3001. 尺寸，μ 网格1，x A common resource block.

[0043] The offset 3013 is the distance from the reference point of the resource grid 3001 to the reference point (N) of the BWP (BandWidth Part) 3003 of the index i1. 开始，μ BWP，i1 ) offset.

[0044] The common resource block set 3200 is a set of common resource blocks for the subcarrier spacing setting μ2.

[0045] The common resource block set 3200 includes the common resource blocks of point 3000 ( Figure 3The black monochrome 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 also be the common resource block of index 0 in the common resource block set 3200.

[0046] Offset 3012 is an offset from a reference point of common resource block set 3200 to a reference point of resource grid 3002. Offset 3012 is represented by the number of common resource blocks for subcarrier spacing μ2. Resource grid 3002 includes N 尺寸，μ 网格2，x A common resource block.

[0047] 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 开始，μ BWP，i2 ) offset.

[0048] Figure 4 FIG. 3 is a diagram showing an example of the configuration of a resource grid 3001 according to one embodiment of the present invention. Figure 4 In the resource grid, the horizontal axis is the OFDM symbol index l sym , the vertical axis is the subcarrier index k sc The resource grid 3001 includes N 尺寸，μ 网格1，x N RB sc subcarriers, including N 子帧，μ 码元 OFDM symbols. Within the resource grid, subcarrier index k sc and OFDM symbol index l sym The identified resource is also called a resource element (RE: Resource Element).

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

[0050] The resource block unit is a set of resources corresponding to one OFDM symbol in one resource block. That is, one resource block unit includes 12 resource elements corresponding to one OFDM symbol in one resource block.

[0051] The common resource blocks for a certain subcarrier spacing setting μ are indexed in ascending order starting from 0 in the frequency domain in a certain common resource block set. The common resource blocks with index 0 for a certain subcarrier spacing setting μ include (or contend for, or agree on) point 3000. The index n of the common resource blocks for a certain subcarrier spacing setting μ is μ CRB Satisfy n μ CRB =ceil(k sc / N RB sc ). Here, k sc The subcarrier with =0 is a subcarrier having the same center frequency as the center frequency of the subcarrier corresponding to point 3000.

[0052] The physical resource blocks for a certain subcarrier spacing setting μ are indexed in ascending order starting from 0 in the frequency domain in a certain BWP. The index n of the physical resource block for a certain subcarrier spacing setting μ is μ PRB Satisfy n μ CRB =n μ PRB +N 开始，μ BWP，i Here, N 开始，μ BWP，i Represents the reference point of the BWP with index i.

[0053] BWP is defined as a subset of common resource blocks included in the resource grid. BWP includes a reference point N from the BWP. 开始，μ BWP，i Starting N 尺寸，μ BWP，i Common resource blocks. The BWP set for a downlink carrier is also called a downlink BWP. The BWP set for an uplink component carrier is also called an uplink BWP.

[0054] An antenna port is 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. In addition, a symbol may correspond to an OFDM symbol. In addition, a symbol may correspond to a resource block unit. In addition, a symbol may correspond to a resource element.

[0055] The large-scale property of the channel that transmits the codeword in one antenna port can be estimated based on the channel that transmits the codeword in another antenna port, which is called the two antenna ports are QCL (Quasi Co-Located). Among them, the large-scale property may include at least the long-range property of the channel. The large-scale property may also include at least a part or all of delay spread, Doppler spread, Doppler shift, average gain, average delay and beam parameters (spatial Rx parameters). The beam parameters of the first antenna port and the second antenna port are QCL, which may be that the receiving beam assumed by the receiving side for the first antenna port and the receiving beam assumed by the receiving side for the second antenna port are the same (or corresponding). The beam parameters of the first antenna port and the second antenna port are QCL, which may be that the transmitting beam assumed by the receiving side for the first antenna port and the transmitting beam assumed by the receiving side for the second antenna port are the same (or corresponding). Terminal device 1 may assume that two antenna ports are QCL when the large-scale characteristics of the channel through which symbols are transmitted in one antenna port can be estimated from the channel through which symbols are transmitted in another antenna port. Two antenna ports being QCL may also mean assuming that two antenna ports are QCL.

[0056] Carrier aggregation may be the use of multiple aggregated service cells for communication. In addition, carrier aggregation may also be the use of multiple aggregated component carriers for communication. In addition, carrier aggregation may also be the use of multiple aggregated downlink component carriers for communication. In addition, carrier aggregation may also be the use of multiple aggregated uplink component carriers for communication.

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

[0058] The wireless transceiver unit 30 includes at least a part or all of the wireless transmission unit 30a and the wireless reception unit 30b. Here, the device configuration of the baseband unit included in the wireless transmission unit 30a and the baseband unit included in the wireless reception unit 30b may be the same or different. In addition, the device configuration of the RF unit included in the wireless transmission unit 30a and the RF unit included in the wireless reception unit 30b may be the same or different. In addition, the device configuration of the antenna unit included in the wireless transmission unit 30a and the antenna unit included in the wireless reception unit 30b may be the same or different.

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

[0060] For example, the wireless receiving unit 30b may receive PRACH. For example, the wireless receiving unit 30b may also receive and demodulate PUCCH. The wireless receiving unit 30b may also receive and demodulate PUSCH. For example, the wireless receiving unit 30b may also receive PUCCH DMRS. For example, the wireless receiving unit 30b may also receive PUSCH DMRS. For example, the wireless receiving unit 30b may also receive ULPTRS. For example, the wireless receiving unit 30b may also receive SRS.

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

[0062] The media access control layer processing unit 35 included in the upper layer processing unit 34 performs processing at the MAC layer.

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

[0064] The wireless transceiver 30 (or the wireless transmission unit 30a) performs modulation, coding and other processing. The wireless transceiver 30 (or the wireless transmission unit 30a) generates a physical signal by modulating, coding and generating a baseband signal (converting into a time-continuous signal) the downlink data, and transmits it to the terminal device 1. The wireless transceiver 30 (or the wireless transmission unit 30a) can configure the physical signal to a component carrier and transmit it to the terminal device 1.

[0065] The wireless transceiver 30 (or wireless receiving unit 30b) performs demodulation, decoding and other processing. The wireless transceiver 30 (or wireless receiving unit 30b) separates, demodulates and decodes the received physical signal, and outputs the decoded information to the upper layer processing unit 34. The wireless transceiver 30 (or wireless receiving unit 30b) can implement a channel access process before sending the physical signal.

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

[0067] 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 the CP (Cyclic Prefix) from the converted digital signal, performs a fast Fourier transform (FFT) on the signal after the CP is removed, and extracts a signal in the frequency domain.

[0068] 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 to generate a baseband digital signal, and converts the baseband digital signal into an analog signal. The baseband unit 33 outputs the converted analog signal to the RF unit 32.

[0069] The RF unit 32 uses a low-pass filter to remove unnecessary frequency components from the analog signal input from the baseband unit 33, up-converts the analog signal to a carrier frequency, and transmits it via the antenna unit 31. In addition, the RF unit 32 may also have a function of controlling the transmission power. The RF unit 32 is also called a transmission power control unit.

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

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

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

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

[0074] The SCell may be included in either the MCG or the SCG.

[0075] A serving cell group (cell group) is a name 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 used through carrier aggregation.

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

[0077] One of the one or more downlink BWPs set for the serving cell (or downlink component carrier) may be set as an activated downlink BWP (or one downlink BWP may be activated). One of the one or more uplink BWPs set for the serving cell (or uplink component carrier) may be set as an activated uplink BWP (or one uplink BWP may be activated).

[0078] PDSCH, PDCCH and CSI-RS can be received in the activated downlink BWP. Terminal device 1 can attempt to receive PDSCH, PDCCH and CSI-RS in the activated downlink BWP. PUCCH and PUSCH can be sent in the activated uplink BWP. Terminal device 1 can send PUCCH and PUSCH in the activated uplink BWP. The activated downlink BWP and the activated uplink BWP are collectively referred to as the activated BWP.

[0079] PDSCH, PDCCH and CSI-RS may not be received in a downlink BWP other than the activated downlink BWP (inactivated downlink BWP). Terminal device 1 may not attempt to receive PDSCH, PDCCH and CSI-RS in a downlink BWP that is not an activated downlink BWP. PUCCH and PUSCH may not be sent in an uplink BWP that is not an activated uplink BWP (inactivated uplink BWP). Terminal device 1 may not send PUCCH and PUSCH in an uplink BWP that is not an activated uplink BWP. Inactivated downlink BWP and inactivated uplink BWP are collectively referred to as inactivated BWP.

[0080] Downlink BWP switching is a process for deactivating an activated downlink BWP of a certain serving cell and activating any one of the inactivated downlink BWPs of the certain serving cell. Downlink BWP switching can be controlled by the BWP field included in the downlink control information. Downlink BWP switching can also be controlled based on upper layer parameters.

[0081] The uplink BWP switching is used to deactivate an activated uplink BWP and activate any of the inactivated uplink BWPs that are not the activated uplink BWP. The uplink BWP switching can be controlled by the BWP field included in the downlink control information. The uplink BWP switching can also be controlled based on the parameters of the upper layer.

[0082] Two or more downlink BWPs among one or more downlink BWPs set for the serving cell may not be set as the activated downlink BWPs. Alternatively, one downlink BWP may be activated for the serving cell at a certain time.

[0083] Two or more uplink BWPs among one or more uplink BWPs configured for the serving cell may not be configured as activated uplink BWPs. One uplink BWP may be activated for the serving cell at a certain time.

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

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

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

[0087] For example, the wireless receiving unit 10b may receive and demodulate the PDSCH. For example, the wireless receiving unit 10b may receive and demodulate the PDCCH. For example, the wireless receiving unit 10b may receive and demodulate the 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 DLPTRS.

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

[0089] The media access control layer processing unit 15 included in the upper layer processing unit 14 performs processing at the MAC layer.

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

[0091] The wireless transceiver 10 (or the wireless transmission unit 10a) performs modulation, coding and other processing. The wireless transceiver 10 (or the wireless transmission unit 10a) generates a physical signal by modulating, coding and generating a baseband signal (converting to a time-continuous signal) the uplink data, and transmits it to the base station device 3. The wireless transceiver 10 (or the wireless transmission unit 10a) can configure the physical signal to a certain BWP (activate the uplink BWP) and transmit it to the base station device 3.

[0092] The wireless transceiver 10 (or wireless receiving unit 10b) performs demodulation, decoding and other processing. The wireless transceiver 10 (or wireless receiving unit 30b) can receive a physical signal in a certain BWP (activated downlink BWP) of a certain serving cell. The wireless transceiver 10 (or wireless receiving unit 10b) separates, demodulates and decodes the received physical signal, and outputs the decoded information to the upper layer processing unit 14. The wireless transceiver 10 (wireless receiving unit 10b) can implement a channel access process before sending a physical signal.

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

[0094] 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 CP (Cyclic Prefix) from the converted digital signal, performs Fast Fourier Transform (FFT) on the signal after CP removal, and extracts a signal in the frequency domain.

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

[0096] The RF unit 12 uses a low-pass filter to remove unnecessary frequency components from the analog signal input from the baseband unit 13, up-converts the analog signal into a carrier frequency, and transmits it via the antenna unit 11. In addition, the RF unit 12 may also have a function of controlling the transmission power. The RF unit 12 is also called a transmission power control unit.

[0097] The following describes the physical signal (signal).

[0098] Physical signal is the general term for downlink physical channel, downlink physical signaling, uplink physical channel and uplink physical channel. Physical channel is the general term for downlink physical channel and uplink physical channel. Physical signaling is the general term for downlink physical signaling and uplink physical signaling.

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

[0100] PUCCH can be used to send uplink control information (UCI). PUCCH can be sent to deliver, transmit, convey uplink control information. Uplink control information can be mapped to PUCCH. Terminal device 1 can send PUCCH configured with uplink control information. Base station device 3 can receive PUCCH configured with uplink control information.

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

[0102] Channel state information is also called channel state information bit or channel state information sequence. Scheduling request is also called scheduling request bit or scheduling request sequence. HARQ-ACK information is also called HARQ-ACK information bit or HARQ-ACK information sequence.

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

[0104] A transport block is an information bit sequence delivered from an upper layer. The information bit sequence is also called a bit sequence. The transport block can be distributed via the UL-SCH (UpLink-Shared CHannel) of the transport layer.

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

[0106] HARQ-ACK may also represent ACK or NACK corresponding to a CBG (Code Block Group) included in a transport block.

[0107] The scheduling request can be used at least to request UL-SCH resources for initial transmission (new transmission). The scheduling request bit can be used to indicate either a positive SR (positive SR) or a negative SR (negative SR). The scheduling request bit indicating a positive SR is also referred to as "transmitting a positive SR". A positive SR can indicate that the terminal device 1 requests UL-SCH resources for initial transmission. A positive SR can also indicate that the scheduling request is triggered by an upper layer. A positive SR can be transmitted when the upper layer indicates that a scheduling request is sent. The scheduling request bit indicating a negative SR is also referred to as "transmitting a negative SR". A negative SR can indicate that the terminal device 1 does not request UL-SCH resources for initial transmission. A negative SR can also indicate that the scheduling request is not triggered by an upper layer. A negative SR can be transmitted when the upper layer does not indicate that a scheduling request is sent.

[0108] The channel state information may include at least a part or all of a channel quality indicator (CQI: Channel Quality Indicator), a precoding matrix indicator (PMI: Precoder Matrix Indicator) and a rank indicator (RI: Rank Indicator). CQI is an indicator associated with the quality of a transmission path (e.g., transmission strength) or the quality of a physical channel, and PMI is an indicator associated with precoding. RI is an indicator associated with a transmission rank (or number of transmission layers).

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

[0110] PUCCH may correspond to a PUCCH format. PUCCH may be a set of resource elements used to transmit a PUCCH format. PUCCH may include a PUCCH format. PUCCH may be sent in a certain PUCCH format. It should be noted that a PUCCH format may be interpreted as an information format. In addition, a PUCCH format may also be interpreted as an information set set in a certain information format.

[0111] PUSCH can also be used to transmit one or both of transport blocks and uplink control information. Transport blocks can be configured on PUSCH. Transport blocks distributed by UL-SCH can be configured on PUSCH. Uplink control information can be configured on PUSCH. Terminal device 1 can send PUSCH configured with one or both of transport blocks and uplink control information. Base station device 3 can receive PUSCH configured with one or both of transport blocks and uplink control information.

[0112] PRACH can also be sent to deliver a random access preamble. Terminal device 1 can send PRACH. Base station device 3 can receive PRACH. PRACH sequence x u，v (n) by x u，v (n) = x u (mod(n+C v , L RA )) is defined. Among them, x u is a ZC (Zadoff Chu) sequence. In addition, x u You can use x u =exp(-jπui(i+1) / L RA ). j is an imaginary unit. In addition, π is the circumference of a circle. In addition, C vcorresponds to the cyclic shift of the PRACH sequence. RA Corresponds to the length of the PRACH sequence. In addition, L RA is 839 or 139. In addition, i is 0 to L RA An integer in the range -1. In addition, u is a sequence index for a PRACH sequence.

[0113] 64 random access preambles are defined for each PRACH opportunity. The random access preamble is based on the cyclic shift C of the PRACH sequence. v and the sequence index u used for the PRACH sequence. An index may be added to each of the determined 64 random access preambles.

[0114] An uplink physical signal may correspond to a set of resource elements. An uplink physical signal may not be used to transmit information generated in an upper layer. It should be noted that an uplink physical signal may also be used to transmit information generated in a physical layer. An uplink physical signal may be a physical signal used in an uplink component carrier. The terminal device 1 may send an uplink physical signal. The base station device 3 may receive an uplink physical signal. In a wireless communication system of one embodiment of the present invention, 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)

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

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

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

[0118] The propagation path of the PUSCH can be estimated based on the DMRS used for the PUSCH.

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

[0120] The transmission of the PUCCH and the transmission of the DMRS for the PUCCH may be indicated (or triggered) by a 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 in a PUCCH format. The PUCCH and the DMRS for the PUCCH may be collectively referred to as the PUCCH. Transmitting the PUCCH may also be transmitting the PUCCH and the DMRS for the PUCCH.

[0121] The propagation path of the PUCCH can be estimated based on the DMRS used for the PUCCH.

[0122] A downlink physical channel may correspond to a set of resource elements that transmit information generated in an upper layer. A downlink physical channel may be a physical channel used in a downlink component carrier. The base station device 3 may transmit a downlink physical channel. The terminal device 1 may receive a downlink physical channel. In a wireless communication system of one embodiment of the present invention, 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)

[0123] PBCH can be sent to transmit one or both of MIB (Master Information Block) and physical layer control information. Here, physical layer control information is information generated in the physical layer. MIB is a set of parameters configured in BCCH (Broadcast Control CHannel), which is a logical channel of the MAC layer. The BCCH is configured in BCH, which is a channel of the transport layer. BCH can be configured (mapped) to PBCH. Terminal device 1 can receive PBCH configured with one or both of MIB and physical layer control information. Base station device 3 can send PBCH configured with one or both of MIB and physical layer control information.

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

[0125] The radio frame bit is used to indicate the radio frame in which the PBCH is sent (including the radio frame of the time slot in which the PBCH is sent). The radio frame bit includes 4 bits. The radio frame bit can be composed of 4 bits in the 10-bit radio frame indicator. For example, the radio frame indicator can be used to determine at least the radio frames of index 0 to index 1023.

[0126] The half radio frame bit is used to indicate in which of the first half of the 5 subframes or the second half of the 5 subframes in the radio frame in which the PBCH is transmitted, the PBCH is transmitted. Here, the half radio frame may be configured to include 5 subframes. In addition, the half radio frame may be configured to include the first half of the 5 subframes of the 10 subframes included in the radio frame. In addition, the half radio frame may also be configured to include the second half of the 5 subframes of the 10 subframes included in the radio frame.

[0127] The SS / PBCH block index bit is used to indicate the SS / PBCH block index. The SS / PBCH block index bit includes 3 bits. The SS / PBCH block index bit may also be composed of 3 bits in the 6-bit SS / PBCH block index indicator. The SS / PBCH block index indicator may be used to determine at least SS / PBCH blocks of index 0 to index 63.

[0128] The subcarrier offset bit is used to indicate the subcarrier offset. The subcarrier offset can also be used to indicate the difference between the subcarrier at the start point of mapping the PBCH and the subcarrier at the start point of the control resource set with mapping index 0.

[0129] The PDCCH may be transmitted to transmit downlink control information (DCI: Downlink Control Information). The downlink control information may be configured (mapped) on the PDCCH. The terminal device 1 may receive the PDCCH configured with the downlink control information. The base station device 3 may transmit the PDCCH configured with the downlink control information.

[0130] The downlink control information may be sent with a DCI format. It should be noted that the DCI format may be interpreted as the format of the downlink control information. In addition, the DCI format may also be interpreted as a set of downlink control information set in a certain format of downlink control information.

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

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

[0133] The DCI format specific field may indicate whether the DCI format including the DCI format specific field is an uplink DCI format or a downlink DCI format. That is, the DCI format specific field may be included in each uplink DCI format and downlink DCI format. Among them, the DCI format specific field included in DCI format 0_0 may represent 0.

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

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

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

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

[0138] DCI format 0_0 may not include a field for CSI request (CSI request).

[0139] DCI format 0_0 may also not include a carrier indicator field. That is, the service cell to which the uplink component carrier configured with the PUSCH scheduled by DCI format 0_0 belongs may be the same as the service cell to which the uplink component carrier configured with the PDCCH including the DCI format 0_0 belongs. The terminal device 1 may recognize that the PUSCH scheduled by the DCI format 0_0 is configured on the uplink component carrier of a certain service cell based on the detection of DCI format 0_0 in a certain downlink component carrier of the certain service cell.

[0140] DCI format 0_0 may not include a BWP field. DCI format 0_0 may be a DCI format for scheduling PUSCH without changing the activated uplink BWP. Terminal device 1 may recognize that the PUSCH is sent without switching the activated uplink BWP based on detecting DCI format 0_0 for PUSCH scheduling.

[0141] DCI format 0_1 ​​is used to configure at least PUSCH scheduling in a certain cell. DCI format 0_1 ​​is configured to include at least a part or all of the fields 2A to 2H. 2A) DCI format specific fields 2B) Frequency Domain Resource Allocation Field 2C) Time domain resource allocation field for uplink 2D) Frequency Hopping Flag Field 2E) MCS field 2F) CSI request field 2G)BWP field 2H) Carrier indicator field

[0142] The DCI format specific field included in DCI format 0_1 ​​may represent 0.

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

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

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

[0146] The BWP field of DCI format 0_1 ​​can be used to indicate the uplink BWP configured with the PUSCH scheduled by the DCI format 0_1. That is, DCI format 0_1 ​​can change according to the activation of the uplink BWP. The terminal device 1 can identify the uplink BWP configured with the PUSCH based on the detection of DCI format 0_1 ​​for PUSCH scheduling.

[0147] DCI format 0_1 ​​not including the BWP field may be a DCI format for scheduling PUSCH without changing the activated uplink BWP. Terminal device 1 is DCI format 0_1 ​​for PUSCH scheduling, and can recognize that the PUSCH is sent without switching the activated uplink BWP based on detecting DCI format D0_1 not including the BWP field.

[0148] The BWP field is included in DCI format 0_1, but when terminal device 1 does not support the function of switching BWP through DCI format 0_1, terminal device 1 can ignore the BWP field. That is, terminal device 1 that does not support the BWP switching function is DCI format 0_1 ​​for PUSCH scheduling, and can identify that the PUSCH is sent without switching to activate the uplink BWP based on the detection of DCI format 0_1 ​​including the BWP field. Among them, when terminal device 1 supports the BWP switching function, in the function information reporting process of the RRC layer, it can be reported that "terminal device 1 supports the BWP switching function".

[0149] The CSI request field is used to indicate a CSI report.

[0150] Alternatively, in the case where the carrier indicator field is included in the DCI format 0_1, the carrier indicator field is used to indicate the uplink component carrier configured with the PUSCH. Alternatively, in the case where the carrier indicator field is not included in the DCI format 0_1, the uplink component carrier configured with the PUSCH is the same as the uplink component carrier configured with the PDCCH including the DCI format 0_1 ​​for scheduling the PUSCH. Alternatively, in the case where the number of uplink component carriers set for the terminal device 1 in a certain service cell group is 2 or more (in the case where uplink carrier aggregation is used in a certain service cell group), the number of bits of the carrier indicator field included in the DCI format 0_1 ​​for scheduling the PUSCH configured for the certain service cell group is 1 bit or more (for example, 3 bits). It may also be that, when the number of uplink component carriers set for terminal device 1 in a certain service cell group is 1 (when uplink carrier aggregation is not used in a certain service cell group), the number of bits of the carrier indicator field included in the DCI format 0_1 ​​used for scheduling of PUSCH configured for the certain service cell group is 0 bits (or the carrier indicator field is not included in the DCI format 0_1 ​​used for scheduling of PUSCH configured for the certain service cell group).

[0151] DCI format 1_0 is used to configure at least PDSCH scheduling in a certain cell. DCI format 1_0 is configured to include at least a part or all of 3A to 3F. 3A) DCI format specific fields 3B) Frequency Domain Resource Allocation Field 3C) Time Domain Resource Allocation Field 3D)MCS field 3E)PDSCH_HARQ feedback timing indicator field (PDSCH to HARQ feedback timing indicator field) 3F)PUCCH resource indicator field

[0152] The DCI format specific field included in DCI format 1_0 may represent 1.

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

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

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

[0156] The PDSCH_HARQ Feedback Timing Indication field may be used to indicate an offset from a slot including a last OFDM symbol of a PDSCH to a slot including an OFDM symbol of a start point of a PUCCH.

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

[0158] DCI format 1_0 may not include a carrier indicator field. That is, a downlink component carrier configured with a PDSCH scheduled by DCI format 1_0 may be the same as a downlink component carrier configured with a PDCCH including the DCI format 1_0. The terminal device 1 may recognize that the PDSCH scheduled by the DCI format 1_0 is configured on a downlink component carrier based on the detection of DCI format 1_0 in the downlink component carrier.

[0159] DCI format 1_0 may not include a BWP field. DCI format 1_0 may be a DCI format for scheduling PDSCH without changing the activated downlink BWP. The terminal device 1 may recognize that the PDSCH is received without switching the activated downlink BWP based on the detection of DCI format 1_0 for PDSCH scheduling.

[0160] DCI format 1_1 is used to configure at least PDSCH scheduling in a certain cell. DCI format 1_1 may be configured to include at least a part or all of 4A to 4I. 4A) DCI format specific fields 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 indicator field 4H) BWP field 4I) Carrier Indicator Field

[0161] The DCI format specific field included in DCI format 1_1 may represent 1.

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

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

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

[0165] Alternatively, when the PDSCH_HARQ feedback timing indication field is included in the DCI format 1_1, the PDSCH_HARQ feedback timing indication field is used to at least indicate an offset from a time slot including the last OFDM symbol of the PDSCH to a time slot including an OFDM symbol of the starting point of the PUCCH. Alternatively, when the PDSCH_HARQ feedback timing indication field is not included in the DCI format 1_1, the offset from a time slot including the last OFDM symbol of the PDSCH to a time slot including an OFDM symbol of the starting point of the PUCCH is determined by an upper layer parameter.

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

[0167] The BWP field of DCI format 1_1 can be used to indicate the downlink BWP configured with the PDSCH scheduled by the DCI format 1_1. That is, DCI format 1_1 can change according to the activation of the downlink BWP. The terminal device 1 can identify the downlink BWP configured with the PUSCH based on the detection of DCI format 1_1 for PDSCH scheduling.

[0168] The DCI format 1_1 not including the BWP field may be a DCI format for scheduling the PDSCH without changing the activated downlink BWP. The terminal device 1 is a DCI format 1_1 for PDSCH scheduling, and can recognize that the PDSCH is received without switching the activated downlink BWP based on the detection of the DCI format 1_1 not including the BWP field.

[0169] The DCI format 1_1 includes a BWP field, but when the terminal device 1 does not support the function of switching the BWP through the DCI format 1_1, the terminal device 1 can ignore the BWP field. That is, the terminal device 1 that does not support the BWP switching function is the DCI format 1_1 used for PDSCH scheduling, and can recognize that the PDSCH is received without switching the activated downlink BWP based on the detection of the DCI format 1_1 including the BWP field. Among them, when the terminal device 1 supports the BWP switching function, in the function information reporting process of the RRC layer, it can be reported that "the terminal device 1 supports the BWP switching function".

[0170] Alternatively, when the carrier indicator field is included in the DCI format 1_1, the carrier indicator field is used to indicate the downlink component carrier configured with the PDSCH. Alternatively, when the carrier indicator field is not included in the DCI format 1_1, the downlink component carrier configured with the PDSCH is the same as the downlink component carrier configured with the PDCCH including the DCI format 1_1 for scheduling the PDSCH. Alternatively, when the number of downlink component carriers set for the terminal device 1 in a certain service cell group is 2 or more (when downlink carrier aggregation is used in a certain service cell group), the number of bits of the carrier indicator field included in the DCI format 1_1 for scheduling the PDSCH configured for the certain service cell group is 1 bit or more (for example, 3 bits). Alternatively, when the number of downlink component carriers set for the terminal device 1 in a certain service cell group is 1 (when downlink carrier aggregation is not used in a certain service cell group), the number of bits of the carrier indicator field included in the DCI format 1_1 used for scheduling of the PDSCH configured for the certain service cell group is 0 bits (or, the carrier indicator field is not included in the DCI format 1_1 used for scheduling of the PDSCH configured for the certain service cell group).

[0171] PDSCH can be sent to deliver transport blocks. PDSCH can also be used to send transport blocks distributed by DL-SCH. PDSCH can be used to deliver transport blocks. Transport blocks can be configured on PDSCH. Transport blocks corresponding to DL-SCH can also be configured on PDSCH. Base station device 3 can send PDSCH. Terminal device 1 can receive PDSCH.

[0172] A downlink physical signal may correspond to a set of resource elements. A downlink physical signal may not carry information generated in an upper layer. A downlink physical signal may be a physical signal used in a downlink component carrier. A downlink physical signal may be sent by a base station device 3. A downlink physical signal may also be sent by a terminal device 1. In a wireless communication system of one embodiment of the present invention, 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)

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

[0174] Figure 7 FIG. 1 is a diagram showing an example of the configuration of an SS / PBCH block according to one embodiment of the present invention. Figure 7 In the figure, the horizontal axis is the time axis (OFDM symbol index l sym ), the vertical axis represents the frequency domain. In addition, block 700 represents a set of resource elements for PSS. In addition, block 702 represents a set of resource elements for SSS. In addition, four blocks (blocks 710, 711, 712, and 713) represent a set of resource elements for PBCH and DMRS for the PBCH (DMRS associated with PBCH, DMRS included in PBCH, DMRS corresponding to PBCH).

[0175] like Figure 7As shown, the SS / PBCH block includes PSS, SSS and PBCH. In addition, the SS / PBCH block includes 4 consecutive OFDM symbols. The SS / PBCH block includes 240 subcarriers. PSS is configured on the 57th to 183rd subcarriers in the first OFDM symbol. SSS is configured on the 57th to 183rd subcarriers in the third OFDM symbol. The 1st to 56th subcarriers of the first OFDM symbol can be set to zero. The 184th to 240th subcarriers of the first OFDM symbol can also be set to zero. The 49th to 56th subcarriers of the third OFDM symbol can also be set to zero. The 184th to 192nd subcarriers of the third OFDM symbol can also be set to zero. PBCH is configured in the subcarriers that are the 1st to 240th subcarriers of the second OFDM symbol and are not configured with DMRS for PBCH. The PBCH is configured in the subcarriers that are the 1st to 48th subcarriers of the third OFDM symbol and are not configured with DMRS for the PBCH. The PBCH is configured in the subcarriers that are the 193rd to 240th subcarriers of the third OFDM symbol and are not configured with DMRS for the PBCH. The PBCH is configured in the subcarriers that are the 1st to 240th subcarriers of the fourth OFDM symbol and are not configured with DMRS for the PBCH.

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

[0177] The PBCH of a symbol conveying the PBCH in a certain antenna port may be estimated based on the DMRS for the PBCH which is configured to a slot in which the PBCH is mapped and which is included in a SS / PBCH block including the PBCH.

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

[0179] The set of antenna ports for DMRS for PDSCH (DMRS associated with PDSCH, DMRS included in PDSCH, DMRS corresponding to PDSCH) can be given based on the set of antenna ports for the PDSCH. That is, the set of antenna ports for DMRS for PDSCH can be the same as the set of antenna ports for the PDSCH.

[0180] 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 be transmitting the PDSCH and the DMRS for the PDSCH.

[0181] The transmission path of the PDSCH can be estimated based on the DMRS used for the PDSCH. If a set of resource elements for conveying a codeword of a certain PDSCH and a set of resource elements for conveying a codeword of the DMRS used for the certain PDSCH are included in the same precoding resource group (PRG: Precoding Resource Group), the PDSCH conveying the codeword of the PDSCH in a certain antenna port can be estimated based on the DMRS used for the PDSCH.

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

[0183] The PDCCH can be estimated based on the DMRS used for the PDCCH. That is, the transmission path of the PDCCH can be estimated based on the DMRS used for the PDCCH. If the same precoding is applied (assumed to be applied, assumed to be applied) in a set of resource elements conveying a codeword of a certain PDCCH and a set of resource elements conveying a codeword of the DMRS used for the certain PDCCH, then the PDCCH conveying the codeword of the PDCCH in a certain antenna port can be estimated based on the DMRS used for the PDCCH.

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

[0185] The BCH of the transport layer is mapped to the PBCH of the physical layer. That is, the transport block of the BCH of the transport layer is distributed to the PBCH of the physical layer. In addition, the UL-SCH of the transport layer is mapped to the PUSCH of the physical layer. That is, the transport block of the UL-SCH of the transport layer is distributed to the PUSCH of the physical layer. In addition, the DL-SCH of the transport layer is mapped to the PDSCH of the physical layer. That is, the transport block of the DL-SCH of the transport layer is distributed to the PDSCH of the physical layer.

[0186] One UL-SCH and one DL-SCH may be provided for each serving cell. BCH may be provided by PCell. BCH may also not be provided by PSCell or SCell.

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

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

[0189] The upper layer parameters shared by multiple terminal devices 1 are also called common upper layer parameters. The common upper layer parameters can be defined as parameters specific to a service cell. The parameters specific to a service cell can be parameters shared by terminal devices (e.g., terminal devices 1-A, B, C) that set the service cell.

[0190] For example, the common upper layer parameters may be included in an RRC message distributed to the BCCH. For example, the common upper layer parameters may be included in an RRC message distributed to the DCCH.

[0191] In a certain upper layer parameter, an upper layer parameter different from a common upper layer parameter is also referred to as a dedicated upper layer parameter. Among them, the dedicated upper layer parameter can provide a dedicated RRC parameter to the terminal device 1-A that sets the service cell. That is, the dedicated RRC parameter is an upper layer parameter that can provide a specific setting for each of the terminal devices 1-A, B, and C.

[0192] The BCCH of the logical channel can be mapped to the BCH or DL-SCH of the transport layer. For example, a transport block including MIB information is distributed to the BCH of the transport layer. In addition, a transport block including system information other than MIB is distributed to the DL-SCH of the transport layer. In addition, CCCH is mapped to DL-SCH or UL-SCH. That is, the transport block mapped to CCCH is distributed to DL-SCH or UL-SCH. In addition, DCCH is mapped to DL-SCH or UL-SCH. That is, the transport block mapped to DCCH is distributed to DL-SCH or UL-SCH.

[0193] The RRC message includes one or more parameters managed in the RRC layer. Among them, the parameters managed in the RRC layer are also called RRC parameters. For example, the RRC message may include MIB. In addition, the RRC message may also include system information. In addition, the RRC message may also include a message corresponding to the CCCH. In addition, the RRC message may also include a message corresponding to the DCCH. The RRC message including a message corresponding to the DCCH is also called a dedicated RRC message.

[0194] The upper layer parameters (upper layer parameters) are RRC parameters or parameters included in MAC CE (Medium Access Control Control Element: control element of media access control). That is, the upper layer parameters are a general 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 sent through MAC CE (Control Element: control element) commands.

[0195] The process performed by the terminal device 1 includes at least a part or all of the following 5A to 5C. 5A) Cell search 5B) Random access 5C) Data communication

[0196] Cell search is a process for synchronizing a cell in time and frequency domains and detecting a physical cell ID (physical cell identity) through the terminal device 1. That is, the terminal device 1 can synchronize with a cell in time and frequency domains and detect a physical cell ID through cell search.

[0197] The sequence of the PSS is given based on at least the physical cell ID. The sequence of the SSS is given based on at least the physical cell ID.

[0198] The SS / PBCH block candidates indicate resources for which transmission of SS / PBCH blocks is permitted (able to, reserved, set, specified, or possible).

[0199] The set of SS / PBCH block candidates in a half radio frame is also called an SS burst set. An SS burst set is also called a transmission window, an SS transmission window, or a DRS transmission window. An SS burst set is a general term for at least a first SS burst set and a second SS burst set.

[0200] The base station device 3 sends one or more indexed SS / PBCH blocks at a predetermined period. The terminal device 1 can detect at least any one of the one or more indexed SS / PBCH blocks and attempt to decode the PBCH included in the SS / PBCH block.

[0201] Random access is a process including at least part or all of message 1, message 2, message 3 and message 4.

[0202] Message 1 is a process of sending PRACH by terminal device 1. Terminal device 1 sends PRACH in a PRACH opportunity selected from one or more PRACH opportunities based at least on an index of an SS / PBCH block candidate, wherein the index of the SS / PBCH block candidate is detected based on a cell search. Each PRACH opportunity is defined based on at least a time domain resource and a frequency domain resource.

[0203] The terminal device 1 transmits one random access preamble selected from the PRACH opportunities corresponding to the index of the SS / PBCH block candidate for detecting the SS / PBCH block.

[0204] Message 2 is a process of attempting to detect DCI format 1_0 with CRC (Cyclic Redundancy Check) encrypted by RA-RNTI (Random Access-Radio Network Temporary Identifier) ​​by terminal device 1. Terminal device 1 attempts to detect PDCCH including the DCI format in resources indicated based on the settings of control resource set and search area set, wherein the settings of control resource set and search area set are given based on MIB of PBCH included in SS / PBCH block detected based on cell search. Message 2 is also called random access response.

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

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

[0207] The retransmission of message 3 PUSCH is scheduled by DCI format 0_0 with a CRC scrambled based on TC-RNTI (Temporary Cell-Radio Network Temporary Identifier).

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

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

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

[0211] 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 can be composed of continuous resources (non-interleaved mapping) or distributed resources (interleaver mapping).

[0212] The set of resource blocks constituting the control resource set may be represented by a higher layer parameter. The number of OFDM symbols constituting the control resource set may also be represented by a higher layer parameter.

[0213] Terminal device 1 attempts to detect PDCCH in the search area set. Here, attempting to detect PDCCH in the search area set may be attempting to detect PDCCH candidates in the search area set, or attempting to detect DCI formats in the search area set, or attempting to detect PDCCH in the control resource set, or attempting to detect PDCCH candidates in the control resource set, or attempting to detect DCI formats in the control resource set.

[0214] The search area set is defined as a set of PDCCH candidates. The search area set can be a CSS (Common Search Space) set or a USS (UE-specific Search Space) set. Terminal device 1 attempts to detect PDCCH candidates in part 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 PDCCH search space set.

[0215] The type 0 PDCCH common search region set may be used as the common search region set of index 0. The type 0 PDCCH common search region set may also be the common search region set of index 0.

[0216] The CSS set is a general term for type 0 PDCCH common search area set, type 0a PDCCH common search area set, type 1 PDCCH common search area set, type 2 PDCCH common search area set, and type 3 PDCCH common search area set. The USS set is also called a UE-specific PDCCH search area set.

[0217] A certain search area set is associated with (includes, corresponds to) a certain control resource set. The index of the control resource set associated with the search area set may be represented by an upper layer parameter.

[0218] For a certain search area set, at least part or all of 6A to 6C may be represented by upper layer parameters. 6A) PDCCH monitoring periodicity 6B) PDCCH monitoring pattern within a slot 6C) PDCCH monitoring offset

[0219] A monitoring occasion of a certain search area set may correspond to an OFDM symbol configured with an OFDM symbol of a starting point of a control resource set associated with the certain search area set. A monitoring occasion of a certain search area set may also correspond to resources of the control resource set starting from an OFDM symbol of a starting point of a control resource set associated with the certain search area set. The monitoring occasion of the search area set is given based on at least a portion or all of a monitoring interval of a PDCCH, a monitoring mode of a PDCCH within a time slot, and a monitoring offset of a PDCCH.

[0220] Figure 8 FIG. 1 is a diagram showing an example of monitoring opportunities of a search area set according to one embodiment of the present invention. Figure 8 In the embodiment, search area set 91 and search area set 92 are set in primary cell 301 , search area set 93 is set in secondary cell 302 , and search area set 94 is set in secondary cell 303 .

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

[0222] The monitoring interval of search area set 91 is set to 1 time slot, the monitoring offset of search area set 91 is set to 0 time slots, and the monitoring pattern of search area set 91 is set to [1, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0]. That is, the monitoring opportunities of search area set 91 correspond to the starting OFDM symbol (OFDM symbol #0) and the 8th OFDM symbol (OFDM symbol #7) in each time slot.

[0223] The monitoring interval of search area set 92 is set to 2 time slots, the monitoring offset of search area set 92 is set to 0 time 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]. That is, the monitoring opportunity of search area set 92 corresponds to the OFDM symbol (OFDM symbol #0) at the start point in each even time slot.

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

[0225] The monitoring interval of search area set 94 is set to 2 time slots, the monitoring offset of search area set 94 is set to 1 time 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]. That is, the monitoring opportunity of search area set 94 corresponds to the OFDM symbol (OFDM symbol #0) at the start point in each odd time slot.

[0226] The type 0 PDCCH common search area set can be used at least for a DCI format with a CRC (Cyclic Redundancy Check) sequence scrambled by SI-RNTI (System Information-Radio Network Temporary Identifier).

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

[0228] The type 1 PDCCH common search space set can be used for at least a DCI format with a CRC sequence scrambled by an RA-RNTI (Random Access-Radio Network Temporary Identifier) ​​and / or a CRC sequence scrambled by a TC-RNTI (Temporary Cell-Radio Network Temporary Identifier).

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

[0230] The type 3 PDCCH common search area set can be used for a DCI format with a CRC sequence scrambled by a C-RNTI (Cell-Radio Network Temporary Identifier).

[0231] The UE-specific PDCCH search area set may be used at least for a DCI format to which a CRC sequence scrambled by a C-RNTI is attached.

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

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

[0234] In the configured grant, the uplink grant for scheduling PUSCH is configured for each transmission period of the PUSCH. When the PUSCH is scheduled by an uplink DCI format, part or all of the information indicated by the uplink DCI format may be indicated by the configured uplink grant in the configured scheduling.

[0235] A UL time slot may be a time slot consisting of UL symbols. A special time slot may be a time slot consisting of UL symbols, variable symbols, and DL symbols. A DL time slot may be a time slot consisting of DL symbols.

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

[0237] The DL symbol may be an OFDM symbol set or indicated for the downlink in time division duplex. The DL symbol may be an OFDM symbol set or indicated for the PDSCH or PDCCH. The DL symbol may be provided by the upper layer parameter tdd-UL-DL-ConfigurationCommon. The DL symbol may also be provided by the upper layer parameter tdd-UL-DL-ConfigurationDedicated. The DL timeslot may be provided by the upper layer parameter tdd-UL-DL-ConfigurationCommon. The DL timeslot may also be provided by the upper layer parameter tdd-UL-DL-ConfigurationDedicated.

[0238] The variable symbol may be an OFDM symbol in a certain period that is not set or indicated as a UL symbol or a DL symbol. The certain period may be a period given by the upper layer parameter dl-UL-TransmissionPeriodicity. The variable symbol may be an OFDM symbol set or indicated for PDSCH, PDCCH, PUSCH, PUCCH or PRACH.

[0239] The upper layer parameter tdd-UL-DL-ConfigurationCommon may be a parameter for setting any one of a UL time slot, a DL time slot, and a special time slot for each of one or more time slots. The upper layer parameter tdd-UL-DL-ConfigurationDedicated may be a parameter for setting any one of a UL codeword, a DL codeword, and a variable codeword for a variable codeword in each of the one or more time slots. tdd-UL-DL-ConfigurationCommon may be a common upper layer parameter. tdd-UL-DL-ConfigurationDedicated may be a dedicated upper layer parameter.

[0240] PUSCH-Config can be a dedicated upper layer parameter. PUSCH-ConfigCommon can be a common upper layer parameter. PUSCH-Config can be set for PUSCH transmission per BWP. PUSCH-Config can include multiple upper layer parameters related to PUSCH transmission. PUSCH-Config can be a UE-specific setting. For example, the PUSCH-Config for terminal device 1A, terminal device 1B and terminal device 1C in a cell or the multiple upper layer parameters included in the PUSCH-Config can be different. PUSCH-ConfigCommon can also be set for PUSCH transmission per BWP. PUSCH-ConfigCommon can include multiple upper layer parameters related to PUSCH transmission. PUSCH-ConfigCommon can be a cell-specific setting. For example, the PUSCH-ConfigCommon for terminal device 1A, terminal device 1B and terminal device 1C in a cell can be shared. For example, PUSCH-ConfigCommon can be given by system information.

[0241] Repeated transmission may be applied to PUSCH. For example, repeated transmission may be applied to PUSCH scheduled by DCI. In addition, repeated transmission may also be applied to PUSCH scheduled by a set uplink grant. The PUSCH repetition type may be any one of PUSCH repetition type A and PUSCH repetition type B. The PUSCH repetition type may be set by an upper layer parameter. The PUSCH repetition type may be based on the DCI format. For example, the first PUSCH repetition type for PUSCH scheduled by DCI format 0_1 ​​may be different from the second PUSCH repetition type for PUSCH scheduled by DCI format 0_2.

[0242] The number of repetitions for PUSCH repeated transmission can be set by upper layer parameters. For example, the upper layer parameter numberOfRepetitioins can be a parameter including the number of repetitions for PUSCH repeated transmission. In the PUSCH repeated transmission corresponding to PUSCH repetition type A, the number of repetitions for PUSCH repeated transmission can be determined by the value of the upper layer parameter numberOfRepetitions. In PUSCH repetition type A, when there is numberOfRepetitions in the resource allocation table, the number of repetitions of the PUSCH sent by the DCI format indication with a CRC encrypted by any one of C-RNTI, MCS-C-RNTI and CS-RNTI can be equal to numberOfRepetitions. When a PUSCH-TimeDomainResourceAllocation includes one or more PUSCH-Allocations, the upper layer parameter numberOfRepetitions can be set for each PUSCH-Allocation. In addition, PUSCH-TimeDomainResourceAllocation can be called a resource allocation table.

[0243] The upper layer parameter pusch-AggregationFactor may be a parameter indicating the number of repetitions of PUSCH repetition transmission. In PUSCH repetition transmission corresponding to PUSCH repetition type A, the number of repetitions for PUSCH repetition transmission may be determined by the value of the upper layer parameter pusch-AggregationFactor. In PUSCH repetition type A, when pusch-AggregationFactor is set, the number of repetitions of PUSCH transmitted by a DCI format indication with a CRC encrypted by any one of C-RNTI, MCS-C-RNTI and CS-RNTI may be equal to pusch-AggregationFactor. pusch-AggregationFactor may be set for PUSCH-Config.

[0244] The number of repetitions corresponding to PUSCH repetition type A may be the number of slots used for PUSCH repetition transmission. In addition, one TB may be repeated in one or more slots. PUSCH repetitions transmitted in different slots may apply the same OFDM symbol allocation.

[0245] In the PUSCH repetition transmission corresponding to the PUSCH repetition type B, it can be based on nominal repetition (NominalRepetition) and actual repetition (ActualRepetition).

[0246] The frequency hopping mode can be set by upper layer parameters. The upper layer parameters frequencyHopping, frequencyHoppingDCI-0-1 and frequencyHoppingDCI-0-2 can be parameters for providing a frequency hopping mode for PUSCH. For example, the frequency hopping mode corresponding to the frequency hopping for PUSCH can be set by frequencyHoppingDCI-0-2 in PUSCH-Config. In addition, the frequency hopping mode corresponding to the frequency hopping for PUSCH can also be set by frequencyHopping in PUSCH-Config. In addition, the frequency hopping mode corresponding to the frequency hopping for the set PUSCH transmission can also be set by frequency hopping (frequency Hopping) in configuredGrantConfig. The frequency hopping mode can be any one of intra-slot frequency hopping, inter-slot frequency hopping and inter-repetition frequency hopping. In addition, the frequency hopping interval corresponding to intra-slot frequency hopping can be within one slot. The frequency hopping interval corresponding to inter-slot frequency hopping can be one slot or multiple slots. The frequency hopping interval corresponding to inter-repetition frequency hopping can be based on nominal repetition.

[0247] For example, the frequency hopping interval may be provided by an upper layer parameter. For example, the upper layer parameter may be a dedicated upper layer parameter.

[0248] Whether to perform frequency hopping may be determined at least based on the DCI. Whether frequency hopping is applied to the PUSCH sent by the DCI format indication may be determined at least based on the value of the frequency hopping flag field included in the DCI format. Whether frequency hopping is applied to the PUSCH sent by the random access response indication may also be determined at least based on the value of the frequency hopping flag field included in the random access response grant. For example, frequency hopping for the PUSCH may also be performed based at least on the value of the frequency hopping flag field being 1.

[0249] Intra-slot frequency hopping may also be applied to PUSCH transmissions in one or more time slots. For example, intra-slot frequency hopping may also be applied to repeated PUSCH transmissions. For a PUSCH to which intra-slot frequency hopping is applied, the configuration may be switched according to one or more OFDM symbols. For example, for a PUSCH to which intra-slot frequency hopping is applied, the configuration of the resource block may be switched to be the first hop or the second hop according to one or more OFDM symbols. In addition, in the case of performing intra-slot frequency hopping for the PUSCH, the first hop and the second hop may be switched according to one or more OFDM symbols. The difference between the position of the starting resource block of the first hop and the position of the starting resource block of the second hop may be RB offset RB offset It can be set by upper layer parameters. The one or more OFDM symbols can be within a time slot. The one or more OFDM symbols can be half of the number of OFDM symbols used for PUSCH in a time slot. Intra-time slot frequency hopping can be applied to PUSCH corresponding to PUSCH repetition type A.

[0250] Inter-slot frequency hopping can be applied to PUSCH transmissions in multiple time slots. For PUSCH to which inter-slot frequency hopping is applied, the configuration of resource blocks can be switched per time slot. For example, inter-slot frequency hopping can be applied to repeated PUSCH transmissions. In addition, in the case of performing inter-slot frequency hopping for PUSCH, the configuration of resource blocks can be switched per time slot as to whether they are the first hop or the second hop. For example, in a certain time slot, the slot index n μ s，f When the timeslot index n is an even number, the PUSCH transmission in the certain time slot may correspond to the first hop. μ s，f When t is an odd number, the PUSCH transmission in the certain time slot may correspond to the second hop. Inter-slot frequency hopping may be applied to a PUSCH corresponding to either PUSCH repetition type A or PUSCH repetition type B.

[0251] Inter-repetition hopping may be applied to a PUSCH corresponding to PUSCH repetition type B. For a PUSCH to which inter-repetition hopping is applied, a first hop and a second hop may be switched based on a nominal repetition.

[0252] pusch-TransCoherence may define support for uplink codebook subsets for PUSCH transmission. A UE indicating support for partially coherent codebook subsets may also support non coherent codebook subsets. A UE indicating support for fully coherent codebook subsets may also support both partially coherent and non coherent codebook subsets.

[0253] pusch-TransCoherence-r18 can define support for uplink codebook subsets for PUSCH transmission. UEs that indicate support for the 2ports partial coherent codebook subset can also support the non coherent codebook subset. UEs that indicate support for the 4portspartial coherent codebook subset can also support 2ports partialcoherent and non coherent codebook subsets. UEs that indicate support for the fully coherent codebook subset can also support 4ports partial coherent, 2ports partial coherent, and non coherent codebook subsets. pusch-TransCoherence-r18 can be used as a UE capability to support 8Tx transmission.

[0254] pusch-TransCoherence-r18 may define support for uplink codebook subsets for PUSCH transmission. UEs indicating support for non coherent codebook subsets may only support non coherent codebook subsets. UEs indicating support for 2ports partial coherent codebook subsets may only support 2ports partial coherent codebook subsets. UEs indicating support for 4ports partial coherent codebook subsets may only support 4ports partial coherent codebook subsets. UEs indicating support for fully coherent codebook subsets may only support fully coherent codebook subsets.

[0255] At least two transmission methods may be supported for PUSCH. For example, codebook transmission (Codebook-basedtransmission) may be one of the transmission methods for PUSCH. For example, non-codebook transmission (Non-codebook-basedtransmission) may be one of the transmission methods for PUSCH. The upper-layer parameters may provide any one of codebook transmission and non-codebook transmission. For example, when 'codebook' is set for the upper-layer parameters, the terminal device 1 may set the codebook transmission. For example, when 'nonCodebook' is set for the upper-layer parameters, the terminal device 1 may set the non-codebook transmission. The upper-layer parameter may be txConfig. The upper-layer parameter may be usage. For example, when the upper-layer parameters are not set, the terminal device 1 may not expect scheduling through any of DCI formats 0_1 and DCI formats 0_2. When PUSCH is scheduled through DCI format 0_0, the transmission of the PUSCH may be based on at least one antenna port.

[0256] In codebook transmission, PUSCH can be scheduled by DCI format. The DCI format can be any one of DCI format 0_0, DCI format 0_1 ​​and DCI format 0_2. In codebook transmission, PUSCH can be set to be sent semi-statically. Terminal device 1 can determine one or more precoders for PUSCH transmission. For example, precoding can be determined based on part or all of SRI (SRS Resource indicator), TPMI (Transmitted Precoding Matrix Indicator: Transmitted Precoding Matrix Indicator) and transmission rank (Transmission rank or rank). For example, SRI can be provided by one or two DCI fields of SRS resource indicators (SRS resource indicator). For example, TPMI can be provided by one or two DCI fields of precoding information (Precodinginformation). For example, the transmission rank can be provided by the DCI field of the number of layers (number of transmission layers). SRI can be provided by a first upper layer parameter. TPMI and transmission rank can be provided by a second upper layer parameter. The first upper layer parameter may be srs-ResourceIndicator or srs-ResourceIndicator2. The second upper layer parameter may be precodingAndNumberOfLayers or precodingAndNumberOfLayers2.

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

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

[0259] When one SRS resource set is set, the SRI and TPMI may be given by the DCI field. TPMI may be used to indicate precoding. Precoding may be applied across v layers. When multiple SRS resources are set, one SRS resource may be selected via SRI. The transmit precoder (precoder) may be selected from a codebook (uplink codebook). For example, a codebook may have the number of antenna ports. The number of antenna ports may be the same as the upper layer parameter nrofSRS-Ports. When 'codebook' is set for the upper layer parameter txConfig, the terminal device 1 may set at least one SRS resource. The indicated SRI may be associated with the transmission of the SRS resource determined by the SRI.

[0260] When two SRS resource sets are set, one or two SRIs and one or two TPMIs may be given by the DCI field. For example, the DCI field may be one or both of the DCI field of the SRS resource indicator, the precoding information, and the DCI field of the number of layers. The terminal device 1 may apply the indicated SRI and TPMI to one or more PUSCH repetitions. The TPMI may be used to indicate precoding based on the code point of the SRS resource set indicator. Precoding may be applied to layers 0 to v-1. Precoding may correspond to the SRS resources selected by the SRI. Multiple SRS resources may be set for applicable SRS resource sets. In one or two TPMIs, the transmit precoder may be selected from a codebook (uplink codebook). When indicating two SRIs, the terminal device 1 may expect the same number of antenna ports for the two indicated SRS resources. The number of antenna ports may be provided by upper layer parameters.

[0261] 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 reception of a certain upper-layer parameter. The certain upper-layer parameter may be codebookSubset, codebookSubset-r18, or codebookSubsetDCI-0-2. The certain upper-layer parameter may be determined based at least on the number of SRS ports. For example, when the number of SRS ports is less than 4, the certain upper-layer parameter may be codebookSubset or codebookSubsetDCI-0-2. For example, when the number of SRS ports is greater than 4, the certain upper-layer parameter may be codebookSubset-r18. The certain upper-layer parameter may be set to any one of 'fullyAndPartialAndNonCoherent', 'partialAndNonCoherent', 'nonCoherent', 'fullyCoherent', 'partialCoherent', '4portsPartialCoherent', and '2portsPartialCoherent'. For example, when at least some upper layer parameter sets 'partialAndNonCoherent', the codebook subset associated with the two-port SRS resource (SRS resource with two ports) may be 'nonCoherent'. For example, the codebook may include at least one SRS resource with four ports and at least one SRS resource with two ports. For example, when at least some upper layer parameter sets '4portsPartialCoherent', the codebook subset associated with the four-port SRS resource (SRS resource with four ports) may be 'fullyAndPartialAndNonCoherent'. For example, when at least some upper layer parameter sets '2portsPartialCoherent', the codebook subset associated with the two-port SRS resource (SRS resource with two ports) may be 'partialAndNonCoherent'. For example, the codebook may include at least one SRS resource with eight ports and at least one SRS resource with four ports.

[0262] In the case where the terminal device 1 reports the UE capability of sending 'partialAndNonCoherent', the terminal device 1 may not expect to set the codebook subset with 'fullyAndPartialAndNonCoherent'.

[0263] In the case where the terminal device 1 reports the UE capability of 'nonCoherent' transmission, the terminal device 1 may not expect to set the codebook subset with 'fullyAndPartialAndNonCoherent' or 'partialAndNonCoherent'.

[0264] In the case where the terminal device 1 reports the UE capability of sending 'fullyCoherent', the terminal device 1 may not expect to set the codebook subset with 'partialCoherent' or 'nonCoherent'.

[0265] In the case where the terminal device 1 reports the UE capability of sending 'partialCoherent', the terminal device 1 may not expect to set a codebook subset with 'fullyCoherent' or 'nonCoherent'.

[0266] In the case where the terminal device 1 reports the UE capability of 'nonCoherent' transmission, the terminal device 1 may not expect to set the codebook subset with 'fullyCoherent' or 'partialCoherent'.

[0267] In the case where the terminal device 1 reports the UE capability of 'fully Coherent' transmission, the terminal device 1 may not expect to set a codebook subset with '2ports Partial Coherent', '4ports Partial Coherent', or 'non Coherent'.

[0268] In the case where the terminal device 1 reports the UE capability transmitted by '4portsPartialCoherent', the terminal device 1 may not expect to set a codebook subset with 'fullyCoherent', '2portsPartialCoherent', or 'nonCoherent'.

[0269] In the case where the terminal device 1 reports the UE capability transmitted by '2portsPartialCoherent', the terminal device 1 may not expect to set a codebook subset with 'fullyCoherent', '4portsPartialCoherent', or 'nonCoherent'.

[0270] In the case where the terminal device 1 reports the UE capability of 'nonCoherent' transmission, the terminal device 1 may not expect to set the codebook subset with 'fullyCoherent', '4portsPartialCoherent' or '2portsPartialCoherent'.

[0271] When the maximum number of SRS antenna ports set by the antenna port number indication is 2, the terminal device 1 may not expect to set the upper layer parameter in which 'partialAndNonCoherent' is set. The upper layer parameter may be codebookSubset or codebookSubsetForDCI-Format0-2. The number of antenna ports may be determined by the upper layer parameter nrofSRS-Ports.

[0272] When the maximum number of SRS antenna ports set by the antenna port number indication is 2 or 4, the terminal device 1 may not expect to set the upper layer parameter setting 'fully Coherent'. The upper layer parameter may be codebookSubset-r18 or codebookSubsetForDCI-Format0-2-r18. The number of antenna ports may be determined by the upper layer parameter nrofSRS-Ports.

[0273] When the maximum number of SRS antenna ports set by the antenna port number indication is 2, the terminal device 1 may not expect to set the upper layer parameter of setting 'fullyCoherent' or '4portsPartialCoherent'. The upper layer parameter may be codebookSubset-r18 or codebookSubsetForDCI-Format0-2-r18. The number of antenna ports may be determined by the upper layer parameter nrofSRS-Ports.

[0274] When the maximum number of SRS antenna ports set by the antenna port number indication is 4, the terminal device 1 may not expect to set the upper layer parameter setting 'fullyCoherent' or '2portsPartialCoherent'. The upper layer parameter may be codebookSubset-r18 or codebookSubsetForDCI-Format0-2-r18. The number of antenna ports may be determined by the upper layer parameter nrofSRS-Ports.

[0275] In codebook transmission, an SRS resource can be determined from an SRS resource set based on SRI. Except for the case where 'fullpowerMode2' is set for the first upper layer parameter, the maximum number of SRS resources set for codebook transmission can be 2. The first upper layer parameter may be ul-FullPowerTransmission. The DCI may indicate the transmission of SRS resources. For example, when aperiodic SRS is set, the SRS request field in the DCI may indicate the transmission of aperiodic SRS resources. Terminal device 1 may not expect the first upper layer parameter of 'fullpowerMode1' to be set and the second upper layer parameter of 'fullAndPartialAndNonCoherent' to be set.

[0276] As one or more SRS ports in the SRS resource indicated by the DCI format or upper layer parameters, the terminal device 1 can use the same one or more antenna ports to transmit PUSCH. For example, the SRS port can be the same as the antenna port used for PUSCH transmission. The DMRS antenna port can be determined based on the ordering of the DMRS ports.

[0277] When a plurality of SRS resources are set by an SRS resource set, the terminal device 1 may expect that an upper layer parameter nrofSRS-Ports having the same value is set for these SRS resources. The SRS resource set may be an upper layer parameter SRS-ResourceSet with an upper layer parameter usage having 'codebook' set.

[0278] When 'fullpowerMode2' is set for the upper-layer parameter, one or more SRS resources with the same or different number of SRS ports can be set in one SRS resource set. When 'fullpowerMode2' is set for the upper-layer parameter, up to two different spatial relations can be set for all SRS resources in one SRS resource set. When 'fullpowerMode2' is set for the upper-layer parameter, up to two or four SRS resources can be set in one SRS resource set. In addition, up to eight SRS resources can also be set in one SRS resource set. The SRS resource set can be an SRS resource set with the upper-layer parameter usage set with 'codebook'.

[0279] In non-codebook transmission, PUSCH can be scheduled by DCI format 0_0, DCI format 0_1 ​​or DCI format 0_2. Terminal device 1 can determine the precoding and transmission rank of PUSCH based on SRI. For example, when multiple SRS resources are set, SRI can be given by one or two SRS resource indicators in DCI. For example, SRI can be given by upper layer parameters. The SRS resource set applied to PUSCH can be defined by the entry of the upper layer parameter. The upper layer parameter can be srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2.

[0280] The terminal device 1 can use one or more SRS resources for SRS transmission. The maximum number of SRS resources in an SRS resource set can be sent to the base station device 3 as a UE capability. SRS resources can be set for simultaneous transmission in the same OFDM codeword. Multiple SRS resources sent simultaneously can occupy the same resource block. An SRS port can be set in each SRS resource. One or two SRS resource sets can also be set in the upper-layer parameter srs-ResourceSetToAddModList in which the upper-layer parameter usage in the upper-layer parameter SRS-ResourceSet is set to 'nonCodebook'. When two SRS resource sets are set, one or two SRIs can be given by the DCI field. The DCI field can be a DCI field of two SRS resource indicators.

[0281] The terminal device 1 may apply the indicated SRI to one or more PUSCH repetitions. For example, depending on the SRS resource set of the PUSCH repetitions, the terminal device 1 may apply the indicated SRI to one or more PUSCH repetitions. The maximum number of SRS resources for each SRS resource set set for non-codebook transmission may be 4. The maximum number of SRS resources for each SRS resource set set for non-codebook transmission may be 8. The indicated one or two SRIs may be associated with the latest transmission of the SRS resources of the SRS resource set identified by the SRI, respectively. The SRS transmission may be before the PDCCH that conveys the SRI. The terminal device 1 may also not expect different numbers of SRS resources to be set in the two SRS resource sets.

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

[0283] In non-codebook transmission, the UE may calculate the precoder. For example, the precoder for SRS transmission may be calculated based on the measurement of the NZP CSI-RS resource. An NZP CSI-RS resource may be set for an SRS resource set. For example, an SRS resource set may be an SRS resource set with upper layer parameters set to 'nonCodebook'.

[0284] When an aperiodic SRS resource set is set, the NZP-CSI RS can be indicated via the SRS request field. The SRS request field can be one of the DCI fields in any one of DCI format 0_1, DCI format 0_2, DCI format 1_1 and DCI format 1_2. The first upper layer parameter may indicate the association between the aperiodic SRS (aperiodic SRS triggering state) and the SRS resource set. The first upper layer parameter, the triggered SRS resource, the srs-ResourceSetId and the csi-RS can be set 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 as an upper layer parameter. The list as an upper layer parameter may be an upper layer parameter srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2. Terminal device 1 may not expect to update precoding information (SRS precoding information). For example, when the interval from the last OFDM symbol received by the non-periodic NZP-CSI-RS resource to the first OFDM symbol sent by the non-periodic SRS is less than 42 OFDM symbols, terminal device 1 may not expect to update precoding information.

[0285] In the case where an aperiodic SRS associated with an aperiodic NZP CSI-RS resource is set, the presence of CSI-RS can be indicated by the SRS request field. In the case where the value of the SRS request field is not '00' and the scheduling DCI is not used for cross carrier scheduling or cross BWP scheduling, the presence of CSI-RS can be indicated by the SRS request field.

[0286] The terminal device 1 can perform a one-to-one mapping. The one-to-one mapping can be a mapping from SRI to the PUSCH layer corresponding to the DMRS port. PUSCH layers from 0 to v-1 can be given. v can be the number of layers. The number of layers can be set by upper layer parameters. The terminal device 1 can use the same antenna port as the SRS port to send PUSCH. For example, the SRS port in the SRS resource indicated by SRI can be indexed as pi=1000+i. For example, the SRS port in the (i+1)th SRS resource can be pi. In addition, the SRS port in the (i+1)th SRS resource can be indexed as pi. pi can also be 1000+i. That is, it can also be pi=1000+i.

[0287] In non-codebook transmission, the terminal device 1 may not expect to set both the 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. The spatial relationship information can be determined by the upper-layer parameter. The spatial relationship information can be the upper-layer parameter spatialRelationInfo. In non-codebook transmission, when at least one SRS resource is set in the SRS resource set with the upper-layer parameter set 'nonCodebook', the terminal device 1 can be scheduled through DCI format 0_1 ​​or DCI format 0_2.

[0288] The CQI indicator used to report the CQI and its interpretation may be indicated based on the modulation scheme.

[0289] The terminal device 1 can derive the highest CQI indicator that satisfies the following conditions based on an observation interval that is unlimited in time and an observation interval that is unlimited in frequency, for each CQI value reported in uplink time slot n. In the combination of modulation mode, target coding rate, and transport block size corresponding to the CQI indicator, a single PDSCH transport block occupying a downlink physical resource block group called a CSI reference resource can be received in a manner that does not exceed the transport block error probability, but it can also be a condition.

[0290] When the upper layer parameter timeRestrictionForChannelMeasurements is set to "notConfigured", the terminal device 1 can derive channel measurements for calculating the CSI value reported in UL time slot n only based on the NZP CSI-RS no later than the CSI reference resource associated with the CSI resource configuration.

[0291] When the upper layer parameter timeRestrictionForChannelMeasurements of CSI-ReportConfig is "Configured", the terminal device 1 can derive the channel measurement for CSI calculation reported in UL time slot n only based on the latest opportunity of the NZP CSI-RS associated with the CSI resource configuration and not later than the CSI reference resource.

[0292] When the upper layer parameter timeRestrictionForInterferenceMeasurements is set to "notConfigured", the terminal device 1 can derive the interference measurement value for calculating the CSI value reported in the UL time slot n based solely on the CSI-IM and / or NZP CSI-RS, no later than the CSI reference resource associated with the CSI resource setting.

[0293] When the upper layer parameter timeRestrictionForInterferenceMeasurements of CSI-ReportConfig is "Configured", the terminal device 1 can derive the interference measurement value used to calculate the CSI value reported in the UL time slot n based on the opportunity of the latest interference measurement CSI-IM and / or NZP CSI-RS associated with the CSI resource setting no later than the CSI reference resource.

[0294] For each subband index s, a 2-bit subband differential CQI may be defined as follows. Subband offset level (s) = subband CQI index (s) - wideband CQI index

[0295] The combination of the modulation mode and the transport block size may correspond to the CQI index in the following cases. According to the determination of the transport block size, when it is possible to signal for transmission on the PDSCH of the CSI reference resource, and the modulation mode is indicated by the CQI index, and the combination of the transport block size and the modulation mode is applied to the reference resource, an effective channel coding rate closest to the coding rate indicated by the CQI indicator can be obtained. There are multiple combinations of transport block size and modulation mode, and when an effective channel coding rate equal to and close to the coding rate indicated by the CQI index is obtained, only the combination with the smallest transport block size can be associated.

[0296] When the terminal device 1 has two antenna ports and the upper-layer parameter codebookType is set to "typeI-SinglePanel", each PMI value can correspond to the codebook index in the following manner. The terminal device 1 can set the upper-layer parameter twoTX-CodebookSubsetRestriction. The bitmap parameter twoTX-CodebookSubsetRestriction can form a bit string a5...a1, a0 with a0 as LSB and a5 as MSB. The bit value 0 may indicate that the PMI report is not allowed to correspond to the precoding associated with the bit. Bits 0 to 3 may be associated with codebook indices 0 to 3 with a layer number of 1, respectively, and bits 4 and 5 may be associated with codebook indices 0 and 1 with a layer number of 2, respectively.

[0297] When the terminal device 1 has more than four antenna ports and the upper layer parameter codebookType is set to "typeI-SinglePanel", each PMI or TPMI value can correspond to the codebook index in the following manner. When the number of layers v≠{2, 3, 4}, each PMI value can correspond to three codebook indexes i 1，1 、i 1，2 In the case of the number of layers v = {2, 3, 4}, each PMI value can correspond to four codebook indexes i 1，1 、i 1，2 、i 1，3 , i2 corresponds to. The composite codebook index i1 can be i 1，1 、i 1，2 、i 1，3 part or all of it.

[0298] k1 and k2 can be based on i 1，3 , the number of layers v, and the antenna configuration N1, N2 of the terminal device 1 are determined to be 0 or multiples of O1, O2. Here, N1, N2 can be the number of antennas in the horizontal and vertical directions configured on the antenna panel of the terminal device 1. In addition, O1, O2 can be the number of oversampling steps for determining the horizontal and vertical beam scanning steps of the terminal device 1. The supported combinations of (N1, N2) and (O1, O2) can be based on the number of CSI-RS ports P of the terminal device 1. CSI-RS to be sure.

[0299] The values ​​of N1 and N2 can be set by the upper layer parameters n1-n2. P as the number of CSI-RS ports CSI-RS It can be given by 2N1N2. When the value of N2 is 1, the terminal device 1 can only use i 1，2 = 0, do not report i 1，2 .

[0300] The bitmap parameters n1-n2 can be formed by a0 being the LSB and a Ac-1 The bit string a is the MSB Ac-1 ...a1, a0. A bit value of 0 may indicate that the PMI report is not allowed to correspond to any precoding associated with this bit. The number of bits may be given by Ac=N1O1N2O2. Except for the case where the number of layers v∈{3, 4} and the number of antenna ports is 16, 24, 32, bit a N2O2，l+m Can be based on the amount v l，m , l=0……N1O1-1、m=0……N2O2-1 are associated. When the number of layers v∈{3, 4} and the number of antenna ports is any one of 16, 24, and 32, bit a (N2O2(2l-1)+m)modN1O1N2O2 、a N2O2(2l)+m and a N2O2(2l+1)m can be based on the quantity v l，m , l = 0 ... N1O1-1, m = 0 ... N2O2-1 are associated with all precodings. In the case where one or more of the associated bits is zero, the PMI report may not correspond to the precoding based on v l，m any precoding.

[0301] When the upper layer parameter codebookType is set to "typeI-SinglePanel", the bitmap parameter typeI-SinglePanel-ri-Restriction may form a bit string r7...r1, r0, where r0 is the LSB and r7 is the MSB. i When i∈{0, 1, ..., 7}, the reporting of PMI and RI may not correspond to any precoding associated with layer v=i+1.

[0302] When the upper layer parameter reportQuantity is set to "cri-RI-i1-CQI", the bitmap parameter typeI-SinglePanel-codebookSubsetRestriction-i2 can be formed with b0 as LSB and b 15 b for MSB 15 ...a bit string of b1, b0. Bit b i An association can be established with the precoding corresponding to the codebook index i2=i. i When the precoding is 0, the precoding randomly selected for CQI calculation may not correspond to bit b. i Any precoding associated is established.

[0303] The precoding matrix W can be based on the number of CSI-RS ports P CSI-RS And the amount θ p 、um 、v l，m 、v ～ l，m In addition, the amount can be determined based on part or all of l, m, n, and p, respectively, and l, m, n, and p can also be determined based on part or all of i1 and i2.

[0304] When the terminal device 1 has eight or more antenna ports and the upper layer parameter codebookType is set to "typeI-MultiPanel", N g The values ​​of N1, N2 and N4 can be set by the upper layer parameters ng-n1-n2. CSI-RS It can be obtained by 2N g N1N2 is given. Supported (N g , N1, N2) and (O1, O2) can be based on the number of CSI-RS ports P of terminal device 1 CSI-RS To determine. g = 2, codebookMode can be set to 1 or 2. g = 4, codebookMode can be set to 1. Here, N g The number of panels that constitute the antenna panel of the terminal device 1 may be sufficient.

[0305] The bitmap parameters ng-n1-n2 can be formed with a0 as LSB and a Ac-1 The bit string a is the MSB Ac-1 ...a1, a0. In the case of a bit value of 0, it may indicate that the PMI report cannot correspond to any precoding associated with this bit. The number of bits Ac may be given by N1O1N2O2. Bit a N2O2l+m Can be based on the amount v l，m , l=0……N1O1-1, m=0……N2O2-1 all precodings are associated. The bitmap parameter ri-Restriction can form a bit string r3……r1, r0 with r0 as LSB and r3 as MSB. i When i∈{0, 1, ..., 3}, the reporting of PMI and RI may not correspond to any precoding associated with layer v=i+1.

[0306] Each PMI value may correspond to a codebook indicator i1 and i2. In the case of the number of layers v=1, i1 may be 1，1 、i 1，2 、i 1，4 In the case of layer number v∈{2, 3, 4}, i1 can be composed of i 1，1 、i 1，2、i 1，3 、i 1，4 Here, v can be associated with the RI value.

[0307] Set codebookMode to 1, N g =2, i 1，4 Can be 1，4，1 When codebookMode is set to 1, N g =4, i 1，4 Can be 1，4，1 、i 1，4，2 、i 1，4，3 When codebookMode is set to 2, i 1，4 Can be 1，4，1 、i 1，4，2 In addition, i2 can be composed of i 2，0 、i 2，1 、i 2，2 part or all of it.

[0308] k1 and k2 can be based on i 1，3 , the number of layers v and the antenna configuration N of the terminal device 1 g , N1, and N2 are determined to be 0 or multiples of O1 and O2. In the case of N2=1, the terminal device 1 can use only i 1，2 = 0, do not report i 1，2 .

[0309] Precoding matrix W (v) l，m，p，n Can be W 1，2，1 l，m，p，n , W 2，2，1 l，m，p，n , W 1，4，1 l，m，p，n , W 2，4，1 l，m，p，n , W 1 ，2，2 l，m，p，n , W 2，2，2 l，m，p，n Here, W 1，2，1 l，m，p，n , W 2，2，1 l，m，p，n , W 1，4，1 l，m，p，n , W 2 ，4，1 l，m，p，n , W 1，2，2 l，m，p，n , W 2，2，2 l，m，p，nIt can be based on the number of CSI-RS ports P CSI-RS And the amount a p 、b n 、u m 、v l，m In addition, the amount can be determined based on part or all of l, m, n, and p, respectively, and l, m, n, and p can also be determined based on part or all of i1 and i2. Here, p can be composed of part or all of p1, p2, and p3, and n can be composed of part or all of n0, n1, and n2.

[0310] Fig. 9 FIG. 1 is a diagram showing an example of a method for applying a precoding matrix according to one embodiment of the present invention. Fig. 9 In , W represents a precoding matrix, and precoding for PUSCH is performed based on the precoding matrix W.

[0311] exist Fig. 9 In the above example, for vectors d1, d2, ... K Perform precoding based on the precoding matrix W and transform it into vectors x1, x2, ... M . Vectors d1, d2, ... d K It can be PUSCH data of layer number K. Vector x1, x2...x M It can be the transmission data of the transmitting side antenna port number M. In this case, from d1, d2...d K To x1, x2, ... x M The transformation of can be obtained by multiplying by the precoding matrix W. The size of the precoding matrix W can be determined based on the number of layers K and the number of antenna ports M on the transmitting side. M Via the transmission channel H as vectors y1, y2, ...y N Received. Vectors y1, y2, ... y N It can be the received data of the number of antenna ports on the receiving side N. The size of the transmission channel H can be determined based on the number of antenna ports M on the transmitting side and the number of antenna ports N on the receiving side.

[0312] In the case of non-codebook transmission, the precoding matrix W can be equal to the unit matrix. In the case of codebook transmission, the precoding matrix W can be given by W=1 in the case of one-layer transmission of a single antenna port. In other cases, it can also be given by the DCI of the scheduling PUSCH or the TPMI index obtained from the upper layer parameters. When the upper layer parameter "txConfig" is not set, the precoding matrix W can be set to 1.

[0313] The antenna configuration of the terminal device 1 can be given based on n1-n2-codebookSubsetRestriction, n1-n2-codebookSubsetRestriction-r16, and n1-n2-codebookSubsetRestriction-r18.

[0314] The terminal device 1 can edit the terminal's capability information. The terminal device 1 can send (transfer) the terminal's capability information. When the terminal device 1 receives UECapabilityEnquiry from the network, it can edit and transfer the terminal's capability information (UE capability information). In addition, the notification of the terminal's capability information can be performed according to the following process.

[0315] In the case that the network requires (additional) UE radio access capability information, the process for the terminal can be started through RRC_CONNECTED. The UE capabilities can be obtained only after the AS is securely activated. The UE capabilities obtained before the AS is securely started may not be transmitted to the CN.

[0316] In the case where the UE-CapabilityRAT-RequestList includes a UE-CapabilityRAT-Request with rat-Type set to nr, the terminal device 1 can set the content of the UECapabilityInformation message as follows. The ue-CapabilityRAT-ContainerList may include a UE-CapabilityRAT-Container of type UE-NR-Capability and rat-Type set to nr. It may also include supportedBandCombinationList, featureSets, and featureSetCombinations.

[0317] In the case where the UE-CapabilityRAT-RequestList includes a UE-CapabilityRAT-Request with rat-Type set to eutra-nr and the UE supports (NG) EN-DC or NE-DC, the terminal device 1 can set the content of the UECapabilityInformation message as follows. The ue-CapabilityRAT-ContainerList may include a UE-CapabilityRAT-Container of type UE-MRDC-Capability and rat-Type set to eutra-nr. It may also include supportedBandCombinationList and featureSetCombinations.

[0318] In the case where the UE-CapabilityRAT-RequestList includes a UE-CapabilityRAT-Request with rat-Type set to eutra and the UE supports E-UTRA, the terminal device 1 may set the content of the UECapabilityInformation message as follows. The ue-CapabilityRAT-ContainerList may include a ue-CapabilityRAT-Container with type UE-EUTRA-Capability and rat-Type set to eutra upon reception.

[0319] In the case where the UE-CapabilityRAT-RequestList includes a UE-CapabilityRAT-Request with rat-Type set to utra-fdd and the UE supports UTRA-FDD, the terminal device 1 may set the content of the UECapabilityInformation message as follows. The UE-CapabilityRAT-Container may include the UE radio access capability for UTRA-FDD with rat-Type set to utra-fdd.

[0320] In case segmentation of the RRC message is enabled based on the received field rrc-SegAllowed and the encoded RRC message is larger than the maximum supported size of the PDCP SDU, the terminal device 1 may set the content of the UECapabilityInformation message as follows: The UL message segment transmission procedure may be started.

[0321] In cases other than the above, the terminal device 1 may set the content of the UECapabilityInformation message as follows: The UECapabilityInformation message may be sent to a lower layer and the process may be terminated at that point in time.

[0322] In the case where the NR or E-UTRA network requests the capabilities of the UE related to NR, EUTRA-NR or EUTRA, the terminal device 1 can call the procedure. The procedure can be called once for each requested rat-Type. The terminal device 1 can ensure that the function set ID is consistent in all three UE capability containers where the network queries the same field with the same value, across function sets, combinations of function sets, and combinations of frequency bands. The UE capability container can be a field of UE-CapabilityRequestFilterNR, UE-CapabilityRequestFilterCommon, and UECapabilityEnquiry messages.

[0323] It is also possible to not support capability queries that do not use frequencyBandListFilter.

[0324] In EN-DC, the gNB may require capabilities of RAT types nr and eutra-nr. In addition, in order to determine the NR UE capabilities for the combination of supported MRDC bands, featureSets within UE-NR-Capability may be used together with featureSetCombinations of UE-MRDC-Capability. Similarly, the eNB may also require capabilities of RAT types eutra and eutra-nr. In addition, featureSetsEUTRA within UE-EUTRA-Capability may be used together with featuresSetCombinations within UE-MRDC-Capability to determine the E-UTRA UE capabilities for the combination of supported MRDC bands. The IDs used by featureSets may be consistent with the IDs referenced by featureSetCombinations in all three containers. Necessary conditions related to consistency may mean that there are no undefined sets of functions and combinations of function sets.

[0325] Depending on message size or list size limitations, in the event that the UE cannot include all function sets and combinations of function sets, which function sets and combinations of function sets are prioritized may depend on the UE's installation.

[0326] The terminal device 1 can make a list of "combination candidates of frequency bands" consisting only of the frequency bands included in the frequencyBandListFilter according to the filtering criteria of capabilityRequestFilterCommon (included). In addition, the frequencyBandListFilter can be given a priority. The setting of the priority can be performed by first including a combination of frequency bands including the first listed frequency band, and then including a combination of the remaining frequency bands including the second listed frequency band. Here, for each frequency band of the combination of frequency bands, the parameters of the frequency band can be made not to exceed the parameters of any one of maxBandwidthRequestedDL, maxBandwidthRequestedUL, maxCarriersRequestedDL, maxCarriersRequestedUL, ca-BandwidthClassDL-EUTRA or ca-BandwidthClassUL-EUTRA received.

[0327] Regarding the combinations of frequency bands included in the list of "Candidates for frequency band combination", when the network (E-UTRA) includes the eutra-nr-only field or the requested rat-Type is eutra, the terminal device 1 can delete the combination of only NR frequency bands from the column of "Candidates for frequency band combination".

[0328] The capability for nr can be requested by the E-UTRA network, but the eutra-nr-only flag can also indicate that the UE-NR-Capability does not include a combination of NR bands. In this case, the above process deletes all combinations of NR dedicated bands from the candidate list, thereby also avoiding the combination of the corresponding function set and the following function set.

[0329] In the case of a combination of backup frequency bands that is deemed to have the same capability as other frequency band combinations included in the list of “Candidate frequency band combinations” or in the case where the combination of backup frequency bands is generated by releasing at least one SCell or the uplink configuration of an SCell, the terminal device 1 may delete the frequency band combination from the list of “Candidate frequency band combinations”.

[0330] Even in the case where only NR functionality is requested by the network, the E-UTRA band number may be included in the frequencyBandListFilter so that all feature sets required for the eutra-nr functionality requested later are included in the UE. At this point in the process, the list of "combination candidates for bands" may include all combinations of NR- and / or E-UTRA-NR bands that are consistent with the filter (frequencyBandListFilter) provided by the NW and (in the case where RAT-Type NR is requested by E-UTRA) consistent with the eutra-nronly flag. This candidate list may be used in the following process to derive the combinations of bands, combinations of feature sets, and feature sets reported in the requested capability container.

[0331] When the requested rat-Type is nr, the terminal device 1 can include as many NR-only band combinations as possible from the list of "band combination candidates" in supportedBandCombinationList starting from the first entry. In addition, when srs-SwitchingTimeRequest is received and SRS carrier switching is supported, srs-SwitchingTimesListNR can be included for the combination of each band. At this time, srs-SwitchingTimeRequested can be set to true.

[0332] In the case where the requested rat-Type is nr, the terminal device 1 may include in featureSetCombinations a feature set combination referenced from a corresponding band combination included in supportedBandCombinationList. In addition, the list of "candidate feature set combinations" referenced from the list of "candidate band combinations" may be compiled by removing entries (rows of feature set combinations) with equal or lower capabilities.

[0333] When the requested rat-Type is nr and uplinkTxSwitchRequest is received, the terminal device 1 can include the NR-only band combination that supports UL TX switching in supportedBandCombinationList-UplinkTxSwitch from the list of "candidate band combinations" as much as possible from the first entry. Afterwards, when srs-SwitchingTimeRequest is received and SRS carrier switching is supported, srs-SwitchingTimesListNR can be included for the combination of each band. At this time, srs-SwitchingTimeRequested can be set to true.

[0334] When the requested rat-Type is nr and uplinkTxSwitchRequest is received, the terminal device 1 may include, in featureSetCombinations, a function set combination referenced from the supported band combinations included in supportedBandCombinationList-UplinkTxSwitch.

[0335] The list of "combination candidates of function sets" may include not only combinations of E-UTRA-NR bands, but also combinations of function sets dedicated to NR. This list can be used to derive a list of NR function sets referenced from the combination of function sets within the UE-NR-Capability and the combination of function sets within the UE-MRDC-Capability container.

[0336] When the requested rat-Type is nr, the terminal device 1 may include the feature set referenced from the "combination of candidate feature sets" in featureSets. In addition, a feature set having a parameter exceeding any one of maxBandwidthRequestedDL, maxBandwidthRequestedUL, maxCarriersRequestedDL, and maxCarriersRequestedUL may be received or excluded.

[0337] When the requested rat-Type is eutra-nr, the terminal device 1 can put as many E-UTRA-NR band combinations as possible from the list of "band combination candidates" into supportedBandCombinationList and / or supportedBandCombinationListNEDC-Only in sequence starting from the first entry. In addition, when srs-SwitchingTimeRequest is received and SRS carrier switching is supported, srs-SwitchingTimesListNR and srs-SwitchingTimesListEUTRA may also be included for the combination of each band. At this time, srs-SwitchingTimeRequested can be set to true.

[0338] When the requested rat-Type is eutra-nr, the terminal device 1 may include the feature set combination referenced by the corresponding band combination included in supportedBandCombinationList in featureSetCombinations according to the previous item. In addition, the list of "candidate feature set combinations" referenced from the list of "candidate band combinations" may be compiled by removing entries (rows of feature set combinations) with the same or lower capabilities.

[0339] When the requested rat-Type is eutra-nr and uplinkTxSwitchRequest is received, the terminal device 1 can include the combination of NR dedicated frequency bands supporting UL TX switching in supportedBandCombinationList-UplinkTxSwitch from the list of "combination candidates of frequency bands" as much as possible from the first entry. In addition, when srs-SwitchingTimeRequest is received and SRS carrier switching is supported, srs-SwitchingTimesListNR can be included with respect to the combination of each frequency band. At this time, srs-SwitchingTimeRequested can be set to true.

[0340] When the requested rat-Type is eutra-nr and uplinkTxSwitchRequest is received, the terminal device 1 may include, in featureSetCombinations, a function set combination referenced from the supported band combinations included in supportedBandCombinationList-UplinkTxSwitch.

[0341] When the requested rat-Type is eutra, the terminal device 1 can compile the list of "feature set combination candidates" referenced from the list of "frequency band combination candidates" by removing entries (rows of feature set combination) having the same or lower capabilities.

[0342] The list of "combination candidates of feature sets" may include combinations of feature sets for E-UTRA-NR bands. The list may be used to derive a list of E-UTRA feature sets referenced from combinations of feature sets within the UE-MRDC-Capability container.

[0343] When the requested rat-Type is eutra, the terminal device 1 may include a feature set referenced from the "combination of candidate feature sets" in featureSetsEUTRA (within UE-EUTRA-Capability). In addition, a feature set with parameters exceeding ca-BandwidthClassDL-EUTRA or ca-BandwidthClassUL-EUTRA may be received or excluded.

[0344] Except in the case where the requested rat-Type is nr and the eutra-nr-only field is included in the network, the terminal device 1 may include the received frequencyBandListFilter in the appliedFreqBandListFilter field of the requested UE capabilities.

[0345] In the case where ue-CapabilityEnquiryExt is included in the network, the terminal device 1 may include the received ue-CapabilityEnquiryExt in the receivedFilters field.

[0346] Terminal device 1 sends first information, receives second information for determining a precoding matrix for PUSCH, determines the precoding matrix based on DCI for scheduling the PUSCH and the second information for determining the precoding matrix for the PUSCH, and performs precoding for the PUSCH based on the precoding matrix. Terminal device 1 may send first information. Terminal device 1 may receive second information. The second information may be used to determine a precoding matrix for PUSCH. The precoding matrix may be used in precoding for PUSCH. The precoding matrix may be determined based on at least DCI and the second information. DCI may schedule PUSCH. Terminal device 1 may perform precoding for PUSCH based on the precoding matrix. Precoding may be performed based on at least the precoding matrix. The second information may be information for calculating the precoding matrix.

[0347] The first information may be capability information of the terminal device 1. The first information may be the number of antenna ports. The first information may be information indicating the number of one or more antenna ports. The first information may be information indicating the number of two antenna ports and the number of panels. The first information may indicate information indicating the number of first antenna ports of the first dimension and the second dimension. The first information may be determined based on the antenna configuration of the terminal device 1. The first information may be UE capability determined based on the antenna configuration of the terminal device 1. The first information may be sent (reported) to the base station device 3 as UE capability. The first information may be assistance information determined based on the antenna configuration of the terminal device 1. The first information may be an RRC parameter determined based on the antenna configuration of the terminal device 1. The first information may be determined based on channel state information. The first information may be UE capability determined based on channel state information. The first information may be assistance information determined based on channel state information. The first information may be an RRC parameter determined based on channel state information. The first information may be the number of antennas (physical antennas) of the terminal device 1. The first information may be information associated with one or both of the number of antennas and the configuration of the antennas.

[0348] The first information may be nrOfAntennaPorts, twoTX-CodebookSubsetRestriction, n1-n2, typeI-SinglePanel-codebookSubsetRestriction-i2 ,typeI-SinglePanel-ri-Restriction,ng-n1-n2,ri-Restriction,codebookMode,n1-n2-codebookSubsetRestriction,typeII-RI-Restriction,portSelectionSamplingSize, typeII-PortSelectionRI-Restriction, phaseAlphabetSize, subbandAmplitude, numberOfBeams, n1-n2-codebookSubsetRestriction-r16, typeII-RI-Restriction-r16, portS The first information may be part or all of N g , part or all of N1, N2, O1, O2, i1, i2, k1, k2, l, m, n, p.

[0349] The second information may be an RRC parameter. The second information may be an RRC parameter for determining a codebook used in precoding for the PUSCH. The second information may be the number of antenna ports. The second information may be information indicating one or more numbers of antenna ports. The second information may be information indicating two numbers of antenna ports and one number of panels. The second information may also indicate information indicating the number of second antenna ports of the first dimension and the second dimension. The number of first antenna ports indicated by the first information may be different from the number of second antenna ports indicated by the second information. For example, the number of second antenna ports may be the same as or less than the number of first antenna ports. The number of first panels indicated by the first information may be different from the number of second panels indicated by the second information. The second information may be determined based on the antenna configuration of the terminal device 1. The second information may be a UE capability determined based on the antenna configuration of the terminal device 1. The second information may be sent (reported) to the base station device 3 as a UE capability. The second information may be auxiliary information determined based on the antenna configuration of the terminal device 1. The second information may be an RRC parameter determined based on the antenna configuration of the terminal device 1. The second information may be determined based on channel state information. The second information may be a UE capability determined based on the channel state information. The second information may be auxiliary information determined based on the channel state information. The second information may be an RRC parameter determined based on the channel state information. The second information may be information for codebook subset restriction. For example, the second information may be information for restricting a codebook subset. For example, the codebook subset may be determined based at least on the second information.

[0350] The second information may be nrOfAntennaPorts, twoTX-CodebookSubsetRestriction, n1-n2, typeI-SinglePanel-codebookSubsetRestriction-i2 ,typeI-SinglePanel-ri-Restriction,ng-n1-n2,ri-Restriction,codebookMode,n1-n2-codebookSubsetRestriction,typeII-RI-Restriction,portSelectionSamplingSize, typeII-PortSelectionRI-Restriction, phaseAlphabetSize, subbandAmplitude, numberOfBeams, n1-n2-codebookSubsetRestriction-r16, typeII-RI-Restriction-r16, portS The second information may be part or all of N g , part or all of N1, N2, O1, O2, i1, i2, k1, k2, l, m, n, p.

[0351] The information for determining the codebook matrix from the codebook subset restricted based on the first information may be indicated by the DCI. The information for determining the codebook matrix from the codebook subset restricted based on the second information may be indicated by the DCI. Here, the information for determining the codebook matrix may be i1, i2. i1, i2 may be indicated by the DCI. Each value of the TPMI field (TPMIfield) in the DCI may be associated with i1, i2.

[0352] The information indicating the number of antenna ports in the first dimension and the second dimension may be N1 and N2. The information indicating the number of antenna ports in the first dimension and the second dimension may also be N g , N1, N2, or part thereof. The information indicating the number of first antenna ports in the first dimension and the second dimension and the information indicating the number of second antenna ports in the first dimension and the second dimension may be the same or different information. The information indicating the number of first antenna ports in the first dimension and the second dimension and the information indicating the number of second antenna ports in the first dimension and the second dimension may be determined by comparison.

[0353] Terminal device 1 receives a PDCCH configured with a DCI for scheduling a PUSCH, sends the PUSCH, sets a first RRC parameter and a second RRC parameter, wherein the first RRC parameter is information for defining a first codebook subset for the PUSCH, and a preliminary second RRC parameter is information for defining a second codebook subset for the PUSCH, and sets a third RRC parameter, wherein the third RRC parameter is information for determining the number of SRS ports of the SRS resources indicated by the DCI, and when the number of SRS ports is less than 4, the precoding matrix for the PUSCH is determined at least based on the DCI and the first codebook subset, and when the number of SRS ports is greater than 4, the precoding matrix for the PUSCH is determined at least based on the DCI and the second codebook subset.

[0354] Terminal device 1 can receive a PDCCH configured with a DCI for scheduling a PUSCH. Terminal device 1 can send the PUSCH. A first RRC parameter and a second RRC parameter can be set. The first RRC parameter can be information for defining a first codebook subset for the PUSCH. The previous second RRC parameter can be information for defining a second codebook subset for the PUSCH. A third RRC parameter can be set. The third RRC parameter can be information for determining the number of SRS ports of the SRS resource indicated by the DCI. When the number of SRS ports is less than 4, the precoding matrix for the PUSCH can be determined based at least on the DCI and the first codebook subset. When the number of SRS ports is greater than 4, the precoding matrix for the PUSCH can be determined based at least on the DCI and the second codebook subset.

[0355] The first RRC parameter may be codebookSubset. The first RRC parameter may correspond to a part or all of fully coherent capability, partially coherent capability, and non-coherent capability. The first RRC parameter may be set to any one of fullyAndPartialAndNonCoherent, partialAndNonCoherent, and nonCoherent.

[0356] The second RRC parameter may be codebookSubset-r18. The second RRC parameter may correspond to part or all of fully coherent capability, partially coherent capability, and incoherent capability. The second RRC parameter may be set to any one of fullyCoherent, partialCoherent, and nonCoherent. The second RRC parameter may be set to any one of fullyCoherent, 4portsPartialCoherent, 2portsPartialCoherent, and nonCoherent.

[0357] The third RRC parameter may be nrOfSRS-Ports. The third RRC parameter may be nrOfAntennaPorts.

[0358] Terminal device 1 receives a PDCCH configured with a DCI for scheduling a PUSCH, sends the PUSCH, and sends capability information of the terminal, wherein the capability information of the terminal is capability information used to define support of an uplink codebook subset by the terminal device, and the capability information of the terminal may include at least information on partial coherence of two transmit antenna ports and partial coherence of four transmit antenna ports.

[0359] Terminal device 1 may receive a PDCCH configured with a DCI for scheduling a PUSCH. Terminal device 1 may send the PUSCH. Terminal device 1 may send capability information of a first terminal. The capability information of the first terminal may be capability information for supporting an uplink codebook subset defined by the terminal device. The capability information of the first terminal may include at least information that two transmit antenna ports are partially coherent and four transmit antenna ports are partially coherent. Terminal device 1 may send capability information of a second terminal. The capability information of the second terminal may be capability information for supporting an uplink codebook subset defined by the terminal device. The capability information of the second terminal may include at least information that two transmit antenna ports are partially coherent and four transmit antenna ports are partially coherent. Terminal device 1 may send one or both of the capability information of the first terminal and the capability information of the second terminal.

[0360] The capability information of the first terminal may be pusch-TransCoherence. The capability information of the first terminal may indicate support for fully coherent. The capability information of the first terminal may also indicate support for partial coherent. The capability information of the first terminal may also indicate support for non coherent. The capability information of the first terminal may also indicate support for 4ports partial coherent. The capability information of the first terminal may also indicate support for 2ports partial coherent. The capability information of the second terminal may be pusch-TransCoherence-r18. The capability information of the second terminal may indicate support for fully coherent. The capability information of the second terminal may also indicate support for partial coherent. The capability information of the second terminal may also indicate support for non coherent. The capability information of the second terminal may also indicate support for 4ports partial coherent. The capability information of the second terminal may also indicate support for 2ports partial coherent.

[0361] Alternatively, the terminal device 1 receives a PDCCH configured with a DCI for scheduling a PUSCH, sends the PUSCH, sets a first RRC parameter and a second RRC parameter, wherein the first RRC parameter is information for determining the number of SRS ports of the SRS resource indicated by the DCI, and the second RRC parameter is information for defining a codebook subset for the PUSCH; when the number of SRS ports is greater than 4 and the second RRC parameter is of a first coherent type, the first codebook type is selected; when the number of SRS ports is greater than 4 and the second RRC parameter is of a second coherent type, the second codebook type is selected; when the number of SRS ports is greater than 4 and the second RRC parameter is of a third coherent type, the third codebook type is selected; when the number of SRS ports is less than 4, the second codebook type is selected; and a precoding matrix for the PUSCH is determined based at least on the DCI and the selected codebook type.

[0362] The terminal device 1 may receive a PDCCH configured with a DCI for scheduling a PUSCH. The terminal device 1 may send the PUSCH. A first RRC parameter and a second RRC parameter may be set. The first RRC parameter may be information for determining the number of SRS ports of the SRS resource indicated by the DCI. The second RRC parameter may be information for defining a codebook subset for the PUSCH. In the case where the number of SRS ports is greater than 4 and the second RRC parameter is of a first coherent type, the first codebook type may be selected. In the case where the number of SRS ports is greater than 4 and the second RRC parameter is of a second coherent type, the second codebook type may be selected. In the case where the number of SRS ports is greater than 4 and the second RRC parameter is of a third coherent type, the third codebook type may be selected. In the case where the number of SRS ports is less than 4, the second codebook type may be selected. The precoding matrix for the PUSCH may be determined based at least on the DCI and the selected codebook type.

[0363] The first RRC parameter may be nrOfSRS-Ports. The first RRC parameter may also be nrOfAntennaPorts.

[0364] The second RRC parameter may be codebookSubset. The second RRC parameter may correspond to a part or all of fully coherent capability, partially coherent capability, and non-coherent capability. The second RRC parameter may be set to any one of fullyAndPartialAndNonCoherent, partialAndNonCoherent, and nonCoherent.

[0365] The second RRC parameter may be codebookSubset-r18. The second RRC parameter may correspond to part or all of fully coherent capability, partially coherent capability, and incoherent capability. The second RRC parameter may be set to any one of fullyCoherent, partialCoherent, and nonCoherent. The second RRC parameter may be set to any one of fullyCoherent, 4portsPartialCoherent, 2portsPartialCoherent, and nonCoherent.

[0366] The first coherence type may be one or both of fullyAndPartialAndNonCoherent and fullyCoherent. The second coherence type may be part or all of partialAndNonCoherent, partialCoherent, 4TxPartialCoherent, and 2TxPartialCoherent. The third coherence type may be nonCoherent.

[0367] The first codebook type may include a part or all of Type I Single-Panel Codebook, Type I Multi-Panel Codebook, Type II Codebook, Type II Port Selection Codebook, Enhanced Type II Codebook, Enhanced Type II Port Selection Codebook, and Further enhanced Type II port selection codebook. The first codebook type may be a formula-based codebook determined at least based on i1 and i2. The first codebook type may be a codebook determined corresponding to i1 and i2 and the value of the TPMI field. The first codebook type may be a codebook based on a downlink codebook.

[0368] The second codebook type may be a table-based codebook determined based on at least part or all of the number of layers, the number of antenna ports, and the transform precoding setting. The second codebook type may be a codebook determined based on multiple TPMIs. The second codebook type may be a codebook based on a combination of multiple codebooks. The second codebook type may be a codebook based on a combination of uplink codebooks used when the number of SRS ports is 4 or less.

[0369] The third codebook type may be a codebook determined based at least on a vector of a selected port. The third codebook type may be a codebook consisting of only values ​​of 0 and 1. The third codebook type may also be a codebook represented by a unit matrix.

[0370] Hereinafter, various device aspects of one aspect of the present embodiment will be described.

[0371] (1) A first scheme of the present invention is a terminal device, comprising: a receiving unit, receiving a PDCCH configured with a DCI for scheduling a PUSCH; and a sending unit, sending the PUSCH, wherein the sending unit sends capability information of the terminal, wherein the capability information of the terminal is capability information for defining support of an uplink codebook subset by the terminal device, and the capability information of the terminal includes at least information on partial coherence of two transmit antenna ports and partial coherence of four transmit antenna ports.

[0372] (2) Moreover, the terminal device receives a first RRC parameter, and when the capability information of the terminal indicates support for full coherence and the first RRC parameter is set to any one of fullyAndPartialAndNonCoherent, fullyCoherent, partialAndNonCoherent, partialCoherent, 4portsPartialCoherent, 2portsPartialCoherent and nonCoherent, a precoding matrix for the PUSCH is determined from a codebook subset corresponding to full coherence, four-port partial coherence, two-port partial coherence and non-coherence, and when the capability information of the terminal indicates support for four-port partial coherence and the first RRC parameter is set to partialAndNonCoherent, partialCoherent, 4portsPar In the case of any one of partialCoherent, 2portsPartialCoherent and nonCoherent, the precoding matrix for the PUSCH is determined from the codebook subset corresponding to four-port partial coherence, two-port partial coherence and non-coherence; in the case that the capability information of the terminal indicates support for two-port partial coherence and the first RRC parameter is set to any one of partialAndNonCoherent, partialCoherent, 2portsPartialCoherent and nonCoherent, the precoding matrix for the PUSCH is determined from the codebook subset corresponding to two-port partial coherence and non-coherence; in the case that the capability information of the terminal indicates support for non-coherence and the first RRC parameter is set to nonCoherent, the precoding matrix for the PUSCH is determined from the codebook subset corresponding to non-coherence.

[0373] (3) Furthermore, the first RRC parameter is determined based on at least part or all of the number of SRS ports and the antenna configuration of the terminal.

[0374] (4) Furthermore, the first RRC parameter is set to any one of fullyAndPartialAndNonCoherent, partialAndNonCoherent, nonCoherent, fullyCoherent, partialCoherent, 4portsPartialCoherent, and 2portsPartialCoherent.

[0375] (5) In addition, a second scheme of the present invention is a base station device, comprising: a receiving unit, which sends a PDCCH configured with a DCI for scheduling a PUSCH; and a receiving unit, which receives the PUSCH, wherein the receiving unit receives capability information of a terminal, wherein the capability information of the terminal is capability information used to define support for an uplink codebook subset by the terminal device, and the base station device grasps the capability information of the terminal, including at least information on partial coherence of two transmitting antenna ports and partial coherence of four transmitting antenna ports.

[0376] (6) Furthermore, the base station apparatus sends a first RRC parameter, and the base station apparatus grasps the following situations: when the capability information of the terminal indicates support for full coherence and the first RRC parameter is set to any one of fullyAndPartialAndNonCoherent, fullyCoherent, partialAndNonCoherent, partialCoherent, 4portsPartialCoherent, 2portsPartialCoherent, and nonCoherent, a precoding matrix for the PUSCH is determined from a codebook subset corresponding to full coherence, four-port partial coherence, two-port partial coherence, and noncoherence; when the capability information of the terminal indicates support for four-port partial coherence and the first RRC parameter is set to any one of partialAndNonCoherent, partialCoherent, 4portsPartialCoherent, 2portsPartialCoherent, and nonCoherent. ortsPartialCoherent, 2portsPartialCoherent and nonCoherent, the precoding matrix for the PUSCH is determined from the codebook subset corresponding to the four-port partial coherence, the two-port partial coherence and the non-coherence; when the capability information of the terminal indicates support for two-port partial coherence and the first RRC parameter is set to any one of partialAndNonCoherent, partialCoherent, 2portsPartialCoherent and nonCoherent, the precoding matrix for the PUSCH is determined from the codebook subset corresponding to the two-port partial coherence and the non-coherence; when the capability information of the terminal indicates support for non-coherence and the first RRC parameter is set to nonCoherent, the precoding matrix for the PUSCH is determined from the codebook subset corresponding to the non-coherence.

[0377] (7) Furthermore, the first RRC parameter is determined based on at least part or all of the number of SRS ports and the antenna configuration of the terminal.

[0378] (8) Furthermore, the first RRC parameter is set to any one of fullyAndPartialAndNonCoherent, partialAndNonCoherent, nonCoherent, fullyCoherent, partialCoherent, 4portsPartialCoherent, and 2portsPartialCoherent.

[0379] (9) In addition, a third scheme of the present invention is a communication method for a terminal device, the communication method comprising the following steps: receiving a PDCCH configured with a DCI for scheduling a PUSCH; and sending the PUSCH, sending capability information of the terminal, the capability information of the terminal is capability information for defining support of an uplink codebook subset by the terminal device, the capability information of the terminal includes at least information about partial coherence of two transmit antenna ports and partial coherence of four transmit antenna ports.

[0380] The program operating in the base station device 3 and the terminal device 1 according to one embodiment of the present invention may be a program (a program that causes a computer to function) that controls a CPU (Central Processing Unit) and the like to realize the functions of the above-mentioned embodiment according to one embodiment of the present invention. Then, the information processed by these devices is temporarily stored in a RAM (Random Access Memory) when processing, and then stored in various ROMs (Read Only Memory) such as a Flash ROM (flash memory) and a HDD (Hard Disk Drive), and is read, modified, and written by the CPU as needed.

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

[0382] It should be noted that the "computer system" mentioned here refers to a computer system built into the terminal device 1 or the base station device 3, and includes hardware such as OS (Operating System), external devices, etc. In addition, "computer-readable recording medium" refers to removable media such as floppy disks, magneto-optical disks, ROMs, CD-ROMs (Compact Disc Read Only Memory), and storage devices such as hard disks built into the computer system.

[0383] Furthermore, "computer-readable recording medium" may also include: a recording medium that stores a program dynamically for a short period of time, such as a communication line when the program is transmitted via a network such as the Internet or a communication line such as a telephone line; and a recording medium that stores a program for a fixed period of time, such as a volatile memory inside a computer system that serves as a server or client in this case. In addition, the above program may be a program for realizing a part of the above functions, and may also be a program that can realize the above functions by combining with a program already recorded in a computer system.

[0384] In addition, the base station device 3 in the above-mentioned embodiment can also be implemented as an aggregate (device group) composed of multiple devices. Each device constituting the device group can have a part or all of the functions or functional blocks of the base station device 3 involved in the above-mentioned embodiment. As a device group, it is sufficient to have all the functions or functional blocks of the base station device 3. In addition, the terminal device 1 involved in the above-mentioned embodiment can also communicate with the base station device as an aggregate.

[0385] In addition, the base station device 3 of the above-mentioned embodiment may be EUTRAN (Evolved Universal Terrestrial Radio Access Network) and / or NG-RAN (NextGenRAN, NR RAN, Next Generation Radio Access Network). In addition, the base station device 3 of the above-mentioned embodiment may also have part or all of the functions of the upper node for eNodeB and / or gNB.

[0386] In addition, part or all of the terminal device 1 and the base station device 3 of the above-mentioned embodiment may be implemented as an LSI, which is typically an integrated circuit, or as a chipset. Each functional block of the terminal device 1 and the base station device 3 may be individually chip-based, or part or all of the functional blocks may be integrated and chip-based. In addition, the method of integrated circuitization is not limited to LSI, and may be implemented by a dedicated circuit or a general-purpose processor. In addition, when a technology for integrated circuitization that replaces LSI emerges with the advancement of semiconductor technology, an integrated circuit based on the technology may also be used.

[0387] In addition, in the above-mentioned 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 fixed or non-movable electronic devices installed indoors and outdoors, such as AV equipment, kitchen equipment, cleaning / washing equipment, air-conditioning equipment, office equipment, vending machines and other life equipment and other terminal devices or communication devices.

[0388] The embodiments of the present invention are described in detail above with reference to the accompanying drawings, but the specific configuration is not limited to the present embodiment, and also includes design changes within the scope of the gist of the present invention. In addition, a scheme of the present invention can be variously modified within the scope indicated by the claims, and the embodiments obtained by appropriately combining the technical solutions disclosed in different embodiments are also included in the technical scope of the present invention. In addition, it also includes a configuration obtained by replacing the elements having the same effect as the elements described in the above embodiments with each other. Industrial Applicability

[0389] One aspect of the present invention can be used for example in a communication system, a communication device (such as a mobile phone device, a base station device, a wireless LAN device, or a sensor device), an integrated circuit (such as a communication chip), a program, or the like. Description of Reference Numerals 1(1A, 1B, 1C): Terminal device 3: Base station device 10, 30: Wireless transceiver 10a, 30a: Wireless transmission unit 10b, 30b: Wireless receiving unit 11, 31: Antenna 12, 32: RF department 13, 33: Baseband 14, 34: Upper processing unit 15, 35: Media access control layer processing unit 16, 36: Radio resource control layer processing unit 91, 92, 93, 94: Search area set 300: Component carrier 301: Main cell 302, 303: Auxiliary cells 700: A collection of resource elements for PSS 710, 711, 712, 713: A set of resource elements for PBCH and DMRS for PBCH 720: A collection of resource elements for SSS 3000: points 3001, 3002: Resource grid 3003, 3004: BWP 3011, 3012, 3013, 3014: Offset 3100, 3200: Public resource block set

Claims

1. A terminal device comprising: a receiving unit, receiving a physical downlink control channel PDCCH configured with downlink control information DCI for scheduling a physical uplink shared channel PUSCH; and a transmitting unit, transmitting the PUSCH, The sending unit sends the capability information of the terminal, The terminal capability information is information for defining support of an uplink codebook subset by a terminal device.

2. The terminal device according to claim 1, wherein: The terminal device also receives a first radio resource control RRC parameter, In a case where the capability information of the terminal indicates a first coherence type, a precoding matrix for the PUSCH is determined from a codebook subset corresponding to a second coherence type.

3. A base station device, comprising: A receiving unit transmits a physical downlink control channel PDCCH configured with downlink control information DCI for scheduling a physical uplink shared channel PUSCH; and A receiving unit receives the PUSCH, The receiving unit receives the capability information of the terminal, The terminal capability information is capability information for defining support of an uplink codebook subset by the terminal device.

4. The base station device according to claim 3, wherein: The base station device also sends a first radio resource control RRC parameter, The base station apparatus understands that, when the capability information of the terminal indicates the first coherence type, a precoding matrix for the PUSCH is determined from a codebook subset corresponding to a second coherence type.

5. A communication method comprising the following steps: receiving a physical downlink control channel PDCCH configured with downlink control information DCI for scheduling a physical uplink shared channel PUSCH; and sending the PUSCH, Send terminal capability information, The terminal capability information is capability information for defining support of an uplink codebook subset by the terminal device.

Images