Terminal equipment, base station equipment, and communication method

Abstract

The present invention comprises a reception unit that receives a DCI format, and a transmission unit that transmits a first PUSCH instance and a second PUSCH instance on the basis of the DCI format. A first resource allocation setting is determined on the basis of at least all or part of a first setting relating to the mapping type of the first instance, second setting for allocating time domain resources for the first instance, and first setting for an additional DMRS for the first instance; and the first resource allocation setting is determined on the basis of at least all or part of the first setting relating to the mapping type of the first instance, second setting for allocating time domain resources for the first instance, and first setting of the additional DMRS for the first instance.

Description

[Technical Field]

[0001] The present invention relates to a terminal device, a base station device, and a communication method. This application claims priority with respect to Japanese Patent Application No. 2020-161577, filed in Japan on September 28, 2020, and the contents of that application are incorporated herein by reference. [Background technology]

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

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

[0004] 3GPP is considering expanding the services supported by NR (Non-Patent Document 2). [Prior art documents] [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 [Overview of the Initiative] [Problems that the invention aims to solve]

[0006] The present invention provides a terminal device for efficient communication, a communication method used in the terminal device, a base station device for efficient communication, and a communication method used in the base station device. [Means for solving the problem]

[0007] (1) A first aspect of the present invention is a terminal device comprising a receiving unit for receiving a DCI format and a transmitting unit for transmitting a first entity of PUSCH and a second entity of PUSCH based on the DCI format, wherein a first resource allocation setting is determined based on at least some or all of a first setting relating to the mapping type of the first entity, a second setting relating to time-domain resource allocation for the first entity, and a first setting relating to additional DMRS for the first entity.

[0008] (2) A second aspect of the present invention is a base station device comprising: a transmitting unit that transmits a DCI format; and a receiving unit that receives a first entity of PUSCH and a second entity of PUSCH based on the DCI format, wherein a first resource allocation setting is determined based on at least some or all of a first setting relating to the mapping type of the first entity, a second setting relating to time-domain resource allocation for the first entity, and a first setting relating to additional DMRS for the first entity.

[0009] (3) A third aspect of the present invention is a communication method used in a terminal device, comprising the steps of receiving a DCI format and transmitting a first entity of PUSCH and a second entity of PUSCH based on the DCI format, wherein a first resource allocation setting is determined based on at least some or all of a first setting relating to the mapping type of the first entity, a second setting relating to time-domain resource allocation for the first entity, and a first setting relating to additional DMRS for the first entity.

[0010] (4) A fourth aspect of the present invention is a communication method comprising the steps of transmitting a DCI format and receiving a first entity of PUSCH and a second entity of PUSCH based on the DCI format, wherein a first resource allocation setting is determined based on at least some or all of a first setting relating to the mapping type of the first entity, a second setting relating to time-domain resource allocation for the first entity, and a first setting relating to additional DMRS for the first entity. [Effects of the Invention]

[0011] According to this invention, terminal devices can communicate efficiently. Furthermore, base station devices can communicate efficiently. [Brief explanation of the drawing]

[0012] [Figure 1] This is a conceptual diagram of a wireless communication system according to one aspect of this embodiment. [Figure 2] This is an example showing the relationship between the subcarrier spacing setting μ, the number of OFDM symbols per slot Nslot symb, and the CP (cyclic prefix) setting according to one aspect of this embodiment. [Figure 3] This figure shows an example of a method for configuring a resource grid according to one aspect of this embodiment. [Figure 4] This figure shows an example configuration of a resource grid 3001 according to one aspect of this embodiment. [Figure 5] This is a schematic block diagram showing an example of the configuration of a base station device 3 according to one aspect of this embodiment. [Figure 6] This is a schematic block diagram showing an example of the configuration of a terminal device 1 according to one aspect of this embodiment. [Figure 7] This figure shows an example of the configuration of an SS / PBCH block according to one aspect of this embodiment. [Figure 8] This figure shows an example of a monitoring opportunity for a search area set according to one aspect of this embodiment. [Figure 9] This figure shows an example of a PUSCH transmission procedure according to one aspect of this embodiment. [Figure 10] This figure shows an example of DMRS configuration for PUSCH according to one aspect of this embodiment. [Figure 11] This figure shows an example of a method for setting up a DMRS according to one aspect of this embodiment. [Figure 12] This figure shows an example of a PUSCH transmission procedure according to one aspect of this embodiment. [Figure 13] This figure shows an example of a method for setting up grouping of PUSCH entities according to one aspect of this embodiment. [Modes for carrying out the invention]

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

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

[0015] In a wireless communication system according to one aspect of this embodiment, at least OFDM (Orthogonal Frequency Division Multiplex) is used. An OFDM symbol is a time-domain unit of OFDM. An OFDM symbol includes at least one or more subcarriers. An 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 may be given by applying transform precoding to CP-OFDM.

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

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

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

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

[0020] A serving cell may consist of at least one downlink component carrier (downlink carrier) and / or one uplink component carrier (uplink carrier). A serving cell may consist of at least two or more downlink component carriers and / or two or more uplink component carriers. Downlink component carriers and uplink component carriers are also referred to as component carriers (carriers).

[0021] For example, one resource grid may be provided for one component carrier. Also, one resource grid may be provided for one component carrier and a subcarrier spacing configuration μ. Here, the subcarrier spacing configuration μ is also referred to as numerology. The resource grid contains N size,μ grid,x N RB sc subcarriers. The resource grid starts from the common resource block N start,μ grid,x The common resource block N start,μ grid,x is also referred to as the reference point of the resource grid. The resource grid contains N subframe,μ symb OFDM symbols. x is a subscript indicating the transmission direction, indicating either the downlink or the uplink. One resource grid is provided for a set of an antenna port p, a subcarrier spacing configuration μ, and a transmission direction x.

[0022] N size,μ grid,x and N start,μ grid,x are provided based at least on the upper layer parameter (CarrierBandwidth). This upper layer parameter is also referred to as the SCS specific carrier. One resource grid corresponds to one SCS specific carrier. One component carrier may include one or more SCS specific carriers. The SCS specific carrier may be included in the system information. For each SCS specific carrier, one subcarrier spacing configuration μ may be provided.

[0023] The subcarrier spacing (SCS: SubCarrier Spacing) Δf is Δf = 2 μIt may also be 15 kHz. For example, the subcarrier spacing setting μ may be 0, 1, 2, 3, or 4.

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

[0025] In a wireless communication system according to one aspect of this embodiment, a time unit T is used to represent the length of time in the time domain. c The following may be used. Time unit T c is, T c = 1 / (Δf max ·N f ) is Δf max = 480kHz. f = 4096. The constant κ is given by κ = Δf max ·N f / (Δf ref N f,ref ) = 64. Δf ref It is 15kHz. f,ref The answer is 2048.

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

[0027] For a certain subcarrier interval setting μ, the number of slots and their indices within the subframe may be given. For example, slot index n μ s In the subframe, the range is from 0 to N subframe,μ slot The values ​​may be given in ascending order as integers in the range of -1. For setting the subcarrier interval μ, the number of slots and their indices in the radio frame may be given. Also, the slot index n μ s,f In wireless frames, the range is 0 to N frame,μ slot The integers may be given in ascending order within the range of -1. slot symb Each OFDM symbol may be contained within a single slot. slot symb = 14

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

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

[0030] Point 3000 is an identifier used to identify a particular 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 interval setting μ1.

[0031] Among the common resource block set 3100, the common resource block containing point 3000 (the block shown by the upward-sloping diagonal line in Figure 3) is also referred to as the reference point of the common resource block set 3100. The reference point of the common resource block set 3100 may also be the common resource block with index 0 in the common resource block set 3100.

[0032] Offset 3011 is the offset from the reference point of the common resource block set 3100 to the reference point of the resource grid 3001. Offset 3011 is indicated by the number of common resource blocks relative to the subcarrier spacing setting μ1. The resource grid 3001 starts from the reference point of the resource grid 3001. size,μ grid1,x Includes several common resource blocks.

[0033] Offset 3013 is the distance from the reference point of resource grid 3001 to the reference point of BWP (BandWidth Part) 3003 of index i1 (N start,μ BWP,i1 This is the offset up to ).

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

[0035] Among the common resource block set 3200, the common resource block containing point 3000 (the block shown by the upward-sloping diagonal line in Figure 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 with index 0 in the common resource block set 3200.

[0036] Offset 3012 is the offset from the reference point of the common resource block set 3200 to the reference point of the resource grid 3002. Offset 3012 is indicated by the number of common resource blocks relative to the subcarrier interval μ2. The resource grid 3002 starts from the reference point of the resource grid 3002. size,μ grid2,x Includes several common resource blocks.

[0037] Offset 3014 is the distance from the reference point of resource grid 3002 to the reference point of BWP3004 of index i2 (N start,μ BWP,i2 This is the offset up to ).

[0038] Figure 4 shows an example configuration of a resource grid 3001 according to one aspect of this embodiment. In the resource grid of Figure 4, the horizontal axis is the OFDM symbol index l sym The vertical axis represents the subcarrier index k. sc Resource grid 3001 is N size,μ grid1,x N RB scincluding sub - carriers and N subframe,μ symb OFDM symbols. In the resource grid, the sub - carrier index k sc and the OFDM symbol index l sym identify a resource which is also called a resource element (RE).

[0039] A resource block (RB) includes N RB sc consecutive sub - carriers. The resource block is a general term for a common resource block, a physical resource block (PRB), and a virtual resource block (VRB). Here, N RB sc = 12.

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

[0041] For a common resource block with a sub - carrier spacing setting μ, in a certain common resource block set, the index is assigned in ascending order from 0 in the frequency domain (indexing). The common resource block with index 0 for a sub - carrier spacing setting μ includes (or collides with, coincides with) point 3000. The index n μ CRB of the common resource block for a sub - carrier spacing setting μ μ CRB satisfies the relationship n sc / N RB sc ) where k scA subcarrier with =0 is a subcarrier that has the same center frequency as the subcarrier corresponding to point 3000.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0063] PSCell is a serving cell included in SCG (Secondary Cell Group). PSCell is a serving cell that is randomly accessed by terminal device 1 during the reconfiguration procedure with synchronization.

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

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

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

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

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

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

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

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

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

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

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

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

[0076] For example, the wireless transmitter 10a may generate and transmit a PRACH baseband signal. For example, the wireless transmitter 10a may generate and transmit a PUCCH baseband signal. The wireless transmitter 10a may generate and transmit a PUSCH baseband signal. For example, the wireless transmitter 10a may generate and transmit a PUCCH DMRS baseband signal. For example, the wireless transmitter 10a may generate and transmit a PUSCH DMRS baseband signal. For example, the wireless transmitter 10a may generate and transmit a UL PTRS baseband signal. For example, the wireless transmitter 10a may generate and transmit an SRS baseband signal.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0093] HARQ-ACK information may include at least a HARQ-ACK corresponding to a transport block (or TB: Transport block, MAC PDU: Medium Access Control Protocol Data Unit, DL-SCH: Downlink-Shared Channel, UL-SCH: Uplink-Shared Channel, PDSCH: Physical Downlink Shared Channel, PUSCH: Physical Uplink Shared Channel). A HARQ-ACK may indicate an ACK (acknowledgement) or NACK (negative-acknowledgement) corresponding to a transport block. An ACK may indicate that the decoded transport block has been successfully completed. A NACK may indicate that the decoded transport block has not been successfully completed. HARQ-ACK information may include a HARQ-ACK codebook containing one or more HARQ-ACK bits.

[0094] The correspondence between HARQ-ACK information and a transport block may also mean that the HARQ-ACK information and the PDSCH used to transmit the transport block correspond.

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

[0096] A scheduling request may be used to request a PUSCH (or UL-SCH) resource for a new transmission. The scheduling request bit may be used to indicate either a positive SR or a negative SR. When the scheduling request bit indicates a positive SR, it is also referred to as "a positive SR is sent." A positive SR may indicate that terminal device 1 is requesting a PUSCH (or UL-SCH) resource for a new transmission. A positive SR may indicate that the scheduling request is triggered by a higher layer. A positive SR may be sent when the higher layer instructs it to send a scheduling request. When the scheduling request bit indicates a negative SR, it is also referred to as "a negative SR is sent." A negative SR may indicate that terminal device 1 is not requesting a PUSCH (or UL-SCH) resource for a new transmission. A negative SR may indicate that the scheduling request is not triggered by a higher layer. A negative SR may be sent if the higher layer does not instruct it to send a scheduling request.

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

[0098] Channel status information may be provided at least based on receiving a physical signal (e.g., CSI-RS) used for channel measurement. Channel status information may be selected by terminal device 1 at least based on receiving a physical signal used for channel measurement. Channel measurement may include interference measurement.

[0099] PUCCH may support the PUCCH format. PUCCH may be a set of resource elements used to transmit the PUCCH format. PUCCH may contain the PUCCH format.

[0100] PUSCH may be used to transmit transport blocks and / or uplink control information. PUSCH may be used to transmit transport blocks corresponding to UL-SCH and / or uplink control information. PUSCH may be used to transmit transport blocks and / or uplink control information. PUSCH may be used to transmit transport blocks corresponding to UL-SCH and / or uplink control information. Transport blocks may be placed on PUSCH. Transport blocks corresponding to UL-SCH may be placed on PUSCH. Uplink control information may be placed on PUSCH. Terminal device 1 may transmit a PUSCH containing transport blocks and / or uplink control information. Base station device 3 may receive a PUSCH containing transport blocks and / or uplink control information.

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

[0102] For a given PRACH opportunity, 64 random access preambles are defined. Each random access preamble is a cyclic shift C of the PRACH sequence. v , and identified (determined, given) based at least on the sequence index u for the PRACH sequence. Each of the identified 64 random access preambles may be indexed.

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

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

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

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

[0107] PUSCH may be estimated from the DMRS for that PUSCH. In other words, the propagation path of PUSCH may be estimated from the DMRS for that PUSCH.

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

[0109] The transmission of a PUCCH and the transmission of a DMRS for that PUCCH may be indicated (or triggered) by a single DCI format. The resource element mapping of a PUCCH and / or the resource element mapping of a DMRS for that PUCCH may be given by a single PUCCH format. A PUCCH and a DMRS for that PUCCH may be collectively referred to as a PUCCH. Sending a PUCCH may be equivalent to sending a PUCCH and a DMRS for that PUCCH.

[0110] PUCCH may be estimated from the DMRS for that PUCCH. In other words, the propagation path of PUCCH may be estimated from the DMRS for that PUCCH.

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

[0112] A PBCH may be used to transmit an MIB (Master Information Block) and / or physical layer control information. A PBCH may be transmitted to deliver, transmit, or convey an MIB and / or physical layer control information. A BCH may be mapped onto the PBCH. Terminal device 1 may receive a PBCH on which an MIB and / or physical layer control information is mapped. Base station device 3 may transmit a PBCH on which an MIB and / or physical layer control information is mapped. The physical layer control information is also referred to as the PBCH payload or timing-related PBCH payload. An MIB may contain one or more higher-layer parameters.

[0113] The physical layer control information includes 8 bits. The physical layer control information may include at least some or all of the following 0A to 0D. 0A) Wireless frame bit 0B) Half Wireless Frame (Half System Frame, Half Frame) Bit 0C) SS / PBCH Block Index Bit 0D) Subcarrier offset bit

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

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

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

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

[0118] A PDCCH may be used to transmit Downlink Control Information (DCI). A PDCCH may be transmitted to deliver, transmit, or convey Downlink Control Information. Downlink Control Information may be mapped onto a PDCCH. Terminal device 1 may receive a PDCCH on which Downlink Control Information has been mapped. Base station device 3 may transmit a PDCCH on which Downlink Control Information has been mapped.

[0119] Downlink control information may be compatible with the DCI format. Downlink control information may be included in the DCI format. Downlink control information may be placed in each field of the DCI format.

[0120] DCI format 0_0, DCI format 0_1, DCI format 1_0, and DCI format 1_1 are DCI formats that each contain a different set of fields. Uplink DCI format is a general term for DCI format 0_0 and DCI format 0_1. Downlink DCI format is a general term for DCI format 1_0 and DCI format 1_1.

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

[0122] A DCI format-specific field may indicate whether the DCI format containing the DCI format-specific field is an uplink DCI format or a downlink DCI format. The DCI format-specific field in DCI format 0_0 may indicate 0 (or indicate that DCI format 0_0 is an uplink DCI format).

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

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

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

[0126] The MCS field in DCI format 0_0 may be used to indicate at least some or all of the modulation scheme and / or target coding rate for the PUSCH. The target coding rate may be the target coding rate for the transport block of the PUSCH. The transport block size (TBS) of the PUSCH may be given based at least some or all of the target coding rate and the modulation scheme for the PUSCH.

[0127] DCI format 0_0 does not have to include fields used in a CSI request. In other words, a CSI is not required to be requested using DCI format 0_0.

[0128] DCI format 0_0 does not have to include a carrier indicator field. In other words, the uplink component carrier on which a PUSCH scheduled by DCI format 0_0 is located may be the same as the uplink component carrier on which a PDCCH containing DCI format 0_0 is located.

[0129] DCI format 0_0 does not have to include a BWP field. In other words, the uplink BWP on which a PUSCH scheduled by DCI format 0_0 is located may be the same as the uplink BWP on which a PDCCH containing DCI format 0_0 is located.

[0130] DCI format 0_1 ​​is used at least for scheduling PUSCHs (placed in a given cell) within a given cell. DCI format 0_1 ​​consists of at least some or all of the fields 2A through 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

[0131] The DCI format specific field included in DCI format 0_1 ​​may indicate 0 (or it may indicate that DCI format 0_1 ​​is an uplink DCI format).

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

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

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

[0135] If DCI format 0_1 ​​includes a BWP field, the BWP field may be used to indicate the uplink BWP on which the PUSCH is located. If DCI format 0_1 ​​does not include a BWP field, the uplink BWP on which the PUSCH is located may be the same as the uplink BWP on which the PDCCH, which includes DCI format 0_1 ​​used for scheduling the PUSCH, is located. If the number of uplink BWPs set for terminal device 1 on an uplink component carrier is two or more, the number of bits in the BWP field included in DCI format 0_1 ​​used for scheduling the PUSCH located on that uplink component carrier may be one or more. If the number of uplink BWPs set for terminal device 1 on an uplink component carrier is one, the number of bits in the BWP field included in DCI format 0_1 ​​used for scheduling the PUSCH located on that uplink component carrier may be zero (or the DCI format 0_1 ​​used for scheduling the PUSCH located on that uplink component carrier may not include a BWP field).

[0136] The CSI request field is used, at a minimum, to direct the CSI report.

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

[0138] DCI format 1_0 is used for scheduling PDSCHs (placed in a given cell) within a given cell. DCI format 1_0 consists of at least some or all of 3A through 3F. 3A) DCI Format Specific Fields 3B) Frequency Domain Resource Allocation Field 3C) Time Domain Resource Allocation Field 3D) MCS Field 3E) PDSCH to HARQ feedback timing indicator field 3F) PUCCH resource indicator field

[0139] The DCI format specific field included in DCI format 1_0 may indicate 1 (or indicate that DCI format 1_0 is a downlink DCI format).

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

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

[0142] The MCS field included in DCI format 1_0 may be used to indicate at least part or all of the modulation scheme and / or target coding rate for the PDSCH. The target coding rate may be the target coding rate for the transport block of the PDSCH. The transport block size (TBS) of the PDSCH may be given based at least part or all of the target coding rate and the modulation scheme for the PDSCH.

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

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

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

[0146] DCI format 1_0 does not have to include a BWP field. In other words, the downlink BWP on which a PDSCH scheduled by DCI format 1_0 is located may be the same as the downlink BWP on which a PDCCH containing DCI format 1_0 is located.

[0147] DCI format 1_1 is used for scheduling PDSCHs in (or placed in) a cell. DCI format 1_1 consists of at least some or all of 4A through 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 Indicator Field 4G)PUCCH resource instruction field 4H) BWP Field 4I) Carrier Indicator Field

[0148] The DCI format specific field included in DCI format 1_1 may indicate 1 (or indicate that DCI format 1_1 is a downlink DCI format).

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

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

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

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

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

[0154] If DCI format 1_1 includes a BWP field, the BWP field may be used to indicate the downlink BWP on which the PDSCH is located. If DCI format 1_1 does not include a BWP field, the downlink BWP on which the PDSCH is located may be the same as the downlink BWP on which the PDCCH is located, which includes DCI format 1_1 used for scheduling the PDSCH. If the number of downlink BWPs set up on terminal device 1 in a downlink component carrier is two or more, the number of bits in the BWP field included in DCI format 1_1 used for scheduling the PDSCH located in that downlink component carrier may be one or more. If the number of downlink BWPs set up on terminal device 1 in a downlink component carrier is one, the number of bits in the BWP field included in DCI format 1_1 used for scheduling the PDSCH located in that downlink component carrier may be zero (or the DCI format 1_1 used for scheduling the PDSCH located in that downlink component carrier may not include a BWP field).

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

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

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

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

[0159] Figure 7 shows an example of the configuration of an SS / PBCH block according to one aspect of this embodiment. In Figure 7, the horizontal axis is the time axis (OFDM symbol index l sym The vertical axis represents the frequency domain. The shaded blocks represent sets of resource elements for PSS. The grid lines represent sets of resource elements for SSS. The horizontal lines represent sets of resource elements for PBCH and DMRS for the PBCH (DMRS related to the PBCH, DMRS contained in the PBCH, and DMRS corresponding to the PBCH).

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

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

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

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

[0164] The set of antenna ports for a DMRS for a PDSCH (DMRS associated with a PDSCH, DMRS included in a PDSCH, DMRS corresponding to a PDSCH) may be given based on the set of antenna ports for the PDSCH. In other words, the set of antenna ports for a DMRS for a PDSCH may be the same as the set of antenna ports for the PDSCH.

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

[0166] A PDSCH may be inferred from the DMRS for that PDSCH. In other words, the propagation path of a PDSCH may be inferred from the DMRS for that PDSCH. If the set of resource elements on which a PDSCH symbol is transmitted and the set of resource elements on which the DMRS symbol for that PDSCH is transmitted are in the same Precoding Resource Group (PRG), then the PDSCH on which the PDSCH symbol is transmitted at a given antenna port may be inferred from the DMRS for that PDSCH.

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

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

[0169] BCH (Broadcast Channel), UL-SCH (Uplink-Shared Channel), and DL-SCH (Downlink-Shared Channel) are transport channels. Channels used in the MAC layer are called transport channels. The unit of transport channel used in the MAC layer is also called a transport block (TB) or MAC PDU (Protocol Data Unit). In the MAC layer, HARQ (Hybrid Automatic Repeat request) control is performed for each transport block. A transport block is the unit of data that the MAC layer delivers to the physical layer. In the physical layer, transport blocks are mapped to codewords, and modulation processing is performed for each codeword.

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

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

[0172] An RRC message contains one or more RRC parameters (information elements). For example, an RRC message may contain an MIB. An RRC message may also contain system information. Furthermore, an RRC message may contain a message corresponding to CCCH. An RRC message may also contain a message corresponding to DCCH. An RRC message containing a message corresponding to DCCH is also called an individual RRC message.

[0173] BCCH in the logical channel may be mapped to BCH or DL-SCH in the transport channel. CCCH in the logical channel may be mapped to DL-SCH or UL-SCH in the transport channel. DCCH in the logical channel may be mapped to DL-SCH or UL-SCH in the transport channel.

[0174] UL-SCH in the transport channel may be mapped to PUSCH in the physical channel. DL-SCH in the transport channel may be mapped to PDSCH in the physical channel. BCH in the transport channel may be mapped to PBCH in the physical channel.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0202] In Figure 8, the blocks indicated by grid lines represent search area set 91, the blocks indicated by diagonal lines rising to the right represent search area set 92, the blocks indicated by diagonal lines rising to the left represent search area set 93, and the blocks indicated by horizontal lines represent search area set 94.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0216] Figure 9 shows an example of the transmission procedure of PUSCH according to one aspect of this embodiment. In Figure 9, the horizontal axis represents the time domain. The grid on the line representing the time domain indicates the boundaries of the slots. Here, in the upper part of Figure 9, the first slot is designated as slot #0. The shaded blocks shown below the line representing the time domain indicate that the time domain corresponding to that shaded block is the downlink domain. The vertical blocks shown below the line representing the time domain indicate that the time domain corresponding to that vertical block is the uplink domain. The lower part of Figure 9 is an extended view of a portion of slots #3 and #4.

[0217] In Figure 9, PUSCH is assigned to slots #3 and #4. Here, 9001 is an instance of PUSCH assigned to OFDM symbols #12 and #13 in slot #3. Also, 9002 is an instance of PUSCH assigned to OFDM symbols #0 and #5 in slot #4. Also, 9003 is an instance of PUSCH assigned to OFDM symbols #6 through #13 in slot #4. In this way, dividing and assigning PUSCH so that instances of PUSCH do not cross slot boundaries is preferable in some scenarios. Here, for example, an instance of PUSCH may be a single PUSCH. Also, for example, an instance of PUSCH may be a repeatation of PUSCH. For example, the mapping of the resource elements of the modulation symbols may be performed for each instance of PUSCH. For example, the size of the transport block may be determined for each instance of PUSCH. For example, the placement of DMRS for PUSCH may be determined on a per-PUSCH basis.

[0218] For example, the DMRS for PUSCH may be determined based at least in part on some or all of the mapping type of PUSCH, the setting of Additional DMRS, and the number of OFDM symbols included in the PUSCH entity. Here, the mapping type of PUSCH is also referred to as the setting of front loaded DMRS or the mapping type of DMRS.

[0219] FIG. 10 is a diagram showing an example of the setting of DMRS for PUSCH according to one aspect of the present embodiment. In FIG. 10, l d indicates the number of OFDM symbols included in the PUSCH entity. Also, the time domain positions of DMRS are set for the combination of l d , the mapping type of PUSCH, and the setting of dmrs-AdditionalPosition. Here, the mapping type of PUSCH is a setting indicating either type A (PUSCH mapping type A) or type B (PUSCH mapping type B). Also, the setting of Additional DMRS is a setting indicating any one of pos0, pos1, pos2, pos3.

[0220] For example, in FIG. 10, when l d is 2, the mapping type of PUSCH is type B, and the setting of Additional DMRS is pos0, the index of the OFDM symbol in which the DMRS for PUSCH is arranged is l0. Also, when l d is 6, the mapping type of PUSCH is type B, and the setting of Additional DMRS is pos2, the indexes of the OFDM symbols in which the DMRS for PUSCH is arranged are l0 and 4. Also, when l d is 8, the mapping type of PUSCH is type A, and the setting of Additional DMRS is pos1, the indexes of the OFDM symbols in which the DMRS for PUSCH is arranged are l0 and 7.

[0221] Here, when the mapping type of PUSCH is type A, the reference point of the index of the OFDM symbol where DMRS for PUSCH is placed is the OFDM symbol at the start of the slot. That is, when the mapping type of PUSCH is type A, in the determination of the OFDM symbol where DMRS for PUSCH is placed, it is assumed that the OFDM symbol at the start of the slot is index 0.

[0222] Also, when the mapping type of PUSCH is type B, the reference point of the index of the OFDM symbol where DMRS for PUSCH is placed is the OFDM symbol at the start of PUSCH. That is, when the mapping type of PUSCH is type B, in the determination of the OFDM symbol where DMRS for PUSCH is placed, it is assumed that the OFDM symbol at the start of PUSCH is index 0.

[0223] For example, the setting regarding the mapping type of PUSCH may be set for each PUSCH entity. That is, for example, for PUSCH entity 9001, the mapping type of PUSCH may be type B, and for PUSCH entities 9002 and 9003, the mapping type of PUSCH may be type A.

[0224] For example, the setting regarding the mapping type of PUSCH may be common for PUSCH entities. For example, when a plurality of PUSCH entities are scheduled by one DCI format, the mapping type of PUSCH for the plurality of PUSCH entities may be common.

[0225] For example, the setting of additional symbols may be set for each PUSCH entity. That is, for example, for PUSCH entity 9001, the setting of additional symbols may be pos0, for PUSCH entity 9002, the setting of additional symbols may be pos1, and for PUSCH entity 9003, the setting of additional symbols may be pos2.

[0226] Figure 11 shows an example of a DMRS configuration method according to one aspect of this embodiment. The time domain configuration 11000 shown in Figure 11 includes N multiple push configurations 11001 to 1100N, where N is an integer of 1 or more. For example, N may be 1.

[0227] The base station device 3 transmits a signal including the time domain setting 11000 to the terminal device 3. The terminal device 1 receives the signal including the time domain setting 11000. Here, the time domain setting 11000 may be a parameter of a higher layer. For example, the time domain setting 11000 may be included in the RRC signaling.

[0228] From among the N multi-PUSCH settings included in the time domain setting 11000, one may be selected based on the value of a field included in the DCI format. The base station device 3 may instruct the terminal device 1 to use one multi-PUSCH setting by setting the value of the time domain resource allocation field included in the DCI format used for scheduling PUSCH to a predetermined value. The terminal device 1 may detect the DCI format and execute a PUSCH transmission using the instructed multi-PUSCH setting.

[0229] For example, if N is 1, the number of bits in the time domain resource allocation field in the DCI format may be 0. For example, if N is 1, terminal device 1 may perform a PUSCH transmission using one multi-PUSCH setting that is configured.

[0230] Each of the N multi-PUSCH configurations may contain one or more PUSCH instance configurations. In Figure 11, multi-PUSCH configuration 11001 contains X PUSCH instance configurations 11011 to 110X1. Also, multi-PUSCH configuration 1100N contains Y PUSCH instance configurations 1101N to 110YN.

[0231] For example, each PUSCH entity setting may include at least some or all of the following elements E1 through E5: E1) PUSCH time-domain resource configuration E2) Settings for PUSCH mapping type E3) Additional DMRS configuration E4) Settings regarding the presence or absence of DMRS E5) Settings related to the time and location of DMRS

[0232] The time-domain resource settings for PUSCH may also be settings related to the time-domain resources of PUSCH. Here, the settings related to the time-domain resources of PUSCH may be used to determine at least one or both of the index of the first OFDM symbol of PUSCH, or the number of OFDM symbols of PUSCH.

[0233] The setting for PUSCH's mapping type may indicate whether PUSCH's mapping type is type A or type B.

[0234] The additional DMRS configuration may also indicate whether the additional DMRS is configured as pos0, pos1, pos2, or pos3.

[0235] The setting regarding the presence or absence of a DMRS may be used, at a minimum, to determine whether or not a DMRS is to be provided for a PUSCH. For example, if it is determined that a DMRS will not be provided for a PUSCH, that PUSCH may be associated with the DMRS of other PUSCHs.

[0236] The time position setting of the DMRS may be used to determine the time position of the DMRS for PUSCH. For example, the time position setting of the DMRS may be determined as an offset of the time position of the DMRS.

[0237] For example, the time position offset of DMRS is determined by the mapping type of PUSCH and the number of OFDM symbols in PUSCH. d The offset to the index of the OFDM symbol in which the DMRS for PUSCH is located, which is determined based on at least one or both of the following, may be indicated. For example, if the index of the OFDM symbol in which the DMRS for PUSCH is located is determined to be x, x+3, then the time position of the DMRS actually transmitted will be x+l o x+3+l o , or it may be. Here, l o This is the time position offset of the DMRS.

[0238] For example, the time position offset of a DMRS may be an offset relative to a front-loaded DMRS. Alternatively, the time position offset of a DMRS may be an offset relative to an additional DMRS.

[0239] For example, the setting for the time position of the DMRS may be a setting that indicates the time position of the DMRS. For example, the time position of the DMRS may be indicated by a bitmap or the like.

[0240] The terminal device 1 may determine one multi-PUSCH configuration based on the detection of the DCI format and transmit the PUSCH. Here, the terminal device 1 may transmit the entity of the PUSCH based on each of the PUSCH entity configurations included in the one multi-PUSCH configuration. For example, when the multi-PUSCH configuration 11001 is determined as one multi-PUSCH configuration, the terminal device 1 may transmit X entities of the PUSCH. For example, the first PUSCH entity among the X PUSCH entities may be configured based on the PUSCH entity configuration 11011. Also, the nth PUSCH entity among the X PUSCH entities may be configured based on the PUSCH entity configuration 1101n. Here, n is an integer of 1 or more.

[0241] For example, 11011a may be any one of elements E1 to E5. For example, 11011b may be any one of elements E1 to E5. For example, 110X1a may be any one of elements E1 to E5. For example, 110X1b may be any one of elements E1 to E5. For example, 1101Na may be any one of elements E1 to E5. For example, 1101Nb may be any one of elements E1 to E5. For example, 110YNa may be any one of elements E1 to E5. For example, 110YNb may be any one of elements E1 to E5.

[0242] Here, the time-domain resources for each of the X PUSCH entities may be arranged continuously or discontinuously.

[0243] Figure 12 shows an example of a PUSCH transmission procedure according to one aspect of this embodiment. In Figure 12, 9001, 9002, 9003, 12001, 12002, and 12003 are PUSCH entities scheduled using a single DCI format. As shown in Figure 12, the resources in each time domain of a PUSCH entity scheduled using a single DCI format may be arranged discontinuously. For example, the DMRS for 9001, 9002, and 9003 may be shared, but the DMRS for 9001 and 12001 may not be shared.

[0244] Here, the sharing of the DMRS of 9001 and 9002 may mean that the DMRS of 9001 transmitted at a certain antenna port can demodulate the channel of 9002 transmitted at that antenna port.

[0245] For example, if multiple PUSCH entities are transmitted using a single DCI format, sequentially placed PUSCH entities may be grouped together. For instance, in Figure 12, 9001, 9002, and 9003 may be grouped together. Similarly, 12001, 12002, and 12003 may be grouped together. The DMRS for each of the grouped PUSCH entities may be shared.

[0246] For example, the grouping of PUSCH entities may be determined based on the configuration of the uplink region. For example, PUSCH entities that are included in consecutive uplink regions may be grouped. For example, 9001, 9002, and 9003 may be grouped based on the fact that they are included in one consecutive uplink region. Alternatively, 12001, 12002, and 12003 may be grouped based on the fact that they are included in one consecutive uplink region.

[0247] For example, the grouping of PUSCH entities may be set by parameters in a higher layer.

[0248] Figure 13 shows an example of a method for setting up grouping of PUSCH entities according to one aspect of this embodiment. In Figure 13, a multi-PUSCH setting 11001 is shown. Other multi-PUSCH settings may be set up in the same way as multi-PUSCH setting 11001.

[0249] In Figure 13, the multi-PUSCH configuration 11001 includes Z group configurations 13001 to 1300Z. Each of the Z group configurations includes one or more PUSCH entity configurations. Here, two PUSCH entities 11011 and 11012, corresponding to each of the two PUSCH entity configurations included in group configuration 13001, are grouped together. Similarly, two PUSCH entities 1101v and 1101w, corresponding to at least two PUSCH entity configurations included in group configuration 1300Z, are grouped together.

[0250] In this way, suitable communication can be achieved by setting the time position of the DMRS for each PUSCH entity. For example, an offset for the time position of the front-load DMRS may be set for each PUSCH entity. Alternatively, an offset for the time position of additional DMRS may be set for each PUSCH entity. Furthermore, it may be set whether or not to deploy a DMRS for each PUSCH entity. Additionally, the time placement of the DMRS may be set for each PUSCH entity.

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

[0252] (1) In order to achieve the above objectives, aspects of the present invention have taken the following measures. Specifically, a first aspect of the present invention is a terminal device comprising: a receiving unit that receives a DCI format; and a transmitting unit that transmits a first entity of PUSCH and a second entity of PUSCH based on the DCI format, wherein the first resource allocation setting is determined based on at least some or all of a first setting relating to the mapping type of the first entity, a second setting relating to the time domain resource allocation for the first entity, and a first setting relating to additional DMRS for the first entity.

[0253] (2) A second aspect of the present invention is a base station device comprising: a transmitting unit that transmits a DCI format; and a receiving unit that receives a first entity of PUSCH and a second entity of PUSCH based on the DCI format, wherein the first resource allocation setting is determined based on at least some or all of a first setting relating to the mapping type of the first entity, a second setting relating to time-domain resource allocation for the first entity, and a first setting relating to additional DMRS for the first entity.

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

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

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

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

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

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

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

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

[0262] While embodiments of this invention have been described in detail above with reference to the drawings, the specific configuration is not limited to these embodiments, and design modifications and the like that do not depart from the gist of this invention are also included. Furthermore, the present invention can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of this invention. In addition, configurations in which elements described in each of the above embodiments that produce similar effects are substituted for each other are also included. [Industrial applicability]

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

[0264] 1 (1A, 1B, 1C) Terminal device 3 Base station equipment 10, 30 Wireless Transceiver Unit 10a, 30a Wireless Transmitter 10aa Channel coding / scrambling / modulation section 10ab Layer Mapping Section 10ac pre-recording section 10ad Time signal generation unit 10ae Spatial Filter Section 10af antenna section 10b, 30b Wireless Receiver 10ba channel decoding / descrambling / demodulation unit 10bb Layer Demapping Section 10bc channel demodulation unit 10d frequency signal generation unit 10be spatial filter section 10bf antenna section 11, 31 Antenna section 12, 32 RF section 13, 33 Baseband section 14, 34 Upper Layer Processing Unit 15, 35 Media Access Control Layer Processing Unit 16, 36 Wireless Resource Control Layer Processing Unit 91, 92, 93, 94 Search area set 300 Component Carrier 301 Primary Cell 302, 303 Secondary Cells 1600 Spatial Filter Set 1700 Codebook Set 3000 points 3001, 3002 Resource Grid 3003, 3004 BWP 3011, 3012, 3013, 3014 Offset 3100, 3200 Common Resource Block Sets 9001, 9002, 9003, 12001, 12002, 12003 The actual PUSCH 11000 Time Domain Setting 11001, 1100N Multi-PUSCH settings 11011, 110X1, 1101N, 110YN, 11012, 1101v, 1101w PUSCH physical settings 11011a, 11011b, 110X1a, 110X1b, 1101Na, 1101Nb, 110YNa, 110YNb, 11012a, 11012b, 1101va, 1101vb, 1101wa, 1101wb elements 13001, 13002 Group Settings

Claims

1. A receiving unit that receives one downlink control information (DCI) format, The system comprises a transmission unit that transmits a plurality of PUSCH entities scheduled according to the aforementioned DCI format, In relation to the plurality of PUSCH entities, a first PUSCH entity setting among the plurality of PUSCH entity settings defined based on the DCI format is applied to the first PUSCH entity among the plurality of PUSCH entities. The second PUSCH entity setting among the plurality of PUSCH entity settings is applied to the second PUSCH entity among the plurality of PUSCH entities. The first PUSCH entity setting and the second PUSCH entity setting each include the setting of different reference signals (DMRS), Terminal device.

2. A transmitter unit that transmits one downlink control information (DCI) format, The system comprises a receiving unit that receives a plurality of PUSCH entities scheduled according to the aforementioned DCI format, In relation to the plurality of PUSCH entities, a first PUSCH entity setting among the plurality of PUSCH entity settings defined based on the DCI format is applied to the first PUSCH entity among the plurality of PUSCH entities. The second PUSCH entity setting among the plurality of PUSCH entity settings is applied to the second PUSCH entity among the plurality of PUSCH entities. The first PUSCH entity setting and the second PUSCH entity setting each include the setting of different reference signals (DMRS), Base station equipment.

3. A communication method used in terminal devices, The steps include receiving one downlink control information (DCI) format, The process includes the step of transmitting a plurality of PUSCH entities scheduled in the aforementioned DCI format, In relation to the plurality of PUSCH entities, a first PUSCH entity setting among the plurality of PUSCH entity settings defined based on the DCI format is applied to the first PUSCH entity among the plurality of PUSCH entities. The second PUSCH entity setting among the plurality of PUSCH entity settings is applied to the second PUSCH entity among the plurality of PUSCH entities. The first PUSCH entity setting and the second PUSCH entity setting each include the setting of different reference signals (DMRS), Communication method.

Images