JP2020098946A - Terminal device, base station device, communication method, and integrated circuit - Google Patents

Abstract

To efficiently transmit uplink data.SOLUTION: A terminal device receives an uplink grant and higher layer information that gives instructions to set or release a higher layer parameter, stores the uplink grant as a grant to be set, determines whether an uplink HARQ operation is synchronous or asynchronous based at least on whether the higher layer parameter is set, and clears the grant to be set if the higher layer parameter is previously set and the higher layer information that instructs release of the parameter of the higher layer is received.SELECTED DRAWING: Figure 8

Description

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

Wireless access method and wireless network of cellular mobile communication (hereinafter, "Long Term Evolution (LTE)" or "Evolved Universal Terrestrial Radio Access: EUTRA
Is referred to as “3rd Generation Partnership Project”
Project: 3GPP) (Non-Patent Document 1). In LTE, a base station device is also called an eNodeB (evolved NodeB) and a terminal device is also called a UE (User Equipment). LT
E is a cellular communication system in which a plurality of areas covered by the base station device are arranged in a cell shape. Here, a single base station device may manage a plurality of cells.

LTE is compatible with Time Division Duplex (TDD). LTE adopting the TDD method is also referred to as TD-LTE or LTE TDD. In TDD, an uplink signal and a downlink signal are time division multiplexed. In addition, LTE supports frequency division duplex (FDD).

Latency reduction enhancements are being considered in 3GPP. For example, a high-speed grant (Scheduling request first grant) of a scheduling request and a high-speed grant (Pre-scheduled first grant) scheduled in advance have been studied as an enhancement of reduction of waiting time (Non-Patent Document 2).

"3GPP TS 36.321 V14.2.0 (2017-03) Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification (Release 14)", 22nd-March 2017. "L2 enhancements to reduce latency", R2-153490, Ericsson, 3GPP TSG-RAN WG2#91, Beijing, China, 24-28 August 2015.

However, in the wireless communication system as described above, a specific method has not been sufficiently studied for the procedure when uplink data is transmitted.

The present invention has been made in view of the above points, and an object thereof is to provide a terminal device, a base station device, a communication method, and an integrated circuit capable of efficiently transmitting uplink data. To aim.

(1) In order to achieve the above object, the embodiments of the present invention take the following means. That is, the terminal device according to one aspect of the present invention, whether to generate a MAC protocol data unit based on at least the receiving unit that receives the upper layer parameter skipUplinkTxSPS and whether or not the upper layer parameter skipUplinkTxSPS is set. And a medium access control layer processing unit for determining, based on at least whether the upper layer parameter skipUplinkTxSPS is set when the uplink HARQ operation is asynchronous. , Decide whether to perform non-adaptive retransmissions.

(2) Further, the terminal device according to one aspect of the present invention sets the upper layer information for instructing the setting or release of the upper layer parameter skipUplinkTxSPS, the receiving unit that receives the uplink grant, and the uplink grant. And a medium access control layer processing unit that determines whether the uplink HARQ operation is synchronous or asynchronous based on at least whether or not the upper layer parameter skipUplinkTxSPS is set. The access control layer processing unit is set when the upper layer parameter skipUplinkTxSPS is previously set (previously) and the upper layer parameter indicating the release of the upper layer parameter skipUplinkTxSPS is received, is set. Clear the grant.

(3) In addition, the base station apparatus according to one aspect of the present invention includes a transmitter that transmits an upper layer parameter skipUplinkTxSPS used by the terminal apparatus to determine whether to generate a MAC protocol data unit, and a non-adaptive re-transmission. Receiver that receives the transmission and uplink HA
Medium for determining whether a non-adaptive retransmission is performed by the terminal device, based at least on whether the upper layer parameter skipUplinkTxSPS is set for the terminal device when the RQ operation is asynchronous. And an access control layer processing unit.

(4) In addition, the base station device according to one aspect of the present invention provides upper layer information indicating the setting or release of the upper layer parameter skipUplinkTxSPS, and the uplink grant stored by the terminal device as the set grant. And a medium access control layer processing unit for determining whether the uplink HARQ operation is synchronous or asynchronous based on at least whether the upper layer parameter skipUplinkTxSPS is set for the terminal device. , The medium access control layer processing unit, the upper layer parameter skipUplinkTxSPS is preset to the terminal device (previously), and the upper layer information indicating the release of the upper layer parameter skipUplinkTxSPS Is transmitted to the terminal device, it is considered that the set grant is cleared by the terminal device.

(5) Further, a communication method of a terminal device according to one aspect of the present invention receives an upper layer parameter skipUplinkTxSPS and generates a MAC protocol data unit based on at least whether the upper layer parameter skipUplinkTxSPS is set. If the uplink HARQ operation is asynchronous, then it decides whether to perform a non-adaptive retransmission based at least on whether the upper layer parameter skipUplinkTxSPS is set.

(6) Further, in the communication method of the terminal device according to one aspect of the present invention, the upper layer information for instructing the setting or release of the upper layer parameter skipUplinkTxSPS and the uplink grant are received, and the uplink grant is set. Stored as a grant, and determines whether the uplink HARQ operation is synchronous or asynchronous based on at least whether the upper layer parameter skipUplinkTxSPS is set, and the upper layer parameter skipUplinkTxSPS is set in advance (previously). If the upper layer information indicating that the upper layer parameter skipUplinkTxSPS is released is received, the set grant is cleared.

(7) Also, the communication method of the base station device according to one aspect of the present invention transmits an upper layer parameter skipUplinkTxSPS used by the terminal device to determine whether to generate a MAC protocol data unit, and performs non-adaptive re-transmission. When the transmission is received and the uplink HARQ operation is asynchronous, a non-adaptive retransmission is performed by the terminal device based at least on whether the upper layer parameter skipUplinkTxSPS is set for the terminal device. Decide whether or not

(8) Further, the communication method of the base station device according to one aspect of the present invention is such that upper layer information for instructing setting or release of an upper layer parameter skipUplinkTxSPS and uplink stored by the terminal device as a set grant. Determines whether uplink HARQ operation is synchronous or asynchronous based on at least whether the upper layer parameter skipUplinkTxSPS is set for the terminal device by transmitting a link grant, and the upper layer parameter skipUplinkTxSPS is Pre-configured for the device,
Further, when the upper layer information instructing the release of the upper layer parameter skipUplinkTxSPS is transmitted to the terminal device, it is considered that the set grant is cleared by the terminal device.

According to the present invention, uplink data can be efficiently transmitted.

It is a figure which shows the concept of the wireless communication system in this embodiment. It is a figure which shows the structure of the slot in this embodiment. It is a figure which shows the example of the special field for activation of semi-persistent scheduling in this embodiment. It is a figure which shows the example of the special field for the release of the semi-persistent scheduling in this embodiment. It is a figure for explaining an example of non-empty transmission and empty transmission in this embodiment. It is a figure for explaining a method of clearing a set grant in this embodiment. It is a figure which shows the example of the special field for deactivation of the non-adaptive transmission of the transport block initially transmitted by the semi-persistent PUSCH in this embodiment. It is a schematic block diagram which shows the structure of the terminal device 1 in this embodiment. It is a schematic block diagram which shows the structure of the base station apparatus 3 in this embodiment.

Hereinafter, embodiments of the present invention will be described.

FIG. 1 is a conceptual diagram of a wireless communication system in this 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 are also referred to as the terminal device 1.

Physical channels and physical signals in this embodiment will be described.

In FIG. 1, the following uplink physical channels are used in the uplink wireless communication from the terminal device 1 to the base station device 3. Here, the uplink physical channel is used to transmit the information output from the upper layer.
・PUCCH (Physical Uplink Control Channel)
・PUSCH (Physical Uplink Shared Channel)
・PRACH (Physical Random Access Channel)
The PUCCH is used to transmit uplink control information (Uplink Control Information: UCI). Here, the uplink control information may include channel state information (CSI: Channel State Information) used to indicate the state of the downlink channel. Further, the uplink control information may include a scheduling request (SR: Scheduling Request) used to request the UL-SCH resource. Further, the uplink control information may include HARQ-ACK (Hybrid Automatic Repeat request ACKnowledgement). HARQ-ACK may indicate HARQ-ACK for downlink data (Transport block, Medium Access Control Protocol Data Unit: MAC PDU, Downlink-Shared Channel: DL-SCH, Physical Downlink Shared Channel: PDSCH).

That is, HARQ-ACK may indicate ACK (acknowledgement) or NACK (negative-acknowledgement). Here, HARQ-ACK is replaced with ACK/NACK
, HARQ feedback, HARQ response, HARQ information, or HARQ control information.

PUSCH is used for transmitting uplink data (Uplink-Shared Channel: UL-SCH). The PUSCH may also be used to send HARQ-ACK and/or CSI with the uplink data. Also, PUSCH may be used to transmit only CSI or only HARQ-ACK and CSI. That is, the PUSCH may be used to transmit only the uplink control information.

Here, the base station device 3 and the terminal device 1 exchange (transmit/receive) signals in a higher layer. For example, the base station device 3 and the terminal device 1 have RRC signaling (RRC message: Radio Resource) in the radio resource control (RRC: Radio Resource Control) layer.
Control message, RRC information: also called Radio Resource Control information) may be transmitted and received. Further, the base station device 3 and the terminal device 1 may transmit and receive a MAC control element in a MAC (Medium Access Control) layer. Where R
RC signaling and/or MAC control elements are also referred to as higher layer signaling.

PUSCH may be used to transmit RRC signaling and MAC control elements. Here, the RRC signaling transmitted from the base station device 3 may be common signaling to the plurality of terminal devices 1 in the cell. Further, the RRC signaling transmitted from the base station device 3 may be dedicated signaling (also referred to as dedicated signaling) for a certain terminal device 1. That is, the user device specific information (specific to the user device) may be transmitted to a certain terminal device 1 using dedicated signaling.

The PRACH is used to transmit the random access preamble. The PRACH may also be used to indicate initial connection establishment procedure, handover procedure, connection re-establishment procedure, synchronization for uplink transmission (timing adjustment), and PUSCH resource request. Good.

In FIG. 1, the following uplink physical signals are used in uplink wireless communication. Here, the uplink physical signal is not used for transmitting the information output from the upper layer, but is used by the physical layer.
・Uplink Reference Signal (UL RS)
In this embodiment, the following two types of uplink reference signals are used.
・DMRS (Demodulation Reference Signal)
・SRS (Sounding Reference Signal)
DMRS relates to the transmission of PUSCH or PUCCH. DMRS is time-multiplexed with PUSCH or PUCCH. The base station device 3 uses the DMRS to correct the propagation path of PUSCH or PUCCH. Hereinafter, transmitting both PUSCH and DMRS is simply referred to as transmitting PUSCH. Hereinafter, transmitting both PUCCH and DMRS is simply referred to as transmitting PUCCH.

SRS is not related to the transmission of PUSCH or PUCCH. The base station device 3 uses the SRS to measure the uplink channel condition.

In FIG. 1, the following downlink physical channels are used in downlink radio communication from the base station apparatus 3 to the terminal apparatus 1. Here, the downlink physical channel is used to transmit the information output from the upper layer.
・PBCH (Physical Broadcast Channel)
・PCFICH (Physical Control Format Indicator Channel)
・PHICH (Physical Hybrid automatic repeat request Indicator Channel)
・PDCCH (Physical Downlink Control Channel)
・EPDCCH (Enhanced Physical Downlink Control Channel)
・PDSCH (Physical Downlink Shared Channel)
・PMCH (Physical Multicast Channel)
The PBCH is used to broadcast a master information block (MIB, Broadcast Channel: BCH) commonly used by the terminal device 1.

PCFICH is used to transmit information indicating a region (OFDM symbol) used for transmitting PDCCH.

The PHICH is used to transmit a HARQ indicator (HARQ feedback, response information) indicating ACK (ACKnowledgement) or NACK (Negative ACKnowledgement) for the uplink data (Uplink Shared Channel: UL-SCH) received by the base station device 3. To be

The PDCCH and EPDCCH are used to transmit downlink control information (Downlink Control Information: DCI). Here, for the transmission of the downlink control information,
Multiple DCI formats are defined. That is, a field for downlink control information is defined in the DCI format and mapped to information bits.

For example, as a DCI format for the downlink, a DCI format (eg, DCI format 1, DCI format 1A, and/or) used for scheduling one PDSCH (transmission of one downlink transport block) in one cell. , DCI format 1C) may be defined.

Here, the DCI format for the downlink includes information about PDSCH scheduling. For example, in the DCI format for the downlink, a carrier indicator field (CIF), information about HARQ process number (HARQ process number), information about MCS (Modulation and Coding Scheme), information about redundancy version (Redundancy version). , And/or downlink control information such as information on resource block assignment (Resource block assignment). Here, the DCI format for the downlink is also referred to as a downlink grant and/or a downlink assignment. HARQ process number, HARQ process ID (ident
ifier) also called.

Further, for example, as a DCI format for the uplink, a DCI format (for example, DCI format 0, DCI format 0D, DCI) used for scheduling one PUSCH (transmission of one uplink transport block) in one cell. Format 4) is defined.

Here, the DCI format for the uplink includes information about PUSCH scheduling. For example, the DCI format for the uplink includes a carrier indicator field (CIF), information about a transmission power command (TPC command) for a scheduled PUSCH (TPC command for scheduled PUSCH), information about a cyclic shift for DMRS. (Cyclic shift DMRS), MCS and/or redundancy version information (Modulation and
downlink control information such as coding scheme and/or redundancy version) and/or information on resource block assignment and/or hopping resource allocation. Here, the DCI format for the uplink is also referred to as an uplink grant and/or an uplink assignment.

When the PDSCH resource is scheduled using the downlink assignment, the terminal device 1 may receive the downlink data on the scheduled PDSCH. Moreover, when the resource of PUSCH is scheduled using the uplink grant, the terminal device 1 may transmit the uplink data and/or the uplink control information on the scheduled PUSCH.

Here, the terminal device 1 may monitor a set of PDCCH candidates (PDCCH candidates) and/or EPDCCH candidates (EPDCCH candidates). Hereinafter, PDCCH is P
It may indicate DCCH and/or EPDDCH. Here, the PDCCH candidate indicates a candidate in which the PDCCH may be arranged and/or transmitted by the base station device 3. Further, the monitor may include the meaning that the terminal device 1 attempts to decode each PDCCH in the set of PDCCH candidates according to all the monitored DCI formats.

The set of PDCCH candidates monitored by the terminal device 1 is also referred to as a search space. The search space may include a common search space (CSS: Common Search Space). For example, the CSS may be defined as a common space for the plurality of terminal devices 1. Further, the search space may include a user equipment specific search space (USS: UE-specific Search Space). For example, USS is at least
It may be defined based on the C-RNTI assigned to the terminal device 1. The terminal device 1 may monitor the PDCCH in the CSS and/or the USS and detect the PDCCH addressed to itself.

Here, the RNTI assigned to the terminal device 1 by the base station device 3 is used for transmitting the downlink control information (transmission on the PDCCH). Specifically, a CRC (Cyclic Redundancy check) parity bit is added to the DCI format (which may be downlink control information), and after being added, the CRC parity bit is scrambled by the RNTI. Here, the CRC parity bit added to the DCI format may be obtained from the payload of the DCI format.

The terminal device 1 attempts to decode the DCI format to which the CRC parity bit scrambled by the RNTI is added, and detects the DCI format in which the CRC is successful as the DCI format addressed to itself (also referred to as blind decoding. ). That is, the terminal device 1 may detect the PDCCH accompanied by the CRC scrambled by the RNTI. Further, the terminal device 1 may detect the PDCCH accompanied by the DCI format to which the CRC parity bit scrambled by the RNTI is added.

DCI format/PDCCH/uplink grant/downlink assignment with CRC parity bits scrambled by RNTI, (1) DCI format/PDCCH/uplink grant/downlink assignment corresponding to RNTI, (2 ) DCI format/PDCCH/uplink grant/downlink assignment for RNTI, and (3) DCI format/PDCCH/uplink grant/downlink assignment for RNTI.

Here, the RNTI includes a C-RNTI (Cell-Radio Network Temporary Identifier).
May be included. C-RNTI is a unique (unique) identifier for the terminal device 1, which is used for identification of RRC connection and scheduling. The C-RNTI may also be utilized for dynamically scheduled unicast transmissions.

The RNTI also includes SPS C-RNTI (Semi-Persistent Scheduling C-RNTI).
May be included. SPS C-RNTI is a unique (unique) identifier for the terminal device 1 used for semi-persistent scheduling. The SPS C-RNTI may also be used for semi-persistently scheduled unicast transmissions.

Here, the transmission that is scheduled semi-persistently includes the meaning of transmission that is scheduled periodically. For example, SPS C-RNTI may be utilized for activation, reactivation, and/or retransmission of semi-persistently scheduled transmissions. Hereinafter, activation may include the meaning of reactivation and/or retransmission.

The SPS C-RNTI may also be utilized for release and/or deactivation of semi-persistently scheduled transmissions. Hereinafter, the release may include the meaning of deactivation. Here, in order to reduce the waiting time, the RNTI may be newly defined. For example, the SPS C-RNTI in the present embodiment may include an RNTI newly defined for reducing the waiting time.

The RNTI may include RA-RNTI (Random Access RNTI). RA-RNTI is an identifier used for transmission of a random access response message. That is, RA-RNTI is used for transmitting a random access response message in a random access procedure. For example, the terminal device 1 may monitor the PDCCH accompanied by the CRC scrambled by the RA-RNTI when transmitting the random access preamble. Further, the terminal device 1 may receive the random access response on the PDSCH based on the detection of the PDCCH accompanied by the CRC scrambled by the RA-RNTI.

The RNTI may include P-RNTI (Paging RNTI). P-RNTI
Is an identifier used for notification of changes in paging and system information. For example, P-RNTI is used for sending paging and system information messages. For example, the terminal device 1 may receive the paging on the PDSCH based on the detection of the PDCCH accompanied by the CRC scrambled by the P-RNTI.

The RNTI may also include SI-RNTI (System Information RNTI). SI-RNTI is an identifier used for broadcasting system information. For example, SI-RNTI is used for transmission of system information messages. For example, the terminal device 1 may receive the system information message on the PDSCH based on the detection of the PDCCH accompanied by the CRC scrambled by SI-RNTI.

Here, for example, PDCCH with CRC scrambled by C-RNTI may be transmitted in USS or CSS. Also, the PDCCH with CRC scrambled by RA-RNTI may be transmitted only in CSS. Also, the PDCCH with CRC scrambled by P-RNTI may be transmitted only in CSS. Further, the PDCCH with the CRC scrambled by SI-RNTI may be transmitted only in the CSS.

Also, the PDCCH with CRC scrambled by SPS C-RNTI may be transmitted only in the primary cell and the primary secondary cell. Also, the PDCCH with CRC scrambled by SPS C-RNTI may be transmitted in USS or CSS.

PDSCH is used for transmitting downlink data (Downlink Shared Channel: DL-SCH). The PDSCH is also used to send a system information message. Here, the system information message may be cell-specific (cell-specific) information. Also, the system information is included in the RRC signaling. Further, PDSCH is used for transmitting RRC signaling and MAC control element.

PMCH is used to transmit multicast data (Multicast Channel: MCH).

In FIG. 1, the following downlink physical signals are used in downlink wireless communication. Here, the downlink physical signal is not used to transmit the information output from the upper layer, but is used by the physical layer.
・Synchronization signal (SS)
・Downlink Reference Signal (DL RS)
The synchronization signal is used by the terminal device 1 to synchronize the downlink frequency domain and time domain. In the TDD system, the synchronization signal is arranged in subframes 0, 1, 5, and 6 in the radio frame. In the FDD system, the synchronization signal is placed in subframes 0 and 5 in the radio frame.

The downlink reference signal is used by the terminal device 1 to perform channel correction of the downlink physical channel. Here, the downlink reference signal is used by the terminal device 1 to calculate downlink channel state information.

In this embodiment, the following five types of downlink reference signals are used.
・CRS (Cell-specific Reference Signal)
URS (UE-specific Reference Signal) related to PDSCH
DMRS (Demodulation Reference Signal) related to EPDCCH
・NZP CSI-RS (Non-Zero Power Chanel State Information-Reference Sign
al)
・ZP CSI-RS (Zero Power Chanel State Information-Reference Signal)
・MBSFN RS (Multimedia Broadcast and Multicast Service over Single Frequency Network Reference signal)
・PRS (Positioning Reference Signal)
Here, the downlink physical channel and the downlink physical signal are collectively referred to as a downlink signal. In addition, the uplink physical channel and the uplink physical signal are collectively referred to as an uplink signal. The downlink physical channel and the uplink physical channel are generically called a physical channel. The downlink physical signal and the uplink physical signal are collectively referred to as a physical signal.

BCH, MCH, UL-SCH and DL-SCH are transport channels. A channel used in the medium access control (MAC) layer is called a transport channel. The unit of the transport channel used in the MAC layer is also called a transport block (transport block: TB) or a MAC PDU (Protocol Data Unit). HARQ (Hybrid Automatic Repeat reQuest) control is performed for each transport block in the MAC layer. The transport block is a unit of data delivered by the MAC layer to the physical layer. In the physical layer, transport blocks are mapped to codewords, and an encoding process is performed for each codeword.

Hereinafter, carrier aggregation will be described.

In the present embodiment, one or more serving cells may be set for the terminal device 1. A technique in which the terminal device 1 communicates via a plurality of serving cells is referred to as cell aggregation or carrier aggregation.

Here, the present embodiment may be applied to each of one or more serving cells configured for the terminal device 1. The present embodiment may be applied to a part of one or more serving cells set for the terminal device 1. Further, the present embodiment may be applied to each of one or a plurality of serving cell groups configured for the terminal device 1.

Further, in this embodiment, TDD (Time Division Duplex) and/or FDD (Frequency Division Duplex) may be applied. Here, in the case of carrier aggregation, TDD or FDD may be applied to all of one or more serving cells. Further, in the case of carrier aggregation, the serving cell to which TDD is applied and the serving cell to which FDD is applied may be aggregated. Here, the frame structure corresponding to FDD is also referred to as a frame structure type 1. Further, the frame structure corresponding to TDD is also referred to as a frame structure type 2 (Frame structure type 2).

Here, one or more serving cells to be configured may include one primary cell and zero or more secondary cells. For example, the primary cell is the serving cell that has undergone the initial connection establishment procedure, the serving cell that has initiated the connection re-establishment procedure, or the cell designated as the primary cell in the handover procedure. May be. Here, the secondary cell may be set at the time when the RRC connection is established or later.

Here, in the downlink, a carrier corresponding to a serving cell is referred to as a downlink component carrier. Further, in the uplink, a carrier corresponding to a serving cell is called an uplink component carrier. Further, the downlink component carrier and the uplink component carrier are collectively referred to as a component carrier.

Further, the terminal device 1 may simultaneously perform transmission and/or reception on a plurality of physical channels in one or a plurality of serving cells (component carriers). Here, one physical channel may be transmitted in one serving cell (component carrier) among a plurality of serving cells (component carriers).

Here, the transmission on the PUCCH may be performed only in the primary cell. In addition, the primary cell cannot be deactivated. In addition, cross-carrier scheduling does not apply to primary cell. That is, the primary cell is always scheduled using the PDCCH in the primary cell (primary cell is always scheduled via its PDCCH).

In addition, the secondary cell is activated and/or deactivated. In addition, when the PDCCH (which may be PDCCH monitoring) is configured in a certain secondary cell, cross carrier scheduling may not be applied to the certain secondary cell (In a case that PDCCH (PDCCH monitoring) of a secondary cell is configured, cross-carries scheduling may not apply this secondary cell). That is, in this case, the secondary cell may always be scheduled using the PDCCH in the secondary cell. In addition, when PDCCH (may be PDCCH monitoring) is not configured in a certain secondary cell, cross-carrier scheduling is applied, and the secondary cell always uses the PDCCH in one other serving cell. May be scheduled using.

The configuration of the slots in this embodiment will be described below.

FIG. 2 is a diagram showing the configuration of the slots in this embodiment. In FIG. 2, the horizontal axis represents the time axis and the vertical axis represents the frequency axis. Here, a normal CP (normal Cyclic Prefix) may be applied to the OFDM symbol. Also, an extended CP (extended Cyclic Prefix) may be applied to the OFDM symbol. Also, the physical signal or physical channel transmitted in each of the slots is represented by a resource grid.

Here, in the downlink, the resource grid may be defined by a plurality of subcarriers and a plurality of OFDM symbols. Also, in the uplink, the resource grid may be defined by multiple subcarriers and multiple SC-FDMA symbols. Further, the number of subcarriers forming one slot may depend on the bandwidth of the cell. The number of OFDM symbols or SC-FDMA symbols forming one slot may be seven. Here, each of the elements in the resource grid is referred to as a resource element. Further, the resource element may be identified by using the subcarrier number and the OFDM symbol or SC-FDMA symbol number.

Here, a resource block may be used to represent a mapping of a certain physical channel (such as PDSCH or PUSCH) to a resource element. Further, the resource block may be defined as a virtual resource block and a physical resource block. A physical channel may first be mapped to a virtual resource block. The virtual resource block may then be mapped to the physical resource block. One physical resource block may be defined by 7 consecutive OFDM symbols or SC-FDMA symbols in the time domain and 12 consecutive subcarriers in the frequency domain. Therefore, one physical resource block may be composed of (7×12) resource elements. Further, one physical resource block may correspond to one slot in the time domain and may correspond to 180 kHz in the frequency domain. Further, the physical resource blocks may be numbered from 0 in the frequency domain.

In the time domain, a radio frame consists of 20 slots. In the time domain, a subframe consists of two slots. That is, in the time domain, the radio frame is composed of 10 subframes.

In addition, in the present embodiment, in order to describe the process in the terminal device 1, the process in the MAC entity in the terminal device 1, the “Multiplexing and assembly” entity in the terminal device 1, and/or the HARQ entity in the terminal device 1 is described. doing. Hereinafter, the "Multiplexing and assembly" entity is also referred to as a first entity or a first process. The MAC entity comprises one first entity and one or more HARQ entities. That is, although the processing in the MAC entity in the terminal device 1, the first entity in the terminal device 1, and/or the HARQ entity in the terminal device 1 is described in the present embodiment, the processing in the present embodiment is Of course, the processing is performed by the device 1.

In this embodiment, a process in one MAC entity in the terminal device 1 will be described. In this embodiment, each of the one or more HARQ entities corresponds to one serving cell. For example, one MAC entity of the terminal device 1 may include a HARQ entity corresponding to the primary cell and a HARQ entity corresponding to the secondary cell.

The HARQ entity manages multiple HARQ processes. The HARQ entity directs the HARQ process to trigger an initial transmission or a retransmission. Here, the initial transmission is also referred to as HARQ initial transmission or PUSCH initial transmission. Here, the retransmission is also referred to as HARQ retransmission or PUSCH retransmission.

The terminal device 1 and the base station device 3 provide HARQ functionality. In the uplink, synchronous HARQ (synchronous HARQ) or asynchronous HARQ (asynchronous HARQ)
HARQ) is applied. That is, the uplink HARQ operation includes synchronous and asynchronous.

The base station device 3 may include the parameters of the upper layer in the signal of the upper layer (RRC message) and transmit the signal to the terminal device 1. The base station device 3 may transmit an upper layer signal (RRC message) instructing the setting or release of the upper layer parameters to the terminal device 1.

The base station device 3 may include the HARQ parameter in a higher layer signal (RRC message) and transmit it to the terminal device 1. The base station apparatus 3 may include the information instructing the setting or release of the HARQ parameter in the higher layer signal (RRC message) and transmit the signal to the terminal apparatus 1. Whether synchronous HARQ or asynchronous HARQ applies to the HARQ process may be determined based at least on the HARQ parameters. The HARQ parameter may be set for each serving cell. The HARQ parameter may be set for each group of serving cells. The HARQ parameter may be set for the terminal device 1.
That is, HARQ parameters may correspond to multiple serving cells.

Unless otherwise stated, the embodiments described below describe processing for one serving cell, one HARQ entity, and one HARQ process.

HARQ parameters may be used to determine uplink HARQ timing. k _PUSCH may be provided based at least on the HARQ parameters. k _PUSCH may be provided based at least on whether the HARQ parameter is set. Here, the terminal device 1 adjusts the transmission of the PUSCH in the subframe n based on the detection of the PDCCH (uplink grant) in the subframe n-k _PUSCH . That is, the subframe for transmitting PUSCH may be provided based at least on the HARQ parameter. That is, the subframe for transmitting the PUSCH may be provided based at least on whether the HARQ parameter is set.

Unless otherwise specified, the uplink grants described below are (1) an uplink grant for scheduling PUSCH initial transmission, or (2) an uplink grant for scheduling PUSCH transmission (initial transmission or retransmission). It may be replaced by a grant. The uplink grant for PUSCH initial transmission and the uplink grant for PUSCH retransmission may be detected in different types of search spaces.

In the present embodiment, the terminal device 1 and the base station device 3 support either or both of synchronous HARQ and asynchronous HARQ. The terminal device 1 may determine whether to apply synchronous HARQ or asynchronous HARQ to the HARQ process based on at least some or all of the following elements.
-Element 1: Whether HARQ parameters related to HARQ are set-Element 2: Search space in which PDCCH including uplink grant is detected (common search space, user equipment specific search space)
Element 3: RNTI (C-RNTI, SPS C-RNTI) used for transmission of PDCCH including uplink grant
-Element 4: Whether the uplink grant is a set grant For example, when the HARQ parameter is not set for the terminal device 1, synchronous HARQ may be applied to the corresponding HARQ process. ..

For example, when the HARQ parameter is set for the terminal device 1, asynchronous HARQ may be applied to the corresponding HARQ process.

When the HARQ parameter is set for the terminal device 1, either synchronous HARQ or asynchronous HARQ is applied to the corresponding HARQ process based on the type of search space in which the PDCCH including the uplink grant is detected. It may be decided whether to do it.

For example, when the HARQ parameter is set for the terminal device 1 and the PDCCH including the uplink grant is detected in the common search space, the synchronous HARQ may be applied to the corresponding HARQ process. ..

For example, when the HARQ parameter is set for the terminal device 1 and the PDCCH including the uplink grant is detected in the user equipment specific search space, the asynchronous HARQ is applied to the corresponding HARQ process. Good.

Synchronous HARQ may be applied to the transport blocks transmitted on PUSCH scheduled using DCI format 0. Asynchronous HARQ may be applied to transport blocks transmitted on PUSCH scheduled using DCI format 0D. DCI format 0 does not include information about HARQ process numbers. DCI format 0D contains information about the HARQ process number.

When the HARQ parameter is not set for the terminal device 1, the terminal device 1 may monitor the DCI format 0 in the common search space and the user device specific search space.

When the HARQ parameter is set for the terminal device 1, the terminal device 1 may monitor the DCI format 0 in the common search space and may monitor the DCI format 0D in the user device specific search space. Good.

When the HARQ parameter is set for the terminal device 1, at least based on the type of RNTI (for example, C-RNTI, SPS C-RNTI) used for transmission of the PDCCH including the uplink grant It may be determined whether to apply synchronous HARQ or asynchronous HARQ to the HARQ process that does.

For example, when the HARQ parameter is set for the terminal device 1 and the SPS C-RNTI is used for transmitting the PDCCH including the uplink grant, the synchronous HARQ is applied to the corresponding HARQ process. May be done.

For example, when the HARQ parameter is set for the terminal device 1, the SPS C-RNTI is used for transmitting the PDCCH including the uplink grant, and the PDCCH is detected in the common search space. In addition, synchronous HARQ may be applied to the corresponding HARQ process.

For example, the HARQ parameter is set for the terminal device 1, the SPS C-RNTI is used for transmitting the PDCCH including the uplink grant, and the PDCCH is detected in the user equipment specific search space. If so, asynchronous HARQ may be applied to the corresponding HARQ process.

For example, when the HARQ parameter is set for the terminal device 1 and C-RNTI is used for transmitting the PDCCH including the uplink grant, the asynchronous HARQ is applied to the corresponding HARQ process. May be.

For example, when the HARQ parameter is set for the terminal device 1, C-RNTI is used for transmitting the PDCCH including the uplink grant, and the PDCCH is detected in the common search space. , Synchronous HARQ may be applied to the corresponding HARQ process.

For example, the HARQ parameter is set for the terminal device 1, C-RNTI is used for transmitting the PDCCH including the uplink grant, and the PDCCH is detected in the user equipment specific search space. In some cases, asynchronous HARQ may be applied to the corresponding HARQ process.

When the HARQ parameter is set for the terminal device 1, whether to apply synchronous HARQ or asynchronous HARQ to the corresponding HARQ process is determined at least based on whether or not it is semi-persistent scheduling. May be.

When the HARQ parameter is set for the terminal device 1, either synchronous HARQ or asynchronous HARQ is applied to the corresponding HARQ process based on at least whether the uplink grant is the set grant. May be determined.

When the HARQ parameter is set for the terminal device 1, whether synchronous HARQ or asynchronous HARQ is applied to the corresponding HARQ process based on at least whether the fourth parameter skipUplinkTxSPS is set. May be determined.

When the HARQ parameter is set for the terminal device 1, (1) whether it is a semi-persistent scheduling, (2) whether an uplink grant is a set grant, and/or (3) Whether to apply synchronous HARQ or asynchronous HARQ for the corresponding HARQ process may be determined based at least on whether the fourth parameter skipUplinkTxSPS is set.

For example, when the HARQ parameter is set for the terminal device 1 and the semi-persistent scheduling is performed, the synchronous HARQ may be applied to the corresponding HARQ process.

For example, when the HARQ parameter is set for the terminal device 1 and the semi-persistent scheduling is used, the asynchronous HARQ may be applied to the corresponding HARQ process.

For example, when the HARQ parameter is set for the terminal device 1 and the semi-persistent scheduling is not performed, the synchronous HARQ or the asynchronous HARQ is applied to the corresponding HARQ process based on the above example. Good.

For example, when the HARQ parameter is set for the terminal device 1 and the uplink grant is the set grant, the synchronous HARQ may be applied to the corresponding HARQ process.

For example, when the HARQ parameter is set for the terminal device 1 and the uplink grant is the set grant, the asynchronous HARQ may be applied to the corresponding HARQ process.

For example, when the HARQ parameter is set for the terminal device 1 and the uplink grant is not set, the synchronous HARQ or the asynchronous HARQ is performed for the corresponding HARQ process based on the above-described example. May be applied. The uplink grant that is not the set grant may be the uplink grant corresponding to C-RNTI.

For example, when the HARQ parameter is set for the terminal device 1, the uplink grant is set, and the fourth parameter skipUplinkTxSPS is set, the corresponding HARQ process is set. On the other hand, synchronous HARQ may be applied.

For example, when the HARQ parameter is set for the terminal device 1, the uplink grant is set, and the fourth parameter skipUplinkTxSPS is not set, the corresponding HARQ process is set. On the other hand, asynchronous HARQ may be applied.

The initial transmission in the semi-persistent scheduling will be described below.

In the initial transmission in the semi-persistent scheduling, the operation (process) in the terminal device 1 is basically described, but the base station device 3 performs the same operation (process) in correspondence with the operation (process) of the terminal device 1. Of course).

Here, transmission on PUSCH (or transmission on UL-SCH) is performed at a timing based on SFN (System Fame Number) and subframe. That is, in order to specify the timing of transmission on the PUSCH, the SFN and the subframe number/index in the radio frame corresponding to the SFN are required. Here, SFN is the number/index of the radio frame. The subframe is also referred to as TTI (Transmission Time Interval).

Hereinafter, for simplification of description, the SFN (radio frame) and the subframe in which transmission on the PUSCH is performed are also simply referred to as a subframe. That is, the subframe in the following description may include the meaning of SFN (radio frame) and subframe.

Here, the base station apparatus 3 may set the uplink semi-persistent scheduling interval (cycle) for the terminal apparatus 1. For example, the base station apparatus 3 includes the first parameter semiPersistSchedIntervalUL for instructing the value of the interval of the semi-persistent scheduling in the uplink in the upper layer signal (RRC message) and transmits it to the terminal apparatus 1. Good.

For example,
The base station device 3 uses the first parameter semiPersistSchedIntervalUL as the value of the semi-persistent scheduling interval, 1 (1 subframe), 10 (10 subframes), 20 (20 subframes), 32 (32 subframes). Frames), 40 (40 subframes), 64 (64 subframes), 80 (80 subframes), 128 (128 subframes), 160 (160 subframes), 320 (320 subframes), and/or 640. (640 subframes) may be set.

That is, the base station device 3 may use the first parameter semiPersistSchedIntervalUL to set 1 (1 subframe) as the value of the interval of semi-persistent scheduling.

For example, the first parameter semiPersistSchedIntervalUL may be set for each serving cell. Further, the first parameter semiPersistSchedIntervalUL may be set for the primary cell. The value "1 (1 subframe)" of the semi-persistent scheduling interval may be set for the primary cell and/or the secondary cell (may be set for each serving cell).

Also, the base station apparatus 3 uses the DCI format for the uplink (for example, DCI format 0, DCI format 0D) and is semi-persistent (semi-persistent, semi-persistent, periodic) with respect to the terminal apparatus 1. The terminal device 1 may be instructed to allocate the PUSCH resource (physical resource block) and activate the transmission on the semi-persistent PUSCH. Further, the base station device 3 may instruct the terminal device 1 to release the semi-persistent PUSCH resource by using the DCI format for the uplink.

For example, in the terminal device 1, the CRC parity bit added to the DCI format is scrambled by the SPS C-RNTI, and the field of information about NDI (New data indicator) included in the DCI format is set to '0'. If set, it may be verified (confirmed, checked) whether the fields of the plurality of information items included in the DCI format are set to specific values. That is, the CRC parity bit added to the DCI format scrambled by SPS C-RNTI and the field of information on NDI may be used for validation for semi-persistent scheduling.

Here, if the verification is successful, the terminal device 1 considers that the received DCI format indicates valid semi-persistent activation or valid semi-persistent release. Good (may be recognized). Further, if the verification is not successful, the terminal device 1 may discard (clear) the DCI format.

Here, the semi-persistent activation may include activation of semi-persistent scheduling. Further, the semi-persistent activation may include a meaning of semi-persistent allocation of PUSCH resources. Further, the semi-persistent release may include the meaning of release of semi-persistent scheduling.

That is, the DCI format may be used to indicate the activation of semi-persistent uplink scheduling. The DCI format may also be used to enable activation of semi-persistent scheduling. The DCI format may also be used to indicate semi-persistent release.

FIG. 3 is a diagram illustrating an example of special fields for activation of semi-persistent scheduling. As shown in FIG. 3, multiple fields may be defined for activation of semi-persistent scheduling. Further, a predetermined value (which may be a specific value) set in each of the plurality of fields may be defined in order to activate the semi-persistent scheduling.

As shown in FIG. 3, for example, when the DCI format for the uplink (eg, DCI format 0) is used to activate the semi-persistent schedule, the scheduled PUSCH included in the DCI format for the uplink is used. The field of information on TPC command (TPC command for scheduled PUSCH) is'
00', information about cyclic shift for DMRS (Cyclic shift
Even if the field of DMRS is set to '000' and the most significant bit (MSB) of the field of Modulation and coding scheme and redundancy version (MSB) is set to '0'. Good.

Further, for example, when the DCI format for the uplink (for example, DCI format 0D) is used for activating the semi-persistent schedule, information on the TPC command for the scheduled PUSCH included in the DCI format for the uplink ( TPC command for scheduled PUSCH) field is set to '00', cyclic shift information for DMRS (Cyclic shift DMRS) field is set to '000', and information about MCS and redundancy version (Modulation and coding scheme and The most significant bit (MSB: most significant bit) of the redundancy version) field may be set to '0', and all the fields of the HARQ process number field (HARQ process number) may be set to '0'.

Further, for example, when the DCI format for the downlink (eg, DCI format 1 and/or DCI format 1A) is used for activating the semi-persistent schedule, the HARQ process included in the DCI format for the downlink is included. The number information (HARQ process number) field is '000 (FDD
)'or '0000 (for TDD)', the most significant bit (MSB) of the MCS field (Modulation and Coding scheme) is set to '0', and the redundancy version information The field of (redundancy version) may be set to '00'.

That is, the terminal device 1 may activate the semi-persistent scheduling when each of the plurality of information fields included in the DCI format is set to a specific value defined in advance. Here, it is needless to say that a plurality of information fields used for activation of the semi-persistent scheduling and a predetermined value to which the information fields are set are not limited to the examples described above. For example, a plurality of information fields used for activating semi-persistent scheduling and a predetermined value to which the information fields are set are defined in advance according to specifications and the like, and the base station device 3 and the terminal device are defined. It may be set as known information with respect to 1.

FIG. 4 is a diagram illustrating an example of special fields for release of semi-persistent scheduling. As shown in FIG. 4, multiple fields may be defined for the release of semi-persistent scheduling. Further, for the release of the semi-persistent scheduling, a predetermined value (which may be a specific value) set in each of the plurality of fields may be defined.

As shown in FIG. 4, for example, when the DCI format for the uplink (eg, DCI format 0) is used for releasing the semi-persistent schedule, the TPC for the scheduled PUSCH included in the DCI format for the uplink is used. The field of information on the command (TPC command for scheduled PUSCH) is set to '00', the field of the cyclic shift to DMRS (Cyclic shift DMRS) is set to '000', and the information about the MCS and the redundancy version (Modulation). The field of “and coding scheme and redundancy version” may be set to “11111”, and the fields of information on resource block assignment and hopping resource allocation may be set to “1”.

That is, when the DCI format for the uplink is used for release of semi-persistent scheduling, a field related to resource block allocation (resource allocation) may be set to a predetermined value for release. ..

Also, for example, when the DCI format for the uplink (for example, DCI format 0D) is used for the release of the semi-persistent schedule, information on the TPC command for the scheduled PUSCH included in the DCI format for the uplink (TPC field for command for scheduled PUSCH) is set to '00', and information about cyclic shift for DMRS (Cyclic shift DMRS)
Field is set to '000' and MCS and redundancy version information (Modulation and coding scheme and redundancy version) field is '1'
1111', all the fields of resource block assignment and hopping resource allocation (Resource block assignment and hopping resource allocation) are set to '1', and all the fields of HARQ process number (HARQ process number) are all' It may be set to 0'.

Further, for example, when the DCI format for the downlink (for example, DCI format 1 and/or DCI format 1A) is used for releasing the semi-persistent schedule, the HARQ process number included in the DCI format for the downlink is included. Information (HARQ process number) field is '000 (FD
D)) or '0000 (for TDD)', the MCS information (Modulation and Coding scheme) field is set to '11111', and the redundancy version information (redundancy version) field is set. It may be set to '00', and the field of the information (Resource block assignment) regarding resource block assignment (all fields of a plurality of fields may be set to '1'.

That is, when the DCI format for the downlink is used for release of semi-persistent scheduling, a field related to resource block allocation (resource allocation) may be set to a predetermined value for release. ..

That is, the terminal device 1 may release the semi-persistent scheduling when each of a plurality of information fields included in the DCI format is set to a specific value defined in advance. Here, it is a matter of course that the fields of a plurality of information used for release of the semi-persistent scheduling and the predetermined values to which the fields of the information are set are not limited to the above-mentioned examples. For example, a plurality of information fields used for release of semi-persistent scheduling and a predetermined value to which the information fields are set are defined in advance according to specifications and the like, and the base station device 3 and the terminal device 1 are defined. It may be set as known information between and.

In addition, for example, in the DCI format to which the CRC parity bit scrambled by SPS C-RNTI is added, "1 (1 subframe)" is set for the secondary cell as the value of the interval of semi-persistent scheduling. , May be transmitted to the secondary cell. In addition, for example, in the DCI format to which the CRC parity bit scrambled by SPS C-RNTI is added, an interval shorter than “10 (10 subframes)” is set for the secondary cell as the value of the interval of semi-persistent scheduling. In this case, it may be transmitted to the secondary cell.

Here, the terminal device 1 performs an effective uplink grant (a valid uplink grant) in order to perform transmission on the UL-SCH (transmission on the UL-SCH via the PUSCH, transmission on the UL-SCH on the PUSCH). ) Must have. Here, the uplink grant may include a meaning that the uplink transmission in a certain subframe is grant (granted or given).

For example, a valid uplink grant may be received dynamically on the PDCCH. That is, a valid uplink grant may be indicated using the DCI format with the CRC parity bit scrambled by the C-RNTI added. The uplink grant dynamically received on the PDCCH is also referred to as an uplink grant corresponding to C-RNTI.

Also, the valid uplink grant may be semi-permanently set. That is, a valid uplink grant may be indicated using the DCI format with the CRC parity bits scrambled by SPS C-RNTI.

Further, the terminal device 1 may store the uplink grant dynamically received on the PDCCH and/or the uplink grant semi-permanently set. Here, the HARQ entity passes the uplink grant dynamically received on the PDCCH and/or the semi-permanently configured uplink grant to the HARQ process, and the HARQ process receives the uplink grant from the HARQ entity. Link grants may be stored. Hereinafter, the stored uplink grant dynamically received on the PDCCH and/or the semi-persistently set uplink grant will be referred to as a stored uplink grant.

Also, the terminal device 1 (MAC entity) is configured with an uplink grant when semi-persistent activation is instructed.
Alternatively, the DCI format received from the base station device 3 may be stored. Here, the set uplink grant may be referred to as a set uplink grant (SPS UL grant) of semi-persistent scheduling or a set grant. Further, the set uplink grant may be referred to as a set uplink grant, a set uplink grant (SPS UL grant) of semi-persistent scheduling, and a set grant.

Here, based on the fact that the uplink grant (SPS UL grant) stored by the MAC entity has been cleared, the uplink grant (SPS UL grant) stored by the HARQ process may not be cleared. That is, even if the uplink grant (SPS UL grant) stored by the MAC entity is cleared, retransmission of the semi-persistent PUSCH is performed based on the uplink grant (SPS UL grant) stored by the HARQ process. It is possible to continue.

The uplink grant for semi-persistent scheduling may also be referred to as SPS uplink grant, semi-persistent grant (Semi-persistent grant), or semi-persistent scheduling assignment.

In addition, the base station device 3 may set valid and/or invalid semi-persistent scheduling for the terminal device 1. For example, the base station device 3 may set the validity and/or invalidity of the semi-persistent scheduling using an upper layer signal (for example, an RRC layer signal).

In addition, when semi-persistent scheduling is enabled, SPS C-RNTI, a parameter for indicating the value of the interval of semi-persistent scheduling in uplink, the number of empty transmissions before release (Number of first A parameter for instructing empty transmissions before release (also referred to as a third parameter implicitReleaseAfter) and/or an SPS deactivation timer (SPS deactivation timer, also referred to as a fourth parameter skipUplinkTxSPS) are supplied (set) at least. May be. Here, empty transmission (also referred to as empty transmission) will be described later. The third parameter implicitReleaseAfter and the fourth parameter skipUplinkTxSPS will be described later.

Here, for example, the terminal device 1 starts transmission on the semi-persistent PUSCH in a certain subframe, and then transmits on the semi-persistent PUSCH based on the number (1). The configured uplink grant may be initialized or re-initialized for recurring. That is, the terminal device 1 may continuously consider that the uplink grant to be set is generated in the subframe satisfying the expression (1).

That is, the terminal device 1 sets the value of Subframe_Offset (subframe offset) after setting the SPS uplink grant, and in the subframe specified based on the number (1), the Nth grant (set). It may be considered that the uplink grant and the SPS uplink grant) occur (consider sequentially).

Here, a subframe that satisfies the equation (1) is also referred to as a subframe that satisfies a predetermined condition. In addition, subframes other than the first subframe among the subframes that satisfy the equation (1) are also referred to as subframes that satisfy a predetermined condition. Here, the first subframe among the subframes satisfying the equation (1) may be a DCI-received subframe used for instructing activation, reactivation, or release of semi-persistent scheduling. ..

That is, the terminal device 1 sets the stored DCI format as the SPS uplink grant, and then, based on the number (1), transmits a subframe for transmission on the PUSCH corresponding to the Nth uplink grant to be set. May be specified. Here, in the equation (1), SFN and subframe respectively indicate the SFN and the subframe in which transmission on the PUSCH is performed.

Further, in the equation _{(1), SFN start_time} and subframe _{sta
rt_time} indicates the SFN and subframe at the time when the set uplink grant is initialized or _{reinitialized} , respectively. That is, SFN _{start_time} and subframe _{start_time} are SFN and subframes that start transmission on PUSCH based on the configured uplink grant (that is, initial transmission on PUSCH corresponding to the 0th configured uplink grant). Sub-frame) in which

In addition, in Expression (1), semiPersistSchedIntervalUL indicates an interval of semi-persistent scheduling in the uplink. Further, in the equation (1), Subframe_Offset (subframe offset) indicates the value of the offset used to specify the subframe in which transmission on PUSCH is performed.

Here, after setting the SPS uplink grant, the terminal device 1 sets Subframe_Offset in the number (1) to “0” if the parameter (twoIntervalConfig) is not valid by the upper layer. May be.

Further, the initialization may be performed when the semi-persistent scheduling is not activated. Also, re-initialization may be performed when semi-persistent scheduling is already active. Here, the initialization may include the meaning of initialization and the reinitialization may include the meaning of reinitialization. That is, the terminal device 1 may start transmission on the PUSCH in a certain subframe by initializing or re-initializing the configured uplink grant.

FIG. 5: is a figure for demonstrating the example of non-empty transmission (Non-empty transmission) and empty transmission (Empty transmission) in this embodiment. As shown in FIG. 5, a MAC protocol data unit (MAC PDU) is a MAC header (MAC header), a MAC service data unit (MAC SDU), and a MAC control element (MAC CE: MAC Control Element) and padding (padding bit). Here, the MAC protocol data unit may correspond to uplink data (UL-SCH). The MAC header may include one or more MAC subheaders. The MAC subheader corresponds to one MAC control element or one MAC service data unit. The MAC subheader may include a logical channel identifier corresponding to the MAC control element. The MAC subheader may include a logical channel identifier corresponding to one MAC service data unit.

Here, as the MAC control element, at least an SPS confirmation MAC control element (SPS confirmation MAC CE), a buffer status report MAC control element (BSR MAC CE: Buffer Status Report MAC CE, a MAC control element used for a buffer status report), Timing Advance Command MAC Control Element (TAC MAC CE: Timing Advance Command MAC CE, MAC control element used to send Timing Advance Command), Power Headroom Report MAC Control Element (PHR MAC CE: Power Headroom Report MAC CE, Power Head) MAC control element used for room report) and/or activation/deactivation MAC control element (MAC control element used for sending Activation/Deactivation MAC CE, activation/deactivation command), Multiple MAC control elements may be defined.

Further, as the buffer status report, a plurality of buffer status reports including at least a regular BSR, a periodic BSR, and a padding BSR may be defined. For example, each of the regular BSR, periodic BSR, and padding BSR may be triggered based on different events (conditions).

For example, in the regular BSR, data of a logical channel belonging to a certain logical channel group (LCG: Logical Channel Group) can be transmitted, and its transmission priority is higher than that of an already transmittable logical channel belonging to any LCG. In some cases, it may be triggered when there is no data available for transmission on the logical channel belonging to any LCG. Further, the regular BSR may be triggered when a predetermined timer (retxBSR-Timer) expires and the terminal device 1 has data that can be transmitted in a logical channel belonging to a certain LCG.

Also, the periodic BSR may be triggered when a predetermined timer (periodicBSR-Timer) expires. Further, the padding BSR may be triggered when the UL-SCH is allocated and the number of padding bits is equal to or larger than the size of the buffer status report MAC control element and its subheader.

The terminal device 1 may notify the base station device 3 of the transmission data buffer amount of the uplink data corresponding to each LCG as a message in the MAC layer using the buffer status report.

As shown in FIG. 5, a MAC protocol data unit may include zero, one, or multiple MAC service data units. The MAC protocol data unit may also include zero, one, or multiple MAC control elements. Also, padding may be added at the end of the MAC protocol data unit (Padding may occur at the end of the MAC PDU).

The base station device 3 may transmit the fourth parameter skipUplinkTxSPS to the terminal device 1.
For example, the base station device 3 may transmit the fourth parameter skipUplinkTxSPS using an upper layer signal (for example, an RRC layer signal). The fourth parameter skipUplinkTxSPS is used to determine whether to skip the uplink transmission corresponding to the set grant. When the fourth parameter skipUplinkTxSPS is set and there is no available data for transmission in the buffer of the terminal device 1, the terminal device 1 performs the uplink transmission corresponding to the set grant. Skip. Here, the uplink transmission may be PUSCH transmission. The fourth parameter skipUplinkTxSPS may be applied to the primary cell.

The base station device 3 may transmit the fifth parameter skipUplinkTxDynamic to the terminal device 1. For example, the base station device 3 may transmit the fifth parameter skipUplinkTxDynamic by using an upper layer signal (for example, an RRC layer signal). The fifth parameter skipUplinkTxDynamic is used to determine whether to skip the uplink transmission corresponding to the uplink grant corresponding to C-RNTI. When the fifth parameter skipUplinkTxDynamic is set and there is no available data for transmission in the buffer of the terminal device 1, the terminal device 1 determines the uplink grant corresponding to C-RNTI. Skip the corresponding uplink transmission. Here, the uplink transmission may be PUSCH transmission. The fifth parameter skipUplinkTxDynamic may be applied to multiple serving cells.

Here, the data available for transmission may include a MAC service data unit, a first MAC control element, and aperiodic channel state information. The first MAC control element may include an SPS confirmation MAC control element, a buffer status report MAC control element for regular BSR, and a power headroom report MAC control element. The data available for transmission does not include the second MAC control element. The second MAC control element includes a buffer status report MAC control element for padding BSR and a buffer status report for periodic BSR.

Hereinafter, the inclusion of the MAC service data unit in the MAC protocol data unit may mean that the MAC protocol data unit includes the MAC service data unit and the MAC subheader for the MAC service data unit. Hereinafter, the inclusion of a MAC control element in the MAC protocol data unit may mean that the MAC protocol data unit includes a control element and a MAC subheader for the control element.

That is, the MAC protocol data unit containing the data available for transmission may be the MAC protocol data unit containing at least one of the MAC service data unit and the first MAC control element.

That is, a MAC protocol data unit that does not include data that can be used for transmission includes (1) a MAC service data unit, a MAC protocol data unit that does not include a first MAC control element, and (2) a MAC service data unit, And a MAC protocol data unit that does not include the first MAC control element and that includes the second MAC control element, or (3) that does not include the MAC service data unit and that includes only the second MAC control element. It may be a MAC protocol data unit containing.

The reporting of aperiodic channel state information is requested (triggered) by downlink control information. The reporting of aperiodic channel state information is performed using PUSCH. The terminal device 1 may use the PUSCH to transmit both the MAC protocol data unit and the aperiodic channel state information.

Whether to skip uplink transmission is determined for each subframe.

Skipping the uplink transmission may be defined as an operation (processing) in the first entity in the terminal device 1 and the HARQ entity. The HARQ entity specifies the HARQ process associated with the subframe. The HARQ entity obtains the MAC protocol data unit from the first entity. The HARQ entity indicates the uplink grant to the first entity. The HARQ entity passes the MAC protocol data unit to the specified HARQ process if it can acquire the MAC protocol data unit from the first entity, and instructs the specified HARQ process to trigger an initial transmission. The HARQ entity does not instruct the HARQ process to trigger an initial transmission if it cannot acquire the MAC protocol data unit from the first entity.

The first entity generates a MAC protocol data unit and passes the generated MAC protocol data unit to the HARQ entity. The first entity does not generate a MAC protocol data unit if the following conditions are met.

The first entity is (1) not requested to transmit aperiodic channel state information in this subframe, and (2) the MAC protocol data unit does not include a MAC service data unit, and (3) The MAC protocol data unit includes the second MAC control element, (4) the fourth parameter skipUplinkTxSPS is set, and (5) the uplink grant indicated by the HARQ entity is set. If no MAC protocol data unit is generated for the HARQ entity. That is, the first entity (1) is not requested to transmit aperiodic channel state information in this subframe, and (2) does not contain data available to the MAC protocol data unit for transmission, And (3) if the fourth parameter skipUplinkTxSPS is set, and (4) the uplink grant indicated by the HARQ entity is the set grant, then no MAC protocol data unit for the HARQ entity is generated. .. Here, the uplink grant other than the set grant may be the uplink grant corresponding to C-RNTI.

The first entity is (1) not requested to transmit aperiodic channel state information in this subframe, and (2) the MAC protocol data unit does not include a MAC service data unit, and (3) The MAC protocol data unit includes a second MAC control element, and (4) a fifth parameter skipUplinkTxDynamic is set, and (5) a grant other than the grant to which the uplink grant indicated by the HARQ entity is set. If it is an uplink grant, it does not generate a MAC protocol data unit for the HARQ entity. That is, the first entity (1) is not requested to transmit aperiodic channel state information in this subframe, and (2) does not contain data available to the MAC protocol data unit for transmission, And (3) if the fifth parameter skipUplinkTxDynamic is set, and (4) the uplink grant indicated by the HARQ entity is an uplink grant other than the set grant, the MAC protocol for the HARQ entity. Do not generate a data unit. Here, the uplink grant other than the set grant may be the uplink grant corresponding to C-RNTI.

That is, skipping an uplink transmission means not generating a MAC protocol data unit or instructing the HARQ process to trigger an initial transmission.

"Transmission of aperiodic channel state information in this subframe is not requested, and the MAC protocol data unit does not include a MAC service data unit and the MAC protocol data unit includes a second MAC control element. “Exiting” may mean “the MAC protocol data unit does not contain data that can be transmitted”.

"The MAC protocol data unit does not include the MAC service data unit and the MAC protocol data unit includes the second MAC control element" means "the MAC protocol data unit includes the MAC service data unit and the first MAC control data unit. It does not include a MAC control element”.

When the release of the semi-persistent scheduling is instructed and the fourth parameter skipUplinkTxSPS is not set, the terminal device 1 clears the set grant.

When the release of the semi-persistent scheduling is instructed and the fourth parameter skipUplinkTxSPS is set, the terminal device 1 triggers the SPS confirmation. When the activation of the semi-persistent scheduling is instructed and the fourth parameter skipUplinkTxSPS is set, the terminal device 1 triggers the SPS confirmation.

If the SPS confirmation has been triggered and has not been canceled and the terminal device 1 has the uplink resources allocated for the initial transmission in this subframe, the terminal device 1 is the first entity. To generate an SPS confirm MAC control element, and cancel the triggered SPS confirm. Here, the uplink resource is a PUSCH resource. That is, the SPS confirm MAC control element is the response to the DCI for activation of the semi-persistent schedule. That is, the SPS confirm MAC control element is the response to the DCI for the release of the semi-persistent schedule.

The SPS confirm MAC control element may be specified by the MAC subheader. The SPS confirm MAC control element may be 0 bit. The terminal device 1 clears the set grant after the first transmission of the SPS confirmation MAC control element triggered by the release of the semi-persistent schedule.

As described above, the terminal device 1 semi-permanently (semi-persistently, periodically) performs transmission on the PUSCH (transmission on the UL-SCH) in the subframe specified based on the number (1). Good. When the fourth parameter skipUplinkTxSPS is not set, the terminal device 1
A grant (the configured grant) configured based on the third parameter implicitReleaseAfter (parameter for instructing the number of empty transmissions before release) set by the base station device 3 May be cleared.

For example, in the terminal device 1, the fourth parameter skipUplinkTxSPS is not set, and the number of empty transmissions corresponding to the initial transmission in the continuous semi-persistent PUSCH is determined by using the third parameter implicitReleaseAfter. The indicated value (number of transmissions)
When it reaches, the set grant may be cleared.

That is, if the fourth parameter skipUplinkTxSPS is not set, the terminal device 1 is a MAC protocol data unit that does not include any MAC service data unit (that is, includes zero MAC service data unit), May clear the configured grant immediately after the third parameter number of consecutive new MAC after the third parameter implicitReleaseAfter corresponding to the number of consecutive new MAC protocol data units. PDUs each containing zero MAC SDUs). Here, the number of consecutive empty transmissions corresponding to the initial transmission includes the number of empty transmissions in the resources of the semi-persistent scheduling. Here, the number of consecutive empty transmissions corresponding to the initial transmission does not include the number of empty transmissions on the dynamically scheduled PUSCH resources.

Here, when the fourth parameter skipUplinkTxSPS is not set, the terminal device 1
Uplink resources (semi-persistent scheduling resources, PUSCH resources) allocated by the base station apparatus 3 may be released (cleared) based on the third parameter implicitReleaseAfter. That is, if the fourth parameter skipUplinkTxSPS is not set, the terminal device 1 clears the set grant, similarly to the uplink assigned by the base station device 3 based on the third parameter implicitReleaseAfter. Resources may be released. Here, when the fourth parameter skipUplinkTxSPS is not set, the terminal device 1 clears the set grant when receiving the DCI used to instruct the release of the semi-persistent scheduling described above, and Alternatively, uplink resources may be released.

FIG. 6 is a diagram for explaining a method of clearing the set grant in the present embodiment.

As shown in FIG. 6, the terminal device 1 may receive the DCI used for instructing activation and/or reactivation of semi-persistent scheduling. In addition, the terminal device 1 may execute non-empty transmission with a resource of semi-persistent scheduling. That is, the non-empty transmission based on the set uplink grant may be executed according to the above-mentioned equation (1). In addition, the terminal device 1 may execute empty transmission with a resource of semi-persistent scheduling. That is, when the terminal device 1 does not have data available for transmission, the terminal device 1 may perform empty transmission with the resources of the semi-persistent scheduling.

Here, when the number of consecutive empty transmissions in the resources of the semi-persistent scheduling reaches the value (the number of transmissions) set using the third parameter implicitReleaseAfter, the terminal device 1 is set. You may clear the grant. Also, if the number of consecutive empty transmissions on the semi-persistent scheduling resource reaches the value (number of transmissions) set using the third parameter implicitReleaseAfter,
The terminal device 1 may release uplink resources (semi-persistent scheduling resources). That is, the terminal device 1 may clear the set grant and/or release the uplink resource based on the third parameter implicitReleaseAfter.

The terminal device 1 may clear the set grant when the HARQ parameter is changed. For example, the terminal device 1 may clear the set grant when the HARQ parameter is previously released and the information instructing the setting of the HARQ parameter is received. For example, the terminal device 1 may clear the set grant when the HARQ parameter is not (previously) previously set and the information instructing the setting of the HARQ parameter is received. For example, the terminal device 1 may clear the set grant when the HARQ parameter is previously set and the information indicating the release of the HARQ parameter is received.

When the HARQ parameter is changed, the RRC of the terminal device 1 may instruct the MAC entity to perform a partial reset. For example, when the HARQ parameter has not been released or set in advance (previously) and the information indicating the setting of the HARQ parameter is received, the RRC of the terminal device 1 instructs the MAC entity to perform a partial reset. You may. For example, when the HARQ parameter is previously set and the information indicating the release of the HARQ parameter is received, the RRC of the terminal device 1 causes the MAC entity to partially reset (partial reset).
May be instructed. The MAC entity clears the grant set for the serving cell when a partial reset of the MAC entity for the serving cell is requested by the upper layer (RRC).

Hereinafter, a method for a HARQ entity to identify a HARQ process associated with a subframe will be described. The HARQ entity passes the uplink grant to the specified HARQ process.

In synchronous HARQ, the HARQ entity specifies the HARQ process associated with the subframe without using the information received from the base station device 3. In synchronous HARQ, the HARQ process may be specified based on the subframe with which the uplink grant is associated. For example, in an FDD serving cell, multiple subframes {n+8·i} are associated with the same HARQ process. Here, n and i are integers. Here, the plurality of subframes {n+8·i} include subframe n, subframe n+8, subframe n+16, and the like.

In asynchronous HARQ, the HARQ process number may be specified using the uplink grant included in the PDCCH. Here, the uplink grant included in the PDCCH may include information on the HARQ process number. In asynchronous HARQ, the HARQ process number may be fixed (for example, 0) when the uplink grant does not include information on the HARQ process number.

In the asynchronous HARQ, the HARQ process number associated with the subframe in which the set grant occurs for the set grant may be specified based at least on the SFN and the subframe in which transmission on the PUSCH is performed. .. In asynchronous HARQ, the number of the HARQ process associated with the subframe in which the set grant occurs for the set grant may be given based on the following formula (2).

Here, in the equation (2), SFN and subframe respectively indicate the SFN and the subframe in which transmission on the PUSCH is performed. semiPersistSchedIntervalUL is the above-mentioned first parameter. numberOfConfUlSPS-Processes is the sixth parameter. The base station device 3 may send the sixth parameter numberOfConfUlSPS-Processes to the terminal device 1. For example, the base station device 3 may transmit the sixth parameter numberOfConfUlSPS-Processes using an upper layer signal (for example, an RRC layer signal). Sixth
The parameter numberOfConfUlSPS-Processes of indicates the number of HARQ processes configured for uplink semi-persistent scheduling.

Hereinafter, adaptive HARQ retransmission and non-adaptive HARQ retransmission will be described. Adaptive HARQ retransmissions are also referred to as adaptive retransmissions. Non-adaptive HARQ retransmissions are also called non-adaptive retransmissions.

Adaptive retransmission is retransmission performed based on the PDCCH (uplink grant) received from the base station device 3. A non-adaptive retransmission is a retransmission performed based on the uplink grant previously used by the HARQ process.

For synchronous HARQ, when the PDCCH including the uplink grant instructing retransmission is received after the initial transmission, the terminal device 1 performs adaptive retransmission regardless of the HARQ feedback received using PHICH. May be.

For synchronous HARQ, if the PDCCH including the uplink grant is not received after the initial transmission and the HARQ feedback received using PHICH indicates NACK, the terminal device 1 performs non-adaptive retransmission. Good. Here, the initial transmission may be initial transmission based on the set uplink grant.

For synchronous HARQ, if the PDCCH including the uplink grant is not received after the initial transmission and the HARQ feedback received using PHICH indicates ACK, the terminal device 1 transmits the HARQ (initial transmission, re-transmission). Transmission) is not performed, and the contents (data) of the HARQ buffer are retained.

The HARQ entity may also determine for synchronous HARQ, based on at least some or all of the following elements A through D, whether to direct the identified HARQ process to generate a non-adaptive retransmission. Good.
-Element A: Whether the uplink grant is a set grant-Element B: Whether the first parameter semiPersistSchedIntervalUL shorter than 10 subframes is set for the MAC entity-Element C: Specified HARQ Whether the HARQ buffer of the process is empty. Element D: Whether the state variable HARQ_FEEDBACK of the specified HARQ process is NACK. For example, if the following conditions A to D are satisfied for synchronous HARQ: , The HARQ entity may direct the identified HARQ process to generate non-adaptive retransmissions.
-Condition A: A grant for which an uplink grant is set-Condition B: The first parameter semiPersistSchedIntervalUL shorter than 10 subframes is set for the MAC entity-Condition C: HARQ of the specified HARQ process The buffer is not empty. Condition D: The state variable HARQ_FEEDBACK of the specified HARQ process is NACK. The uplink grant to be set is semi-persistent scheduling or uplink. Grants may be replaced with corresponding SPS C-RNTI. The fact that the uplink grant is not the set grant may be replaced with the fact that the uplink grant is the uplink grant included in the PDCCH or that the uplink grant corresponds to the C-RNTI.

When the uplink grant is the set grant, the terminal device 1 considers that the NDI bit corresponding to the HARQ process is toggled. That is, the condition that the uplink grant is the set grant may include the condition that the NDI bit corresponding to the HARQ process is toggled.

If the HARQ entity requests the HARQ process for an initial transmission or an adaptive retransmission, the HARQ process sets the state variable HARQ_FEEDBACK to NACK. If HARQ feedback for the transport block is received, the HARQ process sets the state variable HARQ_FEEDBACK to the received value (ACK, NACK).

When the first parameter semiPersistSchedIntervalUL shorter than 10 subframes is set, the fourth parameter skipUplinkTxSPS may be set without fail. That is, when the first parameter semiPersistSchedIntervalUL shorter than 10 subframes is set, the first parameter semiPersistSchedIntervalUL shorter than 10 subframes and the fourth parameter skipUplinkTxSPS may be set.

For synchronous HARQ, if condition A is satisfied and any of conditions B to D is not satisfied, the HARQ entity may instruct the specified HARQ process to trigger an initial transmission.

For synchronous HARQ, if Condition A is satisfied, the HARQ entity may instruct the identified HARQ process to perform initial transmission or non-adaptive retransmission based on whether Condition B to Condition D are satisfied.

The HARQ entity also determines for asynchronous HARQ whether to direct the identified HARQ process to generate non-adaptive retransmissions based at least on some or all of the following elements A through E: Good.
-Element A: Whether the uplink grant is a set grant-Element B: Whether the first parameter semiPersistSchedIntervalUL shorter than 10 subframes is set for the MAC entity-Element C: Specified HARQ Whether the HARQ buffer of the process is empty. Element D: Whether the state variable HARQ_FEEDBACK of the specified HARQ process is NACK. Element E: The fourth parameter skipUplinkTxSPS is set for the MAC entity. For example, for asynchronous HARQ, the HARQ entity may instruct the identified HARQ process to generate a non-adaptive retransmission if the following conditions A and E are satisfied.
-Condition A: The grant for which the uplink grant is set-Condition E: The fourth parameter skipUplinkTxSPS is set for the MAC entity In condition E, the length of the first parameter semiPersistSchedIntervalUL is from 10 subframes. It may be long or short. That is, in the condition E, the length of the first parameter semiPersistSchedIntervalUL need not be related.

For asynchronous HARQ, if condition A is satisfied and condition E is not satisfied, the HARQ entity may instruct the identified HARQ process to trigger an initial transmission.

For asynchronous HARQ, if condition A is met, the HARQ entity may indicate to the identified HARQ process an initial transmission or a non-adaptive retransmission based on whether condition E is met. ..

HARQ feedback for uplink transmissions is transmitted using PHICH. Here, the uplink transmission may be PUSCH transmission or transport block transmission. For synchronous HARQ, HARQ feedback for uplink transmissions may be sent using PHICH. For asynchronous HARQ, HARQ feedback for uplink transmission may not be transmitted.

The HARQ entity may determine whether the HARQ feedback for the uplink transmission is transmitted based on at least some or all of the following elements A to E for asynchronous HARQ. Here, whether the HARQ feedback for the uplink transmission is transmitted may be whether or not the HARQ feedback for the uplink transmission is received.
-Element A: Whether the uplink grant is a set grant-Element B: Whether the first parameter semiPersistSchedIntervalUL shorter than 10 subframes is set for the MAC entity-Element C: Specified HARQ Whether the HARQ buffer of the process is empty. Element D: Whether the state variable HARQ_FEEDBACK of the specified HARQ process is NACK. Element E: The fourth parameter skipUplinkTxSPS is set for the MAC entity. Whether or not, for example, for asynchronous HARQ, HARQ feedback for uplink transmission may be transmitted if the following conditions A and E are satisfied.
-Condition A: A grant for which an uplink grant is set.-Condition E: A fourth parameter skipUplinkTxSPS is set for a MAC entity. Condition A is satisfied and condition E is satisfied for asynchronous HARQ. If not satisfied, HARQ feedback for uplink transmission may not be transmitted.

For asynchronous HARQ, if condition A is met, the HARQ entity may determine whether HARQ feedback for the uplink transmission is sent based on whether condition E is met.

If the uplink HARQ operation is asynchronous HARQ and the uplink grant corresponds to C-RNTI, HARQ feedback for the uplink transmission may not be transmitted.

When receiving the NACK in subframe n, the terminal device 1 may perform PUSCH transmission (non-adaptive retransmission) in subframe n+p. When the terminal device 1 does not receive the ACK in the subframe n, the terminal device 1 may perform the PUSCH transmission (non-adaptive retransmission) in the subframe n+p.

If the HARQ entity indicates a non-adaptive retransmission to the HARQ process, the uplink HARQ operation is synchronous HARQ, and the state variable HARQ_FEEDBACK is set to ACK, the HARQ process sends (non-adaptive retransmission). Need not be generated.

If the HARQ entity indicates a non-adaptive retransmission to the HARQ process, the uplink HARQ operation is synchronous HARQ, and the state variable HARQ_FEEDBACK is set to NACK, the HARQ process transmits (non-adaptive retransmission). May be generated.

If the HARQ entity indicates a non-adaptive retransmission to the HARQ process, the uplink HARQ operation is asynchronous HARQ and the state variable HARQ_FEEDBACK is set to ACK, the HARQ process generates a transmission (non-adaptive retransmission). Need not be sent).

If the HARQ entity indicates a non-adaptive retransmission to the HARQ process, the uplink HARQ operation is asynchronous HARQ, and the state variable HARQ_FEEDBACK is set to NACK, the HARQ process transmits (non-adaptive retransmission). May be generated.

If the uplink HARQ operation is asynchronous HARQ and the uplink grant corresponds to C-RNTI, non-adaptive retransmission may not be performed.

The base station device 3 uses the DCI format for the uplink (for example, DCI format 0, DCI format 0D) to deactivate the non-adaptive transmission of the transport block initially transmitted by the semi-persistent PUSCH. You may instruct the terminal device 1.

For example, in the terminal device 1, the CRC parity bit added to the DCI format is scrambled by the SPS C-RNTI, and the field of information about NDI (New data indicator) included in the DCI format is set to '0'. If set, it may be verified (confirmed, checked) whether the fields of the plurality of information items included in the DCI format are set to specific values. That is, the CRC parity bit added to the DCI format scrambled by SPS C-RNTI and the field of information on NDI may be used for validation for semi-persistent scheduling.

Here, if the verification is successful, the terminal device 1 indicates that the received DCI format is a valid instruction for deactivating non-adaptive transmission of the transport block initially transmitted by the semi-persistent PUSCH. You may consider that you are doing (you may recognize). Further, if the verification is not successful, the terminal device 1 may discard (clear) the DCI format.

That is, the DCI format may be used to indicate deactivation of non-adaptive transmission of a transport block initially transmitted on the semi-persistent PUSCH.

FIG. 7 is a diagram showing an example of a special field for deactivating non-adaptive transmission of a transport block initially transmitted by the semi-persistent PUSCH in the present embodiment. As shown in FIG. 7, multiple fields may be defined for the deactivation of the non-adaptive transmission of the transport block initially transmitted on the semi-persistent PUSCH. Further, in order to deactivate the non-adaptive transmission of the transport block initially transmitted on the semi-persistent PUSCH, a predetermined value (which may be a specific value) set in each of the plurality of fields is defined. Good.

As shown in FIG. 7, for example, the DCI format for the uplink (eg, DCI format 0, DCI format 0D) is used for deactivating non-adaptive transmission of the transport block initially transmitted by the semi-persistent PUSCH. In this case, the field of information on the TPC command for the scheduled PUSCH (TPC command for scheduled PUSCH) included in the DCI format for the uplink is '11.
'Is set, the field of cyclic shift for DMRS (Cyclic shift DMRS) is set to '111', and the information of MCS and redundancy version (Modulation and coding scheme and redundancy version) is set to '11111' The fields of information on resource block assignment and hopping resource allocation (Resource block assignment and hopping resource allocation) may all be set to '1'.

One DCI format used for deactivating non-adaptive transmission of transport blocks initially transmitted on the semi-persistent PUSCH may correspond to one HARQ process.

In the case of the DCI format 0D including the information about the HARQ process number, the HARQ process corresponding to the DCI format 0D used for deactivating the non-adaptive transmission of the transport block initially transmitted by the semi-persistent PUSCH corresponds to the HARQ process. It may be given based on information about the number.

In the case of the DCI format 0 which does not include the information about the HARQ process number, the HARQ process corresponding to the DCI format 0 used for deactivating the non-adaptive transmission of the transport block initially transmitted by the semi-persistent PUSCH corresponds to the DCI format 0. Format 0 may be provided based at least on the received subframe.

The terminal device 1 may pass ACK to the MAC entity when the deactivation of the non-adaptive transmission of the transport block initially transmitted by the semi-persistent PUSCH is successfully verified, and the MAC entity is identified. The state variable HARQ_FEEDBACK of the HARQ process may be set to ACK. That is, the non-adaptive transmission deactivation instruction of the transport block initially transmitted on the semi-persistent PUSCH may be a response to the transport block initially transmitted on the semi-persistent PUSCH.

The terminal device 1 (HARQ process) may perform non-adaptive retransmission of the transport block until it detects a response to the transport block initially transmitted on the semi-persistent PUSCH. Here, the response may be a DCI format indicating a response to the transport block initially transmitted on the semi-persistent PUSCH, or HARQ feedback indicating ACK.

The terminal device 1 (HARQ process) may perform initial transmission based on the set grant after detecting a response to the transport block initially transmitted on the semi-persistent PUSCH.

The operation for flushing the HARQ buffer will be described. A maximum number of transmissions may be set for synchronous HARQ. The maximum number of transmissions may be the maximum number of retransmissions. The seventh parameter maxHARQ-Tx indicates the maximum number of transmissions. The base station device 3 may transmit the seventh parameter maxHARQ-Tx to the terminal device 1. For example, the base station device 3 may transmit the seventh parameter maxHARQ-Tx using an upper layer signal (for example, an RRC layer signal). The HARQ process may set the state variable CURRENT_TX_NB to 0 if the HARQ entity requests the HARQ process for initial transmission and the uplink HARQ operation is synchronous HARQ. If the HARQ entity requests a HARQ process for retransmission (adaptive retransmission, non-adaptive retransmission) and the uplink HARQ operation is synchronous HARQ, the HARQ process may increment the state variable CURRENT_TX_NB by one. The HARQ process may flush the HARQ buffer if the uplink HARQ operation is synchronous HARQ and the state variable CURRENT_TX_NB is a predetermined value. Here, the predetermined value may be one less than the maximum number of transmissions.

When the uplink HARQ operation is asynchronous HARQ, the terminal device 1 (HARQ process, HARQ entity) applies the operation regarding the flushing of the HARQ buffer based on at least some or all of the following elements A2 to E. You may decide whether or not to do it.
-Element A2: Whether or not the uplink grant related to initial transmission is a grant-Element B: Whether the first parameter semiPersistSchedIntervalUL shorter than 10 subframes is set for the MAC entity-Element C : Whether the HARQ buffer of the specified HARQ process is empty. Element D: Whether the state variable HARQ_FEEDBACK of the specified HARQ process is NACK. Element E: Fourth parameter to the MAC entity. Whether skipUplinkTxSPS is set. For example, if the uplink HARQ operation is asynchronous HARQ, and if the following conditions A2 and E are satisfied, the HARQ entity instructs the specified HARQ process to generate a non-adaptive retransmission. Good.
-Condition A2: A grant in which an uplink grant related to initial transmission is set.- Condition E: A fourth parameter skipUplinkTxSPS is set for the MAC entity. An uplink grant related to initial transmission is set. Being a grant may be replaced by being semi-persistent scheduling.

If the uplink HARQ operation is asynchronous HARQ and the condition A2 is not satisfied, the operation related to the HARQ buffer flush may not be applied.

If the uplink HARQ operation is asynchronous HARQ, and the condition A2 is satisfied and the condition E is not satisfied, the operation related to the HARQ buffer flush may not be applied.

If the uplink HARQ operation is asynchronous HARQ and the condition A is satisfied, the HARQ entity determines whether the HARQ entity satisfies the condition E or not, and the HARQ entity performs initial transmission or non-adaptive retransmission to the specified HARQ process. May be instructed.

If the uplink HARQ operation is asynchronous HARQ and the state variable CURRENT_TX_NB is a predetermined value, the HARQ process may not flush the HARQ buffer and may not perform non-adaptive retransmission, and , HARQ buffer contents (data) may be retained. Adaptive retransmission may be applied when the uplink HARQ operation is asynchronous HARQ and the state variable CURRENT_TX_NB is greater than or equal to a predetermined value. Here, the predetermined value may be one less than the maximum number of transmissions.

The configuration of the device in this embodiment will be described below.

FIG. 8 is a schematic block diagram showing the configuration of the terminal device 1 in this embodiment. As shown in the figure, the terminal device 1 includes an upper layer processing unit 101, a control unit 103, a receiving unit 105, a transmitting unit 107, and a transmitting/receiving antenna unit 109. The upper layer processing unit 101 includes a radio resource control unit 1011, a medium access control layer processing unit 1012, a scheduling information interpretation unit 1013, and an SPS control unit 1015. Further, the receiving unit 105 includes a decoding unit 1051, a demodulation unit 1053, a demultiplexing unit 1055, a wireless reception unit 1057, and a channel measurement unit 1059. Further, the transmission unit 107 is configured to include an encoding unit 1071, a modulation unit 1073, a multiplexing unit 1075, a wireless transmission unit 1077 and an uplink reference signal generation unit 1079.

The upper layer processing unit 101 outputs the uplink data (transport block) generated by a user's operation or the like to the transmission unit 107. The upper layer processing unit 101 also includes a medium access control (MAC) layer, a packet data integration protocol (Packet).
Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC)
Layer, Radio Resource Control (RRC) layer processing.

The radio resource control unit 1011 included in the upper layer processing unit 101 manages various setting information/parameters of its own device. The radio resource control unit 1011 sets various setting information/parameters based on the upper layer signal received from the base station device 3. That is, the radio resource control unit 1011 sets various setting information/parameters based on the information indicating various setting information/parameters received from the base station device 3. Also, the radio resource control unit 1011 generates information arranged in each uplink channel and outputs the information to the transmission unit 107. The radio resource control unit 1011 is also referred to as a setting unit 1011.

A medium access control layer processing unit 1012 included in the upper layer processing unit 101 performs processing of a medium access control (MAC: Medium Access Control) layer. The medium access control layer processing unit 1012 processes the MAC entity, the HARQ entity, and the first entity.

Here, the scheduling information interpretation unit 1013 included in the upper layer processing unit 101 interprets the DCI format (scheduling information) received via the reception unit 105, and based on the result of interpreting the DCI format, the reception unit 105, Also, control information is generated to control the transmission unit 107 and output to the control unit 103.

In addition, the SPS control unit 1015 included in the upper layer processing unit 101 has various setting information and
The control related to the SPS is performed based on the information related to the SPS such as parameters and the situation.

The control unit 103 also generates a control signal for controlling the reception unit 105 and the transmission unit 107 based on the control information from the upper layer processing unit 101. The control unit 103 outputs the generated control signal to the receiving unit 105 and the transmitting unit 107 to control the receiving unit 105 and the transmitting unit 107.

Further, the receiving unit 105 separates, demodulates, and decodes the received signal received from the base station device 3 via the transmitting/receiving antenna unit 109 according to the control signal input from the control unit 103, and processes the decoded information in upper layer processing. It is output to the unit 101.

Further, the wireless reception unit 1057 converts the downlink signal received via the transmission/reception antenna unit 109 into a baseband signal by quadrature demodulation (down conversion: down covert).
, Removes unnecessary frequency components, controls the amplification level so that the signal level is maintained properly, performs quadrature demodulation based on the in-phase component and quadrature component of the received signal, and digitalizes the quadrature-demodulated analog signal. Convert to signal. The wireless reception unit 1057 removes a portion corresponding to CP (Cyclic Prefix) from the converted digital signal, performs Fast Fourier Transform (FFT) on the signal from which CP is removed, and outputs a signal in the frequency domain. Extract.

Also, demultiplexing section 1055 demultiplexes the extracted signals into PHICH, PDCCH, EPDCCH, PDSCH, and downlink reference signals. The demultiplexing unit 1055 also compensates for the propagation paths of PHICH, PDCCH, EPDCCH, and PDSCH from the propagation path estimated values input from the channel measurement unit 1059. The demultiplexing unit 1055 also outputs the separated downlink reference signal to the channel measuring unit 1059.

Further, demodulation section 1053 multiplies the PHICH by a corresponding code, synthesizes the code, demodulates the synthesized signal by the BPSK (Binary Phase Shift Keying) modulation method, and outputs the demodulated section 1051. The decoding unit 1051 decodes the PHICH addressed to itself, and outputs the decoded HARQ indicator to the upper layer processing unit 101. Demodulation section 1053 demodulates the PDCCH and/or EPDCCH by the QPSK modulation method and outputs the result to decoding section 1051. Decoding section 1051 attempts to decode PDCCH and/or EPDCCH, and if the decoding is successful, outputs the decoded downlink control information and the RNTI corresponding to the downlink control information to upper layer processing section 101.

Further, the demodulation unit 1053 performs demodulation of the modulation scheme notified by the downlink grant such as QPSK (Quadrature Phase Shift Keying), 16QAM (Quadrature Amplitude Modulation), and 64QAM on the PDSCH, and outputs it to the decoding unit 1051. To do. Decoding section 1051 performs decoding based on the information regarding the coding rate notified by the downlink control information, and outputs the decoded downlink data (transport block) to upper layer processing section 101.

Further, the channel measuring unit 1059 measures downlink path loss and channel state from the downlink reference signal input from the demultiplexing unit 1055, and outputs the measured path loss and channel state to the upper layer processing unit 101. Further, channel measuring section 1059 calculates an estimated value of the downlink propagation path from the downlink reference signal, and outputs it to demultiplexing section 1055. The channel measurement unit 1059 performs channel measurement and/or interference measurement in order to calculate CQI (or CSI).

Further, the transmission unit 107 generates an uplink reference signal according to the control signal input from the control unit 103, encodes and modulates the uplink data (transport block) input from the higher layer processing unit 101, PUCCH, PUSCH, and the generated uplink reference signal are multiplexed and transmitted to the base station apparatus 3 via the transmission/reception antenna unit 109. Further, the transmission unit 107 transmits the uplink control information.

The coding unit 1071 also performs coding such as convolutional coding and block coding on the uplink control information input from the higher layer processing unit 101. Further, coding section 1071 performs turbo coding based on information used for PUSCH scheduling.

In addition, the modulation unit 1073 uses the modulation method notified of the coded bits input from the coding unit 1071 by the downlink control information such as BPSK, QPSK, 16QAM, 64QAM, or the modulation method predetermined for each channel. Modulate. Modulation section 1073 determines the number of data sequences to be spatially multiplexed based on information used for PUSCH scheduling, and is transmitted on the same PUSCH by using MIMO (Multiple Input Multiple Output) SM (Spatial Multiplexing). A plurality of pieces of uplink data according to the above are mapped to a plurality of sequences, and precoding is performed on these sequences.

In addition, the uplink reference signal generation unit 1079, a physical layer cell identifier (physical layer cell identity: referred to as PCI, Cell ID, etc.) for identifying the base station apparatus 3, a bandwidth for arranging the uplink reference signal, uplink A sequence determined by a predetermined rule (expression) is generated based on the cyclic shift notified by the link grant, the value of the parameter for generating the DMRS sequence, and the like. The multiplexing unit 1075 rearranges the PUSCH modulation symbols in parallel according to the control signal input from the control unit 103, and then performs a discrete Fourier transform (Discrete).
Fourier Transform: DFT). Also, the multiplexing unit 1075 multiplexes the PUCCH and PUSCH signals and the generated uplink reference signal for each transmission antenna port. That is, multiplexing section 1075 arranges the PUCCH and PUSCH signals and the generated uplink reference signal in resource elements for each transmission antenna port.

In addition, the wireless transmission unit 1077 performs an Inverse Fast Fourier Transform (IFFT) on the multiplexed signal to generate an SC-FDMA symbol, adds a CP to the generated SC-FDMA symbol, and adds the CP to the base. Band digital signal is generated, baseband digital signal is converted to analog signal, excess frequency components are removed by low pass filter, up-converted to carrier frequency, power is amplified, and transmit/receive antenna The data is output to the unit 109 and transmitted.

FIG. 9 is a schematic block diagram showing the configuration of the base station device 3 in this embodiment. As shown in the figure, the base station device 3 includes an upper layer processing unit 301, a control unit 303, a receiving unit 305, a transmitting unit 307, and a transmitting/receiving antenna unit 309. Further, the upper layer processing unit 301 is configured to include a radio resource control unit 3011, a medium access control layer processing unit 3012, a scheduling unit 3013, and an SPS control unit 3015. The receiving unit 305 includes a decoding unit 3051, a demodulation unit 3053, a demultiplexing unit 3055, a wireless reception unit 3057, and a channel measuring unit 3059. Further, the transmission unit 307 is configured to include an encoding unit 3071, a modulation unit 3073, a multiplexing unit 3075, a wireless transmission unit 3077, and a downlink reference signal generation unit 3079.

The upper layer processing unit 301 includes a medium access control (MAC) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a radio resource control (Radio). Resource Control (RRC) layer processing. Further, upper layer processing section 301 generates control information for controlling reception section 305 and transmission section 307, and outputs the control information to control section 303.

Further, the radio resource control unit 3011 included in the upper layer processing unit 301 generates downlink data (transport block), system information, RRC message, MAC CE (Control Element), etc., arranged in the downlink PDSCH, Alternatively, it is acquired from the upper node and output to the transmission unit 307. Further, the wireless resource control unit 3011 manages various setting information/parameters of each terminal device 1. The radio resource control unit 3011 may set various setting information/parameters for each terminal device 1 via a higher layer signal. That is, the radio resource control unit 1011 transmits/notifies information indicating various setting information/parameters. The radio resource control unit 3011 is also referred to as a setting unit 3011.

A medium access control layer processing unit 3012 included in the upper layer processing unit 301 performs processing of a medium access control (MAC: Medium Access Control) layer. The medium access control layer processing unit 3012 processes the MAC entity, the HARQ entity, and the first entity.

Further, the scheduling unit 3013 included in the higher layer processing unit 301 assigns a frequency to which a physical channel (PDSCH and PUSCH) is assigned based on the received channel state information, the estimated value of the propagation path input from the channel measurement unit 3059, the quality of the channel, and the like. And the subframe, the coding rate and modulation scheme of the physical channels (PDSCH and PUSCH), and the transmission power are determined. The scheduling unit 3013 generates control information (for example, DCI format) for controlling the reception unit 305 and the transmission unit 307 based on the scheduling result, and outputs the control information to the control unit 303. The scheduling unit 3013 further determines the timing of performing the transmission process and the reception process.

Further, the SPS control unit 3015 included in the upper layer processing unit 301 performs control related to SPS based on various setting information, information related to SPS such as parameters, and the situation.

Further, the control unit 303 generates a control signal for controlling the reception unit 305 and the transmission unit 307 based on the control information from the upper layer processing unit 301. The control unit 303 outputs the generated control signal to the receiving unit 305 and the transmitting unit 307 to control the receiving unit 305 and the transmitting unit 307.

Further, the receiving unit 305 separates, demodulates, and decodes the received signal received from the terminal device 1 via the transmission/reception antenna unit 309 according to the control signal input from the control unit 303, and decodes the decoded information to the upper layer processing unit 301. Output to. The wireless reception unit 3057 converts an uplink signal received via the transmission/reception antenna unit 309 into a baseband signal by quadrature demodulation (down conversion: down covert), removes unnecessary frequency components, and changes the signal level. The amplification level is controlled so as to be appropriately maintained, quadrature demodulation is performed based on the in-phase component and the quadrature component of the received signal, and the quadrature-demodulated analog signal is converted into a digital signal. The receiving unit 305 also receives the uplink control information.

Also, the wireless reception unit 3057 removes a portion corresponding to a CP (Cyclic Prefix) from the converted digital signal. The wireless reception unit 3057 performs a Fast Fourier Transform (FFT) on the signal from which the CP is removed, extracts a frequency domain signal, and outputs the signal to the demultiplexing unit 3055.

Further, the demultiplexing unit 1055 demultiplexes the signal input from the wireless reception unit 3057 into signals such as PUCCH, PUSCH, and uplink reference signal. Note that this separation is performed based on the radio resource allocation information included in the uplink grant, which the base station device 3 has previously determined by the radio resource control unit 3011 and has notified each terminal device 1. In addition, the demultiplexing unit 3055 determines the PUCCH and PU from the channel estimation value input from the channel measuring unit 3059.
The SCH propagation path is compensated. Also, the demultiplexing unit 3055 outputs the separated uplink reference signal to the channel measuring unit 3059.

In addition, the demodulation unit 3053 performs an inverse discrete Fourier transform (IDFT) on the PUSCH, acquires a modulation symbol, and for each of the modulation symbols of the PUCCH and PUSCH, BPSK (Binary Phase Shift Keying), QPSK, 16QAM
, 64QAM, or the like, or demodulates the received signal using a modulation method that the terminal device has notified to each terminal device 1 in advance by an uplink grant. The demodulation unit 3053 uses the MIMO SM based on the number of spatially multiplexed sequences previously notified to each terminal device 1 by the uplink grant and the information for instructing the precoding to be performed on the sequences. The modulation symbols of a plurality of uplink data transmitted by PUSCH are separated.

In addition, the decoding unit 3051 codes the demodulated PUCCH and PUSCH coded bits in a predetermined coding scheme, in a predetermined manner, or in a self-reported manner to the terminal apparatus 1 by the terminal apparatus 1 through the uplink grant. Decoding is performed at the conversion rate, and the decoded uplink data and the uplink control information are output to upper layer processing section 101. When PUSCH is retransmitted, decoding section 3051 performs decoding using the coded bits held in the HARQ buffer input from upper layer processing section 301 and the demodulated coded bits. The channel measurement unit 309 measures a channel estimation value, channel quality, etc. from the uplink reference signal input from the demultiplexing unit 3055, and outputs it to the demultiplexing unit 3055 and the upper layer processing unit 301.

In addition, the transmission unit 307 generates a downlink reference signal according to the control signal input from the control unit 303, encodes the HARQ indicator, downlink control information, and downlink data input from the higher layer processing unit 301, Then, the signal is modulated, the PHICH, PDCCH, EPDCCH, PDSCH, and the downlink reference signal are multiplexed, and the signal is transmitted to the terminal device 1 via the transmission/reception antenna unit 309.

In addition, the encoding unit 3071 encodes the HARQ indicator, the downlink control information, and the downlink data input from the higher layer processing unit 301 by predetermined encoding such as block encoding, convolutional encoding, and turbo encoding. Encoding is performed using the method, or encoding is performed using the encoding method determined by the radio resource control unit 3011. The modulation unit 3073 modulates the coded bits input from the coding unit 3071 with a predetermined modulation scheme such as BPSK, QPSK, 16QAM, 64QAM or the like, or a modulation scheme determined by the radio resource control unit 3011.

In addition, the downlink reference signal generation unit 3079 determines a sequence known to the terminal device 1 based on a physical layer cell identifier (PCI) for identifying the base station device 3 according to a predetermined rule. Generate as. The multiplexing unit 3075 multiplexes the modulated modulation symbol of each channel and the generated downlink reference signal. That is, multiplexing section 3075 arranges the modulated symbols of each modulated channel and the generated downlink reference signal in resource elements.

In addition, the wireless transmission unit 3077 generates an OFDM symbol by performing an Inverse Fast Fourier Transform (IFFT) on the multiplexed modulation symbols and the like, adds a CP to the generated OFDM symbol, and adds a baseband digital signal. A signal is generated, a baseband digital signal is converted to an analog signal, an extra frequency component is removed by a low-pass filter, up-converted to a carrier frequency, power is amplified, and output to a transmitting/receiving antenna unit 309. To send.

Hereinafter, various aspects of the terminal device 1 and the base station device 3 in the present embodiment will be described.

(1) A first aspect of the present embodiment is a terminal device 1, which uses a MAC protocol based on at least a receiving unit that receives an upper layer parameter skipUplinkTxSPS and whether the upper layer parameter skipUplinkTxSPS is set. And a medium access control layer processing unit for determining whether to generate a data unit, the medium access control layer processing unit based on at least whether or not the upper layer parameter skipUplinkTxSPS is set. Decide whether to perform a send. Here, the medium access control layer processing unit determines whether to perform non-adaptive retransmission based on at least whether the upper layer parameter skipUplinkTxSPS is set when the uplink HARQ operation is asynchronous. You may decide.

(2) In the first aspect of the present embodiment, the medium access control layer processing unit, when the uplink HARQ operation is synchronous, regardless of whether or not the upper layer parameter skipUplinkTxSPS is set, Determines whether to perform non-adaptive retransmission of persistently scheduled transport blocks.

(3) In the first aspect of the present embodiment, the medium access control layer processing unit is a grant in which the upper layer parameter skipUplinkTxSPS is set, and an uplink grant is set, and MAC If the protocol data unit does not include the MAC service data unit but only the MAC CE for the padding BSR or the periodic BSR, the MAC protocol data unit is not generated. In the first aspect of the present embodiment, the medium access control layer processing unit is a grant in which the upper layer parameter skipUplinkTxSPS is set, and an uplink grant is set, and a MAC protocol data unit. Does not include a MAC service data unit and a MAC CE other than the padding BSR or the MAC CE for the periodic BSR, the MAC protocol data unit is not generated.

(4) A second aspect of the present embodiment is the base station device 3, which includes a transmitter that transmits an upper layer parameter skipUplinkTxSPS used by the terminal device to determine whether to generate a MAC protocol data unit. A receiver for receiving non-adaptive retransmissions, and whether or not non-adaptive retransmissions are performed by the terminal device, based at least on whether the upper layer parameter skipUplinkTxSPS is set for the terminal device. And a medium access control layer processing unit for determining. Here, the medium access control layer processing unit, when the uplink HARQ operation is asynchronous, based on at least whether or not the upper layer parameter skipUplinkTxSPS is set for the terminal device, non-adaptive retransmission May be performed by the terminal device.

(5) In the second aspect of the present embodiment, the medium access control layer processing unit, if the uplink HARQ operation is synchronous, whether the upper layer parameter skipUplinkTxSPS is set for the terminal device. Regardless, it determines whether non-adaptive retransmissions of semi-persistently scheduled transport blocks are performed by the terminal.

(6) In the second aspect of the present embodiment, the upper layer parameter skipUplinkTxSPS is set for the terminal device, and an uplink grant is set for the MAC protocol data unit. Does not include a MAC service data unit, but includes a MAC CE for padding BSR or periodic BSR, the MAC protocol data unit is not generated by the terminal device.

(7) A third aspect of the present embodiment is the terminal device 1, which includes upper layer information for instructing setting or release of an upper layer parameter skipUplinkTxSPS, and a receiving unit that receives an uplink grant, and the uplink. A medium access control layer processing unit that stores a link grant as a set grant, and determines whether the uplink HARQ operation is synchronous or asynchronous at least based on whether or not the upper layer parameter skipUplinkTxSPS is set. The medium access control layer processing unit, the parameter skipUplinkTxSPS of the upper layer is previously set (previously), and, when receiving the information of the upper layer indicating the release of the parameter skipUplinkTxSPS of the upper layer, Clear the set grant.

(8) In the third aspect of the present embodiment, the medium access control layer processing unit has not previously (previously) set the upper layer parameter skipUplinkTxSPS, and instructs the setting of the upper layer parameter skipUplinkTxSPS. When receiving the information of the upper layer
Clear the set grant.

(9) In the third aspect of the present embodiment, the medium access control layer processing unit has previously (previously) released the upper layer parameter skipUplinkTxSPS, and instructs the medium access control layer processing unit to set the upper layer parameter skipUplinkTxSPS. When the information of the upper layer is received, the set grant is cleared.

(10) The fourth aspect of the present embodiment is the base station device 3, which stores upper layer information indicating the setting or release of the upper layer parameter skipUplinkTxSPS, and is stored by the terminal device as the set grant. A transmission unit that transmits an uplink grant, and a medium access control layer processing unit that determines whether the uplink HARQ operation is synchronous or asynchronous based on at least whether the upper layer parameter skipUplinkTxSPS is set for the terminal device. And, the medium access control layer processing unit, the parameter skipUplinkTxSPS of the upper layer is preset for the terminal device (previously), and,
When the upper layer information indicating the release of the upper layer parameter skipUplinkTxSPS is transmitted to the terminal device, it is considered that the set grant is cleared by the terminal device.

(11) In the third aspect of the present embodiment, the medium access control layer processing unit is configured such that the parameter skipUplinkTxSPS of the upper layer is not previously set for the terminal device, and When the upper layer information instructing the setting of the parameter skipUplinkTxSPS is transmitted to the terminal device, it is considered that the set grant is cleared by the terminal device.

(12) In the third aspect of the present embodiment, the medium access control layer processing unit has previously (previously) released the upper layer parameter skipUplinkTxSPS in the terminal device, and has the upper layer parameter skipUplinkTxSPS. When the upper layer information instructing the setting of is transmitted to the terminal device, it is considered that the set grant is cleared by the terminal device.

By this means, uplink data can be efficiently transmitted.

A program that operates in the base station device 3 and the terminal device 1 according to the present invention is a program that controls a CPU (Central Processing Unit) or the like (functions a computer so as to realize the functions of the above-described embodiments according to the present invention. Program). Information handled by these devices is temporarily stored in a RAM (Random Access Memory) during the processing, and thereafter, various ROMs such as a flash ROM (Read Only Memory) and an HD.
The data is stored in a D (Hard Disk Drive), and is read out by the CPU as necessary, and correction/writing is performed.

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

The “computer system” referred to here is a computer system built in the terminal device 1 or the base station device 3, and includes an OS and hardware such as peripheral devices. Further, the "computer-readable recording medium" means a portable medium such as a flexible disk, a magneto-optical disk, a ROM, a CD-ROM, or a storage device such as a hard disk built in a computer system.

Further, the "computer-readable recording medium" means a program that dynamically holds a program for a short time, such as a communication line when transmitting the program through a network such as the Internet or a communication line such as a telephone line. In this case, a volatile memory inside the computer system that serves as a server or a client in which the program is held for a certain period of time may be included. Further, the above-mentioned program may be one for realizing a part of the above-mentioned functions, and may be one that can realize the above-mentioned functions in combination with a program already recorded in the computer system.

Further, the base station device 3 in the above-described embodiment can also be realized as an aggregate (device group) composed of a plurality of devices. Each of the devices forming the device group may include some or all of the functions or function blocks of the base station device 3 according to the above-described embodiment. It suffices for the device group to have one type of each function or each functional block of the base station device 3. Further, the terminal device 1 according 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-described embodiment may be an EUTRAN (Evolved Universal Terrestrial Radio Access Network). Moreover, the base station apparatus 3 in the above-mentioned embodiment may have a part or all of the functions of the upper node with respect to the eNodeB.

Further, a part or all of the terminal device 1 and the base station device 3 in the above-described embodiments may be realized as an LSI which is typically an integrated circuit, or may be realized as a chip set. Each functional block of the terminal device 1 and the base station device 3 may be individually made into a chip, or a part or all of them may be integrated and made into a chip. Further, the method of circuit integration is not limited to LSI, and may be realized by a dedicated circuit or a general-purpose processor. In addition, when a technique for forming an integrated circuit that replaces LSI appears with the progress of semiconductor technology, it is possible to use an integrated circuit according to the technique.

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

Although the embodiment of the present invention has been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment, and includes design changes and the like within a range not departing from the gist of the present invention. Further, the present invention can be variously modified 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. Be done. Further, a configuration in which the elements described in each of the above embodiments and having the same effect are replaced with each other is also included.

1 (1A, 1B, 1C) Terminal device 3 Base station device 101 Upper layer processing unit 103 Control unit 105 Reception unit 107 Transmission unit 301 Upper layer processing unit 303 Control unit 305 Reception unit 307 Transmission unit 1011 Radio resource control unit 1012 Medium access Control layer processing unit 1013 Scheduling information interpretation unit 1015 SPS control unit 3011 Radio resource control unit 3012 Medium access control layer processing unit 3013 Scheduling unit 3015 SPS control unit

Claims (16)

Information of the upper layer that instructs the setting or release of the parameters of the upper layer, and a receiving unit that receives the uplink grant,
A medium access control layer processing unit that stores the uplink grant as a set grant, and determines whether the uplink HARQ operation is synchronous or asynchronous based on at least whether the upper layer parameter is set. Equipped with
The medium access control layer processing unit is set when the parameters of the upper layer have been previously set and when the information of the upper layer that indicates the release of the parameters of the upper layer has been received. A terminal device that clears the grant. The medium access control layer processing unit is set when the parameters of the upper layer are not (previously) set and the upper layer information indicating the setting of the parameters of the upper layer is received. The terminal device according to claim 1, which clears the grant. The medium access control layer processing unit is set when the parameters of the upper layer have been previously released and when the information of the upper layer instructing the setting of the parameters of the upper layer is received. The terminal device according to claim 1, which clears the grant. Information of the upper layer that instructs the setting or release of the parameters of the upper layer, and a transmitting unit that transmits the uplink grant stored by the terminal device as the set grant,
A medium access control layer processing unit that determines whether the uplink HARQ operation is synchronous or asynchronous based on at least whether the parameter of the upper layer is set for the terminal device,
The medium access control layer processing unit sets the upper layer parameter to the terminal device in advance (previously), and sets the upper layer information instructing the release of the upper layer parameter to the terminal device. A base station apparatus that considers that the set grant is cleared by the terminal apparatus when transmitted to the terminal apparatus. The medium access control layer processing unit, the upper layer parameters are not previously set to the terminal device (previously), and the upper layer information for instructing the setting of the upper layer parameters, the terminal The base station device according to claim 4, wherein the set grant is considered to be cleared by the terminal device when transmitted to the device. The medium access control layer processing unit, the upper layer parameters have been previously released in the terminal device (previously), and the upper layer information for instructing the setting of the upper layer parameters to the terminal device. The base station apparatus according to claim 4, wherein, when transmitted, the set grant is considered to be cleared by the terminal apparatus. A communication method used for a terminal device,
Receives upper layer information that instructs setting or release of upper layer parameters, and uplink grant,
Store the uplink grant as a set grant,
Determining whether uplink HARQ operation is synchronous or asynchronous based at least on whether the upper layer parameters are set,
A communication method for clearing the set grant when the upper layer parameter is previously set and the upper layer information indicating the release of the upper layer parameter is received. A communication method used for a base station device,
The upper layer information indicating the setting or release of the upper layer parameters, and transmits the uplink grant stored by the terminal device as the set grant,
Determining whether uplink HARQ operation is synchronous or asynchronous based at least on whether the upper layer parameters are configured for the terminal device;
If the upper layer parameters have been previously set for the terminal device and the upper layer information indicating the release of the upper layer parameters has been transmitted to the terminal device, the setting is performed. A communication method in which the grant is considered to be cleared by the terminal device. A receiver for receiving upper layer parameters,
A medium access control layer processing unit that determines whether to generate a MAC protocol data unit based on at least whether the upper layer parameter is set,
When the uplink HARQ operation is asynchronous, the medium access control layer processing unit determines whether to perform non-adaptive retransmission based on at least whether or not the upper layer parameter is set. .. The medium access control layer processing unit, when the uplink HARQ operation is synchronous, performs non-adaptive retransmission of a semi-persistently scheduled transport block regardless of whether or not the upper layer parameter is set. The terminal device according to claim 9, wherein the terminal device determines whether to execute. The medium access control layer processing unit is a grant in which the parameters of the upper layer are set and an uplink grant is set, and the MAC protocol data unit does not include the MAC service data unit, and the padding BSR is set. The terminal device according to claim 9, wherein the MAC protocol data unit is not generated when a MAC CE for a periodic BSR is included. A transmitter for transmitting upper layer parameters used by the terminal device to determine whether to generate a MAC protocol data unit;
A receiver for receiving non-adaptive retransmissions,
Determines whether non-adaptive retransmissions are performed by the terminal, based at least on whether the higher layer parameters are configured for the terminal when the uplink HARQ operation is asynchronous A base station apparatus comprising: a medium access control layer processing unit. The medium access control layer processing unit, when the uplink HARQ operation is synchronous, regardless of whether or not the upper layer parameter is set for the terminal device, the semi-persistently scheduled transport block. 13. The base station apparatus according to claim 12, wherein it determines whether non-adaptive retransmission of is performed by the terminal apparatus. The upper layer parameter is set for the terminal device, and the uplink grant is set, and the MAC protocol data unit does not include the MAC service data unit, and padding BSR or periodic The base station apparatus according to claim 12, wherein the MAC protocol data unit is not generated by the terminal apparatus when the MAC CE for BSR is included. A communication method used for a terminal device,
Receives upper layer parameters,
Determining whether to generate a MAC protocol data unit based at least on whether the upper layer parameter is set, and whether the upper layer parameter is set, if the uplink HARQ operation is asynchronous A communication method for determining whether to perform a non-adaptive retransmission based at least on the. A communication method used for a base station device,
Send upper layer parameters used by the terminal to determine whether to generate a MAC protocol data unit,
Receive non-adaptive retransmissions,
Determines whether non-adaptive retransmissions are performed by the terminal, based at least on whether the higher layer parameters are configured for the terminal when the uplink HARQ operation is asynchronous Communication method.

Images