JP7627229B2 - Terminal device, base station device, and method - Google Patents

Description

The present invention relates to a terminal device, a base station device, and a method.
This application claims priority to Japanese Patent Application No. 2019-215375, filed in Japan on November 28, 2019, the contents of which are incorporated herein by reference.

A radio access method and a radio network for cellular mobile communication (hereinafter referred to as "LTE (Long Term Evolution)" or "EUTRA (Evolved Universal Terrestrial Radio Access)") are being studied in the ^3rd Generation Partnership Project (3GPP). In LTE, a base station device may be referred to as an evolved NodeB (eNodeB), and a terminal device may be referred to as a User Equipment (UE). LTE is a cellular communication system in which a plurality of areas covered by a base station device are arranged in the form of cells. One base station device may manage one or more serving cells.

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

Furthermore, studies are being conducted on coverage enhancement to expand and improve the communication area and communication scenarios of wireless communication methods and/or wireless communication systems that apply NR Radio Access Technology (NR-RAT) (Non-Patent Document 2).

"New SID proposal: Study on New Radio Access Technology", RP-160671, NTT DOCOMO, 3GPP TSG RAN Meeting #71, Goteborg, Sweden, 7th - 10th March, 2016. "Summary of email discussion on NR coverage enhancement", RP-191886, China Telecommunication Corp., 3GPP TSG RAN Meeting #85, Newport Beach, USA, 16th - 19th September, 2019.

One aspect of the present invention provides a terminal device for efficient communication, a method used in the terminal device, a base station device, and a method used in the base station device.

(1) A first aspect of the present invention is a terminal device comprising: a receiving unit that receives a PTRS-UplinkConfig and a DCI (Downlink Control Information) format; and a transmitting unit that transmits a PUSCH (Physical Uplink Shared Channel) and a PT-RS (Phase Tracking Reference Signal) based on a value of an FDRA (Frequency Domain Resource Assignment) field included in the PTRS-UplinkConfig and the DCI format, wherein when modified precoding is enabled, if the value of the FDRA field indicates that the bandwidth scheduled for the PUSCH is smaller than one PRB (Physical Resource Block), the transmitting unit does not transmit the PT-RS, and if the value of the FDRA field indicates that the bandwidth scheduled for the PUSCH is smaller than one PRB and an upper layer parameter indicating that coverage enhancement is enabled is set, the transmitting unit transmits the PT-RS together with the PUSCH.

(2) A second aspect of the present invention is a base station device comprising: a transmitting unit that transmits a PTRS-UplinkConfig and a DCI (Downlink Control Information) format; and a receiving unit that receives a PUSCH (Physical Uplink Shared Channel) and a PT-RS (Phase Tracking Reference Signal) based on a value of an FDRA (Frequency Domain Resource Assignment) field included in the PTRS-UplinkConfig and the DCI format, wherein when modified precoding is set to be enabled and coverage enhancement is set to be enabled, the receiving unit receives the PUSCH assuming that the PT-RS is included in the PUSCH, regardless of the bandwidth scheduled for the PUSCH.

(3) A third aspect of the present invention is a method for use in a terminal device, comprising the steps of receiving a PTRS-UplinkConfig and a DCI (Downlink Control Information) format; transmitting a PUSCH (Physical Uplink Shared Channel) and a PT-RS (Phase Tracking Reference Signal) based on a value of an FDRA (Frequency Domain Resource Assignment) field included in the PTRS-UplinkConfig and the DCI format; not transmitting the PT-RS when modified precoding is enabled and the value of the FDRA field indicates that the bandwidth scheduled for the PUSCH is smaller than one PRB (Physical Resource Block); and transmitting the PT-RS together with the PUSCH when the value of the FDRA field indicates that the bandwidth scheduled for the PUSCH is smaller than one PRB and an upper layer parameter indicating that coverage enhancement is enabled is set.

A fourth aspect of the present invention is a method for use in a base station device, comprising the steps of transmitting a PTRS-UplinkConfig and a DCI (Downlink Control Information) format, receiving a PUSCH (Physical Uplink Shared Channel) and a PT-RS (Phase Tracking Reference Signal) based on a value of an FDRA (Frequency Domain Resource Assignment) field included in the PTRS-UplinkConfig and the DCI format, and, when modified precoding is set to be enabled and coverage enhancement is set to be enabled, receiving the PUSCH assuming that the PT-RS is included therein, regardless of the bandwidth scheduled for the PUSCH.

According to one aspect of the present invention, a terminal device can communicate efficiently. Also, a base station device can communicate efficiently.

1 is a conceptual diagram of a wireless communication system according to an embodiment of the present invention. 1 is an example illustrating a relationship between N ^slot _symb , an SCS setting μ, and a CP setting according to an aspect of the present embodiment. FIG. 2 is a schematic diagram illustrating an example of a resource grid in a subframe according to an aspect of the present embodiment. FIG. 11 is a diagram illustrating an example of a relationship between a PUCCH format and a length N ^PUCCH _symb of the PUCCH format according to one aspect of the present embodiment. 1 is a schematic block diagram showing a configuration of a terminal device 1 according to an aspect of the present embodiment. 1 is a schematic block diagram showing a configuration of a base station device 3 according to one aspect of the present embodiment. A figure showing respective thresholds ptrs-MCSi given by timeDensity and frequencyDensity in one embodiment of the present invention, and a table used to give a mapping pattern of PT-RS based on N _RBi and scheduled MCS (I _MCS ) and bandwidth (N _RB ). FIG. 2 is a diagram showing an MCS index table 1 (an example of an MCS index table) according to one aspect of the present embodiment. FIG. 2 is a diagram showing an MCS index table 2 (another example 1 of the MCS index table) according to one aspect of the present embodiment. FIG. 2 is a diagram showing an MCS index table 3 (another example 2 of the MCS index table) according to one aspect of the present embodiment. FIG. 1 is a flow diagram illustrating a set of one or more time indexes l defined relative to the start of PDSCH configuration according to one aspect of the present embodiment. A figure showing an example of a calculation formula used to estimate the subcarrier k to which the PT-RS in one embodiment of the present invention is mapped. FIG. 13 is a diagram showing a correspondence relationship of k ^RE _ref according to one aspect of the present embodiment. FIG. 13 is a table illustrating an α ^PUSCH _PTRS according to one embodiment of the present invention. FIG. 13 is a diagram showing a PUSCH DM-RS configuration type according to one aspect of the present embodiment. A figure showing the PT-RS scaling factor when modified precoding is enabled in one aspect of this embodiment. A figure showing sequence generation of PT-RS for PUSH when modified precoding in one aspect of this embodiment is not enabled. A figure showing sequence generation of PT-RS for PUSH when modified precoding related to one aspect of this embodiment is enabled. FIG. 2 is a diagram illustrating an example of an orthogonal sequence w(i) according to an aspect of the present embodiment. A diagram showing mapping of PT-RS according to one aspect of this embodiment. FIG. 11 is a diagram showing various parameters for a DM-RS configuration type according to one embodiment of the present invention. A flow diagram showing a set of one or more time indexes l defined relative to the start of PUSCH placement when modified precoding is not enabled in one aspect of this embodiment. A figure showing a calculation formula used to estimate the subcarrier k to which the PT-RS is mapped in one embodiment of the present invention. FIG. 13 is a diagram showing a correspondence relationship of k ^RE _ref according to one aspect of the present embodiment. A diagram showing PT-RS symbol mapping according to one aspect of this embodiment. A flow diagram showing a set of one or more time indexes l defined relative to the start of PUSCH placement when modified precoding is not enabled in one aspect of this embodiment.

The following describes an embodiment of the present invention.

FIG. 1 is a conceptual diagram of a wireless communication system according to one aspect of the present embodiment. In FIG. 1, the wireless communication system includes terminal devices 1A to 1C and a base station device 3. Hereinafter, the terminal devices 1A to 1C may also be referred to as terminal devices 1. The base station device 3 may include some or all of a communication device, a node, an NB (NodeB), an eNB, a gNB, a network device (core network, gateway), and an access point. The terminal device 1 may also be referred to as a UE (User equipment). The eNB is a node that provides EUTRA user plane and control plane protocol termination for one or more terminal devices 1, and an eNB that is connected to a fifth generation core network (5GC) via an NG (Next Generation) interface is referred to as an ng-eNB. The gNB is a node that provides NR user plane and control plane protocol termination for one or more terminal devices 1, and is connected to the 5GC via an NG interface.

The base station device 3 may configure one or both of an MCG (Master Cell Group) and an SCG (Secondary Cell Group). The MCG is a group of serving cells including at least a PCell (Primary Cell). The SCG is a group of serving cells including at least a PSCell (Primary Secondary Cell). The PCell may be a serving cell provided based on an initial connection. The MCG may be configured to include one or more SCells (Secondary Cells). The SCG may be configured to include one or more SCells. The PCell and the PSCell may be referred to as SpCells (Special Cells). Configuring one CG using one SpCell and one or more SCells and performing communication may be referred to as carrier aggregation.

The MCG may be configured with one or more serving cells on the EUTRA. The SCG may be configured with one or more serving cells on the NR. The MCG may be configured with one or more serving cells on the NR. The SCG may be configured with one or more serving cells on the EUTRA. The MCG and the SCG may be configured with one or more serving cells of either the EUTRA or the NR. Here, "on the EUTRA" may include the meaning that the EUTRA RAT (Radio Access Technology) is applied. "on the NR" may include the meaning that the NR RAT is applied.

The MCG may be composed of one or more serving cells on the EUTRA. The SCG may be composed of one or more serving cells on the NR-U. The MCG may be composed of one or more serving cells on the NR. The SCG may be composed of one or more serving cells on the NR-U. The MCG may be composed of one or more serving cells of either the EUTRA or the NR or the NR-U. The SCG may be composed of one or more serving cells of either the EUTRA or the NR or the NR-U. The NR-U is intended to provide NR communications/access/services in a frequency band (operating band) that does not require a frequency license. In the frequency band in which NR-U communication is performed, communication may be performed by a terminal device and/or an access point (and/or a base station device) that performs a wireless LAN (Wireless Local Area Network, Radio LAN) service (communication and/or system), a WAS (Wireless Access Systems) service, an IEEE 802.11 service, a WiFi service, an FWA (Fixed Wireless Access) service, an ITS (Intelligent Transport Systems) service, or an LAA (Licensed Assisted Access) service. On the other hand, NR is intended to perform NR-type communication/access/service in a frequency band that requires a frequency license. LTE is intended to perform LTE-type communication/access/service in a frequency band that requires a frequency license. LAA is intended to perform LTE-type communication/access/service in a frequency band that does not require a frequency license.

The operating bands (carrier frequencies and frequency bandwidths) applicable to each of EUTRA, NR, and NR-U may be defined (specified) separately.

The MCG may be configured by the first base station device. The SCG may be configured by the second base station device. That is, the PCell may be configured by the first base station device. The PSCell may be configured by the second base station device. The first base station device and the second base station device may each be the same as the base station device 3.

The communication technology related to coverage enhancement in one aspect of this embodiment may be used to support a wide-area (long-distance) communication area (coverage), may be used to improve communication conditions between an outdoor base station device and an indoor terminal device, or may be used to improve communication conditions between an indoor base station device and an indoor terminal device.

The frame structure is explained below.

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

The subcarrier spacing (SCS) may be given by the subcarrier spacing Δf=2 ^μ ·15 kHz. For example, the SCS setting μ may be set to any of 0, 1, 2, 3, 4, and/or 5. For a certain BWP (BandWidth Part), the SCS setting μ may be given by a higher layer parameter. That is, regardless of the downlink and/or uplink, the value of μ may be set for each BWP (each downlink BWP, each uplink BWP).

In the wireless communication system according to an aspect of the present embodiment, a time unit _Tc is used to express the length of the time domain. The time unit _Tc may be given by _Tc = 1/(Δf _max · N _f ). Δf _max may be the maximum value of the SCS supported in the wireless communication system according to an aspect of the present embodiment. Δf _max may be Δf _max = 480 kHz. N _f may be N _f = 4096. The constant κ is κ = Δf _max · N _f / (Δf _ref N _f,ref ) = 64. Δf _ref may be 15 kHz. _{N f,ref} may be 2048.

The constant κ may be a value indicating the relationship between the reference SCS and _Tc . The constant κ may be used for the length of the subframe. The number of slots included in the subframe may be given based at least on the constant κ. Δf _ref is the reference SCS, and N _f,ref is a value corresponding to the reference SCS.

The transmission of signals in the downlink and/or the transmission of signals in the uplink is composed of a frame of 10 ms. The frame is composed of 10 subframes. The length of the subframe is 1 ms. The length of the frame may be given regardless of Δf. That is, the setting of the frame may be given regardless of the value of μ. The length of the subframe may be given regardless of Δf. That is, the setting of the subframe may be given regardless of μ.

For a certain SCS setting μ, the number of slots included in one subframe and indexes may be given. For example, the slot number n ^μ _s may be given in the subframe in an ascending order from 0 to N ^subframe,μ _slot −1. For the SCS setting μ, the number of slots included in one frame and indexes may be given. Also, the slot number n ^μ _s,f may be given in the frame in an ascending order from 0 to N ^frame,μ _slot −1. Consecutive N ^slot _symb OFDM symbols may be included in one slot. N ^slot _symb may be given at least based on and/or a part or all of a cyclic prefix (CP) setting. The CP setting may be given at least based on a parameter of a higher layer. The CP setting may be given at least based on dedicated RRC signaling. The slot number may be referred to as a slot index.

Fig. 2 is an example showing the relationship between N ^slot _symb , SCS setting μ, and CP setting according to one aspect of the present embodiment. In Fig. 2A, for example, when the SCS setting μ is 2 and the CP setting is normal CP (NCP), N ^slot _symb = 14, N ^{frame, μ} _slot = 40, and N ^{subframe, μ} _slot = 4. Also, in Fig. 2B, for example, when the SCS setting μ is 2 and the CP setting is extended CP (ECP), N ^slot _symb = 12, N ^{frame, μ} _slot = 40, and N ^{subframe, μ} _slot = 4.

Below, we will explain the physical resources related to this embodiment.

An antenna port is defined by the fact that the channel on which a symbol is transmitted at one antenna port can be estimated from the channel on which another symbol is transmitted at the same antenna port. If the large scale properties of the channel on which a symbol is transmitted at one antenna port can be estimated from the channel on which a symbol is transmitted at the other antenna port, the two antenna ports may be referred to as being Quasi Co-Located (QCL). 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 spatial Rx parameters. The first antenna port and the second antenna port are QCL with respect to beam parameters may be that the receiving beam assumed by the receiving side for the first antenna port and the receiving beam assumed by the receiving side for the second antenna port are the same. The first antenna port and the second antenna port being QCL with respect to the beam parameters may mean that the transmission beam assumed by the receiving side for the first antenna port and the transmission beam assumed by the receiving side for the second antenna port are the same. The terminal device 1 may assume that the two antenna ports are QCL when 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 another antenna port. The two antenna ports being QCL may mean that the two antenna ports are assumed to be QCL.

For a set of SCS configuration μ and carriers, a resource grid is given, defined by N ^size,μ _grid,x N ^RB _sc subcarriers and N ^subframe,μ _symb OFDM symbols. N ^{size,μ grid} _,x may indicate the number of resource blocks given for SCS configuration μ for carrier x. N size,μ grid, _x may indicate the bandwidth of the carrier. N ^size,μ _grid,x may be given by the higher layer parameter CarrierBandwidth included in the SCS-SpecificCarrier information element. That is, N ^size,μ _grid,x may be used to indicate the bandwidth (number of resource blocks) of the carrier. Carrier x may indicate either a downlink carrier or an uplink carrier. That is, x may be either "DL" or "UL". ^{N RB} _sc may indicate the number of subcarriers included in one resource block. N ^RB _sc may be 12. At least one resource grid may be provided for each antenna port p, and/or for each SCS setting μ, and/or for each setting of a transmission direction. The transmission direction includes at least a downlink (DL) and an uplink (UL). Hereinafter, a set of parameters including at least the antenna port p, the SCS setting μ, and a part or all of the setting of the transmission direction may also be referred to as a first radio parameter set. That is, one resource grid may be provided for each first radio parameter set. Note that the radio parameter set may be one or more sets including one or more radio parameters (physical layer parameters or higher layer parameters).

In the downlink, a carrier included in a serving cell is called a downlink carrier (or a downlink component carrier). In the uplink, a carrier included in a serving cell is called an uplink carrier (uplink component carrier). Downlink component carriers and uplink component carriers may be collectively referred to as component carriers (or carriers).

The type of the serving cell may be any of PCell, PSCell, and SCell. The PCell may be a serving cell identified based at least on a cell ID (physical layer cell ID, physical cell ID) obtained from an SSB (Synchronization signal/Physical broadcast channel block) at the initial connection. The SCell may be a serving cell used in carrier aggregation (a serving cell that can be added after the initial connection and/or RRC connection of the PCell is established). The SCell may be a serving cell provided based at least on dedicated RRC signaling. The SSB may be referred to as an SS/PBCH block.

Each element in the resource grid provided for each first radio parameter set may be referred to as a resource element (RE). The resource element is identified by a frequency domain index k _sc and a time domain index l _sym . For a certain first radio parameter set, the resource element is identified by a frequency domain index k _sc and a time domain index l _sym . The resource element identified by the frequency domain index k _sc and the time domain index l _sym may also be referred to as a resource element (k _sc , l _sym ). The frequency domain index k _sc indicates any value from 0 to N ^μ _RB N ^RB _sc -1. N ^μ _RB may be the number of resource blocks provided for the SCS configuration μ. N ^μ _RB may be N ^{size, μ} _{grid, x} . ^{N RB} _sc is the number of subcarriers included in a resource block, and N ^RB _sc =12. The frequency domain index k _sc may correspond to a subcarrier index k _sc . The time domain index l _sym may correspond to an OFDM symbol index l _sym . One or more resource elements may correspond to a physical resource and a complex value (complex-valued modulation symbol). One or more information bits (information bits for control information, transport blocks, and higher layer parameters) may be mapped to each of the one or more resource elements corresponding to the physical resource and/or complex value.

FIG. 3 is a schematic diagram showing an example of a resource grid in a subframe according to an aspect of the present embodiment. In the resource grid of FIG. 3, the horizontal axis is a time domain index l _sym and the vertical axis is a frequency domain index k _sc . In one subframe, the frequency domain of the resource grid includes N ^μ _RB N ^RB _sc subcarriers. In one subframe, the time domain of the resource grid may include 14·2 ^μ OFDM symbols. One resource block includes N ^RB _sc subcarriers. The time domain of the resource block may correspond to one OFDM symbol. The time domain of the resource block may correspond to 14 OFDM symbols. The time domain of the resource block may correspond to one or more slots. The time domain of the resource block may correspond to one subframe.

The terminal device 1 may be instructed to transmit and receive using only a subset of the resource grid. The subset of the resource grid may also be referred to as a BWP, and the BWP may be given based on at least a higher layer parameter and/or a part or all of the DCI. The BWP may also be referred to as a CBP (Carrier Bandwidth Part). The terminal device 1 may not be instructed to transmit and receive using all sets of the resource grid. The terminal device 1 may be instructed to transmit and receive using some frequency resources in the resource grid. One BWP may be composed of multiple resource blocks in the frequency domain. One BWP may be composed of multiple consecutive resource blocks in the frequency domain. The BWP set for the downlink carrier may also be referred to as a downlink BWP. The BWP set for the uplink carrier may also be referred to as an uplink BWP. The BWP may be a subset of the carrier's band (a subset of the frequency domain in the carrier).

One or more downlink BWPs may be configured for each serving cell. One or more uplink BWPs may be configured for each serving cell.

Of one or more downlink BWPs configured for a serving cell, one downlink BWP may be set as an active downlink BWP. The downlink BWP switch is used to deactivate one active downlink BWP and activate inactive downlink BWPs other than the one active downlink BWP. The switching of the downlink BWP may be controlled by a BWP field included in the downlink control information. The switching of the downlink BWP may be controlled based on parameters of a higher layer.

In an active downlink BWP, DL-SCH may be received. In an active downlink BWP, PDCCH may be monitored. In an active downlink BWP, PDSCH may be received.

In an inactive downlink BWP, DL-SCH is not received. In an inactive downlink BWP, PDCCH is not monitored. No CSI is reported for the inactive downlink BWP.

Of one or more downlink BWPs configured for a serving cell, two or more downlink BWPs may not be set as active downlink BWPs.

Of one or more uplink BWPs configured for a serving cell, one uplink BWP may be set as an active uplink BWP. The uplink BWP switch is used to deactivate one active uplink BWP and activate inactive uplink BWPs other than the one active uplink BWP. The switching of the uplink BWP may be controlled by a BWP field included in the downlink control information. The switching of the uplink BWP may be controlled based on parameters of a higher layer.

In an active uplink BWP, a UL-SCH may be transmitted. In an active uplink BWP, a PUCCH may be transmitted. In an active uplink BWP, a PRACH may be transmitted. In an active uplink BWP, an SRS may be transmitted.

In an inactive uplink BWP, UL-SCH is not transmitted. In an inactive uplink BWP, PUCCH is not transmitted. In an inactive uplink BWP, PRACH is not transmitted. In an inactive uplink BWP, SRS is not transmitted.

Of one or more uplink BWPs configured for one serving cell, two or more uplink BWPs may not be configured as active uplink BWPs. In other words, there needs to be at least one active uplink BWP for the serving cell that includes the uplink BWP.

The upper layer parameters are parameters included in the upper layer signal. The upper layer signal may be RRC (Radio Resource Control) signaling or MAC CE (Medium Access Control Control Element). Here, the upper layer signal may be an RRC layer signal or a MAC layer signal. The upper layer parameters provided by the RRC layer signal may be notified from the base station device 3 to the terminal device 1 and may be set.

The higher layer signal may be common RRC signaling. The common RRC signaling may include at least some or all of the following features C1 to C3:
Feature C1) Mapped to the BCCH logical channel or the CCCH logical channel Feature C2) Includes at least the ReconfigurationWithSync information element Feature C3) Mapped to the PBCH

The ReconfigurationWithSync information element may include information indicating a configuration commonly used in the serving cell. The configuration commonly used in the serving cell may include at least a PRACH configuration. The PRACH configuration may at least indicate one or more random access preamble indices. The PRACH configuration may at least indicate a time/frequency resource of the PRACH.

The common RRC signaling may include at least common RRC parameters. The common RRC parameters may be parameters that are commonly used in the serving cell (cell-specific).

The higher layer signaling may be dedicated RRC signaling. The dedicated RRC signaling may comprise at least some or all of the following features D1 to D2:
Feature D1) Mapped to DCCH logical channel Feature D2) Does not include ReconfigurationWithSync information element

For example, the MIB (Master Information Block) and the SIB (System Information Block) may be included in the common RRC signaling. Also, an upper layer message that is mapped to the DCCH logical channel and includes at least the ReconfigurationWithSync information element may be included in the common RRC signaling. Also, an upper layer message that is mapped to the DCCH logical channel and does not include the ReconfigurationWithSync information element may be included in the dedicated RRC signaling. The MIB and the SIB may be collectively referred to as system information.

In addition, the upper layer parameters including one or more upper layer parameters may be referred to as information elements (IEs). In addition, the upper layer parameters including one or more upper layer parameters and/or one or more IEs and/or IEs may be referred to as messages (upper layer messages, RRC messages), information blocks (IBs), or system information.

The SIB may at least indicate a time index of the SSB. The SIB may at least include information related to PRACH resources. The SIB may at least include information related to setting up an initial connection.

The ReconfigurationWithSync information element may include at least information related to PRACH resources. The ReconfigurationWithSync information element may include at least information related to setting up an initial connection.

The dedicated RRC signaling may include at least dedicated RRC parameters. The dedicated RRC parameters may be parameters that are used exclusively for the terminal device 1 (UE-specific). The dedicated RRC signaling may include at least common RRC parameters.

Common RRC parameters and dedicated RRC parameters may also be referred to as higher layer parameters.

The following describes physical channels and physical signals relating to various aspects of this embodiment.

An uplink physical channel may correspond to a set of resource elements carrying information generated in a higher layer. An uplink physical channel is a physical channel used in an uplink carrier. In a wireless communication system according to one aspect of the present embodiment, at least some or all of the following uplink physical channels are used:
・PUCCH (Physical Uplink Control CHannel)
・PUSCH (Physical Uplink Shared CHannel)
・PRACH (Physical Random Access CHannel)

The PUCCH may be used to transmit uplink control information (UCI). The uplink control information includes some or all of the channel state information (CSI), the scheduling request (SR), and the hybrid automatic repeat request ACKnowledgement (HARQ-ACK) information corresponding to the transport block (TB). The TB may also be referred to as the MAC PDU (Medium Access Control Protocol Data Unit), the DL-SCH (Downlink-Shared Channel), or the PDSCH (Physical Downlink Shared Channel).

One or more types of uplink control information may be multiplexed onto the PUCCH. The multiplexed PUCCH may be transmitted. That is, the PUCCH may be multiplexed with multiple HARQ-ACKs, multiple CSIs, multiple SRs, HARQ-ACKs and CSIs, HARQ-ACKs and SRs, or other types of UCI.

The HARQ-ACK information may include at least a HARQ-ACK bit corresponding to the TB. The HARQ-ACK bit may indicate an ACK (acknowledgement) or a NACK (negative-acknowledgement) corresponding to the TB. The ACK may be a value indicating that the decoding of the TB has been successfully completed. The NACK may be a value indicating that the decoding of the TB has not been successfully completed. The HARQ-ACK information may include at least one HARQ-ACK codebook including one or more HARQ-ACK bits. The HARQ-ACK bit corresponding to one or more TBs may correspond to a PDSCH including the one or more TBs.

The HARQ-ACK bit may indicate an ACK or NACK corresponding to one Code Block Group (CBG) included in the TB. HARQ-ACK may also be referred to as HARQ feedback, HARQ information, or HARQ control information.

SR may be used at least to request PUSCH resources for initial transmission. SR may also be used to request UL-SCH resources for new transmission. The SR bit may be used to indicate either a positive SR (positive SR) or a negative SR (negative SR). The SR bit indicating a positive SR may also be referred to as "a positive SR is transmitted". A positive SR may indicate that a PUSCH resource for initial transmission is requested by the terminal device 1. A positive SR may indicate that an SR is triggered by a higher layer. A positive SR may be transmitted when an SR is instructed to be transmitted by a higher layer. The SR bit indicating a negative SR may also be referred to as "a negative SR is transmitted". A negative SR may indicate that a PUSCH resource for initial transmission is not requested by the terminal device 1. A negative SR may indicate that an SR is not triggered by a higher layer. A negative SR may be transmitted if no SR is indicated to be transmitted by higher layers.

The SR bit may be used to indicate either a positive SR or a negative SR for one or more SR configurations. Each of the one or more SR configurations may correspond to one or more logical channels. A positive SR for an SR configuration may be a positive SR for any or all of the one or more logical channels corresponding to the SR configuration. A negative SR may not correspond to a specific SR configuration. An indication of a negative SR may be an indication of a negative SR for all SR configurations.

The SR setting may be a Scheduling Request ID (SR-ID). The SR-ID may be provided by a higher layer parameter.

The CSI may include at least some or all of a channel quality index (CQI), a precoder matrix index (PMI), and a rank index (RI). The CQI is an index related to the quality of the channel (e.g., propagation strength), the PMI is an index indicating the precoder, and the RI is an index indicating the transmission rank (or the number of transmission layers).

The CSI may be provided based at least on receiving a physical signal (e.g., CSI-RS) used at least for channel measurement. The CSI may include a value selected by the terminal device 1. The CSI may be selected by the terminal device 1 based at least on receiving a physical signal used at least for channel measurement. The channel measurement may include interference measurement. Note that the CSI-RS may be set based on the CSI-RS configuration or may be set based on the SSB configuration.

The CSI report is a report of CSI. The CSI report may include CSI part 1 and/or CSI part 2. The CSI part 1 may be configured to include at least a wideband channel quality information (wideband CQI), a wideband precoder matrix index (wideband PMI), and a part or all of the RI. The number of bits of the CSI part 1 multiplexed onto the PUCCH may be a predetermined value regardless of the value of the RI of the CSI report. The number of bits of the CSI part 2 multiplexed onto the PUCCH may be given based on the value of the RI of the CSI report. The rank index of the CSI report may be a value of a rank index used for calculating the CSI report. The RI of the CSI information may be a value indicated by an RI field included in the CSI report.

The set of RIs allowed in a CSI report may be some or all of 1 to 8. The set of RIs allowed in a CSI report may also be given based at least on a higher layer parameter RankRestriction. If the set of RIs allowed in a CSI report includes only one value, the RI of the CSI report may be that one value.

Priority may be set for the CSI report. The priority of the CSI report may be based on at least some or all of the following: a configuration for the time domain behavior (processing) of the CSI report, a type of content of the CSI report, an index of the CSI report, and/or an index of a serving cell for which the measurement of the CSI report is configured.

The settings regarding the time domain behavior (processing) of the CSI reporting may be settings indicating whether the CSI reporting is performed aperiodic, whether the CSI reporting is performed semi-persistent, or whether the CSI reporting is performed quasi-statically.

The content type of the CSI report may indicate whether the CSI report includes Layer 1 Reference Signals Received Power (RSRP).

The index of the CSI report may be given by a higher layer parameter.

The PUCCH supports one or more PUCCH formats (PUCCH format 0 to PUCCH format 4). The PUCCH format may be transmitted on the PUCCH. The transmission of the PUCCH format may be the transmission of the PUCCH.

4 is a diagram showing an example of the relationship between the PUCCH format and the length N ^PUCCH _symb of the PUCCH format according to one aspect of the present embodiment. The length N ^PUCCH _symb of PUCCH format 0 is 1 or 2 OFDM symbols. The length N ^PUCCH _symb of PUCCH format 1 is any of 4 to 14 OFDM symbols. The length N ^PUCCH _symb of PUCCH format 2 is 1 or 2 OFDM symbols. The length N ^PUCCH _symb of PUCCH format 3 is any of 4 to 14 OFDM symbols. The length N ^PUCCH _symb of PUCCH format 4 is any of 4 to 14 OFDM symbols.

The PUSCH is used at least to transmit TBs (MAC PDU, UL-SCH). The PUSCH may be used at least to transmit TBs, HARQ-ACK information, CSI, and some or all of SRs. The PUSCH is used at least to transmit the RAR (Msg2) in the random access procedure and/or random access message 3 (message 3 (Msg3)) corresponding to the RAR grant. Note that the TBs may correspond to both the uplink and the downlink. That is, the PUSCH may be used to transmit TBs for the uplink. The PDSCH may be used to transmit TBs for the downlink.

The PRACH is used at least to transmit a random access preamble (random access message 1, message 1 (Msg1)). The PRACH may be used at least to indicate some or all of the initial connection establishment procedure, handover procedure, connection re-establishment procedure, initial access procedure, synchronization (timing adjustment) for the transmission of the PUSCH, and a request for resources for the PUSCH. The random access preamble may be used to notify the base station device 3 of an index (random access preamble index) provided by a higher layer of the terminal device 1.

The random access preamble may be provided by cyclically shifting a Zadoff-Chu sequence corresponding to a physical root sequence index u. The Zadoff-Chu sequence may be generated based on the physical root sequence index u. A plurality of random access preambles may be defined in one serving cell. The random access preamble may be identified based at least on an index of the random access preamble. Different random access preambles corresponding to different indices of the random access preamble may correspond to different combinations of the physical root sequence index u and the cyclic shift. The physical root sequence index u and the cyclic shift may be provided based at least on information included in the system information. The physical root sequence index u may be an index that identifies a sequence included in the random access preamble. The random access preamble may be identified based at least on the physical root sequence index u.

In Fig. 1, the following uplink physical signals are used in uplink wireless communication: The uplink physical signals may not be used to transmit information output from higher layers, but are used by the physical layer.
・UL DMRS (UpLink Demodulation Reference Signal)
・SRS (Sounding Reference Signal)
・UL PTRS (UpLink Phase Tracking Reference Signal)

UL DMRS is related to the transmission of PUSCH and/or PUCCH. UL DMRS is multiplexed with PUSCH or PUCCH. Base station device 3 may use UL DMRS to perform propagation path correction of PUSCH or PUCCH. Hereinafter, transmitting PUSCH and UL DMRS related to the PUSCH together is simply referred to as transmitting PUSCH. Hereinafter, transmitting PUCCH and UL DMRS related to the PUCCH together is simply referred to as transmitting PUCCH. UL DMRS related to PUSCH is also referred to as UL DMRS for PUSCH. UL DMRS related to PUCCH is also referred to as UL DMRS for PUCCH.

The SRS may not be associated with the transmission of the PUSCH or PUCCH. The base station device 3 may use the SRS for measuring the channel condition. The SRS may be transmitted in an uplink slot, a subframe, or a predetermined number of OFDM symbols from the end of the UpPTS.

The UL PTRS may be a reference signal used at least for phase tracking. The UL PTRS may be associated with a UL DMRS group including at least an antenna port used for one or more UL DMRSs. The association of the UL PTRS with the UL DMRS group may be such that the antenna port of the UL PTRS and some or all of the antenna ports included in the UL DMRS group are at least QCL. The UL DMRS group may be identified based at least on the antenna port with the smallest index in the UL DMRS included in the UL DMRS group. The UL PTRS may be mapped to the antenna port with the smallest index among one or more antenna ports to which one codeword is mapped. The UL PTRS may be mapped to the first layer when one codeword is mapped to at least the first layer and the second layer. The UL PTRS may not be mapped to the second layer. The index of the antenna port to which the UL PTRS is mapped may be given based at least on the downlink control information.

1, the following downlink physical channels are used in downlink wireless communication from the base station device 3 to the terminal device 1. The downlink physical channels are used by the physical layer to transmit information output from a higher layer.
・PBCH (Physical Broadcast Channel)
・PDCCH (Physical Downlink Control Channel)
・PDSCH (Physical Downlink Shared Channel)

The PBCH is used at least to transmit the MIB and/or the PBCH payload. The PBCH payload may include at least information indicating an index related to the transmission timing of the SSB (SSB occasion). The PBCH payload may include information related to an identifier (index) of the SSB. The PBCH may be transmitted based on a predetermined transmission interval. The PBCH may be transmitted at intervals of 80 milliseconds (ms). The PBCH may be transmitted at intervals of 160 ms. The contents of the information included in the PBCH may be updated every 80 ms. A part or all of the information included in the PBCH may be updated every 160 ms. The PBCH may be configured with 288 subcarriers. The PBCH may be configured to include 2, 3, or 4 OFDM symbols. The MIB may include information related to an identifier (index) of the SSB. The MIB may include information indicating at least a portion of the slot number, subframe number, and/or radio frame number in which the PBCH is transmitted.

The PDCCH is used at least for transmitting downlink control information (DCI). The PDCCH may be transmitted including at least the DCI. The PDCCH may be transmitted including the DCI. The DCI may also be referred to as a DCI format. The DCI may indicate at least either a downlink grant or an uplink grant. The DCI format used for scheduling the PDSCH may also be referred to as a downlink DCI format and/or a downlink grant. The DCI format used for scheduling the PUSCH may also be referred to as an uplink DCI format and/or an uplink grant. The downlink grant may also be referred to as a downlink assignment or a downlink allocation. The uplink DCI format includes at least one or both of DCI format 0_0 and DCI format 0_1.

DCI format 0_0 may be configured to include at least some or all of 1A to 1J.
1A) Identifier for DCI formats field
1B) Frequency Domain Resource Allocation Field (FDRA field)
1C) Time Domain Resource Allocation Field (TDRA field)
1D) Frequency hopping flag field (FH field)
1E) MCS field (Modulation and Coding Scheme field)
1F) Channel State Information request field
1G) NDI field (New Data Indicator field)
1H) RV field (Redundancy Version field)
1I) HARQ process ID field, HARQ process number field
1J) TPC (Transmission Power Control) command field for scheduled PUSCH

1A may be used at least to indicate which of one or more DCI formats the DCI format containing 1A corresponds to. The one or more DCI formats may be based at least on some or all of DCI format 1_0, DCI format 1_1, DCI format 0_0, and/or DCI format 0_1.

1B may be used at least to indicate the allocation of frequency resources for a PUSH scheduled by a DCI format including 1B.

1C may be used at least to indicate the allocation of time resources for a PUSH scheduled by a DCI format including 1C.

1D may be used at least to indicate whether frequency hopping is applied to a PUSH scheduled by a DCI format that includes the 1D.

1E may be used at least to indicate a modulation scheme and/or a part or all of a target coding rate for a PUSCH scheduled by a DCI format including the 1E. The target coding rate may be a target coding rate for a TB of the PUSCH. The size of the TB (TBS) may be given based at least on the target coding rate.

1F is used at least to indicate the reporting of CSI. The size of 1F may be a predetermined value. The size of 1F may be 0, 1, 2, or 3. The size of 1F may be determined according to the number of CSI settings set in the terminal device 1.

1G is used to indicate whether the transmission of the PUSCH corresponding to 1I scheduled by the DCI format is a new transmission or a retransmission based on whether the value of 1G is toggled. If the value of 1G is toggled, the PUSCH corresponding to 1I is a new transmission, otherwise, the PUSCH corresponding to 1I is a retransmission. The 1G may be a DCI indicating whether the base station device 3 is requesting a retransmission of the PUSCH corresponding to 1I.

1H is used to indicate the start position of the PUSH bit sequence scheduled by the DCI format.

1I is used to indicate the HARQ process number (HPID) to which the PUSH scheduled by the DCI format corresponds.

1J is used to adjust the transmission power of the PUSH scheduled by the DCI format.

DCI format 0_1 is configured to include at least some or all of 2A to 2K.
2A) DCI format specific field 2B) Frequency domain resource allocation field 2C) Time domain resource allocation field 2D) Frequency hopping flag field 2E) MCS field 2F) CSI request field 2G) BWP field 2H) NDI field 2I) RV field 2J) HPID field 2K) TPC command field for PUSCH

The BWP field may be used to indicate the uplink BWP to which the PUSH scheduled by DCI format 0_1 is mapped.

The CSI request field is at least used to indicate a CSI report. The size of the CSI request field may be based at least on the higher layer parameter ReportTriggerSize.

Fields with the same names as 1A to 1J described above contain the same content, so explanations will be omitted.

The downlink DCI formats include at least one or both of DCI format 1_0 and DCI format 1_1.

DCI format 1_0 may be configured to include at least some or all of 3A to 3L.
3A) DCI format specific field 3B) Frequency domain resource allocation field 3C) Time domain resource allocation field 3D) Frequency hopping flag field 3E) MCS field 3F) CSI request field 3G) PDSCH to HARQ feedback timing indicator field
3H) PUCCH Resource Indication Field (PRI Field)
3I) NDI field 3J) RV field 3K) HPID field 3L) TPC command field for scheduled PUCCH field

3B to 3E may be used for PDSCH scheduled by the DCI format.

3G may be a field indicating timing K1. When the index of the slot including the last OFDM symbol of the PDSCH is slot n, the index of the slot including the PUCCH or PUSCH including at least the HARQ-ACK corresponding to the TB included in the PDSCH may be n+K1. When the index of the slot including the last OFDM symbol of the PDSCH is slot n, the index of the slot including the first OFDM symbol of the PUCCH or the first OFDM symbol of the PUSCH including at least the HARQ-ACK corresponding to the TB included in the PDSCH may be n+K1.

3H may be a field indicating the index of one or more PUCCH resources included in the PUCCH resource set.

3I is used to indicate whether the transmission of the PDSCH corresponding to 3K scheduled by the DCI format is a new transmission or a retransmission based on whether the value of 3I is toggled. If the value of 3K is toggled, the PDSCH corresponding to 3K is a new transmission, otherwise the PDSCH corresponding to 3K is a retransmission.

3J may be used to indicate the start position of the PDSCH bit sequence scheduled by the DCI format.

3K may be used to indicate the number of the HARQ process to which the PDSCH scheduled by the DCI format corresponds.

3L may be used to adjust the transmission power of the PUCCH corresponding to the PDSCH scheduled by the DCI format.

DCI format 1_1 may be configured to include at least some or all of 4A to 4M.
4A) DCI format specific field 4B) Frequency domain resource allocation field 4C) Time domain resource allocation field 4D) Frequency hopping flag field 4E) MCS field 4F) CSI request field 4G) PDSCH to HARQ feedback timing indication field 4H) PUCCH resource indication field 4I) BWP field 4J) NDI field 4K) RV field 4L) HPID field 4M) TPC command field for PUCCH

3A, 4A, like 1A and 2A, are used to identify the DCI format.

4B to 4E may be used for PDSCH scheduled by the DCI format.

4I may be used to indicate the downlink BWP to which the PDSCH scheduled by DCI format 1_1 is mapped.

Fields with the same names as 3A to 3L described above contain the same content, so explanations will be omitted.

Each DCI format may include padding bits to fit a predefined bit size (payload size).

DCI format 2 may include parameters used for transmission power control of PUSH or PUCCH.

In various aspects of this embodiment, unless otherwise specified, the number of resource blocks (RB) indicates the number of resource blocks in the frequency domain. In addition, resource block indexes are assigned in ascending order from resource blocks mapped to the low frequency domain to resource blocks mapped to the high frequency domain. In addition, resource blocks are a general term for common resource blocks and physical resource blocks.

One physical channel may be mapped to one serving cell. One physical channel may be mapped to one CBP configured on one carrier included in one serving cell.

The terminal device 1 is given one or more control resource sets (CORESETS). The terminal device 1 monitors the PDCCH in one or more CORESETS.

The CORESET may indicate a time-frequency region to which one or more PDCCHs may be mapped. The CORESET may be a region in which the terminal device 1 monitors the PDCCHs. The CORESET may be composed of contiguous resources (localized resource(s), contiguous resource(s)). The CORESET may be composed of discontinuous resources (distributed resource(s), discontinuous resource(s)).

In the frequency domain, the unit of mapping of the CORESET may be a resource block (RB). For example, in the frequency domain, the unit of mapping of the CORESET may be 6 resource blocks. That is, the frequency domain mapping of the CORESET may be performed with 6RB×n (n is 1, 2, ...). In the time domain, the unit of mapping of the CORESET may be an OFDM symbol. For example, in the time domain, the unit of mapping of the CORESET may be one OFDM symbol.

The frequency domain of the CORESET may be given based at least on higher layer signaling and/or DCI.

The time domain of the CORESET may be given based at least on higher layer signaling and/or DCI.

A CORESET may be a common CORESET. The common CORESET may be a CORESET that is set in common for multiple terminal devices 1. The common CORESET may be given based on at least a part or all of the MIB, SIB, common RRC signaling, and cell ID. For example, the time resources and/or frequency resources of the CORESET that is set to monitor the PDCCH used for scheduling the SIB may be given based on at least the MIB.

A CORESET may be a dedicated CORESET. The dedicated CORESET may be a CORESET that is set to be used exclusively for the terminal device 1. The dedicated CORESET may be provided based at least on dedicated RRC signaling.

The set of PDCCH candidates monitored by the terminal device 1 may be defined in terms of a search space. That is, the set of PDCCH candidates monitored by the terminal device 1 may be given by a search space.

The search space may be configured to include one or more PDCCH candidates of one or more aggregation levels. The aggregation level of the PDCCH candidate may indicate the number of CCEs that constitute the PDCCH.

The terminal device 1 may monitor at least one or more search space sets in slots where DRX (Discontinuous reception) is not set. DRX may be provided based at least on higher layer parameters. The terminal device 1 may monitor at least one or more search space sets in slots where DRX is not set.

The search space set may be configured to include at least one or more search spaces. The type of the search space set may be any of a type 0 PDCCH common search space, a type 0a PDCCH common search space, a type 1 PDCCH common search space, a type 2 PDCCH common search space, a type 3 PDCCH common search space, and/or a UE-specific PDCCH search space.

The Type 0 PDCCH common search space, the Type 0a PDCCH common search space, the Type 1 PDCCH common search space, the Type 2 PDCCH common search space, and the Type 3 PDCCH common search space may also be referred to as a Common Search Space (CSS). The UE-specific PDCCH search space may also be referred to as a UE specific Search Space (USS).

Each of the search space sets may be associated with one control resource set. Each of the search space sets may be included in at least one control resource set. For each of the search space sets, an index of the control resource set associated with the search space set may be given.

The type 0 PDCCH common search space may be used at least for DCI formats with a CRC (Cyclic Redundancy Check) sequence scrambled by SI-RNTI (System Information-Radio Network Temporary Identifier). The configuration of the type 0 PDCCH common search space may be based at least on the four least significant bits (LSBs) of the upper layer parameter PDCCH-ConfigSIB1. The upper layer parameter PDCCH-ConfigSIB1 may be included in the MIB. The configuration of the type 0 PDCCH common search space may be based at least on the upper layer parameter SearchSpaceZero. The interpretation of the bits of the upper layer parameter SearchSpaceZero may be similar to the interpretation of the four least significant bits (LSBs) of the upper layer parameter PDCCH-ConfigSIB1. The setting of the type 0 PDCCH common search space may be based at least on the higher layer parameter SearchSpaceSIB1. The higher layer parameter SearchSpaceSIB1 may be included in the higher layer parameter PDCCH-ConfigCommon. The PDCCH detected in the type 0 PDCCH common search space may be used at least for scheduling the PDSCH including SIB1 and transmitted. SIB1 is a type of SIB. SIB1 may include scheduling information of SIBs other than SIB1. The terminal device 1 may receive the higher layer parameter PDCCH-ConfigCommon in EUTRA. The terminal device 1 may receive the higher layer parameter PDCCH-ConfigCommon in MCG.

The Type 0a PDCCH common search space may be used at least for DCI formats with a CRC (Cyclic Redundancy Check) sequence scrambled by SI-RNTI (System Information-Radio Network Temporary Identifier). The configuration of the Type 0a PDCCH common search space may be based at least on the higher layer parameter SearchSpaceOtherSystemInformation. The higher layer parameter SearchSpaceOtherSystemInformation may be included in SIB1. The higher layer parameter SearchSpaceOtherSystemInformation may be included in the higher layer parameter PDCCH-ConfigCommon. The PDCCH detected in the Type 0 PDCCH common search space may be used at least for scheduling the PDSCH transmitted including SIBs other than SIB1.

The type 1 PDCCH common search space may be used at least for a CRC sequence scrambled by a Random Access-Radio Network Temporary Identifier (RA-RNTI) and/or a DCI format with a CRC sequence scrambled by a Temporary Common-Radio Network Temporary Identifier (TC-RNTI). The RA-RNTI may be provided at least based on the time/frequency resources of a random access preamble transmitted by the terminal device 1. The TC-RNTI may be provided by a PDSCH (also called a random access message 2, message 2 (Msg2), or random access response (RAR)) scheduled by a DCI format with a CRC sequence scrambled by the RA-RNTI. The type 1 PDCCH common search space may be provided at least based on a higher layer parameter ra-SearchSpace. The higher layer parameter ra-SearchSpace may be included in SIB1. The higher layer parameter ra-SearchSpace may be included in the higher layer parameter PDCCH-ConfigCommon.

The Type 2 PDCCH common search space may be used for DCI formats with a CRC sequence scrambled by a Paging-Radio Network Temporary Identifier (P-RNTI). The P-RNTI may be used at least for transmission of DCI formats including information notifying a change in the SIB. The Type 2 PDCCH common search space may be given based at least on the higher layer parameter PagingSearchSpace. The higher layer parameter PagingSearchSpace may be included in SIB1. The higher layer parameter PagingSearchSpace may be included in the higher layer parameter PDCCH-ConfigCommon.

The Type 3 PDCCH common search space may be used for a DCI format with a CRC sequence scrambled by a Cell-Radio Network Temporary Identifier (C-RNTI). The C-RNTI may be provided based at least on a PDSCH (which may also be referred to as a Random Access Message 4, Message 4 (Msg4), or Contention Resolution) scheduled by a DCI format with a CRC sequence scrambled by a TC-RNTI. The Type 3 PDCCH common search space may be the search space set provided when the higher layer parameter SearchSpaceType is set to common.

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

When a C-RNTI is provided to the terminal device 1, a Type 0 PDCCH common search space, a Type 0a PDCCH common search space, a Type 1 PDCCH common search space, and/or a Type 2 PDCCH common search space may be used at least for DCI formats with a CRC sequence scrambled with the C-RNTI.

When a C-RNTI is provided to the terminal device 1, a search space set provided based at least on any of the upper layer parameter PDCCH-ConfigSIB1, the upper layer parameter SearchSpaceZero, the upper layer parameter SearchSpaceSIB1, the upper layer parameter SearchSpaceOtherSystemInformation, the upper layer parameter ra-SearchSpace, or the upper layer parameter PagingSearchSpace may be used at least for a DCI format with a CRC sequence scrambled with the C-RNTI.

A common CORESET may include at least one or both of CSS and USS. A dedicated CORESET may include at least one or both of CSS and USS.

The physical resources of the search area are composed of one or more control channel elements (CCEs). A CCE is composed of six resource element groups (REGs). A REG may be composed of one OFDM symbol of one PRB (Physical Resource Block). In other words, a REG may be composed of 12 resource elements (REs). A PRB may also be simply referred to as a resource block (RB).

The PDSCH is used at least to transmit the TB. The PDSCH may also be used at least to transmit a random access message 2 (RAR, Msg2). The PDSCH may also be used at least to transmit system information including parameters used for initial access.

In Fig. 1, the following downlink physical signals are used in downlink wireless communication: The downlink physical signals may not be used to transmit information output from higher layers, but are used by the physical layer.
・Synchronization signal
・DL DMRS (DownLink DeModulation Reference Signal)
・CSI-RS (Channel State Information-Reference Signal)
・DL PTRS (DownLink Phase Tracking Reference Signal)
・TRS (Tracking Reference Signal)

The synchronization signal is used by the terminal device 1 to synchronize the frequency domain and/or time domain of the downlink. The synchronization signal includes a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS).

An SSB (SS/PBCH block) is configured to include at least some or all of a PSS, SSS, and PBCH. The antenna ports of the PSS, SSS, and some or all of the PBCH included in the SS block may be the same. The PSS, SSS, and some or all of the PBCH included in the SSB may be mapped to consecutive OFDM symbols. The CP settings of the PSS, SSS, and some or all of the PBCH included in the SSB may be the same. The same value of SCS setting μ may be applied to the PSS, SSS, and some or all of the PBCH included in the SSB.

DL DMRS is related to the transmission of PBCH, PDCCH, and/or PDSCH. DL DMRS is multiplexed on PBCH, PDCCH, and/or PDSCH. The terminal device 1 may use the DL DMRS corresponding to the PBCH, the PDCCH, or the PDSCH to perform propagation path correction of the PBCH, the PDCCH, or the PDSCH. Hereinafter, the transmission of the PBCH and the DL DMRS associated with the PBCH may be referred to as the transmission of the PBCH. Also, the transmission of the PDCCH and the DL DMRS associated with the PDCCH may be simply referred to as the transmission of the PDCCH. Also, the transmission of the PDSCH and the DL DMRS associated with the PDSCH may be simply referred to as the transmission of the PDSCH. The DL DMRS associated with the PBCH may also be referred to as the DL DMRS for the PBCH. The DL DMRS associated with the PDSCH may also be referred to as a DL DMRS for the PDSCH. The DL DMRS associated with the PDCCH may also be referred to as a DL DMRS associated with the PDCCH.

The DL DMRS may be a reference signal that is individually set to the terminal device 1. The sequence of the DL DMRS may be given based at least on a parameter that is individually set to the terminal device 1. The sequence of the DL DMRS may be given based at least on a UE-specific value (e.g., C-RNTI, etc.). The DL DMRS may be transmitted individually for the PDCCH and/or the PDSCH.

The CSI-RS may be a signal used at least to calculate the CSI. The CSI-RS may also be used to measure RSRP (Reference Signal Received Power) and RSRQ (Reference Signal Received Quality). The CSI-RS pattern assumed by the terminal device 1 may be given by at least upper layer parameters.

The DL PTRS may be a signal used at least for phase noise compensation. The DL PTRS pattern assumed by the terminal device 1 may be based at least on higher layer parameters and/or DCI.

The DL PTRS may be associated with a DL DMRS group that includes at least an antenna port used for one or more DL DMRSs. The association of the DL PTRS with the DL DMRS group may be such that the antenna port of the DL PTRS and some or all of the antenna ports included in the DL DMRS group are at least QCL. The DL DMRS group may be identified based at least on the antenna port with the smallest index in the DL DMRS included in the DL DMRS group.

The TRS may be a signal used at least for time and/or frequency synchronization. The pattern of TRS assumed by the terminal device may be based at least on higher layer parameters and/or DCI.

The downlink physical channel and the downlink physical signal may also be referred to as downlink signals. The uplink physical channel and the uplink physical signal may also be referred to as uplink signals. The downlink signal and the uplink signal may also be referred to as physical signals or signals. The downlink physical channel and the uplink physical channel may also be referred to as physical channels. In the downlink, the physical signal may include some or all of SSB, PDCCH (CORESET), PDSCH, DL DMRS, CSI-RS, DL PTRS, and TRS. In the uplink, the physical signal may include some or all of PRACH, PUCCH, PUSCH, UL DMRS, UL PTRS, and SRS. The physical signal may be a signal other than the above-mentioned signals. That is, the physical signal may include one or more types of physical channels and/or physical signals, or may include one or more physical channels and/or physical signals.

BCH (Broadcast CHannel), UL-SCH (Uplink-Shared CHannel), and DL-SCH (Downlink-Shared CHannel) are transport channels. A channel used in the Medium Access Control (MAC) layer may be called a transport channel. The unit of the transport channel used in the MAC layer may be called a TB or MAC PDU. In the MAC layer, HARQ control is performed for each TB. A TB is a unit of data that the MAC layer delivers to the physical layer. In the physical layer, a TB is mapped to a codeword, and modulation processing is performed for each codeword.

The base station device 3 and the terminal device 1 exchange (transmit and receive) higher layer signals in a higher layer. For example, the base station device 3 and the terminal device 1 may transmit and receive RRC signaling (RRC messages, RRC information, RRC parameters, RRC information elements) in the radio resource control (RRC) layer. The base station device 3 and the terminal device 1 may also transmit and receive MAC CE (Control Element) in the MAC layer. Here, the RRC signaling and/or MAC CE are also referred to as higher layer signaling.

The PUSCH and the PDSCH may be used at least to transmit RRC signaling and/or MAC CE. Here, the RRC signaling transmitted from the base station device 3 on the PDSCH may be common signaling for multiple terminal devices 1 in the serving cell. The signaling common to multiple terminal devices 1 in the serving cell may also be referred to as common RRC signaling. The RRC signaling transmitted from the base station device 3 on the PDSCH may be dedicated signaling for a certain terminal device 1 (which may also be referred to as dedicated signaling or UE specific signaling). The signaling dedicated to the terminal device 1 may also be referred to as dedicated RRC signaling. The parameters of the upper layer specific to the serving cell may be transmitted using common signaling for multiple terminal devices 1 in the serving cell or dedicated signaling for a certain terminal device 1. UE-specific higher layer parameters may be transmitted using dedicated signaling for a certain terminal device 1.

BCCH (Broadcast Control CHannel), CCCH (Common Control CHannel), and DCCH (Dedicated Control CHannel) are logical channels. For example, BCCH is an upper layer channel used to transmit MIB. CCCH (Common Control CHannel) is an upper layer channel used to transmit information common 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) is an upper layer channel that is used at least to transmit dedicated control information to terminal device 1. Here, DCCH may be used, for example, for terminal devices 1 that are RRC-connected.

The BCCH in the logical channel may be mapped to the BCH, DL-SCH, or UL-SCH in the transport channel. The CCCH in the logical channel may be mapped to the DL-SCH or UL-SCH in the transport channel. The DCCH in the logical channel may be mapped to the DL-SCH or UL-SCH in the transport channel.

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

Below, we will explain an example configuration of a terminal device 1 related to one aspect of this embodiment.

Figure 5 is a schematic block diagram showing the configuration of a terminal device 1 according to one aspect of this embodiment. As shown in the figure, the terminal device 1 includes a radio transmission/reception unit 10 and an upper layer processing unit 14. The radio transmission/reception unit 10 includes at least an antenna unit 11, an RF (Radio Frequency) unit 12, and a part or all of a baseband unit 13. The upper layer processing unit 14 includes at least a medium access control layer processing unit 15, and a part or all of a radio resource control layer processing unit 16. The radio transmission/reception unit 10 may also be referred to as a transmitting unit, a receiving unit, a physical layer processing unit, and/or a lower layer processing unit.

The upper layer processing unit 14 outputs uplink data (TB, UL-SCH) generated by user operation, etc., to the wireless transceiver unit 10. The upper layer processing unit 14 processes the MAC layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and RRC layer.

The media access control layer processing unit 15 provided in the upper layer processing unit 14 performs processing of the MAC layer.

The radio resource control layer processing unit 16 included in the upper layer processing unit 14 performs RRC layer processing. The radio resource control layer processing unit 16 manages various setting information/parameters of the own device. The radio resource control layer processing unit 16 sets various setting information/parameters based on upper layer signals received from the base station device 3. In other words, the radio resource control layer processing unit 16 sets various setting information/parameters based on information indicating the various setting information/parameters received from the base station device 3. The parameters may be upper layer parameters and/or information elements.

The wireless transceiver unit 10 performs physical layer processing such as modulation, demodulation, encoding, and decoding. The wireless transceiver unit 10 separates, demodulates, and decodes the received physical signal, and outputs the decoded information to the upper layer processing unit 14. These processes may be referred to as reception processing. The wireless transceiver unit 10 generates a physical signal (uplink signal) by modulating, encoding, and generating a baseband signal (converting to a time-continuous signal) on the data, and transmits the physical signal to the base station device 3. These processes may be referred to as transmission processing.

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

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

The baseband unit 13 performs an inverse fast Fourier transform (IFFT) on the data to generate OFDM symbols, adds a CP to the generated OFDM symbols, generates 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.

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

Below, we will explain an example configuration of a base station device 3 related to one aspect of this embodiment.

Figure 6 is a schematic block diagram showing the configuration of a base station device 3 according to one aspect of this embodiment. As shown in the figure, the base station device 3 includes a radio transmission/reception unit 30 and an upper layer processing unit 34. The radio transmission/reception unit 30 includes an antenna unit 31, an RF unit 32, and a baseband unit 33. The upper layer processing unit 34 includes a medium access control layer processing unit 35 and a radio resource control layer processing unit 36. The radio transmission/reception unit 30 is also referred to as a transmitting unit, a receiving unit, or a physical layer processing unit.

The upper layer processing unit 34 performs processing of the MAC layer, PDCP layer, RLC layer, and RRC layer.

The media access control layer processing unit 35 provided in the upper layer processing unit 34 performs processing of the MAC layer.

The radio resource control layer processing unit 36 included in the upper layer processing unit 34 performs processing of the RRC layer. The radio resource control layer processing unit 36 generates downlink data (TB, DL-SCH), system information, RRC messages, MAC CE, etc. to be placed in the PDSCH, or acquires them from the upper node, and outputs them to the radio transceiver unit 30. The radio resource control layer processing unit 36 also manages various setting information/parameters for each terminal device 1. The radio resource control layer processing unit 36 may set various setting information/parameters for each terminal device 1 via signals from the upper layer. That is, the radio resource control layer processing unit 36 transmits/reports information indicating various setting information/parameters.

The basic functions of the wireless transceiver unit 30 are the same as those of the wireless transceiver unit 10, so a description thereof will be omitted. The wireless transceiver unit 30 transmits the physical signal generated in the wireless transceiver unit 30 to the terminal device 1 (i.e., performs transmission processing). The wireless transceiver unit 30 also performs reception processing of the received physical signal.

The medium access control layer processing unit 15 and/or 35 may be referred to as a MAC entity.

Each of the units numbered 10 to 16 in the terminal device 1 may be configured as a circuit. Each of the units numbered 30 to 36 in the base station device 3 may be configured as a circuit. Some or all of the units numbered 10 to 16 in the terminal device 1 may be configured as a memory and a processor connected to the memory. Some or all of the units numbered 30 to 36 in the base station device 3 may be configured as a memory and a processor connected to the memory. Various aspects (operations, processing) of this embodiment may be realized (performed) in the memory included in the terminal device 1 and/or the base station device 3 and the processor connected to the memory.

Next, we will explain the DL PT-RS related to this embodiment.

Here, the PT-RS transmitted by the terminal device 1 may be referred to as the UL PT-RS, and the PT-RS received by the terminal device 1 may be referred to as the DL PT-RS. Note that, in the case where sidelink transmission and reception is possible in the terminal device 1, the transmission and reception of the SL PT-RS may be possible. If the PT-RS is included in the PUSCH transmission, it may be referred to as the PT-RS for the PUSCH. If the PT-RS is included in the PDSCH transmission, it may be referred to as the PT-RS for the PDSCH.

The PT-RS reception procedure in the terminal device 1 in this embodiment is described below.

The terminal device 1 may report a desired MCS and bandwidth threshold for each SCS applied to a data channel (PDSCH, PDCCH, PBCH, PCH, MIB, SIB) at a particular carrier frequency based on the capabilities (UE capabilities) of the terminal device 1 at the particular carrier frequency, assuming an MCS table with the maximum modulation order that it reports as being supported.

If the terminal device 1 has the higher layer parameter phaseTrackingRS in DMRS-DownlinkConfig set, the higher layer parameters timeDensity and frequencyDensity in PTRS-DownlinkConfig may indicate respective thresholds, ptrs-MCSi (i=1,2,3) and N _RBi (i=0,1). Here, the higher layer parameter phaseTrackingRS in DMRS-DownlinkConfig may be provided by setting up and/or releasing PTRS-DownlinkConfig. If either or both of the higher layer parameters timeDensity and/or frequencyDensity in PTRS-DownlinkConfig are set and RNTI is the same value as MCS-C-RNTI, C-RNTI, or CS-RNTI, the terminal device 1 assumes the function (role) of the scheduled MCS and scheduled bandwidth of the corresponding codeword in the corresponding BWP where the presence and pattern of PT-RS antenna ports are shown in FIG. 7. If the higher layer parameter timeDensity is not set, the terminal device 1 may assume that L _PT-RS = 1. If the higher layer parameter frequencyDensity is not set, the terminal device 1 may assume that K _PT-RS = 2. If both the higher layer parameters timeDensity and frequencyDensity in PTRS-DownlinkConfig are set and the RNTI has the same value as the MCS-C-RNTI, C-RNTI, or CS-RNTI, the terminal device 1 may assume that a PT-RS with L _PT-RS = 1 and K _PT-RS = 2 exists. If the scheduled MCS index in FIG. 8 is smaller than 10, or the scheduled MCS index in FIG. 9 is smaller than 5, or the scheduled MCS index in FIG. 10 is smaller than 15, or the number of scheduled RBs (bandwidth) is smaller than 3RBs, the terminal device 1 may assume that the PT-RS (DL PT-RS) does not exist. Otherwise, if the RNTI is the same value as the RA-RNTI, SI-RNTI, or P-RNTI, the terminal device 1 may assume that the PT-RS does not exist. Here, the values of the MCS indexes in FIG. 8, FIG. 9, and FIG. 10 may be given by the DCI format used to schedule the PDSCH, or may be given based on higher layer parameters. In other words, the base station device 3 does not need to transmit the PT-RS together with the PDSCH if these conditions are met.

FIG. 7 is a diagram showing a table used to provide respective thresholds ptrs-MCSi given by timeDensity and frequencyDensity according to one embodiment of the present invention, and a mapping pattern of PT-RS based on N _RBi and scheduled MCS (I _MCS ) and bandwidth (N _RB ).

FIG. 7(a) is a table showing a time domain mapping pattern (L _PT-RS ) of PT-RS based on the threshold ptrs-MCSi given by timeDensity and the scheduled MCS (I _MCS ).

FIG. 7(b) is a table showing a mapping pattern (K _PT-RS ) of the PT-RS in the frequency domain based on the threshold N _RBi and the scheduled bandwidth (N _RB ) given by frequencyDensity.

Figure 8 is a diagram showing MCS index table 1 (an example of an MCS index table) relating to one aspect of this embodiment.

Figure 9 is a diagram showing an MCS index table 2 (another example 1 of an MCS index table) relating to one aspect of this embodiment.

Figure 10 is a diagram showing an MCS index table 3 (another example 2 of an MCS index table) relating to one aspect of this embodiment.

Each MCS index table is used to indicate the relationship between the MCS index I _MCS and the modulation order, the target code rate, and the spectral efficiency. The MCS index may be indicated via DCI or by higher layer parameters.

If the upper layer parameter phaseTrackingRS in DMRS-DownlinkConfig is not set, the terminal device 1 may assume that a PT-RS does not exist.

The higher layer parameter timeDensity in PTRS-DownlinkConfig may be used to provide ptrs-MCS _i (i=1,2,3). ptrs-MCS _i (i=1,2,3), i.e., ptrs-MCS ₁ , ptrs-MCS ₂ , and ptrs-MCS ₃ may be configured with MCS indexes 0 to 29 in FIG. 8 or FIG. 10 when FIG. 8 or FIG. 10 is used, and with MCS indexes 0 to 28 in FIG. 9 when FIG. 9 is used. ptrs-MCS ₄ is not explicitly configured by higher layers, but may be assumed to be 29 when FIG. 8 or FIG. 10 is used, and 28 when FIG. 9 is used. Note that the values of ptrs-MCS ₁ , ptrs-MCS ₂ , and ptrs-MCS ₃ may be given to satisfy 0≦ptrs-MCS ₁ ≦ptrs-MCS ₂ ≦ptrs-MCS ₃ ≦29 or 28, respectively.

The higher layer parameter frequencyDensity in PTRS-DownlinkConfig may be used to provide N _RBi (i=0,1). N _RBi (i=0,1), i.e., N _RB0 and N _RB1, may each be configured with a value from 1 to 276. Note that the values of N _RB0 and N _RB1 may each be given to satisfy 1≦N _RB0 ≦N _RB1 ≦276.

If the higher layer parameter timeDensity in PTRS-DownlinkConfig indicates a time density threshold ptrs-MCS _i = ptrs-MCS _i+1 , then the time density L _PT-RS of the relevant table row where both thresholds exist in Fig. 7(a) may be considered not valid. For example, if ptrs-MCS ₁ = ptrs-MCS ₂ , then the second row in Fig. 7(a) (the row with ptrs-MCS ₁ = < I _MCS < ptrs-MCS ₂ ) may be considered not valid.

If the higher layer parameter frequencyDensity in PTRS-DownlinkConfig indicates a frequency density threshold N _RBi =N _RBi+1 , then the frequency density K _PT-RS of the relevant table row indicated by both of these thresholds in Fig. 7(b) may be considered not valid. For example, if N _RB0 =N _RB1 , then the second row in Fig. 7(b) (the row where N _RB0 =< N _RB < N _RB1 ) may be considered not valid.

In FIG. 7, if either or both of the PT-RS time density (L _PT-RS ) and the PT-RS frequency density (K _PT-RS ) are set as “PT-RS not present,” the terminal device 1 may assume that a PT-RS is not present.

When the terminal device 1 receives a PDSCH with an allocation period of 2 symbols or less, and if the L _PT-RS is set to 2 or 4, the terminal device 1 may assume that the PT-RS is not transmitted. Also, when the terminal device 1 receives a PDSCH with an allocation period of 4 symbols or less, and if the L _PT-RS is set to 4, the terminal device 1 may assume that the PT-RS is not transmitted.

When the terminal device 1 is scheduled to transmit the PDSCH for retransmission, if the terminal device 1 is scheduled with I _MCS >V, the MCS for PT-RS time density determination may be obtained from the DCI for the same transport block of the initial transmission, where V may be the MCS index 28 in Figures 8 and 10 and the MCS index 27 in Figure 9. The MCS obtained from the DCI for the same transport block of the initial transmission may be less than or equal to V.

One or more DL DM-RS ports associated with one PT-RS port may be assumed to be quasi co-location (QCL) associated with {'QCL-TypeA' and 'QCL-TypeD'}. If the terminal device 1 is scheduled with one codeword, the PT-RS antenna port may be associated with the DM-RS antenna port with the lowest index among the multiple DM-RS antenna ports assigned to the PDSCH.

If the terminal device 1 is scheduled with two codewords, the PT-RS antenna port may be associated with the DM-RS antenna port with the lowest index among the multiple DM-RS antenna ports assigned to the codeword with the highest MCS (MCS index). If the MCS index of the two codewords is the same value, the PT-RS antenna port may be associated with the DM-RS antenna port with the lowest index assigned to codeword 0.

Next, we will explain sequence generation and mapping to physical resources of PT-RS for PDSCH in this embodiment.

The sequence of PT-RS for subcarrier k may be given by r _k =r(2m+k′), where r(2m+k′) is the sequence of DM-RS given at position l ₀ and subcarrier k.

The terminal device 1 may assume that the PT-RS is only present in one or more resource blocks used for the PDSCH.

If a PT-RS is present, the terminal device 1 scales the PT-RS by a factor β _PT-RS,i to match its transmission power and maps it to a resource element (k,l) _p,μ corresponding to α ^(p,μ) _k,l =β _PT-RS,i r _k , where l is within one or more OFDM symbols configured for PDSCH transmission. Resource element (k,l) _p,μ may not be used for DM-RS, non-zero power CSI-RS, zero power CSI-RS, SS/PBCH blocks, detected PDCCH, or physical resources declared as 'not available'.

11 is a flow diagram showing a set of one or more time indexes l defined in relation to the start of PDSCH configuration according to one aspect of this embodiment. In step 1101, the terminal device 1 sets i=0 and _lref =0. In step 1102, if any symbol in the interval max( _lref +(i-1) _LPT-RS +1, _lref ),..., _lref +iLPT _-RS overlaps with a symbol used for DM-RS, the terminal device 1 sets i=1, sets _lref to the symbol index of the DM-RS symbol in the case of single-symbol DM-RS, or to the symbol index of the second DM-RS symbol in the case of double-symbol DM-RS, and repeats step 1102 as long as _lref +iLPT _-RS is in the PDSCH configuration. In step 1103, the terminal device 1 adds l _ref +iL _PT-RS to the set of time indexes of PT-RS. In step 1104, the terminal device 1 increments i by 1. In step 1105, the terminal device 1 repeats step 1102 until l _ref +iL _PT-RS exceeds the PDSCH configuration, where L _PT-RS ∈{1, 2, 4}.

The PT-RS is mapped to an OFDM symbol that follows the OFDM symbol to which the reference DM-RS is mapped.

For the purpose of PT-RS mapping, the resource block(s) allocated for PDSCH transmission are numbered from 0 to N _RB −1, from the lowest scheduled resource block to the highest. The subcarriers corresponding to a set of one or more resource blocks are numbered from 0 to N ^RB _SC N _RB −1, starting from the lowest frequency. The subcarriers to which the terminal device 1 assumes the PT-RS are mapped may be given by FIG. 12.

FIG. 12 is a diagram showing an example of a calculation formula used to assume a subcarrier k to which a PT-RS is mapped according to one aspect of the present embodiment. i is 0, 1, 2, .... ^{k RE} _ref may be given by FIG. 13 showing an offset (frequency offset) corresponding to a DM-RS port associated with a PT-RS port. If the higher layer parameter resourceElementOffset in PTRS-DownlinkConfig is not set, one or more values shown in the column corresponding to offset00 may be used. _{n RNTI} is the RNTI associated with the DCI that schedules the transmission. N _RB is the number of scheduled resource blocks. _{K PT-RS} may be given by the procedure related to FIG. 7. ^{k RE} _ref may correspond to a frequency offset at the RE level within one RB. _{iK PT-RS} and k ^RB _ref may correspond to a frequency offset at the RB level.

13 is a diagram showing a correspondence relationship of k ^RE _ref according to one aspect of the present embodiment. ^{k RE} _ref may be determined based on the value of the DM-RS antenna port p, the DM-RS Configuration type, and resourceElementOffset.

If the bandwidth scheduled for the PDSCH is smaller than a predetermined bandwidth, the terminal device 1 may assume that the PT-RS does not exist in the PDSCH. Here, if coverage enhancement is indicated for the downlink based on the higher layer parameters or DCI, the terminal device 1 may perform reception processing assuming that the PT-RS exists in the PDSCH even if the PDSCH is scheduled with a bandwidth smaller than the predetermined bandwidth. In other words, when coverage enhancement can be performed for the downlink and when the base station device 3 schedules the PDSCH with a bandwidth smaller than the predetermined bandwidth, the base station device 3 may transmit the PT-RS together with the PDSCH with the frequency density K _PT-RS set to a predetermined value.

When the scheduled bandwidth is smaller than 1 PRB and there are multiple DM-RS antenna ports, some of the resourceElementOffsets listed in FIG. 13 may not be selected. For example, when the scheduled bandwidth is 10 subcarriers, offset11 may not be selected for DM-RS Configuration type1, and offset10 and offset11 may not be selected for DM-RS Configuration type2. That is, the selectable offset may be limited according to the number of subcarriers of the scheduled bandwidth. Alternatively, the terminal device 1 may perform a MOD operation on the value of k ^RE _ref corresponding to each antenna port and offset with the total number of DM-RS antenna ports, and use the obtained value as k ^RE _ref corresponding to each DM-RS antenna port.

When the base station device 3 schedules PDSCH transmission with a bandwidth smaller than one PRB and transmits a PT-RS together with the PDSCH, it does not need to set the higher layer parameter frequencyDensity in PTRS-DownlinkConfig for the terminal device 1. Based on this setting, the terminal device 1 can always perform reception processing assuming that a PT-RS exists together with the PDSCH.

Note that the terminal device 1 does not need to expect that the total number of used DM-RS antenna ports is greater than the number of subcarriers in the scheduled bandwidth. In other words, it is not needed to expect that a plurality of DM-RS antenna ports are shared with one k ^RE _ref . The base station device 3 does not need to schedule a PDSCH such that the total number of used DM-RS antenna ports is greater than the number of subcarriers in the scheduled bandwidth.

Next, we will explain the UL PT-RS related to this embodiment.

If the upper layer parameter phaseTrackingRS included in DMRS-UplinkConfig is not set, the terminal device 1 does not need to transmit a PT-RS (UL PT-RS).

The UL PT-RS may only be present (mapped) in a PUSH scheduled by a PDCCH with a CRC scrambled by MCS-C-RNTI, C-RNTI, CS-RNTI, SP-CSI-RNTI, or a PUSH corresponding to a CUL (Configured UL, configured grant).

Next, we will explain the PT-RS transmission procedure in terminal device 1 when modified precoding related to one aspect of this embodiment is not enabled.

When modified precoding is not enabled, and if the upper layer parameter phaseTrackingRS in the DMRS-UplinkConfig is configured by the terminal device 1, the upper layer parameters timeDensity and frequencyDensity in the PTRS-UplinkConfig may indicate respective thresholds, ptrs-MCSi (i=1,2,3) and N _RBi (i=0,1). Here, the upper layer parameter phaseTrackingRS in the DMRS-UplinkConfig may be provided by setting up and/or releasing the PTRS-UplinkConfig. If either or both of the upper layer parameters timeDensity and/or frequencyDensity in the PTRS-UplinkConfig are configured, the terminal device 1 assumes the presence and pattern of the PT-RS antenna ports as a function (role) of the corresponding scheduled MCS and scheduled bandwidth in the corresponding BWP shown in FIG. 7. If the upper layer parameter timeDensity is not configured, the terminal device 1 may assume L _PT-RS =1. Also, if the higher layer parameter frequencyDensity is not set, the terminal device 1 may assume that K _PT-RS = 2. If neither the higher layer parameters timeDensity nor frequencyDensity in PTRS-UplinkConfig is set, the terminal device 1 may assume that L _PT-RS = 1 and K _PT-RS = 2.

The higher layer parameter PTRS-UplinkConfig may be used to provide ptrs-MCS _i ( _i =1,2,3), i.e., ptrs-MCS ₁ , ptrs-MCS ₂ , and ptrs-MCS ₃ may be configured with MCS indexes 0-29 in Figure 8 when Figure 8 is used, and with MCS indexes 0-28 in Figure 9 when Figure 9 is used. Ptrs-MCS ₄ is not explicitly configured by higher layers, but may be assumed to be 29 when Figure 8 is used, and 28 when Figure 9 is used.

The higher layer parameter frequencyDensity in PTRS-UplinkConfig may be used to provide N _RBi (i=0,1). N _RBi (i=0,1), i.e., N _RB0 and N _RB1, may each be configured with a value from 1 to 276. Note that the values of N _RB0 and N _RB1 may each be given to satisfy 1≦N _RB0 ≦N _RB1 ≦276.

If the higher layer parameter timeDensity in PTRS-UplinkConfig indicates a time density threshold ptrs-MCS _i = ptrs-MCS _i+1 , then the time density L _PT-RS of the relevant table row where both thresholds exist in Fig. 7(a) may be considered not valid. For example, if ptrs-MCS ₁ = ptrs-MCS ₂ , then the second row in Fig. 7(a) (the row with ptrs-MCS ₁ = < I _MCS < ptrs-MCS ₂ ) may be considered not valid.

If the higher layer parameter frequencyDensity in PTRS-UplinkConfig indicates a frequency density threshold N _RBi =N _RBi+1 , then the frequency density K _PT-RS of the relevant table row in Fig. 7(b) where both thresholds exist may be considered not valid. For example, if N _RB0 =N _RB1 , then the second row in Fig. 7(b) (row where N _RB0 =< N _RB < N _RB1 ) may be considered not valid.

In FIG. 7, if either or both of the PT-RS time density (L _PT-RS ) and the PT-RS frequency density (K _PT-RS ) are set as “PT-RS not present,” the terminal device 1 may assume that a PT-RS is not present.

When the terminal device 1 is scheduled to transmit a PUSCH with an allocation period of 2 symbols or less, and if L _PT-RS is set to 2 or 4, the terminal device 1 does not need to transmit a PT-RS. Also, when the terminal device 1 is scheduled to transmit a PUSCH with an allocation period of 4 symbols or less, and if L _PT-RS is set to 4, the terminal device 1 does not need to transmit a PT-RS.

When the terminal device 1 is scheduled to transmit a PUSCH for retransmission, if the terminal device 1 is scheduled with I _MCS >V, the MCS for PT-RS time density determination may be obtained from the DCI for the same transport block of the initial transmission, where V may be the MCS index 28 in Fig. 8 or the MCS index 27 in Fig. 9. The MCS obtained from the DCI for the same transport block of the initial transmission may be less than or equal to V.

The maximum number of configured PT-RS ports may be given by the upper layer parameter maxNrofPorts in PTRS-UplinkConfig. The terminal device 1 is not expected to be configured with a number of PT-RS ports greater than the number of PT-RS ports configured in maxNrofPorts. The number of PT-RS ports may be the number of PT-RS antenna ports.

If the terminal device 1 reports capability information indicating that it supports full coherent UL transmission, the terminal device 1 may expect that if a UL PT-RS is configured, the number of UL PT-RS ports will be set to 1. In other words, if the base station device 3 receives a report of capability information from the terminal device 1 indicating that it supports full coherent UL transmission, the base station device 3 may set the number of UL PT-RS ports for the terminal device 1 to 1.

For UL transmissions based on a codebook or non-codebook, the association between one or more UL PT-RS ports and one or more DM-RS ports may be signaled by the PT-RS association field of DCI format 0_1. For a PUSH corresponding to a CUL type 1 transmission, the terminal device 1 may assume an association between one or more PT-RS ports and one or more DM-RS ports by a value of 0 in the PTRS-DMRS association for UL PTRS port 0 field or a value of 00 in the PTRS-DMRS association for UL PTRS port 0 and 1 field in DCI format 0_1.

For a PUSH scheduled by DCI format 0_0 or activation DCI format 0_0, the UL PT-RS port may be associated with DM-RS port 0.

For non-codebook based UL transmission, the actual number of UL PT-RS ports for transmission may be determined based on the SRS resource indicator (SRI) in DCI format 0_1 or the higher layer parameter sri-ResourceIndicator in rrc-ConfiguredUplinkGrant. If the terminal device 1 configures the higher layer parameter phaseTrackingRS in DMRS-UplinkConfig, the PT-RS port index for each configured SRS resource may be configured by the higher layer parameter ptrs-PortIndex configured by SRS-Config. If the PT-RS port indexes associated with different SRIs are the same, the corresponding one or more UL DM-RSs may be associated with one PT-RS port.

For UL transmissions based on partial coherent and non-coherent codebooks, the actual number of UL PT-RS ports may be determined based on the Transmit Precoding Matrix Indicator (TPMI) in DCI format 0_1, and/or the Transmit Rank Indicator (TRI), and/or the number of layers indicated by the Precoding information and number of layers field in DCI format 0_1, and/or the number of layers set by the higher layer parameter precodingAndNumberOfLayers. Assuming that the higher layer parameter maxNrofPorts in PTRS-UplinkConfig is set to 'n2', the actual UL PT-RS ports and associated transmission layers are obtained from the indicated TPMI, and PUSCH antenna ports 1000 and 1002 in the indicated TPMI share PT-RS port 0, and PUSCH antenna ports 1001 and 1003 in the indicated TPMI share PT-RS port 1. UL PT-RS port 0 may be associated with UL layer [x] of the multiple layers transmitted with PUSCH antenna ports 1000 and 1002 in the indicated TPMI, and UL PT-RS port 1 may be associated with UL layer [y] of the multiple layers transmitted with PUSCH antenna ports 1001 and 1003 in the indicated TPMI. UL layer [x] and/or [y] may be given by the PTRS-DMRS association field in DCI format 0_1.

When the terminal device 1 is scheduled with PT-RS ports of Q _p = {1,2} (one PT-RS port or two PT-RS ports) in the uplink and the number of scheduled layers is n ^PUSCH _layers , if the terminal device 1 is configured with a higher layer parameter ptrs-Power, the PUSCH to PT-RS power ratio ρ ^PUSCH _PTRS per RE per layer may be given by ρ ^PUSCH _PTRS = -α ^PUSCH _PTRS [dB]. Q _p may be used to indicate the number of PT-RS ports. α ^PUSCH _PTRS is shown by FIG. 14 corresponding to the higher layer parameter ptrs-Power, and the PT-RS scaling factor β _PTRS may be given by β _PTRS = 10^ (-ρ ^PUSCH _PTRS / 20) and in the Precoding Information and Number of Layers of the DCI. In the case of a non-codebook-based PUSCH or if ptrs-Power is not set, the terminal device 1 may assume that PTRS-UplinkConfig is set to state "00". Fig. 14 is a table diagram showing α ^PUSCH _PTRS according to one aspect of the present embodiment. α ^PUSCH _PTRS may be determined based on the number of PUSCH layers, the type of PUSCH transmission scheme, and the type of codebook subset.

Next, we will describe the PT-RS transmission procedure in terminal device 1 when modified precoding related to one aspect of this embodiment is enabled.

When modified precoding is enabled, and if the terminal device 1 sets the upper layer parameter transformPrecoderEnabled in PTRS-UplinkConfig, the terminal device 1 assumes that one or more upper layer parameters sampleDensity are set, and the terminal device 1 assumes that the presence of PT-RS antenna ports and the PT-RS group pattern are a function of the corresponding scheduled bandwidth in the corresponding BWP, as shown in FIG. 15. The terminal device 1 may assume that the PT-RS does not exist when _NRB0 >1, or when the RNTI is the same value as the TC-RNTI and the number of scheduled RBs (bandwidth) is less (smaller) than _NRB0 . The terminal device 1 may set _LPT-RS =2 based on the upper layer parameter timeDensityTransformPrecoding. Otherwise, the terminal device 1 may assume that _LPT-RS =1 when modified precoding is enabled. If the higher layer parameter sampleDensity indicates that the sample density threshold N _RBi =N _RBi+1 , the relevant row in which both thresholds exist in Fig. 15 is not valid. For example, if N _RB0 =N _RB1 , the top row (row where N _RB0 =< N _RB <N _RB1 ) in Fig. 15 is not valid. Fig. 15 is a diagram showing a PUSCH DM-RS configuration type according to one aspect of the present embodiment.

The higher layer parameter sampleDensity in PTRS-UplinkConfig may be used to provide N _RBi (i=0,1,2,3,4). N _RBi (i=0,1,2,3,4), i.e., N _RB0 , N _RB1 , N _RB2 , N _RB3 , and N _RB4 , may each be configured with a value from 1 to 276. Note that the values of N _RB0 , N _RB1 , N _RB2 , N _RB3 , and N _RB4 may each be given a value such that 1≦N _RB0 ≦N _RB1 ≦N _RB2 ≦N _RB3 ≦N _RB4 ≦276 is satisfied.

When modified precoding is enabled, and if the upper layer parameter transformPrecoderEnabled in the PTRS-UplinkConfig of the terminal device 1 is set, the PT-RS scaling factor β' may be determined by the scheduled modulation order as shown in Figure 16. Figure 16 is a diagram showing the PT-RS scaling factor when modified precoding according to one aspect of the present embodiment is enabled.

Next, we will explain sequence generation and mapping to physical resources of PT-RS for PUSH in one embodiment of this invention.

If modified precoding is not enabled, the precoded PT-RS for subcarrier k of layer j may be given based on the sequence generation of Figure 17.

Figure 17 is a diagram showing the generation of a sequence of PT-RS for PUSCH when modified precoding according to one aspect of the present embodiment is not enabled. The antenna port associated with the PT-RS transmission may be given based on the procedure described above. r(m) may be given based on the sequence of DM-RS for PUSCH. r(m) may be given at the position of the first DM-RS symbol if no PUSCH intra-slot frequency hopping is performed, or at the position of the first DM-RS symbol per hop if PUSCH intra-slot frequency hopping is performed.

If modified precoding is enabled, the sequence r _m (m′) of the PT-RS mapped at position m before modified precoding may be generated based on the sequence generation in FIG.

FIG. 18 is a diagram showing sequence generation of PT-RS for PUSCH when modified precoding according to one aspect of the present embodiment is enabled. m according to this embodiment may be based on the number of PT-RS groups N ^PT-RS _group , the number of samples per PT-RS group N ^group _samp , and the number of subcarriers M ^PUSCH _SC corresponding to the scheduled bandwidth used for PUSCH transmission. c(i) is a pseudo-random sequence, and the pseudo-random sequence generator may be initialized with c _init at a certain timing. l is the lowest OFDM symbol number in the PUSCH arrangement in slot n ^μ _s,f including PT-RS. N _ID may be given by the higher layer parameter nPUSCH-Identity. w(i) may be given by FIG. 19. FIG. 19 is a diagram showing an example of an orthogonal sequence w(i) according to one aspect of the present embodiment.

Next, we will describe precoding and mapping to physical resources when modified precoding in one aspect of this embodiment is not enabled.

If the PT-RS transmission procedure of terminal device 1 indicates that PT-RS is used, terminal device 1 transmits PT-RS only in one or more resource blocks used for PUSH.

The PT-RS may be mapped to resource elements according to FIG. 20. FIG. 20 is a diagram showing mapping of PT-RS according to one embodiment of the present invention. l is any of the OFDM symbols arranged for PUSCH transmission. The resource elements used for PT-RS are not used for DM-RS. k′ and Δ correspond to antenna ports and may be given by FIG. 21 and the DM-RS configuration type. The DM-RS configuration type may be given by the higher layer parameter DMRS-UplinkConfig. The precoding matrix W may be given based on the corresponding PUSCH. _{β PT-RS} is a scaling factor used to match the specified transmission power. FIG. 21 is a diagram showing various parameters for the DM-RS configuration type according to one embodiment of the present invention.

22 is a flow diagram showing a set of one or more time indexes l defined in relation to the start of a PUSCH arrangement when modified precoding according to one aspect of the present embodiment is not enabled. In step 2201, the terminal device 1 sets i=0 and _lref =0. In step 2202, if any symbol in the interval max( _lref +(i-1) _LPT-RS +1, _lref ),..., _lref + _iLPT-RS overlaps with a symbol used for DM-RS, the terminal device 1 sets i=1, sets _lref to the symbol index of the DM-RS symbol in the case of single-symbol DM-RS, and sets lref to the symbol index of the second DM-RS symbol in the case of double-symbol DM-RS, and repeats step 2202 as long as _lref + _iLPT-RS is in the PUSCH arrangement. In step 2203, the terminal device 1 adds l _ref +iL _PT-RS to the set of time indexes of PT-RS. In step 2204, the terminal device 1 increments i by 1. In step 2205, the terminal device 1 repeats step 2202 until l _ref +iL _PT-RS exceeds the PUSCH configuration, where L _PT-RS ∈{1, 2, 4}.

The PT-RS is mapped to an OFDM symbol that follows the OFDM symbol to which the reference DM-RS is mapped.

For the purpose of PT-RS mapping, the resource block or blocks allocated for PUSCH transmission are numbered from 0 to N _RB −1, from the lowest scheduled resource block to the highest. The subcarriers corresponding to a set of one or more resource blocks are numbered from 0 to N ^RB _SC N _RB −1, starting from the lowest frequency. The subcarriers to which the terminal device 1 assumes the PT-RS are mapped may be given by FIG. 23.

FIG. 23 is a diagram showing a calculation formula used to assume a subcarrier k to which a PT-RS is mapped according to one aspect of the present embodiment. i is 0, 1, 2, .... ^{k RE} _ref may be given by FIG. 24 showing an offset (frequency offset) for a DM-RS port associated with a PT-RS port. If the higher layer parameter resourceElementOffset in PTRS-DownlinkConfig is not set, one or more values shown in the column corresponding to offset00 may be used. n _RNTI is the RNTI associated with the C-RNTI, CS-RNTI, MCS-C-RNTI, DCI scheduling transmission using SP-CSI-RNTI, or CS-RNTI in case of CUL (Configured UL, configured grant). N _RB is the number of scheduled resource blocks. _{K PT-RS} may be given by the procedure related to FIG. 7. k ^RE _ref may correspond to a frequency offset at the RE level within one RB, and _{iK PT-RS} and k ^RB _ref may correspond to a frequency offset at the RB level.

24 is a diagram showing a correspondence relationship of k ^RE _ref according to one aspect of the present embodiment. ^{k RE} _ref may be determined based on the value of the DM-RS antenna port p, the DM-RS Configuration type, and resourceElementOffset.

Next, we explain the mapping to physical resources when modified precoding is enabled.

If the PT-RS transmission procedure of terminal device 1 indicates that PT-RS is used, terminal device 1 transmits PT-RS only in one or more resource blocks used for PUSH.

The sequence r(m') is multiplexed by β' and mapped to N ^group _samp N ^PT-RS _group complex-valued symbols in χ ⁰ (m), where ^{χ 0} (m) is one or more complex-valued symbols in OFDM symbol l before modified precoding. m may be based on the number of PT-RS groups N ^PT-RS _group , the number of samples per PT-RS group N ^group _samp , and the number of subcarriers M ^PUSCH _SC corresponding to the scheduled bandwidth used for PUSCH transmission according to FIG. 25. s in FIG. 25 may correspond to a value obtained based on the number of PT-RS groups, and k in FIG. 25 may correspond to a value obtained based on the number of samples per PT-RS group. β′ is the ratio between the amplitude of one of the outermost constellation points for π/2-BPSK and the amplitude of one of the outermost constellation points for the modulation scheme used for PUSCH. Figure 25 shows a PT-RS symbol mapping according to one aspect of this embodiment.

26 is a flow diagram showing a set of one or more time indexes l defined in relation to the start of a PUSCH arrangement when modified precoding according to one aspect of the present embodiment is not enabled. In step 2601, the terminal device 1 sets i=0 and _lref =0. In step 2602, if any symbol in the interval max( _lref +(i-1) _LPT-RS +1, _lref ),..., _lref + _iLPT-RS overlaps with a symbol used for DM-RS, the terminal device 1 sets i=1, sets _lref to the symbol index of the DM-RS symbol in the case of single-symbol DM-RS, and sets lref to the symbol index of the second DM-RS symbol in the case of double-symbol DM-RS, and repeats step 2602 as long as _lref + _iLPT-RS is in the PUSCH arrangement. In step 2603, the terminal device 1 adds l _ref +iL _PT-RS to the set of time indexes of PT-RS. In step 2604, the terminal device 1 increments i by 1. In step 2605, the terminal device 1 repeats step 2602 until l _ref +iL _PT-RS exceeds the PUSCH configuration. Here, L _PT-RS ∈{1,2}, and the value of L _PT-RS may be given by the higher layer parameter timeDensityTransformPrecoding in PTRS-UplinkConfig. timeDensityTransformPrecoding may be used when the OFDM symbol level time density L _PT-RS of PT-RS for DFT-s-OFDM indicates 2. If timeDensityTransformPrecoding is not configured, the terminal device 1 may apply L _PT-RS as 1.

Next, a PT-RS transmission procedure in coverage enhancement according to one aspect of this embodiment will be described. Here, the terminal device 1 and the base station device 3 support at least one capability among various capabilities related to coverage enhancement. In response to an inquiry from the base station device 3, the terminal device 1 may transmit information indicating that it supports capabilities related to coverage enhancement to the base station device 3.

When modified precoding is not enabled, if the upper layer parameter phaseTrackingRS in DMRS-UplinkConfig is set, the upper layer parameters timeDensity and frequencyDensity in PTRS-UplinkConfig corresponding to phaseTrackingRS are set, and the scheduled MCS index I _MCS is smaller than ptrs-MCS ₁ and/or the scheduled bandwidth N _RB is smaller than N _RB0 , the terminal device 1 does not need to transmit the PT-RS. Here, when the configuration regarding coverage enhancement for the uplink is enabled, the terminal device 1 may further assume that L _PT-RS is a first predetermined value and K _PT-RS is a second predetermined value, map the PT-RS to physical resources, and transmit the PT-RS.

For example, the base station device 3 cannot set the values of _NRB0 and _NRB1 given by the higher layer parameter frequencyDensity in PTRS-UplinkConfig to a PRB number smaller than 1 PRB. If the base station device 3 can set the scheduled bandwidth ( _NRB ) to a value smaller than 1 PRB, the terminal device 1 cannot transmit the PT-RS in the PUSCH arrangement based on the description of Fig. 7. Therefore, if it is indicated that coverage enhancement is enabled based on a certain higher layer parameter, the terminal device 1 may assume _KPT-RS = 1 or _KPT-RS = 2 even if the scheduled bandwidth is smaller than 1 PRB.

When the scheduled bandwidth is smaller than 1 PRB and there are multiple DM-RS antenna ports, some of the resourceElementOffsets listed in FIG. 23 may not be selected. For example, when the scheduled bandwidth is 10 subcarriers, offset11 may not be selected for DM-RS Configuration type1, and offset10 and offset11 may not be selected for DM-RS Configuration type2. That is, the selectable offset may be limited according to the number of subcarriers of the scheduled bandwidth. Alternatively, the terminal device 1 may perform a MOD operation on the value of k ^RE _ref corresponding to each antenna port and offset with the total number of DM-RS antenna ports, and use the obtained value as k ^RE _ref corresponding to each DM-RS antenna port.

When the base station device 3 schedules PUSCH transmission with a bandwidth smaller than one PRB and when a PT-RS is present in the PUSCH arrangement, the base station device 3 does not need to set the higher layer parameter frequencyDensity in PTRS-UplinkConfig for the terminal device 1. Based on this setting, the terminal device 1 can always transmit PUSCH including a PT-RS.

Note that the terminal device 1 does not need to expect that the total number of used DM-RS antenna ports is greater than the number of subcarriers in the scheduled bandwidth. In other words, it is not needed to expect that multiple DM-RS antenna ports are shared with one k ^RE _ref .

When modified precoding is enabled, the values of _NRB0 to _NRB4 given by the higher layer parameter sampleDensity in PTRS-UplinkConfig are each equal to or greater than 1. Note that when modified precoding is enabled, the higher layer parameter sampleDensity in PTRS-UplinkConfig may be a higher layer parameter that is always set.

When modified precoding is enabled, if the upper layer parameter phaseTrackingRS in DMRS-UplinkConfig is set, the upper layer parameters timeDensityTransformPrecoding and sampleDensity in PTRS-UplinkConfig corresponding to phaseTrackingRS are set, and the scheduled MCS index I _MCS is smaller than ptrs-MCS ₁ and/or the scheduled bandwidth N _RB is smaller than N _RB0 , the terminal device 1 does not need to transmit the PT-RS. Here, when the setting related to coverage enhancement for the uplink is enabled, the terminal device 1 may further assume that L _PT-RS is a third predetermined value, the number of PT-RS groups is a fourth predetermined value, and the number of samples for each PT-RS group is a fifth predetermined value, and may perform mapping of the PT-RS to physical resources and transmit the PT-RS. In this case, the index m of one or more PT-RS samples in the OFDM symbol l before modified precoding may be determined based on the value obtained from FIG. 25, or may be determined based on a new definition. When the setting regarding coverage enhancement is valid, and if the scheduled bandwidth N _RB is smaller than N _RB0 , PT-RS transmission may be performed assuming that at least the number of PT-RS groups is 1 (for example, s=0 in FIG. 25, or any one of values from 0 to N _RB -1 (when N _RB is expressed by the number of subcarriers)), or PT-RS transmission may be performed assuming that at least the number of samples per PT-RS group is 1 (for example, k=0 in FIG. 25, or any one of values from 0 to N _RB -1 (when N _RB is expressed by the number of subcarriers)). Note that N _RB may be M ^PUSCH _SC .

For example, "scheduling a PUSCH transmission with a bandwidth smaller than 1 PRB" may mean that the number of subcarriers used for the PUSCH transmission is less than 12 subcarriers.

For example, "scheduling PUSCH transmission with a bandwidth smaller than one PRB" may mean that the number of subcarriers used for the PUSCH transmission at a certain time is less than 12 subcarriers. Here, the PUSCH transmission is performed at a first timing and a second timing, and the set of subcarriers used at the first timing and the set of subcarriers used at the second timing may be different. Also, the first timing and the second timing may be different. For example, the first timing may correspond to a first slot, and the second timing may correspond to a second slot different from the first slot. Also, the first timing may correspond to a first OFDM symbol, and the second timing may correspond to a second OFDM symbol different from the first OFDM symbol.

For example, "scheduling PUSCH transmission with a bandwidth smaller than one PRB" may indicate that PUSCH is transmitted with resources given in units of bandwidth smaller than one PRB. For example, the resources related to the PUSCH transmission may be distributed over two bandwidths at a certain time. Each of the two bandwidths may be smaller than one PRB. For example, each of the two bandwidths may be composed of X consecutive subcarriers. Here, X may be a value smaller than 12.

This enables the terminal device 1 and the base station device 3 to transmit and receive PT-RS even in resource mapping for coverage enhancement.

Various aspects of the device relating to one aspect of this embodiment are described below.

(1) In order to achieve the above object, the aspects of the present invention take the following measures. That is, a first aspect of the present invention is a terminal device, comprising: a receiving unit that receives a PTRS-UplinkConfig and a DCI (Downlink Control Information) format; and a transmitting unit that transmits a PUSCH (Physical Uplink Shared Channel) and a PT-RS (Phase Tracking Reference Signal) based on a value of an FDRA (Frequency Domain Resource Assignment) field included in the PTRS-UplinkConfig and the DCI format, and when modified precoding is enabled, if the value of the FDRA field indicates that the bandwidth scheduled for the PUSCH is smaller than one PRB (Physical Resource Block), the transmitting unit does not transmit the PT-RS, and if the value of the FDRA field indicates that the bandwidth scheduled for the PUSCH is smaller than one PRB and an upper layer parameter indicating that coverage enhancement is enabled is set, the transmitting unit transmits the PT-RS together with the PUSCH.

(2) A second aspect of the present invention is a terminal device of the first aspect, wherein when the modified precoding is not enabled, the transmitting unit determines whether to transmit the PT-RS together with the PUSH based on whether the PTRS-UplinkConfig includes an upper layer parameter frequencyDensity when the value of the FDRA field indicates that the bandwidth scheduled for the PUSH is smaller than 1 PRB.

(3) A third aspect of the present invention is a base station device comprising: a transmitting unit that transmits a PTRS-UplinkConfig and a DCI (Downlink Control Information) format; and a receiving unit that receives a PUSCH (Physical Uplink Shared Channel) and a PT-RS (Phase Tracking Reference Signal) based on a value of an FDRA (Frequency Domain Resource Assignment) field included in the PTRS-UplinkConfig and the DCI format, wherein when modified precoding is set to be enabled and coverage enhancement is set to be enabled, the receiving unit receives the PUSCH assuming that the PT-RS is included in the PUSCH, regardless of the bandwidth scheduled for the PUSCH.

(4) Also, a fourth aspect of the present invention is a base station device of the third aspect, wherein when the transmitting unit sets the modified precoding to be ineffective, and when the transmitting unit sets a bandwidth smaller than one PRB (Physical Resource Block) for the PUSH, and when the PT-RS is received together with the PUSH, the transmitting unit sets the PTRS-UplinkConfig without including the upper layer parameter frequencyDensity.

(5) A fifth aspect of the present invention is a method for use in a terminal device, comprising the steps of: receiving a PTRS-UplinkConfig and a Downlink Control Information (DCI) format; transmitting a Physical Uplink Shared Channel (PUSCH) and a Phase Tracking Reference Signal (PT-RS) based on a value of a Frequency Domain Resource Assignment (FDRA) field included in the PTRS-UplinkConfig and the DCI format; not transmitting the PT-RS when modified precoding is enabled and the value of the FDRA field indicates that the bandwidth scheduled for the PUSCH is smaller than one Physical Resource Block (PRB); and transmitting the PT-RS together with the PUSCH when the value of the FDRA field indicates that the bandwidth scheduled for the PUSCH is smaller than one PRB and an upper layer parameter indicating that coverage enhancement is enabled is set.

(6) Also, a sixth aspect of the present invention is the method of the sixth aspect, wherein when the modified precoding is not effective,
If the value of the FDRA field is such that the bandwidth scheduled for the PUSH is less than one PRB, the step of determining whether to transmit the PT-RS together with the PUSH based on whether the PTRS-UplinkConfig includes an upper layer parameter frequencyDensity is included.

(7) A seventh aspect of the present invention is a method for use in a base station device, comprising the steps of: transmitting a PTRS-UplinkConfig and a DCI (Downlink Control Information) format; receiving a PUSCH (Physical Uplink Shared Channel) and a PT-RS (Phase Tracking Reference Signal) based on a value of an FDRA (Frequency Domain Resource Assignment) field included in the PTRS-UplinkConfig and the DCI format; and, when modified precoding is set to be enabled and coverage enhancement is set to be enabled, receiving the PUSCH assuming that the PT-RS is included therein, regardless of the bandwidth scheduled for the PUSCH.

(8) Furthermore, an eighth aspect of the present invention is a method of the seventh aspect, which includes a step of setting the PTRS-UplinkConfig without including the upper layer parameter frequencyDensity when the modified precoding is set to be ineffective and when a bandwidth smaller than one PRB (Physical Resource Block) is set for the PUSH and when the PT-RS is received together with the PUSH.

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

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

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

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

The base station device 3 in the above-described embodiment can also be realized as an aggregate (device group) consisting of multiple devices. Each of the devices constituting the device group may have some or all of the functions or functional blocks of the base station device 3 related to the above-described embodiment. It is sufficient for an device group to have all of the functions or functional blocks of the base station device 3. The terminal device 1 related to the above-described embodiment can also communicate with the base station device as an aggregate.

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

In addition, some or all of the terminal device 1 and base station device 3 in the above-mentioned embodiments may be realized as an LSI, which is typically an integrated circuit, or as a chip set. Each functional block of the terminal device 1 and base station device 3 may be individually chipped, or some or all may be integrated and chipped. The integrated circuit method is not limited to LSI, and may be realized by a dedicated circuit or a general-purpose processor. Furthermore, if an integrated circuit technology that can replace LSI emerges due to advances in semiconductor technology, it is also possible to use an integrated circuit based on that technology.

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

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

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

1 (1A, 1B, 1C) Terminal device 3 Base station device 10, 30 Radio transmission/reception unit 11, 31 Antenna unit 12, 32 RF unit 13, 33 Baseband unit 14, 34 Upper layer processing unit 15, 35 Media access control layer processing unit 16, 36 Radio resource control layer processing unit

Claims (5)

A receiving unit for receiving a PTRS-UplinkConfig and a DCI (Downlink Control Information) format;
A transmitter that transmits a Physical Uplink Shared Channel (PUSCH) and a Phase Tracking Reference Signal (PT-RS) based on a value of a Frequency Domain Resource Assignment (FDRA) field included in the PTRS-UplinkConfig and the DCI format,
The transmission unit is
When modified precoding is enabled,
If the value of the FDRA field indicates that the bandwidth scheduled for the PUSCH is smaller than one PRB (Physical Resource Block), then do not transmit the PT-RS;
A terminal device that transmits the PT-RS together with the PUSH if the value of the FDRA field indicates that the bandwidth scheduled for the PUSH is smaller than one PRB and if an upper layer parameter indicating that coverage enhancement is enabled is set. The transmission unit is
When the modified precoding is not enabled,
The terminal device of claim 1, further comprising: when the value of the FDRA field indicates that the bandwidth scheduled for the PUSH is smaller than one PRB, the terminal device determines whether to transmit the PT-RS together with the PUSH based on whether the PTRS-UplinkConfig includes an upper layer parameter frequencyDensity. A transmitter that transmits a PTRS-UplinkConfig and a DCI (Downlink Control Information) format;
A receiving unit that receives a Physical Uplink Shared Channel (PUSCH) and a Phase Tracking Reference Signal (PT-RS) based on a value of a Frequency Domain Resource Assignment (FDRA) field included in the PTRS-UplinkConfig and the DCI format,
The receiving unit is
A base station device that, when modified precoding is set to be enabled and coverage enhancement is set to be enabled, receives the PUSCH assuming that the PT-RS is included in the PUSCH regardless of a bandwidth scheduled for the PUSCH. The transmission unit is
When the modified precoding is not set, if a bandwidth smaller than one PRB (Physical Resource Block) is set for the PUSCH,
The base station device according to claim 3, wherein when the PT-RS is received together with the PUSCH, the PTRS-UplinkConfig is set without including the higher layer parameter frequencyDensity. receiving a PTRS-UplinkConfig and a Downlink Control Information (DCI) format;
Transmitting a Physical Uplink Shared Channel (PUSCH) and a Phase Tracking Reference Signal (PT-RS) based on a value of a Frequency Domain Resource Assignment (FDRA) field included in the PTRS-UplinkConfig and the DCI format;
When modified precoding is enabled,
not transmitting the PT-RS if the value of the FDRA field indicates that the bandwidth scheduled for the PUSCH is smaller than one PRB (Physical Resource Block);
If the value of the FDRA field indicates that the bandwidth scheduled for the PUSH is smaller than one PRB and if a higher layer parameter indicating that coverage enhancement is enabled is set, transmitting the PT-RS together with the PUSH.

Images