JP7717575B2 - Terminal device, base station device, and communication method - Google Patents

Description

The present invention relates to a terminal device, a base station device, and a communication method.

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

The 3GPP has been formulating a wireless communication standard (NR: New Radio).
Further expansion of the wireless communication standard is being considered (Non-Patent Document 1).

“Summary of RAN Rel-18 Workshop”, RWS-210659, RAN chair, 3GPP RAN Rel-18 workshop, 28th June ― 2nd July, 2021

The present invention provides a terminal device, a base station device, and a communication method used by the terminal device that communicates efficiently.

(1) A first aspect of the present invention is a terminal device comprising: a receiving unit that acquires a random access response grant; and a transmitting unit that transmits a PUSCH scheduled by the random access response grant, wherein an MCS field included in the random access response grant is set to indicate one MCS value from one MCS index candidate set, and the transmitting unit selects the one MCS index candidate set from multiple MCS index candidate sets based on one or both of: 1) the amount of resources for the PUSCH; and 2) the values of fields other than the MCS field included in the random access response grant.

(2) A second aspect of the present invention is a base station device comprising: a transmitter that transmits a random access response grant; and a receiver that receives a PUSCH scheduled by the random access response grant, wherein the MCS field included in the random access response grant is set to indicate one MCS value from one MCS index candidate set, and the receiver selects the one MCS index candidate set from multiple MCS index candidate sets based on one or both of: 1) the amount of resources for the PUSCH; and 2) the values of fields other than the MCS field included in the random access response grant.

(3) A third aspect of the present invention is a communication method used in a terminal device, comprising the steps of: acquiring a random access response grant; and transmitting a PUSH scheduled by the random access response grant, wherein an MCS field included in the random access response grant is set to indicate one MCS value from one MCS index candidate set, and the one MCS index candidate set is selected from a plurality of MCS index candidate sets based on one or both of: 1) a resource amount for the PUSH; and 2) values of fields other than the MCS field included in the random access response grant.

This invention allows terminal devices to communicate efficiently. It also allows base station devices to communicate efficiently.

1 is a conceptual diagram of a wireless communication system 9 according to an aspect of the present embodiment. FIG. 1 is a diagram illustrating an example of the configuration of a resource grid according to an aspect of the present embodiment. FIG. 2 is a schematic block diagram illustrating an example of the configuration of a base station device 3 according to one aspect of the present embodiment. 1 is a schematic block diagram illustrating an example of the configuration of a terminal device 1 according to an aspect of the present embodiment. A figure showing an example of a procedure for transmitting a PUSH between a terminal device 1 and a base station device 3 in one aspect of this embodiment. A figure showing an example of transmitting a PUSH according to one aspect of this embodiment. FIG. 10 is a diagram illustrating an example of the configuration of a TDRA table according to one aspect of this embodiment. A figure showing an example of transmitting a PUSH according to one aspect of this embodiment. FIG. 10 is a diagram illustrating an example of the configuration of a TDRA table according to one aspect of this embodiment.

The following describes an embodiment of the present invention.

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

Figure 1 is a conceptual diagram of a wireless communication system 9 according to one aspect of this embodiment. In Figure 1, the wireless communication system includes terminal devices 1A-1C and a base station device 3 (BS#3: Base station#3). Hereinafter, terminal devices 1A-1C will be collectively referred to as terminal device 1 (UE#1: User Equipment#1), and the terminal device communicating with base station device 3 will also be referred to as terminal device 1 (UE#1: User Equipment#1).

In the wireless communication system 9, the terminal device 1 and the base station device 3 may use one or more communication methods. For example, CP-OFDM (Cyclic Prefix - Orthogonal Frequency Division Multiplexing) may be used in the downlink of the wireless communication system 9. Furthermore, either CP-OFDM or DFT-s-OFDM (Discrete Fourier Transform - Spread - Orthogonal Frequency Division Multiplexing) may be used in the uplink of the wireless communication system 9. Here, DFT-s-OFDM is a communication method in which transformed precoding is applied prior to signal generation in CP-OFDM. Here, transformed precoding is also referred to as DFT precoding.

As shown in FIG. 1, base station device 3 may be configured with one transceiver device (or transmission point, transmission device, reception point, reception device, transmission/reception point). On the other hand, in some cases, base station device 3 may be configured to include multiple transceivers. When base station device 3 is configured with multiple transceivers, each of the multiple transceivers may be located in a different geographical location.

The base station device 3 may provide one or more serving cells. A serving cell may be defined as a set of resources used in the wireless communication system 9. Here, a serving cell is also referred to as a cell.

A serving cell may be configured to include one downlink component carrier and/or one uplink component carrier. A serving cell may be configured to include two or more downlink component carriers and/or two or more uplink component carriers. Downlink component carriers and uplink component carriers are also collectively referred to as component carriers.

For a component carrier, one or more SCS-specific carriers
One subcarrier-spacing configuration μ may be associated with one SCS-specific carrier.

Resources in the wireless communication system 9 may be managed using a resource grid that uses subcarrier indexes and OFDM symbol indexes.

The subcarrier spacing (SCS) for a certain subcarrier spacing setting μ
) Δf may be Δf= ^2μ ·15 kHz. For example, the subcarrier spacing setting μ may represent any of 0, 1, 2, 3, or 4.

A time unit _Tc = 1/( _Δfmax · _Nf ) may be used to express the length of the time domain. Here, _Δfmax = 480 kHz. _Nf = 4096. The constant κ may be κ = _Δfmax · _Nf /( _Δfref ·Nf _,ref ) = 64. _Δfref may be 15 kHz. _Nf,ref is 2048.

The transmission of downlink/uplink signals may be organized into radio frames (system frames, frames) of length _Tf , where _Tf = ( _Δfmax · _Nf /100)· _Ts = 10 ms.

A radio frame may include 10 subframes, where the length of a subframe T _sf = (Δf _max · N _f /1000) · T _s = 1 ms, and the number of OFDM symbols per subframe may be N ^subframe,μ _symb = N ^slot _symb · N ^subframe,μ _slot .

An OFDM symbol is used as a unit of time domain for the communication method used in the wireless communication system 9. For example, an OFDM symbol may be used as a unit of time domain for CP-OFDM. Also, an OFDM symbol may be used as a unit of time domain for DFT-s-OFDM.

A slot may be configured to include multiple OFDM symbols. For example, one slot may be configured by N ^slot _symb consecutive OFDM symbols. For example, in the normal CP setting, N ^slot _symb = 14. Also, in the extended CP setting, N ^slot _symb = 12.

The slots may be indexed in the time domain. For example, the slot index n ^μ _s may be given in ascending order as integer values ranging from 0 to N ^subframe,μ _slot −1 in a subframe. Also, the slot index n ^μ _s,f may be given in ascending order as integer values ranging from 0 to N ^frame,μ _slot −1 in a radio frame.

Figure 2 is a diagram showing an example of the configuration of a resource grid according to one aspect of this embodiment. In the resource grid of Figure 2, the horizontal axis represents the OFDM symbol index l _sym and the vertical axis represents the subcarrier index k _sc . The resource grid of Figure 2 includes N ^size,μ _grid,x ·N ^RB _sc subcarriers and N ^subframe,μ _symb OFDM symbols. Here, N ^size,μ _grid,x represents the bandwidth of the SCS-specific carrier. The value of N ^size,μ _grid,x is expressed in resource blocks.

Within the resource grid, a resource identified by a subcarrier index k _sc and an OFDM symbol index l _sym is called a resource element (RE).
It is also called the Element.

A resource block (RB) includes N ^RB _sc consecutive subcarriers. The resource block is a collective term for a common resource block, a physical resource block (PRB), and a virtual resource block (VRB). For example, N ^RB _sc may be 12.

A BWP (BandWidth Part) may be configured as a subset of the resource grid. Here, the BWP configured for the downlink is also referred to as the downlink BWP. The BWP configured for the uplink is also referred to as the uplink BWP.

An antenna port may be defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. For example, a channel may correspond to a physical channel. Alternatively, a symbol may correspond to a modulation symbol assigned to a resource element. Here, "channel" may mean "propagation path." Alternatively, "channel" may mean "physical channel."

Two antenna ports are considered to be in a Quasi Co-Located (QCL) relationship if the large-scale properties of the channel through which symbols are transmitted at one antenna port can be estimated from the channel through which symbols are transmitted at the other antenna port. Here, the large-scale properties may include long-range channel properties. The large-scale properties may include some or all of delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters. A first antenna port and a second antenna port being QCL with respect to beam parameters may mean that the receive beam assumed by the receiver for the first antenna port and the receive beam assumed by the receiver for the second antenna port are the same (or correspond to each other). The first antenna port and the second antenna port being QCL with respect to beam parameters may mean that the transmit beam assumed by the receiving side for the first antenna port and the transmit beam assumed by the receiving side for the second antenna port are the same (or correspond to each other). The terminal device 1 may assume that the two antenna ports are QCL if the large-scale characteristics of the channel through which symbols are transmitted at one antenna port can be estimated from the channel through which symbols are transmitted at another antenna port. The two antenna ports being QCL may mean that the two antenna ports are assumed to be QCL.

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

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

The physical layer processing unit 30 performs physical layer processing. Here, physical layer processing may include some or all of the following: generating a baseband signal for a physical channel, generating a baseband signal for a physical signal, detecting information transmitted by the physical channel, and detecting information transmitted by the physical signal. Furthermore, physical layer processing may include mapping a transport channel to a physical channel. Here, a baseband signal is also referred to as a time-continuous signal.

For example, the physical layer processing unit 30 may generate a baseband signal for a downlink physical channel. Here, a transport block delivered from a higher layer on the DL-SCH may be placed on the downlink physical channel.

For example, the physical layer processing unit 30 may generate a baseband signal for the downlink physical signal.

For example, the physical layer processing unit 30 may attempt to detect information transmitted by the uplink physical channel. Here, the transport block of the information transmitted by the uplink physical channel may be delivered to higher layers on the UL-SCH.

For example, the physical layer processing unit 30 may attempt to detect information transmitted by an uplink physical signal.

The upper layer processing unit 34 performs some or all of the processing of the Medium Access Control (MAC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and RRC layer. Here, the MAC layer is also referred to as the MAC sublayer. The PDCP layer is also referred to as the PDCP sublayer. The RLC layer is also referred to as the RLC sublayer. The RRC layer is also referred to as the RRC sublayer.

The media access control layer processing unit (MAC layer processing unit) 35 performs MAC layer processing.
The MAC layer processing includes mapping between logical channels and transport channels, multiplexing one or more MAC SDUs (Service Data Units) into a transport block,
One or more MACs of transport blocks delivered from the physical layer on the UL-SCH
This may include some or all of the following: disassembly into SDUs, application of Hybrid Automatic Repeat reQuest (HARQ) to transport blocks, and processing of scheduling requests.

The radio resource control layer processing unit 36 performs RRC layer processing. RRC layer processing may include some or all of broadcast signal management, RRC connection/RRC idle state management, and RRC reconfiguration.

The radio resource control layer processing unit 36 may manage RRC parameters used for various settings of the terminal device 1. For example, the radio resource control layer processing unit 36 may include the RRC parameters in an RRC message on a certain logical channel and transmit the RRC message to the terminal device 1. Here, the RRC message may be mapped to any of the BCCH (Broadcast Control CHannel), CCCH (Common Control CHannel), and DCCH (Dedicated Control CHannel).

The radio resource control layer processing unit 36 may determine the RRC parameters to be transmitted to the terminal device 1 based on the RRC parameters included in the RRC message transmitted from the terminal device 1. Here, the RRC message transmitted from the terminal device 1 may be related to a functional information report of the terminal device 1.

The physical layer processing unit 30 may perform some or all of the modulation processing, encoding processing, and transmission processing. The physical layer processing unit 30 may generate a physical signal based on some or all of the encoding processing, modulation processing, and baseband signal generation processing for the transport block. The physical layer processing unit 30 may place the physical signal in a certain BWP. The physical layer processing unit 30 may transmit the generated physical signal.

The physical layer processing unit 30 may perform either or both of demodulation and decoding. The physical layer processing unit 30 may deliver transport blocks of information detected based on the demodulation and decoding processes of the received physical signal to higher layers on the UL-SCH.

If carrier sensing is required in the band of the serving cell, the physical layer processing unit 30 may perform carrier sensing prior to transmitting the physical signal.

The RF unit 32 converts the signal received via the antenna unit 31 into a baseband signal.
The RF unit 32 outputs the baseband signal to the baseband unit 33.

The baseband unit 33 may digitize the baseband signal input from the RF unit 32. The baseband unit 33 derives a CP (Cy
The baseband unit 33 may perform a fast Fourier transform (FFT) on the baseband signal from which the CP has been removed, to extract a signal in the frequency domain.

The baseband unit 33 may generate a baseband signal by performing an inverse fast Fourier transform (IFFT) on the physical signal.
The baseband unit 33 may add a CP to the generated baseband signal. The baseband unit 33 may convert the baseband signal to which the CP has been added into an analog signal. The baseband unit 33 may output the analog baseband signal to the RF unit 32.

The RF unit 32 may remove unnecessary frequency components from the baseband signal input from the baseband unit 33. The RF unit 32 may upconvert the baseband signal to a carrier frequency to generate an RF signal. The RF unit 32 may transmit the RF signal via the antenna unit 31. The RF unit 32 may also have a function for controlling transmission power.

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

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

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

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

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

Serving cell group (cell group) is a general term for MCG, SCG, and PUCCH cell group. A serving cell group may include one or more serving cells (or component carriers). One or more serving cells (or component carriers) included in a serving cell group may be operated using carrier aggregation.

One or more downlink BWPs may be configured for the terminal device 1. One or more uplink BWPs may be configured for the terminal device 1.

Of one or more downlink BWPs configured for the terminal device 1, one downlink BWP may be set as the active downlink BWP (or one downlink BWP may be activated). Of one or more uplink BWPs configured for the terminal device 1, one uplink BWP may be set as the active uplink BWP (or one uplink BWP may be activated).

The physical layer processing unit 30 may attempt to transmit the PDSCH, PDCCH, and CSI-RS on the active downlink BWP. The physical layer processing unit 10 may attempt to receive the PDSCH, PDCCH, and CSI-RS on the active downlink BWP. The physical layer processing unit 30 may attempt to receive the PUCCH and PUSCH on the active uplink BWP. The physical layer processing unit 10 may attempt to transmit the PUCCH and PUSCH on the active uplink BWP. Here, the active downlink BWP and the active uplink BWP are collectively referred to as the active BWP.

The physical layer processing unit 30 may not attempt to transmit the PDSCH, PDCCH, or CSI-RS on an inactive downlink BWP (a downlink BWP that is not an active downlink BWP). The physical layer processing unit 10 may not attempt to receive the PDSCH, PDCCH, or CSI-RS on an inactive downlink BWP. The physical layer processing unit 30 may not attempt to receive the PUCCH or PUSCH on an inactive uplink BWP (an uplink BWP that is not an active uplink BWP). The physical layer processing unit 10 may not attempt to transmit the PUCCH or PUSCH on an inactive uplink BWP. Here, the inactive downlink BWP and the inactive uplink BWP are collectively referred to as the inactive BWP.

Downlink BWP switch is a procedure for deactivating one active downlink BWP of a serving cell and activating one of the inactive downlink BWPs of the serving cell. Downlink BWP switch may be controlled by the physical layer, MAC layer, or RRC layer.

Uplink BWP switching is used to deactivate one active uplink BWP of a serving cell and activate one of the inactive uplink BWPs of the serving cell. Uplink BWP switching may be controlled by the physical layer, MAC layer, or RRC layer.

Of the one or more downlink BWPs configured for the terminal device 1, two or more downlink BWPs may not be set as active downlink BWPs. For a given component carrier, one downlink BWP may be active at a given time.

Of the one or more uplink BWPs configured for the terminal device 1, two or more uplink BWPs may not be set as active uplink BWPs. For a given component carrier, one uplink BWP may be active at a given time.

For each downlink component carrier, one downlink BWP may be set as the active BWP. In other words, for a given downlink component carrier, two or more downlink BWPs may not be set as the active downlink BWP.

For each uplink component carrier, one uplink BWP may be set as the active BWP. In other words, for a given uplink component carrier, two or more uplink BWPs may not be set as the active uplink BWP.

4 is a schematic block diagram showing an example configuration of a terminal device 1 according to one aspect of the present embodiment. As shown in FIG. 4, the terminal device 1 includes a physical layer processing unit (radio transmitting/receiving unit) 10 and part or all of an upper layer processing unit 14. The radio transmitting/receiving unit 10 includes an antenna unit 11, an RF unit 12, and part or all of a baseband unit 13. The upper layer processing unit 14 includes a medium access control layer processing unit 15 and part or all of a radio resource control layer processing unit 16.

The physical layer processing unit 10 performs physical layer processing.

For example, the physical layer processing unit 10 may generate a baseband signal for an uplink physical channel. Here, a transport block delivered from a higher layer on the UL-SCH may be mapped to the uplink physical channel.

For example, the physical layer processing unit 10 may generate a baseband signal for the uplink physical signal.

For example, the physical layer processing unit 10 may attempt to detect information transmitted by the downlink physical channel. Here, the transport block of the information transmitted by the downlink physical channel may be delivered to higher layers on the DL-SCH.

For example, the physical layer processing unit 10 may attempt to detect information transmitted by a downlink physical signal.

The upper layer processing unit 14 performs some or all of the processing of the Medium Access Control (MAC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and RRC layer.

The media access control layer processing unit (MAC layer processing unit) 15 performs MAC layer processing.

The radio resource control layer processing unit 16 performs RRC layer processing.

The radio resource control layer processing unit 16 may manage RRC parameters transmitted from the base station device 3. For example, the radio resource control layer processing unit 16 may acquire RRC parameters contained in an RRC message on a certain logical channel and set the acquired RRC parameters in a memory area of the terminal device 1. The RRC parameters set in the memory area of the terminal device 1 may be provided to a lower layer.

The radio resource control layer processing unit 16 may include functional information generated based on the functions provided by the terminal device 1 in an RRC message and transmit it to the base station device 3.

The physical layer processing unit 10 may perform some or all of the modulation processing, encoding processing, and transmission processing. The physical layer processing unit 10 may generate a physical signal based on some or all of the encoding processing, modulation processing, and baseband signal generation processing for the transport block. The physical layer processing unit 10 may place the physical signal in a certain BWP. The physical layer processing unit 10 may transmit the generated physical signal.

The physical layer processing unit 10 may perform either or both of demodulation and decoding. The physical layer processing unit 10 may deliver transport blocks of information detected based on the demodulation and decoding processes of the received physical signal to higher layers on the DL-SCH.

If carrier sensing is required in the band of the serving cell, the physical layer processing unit 10 may perform carrier sensing prior to transmitting a physical signal.

The RF unit 12 converts the signal received via the antenna unit 11 into a baseband signal.
The RF unit 12 outputs the baseband signal to the baseband unit 13.

The baseband unit 13 may digitize the baseband signal input from the RF unit 12. The baseband unit 13 may remove a portion corresponding to a cyclic prefix (CP) from the digitized baseband signal. The baseband unit 13 may perform a fast Fourier transform (FFT) on the baseband signal from which the CP has been removed to extract a frequency domain signal.

The baseband unit 13 may generate a baseband signal by performing an inverse fast Fourier transform (IFFT) on the physical signal.
The baseband unit 13 may add a CP to the generated baseband signal. The baseband unit 13 may convert the baseband signal to which the CP has been added into an analog signal. The baseband unit 13 may output the analog baseband signal to the RF unit 12.

The RF unit 12 may remove unnecessary frequency components from the baseband signal input from the baseband unit 13. The RF unit 12 may upconvert the baseband signal to a carrier frequency to generate an RF signal. The RF unit 12 may transmit the RF signal via the antenna unit 31. The RF unit 12 may also have a function for controlling transmission power.

The physical signals are explained below.

Physical signal is a general term for downlink physical channel, downlink physical signal, uplink physical channel, and uplink physical channel. Physical channel is a general term for downlink physical channel and uplink physical channel. Physical signal is a general term for downlink physical signal and uplink physical signal.

The uplink physical channel may correspond to a set of resource elements that convey information generated in a higher layer. The uplink physical channel may be a physical channel used in an uplink component carrier. The uplink physical channel may be transmitted by the physical layer processing unit 10. The uplink physical channel may be received by the physical layer processing unit 30. In the uplink of the wireless communication system according to one aspect of the present embodiment, some or all of the following uplink physical channels may be used.
・PUCCH (Physical Uplink Control CHannel)
・PUSCH (Physical Uplink Shared CHannel)
・PRACH (Physical Random Access CHannel)
The PUCCH may be transmitted to deliver, transmit, or convey uplink control information (UCI). The uplink control information may be mapped to the PUCCH. The physical layer processing unit 10 may transmit the PUCCH in which the uplink control information is mapped. The physical layer processing unit 30 may receive the PUCCH in which the uplink control information is mapped.

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

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

The HARQ-ACK information may be composed of HARQ-ACK bits corresponding to a transport block (TB). A HARQ-ACK bit may indicate an acknowledgement (ACK) or a negative acknowledgement (NACK) corresponding to the transport block. An ACK may indicate that decoding of the transport block has been successfully completed. A NACK may indicate that decoding of the transport block has not been successfully completed. The HARQ-ACK information may include one or more HARQ-ACK bits.

HARQ-ACK for a transport block is also referred to as HARQ-ACK for a PDSCH. Here, "HARQ-ACK for a PDSCH" refers to a HARQ-ACK for a transport block included in the PDSCH.

The scheduling request may be used to request UL-SCH resources for an initial transmission. The scheduling request bit may be used to indicate either a positive SR or a negative SR. When the scheduling request bit indicates a positive SR, this is also referred to as "a positive SR is transmitted." A positive SR may indicate that UL-SCH resources for the initial transmission are requested by the media access control layer processing unit 15. When the scheduling request bit indicates a negative SR, this is also referred to as "a negative SR is transmitted." A negative SR may indicate that UL-SCH resources for the initial transmission are not requested by the media access control layer processing unit 15.

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

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

The PUCCH may be accompanied by a certain PUCCH format. Here, the PUCCH format may be the format of the physical layer processing of the PUCCH. The PUCCH format may also be the format of the information transmitted using the PUCCH.

The PUSCH may be transmitted to transmit uplink control information and/or a transport block. The PUSCH may be used to transmit uplink control information and/or a transport block. The terminal device 1 may transmit a PUSCH in which uplink control information and/or a transport block are allocated. The base station device 3 may receive a PUSCH in which uplink control information and/or a transport block are allocated.

The PRACH may be transmitted to convey the index of the random access preamble. The terminal device 1 may transmit the PRACH. The base station device 3 may receive the PRACH. The terminal device 1 may transmit the random access preamble on the PRACH. The base station device 3 may receive the random access preamble on the PRACH.

The uplink physical signal may correspond to a set of resource elements. The uplink physical signal does not have to be used to transmit information generated in a higher layer. The uplink physical signal may be used to transmit information generated in the physical layer. The uplink physical signal may be a physical signal used in an uplink component carrier. The physical layer processing unit 10 may transmit the uplink physical signal. The physical layer processing unit 30 may receive the uplink physical signal. In the uplink of the wireless communication system according to one aspect of the present embodiment, some or all of the following uplink physical signals may be used.
・UL DMRS (UpLink Demodulation Reference Signal)
・SRS (Sounding Reference Signal)
・UL PTRS (UpLink Phase Tracking Reference Signal)
UL DMRS is a general term for DMRS for PUSCH and DMRS for PUCCH.

The set of antenna ports for DMRS for PUSCH (DMRS associated with PUSCH, DMRS included in PUSCH, DMRS corresponding to PUSCH) may be determined based on the set of antenna ports for the PUSCH. For example, the set of antenna ports for DMRS for PUSCH may be the same as the set of antenna ports for the PUSCH.

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

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

The propagation path of the PUCCH may be estimated from the DMRS for that PUCCH.

The downlink physical channel may correspond to a set of resource elements that convey information generated in a higher layer. The downlink physical channel may be a physical channel used in a downlink component carrier. The physical layer processing unit 30 may transmit the downlink physical channel. The physical layer processing unit 10 may receive the downlink physical channel. In the downlink of the wireless communication system according to one aspect of the present embodiment, some or all of the following downlink physical channels may be used.
・PBCH (Physical Broadcast Channel)
・PDCCH (Physical Downlink Control Channel)
・PDSCH (Physical Downlink Shared Channel)
The PBCH may be transmitted to convey one or both of a Master Information Block (MIB) and physical layer control information, where the physical layer control information is information generated in the physical layer. The MIB is an RRC message delivered from higher layers on the Broadcast Control Channel (BCCH).

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

Downlink control information may be transmitted using a DCI format. Note that a DCI format may be interpreted as the format of downlink control information. A DCI format may also be interpreted as a set of downlink control information set in a certain downlink control information format.

The base station device 3 may notify the terminal device 1 of downlink control information using a PDCCH with a DCI format. Here, the terminal device 1 may monitor the PDCCH to acquire the downlink control information. Unless otherwise specified, the DCI format and downlink control information may be described as equivalent. For example, the base station device 3 may include the downlink control information in a DCI format and transmit it to the terminal device 1. Furthermore, the terminal device 1 may control the physical layer processing unit 10 using the downlink control information included in the detected DCI format.

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

DCI format 0_0 is used for scheduling a PUSCH located in a certain cell, and may include some or all of fields 1A to 1E.
1A) Identifier field for DCI formats
1B) Frequency domain resource assignment field
field)
1C) Time domain resource assignment field
)
1D) Frequency hopping flag field
1E) MCS field (Modulation and Coding Scheme field)
The DCI format identification field may indicate whether the DCI format including the DCI format identification field is an uplink DCI format or a downlink DCI format. That is, the DCI format identification field may be included in both the uplink DCI format and the downlink DCI format. Here, the DCI format identification field included in DCI format 0_0 may indicate 0.

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

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

The frequency hopping flag field may be used to indicate whether frequency hopping is applied to the PUSCH scheduled by the DCI format 0_0.

The MCS field included in DCI format 0_0 may be used to indicate one or both of a modulation scheme for a PUSCH scheduled by DCI format 0_0 and a target coding rate scheduled by DCI format 0_1. The target coding rate may be a target coding rate for a transport block assigned to the PUSCH. The size of the transport block (TBS) assigned to the PUSCH may be determined based on part or all of the target coding rate and the modulation scheme for the PUSCH.

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

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

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

DCI format 0_1 is used for scheduling a PUSCH allocated to a certain cell, and is configured to include some or all of fields 2A to 2H.
2A) DCI format specific field 2B) Frequency domain resource allocation field 2C) Uplink time domain resource allocation field 2D) Frequency hopping flag field 2E) MCS field 2F) CSI request field
2G) BWP field
2H) Carrier Indicator Field
The DCI format specific field included in DCI format 0_1 may indicate 0.

The frequency domain resource allocation field included in DCI format 0_1 may be used to indicate the allocation of frequency resources for the PUSCH scheduled by DCI format 0_1.

The time domain resource allocation field included in DCI format 0_1 may be used to indicate the allocation of time resources for the PUSCH scheduled by DCI format 0_1.

The MCS field included in DCI format 0_1 may be used to indicate one or both of the modulation scheme for the PUSCH scheduled by DCI format 0_1 and the target coding rate for the PUSCH scheduled by DCI format 0_1.

The BWP field of DCI format 0_1 may be used to indicate the uplink BWP in which the PUSCH scheduled by DCI format 0_1 is allocated. In other words, DCI format 0_1 may or may not involve a change in the active uplink BWP. The terminal device 1 may recognize the uplink BWP in which the PUSCH is allocated based on detecting DCI format 0_1 used for scheduling the PUSCH.

DCI format 0_1 that does not include a BWP field may be a DCI format that schedules a PUSCH without changing the active uplink BWP. Based on detecting DCI format 0_1 that is used for scheduling a PUSCH and does not include a BWP field, the terminal device 1 may recognize that the PUSCH will be transmitted without switching the active uplink BWP.

If DCI format 0_1 includes a BWP field but the terminal device 1 does not support the BWP switching function using DCI format 0_1, the BWP field may be ignored by the terminal device 1. In other words, a terminal device 1 that does not support the BWP switching function may recognize that it will transmit the PUSCH without switching the active uplink BWP based on detecting DCI format 0_1 that is used for PUSCH scheduling and includes a BWP field. Here, if the BWP switching function is supported, the radio resource control layer processing unit 16 may include function information indicating that the BWP switching function is supported in the RRC message.

The CSI request field may be used to indicate the reporting of CSI.

When DCI format 0_1 includes a carrier indicator field, the carrier indicator field may be used to indicate the serving cell of the uplink component carrier on which the PUSCH is allocated. Based on detecting DCI format 0_1 on the downlink component carrier of a serving cell, the terminal device 1 may recognize that the PUSCH scheduled by the DCI format 0_1 is allocated to the uplink component carrier of the serving cell indicated by the carrier indicator field included in the DCI format 0_1.

If DCI format 0_1 does not include a carrier indicator field, the serving cell to which the uplink component carrier on which the PUSCH scheduled by DCI format 0_1 is allocated may be the same as the serving cell of the downlink component carrier on which the PDCCH including DCI format 0_1 is allocated. Based on detecting DCI format 0_1 on a downlink component carrier of a serving cell, the terminal device 1 may recognize that the PUSCH scheduled by DCI format 0_1 is to be allocated on the uplink component carrier of the serving cell.

DCI format 1_0 is used for scheduling a PDSCH allocated to a certain cell, and is configured by including some or all of DCI format 3A to 3F.
3A) DCI format specific field 3B) Frequency domain resource allocation field 3C) Time domain resource allocation field 3D) MCS field 3E) PDSCH to HARQ feedback timing indicator field
3F) PUCCH resource indicator field
The DCI format specific field included in DCI format 1_0 may indicate 1.

The frequency domain resource allocation field included in DCI format 1_0 may be used to indicate the allocation of frequency resources for the PDSCH scheduled by that DCI format.

The time domain resource allocation field included in DCI format 1_0 may be used to indicate the allocation of time resources for the PDSCH scheduled by that DCI format.

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

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

The PUCCH resource indication field may be used to indicate the PUCCH resource.

DCI format 1_0 may not include a carrier indicator field. In other words, the downlink component carrier on which the PDSCH scheduled by DCI format 1_0 is allocated may be the same as the downlink component carrier on which the PDCCH including DCI format 1_0 is allocated. Based on detecting DCI format 1_0 on a certain downlink component carrier, the terminal device 1 may recognize that the PDSCH scheduled by DCI format 1_0 is to be allocated to that downlink component carrier.

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

DCI format 1_1 is used for scheduling a PDSCH allocated to a certain cell, and is configured to include some or all of 4A to 4I.
4A) DCI format specific field 4B) Frequency domain resource allocation field 4C) Time domain resource allocation field 4E) MCS field 4F) PDSCH_HARQ feedback timing indication field 4G) PUCCH resource indication field 4H) BWP field 4I) Carrier indicator field The DCI format specific field included in DCI format 1_1 may indicate 1.

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

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

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

If DCI format 1_1 includes a PDSCH_HARQ feedback timing indication field, the PDSCH_HARQ feedback timing indication field may be used to indicate the offset from the slot containing the last OFDM symbol of the PDSCH to the slot containing the first OFDM symbol of the PUCCH. If DCI format 1_1 does not include a PDSCH_HARQ feedback timing indication field, a parameter indicating the offset from the slot containing the last OFDM symbol of the PDSCH to the slot containing the first OFDM symbol of the PUCCH may be provided by the RRC layer.

The PUCCH resource indication field may be used to indicate the PUCCH resource.

The BWP field of DCI format 1_1 may be used to indicate the downlink BWP in which the PDSCH scheduled by DCI format 1_1 is allocated. In other words, DCI format 1_1 may or may not involve a change in the active downlink BWP. The terminal device 1 may recognize the downlink BWP in which the PDSCH is allocated based on detecting DCI format 1_1 used for scheduling the PDSCH.

The DCI format 1_1, which does not include a BWP field, may be a DCI format for scheduling the PDSCH without changing the active downlink BWP.
Based on detecting DCI format 1_1 which is 1 and does not include a BWP field, it may be recognized that the PDSCH will be received without switching the active downlink BWP.

If DCI format 1_1 includes a BWP field but the terminal device 1 does not support the BWP switching function using DCI format 1_1, the BWP field may be ignored by the terminal device 1. In other words, a terminal device 1 that does not support the BWP switching function may recognize that it will receive the PDSCH without switching the active downlink BWP based on detecting DCI format 1_1 that is used for PDSCH scheduling and includes a BWP field. Here, if the BWP switching function is supported, the radio resource control layer processing unit 16 may include function information indicating that the BWP switching function is supported in the RRC message.

When DCI format 1_1 includes a carrier indicator field, the carrier indicator field may be used to indicate the serving cell of the downlink component carrier on which the PDSCH scheduled by DCI format 1_1 is allocated. Based on detecting DCI format 1_1 on the downlink component carrier of a serving cell, the terminal device 1 may recognize that the PDSCH scheduled by DCI format 1_1 is allocated on the downlink component carrier of the serving cell indicated by the carrier indicator field included in DCI format 1_1.

If DCI format 1_1 does not include a carrier indicator field, the downlink component carrier on which the PDSCH scheduled by DCI format 1_1 is allocated may be the same as the downlink component carrier on which the PDCCH including DCI format 1_1 is allocated. Based on detecting DCI format 1_1 on a certain downlink component carrier, the terminal device 1 may recognize that the PDSCH scheduled by DCI format 1_1 is allocated to that downlink component carrier.

The PDSCH may be transmitted to transmit a transport block. The PDSCH may be used to transmit a transport block. The transport block may be allocated to the PDSCH. The base station device 3 may transmit a PDSCH in which a transport block is allocated. The terminal device 1 may receive a PDSCH in which a transport block is allocated.

The downlink physical signal may correspond to a set of resource elements. The downlink physical signal does not have to be used to transmit information generated in a higher layer. The downlink physical signal may be used to transmit information generated in the physical layer. The downlink physical signal may be a physical signal used in a downlink component carrier. The physical layer processing unit 10 may transmit the downlink physical signal. The physical layer processing unit 30 may receive the downlink physical signal. In the downlink of the wireless communication system according to one aspect of the present embodiment, at least some or all of the following downlink physical signals may be used.
・Synchronization signal (SS)
・DL DMRS (DownLink DeModulation Reference Signal)
・CSI-RS (Channel State Information-Reference Signal)
・DL PTRS (DownLink Phase Tracking Reference Signal)
The synchronization signal may be used by the terminal device 1 to synchronize one or both of the frequency domain and the time domain of the downlink. The synchronization signal is a general term for a PSS (Primary Synchronization Signal) and an SSS (Secondary Synchronization Signal).

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

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

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

The set of antenna ports for DMRS for a PDSCH (DMRS associated with a PDSCH, DMRS included in a PDSCH, DMRS corresponding to a PDSCH) may be determined based on the set of antenna ports for the PDSCH. For example, the set of antenna ports for DMRS for a PDSCH may be the same as the set of antenna ports for the PDSCH.

The propagation path of a PDSCH may be estimated from the DMRS for that PDSCH. If the set of resource elements on which a certain PDSCH symbol is transmitted and the set of resource elements on which a DMRS symbol for that PDSCH is transmitted are included in the same precoding resource group (PRG), the PDSCH on which the PDSCH symbol is transmitted at a certain antenna port may be estimated from the DMRS for that PDSCH.

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

The propagation path of a PDCCH may be estimated from the DMRS for that PDCCH. If the same precoder is applied (or is assumed to be applied, or is assumed to be applied) to the set of resource elements on which a certain PDCCH symbol is transmitted and the set of resource elements on which a DMRS symbol for that PDCCH is transmitted, the PDCCH on which the PDCCH symbol is transmitted at a certain antenna port may be estimated from the DMRS for that PDCCH.

BCH (Broadcast CHannel), UL-SCH (Uplink-Shared CHannel), and DL-SCH (Downlink-Shared CHannel) are transport channels.

The BCH of the transport layer may be mapped to the PBCH of the physical layer. That is, a transport block delivered from a higher layer on the BCH of the transport layer may be placed on the PBCH of the physical layer. The UL-SCH of the transport layer may be mapped to the PUSCH of the physical layer. That is, a transport block delivered from a higher layer on the UL-SCH of the transport layer may be placed on the PUSCH of the physical layer. The DL-SCH of the transport layer may be mapped to the PDSCH of the physical layer. That is, a transport block delivered from a higher layer on the DL-SCH of the transport layer may be placed on the PDSCH of the physical layer.

The transport layer may apply HARQ (Hybrid Automatic Repeat reQuest) to the transport block.

A BCCH (Broadcast Control CHannel), a CCCH (Common Control CHannel), and a DCCH (Dedicated Control CHannel) are logical channels. For example,
The BCCH may be used to deliver an RRC message including an MIB or an RRC message including system information. The CCCH may be used to transmit an RRC message including RRC parameters common to multiple terminal devices 1. Here, the CCCH may be used, for example, for terminal devices 1 that are not RRC-connected. The DCCH may be used to transmit an RRC message dedicated to a certain terminal device 1. Here, the DCCH may be used, for example, for terminal devices 1 that are RRC-connected.

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

For example, the common RRC parameters may be included in an RRC message transmitted on the BCCH. For example, the common RRC parameters may be included in an RRC message transmitted on the DCCH.

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

The BCCH may be mapped to the BCH or DL-SCH. In other words, RRC messages containing MIB information may be delivered on the BCH. RRC messages containing system information other than MIB may be delivered on the DL-SCH. The CCCH is mapped to the DL-SCH or UL-SCH. In other words, RRC messages mapped to the CCCH may be delivered on the DL-SCH or UL-SCH. The DCCH may be mapped to the DL-SCH or UL-SCH. In other words, RRC messages mapped to the DCCH may be delivered on the DL-SCH or UL-SCH.

Figure 5 is a diagram showing an example of a procedure for transmitting a PUSCH between a terminal device 1 and a base station device 3 according to one aspect of this embodiment. As shown in Figure 5, the radio resource control layer processing unit 36 and the radio resource control layer processing unit 16 exchange RRC messages. Furthermore, the medium access control layer processing unit 35 and the medium access control layer processing unit 15 exchange MAC CE. Furthermore, the physical layer processing unit 30 notifies the physical layer processing unit 10 of the DCI format.

The physical layer processing unit 10 interprets the received DCI format and delivers a portion of the information obtained based on this interpretation to the medium access control layer processing unit 15. Here, this portion of the information obtained based on this interpretation is also referred to as HARQ information. For example, the HARQ information may include at least one or both of a HARQ process index (HPN) and a new data indicator (NDI). Here, if the received DCI format schedules the transmission of a PUSCH, this DCI format corresponds to an uplink grant.

In some cases, the DCI format may be replaced with a random access response grant. For example, a random access response grant may be used to schedule the initial transmission of a message 3 PUSCH in a random access procedure. Here, a PUSCH scheduled using a random access response grant in a 4-step contention-based random access procedure is classified as a message 3 PUSCH. Also, a PUSCH scheduled using a DCI format with a CRC sequence scrambled by the TC-RNTI in a 4-step contention-based random access procedure is classified as a message 3 PUSCH. Also, a PUSCH scheduled using a random access response grant in a contention-free random access procedure is not classified as a message 3 PUSCH.

Here, in the two-step collision-based random access procedure, a PUSCH scheduled by a fallback random access response grant is classified as a fallback message 3 PUSCH. Also, in the two-step collision-based random access procedure, a PUSCH scheduled by a DCI format with a CRC sequence scrambled by the TC-RNTI is classified as a fallback message 3 PUSCH.

The media access control layer processing unit 15 then issues a transmission instruction to the physical layer processing unit 10 based on the uplink grant. To issue the transmission instruction, the media access control layer processing unit 15 may further refer to RRC parameters provided by the radio resource control layer processing unit 16.

Next, the physical layer processing unit 10 transmits the PUSCH based on a transmission instruction issued by the medium access control layer processing unit 15. Here, to transmit the PUSCH, the physical layer processing unit 10 may further refer to RRC parameters provided by the radio resource control layer processing unit 16.

Here, the RRC parameters that the radio resource control layer processing unit 16 provides to the medium access control layer processing unit 15 or the physical layer processing unit 10 may be parameters managed by the radio resource control layer processing unit 16 based on the RRC message transmitted from the radio resource control layer processing unit 36.

Here, the radio resource control layer processing unit 36 may include RRC parameters for determining the method for determining PUSCH transmission opportunities in an RRC message and transmit the RRC parameters to the radio resource control layer processing unit 16.

Figure 6 is a diagram showing an example of PUSCH transmission according to one aspect of this embodiment. Here, 6000 indicates a pattern. Pattern 6000 is composed of regions 6001, 6002, and 6003. Also, 6010 is a pattern. Here, patterns 6000 and 6010 have the same configuration. In other words, pattern 6010 is composed of regions 6011, 6012, and 6013. Region 6001 corresponds to region 6011. Region 6002 corresponds to region 6012. Region 6003 corresponds to region 6013.

6, region 6001 includes the time regions of slot #n, slot #n+1, and slot #n+2. Region 6001 also includes a portion of the time region of slot #n+3. Region 6001 is also referred to as a downlink region.

In Figure 6, region 6002 includes part of the time domain of slot #n+3. Region 6002 is also called the flexible region.

In Figure 6, region 6003 includes part of the time domain of slot #n+3. Region 6003 also includes the time domain of slot #n+4. Region 6003 is also referred to as the uplink region.

In Figure 6, region 6011 includes the time regions of slot #n+5, slot #n+6, and slot #n+7. Region 6011 also includes part of the time region of slot #n+8. Region 6011 is also referred to as the downlink region.

In Figure 6, region 6012 includes part of the time domain of slot #n+8. Region 6012 is also called the flexible region.

In Figure 6, region 6013 includes part of the time domain of slot #n+8. Region 6013 also includes the time domain of slot #n+9. Region 6013 is also referred to as the uplink region.

For example, the configuration of the downlink region may be determined based on common RRC parameters provided by the radio resource control layer processing unit 16. Furthermore, the configuration of the flexible region may be determined based on common RRC parameters provided by the radio resource control layer processing unit 16. Furthermore, the configuration of the uplink region may be determined based on common RRC parameters provided by the radio resource control layer processing unit 16.

OFDM symbols included in the downlink region are also called downlink symbols. OFDM symbols included in the flexible region are also called flexible symbols. OFDM symbols included in the uplink region are also called uplink symbols.

The flexible region is a region that can be changed based on dedicated RRC parameters. For example, the dedicated RRC parameters can change part of the flexible region to a downlink region. Also, the dedicated RRC parameters can change part of the flexible region to an uplink region.

The flexible region is a region that can be changed based on the information indicated by DCI format 2_0. For example, the information indicated by DCI format 2_0 can change part of the flexible region to a downlink region. Also, the information indicated by DCI format 2_0 can change part of the flexible region to an uplink region.

In Fig. 6, 6100 denotes a PDCCH. Here, the DCI format included in the PDCCH 6100 is used for scheduling the PUSCH. After detecting the DCI format included in the PDCCH 6100, the terminal device 1 determines a transmission occasion for the PUSCH. Here, either physical slot counting or available slot counting may be used as a method for determining a transmission opportunity for the PUSCH.

6 shows an example of a physical slot count when the number of repetitions K is 4. Here, in the physical slot count, four slots are identified, from the first slot (slot #n+3) of the PUSCH to slot #n+6. One transmission opportunity is allocated to each of the four identified slots. That is, transmission opportunity 6101 is allocated to slot #n+3, transmission opportunity 6102 is allocated to slot #n+4, transmission opportunity 6103 is allocated to slot #n+5, and transmission opportunity 6104 is allocated to slot #n+6.

In other words, in physical slot counting, the physical layer processing unit 10 may identify four consecutive slots starting from the first slot of the PUSCH.

Here, the first slot of the PUSCH may be determined based on information provided by the DCI format. For example, one row of a Time Domain Resource Assignment (TDRA) table may be identified by the value of a time domain resource allocation field included in the DCI format. Here, the first slot of the PUSCH may be determined based on a parameter K2 associated with the identified row. Here, the parameter K2 may be a parameter that provides a slot offset from the slot in which the PDCCH 6100 is allocated to the first slot of the PUSCH.

At least parameter K2 may be associated with each row in a TDRA table.

Figure 7 is a diagram showing an example of the configuration of a TDRA table according to one aspect of this embodiment. The TDRA table shown in Figure 7 includes four rows, each corresponding to one value. For example, when the value of the time domain resource allocation field is 0, the slot offset K2 is 3, the first symbol index S is 0, the PUSCH length L is 14, and the number of repetitions K is 4. In this way, the base station device 3 can control the time domain resources of the PUSCH by setting the value of the time domain resource allocation field to an appropriate value. Furthermore, the terminal device 1 can determine the values of the parameters K2, SLIV, and the number of repetitions K based on the value of the time domain resource allocation field.

Here, SLIV is defined as a parameter for determining the first symbol index S and the length L of the PUSCH. The value of SLIV may be given by joint coding of S and L.

The first symbol index S is a parameter that indicates the index of the OFDM symbol at which one PUSCH transmission opportunity begins. The PUSCH length L is a parameter that indicates the number of OFDM symbols in one PUSCH transmission opportunity.

Furthermore, the number of repetitions K is a parameter used to determine the number of transmission opportunities determined for transmitting the PUSCH.

In this way, the TDRA table may be a table used to determine some or all of the first symbol index S of the PUSCH, the length L of the PUSCH, the parameter K2, and the number of repetitions K of the PUSCH.

Figure 8 is a diagram showing an example of PUSCH transmission according to one aspect of this embodiment. After detecting the DCI format included in the PDCCH 6100, the terminal device 1 determines a PUSCH transmission opportunity. In Figure 8, available slot count is used as a method for determining a PUSCH transmission opportunity.

For example, the available slot count may identify the first K slots among those available after the first slot of the PUSCH. In FIG. 8 , first, the availability of slots after the first slot of the PUSCH (slot #n+3) is checked, and slots #n+3, #n+4, #n+8, and #n+9, which correspond to the first K slots among those available, are identified based on the check. One transmission opportunity is allocated to each of the identified four available slots. That is, transmission opportunity 8101 is allocated to slot #n+3, transmission opportunity 8102 is allocated to slot #n+4, transmission opportunity 8103 is allocated to slot #n+8, and transmission opportunity 8104 is allocated to slot #n+9.

In this way, the physical slot count (first slot count) may be a method in which slots after the first slot of the PUSCH are counted to identify K slots. In other words, the physical slot count (first slot count) may be a method in which slots are counted without checking the availability of each slot to identify K slots. Also, the available slot count (second slot count) may be a method in which available slots after the first slot of the PUSCH are counted to identify K available slots. In other words, the available slot count may be a method in which slots are counted based on an availability check for each slot to identify K available slots. Identifying available slots (checking slot availability) will be described later.

In another example, the available slot count may be a method of counting and identifying available slots among the slots after the first slot of the PUSCH. That is, the available slot count may be a method of counting slots based on an availability check for each slot after the first slot of the PUSCH to identify K-1 available slots. Here, the first slot of the PUSCH may be determined to be an available slot without checking the slot's availability. As a result, the available slot count may identify a total of K available slots, including 1 available slot and K-1 available slots based on an availability check for each slot after the first slot of the PUSCH.

Here, when checking the availability of a slot, a check may be made to check the availability of a set of OFDM symbols. Here, the set of OFDM symbols may be determined based on the first symbol index S of the PUSCH and the length L of the PUSCH. For example, the set of OFDM symbols may include the OFDM symbols from the OFDM symbol with index S to the OFDM symbol with index S+L-1.

In checking the availability of a slot, a slot may be determined to be an available slot such that one or both of the following items 1 and 2 are satisfied for a set of OFDM symbols.
Item 1: None of the OFDM symbols included in the set of OFDM symbols is a downlink symbol determined by an RRC parameter. Item 2: None of the OFDM symbols included in the set of OFDM symbols is an OFDM symbol configured for transmitting an SS/PBCH block. In other words, the availability of a slot may be determined based on one or both of whether the set of OFDM symbols includes a downlink symbol determined by an RRC parameter and whether the set of OFDM symbols includes an OFDM symbol configured for transmitting an SS/PBCH block. Note that the check based on Item 2 may be performed on flexible symbols determined by an RRC parameter.

The availability of slots may not be affected by a change in the flexible region by DCI format 2_0. For example, even if part of the set of OFDM symbols is flexible symbols and the flexible symbols are changed to downlink symbols by information provided by DCI format 2_0, the check of slot availability may be performed under the assumption that part of the set of OFDM symbols is flexible symbols.

RRC parameters indicating the settings for transmitting SS/PBCH blocks may be provided by the radio resource control layer processing unit 16.

The physical layer processing unit 10 may provide the number of repetitions K or the number of identified transmission opportunities to the medium access control layer processing unit 15. The physical layer processing unit 10 may also provide HARQ information related to the transmission of the PUSCH to the medium access control layer processing unit 15.

The media access control layer processing unit may invoke the HARQ process up to K times based on the uplink grant corresponding to DCI format 6100. Here, each time the HARQ process is invoked, the HARQ process may issue a PUSCH transmission instruction to the physical layer processing unit 10.

The physical layer processing unit 10 may transmit the PUSCH in accordance with a PUSCH transmission instruction from the HARQ process. The PUSCH transmission may be omitted (cancelled or dropped). For example, the PUSCH transmission may be omitted when any of items 3 to 6 is satisfied for a set of OFDM symbols.
Item 3: At least one of the OFDM symbols included in the set of OFDM symbols is a downlink symbol. Item 4: At least one of the OFDM symbols included in the set of OFDM symbols is an OFDM symbol configured for transmitting an SS/PBCH block. Item 5: At least a part of the PUSCH transmission collides with a PUSCH having a higher priority than the PUSCH. Item 6: At least a part of the PUSCH transmission collides with a PRACH. In determining whether to omit PUSCH transmission, a change in the flexible region based on DCI Format 2_0 may be taken into consideration. For example, if some of the set of OFDM symbols are flexible symbols and the flexible symbols are changed to downlink symbols based on information provided by DCI Format 2_0, the determination of whether to omit PUSCH transmission may be performed under the assumption that some of the set of OFDM symbols are downlink symbols.

The TDRA table referenced for Message 3 PUSCH may not include a parameter indicating the repetition count K. In such cases, another method is needed to provide the repetition count K for Message 3 PUSCH.

For example, the MCS field included in the random access response grant may be used to provide the number of repetitions K. For example, X bits of the 4-bit MCS field included in the random access response grant may be used to set the number of repetitions K. Here, the remaining 4-X bits of the MCS field may be used to indicate an MCS index. Here, the MCS index is associated with a set of a certain modulation scheme and a certain target coding rate value.

For example, the number of repetitions K may be determined based on the value of the X bit. For example, if X=2 and {1, 2, 4, 8} is given as the set of the number of repetitions K, the code point for the X=2 bits may be set to indicate one of the set of the number of repetitions K. For example, if the code point for the X=2 bits is '00', it may be associated with 1, which is the first element of the set of the number of repetitions K. If the code point for the X=2 bits is '01', it may be associated with 2, which is the second element of the set of the number of repetitions K. If the code point for the X=2 bits is '10', it may be associated with 4, which is the third element of the set of the number of repetitions K. If the code point for the X=2 bits is '11', it may be associated with 8, which is the fourth element of the set of the number of repetitions K.

For example, the set of repetition count K may be provided by RRC signaling. Alternatively, the set of repetition count K may be provided by common RRC signaling. Alternatively, the set of repetition count K may be provided by SIB1.

On the other hand, the 4-X bit code point may be set to indicate an MCS index. For example, if X = 2, the 4-X = 2 bit code point may be set to indicate one of the sets of repetition count K. For example, the 4-X = 2 bit code point '00' may be associated with MCS index 0. The 4-X = 2 bit code point '01' may be associated with MCS index 1. The 4-X = 2 bit code point '10' may be associated with MCS index 2. The 4-X = 2 bit code point '11' may be associated with MCS index 3.

As mentioned above, the method of indicating the number of repetitions K using some of the bits in the MCS field has the problem of reducing the number of MCS index candidates available for the message 3 PUSCH.

For example, by selectively using multiple MCS index candidate sets, it is possible to alleviate the problem of a reduction in available MCS index candidates.

For example, a first MCS index candidate set and a second MCS index candidate set may be provided. Here, the physical layer processing unit 10 may determine whether to use the first MCS index candidate set or the second MCS index candidate set for the PUSCH based on one or both of: 1) a candidate set parameter that is a field included in the random access response grant and is determined by the value of the field that is different from the MCS field; or 2) the amount of PUSCH resources scheduled by the random access response grant.

For example, the time domain resource allocation field included in the random access response grant may be used to determine the candidate set parameters used for selecting the MCS index candidate set.

Figure 9 is a diagram showing an example of the configuration of a TDRA table according to one aspect of this embodiment. The table shown in Figure 9 includes columns indicating candidate set parameters. That is, one value for the parameter corresponds to a row corresponding to a value in the time domain resource allocation field. Here, a value of 0 for the candidate set parameter may correspond to the physical layer processing unit 10 selecting the first MCS index candidate set. Also, a value of 1 for the candidate set parameter may correspond to the physical layer processing unit 10 selecting the second MCS index candidate set.

For example, the frequency resource allocation field included in the random access response grant may be used to determine the candidate set parameters.

For example, the CSI request field included in the random access response grant may be used to determine the candidate set parameters.

For example, the physical layer processing unit 10 may determine the MCS index candidate set based on the length L of the PUSCH scheduled by the random access response grant. For example, the physical layer processing unit 10 may select the MCS index candidate set based on a comparison between the length L of the PUSCH scheduled by the random access response grant and a predetermined value. For example, if L is equal to or greater than the predetermined value, the physical layer processing unit 10 may select the first MCS index candidate set. Alternatively, if L is less than the predetermined value, the physical layer processing unit 10 may select the second MCS index candidate set.

For example, the physical layer processing unit 10 may determine the MCS index candidate set based on the number _{L_D} of OFDM symbols used for data in the PUSCH scheduled by the random access response grant. Here, the number _{L_D} of OFDM symbols used for data in the PUSCH may be given as the length L of the PUSCH minus the number _{L_DMRS} of OFDM symbols for DMRS per slot for the PUSCH. For example, the physical layer processing unit 10 may select the MCS index candidate set based on a comparison between _{L_D} and a predetermined value. For example, if _{L_D} is equal to or greater than the predetermined value, the physical layer processing unit 10 may select the first MCS index candidate set. Alternatively, if _{L_D} is less than the predetermined value, the physical layer processing unit 10 may select the second MCS index candidate set.

For example, the physical layer processing unit 10 may determine the MCS index candidate set based on the number _NRB of PUSCH resource blocks scheduled by the random access response grant. For example, the physical layer processing unit 10 may select the MCS index candidate set based on a comparison between the number _NRB of PUSCH resource blocks scheduled by the random access response grant and a predetermined value. For example, if _NRB is equal to or greater than the predetermined value, the physical layer processing unit 10 may select the first MCS index candidate set. Alternatively, if _NRB is less than the predetermined value, the physical layer processing unit 10 may select the second MCS index candidate set.

For example, the physical layer processing unit 10 may determine the MCS index candidate set based on the number N _RE of PUSCH resource elements scheduled by the random access response grant. Here, N _RE may be given by L*N _RB *N ^RB _sc . Or, N _RE may be given by (L-L _DMRS )*N _RB *N ^RB _sc . For example, the physical layer processing unit 10 may select the MCS index candidate set based on a comparison between N _RE and a predetermined value. For example, if N _RE is equal to or greater than the predetermined value, the physical layer processing unit 10 may select the first MCS index candidate set. Alternatively, if N _RE is less than the predetermined value, the physical layer processing unit 10 may select the second MCS index candidate set.

For example, DCI format 0_0 with a CRC sequence scrambled by the TC-RNTI may include a field indicating the candidate set parameters. In other words, when PUSCH is scheduled using DCI format 0_0 with a CRC sequence scrambled by the TC-RNTI, the physical layer processing unit 10 may determine the candidate set parameters based on the value of this field included in the DCI format.

For example, DCI format 0_0 with a CRC sequence scrambled by the TC-RNTI may include a parameter indicating the number of repetitions, where the MCS field included in DCI format 0_0 may not be used to indicate the number of repetitions.

The following describes various aspects of the device according to one aspect of this embodiment.

(1) In order to achieve the above object, aspects of the present invention employ the following means. That is, a first aspect of the present invention is a terminal device comprising a receiving unit that acquires a random access response grant and a transmitting unit that transmits a PUSCH scheduled by the random access response grant, wherein an MCS field included in the random access response grant is set to indicate one MCS value from one MCS index candidate set, and the transmitting unit selects the one MCS index candidate set from multiple MCS index candidate sets based on one or both of 1) the amount of resources for the PUSCH and 2) the values of fields other than the MCS field included in the random access response grant.

(2) A second aspect of the present invention is a base station device comprising: a transmitter that transmits a random access response grant; and a receiver that receives a PUSCH scheduled by the random access response grant, wherein the MCS field included in the random access response grant is set to indicate one MCS value from one MCS index candidate set, and the receiver selects the one MCS index candidate set from multiple MCS index candidate sets based on one or both of: 1) the amount of resources for the PUSCH; and 2) the values of fields other than the MCS field included in the random access response grant.

The programs that run on the base station device 3 and terminal device 1 according to the present invention may be programs that control a CPU (Central Processing Unit) or the like (programs that make a computer function) so as to realize the functions of the above-described embodiments according to the present invention. Information handled by these devices is temporarily stored in RAM (Random Access Memory) during processing, and then stored in various ROMs such as Flash ROM (Read Only Memory) or HDD.
The data is stored in a hard disk drive (D) and is read, modified, and written by the CPU as needed.

In addition, parts of the terminal device 1 and base station device 3 in the above-described embodiments may be implemented by a computer. In this case, the program for implementing this control function may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be read into a computer system and executed to implement the function.

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

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

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

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

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

Furthermore, while the above-described embodiment describes a terminal device as an example of a communications device, the present invention is not limited to this and can also be applied to terminal devices or communications devices such as stationary or non-mobile 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 the embodiments of the present invention have been described above in detail with reference to the drawings, the specific configuration is not limited to this embodiment and includes design modifications within the scope of the invention. Furthermore, the present invention is susceptible to various modifications within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included within the technical scope of the present invention. Furthermore, configurations in which elements described in the above embodiments are substituted for elements that achieve similar effects are also included.

1 (1A, 1B, 1C) Terminal device 3 Base station device 9 Wireless communication system 10, 30 Physical layer processing unit 10a, 30a Radio transmission unit 10b, 30b Radio reception unit 11, 31 Antenna unit 12, 32 RF unit 13, 33 Baseband unit 14, 34 Upper layer processing unit 15, 35 Medium access control layer processing unit 16, 36 Radio resource control layer processing unit 6000, 6010 Pattern 6001, 6002, 6003, 6011, 6012, 6013 Area 6100 PDCCH
6101, 6102, 6103, 6104, 8101, 8102, 8103, 8104 Transmission Opportunities

Claims (3)

a receiver for receiving a random access response grant;
a transmission unit that transmits a PUSCH scheduled by the random access response grant,
an MCS field included in the random access response grant is set to indicate an MCS value from an MCS index candidate set;
The transmitting unit selects the one MCS index candidate set from a plurality of MCS index candidate sets based on one or both of: 1) an amount of resources for the PUSCH; and 2) values of fields other than the MCS field included in the random access response grant. a transmitter for transmitting a random access response grant;
a receiving unit that receives a PUSCH scheduled by the random access response grant,
an MCS field included in the random access response grant is set to indicate an MCS value from an MCS index candidate set;
The base station device, wherein the receiving unit selects the one MCS index candidate set from a plurality of MCS index candidate sets based on one or both of: 1) an amount of resources for the PUSCH; and 2) values of fields other than the MCS field included in the random access response grant. A communication method used in a terminal device, comprising:
obtaining a random access response grant;
transmitting a PUSCH scheduled by the random access response grant;
an MCS field included in the random access response grant is set to indicate an MCS value from an MCS index candidate set;
The one MCS index candidate set is selected from a plurality of MCS index candidate sets based on one or both of: 1) an amount of resources for the PUSCH; and 2) values of fields other than the MCS field included in the random access response grant.