JP6481988B2 - Integrated circuit - Google Patents

Description

  The present invention relates to an integrated circuit for controlling a mobile station based on a flexible TDD uplink / downlink configuration.

Long Term Evolution (LTE)

  Third generation mobile communication systems (3G) based on WCDMA® radio access technology are being deployed on a wide scale around the world. As the first step in enhancing or evolving and evolving this technology, high-speed downlink packet access (HSDPA) and enhanced uplink (also referred to as high-speed uplink packet access (HSUPA)) were introduced. Wireless access technologies that are extremely competitive have been provided.

  In order to meet the increasing demand from users and ensure competitiveness for new radio access technologies, 3GPP has introduced a new mobile communication system called Long Term Evolution (LTE). LTE is designed to provide the carrier required for high speed data and media transmission and high volume voice support over the next decade. The ability to provide high bit rates is an important strategy in LTE.

  The specifications of work items (WI) for LTE (Long Term Evolution) are E-UTRA (Evolved UMTS Terrestrial Radio Access (UTRA)) and E-UTRAN (Evolved UMTS Terrestrial Radio Access Network (UTRAN)). : Evolved UMTS Terrestrial Radio Access Network) and will eventually be released as Release 8 (LTE Release 8). The LTE system is a packet-based efficient radio access and radio access network that provides all IP-based functions with low latency and low cost. In LTE, multiple transmission bandwidths (eg, 1.4 MHz, 3.0 MHz, 5.0 MHz, 10.0 MHz, 15.0 MHz, etc.) are used to achieve flexible system deployment using a given spectrum. And 20.0 MHz). The downlink employs radio access based on OFDM (Orthogonal Frequency Division Multiplexing). Because such radio access is inherently less susceptible to multipath interference (MPI) due to its low symbol rate, uses cyclic prefix (CP), and supports various transmission bandwidth configurations Because it is possible. The uplink employs radio access based on SC-FDMA (Single-Carrier Frequency Division Multiple Access). This is because, given the limited transmission output of the user equipment (UE), priority is given to providing a wider coverage area than to improve the peak data rate. In LTE Release 8/9, a number of major packet radio access technologies (eg, MIMO (Multiple Input Multiple Output) channel transmission technology) are employed to achieve a highly efficient control signaling structure.

LTE architecture

  FIG. 1 shows the overall architecture of LTE, and FIG. 2 shows the architecture of E-UTRAN in more detail. E-UTRAN is composed of eNodeB, which terminates E-UTRA user plane (PDCP / RLC / MAC / PHY) and control plane (RRC) protocols for UE. eNodeB (eNB) consists of physical (PHY) layer, media access control (MAC) layer, radio link control (RLC) layer, and packet data control protocol (PDCP) layer (these layers are user plane header compression and encryption) Hosting). The eNB also provides a radio resource control (RRC) function corresponding to the control plane. eNB performs radio resource management, admission control, scheduling, negotiated uplink QoS (quality of service), cell information broadcast, user plane data and control plane data encryption / decryption, downlink / uplink It performs many functions such as compression / decompression of user plane packet headers. The plurality of eNodeBs are connected to each other by an X2 interface.

  In addition, a plurality of eNodeBs are configured by EPC (Evolved Packet Core) via the S1 interface, more specifically, MME (Mobility Management Entity) via S1-MME, and serving gateway ( SGW: Serving Gateway) The S1 interface supports a many-to-many relationship between the MME / serving gateway and the eNodeB. While the SGW routes and forwards user data packets, it functions as a mobility anchor for the user plane during handover between eNodeBs, and also an anchor for mobility between LTE and another 3GPP technology (S4 Terminates the interface and relays traffic between the 2G / 3G system and the PDN GW). The SGW terminates the downlink data path for idle user equipment and triggers paging when downlink data arrives for that user equipment. The SGW manages and stores user equipment contexts (eg, IP bearer service parameters, network internal routing information). In addition, the SGW performs replication of user traffic in case of lawful interception.

  The MME is the main control node of the LTE access network. The MME is responsible for idle mode user equipment tracking and paging procedures (including retransmissions). The MME participates in the bearer activation / deactivation process, and also selects the SGW of the user equipment at the first attach and at the intra-LTE handover with relocation of the core network (CN) node Also plays a role. The MME is responsible for authenticating the user (by interacting with the HSS). Non-Access Stratum (NAS) signaling is terminated at the MME, which is also responsible for generating a temporary ID and assigning it to the user equipment. The MME checks the authentication of the user equipment to enter the service provider's Public Land Mobile Network (PLMN) and enforces roaming restrictions on the user equipment. The MME is a termination point in the network in encryption / integrity protection of NAS signaling, and manages security keys. Lawful interception of signaling is also supported by the MME. In addition, the MME provides a control plane function for mobility between the LTE access network and the 2G / 3G access network and terminates the S3 interface from the SGSN. Furthermore, the MME terminates the S6a interface towards the home HSS for the roaming user equipment.

Component carrier structure in LTE (Release 8)

  The downlink component carrier of 3GPP LTE (release 8 or later) is divided into so-called subframes in the time-frequency domain. In 3GPP LTE (release 8 and later), as shown in FIG. 3, each subframe is divided into two downlink slots, and the first downlink slot is the control channel in the first few OFDM symbols. A region (PDCCH region) is included. Each subframe consists of a specific number of OFDM symbols in the time domain (12 or 14 OFDM symbols in 3GPP LTE (release 8 and later)), each of which covers the entire bandwidth of the component carrier. . Therefore, each OFDM symbol includes a plurality of modulation symbols transmitted on each of NDLRB × NRBsc subcarriers, as shown in FIG.

For example, when considering a multi-carrier communication system that employs, for example, OFDM used in 3GPP LTE (Long Term Evolution), the minimum unit of resources that can be allocated by the scheduler is one “resource block”. As illustrated in FIG. 4, the physical resource block (PRB) includes N ^DL _symb continuous OFDM symbols in the time domain (eg, 7 OFDM symbols) and N ^RB _sc in the frequency domain. Defined as consecutive subcarriers (eg, 12 subcarriers of component carrier). Therefore, in 3GPP LTE (Release 8), a physical resource block is composed of N ^DL _symb × N ^RB _sc resource elements, and corresponds to one slot in the time domain and 180 kHz in the frequency domain (for the downlink resource grid). For further details, see for example Section 6.2 of Non-Patent Document 1) (available on the 3GPP website and incorporated herein by reference).

A subframe consists of two slots, so there are 14 OFDM symbols in a subframe when a so-called “normal” CP (cyclic prefix) is used, so-called “extended” CP is used. When there are 12 OFDM symbols in a subframe. In technical terms, in the following, a time-frequency resource equal to the same N ^RB _sc consecutive subcarriers throughout the subframe is referred to as a “resource block pair” or, in the same sense, an “RB pair” or “PRB pair”. Called.

  The term “component carrier” means a combination of several resource blocks in the frequency domain. In future releases of LTE, the term “component carrier” will no longer be used. Instead, the term is changed to “cell”. “Cell” means a combination of downlink resources and optionally uplink resources. The linking between the carrier frequency of the downlink resource and the carrier frequency of the uplink resource is indicated in the system information transmitted on the downlink resource.

  Similar assumptions for the component carrier structure apply to subsequent releases.

Logical and transport channels

  The MAC layer provides a data transmission service to the RLC layer through a logical channel. The logical channel is either a control logical channel that carries control data such as RRC signaling or a traffic logical channel that carries user plane data. The broadcast control channel (BCCH), paging control channel (PCCH), common control channel (CCCH), multicast control channel (MCCH), and dedicated control channel (DCCH) are control logical channels. Dedicated traffic channels (DTCH) and multicast traffic channels (MTCH) are traffic logical channels.

  Data from the MAC layer is exchanged with the physical layer through a transport channel. Data is multiplexed into the transport channel according to the radio transmission scheme. Transport channels are classified as downlink or uplink as follows. Broadcast channel (BCH), downlink shared channel (DL-SCH), paging channel (PCH), and multicast channel (MCH) are downlink transport channels, whereas uplink shared channel (UL-SCH). ) And random access channel (RACH) are uplink transport channels.

  Multiplexing is performed between the logical channel and the transport channel in the downlink and uplink, respectively.

Layer 1 / Layer 2 (L1 / L2) control signaling

  Layer 1 / Layer 2 control signaling is used to inform scheduling users of user allocation status, transport format, and other data related information (eg, HARQ information, transmit power control (TPC) commands). Sent on the downlink along with the data. Layer 1 / Layer 2 control signaling is multiplexed with downlink data within a subframe (assuming user assignments can vary from subframe to subframe). Note that user allocation can also be performed on a TTI (transmission time interval) basis, in which case the TTI length is a multiple of a subframe. The TTI length can be constant for all users in the service area, can be different for each user, or can be dynamic for each user. Layer 1 / Layer 2 control signaling generally only needs to be transmitted once per TTI. Without loss of generality, the following assumes that TTI is equal to one subframe.

  Layer 1 / Layer 2 control signaling is transmitted on the physical downlink control channel (PDCCH). The PDCCH conveys a message as downlink control information (DCI), which most often includes resource allocation information and other control information for a group of mobile terminals or user equipment. In general, several PDCCHs can be transmitted in one subframe.

  Note that in 3GPP LTE, the assignment for uplink data transmission (also referred to as uplink scheduling grant or uplink resource assignment) is also transmitted on the PDCCH.

In general, the information (especially LTE (-A) Release 10) sent in the Layer 1 / Layer 2 control signaling for allocating uplink or downlink radio resources can be classified into the following items.
-User ID. Indicates the user to be assigned. This is typically included in the checksum by masking the CRC with the user ID.
-Resource allocation information. Indicates a resource (resource block (RB)) to which a user is allocated. Note that the number of RBs to which a user is assigned can be dynamic.
− Carrier indicator. Used when the control channel transmitted on the first carrier allocates resources related to the second carrier, i.e. resources on the second carrier or resources related to the second carrier.
A modulation and coding scheme that determines the modulation scheme and coding rate used;
-HARQ information such as New Data Indicator (NDI) and Redundant Version (RV), which is particularly useful when retransmitting data packets or parts thereof.
A power control command that adjusts the transmission power for transmission of allocated uplink data and control information.
-Reference signal information such as applied cyclic shift and orthogonal cover code index. Used to transmit or receive reference signals related to allocation.
-Uplink or downlink assignment index used to identify the order of assignment. It is particularly useful with TDD systems.
-Hopping information. For example, it indicates whether and how to apply resource hopping to increase frequency diversity.
-CSI request. Used to trigger transmission of channel state information in the allocated resource.
-Multi-cluster information. A flag used to indicate and control whether transmission occurs in one cluster (consecutive set of RBs) or multiple clusters (at least two non-contiguous sets of contiguous RBs). Multi-cluster allocation has been introduced from 3GPP LTE- (A) Release 10.

  Note that the above list is not complete, and depending on the DCI format used, not all of the above information items need to be present in each PDCCH transmission.

  Downlink control information is performed in several formats with different overall sizes and information contained in the fields. The various DCI formats currently defined in LTE are as follows and are described in Non-Patent Document 2 (available on the 3GPP website and incorporated herein by reference): 53.3 It is described in detail in section 1.1. For further details regarding the DCI format and the specific information transmitted in DCI, please refer to Technical Standards or Chapter 9.3 of Non-Patent Document 3 (incorporated herein by reference).

Format 0 : DCI format 0 is used to transmit a PUSCH resource grant that uses single antenna port transmission in uplink transmission mode 1 or 2.

Format 1 : DCI format 1 is used to transmit resource assignments for single codeword PDSCH transmissions (downlink transmission modes 1, 2, and 7).

Format 1A : DCI format 1A is used to compactly signal resource assignment for single codeword PDSCH transmission and to assign a dedicated preamble signature to the mobile terminal for contention free random access.

Format 1B : DCI format 1B is used to compactly signal resource allocation for PDSCH transmission using closed loop precoding in rank 1 transmission (downlink transmission mode 6). The transmitted information is the same as in format 1A, but an indicator of a precoding vector applied to PDSCH transmission is added.

Format 1C : DCI format 1C is used to transmit PDSCH assignments very compactly. When format 1C is used, PDSCH transmission is limited to the use of QPSK modulation. For example, it is used for signaling a paging message or a broadcast system information message.

Format 1D : DCI format 1D is used to compactly signal resource allocation for PDSCH transmission using multi-user MIMO. The information to be transmitted is the same as in format 1B, but instead of one bit of the precoding vector indicator, there is one bit indicating whether a power offset is applied to the data symbol. This function needs to indicate whether the transmission power is shared between the two UEs. In future versions of LTE, this may be extended for power sharing among more UEs.

Format 2 : DCI format 2 is used to transmit PDSCH resource assignments for closed-loop MIMO operation.

Format 2A : DCI format 2A is used to transmit PDSCH resource assignments for open-loop MIMO operation. The information to be transmitted is the same as in format 2, but if the eNodeB has two transmit antenna ports, there is no precoding information, and if there are four antenna ports, 2 bits are used to indicate the transmission rank. The point is different.

Format 2B : Introduced in Release 9, used to transmit PDSCH resource assignments for two-layer beamforming.

Format 2C : Introduced in Release 10, used to transmit PDSCH resource assignments for up to 8 layers of closed-loop single-user or multi-user MIMO operation.

Format 2D : Introduced in Release 11, used for transmission of up to 8 layers, mainly used for COMP (Cooperative Multipoint).

Formats 3 and 3A : DCI formats 3 and 3A are used to transmit PUCCH and PUSCH power control commands including 2-bit or 1-bit power adjustment values, respectively. These DCI formats contain individual power control commands for groups of UEs.

Format 4 : DCI format 4 is used for scheduling PUSCH using uplink transmission mode 2 closed loop spatial multiplexing transmission.

  The following table shows some overviews of DCI formats that can be used and typical number of bits, but for purposes of illustration, assume that the eNodeB has a system bandwidth of 50 RBs and four antennas. The number of bits shown in the right column includes the bits for a specific DCI CRC.

  Error detection is provided using a 16-bit CRC appended to the end of each PDCCH (ie, DCI) so that the UE can identify whether it has correctly received a PDCCH transmission. Furthermore, it is necessary for the UE to be able to identify the PDCCH intended for itself. This can theoretically be achieved by adding an identifier to the PDCCH payload, but it has been found that scrambling the CRC with “UE ID” is more efficient and can save additional overhead. . The CRC can be computed and scrambled as defined in detail in Section 5.3.3.2 “CRC attachment” of Non-Patent Document 2, which is incorporated herein by reference. The section describes a scheme in which error detection is provided for DCI transmission through cyclic redundancy check (CRC). A brief summary is given below.

  Calculate the CRC parity bits using the entire payload. The parity bit is calculated and added. If UE transmit antenna selection is not configured or not applicable, the CRC parity bit is scrambled with the corresponding RNTI after addition.

  Scrambling may further depend on the UE's selection of transmit antennas, as is apparent from Non-Patent Document 2. When the transmission antenna selection of the UE is set and applicable, the CRC parity bit is scrambled with the antenna selection mask and the corresponding RNTI after addition. In both cases, RNTI is involved in the scrambling operation, and for the sake of brevity and without loss of generality, in the description of the embodiments below, the CRC is simply scrambled with RNTI (and where applicable). Therefore, regardless of such a description, RNTI should be understood as yet another element in the scrambling process, such as an antenna selection mask.

  Correspondingly, the UE unscrambles the CRC by applying the “UE ID”, and if no CRC error is detected, the UE is reporting its control information for its own device. to decide. In the process of scrambling the CRC with an ID, the terms “mask” and “unmask” are also used.

  SI-RNTI (System Information Radio Network Temporary Identifier) can be used as the above-mentioned “UE ID” that can scramble the CRC of DCI, but SI-RNTI itself is “UE”. It is not an “ID” but an identifier associated with the type of information shown and transmitted, in this case system information. SI-RNTI is usually fixed in the specification and is therefore known in advance to all UEs.

  There are various types of RNTI that are used for different purposes. The following table is taken from Chapter 7.1 of Non-Patent Document 4 and outlines various 16-bit RNTIs and their usage.

Physical downlink control channel (PDCCH) and physical downlink shared channel (PDSCH)

  The physical downlink control channel (PDCCH) carries, for example, a scheduling grant that allocates resources for transmitting data on the downlink or uplink. A plurality of PDCCHs can be transmitted in one subframe.

The PDCCH to the user equipment is the first N ^PDCCH _symb OFDM symbols in the _subframe (usually 1, 2 or 3 OFDM symbols (indicated by PCFICH), 2 in exceptional cases 3 or 4 OFDM symbols (indicated by PCFICH)), which extend over the entire system bandwidth. The system bandwidth is generally equal to the cell or component carrier range. A region _{occupied by the} first N ^PDCCH _symb OFDM symbols in the time domain and N ^DL _RB × N ^RB _sc subcarriers in the frequency domain is also referred to as a PDCCH region or a control channel region. The remaining N ^PDSCH _symb = 2 * N ^DL _symb −N ^PDCCH _symb OFDM symbols in the time domain, spanning N ^DL _RB × N ^RB _sc subcarriers in the frequency domain, are referred to as PDSCH or shared channel regions (Described later).

  In the downlink grant (ie resource allocation) for the physical downlink shared channel (PDSCH), the PDCCH allocates PDSCH resources for (user) data in the same subframe. The PDCCH control channel region in a subframe consists of a series of CCEs, and the total number of CCEs in the control region of the subframe is distributed over the entire time-frequency control resource. Multiple CCEs can be combined to effectively reduce the coding rate of the control channel. CCEs are combined in a predetermined way that uses a tree structure to achieve different code rates.

  At the transport channel level, the information transmitted over the PDCCH is also referred to as layer 1 / layer 2 control signaling (see layer 1 / layer 2 control signaling above for details).

  There is a specific predefined timing relationship between the uplink resource allocation received in a subframe and the corresponding PUSCH uplink transmission. Details can be obtained in chapter 8.0 “UE procedure for transmitting the physical uplink shared channel” of Non-Patent Document 5, which is incorporated herein by reference.

  In particular, Table 8-2 of Non-Patent Document 5 reproduced in FIG. 7 defines a parameter k for TDD configurations 0 to 6, where k is a positive offset of an uplink resource allocation target received in a subframe. Indicates. For TDD configuration 0, there is an additional definition of timing for uplink subframes 3 and 8, but is omitted here for brevity. For example, the parameter k is 6 in subframe 1 of TDD configuration 1, which means that the allocation of uplink resources received in subframe 1 of TDD configuration 1 covers subframe 1 + 6 = 7 of TDD configuration 1 This means that the subframe 7 is actually an uplink subframe or the like.

Hybrid ARQ method

  A technique widely used for error detection and correction of an unreliable channel in a packet transmission system is called a hybrid automatic repeat request (HARQ). Hybrid ARQ is a combination of forward error correction (FEC) and ARQ.

  If an FEC-encoded packet is sent and the receiver cannot decode the packet correctly (errors are typically checked with a CRC (Cyclic Redundancy Check)), the receiver Request transmission. In general (and throughout this document), the transmission of additional information is referred to as a “(packet) retransmission”, but this retransmission does not necessarily mean transmitting the same encoded information; For example, it may mean transmission of additional redundant information).

  The following hybrid ARQ schemes are defined depending on the information comprising the transmission (generally code bits / symbols) and how the receiver processes the information.

  In the Type I HARQ method, when the receiver cannot correctly decode the packet, the information of the encoded packet is discarded and retransmission is requested. This means that every transmission is decoded one by one. In general, a retransmission contains exactly the same information (code bits / symbol) as the first transmission.

  In the Type II HARQ scheme, if the receiver cannot correctly decode the packet, retransmission is requested, and the receiver converts the information of the encoded packet (received with an error) into soft information (soft bits). / Symbol). This means that a soft buffer is required at the receiver. According to the same packet as the previous transmission, the retransmission may consist of exactly the same information, partly the same information, or not the same information (code bits / symbol). When the retransmission is received, the receiver combines the information stored in the soft buffer and the information received this time, and tries to decode the packet based on the combined information. (The receiver can also attempt to decode the transmissions individually, but generally combining the transmissions improves performance.) Combining the transmissions is called so-called “soft-combining” A plurality of received code bits / symbols are likelihood combined, and a single received code bit / symbol is code combined. Commonly used soft combining methods are Maximum Ratio Combining (MRC) and log-likelihood-ratio (LLR) combining of received modulation symbols (LLR combining is performed on code bits). Only valid).

  The Type II scheme is higher in performance than the Type I scheme because the probability of correctly receiving a packet increases with each received retransmission. This increase comes at the cost of requiring a soft buffer for hybrid ARQ at the receiver. Using this scheme, dynamic link adaptation can be performed by controlling the amount of information retransmitted. For example, if the receiver detects that the decoding is “nearly” successful, the receiver will request to send only a small amount of information (a smaller number of code bits / symbol than the previous transmission) at the next retransmission. be able to. In this case, there is a possibility that the packet cannot theoretically be decoded correctly only by considering the retransmission itself (retransmission that cannot be self-decoded).

  The Type III HARQ scheme can be considered a subset of the Type II scheme. In addition to Type II requirements, each transmission of Type III must be capable of self-decoding.

  Synchronous HARQ means that HARQ block retransmissions occur at predefined periodic intervals. Thus, explicit signaling to inform the receiver of the retransmission schedule is not necessary.

  Asynchronous HARQ provides flexibility in scheduling retransmissions based on air interface conditions. In this case, some identification of the HARQ process needs to be signaled to allow correct synthesis and protocol operation. In 3GPP LTE system, HARQ operation with 8 processes is used. The HARQ protocol operation for transmitting downlink data may be similar to HSDPA or may be exactly the same as HSDPA.

  In uplink HARQ protocol operation, there are two different options for the retransmission scheduling method. The retransmissions are either “scheduled” with a NACK (also called synchronous non-adaptive retransmissions), or are explicitly scheduled by the network by sending PDCCH (also called synchronous adaptive retransmissions). Or one. For synchronous non-adaptive retransmissions, retransmission uses the same parameters as the previous uplink transmission. That is, retransmissions are signaled on the same physical channel resource, each using the same modulation scheme / transport format.

  Since synchronous adaptive retransmission is explicitly scheduled via PDCCH, it is possible for the eNodeB to change certain parameters for retransmission. The retransmissions can be scheduled with different frequency resources to avoid fragmentation in the uplink, for example, or the eNodeB changes the modulation scheme or informs the user equipment about the redundant version to use for the retransmission. You can also. Note that HARQ feedback (ACK / NACK) and PDCCH signaling are performed at the same timing. Thus, the user equipment is whether synchronous non-adaptive retransmission is triggered (ie, only NACK is received) or whether the eNodeB is requesting synchronous adaptive retransmission (ie, PDCCH is signaled) Whether you only need to check once.

HARQ and control signaling for TDD operation

  As described above, when transmitting downlink or uplink data by HARQ, a reception notification (ACK or negative ACK) is sent in the opposite direction to indicate whether the packet reception is successful or unsuccessful. Need to be notified.

  For FDD operation, a reception notification indicator related to data transmission in subframe n is transmitted in the opposite direction at subframe n + 4, and there is a pair between the moment the transport is transmitted and the corresponding reception notification. There is one synchronized mapping. On the other hand, for TDD operation, subframes are specified per cell as uplink or downlink or special (see next chapter), so that resource grant, data transmission, acknowledgment and retransmission Limit the time that can be sent in their own direction. Therefore, the LTE design of TDD supports the transmission of grouped ACK / NACK to convey multiple acknowledgments in one subframe.

  In uplink HARQ, it is not a problem to send a plurality of reception notifications (in one downlink subframe) through a physical hybrid ARQ indicator channel (PHICH). This is because when viewed from the eNodeB, this is not much different from the case where one reception notification is simultaneously sent to a plurality of UEs. However, for downlink HARQ, if the asymmetry is biased towards the downlink, the FDD uplink control signaling (PUCCH) format is insufficient to convey additional ACK / NACK information. Each TDD subframe configuration in LTE (see below and FIG. 5) has its own such mapping predefined between downlink and uplink subframes for HARQ, This mapping is designed to achieve a balance between minimizing the acknowledgment delay and distributing ACK / NACK evenly among the available uplink subframes. Further details are provided in Section 7.3 of Non-Patent Document 5 and are incorporated herein by reference.

  TDD HARQ-ACK feedback procedure is described in Section 10.1.3 of Non-Patent Document 5, which is incorporated herein by reference.

  Table 10.1.3-1 of Non-Patent Document 5 reproduced in FIG. 6 shows an index of the downlink correspondence set of the ACK / NACK / DTX response for the subframe of the radio frame, and corresponds to the TDD configuration. The number in the frame to indicate the negative offset of the subframe in which the HARQ feedback for that subframe is transmitted. For example, subframe 9 of TDD configuration 0 transmits HARQ feedback of subframe 9-4 = 5, and subframe 5 of TDD configuration 0 is actually a downlink subframe (see FIG. 5).

  In HARQ operation, the eNB may send a different encoded version than the original TB upon retransmission, so the UE uses incremental redundancy (IR) combining [8] to increase the combining gain. In addition, additional coding gains can be obtained. However, in an actual system, the eNB transmits a TB to one specific UE in one resource segment, but the UE may not be able to detect data transmission due to loss of DL control information. In that case, systematic data is not available at the UE, so IR combining has a very poor ability to decode retransmissions. To alleviate this problem, the UE should feed back the third state, ie discontinuous transmission (DTX) feedback, to inform that the TB is not detected in the associated resource segment (this Is different from NACK informing the decoding failure).

Time division duplex: TDD

  LTE is a frequency division duplex (FDD) mode and time division duplex (TDD) in a harmonized framework designed to support the evolution of TD-SCDMA (Time Division Synchronous Code Division Multiple Access). Can operate in mode. In TDD, uplink transmission and downlink transmission are separated in the time domain, but the frequency remains the same.

  The term “duplex” means two-way communication between two devices and is distinguished from one-way communication. In the bi-directional case, transmission over the link in each direction can occur simultaneously (full duplex) or alternate (half duplex).

  For TDD in the unpaired radio spectrum, the basic structure of resource blocks and resource elements is shown in FIG. 4, but only a subset of the subframes of the radio frame are available for downlink transmission. . The remaining subframes are used for uplink transmission or used for special subframes. Special subframes are important to advance the timing of uplink transmissions and ensure that the signals transmitted from each UE (ie, uplink) reach the eNodeB almost simultaneously. Because signal propagation delay is related to the distance between the transmitter and receiver (ignoring reflections and other similar effects), this means that signals transmitted from UEs near the eNodeB are far from the eNodeB. This means that the travel time is shorter than the signal transmitted from the UE. To arrive at the same time, far UEs must send signals earlier than near UEs, which is solved by the so-called “timing advance” procedure of the 3GPP system.

  In TDD, this results in an additional situation where transmission and reception occur on the same carrier frequency, ie the downlink and uplink need to be duplexed in the time domain. UEs far from the eNodeB need to start uplink transmission earlier than near UEs, but conversely, downlink signals are received earlier to UEs farther than far UEs. A guard time is defined in the special subframe so that the circuit can be switched from DL reception to UL transmission. To further address the timing advance problem, the guard time of the far UE needs to be longer than the near UE.

  In 3GPP LTE Release 8 and later, this TDD structure is known as “Frame Structure Type 2”, and seven different uplink-downlink configurations have been defined, and these configurations allow for various downlink-uplinks. Ratios and switching cycles are possible. FIG. 5 shows a table of seven different TDD uplink-downlink configurations (numbers 0-6), where “D” means downlink subframe and “U” means uplink subframe. This means that “S” means a special subframe. As can be seen from the table, the seven available TDD uplink-downlink configurations can provide 40% -90% of the downlink subframes (a portion of the special subframe is available for downlink transmission). Therefore, special subframes are regarded as downlink subframes for brevity).

  FIG. 5 shows frame structure type 2 especially in the case of a switching point periodicity of 5 ms (ie TDD configurations 0, 1, 2, 6).

  FIG. 8 shows a radio frame that is 10 ms long and two corresponding half-frames that are each 5 ms. The radio frame is composed of 10 subframes of 1 ms each, and each subframe has an uplink, a downlink, as defined in one of the uplink-downlink configurations according to the table of FIG. Each type of link or special is assigned.

As can be understood from FIG. 5, subframe # 1 is always a special subframe, and subframe # 6 is a special subframe in the case of TDD configurations 0, 1, 2, and 6, and TDD configurations 3 and 4 are used. , 5 is a downlink subframe. The special subframe includes three fields: DwPTS (downlink pilot time slot), GP (guard period), and UpPTS (uplink pilot time slot). The following table shows information about special subframes, in particular DwPTS (downlink pilot time slot), as a multiple of the sample time T _s = (1/30720) ms as defined in 3GPP LTE Release 11. The lengths of GP (guard period) and UpPTS (uplink pilot time slot) are shown.

  The TDD configuration applied in the system includes a number of operations performed at mobile stations and base stations, such as radio resource management (RRM) measurement, channel state information (CSI) measurement, channel estimation, PDCCH detection, HARQ timing, etc. Affect.

  In particular, the user equipment knows about the TDD configuration in its current cell by reading the system information, i.e. subframe monitoring for measurement, subframe monitoring for CSI measurement and reporting, channel estimation. Recognize subframes to be monitored for time domain filtering, subframes to be monitored for PDCCH detection, or subframes to be monitored for UL / DL ACK / NACK feedback.

Disadvantages of current semi-static TDD uplink / downlink configuration scheme

  The current mechanism for adapting the UL-DL assignment is based on a system information acquisition procedure or a system information change procedure, which depends on the specific UL-DL TDD, depending on the TDD configuration parameters in the SIB, in this case SIB1. The configuration is shown (see section 8.1.1 of Non-Patent Document 6 for details on broadcasting system information, which is incorporated herein by reference).

  In the system information change procedure specified in LTE Release 8, the supported time scale for TDD UL / DL reconfiguration is 640 ms or more every time. When reusing ETWS (Earthquake Tsunami Warning System), the supported time scale for UL-DL TDD reconfiguration is over 320ms every depending on the default paging cycle that is set.

  Nevertheless, the semi-static allocation of TDD UL / DL configurations may or may not reflect instantaneous traffic conditions. The system information change procedure is too time consuming for dynamic TDD UL / DL reconfiguration if the traffic situation changes rapidly from uplink dominant traffic situation to downlink dominant traffic situation. As such, semi-static TDD UL / DL reconfiguration takes too long to maximize subframe utilization for instantaneous traffic conditions.

  In this regard, dynamic TDD UL / DL reconfiguration is widely considered in the context of LTE Release 12. Dynamic TDD UL / DL reconfiguration is expected to adapt the TDD UL / DL configuration to current traffic demands, for example, mitigating interference in uplink or downlink communications and communications with neighboring cells Therefore, it is expected to dynamically generate more downlink subframes to increase the downlink bandwidth and to dynamically generate more blank uplink subframes.

  In particular, LTE Release 12 is expected to support explicit signaling for dynamic TDD UL / DL reconfiguration. To that end, various signaling mechanisms are currently under consideration. Such a signaling mechanism allows information about TDD UL / DL reconfiguration to be instantaneously distributed within the communication system and also allows the mobile / base station to reconfigure the TDD UL / DL configuration without delay. To.

  It has been found that the currently used RRC signaling mechanism cannot guarantee the short TDD UL / DL reconfiguration interval needed to meet the demand for dynamic TDD UL / DL reconfiguration. In this regard, it is currently expected that a DCI signaling mechanism will be defined to allow dynamic TDD UL / DL reconfiguration. It is assumed that the reconstruction is effective over at least one radio frame (ie 10 ms).

  Due to the system constraints defined above, dynamic TDD UL / DL reconfiguration is not only the timing relationship between DCI and PUSCH defined for each TDD configuration, but also the timing between PDSCH and HARQ-ACK. You must overcome inconsistencies between relationships.

  As already explained, for each of TDD configurations 0-6, the timing between uplink resource allocation (eg UL grant) in DCI format 0/4 message and target PUSCH transmission in the corresponding uplink subframe. A relationship is defined. Specifically, the timing relationship between DCI and PUSCH enables scheduling of target PUSCH transmissions that overlap radio frame boundaries. In other words, PUSCH transmission and related DCI transmission can be performed in different radio frames. For example, according to TDD configuration 6, PUSCH transmission of subframe 2 of a certain radio frame relates to DCI transmission performed in the previous radio frame.

  Similarly, each TDD configuration 0-6 defines a timing relationship between one or more PDSCH transmissions and one or more subsequent hybrid ARQ-ACK transmissions. Even in the timing relationship between PDSCH and HARQ-ACK, HARQ-ACK transmission overlapping radio frame boundaries can be performed. In other words, HARQ-ACK transmission and related PDSCH transmission can be performed in different radio frames. For example, according to TDD configuration 5, HARQ-ACK transmission of subframe 2 of a certain radio frame is related to PDSCH transmission performed in two radio frames preceding it.

  In this regard, in TDD UL / DL reconfiguration between subsequent subframes, even if the timing relationship between the corresponding DCI and PUSCH is applied, the resources of all supported uplink subframes are not allocated continuously. Can not. Such an uplink resource allocation inconsistency is illustrated below, but in this case, the UL grant is in the DCI transmission that was transmitted before TDD reconfiguration took effect and the PUSCH transmission related to that DCI transmission. Are scheduled after TDD reconstruction is enabled.

  As an example, a TDD UL / DL reconfiguration from TDD configuration 3 to TDD configuration 6 is shown in FIG. 9A. For each of TDD configuration 3 and TDD configuration 6, the timing relationship between DCI and PUSCH is indicated by a dashed arrow. Accordingly, in order to allocate PUSCH transmission (ie, uplink transmission) to subframes supporting uplink transmission, DCI transmission related to each PUSCH transmission is indicated as a starting point of a chain line arrow.

  However, since the TDD UL / DL reconfiguration from the TDD configuration 3 to the TDD configuration 6 is performed, PUSCH transmission using a subframe having an index 24 is not possible. In particular, the TDD configuration 6 is used after the TDD UL / DL reconfiguration is enabled (that is, after the subframe of the index 20). In the timing relationship between the DCI and the PUSCH of the TDD configuration 6, the result is as follows. As a result, DCI transmission in which PUSCH transmission can be performed in the subframe of index 24 is not possible. In FIG. 9A, this can be understood by the absence of an arrow ending with PUSCH in subframe 24.

  For example, assume that PUSCH transmission related to DCI transmission before TDD UL / DL reconfiguration is performed after TDD UL / DL reconfiguration as shown in PUSCH transmission of subframes with indexes 22 and 23 As a result, there is no possibility of DCI transmission where PUSCH transmission is scheduled in the subframe of index 24.

  FIG. 10 shows another example of TDD UL / DL reconfiguration from TDD configuration 0 to TDD configuration 6. Even in this example, there is no possibility of DCI transmission as a result of which the PUSCH transmission is scheduled in the subframe of index 24.

  Therefore, the uplink bandwidth cannot be used immediately after TDD UL / DL reconfiguration because the timing relationship between DCI and PUSCH is predefined for each TDD configuration.

  As a further example, a TDD UL / DL reconfiguration from TDD configuration 3 to TDD configuration 6 is also shown in FIG. 9B. For each of the TDD configuration 3 and the TDD configuration 6, the timing relationship between PDSCH and HARQ-ACK is indicated by a chain line arrow. Accordingly, for HARQ-ACK transmission in a subframe that supports uplink transmission, PDSCH transmission related to each HARQ-ACK transmission is indicated as a starting point of a chain line arrow.

  However, since it is a TDD UL / DL reconfiguration from TDD configuration 3 to TDD configuration 6, HARQ-ACK transmission for PDSCH transmission of subframes with indexes 11, 17, and 18 is not possible. In particular, the TDD configuration 6 is used after the TDD UL / DL reconfiguration is performed (that is, after the subframe of the index 20). In the timing relationship between the PDSCH and the HARQ-ACK in the TDD configuration 6 , HARQ-ACK transmission related to PDSCH transmission in subframes with indices 11, 17, and 18 cannot be performed.

  For example, as shown in HARQ-ACK transmission related to PDSCH transmission in subframes with indexes 15, 16, and 19, HADD-ACK transmission related to PDSCH transmission performed before TDD UL / DL reconfiguration is TDD. Even assuming that it is performed after UL / DL reconfiguration, there is no possibility of HARQ-ACK transmission that will notify the reception of PDSCH transmission in subframes with indexes 11, 17, and 18.

  Therefore, since the timing relationship between PDSCH and HARQ-ACK is predefined for each TDD configuration, the assigned hybrid ARQ function cannot be used immediately after TDD UL / DL reconfiguration.

  At the recent 3GPP LTE meeting, various techniques for TDD UL / DL reconstruction were considered. Specifically, separate reference configurations are defined for the timing relationship between DCI and PUSCH and the timing relationship between PDSCH and HARQ-ACK that must be applied continuously after TDD UL / DL reconfiguration. Proposed to do. As an example, despite the SIB1 TDD configuration being operated, the UE will continuously apply the timing relationship specified in the newly defined reference configuration.

  However, this method has the following drawbacks. First, an additional upper layer configuration is required. Second, the timing relationship of the reference configuration must be applied even when it is not needed (eg when it is no longer needed).

  In the exemplary case of SIB1 TDD configuration, this results in an unnecessarily long delay for some HARQ-ACK transmissions and an unnecessarily long delay between DCI and PUSCH transmissions due to some TDD configurations. , HARQ-ACK transmission is unnecessarily bundled or multiplexed into several PUCCH subframes.

3GPP TS 36.211, "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and Modulation (Release 8)" 3GPP TS 36.212, "Multiplexing and channel coding" LTE-The UMTS Long Term Evolution-From Theory to Practice, Edited by Stefanie Sesia, Issam Toufik, Matthew Baker 3GPP 36.321 TS 36.213 v11.1.0 "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures (Release 11)" 3GPP TS 25.331, "Radio Resource Control (RRC)", version 6.7.0

  One object of the present invention is to provide an improved time division duplex reconfiguration operation that solves the problems of the prior art described above.

  This object is solved by the subject matter of the independent claims. Advantageous embodiments are the subject matter of the dependent claims.

  Various embodiments of the present invention differ in TDD UL / DL reconfiguration from the TDD radio frame configuration in terms of the timing relationship between DCI and PUSCH and / or the timing relationship between PDSCH and HARQ-ACK. Based on the concept that it should be applied in form (ie individually). The distinction between the TDD radio frame configuration and the timing relationship is performed only during a short period before and / or after the reconfiguration becomes effective.

  In particular, a predefined TDD radio frame configuration or TDD configuration allows a subframe reservation in a radio frame to be a downlink (abbreviated “D”) subframe, an uplink (abbreviated “U”) subframe, or It is defined as a special (abbreviated “S”) subframe. In this regard, when performing TDD UL / DL reconfiguration, the source TDD configuration defines the reservation of subframes before reconfiguration is enabled, and the target TDD configuration is the subframe after reconfiguration is enabled. Define frame reservation.

  Here, the reservation for the downlink or uplink serves only to indicate the transmission / reception direction (ie, downlink transmitted from the base station to the mobile station, uplink transmitted from the mobile station to the base station), and It is important to note that such transmissions (eg, PDSCH corresponding to D subframes or PUSCH corresponding to U subframes) are not necessarily actually performed. In this regard, uplink transmission can be performed only in the U subframe (or UpPTS portion of the S subframe), but not all U (or UpPTS portion of S) subframes carry the uplink transmission. Similarly, downlink transmission can occur in only the D subframe (or DwPTS portion of the S subframe), but not all D (or DwPTS portions of S) subframes carry downlink transmission.

  As an example, when performing TDD UL / DL reconfiguration from source TDD configuration 3 to target TDD configuration 6, source TDD configuration 3 defines the reservation of subframes in the radio frame before the reconfiguration becomes valid Then, the target TDD configuration 6 defines the reservation of subframes in the reconfigured radio frame. In this regard, in the TDD communication method, before the reconfiguration is enabled, the TDD configuration pattern “D, S, U, U, U, D, D, D, D, D” is used to enable the reconfiguration. After that, the TDD configuration pattern “D, S, U, U, U, D, S, U, U, D” is used.

  In accordance with the present invention, the timing relationship between DCI and PUSCH and / or the timing relationship between PDSCH and HARQ-ACK may be determined during a period of time before and / or after TDD UL / DL reconfiguration is enabled. It is applied differently than the target TDD configuration. In other words, although each source / target TDD configuration defines a timing relationship between DCI and PUSCH and / or a timing relationship between PDSCH and HARQ-ACK, the present invention enables TDD UL / DL reconfiguration. This provisional rule is broken only for a short period before and / or after.

  In particular, the term “timing relationship between DCI and PUSCH” defines when (ie in which subframe) PUSCH transmission related to DCI transmission must be performed. In particular, since a PUSCH transmission requires a UL grant preceding it, a DCI transmission involving PUSCH transmission is essentially a DCI transmission that carries the UL grant. In other words, in LTE Release 11, the corresponding DCI transmission is format 0/4.

  Similarly, the term “timing relationship between PDSCH and HARQ-ACK” defines when (ie in which subframe) HARQ-ACK transmission related to PDSCH transmission should be performed. In the context of the present invention, the term “HARQ-ACK transmission” means transmission of ACK / NACK / DTX information related to a certain PDSCH transmission. In this regard, in the following description, if HARQ-ACK transmission is not performed in subframe O related to PDSCH transmission in subframe P, HARQ-ACK transmission that may be performed in subframe O is performed in PDSCH. It should be interpreted to mean that it does not include ACK / NACK / DTX information related to transmission P. In other words, HARQ-ACK transmission may be performed in subframe O for PDSCH transmission in subframes other than subframe P.

  According to the present invention, during TDD UL / DL reconfiguration, the timing relationship related to DCI and PUSCH and / or between PDSCH and HARQ-ACK, respectively, predefined for TDD configuration, can be In order to improve utilization and / or to enable the hybrid ARQ function, it is applied differently from the TDD radio frame configuration.

  According to a first aspect of the invention, communication between a mobile station and a base station in a communication system is defined with improved TDD UL / DL reconfiguration. Communication is reconfigured from the source TDD configuration to the target TDD configuration.

  The source TDD configuration is one of a plurality of preset TDD configurations. For example, the source TDD configuration is one of a subset of TDD configurations 1-6, and the plurality of TDD configurations include TDD configurations 0-6. The target TDD configuration is an arbitrary one of a plurality of TDD configurations set in advance, and is, for example, any one of TDD configurations 0 to 6.

  When the communication between the mobile station and the base station is to be reconfigured for a predetermined subframe N at the beginning of the radio frame, the subframes prior to the subframe N for which the reconfiguration is valid are based on the source TDD configuration. In contrast, the subframes after the subframe N are set based on the target TDD configuration.

  Also, if the mobile station detects one or more downlink control information (DCI) transmissions that carry UL grants, the mobile station responds to the detected DCI transmissions according to the following scheme: Physical uplink shared channel (PUSCH) transmission is performed.

  The mobile station applies the source TDD configuration to PUSCH transmissions related to DCI transmissions received by the mobile station up to subframe N-6 including subframe N-6. Specifically, the mobile station determines the source TDD for one or more PUSCH transmissions scheduled in response to one or more DCI transmissions carrying each UL grant received during those subframes. Apply the timing relationship defined in the configuration to determine when that one or more PUSCH transmissions will occur.

  For PUSCH transmission related to DCI transmission received by the mobile station between subframe N-5 and subframe N-1 (including subframe N-5 and subframe N-1), the mobile station Apply the (ie predefined) TDD configuration. In particular, the mobile station may include intermediate transmissions for one or more PUSCH transmissions scheduled in response to one or more DCI transmissions carrying respective UL grants received during those subframes. Apply the timing relationship defined in the TDD configuration (ie, predefined) to determine when one or more PUSCH transmissions will occur.

  For PUSCH transmissions related to DCI transmissions received by the mobile station after subframe N, the mobile station applies the target TDD configuration. Specifically, the mobile station may send a target TDD for one or more PUSCH transmissions scheduled in response to one or more DCI transmissions carrying each UL grant received during those subframes. Apply the timing relationship defined in the configuration to determine when one or more PUSCH transmissions will occur.

  The intermediate (ie, predefined) TDD configuration is one of a plurality of preset TDD configurations, for example, any one of TDD configurations 0-6.

  In particular, by applying an intermediate (ie predefined) TDD configuration to the PUSCH transmission related to the DCI transmission just before the TDD UL / DL reconfiguration (and thus the target TDD configuration) becomes valid, Uplink bandwidth utilization can be improved.

  According to a second aspect of the present invention, communication between a mobile station and a base station in a communication system is specified using an improved TDD UL / DL reconfiguration different from the first aspect. Communication is reconfigured from the source TDD configuration to the target TDD configuration.

  The source TDD configuration is a preset one of a plurality of preset TDD configurations. For example, the source TDD configuration is TDD configuration 0. The target TDD configuration is any one of a plurality of TDD configurations set in advance, for example, any one of TDD configurations 0 to 6.

  When the communication between the mobile station and the base station is to be reconfigured for a predetermined subframe N at the beginning of the subframe, the radio frames before the subframe N for which the reconfiguration is valid are based on the source TDD configuration. In contrast, the radio frames after subframe N are set based on the target TDD configuration.

  Further, if the mobile station detects one or more downlink control information (DCI) transmissions that carry UL grants, the mobile station responds to the detected DCI transmissions according to the following scheme: Uplink shared channel (PUSCH) transmission is performed.

  For PUSCH transmissions related to DCI transmissions received by the mobile station (including subframe N) by subframe N, the mobile station applies the source TDD configuration. Specifically, the mobile station may receive source TDD for one or more PUSCH transmissions scheduled in response to one or more DCI transmissions carrying each UL grant received during those subframes. Apply timing relationships defined in the configuration.

  For PUSCH transmission related to DCI transmission received by the mobile station after subframe N + 1, the mobile station applies the target TDD configuration. Specifically, the mobile station may send a target TDD for one or more PUSCH transmissions scheduled in response to one or more DCI transmissions carrying each UL grant received during those subframes. Apply timing relationships defined in the configuration.

  In particular, by applying the target TDD configuration to the PUSCH transmission related to the DCI transmission received immediately after TDD UL / DL reconfiguration is enabled (ie subframe N), the uplink bandwidth in the communication system Use can be improved.

  According to a third aspect of the invention, communication between a mobile station and a base station in a communication system is specified using another improved TDD UL / DL reconfiguration. Communication is reconfigured from the source TDD configuration to the target TDD configuration.

  The source and target uplink / downlink configurations are TDD configurations of a plurality of TDD configurations. For example, the source and target TDD configurations are any one of a plurality of preset TDD configurations 0-6.

  When the communication between the mobile station and the base station is to be reconfigured for a predetermined subframe N at the beginning of the subframe, the radio frames before the subframe N for which the reconfiguration is valid are based on the source TDD configuration. In contrast, the radio frames after subframe N are set based on the target TDD configuration.

  Further, when the mobile station performs hybrid ARQ-ACK transmission in response to physical downlink shared channel (PDSCH) transmission, the mobile station performs HARQ-ACK transmission according to the following scheme.

  For the hybrid ARQ-ACK transmission transmitted from the mobile station up to subframe N-1 (including subframe N-1), the mobile station applies the source TDD configuration. Specifically, the mobile station is not responsible for one or more HARQ-ACK transmissions transmitted during those subframes in response to one or more PDSCH transmissions previously received by the mobile station. Apply the timing relationship defined in the source TDD configuration.

  For hybrid ARQ-ACK transmissions sent from the mobile station during subframes N + 1 to N + 12, the mobile station applies another intermediate (ie, predefined) TDD configuration. Specifically, the mobile station is not responsible for one or more HARQ-ACK transmissions transmitted during those subframes in response to one or more PDSCH transmissions previously received by the mobile station. Apply the timing relationship defined in the other intermediate (ie predefined) TDD configuration. The other intermediate TDD configuration is one of a plurality of TDD configurations.

  For the hybrid ARQ-ACK transmission sent from the mobile station after subframe N + 13, the mobile station applies the target TDD configuration. Specifically, the mobile station may, in those subframes, send one or more HARQ-ACK transmissions in response to one or more PDSCH transmissions previously received by the mobile station to target Apply the timing relationship defined in the TDD configuration.

  In particular, by applying another intermediate (ie pre-defined) TDD configuration to the HARQ-ACK transmission sent / received immediately after TDD UL / DL reconfiguration is enabled (ie subframe N), The hybrid ARQ function can be used continuously.

  According to a first embodiment according to the first aspect of the present invention, a method for communicating between a mobile station and a base station in a communication system is proposed. Communication is reconfigured from a source uplink / downlink configuration to a target uplink / downlink configuration. The source uplink / downlink configuration is one of a subset of the multiple uplink / downlink configurations, and the target uplink / downlink configuration is any of the multiple uplink / downlink configurations One. Multiple uplink / downlink configurations are pre-configured for time division duplex (TDD) communication. When reconfiguring communication for a predetermined subframe N at the head of the radio frame, the communication system responds to transmission of downlink control information (DCI) by subframe N-6 including subframe N-6. A source uplink / downlink configuration is applied to PUSCH transmissions related to received DCI transmissions, and PUSCH transmissions related to DCI transmissions received during subframes N-5 to N-1 are predefined. Physical uplink shared channel (PUSCH) so that the applied uplink / downlink configuration is applied and the target uplink / downlink configuration is applied to PUSCH transmissions related to DCI transmissions received after subframe N Transmit, and the predefined uplink / downlink configuration is the multiple uplink / downlink It is one of the down link configuration.

  According to a more detailed embodiment of this method, the predefined uplink / downlink configuration is different from the source uplink / downlink configuration.

  According to another more detailed embodiment of this method, the multiple uplink / downlink configurations are uplink / downlink configurations 0-6 and the source uplink / downlink configuration is uplink / downlink configuration 1 The predefined uplink / downlink configuration is the uplink / downlink configuration 6.

  According to a second embodiment according to the second aspect of the present invention, a method for communicating between a mobile station and a base station in a communication system is proposed. Communication is reconfigured from a source uplink / downlink configuration to a target uplink / downlink configuration. The source uplink / downlink configuration is a predefined one of multiple uplink / downlink configurations, and the target uplink / downlink configuration is any of the multiple uplink / downlink configurations It is one of. Multiple uplink / downlink configurations are pre-configured for time division duplex (TDD) communication. When reconfiguring communication for a predetermined subframe N at the beginning of a radio frame, the communication system receives DCI received by subframe N including subframe N in response to downlink control information (DCI) transmission. Physically, the source uplink / downlink configuration is applied to PUSCH transmissions related to transmission, and the target uplink / downlink configuration is applied to PUSCH transmissions related to DCI transmission received after subframe N + 1. Uplink shared channel (PUSCH) transmission is performed.

  According to a more detailed embodiment of this method, the multiple uplink / downlink configurations are uplink / downlink configurations 0-6 and the source uplink / downlink configuration is uplink / downlink configuration 0.

  According to another more detailed embodiment of the method, each of a plurality of uplink / downlink configurations determines a timing offset between the DCI transmission and the corresponding PUSCH transmission.

  According to yet another more detailed embodiment of this method, the source uplink / downlink configuration is in which subframes are reserved for downlink transmission up to subframe N-1 including subframe N-1. Or indicates a special subframe that supports both downlink and uplink transmissions, and the target uplink / downlink configuration is for subframe N and beyond, Indicates whether the subframe is reserved for downlink transmission, reserved for uplink transmission, or a special subframe that supports both downlink and uplink transmissions.

  According to yet another more detailed embodiment of this method, information is distributed within the communication system indicating that communication between the mobile station and the base station should be reconfigured, and the information is subframe N-14. In the case of distribution within an interval from the subsequent to the subframe N-5 including the subframe N-5, communication is reconfigured for a predetermined subframe N by the distribution of the information, and N is at the head of the radio frame. It is a subframe.

  According to a third embodiment according to the third aspect of the present invention, a method for communicating between a mobile station and a base station in a communication system is proposed. Communication is reconfigured from a source uplink / downlink configuration to a target uplink / downlink configuration. The source and target uplink / downlink configurations are uplink / downlink configurations of a plurality of uplink / downlink configurations. Multiple uplink / downlink configurations are pre-configured for time division duplex (TDD) communication. When reconfiguring communication for a predetermined subframe N at the beginning of a radio frame, the communication system responds to physical downlink shared channel (PDSCH) transmission up to subframe N-1 including subframe N-1. The source uplink / downlink configuration is applied to the hybrid ARQ-ACK transmissions of the same, and another predefined uplink / downlink configuration is applied to the hybrid ARQ-ACK transmissions between subframes N to N + 12. The hybrid ARQ-ACK transmission is performed such that the target uplink / downlink configuration is applied to the hybrid ARQ-ACK transmission after the subframe N + 13, and the other predefined uplink / downlink configuration is as described above. In one of multiple uplink / downlink configurations That.

  The third embodiment can be combined with the first or second embodiment.

  According to a more detailed embodiment of this method, another predefined uplink / downlink configuration is different from the target uplink / downlink configuration.

  According to another more detailed embodiment of this method, another predefined uplink / downlink configuration is uplink / downlink configuration 5.

  According to an even more detailed embodiment of this method, said another predefined uplink, wherein any of a plurality of uplink / downlink configurations is applied to hybrid ARQ-ACK transmission between subframes N to N + 12 / Information indicating whether it corresponds to the downlink configuration is distributed in the communication system.

  According to yet another more detailed embodiment of the method, each of a plurality of uplink / downlink configurations determines a timing offset between the PDSCH transmission and a corresponding hybrid ARQ-ACK transmission.

  According to an even more detailed embodiment of this method, in response to a physical downlink shared channel (PDSCH) transmission, where the source uplink / downlink configuration is applied, the source uplink / downlink configuration is: If hybrid ARQ-ACK transmission up to subframe N-1 including subframe N-1 is defined, and the hybrid ARQ-ACK transmission is related to the PDSCH transmission, and the other predefined uplink / downlink If a link configuration is applied, the other predefined uplink / downlink configuration defines a hybrid ARQ-ACK transmission between subframes N to N + 12, and the hybrid ARQ-ACK transmission is the PDSCH. In the case of transmission, the mobile station Or perform only Hybrid ARQ-ACK transmission to subframe N-1 containing, or, the mobile station performs only Hybrid ARQ-ACK transmission between subframe N to N + 12.

  According to yet another more detailed embodiment of the method, said another predefined uplink / downlink configuration is applied, and said another predefined uplink / downlink configuration is an uplink Define hybrid ARQ-ACK transmission between subframes N to N + 12 for at least one subframe configured to support transmission only, wherein the at least one subframe includes subframe N-11 to subframe N If the mobile station is within the interval up to subframe N-1 including −1, the mobile station may only perform hybrid ARQ− related to subframes configured to support downlink transmission during subframes N to N + 12. The mobile station performs ACK transmission or the mobile station transmits the at least one subframe. Indicating that Uplink not related only to the support and PDSCH Send performs hybrid ARQ-ACK transmission containing predefined information of the at least one sub-frame is configured to support only the uplink transmission.

  Furthermore, a mobile station that communicates with a base station in a communication system is proposed for the first embodiment. Communication is reconfigured from a source uplink / downlink configuration to a target uplink / downlink configuration. The source uplink / downlink configuration is one of a subset of the multiple uplink / downlink configurations, and the target uplink / downlink configuration is any of the multiple uplink / downlink configurations One. Multiple uplink / downlink configurations are pre-configured for time division duplex (TDD) communication. When reconfiguring communication for a predetermined subframe N at the head of the radio frame, the mobile station responds to downlink control information (DCI) transmission until the subframe N-6 including the subframe N-6. A source uplink / downlink configuration is applied to PUSCH transmissions related to received DCI transmissions, and predefined for PUSCH transmissions related to DCI transmissions received during subframes N-5 to N-1. Physical uplink shared channel (PUSCH) transmission, such that the target uplink / downlink configuration is applied to PUSCH transmissions related to DCI transmission received after subframe N, and the uplink / downlink configuration is applied. The predefined uplink / downlink configuration is the same as the above multiple uplink / downlink configurations. It is one of the click structure.

  According to this more detailed embodiment of the mobile station, the predefined uplink / downlink configuration is different from the source uplink / downlink configuration.

  According to another more detailed embodiment of this mobile station, the multiple uplink / downlink configurations are uplink / downlink configurations 0-6 and the source uplink / downlink configuration is an uplink / downlink configuration One of the 1 to 6 subsets and the predefined uplink / downlink configuration is the uplink / downlink configuration 6.

  Further, for the second embodiment, a mobile station that communicates with a base station in a communication system is proposed. Communication is reconfigured from a source uplink / downlink configuration to a target uplink / downlink configuration. The source uplink / downlink configuration is a predefined one of multiple uplink / downlink configurations, and the target uplink / downlink configuration is any of the multiple uplink / downlink configurations It is one of. Multiple uplink / downlink configurations are pre-configured for time division duplex (TDD) communication. When reconfiguring communication for a predetermined subframe N at the beginning of a radio frame, the mobile station receives DCI received by subframe N including subframe N in response to downlink control information (DCI) transmission. Physically, the source uplink / downlink configuration is applied to PUSCH transmissions related to transmission, and the target uplink / downlink configuration is applied to PUSCH transmissions related to DCI transmission received after subframe N + 1. Uplink shared channel (PUSCH) transmission is performed.

  According to a more detailed embodiment of this mobile station, the multiple uplink / downlink configurations are uplink / downlink configurations 0-6 and the source uplink / downlink configuration is uplink / downlink configuration 0. .

  According to another more detailed embodiment of this mobile station, each of a plurality of uplink / downlink configurations determines a timing offset between the DCI transmission and the corresponding PUSCH transmission.

  According to an even more detailed embodiment of this mobile station, the source uplink / downlink configuration is such that subframes are reserved for downlink transmission up to subframe N-1 including subframe N-1. Or indicates a special subframe that supports both downlink and uplink transmissions, and the target uplink / downlink configuration is subframed for subframe N and beyond. Indicates whether the frame is reserved for downlink transmission, reserved for uplink transmission, or a special subframe that supports both downlink and uplink transmissions.

  According to yet another more detailed embodiment of this mobile station, information is distributed in the communication system indicating that communication between the mobile station and the base station should be reconfigured, and the information is subframe N- 14 or later and when it is distributed within an interval from subframe N-5 to subframe N-5, communication is reconfigured for a predetermined subframe N by distributing the information, where N is the head of the radio frame Is a subframe.

  Furthermore, a mobile station that communicates with a base station in a communication system is proposed for the third embodiment. Communication is reconfigured from a source uplink / downlink configuration to a target uplink / downlink configuration. The source and target uplink / downlink configurations are uplink / downlink configurations of a plurality of uplink / downlink configurations. Multiple uplink / downlink configurations are pre-configured for time division duplex (TDD) communication. When reconfiguring communication for a predetermined subframe N at the beginning of a radio frame, the mobile station responds to physical downlink shared channel (PDSCH) transmission up to subframe N-1 including subframe N-1. The source uplink / downlink configuration is applied to the hybrid ARQ-ACK transmissions of the same, and another predefined uplink / downlink configuration is applied to the hybrid ARQ-ACK transmissions between subframes N to N + 12. The hybrid ARQ-ACK transmission is performed such that the target uplink / downlink configuration is applied to the hybrid ARQ-ACK transmission after the subframe N + 13, and the other predefined uplink / downlink configuration is as described above. One of a plurality of uplink / downlink configurations.

  According to this more detailed embodiment of the mobile station, another predefined uplink / downlink configuration is different from the target uplink / downlink configuration.

  According to another more detailed embodiment of this mobile station, another predefined uplink / downlink configuration is an uplink / downlink configuration 5.

  According to an even more detailed embodiment of this mobile station, said another predefined up link, which of a plurality of uplink / downlink configurations is applied to hybrid ARQ-ACK transmission between subframes N to N + 12 Information indicating whether the link / downlink configuration is supported is distributed in the communication system.

  According to yet another more detailed embodiment of this mobile station, each of a plurality of uplink / downlink configurations determines a timing offset between the PDSCH transmission and a corresponding hybrid ARQ-ACK transmission.

  According to an even more detailed embodiment of this mobile station, when the source uplink / downlink configuration is applied in response to a physical downlink shared channel (PDSCH) transmission, the source uplink / downlink configuration is Stipulates hybrid ARQ-ACK transmission up to subframe N-1 including subframe N-1, where the hybrid ARQ-ACK transmission relates to the PDSCH transmission, and the other predefined uplink When the / downlink configuration is applied, the other predefined uplink / downlink configuration defines a hybrid ARQ-ACK transmission between subframes N to N + 12, and the hybrid ARQ-ACK transmission is When related to the PDSCH transmission, the mobile station Or perform only Hybrid ARQ-ACK transmission to subframe N-1 containing 1 or the mobile station performs only Hybrid ARQ-ACK transmission between subframe N to N + 12.

  According to yet another more detailed embodiment of this mobile station, said another predefined uplink / downlink configuration is applied and said another predefined uplink / downlink configuration is Define hybrid ARQ-ACK transmission between subframes N to N + 12 for at least one subframe configured to support only link transmission, where the at least one subframe is subframe from subframe N-11 If the mobile station is within the interval up to subframe N-1 including N-1, the mobile station may perform a hybrid ARQ relating only to subframes configured to support downlink transmission during subframes N to N + 12. -ACK transmission is performed, or the mobile station determines that the at least one subframe is Indicating that uplinks not related only to the support and PDSCH Send performs hybrid ARQ-ACK transmission containing predefined information of the at least one sub-frame is configured to support only the uplink transmission.

  Still further, for a first embodiment, a computer readable medium is provided that stores instructions that, when executed by a processor of a mobile station, cause the mobile station to communicate with a base station in a communication system. Communication is reconfigured from a source uplink / downlink configuration to a target uplink / downlink configuration. The source uplink / downlink configuration is one of a subset of the multiple uplink / downlink configurations, and the target uplink / downlink configuration is any of the multiple uplink / downlink configurations One. Multiple uplink / downlink configurations are pre-configured for time division duplex (TDD) communication. When reconfiguring communication for a predetermined subframe N at the head of the radio frame, the mobile station responds to downlink control information (DCI) transmission until the subframe N-6 including the subframe N-6. A source uplink / downlink configuration is applied to PUSCH transmissions related to received DCI transmissions, and PUSCH transmissions related to DCI transmissions received during subframes N-5 to N-1 are predefined. Physical uplink shared channel (PUSCH) so that the applied uplink / downlink configuration is applied and the target uplink / downlink configuration is applied to PUSCH transmissions related to DCI transmissions received after subframe N The transmit and predefined uplink / downlink configuration is the above multiple uplink / downlink It is one of the link configuration.

  Further, for a second embodiment, a computer readable medium is provided that stores instructions that, when executed by a processor of a mobile station, cause the mobile station to communicate with a base station in a communication system. Communication is reconfigured from a source uplink / downlink configuration to a target uplink / downlink configuration. The source uplink / downlink configuration is a predefined one of multiple uplink / downlink configurations, and the target uplink / downlink configuration is any of the multiple uplink / downlink configurations It is one of. Multiple uplink / downlink configurations are pre-configured for time division duplex (TDD) communication. When reconfiguring communication for a predetermined subframe N at the beginning of a radio frame, the mobile station receives DCI received by subframe N including subframe N in response to downlink control information (DCI) transmission. Physically, the source uplink / downlink configuration is applied to PUSCH transmissions related to transmission, and the target uplink / downlink configuration is applied to PUSCH transmissions related to DCI transmission received after subframe N + 1. Uplink shared channel (PUSCH) transmission is performed.

  Still further, for a third embodiment, a computer readable medium is provided that stores instructions that, when executed by a processor of a mobile station, cause the mobile station to communicate with a base station in a communication system. Communication is reconfigured from a source uplink / downlink configuration to a target uplink / downlink configuration. The source uplink / downlink configuration is one of a subset of the multiple uplink / downlink configurations, and the target uplink / downlink configuration is any one of the multiple uplink / downlink configurations. It is. Multiple uplink / downlink configurations are pre-configured for time division duplex (TDD) communication. When reconfiguring communication for a predetermined subframe N at the beginning of a radio frame, the mobile station responds to physical downlink shared channel (PDSCH) transmission up to subframe N-1 including subframe N-1. The source uplink / downlink configuration is applied to the hybrid ARQ-ACK transmissions of the same, and another predefined uplink / downlink configuration is applied to the hybrid ARQ-ACK transmissions between subframes N to N + 12. The hybrid ARQ-ACK transmission is performed such that the target uplink / downlink configuration is applied to the hybrid ARQ-ACK transmission after the subframe N + 13, and the other predefined uplink / downlink configuration is as described above. One of a plurality of uplink / downlink configurations.

  Hereinafter, the present invention will be described in more detail with reference to the accompanying drawings.

1 illustrates an exemplary architecture of a 3GPP LTE system. 1 illustrates an exemplary overview of the entire 3GPP LTE E-UTRAN architecture. Fig. 3 illustrates an exemplary subframe boundary of a downlink component carrier as defined in 3GPP LTE (at release 8/9). Fig. 4 shows an exemplary downlink resource grid of downlink slots defined in 3GPP LTE (at release 8/9). For the seven (static) TDD UL / DL configurations 0 to 6 currently standardized, the definition of 10 subframes and the switching point periodicity in each are shown. The timing of HARQ ACK / NACK / DTX feedback of static TDD configurations 0 to 6 defined in 3GPP LTE is shown. For static TDD configurations 0-6 defined in 3GPP LTE, the timing of physical uplink shared channel (PUSCH) transmission in response to downlink control information (DCI) transmission is shown. A structure of a radio frame composed of two half frames and 10 subframes in the case of a switching point periodicity of 5 ms is shown. 9A and 9B illustrate an exemplary radio frame order and its drawbacks for three types of TDD UL / DL reconfiguration operations. Fig. 4 illustrates an exemplary radio frame order and its drawbacks for three types of TDD UL / DL reconfiguration operations. FIG. 11A illustrates an exemplary TDD UL / DL reconfiguration operation including improved PUSCH transmission allocation according to the first embodiment of the present invention, and FIG. 11B illustrates according to the second embodiment of the present invention. FIG. 6 illustrates an exemplary TDD UL / DL reconfiguration operation including improved HARQ-ACK transmission allocation. FIG. FIG. 6 illustrates an exemplary TDD UL / DL reconfiguration operation including different implementations of improved PUSCH transmission allocation according to a third embodiment of the present invention.

  In the following paragraphs various embodiments of the invention are described. For illustrative purposes only, most of the embodiments are outlined in connection with radio access schemes with 3GPP LTE (Release 8/9) and LTE-A (Release 10/11/12) mobile communication systems. Some of these techniques are described in the Background section above.

  It should be noted that the present invention can be advantageously used in a mobile communication system such as, for example, the 3GPP LTE-A (Release 10/11/12) communication system described in the Background section above. Note that the invention is not limited to use in this particular exemplary communication network.

  In the context of the present invention, the terms “source TDD configuration” or “source uplink / downlink configuration”, as well as “target TDD configuration” or “target uplink / downlink configuration” are used to describe TDD UL / DL reconfiguration. Emphasize the concept of Nevertheless, it will be apparent that the source TDD configuration is not the first configuration applied to communication between a mobile station and a base station in a communication system. Similarly, the target TDD configuration is not the last TDD configuration applied to communications within the communication system.

  Specifically, in the context of the present invention, the term source and target TDD configurations are used when the TDD UL / DL reconfiguration is enabled in subframe N, the source TDD configuration is the interval [N −k, N−6] at least applied and k> = 10, and in the second embodiment, it is applied at least during the interval [N−k, N] and interpreted as meaning k> = 9. can do. Similarly, the target TDD configuration is applied at least during the interval [N, N + j] in the first embodiment, j> = 4, and is applied at least to [N + 1, N + j] in the second embodiment, j > = 10. Similar considerations apply equally to the third and fourth embodiments.

  In the following, some embodiments of the present invention will be described in detail. It should be understood that these descriptions are not intended to limit the invention and are merely examples of embodiments of the invention for a deep understanding of the invention. Those skilled in the art will recognize that the general principles of the present invention as set forth in the claims can be applied to different scenarios or in ways not explicitly described herein. . Accordingly, the following scenarios envisioned for purposes of describing various embodiments do not limit the present invention.

  Various embodiments described in connection with the present invention generally refer to TDD configurations, and in particular provide improved and more flexible TDD configurations and associated mechanisms / processes.

First embodiment

  In the context of the summary of the present invention, various embodiments provide timing relationships related between TCI UL / DL reconfiguration and between DCI and PUSCH and / or between PDSCH and HARQ-ACK as TDD radio. It has already been emphasized that it is based on the concept of applying differently from the frame structure. The distinction between this TDD radio frame configuration and the timing relationship is made only for a short period before and / or after the reconfiguration is enabled.

  According to the first embodiment, the timing relationship between DCI and PUSCH is adapted to enable advantageous TDD UL / DL reconfiguration. Specifically, in this embodiment, the timing relationship between DCI and PUSCH for a short period before reconfiguration becomes effective so that the utilization of uplink bandwidth in the communication system can be improved. Adapt.

  An exemplary TDD UL / DL reconfiguration operation according to the first embodiment is shown in FIG. 11A, which highlights the benefits of distinguishing between TDD radio frame configuration and the timing relationship between DCI and PUSCH. ing. The TDD UL / DL reconfiguration operation shown in FIG. 11A is based on the example shown in FIG. 9A. The example of FIG. 11A similarly assumes TDD UL / DL reconfiguration from TDD configuration 3 to TDD configuration 6. Reconfiguration takes effect in subframe 20, which is the first subframe of a radio frame.

  The first embodiment assumes communication between a mobile station and a base station in a communication system. Communication is reconfigured from the source TDD configuration to the target TDD configuration. In order to make this first embodiment applicable, the source TDD configuration is one of a subset of the plurality of TDD configurations and the target TDD configuration is any one of the plurality of TDD configurations. It is. It is emphasized that the term “reconstruction” essentially defines that the source TDD configuration is different from the target TDD configuration.

  In an advantageous implementation, a subset of TDD configurations corresponds to TDD configurations 1-6, and a plurality of TDD configurations correspond to TDD configurations 0-6. In the above advantageous implementation, TDD configuration 0 appears to be inconvenient as the source TDD configuration of the first embodiment, but the timing relationship between the adapted DCI and PUSCH is still the source TDD configuration is the TDD configuration. It can be applied to the TDD UL / DL reconfiguration of the first embodiment which is zero.

  In order to reconfigure the communication between the mobile station and the base station, information is distributed within a communication system including those mobile stations and base stations. By distributing this information, the communication between the mobile station and the base station is reconfigured for a predetermined subframe N, which is at the beginning of the radio frame.

  According to an exemplary implementation, subframe N for which reconfiguration is enabled corresponds to the first subframe in a radio frame. However, according to different exemplary implementations, subframe N may correspond to the second, third, or fourth subframe in the radio frame.

  In response to one or more downlink control information (DCI) transmissions, the corresponding physical uplink shared channel (PUSCH) transmission is performed by the mobile station according to the timing relationship between DCI and PUSCH as defined in this embodiment. Done. Specifically, the term “timing relationship between DCI and PUSCH” refers to a timing offset defined by a TDD configuration index between one or more DCI transmissions and the corresponding PUSCH transmissions.

  First, the source TDD configuration is applied by the mobile terminal to PUSCH transmission related to DCI transmission received by the mobile station by subframe N-6 including subframe N-6. Specifically, the mobile station may receive source TDD for one or more PUSCH transmissions scheduled in response to one or more DCI transmissions carrying each UL grant received during those subframes. Apply timing relationships defined in the configuration.

  Then, between the subframe N-5 and the subframe N-1 (including subframe N-5 and subframe N-1), the mobile terminal intermediates the PUSCH transmission related to the DCI transmission received by the mobile station. The (ie predefined) TDD configuration is applied. In particular, the mobile station may include intermediate transmissions for one or more PUSCH transmissions scheduled in response to one or more DCI transmissions carrying respective UL grants received during those subframes. Apply the timing relationships defined in the TDD configuration (ie, predefined).

  Finally, the target TDD configuration is applied by the mobile terminal to PUSCH transmission related to DCI transmission received by the mobile station after subframe N. Specifically, the mobile station may send a target TDD for one or more PUSCH transmissions scheduled in response to one or more DCI transmissions carrying each UL grant received during those subframes. Apply timing relationships defined in the configuration.

  According to an advantageous implementation, the intermediate (ie predefined) TDD configuration applied to the PUSCH transmission related to the DCI transmission during subframes N-5 to N-1 is different from the source TDD configuration. In this regard, the communication system will be able to apply the TDD configuration as an intermediate (ie, predefined) TDD configuration that defines the timing relationship between DCI and PUSCH, so that the source TDD configuration and target The loss of uplink bandwidth resulting from the transition to the TDD configuration is mitigated.

  According to an advantageous implementation of the first embodiment, the intermediate (ie predefined) TDD configuration is the TDD configuration 6 as defined in FIG. With this TDD configuration 6, it is possible to perform DCI transmission that conveys UL grants for the three subframes of the next radio frame. In particular, in TDD configuration 6, it is possible to perform PUSCH transmission of subframes (5 + 7) = 12, (6 + 7) = 13, and (9 + 5) = 14 by DCI transmission in subframes 5, 6, and 9. In this regard, TDD configuration 6 performs PUSCH transmission in all subframes in the first half of the next radio frame that can be configured to support uplink transmission (ie, subframes 2, 3, and 4). (See FIG. 5).

  Referring to the example shown in FIG. 11A, TDD configuration 6 is applied to determine the timing relationship between DCI and PUSCH for subframes 15-19 (see the shaded subframes in FIG. 11A). Specifically, TDD configuration 6 has been enabled for TDD UL / DL reconfiguration by applying TDD configuration 6 to PUSCH transmissions related to DCI subframes received in subframes 15, 16, and 19. The PUSCH transmission to be performed later in subframes 22, 23, and 24 is defined (see the dashed arrow in FIG. 11A).

  In this regard, in the first embodiment, during a short period before reconfiguration takes effect, the timing relationship between DCI and PUSCH, ie, the timing relationship corresponding to the intermediate (ie, predefined) TDD configuration, Can be adapted. Thereby, PUSCH subframes that cannot be allocated can be avoided, and utilization of uplink bandwidth in the communication system is improved.

  Specifically, when TDD configuration 6 is used as an intermediate (ie, predefined) TDD configuration that determines the timing relationship between DCI and PUSCH of DCI transmission between subframes N-5 to N-1. Can assign all subframes of the first half of the next radio frame for PUSCH transmission. Specifically, the next radio frame is the first radio frame in which TDD UL / DL reconfiguration is enabled.

Second embodiment

  In the second embodiment, as in the first embodiment, the timing relationship between DCI and PUSCH is adapted to enable advantageous TDD UL / DL reconfiguration. Specifically, in this embodiment, the timing relationship between DCI and PUSCH can be adapted for a short period after reconfiguration is enabled to improve the utilization of uplink bandwidth in the communication system. To.

  Also in the second embodiment, communication between a mobile station and a base station in the communication system is assumed. Communication is reconfigured from the source TDD configuration to the target TDD configuration. In order to make this second embodiment applicable, the source TDD configuration is a predefined one of the plurality of TDD configurations, and the target TDD configuration is any one of the plurality of TDD configurations. One. It is emphasized that the term “reconstruction” essentially defines that the source TDD configuration is different from the target TDD configuration.

  In an advantageous implementation, an intermediate (ie, predefined) TDD configuration of the plurality of TDD configurations corresponds to TDD configuration 0, and a plurality of TDD configurations correspond to TDD configurations 0-6. In the above advantageous implementation, TDD configurations 1-6 appear to be inconvenient as the source TDD configuration of the second embodiment, but the timing relationship between the adapted DCI and PUSCH is still The present invention can be applied to the TDD UL / DL reconfiguration according to the second embodiment which is one of the TDD configurations 1 to 6.

  In order to reconfigure the communication between the mobile station and the base station, information is distributed within a communication system including those mobile stations and base stations. By distributing this information, the communication between the mobile station and the base station is reconfigured for a predetermined subframe N, which is at the beginning of the radio frame.

  According to an exemplary implementation, subframe N for which reconfiguration is enabled corresponds to the first subframe in a radio frame. However, according to another exemplary implementation, subframe N may correspond to the second, third, or fourth subframe in the radio frame.

  In response to one or more downlink control information (DCI) transmissions, the corresponding physical uplink shared channel (PUSCH) transmission is performed by the mobile station according to the timing relationship between DCI and PUSCH as defined in this embodiment. Done. Specifically, the term “timing relationship between DCI and PUSCH” means a timing offset defined by a TDD configuration index between one or more DCI transmissions and the corresponding PUSCH transmissions.

  First, the source TDD configuration is applied by the mobile terminal to PUSCH transmission related to DCI transmission received by the mobile station up to subframe N including subframe N. Specifically, the mobile station may receive source TDD for one or more PUSCH transmissions scheduled in response to one or more DCI transmissions carrying each UL grant received during those subframes. Apply timing relationships defined in the configuration.

  The target TDD configuration is then applied by the mobile terminal to PUSCH transmission related to DCI transmission received by the mobile station after subframe N + 1. Specifically, the mobile station may send a target TDD for one or more PUSCH transmissions scheduled in response to one or more DCI transmissions carrying each UL grant received during those subframes. Apply timing relationships defined in the configuration.

  Since the TDD UL / DL reconstruction is set to be effective for the subframe having the index N at the head of the radio frame, there is no possibility that N corresponds to the last subframe in the radio frame. In this regard, the source TDD configuration is applied to the PUSCH transmission related to the DCI transmission received in one radio frame, and the target TDD configuration is applied to the PUSCH transmission related to the DCI transmission received in another (ie, the next) subframe. Is not likely to apply.

  In other words, by defining the subframe N at the beginning of the radio frame, the switching between the application of the source TDD configuration and the application of the target TDD configuration is prevented from hitting the boundary of the radio frame. This is true only when the source TDD configuration is applied to PUSCH transmissions related to DCI transmissions received up to subframe N-1 including subframe N-1.

  In particular, in an advantageous implementation, it is particularly advantageous to apply TDD configuration 0 to PUSCH transmissions related to DCI transmissions received in subframe N. This is because if this is not done, the allocation of PUSCH transmission to the subframe 24 cannot be guaranteed. As can be easily understood from FIG. 7, TDD configuration 0 enables TDD transmission that conveys UL grants related to two subframes of the next radio frame. In particular, in TDD configuration 0, it is possible to perform respective PUSCH transmissions in subframes (5 + 7) = 12 and (6 + 7) = 13 by DCI transmission in subframes 5 and 6. However, the subframe 14 can also be set to support PUSCH transmission.

  In this regard, TDD configuration 0 is also applied to PUSCH transmissions related to DCI transmissions received in subframe N (eg, subframes 0, 10, 20), whereby subframe N + 4 (eg, subframe 4). , 14, 24) enables PUSCH transmission. In other words, when TDD configuration 0 is used as an intermediate (ie, predefined) TDD configuration that determines the timing relationship between DCI and PUSCH for DCI transmission in subframes up to subframe N including subframe N Can allocate all subframes of the first half of the next radio frame for PUSCH transmission.

  Referring to the example shown in FIG. 12, TDD configuration 0 is applied to determine the timing relationship between DCI and PUSCH for subframe 20 (see subframe in FIG. 12). Specifically, TDD configuration 0 is applied to PUSCH transmission related to the DCI subframe received in subframe 20. Therefore, TDD configuration 0 defines the PUSCH transmission to be performed in subframe 24 after TDD UL / DL reconfiguration is enabled (see the dashed arrow in FIG. 12).

  In general, in the first and second embodiments, each of a plurality of TDD configurations determines a timing offset between the one or more DCI transmissions and a corresponding PUSCH transmission. This timing offset between one or more DCI transmissions and the corresponding PUSCH transmission is also referred to as “timing relationship between DCI and PUSCH” throughout this description.

  Further, in the first and second embodiments, the source TDD configuration is such that subframes are reserved for downlink transmission or up to subframe N-1 including subframe N-1. Indicates a special subframe that specifies whether it is reserved for, or supports both downlink and uplink transmission, and the target TDD configuration indicates that for subframe N and beyond, the subframe is for downlink transmission. Specifies whether it is reserved or reserved for uplink transmission, or indicates a special subframe that supports both downlink and uplink transmission. In this regard, the reconstruction of the TDD radio frame configuration is valid for subframe N including the indicated subframe N.

Third embodiment

  In connection with the third embodiment of the present invention, various embodiments provide timing relationships related between DCI and PUSCH and / or between PDSCH and HARQ-ACK for TDD UL / DL reconfiguration. Again, it is emphasized that it is based on the concept of applying differently from the TDD radio frame configuration. The distinction between this TDD radio frame configuration and the timing relationship is made only for a short period before and / or after the reconfiguration is enabled.

  According to the third embodiment, the timing relationship between PDSCH and HARQ-ACK is adapted to enable advantageous TDD UL / DL reconfiguration. Specifically, in this embodiment, the hybrid ARQ function can be used at all times by adapting the timing relationship between the PDSCH and the HARQ-ACK for a short period after the reconfiguration is enabled.

  An exemplary TDD UL / DL reconfiguration operation according to the third embodiment is shown in FIG. 11B, which illustrates the benefits of distinguishing the TDD radio frame configuration and the timing relationship between PDSCH and HARQ-ACK. Emphasized. The TDD UL / DL reconfiguration operation shown in FIG. 11B is based on the example shown in FIG. 9B. The example of FIG. 11B similarly assumes TDD UL / DL reconfiguration from TDD configuration 3 to TDD configuration 6. Reconfiguration takes effect in subframe 20, which is the first subframe of a radio frame.

  The third embodiment assumes communication between a mobile station and a base station in a communication system. Communication is reconfigured from the source TDD configuration to the target TDD configuration. The source TDD configuration and the target TDD configuration are arbitrary TDD configurations among a plurality of TDD configurations. It is emphasized that the term “reconstruction” essentially defines that the source TDD configuration is different from the target TDD configuration.

  In an advantageous implementation, the source TDD configuration corresponds to one of the TDD configurations 0-6 and the target TDD configuration corresponds to another one of the TDD configurations 0-6.

  In order to reconfigure the communication between the mobile station and the base station, information is distributed within a communication system including those mobile stations and base stations. By distributing this information, the communication between the mobile station and the base station is reconfigured for a predetermined subframe N, which is at the beginning of the radio frame.

  According to an exemplary implementation, subframe N for which reconfiguration is enabled corresponds to the first subframe in a radio frame. However, according to another exemplary implementation, subframe N may correspond to the second, third, or fourth subframe in the radio frame.

  Timing relationship between PDSCH and HARQ-ACK as defined in this embodiment in response to one or more physical downlink shared channel (PDSCH) transmissions and related hybrid ARQ-ACKnowledgement (HARQ-ACK) transmissions According to the mobile station. Specifically, the term “timing relationship between PDSCH and HARQ-ACK” refers to a timing offset defined by the TDD configuration between one or more PDSCH transmissions and the corresponding HARQ-ACK transmissions.

  First, a source TDD configuration is applied by a mobile station to hybrid ARQ-ACK transmission up to subframe N-1 including subframe N-1. Therefore, the mobile station determines whether or not to perform one or more HARQ-ACK transmissions for each subframe up to subframe N-1 including subframe N-1, based on the source TDD configuration. Judgment. Specifically, the mobile station indicates to which one or more PDSCH transmissions (if done) the source TDD configuration indicates HARQ-ACK transmission in each subframe. Determine.

  The hybrid ARQ-ACK transmission between subframe N including subframe N to subframe N + 12 including subframe N + 12 is then applied with another intermediate (ie, predefined) TDD configuration by the mobile station. The Thus, the mobile station determines whether one or more HARQ-ACK transmissions must be performed for each subframe between subframes N to N + 12, in another intermediate (ie, predefined). Determine based on TDD configuration. Specifically, the mobile station may have another intermediate (ie, predefined) TDD configuration for any of one or more previous PDSCH transmissions (ie, if there are PDSCH transmissions), It is determined whether HARQ-ACK transmission is indicated in each subframe.

  Finally, the target TDD configuration is applied by the mobile station to hybrid ARQ-ACK transmission after subframe N + 13. Therefore, the mobile station determines, based on the target TDD configuration, whether one or more HARQ-ACK transmissions must be performed for each subframe after subframe N + 13. Specifically, for any of one or more PDSCH transmissions (ie, when there are PDSCH transmissions) previously made, the mobile station has the target TDD configuration to send HARQ-ACK transmissions in each subframe. Determine whether it is showing.

  According to an advantageous implementation, another intermediate (ie predefined) TDD configuration applied to HARQ-ACK transmission during subframes N to N + 13 is different from the target TDD configuration. In this regard, the communication system will be able to apply a TDD configuration as an intermediate (ie, predefined) TDD configuration that defines the timing relationship between PDSCH and HARQ-ACK, thereby providing a source TDD configuration. The hybrid ARQ function can always be used during the transition from the target TDD configuration to the target TDD configuration.

  According to an advantageous implementation of the third embodiment, another intermediate (ie predefined) TDD configuration is the TDD configuration 5 as defined in FIG. In this TDD configuration 5, HARQ-ACK transmission related to PDSCH transmission received by the mobile terminal in the two preceding radio frames is possible. Specifically, in TDD configuration 5, 9 is related to PDSCH transmission received by the mobile terminal in subframe 2 before 13, 12, 9, 8, 7, 5, 4, 11, and 6 subframes, respectively. Two HARQ-ACK transmissions can be combined.

  Referring to the example shown in FIG. 11B, TDD configuration 5 is applied to determine the timing relationship between PDSCH and HARQ-ACK for HARQ transmission between subframes 20 to 32 (shaded subframe in FIG. 11B). See). Specifically, TDD configuration 5 is applied to HARQ-ACK transmission in subframes 22 and 32, and TDD configuration 5 is a PDSCH transmission related to HARQ-ACK transmission after TDD UL / DL reconfiguration is enabled. (See the arrow with a chain line in FIG. 11B).

  In this regard, the third embodiment accommodates the timing relationship between PDSCH and HARQ-ACK, i.e. another intermediate (i.e. predefined) TDD configuration, during a short period before reconfiguration takes effect. The timing relationship can be adapted. Thereby, the PDSCH subframe in which HARQ-ACK is transmitted can be avoided, and the hybrid ARQ function can be always used.

First implementation

  According to the first implementation of the third embodiment, the other intermediate (ie predefined) TDD configuration is no longer considered a static configuration of the communication system. Instead, other intermediate (ie, predefined) TDD configurations applied to HARQ-ACK transmissions during subframes N to N + 12 are signaled within the communication system.

  Specifically, information indicating a TDD configuration corresponding to another intermediate (ie, predefined) TDD configuration among a plurality of TDD configurations is distributed in the communication system. When the mobile terminal receives this information indicating another intermediate (ie, predefined) TDD configuration, the mobile terminal may receive the other intermediate (ie, predefined) TDD configuration, and subsequent TDD UL / DL reconfiguration. Applied between configurations, i.e., subframes N-N + 12, where subframe N indicates a subframe in which the reconstruction is subsequently valid.

  Optionally, information indicating other intermediate (ie, predefined) TDD configurations may be combined with information indicating a subframe from which communication within the communication system is reconfigured.

Second implementation

  In the second implementation of the third embodiment, the effect of multiple HARQ-ACK transmissions on one PDSCH transmission is examined in detail. As illustratively shown in FIG. 11B, for PDSCH transmission in subframes 9 and 10, HARQ-ACK transmission is performed in response to application of the source TDD configuration (ie, TDD configuration 3), and subsequent HARQ-ACK transmission. Is implemented in response to application of other intermediate (ie, predefined) TDD configurations.

  Specifically, a plurality of HARQ-ACK transmissions are performed as a result of one PDSCH transmission, and in this case, the mobile terminal performs PDSCH transmission up to the subframe N-1 including the subframe N-1 in the source TDD configuration. Define related HARQ-ACK transmissions, and determine that other intermediate (ie, predefined) TDD configurations specify HARQ-ACK transmissions between subframes N-N + 12 related to the same PDSCH transmission.

  According to the second implementation, the mobile station additionally determines which of HARQ-ACK transmissions that may be performed multiple times for one PDSCH transmission. More specifically, in response to one PDSCH transmission, application of the source TDD configuration defines HARQ-ACK transmission up to subframe N-1 including subframe N-1 related to the PDSCH transmission, and the other If an intermediate (ie, predefined) TDD configuration application defines HARQ-ACK transmission between subframes N to N + 12 related to that PDSCH transmission, then the mobile node includes subframe N−1 Only the HARQ-ACK transmission up to the subframe N-1 is performed, or the mobile node performs only the HARQ-ACK transmission between the subframes N to N + 12.

  Specifically, if the mobile terminal only performs HARQ-ACK transmission up to subframe N-1 including subframe N-1, a delay related to HARQ-ACK feedback can be reduced. Furthermore, the payload generated as a result of HARQ-ACK transmission between subframes N to N + 12 can be reduced.

  According to an advantageous variation of the second implementation, when a plurality of HARQ-ACK transmissions are performed for one PDSCH transmission, the mobile station can perform HARQ-ACK until subframe N-1 including subframe N-1. In addition, HARQ-ACK transmission including predefined information, for example, discontinuous transmission (DTX) information, is performed during subframes N to N + 12.

  More specifically, in response to one PDSCH transmission, application of the source TDD configuration defines HARQ-ACK transmission up to subframe N-1 including subframe N-1 related to the PDSCH transmission, and the other If an intermediate (ie, predefined) TDD configuration application defines HARQ-ACK transmission between subframes N to N + 12 related to that PDSCH transmission, then the mobile node includes subframe N−1 HARQ-ACK transmission up to subframe N-1 is performed, and HARQ-ACK transmission including DTX information is performed between subframes N to N + 12.

Third implementation

  The third implementation of the third embodiment focuses on HARQ-ACK transmissions defined in other intermediate (ie, predefined) TDD configurations, but this HARQ-ACK transmission is used for PDSCH transmissions. Related to previous subframes that have never been reserved.

  As already described in detail with respect to the third embodiment, other intermediate (i.e. predefined) TDD configurations are applied to which subframes N.sub. It is determined whether HARQ-ACK transmission should be performed during N + 12. This is different from the TDD radio frame configuration specified in the source TDD configuration for the subframe N-1 including the subframe N-1 and the TDD radio frame configuration specified in the target TDD configuration for the subframe N and later. To be done.

  In other words, the other intermediate (ie predefined) TDD configuration reflects a different TDD radio frame configuration and is different (ie more) PDSCH transmissions than the subframes actually reserved in the source TDD configuration. Indicates the trust subframe.

  According to a third implementation, for at least one subframe configured to support only uplink transmission, the application of other intermediate (ie predefined) TDD configuration is between subframes N to N + 12. When prescribing hybrid ARQ-ACK transmission, the mobile node performs hybrid ARQ-ACK transmission related only to subframes configured to support downlink transmission during subframes N to N + 12, or The mobile terminal performs hybrid ARQ-ACK transmission including predefined information.

  Advantageously, the predefined information may indicate that the at least one subframe supports only uplink transmission and is not related to PDSCH transmission.

Further implementation

  In any of the above embodiments, the communication between the mobile station and the base station can be reconfigured for subframe N based on the distribution of information informing the reconfiguration in the communication system.

  By distributing the information, communication between the mobile station and the base station is reconfigured for a predetermined subframe N, and the subframe N is at the head of the radio frame.

  In this regard, if the mobile terminal receives information that informs it to reconfigure the communication between the mobile station and the base station, the mobile terminal is related between DCI and PUSCH and / or between PDSCH and HARQ-ACK. Each TDD UL / DL reconfiguration is performed by applying the timing relationship differently (ie, individually) from the TDD radio frame configuration.

  Advantageously, the information indicating the reconfiguration is moved only if it is distributed within the interval from subframe N-14 to subframe N-5 (including subframe N-14 and subframe N-5). Considered by the station and / or base station, subframe N indicates when the reconfiguration is valid. In order to reduce the risk that the mobile station will detect and apply the reconfiguration in error, the reconfiguration that is indicated only if the information that informs the reconfiguration is detected multiple times, eg twice, during the interval It is further advantageous for the UE to apply reconfiguration only if are the same multiple times. For example, if the probability that one piece of reconfiguration information is erroneously detected is 1%, the probability that one piece of reconfiguration information is erroneously detected twice is 0.01%. These approaches are particularly useful when the reconfiguration is signaled with an explicit message, i.e. a signal containing at least the target configuration as information.

  An alternative method for more implicitly determining reconfiguration is the uplink transmission or uplink for PUSCH according to the timing of the uplink subframe according to the source UL / DL configuration (or UL / DL configuration indicated by SIB1) Check for missing (or missing) resource allocation. For example, referring to FIGS. 5 and 7, the following table shows how the lack of PUSCH assignment for subframe j can indicate reconfiguration to the target TDD configuration depending on the source TDD configuration: A preferred embodiment is shown. The advanced method determines the reconfiguration only by the lack of PUSCH allocation for the first subframe j of the radio frame. For example, if the source configuration is 0 and no PUSCH assignment is detected for subframe 3 of the radio frame, the target configuration is determined to be configuration 2. Even if there is a further lack of PUSCH assignment for subframe 4 of the same radio frame, the target configuration is not further changed.

Fourth embodiment

  According to the fourth embodiment, the concept of the present invention is also applied to transmission power control (TPC) command signaling. The TPC command is distributed within the communication system to indicate the transmission power to be used at the mobile station. Thus, upon receiving a TPC command, the mobile station considers the value transmitted with that command for future uplink transmissions.

  In 3GPP LTE, the TPC command is specified to indicate only the difference power change amount of the transmission power executed by the mobile terminal. For example, the TPC command may instruct the mobile terminal to increase the transmit power by the value included in the command or decrease the transmit power by another value included in the command. In this regard, the continuous signaling of TPC commands improves the flexibility of power adjustment performed by the mobile terminal.

  It is important to note that TPC commands can be sent regardless of the uplink transmission performed by the mobile terminal. In other words, the mobile terminal calculates the transmission power of each subframe based on the received TPC command before actual uplink transmission. Thus, constantly, one or more TPC commands are received and the transmission power is evaluated for each subframe by the mobile terminal.

  Nevertheless, applicable TPC commands for a given uplink transmission only transmit based on a pre-configured timing relationship corresponding to what was discussed above as between DCI and PUSCH and / or between PDSCH and HARQ-ACK. be able to. Specifically, a PUSCH TPC command and a PUCCH TPC command are distinguished.

  The PUSCH TPC command is included in the DCI transmission carrying the UL grant or in the DCI transmission of the transmit power control (TPC) command. DCI transmissions including PUSCH TPC commands are in format 0/4 or format 3 / 3A and correspond to DCI transmissions related to PUSCH transmission discussed in connection with the first and second embodiments. Nevertheless, the PUSCH TPC command can also be received and processed as part of PUSCH power control via DCI transmission that does not schedule PUSCH, such as in DCI format 3 or 3A, thus defining different timing relationships.

  In particular, Table 5.1.1.1-1 defined in Section 5.1.1.1 “UE behavior” of Non-Patent Document 5, which is incorporated herein by reference, is one example of PUSCH power control. This defines a timing relationship between transmission of a PUSCH TPC command as a part and processing thereof. Specifically, the timing relationship between this TPC and PUSCH is specified in Table 5.1.1.1-1 in the reverse subframe direction. Specifically, for PUSCH power control performed in subframe i, the mobile terminal refers to a previous TPC command corresponding to PUSCH transmission up to subframe i-k including subframe i-k. In other words, the subframe number i shown in Table 5.1.1.1-1 corresponds to the PUSCH transmission received k subframes before the subframe of number i for which PUSCH power control is performed. TPC command.

  In order to enable continuous PUSCH power control in the mobile terminal during TDD UL / DL reconfiguration, the same considerations as in the above embodiment are reflected in the following mechanism, which is used between the mobile terminal and the base station. Communication can be reconfigured individually or combined with any of the above embodiments.

  According to one variation, it is assumed that the mobile station communicates with the base station within the communication system. Communication is reconfigured from the source TDD configuration to the target TDD configuration. Further, the source TDD configuration is one of a subset of the plurality of TDD configurations, and the target TDD configuration is any one of the plurality of TDD configurations. Multiple TDD configurations are preset for time division duplex (TDD) communication. When reconfiguring communication for a predetermined subframe N at the beginning of a radio frame, the mobile station performs PUSCH power control according to a TPC command for PUSCH transmission according to the following scheme.

  First, the source TDD configuration is applied to perform PUSCH power control for subframes related to TPC commands corresponding to PUSCH transmissions received up to subframe N-6 including subframe N-6. An intermediate (ie, predefined) TDD configuration is then used to perform PUSCH power control for subframes related to TPC commands corresponding to PUSCH transmissions received during subframes N-5 to N-1. Apply. Finally, the target TDD configuration is applied to perform PUSCH power control for subframes related to TPC commands corresponding to PUSCH transmissions received after subframe N. The intermediate (ie, predefined) TDD configuration is one of the plurality of TDD configurations. Advantageously, the intermediate (ie predefined) TDD configuration is different from the source TDD configuration and is preferably the TDD configuration 6.

  According to another variation, it is also assumed here that the mobile station communicates with the base station within the communication system. Communication is reconfigured from the source TDD configuration to the target TDD configuration. Further, the source TDD configuration is a predefined one of the plurality of TDD configurations, and the target TDD configuration is any one of the plurality of TDD configurations. Multiple TDD configurations are preset for time division duplex (TDD) communication.

  When reconfiguring communication for a predetermined subframe N at the beginning of a radio frame, the mobile station performs PUSCH power control according to a TPC command for PUSCH transmission according to the following scheme.

  First, the source TDD configuration is applied to perform PUSCH power control for subframes related to TPC commands corresponding to PUSCH transmissions received up to subframe N including subframe N. The target TDD configuration is then applied to perform PUSCH power control for subframes related to TPC commands corresponding to PUSCH transmissions received after subframe N + 1. Advantageously, the source TDD configuration is TDD configuration 0.

  According to a further variation, it is also assumed here that the mobile station communicates with the base station within the communication system. Communication is reconfigured from the source TDD configuration to the target TDD configuration. Further, the source and target TDD configurations are any TDD configuration of a plurality of TDD configurations. Multiple TDD configurations are preset for time division duplex (TDD) communication.

  When reconfiguring communication for a predetermined subframe N at the head of a radio frame, the mobile station performs power control adjustment for PUSCH transmission according to the TPC command for PUSCH transmission according to the following scheme.

  First, the source TDD configuration is applied to perform PUSCH power control for subframes related to TPC commands corresponding to PUSCH transmissions received up to subframe N including subframe N. The target TDD configuration is then applied to perform PUSCH power control for subframes related to TPC commands corresponding to PUSCH transmissions received after subframe N + 1. Advantageously, the source TDD configuration is TDD configuration 0.

  First, in order to perform power control adjustment for PUSCH transmission in subframes including subframe N + 1 to subframe N + 1, the source TDD configuration is applied to determine which subframe includes the corresponding TPC command. judge. Then, to make power control adjustments for PUSCH transmissions in subframes N + 2 to N + 4, an intermediate (ie, predefined) TDD configuration is applied and which subframe contains the corresponding TPC command Determine. Finally, in order to perform power control adjustment for PUSCH transmission in subframes N + 5 and later, the target TDD configuration is applied to determine which subframe includes the corresponding TPC command. Alternatively, the last subframe to which the source TDD configuration is applied may be N-1 or N, and the first subframe to which the intermediate (ie, predefined) TDD configuration is applied is N or N + 1, respectively. There may be. The intermediate (ie, predefined) TDD configuration is one of the plurality of TDD configurations. Advantageously, the intermediate (ie predefined) TDD configuration is different from the source TDD configuration and is preferably the TDD configuration 6.

  The PUCCH TPC command is included in the DCI transmission for PDSCH assignment or the transmission power control (TPC) command DCI transmission. DCI transmission including PUCCH TPC command is in format 1A / 1B / 1D / 1 / 2A / 2 / 2B / 2C / 2D and corresponds to DCI transmission related to PDSCH transmission discussed in the context of the third embodiment To do. Nevertheless, different timing relationships are defined because the PUCCH TPC command can also be received and processed as part of PUCCH power control via DCI transmissions that do not schedule PUCCH.

  In particular, Non-Patent Document 5 (refer to Table 10.1.3.1-1 in Section 10.1.1.3.1 “TDD HARQ-ACK procedure for one configured serving cell”). In section 5.1.2.1 “UE behavior” of (incorporated in the specification), the timing relationship between the transmission of a PUCCH TPC command as part of PUCCH power control and its processing is described as PUCCH Timing relationships are defined. Specifically, the timing relationship between TPC and PUCCH is specified to correspond to the timing relationship between PDSCH and HARQ-ACK. The correspondence between this timing relationship arises from the fact that DCI transmissions containing PUCCH TPC commands are implemented in the same subframe as PDSCH transmissions involving HARQ-ACK transmission.

  In this regard, in order to enable continuous PUCCH power control in the mobile terminal at the time of TDD UL / DL reconfiguration, the same consideration as in the above embodiment is reflected in the following mechanism, and this mechanism includes the mobile terminal and the base station. Can be performed individually when reconfiguring communication between, or combined with any of the above embodiments.

  According to yet another variation, it is assumed that the mobile station communicates with the base station within the communication system. Communication is reconfigured from the source TDD configuration to the target TDD configuration.

  Further, the source TDD configuration is a predefined one of the plurality of TDD configurations, and the target TDD configuration is any one of the plurality of TDD configurations. Multiple TDD configurations are preset for time division duplex (TDD) communication.

  When reconfiguring communication for a predetermined subframe N at the beginning of a radio frame, the mobile station performs PUCCH power control according to one or more TPC commands for PUCCH transmission according to the following scheme.

  First, the source TDD configuration is applied to perform PUCCH power control up to subframe N-1 including subframe N-1. In order to perform PUCCH power control between subframes N to N + 12, another intermediate (ie, predefined) TDD configuration is applied. Finally, the target TDD configuration is applied to perform PUCCH power control after subframe N + 13. Here, the other intermediate (ie, predefined) TDD configuration is one of the plurality of TDD configurations. Advantageously, the intermediate (ie predefined) TDD configuration is different from the target TDD configuration, and is preferably TDD configuration 5.

Hardware and software implementation of the present invention

  Other embodiments of the invention relate to implementing the various embodiments described above using hardware and software. In this context, the present invention provides user equipment (mobile station) and eNodeB (base station). The user equipment is adapted to perform the method of the present invention.

  It is further recognized that the various embodiments of the invention may be implemented or performed using computing devices (processors). The computing device or processor is, for example, a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device. Various embodiments of the present invention may also be implemented or embodied by combinations of these devices.

  Further, the various embodiments of the invention may also be implemented by software modules. These software modules are executed by a processor or directly in hardware. A combination of software modules and hardware implementation is also possible. The software module may be stored in any type of computer readable storage medium, such as RAM, EPROM, EEPROM, flash memory, registers, hard disk, CD-ROM, DVD, and the like.

  Furthermore, it should be noted that individual features of different embodiments of the present invention may be another subject matter of the present invention, either individually or in any combination.

  It will be apparent to those skilled in the art that various changes and / or modifications can be made to the invention described in the specific embodiments without departing from the broader concept or scope of the invention. Will be understood. Accordingly, the embodiments presented herein are to be considered in all respects only as illustrative and not restrictive.

Claims (15)

An integrated circuit that controls a mobile station that communicates with a base station in a communication system, wherein the communication is reconfigured from a source uplink / downlink configuration to a target uplink / downlink configuration,
The source uplink / downlink configuration is one of a subset of a plurality of uplink / downlink configurations, and the target uplink / downlink configuration is one of the plurality of uplink / downlink configurations. And the plurality of uplink / downlink configurations are preset for time division duplex (TDD) communication,
When reconfiguring the communication for a predetermined subframe N at the beginning of a radio frame, the mobile station responds to a downlink control information (DCI) transmission,
Applying the source uplink / downlink configuration to physical uplink shared channel (PUSCH) transmission related to DCI transmission received up to subframe N-6 including subframe N-6,
Apply a predefined uplink / downlink configuration to PUSCH transmissions related to DCI transmissions received during subframes N-5 to N-1,
Apply the target uplink / downlink configuration to PUSCH transmission related to DCI transmission received after subframe N,
So that PUSCH transmission
The predefined uplink / downlink configuration is one of the plurality of uplink / downlink configurations;
Integrated circuit. The predefined uplink / downlink configuration is different from the source uplink / downlink configuration;
The integrated circuit according to claim 1. The plurality of uplink / downlink configurations are uplink / downlink configurations 0-6;
The subset includes at least one of the uplink / downlink configurations 1-6;
The predefined uplink / downlink configuration is an uplink / downlink configuration 6;
The integrated circuit according to claim 1 or 2. An integrated circuit that controls a mobile station that communicates with a base station in a communication system, wherein the communication is reconfigured from a source uplink / downlink configuration to a target uplink / downlink configuration,
The source uplink / downlink configuration is a predefined one of a plurality of uplink / downlink configurations, and the target uplink / downlink configuration is a component of the plurality of uplink / downlink configurations. And the plurality of uplink / downlink configurations are pre-configured for time division duplex (TDD) communication,
When reconfiguring the communication for a predetermined subframe N at the beginning of a radio frame, the mobile station responds to a downlink control information (DCI) transmission,
Applying the source uplink / downlink configuration to physical uplink shared channel (PUSCH) transmission related to DCI transmission received up to subframe N-1 including subframe N-1,
Apply the target uplink / downlink configuration to PUSCH transmission related to DCI transmission received after subframe N,
To perform PUSCH transmission,
Integrated circuit. The plurality of uplink / downlink configurations are uplink / downlink configurations 0-6;
The source uplink / downlink configuration is uplink / downlink configuration 0;
The integrated circuit according to claim 4. Each of the plurality of uplink / downlink configurations determines a timing offset between the DCI transmission and a corresponding PUSCH transmission;
The integrated circuit as described in any one of Claims 1-5. In the source uplink / downlink configuration, each subframe up to subframe N-1 including subframe N-1 is a downlink subframe for downlink transmission or an uplink subframe for uplink transmission. Or a special subframe that supports both the downlink transmission and the uplink transmission,
The target uplink / downlink configuration indicates whether each subframe after subframe N is the downlink subframe, the uplink subframe, or the special subframe.
The integrated circuit as described in any one of Claims 1-6. Information notifying that communication between the mobile station and the base station should be reconfigured is distributed in the communication system, and the information includes subframe N-5 from subframe N-14 onward. When distributed within the interval up to -5, the communication is reconfigured for the predetermined subframe N by the distribution of the information, where N is a subframe at the beginning of the radio frame;
The integrated circuit as described in any one of Claims 1-7. In response to a physical downlink shared channel (PDSCH) transmission, the mobile station
Applying the source uplink / downlink configuration to hybrid ARQ-ACK transmission up to subframe N-1 including subframe N-1,
Apply another predefined uplink / downlink configuration for hybrid ARQ-ACK transmission between subframes N to N + 12;
Applying the target uplink / downlink configuration to hybrid ARQ-ACK transmission after subframe N + 13,
To perform hybrid ARQ-ACK transmission,
The another predefined uplink / downlink configuration is one of the plurality of uplink / downlink configurations;
The integrated circuit as described in any one of Claims 1-8. The another predefined uplink / downlink configuration is different from the target uplink / downlink configuration;
The integrated circuit according to claim 9. Said another predefined uplink / downlink configuration is uplink / downlink configuration 5;
The integrated circuit according to claim 9 or 10. Information indicating which of the plurality of uplink / downlink configurations corresponds to the another predefined uplink / downlink configuration applied to hybrid ARQ-ACK transmission between subframes N to N + 12 Is distributed within the communication system,
The integrated circuit as described in any one of Claims 9-11. Each of the plurality of uplink / downlink configurations determines a timing offset between the PDSCH transmission and a corresponding hybrid ARQ-ACK transmission;
The integrated circuit as described in any one of Claims 9-12. In response to a physical downlink shared channel (PDSCH) transmission,
When the source uplink / downlink configuration is applied, the source uplink / downlink configuration defines a hybrid ARQ-ACK transmission up to a subframe N-1 including a subframe N-1, and the hybrid An ARQ-ACK transmission is related to the PDSCH transmission; and
Where the other predefined uplink / downlink configuration is applied, the other predefined uplink / downlink configuration defines a hybrid ARQ-ACK transmission between subframes N to N + 12 And if the hybrid ARQ-ACK transmission is related to the PDSCH transmission,
The mobile station only performs the hybrid ARQ-ACK transmission up to subframe N-1 including subframe N-1, or the mobile station transmits the hybrid ARQ-ACK transmission between subframes N to N + 12. Only do the
The integrated circuit as described in any one of Claims 9-13. Said another predefined uplink / downlink configuration is applied, and said another predefined uplink / downlink configuration is configured to support only uplink transmissions Define a hybrid ARQ-ACK transmission between subframes N to N + 12 for a frame, wherein the at least one subframe is within an interval from subframe N-11 to subframe N-1 including subframe N-1. If there is
The mobile station performs hybrid ARQ-ACK transmission related only to subframes configured to support downlink transmission during subframes N to N + 12, or the mobile station transmits the at least one Hybrid ARQ- containing predefined information about the at least one subframe configured to support only uplink transmission, signaling that one subframe supports only uplink transmission and is not related to PDSCH transmission ACK transmission,
The integrated circuit as described in any one of Claims 9-14.